323 001533 600_MPX 32_Revision_3.5_Reference_Manual_Volume_III_Apr90 600 MPX 32 Revision 3.5 Reference Manual Volume III Apr90
323-001533-600_MPX-32_Revision_3.5_Reference_Manual_Volume_III_Apr90 manual pdf -FilePursuit
323-001533-600_MPX-32_Revision_3.5_Reference_Manual_Volume_III_Apr90 323-001533-600_MPX-32_Revision_3.5_Reference_Manual_Volume_III_Apr90
User Manual: 323-001533-600_MPX-32_Revision_3.5_Reference_Manual_Volume_III_Apr90
Open the PDF directly: View PDF 
.
Page Count: 540
| Download | |
| Open PDF In Browser | View PDF |
MPX-32 ™
Installation and System Administration
C.,
./
Revision 3.5
Reference Manual Volume III
April 1990
323-001553-600
IIII~IIIIIIIIII 11111111111 11111 111111111111111 1111 111111111111111111111111
Limited Rights
o
This manual is supplied without representation or warranty of any kind. Encore
Computer Corporation therefore assumes no responsibility and shall have no liability of
any kind arising from the supply or use of this publication or any material contained
herein.
Proprietary Information
The information contained herein is proprietary to Encore Computer Corporation
and/or its vendors, and its use, disclosure, or duplication is subject to the restrictions
stated in the standard Encore Computer Corporation License terms and conditions or
the appropriate third-party sublicense agreement.
Restricted Rights
Use, duplication, or disclosure by the Government is subject to restrictions as set forth
in subdivision (c) (1) (ii) of the Rights in Technical Data and Computer Software clause
at 252.227.7013.
Encore Computer Corporation
6901 West Sunrise Boulevard
Fort Lauderdale, Florida 33313
TM
/
MPX-32 is a trademark of Encore Computer Corporation
® CONCEPT/32 is a registered trademark of Encore Computer Corporation
Copyright © 1990 by Encore Computer Corporation
ALL RIGHTS RESERVED
Printed in the U.S A.
o
History
The MPX-32 Release 3.0 Reference Manual, Publication Order Number
323·001550·000, was printed June, 1982.
Publication Order Number 323·001553·100, (Revision I, Release 3.2) was printed
June, 1983.
Publication Order Number 323·001553·200, (Revision 2, Release 3.2B) was printed
March, 1985.
Publication Order Number 323·001553.201, (Change 1 to Revision 2, Release 3.2C)
was printed December, 1985.
Publication Order Number 323·001553·300, (Revision 3, Release 3.3) was printed
December, 1986.
Publication Order Number 323·001553·400, (Revision 4, Release 3.4) was printed
January, 1988.
Publication Order Number 323·001553·500, (Revision 3.4U03) was printed October,
1989.
Publication Order Number 323·001553·600, (Revision 3.5) was printed April, 1990.
This manual contains the following pages:
Title page
Copyright page
iii/iv through xxiii/xxiv
1-1 through 1-2
2-1 through 2-27/2-28
3-1 through 3-5/3-6
4-1 through 4-9/4-10
5-1 through 5-5/5-6
6-1 through 6-4
7 -1 through 7-66
8-1 through 8-33/8-34
9-1 through 9-11/9-12
10-1 through 10-62
11-1 through 11-15/11-16
12-1 through 12-17/12-18
13-1 through 13-23/13-24
14-1 through 14-6
A-I through A-7/A-8
B-1 through B-42
C-l through C-32
0-1 through 0-2
E-l through E-2
F-l through F-2
G-l through G-2
H-l through H-2
1-1/1-2
J-l through J-2
K-l/K-2
L-l through L-79/L-80
GL-l through GL-I0
IN-I through IN-31/IN-32
c
iii/iv
Contents
Page
Documentation Conventions ....................................................................................xxi
1
Building and Maintaining the System
1.1
2
Installing a Starter System
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
(--~
3
Introduction ............................................................................................... 1-1
Introduction ............................................................................................... 2-1
Hardware Configuration ............................................................................ 2-1
The Master System Distribution Tape (SDT) .......................................... 2-2
2.3.1 Magnetic Tape ........................................................................... 2-10
2.3.2 Utility Tape ................................................................................ 2-10
Booting a System from the Master SDT ................................................ 2-12
2.4.1 Control Switches ....................................................................... 2-21
Philosophy of Bootstrapping .................................................................. .2-22
The System Builder ................................................................................. 2-23
Operating Under the Starter System ....................................................... 2-23
Restoring Utility Processors, Libraries, and Other Files ....................... .2-24
Example of First Use of Master SDT on User System .......................... 2-25
2.9.1 Using the Default Master SDT Image
on a CONCEPT 32/97 ............................................................. 2-25
2.9.2 Overriding the Default Image ................................................... 2-26
2.9.2.1 Selecting MSTREXT for a CONCEPT 32/97 ............ 2-26
2.9.2.2 Selecting MSTRALL for a CONCEPT 32/2000 ........ 2-27
2.9.2.3 Errors ............................................................................ 2-27
Building and Testing a System
3.1
3.2
3.3
3.4
3.5
Introduction ............................................................................................... 3-1
Building the SYSGEN Input Files ........................................................... .3-1
3.2.1 Building the Directive Input File ............................................... .3-1
3.2.2 Building the Object Input File ................................................... .3-1
3.2.3 The COMPRESS Task ............................................................... .3-2
Running SySGEN ..................................................................................... 3-3
Testing a SYSGENed System .................................................................. .3-4
Terminal Initialization and System Protection ........................................ .3-5
MPX-32 Reference Volume III
v
Contents
Page
4
Installing a User-Configured System
4.1
4.2
4.3
4.4
4.5
5
Online Restart
5.1
5.2
5.3
5.4
5.5
5.6
6
Introduction ............................................................................................... 6-1
Recovery from Disk at the Console .......................................................... 6-1
Errors During Start-up ............................................................................... 6-1
System Halt Analysis ................................................................................ 6-2
Automatic IPL ........................................................................................... 6-4
System Generation (SYSGEN)
7.1
7.2
7.3
7.4
7.5
7.6
vi
Introduction ............................................................................................... 5-1
Bootstrap Programs ...................................................................................5-1
TSM $RESTART Directive ..................................................................... .5-2
Precautions ................................................................................................5-4
Using $RESTART ..................................................................................... 5-4
Errors .........................................................................................................5-5
Recovering the System
6.1
6.2
6.3
6.4
6.5
7
Introduction ...............................................................................................4-1
Creating a User System Distribution Tape (SDT) .................................. .4-1
Installing a User System Distribution Tape (SDT) ................................. .4-3
Saving/Restoring System Processor and Utility Load Modules ............. .4-3
Booting a System from a User SDT ........................................................ .4-4
4.5.1 Example .......................................................................................4-9
Introduction ............................................................................................... 7-1
General Description ................................................................................... 7-1
SYSGEN Logical File Codes .................................................................... 7-2
7.3.1 LFC Summary ............................................................................. 7-3
Options ......................................................................................................7-3
Accessing SYSGEN .................................................................................. 7-4
SYSGEN Directives .................................................................................. 7-4
7.6.1 ACTIVATE Directive ............................................................... 7-10
7.6.2 AGE Directive ........................................................................... 7-10
7.6.3 ARTSIZE Directive ................................................................... 7-11
Contents
{"\
~J)
Contents
Page
7.6.4
7.6.5
7.6.6
7.6.7
7.6.8
7.6.9
7.6.10
7.6.11
7.6.12
7.6.13
7.6.14
7.6.15
7.6.16
7.6.17
7.6.18
7.6.19
7.6.20
7.6.21
7.6.22
7.6.23
7.6.24
7.6.25
7.6.26
7.6.27
7.6.28
7.6.29
7.6.30
7.6.31
7.6.32
7.6.33
7.6.34
7.6.35
BATCHMSG Directive .............................................................7-11
BATCHPRI Directive ................................................................7-11
BEGPGOUT Directive .............................................................. 7-12
CDOTS Directive ......................................................................7-12
/CHANNELS Directive .............................................................7-13
CMIMM Directive .....................................................................7-13
CMPMM Directive ....................................................................7-13
CONTROLLER Directive ......................................................... 7-13
DBGFlLE Directive ................................................................... 7-16
DEBUGTLC Directive .............................................................. 7-16
DELTA Directive ....................................................................... 7-17
DEMAND Directive ..................................................................7-17
DEVICE Directive ..................................................................... 7-18
7.6.16.1 DEVICE Syntax for Disks ..........................................7-19
7.6.16.2 DEVICE Syntax for Console,
Terminals and 8-Line Serial Printers ......................... 7-21
7.6.16.3 DEVICE Syntax for Tape Drives ............................... 7-23
7.6.16.4 DEVICE Syntax for lOP Printers
and Null Devices ........................................................7-25
DISP Directive ........................................................................... 7-26
DPTIMO Directive ....................................................................7-27
DPTRY Directive ....................................................................... 7-27
DTSAVE Directive .................................................................... 7-27
//END Directive ......................................................................... 7-28
ENDPGOUT Directive .............................................................. 7-28
EXTDMPX Directive ................................................................ 7-28
/FILES Directive ........................................................................7-30
FLTSIZE Directive .................................................................... 7-30
//HARDWARE Directive ..........................................................7-30
HELP Directive .......................................................................... 7-30
/INTERRUPTS Directive .......................................................... 7-31
IOQPOOL Directive .................................................................. 7-31
IPU Directive ............................................................................. 7-32
ITIM Directive ........................................................................... 7-32
ITLB Directive ...........................................................................7-32
JOBS Directive .......................................................................... 7-32
KTIMO Directive .......................................................................7-33
LOD Directive ............................................................................7-33
MPX-32 Reference Volume III
vii
Contents
Page
7.6.36
7.6.37
7.6.38
7.6.39
7.6.40
7.6.41
7.6.42
7.6.43
7.6.44
7.6.45
7.6.46
7.6.47
7.6.48
7.6.49
7.6.50
7.6.51
7.6.52
7.6.53
7.6.54
7.6.55
7.6.56
7.6.57
7.6.58
7.6.59
7.6.60
7.6.61
7.6.62
7.6.63
7.6.64
7.6.65
7.6.66
7.6.67
7.6.68
7.6.69
7.6.70
7.6.71
7.6.72
7.6.73
7.6.74
7.6.75
viii
LOGON Directive .....................................................................7-33
MACHINE Directive ................................................................7-34
MAPOUT Directive .................................................................. 7-35
MDT Directive ..........................................................................7-35
/MEMORY Directive ...............................................................7-35
MMSG Directive ......................................................................7-36
MNWI Directive ....................................................................... 7-36
MODE Directive ....................................................................... 7-36
MODULE Directive .................................................................7-37
/MODULES Directive ..............................................................7-38
MRUN Directive ....................................................................... 7-38
MSGPOOL Directive ...............................................................7-38
MTIM Directive ........................................................................ 7-39
NAME Directive ....................................................................... 7-39
NOANSI Directive ................................................................... 7-40
NOBASE Directive ................................................................... 7-40
NOCMS Directive .................................................................... 7-40
NODEMAND Directive ........................................................... 7-40
NOLACC Directive .................................................................. 7-41
NOMAPOUT Directive ............................................................7-41
NOSYSVOL Directive ............................................................. 7-41
NOTDEF Directive ................................................................... 7-41
NOTSMEXIT Directive ........................................................... 7-42
NTIM Directive ........................................................................7-42
OTHERS Directive ................................................................... 7-42
/OVERRIDE Directive .............................................................7-43
OWNER Directive ....................................................................7-43
OWNERNAME Directive ........................................................ 7-44
/pARAMETERS Directive ....................................................... 7-44
/pARTITION Directive ............................................................7-44
PASSWORD Directive ............................................................. 7-44
PATCH Directive ..................................................................... 7-45
PCHFILE Directive .................................................................. 7-45
POD Directive ........................................................................... 7-45
POOL Directive ........................................................................ 7-46
PRIORITY Directive ................................................................ 7-46
PROGRAM Directive ............................................................... 7-47
PROJECT Directive .................................................................. 7-48
RLWU Directive ....................................................................... 7-48
/RMSTABLS Directive ............................................................7-49
Contents
;l;
",-",-
Contents
(
....
Page
7.6.76
7.6.77
7.6.78
7.6.79
7.6.80
7.6.81
7.6.82
7.6.83
RMTSIZE Directive ...................................................................7-49
SAPASSWD Directive .............................................................. 7-49
/SECURITY Directive ...............................................................7-49
SEQUENCE Directive ...............................................................7-50
SGOSIZE Directive ...................................................................7-50
SHARE Directive .......................................................................7-51
SID Directive .............................................................................7-51
SIZE Directive ...........................................................................7-51
7.6.83.1 Original SIZE Directive Syntax ..............................7-52
7.6.83.2 Preferred SIZE Directive Syntax ............................7-55
7.6.83.3 Shadow Memory Error Messages ...........................7-56
7.6.83.3 Shared Memory Error Messages .............................7-57
7.6.84 SMD Directive ........................................................................... 7-57
7.6.85 //SOFTWARE Directive ............................................................7-57
7.6.86 SVC Directive ............................................................................ 7-58
7.6.87 SWAPDEV Directive ................................................................ 7-58
7.6.88 SWAPLIM Directive ................................................................. 7-59
7.6.89 SWAPSIZE Directive ................................................................7-59
7.6.90 SWP Directive ...........................................................................7-60
7.6.91 SYCSIZE Directive ................................................................... 7-60
7.6.92 SYMfAB Directive ...................................................................7-60
7.6.93 /SYSDEVS Directive .................................................................7-60
7.6.94 SYSMOD Directive ...................................................................7-61
7.6.95 SYSONLY Directive .................................................................7-61
7.6.96 SYSTEM Directive .................................................................... 7-61
7.6.97 SYSTRAP Directive ..................................................................7-62
7.6.98 {fABLES Directive ...................................................................7-62
7.6.99 TERMPRI Directive .................................................................. 7-62
7.6.100 TIMER Directive ......................................................................7-62
7.6.101 TITLE Directive ........................................................................7-63
7.6.102 TQFULL Directive .................................................................... 7-63
7.6.103 TQMIN Directive ......................................................................7-63
7.6.104 TRACE Directive ......................................................................7-64
7.6.105 {fRAPS Directive .....................................................................7-64
7.6.106 TSMEXIT Directive ..................................................................7-64
7.6.107 USERPROG Directive ..............................................................7-65
7.6.108 NP Directive .............................................................................7-65
7.6.109 VP Directive ..............................................................................7-65
7.6.110 VPID Directive ..........................................................................7-66
MPX-32 Reference Volume III
ix
Contents
~
Page
8
System Debugger
8.1
8.2
8.3
8.4
x
l:'~'
.. i
Introduction ............................................................................................... 8-1
Using the Debugger................................................................................... 8-2
8.2.1 Arithmetic and Special Operators ............................................... 8-2
8.2.2 Special Functions ......................................................................... 8-3
8.2.3 Execution Breakpoints .................................................................8-3
8.2.4 Debugger Bases ...........................................................................8-4
8.2.5 Base Characters ...........................................................................8-4
8.2.6 Operator Restrictions ................................................................... 8-5
8.2.7 Expressions ..................................................................................8-5
8.2.8 Registers ......................................................................................8-5
8.2.9 Indirection .................................................................................... 8-5
Accessing the Debugger ............................................................................ 8-6
Debugger Directives .................................................................................. 8-7
8.4.1 AB (Absolute) Directive ............................................................. 8-9
8.4.2 AD (Address) Directive ............................................................... 8-9
8.4.3 AR (Arithmetic) Directive ........................................................ 8-10
8.4.4 AS (Assemble Instruction) Directive ........................................8-10
8.4.5 BA (Base) Directive ..................................................................8-10
8.4.6 BR (Breakpoint) Directive ........................................................8-11
8.4.7 BY (Bye) Directive ................................................................... 8-11
8.4.8 CB (Change Base Register) Directive ...................................... 8-12
8.4.9 CD (Display Command List) Directive .................................... 8-12
8.4.10 CE (Zero Command List) Directive .........................................8-12
8.4.11 CH (Display Controller Definition Table Entry) Directive ..... 8-12
8.4.12 CL (Terminate Build Directive List Mode) Directive ............. 8-13
8.4.13 CM (Change Memory) Directive ............................................. 8-13
8.4.14 CO (Continue) Directive .......................................................... 8-13
8.4.15 CR (Change Register) Directive ............................................... 8-14
8.4.16 CS (Build Directive List) Directive ......................................... 8-14
8.4.17 CT (Continue then Terminate) Directive ................................. 8-14
8.4.18 CX (Execute Directive List) Directive ..................................... 8-14
8.4.19 DB (Display Base Register) Directive ..................................... 8-15
8.4.20 DE (Delete) Directive ............................................................... 8-15
8.4.21 DI (Display Instruction) Directive ........................................... 8-15
8.4.22 DM (Display Memory) Directive .................. ~ .......................... 8-15
8.4.23 DQ (Display Dispatch Queue Entry) Directive .......................8-16
8.4.24 DR (Display Register) Directive .............................................. 8-16
8.4.25 DS (Display Symbolic) Directive ............................................ 8-16
Contents
/
o
Contents
(-Page
8.4.26
8.4.27
8.4.28
8.4.29
8.4.30
8.4.31
8.4.32
8.4.33
8.4.34
8.4.35
8.4.36
8.4.37
8.4.38
8.4.39
8.4.40
8.4.41
8.4.42
(~~'-
8.4.43
8.4.44
8.4.45
8.4.46
8.4.47
8.4.48
8.4.49
8.4.50
8.4.51
8.4.52
8.4.53
8.4.54
8.4.55
8.4.56
8.4.57
8.5
System
8.5.1
8.5.2
8.5.3
8.5.4
DT (Display Event Trace) Directive ........................................ 8-17
DU (Dump) Directive ............................................................... 8-17
EC (Echo) Directive ................................................................. 8-17
ET (Enter Event Trace Point) Directive ................................... 8-17
GO (Go) Directive .................................................................... 8-18
HC (Display Dispatch Queue Head Cell) Directive ................ 8-18
LB (List Breakpoint) Directive ................................................ 8-19
LP (Line Printer) Directive ...................................................... 8-19
LT (List Mobile Event Trace Point) Directive ........................ 8-19
MR (Map Register) Directive .................................................. 8-19
MS (Modify CPU Scratchpad Location) Directive ................. 8-20
PD (Display Patch List) Directive ........................................... 8-20
PE (Zero Patch List) Directive ................................................. 8-20
PR (Terminate Build Patch List Mode) Directive ................... 8-21
PS (Program Status) Directive ................................................. 8-21
PT (Build Patch List) Directive ............................................... 8-21
PV (Convert Physical Address to Virtual Address)
Directive .................................................................................... 8-21
PX (Execute Patch List) Directive ........................................... 8-21
RB (Reset Bases) Directive ...................................................... 8-22
RE (Remap) Directive .............................................................. 8-22
RT (Remove Event Trace Point) Directive .............................. 8-22
SE (Search Equivalent) Directive ............................................. 8-23
SM (Set Mask) Directive .......................................................... 8-23
SP (Scratchpad Dump) Directive ............................................. 8-23
SY (Symbolic) Directive .......................................................... 8-23
TB (Trace Back) Directive ....................................................... 8-24
TE (Terminate) Directive ......................................................... 8-24
TR (Trace) Directive ................................................................ 8-24
TS (Trace Stop) Directive ........................................................ 8-25
TY (Terminal) Directive ........................................................... 8-25
UD (Display Unit Definition Table Entry) Directive .............. 8-25
VP (Convert Virtual Address to Physical Address)
Directive ....................................................................................8-26
Debugger Practice Debug Session ............................................. 8-26
Step One - Accessing the Debugger .........................................8-26
Step Two - Task Debugging with the System Debugger......... 8-27
Using the System Debugger to Display Memory ..................... 8-27
Using Debug to Display a Program .......................................... 8-29
MPX-32 Reference Volume III
xi
Contents
Page
8.6
8.7
9
Online System Patch Facility (J.lNIT)
9.1
9.2
9.3
9.4
9.5
9.6
9.7
10
Introduction ...............................................................................................9-1
9.1.1 Dedicated Names ......................................................................... 9-2
9.1.2 Conventions .................................................................................9-2
Patch Directives .........................................................................................9-3
9.2.1 /B (Define a Base Address) Directive .........................................9-3
9.2.2 IC (Change the Contents of a Memory Location) Directive ......9-3
9.2.3 /D (Define a Named Value) Directive ........................................9-4
9.2.4 IE (Exit) Directive ....................................................................... 9-4
9.2.5 IG (Go to the Patch Area from a Specified Memory Location)
Directive ...................................................................................... 9-5
9.2.6 10 (Select Patch Options) Directive ............................................ 9-5
9.2.7 /P (Define a Patch Area) Directive ............................................. 9-6
9.2.8 /R (Return from the Patch Area) Directive ................................. 9-6
9.2.9 IF, {f, IN (Conditional) Directives .............................................. 9-6
9.2.10 1$ (Enter a Value into the Patch Area) Directive ........................ 9-7
9.2.11 I; (Comments) Directive ..............................................................9-8
Entry Conditions .......................................................................................9-8
Exit Conditions .......................................................................................... 9-8
External References ................................................................................... 9-9
Examples ................................................................................................. 9-10
Automatic Mounting of Public Volumes ................................................ 9-11
System Administrator Services
10.1
10.2
xii
8.5.5 Summary .................................................................................... 8-31
Example of Directive List Use ............................................................... 8-32
Example of Patch List Use ..................................................................... 8-33
Introduction ............................................................................................. 10-1
M.KEY File ............................................................................................ 10-2
10.2.1 Using KEY ................................................................................. I0-3
10.2.2 Directives ................................................................................... 10-3
10.2.2.1 ADD Directive ........................................................... l0-4
10.2.2.2 CHANGE Directive ................................................... 10-7
10.2.2.3 DEFAULTS Directive ............................................... 10-8
10.2.2.4 DELETE Directive .................................................... 10-9
Contents
C
Contents
Page
c\
10.2.2.5 LOG Directive ........................................................... 10-9
10.2.2.6 NEWFILE Directive .................................................. 10-9
10.2.2.7 X Directive ............................................................... 10-10
10.2.3 Examples of Directive Usage .................................................. 10-10
10.3 M.PRJCT File ....................................................................................... 10-11
10.3 .1 Using the PROJECT Program ................................................. 10-11
10.3.2 Directives ................................................................................. 10-12
10.3.2.1 ADD Directive ........................................................... 10-12
10.3.2.2 CHANGE Directive ................................................... 10-13
10.3.2.3 DELETE Directive ..................................................... 10-13
10.3.2.4 LOG Directive ............................................................ 10-13
10.3.2.5 NEWFILE Directive .................................................. 10-14
10.3.2.6 X Directive ................................................................. 10-14
10.3.3 Examples of Directive Usage .................................................. 10-14
10.4 M.ACCNT File ..................................................................................... 10-15
10.5 M.CNTRL File ..................................................................................... 10-17
10.6 M.ERR File and xx.ERR Files ............................................................. 10-18
10.6.1 Creating xx.ERR File ............................................................... 10-18
10.7 TerminaljAUM/ACM Initialization (INIT) ......................................... 1O-19
10.7.1 The LOGONFLE ..................................................................... 10-20
10.7.2 Security Counters ..................................................................... 10-22
10.7.2.1 Logon Attempt Counter. .......................................... 10-22
10.7.2.2 Logon Timeout Counter .......................................... 10-23
10.7.2.3 Terminal Timeout Counter ...................................... 10-23
10.7.2.4 Security Counters Example ..................................... 10-24
10.7.3 ALIM Terminal Record Syntax and Defaults ......................... 10-25
10.7.3.1 AUM Initialization Format.. ................................... 10-26
10.7.4 ACMjMFP Controller Record Syntax and Defaults ............... 10-33
10.7.4.1 ACM/MFP Initialization Format.. ........................... 10-35
10.7.4.2 Example ................................................................... 10-37
10.7.4.3 True Full-Duplex Operation for the ACM .............. 1O-37
10.7.5 Sample LOGONFLE................................................................ 10-38
10.8 Using INIT ............................................................................................ 10-39
10.9 INIT Errors ........................................................................................... 10-39
10.10 System Console Messages .................................................................... 10-41
10.10.1 Information Messages ......................................................... 10-41
10.10.2 Action Messages .................................................................. 10-41
10.10.3 Terminal Messages .............................................................. 10-41
10.11 Floppy Disk Media Initialization (J.FORMF) ..................................... 10-42
MPX-32 Reference Volume '"
xiii
Contents
Page
10.12
10.13
10.14
10.15
10.16
10.17
10.18
10.19
10.20
10.21
M.MOUNT File ................................................................................... 10-43
Operator Intervention Inhibit ............................................................... l0-44
System Date/fime Backup Program (J.DTSAVE) ............................. IO-44
System Shutdown ................................................................................ 10-45
10.15.1 Using J.SHUTD ..................................................................... 10-45
10.15.2 Shutdown and Volume Cleanup ............................................ 10-46
10.15.3 SHUTDOWN Macro ............................................................. 10-46
10.15.4 Using SHUTDOWN .............................................................. 10-46
10.15.5 Modifying the SHUTDOWN Macro ..................................... 10-47
10.15.6 Error Messages ....................................................................... 10-48
Swap Scheduler Control Options ........................................................ 10-49
10.16.1 Swapper Algoritluns .............................................................. 10-50
10.16.2 Wait State Ordering ............................................................... 10-50
10.16.3 Wait State Swap-on Priority Only (SOPO) ........................... 10-51
10.16.4 Call Back Swap-on Priority Only (CB.SOPO) ..................... 10-51
10.16.5 User Set Swap-on Priority Only Flag (US.SOPO) ............... 10-51
10.16.6 User Set Swap Inhibit Flag (US.SWIF) ................................ 10-51
10.16.7 Swap Thrash Control ............................................................. 10-51
10.16.8 Task Group Out swap Limits ................................................. 10-52
10.16.8.1 Errors ................................................................... 10-53
Multiprocessor Recovery Task (J.UNLOCK) ..................................... 1O-53
Shadow Memory .................................................................................. 10-54
Error Messages .................................................................................... 10-57
Memory Disk ....................................................................................... l0-58
10.20.1 Memory Disk Configuration .................................................. 10-59
10.20.2 Memory Disk Usage .............................................................. 10-59
10.20.2.1 Formatting and Mounting a Memory Disk ......... l0-59
10.20.2.2 Accessing a Memory Disk .................................. l0-59
10.20.2.3 Dismounting a Memory Disk ............................. 10-59
10.20.3 Memory Disk Aborts and Errors ........................................... 10-59
10.20.3.1 Abort Cases ......................................................... 10-59
10.20.3.2 Errors ................................................................... 10-60
10.20.4 Memory Disk Save Task (J.MDSAVE) ................................ 10-60
10.20.5 Memory Disk Restore Task (J.MDREST) ............................ 10-61
Label ANSI Tape Utility (J.LABEL) .................................................. 1O-62
(
~~~
'It"J
",!
xiv
Contents
Contents
(
Page
11
Device Initializer/Loader (DEVINITL)
11.1
11.2
11.3
11.4
11.5
11.6
11.7
11.8
12
Introduction ............................................................................................. 11-1
Initialization Directive File .................................................................... 11-1
Finnware File ......................................................................................... 11-3
11.3.1 Loader Data Record Format.. .................................................. 11-5
Using DEVINITL ................................................................................... 11-6
DEVINITL Directives ............................................................................ 11-7
11.5.1 DEV_CNTRL Directive .......................................................... 11-8
11.5.2 DEVICE Directive ................................................................... 11-9
11.5.3 IDENT Directive ..................................................................... 11-9
11.5.4 OPTION Directive ................................................................. 11-10
1l.5.5 REREAD Directive ............................................................... 11-11
11.5.6 RETRY Directive ............................................................ :..... 11-11
1l.5.7 WCS_FILE Directive ............................................................ 11-12
Example Initialization Directive File ................................................... 11-12
Milestone Messages .............................................................................. 11-13
Error Conditions and Messages ........................................................... 11-13
1l.8.1 Initialization Directive File Errors ........................................ 11-13
11.8.2 Device Loading Errors .......................................................... 11-14
1l.8.3 Directive Parsing Errors ........................................................ 11-14
Alterable Control Store (ACS)
12.1
12.2
12.3
12.4
12.5
12.6
Introduction ............................................................................................. 12-1
LOADACS Directive File (M.ACS) ...................................................... 12-1
Finnware File ......................................................................................... 12-2
12.3.1 CONCEPT 32/67 Usage .......................................................... 12-2
12.3.2 Finnware File Record .............................................................. 12-2
LOADACS .............................................................................................. 12-4
DUMPACS ............................................................................................. 12-5
ACS Directives ....................................................................................... 12-5
12.6.1 CHECKSUM Directive ........................................................... 12-6
12.6.2 COMPARE Directive .............................................................. 12-6
12.6.3 COpy Directive ....................................................................... 12-7
12.6.4 DUMP Directive ...................................................................... 12-8
12.6.5 ENABLE Directive .................................................................. 12-8
12.6.6 EXIT Directive ........................................................................ 12-9
12.6.7 LOAD Directive ...................................................................... 12-9
MPX·32 Reference Volume III
xv
Contents
Page,-_~
12.7
12.8
13
Volume Formatter (J. VFMT)
13.1
13.2
13.3
13.4
13.5
13.6
13.7
13.8
13.9
13.10
13.11
13.12
13.13
13.14
13.15
13.16
xvi
12.6.8 MODE Directive .................................................................... 12-10
12.6.9 PATCH Directive .................................................................. 12-11
12.6.10 REVISION Directive ............................................................. 12-12
12.6.11 VERIFY Directive ................................................................. 12-13
Srunp1e M.ACS File ............................................................................. 12-13
Error Conditions and Messages ........................................................... 12-14
12.8.1 LOADACS Error Conditions and Messages ........................ 12-14
12.8.2 DUMPACS Error Conditions and Messages ........................ 12-16
Introduction ............................................................................................. 13-1
General Description ................................................................................ 13-1
Logical File Code Assignments ............................................................. 13-1
13.3.1 Audit Trail (SLO) ...................................................................... 13-1
13.3.2 Directive Input (SyC) ................................................................ 13-2
Using J.VFMf ........................................................................................ 13-2
13.4.1 Directive Syntax Rules .............................................................. 13-3
13.4.1.1 Verb .......................................................................... 13-3
13.4.1.2 Parruneters ................................................................. 13-3
13.4.1.3 Options ...................................................................... 13-3
13.4.2 Directive Line Continuation ...................................................... 13-3
13.4.3 The CONFIRM Parruneter ......................................................... 13-4
Accessing the Volume Formatter ........................................................... 13-4
Volume Formatter Directives ................................................................. 13-5
COpy Directive ...................................................................................... 13-5
EDITFMAP Directive ............................................................................ 13-7
EXIT Directive ....................................................................................... 13-9
FORMAT Directive ............................................................................... 13-9
INITIALIZE Directive ......................................................................... 13-12
NEWBOOT Directive .......................................................................... 13-16
REPLACE Directive ............................................................................ 13-17
J.VFMT Errors ..................................................................................... 13-18
Exrunp1es .............................................................................................. 13-18
Online Disk Media Management ........................................................ 13-19
13.16.1 Media Management Terminology ........................................... 13-19
13.16.2 Initializing Media .................................................................... 13-20
13.16.2.1 Disk I/O Caution During Initialization ................ .13-21
Contents
o
Contents
Page
13.16.3 Editing Media Flaw Data ........................................................ 13-21
13.16.3.1 Read-Only Mode ................................................. 13-21
13.16.3.2 No I/O Mode ....................................................... 13-22
13.16.4 Special Considerations During SDT Boot.. ............................ 13-22
13.16.5 Managing SCSI Disks ............................................................. 13-23
13.16.6 Media Flaw Map Fonnat ........................................................ 13-23
14
Volume Compress (J.DSCMP)
14.1
14.2
14.3
14.4
("
General Description ................................................................................ 14-1
14.1.1 Phase One ................................................................................ 14-1
14.1.2 Phase Two................................................................................ 14-1
14.1.3 Perfonnance ............................................................................. 14-2
Logical File Code Assignments ............................................................. 14-2
Using Volume Compress ....................................................................... 14-3
14.3.1 Disk Status Report ................................................................... 14-3
14.3.2 Segment Report ....................................................................... 14-3
14.3.3 TYP Codes ............................................................................... 14-5
Error Messages ....................................................................................... 14-6
A
MPX-32 Device Access ........................................................................................A-l
B
System Services Cross-Reference .................................................................B-l
C
MPX-32 Abort and Crash Codes ......................................................................C-l
D
Numerical Information .........................................................................................D-l
E
Powers of Integers .................................................................................................E-l
F
ASCII Interchange Code Set ...............................................................................F-l
G
IOP/MFP Panel Mode ............................................................................................G-l
H
Standard Date and Time Formats ....................................................................H-l
I
Compressed Source Format ...............................................................................I-l
j
MPX-32 Reference Volume III
xvii
Contents
Page
J
Map Block Address Assignments ....................................................................1-1
K
Control Switches ....................................................................................................K-l
L
Data Structures .......................................................................................................L-l
Glossary ...............................................................................................................................GL-l
Index .......................................................................................................................................IN-l
""
.,
-'.'
c···
xviii
Contents
(,":
List of Figures
Figure
1-1
MPX-32 Installation/Configuration Overview ..................................................... 1-2
2-1
Master System Distribution Tape Format ......................................................... 2-11
3-1
Testing a User-Configured System ..................................................................... .3-4
4-1
User System Distribution Tape Format ...............................................................4-2
5-1
Establishing a New Default System ....................................................................5-3
10-1
10-4
Shadow Memory Configuration - Single Processor/Single Region
of Shadow Memory .......................................................................................... 10-54
Shadow Memory Configuration - Two Processors/Single Region
of Shadow Memory .......................................................................................... 10-55
Shadow Memory Configuration - Two Processors/fwo Regions
of Shadow Memory .......................................................................................... 10-55
Memory Disk .................................................................................................... 10-61
11-1
Initialization Directive File Format ................................................................... 11-2
14-1
J.DSCMP Segment Report ................................................................................. 14-4
10-2
("~
Page
10-3
c
MPX-32 Reference Volume III
xix
List of Tables
Table
Page
2-1
Deliverable Software for MPX-32 ....................................................................... 2-3
7-1
7-2
MPX-32 Device Type Handlers .........................................................................7-15
Disk: Device Codes ............................................................................................. 7-21
10-1
10-2
Restricted Keywords .......................................................................................... 10-6
LOGONFLE Field Keywords .......................................................................... 10-21
11-1
Valid Control Record Types .............................................................................. 11-4
13-1
13-2
J.VFMT Logical File Code Assignments .......................................................... 13-2
Allocation Units ............................................................................................... 13-12
14-1
Volume Compress Logical File Code Assignments .......................................... 14-2
o
xx
Contents
Documentation Conventions
Conventions used in directive syntax, messages, and examples throughout the
MPX-32 documentation set are described below.
Messages and Examples
Text shown in this distinctive font indicates an actual representation of a
system message or an example of actual input and output. For example,
VOLUME MOUNT SUCCESSFUL
or
TSM>!ACTIVATE MYTASK
TSM>
Lowercase Italic Letters
In directive syntax, lowercase italic letters identify a generic element that must be
replaced with a value. For example,
$NOTE message
means replace message with the desired message. For example,
$NOTE 10/12/89 REV 3
In system messages, lowercase italic letters identify a variable element. For example,
**BREAK** ON: taskname
means a break occurred on the specified task.
Uppercase Letters
In directive syntax, uppercase letters specify the input required to execute that
directive. Uppercase bold letters indicate the minimum that must be entered. For
example,
$ASSIGN lfc TO resource
means enter $AS or $ASSIGN followed by a logical file code, followed by TO and a
resource specification. For example,
$AS OUT TO OUTFILE
In messages, uppercase letters specify status or information. For example,
TERMDEF HAS NOT BEEN INSTALLED
MPX-32 Reference Volume I
xxi
Documentation Conventions
o
Brackets []
An element inside brackets is optional. For example,
$CALL pathname [arg]
means supplying an argument (arg) is optional.
Multiple items listed within brackets means enter one of the options or none at all.
The choices are separated by a vertical line. For example,
$SHOW [CPUTIME IJOBS IUSERS]
means specify one of the listed parameters, or none of them to invoke the default.
Items in bracketS within encompassing brackets or braces can be specified only when
the other item is specified. For example,
BACKSPACE FIT..E [[FILES=] eols]
indicates if eols is supplied as a parameter, FIL= or FILES= can precede the value
specified.
Commas within brackets are required only if the bracketed element is specified. For
example,
LIST [taskname][,[ownername] [,pseudonym]]
indicates that the first comma is required only if ownername and/or pseudonym is
specified. The second comma is required only if pseudonym is specified.
Braces { }
Elements listed inside braces specify a required choice. Choices are separated by a
vertical line. Enter one of the arguments from the specified group. For example,
[BLOCKED={Y I N}]
means Y or N must be supplied when specifying the BLOCKED option.
Horizontal Ellipsis ...
The horizontal ellipsis indicates the previous element can be repeated. For example,
$0 EFM [par] [. par] ...
means one or more parameters (par) separated by commas can be entered.
o
xxii
Documentation Conventions
Documentation Conventions
Vertical Ellipsis
The vertical ellipsis indicates directives, parameters, or instructions have been omitted.
For example,
$DEFM SI,ASSEMBLE,NEW,OP
$IFA %OP ASSM
means one or more directives have been omitted between the $DEFM and $IFA
directives.
Parentheses ( )
In directive syntax, parentheses must be entered as shown. For example,
(value)
means enter the proper value enclosed in parentheses; for example, (234).
Special Key Designations
The following are used throughout the documentation to designate special keys:
C·
/'
or
control key
carriage return/enter key
tab key
break key
backspace key
delete key
When the key designation is used with another key, press and hold the control
key, then press the other key. For example,
c
means press and hold the control key, then press the c.
Change Bars
Change bars are vertical lines (I) appearing in the right-hand margin of the page for
your convenience in identifying the changes made in MPX-32 Revision 3.5.
When an entire chapter has been changed or added, change bars appear at the chapter
title only. When text within figures has changed, change bars appear only at the top
and bottom of the figure box.
c
MPX·32 Reference Volume I
xxiii/xxiv
()
o
1
Building and Maintaining the System
1.1
Introduction
MPX-32 uses system utilities such as the Volume Manager and Text Editor to provide
mechanisms for building and maintaining resident operating systems. A resident
system is configured by running the System Generator utility. SYSGEN. A tailored
system is configured by modifying the Master System Distribution Tape (SDT) and
SYSGEN file before installation. A System Debugger is supplied that can debug a
resident operating system or resident user-developed interrupt and device handlers.
This volume provides documentation on installation from a System Distribution Tape
(SDT) and Utility Tape. SYSGEN, online and lOP console restart capability. the
System Debugger. the System Patch facility. System Administrator Services. the
Device Initializer/Loader. the Alterable Control Store Load and Display utility, the
Volume Formatter. and Volume Compress.
The MPX-32 operating system supports floppy disk usage. All references to the
System Distribution Tape (SDT) apply whether the distribution medium is magnetic
tape or floppy disk.
Figure 1-1 provides an overview of installation and configuration as described in
Chapters 2 through 4 of this volume.
(
MPX-32 Reference Volume III
1-1
Building and Maintaining the System
o
MASTER
SOT
~
...
BUILD
NEWSDT
...
BOOT
SYSTEM
t
~
RESTART
TO TEST
SYSTEM
SYSINIT
INITIALIZES
MPX-32
ENVIRONMENT
•
t
...-
SOT
RUN
SYSGEN
RUN
VOLUME
FORMATTER
t
~
EDIT SYSGEN
CONFIGURATION
FILE
SYSTEM
MOUNT
SERVICE
t
~
VOLUME MANAGEFi
RESTORE
UNBUNDLED
SOFTWARE FILES
RUN
SWAPPER
t
~
UNBUNDLED
SOFTWARE
TAPE
VOLUME MANAGER
RESTORE
KEY LOAD
MODULES
...
R3010
Figure 1-1
MPX-32 Installation/Configuration Overview
1-2
Building and Maintaining the System
o
2
Installing a Starter System
2.1
Introduction
Starter systems are supplied on the Master System Distribution Tape (SDT). This
chapter describes the minimum hardware configuration supported by the starter system
and the format of the Master SDT. It also includes an example of booting the starter
system.
2.2 Hardware Configuration
The following hardware and logical addresses are used for installing the starter system
on a CONCEPT/32 computer:
Hardware
Software
(
128KW Memory
XIO magnetic tape
MFP SCSI tape
MFP/IOP console -orCONCEPT 32/2000
on-board CPU console
MFP/IOP line printer
Disk drive (XIO)
(Class F)
Channel
Subaddress
xxxx
xx
xx
7E40
7EFC
7E
7E
40
Fe
02FC
7EF8
02
7E
FC
F8
xxxx
xx
xx
User-definable addresses are indicated by x.
Only the system console is configured in the starter system. User terminals are
configured by the SYSGEN utility. Once terminals have been configured, they can be
initialized by the system module J.TINIT. If a terminal initialization file called
LOGONFLE has not yet been created, all terminals are marked online, but noted as
failed devices (dead terminals). Before LOGONFLE is created, all terminals have the
following defaults:
Wakeup Character - ?
Baud Rate - 9600
Parity - EVEN
Character Size - 7
ALIM Only - HALF DUPLEX
For details on creating a LOGONFLE file, see Chapter 10 of this volume.
MPX·32 Reference Volume III
2·1
Hardware Configuration
The following disks are supported by MPX-32 and can be used when booting from
the Master SDT:
Disk
80MB moving head disk - UDP/DPII
160MB moving head disk - UDP/DPII
300MB moving head disk - UDP/DPII
340MB moving head disk - UDP/DPII
600MB moving head disk - UDP/DPII
80MB cartridge module disk - HSDP
337MB moving head disk - HSDP
474MB moving head disk - HSDP
500MB moving head disk - HSDP
689MB moving head disk - HSDP
800MB moving head disk - HSDP
850MB moving head disk - HSDP
858MB moving head disk - HSDP
1230MB moving head disk - HSDP
150MB moving head disk - SCSI
300MB moving head disk - SCSI
700MB moving head disk - SCSI
Any other non-floppy disk
SYSGEN
Type Code
MH080
MHl60
MH300
MH340
MH600
ANY
ANY
ANY
ANY
ANY
ANY
ANY
ANY
ANY
ANY
ANY
ANY
ANY
o
J.VFMTOisk
Parameter
Type Code
DC0080
DC0160
DC0300
DC0340
DC0600
OP0080
OP0337
0P0474
OP05OO
OP0689
OP08oo
OP0850
OP0858
OP01230
SD0150
SD0300
S00700
NOT AVAILABLE
* Oisk code applies to both lOP disks and disk processors.
If a disk code is specified and a mismatch with the drive occurs, an error results. If
disk code ANY is specified with a nonfloppy disk, a mismatch error cannot occur
since the relevant operating system table entries are modified to reflect the drive.
2.3 The Master System Distribution Tape (SOT)
The system initialization (SYSINIT) process (see section 2.6, System Builder)
distinguishes between a Master and user SOT by the system name stored in the
communications region of the MPX-32 operating system (C.SYSTEM). Therefore,
the following file names are reserved for the system: MSTRALL; MSTREXT; and
MSTROUT.
When MSTRALL, MSTREXT, or MSTROUT is detected by SYSINIT, the
processing of the system images for a master SOT boot is performed. Therefore,
these files should not be modified.
Following the system images are a group of saved files. These files include all
essential load modules to support a fully operational MPX-32 system. Also included
are the object files required to SYSGEN an MPX-32 system tailored to individual
hardware and software requirements.
Figure 2-1 shows the format of the Master SOT. Table 2-1 lists the software included
on the Master SOT.
2-2
Installing a Starter System
o
The Master System Distribution Tape (SOT)
(
Table 2-1
Deliverable Software for MPX-32
Operating System Modules
The following modules are memory resident:
('
Source
File Name
Object
File Name
Program
Name
SH.ACBA
SH.ADA
SH.ALOC
OH.ACBA
OH.ADA*
OH.ALOC*
H.ACBA
H.ADA
H.ALOC
SH.BKDM
SH.DBUGI
OH.BKDM*
OH.DBUGI*
H.BKDM
H.DBUGI
SH.DBUG2
OH.DBUG2*
H.DBUG2
SH.DMPMT
SH.EXEC
SH.EXEC2
OH.DMPMT*
OH.EXEC*
OH.EXEC2*
H.DMPMT
H.EXEC
H.EXEC2
SH.EXEC3
SH.EXSUB
SH.FISE
SH.IOCS
SH.MDT
SH.MEMM
SH.MEMM2
SH.MONS
OH.EXEC3*
OH.EXSUB*
OH.FISE*
OH.lOCS*
OH.MDT*
OH.MEMM*
OH.MEMM2*
OH.MONS*
H.EXEC3
H.EXSUB
H.FISE
H.lOCS
H.MDT
H.MEMM
H.MEMM2
H.MONS
SH.MVMT
OH.MVMT*
H.MVMT
SH.PET
SH.PTRAC
SH.REMM
SH.REXS
SH.SINIT
SH.SURE
OH. PET **
OH.PTRAC*
OH.REMM*
OH.REXS*
OH.SINIT*
OH.SURE*
H.PET
H.PTRAC
H.REMM
H.REXS
H.SINIT
H.SURE
SH.SWAPR
SH.TAMM
SH.TDEF
SH.TSM
SH.VOMM
OH.SWAPR*
OH.TAMM*
OH.TDEF
OH.TSM*
OH.VOMM*
H.SWAPR
H.TAMM
H.DEF
H.TSM
H.VOMM
t
(~~,
Description
Vector Processor SVC
Aplex ADA Support
Resource Allocation (Compatible
Interface)
Blocked Data Management Module
Mapped Portion of System
Debugger(for resident O.S.)
Unmapped portion of System Debugger
(for resident O.S.)t
Stand-alone Dump Writer
Executive (CPU & IPU Support)
Optional Executive (CPU & IPU
DELTA Support)
Optional Executive (CPU Only)
Common Executive Subroutines
File System (Compatible Interface)
Input/Output Control System
Rapid File Access Module
Memory Management Module
Optional Memory Management Module
Monitor SeIVices (Compatible
Interface)
Multivolwne Magnetic Tape
Management
Performance Evaluation Module
PTRACE Module
Resource Management Module
Resident Executive SeIVices
System lnitializer
High Performance Suspend/Resume
Module
Swapper (Resident)
Task Management Module
Terminal Definition Module
Terminal Service Manager
Volume Management Module
Remains physically memory resident but is not included in logical address space as part of
the system map.
* These modules reside in directory OBJECT_OUT as well as OBJECT on the Master SDT.
** This module resides in directory PET on the Master SDT.
MPX-32 Reference Volume III
2-3
The Master System Distribution Tape (SOT)
-"
,'('.'.,->.P
I' '
Extended Operating System Modules
,
...
The following modules are Extended MPX-32 modules located in directory OBJECCE.
OH.ALOC
OH.EXSUB
OH.FISE
OH.MEMM
OH.MONS
OH.PTRAC
OH.REMM
OH.REXS
OH.TAMM
OH.TSM
OH.VOMM
Extended H.ALOC
Extended H.EXSUB
Extended H.FISE
Extended H.MEMM
Extended H.MONS
Extended H.PTRAC
Extended H.REMM
Extended H.REXS
Extended H. TAMM
Extended H. TSM
Extended H. VOMM
Interrupt and Trap Handlers
The following routines are memory resident:
Source
File Name
Object
File Name
Program
Name
SH.CALM
SH.CPU
OH.CALM*
OH.CPU*
H.CALM
H.CPU
SH.CPU2
OH.CPU2*
H.CPU2
SH.ICP
SH.IPOO
SH.IP02
SH.IP03
SH.IP04
SH.lP05
SH.IP06
SH.IP07
SH.lP08
SH.IP09
SH.IPOC
SH.IPOF
SH.IPIO
SH.IP13
SH.IPAS
SH.IPCL
SH.IPHT
SH.lPIT
SH.lPPF
SH.IPU
SH.lPUAS
SH.IPUIT
SH.IPVP
OH.ICP*
OH.IPOO*
OH.IP02*
OH.IP03*
OH.IP04*
OH.IP05*
OH.IP06*
OH.lP07*
OH.lP08*
OH.IP09*
OH.IPOC*
OH.lPOF*
OH.IPIO*
OH.lP 13 *
OH.IPAS*
OH.lPCL*
OH.IPHT*
OH.IPIT*
OH.IPPF*
OH.lPU*
OH.IPUAS*
OH.lPUIT*
OH.IPVP*
H.ICP
H.IPOO
H.IP02
H.IP03
H.IP04
H.lP05
H.lP06
H.IP07
H.IP08
H.lP09
H.lPOC
H.lPOF
H.lPlO
H.IP13
H.IPAS
H.IPCL
H.IPHT
H.IPIT
H.IPPF
H.IPU
H.IPUAS
H.IPUIT
H.IPVP
Description
Optional Calm Replacement SVC Trap Processor
IPU to CPU Trap Processor (IPU
Task Scheduler)
Optional IPU to CPU Trap Processor
(IPU Task Scheduler)
Indirectly Connected Interrupt Program
Power Fail Trap Processor
Memory Parity Trap Processor
Nonpresent Memory Trap Processor
Undefined Instruction Trap Processor
Privilege Violation Trap Processor
SVC Trap Processor
Machine Check Trap Processor
System Check Trap Processor
MAP Fault Trap Processor
Address Specification Trap Processor (32/87, 32/97)
Arithmetic Exception Trap Processor
Cache Memory Parity Error Trap Processor
Attention Interrupt Processor
System Auto-start Trap Processor
Real-time Clock Interrupt Processor
CPU Halt Trap Handler
Interval Timer Interrupt Processor
Page Fault Trap Processor
IPU Executive Trap Processor
IPU Power Up Auto Start Trap Processor
IPU Accounting Interval Timer Processor
Vector Processor Interrupt Handler
* These modules reside in directory OBJECT_OUT as well as OBJECT on the Master SDT.
2·4
Installing a Starter System
()
The Master System Distribution Tape (SOT)
(C
Device Handlers
The following handlers are memory resident:
(
Source
File Name
Object
File Name
Load
Module
Description
SH.ASMP
SH.BSMP
SH.CPMP
SH.CnaO
SH.DCSO
SH.DCXIO
SH.DPXIO
SH.F8XIO
SH.GPMCS
SH.HSDG
SH.IBLG
SH.lFXIO
SH.LPXIO
SH.MDXIO
SH.MTSCI
SH.MTXIO
SH.MUXO
SH.NUXIO
SH.SLMP
SH.XIOS
OH.ASMP
OH.BSMP
OH.CPMP
OH. CDaO *
OH.DCSCI*
OH.DCXIO*
OH.DPXIO*
OH.F8XIO*
OH.GPMCS
OH.HSDG*
OH.IBLG*
OH.IFXIO*
OH.LPXIO*
OH.MDXIO*
OH.MTSCI*
OH.MTXIO*
OH.MUXO
OH.NUXIO*
OH.SLMP
OH.XIOS*
H.ASMP
H.BSMP
H.CPMP
H.CDaO
H.DCSCI
H.DCXIO
H.DPXIO
H.F8XIO
H.GPMCS
H.HSDG
H.IBLG
H.IFXIO
H.LPXIO
H.MDXIO
H.MTSO
H.MTXIO
H.MUXO
H.NUXIO
H.SLMP
H.XIOS
ALIM (ASYNC) - GPMC
BLIM (BISYNC) - GPMC
Card Reader/punch - GPMC
lOP Console Terminal
MFP Disk Handler
XIO Disk Handler
HSDP Disk Handler
lOP 8-Line ASYNC (Full duplex support)
GPMC Subroutines
Generic High Speed Data (HSD)
Inter-Bus Link Handler
XIO Channel Interrupt Fielder
XIO Line Printer
XIO Memory Disk
MFP Tape Handler
XIO Magnetic Tape
GPMC Multiplexer
XIO Null Device
SLIM (Synchronous) - GPMC
XIO Common Subroutines
* These modules reside in directory OBJECT_OUT as well as OBJECT on the Master SDT.
Nonresident Routines
Source
File Name
Object
File Name
Load
Module
Description
SJ.ACCNT
SJ.ADMNT
SJ.AMOUNf
SJ.ASTAT
SJ.ATAPE
SJ.AUTO
SJ.AVOLl
SJ.AVOL2
SJ.COMPI
SJ.CRYPT
SJ.DECMP
OJ.ACCNf
OJ.ADMNf
OJ.AMOUNT
OJ.ASTAT
OJ.ATAPE
OJ.AUTO
OJ.AVOLl
OJ.AVOL2
OJ.COMPI
OJ.CRYPT
OJ.DECMP
J.ACCNf
ADMOUNf
AMOUNT
ASTAT
J.ATAPE
N/A
AVOLM
AVOLM
COMPRESS
N/A
N/A
Accounting Utility
Dismount ANSI Labeled Tape Utility
Mount ANSI Labeled Tape Utility
Display ANSI Labeled Tape Utility
ANSI Labeled Tape Processing Task
Auto Disk Geometry Subroutine
Log ANSI Labeled Tape Utility
Log ANSI Labeled Tape Utility
Object Module Concatenation Utility
ANSI Data Encryption Routine
Compressed File Read Subroutine
MPX-32 Reference Volume III
2-5
The Master System Distribution Tape (SOT)
0
Nonresident Routines (Cont.)
Source
FIle Name
Object
File Name
Load
Module
SJ.DEVL
OJ.DEVL
DEVINITL
SJ.DSCMP
SJ.DTSAVE
OJ.DSCMP
OJ.DTSAVE
J.DSCMP
J.DTSAVE
SJ.ENABLE
SJ.ERR
SJ.xx.ER
SJ.FORMF
SJ.FREAD
OJ.ENABLE
OJ.ERR
N/A
OJ.FORMF
OJ.FREAD
ENABLE
M.ERR
N/A
J.FORMF
N/A
SJ.HELP
SJ.HELPT
SJ.HLP
SJ.INIT
SJ.KEY
SJ.KEYWD
SJ.LABEL
SJ:UST
SJ.LOGCNT
SJ.LOGTIME
SJ.MDREST
SJ.MDSAVE
SJ.MDTI
SJ.MOUNT
SJ.OPCOM
SJ.PAUSE
SJ.PROJ
SJ.PSWD
SJ.REST
SJ.SHAD
SJ.SOEX
SJ.SOUT
SJ.SSIN
SJ.SSIN
SJ.SWAPR1
SJ.SWAPR2
SJ.TOEFI
OJ.HELP
OJ.HELPT
OJ.ffi.P
OJ.INIT
OJ.KEY
OJ.KEYWD
OJ.LABEL
OJ.UST
OJ.LOGCNT
OJ.LOGTIME
OJ.MDREST
OJ.MDSAVE
OJ.MDTI
OJ.MOUNT
OJ.OPCOM
OJ.PAUSE
OJ.PROJ
OJ.PSWD
OJ.REST
OJ.SHAD
OJ.SOEX
OJ.SOUT
OJ.SSIN
OJ.SSIN
OJ.SWAPRI
OJ.SWAPR2
OJ.TOEFI
HELP
HELPT
J.HLP
J.INIT
KEY
KEYWORD
J.LABEL
LIST
LOGCNT
LOGTIME
J.MDREST
J.MDSAVE
J.MDTI
J.MOUNT
OPCOM
PAUSE
J.PRJCT
PASSWORD
RESTART
J.SHAD
J.SOEX
J.SOUT
J.SSINl
J.SSIN2
J.SWAPR
J.SWAPR
J.TOEFI
SJ.TERMOUT
OJ.TERMOUT
TERMOUT
Description
Write Control Storage (WCS)
Initializer
Disk Compress Module
Auto Date and Time Update for
Mounted Volumes
Terminal Online Task (SA only)
MPX-32 Abort Code Module
Sample Source for Error File
Format Floppy Formatter Program
Read Subroutine for Key and
Project
Help Service
Help Translator
Help Load Module
System Initializer
M.KEY FIle Editor
User Key Task
Label ANSI Tape Utility
List File Utility
Terminal Logon Counter Task
Terminal Logon Timer Task
Memory Disk Restore Task
Memory Disk Save Task
MDT Initialization Task
System Mount Service
Operator Communications
Pause Task
Project Accounting Utility
User Password Task
On-line Restart
Shadow Memory RRS Utility
Output Spooling Executive
Output Spooler
Input Spooling - Files
Input Spooling - Devices
Nonresident Swapper (code)
Nonresident Swapper (parameters)
Terminal Definition
Initialization Task
Terminal Session Timer Task
(-"\
\0
o
2-6
Installing a Staner System
The Master System Distribution Tape (SOT)
(-Nonresident Routines (Cont.)
Source
File Name
Object
File Name
Load
Module
SJ.TINIT
SJ.TSET
SJ.TSM
SJ.UNLCK
SJ.UFDPT
SJ.VFMT
SJ.VPRE
OJ.TINIT
OJ.TSET
OJ.TSM
OJ.UNLCK
OJ.UPDPT
OJ.VFMT
N/A
J.TINIT
J.TSET
J.TSM
J.UNLOCK
N/A
J.VFMT
N/A
SORT. MERGE
FVP**
OJ.SORT.MERGE
N/A**
FSORT2
VOLMGR
Description
Terminal Initializer
Set Terminal Type Utility
Terminal Service Monitor
Dual Port Unlock Utility
V olume Formatter Disk Parameter Table
V olume Formatter
V olume Formatter and Volume
Manager PRE File
Sort/Merge *
Volume Manager **
* Directory SORT. MERGE contains the source file, SOR.SRC, used to create the object
used to build the sort/merge library and FSORT2.
** Directory FUP contains all source files used to create the object library FUP.LIB arid
object directory FUP.DIR. These are used for building VOLMGR.
SYSGEN
The following are SYSGEN load module components:
Source
File Name
Object
File Name
Description
SJ.FMTIO
SJ.OBUTL
SJ.PSCAN
SJ.SDBUG
SJ.SEXEC
SJ.SGINI
SJ.SPHOI
SJ.SPH02
SJ.SPH03
SJ.SPH04
SJ.SSCAN
SJ.STACK
SJ.STBLS
OJ.FMTIO
OJ.OBUTL
OJ.PSCAN
OJ.SDBUG
OJ.SEXEC
OJ.SGINI
OJ.SPHOI
OJ.SPH02
OJ.SPH03
OJ.SPH04
OJ.SSCAN
OJ. STACK
OJ.STBLS
SYSGEN Formatter
Object Processor
SYSGEN Scanner
SYSGEN Debugger
Executive (Root Segment)
Initialization Overlay
Phase 1
Phase 2
Phase 3
Phase 4
Keyword Scanner
SYSGEN Stack
Device Type Table
MPX-32 Reference Volume III
2-7
The Master System Distribution Tape (SOT)
The following are SYSGEN files:
File Name
Description
MSTRALL
MSTRALLS
MSTRALLD
MSTREXT
MSTREXTS
MSTREXTD
MSTROUT
MSTROUTS
MSTROUTD
OH.32
OH.32_E
OH.32_0UT
SG.32
JH.32
JH.32_E
JH.32_0UT
System Image File for all CONCEPT 32/xx machines
System Symbol Table File for all CONCEPT 32/xx machines
Directive File for all CONCEPT 32/xx machines
System Image File for extended-mode image
System Symbol Table File for extended-mode image
Directive File for extended-mode image
Mapped Out System Image File for CONCEPT 32/2000
Mapped Out System Symbol Table File for CONCEPT 32/2000
Mapped Out Directive File for 32/2000
Compressed System Object
Extended Compressed System Object
Mapped Out Compressed System Object
Sample SYSGEN Macro/Directives
COMPRESS Input Directives
Extended COMPRESS Input Directives
Mapped Out COMPRESS Input Directives
Miscellaneous
The following are Help text files:
File Name
Description
DS.HLP
GMPX.HLP
PROC.HLP
SAT.HLP
SVC.HLP
TOP.HLP
Data Structures
General MPX Help
Processors
System Administrator Tools
SVC Calls
Top Level Menu
The following are macro library files:
File Name
Description
M.EQUATESX32
M.MACLIB
M.MPXMAC
M.OSEQUATESX32
M.SERVICESX32
SM.EQUATESX32
SM.MPXMC
SM.OSEQUATESX32
SM.RTMMC
SM.SERVICESX32
X32 Macros for user data structures
MPX/RTM Macro Library
MPX-32 Macro Library
X32 macros for system data structures
X32 macros for system services
Source used to load M.EQUATESX32
Source used to load M.MPXMAC (MPX-32 macros)
Source used to load M.OSEQUATESX32
Source used to load M.MACLIB (RTM compatible macro library)
Source used to load M.SERVICESX32
()
2-8
Installing a Starter System
The Master System Distribution Tape (SOT)
(~
The following are subroutine library files.
File Name
Description
MPXDIR
MPXLIB
FUP.DIR
FUP.LIB
SORT.DIR
SORT.LIB
MPX-32 System Subroutine Directory (null)
MPX-32 System Subroutine Library (null)
File Utility Program (VOLMGR) Subroutine Directory
File Utility Program Library
Sort/Merge Directory
Sort/Merge Library
The following are PRE files:
File Name
Description
MPX_EXT
MPX_NON
MPX_OUT
MPXPRE
PRE File for
PRE File for
PRE File for
Default PRE
assembly of Extended MPX-32 modules
assembly of Nonextended MPX-32 modules
assembly of mapped out modules (CONCEPT 32/2000 only)
File for macro assembler
The following are Job Control Language (JCL) files:
File Name
Description
JJ.A.HLP
JJ.A.NON
JJ.A.ONE
JJ.A.RSI
JJ.A.RS2
JJ.A.RS3
JJ.A.SGN
JJ.A.SWP
JJ.A.TDI
JJ.A.VOL
JJ.B.LIB
JJ.B.MAC
JJ.C.VOL
JJ.COMPR
JJ.ID
JCL to assemble/catalog online help modules
JCL to assemble/catalog nonresident modules
JCL to assemble a component of VOLMGR
JCL to assemble resident modules (Services/processors)
JCL to assemble resident modules (Interrupts/I'raps)
JCL to assemble resident modules (Device Handlers)
JCL to assemble/catalog SYSGEN
JCL to create swapper load module (J.SWAPR)
JCL to assemble/catalog J.TOEFI
JCL to batch all assemblies for components of VOLMGR
JCL to create/build the null MPXLIB/MPXDIR
JCL to create/build macro libraries M.MPXMAC,M.MACLIB
JCL to build VOLMGR
JCL to create/load COMPRESSed files Object Module
JCL to run SEARCHER to create MPX-32 ID (time/date and program ID
information)
JCL to assemble/catalog M.ERR (MPX-32 Revision 3.x Aborts)
JCL to create Master System Images
JCL to build Sort/Merge
JCL to assemble/catalog SJ.xx.ER (User Aborts)
JCL for building MPX-32 Rev. 3 by processing JCL files
JCL to build the Master SDT
JCL to build the Master Source Tape
JJ.M.ERR
JJ.MSTR
JJ.SORT
JJ.XX.ER
BATCH.OS
MSTRSDT
MSTRSRCE
MPX-32 Reference Volume III
2-9
The Master System Distribution Tape (SOT)
o
Support Files
The following are support files:
File Name
Description
LOGONFLE
M.CNTRL
M.KEY
M.PATCH
MPX.PRO
MPX.PRO.NOTDEF
MPX.PRO.TDEF
TDEFLIST
TERMDEF
VOLM
Tenninal initialization file
System Control File
Key file
Patch file
Tenninal Profile
Tenninal Profile when TERMDEF file is not installed
Tenninal Profile when TERMDEF file is installed
List of supported TERMDEF functions
Tenninal definition file
Macro for invoking VOLMGR
Directories
FUP
OBJECT
OBJECT_E
OBJECT_OUT
PET
SORT. MERGE
File Utility Program containing source files for creating libraries used to build
VOLMGR
Object files
Object modules for extended MPX-32
Object modules for mapped out (CONCEPT 32/2000 only)
Perfonnance Evaluation Tool
Sort/Merge
2.3.1 Magnetic Tape
The fonnat of the magnetic tape Master SDT is similiar to the User SDT. Both
contain a tape boot loader followed by an MPX-32 image. The master tape, however,
contains three MPX-32 images instead of one. The three images are:
• MSTRALL -
default image for all CONCEPT 32/xx computers
• MSTREXT - extended-mode image
• MSTROUT - default image for CONCEPT 32/2000 computers
When building the Master SDT, the Volume Manager sets a flag enabling the tape
boot loader to recognize a master boot and skip to the proper image for the
appropriate CPU. If an image other than the default is desired, it can be selected
using console panel mode commands. (See section 2.4, Booting a System from the
Master SDT, in this chapter.)
2.3.2 Utility Tape
The utilities are contained on a separate tape, as an unbundled product, as shown in
Figure 2-1. After the SDT has been restored, restore the desired utilities before exiting
the Volume Manager.
o
2-10
Installing a Staner System
The Master System Distribution Tape (SOT)
MAGNETIC TAPE
BOOT LOADER
MPX-32
IMAGE 1
EOF
MPX-32
IMAGE 2
EOF
MPX-32
IMAGE 3
EOF
J.VFMT
EOF
J.MOUNT
J.SWAPR
VOLMGR
EOF
EOF
*
MASTERSDT
SAVED FILES
SEPARATE UTILITY
TAPE
*DOUBLE EOF REQUIRED BY VOLMGR
R3020
Figure 2-1
Master System Distribution Tape Format
MPX·32 Reference Volume III
2·11
Booting a System from the Master SOT
2.4 Booting a System from the Master SOT
Mount the Master SDT on a tape drive and note its address. If the system console is
connected to an lOP or MFP controller, the controller must be configured to channel
X'7E'. If the system console is to be connected to the CONCEPT 32/2000 CPU's
on-board F-class controller, it is recommended that the controller be configured to
channel X'02'.
To boot a CONCEPT/32 computer with the system console connected to an lOP or
MFP controller, perform the following steps on the system console:
Enter panel mode by typing:
System response:
Halt the system by typing:
System response:
Reset the system by typing:
System response:
Clear memory by typing:
System response:
@@P
II
IIHALT
II
IIRST
II
IICLE
II
Skip the next step if you wish to boot
the default system image.
Override the default system image by typing:
IIGPRO=n
n = 1 to select MSTRALL
(non-extended MPX-32) image
n = 2 to select MSTREXT
(extended MPX-32) image
System response:
II
Load the system by typing:
I I IP L=address of tape unit
(Skip the following instructions regarding booting on a windowing console and
continue booting after the system has been loaded.)
To boot a CONCEPT 32/2000 computer with the system console connected to the
F-class I/O channel on the CPU, perform the following steps on the windowing
console:
Enter panel mode by activating the Panel Window on the windowing console.
System Response: The Panel Window drag bars become solid.
Halt the system, if not already halted, by selecting the halt command from
the Panel Window menu.
System Response: The Node Status Window indicates that the CPU is halted.
Reset the system by selecting the reset command from the Panel Window
menu.
System Response: The CPU registers and PSD displayed in the Panel
Window are cleared.
2-12
Installing a Starter System
o
Booting a System from the Master SOT
Clear memory by selecting the clear mem command from the Panel
Window menu.
System Response: The mouse pointer changes to wait while memory is
being cleared.
Override the default system image by changing the contents of GPRO to:
00000001 to select MSTRALL (non-extended MPX-32)
gprO:
image.
00000002 to select MSTREXT (extended MPX-32) image.
gprO:
Load the system by selecting ipl from the Panel Window menu.
System Response: A sub-window prompting for the address of the tape unit
appears.
Enter the tape unit's address in the sub-window.
The boot loader on the Master SDT begins execution. It selects and loads the proper
system image for the CPU to be used, and passes control to SYSINIT, the system
initialization program. The following prompts are displayed on the system console:
»
(
This prompt is displayed whenever the system debugger is configured in the
system image being loaded. The system debugger is configured in all Master
SDT images. Enter TE to continue normal system operation. When upgrading
to a new revision of MPX-32, terminal initialization is inhibited at this point
by responding to the system debugger as follows:
»
»
CM 780, 10000000
TE
This sets control switch 3.
BOOT FROM A SCSI TAPE?
(REPLY Y OR N) :
Enter Y if booting from a SCSI tape drive.
MPX-32 MASTER SDT FOR CONCEPT 32/n COMPUTERS
nis 67fora32/67,nis 87 fora 32/87, 97 fora 32/97, or 2000 fora
32/2000.
ENTER SYSTEM DEVICE CHANNEL AND SUBADDRESS:
Enter the channel and subaddress of the desired disk drive (for example,
0800) as the logical device address where MPX-32 is to be installed. If an
invalid system device address is entered, the following message appears:
CANNOT FIND PROPER DISC UDT ...
SYSINIT ABORT RECEIVER ENTERED ...
»
MPX-32 Reference Volume III
2-13
Booting a System from the Master SOT
ENTER DISC CONTROLLER TYPE: XIO (UDP OR DP II), HSDP, OR
MFP (REPLY X, H, OR M) :
Enter the appropriate response for this disk prompt. If an incorrect value is
entered, J.VFMT will detect the error during execution (see below) and abort.
MEMORY INITIALIZATION STARTED ....... .
MEMORY INITIALIZATION COMPLETE ...... .
ENTER DATE AND TIME:
Enter the date and time using the following syntax:
date,hh[:]mn[:ss][, [D) [,Tz=num]]
date
is the current date in one of the following formats:
mm/dd/yy
dd-mm-yy
ddmmmyy
hh
mn
ss
D
TZ=num
where mm is the 2-digit decimal month, dd is the 2-digit
decimal day, yy is the 2-digit decimal year, and mmm is the
3-ASCII-character month abbreviation.
is the 2-digit decimal hour (24 hour time)
is the 2-digit decimal minute
is the 2-digit decimal second. If the colon between hh and
mm is omitted. this parameter is ignored.
indicates daylight savings time. Specifying this field causes
the internally stored binary time to be adjusted by one hour.
allows the internal binary time to be biased by num hours.
The value of num can be positive or negative. This field
allows file times to be kept according to a given standard
while the displayed time (see OPCOM TIME directive) is the
correct local time.
Examples:
06/16/81,08:45:00
06/09/81,11:20:00
14-06-81,13:00:00
03NOV81,09:25:00
08/29/81,10:33,D
15-04-81,19:15:00,D,TZ=-3
05MAY81,16:15"TZ=10
TASK LOADING FROM TAPE STARTED .....
Ci
~··),,·
/'", ,
"
2-14
Installing a Starter System
,;j
Booting a System from the Master SOT
(
FMT>
This is the Volume Fonnatter prompt. The Volume Fonnatter builds the
on-disk structures required by the MPX-32 file system.
Important: See Chapter 13 of this volume for more infonnation on the
Volume Fonnatter. Many important user-selected parameters are only
available at this point and cannot be changed later without removal of all user
data on the disk.
If you are installing MPX-32 for the first time, and targeting a new disk media
that has never been media verified, follow step Abelow. As an alternative to
step A (INITIALIZE) you may choose to run the Level n Diagnostic Media
Verification program (HSDP or UOP/DP II controllers) or the Level II
Diagnostic program (MFP SCSI) before installing the SOT. The instructions
in step A can also be used to reconfigure structures built by the INITIALIZE
directive on a currently fonnatted disk.
If you are installing MPX-32 for the first time and targeting disk media that
has been media verified, or if you are upgrading MPX-32, but wish to
reconfigure currently fonnatted disk structures built by the FORMAT .directive,
follow step B below.
If you are only upgrading MPX-32 with a Master SOT tape, follow step C
below.
(\
Warning: Selecting steps A or B below will result in the removal of all user
data on the disk. Be sure all important files have been saved to tape or another
disk.
A. The minimum response required at this prompt is:
FMT> INITIALIZE DEVICE=devmnc DISC=dcode
devmnc
dcode
is a 6-character device mnemonic (2-character device type
mnemonic, 2-digit hexadecimal channel number, 2-digit
hexadecimal device subaddress); for example, DM0800
or DM0402.
dcode is the disk storage device type code. Refer to Note
I in the INITIALIZE directive section of Chapter 13 for a
list of disk type codes.
If desired, other INITIALIZE command parameters may also be
included on the command line. The INCLUDE parameter must not be
used. If the FMAP parameter is specified, the line printer must be
online.
This command causes the hardware-required disk structures (e.g.,
track and sector labels) to be written to the disk. This is in
preparation for item B below.
At the completion of the INITIALIZE command, FMT> appears
again. When this prompt appears, follow step B below.
MPX-32 Reference Volume III
2-15
Booting a System from the Master SDT
B. The minimum response required at this prompt is:
FMT> FORMAT DEVICE=devmnc VOLUME=volname
devmnc
volname
o
is a 6-character device mnemonic (2-character device type
mnemonic, 2-digit hexadecimal channel number, 2-digit
hexadecimal device subaddress); for example, DM0800
or DF0802.
is a 1- to 16-character volume name. Valid characters are
A through Z, 0 to 9, dot (.) and underscore C).
If desired, other FORMAT command parameters may also be included
on the command line, for example, ACCESS=, CONFIRM=,
MAXRES=. The IMAGE parameter must not be used. If the
BOOTFILE parameter is used, the only acceptable values are OLD
and NEW.
This command causes the volume structures required by the MPX-32
file system to be written to the disk, the selected image on the Master
SOT to be the default image, and the disk bootstrap to be updated.
Volume Formatter will exit upon completion of this command.
C. Enter only the following at the Volume Formatter prompt:
FMT> REPLACE DEVICE=devmnc VOLUME=volname
devmnc
volname
is a 6-character device mnemonic (2-character device type
mnemonic, 2-digit hexadecimal channel number, 2-digit
hexadecimal device subaddress); for example, DM0800
or DM0402.
is a 1- to 16-character volume name. Valid characters are
A through Z, 0 to 9, dot (.) and underscore C).
This command cause the image on the Master SOT to be the new
default image and the disk bootstrap to be updated. Volume Formatter
will exit upon succesfull completion of this command.
Note:
If the Volume Formatter determines that volume structures exist on the
specified disk device, this interactive prompt is issued:
DESTROY OPTION NOT ENABLED FOR FORMATTED VOLUME,
VOLUME NAME=volname
CONTINUE - yiN?
where volname is the current volume name of the specified disk device.
Enter Y to continue. If you select N, you must rewind the SOT tape
and start the boot procedure anew. Entering DESTROY=Y on the
command line for steps A or B will prevent this prompt from appearing.
This is not an option for step C.
For all steps (A, B, or C), if the CONFIRM=N parameter is not entered
at the command line, an interactive prompt to continue is written to the
screen. You may make changes in the displayed parameters or enter
CONFIRM=N to continue.
2-16
Installing a Starter System
o
Booting a System from the Master SOT
(
Important: If any error messages are issued by Volume Formatter
followed by an abort, take corrective action, rewind the SDT tape, and
start the boot procedure anew.
J. MOUNT - MOUNTING VOLUME vo/name ON devnmc
If volume clean up is required, the following message is issued.
J. MOUNT - VOLUME CLEAN UP ON vo/name
VOL>
This is the Volume Manager prompt. When installing MPX-32 for the first
time (e.g. steps A and B or step B above were performed), the system
directory must be created before files on the SOT can be restored. Only the
system directory is required. OBJECT, SOURCE, HELP, SORT.MERGE,
BUILO.JCL, FUP, PET, REDUCE, MIPS.SRC, CSWI, INTR, and OEMO are
optional and do not have to be created by the user.
The minimum response required at the Volume Manager prompt is:
VOL> CREATE D SYSTEM ENTRIES=nn
Note:
The number of entries allowed in the SYSTEM directory (nn above)
must be greater than 300 to accommodate all system files on the
Master SOT.
If desired, other parameters such as OWNER=, PROJECTGROUP=, and
ACCESS= may also be included with this directive.
Saved files on the Master SOT can now be restored. Restore the first three
images using the RESTORE directive. Then exit Volume Manager.
VOL> RESTORE VOLUME=SYSTEM
(information files and INSTALLSOT)
VOL> RESTORE VOLUME=SYSTEM
(non-resident module)
VOL> RESTORE VOLUME=SYSTEM
(non-resident module)
VOL> EXIT
A series of messages -- DISC FFFF MARKED OFF LINE -- are now
displayed.
If J.TINIT is restored from the Master SOT, one of these initialization
messages is displayed. The one that is displayed depends on whether the
system file, LOGONFLE, exists or was restored on the currently mounted
system volume. See Chapter 10 of this volume for details on how to build
LOGONFLE.
MPX·32 Reference Volume '"
2·17
Booting a System from the Master SOT
o
INITIALIZATION COMPLETE
TERMINAL SETUP COMPLETE
(or)
INITIALIZATION COMPLETE
M.ASSN DENIAL, NO LOGON FILE, DEFAULT USED
TERMINAL SETUP COMPLETE
PRESS ATTENTION FOR TSM
Upon entering @@A for attention, a prompt is issued to enter a 1- to 8character logon owner name and a 1- to 8-character logon key. The following
characters cannot be used in owner names or keys: blanks, commas,
semicolons, equal signs, line feeds, dollar signs, exclamation points, percent
signs, and left or right parentheses. After entering a valid owner name and
key, the TSM prompt is displayed and any valid TSM directive can be entered.
If a valid M.KEY file does not exist at logon, the following message is
displayed prior to the TSM> prompt:
UNABLE TO ESTABLISH A DEFAULT WORKING DIRECTORY
YOUR CURRENT WORKING DIRECTORY IS @SYSTEM(SYSTEM)
Initiate the Master SOT tape installation macro by typing INSTALLSDT.
TSM> INSTALLSDT
This macro will restore the other images on the Master SOT. Through a series
of interactive prompts, the macro allows you to choose which Master SOT
images to restore, or simply restore all of them.
WOULD YOU LIKE A HARDCOPY OF THE SDT.CONTENTS FILE
TO ASSIST YOU IN THIS INSTALLATION ? (YIN):
Enter Y to print a copy of the SOT. CONTENTS file.
IS THIS A COLD START (YIN)
:
For a cold start, enter Y. The following prompt will appear:
ENTER LINE PRINTER DEVICE ADDRESS (LP7EF8)
Respond to this prompt by typing the address of the line printer device.
For a warm start, enter N.
The next prompt provides the option of restoring the entire Master SOT tape.
DO YOU WISH TO INSTALL THE ENTIRE TAPE ? (YIN)
If you wish to restore every image on the Master SOT (except the first three),
enter Y and follow step A below. If you wish to restore some images on the
Master SOT, but not others, enter N and follow step B below.
A. After Y is entered, the following prompts appear.
ENTER MAGNETIC TAPE DEVICE ADDRESS (M91000)
Enter the address at which the Master SOT is mounted.
2-18
Installing a Starter System
o
Booting a System from the Master SOT
(
ENTER THE VOLUME NAME WHICH THE SDT WILL BE
INSTALLED ON :
Enter S YSTEM here.
MOUNT MESSAGES ARE NOW TURNED OFF UNTIL
INSTALLATION HAS COMPLETED.
As each image is restored, a message appears stating that the image
has been restored. After the process of restoring the Master SOT
images is complete, the following appears:
THE SDT HAS BEEN INSTALLED ACCORDING TO THE
INTSTRUCTIONS SUPPLIED BY THE USER.
The INSTALLSOT macro then rewinds the Master SOT tape, issues
the following message, and exits:
MOUNT MESSAGES ARE NOW TURNED BACK ON
B. After N is entered, a series of prompts appears asking which images
are to be restored. Each prompt lists a group of images and asks if
these images should be restored. These prompts appear in the order
shown below, grouping the images as follows:
• required images (nonresident routines, COMPRESS object, resident
services and processor objects, resident interrupt and trap objects,
resident device handler objects, HELP text files, macro libraries.
PRE files, macros, TERMDEF, and SYSGEN files)
•
•
•
•
•
•
•
extended MPX-32 image
mapped-out images
sort merge files
unsupported load modules and source images
patch file image
optional files (can be skipped for warm starts)
JCL files for building the operating system, source files contained
on the SOT, and macro library source
• FUP library, nonresident object, and SYSGEN object
• Performance Evaluation Toolkit
• MIPSMON images, M.SURE test suite, and H.ICP test suite
• MPX-32 Oemo images
If you enter Y in response to a prompt, all of the images listed in
that prompt will be restored. If you enter N, none within that prompt
will be restored.
After these 12 prompts have been responded to, follow step A above,
begining with the ENTER MAGNETIC TAPE DEVICE ADDRESS
prompt, to restore aU those images responded to with Y.
MPX·32 Reference Volume III
2·19
Booting a System from the Master SDT
After the INSTALLSDT macro has exited, mount any unbundled software
tapes on the tape drive and restore them using the Volume Manage RESTORE
directive.
Type the following to assign the task to tape:
TSM> AS TAP TO DEV=M9 BLO=N
Then type VOLMGR to re-enter Volume Manager. After all desired saved files
are restored, type EXIT to exit the Volume Manager.
TSM> VOLMGR
VOL> RESTORE VOLUME=SYSTEM
VOL> EXIT
Note: If the system does not install as described, check the hardware/firmware
revisions of the system and contact the Encore Field Representative.
o
2-20
Installing a Starter System
Booting a System from the Master SOT
2.4.1 Control Switches
While rebooting the system, various initialization processes can be inhibited or
enabled by setting the appropriate control switches. The assignment of the 13 switches
is:
Switch
o
inhibits volume clean-up by I.MOUNT
1
2
3
4
SYSINIT enters the system debugger before processing patches
inhibits patch processing (See Chapter 9, Entry Conditions.)
inhibits terminal initialization
inhibits accounting functions including the M.KEY, M.PRJCT,
M.ACCNT, and M.ERR files
inhibits processing of the sequential task activation table at
IPL time
5
6
7
(.
Function if set
8
9
10
11
12
If I.MOUNT encounters an invalid resource descriptor due to an
invalid resource descriptor type field or space definition, it
branches and links to the system debugger (if present) with R2
pointing to the resource descriptor.
I.MOUNT prereads the file space bit map (SMAP) or the resource
descriptor allocation bit map (DMAP). I.MOUNT will not perform file
overlap protection.
delete spooled output files instead of resubmitting them for
processing
inhibits activating LOADACS during IPL or RESTART operations
enables faster memory initialization by checking only one location
per map block to determine if that map block is present. It is not
recommended that this switch be set on the first IPL after power up.
inhibits initialization of the memory descriptor table (MDT)
for RMSS: inhibits booting of nodes while I.BOOT executes
The control switches can be accessed by the console. The proper time to set the
switches is while the system is waiting for the date and time to be entered. To set, for
example, switch 3, the following must be entered at an MPF or lOP console:
ENTER DATE AND TIME: @@P
/ /CS=10000000 Terminal Initialization Inhibited
//@@C
INVALID DATE FORMAT=MM/DD/XX
ENTER DATE AND TIME:
(Refer to the CONCEPT 32/2000 Operation manual for instructions on the windowing
console.)
During power up, control switches are prezeroed if the proper firmware revision level
has been installed. Power up without prezeroing can cause unexpected system
responses due to incorrect control settings.
MPX-32 Reference Volume III
2-21
Booting a System from the Master SOT
All control switch settings are preserved during system reboots not involving system
power up (i.e., online restart and IPL).
o
2.5 Philosophy of Bootstrapping
The SDT process attempts to eliminate as much stand alone I/O from the startup code
as possible because it is difficult to maintain stand alone capability for a number of
different types of controllers. This philosophy is reflected in the operation of the
system initialization program SYSINIT. For further details on SYSINIT, see section
2.6 of this chapter.
Because there may be no information on the disk at IPL time, tasks cannot be
activated from the disk. Therefore, the four needed tasks (Volume Formatter, Mount,
J.SWAPR, and Volume Manager) are supplied in load module format on the Master
SDT. SYSINIT performs tape activations on these four load modules to allow the
System Builder to:
•
•
•
•
format the disk and build a bootable operating system (Volume Formatter)
mount the system volume (Mount)
activate the swapper (J.SWAPR)
restore the files needed from the Master SDT and the Utility tape to make the
system function (Volume Manager).
o
2·22
Installing a Starter System
The System Builder
2.6 The System Bu ilder
Following the operating system in memory is a two-part module called SYSINIT.
This module is included by SYSGEN and is responsible for initializing the MPX-32
environment.
The first part, Phase I, runs stand alone. That is, MPX-32 is not yet functioning.
Phase I loads the CPU scratchpad, enables interrupt levels, resets I/O channels, and
performs any other cleanup operations required. It then sets up Phase II to run as an
MPX-32 task. When Phase I enables interrupts, a clock interrupt occurs and causes
Phase II to begin execution as a task.
Phase II activates the Volume Formatter, allowing the new volume to be formatted.
Next, the volume mount service is activated and mounts the system volume. Mter the
system volume is mounted, J .SWAPR is activated. Because there may be no
information on the disk at IPL time, activations are made from the SDT, causing
backward and forward movement of the tape. Mter this, the Volume Manager is run.
This utility restores any files that are required for system operation. These files must
include all key load modules and may also include any desired files. When Phase II
completes, the system is fully initialized and must be opened for user access. Phase II
accomplishes this by activating J.INIT, J.TINIT and J.TSM.
The user interaction for the above procedure on a Master SDT is described in section
2.4, Booting a System from the Master SDT.
The user interaction for the above procedure on a User SDT is described in Chapter 4
of this volume.
2.7 Operating Under the Starter System
The MPX-32 system is both disk and memory resident. TSM can be entered by
entering @@A then the system owner name and no key. Valid owner names are
created by the KEY utility.
(
MPX-32 Reference Volume III
2-23
Restoring Utility Processors, Libraries, and Other Files
2.8 Restoring Utility Processors, Libraries, and Other Files
o
The Volume Formatter (J.VFMT) and Volume Manager (VOLMGR) utilities are
supplied on the Master SDT. All other utilities such as the Text Editor, Macro
Assembler, and Media are an unbundled product. After all required files have been
restored from the Master SOT, all desired unbundled software must be restored.
Load modules on the tapes are saved by using Volume Manager SAVB directives and
can be restored from the tapes by using Volume Manager RESTORE directives. Each
save directive allows up to 48 entries. An end-of-file (EOF) is written after each group
saved.
When restoring files, use a restore directive for each group. Initially, all files should be
restored from the Master SOT and the Utility tape using the Volume Manager
RESTORE VOLUME directive. In subsequent interactions, selective restore
capabilities of the Volume Manager can be used for system installation and
maintenance.
The number of groups of files saved on the tapes can vary, and an equivalent number
of restore directives are required to install them. A listing is provided with the Master
SOT showing the groups in which the files were saved. Before continuing, check the
listing. Restore all groups of libraries, system files, and utilities (one restore directive
per group) using the listing as a guide.
o
2·24
Installing a Starter System
Example of First Use of Master SOT on User System
(
2.9 Example of First Use of Master SOT on User System
The following examples show how to boot a starter system from the Master SDT.
The first illustrates the entire booting process. The next two show the commands
needed to choose a system image other than the default.
2.9.1
Using the Default Master SOT Image on a CONCEPT 32/97
//HALT
//RST
//CLE
//IPL=1000
»TE
BOOT FROM A SCSI TAPE? (REPLY Y OR N): N
MPX-32 MASTER SDT FOR CONCEPT 32/97 COMPUTERS
ENTER SYSTEM DEVICE CHANNEL AND SUBADDRESS: 0800
ENTER DISC CONTROLLER TYPE: XIO (UDP OR DP II), HSDP, OR MFP
(REPLY X, H, OR M): X
MEMORY INITIALIZATION STARTED .... .
MEMORY INITIALIZATION COMPLETE .... .
ENTER DATE AND TIME: 04/23/90,13:30
TASK LOADING FROM TAPE STARTED ....
FMT> FORMAT DEVICE=DM0800 VOLUME=JONES MAXRES=3000FMT CONFIRM=Y
Enter CONF IRM=N to continue execution, or enter any changes.
FMT> CONFIRM=N
DEVICE=DM0800 -- VOLUME FORMATTING SUCCESSFULLY
COMPLETED
J.MOUNT - MOUNTING VOLUME JONES ON DM0800
VOL> CREATE D SYSTEM ENTR=1000
VOL> RESTORE VOLUME=SYSTEM
VOL> RESTORE VOLUME=SYSTEM
VOL> RESTORE VOLUME=SYSTEM
VOL> EXIT
DISC FFFF MARKED OFF LINE
INITIALIZATION COMPLETE
TERMINAL SETUP COMPLETE
PRESS ATTENTION FOR TSM
@@A
TSM> INSTALLSDT
WOULD YOU LIKE A HARD COPY OF THE SDT.CONTENTS FILE
TO ASSIST YOU IN THIS INSTALLATION ? (Y/N) Y
IS THIS A COLD START (Y/N) : Y
ENTER LINE PRINTER DEVICE ADDRESS (LP7EF8)
LP7EF8
DO YOU WISH TO INSTALL THE ENTIRE TAPE ? (Y/N) Y
ENTER MAGNETIC TAPE DEVICE ADDRESS (M91000) : M91000
MPX-32 Reference Volume III
2-25
Example of First Use of Master SOT on User System
ENTER THE VOLUME NAME WHICH THE SDT WILL BE
INSTALLED ON: SYSTEM
MOUNT MESSAGES ARE NOW TURNED OFF UNTIL INSTALLATION
HAS COMPLETED.
IMAGES 2 & 3 - NONRESIDENT ROUTINES ARE NOW
BEING ...
IMAGE 4 - COMPRESS OBJECTS ARE NOW BEING ...
IMAGE 5 - RESIDENT SERVICES & PROCESSORS ARE NOW
BEING ...
THE SDT HAS BEEN INSTALLED ACCORDING TO THE
INSTRUCTIONS SUPPLIED BY THE USER.
MOUNT MESSAGES ARE NOW TURNED BACK ON
(The following steps install optional tapes.)
TSM> AS TAP TO DEV=M9 BLO=N
TSM> VOLMGR
VOL> RESTORE VOLUME=SYSTEM
VOL> EXIT
2.9.2 Overriding the Default Image
2.9.2.1 Selecting MSTREXT for CONCEPT 32/97
To select MSTREXT, the extended MPX-32 Master SOT image, enter the following:
//HALT
//RST
//CLE
//GPRO=2
//IPL=1000
»TE
BOOT FROM A SCSI TAPE? (REPLY Y OR N): N
MPX-32 MASTER SDT FOR CONCEPT 32/97 COMPUTERS
(Continue as in the first example.)
2-26
Installing a Starter System
o
Example of First Use of Master SOT on User System
2.9.2.2 Selecting MSTRALL for CONCEPT 32/2000
To select MSTRALL as the Master SOT image when booting a CONCEPT 32/2000
computer, do the following:
Enter panel mode by activating the Panel Window on the windowing console.
Halt the system, if not already halted, by selecting the halt command from
the Panel Window menu.
Reset the system by selecting the reset command from the Panel Window
menu.
Clear memory by selecting the clear mem command from the Panel
Window menu.
Override the default system image by changing the contents of GPRO to
gprO:
00000001.
Load the system by selecting the ipl command from the Panel Window
menu.
Enter the tape unit's address in the sub-window.
»TE
BOOT FROM A SCSI TAPE? (REPLY Y OR N): N
MPX-32 MASTER SDT FOR CONCEPT 32/2000 COMPUTERS
(Continue as in the first example.)
2.9.2.3 Errors
Errors that occur while the user is selecting the Master SOT image cause a program
halt. After such an error occurs, GPR4 and GPRS contain the ASCII values for the
message BOOTFAIL and GPR6 and GPR7 contain the ASCII values for one of the
following error messages:
• INV GPRO • MACHTYPE -
invalid value in GPRO before IPL (must be 0, 1, or 2)
invalid machine type from CPU status word. Valid machine types:
o = CONCEPT 32/2000
3 =CONCEPT 32/67
4
5
= CONCEPT 32/87
= CONCEPT 32/97
• INV IMAG - invalid image selected (mismatch of image type and machine type)
• LOAD MOD - bad load module (mismatch of current and expected block number
in reading image)
• CHECKSUM - checksum error in reading image
• IO ERROR - SOT tape I/O error
MPX-32 Reference Volume III
2-27/2-28
0l '·,
o
3
Building and Testing a System
3.1
Introduction
This chapter describes how to SYSGEN and test a resident system configured for a
specific installation. Once the starter system has been installed, modifications can be
made to the input files used by the System Generation utility, SYSGEN, to configure
a tailored system. The modified data is saved to tape. This tape then becomes the
user SOT. The SYSGEN utility is described in Chapter 7 of this volume. This
chapter establishes SYSGEN in the cycle of building an MPX-32 system.
3.2 Building the SYSGEN Input Files
3.2.1
Building the Directive Input File
The directive input file for SYSGEN determines the configuration of the system. The
input file specifies such items as: hardware to support, interrupts to connect, and
devices to use for spooled system I/O. File SG.32, provided on the Master SOT, can
be used as a model or as a working base for preparing a SYSGEN directive file for the
CONCEPT/32. Either edit this file or build a directive input file from scratch using
the Text Editor. The resulting file must be uncompressed.
(
The system debugger, DEBUG, can be included in the resident system by specifying a
SYSGEN PROGRAM or USERPROG directive. This is recommended, particularly
in an initial system. The system debugger adds approximately 300W to the size of the
resident system. See Chapter 8 of this volume for further details on the system
debugger.
The size of the target system image can be reduced by one 2KW map block by
removing compatibility mode system modules H.ALOC, H.FISE, H.MONS, and
H.CALM using the SYSGEN NOCMS directive. Because the system image end
address is map block bounded, and the compatibility mode system modules total less
'
than one map block, the size of the system image may not be affected if the
compatibility mode modules are removed.
3.2.2 Building the Object Input File
Using the directive input file, SYSGEN determines which system modules, user
modules, interrupt handlers, and trap handlers are needed to build the target system.
SYSGEN reads the object code for these modules and handlers from the object input
file. An object input file, OH.32, for the CONCEPT/32 is provided on the Master
SOT.
User object modules can be added to the object input file. The names of these
modules are added to the file JH.32 supplied on the Master SOT. The file is then
compressed using the COMPRESS task. This task is described in the next section.
MPX·32 Reference Volume III
3·1
Building the SYSGEN Input Files
o
3.2.3 The COMPRESS Task
The COMPRESS task builds a file containing any number of object files. Its input
file must contain the ASCII names, one per record/line, of the object modules to copy
to the output file. The logical file code for input to COMPRESS is IN. The default
assignment of IN is to the system file IH.32. The logical file code for output from
COMPRESS is OT. The default assignment of OT is to the system file OH.32.
COMPRESS writes a control stream naming the files copied and lists the number of
records each contains. It also reports any allocation or read errors.
Syntax
COMPRESS
The provided object input file used by SYSGEN is created using the COMPRESS
task. The COMPRESS input file for the SYSGEN object input file is included on the
Master SDT and can be a model or a working base for modifying the SYSGEN object
input file. Proper execution of SYSGEN depends on the order of the following
modules in the COMPRESS input file:
Oli H.IP06 must be specified before H.CALM is specified.
• H.lOCS must be specified before H.MVMT or H.BKDM is specified.
• H.xIOS must be specified before H.IFXIO is specified.
• H.IFXIO must be specified before H. nXIO is specified, where?? are any valid
ASCII characters.
• H.MUXO must be specified before H.??MP is specified, where?? are any valid
ASCII characters.
• H.SWAPR must be specified before H.SINIT is specified. H.SWAPR and H.SINIT
must be the last two names in the input file, if the system debugger is not to be
configured in the system image. When the system debugger is specified
(USERPROG=DEBUG) the unmapped portion, H.DBUG2, must be the last name
in the input file immediately following H.SINIT. The mapped portion of the
system debugger, H.DBUGl, can be positioned anywhere in the input file before
H.SWAPR.
• H.MUXO and H.IPOO must both reside in the first 64K of memory.
• H.EXSUB must be specified before H.EXEC, H.EXEC2, or H.EXEC3 is specified.
H.lOCS, H.IFXIO, and H.MUXO are only specified one time in the input file.
COMPRESS IN Assignment
IH.32
COMPRESS OT Assignment!
SYSGEN OBI Assignment
OH.32
o
3-2
Building and Testing a System
Building the SYSGEN Input Files
Example
TSM> CHAN DIRE=AOBJECT
TSM> ASSIGN IN TO JH.32 BLOCKED=Y
TSM> ASSIGN OT TO OH.32 BLOCKED=Y
TSM> ASSIGN LO TO LFC=UT
TSM> COMPRESS
COPIED - 2 RECORDS FROM PATH pathname
COPIED - 2 RECORDS FROM PATH pathname
TSM>
pathname
is the name of the file from which the records were copied.
If a complete pathname is specified in the COMPRESS input file, the complete
patbname is displayed. If only a file name is specified in the COMPRESS input file
and the file is found on the current working volume and directory, only the file name
is displayed. If only a file name is specified in the COMPRESS input file and the file
is not found on the current working volume and directory, the system volume and
directory are searched; if the file is found, the complete pathname is displayed. If a
file name specified in the COMPRESS input file cannot be found, a message is
displayed and the COMPRESS task continues execution.
3.3 Running SYSGEN
For information on interactive and batch access, required and default assignments, and
other aspects of running SYSGEN refer to Chapter 7 of this volume. This section
describes a simple path for configuring a system.
The logical file code (LFC) for a SYSGEN directive file is DIR. A modified version
of SG .32 created by the user (called SG. DIR in the example below) can be assigned
to DIR.
The object input file, OH.32, can be assigned to OBJ, which is the logical file code for
the SYSGEN object input file. A TSM ASSIGN directive can assign the input files as
shown below.
TSM> ASSIGN OBJ TO OH.32 BLOCKED=Y
TSM> ASSIGN DIR TO SG.DIR BLOCKED=Y
TSM> SYSGEN
Alternatively, a job file can run SYSGEN in the batch mode with the above file
assignments.
The SYSGEN output file to contain the system image is specified with the SYSTEM
directive in the SYSGEN directives file. The output file is then created by SYSGEN.
File space for the output file need not be created before running SYSGEN. The file
name specified with the SYSTEM directive is the name to specify as the system load
file when restarting to test a system image.
MPX·32 Reference Volume III
3-3
Testing a SYSGENed System
3.4 Testing a SYSGENed System
After the tailored image is configured, it can be tested by restarting with the
RESTART directive or the shutdown task, J.SHUTD. Any owner can use the
RESTART directive unless prohibited in the M.KEY file. (Refer to Chapter 5 of this
volume for more information on RESTART.) The J.SHUID task is available only to
the system administrator. (Refer to Chapter 10 of this volume for more information
on J.sHUID.)
Restarting without specifying an image file or performing IPL from the console causes
the default system image (the starter system when running from SOT) to return as the
working system image. You can continue developing configurations by using the
editor, SYSGEN, and one-shot restarts as needed. Figure 3-1 shows the online restart
test process in overview.
MEMORY
SYSTEM 1
OR
STARTER SYSTEM
DISC
STARTER SYSTEM
(MPX-32)
ONE-SHOT
ONUNE
RESTART
SYSGENED
image
SYSfile
SYSGENED
image
SYSfile
•••
sysfile
R3030
Figure 3-1
Testing a User-Configured System
3-4
Building and Testing a System
Terminal Initialization and System Protection
f'
3.5 Terminal Initialization and System Protection
Chapter 10 of this volume describes how to initialize terminals on MPX-32 and how
to build an M.KEY file to authorize owners for access to the system and implement
owner privileges. If LOGONFLE and M.KEY files exist, RESTART initializes
terminals and M.KEY privileges.
MPX-32 Reference Volume III
3-5/3-6
o
C~'j
-~
o
('
4
Installing a User-Configured System
4.1
Introduction
Once a configured system is tested and ready to install in place of the starter system,
the Volume Manager builds a user System Distribution Tape (SDT).
4.2 Creating a User System Distribution Tape (SOT)
A user SDT is created by the Volume Manager and is similar to the Master SDT.
Figure 4-1 shows the layout of a user SDT. The first image on the SDT, called the
SDT image, contains the desired system image and four essential load modules that
must be configured in the following order for the system to be built properly:
•
•
•
•
Volume Formatter (J.VFMT)
System Mount (J.MOUNT)
Swapper (J.SWAPR)
Volume Manager (VOLMGR)
See MPX-32 Reference Manual, Volume II, Chapter 3 for information on creating the
SDT.
During SDT processing, the load modules on the SDT image are loaded into memory
and automatically activated. They are not restored to the system disk since directory
information has not been retained about them. Therefore, these four modules must
also be saved in one of the save images following the SDT image. At the VOLMGR
prompt during SDT processing, these load modules can then be restored to the system
disk.
In addition to the system image and essential load modules, another group of files
required for system operation must be saved: OPCOM, J.lNIT, and J.TSM. These
files must also be restored to disk when the VOLMGR program is activated.
Therefore, the minimum required modules on the SDT save are: OPCOM, VOLMGR,
J.lNIT, J.MOUNT, J.TSM, J.SWAPR, and J.VFMT.
The recommended set of load modules for an SDT is: VOLMGR, J.MOUNT,
J.VFMT, J.SWAPR, OPCOM, J.lNIT, J.TSM, J.SOUT, J.SSIN1, J.SSIN2, J.TINIT,
J.SOEX, and EDIT.
As boot programs cannot process multivolume headers, a user SDT should not be
created on multivolume tape.
MPX-32 Reference Volume III
4-1
Creating a User System Distribution Tape (SOT)
STANDARD OS
PLUS
SYSINIT
J.VFMT
EOF
J.MOUNT
J.SWAPR
VOLMGR
EOF
*
EOF
SAVED FILES
(MUST INCLUDE ALL KEY
LOAD MODULES)
...----'V-----..
EOF
*DOUBLE EOF REQUIRED BY VOLMGR
R3040
Figure 4-1
User System Distribution Tape Format
4-2
Installing a User-Configured System
-~.\
c·
"
"
Installing a User System Distribution Tape (SOT)
4.3 Installing a User System Distribution Tape (SOT)
All devices specified in the SYSGEN configuration should be connected.
The procedure to install a user SDT is similar to the procedure to install a Master SDT
as described in Chapter 2 of this volume.
J.TINIT searches for a file in the system directory named LOGONFLE. The
LOGONFLE can be built using the editor as documented in Chapter 10 of this
volume. If LOGONFLE exists as a system file, J .TINIT uses the parameters
contained in the file to initialize the terminals on the system. When terminal
initialization is completed, the following message is displayed on the console:
INITIALIZATION COMPLETE
TERMINAL SETUP COMPLETE
SYSTEM READY ... PRESS ATTENTION FOR TSM
If LOGONFLE does not exist as a system file, J.TINIT uses default parameters for all
terminals configured in the current system image (default parameter values are
described in Chapter 2 of this volume). Once terminal initialization is completed and
default values are assumed, the following message is displayed on the console:
INITIALIZATION COMPLETE
M.ASSN DENIAL, NO LOGON FILE, DEFAULT USED
TERMINAL SETUP COMPLETE
SYSTEM READY ... PRESS ATTENTION FOR TSM
4.4 Saving/Restoring System Processor and Utility Load
Modules
Additional load modules, libraries, and files are saved and restored using Volume
Manager save and restore directives.
MPX-32 Reference Volume III
4-3
Booting a System from a User SOT
4.5 Booting a System from a User SOT
To boot a CONCEPT/32 computer with the system console connected to an lOP or
MFP controller, perform the following steps on the system console:
Enter panel mode by typing:
System response:
Halt the system by typing:
System response:
Reset the system by typing:
System response:
Clear memory by typing:
System response:
Load the system by typing:
@@P
II
IIHALT
II
IIRST
II
IICLE
II
I I IPL=address of tape unit
The following prompts are displayed on the system console:
This prompt is displayed only if the system debugger is configured in the
system:
»
Enter TE to continue normal system operation.
ENTER SYSTEM DEVICE CHANNEL AND SUBADDRESS:
Enter the 2-character channel number and 2-character subaddress of the system
volume, for example, 0800 or 0801.
MEMORY INITIALIZATION STARTED .... .
MEMORY INITIALIZATION COMPLETE .... .
ENTER DATE AND TIME:
Enter the date and time using the following syntax:
date,hh[: ]mn[: ss] [, [D] [, TZ=num] ]
date
is the current date in one of the following formats:
mm/dd/yy
dd-mm-yy
ddmmmyy
mm is the 2-digit decimal month, dd is
the 2-digit decimal day, yy is the 2-digit decimal
year, and mmm is the 3-ASCII-character month
abbreviation.
4-4
hh
is the 2-digit decimal hour in 24 hour time.
mn
is the 2-digit decimal minute.
ss
is the 2-digit decimal second. If the colon
between hh and mn is omitted, this parameter is
ignored.
Installing a User-Configured System
Booting a System from a User SOT
(
D
indicates daylight savings time is in effect. Specifying
this field causes the internally stored binary time to be
adjusted by one hour.
TZ=num
allows the internal binary time to be biased
by num hours. The value of num can be positive or
negative. This field allows file times to be kept
according to a given standard while the displayed time
by the OPCOM TIME directive is the correct local time.
Examples:
06/16/81,08:45:00
06/09/81,11:20:00
14-06-81,13:00:00
03NOV81,09:25:00
08/29/81,10:33,D
15-04-81,19:15:00,D,TZ=-3
05MAY81,16:15"TZ=10
TASK LOADING FROM TAPE STARTED .....
Note:
If an invalid system volume channel or subaddress was entered before
entering the date and time, the following message appears at this
point:
INVALID SYSTEM OR SWAP VOLUME ENTERED
(
The user must then enter a valid system volume channel and
subaddress. Booting then continues with the FMT> prompt as show
below.
FMT>
This is the Volume Formatter prompt. The Volume Formatter builds the
on-disk structures required by the MPX-32 system.
Important: See Chapter 13 of this volume for more information on the
Volume Formatter. Many important user-selected parameters are only
available at this point and cannot be changed later without removal of all user
data on the disk.
For successful installation of the current release of MPX-32, the minimum
response to this prompt is the REPLACE directive (step C).
If you are installing MPX-32 for the first time, and targeting a new disk drive
that has never been media verified, follow step Abelow. As an alternative to
step A (INITIALIZE) you may choose to run the Level II Diagnostic Media
Verification program (HSOP or UDP/DP II controllers) or the Level II
Diagnostic program (MFP SCSI) before installing the SDT. The instructions
in step A can also be used to reconfigure structures built by the INITIALIZE
directive on a currently formatted disk.
If you are upgrading MPX-32, but wish to reconfigure currently formatted disk
structures built by the FORMAT directive, follow step B below.
If you are only upgrading MPX-32 with a user SOT tape, follow step C below.
MPX·32 Reference Volume III
4-5
Booting a System from a User SOT
Warning: Selecting steps A or B below will result in the removal of all user
data on the disk. Be sure all important files have been saved to tape or another
disk.
A. The minimum response required at this prompt is:
FMT> INITIALIZE DEVICE=devmne DrsC=deode
devmne
deode
is a 6-character device mnemonic (2-character device type
mnemonic, 2-digit hexadecimal channel number, 2-digit
hexadecimal device subaddress); for example, DM 08 00
or DM0802.
de ode is the disk storage device type code. Refer to Note
1 in the INITIALIZE directive section of Chapter 13 for a
list of disk type codes.
If desired, other INITIALIZE command parameters may also be
included on the command line. The INCLUDE parameter must not be
used. If the FMAP parameter is specified, the line printer must be
online.
At the completion of the INITIALIZE command, FMT> appears
again. When this prompt appears, follow step B below.
B. The minimum response required at this prompt is:
FMT> FORMAT DEvrCE=devmne VOLUME=volname
devmne
volname
is a 6-character device mnemonic (2-character device type
mnemonic, 2-digit hexadecimal channel number, 2-digit
hexadecimal device subaddress); for example, DM0800
or DM0802.
is a 1- to 16-character volume name. Valid characters are
A through Z. 0 to 9, dot (.) and underscore (J.
If desired, other FORMAT command parameters may also be included
on the command line, for example, ACCESS=, CONFIRM=,
MAXRES=. The IMAGE parameter must not be used. If the
BOOTFILE parameter is used. the only acceptable values are OLD
and NEW. Volume Formatter will exit upon completion of this
command.
C. Enter only the following at the Volume Formatter prompt:
FMT> REPLACE DEVrCE=devmne VOLUME=volname
devmne
volname
is a 6-character device mnemonic (2-character device type
mnemonic, 2-digit hexadecimal channel number, 2-digit
hexadecimal device subaddress); for example, DM0800
or DM0402.
is a 1- to 16-character volume name. Valid characters are
A through Z, 0 to 9, dot (.) and underscore L).
This causes the image on the user SDT to be the new default image.
Volume Formatter will exit upon completion of this command.
4·6
Installing a User-Configured System
o
Booting a System from a User SOT
(
Note:
IT the Volume Formatter determines that volume structures exist on the
specified disk device, this interactive prompt is issued:
DESTROY OPTION NOT ENABLED FOR FORMATTING VOLUME,
VOLUME NAME=volname
CONTINUE - yiN?
Enter Y to continue. If you select N, you must rewind the SOT tape
and start the boot procedure anew. Entering DESTROY=Y on the
command line for steps A or B will prevent this prompt from appearing.
This is not an option for step C.
For all steps (A, B, or C), if the CONFIRM=N parameter is not entered
at the command line, an interactive prompt to continue is written to the
screen. You may make changes in the dispalyed parameters or enter
CONFIRM=N to continue.
IT any error messages are issued by Volume Formatter, take corrective
action, rewind the SOT tape, and start the boot procedure anew.
J.MOUNT - MOUNTING VOLUME JONES ON DM0800
VOL>
This is the Volume Manager prompt. If a system directory larger than the
default is required, a system directory can be created before files on the SOT
are restored. However, if the REPLACE command was used above (meaning
the volume had already been formatted), the system directory may already
exist on the disk. If the system directory already exists, do not execute the
CREATE OIRECTORY command.
VOL> CREATE D SYSTEM ENTRIES=xx
Other parameters can also be included on the directive line, for example
OWNER=, PROJECTGROUP=, ACCESS=.
Saved files on the SOT can now be restored. Each RESTORE directive
processes one save image. Repeat this directive until all desired saved files on
the SOT have been restored. Mount any unbundled software tapes on the tape
drive and restore in the same manner. After all desired saved files are restored,
type EXIT to exit the Volume Manager.
VOL> RESTORE VOLUME=SYSTEM
VOL> EXIT
If using floppy disks, only the system image is on the boot floppy. Saved files
are on additional floppy disks.
MPX-32 Reference Volume III
4-7
Booting a System from a User SOT
INITIALIZATION COMPLETE
TERMINAL SETUP COMPLETE
(or)
INITIALIZATION COMPLETE
M.ALOCl DENIAL, NO LOGON FILE, DEFAULT USED
Ie)
TERMINAL SETUP COMPLETE
If J.TINIT is restored from the SDT, one of these initialization messages is
displayed; which one depends on whether the system file, LOGONFLE, exists
on the currently mounted system volume. See Chapter 10 of this volume for
details on how to build LOGONFLE.
PRESS ATTENTION FOR TSM
The system is now fully operational. Upon entering @@A for attention, a
prompt is issued to enter a 1- to 8-character logon owner name and 1- to 8character logon key. The following characters cannot be used in owner names
or keys: blanks, commas, semicolons, equal signs, line feeds, dollar signs,
exclamation points, percent signs, and left or right parentheses. Mter entering
a valid owner name and key, the TSM prompt is displayed and any valid TSM
directive can be entered.
o
4-8
Installing a User-Configured System
Booting a System from a User SOT
4.5.1
Example
IIHALT
IIRST
IIIPL=1000
»TE
ENTER SYSTEM DEVICE CHANNEL AND SUBADDRESS:OBOO
MEMORY INITIALIZATION STARTED .... .
MEMORY INITIALIZATION COMPLETE .... .
ENTER DATE AND TIME: 27APR90,OB:OO:OO
TASK LOADING FROM TAPE STARTED .....
FMT> FORMAT DEVICE=DMOBOO VOLUME=JONES MAXRES=3000FMT CONFIRM=Y
Enter CONFIRM=N to continue exection, or enter any changes.
FMT> CONFIRM=N
DEVICE=DMOBOO -- VOLUME FORMATTING SUCCESSFULLY
COMPLETED
J.MOUNT - MOUNTING VOLUME JONES ON DMOBOO
VOL> CREATE D SYSTEM ENTR=1000
VOL> RESTORE VOLUME=SYSTEM
VOL> EXIT
PRESS ATTENTION FOR TSM
MPX-32 Reference Volume '"
4-9/4-10
o
o
(
5
Online Restart
5.1
Introduction
An online restart halts the current system and restarts to the default or specified image.
It does not alter control switch settings. Online restart makes separate allocation
requests to allocate the volume descriptor (block 4) and the bootstrap blocks (blocks
0-3) of the target disk.
Online restart is initiated with the TSM $RESTART directive or by specifying the
RESTART option for the J.sHUID task. Refer to Chapter 10 of this volume for more
information on J.sHUID.
5.2 Bootstrap Programs
MPX-32 has two standard bootstrap progams. The first bootstrap program (referred to
as OLD in the Volume Formatter chapter of this volume) loads images requiring no
more than five Input/Output Command Doublewords (lOCOs). The second bootstrap
program (called NEW) handles images requiring six or more lOCOs to load, -as well
as those requiring no more than five.
The volume descriptor reserves space for five Read lOCOs. This is sufficient for
loading images up to 50 KB (hexadecimal), but it leaves no space for additional
lOCOs. To accommodate images requiring more than five lOCOs, the NEW bootstrap
program itself contains the image load (Read) lOCOs.
Online restart supports both bootstrap programs. However, when restarting to a disk
containing an OLD-style bootstrap program, an image requiring six or more lOCOs
cannot be used as the restart image.
To determine the bootstrap program being used on a volume, perform a disk dump
(DO) of the disk's volume descriptor (block 4). If the old bootstrap program is being
used, VO.IOCDI contains read lOCOs. If the new bootstrap program is being used,
VO.IOCDI contains the following ASCII text:
NEW DISC BOOTSTRAP. lOCOS IN BOOT BLOCK.
Note:
Because of current firmware limitations, MFP SCSI disks may not be able to
use the NEW standard bootstrap program or NEW-style custom bootstrap
programs. MFP SCSI images that require six or more lOCOs to load must
use MFP ECO 88-188, Revision E or greater. A six-lOCO image can be
restarted, but cannot be made the default image and IPLed when using less
than Revision E. Refer to MFP ECO 88-188 for more information about the
MFP solutions and availability.
MPX-32 Reference Volume III
5-1
Bootstrap Programs
5.3 TSM $RESTART Directive
The TSM $RESTART directive is available to any user unless restricted in the
M.K.EY file. This directive can be used to:
• restart the current default image or specified image
• one-shot test a new system image
• establish a new default system image
Figure 5-1 illustrates how a default system image is established.
Note:
Because this directive does not re-initialize the Analog/Digital Interface
(ADI) board or its associated Real-Time Peripheral (RTP) Equipment, system
images containing the ADI handler should be brought up using IPL
procedures.
C'
"I
5·2
Online Restart
,I
.'."
T5M $RE5TART Directive
(
MEMORY
SYSTEM 1
(
..
DISK
TAPE SYSTEM
SOT
(MPX -32)
SYSGEN ED
image
SYSfile
RESTART
SYSfile
DEFAULT
SYSGEN ED
image
SYSfile
••
•
sysfile
R3050
Figure 5-1
Establishing a New Default System
MPX-32 Reference Volume III
5-3
TSM $REST ART Directive
5.4 Precautions
Before using the TSM RESTART directive, perform the following steps:
• Use the TSM $SIGNAL directive to notify all terminal users to stop interactive and
batch activity and logoff.
• Use the OPCOM LIST directive to see if any user tasks remain active. Abort any
tasks by task number using the OPCOM ABORT directive.
• Check batch stream activity. It should end as users logoff.
• Because independent tasks are killed and pending I/O is lost during restart, reactive
or re-establish independent tasks following a restart.
5.5 Using $REST ART
Syntax
$RESTART [sysfile]
sysfile
is the pathname of the file containing the image to restart. This filename
is the same as the filename supplied with the file's SYSGEN SYSTEM
directive. If the filename is omitted, $RESTART uses the current default
image.
$RESTART issuses the following prompts:
DO YOU WISH TO RESTART? (Y OR N) :
DO YOU WISH THIS TO BE YOUR DEFAULT IMAGE? (Y OR N) :
Note:
Do not specify an image as the default image until it has been thoroughly
tested.
Possible responses to these prompts and their resulting actions are:
Restart
Prompt
Default
Image Prompt
y
y
N
N
y
N
Resulting Action
restarts and establishes
a new system default image
restarts to specified image,
but does not change default
image (one-shot test)
no restart, but establishes new
default image
no action. MPX-32 ignores the
REST ART directive.
To one-shot test a new image, restart the image but respond
prompt.
5-4
N
to the default image
Online Restart
Errors
5.6 Errors
If an allocation request for the volume descriptor or the bootstrap blocks fails,
RESTART displays one of the following messages and ends processing:
RESTART ... UNABLE TO ALLOCATE VOLUME DESCRIPTOR
RESTART ... UNABLE TO ALLOCATE BOOTSTRAP BLOCKS
If the bootstrap program on a disk cannot be identified or properly handled (e.g. it is a
custom bootstrap), RESTART issues the following messages and ends processing:
RESTART ... INVALID BOOTSTRAP ON DISC VOLUME
RESTART ... EXECUTE J.VFMT "REPLACE" TO WRITE NEW
BOOTSTRAP AND IMAGE TO VOLUME
When using the old bootstrap program, if the user restarts to an image requiring six
lOCOs to load and specifies that image as the default, RESTART displays the
following message but does not end processing:
RESTART ... NEW IMAGE TOO LARGE TO MAKE DEFAULT WITH
CURRENT BOOTSTRAP ON DISC
Subsequent IPLs result in loading of the previous image.
When using the old bootstrap program, if the user restarts to an image requiring seven
or more lOCOs to load and specifies that image as the default, RESTART displays the
following messages and ends processing:
RESTART ... NEW IMAGE TOO LARGE TO RESTART WITH CURRENT
BOOTSTRAP ON DISC
RESTART ... EXECUTE J.VFMT "REPLACE" TO WRITE NEW
BOOTSTRAP AND IMAGE TO VOLUME
If the user restarts to the default image when no system volume is configured,
RESTART aborts with the following message:
RESTART ... RESTART TO DEFAULT IMAGE CANNOT BE PERFORMED
ON REMOTE NODE
MPX-32 Reference Volume III
5-5/5-6
l<·~j.'
... ·'··"
o
6
Recovering the System
6.1 Introduction
If the operating system halts, a fresh copy of the disk file containing the operating
system image can usually be restored into memory from the lOP console. This is an
initial program load (IPL) and restart operation, and goes through the restart cycle
illustrated in the previous chapter.
The following instructions apply to input on an 10P/MFP console. When using a
windowing console (CONCEPT 32/2000 only), refer to the CONCEPT 32/2000
Operations Manual.
6.2 Recovery from Disk at the Console
To IPL and restart the default MPX-32 system from disk, enter the following at the
console:
IIRST
I IIPL xxxx
xxxx is the address of the system disk.
(
Restart logic is always located on the system disk, and directs processing to the most
recent default system file regardless of its disk location.
6.3 Errors During Start-up
If the system halts at or near location X'6FC' during IPL from disk, enter GPR at the
I I prompt to read the contents of R 1.
Rl contains one of the following error codes that will aid in debugging:
Error Code
1
Description
checksum error detected on system image
2
system image was not located at address specified to bootstrap
3
fatal I/O error reading system image
4
error retry attempts exhausted
5
system does not match machine type
MPX-32 Reference Volume III
6-1
Errors During Start-up
If the system halts during system initialization (SYSINIT) Phase I, R5 contains abort
code SYOI. Rl contains one of the following error codes:
Error Code
1
Description
unrecognizable IPL device indicator
2
invalid machine type
3
no UDT associated with the IPL device
4
target system image not compatible with CPU model
5
cannot boot extended mode MPX-32 on a 32/27
6
a device is configured at the CPU's F-class channel,
preventing H.SINIT from dynamically configuring an
operator console for a 32/2000 system
7
no priorities are available for the dynamically configured
operator console on a 32/2000 system
C-''
\J
If the system halts during SYSINIT Phase II, an abort message is displayed on the
system console.
6.4 System Halt Analysis
If the operating system halts, the following procedure can be used on a CONCEPT/32
computer to determine what operations were in progress when a halt occurred.
1. Check the CPU front panel to determine if the halt was caused by a
hardware failure. Check interrupt active, run, halt, and any other
pertinent indicators .
. 2. Read PSW and Instruction:
//psw
3. Read registers 0 - 7:
a. / /GPR
b. If R7=X'54524150', a trap, the registers contain the following
information:
Register
o
1
2
3
4
5
6
6·2
Contents
PSD word 1
PSD word 2
real address of the instruction causing
the trap
instruction causing the trap
trap status word
ASCII trap type (e.g. MF01)
address of registers saved at time of trap
Recovering the System
o
System Halt Analysis
If R5 = X'56403939' (a potential file overlap) and R7 = X'00000034'
(a double allocation error) occur, the registers contain the following
information:
RO=PSW
Rl = VOMM FCB address
R2 = MVTE address
R3 = requested size in number of allocation units
R4 = next available SMAP bit position
R6 = internal VOMM error code
If R5 = X'56403939' (a potential file overlap) and R7 = X '00000000 ,
(a double deallocation error) occur, the registers contain the
following information:
RO=PSW
Rl = VOMM FCB address
R2 = MVTE address
R3 = MVTE address
R4 = start SMAP bit position to perform deallocation
R6 = SMAP start block number
c. The registers at the time of the trap are examined by entering:
liMA = x
x is the contents of R6
(
followed by seven returns. Each return displays the contents of the
next register.
d. PS02, real address, instruction, and status is examined by entering four
returns, one return for each item.
4. Access system debugger, if configured:
a. IIRST
b. lIMA=B5C
c. Ilpc=x
C.OEBUG (address of system debugger or
o if not included in SYSGEN)
x is the address displayed as MD=x
resulting from the MA=B5C step
d. IIRUN
5. In the system debugger:
a.
b.
c.
d.
e.
f.
g.
{"
DT
ABS
ECHO
REMAP
8E8
8E8,+40
DU 0, nnnn
h. DU N,2000N
MPX-32 Reference Volume III
systems with event trace enabled
determines current task
dumps dispatch queue information
nnnn is the address of H.IPOO, obtained
from the SYSGEN load map
user task TSA
6-3
System Halt Analysis
6. Make a dump tape, if a crash dump routine is configured
a. Mount a tape on MTlOOO
b. IIHALT
c. IIRST
d. l1MA=C28
e. Ilpc=x
C.CRDUMP (address of crash dump routine
or 0 if H.DEBUG2 or H.DMPMT is not
included in system)
x is the address displayed as MD=x
resulting from the MA=C2 8 step
f. IIRUN
g. When the system is up, use ANALYZE to study the crash dump
6.5 Automatic IPL
If automatic IPL is hardware enabled and the system halts because of a power failure,
the CPU initiates an IPL during the power up initialization. Automatic restart, the
ability to restart or continue a software program that was interrupted by a power
outage, is not supported. The software does, however, provide the required
parameters for user implementation of the power up automatic restart feature.
If operator intervention is inhibited, all prompts normally displayed on the system
console during system initialization are inhibited. The system provides default
responses for the inhibited prompts. See the Operator Intervention Inhibit section, in
Chapter 10 of this volume.
c
6-4
Recovering the System
(
'.
".,
7
System Generation (SYSGEN)
7.1
Introduction
System Generation (SYSGEN) for an MPX-32 system involves supplying a set of
configuration directives to the SYSGEN utility. Using these directives, the utility
creates a permanent file containing the installation specific MPX-32 system in
memory image absolute format.
7.2 General Description
SYSGEN is a privileged system utility that operates in a standard MPX-32 system.
SYSGEN can be executed in batch or interactive mode. The system where SYSGEN
is executed must have enough free memory to hold the generated system and
SYSGEN itself. SYSGEN requires 16KW.
The resources that SYSGEN requires are:
• directives
• system object modules
The directives can be supplied interactively or by using batch from magnetic tape,
disk, or card reader. If supplied on a magnetic tape, the tape can include SYSGEN
resident object modules and MPX-32 modules. The file for the resident system image
and the system table file are permanent disk files created by SYSGEN.
System object modules include: interrupt and trap processors such as H.IPOO and
H.IPIT, modules that form the MPX-32 nucleus such as H.EXEC and H.REMM,
resident system tasks such as J.SW APR and the system debugger and the object for
SYSINIT. These modules are provided as files to be restored from the Master SOT
after a starter system is installed. The file naming convention for SOT files that are
designed to be part of the resident system is OH.module.
User object modules for interrupt handlers, resident system tasks, and user-callable
modules defined with the MODULE directive must also be included in the object file
for SYSGEN.
A task called COMPRESS, provided on the Master SOT, concatenates object code.
This task selects all required system module files for SYSGEN into the SYSGEN
object input file. The COMPRESS input file can be modified to contain any modules,
interrupt handlers, resident tasks, or device handlers needed to configure the resident
operating system. See Chapter 3 of this volume for more information on COMPRESS.
Any handlers or tasks that are SYSGENed must be Assembler object modules that
conform to the following basic structure. The modules must begin with a handler
address table (HAT), end with an initialization entry point, and use the following
system macros: M.EIR, M.XIR, M.MODT, M.SVCT, and M.SVCP.
MPX-32 Reference Volume III
7-1
General Description
System tables are constructed and linked to the resident system modules, handlers, and
user-supplied resident modules and handlers as specified by SYSGEN directives. A
resident system image is formed and subsequently written to the dynamically acquired
disk file specified in the SYSTEM directive. Concurrent with this process, a listing of
directives is built and a load map of the system is generated. The symbol table can be
saved in a system symbol table file specified with the SYMTAB directive and used in
patching the system.
SYSGEN uses big blocking buffers for object processing. To inhibit use of these
blocking buffers, set option 1 before activation.
7.3 SYSGEN logical File Codes
The logical file codes associated with SYSGEN are directives file (DIR), object
module file (OBJ), base object module file (OBR), and listed output (SLO).
DIR Default and Optional Assignments
The file containing SYSGEN directives is assigned to logical file code DIR. The
default assignment for DIR is to SYC. The optional assignment for DIR is to
pathname.
$ASSIGN DIR TO pathname BLO=Y
pathname
is the name of a file containing the SYSGEN directives
OBJ Default and Optional Assignments
The file containing system resident modules is assigned to logical file code OBJ.
There are two default assignments for OBJ: OH.32_0UT (mapped out) is the default
if the system image has been specified for a CONCEPT 32/2000 (see the MACHINE
directive in this chapter); OH.32 is the default if it has not. In addition, there is an
optional assignment for OBJ:
$ASSIGN OBJ TO pathname BLO=Y
path name
is the name of a file containing system resident object files
OBR Default and Optional Assignments
The file containing extended system modules is assigned to logical file code OBR.
OBR must not be reassigned when building a mapped out image.
The default for OBR is to NU (null device). There is one optional assignment for
OBR:
$ASSIGN OBR TO pathname BLO=Y
path name
7-2
is the name of the file containing extended system modules
System Generation (SYSGEN)
()
SYSGEN Logical File Codes
SLO Default and Optional Assignments
SYSGEN listed output - the directives list, the load map, and the error list are
assigned to logical file code SLO.
The default assignment for SLO is to SLO.
There are three optional assignments for SLO:
$ASSIGN SLO TO {DEV=devmnc I LFC=UT Ipathname}
DEV=devmnc
devmnc is the device mnemonic of a device to contain SYSGEN
listed output
LFC=UT
specifies the logical file code UT
path name is the name of the file to contain SYSGEN listed output.
7.3.1
LFC Summary
Default
Assignment
LFC
Optional
Assignment
DIR
SYC
pathname
OBI
OH.32 (or OH.32_0UT)
pathname
OBR
NU (null device)
pathname
SLO
SLO
pathname
DEV=devmnc
LFC=UT
7.4 Options
Option
1
17
18
19
Description
big blocking buffers inhibited
each overlay module is debuggable
enter SYSGEN debugger when initializing system modules
enter SYSGEN debugger after a break or abort request is issued.
Options 17, 18, and 19 are processed only when bit C.DEV of C.BIT is set. This bit
must be set to debug SYSGEN.
MPX·32 Reference Volume III
7-3
Accessing SYSGEN
7.5 Accessing SYSGEN
SYSGEN is accessed from batch or TSM in this way:
[$] [EXECUTE] SYSGEN
or
$RUN @SYSTEM(SYSTEM)SYSGEN
When directive input (DIR) is assigned to a terminal, a SY S> prompt is displayed.
To exit SYSGEN and return to TSM, use C.
7.6 SYSGEN Directives
There are three types of SYSGEN directives:
• Section directives - begin with II and indicate the beginning of the three major
sections: f/HARDWARE, IISOFTW ARE, and f/END.
• Subsection directives - begin with / and indicate the subsections within major
sections.
• Keyword directives - have no slash, and are part of a subsection.
SYSGEN directives begin in column 1 of the record and contain no embedded blanks.
An asterisk in column 1 specifies a comment line. Within a line, a blank: starts
comment processing.
Numeric values are represented by decimal numbers unless otherwise specified.
Directives, except TITLE, can be continued across more than one input line by
placing a hyphen (-) as the last significant character on the line to be continued.
SYSGEN directives are optional unless specifically described as required. In general,
the order or presentation of SYSGEN directives is not critical within a directive
subsection. However, if the order is critical, the individual directive discussion
clarifies the proper order.
File SG.32 contains a starter SYSGEN directive file. It can be used as it exists or it
can be modified. It contains the required directives and a wide assortment of possible
configurations that can be activated by removing the comment designation (*).
SYSGEN directives are summarized below in the order they could appear in your
directive file. Directives are described individually, in alphabetical order, on the
following pages.
7-4
Directive
Description
TITI..E
permits identifying information to be printed on the listed
output file
//HARDWARE
indicates the beginning of the hardware section of directives
/pARAMETERS
designates the parameters subsection of the //HARDW ARE
section
System Generation (SYSGEN)
C
c,
,
",
~
SYSGEN Directives
(
(
Directive
Description
MACHINE
specifies the type of computer for which the system is being
configured
IPU
specifies an Internal Processing Unit will be configured into the
target system
/MEMORY
designates the memory subsection of the //HARDW ARE section
RLWU
specifies whether read/lock write/unlock applies to all memory
SIZE
specifies the memory configuration of the target system
/CHANNELS
designates the controller and device directives subsection of the
//HARDWARE section
CONTROLLER
specifies hardware channels to be configured
DEVICE
defines configured hardware I/O devices
/INTERRUPTS
designates the interrupt directives subsection of the
//HARDWARE section
PRIORITY
specifies the interrupt configuration and the interrupt processors
to be used by the target system
{fRAPS
designates the trap directives subsection of the //HARDWARE
section
PROGRAM
specifies the names of trap handlers to be configured on the
system
SYSTRAP
specifies the default trap handlers that are to be overridden. This
directive can only be used if a PROGRAM directive is not
specified.
USERPROG
specifies the names of trap handlers and resident system
modules to be configured on the system if a PROGRAM
directive is not specified
/SYSDEVS
designates the system device directives subsection of the
//HARDWARE section
LOD
specifies a system listed output device. Used as the default
device in related OPCOM directives
POD
specifies a system punched output device. Used as the default
device in related OPCOM directives.
SID
specifies a system input device (SID). Used as the default
device in related OPCOM directives.
SWAPDEV
specifies the default swap device
SWP
This directive is ignored.
MPX·32 Reference Volume III
7·5
SYSGEN Directives
... 'c,
(
i;"~
Directive
Description
/VP
designates the Vector Processor subsection of the
//HARDWARE section
VP
specifies the device characteristics of the Vector Processors to
be configured
VPID
specifies the unit-specific infonnation for a Vector Processor
//SOFfWARE
indicates the beginning of the software section of directives
/pARAMETERS
designates the parameters subsection of the //SOFTWARE
section
SYSTEM
specifies the name of the file to be used as storage for the
generated MPX-32 resident image
SYMTAB
specifies the name of the file to be used as storage for the
system symbol table
DELTA
selects optional IPU/CPU scheduling algorithm
BATCHMSG
specifies suppression of task messages sent to users' tenninals
or the system console
DISP
detennines the number of entries in the dispatch queue.
LOGON
specifies single or multiple logons using the same owner name
POOL
specifies the size of the memory pool to reserve
IOQPOOL
specifies the number of words to reserve for the IOQ memory
pool
MSGPOOL
specifies the number of words to reserve for the MSG
memory pool
MTIM
specifies the number of real-time clock interrupts per second
NTIM
specifies the number of real-time clock interrupts per time unit
ITIM
specifies the time interval set for the interval timer on the
RTOM module
NOTSMEXIT
specifies that TSM remains active when not in use
TSMEXIT
specifies that TSM exits from the system when no longer
required
ITLB
generates an Indirectly Connected Task Linkage Block
MMSG
specifies the maximum number of no-wait messages to be sent
by an unprivileged task
MRUN
specifies the maximum number of no-wait run request to be
sent by a task
MNWI
specifies the maximum number of no-wait I/O requests that
can be concurrently outstanding for a task
C·"
, .,!
7-6
System Generation (SYSGEN)
SYSGEN Directives
("
(
(:
Directive
Description
TQFULL
specifies the largest time quantum a single user timedistribution task acquires before being relinked to the bottom
of the priority list at its base execution priority
TQMIN
specifies the smallest time quantum a single user task acquires
before preemption by a higher priority user time-distribution
task
BATCHPRI
specifies the execution base priority for batch jobs
TERMPRI
specifies the execution priority level for all tasks activated in
the interactive terminal environment
PATCH
specifies a patch area to append to the MPX-32 resident image
MODE
requests special system operations
SVC
increases the size of the SVC table
FLTSIZE
This directive is ignored.
RMTSIZE
increases the size of the Resourcemark Table
ACTIVATE
specifies the names of load modules to be activated after the
system has been booted. Status is not checked.
SEQUENCE
specifies the names of load modules to be activated after the
system has been booted. Status is checked.
TRACE
allows initialization of the system trace flag word C.TRACE
DEBUGTLC
allows specification of the console address for the System
Debugger's stand-alone I/O
PCHFILE
provides the name of the file to be used as the patch file for
the generated system
DBGFILE
provides the name of the file containing the default task
debugger load module for the generated system
DPTIMO
specifies a default time-out value to be applied to resource
delays encountered when attempting to access a
mUltiprocessor, shared-volume resource
OPTRY
specifies the decimal number of tries to obtain a
multiprocessor resource before issuing a denial
KTIMO
specifies the number of seconds the kill directive will attempt
to abort a task before it kills it
OTSAVE
specifies the elapsed time before the date/time backup
program resumes
SWAPSIZE
specifies the initial swap file size
SWAPLIM
specifies the minimum partial swap quantum
EXTDMPX
specifies the location for extended memory MPX-32 and/or
the TSA for tasks cataloged SYSTSA
MPX·32 Reference Volume III
7·7
SYSGEN Directives
I(
I
7-8
Directive
Description
HELP
specifies the directory containing help files and activates
J.HLP
DEMAND
specifies which tasks are demand page processed
NODEMAND
inhibits demand page processing
AGE
specifies the amount of virtual time to pass before an
unreferenced page is considered aged during demand
page processing
BEGPGOUT
specifies the minimum percentage of total memory
desired for free pages on a demand page system
ENDPGOUT
specifies the maximum percentage of total memory
desired for free pages on a demand page system
MAPOUT
designates mapped out as the default execution mode for
tasks cataloged with the ENVIRONMENT SYSMAP
keyword
NOMAPOUT
designates mapped in as the default execution mode for
tasks cataloged with the ENVIRONMENT SYSMAP
keyword
/MODULES
designates the modules subsection of the //SOFTWARE
section
MODULE
defines the name of an optional user module to be
included in the MPX-32 resident image, the module
number to be associated with the module, and the
number of SVC callable entry points in that module
/OVERRIDE
designates the override subsection of the //SOFTW ARE
section
SYSMOD
replaces a system module with another module, or
removes modules H.ALOC, H.CALM, H.FISE, and
H.MONS
NOLACC
disables the MPX-32 functionality for tracking last date,
time, and owner name of access to task-level resource
NOANSI
excludes support for ANSI labeled tapes from the system
image
NO BASE
automatically excludes support for the execution of tasks
utilizing base register addressing from the system image
NOCMS
automatically excludes support for MPX-32 Rev. 1
compatibility mode services (modules H.ALOC, H.FISE,
H.MONS, and H.CALM) from the system image
CMIMM
returns the MPX-32 Revision 3.3 functionality for
implidt volume mount management
CMPMM
inhibits public volume dismount
_,j
G
System Generation (SYSGEN)
SYSGEN Directives
Directive
Description
NOTDEF
excludes support for the TERMDEF Facility from the
system image
NOSYSVOL
inhibits mounting and use of system volume for RMSS
systems
/pARTITION
designates the partition subsection of the //SOFTWARE
section
NAME
defines Datapool or Global Common memory partitions
OWNER
specifies an owner name and access rights that apply to a
memory partition defined by a NAME directive
PROJECT
specifies a project group name and access rights which apply
to a memory partition defined by a NAME directive
OTHERS
specifies access rights that apply to users of a memory
partition defined by a NAME directive who are not the
owner or members of the associated project group
/SECURITY
specifies the security subsection of the //SOFTW ARE
section
OWNERNAME
inhibits echoing of owner name at logon
PASSWORD
specifies that passwords are required for logon
SAPASSWD
disables the PASSWORD task so that only the system
administrator can change a password
SYSONLY
specifies SYSTEM as the only valid ownemame if there is
no M.KEY file
/TABLES
designates the tables subsection of the //SOFTW ARE section
CDOTS
specifies the size of the user CDOT array
JOBS
specifies the maximum number of batch jobs that can be
active concurrently
MDT
enables rapid file allocation through a memory resident
descriptor table (MDT)
SHARE
specifies the number of entries in the shared memory table
TIMER
specifies the number of timer entries to be generated in the
MPX-32 resident image
/RMSTABLS
designates the Resource Management System Tables
subsection of the //SOFTW ARE section
ARTSIZE
specifies the size of the allocated resource table (ART)
/FILES
designates the system files subsection of the //SOFTWARE
section
SMD
This directive is ignored.
MPX·32 Reference Volume III
7·9
SYSGEN Directives
( -"
I
\'
Directive
Description
SYCSIZE
included for compatibility only. This directive is accepted by
SYSGEN, but the results are not used in job processing.
SGOSIZE
included for compatibility only. This directive is accepted by
SYSGEN, but the results are not used in job processing.
fIEND
required as the last SYSGEN directive
7.6.1 ACTIVATE Directive
The ACTIVATE directive names load modules to be activated by SYSINIT
immediately after the target system is booted. Status checks are not performed on
these tasks. This directive appears under the //SOFTWARE /pARAMETERS
subsection.
Syntax
ACTIVATE=(name} ,... name7)
name} , ... name7
are the 1- to 8-character ASCII load module names to be activated,
separated by commas. A maximum of 7 names can be entered per
directive.
7.6.2 AGE Directive
The AGE directive indicates the amount of virtual time allowed to pass before an
unreferenced page is considered aged during demand page processing. Virtual time is
the time the task has control of the CPU.
If NODEMAND is specified, this directive is ignored. If this directive is not specified
and demand page processing is supported, the default is the value in effect for
TQMIN.
This directive appears under the f/SOFTW ARE /pARAMETERS subsection.
Syntax
AGE=.,u
xx
7·10
is the amount of virtual time in milliseconds (decimal) allowed to pass
before an unreferenced page is considered aged. If not greater than zero,
the value in effect for TQMIN is used.
System Generation (SYSGEN)
-
-j';'
SYSGEN Directives
7.6.3 ARTSIZE Directive
The ARTSIZE directive specifies the size of the allocated resource table (ART). The
number of entries in the ART determines the maximum number of system resources
that can be allocated in the system at one time. The size of each entry is 8 words. If
this directive is not specified, 100 entries are reserved for the ART.
This directive appears under the //SOFfWARE /RMSTABLS subsection.
Syntax
ARTSIZE=entries
entries
is the number of entries to be reserved for the allocated resource table
(ART).
7.6.4 BATCHMSG Directive
The BATCHMSG directive inhibits batch messages from going to the system console,
or to terminals logged on with the owner name to which the message is sent, or both.
If the BATCHMSG directive is not specified, messages will go to all appropriate
terminals and to the system console.
This directive appears under the //SOFfWARE /pARAMETERS subsection.
Syntax
BATCHMSG= ( { {TERM I NOTERM I CONS I NOCONS} I {TERM I NOTERM},
{CONS I NOCONS} } )
TERM
J.TSM allows batch messages to go to all terminals except the system
console
NOTERM J.TSM inhibits batch messages from going to all terminals except the
system console
CONS
J.TSM allows batch messages to go to the system console
NOCONS J.TSM inhibits batch messages from going to the system console
If neither TERM or NOTERM is specified, TERM is the default. If neither CONS or
NOCONS is specified, CONS is the default.
If both NOTERM and NOCONS are specified, task messages will not appear
anywhere.
7.6.5 BATCHPRI Directive
The BATCHPRI directive specifies the execution priority level of all batch jobs. This
directive appears under the //SOFTWARE /pARAMETERS subsection. If this
directive is not specified, the priority level is 61.
MPX-32 Reference Volume III
7-11
SYSGEN Directives
Syntax
BATCHPRI=nn
nn
is the 2-digit decimal time-distribution priority level, 55-64, to use for
batch jobs.
7.6.6 BEGPGOUT Directive
The BEGPGOUT directive specifies the minimum percentage of total memory desired
for free pages on a demand page system, the lower page-out threshold. When the
BEGPGOUT value is reached, J.SWAPR begins writing modified, unreferenced pages
which are queued for page-out to the swap file.
If NODEMAND is specified, this directive is ignored. If this directive is not specified
and demand page processing is supported, the default is 10% of the total available
memory on the system.
This directive appears under the //SOFfWARE /pARAMETERS subsection.
Syntax
BEGPGOUT=xx
xx
is a percentage (00 through 100) of the total available memory on the
system. H.SINIT converts this percentage to the correct number of pages
(map blocks). xx must be less than the value specified for ENDPGOUT.
7.6.7 COOTS Directive
The CDOTS directive specifies the size of the user CDOT array which follows the
fixed communications area in lower memory. The user array can be read by any task
but can only be written into by privileged tasks. C.USERVA is the starting point of
the user array. If this directive is not specified, no user communications region is
established.
If specified, this directive appears under the //SOFfWARE {fABLES subsection.
Syntax
CDOTS=number
number
is the decimal number of words in the user communications variable array
c
7-12
System Generation (SYSGEN)
SYSGEN Directives
7.6.8 /CHANNELS Directive
The /CHANNELS directive designates the controller and device subsection of the
//HARDWARE section. This directive is required.
Syntax
/CHANNElS
7.6.9 CMIMM Directive
The CMIMM directive returns the MPX-32 3.3 revision functionality for implicit
mount management. This includes the following features:
• OPCOM-mounted volumes can only be dismounted using the OPCOM
DISMOUNT directive.
• TSM $CHANGE DIRECTORY directive allows access to any nonpublic user
volume that is logically mounted to J.TSM.
• Logical dismount of the last user or assigner on a nonpublic user volume causes a
physical dismount of that volume.
This directive appears under the //SOFTWARE /OVERRIDE subsection.
(
Syntax
CMIMM
7.6.10 CMPMM Directive
The CMPMM directive inhibits public volume dismount. This directive appears
under the //SOFTWARE /OVERRIDE subsection.
Syntax
CMPMM
7.6.11
CONTROLLER Directive
The CONTROLLER directive represents one hardware channel to be configured in the
generated system. This directive is required and must be repeated for each channel to
be configured. The CONTROLLER directive appears under the /jHARDWARE
/CHANNELS subsection.
The HANDLER keyword permits specification of reentrancy and controller definition
table (CDT) generation. The type of reentrancy specified the first time a handler name
appears in a CONTROLLER or DEVICE statement is used for the entire system.
MPX-32 Reference Volume III
7-13
SYSGEN Directives
The COT per unit definition table (UOT) specification applies until another
HANDLER keyword or CONTROLLER statement is processed. Nonpresent channels
can be configured.
Syntax
CONTROLLER=ttcc,PRIORITY=intlev,CLASS=class [,CACHE]
[,HANDLER={ name I (name [,II,S] [,C))}] [,MUX=type] [,SUBCH=a]
tt
is the 2-character ASCII device mnemonic (see Table 7-1)
cc
is the 2-digit hexadecimal channel number
PRIORITY =intlev
intlev is the hexadecimal interrupt level. If the device class (see class
below) is memory disk, a priority interrupt is not required. If the
interrupt is on an lOP or MFP device, the priority must be the same as
other devices on that IOP/MFP.
CLASS=class
class is the device class
o
F
M
specifies 16MB addressable E class
specifies extended 1/0
specifies memory disk
[,CACHE] specifies a cache controller. All devices under a cache controller are also
cache.
[,HANDLER={ name I (name [,II,S] [,C))}]
name
is the 1- to 8-character handler name (see Table 7-1). If not
specified, the following defaults are used: H.IFXIO (XIO,
lOP, or MFP controllers), H.MVXO (GPMC controllers), and
H.NUXIO (null device).
specifies interrupt priority level reentrancy, one copy per
channel
S
specifies system level reentrancy, one copy per system
C
specifies one COT for each UOT
[,MUX=type]
type is the type of multiplex controller being configured:
GPMC
XIO
lOP
MFP
specifies general purpose multiplex controller and includes
H.GPMCS in the system image
specifies extended 1/0 and includes HXIOS in the system
specifies inputloutput processor and includes HXIOS in the
system image
specifies multi-function processor
C.'\
,
7-14
System Generation (SYSGEN)
.)
SYSGEN Directives
[,SUBCH=a]
a is the subchannel the controller is connected to. This subchannel will be
used to verify proper device address specifications on subsequent device
directives. For example, the subchannel should match the first device
address digit.
Table 7-1
MPX-32 Device Type Handlers
(-
Device
Mnemonic
Device
Handler
Default
Handlers
Device Description
cr
H.CfXIO
H.CfXIO
operator console (not assignable)
DC
H.DCXIO
H.DCXIO
any disk unit except memory disk
H.DCXIO
any moving head disk
DM
H.DCXIO
DM
H.MDXIO
any memory disk (HANDLER must be specified)
DM
H.DCSCI
any SCSI disk (HANDLER must be specified)
DF
H.DCXIO
H.DCXIO
any fixed head disk
MT
H.MTXIO
H.MTXIO
any magnetic tape unit
MT
H.MTSCI
M9
H.MTXIO
H.MTXIO
any 9-track magnetic tape unit*
M7
H.MTXIO
H.MTXIO
any 7 -track magnetic tape unit*
CR
H.CPMP
LP
H.LPXIO
any SCSI tape unit (HANDLER must be specified)
any card reader
H.LPXIO
any line printer
PT
H.CPMP
TY
H.F8XIO
H.F8XIO
any terminal/teletypewriter (other than console) **
cr
H.CfXIO
H.CTXIO
operator console (assignable)
FL
H.DCXIO
H.DCXIO
floppy disk
NU
H.NUXIO
H.NUXIO
null device
CA
N/A
communications adapter (binary synchronous/
asynchronous)
UO-U9
N/A
any available user-defined applications
LF
N/A
line printer/floppy controller (used only with
SYSGEN)
H.DCXIO
any nonfioppy disk except memory disk
ANY
H.DCXIO
any paper tape reader/punch
* When both 7- and 9-track magnetic tape units are configured, the
designation must be 7 -track.
** GPMC terminals have H.ASMP as their default handler.
Notes:
Multiple controller directives are invalid on a single channel, even if the devices
configured on the channel have mixed device types.
MPX-32 Reference Volume III
7-15
SYSGEN Directives
Extended I/O handlers default to system reentrant handlers. The extended I/O interrupt
fielder (H.IFXIO) is channel reentrant. One copy should be specified for each extended
1/0 channel configured by using the I parameter.
o
GPMC device handlers default to system reentrant handlers.
If a line printer and a floppy disk are configured on the same lOP channel, only one
CONTROLLER directive should be used. Multiple DEVICE directives specify the
device and handler.
The XIO common subroutines (H.XIOS) are not named within the SYSGEN directive
file. They are automatically included during SYSGEN if MUX=XIO or MUX=IOP is
specified.
The GPMC subroutines (H.GPMCS) are not named within the SYSGEN directive file.
They are automatically included during SYSGEN if MUX=GPMC is specified.
Memory disks must be configured on channel 00 as DMOO.
The High Speed Data Handler (HSDG) is a D-class I/O controller that must be
SYSGENed as interrupt priority reentrant, one copy per channel, using the generic
software handler, H.HSDG. An example of the controller and device statements is:
CONTROLLER=U040,PRIORITY=OA,CLASS=D,HANDLER=(H.HSDG,I)
DEVICE=OO,DTC=UO
The SG.32 file on the SDT contains examples of how to SYSGEN other types of
controllers.
7.6.12 DBGFllE Directive
The DBGFILE directive names the permanent file containing the default task
debugger load module for the system being generated. This directive appears under
the IISOFfWARE /pARAMETERS subsection. If this directive is not specified, the
default filename is AIDDB.
Syntax
DBGFILE=filename
filename
is the 1- to 8-character ASCII file name of the file containing the default
task debugger load module
7.6.13 DEBUGTlC Directive
The DEBUGTLC directive specifies the console address for the System Debugger's
stand-alone I/O. If this directive is not specified, the default address is the address of
the system console. This directive appears under the IISOFfWARE /pARAMETERS
subsection.
7-16
System Generation (SYSGEN)
o
SYSGEN Directives
Syntax
DEBUGTLC=cc
cc
is a 2-digit hexadecimal channel number.
7.6.14 DELTA Directive
The DELTA directive selects the optional IPU/CPU scheduler. This directive appears
under the //SOFTWARE /pARAMETERS subsection. When DELTA is specified,
H.EXEC2 replaces H.EXEC, and H.CPU2 replaces H.CPU. For more information,
see the Internal Processing Unit section, in Chapter 2 of MPX-32 Reference Manual
Volume I.
Syntax
DELTA=cc
cc
is a 2-digit decimal number between 0 and 54 specifying the IPU bias
task boost value
Notes:
The IPU directive must be present to perform the substitution. If it is not specified, the
DELTA directive is ignored.
Do not include H.CPU2 or H.EXEC2 in the USERPROG directive, as they are
automatically selected.
7.6.15 DEMAND Directive
The DEMAND directive specifies which tasks are demand page processed.
When the mapped out object file is assigned at SYSGEN execution, demand page
processing is supported, unless NODEMAND is specified. The DEMAND directive
determines which eligible tasks are demand page processed. If other than the mapped
out object file is assigned, demand page is not supported and this directive is ignored.
If this directive is not specified and demand page processing is supported, the
following tasks are demand paged:
• eligible tasks at a priority range of 55 to 64
• tasks at priority levels 1 through 54 which are cataloged to run demand page
For more information about task eligibility for demand paging, refer to Reference
Manual, Volume I, Chapter 3.
When specified, this directive appears under the //SOFTW ARE /pARAMETERS
subsection.
MPX-32 Reference Volume III
7-17
SYSGEN Directives
.(-
i.-I
. . "'.'
\ .Y
Syntax
DEMAND={ NONE Ipp}
NONE
specifies that only those tasks specified as demand page tasks when
cataloged or linked are demand page processed
pp
is the highest priority level at which an eligible task runs in demand page
mode. The default is 55.
7.6.16 DEVICE Directive
The DEVICE directive defines the configured hardware I/O devices. This directive is
required. The DEVICE directive appears under the //HARDWARE /CHANNELS
subsection.
The HANDLER keyword permits specification of reentrancy and of controller
definition table (COT) generation. The type of reentrancy specified the first time a
handler name appears in a CONTROLLER or DEVICE statement is used for the
entire system.
The COT per unit definition table (UDT) specification applies until another
HANDLER keyword or CONTROLLER statement is processed. Nonpresent devices
can be configured. When the devices are added, a warm start with the devices marked
online allows them to be used.
The null device, NU, must be included in every configuration.
Notes:
Extended I/O handlers default to system reentrant handlers.
GPMC device handlers default to system level reentrant handlers.
A COT is generated each time a HANDLER keyword appears, except on the first
DEVICE statement following a CONTROLLER statement with a HANDLER
specification.
GPMCs support a maximum of 16 subaddresses per controller.
For XIO devices, the subaddress specified as the aa parameter is 2 hexadecimal digits.
The first digit is the controller address and the second digit is the device address. For
lOP devices, the digit specified for the controller address must be equal to the digit
specified in the CONTROLLER directive SUBCH parameter. Except for floppy
disks, all F-class disks must specify an even device address. The device address is
determined by the unit address plug installed in the drive or by switches in the drive.
(
"",
'.)
..
7-18
System Generation (SYSGEN)
,
SYSGEN Directives
(~
The device address is the unit address multiplied by 2 and converted to its
hexadecimal equivalent (for example, unit address 1 is device address 2, unit address
7 is device address E). If more than one device is configured using one DEVICE
directive, the device address and the increment (inc) must be even numbers. F-class
cartridge module drives adhere to the same conventions. SYSGEN automatically
configures the captive media portion of the drive at the next sequential odd device
address. Once configured, cartridge module drives are treated as individual devices.
The removable media portion is treated as a moving head disk at the even device
address, and the captive media portion is treated as a fixed head disk at the next
sequential odd device address.
7.6.16.1 DEVICE Syntax for Disks
Syntax
DEVICE: {aa I (aa,n,inc)} [,DEAL]
[,DISC: {mdsize I (mdsize [,0]) I devcode I (devcode I [,MIPID]) }] [,DTC:tt]
[,HANDLER: {name I (name[,II,S] [,C])}] [,IOQ:mode] [,OFF]
[,PHYSA:ccaa] [,SHR] [,START:start]
aa
is the 2-digit hexadecimal device subaddress. The first digit is the
controller address; the second digit is the device address.
n
is an optional parameter specifying the decimal number of devices starting
at the subaddress
inc
is an optional parameter specifying the hexadecimal address increment for
each additional device. If not specified, the default is 1.
[,DEAL]
specifies that memory for the memory disk is not allocated at system
initialization. DEAL is valid only for single-ported memory disk. If
DEAL is supplied with a dual-ported memory disk, it is ignored.
[,DISC: {mdsize I (mdsize [,0]) I devcode I (devcode I [,MIPID]) } ]
mdsize
specifies the size in KBs if the device is a memory disk
devcode
is the 5-character device mnemonic for disk storage devices.
It is not required for devices other than disk. See Table 7-2.
specifies the device is a multiport disk that is compatible with
an MPX-32 Revision 3.3 or later system
M
P
specifies the device is a multiport disk that is compatible with
an MPX-32 Revision 3.2C or earlier system
o
specifies the device is a dual-ported disk (for compatibility
only)
[,DTC:tt] tt is a 2-character device mnemonic (see Table 7-1). If not specified, the
device mnemonic specified on the associated CONTROLLER directive is
used.
MPX-32 Reference Volume III
7-19
SYSGEN Directives
[,HANDLER= {name I (name[,II,S]
name
o
[,C])}]
is the 1- to 8-character handler name (see Table 7-1). If not
specified, a default handler is assigned in the following
manner:
• If the device has a default handler associated with it, that
handler is assigned to the device.
• If the device does not have a default handler associated
with it, the device is assigned the same handler as the
device which was most recently defined to the subchannel
to which this device is being defined (aa above). If no
device has yet been defined to this subchannel, then the
handler associated with the CONTROLLER directive for
the subchannel is assigned.
An error is generated if an invalid handler is selected by
default.
This parameter must be specified for a memory disk
(H.MOXIO).
specifies interrupt priority level reentrancy, one copy per
channel
S
specifies system level reentrancy, one copy per system
C
specifies one CDT for each UDT
[,IOQ=mode]
is used by the lOP and GPMC to indicate the I/O queue entries are to be
linked from the UDT (IOQ=DEV) or from the CDT (IOQ=CONT). The
default mode is 10Q=CONT. However, most handlers provide their own
initialization for this parameter and ignore any value specified by
SYSGEN. Therefore. this parameter should not be used for any standard
MPX-32 handler supplied by Encore unless such a requirement is specified
in the installation instructions for that handler.
[,OFF]
specifies that the device or devices described by this directive are to be
SYSGENed in an offline state
[,PHYSA=ccaa]
specifies the physical (bus) channel address and device subaddress for
devices. Used when logical channel and subaddress do not match the
physical channel and subaddress.
ccaa
[,SHR]
is the 2-digit hexadecimal channel address and 2-digit
hexadecimal device subaddress
specifies the device is a shared device
[,START=start]
start specifies the decimal start map block number of the memory disk. If
not specified. default is the highest possible address in memory.
7-20
System Generation (SYSGEN)
o
SYSGEN Directives
Notes:
Memory disks must be configured on the even subaddresses of channel 00. The
subaddress of the memory disk cannot be the same as the null device subaddress.
Table 7-2
Disk Device Codes
Disk
Reserved
1.2MB floppy disk - Class F device
40MB moving head disk - Class F device
80MB moving head disk - Class F device
160MB moving head disk - Oass F device
300MB moving head disk - Class F device
340MB (Winchester) moving head disk - Class F device
600MB moving head disk - Oass F device
5MB fixed head disk - Class F device
32MB cartridge module disk - Class F device
Any nonfloppy disk - Class F device
Disk
Code
FE004
FLOOI
MH040
MH080
MH160
MH300
MH340
MH600
FH005
. CD032
ANY
7.6.16.2 DEVICE Syntax for Console, Terminals and a-Line Serial Printers
Syntax
DEVICE={aa I (aa,n,inc)} [,CACHE] [,DTC=It] [,FEOP] [,FULL]
[,HANDLER= (name I (name[,II,S] [,C])}] [,IOQ=mode] [,LlNSIZ=x] [,OFF]
[,PAGE=y] [,PHYSA=ccaa] [,SLPR]
aa
is the 2-digit hexadecimal device subaddress. The first digit is the
controller address; the second digit is the device address.
n
is an optional parameter specifying the decimal number of devices starting
at the subaddress
inc
is an optional parameter specifying the hexadecimal address increment for
each additional device. If not specified, the default is 1.
[,CACHE] specifies a cache device. This option is not necessary if the associated
CONTROLLER statement includes CACHE.
[,DTC=It]
It is a 2-character device mnemonic (see Table 7-1). If not specified, the
device mnemonic specified on the associated CONTROLLER directive is
used.
[,FEOP]
specifies that J.SOUT inhibits the normal initial form feed and terminates
all printing with an additional form feed, if specified for LP device. FEOP
is applicable only on electrostatic printers and laser printers that retain the
last page of output until a form feed (EJECT) is received.
MPX-32 Reference Volume III
7-21
SYSG EN Directives
[,FULL]
allows full-duplex mode of operation if FULL and NOECHO are
specified in LOGONFLE. This causes a UOT to be created for both the
read and write subaddresses even though only the read subaddress is
specified. Valid only for 8-line asynch devices.
[,HANDLER= {name I (name[,II,S]
name
[,C])}]
is the 1- to 8-character handler name (see Table 7-1). If not
specified, a default handler is assigned in the following
manner:
• If the device has a default handler associated with it, that
handler is assigned to the device.
• If the device does not have a default handler associated
with it, the device is assigned the same handler as the
device which was most recently defined to the subchannel
to which this device is being defined (aa above). If no
device has yet been defined to this subchannel, then the
handler associated with the CONTROLLER directive for
the subchannel is assigned.
An error is generated if an invalid handler is selected by
default.
specifies interrupt priority level reentrancy, one copy per
channel
S
specifies system level reentrancy, one copy per system
C
specifies one CDT for each UDT
[,IOQ=mode]
is used by the lOP and GPMC to indicate the I/O queue entries are to be
linked from the UOT (IOQ=OEV) or from the COT (IOQ=CONT). The
default mode is IOQ=CONT. However, most handlers provide their own
initialization for this parameter and ignore any value specified by
SYSGEN. Therefore. this parameter should not be used for any standard
MPX-32 handler supplied by Encore unless such a requirement is specified
in the installation instructions for that handler.
[,LlNSIZ::x] x specifies the number of characters per line for TSM devices. The
default is 80.
[,OFF]
specifies that the device or devices described by this directive are to be
SYSGENed in an offline state
[,PAGE=y] y specifies the number of lines per screen for TSM devices or number of
lines per page for listed output devices. Zero prevents ENTER CR FOR
MORE. The default is 24 lines.
[,PHYSA=ccaa]
specifies the physical (bus) channel address and device subaddress for
devices. Used when logical channel and subaddress do not match the
physical channel and subaddress.
7-22
System Generation (SYSGEN)
c·"· ·
,';
\,
SYSGEN Directives
ccaa
[,SLPR]
is the 2-digit hexadecimal channel address and 2-digit
hexadecimal device subaddress
indicates the device is a serial printer. See Notes.
Notes:
The CACHE parameter can be applied to ACM devices (H.F8XIO), to quadruple the
normal I/O time out. This is intended for slow spooling devices with large internal
buffers using XONjXOFF (WXON) flow control. The CACHE parameter can also be
applied to a buffered tape processor (BTP), but not to the cache disk accelerator.
When SLPR is specified: the HANDLER parameter must equal H.F8XIO; the
LINESIZ and PAGE parameter must be used (suggested settings LINSIZ=133 and
PAGE=60); the DEVICE FULL parameter must not be specified. If the printer has a
large buffer, the DEVICE CACHE parameter should be specified to extend the normal
time-out. This will account for long I/O wait times (XOFF) while the buffer is
purging.
7.6.16.3 DEVICE Syntax for Tape Drives
Syntax
DEVICE= {aa I (aa,n,inc)} [,ANSI] [,CACHE] [,DTC=tt]
(
[,HANDLER={ name I (name[,II,S] [,C])}] [,IOa=mode] [,OFF] [,PHYSA=ccaa]
[,alTO] [,SHR]
aa
is the 2-digit hexadecimal device subaddress. The first digit is the
controller address; the second digit is the device address.
n
is an optional parameter specifying the decimal number of devices starting
at the subaddress
inc
is an optional parameter specifying the hexadecimal address increment for
each additional device. If not specified, the default is 1.
[,ANSI]
specifies this drive is used only for ANSI tape processing. Refer to
Reference Manual Volume II, Chapter 7, for details. This parameter does
not restrict the system administrator.
[,CACHE] specifies a cache device. This option is not necessary if the associated
CONTROLLER statement includes CACHE.
[,DTC=tt]
tt is a 2-character device mnemonic (see Table 7-1). If not specified, the
device mnemonic specified on the associated CONTROLLER directive is
used.
MPX-32 Reference Volume III
7-23
SYSGEN Directives
[,HANDLER= {name I (name[,II,S]
name
[,C])}]
is the 1- to 8-character handler name (see Table 7-1). If not
specified, a default handler is assigned in the following
manner:
• If the device has a default handler associated with it in
Table 7-1, that handler is assigned to the device.
• If the device does not have a default handler associated
with it, the device is assigned the same handler as the
device which was most recently defined to the subchannel
to which this device is being defined (aa above). If no
device has yet been defined to this subchannel, then the
handler associated with the CONTROLLER directive for
the subchannel is assigned.
An error is generated if an invalid handler is selected by
default.
specifies interrupt priority level reentrancy, one copy per
channel
S
specifies system level reentrancy, one copy per system
C
specifies one CDT for each UDT
[,IOa=mode]
is used by the lOP and GPMC to indicate the I/O queue entries are to be
linked from the UDT (IOQ=DEV) or from the CDT (IOQ=CONT). The
default mode is 10Q=CONT. However, most handlers provide their own
initialization for this parameter and ignore any value specified by
SYSGEN. Therefore, this parameter should not be used for any standard
MPX-32 handler supplied by Encore unless such a requirement is specified
in the installation instructions for that handler.
[,OFF]
specifies that the device or devices described by this directive are to be
SYSGENed in an offline state
[,PHYSA=ccaa]
specifies the physical (bus) channel address and device subaddress for
devices. Used when logical channel and subaddress do not match the
physical channel and subaddress.
ccaa
is the 2-digit hexadecimal channel address and 2-digit
hexadecimal device subaddress
[,alTO]
specifies a quarter-inch tape drive
[,SHR]
specifies the device is a shared device
c
7-24
System Generation (SYSGEN)
SYSGEN Directives
Notes:
The CACHE parameter can be applied to ACM devices (H.F8XIO), to quadruple the
normal I/O time out. This is intended for slow spooling devices with large internal
buffers using XON/XOFF (WXON) flow control. The CACHE parameter can also be
applied to a buffered tape processor (BTP), but not to the cache disk accelerator.
7.6.16.4 DEVICE Syntax for lOP Printers and Null Device
Syntax
DEVICE= {aa I (aa,n,inc)} [,CACHE] [,DTC=It] [,FEOP]
[,HANDLER= {name I (name[,II,S] [,C])}] [,IOQ=mode] [,OFF] [,PHYSA=ccaa]
[,SHR] [,SPOOL=(code,code, ... )]
aa
is the 2-digit hexadecimal device subaddress. The first digit is the
controller address; the second digit is the device address.
n
is an optional parameter specifying the decimal number of devices starting
at the subaddress
inc
is an optional parameter specifying the hexadecimal address increment for
each additional device. If not specified, the default is 1.
[,CACHE] specifies a cache device. This option is not necessary if the associated
CONTROLLER statement includes CACHE.
[,DTC=It]
is a 2-character device mnemonic (see Table 7-1). If not specified, the
device mnemonic specified on the associated CONTROLLER directive is
used.
[,FEOP]
specifies that J.SOUT inhibits the normal initial form feed and terminates
all printing with an additional form feed, if specified for LP device. FEOP
is applicable only on electrostatic printers and laser printers that retain the
last page of output until a form feed (EJECT) is received.
It
[,HANDLER= {name I (name[,II,S] [,C])}]
name
is the 1- to 8-character handler name (see Table 7-1). If not
specified, a default handler is assigned in the following
manner:
• If the device has a default handler associated with it in
Table 7-1, that handler is assigned to the device.
• If the device does not have a default handler associated
with it, the device is assigned the same handler as the
device which was most recently defined to the subchannel
to which this device is being defined (aa above). If no
device has yet been defined to this subchannel, then the
handler associated with the CONTROLLER directive for
the subchannel is assigned.
MPX-32 Reference Volume III
7-25
SYSGEN Directives
~:"."'
(.. jP
..."
"
An error is generated if an invalid handler is selected by
default.
specifies interrupt priority level reentrancy, one copy per
channel
S
specifies system level reentrancy, one copy per system
C
specifies one COT for each UDT
[,IOQ=mode]
is used by the lOP and GPMC to indicate the I/O queue entries are to be
linked from the UDT (IOQ=DEV) or from the COT (IOQ=CONT). The
default mode is IOQ=CONT. However, most handlers provide their own
initialization for this parameter and ignore any value specified by
SYSGEN. Therefore, this parameter should not be used for any standard
MPX-32 handler supplied by Encore unless such a requirement is specified
in the installation instructions for that handler.
[,OFF]
specifies that the device or devices described by this directive are to be
SYSGENed in an offline state
[,PHYSA=ccaa]
specifies the physical (bus) channel address and device subaddress for
devices. Used when logical channel and subaddress do not match the
physical channel and subaddress.
ccaa
[,SHR]
is the 2-digit hexadecimal channel address and 2-digit
hexadecimal device subaddress
specifies the device is a shared device
[,SPOOL=(code,code, ... )]
indicates the device is available for automatic selection as the destination
device for spooled printed and punched output. code consists of 2character codes separated by commas. The codes and their use for output
are:
BL
batch
SLO
batch
SBO
BB
real-time
SLO
RL
real-time
SBO
RB
Notes:
The CACHE parameter can be applied to ACM devices (H.F8XIO), to quadruple the
normal I/O time out. This is intended for slow spooling devices with large internal
buffers using XON/XOFF (WXON) flow control. The CACHE parameter can also be
applied to a buffered tape processor (BTP), but not to the cache disk accelerator.
7.6.17 DISP Directive
The DISP directive determines the number of entries in the dispatch queue. One entry
is used for each concurrently operating task. Each entry requires 64 words of resident
image storage. This directive appears under the //SOFIW ARE /pARAMETERS
subsection.
7-26
System Generation (SYSGEN)
()
SYSGEN Directives
('
Syntax
DISP=entries
entries
specifies the decimal number of entries in the dispatch queue. This value
cannot exceed 255 and must be at least 8. If not specified, the default is
10.
7.6.18 OPTIMO Directive
The DPTIMO directive specifies a time-out value for resource delays encountered
when attempting to access a multiprocessor, shared-volume resource. If this directive
is not specified, the system assigns a sufficient number of time units to result in a
delay a maximum of 1 second long. This directive appears under the //SOFTWARE
/pARAMETERS subsection.
Syntax
DPTIMO=num
num
is the decimal number of time units to wait before timing out. Because a
delay request is likely to be entered within a time unit, num should be a
value large enough to result in delay one time unit longer than the actual
maximum delay desired. For example, if NTIM is 1 and MTIM is 60,
DPTIMO must be 61 (l second plus 1 time unit) to ensure a maximum
delay of 1 second. (For more information on time units, see the MTIM
Directive and NTIM Directive section of this chapter.)
7.6.19 DPTRY Directive
The DPTR Y directive specifies the decimal number of times that a system tries to
obtain a multiprocessor resource before returning a denial. If this directive is not
specified, the default is 0, which causes the system to try until the resource is
obtained. This directive appears under the //SOFTWARE /pARAMETERS
subsection.
Syntax
DPTRV=num
num
is the decimal number of tries to obtain a multiprocessor resource.
7.6.20 DTSAVE Directive
The DTSAVB directive specifies the decimal number of minutes to elapse before
J.DTSAVB is resumed. If this directive is not specified, the default time is 5 minutes.
This directive appears under the //SOFTWARE /pARAMETERS subsection.
MPX·32 Reference Volume III
7-27
SYSGEN Directives
Syntax
DTSAVE=time
time
is the nwnber of minutes to elapse before J.DTSAVE reswnes.
7.6.21 /lEND Directive
The fIEND directive is required as the last directive in the SYSGEN directives file.
Syntax
fiEND
7.6.22 ENDPGOUT Directive
The ENDPGOUT directive specifies the maximwn percentage of total memory desired
for free pages on a demand page system, the upper page-out threshold. J.SWAPR
stops writing pages queued for page-out to the swap file when the ENDPGOUT value
is reached or the queues are empty.
If NODEMAND is specified, this directive is ignored. If this directive is not specified
and demand page processing is supported, the default is 25% of the total available
memory on the system.
This directive appears under the IfSOFfW ARE /pARAMETERS subsection.
Syntax
ENDPGOUT::xx
xx
is a percentage (00 through 100) of the total available memory (SRAM
only) on the system. H.SINIT converts this percentage to the correct
nwnber of pages (map blocks). xx must be greater than the value specified
for BEGPGOUT.
7.6.23 EXTDMPX Directive
The EXTDMPX directive can be used on a system wide basis to designate the starting
address of the TSA and extended MPX-32 (if configured). This directive appears
under the /lSOFTW ARE /pARAMETERS subsection.
This directive applies only to the TSA when extended MPX is not configured. Refer
to Reference Manual Volwne I, Chapter 3, for information on how to configure
extended MPX-32.
C"'·
I
,
7·28
System Generation (SYSGEN)
'
)
SYSGEN Directives
(
The NOTSA or TSA option is ignored when the load module has been cataloged in
the compatible mode, or using the TSA keyword in the cataloger EX1D'MPX
directive. The NOTSA or TSA option is effective only when the load module has
been cataloged using the SYSTSA keyword in the Cataloger EXTDMPX directive.
When this requirement has been met, a TSM or M.PTSK request will override the
SYSGEN request.
If the EXTDMPX directive is not used, the default is MINADDR and NOTSA. This
directive establishes the default TSA and extended MPX-32 logical starting address
unless overridden via the CATALOG, TSM, or M.PTSK assignments.
Syntax
EXTDMPX={logmapbll MAXADDR I MINADDR} [,NOTSA I ,TSA]
logmapbl
is a decimal value between 64 and 2047 that specifies a starting map
block in the task's logical address space where the TSA (optionally) and
extended MPX-32 (if configured) are positioned. The NOTSA(fSA
keyword controls positioning of the TSA.
MAXADDR positions the TSA (optionally) and extended MPX-32 (if configured) at
the top of the the task's logical memory. The NOTSA(fSA keyword
controls positioning of the TSA.
MINADDR positions the TSA and extended MPX-32 (if configured) at the bottom of
the task's logical memory above MPX-32 (when mapped in), and below
the task's DSECT. The TSA keyword defaults to NOTSA for
MINADDR.
NOTSA
directs the logical position of the TSA to be above MPX-32 (when
mapped in) and below extended MPX-32 (if configured and at
MINADDR), and below the task's DSECT.
TSA
directs the repositioning of the TSA in accordance with the MAXADDR,
or logmapbl specification used. For MAXADDR the TSA is located at
the top of the task's logical memory, followed by extended MPX-32 (if
configured). For logmapbl, the TSA logically starts at logmapb/,
followed by extended MPX-32 (if configured).
Note:
An error, ***INVALID KEYWORD, is displayed on the user's terminal (or
printed to the listed output) if NOTSA or TSA keywords are incorrectly
spelled. SYSGEN aborts and no image is built.
At runtime, values for MAXADDR or /ogmapb/ that conflict with the task's
code, data, or partition memory requirements cause an abnormal termination
in the task activation.
MPX·32 Reference Volume III
7·29
SYSGEN Directives
( -,."
l~"
7.6.24 /FILES Directive
....\."
The /FILES directive designates the system files subsection of the //SOFfWARE
section. This section is included for compatibility only.
Syntax
IFILES
7.6.25 FL TSIZE Directive
The FLTSIZE directive is included for compatibility and is ignored by SYSGEN.
Items following this directive on the same line are ignored.
Syntax
FLTSIZE
7.6.26 //HARDWARE Directive
The //HARDWARE directive indicates the beginning of the hardware configuration
section of directives. This directive is required.
Syntax
IIHARDWARE
7.6.27 . HELP Directive
The HELP directive specifies the volume and/or directory containing help files. The
default is @SYSTEM A(HELP) directory. The directive also activates J.HLP. This
directive appears under the //SOFTWARE /pARAMETERS subsection.
Syntax
HELP [,VOL=vo!name] [,DIR=dirname]
vo/name
is the volume where help files are located. If not specified, the default is
the SYSTEM volume.
dirname
is the directory where help files are located. If not specified, the default is
the HELP directory.
I~"'.·
\....)
7·30
System Generation (SYSGEN)
SYSGEN Directives
7.6.28 IINTERRUPTS Directive
The /INTERRUPTS directive designates the interrupt subsection of the
I/HARDWARE section. This directive is required.
Syntax
IINTERRUPTS
7.6.29 IOQPOOl Directive
The 10QPOOL directive specifies the number of words to reserve at SYSGEN for the
10Q memory pool. This directive appears under the //SOFTWARE /pARAMETERS
subsection. If this directive is specified, the 10Q memory pool is used only for IOQ
requests. IOQ memory pool is required for each preallocated 10Q and for each I/O in
progress.
To estimate the minimum size to request for the IOQ memory pool, calculate the
average 10Q size (26 words plus the length in words of the associated I/O command
list (IOCL». (The length of the 10CL varies according to the I/O operation and the
device.) The calculated size is rounded up to a doubleword. Then multiply the
average IOQ size by the estimated number of 10Qs in use at anyone time.
The size of the 10QPOOL should be greater than the worst case I/O load. If the
10QPOOL becomes used up, causing rollover to miscellaneous memory pool, the
probability of deadlock occurring from requesting memory pool increases. When
rollover to miscellaneous memory pool occurs, a bit (C.ROLIOQ) is set in the
communications region.
If the MNWI directive is not specified, unprivileged tasks can have one wait I/O or
five nowait I/Os outstanding at a given time. Privileged tasks can have any number of
nowait I/Os outstanding.
Syntax
IOOPOOl=n[,PERMIOQ [,NOROll]]
n
is the decimal number of words to reserve. If n is not specified, an IOQ
memory pool is not reserved and the memory pool that is specified by the
POOL directive handles any 10Q requests.
PERMIOO specifies static 10Q. This parameter is valid only when parameter n is
greater than O. PERMIOQ enables an 10Q to be allocated when the file is
opened and deallocates that 10Q when the file is closed. If PERMIOQ is
not specified, 10Qs are allocated as described in the Operating System
Memory Allocation section, in Chapter 3 of MPX-32 Reference Manual,
Volume I.
NOROll specifies no rollover to the memory pool specified by the POOL directive
(-
for static 10Qs when the 10Q memory pool is full.
MPX·32 Reference Volume III
7·31
SYSGEN Directives
7.6.30 IPU Directive
The IPU directive specifies an IPU will be configured into the system. This directive
appears under the //HARDWARE /pARAMETERS subsection.
Syntax
IPU
7.6.31
ITIM Directive
The mM directive provides the expiration time interval of the RTOM interval timer.
This directive appears under the //SOFIWARE /pARAMETERS subsection. If this
directive is not specified, the default time interval is 38.4 microseconds.
Syntax
ITIM=value
value
is the quantity expressed in tenths of microseconds of an RTOM interval·
timer time quantum. For example, 38.4 microseconds is represented as
384.
7.6.32 ITLB Directive
The ITLB directive generates an Indirectly Connected Task Linkage Block. This
directive appears under the //SOFTWARE /pARAMETERS subsection. One ITLB
directive is required for each indirectly linked task concurrently active in the system.
Syntax
ITLB=intlevel
intlevel
is the 2-character hexadecimal interrupt priority level where the task will
be indirectly connected
7.6.33 JOBS Directive
The JOBS directive specifies the maximum number of batch jobs that can be
concurrently active. Any number is valid. However, a large number can cause an
increase in system response time due to increased system overhead associated with
J.TSM processing. Therefore, 10 is suggested. If this directive is not specified, the
default is 1.
This directive appears under the //SOFIWARE /TABLES subsection.
7-32
System Generation (SYSGEN)
SYSGEN Directives
Syntax
JOBS=number
number
is the number of entries in the job table.
7.6.34 KllMO Directive
The KTIMO directive specifies the number of seconds the kill directive will attempt to
abort a task before it kills it. If 0 is specified, an immediate kill is performed. If this
directive is not specified, a kill is performed after 10 seconds. This directive appears
under the //SOFTWARE /pARAMETERS subsection.
Syntax
KTIMO=number
number
is the decimal number of seconds to attempt an abort
7.6.35 LOD Directive
The LOD directive specifies a system listed output device that is the default device for
SLO. This directive is required if a line printer is configured. This directive appears
under the //HARDWARE /SYSDEVS subsection.
(
Syntax
LOD=devmnc [,IBP]
devmnc
is the 2-character device mnemonic (see Table 7-1), the 2-digit
hexadecimal channel number. and the 2-digit hexadecimal device
subaddress.
IBP
inhibits banner page produced on the SLO device
7.6.36 LOGON Directive
The LOGON directive specifies whether users may log into MPX-32 multiple times
using the same owner name. It also provides an option for restricting the owner name
"SYSTEM" from logging on to more than one TSM device at a time. If the LOGON
directive is not specified. J.TSM allows one logon per owner name.
This directive appears under the //SOFTWARE /pARAMETERS subsection.
('
MPX·32 Reference Volume III
7-33
SYSGEN Directives
{~.
',j
Syntax
LOGON={MULTI [,NOSYS] I SINGLE}
MULTI
1.TSM allows a user to log on multiple times using the same owner name
[,NOSYS] restricts the owner name "SYSTEM" to one logon at a time
SINGLE
1.TSM allows one logon per owner name
When an owner name is logged on multiple times, all messages and signals directed to
that owner name go to all terminals logged on with that owner name. (See the
BATCHMSG directive in this chapter for information on inhibiting task messages.)
Note: This directive was previously called LOGIN. "LOGIN" in place of
"LOGON" remains valid syntax.
7.6.37 MACHINE Directive
The MACHINE directive indicates the type of computer for which the resultant
system is being configured. If this directive is not specified, any CONCEPT/32
machine can be used.
If the type of computer specified is a CONCEPT 32/2000, the system file
OH.32_0UT is dynamically assigned as SYSGEN's object module file (OBI) and a
mapped out image is built. If any other type of computer is specified or if the entire
directive is omitted, OH.32 is assigned to OBJ and a mapped in image is built. These
file assignments can be overridden by assigning OBI before running SYSGEN. (See
section 7.3 of this chapter for more information on assigning the object module file.)
If this is done, the MACHINE directive indicates only the computer type; the image is
built from the specified object module file. Any conflicts are resolved by SYSGEN in
a later phase or by H.SINIT.
The MACHINE directive controls the automatic console configuration functionality.
Automatic console configuration is the process of dynamically configuring the
operator console for a CONCEPT 32/2000 system. This console will be dynamically
configured at the CPU's F-class channel.
If no MACHINE directive is specified or if a CONCEPT 32/2000 is specified
(MACHINE=2 0 0 0), the operator console will be dynamically configured when the
resultant system image is booted on a CONCEPT 32/2000 machine. The operator
console will not be dynamically configured if a computer type other than a CONCEPT
32/2000 is specified or the system image is booted on a machine other than a
CONCEPT 32/2000.
If this directive is specified, it must be the first directive in the //HARDWARE
/pARAMETERS subsection.
Syntax
MACHINE=type
type
7-34
is the machine type 3267, 3287, 3297 or 2000.
System Generation (SYSGEN)
SYSGEN Directives
(
7.6.38 MAPOUT Directive
The MAPOUT directive designates that the default execution mode for aU tasks
cataloged with the ENVIRONMENT keyword SYSMAP is executed with MPX-32
mapped out of the task's address space. If neither the MAPOUT or NOMAPOUT
directive is specified the compatible or NOMAPOUT mode is the default.
If the MAPOUT directive is present with a MACHINE directive specifying any type
other than 2000, or if both MAPOUT and NOMAPOUT are specified, a
***CONFLICTING OPTIONS error is generated by SYSGEN. If this error occurs,
SYSGEN aborts and no image is produced.
This directive appears under the I/S0FTWARE /pARAMETERS subsection.
Syntax
MAP OUT
7.6.39 MDT Directive
The MDT directive enables rapid file allocation through a memory resident descriptor
table (MDT). The MDT's parameters are defined by this directive, and module
H.MDT is included in the resident operating system. This directive appears under the
//SOFTWARE {fABLES subsection.
Syntax
MDT=n [,BLOC=b]
n
specifies the decimal number of MDT entries. MDT entries are 192 words
in length. To accommodate collision resolution, the actual number
allocated is 25% greater than the specified number.
[,BLOC=b] specifies the decimal starting physical map block number. If not
specified, the default is the highest contiguous memory available.
If the specified starting map block is not available, initialization processing halts and
an abort code is displayed at system initialization.
7.6.40 IMEMORY Directive
The /MEMORY directive designates the memory subsection of the //HARDWARE
section. This directive is required.
Syntax
IMEMORY
MPX-32 Reference Volume III
7-35
SYSGEN Directives
7.6.41
MMSG Directive
The MMSG directive specifies the maximum number of no-wait messages that an
unprivileged task can send. If this directive is not specified, the default is 5. This
directive appears under the IISOFTW ARE /pARAMETERS subsection.
Syntax
MMSG=num
num
is the maximum number of no-wait messages to be sent by a unprivileged
task.
7.6.42 MNWI Directive
The MNWI directive specifies the maximum number of no-wait I/O requests that can
be concurrently outstanding for a task. If this directive is not specified, the default is
5. This directive appears under the IISOFTW ARE /pARAMETERS subsection.
Syntax
MNWI=num
num
is the maximum number of no-wait I/O requests that can be concurrently
outstanding for a task.
7.6.43 MODE Directive
The MODE directive requests the following special system operations:
• Continuous Batch - Batch stream input from SID is processed until the job control
statement $$$ is encountered. All $$ job control statements are ignored.
• Inhibit Banner Page - Suppresses the banner page produced by system output
tasks when processing SLO files.
• Inhibit Mount Message - Suppresses the mount message produced by I.MOUNT.
This specification is not valid with multivolume magnetic tape operations.
• Dump - Performs a dump if an independent task aborts.
• Scratchpad Locations - Does not zero unused CPU scratchpad locations at IPL.
• Inhibit Operator Intervention - Suppresses all prompts normally displayed on the
system console during system initialization.
• Real-time Accounting - Turns real-time accounting on or off.
Specify a separate MODE directive for each mode desired. If no MODE directive is
specified, only real-time accounting is functional in the resulting system image. If this
directive is specified. it appears under the IISOFTWARE /pARAMETERS subsection.
7-36
System Generation (SYSGEN)
SYSGEN Directives
(.
Syntax
MODE=mode
mode
is any of the following:
DUMP
sets dump request for aborting real-time tasks
LSPA
inhibits zeroing of unused scratchpad locations during IPL
processing. If not specified, the IPL process zeroes all unused
CPU scratchpad locations.
ONRA
turns real-time accounting on. (This is the default.)
OFRA
turns real-time accounting off
SCBT
sets continuous batch
SIBP
sets inhibit banner page
SIMM
sets inhibit mount messages for nonmultivolume magnetic
tape operations
SNOP
sets inhibit operator intervention
7.6.44 MODULE Directive
(
The MODULE directive names optional user modules to be included in the MPX-32
resident image. One MODULE directive is required for each user module to be
included. This directive appears under the //SOFfWARE /MODULES subsection.
'."
/
Syntax
MODU LE=(name,module ,entpoints)
name
is the 1- to 8-character ASCII module name. The name cannot contain a
comma, an equal sign, or a left or right parenthesis. The module name
N.ACXRF is reserved for use only as module number 12.
module
is a 2-digit decimal number representing the internal identification number
of the module. Modules 00 through 12 are reserved for MPX-32 modules.
A module number of 12 is allowed only if the module name is
N.ACXRF.
entpoints
is the hexadecimal number of entry points contained in this module. The
last entry point of each user-supplied module is an initialization entry
point called by SYSGEN during construction of the MPX-32 image and is
overlaid following execution. This entry point should not be included in
entpoints.
Module initialization must include the system macros M.EIR, M.xIR, M.MODT, and
M.SVCT.
MPX-32 Reference Volume III
7-37
SYSGEN Directives
7.6.45 /MODULES Directive
The /MODULES directive designates the modules subsection of the //SOFTWARE
section. If the MODULE directive is not specified, this directive is not required.
Syntax
/MODULES
7.6.46 MRUN Directive
The MRUN directive specifies the maximum number of no-wait run requests to be
sent by a task. If this directive is not specified, the default is 5. This directive appears
under the //SOFTWARE /pARAMETERS subsection.
Syntax
MRUN=num
num
is the maximum number of run requests that can be sent by a task.
7.6.47 MSGPOOL Directive
The MSGPOOL directive specifies the number of words to reserve at SYSGEN for
the MSG memory pool. This directive appears under the //SOFTW ARE
/pARAMETERS subsection. If this directive is specified, any message or run request
queue (MRRQ) requests use this memory pool. Each MRRQ request corresponds to a
message or run request sent by a task. To estimate the minimum size to request for
MSG memory pool, calculate the average message send size or message return size
(whichever is greater) and add 8 words for a message header. Multiply this average
. size by the estimated number of messages at any instant. The specified size is rounded
up to a doubleword. Messages are sent from:
• J .TSM or OPCOM to physically mount volumes
• J .TSM to J.SSIN and back to batch tasks
• J.TSM to J.SOUT and J.sOEX to process spooled output
When rollover to miscellaneous memory pool occurs, a bit (C.ROLMSG) is set in the
communications region.
(0 . ),.
V
7-38
System Generation (SYSGEN)
SYSGEN Directives
Syntax
MSGPOOl=n[,NOROll]
n
is the decimal number of words to reserve. If n is not specified, the MSG
memory pool is not reserved and the memory pool that is specified by the
POOL directive handles all MRRQ requests.
[,NOROll] specifies no rollover to the memory pool specified by the POOL
directive for MRRQ requests when the MSGPooL is full
7.6.48 MTIM Directive
The MTIM directive provides the number of real-time clock interrupts per second. If
this directive is not specified, the default is 60. This directive appears under the
IISOFrW ARE /pARAMETERS subsection.
Syntax
MTIM=number
number
(
Note:
.. _.
,
is the number of real-time clock interrupts per second.
The number of time units per second is the value of NTIM divided by the
value of MTIM. See the NTIM directive in this chapter for more
information.
7.6.49 NAME Directive
The NAME directive defines static Datapool or Global Common memory partitions.
This directive appears under the IISOFTWARE /pARTITION subsection.
If multiple static partitions are defined within a map block, only one partition can be
included in the task's logical address space at a given time. One NAME directive is
required for each memory partition desired.
Syntax
NAME=name,SIZE=np,STRTPG=sp,MAP=pm
name
is the 1- to 8-character partition name
np
sp
is the decimal number of 512-word protection granules for the partition
is the logical hexadecimal starting protection granule for the partition
pm
is the starting physical decimal map block number. A map block is 2KW.
MPX-32 Reference Volume III
7-39
SYSGEN Directives
7.6.50 NO ANSI Directive
The NOANSI directive excludes support for ANSI labeled tapes from the system
image. This directive appears under the {{SOFfWARE {OVERRIDE subsection.
Syntax
NOANSI
7.6.51
NOBASE Directive
The NOBASE directive excludes support in H.EXEC, H.IPOO, H.IP04, H.IPOF, and
H. TAMM for the execution of tasks utilizing base mode addressing from the system
image. This directive appears under the IISOFfWARE {OVERRIDE subsection.
Syntax
NOBASE
7.6.52 NOCMS Directive
The NOCMS directive automatically excludes support for MPX-l.x compatibility
mode services (modules H.ALOC, H.FISE, H.MONS, and H.CALM) from the system
image. Software that calls a removed compatibility mode system module is aborted
with an SV09 abort code. Do not include this directive in the SYSGEN file if you
plan to use compatiblility mode services.
This directive appears under the IISOFfWARE {OVERRIDE subsection.
Syntax
NOCMS
7.6.53 NODEMAND Directive
The NODEMAND directive indicates demand page processing is not allowed.
Demand page processing is supported when the mapped out object file is assigned at
SYSGEN execution. If other than the mapped out object file is assigned, demand
page is not supported, and this directive is ignored.
If specified, this directive appears under the IISOFTWARE /pARAMETERS
subsection.
Syntax
NODEMAND
7-40
System Generation (SYSGEN)
SYSGEN Directives
7.6.54 NOLACC Directive
The NOLACC directive overrides the MPX-32 default option of tracking last date,
time, and owner name of access to task level resources. This directive, if specified,
appears under the IISOFfW ARE /OVERRIDE subsection.
Syntax
NOLACC
7.6.55 NOMAPOUT Directive
The NOMAPOUT directive designates that the default execution mode for all tasks
cataloged with the ENVIRONMENT keyword SYSMAP is executed with MPX-32
mapped into the task's address space. If neither the MAPOUT nor NOMAPOUT
directive is specified the compatible or NOMAPOUT mode is the default.
If both MAPOUT and NOMAPOUT are spectified, a ***CONFLICTING OPTIONS error is generated by SYSGEN. If this error occurs, SYSGEN aborts and
no image is produced.
This directive appears under the IISOFfWARE /pARAMETERS subsection.
Syntax
NOMA POUT
7.6.56 NOSYSVOL Directive
The NOSYSVOL directive prevents mounting and use of the system volume. Use
this directive only when the system is to be configured with no system volume. It is
for use with 3.0 or later revisions of Reflective Memory System Software (RMSS).
This directive forces NOCMS.
This directive appears under the IISOFTWARE /OVERRIDE subsection.
Syntax
NOSYSVOL
7.6.57 NOTDEF Directive
The NOTDEF directive excludes support for the TERMDEF facility from the system
image. This directive appears under the IISOFTWARE IOVERRIDE subsection.
c
Syntax
NOTDEF
MPX-32 Reference Volume III
7-41
SYSGEN Directives
'.,
I
'
c·
7.6.58 NOTSMEXIT Directive
The NOTSMEXIT directive keeps TSM active even though it is not in use. This is
the default directive. If specified, it appears under the I/S0FrWARE
/pARAMETERS subsection. To enable exit of TSM when inactive, see the
TSMEXIT Directive.
Syntax
NOTSMEXIT
7.6.59 NTIM Directive
The NTIM directive provides the number of real-time clock interrupts per time unit.
If this directive is not specified, the default is 60. This directive appears under the
//SOFfWARE /pARAMETERS subsection.
Syntax
NTIM=number
number
Note:
is the number of clock interrupts per time unit.
The number of time units per second is the value of NTIM divided by the
value of MTIM. See the MTIM directive in this chapter for more
infonnation.
7.6.60 OTHERS Directive
The OTHERS directive specifies access rights allowed to users who are not the owner
or members of the project group associated with a partition previously defined with a
NAME directive. If more than one NAME directive has been specified, the OTHERS
directive only applies to the last one specified. If this directive is not specified,
default is OTHERS=(R).
If both read and write access are desired, a comma must be used as a delimiter, for
example, OTHERS=(R,W).
The OTHERS directive must always be specified last when OWNER and/or
PROJECT directives are also specified. The order is OWNER, PROJECT, OTHERS.
This directive appears under the //SOFfWARE /pARTITION subsection.
o
7·42
System Generation (SYSGEN)
SYSGEN Directives
Syntax
OTHERS=( [R] [,W] [,N] )
R
specifies read access is allowed
W
specifies write access is allowed
N
specifies no access is allowed
7.6.61 /OVERRIDE Directive
The /OVERRIDE directive designates the override subsection of the //SOFrWARE
section. This directive is required only if one or more directives belonging under the
jOVERRIDE subsection is specified.
Syntax
/OVERRIDE
7.6.62 OWNER Directive
The OWNER directive specifies the owner name and associated access rights that
apply to the partition previously defined in a NAME directive. If more than one
NAME directive has been specified, the OWNER directive only applies to the last one
specified. If this directive is not specified, default is OWNER=(SYSTEM,R,W).
(
This directive appears under the //SOFrWARE /pARTITION subsection.
Syntax
OWNER=(name [,R] [,W] [,N] )
name
is the 1- to 8-character owner name to be associated with the partition
R
specifies read access is allowed
W
specifies write access is allowed
N
specifies no access is allowed
MPX-32 Reference Volume III
7-43
SYSGEN Directives
7.6.63 OWNERNAME Directive
The OWNERNAME directive prevents the characters of the user's owner name from
echoing to the terminal screen as the user logs on. If OWNERNAME=NOECHO is
specified, no terminals will echo the owner name. If OWNERNAME=ECHO is
specified or if the OWNER NAME directive is not included in the SYSGEN file, all
terminals will echo the owner name.
This directive appears under the //SOFTWARE /SECURITY subsection.
Syntax
OWNERNAME={NOECHO I ECHO}
NO ECHO J.TSM inhibits echoing of owner names on all terminals including the
system console
ECHO
J.TSM allows echoing of owner names on all terminals including the
system console. This is the default.
7.6.64 /PARAMETERS Directive
The /pARAMETERS directive designates the beginning of the parameters subsection
of the //HARDW ARE and IISOFTW ARE sections. This directive is required and it
must be the first subsection of the //HARDWARE and IISOFTW ARE sections.
Syntax
/PARAMETERS
7.6.65 /PARTITION Directive
The /pARTITION directive designates the memory partition and/or global common
subsection of the //SOFTWARE section. This directive is required only if one or
more partition directives is specified.
Syntax
/PARTITION
7.6.66 PASSWORD Directive
The PASSWORD directive specifies that passwords are required to logon to MPX-32.
This directive appears under the //SOFTWARE /SECURITY subsection.
Syntax
PASSWORD
7·44
System Generation (SYSGEN)
SYSGEN Directives
(
7.6.67 PATCH Directive
The PATCH directive specifies a system patch area to append to the MPX-32 resident
image. This directive appears under the //SOFfWARE /pARAMETERS subsection.
If this directive is not specified, a system patch area is not reserved.
Syntax
PATCH=number
number
Note:
specifies the hexadecimal number of bytes to be added to the resident
MPX-32 system as a system patch area. If the extended mode was
activated at SYSGEN this specifies the hexadecimal number of bytes to
be added in the first 16KW of memory.
The system patch area is restricted by SYSGEN to the first 16KW of
memory. SYSGEN also restricts the area from exceeding the first 16KWof
memory.
7.6.68 PCHFILE Directive
The PCHFILE directive names the permanent file which the generated system uses as
its patch file. SYSGEN does not create the file; it must be supplied if patches are to
be generated. If this directive is not specified, the default is M.P ATCH.
This directive appears under the //SOFfWARE /pARAMETERS subsection.
Syntax
PCHFILE=filename
filename
is the 1- to 8-character ASCII file name of the file to contain patches for
the generated system.
7.6.69 POD Directive
The POD directive specifies the system punched output (SPO) device to use as the
default device for SBO. This directive appears under the /jHARDWARE /SYSDEVS
subsection.
Syntax
POD=devmnc
devmnc
is the 2-character device mnemonic (see Table 7-1), the 2-digit
hexadecimal channel number, and the 2-digit hexadecimal device
subaddress.
MPX·32 Reference Volume III
7-45
SYSGEN Directives
7.6.70 POOL Directive
The POOL directive specifies the size in words of the memory pool to be reserved at
SYSGEN time. The specified size of the memory pool is rounded up to the end of the
current map block. If this directive is not specified, then 1000 words are reserved for
the memory pool.
This directive appears under the //SOFfWARE /pARAMETERS subsection.
If the IOQPOOL and MSGPOOL directives are not specified, the memory pool
requested by the POOL directive is the only memory pool. This memory pool is then
used for all requests.
If the IOQPOOL and/or MSGPOOL directive is specified, the total memory pool size
is the memory pool plus the IOQ memory pool and/or the MSG memory pool. This
total is then rounded up one map block boundary.
The memory pool requested by the POOL directive is then used for miscellaneous
requests (requests other than IOQ or MRRQ requests).
This memory pool is also used when there is no space available in the IOQ memory
pool or the MSG memory pool, provided NOROLL was not specified for the IOQ or
MSG memory pool.
Syntax
POOL=words
words
7.6.71
is the decimal number of words to be reserved.
PRIORITY Directive
. The PRIORITY directive specifies the interrupt configuration and interrupt processors
to use for the target system. The interrupt processors provided are: Attention (H.IP13),
Real-time Clock (H.IPCL), and CPU Interval Timer (H.IPIT). The CPU Interval
Timer is directly connected to the lowest interrupt priority level in the system. If a
machine directive is not specified, the lowest interrupt level is 6F.
This directive appears under the //HARDW ARE /INTERRUPTS subsection.
If an IPU is SYSGENed into the system, an IPU accounting processor (H.IPUIT) is
available. This processor is directly connected to the IPU accounting interval timer at
any priority. The lowest available priority is recommended.
I/O channel interrupt levels on a CONCEPT/32 are 04 to 13.
Syntax
PRIORITY=intlev, RTOM=(channel,subaddress) [,PROGRAM=name] [,INTV]
intlev
7-46
is the 2-digit hexadecimal interrupt level. The lowest level is 6F.
System Generation (SYSGEN)
SYSGEN Directives
channel
is the 2-digit hexadecimal RTOM board or lOP RTOM function channel
address
subaddress is the 2-digit hexadecimal RTOM board or lOP RTOM function
subaddress, which is the one's complement of the RTOM relative
physical priority for the interrupt level.
[,PROGRAM=name]
is the 1- to 8-character name of the program located in the file assigned to
LFC OBJ. If the program is to be directly connected to this interrupt
level and SYSGENed with the resident operating system, the name must
be supplied. If tasks are to be indirectly connected to the interrupt level,
no program name should be supplied. An indirectly connected task
linkage block (ITLB) is defined using the ITLB directive.
[,INTV]
indicates the level is an RTOM interval timer. A device entry, whose
address is equal to the interrupt priority level, is being built in the
scratchpad.
7.6.72 PROGRAM Directive
The PROGRAM directive specifies the program names of the trap processors to be
configured on the resident system. This directive appears under the //HARDWARE
(fRAPS subsection.
(
If this directive is specified, no defaults are in effect and all trap handlers to be
included on the system must be listed. If it is not specified, the following defaults are
used:
H.IPOO
H.IPAS
H.IP02
H.IP03
H.IP04
H.IP05
H.IP06
H.IP07
H.IP08
H.IP09
H.IPOC
H.IPOF
H.IPI0
H.IP13
H.IPHT
H.IPU
H.IPUAS (if an IPU is configured)
H.CPU
If the defaults are required along with other optional system modules, the
USERPROG directive should be used instead of the PROGRAM directive.
MPX·32 Reference Volume III
7·47
SYSGEN Directives
Syntax
PROGRAM= (namel, ... name7)
namel ...name7
are 1- to 8-character ASCII program names of the trap handlers assigned
to LFC OBJ, separated by commas. A maximum of 7 names can be
entered per directive.
Note: Do not include H.CPU2 or H.EXEC2 in this directive, because the DELTA
directive automatically selects them.
7.6.73 PROJECT Directive
The PROJECT directive specifies the project group name and associated access rights
which apply to the partition previously defined with a NAME directive. If more than
one NAME directive has been specified, the PROJECT directive only applies to the
last one specified. This directive is optional. If not specified, the default is PROJECT=
(SYSTEM,R,W).
The OWNER directive must precede PROJECT and OTHERS directives if specified.
The order is OWNER, PROJECT, OTHERS.
This directive appears under the //SOFfWARE /pARTITION subsection.
Syntax
PROJECT=(name [,R] [,W] [,N] )
name
is the 1- to 8-character project group name associated with the partition
R
specifies read access is allowed
W
specifies write access is allowed
N
specifies no access is allowed
7.6.74 RLWU Directive
The RLWU directive specifies whether read/lock write/unlock applies to all memory,
or only uncached ranges. This directive should be specified only once. Additional
RLWU directives are ignored. If this directive is not specified, read/lock write/unlock
applies only to uncached ranges. This directive appears under the //HARDW ARE
/MEMORY subsection.
Syntax
RLWU={YINI
7-48
Y
specifies that read/lock write/unlock (RLWU) is employed over all
memory when memory has the read/lock attribute
N
specifies that RLWU is not employed over all memory. RLWU still
applies to uncached ranges.
System Generation (SYSGEN)
SYSGEN Directives
(
7.6.75 IRMSTABlS Directive
The /RMSTABLS directive designates the Resource Management System Tables
subsection of the I/SOFTWARE section. This directive is required if the ARTSIZE
directive is specified.
Syntax
IRMSTABLS
7.6.76 RMTSIZE Directive
The RMTSIZE directive increases the number of bytes per entry in the Resourcemark
Table. If this directive is not specified, the default is O. This directive appears under
the I/SOFfW ARE /pARAMETERS subsection.
Syntax
RMTSIZE=num
num
is a decimal number between 64 and 1000.
7.6.77 SAPASSWD Directive
The SAPASSWD directive disables the PASSWORD task so that only the system
administrator can change a password. This directive appears under the IISOFTWARE
/SECURITY subsection.
Syntax
SAPASSWD
7.6.78 ISECURITY Directive
The /SECURITY directive designates the security subsection of the IISOFfWARE
section. This directive is required only if one or more security directives is specified.
Syntax
ISECURITY
MPX-32 Reference Volume III
7-49
SYSGEN Directives
""""
(:~",,/
,
7.6.79 SEQUENCE Directive
>,
The SEQUENCE directive names load modules to be activated in a sequential manner
by SYSINIT immediately after the target system is booted. Tasks activated with this
directive must complete and exit before the next task is activated.
The system console cannot be used as a TSM terminal until all specified tasks are
complete.
SYSINIT checks the completion status of each task as it exits and displays a message
on the system console if abnormal status was returned. A maximum of 70 bytes of
call back information (in ASCII) can be sent using the receiver exit block (RXB)
when exiting a run receiver task. This information, if present, is displayed by
SYSINIT on the system console. The user status byte, if not zero, is also displayed in
decimal on the system console.
If control switch 5 is set before booting the system, task names listed in the
SEQUENCE directive will not be activated as part of the target system boot (load)
process.
This directive appears under the //SOFTWARE /pARAMETERS subsection.
Syntax
SEQUENCE=(name1, ...name7)
name1, ...name7
are the 1- to 8-character ASCII load module names to be activated,
separated by commas. A maximum of 7 names can be entered per
directive.
7.6.80 SGOSIZE Directive
The SGOSIZE directive is included for compatibility only. This directive is accepted
by SYSGEN, but the results are not used in job processing. This directive appears
under the I/SOFTWARE /FILES subsection.
Syntax
SGOSIZE=blocks
blocks
is the number of 192-word blocks of disk space to be allocated for each
SGO file
o
7-50
System Generation (SYSGEN)
SYSGEN Directives
7.6.81
SHARE Directive
The SHARE directive specifies the number of entries in the shared memory table
(SMT). Each entry defines a shared memory area; for example, CSECf, Global
Common, Datapool, or Shared Image. A minimum of 2 entries must be specified to
use the Text Editor and Volume Manager. If this directive is not specified, the default
for non-extended and mapped out images is one SMT entry for the .MPXTBLS
partition. The default for an extended MPX-32 images is two SMT entries, for the
.extdmpx and .MPXTBLS partitions.
SYSGEN automatically increments C.SMTN for these partitions.
This directive appears under the I/S0FfWARE rrABLES subsection.
Syntax
SHARE=number
number
is the number of entries in the shared memory table. It must be sufficient
to define all static and dynamic partitions.
7.6.82 SID Directive
The SID directive specifies a system input device (SID) to use as the default device in
related OPCOM commands. This directive appears under the I/HARDWARE
/SYSDEVS subsection.
Syntax
SID=devmnc [,DENSITY=density] [,PARITY=parity]
devmnc
is the 2-character device mnemonic (see Table 7-1), the 2-digit
hexadecimal channel number, and the 2-digit hexadecimal device
subaddress.
[,DENSITY =density]
is used only for 7 -track magnetic tape. H is for high density. L is for low
density.
[,PARITY=parity]
is used only for 7-track magnetic tape. E for even parity. 0 for odd parity.
7.6.83 SIZE Directive
The SIZE directive specifies the memory configuration of the target system. This
directive is required. The SIZE directive appears under the //HARDWARE
/MEMORY subsection.
Using multiple SIZE directives, memory types must be specified in order of
configuration in memory; that is, from low address to high address.
MPX·32 Reference Volume '"
7·51
SYSGEN Directives
The SIZE directive now has a second syntax rhich is preferred to the original syntax.
This new syntax allows the user to mix (MS) and RMS shared memory and to
restrict the allocation of multiprocessor shared memory to only those tasks that
physically request it. The original SIZE directive syntax is still accepted.
7.6.83.1
Preferred SIZE Directive Syntax
Syntax
SIZE=blocks, TYPE=mem [,RESERVED]
[,RMS=addr]}] [,CACHE={Y IN}]
LSHARED={NIY [, INIT= {YIN}]
SIZE=blocks
blocks is the memory size in decimal number of map blocks. Maximum
value is 2048.
TYPE=mem
mem is a memory type from the list below. E, H, and S are memory types
that a nonbase task can request with the Catalog ENVIRONMENT
directive.
!YQL
D
E
H
S
N
HI
H2
H3
Description
SelBUS (DRAM) memory (CONCEPT 32/2000 only.
See note 4.)
task delays until E class is available
task delays until H or E class is available
task delays until S, H, or E class is available
indicates absent memory
is CPU shadow memory
is IPU shadow memory
is CPU and IPU shadow memory
[,RESERVED]
reserves shadow memory for requesting tasks. This option is valid only
with types HI, H2, and H3.
[,SHARED={ NIY}]
N specifies that multiprocessor memory is allocated to any task. Y
specifies it is allocated only to tasks requesting physical memory for
shared images or static partitions. N is the default.
[,INIT={YIN}]
N specifies that the memory is not initialized at system startup. Y
specifies to initialize shared memory at system startup. Y is the default.
[,RMS=addr ]
addr is the hexadecimal address of the Reflective Memory System (RMS)
control registers
[,CACHE={ YIN}]
N specifies that memory is uncached. Y specifies that memory is cached.
Y is the default.
7-52
System Generation (SYSGEN)
SYSGEN Directives
This is a multiprocessor shared memory example for two systems with 2MB of
multi-processor shared memory and 4MB of non-shared memory. The two systems are
to share 128KW of memory. The balance of the 2MB is divided for use by the two
systems.
System 1:
/MEMORY
SIZE=512,TYPE=S
SIZE=64,TYPE=S,SHARED=Y,INIT=N,CACHE=N
SIZE=112,TYPE=S,SHARED=Y,INIT=N,CACHE=N
SIZE=80,TYPE=N,SHARED=Y,INIT=N,CACHE=N
4MB OF NON-SHARED
MEMORY
128KW TO BE SHARED
224KW TO BE USED BY
SYSTEM 1
160KW TO BE USED BY
SYSTEM 2
/PARTITION
NAME=GLOBALOl,SIZE=256,STRTPG=100,MAP=512
System 2:
(
/MEMORY
SIZE=512,TYPE=S
SIZE=64,TYPE=S,SHARED=Y,INIT=N,CACHE=N
SIZE=112,TYPE=N,SHARED=Y,INIT=N,CACHE=N
SIZE=80,TYPE=S,SHARED=Y,INIT=N,CACHE=N
MEMORY
128KW TO BE SHARED
224KW TO BE USED BY
SYSTEM 1
160KW TO BE USED BY
SYSTEM 2
/PARTITION
NAME=GLOBALOl,SIZE=256,STRTPG=lOO,MAP=512
MPX-32 Reference Volume III
7-53
SYSG EN Directives
Notes:
1.
SYSGEN memory directives must reflect the hardware cache configuration of the
target machine.
• On a 32/87 or 32/97 processor, the SYSGEN directives for uncaching should
match the memory configuration of CPU board C.
2.
3.
4.
• On a 32/67 or CMOS processor, the hardware cache configuration is software
controllable with the RLWU directive and the SIZE directive CACHE option
if the memory has the proper attributes. If memory is not cache coherent,
CACHE=N must be specified.
The CACHE=N option uncaches a physically contiguous range of memory on
half-megabyte boundaries in half-megabyte increments. This range is bounded
by the highest and lowest map blocks of contiguous ranges resulting from
multiple SIZE directives. The lower bound is set at the first specification of the
CACHE=N option and the higher bound is set at the last CACHE=N. All
memory between these bounds is uncached and the range is ended by the first
CACHE=Y. Mter this, no other CACHE=N can be specified. The CACHE
option must reflect the physical attributes of the configured memory. Memory
used as non-cache coherent must be specified as CACHE=N.
The SHARED option should be used when (MS)2 or reflective memory is shared
among processors. When (MS)2 memory is shared, ranges within physically
shared memory can be treated independently. For example, a system can be
SYSGENed with range A shared by several processors and range B treated as
nonshared. To do this, range A is specified as SHARED= Y on all processors and
should be initialized at system startup by only one processor. Range B is
specified as SHARED=N on the processor using it and as nonpresent (TYPE=N)
on the other processors. Range B should be initialized at system startup by the
processor using it.
Memory types E, H, and S must reside in SRAM memory. Type D memory
must reside in DRAM. Type D memory is only valid for the CONCEPT
32/2000 processors. If DRAM is declared on any processor other than the
CONCEPT 32/2000, it remains defined as type D memory. The restrictions for
DRAM on a CONCEPT 32/2000 apply to DRAM on other processors.
Once type D memory is defined, no more definitions of E, H, or S are valid. If
E, H, or S memory follows the definition of D memory, the following error
message is generated and no image is produced:
***TYPE=E, H OR S IS NOT VALID AFTER TYPE=D
5.
HI, H2, and H3 are not valid for the CONCEPT 32/2000. If defined on a
32/2000, shadow memory defaults to type H.
(~)
7-54
System Generation (SYSGEN)
SYSGEN Directives
7.6.83.2 Original SIZE Directive Syntax
Syntax
SIZE=nn,TYPE=c ,CLASS=x [ [,RESERVED] [,MULTI] [,MS2] ]
nn
is the size in decimal number of map blocks for phyical memory or the
number of pages for memory partitions. Maximum value is 2048.
c
is memory type D, E, H, S, N, HI, H2, or H3. E, H, and S are memory
types as described in Volume I. Absent memory is indicated by N. HI,
H2, and H3 are shadow memory types. D is DRAM memory (CONCEPT
32/2000 only).
x
is memory class C or S:
C
is core memory
S
is semiconductor memory
[,RESERVED]
reserves shadow memory for requesting tasks. Valid only with types HI,
H2,orH3.
[,MULTI]
specifies the multiprocessor memory flag is set indicating this memory is
not to be initialized during the startup procedure. This memory is to be
uncached and have read/lock, write/unlock employed in the uncached
range. It will not be initialized.
[,MS2]
identifies the shared m~mory configured as Multiprocessor Shared
Memory System (MS) rather than the MBC/MBA M¥ltiport Memory
System. Multiprocessor Shared Memory System (MS) is required for any
dual-ported memory disk. This memory is to be cached and have
read/lock, write/unlock employed. It will not be initialized. If MS2 is
used, the MULTI option must also be specified.
This is a multiprocessor shared memory example for two systems with 2MB of
multi-processor shared memory and 4MB of non-shared memory. The two systems are
to share 128KW of memory. The balance of the 2MB is divided for use by the two
systems.
MPX·32 Reference Volume III
7·55
SYSGEN Directives
System 1:
/MEMORY
SIZE=512,TYPE=S,CLASS=S
4MB OF NON-SHARED
MEMORY
128KW TO BE SHARED
224KW TO BE USED BY
SYSTEM 1
160KW TO BE USED BY
SYSTEM 2
SIZE=64,TYPE=S,CLASS=S,MULTI
SIZE=112,TYPE=S,CLASS=S,MULTI
SIZE=80,TYPE=N,CLASS=S,MULTI
/PARTITION
NAME=GLOBAL01,SIZE=256,STRTPG=100,MAP=512
System 2:
/MEMORY
SIZE=512,TYPE=S,CLASS=S
4MB OF NON-SHARED
MEMORY
128KW TO BE SHARED
224KW TO BE USED BY
SYSTEM 1
160KW TO BE USED BY
SYSTEM 2
SIZE=64,TYPE=S,CLASS=S,MULTI
SIZE=112,TYPE=N,CLASS=S,MULTI
SIZE=80,TYPE=S,CLASS=S,MULTI
/PARTITION
NAME=GLOBAL01,SIZE=256,STRTPG=100,MAP=512
I
7.6.83.3 Shadow Memory Error Messages
If shadow memory is not configured properly, the following SYSGEN directive error
message is displayed:
***
SHADOW MEMORY CONFIGURATION VIOLATION
If RESERVED is used with nonshadow memory types, the following SYSGEN
directive error message is displayed:
***
ONLY SHADOW MEMORY CAN BE RESERVED
For more information on shadow memory, refer to Chapter 10 of this volume.
"":
c·
I
7-56
System Generation (SYSGEN)
SYSGEN Directives
7.6.83.4 Shared Memory Error Messages
Note:
A system can have only one type of shared memory configured.
If CACHE=N is specified for a second region of contiguous memory, the following
message is displayed and SYSGEN aborts:
***
ONLY ONE CONTIGUOUS UNCACHED REGION ALLOWED
If INIT or RMS options are used without SHARED=Y, the following message is
displayed and SYSGEN aborts:
***
INVALID KEYWORD WHEN SHARED=Y NOT SPECIFIED
If a SYSGEN SIZE directive specifies the MULTI option for memory discontiguous
with a previous MULTI specification, SYSGEN generates a SG40 error and the
following message is displayed:
WARNING; A CONTIGUOUS MEMORY RANGE WILL BE UNCACHED
7.6.84 SMD Directive
The SMD directive is included for compatibility and is ignored by SYSGEN. Items
following this directive on the same line are ignored.
(Syntax
SMD
7.6.85 //SOFTWARE Directive
The //SOFTW ARE directive indicates the beginning of the software configuration
section of directives. This directive is required.
Syntax
//SOFTWARE
MPX~32
Reference Volume III
7·57
SYSGEN Directives
7.6.86 SVC Directive
The SVC directive increases the size of the SVC type 1 table. If this directive is not
specified, the default size is 7F. This directive appears under the I/SOFfWARE
/pARAMETERS subsection.
Syntax
SVC=num
num
is the hexadecimal number, X'80' through X'FF' of entries allowed in the
SVC type 1 table.
7.6.87 SWAPDEV Directive
The SWAPDEV directive specifies the default swap device. When an IPL or restart is
performed, the default swap device is automatically assigned as the device on which
the swap volume is mounted. This directive appears under the //HARDWARE
/SYSDEVS subsection.
If the SWAPDEV directive is not specified, the system volume is the default swap
volume.
Syntax
SWAPDEV={devmnc IIPLDEV}
devmnc
is the 2-character device mnemonic, the 2-digit hexadecimal channel
number, and the 2-digit hexadecimal device subaddress of the device to be
assigned as the swap device
IPLDEV
specifies the system volume as the swap volume
Specifying SWAPDEV=devmnc causes H.SINIT to mount the swap volume on the
specified device during IPL or restart. If any errors occur while H.SINIT is mounting
the swap device, they are handled according to whether the SYSGEN directive
MODE=SNOP has been specified. (See the MODE Directive section of this chapter
for more information.) If MODE=SNOP has been specified, H.SINIT will report
mounting errors to the system console and make the system volume the swap volume.
If MODE=SNOP has not been specified, an error message will be displayed on the
system console and H.SINIT will prompt the user with the following:
ENTER SWAP DEVICE CHANNEL AND SUBADDRESS
(OR IF SYSTEM VOLUME) :
Specifying SWAPDEV=IPLDEV causes H.SINIT to make the system volume the
swap volume. If an error occurs while H.SINIT is mounting the system volume,
H.SINIT will abort.
7·58
System Generation (SYSGEN)
SYSGEN Directives
If the SWAPDEV directive is not supplied in the SYSGEN directive file, H.SINIT
will issue the following prompt during IPL or restart, unless the MODE=SNOP has
been specified:
ENTER SWAP DEVICE CHANNEL AND SUBADDRESS
(OR IF SYSTEM VOLUME) :
This prompt will appear again if any error occurs while H.SINIT is mounting the
swap volume.
If MODE=SNOP has been specified, H.SINIT will make the system volume the swap
volume without issuing a prompt.
7.6.88 SWAPLIM Directive
The SWAPLIM directive specifies the minimum partial swap quantum. This directive
appears under the //SOFrW ARE /pARAMETERS subsection. If this directive is not
specified or if 0 is specified for n, and if memory allows, swapper swaps on demand
one map block at a time. If a number greater than 0 is supplied for n, swapper swaps
out n map blocks of the task or the entire task, whichever is smaller. To achieve total
task swapping for a 32/87 n must be at least 128. To achieve total task swapping for
a 32/67 or a 32/97 use 2048 for n. The value specified is dependent on system use.
When heavy swapping is anticipated and small tasks are running, a value between 7
and 15 is recommended.
(
Syntax
SWAPLlM=n
n
is the minimum partial swap quantum in map blocks
7.6.89 SWAPSIZE Directive
The SWAPSIZE directive specifies the initial swap file size. If this directive is not
specified, the default is 2 times the configured memory. If 0 is specified, swapping is
inhibited. This directive appears under the //SOFrW ARE /pARAMETERS
subsection.
Syntax
SW APSIZE=size
size
is the initial swap file size in megabytes
MPX·32 Reference Volume III
7·59
SYSGEN Directives
7.6.90 SWP Directive
The SWP directive is included for compatibility and is ignored by SYSGEN. Items
following this directive on the same line are ignored.
Syntax
SWP
7.6.91 SYCSIZE Directive
The SYCSIZE directive is included for compatibility only. This directive is accepted
by SYSGEN, but the results are not used in job processing. Default is tOO blocks.
** .BB This directive appears under the //SOFTWARE /FILES subsection.
Syntax
SVCSIZE=blocks
blocks
is the number of 192-word blocks of disk space to be allocated for each
SYC file
7.6.92 SYMTAB Directive
The SYMTAB directive names the permanent file where the symbol table of the
generated system is written. If the file does not currently exist, SYSGEN creates the
file. This directive is required. It appears under the //SOFTWARE /pARAMETERS
subsection.
Syntax
SVMTAB=filename
filename
is the 1- to 8-character ASCII file name of the system symbol table file
7.6.93 /SYSDEVS Directive
The /SYSDEVS directive designates the system device subsection of the
//HARDWARE section. This directive is required.
Syntax
/SVSDEVS
C'
i"
7-60
System Generation (SYSGEN)
,
. !
SYSGEN Directives
("
7.6.94 SYSMOD Directive
The SYSMOD directive replaces system modules with other modules or removes the
compatibilty mode system modules RALOC, H.FISE, H.MONS, and RCALM. One
SYSMOD directive is required for each system module to be replaced.
This directive appears under the //SOFTWARE /OVERRIDE subsection.
Syntax
SVSMOD=name) ,REPMOD=name2
name}
is the 1- to 8-character ASCII name of the system module to be replaced
or removed
name2
is the 1- to 8-character ASCII name of the replacement module or NULL
7.6.95 SYSONL Y Directive
The SYSONLY directive specifies SYSTEM as the only valid ownemame. This
directive appears under the //SOFTWARE /SECURITY subsection. If an M.KEY file
exists, this directive is ignored. For more information, refer to Chapter 10, the System
Administrator Services chapter, in this volume.
(
Syntax
SVSONLV
7.6.96 SYSTEM Directive
The SYSTEM directive names the permanent file where the generated system is
written. If the file does not currently exist, SYSGEN creates the file as a system file.
This directive is required. It appears under the //SOFTW ARE /pARAMETERS
subsection.
Syntax
SVSTEM=sysjile
sysfile
is the 1- to 8-character name of the file to contain the resident system
image generated at SYSGEN. This file name must not be the same as the
name of the current default image.
("
MPX-32 Reference Volume III
7-61
SYSGEN Directives
(\
~~.j
7.6.97 SYSTRAP Directive
The SYSTRAP directive selectively overrides any of the default trap handlers listed
under the PROGRAM directive. This directive appears under the //HARDWARE
/TRAPS subsection.
The SYSTRAP directive cannot be used if a PROGRAM directive is used.
Syntax
SYSTRAP=namel,REPTRAP=name2
namel
is the default trap handler name to be overridden (e.g., H.IPlO)
name2
is the 1- to 8-character ASCII program name assigned to LFC OBI used
in place of namel
7.6.98 /TABLES Directive
The {fABLES directive designates the tables subsection of the //SOFfWARE
directives. This directive is required.
Syntax
!TABLES
7.6.99 TERMPRI Directive
The TERMPRI directive specifies the execution priority level for all tasks activated in
the interactive terminal environment. If this directive is not specified, the default is
. priority 60. This directive appears under the //SOFfW ARE /pARAMETERS
subsection.
Syntax
TERMPRI=nn
nn
is the 2-digit decimal time-distribution priority level, 55 to 64, for
interactive processing.
7.6.100 TIMER Directive
The TIMER directive specifies the number of timer table entries to be generated in the
MPX-32 resident image. If this directive is not specified, the default value is O. This
directive appears under the //SOFTWARE {fABLES subsection.
7-62
System Generation (SYSGEN)
SYSGEN Directives
Syntax
TIMER=number
number
is the number of timer table entries to be generated
7.6.101 TITLE Directive
The TIlLE directive attaches identifying information to the SYSGEN listed output. If
this directive is specified, it must be the first directive in the directive stream.
Syntax
TITLE=data
data
is 1 to 66 ASCn characters of information
7.6.102 TQFULL Directive
The TQFULL directive specifies the maximum time quantum that a time-distribution
task can acquire prior to preemption by another time-distribution task at the same
priority level. This directive appears under the //SOFfWARE /pARAMETERS
subsection. If TQFULL or TQMIN is supplied, then both are required. TQFULL
must be greater than TQMIN. If not specified, TQFULL defaults to 600 milliseconds.
Syntax
TOFU LL=time
time
is the maximum number of milliseconds in the quantum
7.6.103 TQMIN Directive
The TQMIN directive specifies the minimum time quantum that a time-distribution
task can acquire prior to preemption by another time-distribution task at a higher
priority level. This directive appears under the //SOFfW ARE /pARAMETERS
subsection. If TQMIN or TQFULL is supplied, then both are required. TQMIN must
be less than TQFULL. If not specified, TQMIN defaults to 200 milliseconds.
Syntax
TQMIN=time
time
is the minimum number of milliseconds in the time quantum
MPX-32 Reference Volume III
SYSGEN Directives
7.6.104 TRACE Directive
The TRACE directive initializes the system trace flag word C.TRACE. This directive
appears under the //SOFfWARE /pARAMETERS subsection. Bit indicators within
C.TRACE are described in the MPX-32 Technical Manual, Volume I, Chapter 6.
If this directive is not specified, C.TRACE defaults to X'FFFFFFFE'.
Syntax
TRACE=num
num
is a 1- to 8-character hexadecimal number
If the TRACE directive is specified, the following NAME directive must be specified
under the //SOFfWARE /pARTITION subsection:
NAME=name,SIZE=16,STRTPG=3EF,MAP=60
nameis the 1- to 8- character user-specified name of the trace partition
7.6.105 /TRAPS Directive
The /TRAPS directive designates the trap descriptor subsection of the //HARDWARE
section. This directive is required.
Syntax
!TRAPS
7.6.106 TSMEXIT Directive
The TSMEXIT directive allows TSM to exit from the system when it is no longer
required. TSM will be reactivated when one of the following occurs:
• a wake up character is entered
• a task performs an M.BATCH
• a task performs an M.DEFr
If this directive is specified, it appears under the //SOFrWARE /pARAMETERS
subsection.
To disable exit of TSM, see the NOTSMEXIT Directive.
Syntax
TSMEXIT
7-64
System Generation (SYSGEN)
SYSGEN Directives
7.6.107 USERPROG Directive
The USERPROG directive specifies system modules to be included in the system
along with the default trap handlers or those specified in the PROGRAM directive.
This directive is required to include the H.ADA module. This directive appears under
the //HARDWARE /l'RAPS subsection.
Syntax
USERPROG=(namel, . .. name7)
namel, ...name 7
are 1- to 8-character ASCII program names of modules assigned to LFC
OBI, separated by commas. A maximum of 7 names can be entered per
directive.
7.6.108 /VP Directive
The /VP directive designates the Vector Processor (VP) subsection of the
//HARDWARE section. This directive is required for systems containing a VP3300 or
VP64lO.
Syntax
NP
7.6.109 VP Directive
The VP directive specifies the device characteristics of the Vector Processors to be
configured. This directive is required for systems containing a VP3300 or VP6410 VP.
This directive appears under the //HARDWARE /Vp subsection.
Syntax
VP= {(aa [,number]) I aa} [,PROGRAM=modulel]
aa
is the 2-digit hexadecimal subchannel number
number
is the number of VPs to be configured. If not specified, the default is 1.
modulel
is the name of the module used to include a VP memory partition into a
task's logical address space. If not specified, the default is H.ACBA.
(
,
~' ",
MPX-32 Reference Volume III
7-65
SYSGEN Directives
o
7.6.110 VPID Directive
The VPID directive specifies unit specific information for a VP. This directive is
required for systems containing a VP3300 or VP6410. One VPID directive must be
used for each Vector Processor specified in the VP directive. This directive appears
under the I/HARDWARE /vp subsection.
Syntax
VPID=aa, VPTYPE=tt, STARTBLK=blk, PRIORITY=intlev, INTRPT=(cc,ss)
[,PROGRAM=module2] [,IPCA=ipsize] [,BUSO=bOsize] [,BUS1=blsize]
[,BUS2=b2size] [,BUS3=b3size]
aa
is the 2-digit hexadecimal subchannel number
tt
is the type of VP: 33 specifies a VP3300, and 64 specifies a VP6410
blk
is the decimal starting physical map block address where the VP memory
partitions are to be allocated
intlev
is the 2-digit hexadecimal interrupt level
cc
is the RTOM/IOP channel address
ss
is the RTOM/IOP 2-digit hexadecimal interrupt subaddress
[,PROGRAM=module2]
module2 is the name of the interrupt handler to be used with this VP. If
not specified. the default is H.IPVP.
[,IPCA=ipsize]
ipsize is the number of pages to be allocated for the Interrupt Processor
Context. If not specified, the default is 16 pages.
[,BUSO=bOsize]
bOsize is the number of pages allocated for BUSO. If not specified, the
default is 16 pages. This parameter is valid for VP6410 only.
[,BUS1 =bI size]
bI size is the number of pages allocated for BUS 1. If not specified. the
default is 32 pages for a VP6410 and 48 pages for a VP3300.
[,BUS2=b2size]
b2size is the number of pages allocated for BUS2. If not specified. the
default is no pages. This parameter is valid for VP3300 only.
[,BUS3=b3size]
b3size is the number of pages allocated for BUS3. If not specified. the
default is no pages. This parameter is valid for VP3300 only.
7-66
System Generation (SYSGEN)
(
8
System Debugger
8.1 Introduction
The System Debugger is provided on the Master SDT. It debugs the resident
operating system as well as SYSGENed user interrupt and I/O handlers. The
debugger is SYSGENed as part of the resident MPX-32 starter system, and it can be
included in any user configuration of the resident system by using the SYSGEN
directive USERPROG=DEBUG.
The System Debugger is composed of two parts: a small portion runs mapped as part
of the resident operating system and occupies approximately 600 words of system
logical address space; the remaining portion runs unmapped and represents the bulk of
the debugger. The unmapped portion permanently occupies approximately 8KW of
physical memory, but does not increase the size of the logical address space devoted
to the operating system.
The system debugger only operates in privileged mode because it is using stand-alone
I/O. Therefore, even privileged instructions are executed. Invalid instructions are
flagged with an asterisk immediately following the opcode text. The instructions that
may alter the program counter in the pseudo-PSD are executed, such as LPSD, BRI,
SVC, etc., and traced by the debugger.
(
Unusual instruction sequences (branch increment with positive register contents,
double word instructions using an odd number register, etc.) are flagged with a
question mark following the instruction text. These inform the user of possible
problems.
The debugger always starts in symbolic mode to allow addressing by base name plus
offset. The AB directive switches to absolute addressing. The SY directive switches
back to symbolic addressing. (Absolute or symbolic modes apply to all address
displays.)
Each time the debugger is entered, C.GINT (the global interrupt counter) is
incremented by 1. When the debugger is exited, C.GINT is decremented by 1. This
defers all task scheduling during the debug session. To allow a schedule event to
occur while debugging, use the CT directive specifying the address of the next
instruction to be executed.
Physical and virtual (logical) modes are maintained by the System Debugger. When
entry into the debugger is made from an unmapped state, the physical mode is the
default. When entry is made from a mapped state, the virtual mode is the default.
Execution traces and pure memory references are relative to the default mode
established on entry. Symbolic references to memory toggle the display mode to that
of the base symbol used; however, the execution trace mode remains in the mode of
entry. The BA directive can be used to define or redefine the attributes of any base.
Execution tracing is not permitted within a mapped out task's virtual address space.
MPX-32 Reference Volume III
8·1
Using the Debugger
8.2 Using the Debugger
8.2.1
Arithmetic and Special Operators
The debugger recognizes the following characters as unique operators allowable in any
command or expression:
Character
Usage
GthruZ
R
parenthesis ( )
Colon (:)
Asterisk (*)
Slash (j)
Semicolon (;)
Question Mark (?)
Dollar Sign ($)
Plus Sign (+)
Minus Sign (-)
Asterisk (*)
Slash (j)
Ampersand (&)
At-sign (@)
Right Angle Bracket (»
symbolic base values
register designator
contents of
current value of last displayed contents
indirect address if first character in a field
current total
task high address
task low address
current PC contents from PSD
field on left added to field on right
field on right subtracted from field on left
field on left multiplied by field on right
«)
field on left is shifted left by the count in
the right side field
ASCII text delimiter
subfield delimiter
Left Angle Bracket
Apostrophe (')
Backslash (\)
field on left divided by field on right
field on left is ORed with field on right
field on left is ANDed with field on right
field on left is shifted right by the count
in the right side field
'-/"
o
8-2
System Debugger
Using the Debugger
8.2.2 Special Functions
The debugger expects to read a 2-character directive and options; however, the
following special functions may be input instead of the normal directives:
Character
Usage
1\
display previous location
display location indirect to current location
display next location
right shift current location and display
left shift current location and display
display current location
*
>
<
$
These functions require only the one byte of input.
8.2.3 Execution Breakpoints
A breakpoint is an address where program execution can be interrupted. Eight fixed
breakpoints can be defined. In addition, a one-shot breakpoint can be established for
the directed execution directives GO or CT.
(
MPX-32 Reference Volume III
8-3
Using the Debugger
8.2.4 Debugger Bases
The debugger uses a range of l-character bases to provide symbolic references to
memory. Once established, the base characters (characters G through Z) can be used
in any directive or arithmetic expression. The following bases are initialized by the
debugger when loaded with MPX-32:
Base
G
H
1
J
K
L
M
N
o
P
Q
R
S
T
U
V
W
X
Y
Z
Note:
Module
H.TAMM
H.MEMM
H.EXEC
available
available
H.ALOC
H.FISE
logical starting address of current task's TSA
available
available
IP06 (SVC)
H.SWAPR
X'78000' (User DEBUG)
H.TSM
logical starting address of current task's DSECT
H.VOMM
H.MONS
H.REXS
H.IOCS
H.REMM
401 is equivalent to 40+1 or 1+40.
8.2.5 Base Characters
The characters 'G' through 'Z' can be set to any value by the BA (Base) directive.
For example,
BA G 427FO
defines G as location 427FO. G appears in all address displays in place of 427FO.
G can be used in any directive and it is processed as 427FO.
All predefined bases except N and U have the physical attribute by default; Nand U
have the virtual (logical) attribute by default. These attributes are in effect until
redefined using the BA directive. Virtual addresses are established using the map
registers of the current task executing within the CPU. Therefore, if no task is
current, the virtual attribute is undefined at that instance. Extended MPX-32 module
bases are virtual when a task is current.
c
8-4
System Debugger
Using the Debugger
(
8.2.6 Operator Restrictions
Arithmetic expressions are evaluated left to right.
Operators can appear in any directive and are not restricted in length. For example:
AR D9C35FFF,@3800000,>14
This results in a hexadecimal 18.
AR *34595,<2, +Z, +3000
Iflocation 34595 contained 500 (hex) and Z was set to 30000, the above expression
has a value of 34400.
DM 0 + 34C2 -1>2
The location specified by base 0 was previously set to 30000, so the DM location is
CD30 (30000 + 34C2 -1 and right-shifted 2 bits).
The above examples illustrate expressions that can be used in any appropriate
directive.
8.2.7 Expressions
The debugger processes expressions from left to right. For example,
(
AR 2*32+G/2
breaks down to 2 times 32 plus the value of G. That total is divided by 2 and the
answer is typed.
8.2.8 Registers
The contents of a register is specified in any expression by enclosing the register
number in parentheses. For example,
DM
(1)
displays the contents of Rl.
The DR directive displays registers and the CR directive can modify the registers.
8.2.9 Indirection
Indirection must precede a field. For example,
DM *0
causes the value at location 0 to be obtained and displayed as an address.
MPX-32 Reference Volume III
8-5
Accessing the Debugger
8.3 Accessing the Debugger
If the system debugger is configured as part of a resident system, the debugger is
automatically accessed by SYSINIT when the configured system is installed from the
User SOT. (The installation process is described in Chapter 2 of this volume.) The
debugger is activated by SYSINIT. The debugger input prompt is a double angle
bracket (»).
Debugger directives can be issued from the system console and patches can be made
in the memory resident image of the system. The debugger is terminated by a TE
(Terminate) directive. It returns control to SYSINIT, which continues building the
system as described in Chapter 2.
There are three other ways the debugger can be accessed:
• A privileged user task can code a branch and link through the communications
region variable that points to the debugger (C.DEBUG):
BL *C.DEBUG
Branch and link can only be used in modules or tasks that do not reside in the
extended execution area of MPX-32.
• For modules that reside in the extended execution area or vary between extended
and nonextended placement, the MBR_DBG macro can be used to access the
debugger. The MBR_DBG macro determines the operating mode of the calling
module and inserts the appropriate code for debugger access.
• An OPCOM DEBUG directive can be used.
The system debugger uses stand alone drivers to perform I/O. The debugger routes
listings to the printer configured as LP7E and it gets directives from the terminal or
teletype configured as TY7E (usually the system console). Although any terminal
user can issue the OPCOM DEBUG directive, once the system debugger gains
control, its prompt is displayed on the system console and it accepts directives only
from that device.
o
8-6
System Debugger
~
Debugger Directives
8.4 Debugger Directives
When the debugger is entered, it initializes bases and sets symbolic mode. It is then
ready to receive and process directives.
The directive syntax requires the first two characters be entered unless special
operators are used. Certain directives contain one or more fields of additional
information, separated by a comma.
Debugger directives are summarized below and described in detail in the following
pages. The summary is divided into three sections: general debugging directives,
directive list directives, and patch list directives.
Directive
Description
AB
AD
displays all subsequent addresses as numeric (absolute mode)
displays low and high limits of a task address space
AR
evaluates an arithmetic expression and displays its value
AS
BA
converts an instruction into its hexadecimal equivalent
BR
(
creates, deletes, or modifies the definition of a user base
and displays its addresses
sets a breakpoint at a specified address
exits the debugger (only when entered by a branch and link)
BYorTE
CB
changes the contents of a base register
CH
displays controller definition table (CDT) entries
CM
CO
changes the contents of memory to a new value
continues tracing or execution from a breakpoint set with
a BR command
CR
changes the value of a user register
CT
continues processing, setting a one-shot breakpoint at a specified
address which terminates the trace function
DB
DE
displays the base registers
deletes a breakpoint which was set with the BR command
DI
displays memory locations in instruction format within
a specified address
DM
DQ
displays memory locations within a specified address range
DR
displays all registers
DS
displays memory locations in instruction format within
a specified address range
displays dispatch queue entries
(/
MPX-32 Reference Volume
m
8-7
Debugger Directives
Directive
Description
DT
dumps the event trace table to the printer. This directive assumes
memory partition at hex 78000 and requires reassembly of the entire
resident source with the event table enabled.
DU
dumps output to the line printer
EC
echoes terminal output to the line printer
ET
places an event trace point at a specified address
GO
resumes execution of a user program at a specified address
or the last known user PSW. Optionally sets a one-shot trap
at a specified address.
displays the state queue head cells
HC
8-8
LB
LP
LT
sets line printer output mode
displays a list of the current mobile event trace points
MR
allows inspection of one CPU map register pair on a 32/87
MS
PS
modifies scratchpad locations
lists all breakpoints
displays last known user PSD, program counter, condition codes,
and registers
PV
converts a physical address to a virtual address
RB
RE
resets all bases to the default values
remaps the debugger to the map associated with a specified
dispatch queue entry number or the current program
RT
removes a mobile event trace point at a specified address
SE
compares specified words, in the range set by the SM directive,
to a specified value
SM
sets the mask as a left-justified hexadecimal number for
the SE directive
SP
SY
dumps CPU scratchpad RAM locations
displays subsequent addresses as displacements from bases.
This is symbolic mode.
TB
displays instructions that cause TSA stack push
TE
same as BY directive
TR
traces user programs and displays each instruction after execution
TS
terminates trace initiated by the TR directive
TY
sends output to a terminal and resets echo mode
UD
displays unit definition table (UDT) directive entries
VP
converts a virtual address to a physical address
System Debugger
Debugger Directives
(
The following directives construct a list of system debug directives and execute them
at specified breakpoint(s). The directive list is also executed at the users request. The
BR directive executes a directive list on a breakpoint.
Directive
Description
CD
displays the contents of the directive list
zeros the command list
turns off the directive list building mode
enters the directive list building mode
executes the directive list
CE
CL
CS
CX
The following group of directives can be used during the debug phase of IPL. These
directives build a patch list of debug directives to apply to the system image being
IPLed. The patch list is automatically written to disk as part of the system image at
the return to SYSINIT from the system debugger. Execution of the patches is
automatic at the beginning of the debug phase of IPL.
(
Directive
Description
PD
PE
PR
displays the contents of the patch list
PT
PX
8.4.1
zeros the patch list
turns off the patch list building mode
enters the patch list building mode
executes the patch list
AS (Absolute) Directive
The AB directive displays all subsequent addresses as numeric (absolute mode).
Syntax
AB
8.4.2 AD (Address) Directive
The AD directive displays the low and high limits of a task's address space.
Syntax
AD
MPX·32 Reference Volume III
8-9
Debugger Directives
(
,
i.
The AR directive evaluates an arithmetic expression. The debugger processes the
expression in its left to right order and displays the value.
Syntax
AR expr
is the arithmetic expression to be evaluated
8.4.4 AS (Assemble Instruction) Directive
The AS directive converts an assembly language instruction to its 8-digit hexadecimal
equivalent. Instruction groups supported are memory-reference and register-register.
I/O instruction group is not supported. Also, the Assembler mnemonics used in the
syntax for this directive are abbreviated to only 4 characters rather than 5 characters.
Use the DI directive to display the valid 4-character mnemonics available for use with
the AS directive.
Syntax
AS [8] opcode [,reg] [,offset] [,index] [ (Breg) ]
8
activates base mode operation
opcode
is the 4-character Assembler mnemonic
[,reg]
is a number from 0 to 7
[,offset]
is a hexadecimal number or an expression
[,index]
is the number 1, 2 or 3
[ (Breg)]
is the base register (BO-B7) that is used for base mode instructions. If this
parameter is specified, base mode must be activated (B parameter).
8.4.5 BA (Base) Directive
The BA directive defines a user base by adding its name to the internal base definition
table, deletes a user base name from the base table, or redefines a user base by
changing the value specified in the base name's definition. The new base possesses
the physical or virtual attribute associated with the addr field unless overridden with
the P or V options.
A maximum of 20 bases are definable.
8-10
.\
,.J
8.4.3 AR (Arithmetic) Directive
expr
'
. ....
System Debugger
Debugger Directives
(
Syntax
BA base [addr] [,P I ,V]
base
is a l-character alphanumeric base name.
[addr]
is the logical or physical address for the base dependent upon the virtual
or physical context of addr. If not supplied, the specified base name is
deleted. If addr is supplied and base is already defined. base is redefined
to represent addr.
[,P]
overrides the context for addr and specifies the physical attribute for base
[,V]
overrides the context for addr and specifies the virtual attribute for base
8.4.6 BR (Breakpoint) Directive
The BR directive sets a breakpoint at a specified address. A breakpoint remains in
effect until cleared with the DE directive. Upon execution of the breakpoint.
BRK@addr is displayed along with the contents of the registers to indicate which
breakpoint was executed. A maximum of 8 breakpoints can be set. Breakpoints and
event trace points (see ET command) cannot be set at the same address location.
Syntax
BR addr [,C] [,B]
addr
is the address at which the breakpoint is set
[,C]
specifies execution of a debug directive list at this address
[,B]
specifies that the breakpoint resides in extended MPX-32
8.4.7 BY (Bye) Directive
The BY directive exits the debugger when entry was made using a branch and link
instruction. The debugger returns control to the calling program. See also the TE
directive.
Syntax
BY
MPX-32 Reference Volume III
8-11
Debugger Directives
o
8.4.8 CB (Change Base Register) Directive
The CB directive modifies the contents of one or more user base registers.
Syntax
CB reg, value [,value] ...
reg
is a user register, BO-B7
value
is the 32-bit value to be stored in the specified register. Successive values
are stored in consecutive user registers. Two successive commas with no
intervening value skips the user register corresponding to the missing
value, leaving its contents unchanged. If B7 has been altered or skipped
and an unused value remains, it is ignored.
8.4.9 CD (Display Command List) Directive
The CD directive displays the contents of the system debugger directive list.
Syntax
CD
8.4.10 CE (Zero Command List) Directive
The CE directive zeros the system debugger directive list. Once zeroed, the list can
be replaced or left zeroed to remove the directive list function.
Syntax
CE
8.4.11
CH (Display Controller Definition Table Entry) Directive
The CH directive displays one or all CDT entries.
Syntax
CH [index]
[index]
is the index of the CDT entry to be displayed. If not specified, all CDT
entries are displayed.
o
8-12
System Debugger
Debugger Directives
(---
8.4.12 CL (Terminate Build Directive List Mode) Directive
The CL directive terminates the system debugger directive list building mode.
Syntax
CL
8.4.13 CM (Change Memory) Directive
The CM directive changes the contents of one or more words to a new 32-bit value.
The specified address is changed to either a right-justified hexadecimal value or a
left-justified blank-filled ASCII text word.
Syntax
CM addr,value [,value] ...
addr
is the address of the first or only word to be changed
value
is the 32-bit value to be stored at the specified address. Successive values
are stored in consecutive words beginning at addr. Two consecutive
commas with no intervening value can be used to skip the memory
address corresponding to the missing value, leaving its contents
unchanged.
(
8.4.14 CO (Continue) Directive
The CO directive continues tracing or execution from a breakpoint. If the user is in
trace mode (entered by a TR directive), tracing continues and the debugger does not
exit while TR is active. If the user is not in trace mode, execution continues. (See
GO directive).
Syntax
CO [addr [,stop] ]
addr
is the address where program execution with optional trace continues. If
not specified, the program resumes from the last known location.
stop
is the address where execution and tracing terminates
MPX-32 Reference Volume III
8-13
Debugger Directives
8.4.15 CR (Change Register) Directive
The CR directive modifies the contents of one or more user registers.
Syntax
CR reg,value [,value] ...
reg
is a user register, RO-R7
value
is the 32-bit value to be stored in the specified register. Successive values
are stored in consecutive user registers. Two consecutive commas with
no intervening value skips the user register corresponding to the missing
value, leaving its contents unchanged. If user R7 has been altered or
skipped and an unused value remains, it is ignored.
8.4.16 CS (Build Directive List) Directive
The CS directive puts the system debugger in the directive list build mode. The
following directives are not valid once CS is specified: CD, CE, CL, CX, or another
CS directive.
Syntax
CS
8.4.17 CT (Continue then Terminate) Directive
The CT directive continues processing from a specified dollar sign ($) location, setting
a one-shot breakpoint at a specified address which terminates the trace function.
Syntax
CT [addr]
[addr]
is the address where an optional one-shot breakpoint is set. Tracing is
terminated and the users program re-entered. If not specified, return to
the user's program is at the last known program counter value.
8.4.18 CX (Execute Directive List) Directive
The CX directive executes the system debugger directive list.
Syntax
CX
8-14
System Debugger
Debugger Directives
8.4.19 DB (Display Base Register) Directive
The DB directive displays one or more user base registers.
Syntax
DB [Breg]
[Breg]
is a user base register, 0-7. If no register is specified, the default is all
user base registers are displayed.
8.4.20 DE (Delete) Directive
The DE directive deletes a breakpoint that was set with a BR directive and restores
user instructions to their original locations.
Syntax
DE addr
addr
(
8.4.21
is the address where the breakpoint is deleted and the user's instruction is
restored to its original location
DI (Display Instruction) Directive
The DI directive displays any memory locations within a specified address range, in
instruction format, one line at a time (same as OS directive).
Syntax
01 add] [,add2] [,B]
add]
is the address where the display starts
[,add2]
is the address where the display ends. If not specified, the display
continues until a character other than a carriage return is entered at the
end of a line.
[,B]
specifies base mode instruction display
8.4.22 DM (Display Memory) Directive
The OM directive displays all memory locations within the specified address range. A
carriage return continues the display; any other character entered terminates the
display.
MPX·32 Reference Volume III
8-15
Debugger Directives
Syntax
OM [add] [,add2] [,number] ]
add]
is the address where the display starts
[,add2]
is the address where the display ends. If not specified, the ending address
defaults to the starting address. For example, add] is the only location
displayed.
[,number]
is the nwnber of words to be displayed per line on the console (minimwn
of 1, maximwn of 8). If not specified, the default is 4.
8.4.23 DQ (Display Dispatch Queue Entry) Directive
The DQ directive displays one or all DQE entries.
Syntax
OQ [index]
[index]
is the index of the DQE entry to be displayed. If not specified, all DQE
entries are displayed.
8.4.24 DR (Display Register) Directive
The DR directive displays the memory locations of registers.
Syntax
DR [reg]
[reg]
is a user register (RO-R7). If not specified, all registers are displayed.
8.4.25 OS (Display Symbolic) Directive
The DS directive displays any memory locations within a specified address range, in
instruction format, one line at a time (same as DI directive).
Syntax
OS addl[,add2] [,B]
8-16
add]
is the address where the display starts
[,add2]
is the address where the display ends. If not specified, the display
continues until a character other than a carriage return is entered at the
end of a line.
[,B]
specifies base mode instruction display
System Debugger
Debugger Directives
(
8.4.26 DT (Display Event Trace) Directive
The DT directive dumps the event trace table to the line printer. Event trace is
disabled until printing is completed.
Notes:
This directive assumes memory partition at hexadecimal 78000 and requires
reassembly of the entire resident source with event trace enabled.
Syntax
DT
8.4.27 DU (Dump) Directive
The DU directive writes a range of memory to a line printer. ASCII format is used
for the right-hand side of the memory display.
Syntax
DU [start [,stop] ]
('
start
is the memory address where the dump starts
stop
is the memory address where the dump stops. If not specified, the default
is the end of the operating system.
If no parameters are specified, the entire operating system area is output.
8.4.28 EC (Echo) Directive
The EC directive generates hard copy output when a CRT is the terminal device.
Output is listed, line by line, on the line printer for every carriage return on the
terminal. To terminate the EC directive, specify the TY directive.
Syntax
EC
8.4.29 ET (Enter Event Trace Point) Directive
The ET directive places an event trace point within either resident or nonresident code
without requiring reassembly of a program. To turn on the trace, this directive resets
bits 21 and 22 of C.TRACE.
MPX-32 Reference Volume III
8-17
Debugger Directives
Prerequisites are:
1.
2.
The system must have been SYSGENed with a static partition for the event trace
table.
Both H.DBUG (System Debugger) and H.IP06 (SVC Trap Handler) must have
been assembled with TRACE set true.
A maximum of 8 event trace points can be set. Event trace points and breakpoints
(see BR directive) cannot be set at the same address location.
Syntax
ET addr [,8]
addr
is an absolute or relative address with a symbolic base
[,8]
specifies that the event trace point resides in extended MPX-32
8.4.30 GO (Go) Directive
The GO directive transfers control to the user task, optionally setting a one-shot trap
at a specified address.
Syntax
GO [start [,stop] ] [,8]
[start]
start is the address where the program starts executing
[,stop]
stop is the address where the program stops executing. When specified, a
breakpoint is set at this address before execution begins at the start
address. If not specified, the program is reactivated at the start address.
[,8]
specifies base mode execution
If no parameters are specified, the program is entered at the last known user PSW.
8.4.31
HC (Display Dispatch Queue Head Cell) Directive
The HC directive produces a 3-column display of the MPX-32 state queue head cells.
Each entry is 3 words long.
Syntax
He
8-18
System Debugger
Debugger Directives
8.4.32 LB (List Breakpoint) Directive
The LB directive lists all active fixed breakpoints set using a BR directive.
Syntax
LB
8.4.33 LP (Line Printer) Directive
The LP directive directs output to the line printer. If the user is tracing, no request is
made for input after each instruction. A breakpoint must be set to terminate the trace.
Syntax
LP
8.4.34 LT (List Mobile Event Trace Point) Directive
The LT directive lists current mobile event trace points within resident or non-resident
code.
(-
Prerequisites are:
1.
2.
The system must have been SYSGENed with a static partition for the event trace
table.
Both H.DBUG (system debugger), and H.IP06 (SVC trap handler), must have
been assembled with TRACE set true.
Syntax
LT
8.4.35 MR (Map Register) Directive
The MR directive allows inspection of one CPU map register pair. This directive is
available only on the 32/87 computer.
Syntax
MR index
index
is the number of the map register from 0 to FF
MPX-32 Reference Volume III
8-19
Debugger Directives
8.4.36 MS (Modify CPU Scratch pad location) Directive
The MS directive modifies any location within the CPU scratchpad random access
memory. Because the scratchpad is used by the CPU to process I/O and interrupt
requests, incorrect modification of scratchpad locations could cause undesirable
results. This directive should be used with extreme caution.
The scratchpad address specified in this directive can be within two ranges. The first
range is a number between 0 and FF corresponding to the actual scratchpad address as
defined in hardware. The second range is a number between 300 and 6FC
corresponding to a scratchpad location obtained by using the SP directive to display
all scratchpad locations.
If an invalid address is specified or an attempt is made to write past the end of
scratchpad, an error message is displayed.
Syntax
MS loe,vaiue [,value] ...
loe
is the scratchpad address 0 to FF, or 300 to 6FC
value
is the 32-bit value stored in the specified location. Successive values are
stored in successive locations.
8.4.37 PO (Display Patch list) Directive
The PO directive displays the contents of the system debugger patch list. The display
list is either the previous patch list written to disk or the current edited version.
Syntax
PO
8.4.38 PE (Zero Patch list) Directive
The PE directive zeros the system debugger patch list. Once zeroed, the list can be
replaced or left zeroed to remove the patch function.
Syntax
PE
8-20
System Debugger
Debugger Directives
8.4.39 PR (Terminate Build Patch List Mode) Directive
The PR directive terminates the system debugger patch list building mode.
Syntax
PR
8.4.40 PS (Program Status) Directive
The PS directive displays the user program status doubleword (PSD), program
counter, condition codes, and registers.
Syntax
PS
8.4.41
PT (Build Patch List) Directive
The PT directive causes the system debugger to enter the patch list build mode. The
following directives are not valid after PT has been specified: PO, PE, PR, PX, or
another PT directive.
Syntax
PT
8.4.42 PV (Convert Physical Address to Virtual Address) Directive
The PV directive converts a physical address to a virtual address.
Syntax
PVaddr
addr
is the physical address to be converted to a virtual address
8.4.43 PX (Execute Patch List) Directive
The PX directive executes the system debugger patch list.
Syntax
PX
MPX-32 Reference Volume III
8-21
Debugger Directives
{-~"
:~j
8.4.44 RB (Reset Bases) Directive
The RB directive resets all bases to their initial default values.
Syntax
RS
8.4.45 RE (Remap) Directive
The RE directive remaps the debugger to the map associated with a program.
Syntax
RE [number]
[number]
is the dispatch queue number in the range 0 to FF where remapping is
associated. If not specified, remapping defaults to the dispatch queue
number in C.CURR.
8.4.46 RT (Remove Event Trace Point) Directive
The RT directive removes a mobile event trace point within resident or nonresident
code.
Prerequisites are:
1.
2.
The system must have been SYSGENed with a static partition for the event
trace table.
Both H.DBUG (system debugger), and H.lP06 (SVC trap handler), must
have been assembled with TRACE set true.
Syntax
RT addr
addr
8-22
is an absolute or relative address with a symbolic base
System Debugger
Debugger Directives
(
8.4.47 SE (Search Equivalent) Directive
The SE directive compares specified words to a specified value. Each word is ANDed
with the search mask (see SM directive) before being compared to the value. Each bit
in the range is listed.
Syntax
SE value, start, stop
value
is the value where each word is compared
start
is the address where the search begins
stop
is the address where the search ends
8.4.48 SM (Set Mask) Directive
The SM directive sets the mask for the SE directive. The mask parameter is.
interpreted as a left-justified hexadecimal number or right-justified ASCII character
string.
Syntax
SM [mask]
mask
is a new mask value. If not specified, the default is the previously entered
value; if none, X'FFFFFFFF' is used.
8.4.49 SP (Scratchpad Dump) Directive
The SP directive outputs to the terminal the contents of the scratchpad locations (23
lines of text are output at a time). A carriage return continues output, entering any
other character terminates output.
Syntax
SP [Ioe]
[loc]
is the CPU scratchpad address 0 to FF. If not specified, all scratchpad
locations are displayed.
8.4.50 SV (Symbolic) Directive
The SY directive displays all subsequent addresses as displacements from bases
(symbolic mode).
Syntax
SV
MPX-32 Reference Volume '"
8-23
Debugger Directives
8.4.51
TB (Trace Back) Directive
The TB directive displays the instructions that caused each TSA stack push. TB is
only valid if there is a current task which is not ar..the base level of its stack. Make
sure the debugger is mapped with the correct task space. The instructions are
displayed in logical order. For example, the first instruction shown is the instruction
executed by the task (usually a SVC) that caused the first push. Because some
operating system routines allocate extra stack frames as work space, some displays can
contain apparently invalid information.
Syntax
TB
8.4.52 TE (Terminate) Directive
The TE directive exits the debugger if it was entered using a branch and link. Control
returns to the calling program. See the BY directive.
The TE directive should not exit from a breakpoint. See the CO and CT directives.
Syntax
TE
8.4.53 TR (Trace) Directive
The TR directive executes and displays results of user instructions one at a time.
Addresses are displayed as a base character plus offset value.
The last instruction executed is displayed and the cursor is held at the end of the line
awaiting a user directive. A carriage return or line feed causes the next instruction to
be executed and displayed. An up arrow (1\) causes the previous instruction to be
redisplayed. An equal sign (=) causes the hexadecimal equivalent of the instruction
just executed to be displayed. Any other character causes the debugger to prompt for
a directive.
Symbols established by the BA directive are used for display purposes if the SY
directive was set.
Execution tracing is not permitted within a mapped out task's virtual address space.
o
8-24
System Debugger
Debugger Directives
Syntax
TR [start [,stop] ] [,B]
[start [,stop] ]
[, B]
start
is the address of the first user instruction to be traced. If not
specified, the default is $ (cWTent PSD value) ..
stop
is the address of the last user instruction to be traced. If not
specified, tracing continues without bounds.
specifies base mode display and execution for tracing through extended
MPX-32.
8.4.54 TS (Trace Stop) Directive
The TS directive exits the trace mode initiated by the TR directive. All further I/O is
directed to the user's tenninal.
Syntax
TS
8.4.55 TV (Terminal) Directive
The TY directive directs output to a tenninal and to reset EC (Echo) mode.
Syntax
TV
8.4.56 UD (Display Unit Definition Table Entry) Directive
The UD directive displays one or all UDT entries.
Syntax
UD [index]
[index]
is the index of the UDT entry to be displayed. If not specified, all UDT
entries are displayed.
MPX-32 Reference Volume III
8·25
Debugger Directives
.(
.. \
lit...
;
,~
8.4.57 VP (Convert Virtual Address to Physical Address) Directive
The VP directive converts a virtual address to a physical address.
Syntax
VP addr
addr
is the virtual address to be converted to a physical address
8.5 System Debugger Practice Debug Session
The following example is for first time users of the system debugger. It is
recommended that the user try the following directives on the system console of an
MPX-32 system. This should only be done on a stand-alone system (with no other
users on the system), because it is very easy for the inexperienced user to crash the
system.
This example does not attempt to explain every directive or even the complete syntax
of the directives. It is intended to help use the system debugger. While using this
example, please refer to the directives descriptions and read each description before
proceeding.
8.5.1
Step One - Accessing the Debugger
The debugger is generally entered using the instruction:
BL *C.DEBUG
This is the case whether it is entered by a user written program or through the
OPCOM DEBUG directive. The calling program must be privileged to make this
call. Also, the macro 'M.EQUS' or 'M.COMM.' must be included in the program to
allow the symbol 'C.DEBUG' to be properly assembled.
To exit the debugger, when entered by a branch and link, use the TE directive.
At the operator's console, invoke the debugger using OPCOM.
TSM>OPCOM
??DEBUG
TSM>OPCOM DEBUG
or
»
TSM>!DEBUG
or
»
»
Then exit.
»TE
??
»TE
TSM>
»TE
TSM>
Notice you return to the process you left.
,(·'')\i
\
8-26
System Debugger
i
c/
System Debugger Practice Debug Session
8.5.2 Step Two - Task Debugging with the System Debugger
While it is normally best to debug a task using the task debugger, there are cases
where the system debugger is the better tool, because the system debugger allows the
user to trace through system calls.
8.5.3 Using the System Debugger to Display Memory
At the console, perform the following:
TSM>! DEBUG
Enter the debugger (OPCOM is the task)
»
Because Assembler generated listings have the program relative addresses listed, it is
necessary to set a base at the start of the task to be debugged. This allows the use of
the offsets given by the Assembler. To do this, it is necessary to know where the task
starts. This information is contained within the Task Service Area (TSA) represented
by the predefined debug base N.
To set a user base, first select the character desired as the base. In this example, use
P. Using the macro expansion of the TSA variables, the start of the task is at T.BIAS
which equates to hexadecimal '704'. To set the base, use the following debug
directive.
»BA P *704N
This sets base P to equal the virtual address stored at hexadecimal '7 04' relative to
the TSA. The * indicates the address specified is indirect. When referencing
locations that consist of an offset and a base, as in the 70 4N above, the + operator is
implied.
Now, use the base to look at information contained within the task.
To find where the debug call is made, use the DI (Display Instruction) directive to list
the instructions with their program relative offsets. The current task program counter
is pointing one word past the call to the debugger, so the following instruction
displays the debug call:
»DI $-4
P+5C40 BL O,Xl
P+5C44 LF RO,P+20
The $ indicates the current program counter location. In this case, the debugger is
entered by an indexed branch to allow OPCOM to test for the presence of the
debugger before attempting to branch to it.
To look at more instructions, repeated carriage returns display successive physical
memory locations in instruction format.
To display noninstruction memory contents, use the DM (Display Memory) directive.
This directive is the default directive. If only a number is entered, the data contained
at the specified address is displayed on the terminal.
MPX-32 Reference Volume III
8-27
System Debugger Practice Debug Session
o
For example:
»DM 50P
P+50 46554C20 *FUL *
»50P
P+50 46554C20 *FUL *
The DM directive is not always defaultable. If the memory location to be displayed is
ambiguous with a debug directive, then DM must be entered.
»EC04
Would be interpreted by the debugger as the ECHO directive. DM
must be entered.
»DM EC04
Other potentially ambiguous directives are:
•
•
•
•
•
AB AD BA DE EC -
set absolute addressing mode
display task address limits
define base
delete breakpoint
echo terminal output to line printer
To display the registers at any point, two directives are used. The first is the DR
(Display Register) directive. DR lists any or all of the eight general purpose registers.
/'
I
A1037C44 00021F8C 00000000 0000002F
OOOOOOOD 00000004 44544255 20202020
»DR R5
00000004
*
D ••••••••.••
/*
* ........ DEBU *
*
*
.The second directive is the PS (Program Status) directive. PS lists the program status
doubleword, program counter, condition codes, and general purpose registers.
»PS
PSD=
PC=
A0037C44 80000058
G+103C
CC= 0100
RO-7
A1037C44 00021F8C 00000000 0000002F
OOOOOOOD 00000004 44544255 20202020
D ........... /*
*
........
DEBU *
*
Often, calls to system services require data structure addresses be passed in registers.
An example is the FCB address in almost all I/O service calls. If examination of such
a structure is required, two methods can be employed.
The first is to display the registers, or a particular register using the DR directive.
Then the memory locations pointed to by the register containing the data can be
examined by the DM (Display Memory) directive. If the last base referenced had a
physical attribute, the memory displayed is physical. If the last base had a virtual
attribute, the memory displayed is logical.
•
8·28
I
"'-/
»DR
System Debugger
o
System Debugger Practice Debug Session
The second involves using the DM directive with a special operator, the parentheses,
indicating 'contents of a register'. A number in the range of 0 to 7 is enclosed in
parentheses and indicates the contents of a register. To look at a 16 word FCB, use
the following directive.
»DM (1, (1+40
or
»(1, (1+40
By using the debug directives to their maximum potential, a great deal of information
about a task is made readily available to the user. Two examples of such directives
follow.
1. Displaying the Dispatch Queue Entry for the Current Task
In general, have an MPX-32 Technical Manual available so that system data
structures can be analyzed. For the debugger to display the actual relative
addresses displayed in the diagrams, and not the absolute addresses, set a debug
base. Q is an appropriate base to use for the dispatch queue. Set the base as
follows.
»BA Q *8E8
(
Because the * indicates indirect, base Q is set to the address stored at X' 8E 8'.
The number X'SES' was determined by looking at a C-dot cross reference for
C.CURR. This is the dispatch queue head cell for the current task. To examine
any part of the queue entry, refer to the proper offset followed by Q.
..
»Q,20Q
Q+O 000008E8 000008E8 3C3C3C02 17000015 * ........ «< ..... *
Q+10 53595354 454D2020 4F50434F 4D202020 *SYSTEM OPCOM *
The state queue linkage, the task number, the owner name, and the task name
for the current task are shown.
2.
Traversing a Linked Queue
If the integrity of a linked queue is in doubt, the debugger easily traces through
the entries as shown below:
»Q
Q+O 000008E8
*
8E8 0OO03D30
* .. =0*
Q+O 0OOO08E8
*
*
»*
»*
*
Because the * indicates indirect, it refers to the address displayed on the previous
line. In this manner, linked queues of any length can be traversed to ensure they
contain all required entries, are connected, or whatever else may be desired.
8.5.4 Using Debug to Display a Program
Assume a program is failing in one particular subroutine. By using the breakpoint
capabilities of debug, let the program run at machine speed until the trouble spot is
encountered. To set a breakpoint, use the following directive.
»BR addr
MPX-32 Reference Volume III
8·29
System Debugger Practice Debug Session
'~.'\
..
To let the program run until reaching the breakpoint, do the following:
»TE
"l./
If the debugger was entered by BL *C. DEBUG
(or)
»BY
If the debugger was entered by BL *C . DEBUG
(or)
»CO
If the debugger was entered from a breakpoint
(or)
> >C T
If the debugger was entered from a breakpoint
An explanation of the four different debug exit directives follows.
TE or BY either of these two directives can exit the debugger when it is entered by a
branch and link. These are the only directives that are acceptable. Use of
the CO or CT directives produce errors later on.
CO
continues the last mode of execution. If the user was tracing, then
terminated trace mode using a noncarriage return input and now wishes to
resume tracing, either CO or TR accomplishes it. If the program was
running normally and was stopped by a debug breakpoint, CO will
continue execution of the program in run mode. This directive should be
used only if the most recent entry into the debugger was through a
breakpoint.
CT
continues execution of the task in run mode regardless of the previous
mode (trace or run). Like the CO directive. CT should only be used when
the most recent entry into the debugger was through a breakpoint.
Upon reaching the breakpoint, the following is displayed:
»BR 5C48P
»TE
BRK P+5C48 CC 0100
RO-7
89032C08 FFFFFFFO 00000000 0000002F * .. , ............ /*
OOOOOOOD 00000004 44454255 20202020 * ........ DEBU *
Note:
Breakpoints cannot be set on SVC instructions. An error message is
displayed should the user attempt this. The trace mode should only be used
when the debugger is invoked by a breakpoint. If entry was accomplished by
a branch and link, a breakpoint should be set, TE executed, and the trace
started after entering the breakpoint. Breakpoints cannot be set within
mapped out tasks.
When the area of code to be debugged has been reached, a helpful directive is TR
(Trace). This directive executes instructions, one at a time, and displays the
disassembled instruction, along with any pertinent registers or memory locations, on
the console.
8-30
C·"
',.\
»TR
I:'
System Debugger
"
"~I
System Debugger Practice Debug Session
After tracing several instructions, a bug is found. The instruction at xxxxP is:
LD R4,100,X2
what should have been there is:
LD R4,100,X3
In order to continue the debugging process, the instruction must be modified and reexecuted. The CM (Change Memory) directive does this.
»CM addr, value
This directive requires the correct hexadecimal value for the new instruction. The
debugger assembles memory reference and register-register instructions. The result is
displayed in hexadecimal. To find the value needed above use:
»AS LD,4,100,3
AE600102
Then to patch the bad instruction:
»CM xxxxP, AE 60 01 02
and to re-execute it:
»TRxxxxP
(
If it is desired, registers can be modified by using the CR directive.
This method for patching a program works for single line errors. That is, a bad
memory address, an incorrect register, or any other error requiring modification of
only one line of code. For more major problems that require the insertion of more
instructions, the following technique can be employed.
Because several low memory areas (for example, X'DO' to X'FF') are not used after
the system is booted, we can use these locations as a scratch area for building patches.
MPX-32 has a section of memory reserved for patching by J.INIT that can build
temporary debug patches. It is found by examining C.MPAC (determine actual
address by assembling M.EQUS). This word contains the next available address
within the MPX-32 patch area. The patch area end address is contained in c.MP AH.
To use the available memory locations, first, select the instruction where code is to be
added. Using the area mentioned above, replace the instruction with a branch to
X'DO'. At location X'DO', build the desired instructions ending with a branch back to
the proper return location. This is generally one word past the branch to X'DO'. The
instructions are, for the most part, generated by the debug AS directive, placed by the
CM directive, and verified before being executed by the DI directive.
8.5.5 Summary
(
The best way to learn the debugger is to use it. Reread section 8.4, Debugger
Directives, in this chapter for complete descriptions of the directives because the
following summary does not cover all of the directives or make full use of the ones
covered. Type carefully because the debugger executes exactly as requested. If you
do not specify a base for an address, the debugger references the absolute location.
MPX-32 Reference Volume III
8-31
Example of Directive List Use
8.6 Example of Directive List Use
Problem:
Log contents of FCB after repeated I/O operations performed by new resident
operating system module without continuous user intervention.
Solution:
Place a breakpoint at 63C relative to new module. Start with the directive list
option and create a directive list to dump the FCB and continue.
Implementation:
Build Directive List
1.
Access the system debugger
TSM> ! DEBUG
2.
Clear the directive list
»CE
3.
Set directive list build mode
»CS
4.
Construct directive list to dump FCB
»DU (1, (1+40
»CO
5.
Terminate directive list build mode
»CL
6.
Display directive list
»CD
Resultant CRT display:
CL
CL
7.
-7
-7
DU (1, (1+40
CO
Set breakpoint
»BR 63CX,C
8.
Return to TSM
»TE
o
8-32
System Debugger
Example of Patch list Use
8.7 Example of Patch List Use
Problem:
System is generated containing user created operating system modules. The
new module contains the patchable coding error
LW Rl,OW,R3
(should be)
LA Rl,OW,R3
Solution:
System debugger patch list containing a Change Memory (CM) directive
Implementation:
Build Patch List
1.
IPL system. When the debug prompt appears, locate erroneous instruction
(for example, location 43C relative).
2.
Use the Assemble directive to construct new instruction
»AS LA,1,O,3
Result: 34EOOOOO
3.
Clear patch list
»PE
4.
Set patch list build mode
»PT
5.
Build patch list
»CM 43C(relative),34EOOOOO
»TE
6.
Replace instruction at 43C relative
Return to SYSINIT
Terminate patch list build mode
»PR
7.
Display patch list
»PD
Result:
PL
PL
8.
--t
--t
CM 43C(relalive),34EOOOOO
TE
Execute patch list
»PX
Result:
Location 43C (relative) changed to 34EOOOOO and control returns to
SYSINIT when the patch list is written to disk.
MPX-32 Reference Volume III
8-33/8-34
()
o
9
Online System Patch Facility (J.lNIT)
9.1 Introduction
J.INIT provides for temporary or permanent patching of the MPX-32 resident image.
In addition, J.INIT performs the Alterable Control Store/Writable Control Store
(ACS/WCS) loading function. See Chapter 12 of this volume.
J .INIT also initiates mount requests for any public volumes to be mounted at IPL
time. The information for these requests is provided in the system file, M.MOUNT.
See section 9.7, Automatic Mounting of Public Volumes, in this chapter.
J.INIT processes patch directives from the patch file.
The patch file name is supplied in the SYSGEN PCHFILE directive. This file should
contain valid patch directives as described in the Patch Directives section of this
chapter. The patch file is maintained by the Text Editor and should be stored as a
blocked, uncompressed file. An associated symbol table file is built by SYSGEN
when the SYMTAB directive is specified. The SYSGEN PATCH directive should
define the size of the patch area.
Only one patch area is used for extended, nonbase, and mapped out modules. If the
extended mode is activated at SYSGEN, the patch area must be located in the first
16KW of memory. Otherwise, the patch area can be located anywhere in the resident
MPX-32 system.
Patches for any modules that are located in extended memory must be constructed by
using the appropriate base register instructions. J.INIT is unable to perform opcode
decoding or substitution for extended modules. Memory reference instructions must
be encoded with the base register field equal to O. If these instructions are designated
relocatable, J.INIT inserts the appropriate base register and offsets into the address
field. J .INIT generates an error if an attempt is made to enter a relocatable base
register instruction with a nonbase zero field.
Entry of a patch that invokes a branch between extended and nonbase modules is not
supported. Because the adapter code addresses are not available to J.INIT, and
because J.INIT cannot build adapter sequences, the user must locate the required
adapter and enter the branch in absolute mode.
Patch processing terminates when the Exit (JE) directive is encountered in the patch
input file. At this time, an audit trail of all patches specified is written to the SLO
file. The audit trail listing is suppressed by specifying the NPR option with the option
(/0) directive. The patch program accepts directives to control processing. The
general format of a directive is:
/d12 f3 f4 In
/d
is the directive name that must be followed by one or more spaces. This is
called field 1 for error messages.
12 - In
are fields containing the names, values, and special symbols processed by
the directive. Fields must be separated by one or more spaces or a comma.
MPX-32 Reference Volume III
9-1
Introduction
For a patch directive to reference an extended module's DSECT data, SYSGEN
generates system symbol table entries containing the DSECT base addresses. The
name for these entries in the system symbol table is the module name with the first
character replaced by "$.". For example, $.REMM indicates the address of
H.REMM's DSECT data. These names are used on relocatable patches that are
DSECT relative.
One character module names (A,B,C,etc.) or module names with only the first
character unique (AMOD, BMOD, CMOD, etc.) cause the generation of multiply
defined DSECT symbol table entries ($,$MOD). This generates an error in J.INIT.
9.1.1
Dedicated Names
Dedicated names used by J.INIT are:
Dedicated
Name
$
R
-R
Description
equivalent to the address of the next free patch area location
indicates a relative address in the positive direction
indicates a relative address in the negative direction
delimits fields to be processed and comments
9.1.2 Conventions
All field entries on patch directives must conform to the following conventions:
name
value
address
label
9-2
1 to 8 ASCII characters, one of which must be nonnumeric
1 to 8 hexadecimal digits; leading zeros need not be specified. Only
whole words are generated.
1 to 5 hexadecimal digits; leading zeros need not be specified. Must be
word resolution (bits 30-31 equal 0).
1 to 8 ASCII characters, one of which must be nonnumeric
Online System Patch Facility (J.lNIT)
Patch Directives
9.2 Patch Directives
Patch directives are summarized below and described in detail on the following pages.
Directive
/B
IC
/D
IE
IG
10
/P
/R
IF.fN.rr
!$
I;
9.2.1
Description
define a base address
change the contents of a memory location
define a named value
exit
go to the patch area from a specified memory location
select patching options
define a patch area
return from the patch area
process patch directives conditionally
enter a value into the patch area
comment only
18 (Define a 8ase Address) Directive
The /B directive allows a name to be equated to a base address. This definition is
inserted in the internal symbol table and can be referenced by subsequent directives.
Syntax
18 name address
name is equated to address
18 name1 name2
name1 is equated to the address value of name2
9.2.2 IC (Change the Contents of a Memory Location) Directive
The IC directive changes the value of any location in memory.
Syntax
Ie address value
the specified value is inserted at the specified address
Ie address value R
the address field of the value parameter is added to the address parameter to form the
address field of value. The specified value is inserted at the calculated address.
Ie address value -R
The address field of the value parameter is subtracted from the address parameter to
form the address field of value. The specified value is inserted at the calculated
address.
MPX-32 Reference Volume III
9-3
Patch Directives
Ie name address value
The value of the name parameter is added to the address parameter to form the actual
address. The specified value is inserted at the actual address.
Ie name address value R
the specified value is inserted at the specified address, relative to name. The value of
name is added to value to form the actual address.
Ie name address value-R
the specified value is inserted at the specified address, relative to name. The address
field of value is subtracted from name to form the address portion of value.
Ie name1 address value name2
the value of name2 is added to the value parameter and inserted at the actual address.
The value of name1 is added to the address parameter to form the actual address.
9.2.3 10 (Define a Named Value) Directive
The /D directive equates a name to the address of a value. The value is stored in the
next free location of the patch area. The definition is inserted in the internal symbol
table and can be referenced by subsequent directives.
Syntax
10 name value
name is equated to the address of value in the patch area
10 name1 name2
!lame1 is equated to the address of the value of name2 in the patch area
9.2.4 IE (Exit) Directive
The IE directive terminates directive processing.
Syntax
IE
9·4
Online System Patch Facility (J.lNIT)
Patch Directives
(
9.2.5 /G (Go to the Patch Area from a Specified Memory Location)
Directive
The /G directive inserts an unconditional branch to the patch area at any memory
location. The location branched to will be the next free location of the patch area
plus, optionally, an offset.
Syntax
/G address
an unconditional branch to the specified address of the patch area is inserted
/G name address
an unconditional branch to the specified address of the patch area relative to name is
inserted. The value of name is added to address to determine the actual address of the
branch in the patch area.
/G name address value
an unconditional branch to the patch area at address, relative to name is inserted. The
branch is to the next free patch location plus value number of bytes (word resolution).
The offset area is thus reserved. The basic form, with no name field, can also be used.
(
9.2.6 /0 (Select Patch Options) Directive
The /0 directive specifies options for controlling the processing of subsequent
directives.
Syntax
/0 name1 name2 namen
name l' name2 and namen are the option names. A single 10 directive can contain
more than one name parameter. There can be any number of /0 directives.
The available options are:
Name
NAM
Use
informs UNIT that the definitions in the patch file
should be merged into the internal symbol table. This
option should be specified once per single run;
NHE
informs J.INIT not to halt if patch errors are detected.
If not specified, any patch error causes a halt. Entering
//RUN continues processing.
NPR
informs J .INIT that a patch listing is not to be produced.
SYM
directs J.INIT to produce a listing of the internal symbol
table. This specification should not be made in the first
directive of a patch deck.
MPX-32 Reference Volume III
9·5
Patch Directives
",j
,{'--"-
9.2.7 IP (Define a Patch Area) Directive
The /p directive defines a temporary patch area or appends patches to the patch area
defined by SYSGEN. It should be used during debugging.
Syntax
/P address value
a patch area is defined starting at location address, value (word resolution) bytes long.
If the extended mode is active in SYSGEN, the address must be in the first 16KW of
memory. Since no attempt is made to protect this area, it should be some area of the
resident image not used during debug operations.
/P modname
modname signals J.INIT to determine the operating mode of a module and to generate
a temporary patch area address according to the mode. This allows a patch area to be
situated in the extended partition.
/PCUR
subsequent patches are added to those entered during a previous patch run
9.2.8 IR (Return from the Patch Area) Directive
The /R directive allows an unconditional branch back to the instruction plus one word
produced by the last IG directive encountered. An offset can be specified to reserve a
number of patch locations immediately following the branch back.
Syntax
fR
an unconditional branch is inserted to the location plus one word containing the last
branch generated by a IG directive
fR value
an unconditional branch is inserted to the location plus one word containing the last
branch generated by a /G directive value number of bytes of the patch area (word
resolution) are reserved. This reserved area follows the generated branch.
9.2.9 IF, IT, IN (Conditional) Directives
The IF and rr directives allow skipping the processing of other directives based on
whether the directive statement is true ((f) or false (IF). Processing continues when a
IN statement with the matching label is encountered. This creates a general patch file
that attempts to modify only those modules included in the resident image.
()
9-6
Online System Patch Facility (J.INIT)
Patch Directives
(~
Syntax
IF name label
if name is false or not defined in the symbol table, discontinue directive processing
until a IN directive containing label is encountered
IT name label
if name is true or defined in the symbol table, discontinue directive processing until a
IN directive containing label is encountered
IT EXTDMPX modname label
IF EXTDMPX modname label
if the operation mode of modname is extended (ff) or nonextended (IF), directive
processing is discontinued until a IN directive containing label is encountered
IT MAPOUT label
IF MAPOUT label
if the current image is mapped out (ff) or mapped in (fF), directive processing is
discontinued until a IN directive containing label is encountered
IN label
(
continues directive processing
9.2.10 /$ (Enter a Value into the Patch Area) Directive
The /$ directive inserts a value into the next free location of the patch area.
Syntax
1$ value
value is inserted into the next free patch location
1$ value R
value is inserted, relative at the actual location. The value of $ is added to the address
field of the value parameter for the actual location.
1$ value -R
the address field of value is subtracted from $ to form the actual address field of value.
Value is then stored at the next free patch location.
1$ name value
value is inserted, relative to name. The value of name is added to the value and
placed into the next free patch location.
MPX·32 Reference Volume 11\
9-7
Patch Directives
o
9.2.11 /; (Comments) Directive
The /; directive can be included on any patch directive as a delimiter. The total
directive can be designated as a comment by the use of this directive.
Syntax
I; text
9.3 Entry Conditions
Calling Sequence:
J.INIT is activated by SYSINIT at start-up. If the system is running, J.INIT can also
be activated from TSM or OPCOM. To activate J .INIT from TSM, enter:
TSM>J .INIT
To activate from OPCOM, enter:
??ACTIVATE J.INIT
Patch processing is inhibited by setting control switch 2.
9.4 Exit Conditions
Return Sequence:
M.EXIT
Exit to MPX-32
Registers:
None
o
9·8
Online System Patch Facility (J.JNIT)
External References
9.5 External References
Abort Cases:
Halt if error detected and the NHE option has not been specified.
Output Messages:
J.INIT produces an audit trail of all patches made unless the NPR option is
specified. The information produced includes a source image of each patch, the
actual location patched, the actual value stored, and the previous contents of the
location. The number of remaining free patch locations is also listed.
J.INIT can include error messages along with the audit trail listing. All error
messages are preceded and/or followed by asterisks (*******). Possible error
messages are:
ERROR IN PREVIOUS PATCH-FIELD-n
n = number of the field containing the error (/d = field 1)
BASE TABLE OVERFLOW
An attempt has been made to insert too many names in the internal
symbol table (limit = 215 10).
PATCH AREA OVERFLOW
An attempt has been made to insert too many patches in the area defined
during SYSGEN or on the /P directive.
DUPLICATE NAME -name
An attempt has been made to insert the displayed name in the internal
symbol table and it is currently in the table.
END OF FILE ON patchfilename
An attempt has been made to save the source image of a patch on the
patch file and it is full (limit = 900 images).
UNABLE TO ALLOCATE patchfilename
If the patch file does not exist, J.P ATCH attempts to create it. This
message indicates that sufficient disk space was unavailable. 100 blocks
are required.
UNABLE TO ALLOCATE INPUT DEVICE
The request to allocate the patch input device has been denied.
PATCH ERRORS DETECTED
Output at the end of the audit trail if any patch errors were detected. Also
output to the console teletypewriter.
(
EXTD/NONEXTD ADDRESS CONFLICT
Indicates an extended patch exceeds the first 16KW of memory or an
attempt was made to: place a nonbase patch in the extended area or place
an extended patch in a nonbase area.
MPX-32 Reference Volume III
9-9
Examples
,{~-""
(~JI
9.6 Examples
Changing locations in a resident module
/0 NAM
/C H.rOCS 2154 CA803331
/C H.rOCS 574 EC001003 R
/E
Get module description
See Note 1
See Note 2
End of patches
Notes:
1.
2.
Changes location 21540f H.rOCStoaLIR5,x'3331'.
Changes location 574 of H. rocs to a BU to location 10030fH.lOCS.
Inserting into the patch area
/0
/G
/$
/$
/$
/R
/$
/0
/E
NPR NHE NAM
H.REXS 100
CB050001
H.REXS F20005E5
EE000009 R
00000000
SYM
See
See
See
See
Note
Note
Note
Note
1
2
3
4
List symbol table
End of patches
Notes:
1.
2.
3.
4.
No print, no haIt on error, get module definitions, save patches.
Branch to the patch area from location 100 of H. REXS.
CI R6, 1 inserted in the next free location of patch area.
BCF EQ,5E 5 of H. REXS inserted.
c
9-10
Online System Patch Facility (J.lNIT)
Automatic Mounting of Public Volumes
9.7 Automatic Mounting of Public Volumes
The last function of J.INIT before exiting is the mounting of any volumes in the
M.MOUNT file.
See Chapter 10 of this volume for more information.
(-
.
MPX-32 Reference Volume III
9-11/9-12
o
o
10
10.1
System Administrator Services
Introduction
The system administrator (SA) implements and controls the system and resource
protection facilities provided by MPX-32. System protection is concerned primarily
with user access to the system. The system protection facilities are implemented by
the M.KEY and M.PRJCT file.
While not a direct function of the M.KEY and M.PRJCT files, resource protection
facilities are not fully utilized unless these files are present and set up properly.
An individual can be designated to have the responsibilities of initializing terminals,
responding to system console messages as necessary for system operation, and
initializing floppy disk media.
Within a task, a privileged function can be performed for an unprivileged user with an
SVC call. At the command processor level, this is done by allowing users to execute
tasks that have the SA attribute. This attribute is established when the load module or
executable image is created.
The SA attribute permits the task to:
(
•
•
•
•
•
•
access resources without authorization checking
use the M.CALL macros (SVC 0)
mount public volumes
update the current system date and time
invoke the dual-processor shared-volume recovery task (J.UNLOCK)
set and override timeout and logon counters for security purposes
The SA attribute is honored only if the load module or executable image file resides
on the system volume and the owner of the file is SYSTEM.
Any task executed with OWNER=SYSTEM also has the SA attribute.
A task cataloged with SA can also specify the NODEBUG attribute to prevent
unauthorized users from modifying the code.
M.CALL macros can be used by SA tasks that are not privileged. Therefore,
programs for such tasks should be written only by users with a thorough knowledge of
the operating system.
MPX-32 Reference Volume III
10-1
Introduction
The operating system also provides various optional services to control access to the
system, accounting services, and user diagnostics. These services are invoked through
the following system files:
• M.KEY - Defines the set of authorized users of the system. Absence of this file
prevents control of access to the system. This file is managed by the KEY
program.
• M.PRJCT - Defines the set of authorized project group names for resource access
and accounting. This file is managed by J.PRJCT.
• M.ACCNT - Records accounting information for terminal sessions and jobs
• M.CNTRL - Provides automatic command file processing at logon
• M.ERR - Contains system error explanations. This file can be modified to include
user error messages.
• M.MOUNT - Provides automatic mounting of specified volumes during IPL
If the M.KEY, M.PRJCT, M.ACCNT, or M.ERR file is recreated, the new file is
immediately effective. If control switch 4 is set at IPL, these four files are ignored
while the system is running.
10.2 M.KEY File
The M.KEY file controls access to the system.
Any user may logon to the system if the M.KEY file does not exist. All users who
logon while the M.KEY file does not exist will be assigned the working directory
@SYSTEM(SYSTEM).
Once the M.KEY file has been created, only users established in this file may use the
system.
For each user in the file, the SA can specify the following attributes or restrictions:
•
•
•
•
•
•
•
password - a 1- to 16-character owner password required for logon
key - a 1- to 8-character owner key required for logon
default project group name
default volume name
default working directory
default tab settings
ftagwords - a series of directives that determine access to various parts of the
system
If a user has been assigned a default volume or default working directory that cannot
be located when the user logs on to the system, the following message is displayed:
*YOUR DIRECTORY IS UNAVAILABLE, PLEASE CHANGE DIRECTORY
When this occurs, the user may only execute TSM directives. The user's volume and
directory name will be shown as asterisks by the $SHOW directive.
10-2
System Administrator Services
M.KEY File
(To prevent access to the M.KEY file by any user except SYSTEM, start up the system
with control switch 4 set and create an M.KEY file under owner name SYSTEM using
the following VOLMGR directive:
VOL>CREATE @SYSTEM(SYSTEM)M.KEY ACCE=OW(R W A D)VOL>ACCE=PR() ACCE=OT() ZERO=Y AUTO=N SIZE=N VOL>REPLACE=Y
Restart the system with control switch 4 reset.
When these access rights are specified, users cannot change their password or key at
logon and the PASSWORD and KEYWORD tasks do not function.
10.2.1
Using KEY
The system administrator attribute is required to run the KEY program. The primary
file required to use KEY is an input file containing M.KEY information for each
owner.
M.KEY is supplied on the Master SDT with owner name SYSTEM.
If the M.KEY file is recreated, the new file is immediately effective. If control switch
4 is set at IPL, the M.KEY file is ignored while the system is running.
The input file is prepared using the Edit STORE command. This file must be
assigned to logical file code INP. Output is unblocked and automatically assigned to
the system file M.KEY.
When recreating the M.KEY file, valid owner names must be specified before logging
off the system so that valid names exist for future logons.
TSM>$ASSIGN INP TO FILENAME
TSM>$KEY
10.2.2 Directives
KEY directives have one or more associated parameters. Some parameters can be
preceded by a keyword and equal sign. Multiple parameters can be separated by TSM
delimiters: spaces, commas, equal sign, and parentheses.
Continuation of the directive to the next physical line is specified by a comma
following the last parameter on the line.
KEY directives are summarized below and described individually on the following
pages.
(:
MPX-32 Reference Volume III
10-3
M.KEY File
Directive
Description
ADD
authorizes a new user access to the system
CHANGE
changes the attributes of an existing owner
DEFAULTS
resets system defaqlts and establishes defaults for subsequent ADD
commands
DELETE
removes an existing owner from the M.KEY file
LOG
lists existing owners and all attributes except their key
NEWFll..E
clears the M.KEY file of all existing entries
X
indicates end of file and exits
10.2.2.1 ADD Directive
The ADD directive authorizes new users access to the system and specifies any
restrictions applicable to them.
Syntax
ADD
[OWNER=]name [attribute]
[OWNER=]name
name is the 1- to 8-character owner name
[attribute] is one of the following attributes or restrictions to be in effect for the
specified owner:
PASSWORD=name
name is the 1- to 16-character owner password associated
with this owner. If this parameter is not specified, the default
is no password.
KEY=name
name is the 1- to 8-character key associated with this owner.
If not specified, the default is no key. For a list of restricted
keywords refer to Table 10-1.
VOLUME=name
name is the 1- to 16-character default volume name
associated with this owner. If not specified, the default is
SYSTEM.
DIRECTORY=name
name is the 1- to 16-character default directory name
associated with this owner. If not specified, the default is
SYSTEM.
PROJECT=name
name is the 1- to 8-character default project group name
associated with this owner. If not specified, the default is
SYSTEM.
"
10-4
System Administrator Services
o
M.KEY File
(
TABS=tab [,tab] ...
sets decimal tab positions to be associated with this owner.
As many as 8 tab positions can be set. If not specified,
default tabs are set at 10, 20, and 36.
[FLAGS= ]restrict
restrict is one of the following:
ALL
specifies all restrictions apply to this owner
NONE
specifies no restrictions apply to this owner
ALLEXCEPT Jfist
specifies all restrictions except the following
listed key words (jUst) apply to this owner
jUst
specifies the key words whose operations cannot
be performed by this owner. See Table 10-1.
(
MPX-32 Reference Volume 1\1
10-5
M.KEY File
Table 10-1
Restricted Keywords
The following keywords disable the corresponding OPCOM directives:
ABORT
ACnvATE
BATcH
BREAK
CONNECf
CONTINUE
DELETEfIMER
DEPRINT
DEPUNCH
DISABLE
DISCONNECf
DISMOUNT
DUMp
ENABLE
ESTABLISH
HOLD
KILL
LIST
MODE
MODIFY
MOUNT
OFFLINE
ONLINE
PURGEAC
REDIRECf
REPRINT
REPUNCH
REQUEST
RESUME
SEARCH
SEND
SETTIMER
SNAP
STATUS
SYSASSIGN
TIME
When the following keywords are specified, the corresponding restrictions apply:
Keyword
Restriction
CATPRIV
CHANGEDEF
MDT
OWNERAcC
PRIORITY
PRIVll..EGE
REMOVE
RESTART
USERFLAGS (n)
Cannot catalog privileged programs.
Cannot change working directory or project group.
Cannot use the I.MDTI utility*
Cannot access tasks with different owner name
Cannot use the TSM $URGENT directive
Cannot run privileged programs other than OPCOM
Cannot use TSM $REMOVE directive
Cannot use the TSM $RESTART directive
Decimal number in range 0 to 255 for use by user for security.
User programs may examine this number in bits 56 to 63 of
T.ACCESS.
When the following keywords are specified, the corresponding defaults apply:
Keyword
Default
NOCOMMAND
SEQQUENTIAL
OPTION NOCOMMAND in TSM
If more than one job is submitted by a TSM $SUBMIT
directive, the jobs execute sequentially. If sequential
execution is required for jobs run using a BATCH or RUN
directive, S must be specified on the $10B directive line.
* The restrictions on this keyboard apply to only the KEY ADD directive.
10·6
System Administrator Services
M.KEY File
10.2.2.2 CHANGE Directive
The CHANGE directive changes the attributes of an existing owner of the system.
Syntax
CHANGE [OWNER=]name [attribute]
[OWNER= ]name
name is the 1- to 8-character owner name
[attribute]
is one of the following attributes or restrictions to be in effect for the
specified owner:
PASSWORD=name
name is the 1- to 16-character owner password associated
with this owner. If this parameter is not specified, the default
is no password.
KEY=name
name is the 1- to 8-character key associated with this owner.
If not specified, the default is no key. For a list of restricted
keywords refer to Table 10-1.
VOLUME=name
name is the 1- to 16-character default volume name
associated with this owner. If not specified. the default is
SYSTEM.
DIRECfORY=name
name is the 1- to 16-character default directory name
associated with this owner. If not specified. the default is
SYSTEM.
PROJECf=name
name is the 1- to 8-character default project group name
associated with this owner. If not specified, the default is
SYSTEM.
TABS=tab [,tab] ...
sets decimal tab positions to be associated with this owner.
As many as 8 tab positions can be set. If not specified,
default tabs are set at 10. 20, and 36.
[FLAGS=]restrict
restrict is one of the following:
ALL
specifies all restrictions apply to this owner
NONE
specifies no restrictions apply to this owner
ALLEXCEPT jUst
JUst
MPX-32 Reference Volume III
specifies all restrictions except the following
listed key words (jlist) apply to this owner
adds the listed keywords to the existing
restrictions for this owner. See Table 10-1.
10-7
M.KEY File
10.2.2.3 DEFAULTS Directive
The DEFAULTS directive establishes defaults for subsequent ADD directives.
Each DEFAULTS remains in effect until the next DEFAULTS is specified. When the
next DEFAULTS is specified, the default for any keyword not specified is the
SYSTEM default. When more than one keyword default is to be defined for a group
of users, all defaults must be specified with one DEFAULTS directive as shown in the
example of directive usage.
Syntax
DEFAULTS [attribute]
[attribute]
are the following attributes or restrictions to be used as defaults for
subsequent ADD directives:
KEY=name name is the 1- to 8-character key associated with the specified
owner. If not specified, the default is no key. For a list of
restricted keywords refer to Table 10-1.
VOlUME=name
name is the 1- to 16-character default volume name
associated with the specified owner. If not specified, the
default is SYSTEM.
DIRECfORY=name
name is the 1- to 16-character default directory name
associated with the specified owner. If not specified, the
default is SYSTEM.
PROJECf=name
name is the 1- to 8-character default project group name
associated with the specified owner. If not specified, the
default is SYSTEM.
TABS=tab [,tab] ...
sets decimal tab positions to be associated with the specified
owner. As many as 8 tab positions can be set. If not
specified, default tabs are set at 10, 20, 36, and 64.
c
10-8
System Administrator Services
M.KEY File
[FLAGS=]restrict
restrict is one of the following:
ALL
specifies all restrictions apply to the specified
owner
NONE
specifies no restrictions apply to the specified owner
ALL EXCEPT JUst
specifies all restrictions except the following
listed key words (jUst) apply to the specified
owner
Jlist
specifies the key words whose operations cannot
be performed by the specified owner. See Table
10-1.
10.2.2.4 DELETE Directive
The DELETE directive removes an existing owner from the M.KEY file.
Syntax
DELETE [OWNER=]name
[OWNER= ]name
(
name is the 1- to 8-character owner name
10.2.2.5 LOG Directive
The LOG directive lists existing owners and all attributes except their key.
Syntax
LOG [[OWNER=]name]
[[OWNER=]name]
name is the 1- to 8-character owner name whose attributes are to be
displayed. If not specified, all owners attributes are displayed.
10.2.2.6 NEWFILE Directive
The NEWFlLE directive clears the M.KEY file of all existing entries. If present, it
must be the first directive specified.
Syntax
NEWFILE
MPX-32 Reference Volume III
10-9
M.KEY File
10.2.2.7 X Directive
The X directive indicates end-of-file and exit.
Syntax
X
10.2.3 Examples of Directive Usage
NEWFILE
ADD OWNER=SYSTEM VOLUME=SYSTEM DIRECTORY=SYSTEM
DEFAULTS PROJECT=WORK TABS=7,12,24 FLAGS=NONE
ADD OWNER=OWNl VOLUME=VOLl DIRECTORY=DIRl
ADD OWNER=OWN2 VOLUME=VOL2 DIRECTORY=DIR2
ADD OWNER=OWN3
DEFAULTS VOLUME=TEST PROJECT=EXAM
ADD OWNER=OWN4 KEY=0416 TABS=10,25,50
CHANGE OWNER=OWN3 VOLUME=VOL3
ADD OWNER=OWN5 FLAGS=ALLEXCEPT MOUNT, SEARCH, PRIVILEGE, SEQUENTIAL
ADD OWNER=OWN6
DEFAULTS VOLUME=TEST DIRECTORY=DIR3 PROJECT=UTIL FLAGS=ABORT,HOLD,
MOUNT,MODIFY,PRIVILEGE,PRIORITY,SEQUENTIAL TABS=9,18,36
ADD OWNER=OWN7 KEY=1205
ADD OWNER=OWN8 KEY=1103
ADD OWNER=OWN9 KEY=0613
DELETE OWN3
LOG
x
c
10-10
System Administrator Services
M.PRJCT File
10.3 M.PRJCT File
The M.PRJCT file contains the project group names that are valid to use with the
TSM CHANGE PROJECT directive and are used by the accounting utility
M.ACCNT. If a M.PRJCT file does not exist. any project group name is valid. If an
M.PRJCT file does exist and an owner has a default project name not contained in
M.PRJCT. no project name is extablished at logon.
When using the accounting utility. project group names can be established for each
owner name in two ways:
1.
Using the Volume Manager. an M.PRJCT file can be created under the owner
SYSTEM as a nonextendible file that is not accessible by PROJECTGROUP or
OTHER. The file should be zeroed. Eight entries per block can be placed in this
file from an editor-created user file using the PROJECT program J.PRJCT. The
output from the PROJECT program need not be assigned; output automatically
goes to M.PRJCT unblocked. Only users with the system administrator attribute
can use the PROJECT program.
Example
ENTER YOUR OWNERNAME:SYSTEM
TSM>VOLMGR
VOL>CREATE @SYSTEM(SYSTEM)M.PRJCT AUTO=N ZERO=YVOL>ACCESS=PROJECTGROUP()VOL>ACCESS=OTHER() SIZE=4
VOL>X
TSM>$ASSIGN INP TO PFILE
TSM>PROJECT
(
2.
Using the KEY utility. default project group names can be established for each
owner name.
Project group names can be changed by a user with the TSM $CHANGE PROJECT
directive. When a project group name is changed. the account utility is terminated for
the previous group name and initiated for the new group name. The change remains
in effect until changed again or the user logs off the system. When the user logs on
the system. default project group names are re-established.
10.3.1
Using the PROJECT Program
The primary file required to use PROJECT is an input file containing M.PRJCT
information for each owner.
This input file (filename in the following example) is prepared using the Edit STORE
directive. It must be assigned to the logical file code INP. Output is unblocked and
automatically assigned to the system file M.PRJCT.
Example
TSM>$ASSIGN INP TO filename
TSM>$PROJECT
MPX-32 Reference Volume III
10-11
M.PRJCT File
",(---'
Only owners with the system administrator attribute can run the PROJECT program.
-~--_/
If the M.PRJCT file is modified or recreated, the changed or new file does not
become effective until the system is rebooted. If control switch 4 is set at IPL, the
M.PRJCT file is ignored while the system is running.
. 10.3.2 Directives
Input to the PROJECT program is a series of directives that are summarized below
and described in detail on the following pages.
PROJECT directives have one or more associated parameters. Some parameters can
be preceded by a keyword and equal sign. Multiple parameters can be separated by
the normal TSM delimiters: spaces, commas, equal sign, and parentheses.
Continuation of a directive to the next physical line is specified by a comma following
the last parameter on the line.
PROJECT directives are summarized below and described individually on the
following pages.
10.3.2.1
Directive
Description
ADD
authorizes a new project group name
CHANGE
changes a key associated with a project group name
DELETE
removes a project group name from the PROJECT file
LOG
lists existing project group names
NEWFILE
clears the M.PRJCT file of all existing entries
X
indicates end-of-file and exits
ADD Directive
The ADD directive adds new project group names.
Syntax
ADD [PROJECf=]pname [KEY=key]
[PROJECf= ]pname
pname is the 1- to 8-character project group name to be added
[KEY=key]
key is the 1- to 8-character key to be associated with this project group
name
10-12
System Administrator Services
',--
/'
M.PRJCT File
(
10.3.2.2 CHANGE Directive
The CHANGE directive changes an existing key associated with a project group name
or establishes a key with an existing project group name that does not have an
associated key. A key cannot be deleted with this directive. If a key is to be deleted,
the DELETE directive must be used to delete the project name; the ADD directive
must then be used to re-establish the project name without a key.
Syntax
CHANGE [PROJECf=]pname [KEY=key]
[PROJECf= ]pname
pname is the 1- to 8-character project group name
[KEV=key]
key is the new 1- to 8-character key to be associated with this project
group name
10.3.2.3 DELETE Directive
The DELETE directive removes an existing project group name from the PROJECT
file.
Syntax
DELETE [PROJECf= ]pname
[PROJECf= ]pname
pname is the 1- to 8-character project group name to be deleted
10.3.2.4 LOG Directive
The LOG directive lists existing project group names.
Syntax
LOG [PROJECf= ]pname
[PROJECf=]pname
pname
is the 1- to 8-character project group name whose authorization is to be
listed. If not specified, all project group names are displayed.
MPX-32 Reference Volume III
10-13
M.PRJCT File
10.3.2.5 NEWFILE Directive
The NEWFILE directive clears the M.PRJCf file of all existing entries. If present, it
must be the first directive specified.
Syntax
NEWF1LE
10.3.2.6 X Directive
The X directive indicates end-of-file and exit.
Syntax
X
10.3.3 Examples of Directive Usage
NEWFILE
ADD PROJECT=SYSTEM
ADD PROJECT=WORK
ADD PROJECT=EXAM
ADD PROJECT=UTIL
ADD TEST
ADD LANG KEY=XYZ
ADD DOC KEY=JM
CHANGE PROJECT=LANG KEY=DR
CHANGE TEST KEY=CASE
DELETE PROJECT=DOC
ADD DOC
LOG
X
10-14
System Administrator Services
M.ACCNT File
10.4 M.ACCNT File
The job accounting program indicates elapsed time, CPU time, and IPU time for all
jobs. The M.ACCNT file must be created by the Volume Manager under the owner
name SYSTEM as a nonextendible zeroed file with read access by PROJECTGROUP
and OTHER. Its size is determined by the need of the individual site. Its format is
16 word entries in an unblocked 192W physical record. This file is where job
accounting information is collected for use by TSM.
Example
ENTER YOUR OWNERNAME:SYSTEM
TSM>VOLMGR
VOL>CREATE @SYSTEM(SYSTEM)M.ACCNT AUTO=N ZERO=Y SIZE=lOOVOL>ACCESS=PROJECTGROUP(R)VOL>ACCESS=OTHER(R)
The M.ACCNT file is created as a nonextendible file on volume SYSTEM and
directory SYSTEM. PROJECTGROUP and OTHER have read access. As many as
1200 entries can be specified.
If the M.ACCNT file is recreated, the new file does not become effective until the
system is rebooted. If control switch 4 is set at IPL, the M.ACCNT file is ignored
while the system is running.
Default project group names for accounting purposes can be established with the
M.KEY utility.
Data collected by the accounting program can be retrieved with the OPCOM LIST
command. Refer to the OPCOM chapter in Reference Manual Volume II.
The format of M.ACCNT file entries follows.
MPX·32 Reference Volume III
10-15
M.ACCNT File
o
Word 0-1
2-3
7 8
15
16
23
24
31
Owner name (1- to 8-character ASCII). See Note 1.
Project (1- to 8-character ASCII). See Note 2.
4-5
Date (mm/dd/yy) (ASCII). See Note 3.
6-7
Logon time (hh/mm/ss) (ASCII). See Note 4.
8-9 Elapsed time (hh:mm:ss) (ASCII). See Note 5.
10
Raw CPU time (Binary). See Note 6.
11
Raw IPU time (Binary). See Note 7.
12-13
Origin (1- to 8-character ASCII). See Note 8.
14-15
Reserved
Notes:
1.
2.
3.
4.
5.
6.
7.
8.
10-16
Owner name - the 1- to 8-character ASCII owner name associated with the job
Project - the 1- to 8-character ASCII alphanumeric project name or number
associated with the job
Date - the ASCII numeric date associated with the job
Logon time - the ASCII numeric time of day on the 24-hour clock the user
signed on the system
Elapsed time - the total time (24-hour clock) the user was signed on the system
in ASCII
Raw CPU time - the actual number of 38.4 microsecond intervals of CPU time
for the job (unformatted equivalent of CPU time) in binary
Raw IPU time - the actual number of 38.4 microsecond intervals of IPU time for
the job (unformatted equivalent of IPU time) in binary
Origin - the ASCII task pseudonym for the accounting session
System Administrator Services
M.CNTRL File
(~
10.5 M.CNTRL File
The M.CNTRL file is a TSM command file selected by J.TSM automatically when a
user logs on. If the M.CNTRL file exists, it must be located in the system directory.
As the M.CNTRL file can contain TSM directives and comments, it can establish
defaults, send messages, and further restrict access to the TSM environment.
Example
EDT>COL
1. NOTE LOG ON AT
2.
! TIME
3.
EDT>STO M.CNTRL SYS
This causes the time and date to be automatically displayed when a user logs on the
system. NOTE indicates the line is a comment line.
Notes:
Attempts to break out of the M.CNTRL file are ignored.
Errors in M.CNTRL file processing result in normal error processing for control files.
('
(
MPX-32 Reference Volume III
10-17
M.ERR File and xx.ERR Files
10.6 M.ERR File and xx.ERR Files
The M.ERR file contains system abort codes and messages, and should not be
modified. The xx.ERR files contain messages for unbundled products and user abort
codes. For example, Ff.ERR contains FORTRAN 77+ abort messages.
The abort code format is:
xxnn
x
n
is an alphabetic character
is a numeral
The file SJ.XX.ER is provided on the SDT and can be modified with other abort
messages by using the Text Editor (EDIT). When an abort code cannot be found in
the M.ERR file, J.TSM appends .ERR to the abort code's prefix. Using the resulting
name, J.TSM attempts to allocate a file in the system directory. If allocation occurs,
the file is searched for the error code.
10.6.1
Creating xx.ERR File
Modify SJ.XX.ERR as follows:
1.
2.
3.
Enter EDIT.
Use file SJ.XX.ER.
Modify the prefix at label STARTX.
Example:
4.
. 5.
6.
STARTX PREFIX C'MD' MEDIA ERRORS
Remove the example messages .
Add messages using C strings.
After each message, call macro MSG xX,nn where xx is the prefix specified at
STARTX; nn is the abort number in ascending order.
Example (starts in the second column):
7.
DATA C'ERROR ENCOUNTERED READING SYC FILE'
MSG LM,Ol
DATA C'ERROR ENCOUNTERED WRITING TO SLO'
MSG LM,03
Save the completed file.
Example:
EDT>SAVE @SYSTEM(SOURCE)SJ.xx.ER
(xx is the prefix specified at STARTX)
( "'
,
''',
'-_ ..
..•
.J
10-18
System Administrator Services
M.ERR File and xx.ERR Files
(
8.
9.
Exit EDIT.
Submit the following job stream to install the new error file:
$JOB NEWERR OWNER
$ASSIGN SI TO SJ.xx.ER BLOCK=Y
(SJ.xx.ER is the file previously
saved in Step 7 by the Text Editor
(EDIT»
$ASSIGN BO TO OJ.XX.ER BLOCK=Y
$OPTION 1 4
$ASSEMBLE
$AS SGO TO OJ.xx.ER BLOCK=Y
(OJ. xx.ER must be created
prior to this assignment)
$IFF PATH=@SYSTEM (SYSTEM) XX. ERR GO
(xx is the prefix entered in Step 3.
This text ensures that an existing
abort file code is not destroyed).
A
$NOTE ERROR - ATTEMPT MADE TO WRITE OVER EXISTING ABORT FILE
$GOTO END
$DEFNAME GO
$ CATALOG
CATALOG xx. ERR
(xx is the prefix entered in Step 3)
$DEFNAME END
$EOJ
$$
Abort messages are immediately in effect without rebooting the system.
10.7 Terminal/ALIM/ACM Initialization (INIT)
Terminal/ALIM/ACM initialization is the process of defining hardware characteristics
of TSM and non-TSM devices. For purposes of this section, TSM devices are defined
as terminals, device type code X'OC' TY, connected through model 9110 ALIM or
8510.8511, or 8512 Eight-line Asynchronous Communications controllers. Non-TSM
devices are defined as devices other than terminals; the device type code is not TY.
but the device can be connected through these same controllers.
Hardware characteristics are typically defined by a user-created system file named
LOGONFLE, or in its absence, by a set of system supplied defaults. Characteristics
include baud rate, parity. and half or full duplex. The wakeup (ring) character for all
terminals is also defined as a hardware characteristic.
Initialization of a TSM device is handled automatically when a system is installed or
restarted. regardless of the existence of a LOGONFLE. Initialization of a non-TSM
device requires a LOGONFLE entry defining the characteristics of the non-TSM
device and the keyword NOTSM.
(
Although the lOP console is normally treated as a TSM device, it is not initialized by
INIT.
MPX-32 Reference Volume III
10-19
Terminal/ ALiM/ ACM Initialization (INIT)
10.7.1 The LOGONFLE
The LOGONFLE must contain the logon records in blocked, uncompressed format.
The Editor STORE directive can create this file.
The form of a LOGONFLE is shown below. LOGONFLE must contain a record for
the wakeup character definition and one record for each device definition. Only
characters 1 to 72 of each record are interpreted. An asterisk (*) in column 1, from
Record 2 on, indicates the line is a comment line. A semicolon (;) or an exclamation
point (!) in any position of a line, from Record 2 on, permits comments to follow on
the line.
Record 1: wakeup
Record 2: ccaa field field ...
EOF
10-20
wakeup
is a 2-digit hexadecimal number defining the character which must be
typed at interactive terminals to start a logon sequence.
ccaa
is the channel number and subaddress of the device to initialize. Must be
supplied in LOGONFLE for each device. If LOGONFLE was not
created, the system default is to initialize all addresses defined at
SYSGEN as device type TY with the system default parameters. If
channel cc exists, but no device is connected to subaddress aa, J.TINIT
will mark the device online but note them as failed (dead) devices; if cc
does not exist, J.TINIT will mark the device offline and dead.
field
is a 1- to 8-character keyword, (the first 4 characters are significant,)
describing the characteristics of a device. Fields can be entered in any
order and can be duplicated. Fields are evaluated left to right; later
entries overrule earlier entries. See Table 10-2 for valid keywords and
their significance to ALIM and 8-Line Async devices. If a LOGONFLE
is not created, all devices defined as device type TY at SYSGEN are
initialized with the system default parameters (see section 2.2 of this
chapter). Before LOGONFLE is created, J.INIT or J.TINIT will mark all
TY devices online, but note them as failed devices (dead terminals).
TSM devices not included in the LOGONFLE once it is created retain the
system default parameters and remain online and dead.
System Administrator Services
Terminal/ ALiM/ ACM Initialization (lNIT)
(~
Table 10-2
lOGONFlE Field Keywords
Category
Keyword
ALIM
8-Line Async
Baud Rate
19200
9600
7200
4800
3600
2400
2000
1800
1200
900
600
300
150
134
110
75
50
EXT
not used
9600 bps
7200 bps
4800 bps
3600 bps
2400 bps
not used
1800 bps
1200 bps
900 bps
600 bps
300 bps
150 bps
134.5 bps
110 bps
75 bps
50 bps
external rate
19200 bps
9600 bps
7200 bps
4800 bps
3600 bps
2400 bps
2000 bps
1800 bps
1200 bps
not used
600 bps
300 bps
150 bps
134.5 bps
110 bps
75 bps
50 bps
not used
Parity
ODD
EVEN
NONE
odd parity
even parity
no parity
odd parity
even parity
no parity
Duplex
HALF
half duplex
full duplex
half duplex
full duplex
FULL
full duplex bit set in
UDT
Stop Bits
Sl
S1.5
S2
1 stop bit
1.5 stop bits
2 stop bits
1 stop bit
1.5 stop bits
2 stop bits
Character Size
8
7
6
5
8-bit characters
7 -bit characters
6-bit characters
5-bit characters
8-bit characters
7 -bit characters
6-bit characters
5-bit characters
Miscellaneous
GRAP
MODEM
REMOTE
NOTSM
INIT
graphic device
sets modem bit in UDT
sets dial-up bit in UDT
not a TSM device
initialization data present
max number of logon
attempts allowed
max time allowed at
logon prompt in seconds
max wait time for a
terminal read in minutes
graphic device
sets modem bit in UDT
sets dial-up bit in UDT
not a TSM device
initialization data present
max number of logon
attempts allowed
max time allowed at
logon prompt in seconds
max wait time for a
terminal read in minutes
LGC==nnn
LGT==sss
TMO==mmm
MPX~32
Reference Volume III
10-21
Terminal! ALlM! ACM Initialization (INIT)
Note:
System-wide default values can be set for LGC, LGT, and TMO by specifying
LGC, LGT, and TMO in a comment line that occurs before the first terminal
definition. Refer to the Sample LOGONFLE section in this chapter.
10.7.2 Security Counters
:MPX-32 provides the system administrator with controls that protect the system from
unauthorized access to maintain system integrity. These controls are counters,
specified in the LOGONFLE, that limit access as follows:
• the number of logon attempts allowed
• the time spent when logging on
• the amount of time that a terminal can remain I/O inactive
The following section discusses these counters and provides an example of their
usage.
10.7.2.1
Logon Attempt Counter
The logon attempt counter limits the number of logon attempts. This counter can vary
from terminal to terminal. The system administrator specifies the number of logon
attempts in the LOGONFLE as follows:
LGC=nnn
is the number of logon attempts, 0 to 255, allowed before the terminal is
marked offline. If nnn is 0, there is no limit on the number of logon
attempts. The default is O.
nnn
For more information about the LOGONFLE, refer to section 10.8.1 in this chapter.
To change the logon attempt counter, the system administrator must change the
LOGONFLE. To override the counter until the next terminal initialization, enter the
following:
T 8M> LOGCNT
termaddr nnn
termaddr
specifies the address of the terminal. If termaddr is not specified,
LOGCNT uses the value established as the system default in the
LOGONFLE.
nnn
specifies the number of logon attempts, 0 to 255, allowed. The default is
O.
If a terminal is marked offline, the system administrator can enable the terminal with
the TSM $ENABLE command. See Chapter 1 of the MPX-32 Reference Manual
Volume II for more information.
10-22
System Administrator Services
Terminall ALiM/ ACM Initialization (INIT)
10.7.2.2 Logon Timeout Counter
The logon timeout counter limits the time that can be spent at a logon prompt. If this
counter expires, the terminal is marked offline and the logon attempt counter is
incremented. The system administrator specifies the logon timeout counter in the
LOGONFLE as follows:
LGT=sss
specifies the number of seconds, 0 to 255, that a terminal waits at a logon
prompt before being logged off. The default is O.
sss
To change the logon timeout counter, the system administrator must change the
LOGONFLE. To override the counter until the next terminal initialization, enter the
following:
TSM>LOGTlME termaddr sss
termaddr
specifies the address of the terminal. If termaddr is not specified,
LOGTIME uses the value established as the system default in the
LOGONFLE.
sss
specifies the number of seconds, 0 to 255, that the terminal waits at a
logon prompt. The default is O.
10.7.2.3 Terminal Timeout Counter
The terminal timeout counter limits the time that a terminal can remain I/O inactive.
The system administrator specifies the terminal timeout counter in the LOGONFLE as
follows:
TMO=mmm
mmm
specifies the number of minutes, 0 to 999, that a terminal can be I/O
inactive before it is logged off. If mmm is 0, there is no limit. The
default is O.
To change the terminal timeout counter, the system administrator must change the
LOGONFLE. To override the counter until the next terminal initialization, enter the
following:
T SM>TERMOUT termaddr mmm
termaddr
specifies the address of the terminal. If termaddr is not specified,
TERMOUT uses the value established as the system default in the
LOGONFLE.
mmm
specifies the number of minutes, 0 to 999, that a terminal can be I/O
inactive before it is logged off. If mmm is 0, there is no limit. The
default is O.
If a terminal is marked offline, the system administrator can enable the terminal with
the TSM $ENABLE command. See Chapter 1 of the MPX-32 Reference Manual
Volume II for more information.
MPX-32 Reference Volume III
10-23
Terminal/ ALiM/ ACM Initialization (INIT)
10.7.2.4 Security Counters Example
The following is an example that sets the logon attempt counter, the logon timeout
counter, and the terminal timeout counter.
05
*
!RING IN CTRL/E)
LGC=5 LGT=45 TMO=120 !system defaults
7EAO 19200 FULL EVEN 7 Sl
7EA1 9600 FULL EVEN Sl EXON
7EA2 19200 FULL EVEN 7 SlWXON TMO=60
7EA3 9600 FULL EVEN 7 Sl WXON
7EA4 19200 FULL EVEN 7 Sl LGT=120
7EAS 19200 FULL EVEN 7 Sl
7EA6 19200 FULL EVEN 7 Sl WXON
7EA7 1200 FULL NONE 6 WXON REMOTE LGC=3
!no changes
!no changes
!Sets Term Timeout Ctr
!no changes
!sets logon timer
!no changes
!no changes
!sets logon counter
c
10-24
System Administrator Services
Terminal/ALIM/ACM Initialization (INIT)
10.7.3 ALiM Terminal Record Syntax and Defaults
Syntax
ccaa [baud] [HALFIFULL] [ECHO I NOECHO] [parity] [charsize] [stopbits] [GRAP]
[MODEM] [REMOTE] [NOTSM] [INIT value] [LGC=nnn] [LGT=sss] [TMO=mmm]
ccaa
is the channel and subaddress of the device.
[baud]
is the baud rate: 9600, 7200, 4800, 3600, 2400, 1800, 1200,900,600,
300, 150, 134, 110, 75, 50, or EXT. If EXT is entered, the baud rate is
set externally. The default is 9600 baud.
[HALF I FULL]
is the half or full duplex operation. The default is HALF.
[ECHO I NOECHO]
specifies characters are or are not to be echoed by the computer as they
are received. The default is ECHO for FULL duplex or NOECHO for
HALF duplex.
[parity]
is ODD, EVEN, or NONE. The default is EVEN. If NONE is specified,
the serial character is smaller due to the absence of the parity bit.
[charsize] is the character size: 5,6, 7, or 8. The default is 7.
[stopbits]
is the number of stop bits: Sl, S1.5, or S2. The default is S1.
[GRAP]
sets the graphic bit in the UDT. GRAP specifies that standard message
processing should be suppressed for this device. The default is not
graphic device.
[MODEM] sets modem bit in UDT. The default is not set.
[REMOTE] sets dial-up bit in UDT. The default is not set. Also, sets switched
mode. The default is private mode.
[NOTSM] specifies a non-TSM device. The default is TSM device.
[INIT value]
indicates the presence of hexadecimal initialization data. Five words of
hexadecimal value in the ALIM initialization format. See section
10.7.3.1, ALIM Initialization Format.
[LGC=nnn]
nnn specifies the number of logon attempts, 0 to 255, allowed before the
terminal is marked offline. If nnn is 0, there is no limit on the number of
logon attempts. The default is O.
[LGT=sss] sss specifies the- number of seconds, 0 to 255, that a terminal waits at a
logon prompt before being logged off. The default is O.
[TMO=mmm]
mmm specifies the number of minutes, 0 to 999, that a terminal can
remain I/O inactive.
MPX-32 Reference Volume III
10-25
Terminal! ALlM! ACM Initialization (INIT)
The following table shows possible ALIM terminal configurations and their resulting
operations.
10.7.3.1
SYSGEN Device
Directive, FULL
0Etion Specified
LOGONFLE
FULL/HALF
0Etion Specified
LOGONFLE
ECHO/NOECHO
Option Specified
Resulting
Tenninal
Operation
yes
yes
yes
yes
no
no
no
no
full
full
half
half
full
full
half
half
echo
noecho
echo
noecho
echo
noecho
echo
noecho
half,echo
full,noecho
half,echo
half,noecho
half,echo
half,noecho
half,echo
half,noecho
ALiM Initialization Format
Fields containing an asterisk (*) are required; the remaining fields are optional. If not
specified, the default is OFF.
o
Word 1
7
8
15
16
23
24
31
Channel time-out value*. See Note 1.
2
Mode *. See Note 2.
Baud *. See Note 3.
Fonnat. See Note 4.
Zero
3
Code. See Note 5.
STX. See Note 6.
EXT. See Note 7.
CHAR A.
See Note 8.
4
CHAR B. See Note 9.
CHAR C.
See Note 10.
CHAR D (ring).
See Note 11.
Sl. See
Note 12.
5
S2. See Note 13.
Zero
Notes:
1.
Bits 0-31 specify the channel time-out value in seconds. For example,
X'0000005A' gives a time-out value of 90 seconds.
c-"·
I'
10-26
System Administrator Services
,
,
I
Terminal! ALlM! ACM Initialization (INIT)
2.
Mode bits are defined as follows:
Bits
Description
0-1
Stop bits (SB) are interpreted as follows:
Bit 0
Bit 1
--=:::S=B_ _ __
o
0
invalid
o
1
1 stop bit
0
1.5 stop bits
1
1
1
2 stop bits
2
Parity selection (PS) is interpreted as follows:
Bit Setting
o
1
Description
odd parity
even parity
3
Parity enable (PE) is interpreted as follows:
Description
Bit Setting
o
disable parity
1
enable parity
4-5
Character length (CL) is interpreted as follows:
Bit 4
Bit 5
CL
5 bits
o
o
o
6 bits
1
7 bits
1
o
1
1
8 bits
6-7
Baud rate factor (BRF) is interpreted as follows:
Bit 6
Bit 7
BRF
-----o
0
synch mode
o
1
IX
1
0
16X
1
1
64X
(
MPX-32 Reference Volume III
10-27
Terminal/ALIM/ACM Initialization (INIT)
3.
Baud rate bits are defined as follows:
Bits
Description
8-11
Zero
With 16X selected in bits 6-7, baud rate is interpreted as follows:
Bit 13
Bit 14
Bit 15
Baud Rate
Bit 12
12-15
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
0
4.
0
0
0
1
1
1
1
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
50
75
110
134.5
150
300
600
900
1200
1800
2400
3600
4800
7200
9600
EXT
Format bits are defined as follows:
"10."
Bits
16
17
18
19
Description
enable hardware ring detection
enable break detection
inhibit Ims RTS off delay
full or half duplex interpreted as follows:
Description
Bit Setting
half duplex (HDX)
0
1
full duplex (FOX)
20
Switch indicator is interpreted as follows:
Description
Bit Setting
private
0
1
switched line
21
Must be set for types 103 and 212 modems
Description
Bit Setting
switched
0
I
constant
22-23
Zero
c
10-28
System Administrator Services
Terminal! ALlM! ACM Initialization (INIT)
(
5.
Code bits are defined as follows:
Bits
0-3
Description
zero
4-7
Code bits (4-bit hexadecimal value) are interpreted as follows:
Value
Description
o
no action
1
terminate on CHAR A
2
terminate on CHAR A or B
terminate on CHAR A, B, or C
3
4
terminate on CHAR A * followed by B*
terminate on CHAR A* followed by B*
5
followed by C*
* These characters must be different from STX, ETX, ring, or
strip characters
6.
Start of text character (STX) bits are defined as follows:
Bits
8
Description
Action bit interpreted as follows:
Bit Setting
o
(
1
9-15
Description
recognize character
inhibit character recognition
Start of text character (STX) to be recognized (7-bit ASCII
character). The character must be different from ETX, strip,
ring, and terminate characters.
Upon recognition, unblind mode is set causing this character and subsequent
characters to be passed to memory. Blind mode, which deletes characters or
blocks of characters, is set by either a receive blind order or the recognition of an
ETX character during a receive blind order.
MPX-32 Reference Volume III
10-29
Terminal/ ALiM/ ACM Initialization (INIT)
7.
End of text character (ETX) bits are defined as follows:
Bits
16
Description
Action bit interpreted as follows:
Bit Setting
o
1
17 -23
Description
recognize character
inhibit character recognition
End of text character (ETX) to be recognized (7 -bit ASCII
character). The character must be different from STX, strip,
ring, and terminate characters.
This character is recognized only during a receive blind order. Upon recognition,
blind mode is set which blocks characters from being passed to memory.
However, character recognition is still in effect for the STX and the ABC
characters.
8.
Termination CHAR A bits are defined as follows:
Bits
24
Description
zero
25-31
termination CHAR A (7-bit ASCII character) which must be different
from STX, ETX, ring, and strip characters.
Recognition of CHAR A causes channel end if the character is recognized in the
manner specified in bits 0-7.
9.
Termination CHAR B bits are defined as follows:
Bits
o
1-7
Description
zero
termination CHAR B (7-bit ASCII character) which must be different
from STX, ETX, ring, and strip characters.
Recognition of CHAR B causes channel end if the character is recognized in the
manner specified in Word 3, bits 0-7.
10. Termination CHAR C bits are defined as follows:
Bits
8
Description
zero
9-15
termination CHAR C (7-bit ASCII character) which must be different
from STX, ETX, ring, and strip characters.
Recognition of CHAR C causes channel end if the character is recognized in the
manner specified in Word 3, bits 0-7.
10-30
System Administrator Services
c'· ·
"
.'
Terminal! AliMI ACM Initialization (INIT)
11. Ring interrupt CHAR D bits are defined as follows:
Bits
16
Description
Action bit interpreted as follows:
Bit Setting
o
1
17 -23
Description
recognize character
inhibit character recognition
Ring interrupt CHAR D bits (7 -bit ASCII character) which must be
different from STX, ETX, strip, and terminate characters.
When recognized, and no I/O is in progress, a ring interrupt is
generated. Ring character reporting is enabled and disabled in
the same manner as breaks.
12. Strip character (SI) bits are defined as follows:
Bits
24
Description
Action bit interpreted as follows:
Bit Setting
o
1
25-31
Description
recognize character
inhibit character recognition
Strip character (S 1) bits (7 -bit ASCII character) which must be
different from STX, ETX, ring, and terminate characters.
The SI character is to be stripped from an incoming data stream. The character
is unconditionally removed from the input buffer. The character cannot have
been previously specified for a control function.
13. Strip character (S2) bits are defined as follows:
Bits
o
Description
Action bit interpreted as follows:
Bit Setting
o
1
1-7
Description
recognize character
inhibit character recognition
Strip character (S2) bits (7-bit ASCII character) which must be different
from STX, ETX, ring, and terminate characters.
The S2 character is to be stripped from an incoming data stream. The character
is unconditionally removed from the input buffer. The character cannot have
been previously specified for a control function.
MPX-32 Reference Volume III
10-31
Terminal! ALlM! ACM Initialization (INIT)
Example
The following example shows a dial-in type 103 modem interface to an ALIM with
one stop bit, even parity, parity enabled, 7-bit character length, baud rate factor of
16X, and data rate of 300 baud.
2003 MODEM REMOTE INIT 00001518 7A06CCOO 01808000 80800580 80000000
00001518
time-out of 90 seconds
7A06CCOO
7
A
06
C
C
00
1 stop bit, even parity, parity enabled
7 bit character baud rate factor (16X)
300 baud rate
enable ring and break detection
switched line
must be zero
0180800D
80
80
OD
terminate on CHAR A
STX characters - no action
ETX characters- no action
CHAR A OO=earriage return
80
80
05
80
CHAR B - no action
CHAR C - no action
ring-in character is E (X'05')
strip character 1 - no action
80
strip character 2 - no action
must be zero
01
80800580
80000000
000000
10-32
System Administrator Services
Terminal/ALIM/ACM Initialization (INIT)
10.7.4 ACM/MFP Controller Record Syntax and Defaults
Syntax
ccaa [baud] [HALFIFULL] [ECHOINOECHO] [parity] [charsize] [stopbits]
[REMOTE] [NORTS] [MODEM] [GRAP] [NOTSM] [RXON] [WXON]
[RHWF] [WHWF] [RDTR] [RRTS] [INIT value] [CXR=n] [LGC=nnn]
[LGT=sss] [TMO=mmm]
ccaa
is the channel and subaddress of the device.
[baud]
is the baud rate: 19200,9600, 7200, 4800, 3600, 2400, 2000, 1800, 1200,
600, 300, 150, 134, 110, 75, or 50. If not specified, the default is 9600
baud.
[HALF I FULL]
is the half or full duplex operation. If not specified, the default is HALF.
Refer section 10.8.4.3, True Full-Duplex Operation for the ACM.
(
[ECHO I NOECHO]
specifies characters are or are not to be echoed by the computer as they
are received. If not specified, the default is ECHO for FULL duplex or
NOECHO for HALF duplex.
[parity ]
is ODD, EVEN, or NONE. If not specified, the default is EVEN. If
NONE is specified, the serial character is smaller due to the absence of
the parity bit.
[charsize] is the character size: 5, 6, 7, or 8. If not specified, the default is 7.
[stopbits]
is the number of stop bits: S 1, S 1.5, or S2. If not specified, the default is
Sl.
[REMOTE] sets dial-up bit in UDT. If not specified, the default is not set.
[NORTS] resets the ready to send signal (RTS) after device initialization. This
option allows software control of a peripheral switch controller in
configurations with a controller present.
[MODEM] sets modem bit in UDT. If not specified, the default is not set. Also sets
modem bit for ACE parameters. The default is no modem.
[GRAP]
specifies graphic device. If not specified, the default is not graphic
device.
[NOTSM] specifies a non-TSM device. If not specified, the default is TSM device.
[RXON]
specifies software read flow control (XON/XOFF). If not specified, the
default is no software read flow control. If this option is selected for a
terminal, NOECHO should be specified so the terminal can be used in
local echo mode. This avoids line contention caused by echoplex.
(:
MPX-32 Reference Volume 'III
10-33
Terminal/ ALiM/ ACM Initialization (INIT)
.("
[WXON]
specifies software write flow control (XON/XOFF). If not specified, the
default is no software write flow control.
XON - no timeout value on writes
XOFF - 75 second timeout value on writes
[RHWF]
specifies hardware read flow control (DTR). This parameter cannot be
specified if either RXON or WXON has been specified. If not specified,
the default is no hardware read flow control. If this option is selected for
a terminal, NOECHO should be specified. This avoids line contention
caused by echoplex.
[WHWF]
specifies hardware write flow control (DTR). This parameter cannot be
specified if either RXON or WXON has been specified. If not specified,
the default is no hardware write flow control. If this option is selected for
a terminal, the NOECHO parameter should be specified. This avoids line
contention caused by Echoplex.
[ROTR]
specifies the DTR line is used if RXON has been requested. This is the
default, and it overrides RRTS if both are specified.
[RRTS]
specifies the RTS line is used if RXON has been requested.
[CXR=n]
n specifies the number of seconds to wait for carrier before J.TSM resets
""j
DTR, causing the modem to go on hook. Valid values for n are 1-255.
The value specified by n must include delays introduced by the modem.
The use of this option will also cause a 2 second delay at logon time
before transmitting the logon banner.
[INIT value]
indicates the presence of hexadecimal initialization data. value is a 1word hexadecimal value in the 8-line asynch initialization format. See
ACM/MFP Initialization Format below.
[LGC=nnn]
nnn specifies the number of logon attempts, 0 to 255, allowed before the
terminal is marked offline. If nnn is 0, there is no limit on the number of
logon attempts. The default is O.
[LGT=sss] sss specifies the number of seconds, 0 to 255, that a terminal waits at a
logon prompt before being logged off. The default is O.
[TMO=mmm]
mmm specifies the number of minutes, 0 to 999, that a terminal can
remain I/O inactive.
(~)
10-34
System Administrator Services
Terminal/ALIM/ACM Initialization (INIT)
10.7.4.1
ACM/MFP Initialization Format
31
15 16
23 24
o 1 2 3 4 5 6 7 8 9 10 11 12
Zero
Word 1 D M F P P S C D C W D
Baud
Wake-up
character
u R P S E B L C W D L
rate
p
I
e
x
Bit
Description
o
Full or half duplex bit is defined as follows:
o
full duplex
1
half duplex
Modem ring (MR) bit is defined as follows:
o
disable
1
enable
Forced parity (FP) bit is defined as follows:
o
normal parity as defined
1
force parity to one if odd; force parity to zero if even
Parity selection (PS) bit is defined as follows:
o
odd parity
1
even parity
Parity enabled (PE) bit is defined as follows:
o
disable parity
1
enable parity
Stop bit (SB) defined is as follows:
o
1 stop bit
1
2 stop bits or 1.5 stop bits for 5 character length
Character length (CL) is defined as follows:
Bit 6
Bit 7
CL
o
0
5 bits
o
1
6 bits
1
0
7 bits
1
1
8 bits
1
2
3
4
5
6-7
8
ACM -
Delta carrier (DC) bit is defined as follows:
disable attention on delta carrier
1
enable attention on delta carrier
MFP-zero
o
9
ACM -
Character write (CW) bit is defined as follows:
disable wait for the end of the last character write
1
enable wait for the end of the last character write
MFP-zero
o
MPX-32 Reference Volume III
10-35
Terminall ALiMI ACM Initialization (IN IT)
10
Wake-up detection (WD) bit is defined as follows:
allow wake-up character detection
0
1
inhibit wake-up character detection
11
Diagnostic loop (DL) bit defined as follows:
reset diagnostic loop
0
1
set diagnostic loop
12-15
Baud rate bits defined as follows:
Bit
12
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
16-23
24-31
fe,
!t."J
Bit
13
0
0
0
0
1
1
1
1
0
0
0
0
1
1
1
1
Bit
14
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
Bit
15
0
1
0
1
0
1
0
1
0
1
0
I
0
1
0
1
ACM
Baud
rate
50
75
110
134.5
150
300
600
1200
1800
2000
2400
3600
4800
7200
9600
19200
MFP
Baud
rate
75
110
134.5
150
300
600
1200
2000
2400
4800
1800
9600
19200
38400
External clock is 16X
External clock is 1X
8-bit wake-up character
Must be zero
c
10-36
System Administrator Services
Terminal/ALIM/ACM Initialization (INIT)
10.7.4.2 Example
The following example shows a dial-in modem interface to an ACM S-line
asynchronous with one stop bit, even parity, parity enabled, full duplex, 7-bit
character length, and modem ring enabled.
7ECO MODEM REMOTE INIT 5A050500
5A050500
5
full duplex, enable modem ring, normal parity as defined,
even parity
A
parity enabled, one stop bit, 7-bit character
05
300 baud rate
05
ring-in character is E (X'05')
aa
must be zero
10.7.4.3 True Full-Duplex Operation for the ACM
The ACM device can be used for true full-duplex operation. The device must have
been SYSGENed using the device directive's FULL parameter. This creates two
UDT's per full-duplex subchannel: one for the read sub-channel and one for the write
subchannel. The write subchannel subaddress is the read subchannel address plus
X'S'; for example, a subchannel address of 7EOO derives a write subchannel address
of 7EOS. The device must be initialized as NOECHO (local echoplex) to avoid I/O
contention with the write subchannel. After the device is initialized, it is in fullduplex, single-channel mode; all read and write I/O is performed through the read
subchannel.
To set the device to full-duplex, dual-channel mode, the TSM OPTION UNQUIET
directive must be used. Dual-channell/O reads are performed on the read subchannel;
writes are performed on the write subchannel. Dual-channel mode is also entered by
assigning the read and write subchannels separately, as if OPTION UNQUIET were in
effect, and issuing an M.RELP (SVC l,X'27') before any I/O is performed. I/O is
then performed through the FCB associated with the appropriate subchannel. To reset
to the single-channel mode, use the M.RESP (SVC 1,X'26') service.
MPX·32 Reference Volume III
10-37
Terminal/ ALiM/ ACM Initialization (INIT)
o
10.7.5 Sample LOGONFLE
05
*LGC=3
*LGT=60
*TMO=60
7EAO
7EA1
7EA7
2000
19200 FULL
9600 FULL NONE 8 S1 WXON REMO NOTSM
HALF MODEM REMOTE EVEN 300
9600 FULL EVEN 7
WAKEUP CHARACTER WRITE
SYSTEM-WIDE MAX LOGON
ATTEMPT OF 3
SYSTEM-WIDE MAX LOGON TIMER
OF 60 SECONDS
SYSTEM-WIDE MAX TERMINAL
TIMER OF 60 MINUTES
DEFAULTS FOR OTHER VALUES
SAMPLE SERIAL PRINTER
DIAL-UP LINE
ALIM
REMOTE
sets dial-up bit in UDT. The default is not set.
MODEM
sets modem bit in UDT. The default is not set. Also
sets modem bit for ACE parameters. The default is no modem.
EVEN
even parity is used.
7
7 bit data is used.
FULL
full duplex operation.
NOT8M
specifies a non-TSM device. The default is TSM device.
HALF
half duplex operation.
8
8 bit data is used.
81
specifies 1 stop bit is required.
WXON
device uses software write flow control (XON/XOFF).
LGC=3
specifies a system-wide default logon count of 3
LGT=60
specifies a system-wide default logon timer of 60 seconds
TMO=60
specifies a system-wide default terminal timer of 60 minutes
The following table shows the ACM configurations possible and their resulting
operations.
SYSGEN Device
Directive, FULL
Option Specified
yes
ye~
yes
yes
no
no
no
no
10-38
LOGONFLE
Option Specified
LOGONFLE
ECHO/NOECHO
Option Specified
Resulting
Tenninal
Operation
full
full
half
half
full
full
half
half
echo
noecho
echo
noecho
echo
noecho
echo
noecho
half,echo
full,noecho
half,echo
half,echo
half,echo
half,noecho
half,echo
half,noecho
FULL/HALF
System Administrator Services
0
Terminal/ ALiM/ ACM Initialization (INIT)
(
10.8 Using INIT
INIT is a TSM command. LOGONFLE is assigned for input by default.
Syntax
TSM>$INIT [ccaa]
[ccaa]
specifies the appropriate channel and subaddress (hexadecimal) of a
specific device to be reinitialized. The record from LOGONFLE that
matches the channel and subaddress reinitializes the device.
If no device is specified, INIT uses the current version of LOGONFLE to reinitialize
all devices that are currently free to allocate.
10.9 INIT Errors
INIT generates the following error messages:
ATTEMPT TO MAKE TSM DEVICE A NON TSM DEVICE, ADDR=ccaa
The NOTSM keyword is specified in LOGONFLE for a TSM device.
DEVICE NOT PRESENT ADDR=ccaa
The specified device is not plugged into the CPU.
DEVICE NOT TERMINATED ADDR=ccaa
The specified device is not plugged in on device end of line.
INVALID LOGON COUNTER SUPPLIED.
DEFAULT IS O.
When setting up the defaults, an invalid character was entered for nnn in
LGC=nnn. The default becomes O.
INVALID LOGON COUNTER SUPPLIED.
DEFAULT USED.
When using a terminal-specific counter, an invalid character was entered for nnn
in LGC=nnn. The system default is used.
INVALID LOGON TIMEOUT VALUE SUPPLIED.
DEFAULT IS O.
When setting up the defaults, an invalid character was entered for sss in
LGT=sss. The default becomes O.
INVALID LOGON TIMEOUT VALUE SUPPLIED.
DEFAULT USED.
When setting up a terminal specific timeout value, an invalid character was
entered for sss in LGT=sss. The default becomes O.
MPX-32 Reference Volume '"
10-39
INIT Errors
INVALID NON TSM DEVICE TYPE CODE, ADDR=ccaa
Valid non-TSM device type codes are X'07' (CD) through X'OB' (PT) and
X'OD' (CT) through X' lA' (U9).
INVALID TERMINAL TIMEOUT VALUE SUPPLIED.
DEFAULT IS O.
When setting up the defaults, an invalid character was entered for mmm in
TMO=mmm. The default becomes O.
INVALID TERMINAL TIMEOUT VALUE SUPPLIED.
DEFAULT USED.
When setting up a terminal specific timeout value, an invalid character was
entered for mmm in TMO=mmm. The default becomes o.
M.ASSN DENIAL,NO LOGON FILE DEFAULT USED
A file named LOGONFLE is not on the system. Default parameters have been
set. Non-TSM devices are not initialized.
M.ASSN DENIAL,ADDR=ccaa
The device at the specified channel and subaddress is in use and cannot be
initialized.
NO UDT ENTRY FOR ADDR=ccaa
The specified device is not SYSGENed.
NON TSM DEVICE WITHOUT NOTSM IN LOGONFLE, ADDR=ccaa
A non-TSM device is specified in LOGONFLE without the NOTSM keyword.
ON ADDRESS ccaa, FIELD UNIDENTIFIED: xxxxxxxx
The string xxxxxxx;\" is not a valid keyword for a characteristic.
TERMINAL SET-UP COMPLETE
Initialization complete.
WARNING, LOGON COUNTER VALUE TOO LARGE. CAPPED TO 255 ATTEMPTS
The value nnn in LGC=nnn was larger than 255.
WARNING, LOGON TIME VALUE TOO LARGE. CAPPED TO 255 SECONDS.
The value sss in LGT=sss was larger than 255.
WARNING, TERMINAL TIMEOUT VALUE TOO LARGE. CAPPED TO 999 MINUTES.
The value mmm in TMO=mmm was larger than 999.
c
10-40
System Administrator Services
System Console Messages
10.10 System Console Messages
Some system messages and operations pertain to the system console, and not to
terminals running OPCOM, for example:
• mount and dismount messages for magnetic tape
• abort messages and codes for tasks running in the real-time environment
• I/O error conditions that can either be corrected offline with I/O resumed or aborted
Displaying these messages on the console assumes a central location of configured
system hardware, including the system console, the CPU, printers, and tape units.
User tasks can also send messages to the system console.
10.10.1 Information Messages
Commands or responses to prompts at the system console always take precedence
over messages sent to the console. The maximum output string that cannot be
interrupted for a message is 72 characters.
10.10.2 Action Messages
If a system message requires operator intervention and reply, the condition noted must
be addressed. The operator enters a reply and terminates it with a carriage return. For
example,
*CR7800 INOP : R,A? R
A card reader is not operating. The operator fixes it and responds R and a carriage
return to resume. Input continues.
10.10.3 Terminal Messages
The terminal user receives only the OPCOM messages that pertain to directives issued
from that terminal.
MPX-32 Reference Volume III
10-41
Floppy Disk Media Initialization (J.FORMF)
10.11
Floppy Disk Media Initialization (J.FORMF)
All lOP floppy disks must be properly formatted before they can be used on the
operating system.
To format a floppy disk, type J.FORMF at the TSM prompt. The following message
is displayed:
J.FORMF-SPECIFY FORMAT:MODEO!MODEl!QUIT (REPLY 0, 1, OR Q) :
If 0 (MODEO) is entered, the floppy disk is formatted as double density, 256 bytes
per sector. The first physical sector of all tracks starts at hexadecimal 0 and ends at
hexadecimal 19.
If 1 (MODEl) is entered, the floppy disk is formatted as double density, 256 bytes
per sector. The first physical sector of all tracks starts at hexadecimal 1 and ends at
hexadecimal lAo MODEl formatting allows data files to be transported to other
computer systems that expect the physical sectors to begin at hexadecimal 1 and end
at hexadecimal lA. MODEl is only supported on systems containing a Model 8031
Line Printer/Floppy Disk Controller.
If Q (QUIT) is entered, control returns to TSM and the floppy disk is not formatted.
The default mode selection should be MODEO and must be MODEO if data files are
to be transported to another Encore computer containing either a Model 8030 or 8031
Line Printer/Floppy Disk Controller.
The default device for J.FORMF is device address FL7EFO. To override the default,
specify the following assign directive at the TSM prompt before J.FORMF is
activated:
$ASSIGN FL TO
xxxx
10-42
DEV=FLx~u
BLO=N
is the drive device address to be used by J.FORMF.
System Administrator Services
M.MOUNT File
(".
10.12 M.MOUNT File
The M.MOUNT file automatically mounts volumes at IPL. It can be used to mount
both public and nonpublic volumes. (A nonpublic volume requires a logical mount by
subsequent users to access the resources on that volume). Use of the nonpublic mount
should be determined by the specific needs of the system applications.
The M.MOUNT file directive syntax is the same as the OPCOM MOUNT directive.
Refer to the OPCOM section in the MPX-32 Reference Manual, Volume II. The file
must be stored unnumbered on the SYSTEM volume.
Examples
EDT>COL
1.
2.
MOUNT ATLAS04 ON DM0804 OPTION=PUBL
MOUNT TB02 ON DM0802 OPTION=PUBL
5.
EDT>STO M.MOUNT SYS UNN
If desired, an asterisk (*) can be used in the volume name field. This causes the
volume on the specified drive to be mounted, regardless of its name.
At system initialization, a mount message is displayed for each volume in the file. If
an ABORT (A) is entered to any message, an attempt is made to MOUNT any
remaining volumes.
MPX-32 Reference Volume III
10-43
Operator Intervention Inhibit
10.13 Operator Intervention Inhibit
When operator inteIVention is inhibited, all prompts normally displayed on the system
console are suppressed and the following defaults are in effect:
Prompt
system date/time
swap volume channel and subaddress
mount messages - formatted volumes
dual-port volume cleanup confirmation*
wait I/O request retry
invalid port ID specification*
dual-port volume mount request verification
for an allocated port*
Default
more recent date/time recorded by
J.DTSAVE or last system volume mount
system volume
ready
no
abort (DPO)
port zero
continue
The prompts marked by an asterisk (*) apply only when a dual-processor shared
volume is mounted. If the default responses to these prompts are not the desired
responses, unreliable file system management can result.
After system initialization, wait I/O request retry prompts remain inhibited. When a
wait I/O retry is requested, a message is displayed on the system console specifying
the inoperable device and the request is aborted.
Mount messages are not inhibited after system initialization. The SYSGEN or
OPCOM MODE directive inhibits mount messages after system initialization. If
mount messages are inhibited and a device is not ready when J.MOUNT issues a
mount request, the request is repeated approximately 60 seconds later. If the device is
still not ready after the second request, the mount request is aborted.
When operator inteIVention is inhibited and an attempt is made to boot a master
system image, operator inteIVention inhibit is overridden and an operator must
respond to the prompts.
10.14 System Date/Time Backup Program (J.DTSAVE)
The System Date/Time Backup Program (J.DTSAVE) is a privileged, nonresident
system program. J.DTSA VE records the current date and time to the system volume
at regular intervals. The intervals are established by the SYSGEN directive DTSAVE.
If operator intervention is inhibited, the system date and time are initialized to either
the last date and time recorded by J.DTSAVE or the date and time of the last system
volume mount, whichever is more recent. Entering a chronologically accurate date
increases the reliability of file system management. J.DTSA VE is activated by the
SYSGEN and OPCOM ACnVATE directives.
c··."\
:
10-44
System Administrator Services
")
System Shutdown
10.15 System Shutdown
MPX-32 offers a system shutdown capability to increase reboot performance. The
system administrator can request the following types of shutdown:
Shutdown type
Description
immediate forced
System shuts down immediately, without
waiting for user and task activity to
end.
timed forced
System waits a specified time for user
and task activity to end, then shuts
down when this activity ends or time
expires.
indefinite
System waits indefinitely for all user
and task activity to end before it
shuts down.
Shutdown ends with a system halt or, if requested, with an online restart. This restart
can be to the default system image or to a specified image.
The system administrator requests a shutdown by using either the J.SHUTD task or a
shutdown macro. These differ as follows:
• J.SHUTD task performs a shutdown without notifying users that a shutdown is in
progress. This task deallocates system resources, requests volume dismounts. and
halts or restarts the system.
• A shutdown macro provides an interface to users and application tasks during
shutdown. It informs users when a shutdown is in progress, ends application tasks
specified in the macro, and calls J .SHUTD to perform the shutdown. A sample
macro. SHUTDOWN, is included on the Master SDT and can be customized for
any system.
Note:
To shutdown a system with active users, we recommend using a shutdown
macro. Use the J.SHUTD task only when the system has no active users.
10.15.1 Using J.SHUTD
For a timed or indefinite shutdown, J.SHUTD requests the dismount of all volumes
and sends a message to tasks holding resources on the system volume. When all
system volume resources are deallocated. J .SHUTD marks the volume as quiescent
and physically dismounts it if the current image is the default. Other volumes are
physically dismounted as their resources are deallocated. When the dismounts
complete and the system volume is quiescent, or when time expires, J.SHUTD halts
the system. If a restart is requested, J.SHUTD restarts to the default or specified
image.
C,
For an immediate forced shutdown, J .SHUTD halts the system instantly, without
waiting for volume dismounts or for the system volume to be quiescent. If requested,
J.SHUTD restarts the system.
-
MPX-32 Reference Volume III
10-45
System Shutdown
Syntax
J.SHUTD [[TIME=]ss] [RESTART [image]]
[TIME=]ss specifes the number of seconds for J.SHUID to wait for system activity
to end before forcing a shutdown. Specify 0 to shutdown immediately.
Omit the option to initiate an indefinite shutdown.
RESTART requests an online restart following shutdown. If this option is omitted,
shutdown ends in a system halt.
image
is the file name of the system image to restart. When an image is
specified, MPX-32 cleans up the system volume. If omitted, the default
image is used.
Mter J.SHUID is called, system shutdown cannot be canceled.
10.15.2 Shutdown and Volume Cleanup
MPX-32 cleans up the system volume after shutdown in the following cases:
•
•
•
•
shutdown is forced before the system volume dismounts
the image requested for restart is not the current image
the current image before shutdown is not the default image
a different image is made the default image without restarting
10.15.3 SHUTDOWN Macro
The shutdown macro, SHUIDOWN, notifies users of a pending shutdown and
initiates this shutdown by calling J.SHUID. This macro can be modified to set how
often it sends a message to users, which tasks it deallocates or removes before
shutdown, and what value it passes to the J.SHUID TIME option. The macro can
pass up to four parameters to J.SHUID. These parameters must correspond to the
J.SHUID syntax or an error results.
Shutdown can be canceled while the macro is running by using a $REMOVE
command to remove the job.
10.15.4 Using SHUTDOWN
The SHUIDOWN macro can be run either in batch or interactive mode. To avoid
tying up a terminal during shutdown, we recommend you batch the macro or set the
terminal page size to zero ($PAGESIZE 0) before running the macro interactively.
10-46
System Administrator Services
System Shutdown
Syntax
BATCH SHUTDOWN [[TIME=] ss] [RESTART[=image]]
[TIME=]ss specifies the number of seconds before forcing a shutdown. Specify 0 for
an immediate forced shutdown. Omit a value to initiate an indefinite
shutdown. The macro uses ss in calculating when to call 1.SHUTD.
RESTART requests a restart following shutdown. The macro passes this parameter to
1.SHUTD.
image
specifies the filename of the system image to restart. The macro passes
this parameter to 1.SHUTD.
To run the macro interactively, omit the BATCH keyword from the syntax above.
The macro can also be batched from a program through the TSM procedure call
service (M.TSMPC/M_TSMPC). Refer to the MPX-32 Reference Manual, Volume I,
Chapter 6 or 7 for information on the M.TSMPC or M_TSMPC service.
10.15.5 Modifying the SHUTDOWN Macro
To control the time between signals to users, the macro uses the PAUSE task. Each
call to the task has the following syntax:
PAUSE n
n is the number of seconds the task pauses until the next signal to users.
Each call to PAUSE specifies a value (n) for the number of seconds to pause. The
macro uses smaller n values as the time remaining to shutdown decreases. These n
values can be modified throughout the macro to increase or decrease the pause
between signals.
To determine when to call 1.SHUTD to perform the shutdown, the macro uses the
ACTIME constant. This constant is the number of seconds (less than 60) that the
macro passes to the TIME option of 1.SHUTD. The macro runs for ss minus ACTIME
seconds before calling 1.SHUTD. When the macro is batched with ss less than or
equal to 60, it resets ACTIME to ss. This ACTIME constant can be modified to
increase or decrease the value passed to the 1.SHUTD TIME option.
The macro signals users based on ACTIME and the macro's TIME=ss option as
follows:
• If ss is omitted, the macro informs users that an indefinite shutdown is in progress.
It calls J.SHUTD to handle the shutdown and the macro ends.
• If ss is 0, the macro informs users that the system is shutting down immediately. It
calls 1.SHUTD to halt the system and the macro ends.
C-·,
• If ss is 60 seconds or less, the macro informs users that the system is shutting down
in less than 1 minute. It calls 1.SHUTD and passes ss to the J.SHUTD TIME
option.
/
MPX-32 Reference Volume III
10-47
System Shutdown
• If ss is less than 1 hour and greater than 1 minute, the following table applies:
Minutes until shutdown
1-3
4-5
6-20
21-60
c
Macro signals every
1 minute
3 minutes
5 minutes
15 minutes
When 1 minute remains, the macro sends a final message and pauses for 60 seconds
minus ACflME, then calls J.SHUTD.
• If ss is greater than 1 hour and less than 2 hours, the macro informs users that the
system is shutting down in the given time and it pauses for ss minus 1 hour. It then
sends another message informing users of the time remaining to shutdown. When 1
hour remains, the table above applies.
• If ss is greater than or equal to 2 hours, the macro informs users that the system is
shutting down in the given time and it pauses for 1 hour plus the number of
minutes and seconds in the given time. For example, if TIME=7300 seconds (2
hours, 1 minute, 40 seconds), the macro pauses for 1 hour, 1 minute, 40 seconds
before sending another message. The macro then sends a message every hour until
1 hour remains and the table above applies.
10.15.6 Error Messages
The following messages are written to LFC ERR:
J.SHUTD: SYSTEM ADMINISTRATOR ATTRIBUTE IS REQUIRED
J.SHUTD: IMAGE NAME MUST BE a TO 8 CHARACTERS
J.SHUTD: TOO MANY ARGUMENTS OR INVALID ARGUMENT SUPPLIED
The following messages are written to the console only:
J.SHUTD: DISMOUNT REQUEST TO VOLUME name RETURNED WITH RMnn
name
nn
Note:
is the name of the volume that J.SHUTD requested to dismount
is a REMM abort code. Refer to Appendix C for a list of these abort
codes or use the TSM $ERR directive.
J.SHUTD returns an RM14 error indicating that dismount is
pending if the volume still has resources allocated.
J.SHUTD: RUN REQUEST TO RESTART RETURNED FROM M.SRUNR
WITH STATUS VALUE mm
mm
is a status value returned from the call to M.SRUNR. Refer to the
M.SRUNR system service in Chapter 6 of MPX-32 Reference Volume
I for a list of these status values and their meaning.
If a restart or request for restart fails, halt and reboot the system.
10-48
System Administrator Services
o
System Shutdown
The SHUTDOWN macro sends the following messages to owner SYSTEM:
SHUTDOWN: INVALID ARGUMENT SPECIFIED. JOB TERMINATED.
SHUTDOWN: TIME ARGUMENT IS INVALID. JOB TERMINATED.
SHUTDOWN: IMAGE NAME GIVEN IS INVALID. JOB TERMINATED.
Note:
If the SHUTDOWN macro parameters are entered incorrectly, TSM
issues an INVALID PARAMETER TYPE message.
10.16 Swap Scheduler Control Options
The swap scheduler processes entries in the memory request queue (MRQ). It
provides memory allocation and swap scheduling for individual memory requests. So
that the swap scheduler can function according to the requirements of a system, the
following swap scheduler options can be set by the system administrator:
1.
2.
3.
4.
5.
6.
(
7.
8.
Swapper algorithms
Wait state ordering
Wait state swap-on priority only
Call back swap-on priority only
User set swap-on priority only flag
User set swap inhibit flag
Swap thrash control
Task group outswap limits
To set or reset an option, edit the Swap Option File (SJ.SWAPR2). SJ.SWAPR2
contains instructions on how to edit the file. After the file is edited, it must be
resaved as SJ.SWAPR2. Then, the JCL file, JJ.A.SWP, must be run to catalog the
swapper load module (J.SWAPR). After J.SWAPR is cataloged, the system
administrator must restart the system to incorporate the modified swap scheduler into
the operating system.
If SJ.SWAPR2 is not modified, the swap scheduler options are defaulted so that
J.SWAPR performs similar to MPX-32 Revision 3.2C. To revert to swapping that is
similar to MPX-32 Revision 3.2C after the swap option file has been edited, re-edit
the SJ.SWAPR2 file and set all options to their default settings.
Swap-on priority only (SOPO) means that a task will be outswapped only when
memory is required for an equal or higher priority task, regardless of the task's state.
If swap-on priority only is not in effect, a higher priority task in any wait state can be
outswapped for a lower priority task that is ready to run. If the outswapped higher
priority task changes to a ready-to-run state too soon, the task is inswapped again
causing delays and reducing system performance.
MPX-32 Reference Volume III
10-49
Swap Scheduler Control Options
,{".
D~VINITL DEVICE=CR2008 ID='CARD READER FIRMWARE'DEV> REREAD=O RETRY=lDEV> DEV CNTRL
11-12
Device Initializer/Loader (DEVINITL)
o
Milestone Messages
11.7 Milestone Messages
The following message is displayed when a device is successfully initialized.
DEVICE XXXXXX INITIALIZED
The following message is displayed when firmware is successfully loaded onto a
device.
DEVICE XXXLU HAS BEEN LOADED WITH THE FIRMWARE
CONTAINED IN WCS FILE xxxxxxxx
11.8 Error Conditions and Messages
11.8.1
Initialization Directive File Errors
The following message is displayed when DEVINITL is activated by TSM and a
corresponding device entry is not found in the initialization command file.
NO DEFAULT DATA IS AVAILABLE FOR DEVICE xxxxxx
The following message is displayed when action is not taken on a device entry within
the initialization directive file.
**
WARNING
**
NO ACTION HAS BEEN CARRIED OUT FOR DEVICE xxxxxx
Action is not taken because one of the following occurred:
• option 9 is set
• a DEV_CNTRL command is not specified for the device entry
• a WCS_FILE directive is not specified for the device entry
The following message is displayed when the initialization directive file does not
contain sufficient directives for processing a device before end-of-file detection.
** ERROR ** A PREMATURE END-OF-FILE HAS BEEN DETECTED ON THE
CONTROL FILE
The following message is displayed when a nondecirnal number is specified with a
REREAD directive.
**
ERROR
**
INVALID REREAD PARAMETER SPECIFIEDxxxxrxa
The following message is displayed when a nondecirnal number is specified with a
RETRY directive.
**
ERROR
**
MPX·32 Reference Volume III
INVALID RETRY PARAMETER SPECIFIED xxu:xxxx
11-13
Error Conditions and Messages
11.8.2 Device Loading Errors
When a device cannot be successfully loaded, the following message is displayed
along with the appropriate reason.
** ERROR ** UNABLE TO LOAD DEVICE xuxxx FOR THE FOLLOWING REASON:
DEVICE CHANNEL MUST BE HEXADECIMAL.
FOUND xx
DEVICE TYPE NOT CONFIGURED ON HOST SYSTEM.
UNABLE TO ALLOCATE DEVICE xxxox M.ASSN ERROR CODE:xx
UNABLE TO ALLOCATE FILE xxxuxu M.ASSN ERROR CODE: xx
WCS FILE xxxxuxx IS INVALID - CONTAINS NO TERMINATION RECORD.
WCS FILE xxx~ IS INVALID - CONTAINS AN ERRONEOUS BYTE COUNT.
OFFENDING RECORD BYTE COUNT: xx
FIRMWARE ADDRESS: X~U
WCS FILE XXYXUXY IS TOO LARGE FOR DEVINITL.
OFFENDING RECORD BYTE COUNT: xx
FIRMWARE ADDRESS: xxxx
Including microcode and data, maximum file size is 64K.
WCS FILE XXYXU.U CONTAINS INVALID COMMAND: HEX xx
HARDWARE ERROR STATUS RECEIVED.
STATUS AFTER LAST RETRY:
HEX xxxx
UNABLE TO OPEN DEVICE xxxux DEVICE MAY NOT BE PRESENT
11.8.3 Directive Parsing Errors
The following message is displayed when an invalid pathname is specified with the
WCS_FILE directive. The string xxxuxu contains up to 80 characters.
** ERROR ** PATHNAME SYNTAX ERROR: x..uxxxxx
The following message is displayed when OPTION WCSMATCH=Y and an IDENT
directive have been specified, but a match is not found in the header record of the file
being searched.
**
WARNING ** INCORRECT FIRMWARE REVISION FOR DEVICExyxux
REQUESTED .U.u:X.uxnxux..u
ACTUAL .~uxuxx:xxxxxxxx
The following message is displayed when the execute channel program call fails after
the specified number of RETRY and REREAD attempts. The number output as the
reason is the contents of the third word of the FCB.
DEVICE .uuxx INITIALIZATION FAILED.
REASON x.UYXXXX
The following message is displayed when a non-hexadecimal digit is found during
lOCO creation at initialization time. The initialization line is ignored.
**
ERROR
**
INVALID HEXADECIMAL CHARACTER: x
c
11-14
Device Initializer/Loader (DEVINITL)
Error Conditions and Messages
The following message is displayed when the two least significant bits of the IOCD
operation code directive specified with DEV_ CNTRL CMD=x.x are not set.
**
ERROR **xx IS INVALID IOCL COMMAND
When a parse error occurs for a reason other than those described above, the following
message is displayed along with the appropriate reason. Below this, the erroneous line
is displayed with an exclamation point (!) below the item that caused the parse error.
**
PARSE ERROR
**
AN EQUAL SIGN IS MISSING FOLLOWING A KEYWORD
PREMATURE END OF INPUT STRING
A directive is truncated.
DEVICE IDENTIFICATION IS MISSING
UNRECOGNIZABLE DIRECTIVE
A STRING IS MISSING FOLLOWING AN EQUAL SIGN
A QUOTED STRING IS IMPROPERLY TERMINATED
An end quote is missing or attempt was made to carry a string past one
input line.
(
AN ASSUMED OPTION LINE CONTAINS NO OPTION DIRECTIVES
Parameter WCSMATCH and/or MILESTONE must be specified with an
OPTION command.
A PREMATURE END-OF-STRING OCCURRED IN OPTION
SPECIFICATION
An OPTION directive cannot be carried past one input line.
THE SPECIFIED OPTION IS UNDEFINED
RETRY/REREAD IS NOT A POSITIVE DECIMAL
INVALID OPTION SENSE SPECIFIED OPTIONS=Y,N,T,F, OR
BLANK
(MPX-32 Reference Volume III
11-15/11-16
(
12
12.1
Alterable Control Store (ACS)
Introduction
The Alterable Control Store (ACS) Load and Display Utility performs two functions
- LOADACS and DUMP ACS. LOADACS writes firmware to the ACS or Writable
Control Store (WCS). DUMPACS displays or compares firmware in Programmable
Read Only Memory (PROM), ACS, and WCS. Through the SETCPU instruction,
MPX-32 specifies whether the processor uses the PROM or ACS firmware.
With the exception of the CHECKSUM directive, the ACS Utility runs only on a
CONCEPT 32/67 computer. The CHECKSUM directive can be used on any
CONCEPT/32.
The numbers accepted and generated by LOADACS and DUMPACS are hexadecimal,
except for decimal RMxx error codes.
12.2 LOADACS Directive File (M.ACS)
The LOADACS directives are in a file named M.ACS. M.ACS must be located on
the system volume and the system directory. Use the Text Editor to create the file.
(
M.ACS consists of one or more groups of directives, each group for a particular
processor. There can be more than one group of directives for any processor. The
last directive in each group must be followed by a semicolon. Following is the format
ofM.ACS.
Group 1
COPY, LOAD, or PATCH Directive
VERIFY Directive (optional)
ENABLE Directive (optional)
Group n
COPY, LOAD, or PATCH Directive
VERIFY Directive (optional)
ENABLE Directive (optional)
MPX-32 Reference Volume III
12·1
Firmware File
12.3 Firmware File
The firmware file supplied must be restored as a system file using the Volume
Manager.
The firmware file contains logical blocks of 256 bytes. The last byte of each logical
block is the one's complement of the sum of all other bytes in the logical block.
LOADACS uses this figure as a checksum during a LOAD.
If assigned, the firmware file must be assigned as unblocked.
12.3.1
CONCEPT 32/67 Usage
The CONCEPT 32/67 has two phases of processors, phase 1 and phase 2. The user
must know which phase their system has so the M.ACS file can be properly
constructed.
A properly constructed M.ACS directive loads or patches the proper firmware without
user intervention regardless of the processor's phase. This maintains system
portability from one phase processor to another.
The processor's phase is determined by the processor (CPU or lPU) PROM revision
level. See the REVISION directive. If the last 8 digits of the revision number are
2282000n, where n is any number, the processor is a phase 1.
Any other numbers indicate a phase 2 processor.
12.3.2 Firmware File Record
The maximum record length is one logical block; therefore, the maximum record size
is 251 bytes. The maximum number of 64-bit microwords per record is 31. The
format of a record is:
o
7
Microword Count (Byte 0). See
Note 1.
8
23
Start Address
(Bytes 1 & 2).
See Note 2.
24
n
Data (Bytes
3-250). See Note 3.
Notes:
1.
Byte 0 of a record contains the microword count for the record. A count of 00
means the record is the last in a logical block.
If the last record of a logical block ends in the last 3 bytes of the block, a new
record is not started with a 00 microword count.
An FF microword count indicates an end-of-file.
12-2
Alterable Control Store (ACS)
Firmware File
2.
3.
Bytes 1 and 2 of a record contain the starting address of the record's data. Valid
address ranges are:
0000 to OFFF for ACS or PROM
1000 to 1FFF for 4K x 64 WCS
1000 to 2FFF for 8K x 64 WCS
Bytes 3-250 of a record contain the data to be loaded.
Microword FFD always contains the ACS or PROM firmware revision. The revision's
format is:
C67 rnzzppppppzzzn
C = CONCEPT/32
67 = 2-digit type of CONCEPT/32
r = firmware revision letter
n = firm ware revision number
z=O
p
= 6-digit firmware part number
C67rn, with the variables filled, is the firmware source filename.
The following is an example of an ACS/pROM firmware revision.
C67A300322820003
(~
The example's firmware source filename is C67A3. The firmware part number is
322820.
Microword FFE always contains the ACS or PROM data checksum. The checksum is
the one's complement of the sum of the microwords. It is calculated by LOADACS
during writes to ACS.
c
MPX-32 Reference Volume III
12-3
LOADACS
12.4 LOADACS
LOADACS is a subroutine in J.lNITthat is executed during IPL and RESTART
sequences. LOADACS receives commands from the M.ACS command file. If any of
the following conditions are true, the firmware is not loaded and the load, patch, or
copy message is not displayed:
•
•
•
•
•
control switch 9 is set
the machine is not a CONCEPT 32/67
the sequence is not an IPL or RESTART
M.ACS does not exist
M.ACS is empty
LOADACS accepts different firmware and actions for the CPU and IPU. If the IPU is
offline, a load request causes an error message to be displayed.
LOADACS runs in the processor it is loading. Before loading ACS or WCS,
LOADACS executes the SETCPU instruction to enable transfer in the PROM mode.
LOADACS blocks external interrupts in the CPU before loading, and unblocks them
afterward. In the IPU, LOADACS inhibits context switching.
To load new firmware in ACS or WCS, use the LOAD directive. To load PROM
firmware with modifications, use the COPY directive followed by a LOAD or PATCH
directive. To modify ACS or WCS, use a LOAD or PATCH directive. PROM
cannot be loaded or modified.
All LOADACS output is displayed on the operator console and the LOD device. A
message is displayed after a successful load.
()
12·4
Alterable Control Store (ACS)
DUMPACS
(
12.5 DUMPACS
DUMPACS is a subroutine in J.INIT. When J.INIT is called from TSM and option 1
is set, DUMPACS is the only subroutine called. DUMPACS then displays a DMP
prompt for directives.
TSM> OPTION 1
TSM> J.INIT
DMP>
Depending on the directive, the results are written to logical file code UT or the LOD
device. These logical file codes cannot be reassigned.
DUMPACS dumps the contents of ACS, WCS, and PROM, compare the contents of
these storage areas with a firmware file, and calculate checksums to be used by the
LOADACS PATCH directive. DUMP ACS also displays the revision microword and
the mode of a processor.
12.6 ACS Directives
ACS directives are summarized below, arranged by function type. Each directive is
described in detail in the remainder of this section, arranged alphabetically by
directive name.
(
LOADACS Directives
Directive
Description
COPY
ENABLE
copies contents of PROM to ACS
sets processor in ACS or PROM mode. This directive is
not valid for WCS.
loads firmware file into ACS or WCS
loads data from M.ACS to ACS or WCS
compares ACS or WCS with the data that was
written to ACS or WCS
LOAD
PATCH
VERIFY
DUMPACS Directives
Directive
Description
CHECKSUM
COMPARE
DUMP
EXIT
MODE
REVISION
provides the checksum used by the PATCH directive
compares ACS, WCS, or PROM with a firmware file
dumps specified memory contents to the LOD device
exits DUMP ACS and returns to TSM
displays the mode of a processor
displays revision micro word on LFC UT
MPX-32 Reference Volume III
12-5
ACS Directives
ff··········
\.j
12.6.1 CHECKSUM Directive
The CHECKSUM directive is used by DUMPACS to add values and compute the
one's complement of the sum. The sum is then displayed on LFC UT.
When using LOADACS, the sum is the value entered in the optional SUM parameter
for the PATCH directive.
The CHECKSUM directive can be continued across more than one input line by
placing a hyphen (-) as the last significant character on the line to be continued. The
hyphen must not be embedded in a value.
Syntax
CHECKSUM value [, value ... ]
value
is a value to be patched by LOADACS
Examples
The following example adds three values and computes the one's complement of the
sum. The resulting value can be in the PATCH directive for the SUM parameter.
CHECKSUM 2433F55EC0024, 99FA5500, BB4302
12.6.2 COMPARE Directive
The COMPARE directive is used by DUMPACS to compare the contents of the
specified ACS, WCS, or PROM with a firmware file. When the firmware file and
memory do not match, the memory location's address and contents plus the file's
contents are written to the LOD device. The firmware file must be formatted as
described in section 12.3.2, Firmware File Record, of this chapter.
Syntax
COMPARE {CPU IIPU} {ACS I PROM I WCS} pathname
12-6
CPU
specifies the CPU is the processor that is used
IPU
specifies the IPU is the processor that is used
ACS
specifies the ACS is read
PROM
specifies the PROM is read
WCS
specifies the WCS is read
pathname
is the pathname of the firmware file. If the file does not exist, an error
message is displayed.
Alterable Control Store (ACS)
ACS Directives
Examples
The following example compares the contents of the CPU's ACS to the system file
named FIRM.
COMPARE CPU ACS @SYSTEM(SYSTEM)FIRM
The following example compares the contents of the IPU's wcs to the user file
named FIRM.
COMPARE IPU WCS FIRM
12.6.3 COpy Directive
The COPY directive is used by LOADACS to copy the contents of PROM to the
CPU or IPU ACS.
Syntax
COpy {CPU IIPU }
CPU
specifies the CPU ACS is written
IPU
specifies the IPU ACS is written
( '"
MPX-32 Reference Volume III
12-7
ACS Directives
12.6.4 DUMP Directive
The DUMP directive is used by DUMPACS to write the specified memory contents to
the LOD device. If starting and ending addresses are not specified, the entire contents
of the specified memory are written.
If an invalid address is specified, an error message is displayed on the terminal.
Syntax
DUMP {CPU IIPU} {ACS I PROM I WCS} [startaddr] [, endaddr]
CPU
specifies the CPU is the processor that is used
IPU
specifies the IPU is the processor that is used
ACS
specifies the ACS is read
PROM
specifies the PROM is read
WCS
specifies the WCS is read
startaddr
is the starting address of the dump
endaddr
is the ending address of the dump
Examples
The following example writes the entire contents of the CPU's ACS to the LOD
device.
DUMP CPU ACS
12.6.5 ENABLE Directive
The ENABLE directive is used by LOADACS to set the processor which was just
used for a COPY, LOAD, or PATCH, in the ACS or PROM mode. This directive is
not valid for the WCS mode.
If the ACS mode is requested and a previous LOAD, COPY, PATCH, or VERIFY
directive failed in ACS, the mode is not changed and an error message is written.
If the ENABLE operation is successful, the mode of the processor is reported to the
console and the LOD device. When an ENABLE of IPU ACS causes the IPU to be
marked offline due to incompatible firmware. the message IPU MARKED OFFLINE
is displayed instead of the mode.
Syntax
ENABLE (ACS I PROM}
12-8
ACS
specifies the processor uses the ACS firmware
PROM
specifies the processor uses the PROM firmware
Alterable Control Store (ACS)
ACS Directives
12.6.6 EXIT Directive
The EXIT directive exits DUMP ACS and returns control to TSM.
Syntax
EXIT
12.6.7 LOAD Directive
The LOAD directive is used by LOADACS to load a firmware file into ACS or WCS.
If an ACS load is not successful, the processor used remains in the PROM mode.
The LOAD directive can be continued across more than one line by placing a hyphen
(-) as the last significant character on the line to be continued. The hyphen must not
be embedded in a value and must directly precede the ACSMATCH or WCSMATCH
keyword.
Syntax
LOAD {CPU IIPU} {ACS I WCS} FILE=pl.file [,p2.file]
[{ACSMATCH IWCSMATCH}=plrev fp2rev]]
("
CPU
IPU
specifies the CPU is the processor that is used
specifies the IPU is the processor that is used
ACS
WCS
pl.file
specifies the firmware is loaded into ACS
specifies the firmware is loaded into WCS
specifies the 1- to 16-character name of the file containing the firmware
loaded for a phase 1 processor. If p2.file is not specified, pl.file is loaded
regardless of the processor type.
specifies the 1- to 16-character name of the file containing the firmware
that is loaded for a phase 2 processor. When specified, either pl.file or
p2.file is loaded depending on the processor's phase:
[,p2.file]
pl.file
p2.file
present
present
present
present
not present
not present
present
present
Processor
Phase
File
Loaded
1
pl.file
pl.file
pl.file
p2.file
2
1
2
ACSMATCH
compares the current ACS revision number to the number specified by
revnum. Valid only for warm starts.
WCSMATCH
compares the current WCS revision number to the number specified by
revnum. Valid only for warm starts.
MPX-32 Reference Volume III
12-9
ACS Directives
pI rev
[p2rev]
is a 16-digit revision number. If pI rev and the current revision number
do not match, a load does not take place and an error message is written
to the LOD device. If a match occurs, the firmware is loaded regardless
of the processor type.
is a 16-digit revision number. When specified, the firmware is loaded
conditionally depending on the processor's phase:
pirev
p2rev
Processor
Phase
present
present
1
present
present
2
present
not present
1
present
not present
2
Action
revision number compared
to pirev. If matched,
firmware is loaded. If not
matched, no load occurs.
revision number compared
to p2rev. If matched,
firmware is loaded. If not
matched, no load occurs.
revision number compared
to pI rev. If matched,
firmware is loaded. If not
matched, no load occurs.
revision number compared
to pirev. If matched,
firmware is loaded. If not
matched, no load occurs.
Examples
The following example compares the ACSMATCH revision number to the current
ACS revision number. If the numbers match, the contents of file FIRM are loaded
into the CPU's ACS.
LOAD CPU ACS FILE=FIRM ACSMATCH=C67A303228200003
The following example loads the contents of file FIRM into the IPU's WCS.
LOAD IPU WCS FILE=FIRM
12.6.8 MODE Directive
The MODE directive is used by DUMP ACS to display the mode of a processor on the
device assigned to LFC UT.
Syntax
MODE {CPU IIPU }
12-10
CPU
specifies the mode of the CPU
IPU
specifies the mode of the IPU
c
Alterable Control Store (ACS)
ACS Directives
(
12.6.9 PATCH Directive
The PATCH directive is used by LOADACS to modify the contents of ACS or WCS.
The PATCH directive can be continued across more than one input line by placing a
hyphen (-) as the last significant character on the line to be continued. The hyphen
must not be embedded in a value and must fall after the first value and before the
SUM parameter.
Syntax
PATCH {CPUIIPU} [P1IP2] {ACSIWCS} lOC=addrVAlUE=val[,val... ] [SUM=sum]
CPU
specifies the CPU is the processor that is used
IPU
specifies the IPU is the processor that is used
P1
specifies a phase 1 32/67 processor
P2
specifies a phase 2 32/67 processor
ACS
specifies the ACS is patched
WCS
specifies the WCS is patched
lOC=addr
addr is the address in ACS or WCS loaded with the contents of M.ACS
(
VAlUE=val [,val ... ]
val is a value to be patched
[SUM=sum]
sum is a number to be compared with the one's complement of the sum of
the values. If sum does not equal the one's complement of the sum of the
values, an error message is written.
If the specified phase and the actual phase mismatch, a warning message is sent to the
LOD and the rest of the command group is skipped. Failure to conditionally patch
does not disable ACS.
MPX-32 Reference Volume III
12-11
ACS Directives
····~·\,
c
Examples
The following example compares the one's complement of the sum of the values to
the number in the SUM parameter. If the numbers match, the values are patched into
the CPU's ACS.
PATCH CPU ACS LOC=E30 VALUE=4F55D234, 3534AD24,4536 SUM=FFFFFFFFB0753B3C
The following example patches location lE30 in the IPU's WCS with the value
35F82.
PATCH IPU WCS LOC=lE30 VALUE=35F82
In the following example, the first two directive groups are conditional patches
depending on the 32/67 processor's phase. The third directive group is
unconditionally patched, and the last directive group passes control to ACS.
PATCH CPU Pl ACS LOC=E30 VALUE=FEE, F1EFOEFOO, FACE, FADE
VERIFY;
PATCH CPU P2 ACS LOC=E3E VALUE=O,O, COFFEE, D10DE
VERIFY;
PATCH CPU ACS LOC=E29 VALUE=DEADDEAD, DEADDEAD
VERIFY;
ENABLE ACS;
12.6.10 REVISION Directive
The REVISION directive is used by DUMPACS to display the revision microword on
the device assigned to LFC UT.
Syntax
REVISION {CPU IIPU} {ACS I PROM I WCS}
CPU
specifies the CPU is the processor that is used
IPU
specifies the IPU is the processor that is used
ACS
specifies the ACS is read
PROM
specifies the PROM is read
WCS
specifies the WCS is read
o
12-12
Alterable Control Store (ACS)
ACS Directives
(
VERIFY Directive
12.6.11
The VERIFY directive is used by LOADACS to compare the contents of ACS or
WCS with an internal buffer. The buffer contains the data that was written to ACS or
WCS as the result of the previous directive.
If the verification fails, an error message is written.
Syntax
VERIFY
12.7 Sample M.ACS File
The following is a sample M.ACS file.
COpy CPUi
PATCH CPU ACS LOC=E30 VALUE=4F55D234,35,34AD24,4536 SUM=FFFFFFFFB0753B3C
VERIFY
ENABLE ACSi
LOAD IPU ACS FILE=IPUACSl ACSMATCH=C67A300322820003
ENABLE ACSi
(Group 1)
(Group 2)
(Group 3)
When the sample file is executed, the phase 1 firmware in the CPU PROM is copied
to the CPU ACS with the COpy directive. The semicolon at the end of the directive
signals the end of a group in the M.ACS file.
The PATCH directive changes the contents of CPU ACS locations E30 to E33 to
thevalues 4F55D234, 35, 34AD24,and 4536. The one's complement of the
sum of these numbers is compared to FFFFFFFFB0753B3C.
The VERIFY directive compares the CPU ACS with the contents in the internal
buffer. The buffer contains the M.ACS and ACS contents used in the PATCH
directive.
The ENABLE directive sets the CPU to the ACS mode. The semicolon at the end
of the command signals the end of the second group of directives.
The LOAD directive reads the IPU ACS revision number. If the actual number
does not match the revision number specified, LOADACS goes to the next group of
directives. If the numbers match, the phase 1 firmware in system file IPUACS 1 is
loaded into the IPU ACS.
The last ENABLE directive sets the IPU to the ACS mode if the LOAD was
successful. The semicolon at the end of the directive signals the end of the third
group of directives.
MPX-32 Reference Volume III
12-13
Error Conditions and Messages
.~.
,
(
\
.j
12.8 Error Conditions and Messages
12.8.1 LOADACS Error Conditions and Messages
The LOADACS error messages described in this section are written to the SLO device
and the operator console.
The following message is displayed when the IPU is not online or SYSGENed in and
cannot be loaded. The CPU can be loaded if necessary.
J.INIT: CANNOT {COPYILOADIPATCH} IPU - IPU NOT ONLINE
The following message is displayed when there is an unrecognizable directive in
M.ACS. The directive is displayed and LOADACS goes to the next line of M.ACS.
J.INIT: UNRECOGNIZED COMMAND IN M.ACS, IGNORED:
directive
The following message is displayed when firmware cannot be loaded because of an
invalid address in a firmware file. The address and the file name containing the
address are written. LOADACS goes to the next group of directives.
J.INIT: CANNOT {LOADIPATCH}
address IN filename
{ACSIWCS} FOR {CPUIIPU} - INVALID ADDRESS
The following message is displayed when the machine type in the firmware's revision
number is not C67. The machine type of the new firmware is displayed. LOADACS
goes to the next group of directives.
J.INIT: CANNOT {LOADIPATCH} ACS FOR {CPUIIPU} - NEW FIRMWARE HAS M/C TYPE
~pe
One of the following messages is displayed when the ACSMATCH or WCSMATCH
directive is in effect and the revision number of the current firmware and the number
. specified by ACSMATCH or WCSMATCH do not match. The current firmware's
revision number is shown as PRESENT and the ACSMATCH or WCSMATCH
revision number is shown as EXPECTED. LOADACS goes to the next group of
directives.
J.INIT: CANNOT LOAD {ACSIWCS} FOR {CPUIIPU} - PRESENT REV NUMBER NOT AS
EXPECTED FROM {ACSMATCHIWCSMATCH} COMMAND
PRESENT = revnumber
EXPECTED = revnumber
The following message is displayed when a checksum error occurs during a LOAD,
PATCH, or COPY. LOADACS goes to the next group of directives.
J.INIT: CANNOT {LOAD I PATCH I CopY}
{ACSIWCS} FOR {CPUIIPU} - CHECK SUM ERROR IN {jilenameIPROM}
o
12-14
Alterable Control Store (ACS)
Error Conditions and Messages
The following message is displayed when a verification fails. The address of the
failure is displayed, plus the contents of the differing firmware. LOADACS goes to
the next group of directives.
J.INIT: {COPYILOAD I PATCH}
ADDRESS addr DIFFERS
TO {CPUIIPU} FOR {ACSIWCS} FAILED VERIFICATION,
{PROM lfilename} = contents
{ACS IWCS} = contents
The following message is displayed when the firmware file cannot be assigned. A
decimal error number (RMxx) is returned by H.REMM. LOADACS goes to the next
group of directives.
J. INIT: CANNOT LOAD {ACS I WCS} FOR {CPU I IPU} - UNABLE TO ASSIGN filename
ERROR RMxx
The following message is displayed when an invalid value is found in a firmware file.
The file's name, the invalid value, and the address of the value are displayed.
LOADACS goes to the next group of directives.
J.INIT: CANNOT {LOADIPATCH} {ACSIWCS} FOR {CPUIIPU} - INVALID VALUE
value IN filename AT ADDRESS addr
The following message is displayed when an ENABLE directive is used in a group of
WCS directives. The ENABLE directive is valid for ACS only. Remove the
ENABLE directive.
J.INIT: ENABLE COMMAND IS INVALID WHEN WCS ACTION IS SPECIFIED
The following message is displayed when there is no WCS to load. LOADACS goes
to the next group of directives.
J.INIT: CANNOT {LOADIPATCH}
{CPUIIPU}
WCS - NO WCS PRESENT
The following message is displayed if a previous action to a processor failed. J .INIT
cannot enable the ACS since that firmware has not been properly loaded. LOADACS
goes to the next group of directives.
J.INIT: CANNOT ENABLE {CPUIIPU} ACS - PREVIOUS ACTION TO THIS PROCESSOR FAILED
The following message is displayed if the processor is in the ROMSIM mode, i.e.,
writing to ACS results in a System Check Trap. LOADACS goes to the next group
of directives.
J.INIT: CANNOT {COPYILOADIPATCH}
MPX-32 Reference Volume III
{ACSICPU} FOR {CPUIIPU} - {CPUIIPU} IS IN ROMSIM MODE
12-15
Error Conditions and Messages
t
"
12.8.2 DUMPACS Error Conditions and Messages
The following DUMPACS error messages are written to the device assigned to LFC
UT.
The following message displays when the last directive entered is invalid. Enter a
valid directive at the DMP prompt.
INVALID COMMAND
The following message displays when the last directive entered contains an invalid
processor mnemonic. The valid mnemonics are CPU and IPU.
INVALID PROCESSOR MNEMONIC
The following message displays when the last directive entered contains an invalid
memory type. Valid memory types are PROM, ACS, and WCS.
INVALID MEMORY TYPE
The following message displays when the starting address specified in the DUMP
directive is invalid. Re-enter the directive with a new starting address.
INVALID START ADDRESS
The following message displays when the ending address specified in the DUMP
directive is invalid. Re-enter the directive with a new ending address.
INVALID END ADDRESS
The following message displays when the directives can be used only on a 32/67
machine.
THIS MACHINE IS NOT A 32/67 - CAN NOT DO IT
The following message displays when the IPU was not configured in the system at
SYSGEN time.
IPU NOT CONFIGURED IN SYSTEM
The following message displays when the IPU is offline. IPU directives are not
executed until the IPU is marked online.
IPU MARKED OFFLINE
The following message displays when DUMPACS cannot open LFC SLO to write
required data. If the SLO default is used in this case, a system problem exists.
CAN NOT OPEN SLO
The following message displays when an incorrect address is found in the firmware
file. Correct and reassemble the firmware file, then re-enter the directives.
BAD ADDRESS addr FOUND IN FIRMWARE FILE
The following message displays when the firmware file cannot be assigned. A
decimal error number (RMu) is returned by H.REMM.
UNABLE TO ASSIGN FILE - ERROR RMxx
12-16
Alterable Control Store (ACS)
/
Error Conditions and Messages
<:-.
The following message displays when a parameter in the last directive is invalid.
Correct the parameter and re-enter the directive.
INVALID PARAMETER
The following message displays when the processor used in the directive does not
have WCS.
THERE IS NO WCS ON THIS PROCESSOR
MPX·32 Reference Volume III
12·17/12·18
(
13
Volume Formatter (J.VFMT)
13.1 Introduction
The Volume Formatter (J.VFMT) formats volumes (disks) for use with MPX-32 and
allows you to manage disk media online. With online media management directives,
you can initialize media and perform media flaw editing.
When formatting volumes. J.VFMT FORMAT directive processing creates the
following data structures on each volume:
(
Volume descriptor
Resource descriptor allocation bit map (DMAP)
DMAP descriptor
File space bit map (SMAP)
SMAP descriptor
System image descriptor
General allocatable resource descriptors
Allocatable resource descriptors map
Root directory
Root directory descriptor
DMAP deallocation file
DMAP deallocation file descriptor
SMAP deallocation file
SMAP deallocation file descriptor
Media deallocation file
Media deallocation file descriptor
13.2 General Description
J.VFMT operates in either of two environments: a fully functional MPX-32 system or
a starter system generated by the System Distribution Tape (SDT) when SYSINIT
activates J.VFMT from tape.
When IPL is performed from the SDT. file system support is not present in the form
of a usable disk volume. To format a system volume. SYSINIT makes a static
assignment indicating the system image is coming from tape. and a system image file
is read from the SDT. Therefore. the IMAGE option for the FORMAT directive in
J. VFMT must not be specified.
13.3 Logical File Code Assignments
Logical file codes required by J.VFMT are described in this section and summarized
in Table 13-1.
13.3.1 Audit Trail (SLO)
As J.VFMT processes directives. it produces listed output for operations it performs.
The LFC for the audit trail is SLO.
MPX-32 Reference Volume JIJ
13-1
Logical File Code Assignments
13.3.2 Directive Input (SVC)
Directive input is assigned to J.VFMT from logical file code SYC.
Table 13-1
J.VFMT logical File Code Assignments
Input/Output
Description
Logical
File Code
Default assignments
for J.VFMT
Audit trail
SLO
$ASSIGN SLO TO LFC=UT
Directive input
SYC
$ASSIGN SYC TO SYC
13.4 Using J.VFMT
J.VFMT formats unmounted volumes for use with MPX-32. An attempt to run
J. VFMT on a mounted volume causes an abort.
Generally, only one J.VFMT directive verb can be processed for each FMT prompt.
When the requested function completes, J.VFMT exits and returns to the calling task.
For example,
TSM>$J.VFMT
FMT>FORMAT DEV=DM0802 VOL=EXAM MAXRE=3000 CON=Y
FMT>CON=N
DEVICE=DM0802 -- VOLUME FORMATTING SUCCESSFULLY COMPLETED
TSM>
An exception to this is for the INITIALIZE directive. After processing completes for
this directive, J.VFMT prompts the user for an additional directive. This is useful (and
required during an SDT activation of J.VFMT) to continue processing with the
FORMAT directive.
When run in the batch mode, parameters must be specified in the first input string on
the directive line.
In the interactive mode, J.VFMT prompts for more data after the first input string if:
• required parameters are not specified
• directive line contains a syntax error
• the Boolean flag for confirm is not turned off
If a syntax error occurs, J.VFMT displays an error message and the part of the
directive line in error. The remainder of the directive line is ignored. However,
directives and parameters in the directive line before the syntax error occurred are
processed and need not be respecified.
To recover from certain errors in the interactive mode, J.VFMT requires specific
information specified by error message output. In some cases, additional input is not
accepted until requested.
13-2
Volume Formatter (J.VFMT)
Using J. VFMT
13.4.1 Directive Syntax Rules
The directive line has three parts:
• Verb
• Parameters
• Options
Blank spaces are legal delimiters between directive line components.
13.4.1.1 Verb
The verb defines the action the utility is to take (such as FORMAT, REPLACE,
EXIT) and determines the subset of valid options. The verb must be the first item on
the directive line.
13.4.1.2 Parameters
Parameters are required keywords followed by an equal sign and a value. They are
entered on the directive line after the verb. Parameters specify what is affected by the
action of the directive. Parameters have three types of values:
(
• Boolean - Values are true (T), false (F), yes (Y), no (N), on (ON), and off (OFF).
Values true, yes, and on are synonymous. Values false, no, and off are
synonymous.
• Numeric - Values are either decimal or hexadecimal numbers. For example, radix
can be stated using the radix indicators X and N, e.g., X'AB', N'18'.
• ASCII string - Values are expressed as strings containing alphanumeric characters.
13.4.1.3 Options
Options are optional keywords followed by an equal sign and a value. If specified,
options are entered on the directive line after the parameters. Options are used as
qualifiers (such as ACCESS=, CONFIRM=, IMAGE=). Where applicable, default
values are provided. See the individual directive descriptions for defaults.
13.4.2 Directive Line Continuation
Directive lines can be continued across lines by placing a hyphen (-) as the last
significant character on the line. This results in a prompt for more input when in the
interactive mode, and another read when in batch mode or when reading a selected
file. Each time a directive line is continued, the continuation character is replaced by
a space. The only restriction is that single names, keywords, or an entire pathname
must appear on the same line of input.
MPX-32 Reference Volume III
13-3
Using J. VFMT
13.4.3 The CONFIRM Parameter
The CONFIRM parameter is included in the following Volume Formatter directives:
EDITFMAP, FORMAT, INITIALIZE, NEWBOOT, and REPLACE. This parameter
allows the user to review the specified values of all parameters and options associated
with a directive. The user may then change these values before processing the
directive, or begin processing without making any changes.
CONFIRM is only valid in interactive mode. In any other mode it is ignored.
When CONFIRM=Y (the default) is specified for a given directive, a list of that
directive's options and parameters (and their specified values) is displayed as soon as
the directive is entered. To change the values of any of these options or parameters,
the user must type the option or parameter, an equals sign, and the new value.
Changing an option or parameter requires the same syntax as specifying it as part of a
directive. After the changes are entered, all options and parameters are displayed
again. The directive may then be processed using the new values by entering
CONFIRM=N.
Any number of options and parameters may be changed at one time. Changes can be
made and displayed any number of times.
The user may also choose to exit Volume Formatter without processing the directive.
This is done by typing X or EXI T.
13.5 Accessing the Volume Formatter
The Volume Formatter can be accessed from a batch file or TSM in the following
ways:
$J. VFMT
$EXECUTE J.VFMT
$RUN J. VFMT (valid
from the system directory only)
When logical file code SYC is assigned to a terminal, the FMT> prompt is displayed.
13-4
Volume Formatter (J.VFMT)
Volume Formatter Directives
(
13.6 Volume Formatter Directives
The following directives are supported by J.VFMf.
Directive
Description
COPY
copies a mounted volume to an unmounted volume
EDITFMAP
converts flaw definition information from one medium to another
EXIT
exits the Volume Formatter utility
FORMAT
software formats a disk
INITIALIZE
prepares a disk for volume formatting by writing new labels to its
tracks and sectors, and builds a media descriptor (MD) track
NEWBOOT
writes a new bootstrap process to a formatted volume
REPLACE
writes a new default system image and bootstrap to
a formatted volume
13.7 COPY Directive
The COPY directive copies a mounted volume to an unmounted medium. To do this,
it formats the target medium with the characteristics of the source volume, then copies
the RDs, directories, and files from the source to the target volume. The target
medium must be the same disk type as the source. When using this directive with
HSDP disks, the source and target disks must have the same track and sector
configuration.
(
The COpy directive cannot be specified during SDT processing.
Syntax
COPy VOLUME=volnameTARGET=mmccss [BRIEF=(YIN}] [DESTROY=(YIN}]
VOLUME=volname
volname is the name of the source volume to copy
TARGET=mmccss
mmccss is the device type, channel address, and device subaddress of the
device where the target medium is located. Valid device types are:
DM moving head or memory disk
FL floppy disk
DF fixed head disk
c
[BRIEF=( YIN}]
If N is specified, COpy writes to SLO a list of the directories and files
copied and their size. If Y is specified, only the directories are written to
SLO. However, if a file cannot be copied, its pathname and the
applicable error code is written to SLO. Default is Y.
MPX-32 Reference Volume III
13-5
COPY Directive
[DESTROY={YIN}]
Y permits J.VFMT to overwrite a formatted target disk. The default is N.
If the target disk is formatted but Y has not been specified, J.VFMT
issues a warning message. In batch or command-file mode, J.VFMT then
aborts to TSM. In interactive mode, J.VFMT follows the warning
message with the prompt CONT INUE - YIN? If the user chooses Y,
the disk is overwritten. Otherwise, J.VFMT aborts to TSM.
Notes:
1. J.VFMT does not copy files in the following cases:
• source file cannot be allocated for implicit shared read access with no
previous writers on the file
• target volume lacks enough contiguous file space for the source file or for
the directory file
• source file is in a directory created after the disk copy begins
• source file or partition is created after processing of its directory begins
• source file or partition is deleted before its directory entry is processed
2. Error messages display when:
•
•
•
•
a file or directory cannot be copied
an RID is changed
a file's start address is not maintained at the same start address
the bootability of a volume is not maintained
3. General SLO output contains:
• a list of directories copied
• a snapshot of the free space on the source volume when COpy is initiated
• a snapshot of the free space on the target volume when COPY concludes,
including the amount of contiguous free space
• disk bus performance information. This includes the number of blocks
transferred, the elapsed time of the copy, and a bytes per second rate with a
bus efficiency rating.
• if BRIEF=N is specified, a list of the files copied and their size
c
13-6
Volume Formatter (J.VFMT)
EDITFMAP Directive
(
13.8 EDITFMAP Directive
The EDITFMAP directive converts flaw definition infonnation from one medium to
another. This directive is used for online disk media management. For more
infonnation about managing disk media online, refer to the Online Disk Media
Management section in this chapter.
The EDITFMAP directive executes in either read-only mode or no I/O mode.
• Use read-only mode when the disk is present and has flaw infonnation available for
read-only access. To specify this mode include both the DISC and DEVICE
options with this directive.
• Use no I/O mode when the disk cannot or need not be read. To specify this mode
include the DISC option and omit the DEVICE option with this directive.
The EDITFMAP directive cannot be specified during SDT processing.
Syntax
EDITFMAP DISC=dcode [CONFIRM={ YIN}] [DEVICE=mmccss] [DUMP=(ddccss,idJ)]
[FMAP={ YIN}] [I NCLUDE=mapjile ] [LOAD=(ddccss,id2)]
(
DISC=dcode
dcode is the disk storage device type code. Refer to Note 1 in the
INITIALIZE directive section for a list of disk type codes.
[CONHRM={Y IN}]
specifies whether confinnation is required before processing begins. If Y
is specified, prompts are issued which allow the user to modify options
and parameters, or start processing. If N is specified, no prompt is issued.
The default is Y. This option is valid only in interactive mode; it is
ignored in any other mode.
[DEVICE=mmccss]
mmccss is the device type, channel address, and device subaddress of the
device with the media flaw infonnation to edit. Valid device types are:
DM moving head or memory disk
FL floppy disk
DF fixed head disk
("
MPX-32 Reference Volume III
13-7
EDITFMAP Directive
[DUMP=(ddccss,idl)]
specifies writing media flaw information in dumped media flaw format to
a device and assigns an ID to the output. See note 1.
ddccss
idl
is the device mnemonic, channel address and device subaddress.
The mnemonic can be any magnetic tape mnemonic (M7, M9,
MT) or floppy disk (FL).
is an identifier (1 to 20 ASCII characters) to record on the
external medium with the dumped media flaw data. Successive
single quote marks indicate that idl contains all blanks.
[FMAP= {YIN}]
Y writes the media flaw map to SLO. The default is N.
[I NCLUDE::mapfile ]
mapfile is the pathname of a file containing a media flaw map to include
in the new media flaw data being generated. Refer to section 13.16.6 for
a description of the format for a media flaw map entry.
[LO AD=(ddccss,id2)]
specifies read of media flaw information in dumped media flaw format
from a device. See note 1.
ddccss is the device mnemonic, channel address and device subaddress.
The mnemonic can be any magnetic tape mnemonic (M7, M9,
MT) or floppy disk (FL).
is an identifier (l to 20 ASCII characters) to compare to the ID
id2
recorded on the external medium with the dumped media flaw
data being read. Successive single quote marks indicate that
verification of id2 is not required.
Notes:
1.
The LOAD and DUMP identifiers are incompatible with early releases of the
UDP/DP II MVP that limit identifiers to 4 characters.
Examples
°
The following example converts dumped media flaw data from tape drive M910 0 to
SLO.
EDI DIS=DC0600 CON=N FMAP=Y LOA=(M91000,FLAWS.Dl)
The following example converts flaw definition information from the text file FILEl
to SLO.
EDI DIS=DP0080 FMA=Y INC=@RTO(SYSTEM)FILEl
13-8
Volume Formatter (J.VFMT)
EXIT Directive
(
13.9 EXIT Directive
The EXIT directive exits J.VFMT and returns control to TSM.
Syntax
{EXITIX}
13.10 FORMAT Directive
The FORMAT directive software formats a disk. This directive does not check for
existing data on the disk, but does check for existing volume structures.
For all disks, except floppy and memory disks, the disk media must have been
initialized prior to using the FORMAT directive. This may be accomplished by:
• using the J.VFMT INITIALIZE directive (MFP SCSI, HSDP, or UDPjDP II
controllers)
• running the Level II Diagnostic Media Verification program (HSDP or UDPjDP II
controllers)
• running the Level II Diagnostic program (MFP SCSI)
Syntax
FORMAT DEVICE=mmccss VOLUME=volname [ACCESS=usertype([READ] [DELENT]
[ADD] [TRAVERSE])]. .. [ALOC=blocks] [BOOTFILE=OLD I NEW I bstrap}]
[CONFlRM={YIN}] [DESTROY={YIN\] [DETACH={YIN}] [ECC={YIN\]
[IMAGE=image] [ISIZE=blocks] [MAXAU=units] [MAXRES=rds]
[MAXROOT=entries] [OWNER=ownername] [PROJECTGROUP=proj]
o EVICE=mmccss
mmccss is the device type, channel address, and device subaddress of the
disk to be formatted. Valid device types are:
DM moving head or memory disk
FL floppy disk
DF fixed head disk
VOLUME=volname
volname is a user-specified name for the volume being formatted. This
name can be 1 to 16 characters.
MPX·32 Reference Volume III
13·9
C,-",
FORMAT Directive
"
I.,'
[ACCESS=usertype([READ] [DELENT] [ADD] [TRAVERSE])] ...
I
/'
specifies the access attributes for the root directory of the volume. Empty
parentheses, such as ACCESS=OT ( ) indicate no access possible.
Repeat this option for each usertype desired. If not specified, owner has
complete access, project group has all but delete access, and others have
read only and traverse access.
usertype
is one of the following types of users:
OWNER specifies what access rights the owner has to the
root directory
PROJECfGROUP
specifies what access rights the project group
has to the root directory
OTHERS specifies what access rights others have to the
root directory
READ
permits usertype to read the root directory
DELENT
permits usertype to delete entries from the root directory
ADD
permits usertype to add entries to the root directory
TRAVERSE permits usertype to traverse the root directory
[A LOC=blocks]
blocks is the number of blocks per allocation unit on the disk being
formatted. The maximum value for blocks is the number of sectors per
track. If omitted or set to 0, J.VFMT uses a system default based on the
disk's capacity. For information on allocation units, refer to Table 13-2.
[BOOTFILE={ OLD I NEW I bstrap}]
specifies the bootstrap to be installed to the disk. If this option is omitted,
J.VFMT installs the appropriate standard bootstrap.
OLD
NEW
bstrap
specifies the old standard bootstrap. The old standard
bootstrap is designed for images that require no more than 5
lOCOs to load.
specifies the new standard bootstrap. The new standard
bootstrap is designed for images that require 6 or more
IOCDs to load.
is the patbname of a file containing a nonstandard bootstrap.
This bootstrap may follow either the old or new style. This
file must be in absolute load module format. Its maximum
length is seven I92-word blocks including the load module
preamble. Note: 00 not specify bstrap when J.VFMT is
activated from an SOT.
Not all MFP SCSI interfaces support ne~-style bootstraps. If you specify
NEW, or a pathname containing a nonstandard bootstrap designed for
images requiring 6 or more lOCOs, when formatting an MFP SCSI
interface which does not support the new-style bootstrap, J.VFMT aborts
to TSM.
For more information on the old and new standard bootstraps, see Chapter
5, section 5.2, of this volume.
13-10
Volum~
Formatter (J.VFMT)
(;
FORMAT Directive
[CONFIRM={Y I Nil
specifies whether confirmation is required before processing begins. If Y
is specified, prompts are issued which allow the user to modify options
and parameters, or start processing. If N is specified, no prompt is issued.
The default is Y. This option is valid only in interactive mode; it is
ignored in any other mode.
[DESTROY={Y IN}]
Y permits J.VFMT to overwrite existing volume structures on the disk to
be formatted. The default is N. If the disk to be formatted contains
existing volume structures but Y has not been specified, J.VFMT issues a
warning message. In batch or command-file mode, J.VFMT then aborts
to TSM. In interactive mode, J.VFMf follows the warning message with
the prompt CONTINUE - YIN? If the user chooses Y, the disk is
overwritten. Otherwise, J.VFMT aborts to TSM.
[DETACH={YIN}]
specifies whether J.VFMT should run as an independent task. If Y is
specified, J.VFMT displays the current parameters, then detaches from
the terminal, and returns control to· TSM. Formatting continues as usual.
When it completes, a message displays on the terminal. This option is
valid only in interactive mode.
('"
[ECC={ YIN Il
specifies whether disk sectors with correctable data errors are available for
users to allocate. If Y is specified, users can allocate these sectors. If N
is specified, J.VFMT marks these sectors as allocated (bad block
deallocation). The default is N.
[I MAGE= image]
image is the patbname of a file containing a system image. If the IMAGE
option is not specified and J.VFMf is disk activated, the target volume
will not be bootable. Note: 00 not specify this option when J.VFMT is
activated from an SOT.
[ISIZE=blocks]
blocks is the number of blocks allocated for the system image. The
default is 600.
[MAXAU=units]
units is the number of allocation units on the disk. This number's default
value depends on the ALOC=blocks option or the default granularity if
blocks is not specified. If specified, units must be less than the number of
allocation units physically available.
[MAXRES=rds]
rds is the number of resource descriptors (RO) to reserve disk space for.
One RO is required for every file defined on the volume. The default for
memory disks or floppy disks is 70. All other devices default to 1000.
[MAXROOT=entries]
entries is the number of entries in the root directory to reserve disk space
for. This number can be modified to accommodate various hashing
algorithms. The default is 100.
MPX-32 Reference Volume III
13-11
FORMAT Directive
[OWNER=ownername]
ownername is the owner name to associate with the volume. This name
is recorded in the volume descriptor. If omitted, J.VFMT uses the owner
name associated with the J.VFMT task.
[PROJECTGROUP=proj]
proj is the project group name to associate with the volume. This name is
recorded in the volume descriptor. If omitted, J.VFMI' uses the project
group name associated with the J.VFMI' task.
Table 13-2
Allocation Units
Capacity
Drive type
N/A
N/A
5MB
32MB
40MB
64MB
80MB
96MB
160MB
300MB
337 MB
340MB
447MB
500MB
600MB
687MB
700MB
800MB
850MB
858 MB
1230 MB
floppy moving head
memory disk
fixed head
cartridge module
moving head
cartridge module
moving head
cartridge module
moving head
moving head
moving head
moving head
moving head
moving head
moving head
moving head
moving head
moving head
moving head
moving head
moving head
Default sectors per unit
I
1
1
2
2
2
2
2
4
4
5
4
5
5
10
9
7
9
9
9
11
13.11 INITIALIZE Directive
The INITIALIZE directive prepares a disk for volume formatting by writing new track
and sector labels, and building the media descriptor track. This directive is used for
online disk media management. For more information about managing disk media
online, refer to the Online Disk Media Management section in this chapter.
Because this directive overwrites the disk, for HSDP disk media save any existing
vendor flaw information to a device before initialization or by specifying the DUMP
option with this directive.
13·12
Volume Formatter (J.VFMT)
()
INITIALIZE Directive
(
This directive does not initialize the two cylinders reserved for diagnostic use or the
cylinder reserved for hardware vendor use.
Executing the INITIALIZE directive can be a lengthy process. Depending on the disk
capacity, the directive can take in the order of 30 to 45 minutes to complete. In the
interactive mode, J.VFMT writes status information to the terminal, allowing the user
to follow its progress. For MFP SCSI media, no status information is generated, so
the user must allow an appropriate time for completion.
With the INITIALIZE directive you can:
• read media flaw information from an ASCII text file by specifying the INCLUDE
option
•
•
•
•
read dumped flaw information from a device by specifying the LOAD option
check for additional media flaws on a disk by specifying PATTERN=Y
initialize a disk for dual port use by specifying DUAL=Y
write new media flaw information in dumped media flaw format with the DUMP
option
• write a media flaw map to SLO by specifying FMAP= Y
• perform sector substitution by specifying SSUB=Y. (HSDP disk only)
Syntax
(
INITIALIZE DEVICE=mmccss [CONFIRM=! YIN}] [DESTROY=! YIN}] [DISC::dcode]
[DUAL={ YIN}] [DUMP=(ddccss,idl}] [FMAP={ YIN}] [I NCLUDE=mapjile ]
[LOAD =(ddccss,id2)] [PATTERN={YIN}] [SSUB={Y IN}]
DEVICE=mmccss
mmccss is the device type, channel address, and device subaddress of the
disk
DM
FL
DF
to be initialized. Valid. device types are:
moving head or memory disk
floppy disk
fixed head disk
[CONFlRM=! YIN}]
specifies whether confirmation is required before processing begins. If Y
is specified, prompts are issued which allow the user to modify options
and parameters, or start processing. If N is specified, no prompt is issued.
The default is Y. This option is valid only in interactive mode; it is
ignored in any other mode.
[DESTROY= { YIN} ]
Y permits J.VFMT to overwrite a formatted disk. The default is N. If
the disk to be initialized is formatted but Y has not been specified,
J.VFMT issues a warning message. In batch or command-file mode,
J.VFMT then aborts to TSM. In interactive mode, J.VFMT follows the
warning message with the prompt CONTINUE - YIN? If the user
chooses Y, the disk is overwritten. Otherwise, J.VFMT aborts to TSM.
MPX-32 Reference Volume III
13-13
INITIALIZE Directive
[DISC=dcode]
dcode is the disk device type code. Refer to Note 1 for a list of disk type
codes. Note: This option is required when the target disk is an HSDP
media that has been sector substituted.
[DUAL= {YIN} ]
Y writes track and sector labels with the dual port option bit set in the
DATR field of each label. The default is N.
[DUMP=(ddccss,idJ) ]
specifies writing media flaw information in dumped media flaw format to
a device and assigns an ID to the output. See note 2.
ddccss
is the device mnemonic, channel address and device subaddress.
The mnemonic can be any magnetic tape mnemonic (M7, M9,
MT) or floppy disk (FL).
idl
is an identifier (1 to 20 ASCII characters) to record on the
external medium with the dumped media flaw data. Successive
single quote marks indicate that idl contains all blanks.
[FMAP={ YIN}]
Y writes a media flaw map to SLO after the disk is initialized. The
default is N.
[I NCLUDE=mapfile ]
mapfile is the pathname of a file containing a media flaw map to include
in the new media flaw data being generated. Refer to section 13.16.6 for
a description of the format for a media flaw entry.
[LOAD=(ddccss,id2) ]
specifies read of media flaw information in dumped media flaw format
from a device. See note 2.
ddccss
is the device mnemonic, channel address and device subaddress.
The mnemonic can be any magnetic tape mnemonic (M7. M9.
MT) or floppy disk (FL).
id2
is an identifier (1 to 20 ASCII characters) to compare to the ID
recorded on the external medium with the dumped media flaw
data being read. Successive single quote marks indicate that
verification of id2 is not required.
[PATTERN={ YIN}]
Y tests the disk for flaws by writing a worst-case pattern to the disk, then
reading and comparing it. Any errors detected are added to the media
flaw information. The default is N.
[SSUB={Y IN}]
Y substitutes the spare sector on each of the disk's tracks for a single
flawed sector on that track. This option is valid only for disks with
HSDP disk interfaces. It is ignored when intializing disks with any other
type of disk interface. The default is N.
13·14
Volume Formatter (J.VFMT)
INITIALIZE Directive
Notes:
1.
2.
The disk device type codes valid for the INITIALIZE and EDITFMAP directives
are as follows.
Disk
Type Code
Controller
Model
Number
Description
DPOO80
DP0337
DP0474
DP0500
DP0689
DP0800
DP0850
DP0858
DP1230
HSDP
HSDP
HSDP
HSDP
HSDP
HSDP
HSDP
HSDP
HSDP
8138
8887
8884
8812
8889
8881
8813
8888
8814
CDC 80MB RSD
Fujitsu 337 MB Winchester
Fujitsu 474 MB Winchester
CDC 500 MB EMD
Fujitsu 689 MB Winchester
NEC 800 MB Winchester
CDC 850 MB EMD
CDC 858 MB XMD
CDC 1.23 GB EMD
DC0080
DC0160
DC0300
DC0340
DC0600
UDP/DP
UDP/DP
UDP/DP
UDP/DP
UDP/DP
II
II
II
II
II
var.
8127
9346
8858
8155
CDC
CDC
CDC
CDC
CDC
SD0150
SD0300
SD0700
MFP SCSI
MFP SCSI
MFP SCSI
8820
8828
8833
CDC 150 MB Wren III SCSI
CDC 300 MB Wren IV SCSI
CDC 700 MB Wren V SCSI
80 MB disk
160 MB fixed media
300 MB removable
340 MB Winchester
675 MB fixed media
For UDP/DP II, the SYSGEN disk type codes MHxxx can be used instead of
DCOXU'. This enables compatibility with existing disk type codes defined in the
SYSGEN file.
The LOAD and DUMP ids are incompatible with early releases of the UDP/DP
II Media Verification Programs that limit the id field to 4 characters.
Examples
The following example initializes the disk on device DMO 800 for multiport use.
Before initialization, it writes the disk's existing media flaw information to device
FL 7EFO and assigns it an ID of blanks. After initializating the disk, J.VFMT writes a
media flaw map to SLO.
In non-interactive mode, J.VFMT aborts if the target device, DM0800, is found to be
software formatted. In interactive mode, J.VFMT prompts the user to continue if the
the target device is formatted.
INI DEV=DM0800 DUAL=Y DUMP=(FL7EFO,") FMAP=Y
(,
MPX·32 Reference Volume III
13·15
INITIALIZE Directive
The following example initializes the disk type DP0500 on device DMOCOO. It
includes the media flaw map in MAP 5 00 file and media flaw information from device
M91000 in the new Media Descriptor (MO) track. Any existing structures on the
disk are overwritten.
INIT DEV=DMOCOO DES=Y DISC=DP0500 INC=MAP500LOA=(MT91000,RTSW)
13.12 NEW BOOT Directive
The NEWBOOT directive replaces the bootstrap on a previously formatted volume.
For this volume to be bootable, you must have specified the IMAGE option when
formatting the disk with J.VFMT. See the FORMAT directive. The NEWBOOT
directive is invalid when J.VFMT is activated from an SOT.
Syntax
NEWBOOT DEVICE:mmccss VOLUME:volname [BOOTFILE: {OLD I NEW I bstrap}]
[CONFIRM={ YIN} ]
DEVICE:mmccss
mmccss is the device type, channel address, and device subaddress of the
disk whose bootstrap program is being replaced. Valid device types are:
OM moving head or memory disk
FL floppy disk
OF fixed head disk
VOLUME=volname
volname is the name of the target volume.
[BOOTFILE:{OLD I NEW I bstrap}]
specifies the bootstrap to be installed to the disk. If this option is omitted,
J.VFMT installs the appropriate standard bootstrap.
OLD
NEW
bstrap
specifies the old standard bootstrap. The old standard
bootstrap is designed for images that require no more than 5
lOCOs to load.
specifies the new standard bootstrap. The new standard
bootstrap is designed for images that require 6 or more
lOCOs to load.
is the patbname of a file containing a nonstandard bootstrap.
This bootstrap may follow either the old or new style. This
file must be in absolute load module format. Its maximum
length is seven I92-word blocks including the load module
preamble.
Not all MFP SCSI interfaces support new-style bootstraps. If you specify
NEW, or a patbname containing a nonstandard bootstrap designed for
images requiring 6 or more lOCOs, for an MFP SCSI interface which
does not support the new-style bootstrap, J.VFMT aborts to TSM.
13-16
Volume Formatter (J.VFMT)
NEW BOOT Directive
(
For more information on the old and new standard bootstraps, see Chapter
5, section 5.2, of this volume.
[CONFIRM={ V IN}]
specifies whether confirmation is required before processing begins. If Y
is specified, prompts are issued which allow the user to modify options
and parameters, or start processing. If N is specified, no prompt is issued.
The default is Y. This option is valid only in interactive mode; it is
ignored in any other mode.
13.13 REPLACE Directive
The REPLACE directive writes a new default system image and bootstrap to a
formatted volume. Use this directive to modify system image data in the volume
descriptor. The volume can already contain a default system image.
Syntax
REPLACE DEVlCE=mmccss IMAGE=image VOLUME=volname
[BOOTFILE= { OLD I NEW I bstrap }] [CONFIRM= { V IN} ]
DEVICE=mmccss
mmccss is the device type, channel address, and device subaddress to
write a new system image and bootstrap. Valid device types are:
OM moving head or memory disk
FL
floppy disk
OF
fixed head disk
IMAGE=image
image is the patbname of a file containing a system image.
VOLUME=volname
volname is the name of the target volume.
[BOOTFILE={ OLD I NEW I bstrap}]
specifies the bootstrap to be installed to the disk. If this option is omitted,
J.VFMT installs the appropriate standard bootstrap.
OLD
specifies the old standard bootstrap. The old standard
bootstrap is designed for images that require no more than 5
lOCOs to load.
NEW
specifies the new standard bootstrap. The new standard
bootstrap is designed for images that require 6 or more
lOCOs to load.
bstrap
is the pathname of a file containing a nonstandard bootstrap.
This bootstrap may follow either the old or new style. This
file must be in absolute load module format. Its maximum
length is seven I92-word blocks including the load module
preamble. Note: Do not specify bstrap when J.VFMT is
activated from an SOT.
MPX-32 Reference Volume III
13-17
REPLACE Directive
Not all MFP SCSI interfaces support new-style bootstraps. If you specify
NEW, or a patbname containing a nonstandard bootstrap designed for
images requiring 6 or more lOCOs, when using REPLACE with an MFP
SCSI interface which does not support the new-style bootstrap, J.VFMT
aborts to TSM.
For more information on the old and new standard bootstraps, see Chapter
5, section 5.2, of this volume.
[CONFIRM={ V IN}]
specifies whether confirmation is required before processing begins. If Y
is specified, prompts are issued which allow the user to modify options
and parameters, or start processing. If N is specified, no prompt is issued.
The default is Y. This option is valid only in interactive mode; it is
ignored in any other mode.
13.14 J.VFMT Errors
The following error messages are issued by J.VFMT:
Code
Description
VFOl
ERROR HAS OCCURRED.
VF02
OPEN FAILURE ON AUDIT TRAIL DEVICE/FILE
VF03
EOF/EOM ON AUDIT TRAIL DEVICE/FILE
VF04
I/O ERROR ON AUDIT TRAIL DEVICE/FILE
SEE SLO FILE FOR EXPLANATION.
13.15 Examples
The following example formats a non-bootable disk using the name MASTER. It is
located on device DMO 800, and space for 4000 resource descriptors is reserved.
FMT>FORMAT DEV=DM0800 VOL=MASTER MAXRE=4000
The following example writes the nonstandard bootstrap specified by the BOOTF I LE
parameter to volume NEW located on device DM0802. All parameters will be
displayed. Confirmation will have to be reset to false (Le., CON=N) to continue the
formatting process.
FMT>NEWBOOT DEV=DM0802 VOL=NEWFMT_BOOTFILE=@SYSTEM(USER1)BOOTSTRAPFMT CON=Y
The following example changes the default system image on volume MASTER4
located on device DMO 8 0 4 to the system image defined in file BOOT located on
volume SYSTEM in directory USERl. The appropriate standard bootstrap is also
written to the disk.
FMT>REPLACE DEV=DM0804 VOL=MASTER4FMT_IMA=@SYSTEM(USER1)BOOT
13-18
Volume Formatter (J.VFMT)
Examples
(
The following example formats a disk using the name MAS TER. It is located on
device DM0800, the owner has complete access to the volume, the project group has
read and add access to the volume, and other users have read access to the volume.
FMT>FORMAT DEV=DM0800 VOL=MASTERFMT_ACC=OW(R A D T)FMT_ACC=PR(R A )FMT_ACC=OT(R)
13.16 Online Disk Media Management
To manage disk media online, use the J.VFMT INITIALIZE and EDITFMAP
directives. These directives provide media initialization and media flaw editing for the
following disk interfaces:
• universal disk processor (UDP)
• disk processor II (DP II)
• high speed disk processor (HSDP)
Media management using J.VFMT is generally equivalent to the CONCEPTj32
Diagnostic Facility Level II Media Verification Program (MVP) for these disk
interfaces.
For small computer system interface (SCSI) disks, J.VFMT provides limited media
management capabilities. Refer to the Managing SCSI Disks section later in this
chapter for more information.
The following sections define media management terminology and describe how to
initialize disks and manage media flaw information.
13.16.1 Media Management Terminology
This section defines the terms used in following discussions of media management
directives and procedures. It also notes where HSDP or UDPjDP II use different
terms for similar structures.
Media flaw is a physical defect on a disk. The term media flaw is interchangeable
with the term media defect. This chapter uses flaw, except where defect
is already part of a data structure name.
Vendor flaw information describes disk media flaws detected by the vendor during
factory testing. This information is usually recorded on each track of the
disk in a structure called a vendor label. HSDP can read vendor flaw
information with the Read Vendor Label command. UDPjDP II do not
have this capability.
Media flaw information describes a media flaw in its raw or unformatted track
location. This raw definition is used internally by J.VFMT when
processing flaws and most precisely describes the actual location of the
flaw on the disk. J.VFMT converts all flaw formats to this format for
processing and converts them to the requested output format after
processing.
MPX·32 Reference Volume III
13·19
Online Disk Media Management
Media deallocation data lists the disk sectors that have media flaws or are otherwise
reserved. This data (or data lists) is recorded on the media descriptor track
in a prescribed format and is used in bad block deallocation. HSDP refers
to this information as the media flaw map and UDP/DP II uses the term
media descriptor.
Media descriptor (MD) track contains media deallocation data. It is built by the
INITIALIZE directive or the MVP and is usually located on the next-tolast track of the third-from-last cylinder. An absolute sector pointer to its
location is inserted in word 3 of track label O.
Flaw definition information is also contained elsewhere on disk in a
format different from the media deallocation data. For UDP/DP II, this
alternate format is called flaw data and is located on the MD track. For
HSDP, this is the vendor defect table entries and is located on the track
next to the MD track.
Media flaw map is a text file that contains media flaw information in ASCII. This
map can be written to SLO by specifying the DUMP or INCLUDE option
with the INITIALIZE or EDITFMAP directives. Note that the HSDP
uses this same term to refer to the contents of the MD track.
Dumped media flaw data is media flaw information written to tape or floppy disk in
a format common to all media management processors (Le., HSDP MVP,
UDP/DP II MVP, and J.VFMT). The HSDP MVP refers to this format as
the dumped vendor defect table and the UDP/DP II MVP refers to it as
saved flaw data.
13.16.2 In itializing Media
Disks can be initialized in preparation for volume formatting by using the
INITIALIZE directive. This directive writes new labels to a disk's tracks and sectors
and builds the MD track.
If media flaw information is available for the disk, J.VFMT uses it when building the
new MD track. This media flaw information may be either vendor flaw information
input to the directive or an MD track already existing on the disk.
If media flaw information is unavailable, INITIALIZE writes a worst-case data pattern
to the disk and reads the disk to check it for errors. If any additional media flaws are
detected, J.VFMT adds them to the new MD track.
The INITIALIZE directive does not initialize the two cylinders reserved for diagnostic
use or the cylinder reserved for hardware vendor use.
13·20
Volume Formatter (J.VFMT)
Online Disk Media Management
('.
13.16.2.1 Disk I/O Caution During Initialization
With UDP/DP II, tasks should not attempt disk I/O to another channel subaddress
while the controller is processing an INITIALIZE directive. Tasks attempting such I/O
may be aborted or cause the system to hang. If running on another device subaddress
on the system disk channel, hold the date/time save task (J .DTSAVE) with the
OPCOM HOLD directive before initializing a disk.
If J.VFMT detects thatI/O may be attempted to another channel subaddress, it issues
the following warning message:
PRECAUTION: ENSURE THAT ALL I/O TO OTHER DISC
SUBADDRESSES ON CHANNELxx IS QUIESCENT BEFORE
CONTINUING
When executing in interactive mode, this is followed by a prompt to continue or abort
processing. Enter Y to continue processing or N to abort with a VFOI error and
message GEN.M062. When in batch mode, the following warning message is written
to SLO and processing aborts:
BATCH MODE EXECUTION OF INITIALIZE DIRECTIVE TO
UDP/DPII MEDIA DENIED.
POTENTIAL FOR OTHER I/O ACTIVITY ON TARGET DISC CHANNEL
DETECTED.
13.16.3 Editing Media Flaw Data
Flaw definition information can be converted from one medium to another with the
EDITFMAP directive. This directive executes in two modes: read-only mode and no
I/O mode.
• Use read-only mode when the disk is present and has flaw information available for
read-only access.
• Use no I/O mode when the disk cannot or need not be read.
13.16.3.1 Read-Only Mode
To specify read-only mode, include both the DISC and DEVICE options with the
EDITFMAP directive.
With HSDP, this mode is used primarily to read vendor labels from a new disk
without writing to the disk. In addition, this mode is useful when archiving, since
vendor flaw information can be written to an external device in dumped media flaw
format. It can also be used to obtain a hardcopy listing of a disk's vendor flaw
information to compare to its vendor-supplied hardcopy listing.
MPX-32 Reference Volume III
13-21
Online Disk Media Management
With UDP and DP II, read-only mode is used primarily to perform a trial pass on the
disk's existing IMD track before using the INITIALIZE directive. Perform this trial
pass before initializing any disk verified with the diagnostic MVP. Because previous
MVP revisions for UDP/DP II vary in how they handle entries to the IMD track, the
INITIALIZE directive is not compatible with all MVP revisions. Use the EDITFMAP
directive to identify discrepancies between the MVP-built IMD track and J.VFMT's
interpretation of this information.
If discrepancies are detected, do not use the information in the MVP-built IMD track.
Instead, input either vendor flaw information or the dumped media flaw data to the
INITIALIZE directive. To do this, specify either the LOAD or INCLUDE option with
the INITIALIZE directive.
13.16.3.2 No I/O Mode
To specify no I/O mode, include the DISC option and omit the DEVICE option with
the EDITFMAP directive.
This mode is used primarily with the UDP/DP II or for removable media. Because
these cannot read vendor flaw labels, you must manually enter vendor flaw
information from a hardcopy vendor flaw liSting supplied with the disk. Enter this
vendor flaw information using a text editor and store it unnumbered in an MPX-32
file. Then use the EDITFMAP directive to process this input file and produce the
requested outputs.
No I/O mode is useful for converting media flaw information from one format to
another. For example, it can convert ASCII vendor flaw information in a file to
dumped media flaw data on a floppy disk. The floppy disk could then be used to
enter media flaw data during an SDT boot to initialize and format a single-disk UDP
system.
13.16.4 Special Considerations During SOT Boot
The EDITFMAP directive is not available during SDT boot. Any attempt to use it
causes processing to end and an error message is written to SLO.
The INITIALIZE directive is available but has the following considerations:
• the PATTERN option is not available
• the FMAP option writes SLO directly to an available line printer, instead of
spooling it to disk
• LOAD and DUMP must specify different device addresses if both options are
included with the directive
• devices specified in the LOAD and DUMP options must be online, ready, and
correctly specified before you respond CONFIRM=N
o
13-22
Volume Formatter (J.VFMT)
Online Disk Media Management
13.16.5 Managing SCSI Disks
Media management of SCSI disks differs from media management of UDP/DP II and
HSDP media as follows:
• the EDITFMAP directive is not available for SCSI disks. The intelligent SCSI disk
controller performs this function differently and independently.
• CDC Wren III, IV, and V disks can be initialized using the I.VFMf INITIALIZE
directive and a subset of its options. Options available with SCSI disks are
DEVICE, DESTROY, and DISC. Following is an example using the SCSI syntax:
INI DEV=DM7EOO DES=Y DISC=SD0700
• SCSI disks other than CDC Wren ill or IV can be initialized using the SCSI Disk
Utility's (SDUTll..'s) FORMAT directive. Refer to the SDUTll.. documentation in
Volume IV of the MPX-32 Reference Manual for this utility's syntax and use.
13.16.6 Media Flaw Map Format
Media flaw map format is an ASCII format that enables you to track the exact status
of the disk media and to perform media maintenance. The media flaw map can be
output to a file, edited, and then input to a media management function.
The media flaw map is comprised of flaw definition entries listed one per line in a
format similar to the hardcopy listing provided by the vendor. Each flaw definition
must be numerically higher than the previous one. In each definition:
• all values are decimal numbers
• an asterisk (*) indicates that the entry was flagged as a defective track by the
vendor
• a C as the first nonblank character indicates a comment line. These can be included
anywhere in a flaw map file.
• any number of blanks may precede the entry or separate the fields within it
The format for a flaw definition is:
[*] cylnum {bl,
[*]
{bl,
I hdnum {bl, I posi {bl, lien
indicates that the entry is a vendor-defined defective track
I
required field delimiter, either one or more blanks or a comma
cylnum
the cylinder number of the flaw definition
hdnum
the head number of the flaw definition
posi
the byte position of the flaw from the track index
len
the length in bytes of the flaw definition
MPX-32 Reference Volume III
13-23/13-24
14
Volume Compress (J.DSCMP)
14.1 General Description
Volwne Compress (J .DSCMP) moves resource segments on a mounted volwne to
make the volwne's free space contiguous. It is a privileged system administrator task.
J .DSCMP consolidates free disk space by moving resource segments to one end of a
mounted volwne and free space to the other end. When activated, J.DSCMP
calculates the total free space available on disk and uses it to set the size or location of
the following logical structures:
• vacate area - the area that J.DSCMP attempts to clear of resource segments. It is
located at the high end (high physical block numbers) of the disk and is equal in
size to the total free space available.
• pack area - the area where J.DSCMP moves and packs the resource segments. It
is located at the low end (low physical block numbers) of the disk and is equal in
size to the total allocated space on the disk.
• bound - separates the vacate area and the pack area. J.DSCMP calculates the
location of the bound as the highest physical block number minus the total free
space available on disk.
Mter locating the bound, J.DSCMP compresses a volume in two phases.
14.1.1
Phase One
In phase one, J.DSCMP attempts to fill the available contiguous free space in the pack
area with resource segments from the vacate area. To do this, J .DSCMP compiles a V
list (list of the resource segments in the vacate area), ordered from largest to smallest.
For each segment in the V list, if there is sufficient contiguous free space in the pack
area, J .DSCMP moves the segment below the bound and removes the segment from
the V list. If the contiguous free space is insufficient, the segment remains in the V
list for phase two. Phase one ends when J.DSCMP reaches the end of the V list.
If the V list is empty, compression is complete. Otherwise, phase two begins.
14.1.2 Phase Two
In phase two, J.DSCMP moves segments within the pack area to the low end of the
disk until sufficient free space is available to move a segment in the V list below the
bound. This consolidates resource segments at the low end of the disk and free space
above the bound. Phase two continues until the V list is empty or the migrating free
space moves above the segment with the highest physical address in the V list.
MPX-32 Reference Volume III
14-1
General Description
During compress, J.DSCMP does not move a resource segment if the segment:
•
•
•
•
•
•
•
•
•
is allocated
is not a permanent file (Le., is a static or dynamic partition)
was created with a specific start sector
contains the RD for a directory
contains the default image
is being restored
is a fast file
has an entry in the memory resident descriptor table (MDT)
is larger than the available free space in the pack area
The bound is adjusted for entries in the SMAP deallocation file. For every segment
entry that is within the vacate area, the bound is lowered by that segment size.
J.DSCMP is a multi-copy task. However, only one copy at a time should be run on
the same volume.
J.DSCMP uses standard MPX-32 I/O services to manipulate the data on the disk. All
allocations and I/Os are performed in the wait mode with inunediate denial.
14.1.3 Performance
Following is a list of performance considerations:
• J.DSCMP can be run while the volume is in use. However, compression is most
effective when volume use is minimal.
• When compressing the system disk, compression results are better if M.ERR,
M.PRJCT, M.ACCNT and M.KEY are not allocated. To do this, set control switch
4 when rebooting the system.
• Compression results are better if the disk to be compressed does not contain the
swap file. Remove the swap file by specifying a swap file size of 0 at SYSGEN.
14.2 Logical File Code Assignments
Logical file codes required by J.DSCMP are summarized in Table 14-1.
Table 14-1
Volume Compress Logical File Code Assignments
14-2
Description
Logical
File Code
Default Assignments
for J.DSCMP
Error messages
Informative messages
ERR
OUT
$ASSIGN ERR TO LFC=UT
$ASSIGN OUT TO LFC=UT
Volume Compress (J.DSCMP)
Using Volume Compress
(
14.3 Using Volume Compress
J .DSCMP is called from TSM.
Syntax
$J.DSCMP volname [STAT I [LlST][NOMOVE]]
is the name of the mounted volume to be compressed
STAT
displays the current disk status. The volume is not compressed.
LIST
requests a list of moved segments (V and P segments) while compressing
the volume. See Figure 14-1 for a sample list.
NOMOVE requests a list of nonmovable segments (N segments) while compressing
the volume. The segments remain in the vacate area.
volname
14.3.1
Disk Status Report
J.DSCMP writes a disk status report to LFC OUT before and after compressmg the
volume or when the STAT option is specified in the J.DSCMP command. The disk
status is displayed in the following format:
VOLUME= volume
(
TOTAL NUMBER OF BLOCKS (DEC)
blocks
TOTAL FREE SPACE (DEC,PCT OF TOT)
total tpercent
LARGEST CONTIGUOUS FREE AREA (DEC, PCT OF FREE) free
fpercent
blocks
total
tpercent
free
fpercent
is the
is the
is the
is the
is the
area.
decimal number of blocks on the disk
decimal number of free blocks on disk
percent of blocks on disk that are free
decimal number of blocks in the largest contiguous free area
percent of free blocks on disk that are in the largest contiguous free
100 indicates that all free space is contiguous.
14.3.2 Segment Report
If the LIST and/or NOMOVE options are specified. J.DSCMP displays a list of
moved and/or nonmovable segments during volume compression. For each resource
segment, the segment report lists the following:
• type (TYP) code that identifies whether and where the segment was moved
• original beginning and end sector numbers
• post-move beginning and end sector numbers
• RD address
• segment definition of the RD that was moved
• directory and resource where segment is located
MPX-32 Reference Volume III
14-3
Using Volume Compress
Figure 14-1 shows a sample segment report that was requested specifying both LIST
and NOMOVE. If only LIST is specified, the report lists only the V and P segments.
If NOMOVE is specified, the report lists the N segments.
NEW END
TYP
ORIG BEG
ORIG END
NEW BEG
N
00013FEC
0001404F
MED. MAN. SEGMENT
N
00014050
00014117
MED. MAN. SEGMENT
N
00014118
0001417B
MED. MAN. SEGMENT
N
000012E6
000012EF
NOT PERM. FILE
RD ADDR
SEG
00000026
01
DIRECTORY
RESOURCE
SOURCE
V
0000126E
000012A5
OOOOOFOE
00000F45
00000024
01
TEST.02
P
00000E06
00000E4D
00000DD6
00000E1D
00000015
01
OBJECT E
OH.PTRAC
P
00000E4E
00000Ec5
00000E1E
00000E95
00000016
01
OBJECT E
OH.REMM
CH.TAMM
P
00000EC6
OOOOOFOD
00000E96
OOOOOEDD
00000017
01
OBJECT E
OH.REXS
P
OOOOOFOE
00000F45
OOOOOEDE
00000F15
00000024
01
TEST.02
OH.TAMM
P
00000F46
00000F85
00000F16
00000F55
00000019
01
OBJECT E
OH.VOMM
V
000012A6
000012E5
00000F56
00000F95
00000025
01
TEST. 02
OH.VOMM
P
00000FB6
OOOOOFFD
00000F96
OOOOOFDD
0000001B
01
TEST.01
OH.PTRAC
P
OOOOOFFE
00001075
OOOOOFDE
00001055
0000001c
01
TEST.01
OH.REMM
P
00001076
000010BD
00001056
0000109D
0000001D
01
TEST.01
OH.REXS
P
000010BE
000010F5
0000109E
000010D5
0000001E
01
TEST.01
OH.TAMM
P
000010F6
00001135
000010D6
00001115
0000001F
01
TEST.01
OH.VOMM
V
00001226
0000126D
00001116
0000115D
00000023
01
TEST.02
OH.REXS
Figure 14-1
J.DSCMP Segment Report
14-4
Volume Compress (J.DSCMP)
,1-"',
'~j
Using Volume Compress
(
14.3.3 TYP Codes
After compression, J.DSCMP identifies each resource segment with one of the
following TYP codes:
• N - Nonmovable segment that remains in the vacate area. J.DSCMP lists the
reason why the segment was not moved in the NEW BEG column.
Message
Means that the segment
A DEFAULT IMAGE
A FAST FILE
A MDT FILE
A RESTORING FILE
FAIL CREATE TEMP
FAIL TO OPEN FILE
INVALID RD ADDRESS RD
MED. MAN. SEGMENT
contains a default image
is a fast file
has an entry in the MDT
is being restored
temporary file couldn't be created
cannot be opened by J .DSCMP
address doesn't match address in RID
used by Media Management
(includes bad sectors)
is not a permanent file
was created with a specific start sector
definition changed since the V list
was created
temporary file is not large enough
NOT PERM. FILE
START SECTOR FILE
WRONG SEGMENT-DEF
WRONG TEMP SIZE
• V - V list segment that was successfully moved from the vacate area to the pack
area. The new segment definition (start and end sectors) is always below the
bound.
• P - segment moved in phase two when consolidating segments towards the low
end of the disk. If sufficient free space is not available in the pack area, P moves
occur above the bound in the vacate area.
MPX·32 Reference Volume 11\
14·5
Error Messages
:(~"'\
..
..
14.4 Error Messages
)/
J.DSCMP displays the following error messages on the terminal:
FIRST PARAMETER MUST BE VOLUME NAME
SPECIFIED VOLUME IS NOT MOUNTED
SYSTEM ADMINISTRATOR ATTRIBUTE IS REQDIRED TO RUN THIS TASK
TOO MANY ARGUMENTS OR INVALID ARGUMENT SPECIFIED
UNABLE TO READ VOLUME DESCRIPTOR
UNABLE TO OBTAIN EXTENDED MEMORY
UNABLE TO READ SMAP DESCRIPTOR
UNABLE TO READ SMAP DEALLOCATION FILE DESCRIPTOR
UNABLE TO READ GENERAL ALLOCATABLE RESOURCE DESCRIPTORS'
DESCRIPTOR
UNABLE TO ASSIGN SMAP OR READ ERROR ON SMAP
The following messages display when an I/O error occurs while correcting a previous
I/O error. Because the specified resource segment is no longer marked as allocated in
the SMAP, it is susceptible to allocation to another resource if volume cleanup is not
performed.
COMPRESSION TERMINATED DUE TO FATAL WRITE ERROR ON SEGMENT x (DECIMAL)
OF PATH @pathname
FATAL ERROR.
@pathname
x
path name
J.DSCMP SUSPENDED UNTIL REPAIR AND/OR REBOOT PERFORMED.
is the segment where the error occurred
is the volume, directory, and file where the error occurred
If this occurs, J.DSCMP remains in suspension and retains exclusive allocation of all
relevant disk data until the system administrator performs a volume clean-up with
control switch 7 not set. This corrects the file overlap by deleting the temporary file's
resource descriptor without modifying the segment definition.
Note: If J.DSCMP exits or is deleted, the space used by the permanent file is freed.
o
14·6
Volume Compress (J.DSCMP)
A
MPX-32 Device Access
A.1 Description
Throughout the MPX-32 Reference Manual, the generic descriptor devmnc indicates
that a device can be specified.
Under MPX-32, device addresses are specified using a combination of three levels of
identification. They are device type, device channel/controller address, and device
address/subaddress.
A device can be specified using the generic device type mnemonic only, which results
in allocation of the first available device of the type requested. Device type
mnemonics are listed in Table A-I.
A second method of device specification is achieved by using the generic device type
mnemonic and specifying the channel/controller address. This results in allocation of
the first available device of the type requested on the specified channel or controller.
The third method of device selection requires specification of the device type
mnemonic, channel/controller, and device address/subaddress. This method allows
specification of a particular device.
(
"
--
MPX-32 Reference
A-1
Description
Table A-1
Device Type Mnemonics and Codes
Device
Type
Code
Device
Type
Mnemonic
()()
CT
01
02
03
DC
DM
DF
04
MT
05
M9
M7
CR
LP
06
08
OA
OB
OC
OD
OE
OF
10
PT
TY
CT
FL
NU
1B
CA
UO
UI
U2
U3
U4
U5
U6
U7
U8
U9
LF
N/A
ANY
11
12
13
14
15
16
17
18
19
IA
Device Description
Operator console (not assignable)
Any disk unit except memory disk
Any moving head or memory disk
Any fixed head disk
Any magnetic tape unit
Any 9-track magnetic tape unit*
Any 7-track magnetic tape unit*
Any card reader
Any line printer
Any paper tape reader-punch
Any teletypewriter (other than console)
Operator console (assignable)
Floppy disk
Null device
Communications adapter (binary synchronous/asynchronous)
Available for user-defined applications
Available for user-defined applications
Available for user-defined applications
Available for user-defined applications
Available for user-defined applications
Available for user-defined applications
Available for user-defined applications
Available for user-defined applications
Available for user-defined applications
Available for user-defined applications
Line printer/floppy controller (used only with SYSGEN)
Any nonftoppy disk except memory disk
* When both 7- and 9-track magnetic tape units are configured, the designation
must be 7-track.
o
A-2
MPX-32 Device
Access
Special Device Specifications and Handling
(~
A.2 Special Device Specifications and Handling
A.2.1 Magnetic Tape/Floppy Disk
For magnetic tape and floppy disks, unblocking, density, a reel identifier, and
multivolume number (magnetic tape only) can be included in the device specification.
Syntax
ifc TO DEV=devmnc [BLOCKED={Y 1N}]
[DENSITY={N 1PIG 1800 11600 16250}] [ID=id] [MULTIVOL=number]
$ASSIGN
ifc
is a 1- to 3-character logical file code
oEV=devmnc
devmnc is the device specification of a configured peripheral device (see
the Description section)
[BLOCKED={ YIN}]
if Y is specified, medium is blocked. If N is specified, medium is not
blocked. If not specified the default is blocked.
[DENSITY={N 1PIG 1800 11600 16250}]
specifies density of high speed XIO tape. If not specified, the default is
6250 bpi. Values are as follows:
[lD=id]
Value
Description
N or 800
P or 1600
G or 6250
indicates 800 bpi nonretum to zero inverted (NRZI).
indicates 1600 bpi phase encoded (PE).
indicates 6250 bpi group coded recording (GCR).
This is the default.
id specifies a 1- to 4-character identifier for the reel. If not specified, the
default is SCRA (scratch).
[MULTIVOL=number]
number is a volume number. If multivolume tape, number must be
specified. If not specified, the default is not multivolume (0). This option
is not valid for use with floppy disks.
When the task that has an assignment to tape is activated, a mount message indicates
the name of the task and other infonnation on the system console:
MOUNT reel VOL volume ON devmnc
TASK taskname, taskno REPLY R, H, A, OR DEVICE:
jobno
reel
MPX-32 Reference
specifies a 1- to 4-character identifier for the reel. If not specified, the
default is SCRA (Scratch).
A-3
Special Device Specifications and Handling
volume
identifies the volume number to mount if multivolume tape
devmnc
is the device mnemonic for the tape unit selected in response to the
assignment. If a specific channel and subaddress are supplied in the
assignment, the specific tape drive is selected and named in the message;
otherwise, a unit is selected by the system and its complete address is
named in the message.
jobno
identifies the job by job number if the task is part of a batch job
taskname
is the name of the task to which the tape is assigned
taskno
is the task number assigned to the task by the system
R,H,A, OR DEVICE
the device listed in the message can be allocated and the task resumed
(R), a different device can be selected (DEVICE), the task can be aborted
(A), or the task can be held with the specified device deallocated (H). If
an R response is given and a high speed XIO tape drive is being used, its
density can be changed when the software select feature is enabled on the
tape unit front panel. If specified, it overrides any specification made at
assignment. Example usage: RN, R1600. etc.
Note: Do not insert blanks or commas.
Response:
To indicate the drive specified in the mount message is ready and proceed with the
task, mount the tape on the drive and type R (resume). optionally followed by a
density specification if the drive is a high speed XIO tape unit. To abort the task. type
A (abort). To hold the task and deallocate the specified device, type H (hold). The
task can be resumed by the OPCOM CONTINUE directive; at which time. a tape
drive is selected by the system and the mount message redisplayed.
To select a tape drive other than the drive specified in the message. enter the
mnemonic of the drive to be used. Any of the three levels of device identification can
be used. The mount message is reissued. Mount the tape and type R if satisfactory.
or if not satisfactory. abort. override. or hold as described.
Examples of the three methods of device specification follow:
Type 1 • Generic Device Class
$ASSIGN OUT TO DEV=M9 MUL=l ID=MVOL
In this example. the device assigned to logical file code (LFC) OUT is any 9-track
tape unit on any channel. The multivolume reel number is 1. The reel identifier is
MVOL and the tape is blocked.
o
A·4
MPX·32 Device Access
Special Device Specifications and Handling
(
Type 2 • Generic Device Class and Channel/Controller
$ASSIGN OUT TO DEV=M910 ID=MVOL BLO=N
In this example, the device assigned to logical file code (LFC) OUT is the first
available 9-track tape unit on channel 10. The specification is invalid if a 9-track
tape unit does not exist on the channel. The reel identifier is MVOL. This is not a
multivolume tape and is unblocked.
Type 3 • Specific Device Request
$ASSIGN OUT TO DEV=M91001
In this example, the device assigned to logical file code (LFC) OUT is the 9-track
tape unit 01 on channel 10. The specification is invalid if unit 01 on channel 10 is
not a 9-track tape. The tape reel identifier is SCRA. The tape is blocked and is not
multivolume.
A.2.2 Temporary Disk Space
For a temporary disk file the following can be specified: size, blocking, printing or
punching, and access.
Syntax
$ASSIGN lfc TO TEMP[=(volname)] [ACCESS=([READ] [WRITE] [MODIFY] [UPDATE] [APPEND])]
[BLOCKED={ V IN}] [PRINT I PUNCH] [SIZE=blocks]
lfc
is a 1- to 3-character logical file code
TEMP[=(volname)]
volname is the 1- to 16-character volume name where temporary space is
allocated. If not specified, the default is the current working volume or
any public volume.
[ACCESS=([READ] [WRITE] [MODIFY] [UPDATE] [APPEND])]
specifies the types of access for the file. If not specified, the default is the
access specified at file creation.
[BLOCKED={ V IN}]
if Y is specified, the file is blocked. If N is specified, the file is
unblocked. If not specified, the default is blocked.
[PRINT I PUNCH]
indicates the file is to be printed (PRINT) or punched (PUNCH) after
de assignment
[SIZE=blocks]
blocks is the number of 192-word blocks required. If not specified, the
default is 16 blocks.
MPX·32 Reference
A·5
Special Device Specifications and Handling
Examples
In the following example, the device assigned to logical file code (LFC) OUT is the
current working volume or any public volume and the file prints to the SLO device
after deassignment.
AS OUT TO TEM PRI
The following example designates the system volume as the device for the temporary
blocked fJIe.
AS OUT TO TEMP=(SYSTEM) BLO=Y
A.3 GPMC Devices
GPMC/GPDC device specifications follow the general structure just described. The
terminal at subaddress 04 on GPMC 01 whose channel address is 20 would be
identified as follows:
$AS DEV TO DEV=TY2004
A.4 Null Device
A special device type, NU, is available for null device specifications. Files accessed
using this device type generate an end-of-file (EOF) when a read is attempted and
normal completion when a write is attempted.
A.S
System Console
Logical file codes are assigned to the system console by using the device type
cr.
A.6 Special System Files
There are four special mnemonics provided for access to special system files: SLO,
SBO, SGO and SYC. These are assigned with the $ASSIGN statement, as in:
$ASSIGN OUT TO SLO
For nonbatch tasks, SLO and SBO files are allocated dynamically by the system and
used to disk buffer output to a device selected automatically. For batch tasks, use of
SLO and SBO fJIes is identical, except that automatic selection of a device can be
overridden by assigning a specific file or device.
1 (...
-- \ ,
Y
A-6
MPX-32 Device Access
Samples
(
A.7 Samples
A description of device selection possibilities is constructed as follows:
Disk
DC
DM
DM08
DM0801
DMOO02
DF
DF04
DF0401
Any disk except memory disk
Any moving head or memory disk
Any moving head disk on channel 08
Moving head disk 01 on channel 0 8
Memory disk 02 on channel 00
Any fixed head disk
Any fixed head disk on channel 04
Fixed head disk 01 on channel 0 4
MT
M9
M910
M91002
Any magnetic tape
Any 9-track magnetic tape
Any 9-track magnetic tape on channel 10
9-track magnetic tape 02 on channel 10
Tape
card Equipment
(:
CR
CR78
CR7800
Any card reader
Any card reader on channel 78
Card reader 00 on channel 78
Line Printer
LP
LP7A
LP7AOO
LP7EAO
MPX-32 Reference
Any line printer
Any line printer on channel 7A
Line printer 00 on channel 7A
Serial printer AO on ACM channel 7E
A-7/A-8
("
B
B.1
(
System Services Cross-Reference
Macro Name Listing
Volume I
Ref.Manual
Section
Macro
Description
SVC
Module,
E.P.
M.ACTV
Activate Task
I,X'52'
H.REXS,15
6.2
M_ACTV
Activate Task
1,x'52'
H.REXS,15
7.2
M.ADRS
Memory Address
Inquiry
I ,X '44'
H.REXS,3
6.2
M_ADRS
Memory Address
Inquiry
1,x'44'
H.REXS,3
7.2
M_ADVANCE
Advance Record
Advance File
1,x'33'
I,X'34'
H.IOCS,7
H.IOCS,8
7.2
7.2
M.ALOC
Allocate File or
Peripheral Device
1,x'40'
H.MONS,21
6.4
M.ANYW
Wait for Any No-wait
Operation Complete,
Message Interrupt,
or Break Interrupt
I,X'7C'
H.REXS,37
6.2
M_ANYWAIT
Wait for Any No-wait
Operation Complete,
Message Interrupt,
or Break Interrupt
I,X'7C'
H.REXS,37
7.2
M_ASSIGN
Assign and Allocate
Resource
2,x'52'
H.REXS,21
7.2
M.ASSN
Assign and Allocate
Resource
2,X'52'
H.REXS,21
6.2
M.ASYNCH
Set Asynchronous
Task Interrupt
Set Asynchronous
Task Interrupt
End Action Wait
I,X'IC'
H.REXS,68
6.2
I,X'IC'
H.REXS,68
7.2
1,x'IO'
H.EXEC,40
7.2
M.BACK
Backspace Record
Backspace File
I,X'35'
I,X'36'
H.IOCS,9
H.IOCS,l9
6.2
6.2
M_BACKSPACE
Backspace Record
Backspace File
I,X'35'
I,X'36'
H.IOCS,9
H.IOCS,l9
7.2
7.2
M.BATCH
Batch Job Entry
2,X'55'
H.REXS,27
6.2
M_BATCH
Batch Job Entry
2,x'55'
H.REXS,27
7.2
M_ASYNCH
M_AWAITACTION
C",
MPX-32 Reference
B-1
Macro Name Listing
Volume I
Ref.Manual
Section
Macro
Description
SVC
Module,
E.P.
M.BBTIM
Acquire Current
Date/fime in Byte
Binary Format
2,X'SO'
H.REXS,74
6.2
M_BBTIM
Acquire Current
Date/fime in Byte
Binary Format
2,X'SO'
H.REXS,74
7.2
M.BORT
Abort Specified Task
Abort Self
Abort With Extended
Message
1,x'S6'
1,x'S?'
I,X'62'
H.REXS,19
H.REXS,20
H.REXS,28
6.2
6.2
6.2
M_BORT
Abort Specified
Task
Abort Self
Abort With Extended
Message
1,x'S6'
H.REXS,19
7.2
I,X'S?'
1,x'62'
H.REXS,20
H.REXS,28
7.2
7.2
M.BRK
Break/fask
Interrupt Link/Unlink
I,X'6E'
H.REXS,46
6.2
M_BRK
Break/fask
Interrupt Link/Unlink
I,X'6E'
H.REXS,46
7.2
M.BRKXIT
Exit From Task
Interrupt Level
I,X'70'
H.REXS,48
6.2
M_BRKXIT
Exit From Task
Interrupt Level
N/A
N/A
7.2
M.BTIM
Acquire Current
Date/fime in
Binary Format
2,X'SO'
H.REXS,74
6.2
M_BTIM
Acquire Current
Date/fime in
Binary Format
2,x'SO'
H.REXS,74
7.2
M.CDJS
Submit Job from
Disc File
1,x'61'
H.MONS,27
6.4
M_CHANPROGFCB
Execute Channel
Program File
Control Block
N/A
N/A
7.2
M.CLOSER
Close Resource
2,x'43'
H.REMM,22
6.2
M_CLOSER
Close Resource
2,X'43'
H.REMM,22
7.2
M.CLSE
Close File
1,x'39'
H.IOCS,23
6.2
M_CLSE
Close File
I,X'39'
H.IOCS,23
7.2
Ie:
/--",
~/
C
B-2
System Services Cross-Reference
Macro Name Listing
(-
(
Volume I
Ref.Manual
Section
Macro
Description
SVC
Module,
E.P.
M.CMD
Get Command Line
2,X'61'
H.REXS,88
6.2
M_CMD
Get Command Line
2,X'6l'
H.REXS,88
7.2
M.CONABB
Convert ASCII
Daterrime to
Byte Binary Fonnat
2,X'5l'
H.REXS,75
6.2
M_CONABB
Convert ASCII
Daterrime to
Byte Binary Fonnat
2,X'51'
H.REXS,75
7.2
M.CONADB
Convert ASCII
Decimal to Binary
I,X'28'
H.TSM,7
6.2
M_CONADB
Convert ASCII
Decimal to Binary
I,X'28'
H.TSM,7
7.2
M.CONAHB
Convert ASCII
Hex to Binary
I,X'29'
H.TSM,8
6.2
M_CONAHB
Convert ASCII
Hex to Binary
I,X'29'
H.TSM,8
7.2
M.CONASB
Convert ASCII
Daterrime to
Standard Binary
2,X'51'
H.REXS,75
6.2
M_CONASB
Convert ASCII
Daterrime to
Standard Binary
2,X'51'
H.REXS,75
7.2
M.CONBAD
Convert Binary to
ASCII Decimal
I,X'2A'
H.TSM,9
6.2
M_CONBAD
Convert Binary to
ASCII Decimal
I,X'2A'
H.TSM,9
7.2
M.CONBAF
Convert Binary
Daterrime to
ASCII Fonnat
2,X'51'
H.REXS,75
6.2
M_CONBAF
Convert Binary
Daterrime to
ASCII Fonnat
2,X'51'
H.REXS,75
7.2
M.CONBAH
Convert Binary to
ASCII Hex
I,X'2B'
H.TSM,lO
6.2
M_CONBAH
Convert Binary to
ASCII Hex
I,X'2B'
H.TSM,lO
7.2
M.CONBBA
Convert Byte Binary
Daterrime to ASCII
2,X'51'
H.REXS,75
6.2
(0MPX-32 Reference
8-3
Macro Name Listing
(-",\
Macro
Description
SVC
Module,
E.P.
Volume I
Ref.Manual
Section
M_CONBBA
Convert Byte Binary
Date/Time to ASCII
2,X'51'
H.REXS,75
7.2
M.CONBBY
2,x'51'
Convert Binary
Date/Time to Byte Binary
H.REXS,75
6.2
M_CONBBY
2,x'51'
Convert Binary
Date/Time to Byte Binary
H.REXS,75
7.2
M.CONBYB
Convert Byte Binary
Date/Time to Binary
2,x'51'
H.REXS,75
6.2
M_CONBYB
Convert Byte Binary
Daterrime to Binary
2,x'51'
H.REXS,75
7.2
M.CONN
Connect Task to
Interrupt
I,X'4B'
H.REXS,lO
6.2
M_CONN
Connect Task to
Interrupt
I,X'4B'
H.REXS,lO
7.2
M_CONSTRUCTPATH Reconstruct
Pathname
2,x'2F'
H.VOMM,16 7.2
M_CONVERTTIME
Convert Time
2,x'51'
H.REXS,75
7.2
M.CPERM
Create Permanent
File
2,X'20'
H.VOMM,1
6.2
M.CREATE
Create Permanent
File
I,X'75'
H.FISE,12
6.4
M_CREATEFCB
Create File Control
Block
N/A
N/A
7.2
M_CREATEP
Create Permanent File
2,x'20'
H.VOMM,1
7.2
M_CREATET
Create Temporary File
2,X'21'
H.VOMM,2
7.2
M.CI1M
Convert System
Date/Time Format
2,x'51'
H.REXS,75
6.2
M_CTIM
Convert System
Date/Time Format
2,X'51'
H.REXS,75
7.2
M.CWAT
System Console Wait
l,X'3D' H.IOCS,26
6.2
M_CWAT
System Console Wait
1,X'3D' H.IOCS,26
7.2
M.DALC
Deallocate File
or Peripheral Device
1,X'41'
H.MONS,22
6.4
M.DASN
Deassign and
Deallocate Resource
2,X'53'
H.REXS,22
6.2
~)
"-~,,
"-J
0
8-4
System Services Cross-Reference
Macro Name Listing
(
(~
Volume I
Ref.Manual
Section
Macro
Description
SVC
Module,
E.P.
M.DATE
Date and Time
Inquiry
I,X'IS'
H.REXS,70
6.2
M_DATE
Date and Time
Inquiry
I,X'IS'
H.REXS,70
7.2
M_DEASSIGN
Deassign and
Deallocate Resource
2,x'S3'
H.REXS,22
7.2
M.DEBUG
Load and Execute
Interactive Debugger
I,x'63'
H.REXS,29
6.2
M_DEBUG
Load and Execute
Interactive Debugger
I,X'63'
H.REXS,29
7.2
M.DEFT
Change Defaults
2,X'27'
H.VOMM,8
6.2
M_DEFT
Change Defaults
2,X'27'
H.VOMM,8
7.2
M.DELETE
Delete Permanent
File or Non-SYSGEN
Memory Partition
I,x'77'
H.FISE,I4
6.4
M_DELETER
Delete Resource
2,X'24'
H.VOMM,S
7.2
M.DELR
Delete Resource
2,X'24'
H.VOMM,S
6.2
M.DELTSK
Delete Task
I,X'SA'
H.REXS,31
6.2
M_DELTSK
Delete Task
1,x'SA'
H.REXS,31
7.2
M.DEVID
Get Device Mnemonic
or Type Code
Get Device Mnemonic
or Type Code
1,x'14'
H.REXS,71
6.2
I,X'I4'
H.REXS,71
7.2
M.DFCB
Create File Control
Block
N/A
N/A
5.9.1
M.DIR
Create Directory
2,X'23'
H.VOMM,4
6.2
M_DIR
Create Directory
2,X'23'
H.VOMM,4
7.2
M.DISCON
Disconnect Task
from Interrupt
I,X'SD'
H.REXS,38
6.2
M_DISCON
Disconnect Task
from Interrupt
I,X'SD'
H.REXS,38
7.2
M_DISMOUNT
Dismount Volume
2,X'4A'
H.REMM,19
7.2
M.DLTT
Delete Timer Entry
I,X'47'
H.REXS,6
6.2
M_DLTT
Delete Timer Entry
I,X'47'
H.REXS,6
7.2
M.DMOUNT
Dismount Volume
2,X'4A'
H.REMM,19
6.2
M_DEVID
(
MPX·32 Reference
8·5
Macro Name Listing
8·6
Macro
Description
SVC
Module,
E.P.
Volume I
Ref.Manuai
Section
M.DSMI
Disable Message
Task Interrupt
I,X'2E'
H.REXS,S7
6.2
M_DSMI
Disable Message
Task Interrupt
1,x'2E'
H.REXS,S7
7.2
M.DSUB
Disable User
Break Interrupt
1,x'12'
H.REXS,73
6.2
M_DSUB
Disable User
Break Interrupt
I,X'l2'
H.REXS,73
7.2
M.DUMP
Memory Dump Request
1,x'4F'
H.REXS,12
6.2
M_DUMP
Memory Dump Request
1,x'4F'
H.REXS,12
7.2
M.EAWAIT
End Action Wait
1,x'ID'
H.EXEC,40
6.2
M.ENMI
Enable Message
Task Interrupt
1,x'2F'
H.REXS,S8
6.2
M_ENMI
Enable Message
Task Interrupt
1,x'2F'
H.REXS,S8
7.2
M.ENUB
Enable User
Break Interrupt
I,X'l3'
H.REXS;72
6.2
M_ENUB
Enable User
Break Interrupt
I,X'l3'
H.REXS,72
7.2
M.ENVRMT
Get Task
Environment
2,x'5E'
H.REXS,8S
6.2
M_ENVRMT
Get Task
Environment
2,X'SE'
H.REXS,8S
7.2
M.EXCL
Free Shared Memory
I,X'79'
H.ALOC,14
6.4
M.EXCLUDE
Exclude Memory
Partition
2,x'41'
H.REMM,14
6.2
M_EXCLUDE
Exclude Shared
Image
2,x'41'
H.REMM,14
7.2
M.EXIT
Terminate Task
Execution
1,x'SS'
H.REXS,IS
6.2
M_EXIT
Terminate Task
Execution
1,x'SS'
H.REXS,18
7.2
M.EXTD
Extend File
2,x'2S'
H.VOMM,6
6.2
M_EXTENDFILE
Extend File
2,X'2S'
H.VOMM,6
7.2
M_EXTSTS
Exit With Status
2,X'SF'
H.REXS,86
7.2
MFADD
Permanent File
Address Inquiry
I,X'43'
H.MONS,2
6.4
:
(-"
J
'
:
\-,~
0
System Services Cross-Reference
Macro Name Listing
(
•
(
Macro
Description
SVC
Module,
E.P.
Volume I
Ref.Manual
Section
M.FD
Free Dynamic Extended
Indexed Data Space
I,X'6A'
H.REMM,9
6.2
M.FE
Free Dynamic Task
Execution Space
I,X'68'
H.REMM,11
6.2
M.Fll...E
Open File
I,X'30'
H.IOCS,1
6.4
M_FREEMEMBYTES
Free Memory in Byte
Increments
2,X'4C'
H.REMM,29
7.2
M.FSLR
Release
Synchronization File Lock
I,X'24'
H.FISE,25
6.4
M.FSLS
Set Synchronization
File Lock
I,X'23'
H.FISE,24
6.4
M.FWRD
Advance Record
Advance File
I,X'33'
I,X'34'
H.IOCS,7
H.IOCS,S
6.2
6.2
M.FXLR
Release Exclusive
File Lock
I,X'22'
H.FISE,23
6.4
M.FXLS
Set Exclusive
File Lock
I,X'21'
H.FISE,22
6.4
M.GADRL
Get Address Limits
I,X'65'
H.REXS,41
6.2
M.GADRL2
Get Address Limits
2,X'7B'
H.REXS,SO
6.2
M.GD
Get Dynamic
Extended Data Space
Get Dynamic
Extended Discontiguous
Data Space
I,X'69'
H.REMM,S
6.2
2,X'7C'
H.MEMM,9
6.2
M.GDD
M.GE
Get Dynamic Task
Execution Space
I,X'67'
H.REMM,lO
6.2
M_GETCTX
Get User Context
2,X'70'
H.EXEC,41
7.2
M.GETDEF
Get Terminal Function
Definition
2,X'7A'
H.TSM,15
6.2
M_GETDEF
Get Terminal Function
Definition
2,X'7A'
H.TSM,15
7.2
M_GETMEMBYTES
Get Memory in Byte
Increments
2,X'4B'
H.REMM,2S
7.2
M_GETTIME
Get Current Date
and Time
2,X'50'
H.REXS,74
7.2
M.GMSGP
Get Message
Parameters
1,X'7A'
H.REXS,35
6.2
(
MPX-32 Reference
8-7
Macro Name Listing
Macro
Description
SVC
Module,
E.P.
Volume I
Ref.Manual
Section
M_GMSGP
Get Message
Parameters
I,X'7A'
H.REXS,35
7.2
M.GRUNP
Get Run Parameters
I,X'7B'
H.REXS,36
6.2
M_GRUNP
Get Run Parameters
I,X'7B'
H.REXS,36
7.2
M.GTIM
Acquire System
Dateffime in
Any Format
2,x'50'
H.REXS,74
6.2
M_GTIM
Acquire System
Dateffime in
Any Format
2,x'50'
H.REXS,74
7.2
M.GTSAD
Get TSA Start Address
2,X'7D'
H.REXS,91
6.2
M_GTSAD
Get TSA Start Address
2,X'7D'
H.REXS,91
7.2
M.HOLD
Program Hold
Request
I,X'58'
H.REXS,25
6.2
M_HOLD
Program Hold
Request
1,x'58'
H.REXS,25
7.2
M.ID
Get Task Number
I,X'64'
H.REXS,32
6.2
M_ID
Get Task Number
1,x'64'
H.REXS,32
7.2
M.INCL
Get Shared Memory
I,X'72'
H.ALOC,13
6.4
M.INCLUDE
Include Memory
Partition
2,X'40'
H.REMM,12
6.2
M_INCLUDE
Include Shared
Image
2,x'40'
H.REMM,12
7.2
M_INQUIRER
Resource Inquiry
2,X'48'
H.REMM,27
7.2
M.INQUIRY
Resource Inquiry
2,X'48'
H.REMM,27
6.2
M.INT
Activate Task
Interrupt
1,X'6F'
H.REXS,47
6.2
M_INT
Activate Task
Interrupt
1,X'6F'
H.REXS,47
7.2
M.IPUBS
Set IPU Bias
2,X'SB'
H.REXS,82
6.2
M_IPUBS
Set IPU Bias
2,X'SB'
H.REXS,82
7.2
M_LIMITS
Get Base Mode
Task Address Limits
2,x'SD'
H.REXS,84
7.2
M.LOC
Read Descriptor
2,X'2C'
H.VOMM,13
6.2
M.LOCK
Set Exclusive
Resource Lock
2,X'44'
H.REMM,23
6.2
I'~'"
'lj
(~ ,
J
,
8-8
System Services Cross-Reference
Macro Name Listing
(
(~
Macro
Description
SVC
Module,
E.P.
Volume I
Ref. Manual
Section
M_LOCK
Set Exclusive
Resource Lock
2,X'44'
H.REMM,23
7.2
M.LOG
Permanent File Log
I,X'73'
H.MONS,33
6.4
M.LOOR
Log Resource
or Directory
2,X'29'
H.VOMM,lO
6.2
M_LOGR
Log Resource
or Directory
2,X'29'
H.VOMM,10
7.2
M.MEM
Create Memory
Partition
2,X'22'
H.VOMM,3
6.2
M_MEM
Create Memory
Partition
2,X'22'
H.VOMM,3
7.2
M.MEMB
Get Memory in
Byte Increments
2,X'4B'
H.REMM,28
6.2
M.MEMFRE
Free Memory in
Byte Increments
2,x'4C'
H.REMM,29
6.2
M.MOD
Modify Descriptor
2,X'2A'
H.VOMM,ll
6.2
M_MOD
MOdify Descriptor
2,X'2A'
H.VOMM,11
7.2
M.MODU
Modify Descriptor
User Area
2,X'31'
H.VOMM,26
6.2
M_MODU
Modify Descriptor
User Area
2,X'31'
H.VOMM,26
7.2
M.MOUNT
Mount Volume
2,X'49'
H.REMM,17
6.2
M_MOUNT
Mount Volume
2,X'49'
H.REMM,17
7.2
M.MOVE
Move Data to User
Address
2,X'62'
H.REXS,89
6.2
M_MOVE
Move Data to User
Address
2,x'62'
H.REXS,89
7.2
M.MYID
Get Task Number
I,X'64'
H.REXS,32
6.2
M_MYID
Get Task Number
I,X'64'
H.REXS,32
7.2
M.NEWRRS
Reformat RRS Entry
2,X'54'
H.REXS,76
6.2
M.OLAY
Load Overlay Segment
Load and Execute
Overlay
I,X'50'
I,X'51'
H.REXS,13
H.REXS,14
6.2
6.2
M.OPENR
Open Resource
2,X'42'
H.REMM,21
6.2
M_OPENR
Open Resource
2,X'42'
H.REMM,21
7.2
M_OPTIONDWORD
Task Option
Doubleword Inquiry
2,x'CO'
H.REXS,95
7.2
(~
MPX-32 Reference
8-9
Macro Name Listing
Macro
Description
SVC
Module,
E.P.
Volume I
Ref.Manual
Section
M_OPTIONWORD
Task Option Word
Inquiry
1,x'4C'
H.REXS,24
7.2
M.OSREAD
Physical Memory
Read
2,X'7E'
H.REXS,93
6.2
M_OSREAD
Physical Memory
Read
2,x'7E'
H.REXS,93
7.2
M.OSWRIT
Physical Memory
Write
2,X'AF'
H.REXS,94
6.2
M_OSWRIT
Physical Memory
Write
2,x'AF'
H.REXS,94
7.2
M.PDEV
Physical Device
Inquiry
1,X'42'
H.MONS,l
6.4
M.PERM
Change Temporary
File to Permanent
1,X'76'
H.FISE,13
6.4
M.PGOD
Task Option
Doubleword Inquiry
2,x'CO'
H.REXS,9S
6.2
M.PGOW
Task Option Word
Inquiry
1,X'4C'
H.REXS,24
6.2
M.PNAM
Reconstruct
Pathname
2,x'2F'
H.VOMM,16
6.2
M.PNAMB
Convert Pathname
to Pathname Block
2,X'2E'
H.VOMM,lS
6.2
M_PNAMB
Convert Pathname
to Pathname Block
2,x'2E'
H.VOMM,lS
7.2
M.PRIL
Change Priority Level
l,X'4A'
H.REXS,9
6.2
M_PRIL
Change Priority Level
l,X'4A'
H.REXS,9
7.2
M.PRIV
Reinstate Privilege
Mode to Privilege Task
2,X'S7'
H.REXS,78
6.2
M_PRIVMODE
Reinstate Privilege
Mode to Privilege Task
2,x'S7'
H.REXS,78
7.2
M.PTSK
Parameter Task
Activation
l,x'SF'
H.REXS,40
6.2
M_PTSK
Parameter Task
Activation
l,x'SF'
H.REXS,40
7.2
M_PUTCTX
Put User Context
2,x'71'
H.EXEC,42
7.2
C
II'
;
r ",
~j
o
8-10
System Services Cross-Reference
Macro Name Listing
(~
(
(~
Volume I
Ref. Manual
Section
Macro
Description
SVC
Module,
E.P.
M.QATIM
Acquire Current
Date/fime in
ASCII Format
2,X'50'
H.REXS,74
6.2
M_QATIM
Acquire Current
Date/fime in
ASCII Format
2,X'50'
H.REXS,74
7.2
M.RADDR
Get Real Physical
Address
I,X'OE'
H.REXS,90
6.2
M_RADDR
Get Real Physical
Address
I,X'OE'
H.REXS,90
7.2
M.RCVR
Receive Message
Link Address
I,X'6B'
H.REXS,43
6.2
M_RCVR
Receive Message
Link Address
I,X'6B'
H.REXS,43
7.2
M.READ
Read Record
I,X'31'
H.lOCS,3
6.2
M_READ
Read Record
1,x'31'
H.IOCS,3
7.2
M_READD
Read Descriptor
2,x'2C'
H.VOMM,13
7.2
M.RELP
Release Dualported Disc/Set Dualchannel ACM Mode
I,X'27'
H.IOCS,27
6.2
M_RELP
Release Dualported Disc/Set Dualchannel ACM Mode
1,x'27'
H.lOCS,27
7.2
M.RENAM
Rename File
2,x'2D'
H.VOMM,14
6.2
M_RENAME
Rename File
2,X'2D'
H.VOMM,14
7.2
M.REPLAC
Replace Permanent
File
2,X'30'
H.VOMM,23
6.2
M_REPLACE
Replace Permanent
File
2,X'30'
H.VOMM,23
7.2
M.RESP
Reserve Dualported Disc/Set
Single-channel
ACMMode
1,x'26'
H.lOCS,24
6.2
M_RESP
Reserve Dualported Disc/Set
Single-channel
ACMMode
I,X'26'
H.IOCS,24
7.2
M_REWIND
Rewind File
I,X'37'
H.IOCS,2
7.2
M.REWRIT
Rewrite Descriptor
2,X'2B'
H.VOMM,12
6.2
MPX-32 Reference
8-11
Macro Name Listing
Volume I
Ref.Manual
Section
Macro
Description
SVC
Module,
E.P.
M_REWRIT
Rewrite Descriptor
2,X'2B'
H.VOMM,12
7.2
M.REWRTU
Rewrite Descriptor
User Area
2,X'32'
H.VOMM,27
6.2
M_REWRTU
Rewrite Descriptor
User Area
2,X'32'
H.VOMM,27
7.2
M.ROPL
Reset Option Lower
2,X'78'
H.TSM,14
6.2
M_ROPL
Reset Option Lower
2,X'78'
H.TSM,14
7.2
M.RRES
Release Channel
Reservation
I,X'3B'
H.IOCS,13
6.2
M_RRES
Release Channel
Reservation
I,X'3B'
H.lOCS,l3
7.2
M.RSML
Resourcemark Lock
I,X'19'
H.REXS,62
6.2
M_RSML
Resourcemark Lock
I,X'19'
H.REXS,62
7.2
M.RSMU
Resourcemark Unlock
I,X'IA'
H.REXS,63
6.2
M_RSMU
Resourcemark Unlock
I,X'IA'
H.REXS,63
7.2
M.RSRV
Reserve Channel
I,X'3A'
H.IOCS,l2
6.2
M_RSRV
Reserve Channel
I,X'3A'
H.IOCS,12
7.2
M.RWND
Rewind File
I,X'37'
H.lOCS,2
6.2
M_SETERA
Set Exception
Return Address
2,X'79'
H.REXS,81
7.2
M_SETEXA
Set Exception
Handler
2,X'SC'
H.REXS,83
7.2
M.SETS
Set User Status Word
I,X'48'
H.REXS,7
6.2
M_SETS
Set User Status Word
1,X'48'
H.REXS,7
7.2
M.SETSYNC
Set Synchronous
Resource Lock
2,X'46'
H.REMM,2S
6.2
M_SETSYNC
Set Synchronous
Resource Lock
2,X'46'
H.REMM,2S
7.2
M.SETT
Create Timer Entry
1,X'4S'
H.REXS,4
6.2
M_SETT
Create Timer Entry
I,X'4S'
H.REXS,4
7.2
M.SHARE
Share Memory with
Another Task
I,X'71'
H.ALOC,12
6.4
M.SMSGR
Send Message to
Specified Task
I,X'6C'
H.REXS,44
6.2
M_SMSGR
Send Message to
Specified Task
I,X'6C'
H.REXS,44
7.2
C
(,~,
8-12
System Services Cross-Reference
Macro Name Listing
(
(
Macro
Description
SVC
Module,
E.P.
Volume I
Ref.Manual
Section
M.SMULK
Unlock and Dequeue
Shared Memory
I,X'IF'
H.ALOC,19
6.4
M.SOPL
Set Option Lower
2,X'7?'
H.TSM,13
6.2
M_SOPL
Set Option Lower
2,X'7?'
H.TSM,13
7.2
M.SRUNR
Send Run Request to
Specified Task
I,X'6D'
H.REXS,45
6.2
M_SRUNR
Send Run Request to
Specified Task
I,X'6D'
H.REXS,45
7.2
M.SUAR
Set User Abort
Receiver Address
I,X'60'
H.REXS,26
6.2
M_SUAR
Set User Abort
Receiver Address
I,X'60'
H.REXS,26
7.2
M.SUME
Resume Task
Execution
I,X'53'
H.REXS,16
6.2
M_SUME
Resume Task
Execution
I,X'53'
H.REXS,16
7.2
M.SURE
Suspend/Resumc
5,X'OO'
N/A
6.2
M_SURE
Suspend/Resume
5,X'OO'
N/A
7.2
M.SUSP
Suspend Task
Execution
I,X'54'
H.REXS,17
6.2
M_SUSP
Suspend Task
Execution
I,X'54'
H.REXS,17
7.2
M.SYNCH
Set Synchronous
Task Interrupt
I,X'lB'
H.REXS,67
6.2
M_SYNCH
Set Synchronous
Task Interrupt
I,X'IB'
H.REXS,67
7.2
M.TBRKON
Trap On-line User's
Task
1,x'5C'
H.TSM,6
6.2
M_TBRKON
Trap On-line User's
Task
1,X'5C'
H.TSM,6
7.2
M.TDAY
Time-of-Day Inquiry
I,X'4E'
H.REXS,l1
6.2
M_TDAY
Time-of-Day Inquiry
I,X'4E'
H.REXS,11
7.2
M.TEMP
Create Temporary
File
2,X'21'
H.VOMM,2
6.2
(
MPX-32 Reference
8-13
Macro Name Listing
Volume I
Ref.Manual
Section
--
Macro
Description
SVC
Module,
E.P.
M.TEMPER
Change Temporary
File to Permanent File
2,X'2S'
H.VOMM,9
6.2
M_TEMPFILETOPERM
Change Temporary
File to Permanent File
2,X'2S'
H.VOMM,9
7.2
M.1RNC
Truncate File
2,X'26'
H.VOMM,7
6.2
M_TRUNCATE
Truncate File
2,X'26'
H.VOMM,7
7.2
M.TSCAN
Scan Terminal Input
Buffer
l,X'SB'
H.TSM,2
6.2
M_TSCAN
Scan Terminal Input
Buffer
1,X'SB'
H.TSM,2
7.2
M.TSMPC
TSM Procedure
2,X'AE'
H.TSM,17
6.2
2,X'AE'
H.TSM,17
7.2
C
Call
M_TSMPC
TSM Procedure
Call
M.TSTE
Arithmetic
Exception Inquiry
l,X'4D'
H.REXS,23
6.2
M_TSTE
Arithmetic
Exception Inquiry
1,X'40'
H.REXS,23
7.2
M.TSTS
Test User Status
Word
1,X'49'
H.REXS,S
6.2
M_TSTS
Test User Status
Word
l,X'49'
H.REXS,8
7.2
M.TSTT
Test Timer Entry
I,X'46'
H.REXS,5
6.2
M_TSTT
Test Timer Entry
I,X'46'
H.REXS,5
7.2
M.TURNON
Activate Program at
Given Time of Day
I,X'IE'
H.REXS.66
6.2
M_TURNON
Activate Program at
Given Time of Day
I,X'iE'
H.REXS,66
7.2
M.TYPE
System Console Type
I,X'3F'
H.IOCS,l4
6.2
M_TYPE
System Console Type
I,X'3F'
H.IOCS,14
7.2
M.UNLOCK
Release Exclusive
Resource Lock
2,X'45'
H.REMM,24
6.2
M_UNLOCK
Release Exclusive
Resource Lock
2,x'4S'
H.REMM,24
7.2
\',-~/'
c
8-14
System Services Cross-Reference
Macro Name Listing
(-
(~-
Volume I
Ref.Manual
Section
Macro
Description
SVC
Module,
E.P.
M_UNPRIVMODE
Change Task to
Unprivileged Mode
2,X'58'
H.REXS,79
7.2
M.UNSYNC
Release Synchronous
Resource Lock
2,X'47'
H.REMM,26
6.2
M_UNSYNC
Release Synchronous
Resource Lock
2,X'47'
H.REMM,26
7.2
M.UPRIV
Change Task to
Unprivileged Mode
2,X'58'
H.REXS,79
6.2
M.UPSP
Upspace
1,X'1O'
H.lOCS,20
6.2
M_UPSP
Upspace
1,x'1O'
H.lOCS,20
7.2
M.USER
User Name
Specification
1,x'74'
H.MONS,34
6.4
M.VADDR
Validate Address
Range
2,x'59'
H.REXS,33
6.2
M_VADDR
Validate Address
Range
2,X'59'
H.REXS,33
7.2
M.WAIT
Wait I/O
1,X'3C'
H.lOCS,25
6.2
M_WAIT
Wait I/O
1,x'3C'
H.lOCS,25
7.2
M.WEOF
Write EOF
1,x'38'
H.lOCS,5
6.2
M.WRIT
Write Record
1,X'32'
H.IOCS,4
6.2
M_WRITE
Write Record
1,X'32'
H.lOCS,4
7.2
M_WRITEEOF
WriteEOF
1,X'38'
H.lOCS,5
7.2
M.XBRKR
Exit from Task
Interrupt Level
1,x'70'
H.REXS,48
6.2
M_XBRKR
Exit from Task
Interrupt Level
N/A
N/A
7.2
M.xIEA
No-wait I/O Endaction Return
1,X'2C'
H.lOCS,34
6.2
M_XIEA
No-wait I/O Endaction Return
N/A
N/A
7.2
M.xMEA
Exit from Message
End-action Routine
1,x'7E'
H.REXS,50
6.2
M_XMEA
Exit from Message
End-action Routine
N/A
N/A
7.2
MPX-32 Reference
8-15
Macro Name Listing
·SVC
Module,
E.P.
Volume I
Ref.Manual
Section
Macro
Description
M.XMSGR
Exit from Message
Receiver
l,X'SE'
H.REXS,39
6.2
M_XMSGR
Exit from Message
Receiver
N/A
N/A
7.2
M.XREA
Exit from Run Request
End-action Routine
l,x'7F'
H.REXS,Sl
6.2
M_XREA
Exit from Run Request
End-action Routine
N/A
N/A
7.2
M.XRUNR
Exit Run Receiver
1,x'70'
H.REXS,49
6.2
M_XRUNR
Exit Run Receiver
N/A
7.2
MJITIME
Task CPU Execution
Time
N/A
1,x'20'
H.REXS,6S
6.2
M_XTIME
Task CPU Execution
Time
l,X'20'
H.REXS,6S
7.2
N/A
Allocate File Space
N/A
H.VOMM,19
6.3
N/A
Allocate Resource
Descriptor
N/A
H.VOMM,17
6.3
N/A
Create Temporary File
N/A
H.VOMM,24
6.3
N/A
Deallocate File Space
N/A
H.VOMM,20
6.3
N/A
Deallocate Resource
Descriptor
N/A
H.VOMM,lS
6.3
N/A
Debug Link Service
l,x'66'
H.REXS,42
6.3
N/A
Debug Link ServiceBase Mode
l,x'66'
H.REXS,42
7.3
N/A
Eject/Purge Routine
l,X'OO'
H.IOCS,22
6.3
N/A
Eject/Purge RoutineBase Mode
l,x'OO'
H.IOCS,22
7.3
N/A
Erase or Punch Trailer
l,X'3E'
H.IOCS,21
6.3
N/A
Erase or Punch
Trailer - Base Mode
l,X'3E'
H.IOCS,21
7.3
N/A
Execute Channel
1,x'2S'
H.IOCS,10
6.3
l,X'2S'
H.IOCS,10
7.3
0
~/
Program
N/A
Execute Channel
Program - Base Mode
o
8-16
System SelVlces Cross-Reference
Macro Name Listing
(",
Volume I
Ref.Manual
Section
Macro
Description
SVC
Module,
E.P.
N/A
Get Extended
Memory Array
2,X'7F'
H.MEMM,14
6.3
N/A
Get Extended
Memory Array - Base Mode
2,X'7P'
H.MEMM,14
7.3
N/A
Read/Write
Authorization Pile
N/A
H.VOMM,25
6.3
N/A
Release PHD Port
I,X'27'
H.lOCS,27
6.3
N/A
Release PHD Port Base Mode
I,X'27'
H.IOCS,27
7.3
N/A
Reserve PHD Port
I,X'26'
H.IOCS,24
6.3
N/A
Reserve PHD PortBase Mode
I,X'26'
H.IOCS,24
7.3
N/A
Reserved for
Interactive Debugger
2,X'56'
H.REXS,30
N/A
N/A
Reserved for Rapid
Pile Allocation:
Zero MDT
Locate/Read MDT Entry
Update/Create MDT Entry
Delete MDT Entry
2;X'AA'
2,X'AB'
2,X'AC'
2,X'AD'
H.MDT,1
H.MDT,2
H.MDT,3
H.MDT,4
N/A
Set Tabs in UDT
I,X'59'
H.TSM,5
N/A
N/A
TSM Task Detach
I,X'20'
H.TSM,3
N/A
(
MPX-32 Reference
N/A
8-17
Alphabetic Listing
L;
B.2 Alphabetic Listing
B-18
Volume I
Ref.Manual
Section
Description
Macro
SVC
Module,
E.P.
Abort Self
M.BORT
M_BORT
l,X'S7'
I,X'S?'
H.REXS,20
H.REXS,20
6.2
7.2
Abort Specified
Task
M.BORT
M_BORT
l,X'S6'
1,x'S6'
H.REXS,19
H.REXS,19
6.2
7.2
Abort With Extended
Message
M.BORT
M_BORT
1,X'62'
1,X'62'
H.REXS,28
H.REXS,28
6.2
7.2
Acquire Current
Daterrime in
ASCII Fonnat
M.QATIM
M_QATIM
2,X'SO'
2,X'SO'
H.REXS,74
H.REXS,74
6.2
7.2
Acquire Current
Daterrime in
Binary Fonnat
M.BTIM
M_BTIM
2,X'SO'
2,X'SO'
H.REXS,74
H.REXS,74
6.2
7.2
Acquire Current
Daterrime in
Byte Binary Format
M.BBTIM
M_BBTIM
2,x'SO'
2,x'SO'
H.REXS,74
H.REXS,74
6.2
7.2
Acquire System
Daterrime in
Any Format
M.GTIM
M_GTIM
2,X'SO'
2,x'SO'
H.REXS,74
H.REXS,74
6.2
7.2
Activate Program at
Given Time of Day
M.TURNON
M_TURNON
1,X'lE'
1,X'lE'
H.REXS,66
H.REXS,66
6.2
7.2
Activate Task
M.ACTV
M_ACTV
1,X'S2'
1,X'S2'
H.REXS,lS
H.REXS,lS
6.2
7.2
Activate Task
Interrupt
M.INT
M_INT
1,x'6F'
1,x'6F'
H.REXS,47
H.REXS,47
6.2
7.2
Advance File
M.FWRD
M_ADVANCE
1,X'34'
1,x'34'
H.IOCS,8
H.IOCS,8
6.2
7.2
Advance Record
M.FWRD
M_ADVANCE
1,X'33'
1,x'33'
H.IOCS,7
H.IOCS,7
6.2
7.2
Allocate File or
Peripheral Device
M.ALOC
1,x'40'
H.MONS,21
6.4
Allocate File
Space
N/A
N/A
H.VOMM,19
6.3
Allocate Resource
Descriptor
N/A
N/A
H.VOMM,17
6.3
Arithmetic
Exception Inquiry
M.TSTE
M_TSTE
l,X'4D'
1,X'4D'
H.REXS,23
H.REXS,23
6.2
7.2
System Services Cross-Reference
',,-
0
/
Alphabetic Listing
("
(
Volume I
Ref. Manual
Section
Description
Macro
SVC
Module,
E.P.
Assign and Allocate
Resource
M.ASSN
M_ASSIGN
2,X'52'
2,X'52'
H.REXS,21
H.REXS,21
6.2
7.2
Backspace File
M.BACK
M_BACKSPACE
1,X'36'
1,X'36'
H.IOCS,19
H.IOCS,19
6.2
7.2
Backspace Record
M.BACK
M_BACKSPACE
I,X'35'
I,X'35'
H.IOCS,9
H.IOCS,9
6.2
7.2
Batch Job Entry
M.BATCH
M_BATCH
2,X'55'
2,X'55'
H.REXS,27
H.REXS,27
6.2
7.2
Break/fask
Interrupt Link/Unlink
M.BRK
M_BRK
I,X'6E'
I,X'6E'
H.REXS,46
H.REXS,46
6.2
7.2
Change Defaults
M.DEFf
M_DEFT
2,X'27'
2,X'27'
H.VOMM,8
H.VOMM,8
6.2
7.2
Change Priority
Level
M.PRIL
M]RIL
I,X'4A'
1,x'4A'
H.REXS,9
H.REXS,9
6.2
7.2
Change Task to
Unprivileged Mode
M.UPRIV
M_UNPRIVMODE
2,X'58'
2,x'58'
H.REXS,79
H.REXS,79
6.2
7.2
Change Temporary
File to Permanent
M.PERM
I,X'76'
H.FISE,13
6.4
Change Temporary
File to
Permanent File
M.TEMPER
M_TEMPFILETOPERM
2,X'28'
2,X'28'
H.VOMM,9
H.VOMM,9
6.2
7.2
Close File
M.CLSE
M_CLSE
I,X'39'
I,X'39'
H.IOCS,23
H.IOCS,23
6.2
7.2
Close Resource
M.CLOSER
M_CLOSER
2,X'43'
2,X'43'
H.REMM,22
H.REMM,22
6.2
7.2
Connect Task to
Interrupt
M.CONN
M_CONN
I,X'4B'
I,X'4B'
H.REXS,lO
H.REXS,lO
6.2
7.2
Convert ASCII
Daterrime to
Byte Binary Format
M.CONABB
M_CONABB
2,x'51'
2,X'51'
H.REXS,75
H.REXS,75
6.2
7.2
Convert ASCII
Daterrime to
Standard Binary
M.CONASB
M_CONASB
2,X'51'
2,x'51'
H.REXS,75
H.REXS,75
6.2
7.2
Convert ASCII
Decimal to Binary
M.CONADB
M_CONADB
I,X'28'
I,X'28'
H.TSM,7
H.TSM,7
6.2
7.2
Convert ASCII Hex
to Binary
M.CONAHB
M_CONAHB
I,X'29'
I,X'29'
H.TSM,8
H.TSM,8
6.2
7.2
(
MPX-32 Reference
8-19
Alphabetic Listing
Volume I
Ref.Manual
Section
Description
Macro
SYC
Module,
E.P.
Convert Binary
Dateffime to
ASCII Fonnat
M.CONBAF
M_CONBAF
2,X'51'
2,X'51'
H.REXS,75
H.REXS,75
6.2
7.2
Convert Binary
Dateffime to
Byte Binary
M.CONBBY
M_CONBBY
2,X'5l'
2,X'5l'
H.REXS,75
H.REXS,75
6.2
7.2
Convert Binary to
ASCII Decimal
M.CONBAD
M_CONBAD
1,X'2A'
1,X'2A'
H.TSM,9
H.TSM,9
6.2
7.2
Convert Binary to
ASCII Hex
M.CONBAH
M_CONBAH
1,X'2B'
1,X'2B'
H.TSM,lO
H.TSM,lO
6.2
7.2
Convert Byte
Binary Dateffime
to ASCII
M.CONBBA
M_CONBBA
2,X'5l'
2,X'5l'
H.REXS,75
H.REXS,75
6.2
7.2
Convert Byte
Binary Dateffime
to Binary
M.CONBYB
M_CONBYB
2,X'5l'
2,X'5l'
H.REXS,75
H.REXS,75
6.2
7.2
Convert Pathname
to Pathname Block
M.PNAMB
M_PNAMB
2,X'2E'
2,X'2E'
H.YOMM,15
H.YOMM,15
6.2
7.2
Convert System
Dateffime Format
M.CTIM
M_CTIM
2,X'51'
2,X'5l'
H.REXS,75
H.REXS,75
6.2
7.2
Convert Time
M_CONVERTTIME
2,X'51'
H.REXS,75
7.2
Create Directory
M.DIR
M_DIR
2,X'23'
2,X'23'
H.YOMM,4
H.YOMM,4
6.2
7.2
M.DFCB
N/A
N/A
5.9.1
Create File Control
Block
M_CREATEFCB
N/A
N/A
7.2
Create Memory
Partition
M.MEM
M_MEM
2,X'22'
2,X'22'
H.YOMM,3
H.YOMM,3
6.2
7.2
Create Permanent
File
M.CREATE
1,X'75'
H.FISE,12
6.4
Create Permanent
File
M.CPERM
M_CREATEP
2,X'20'
2,X'20'
H.YOMM,l
H.YOMM,l
6.2
7.2
Create Temporary
File
M.TEMP
M_CREATET
2,X'2l'
2,X'2l'
H.YOMM,2
H.YOMM,2
6.2
7.2
Create Temporary
File
N/A
N/A
H.YOMM,24
6.3
. Create File Control
Block
IC~
;,r-
~'"
0
8·20
System Services Cross-Reference
Alphabetic Listing
("
(
--'
Yolwne I
Ref.Manual
Section
Description
Macro
SYC
Module,
E.P.
Create Timer Entry
M.SETT
M_SETT
1,X'45'
1,X'45'
H.REXS,4
H.REXS,4
6.2
7.2
Date and Time
Inquiry
M.DATE
M_DATE
1,X'15'
1,X'15'
H.REXS,70
H.REXS,70
6.2
7.2
Deallocate File or
Peripheral Device
M.DALC
1,X'4l'
H.MONS,22
6.4
Deallocate File
Space
N/A
N/A
H.YOMM,20
6.3
Deallocate Resource
Descriptor
N/A
N/A
H.YOMM,18
6.3
Deassign and
Deallocate Resource
M.DASN
M_DEASSIGN
2,X'53'
2,x'53'
H.REXS,22
H.REXS,22
6.2
7.2
Debug Link Service
N/A
1,x'66'
H.REXS,42
6.3
Debug Link ServiceBase Mode
N/A
1,x'66'
H.REXS,42
7.3
Delete Permanent
File or Non-SYSGEN
Memory Partition
M.DELETE
1,X'77'
H.FISE,14
6.4
Delete Resource
M.DELR
M_DELETER
2,X'24'
2,X'24'
H.YOMM,5
H.YOMM,5
6.2
7.2
Delete Task
M.DELTSK
M_DELTSK
1,X'5A'
I,X'SA'
H.REXS,31
H.REXS,31
6.2
7.2
Delete Timer Entry
M.DLTT
M_DLTT
1,x'47'
1,X'47'
H.REXS,6
H.REXS,6
6.2
7.2
Disable Message
Task Interrupt
M.DSMI
M_DSMI
l,X'2E'
l,X'2E'
H.REXS,S7
H.REXS,57
6.2
7.2
Disable User Break
Interrupt
M.DSUB
M_DSUB
l,X'12'
l,X'12'
H.REXS,73
H.REXS,73
6.2
7.2
Disconnect Task
from Interrupt
M.DISCON
M_DISCON
l,X'SD'
1,X'SD'
H.REXS,38
H.REXS,38
6.2
7.2
Dismount Volume
M.DMOUNT
M_DISMOUNT
2,x'4A'
2,x'4A'
H.REMM,19
H.REMM,19
6.2
7.2
Eject/Purge Routine
N/A
1,x'OD'
H.IOCS,22
6.3
Eject/Purge RoutineBase Mode
N/A
l,x'OD'
H.IOCS,22
7.3
Enable Message
Task Interrupt
M.ENMI
M_ENMI
l,X'2F'
1,x'2F'
H.REXS,S8
H.REXS,58
6.2
7.2
('"
MPX·32 Reference
8·21
Alphabetic Listing
Volume I
Ref.Manual
Section
Description
Macro
SVC
Module,
E.P.
Enable User Break
Interrupt
M.ENUB
M_ENUB
I,X'I3'
I,X'l3'
H.REXS,72
H.REXS,72
6.2
7.2
End Action Wait
M.EAWAIT
M_AWAITACfION
I,X'ID'
I,X'ID'
H.EXEC,40
H.EXEC,40
6.2
7.2
Erase or Punch
Trailer
N/A
I,X'3E'
H.IOCS,21
6.3
Erase or Punch
Trailer - Base Mode
N/A
I,X'3E'
H.IOCS,21
7.3
Exclude Memory
Partition
M.EXCLUDE
2,X'4I'
H.REMM,I4
6.2
Exclude Shared
Image
M_EXCLUDE
2,X'4I'
H.REMM,14
7.2
Execute Channel
Program
N/A
l,X'2S'
H.IOCS,lO
6.3
Execute Channel
Program - Base Mode
N/A
I,X'2S'
H.IOCS,10
7.3
Execute Channel
Program File
Control Block
M_CHANPROGFCB
N/A
N/A
7.2
Exit from Message
End-action Routine
M.xMEA
M_XMEA
1,X'7E'
N/A
H.REXS,SO
N/A
6.2
7.2
Exit from Message
Receiver
M.xMSGR
M_XMSGR
I,X'SE'
N/A
H.REXS,39
N/A
6.2
7.2
Exit from Run
Request End-action
Routine
M.xREA
M_XREA
I,X'7F'
N/A
H.REXS,SI
N/A
6.2
7.2
Exit from Task
Interrupt Level
M.BRKXIT
M_BRKXIT
M.xBRKR
M_XBRKR
I,X'70'
N/A
l,X'70'
N/A
H.REXS,48
N/A
H.REXS,48
N/A
6.2
7.2
6.2
7.2
Exit Run Receiver
M.xRUNR
M_XRUNR
I,X'7D'
N/A
H.REXS,49
N/A
6.2
7.2
Exit With Status
M_EXTSTS
2,X'SF'
H.REXS,86
7.2
Extend File
M.EXTD
M_EXTENDFILE
2,X'2S'
2,X'2S'
H.VOMM,6
H.VOMM,6
6.2
7.2
Free Dynamic
Extended Indexed
Data Space
M.FD
1,X'6A'
H.REMM,9
6.2
('
,-,/
C
'
,
./
8-22
System Services Cross-Reference
Alphabetic Listing
(
(
Volume I
Ref.Manual
Section
Description
Macro
SVC
Module,
E.P.
Free Dynamic Task
Execution Space
M.FE
1,X'68'
H.REMM,ll
6.2
Free Memory in
Byte Increments
M.MEMFRE
M_FREEMEMBYTES
2,X'4C'
2,X'4C'
H.REMM,29
H.REMM,29
6.2
7.2
Free Shared Memory
M.EXCL
1,X'79'
H.ALOC,14
6.4
Get Address Limits
M.GADRL
1,X'65'
H.REXS,41
6.2
Get Address Limits
M.GADRL2
2,X'7B'
H.REXS,80
6.2
Get Base Mode
Task Address Limits
M_LIMITS
2,X'5D'
H.REXS,84
7.2
Get Command Line
M.CMD
M_CMD
2,X'61'
2,X'61'
H.REXS,88
H.REXS,88
6.2
7.2
Get Current Date
and Time
M_GETTIME
2,X'50'
H.REXS,74
7.2
Get Device Mnemonic
or Type Code
M.DEVID
M_DEVID
1,X'14'
1,X'14'
H.REXS,71
H.REXS,71
6.2
7.2
Get Dynamic
Extended Data Space
M.GD
1,X'69'
H.REMM,8
6.2
Get Dynamic Extended
Discontiguous Data Space
M.GDD
2,X'7C'
H.MEMM,9
6.2
Get Dynamic Task
Execution Space
M.GE
1,X'67'
H.REMM,lO
6.2
Get Extended
Memory Array
N/A
2,X'7F'
H.MEMM,14
6.3
Get Extended
Memory Array Base Mode
N/A
2,X'7F'
H.MEMM,14
7.3
Get Memory in
Byte Increments
M.MEMB
M_GETMEMBYTES
2,X'4B'
2,X'4B'
H.REMM,28
H.REMM,28
6.2
7.2
Get Message
Parameters
M.GMSGP
M_GMSGP
1,X'7A'
1,X'7A'
H.REXS,35
H.REXS,35
6.2
7.2
Get Real
Physical Address
M.RADDR
M_RADDR
1,X'OE'
1,X'OE'
H.REXS,90
H.REXS,90
6.2
7.2
Get Run Parameters
M.GRUNP
M_GRUNP
1,X'7B'
1,X'7B'
H.REXS,36
H.REXS,36
6.2
7.2
Get Shared Memory
M.INCL
1,X'72'
H.ALOC,13
6.4
('
MPX·32 Reference
8·23
Alphabetic Listing
Description
Macro
SVC
Module,
E.P.
Volume I
Ref.Manual
Section
Get Task
Environment
M.ENVRMT
M_ENVRMT
2,X'5E'
2,X'5E'
H.REXS,85
H.REXS,85
6.2
7.2
Get Task Number
M.ID
M_ID
M.MYID
M_MYID
I,X'64'
I,X'64'
I,X'64'
I,X'64'
H.REXS,32
H.REXS,32
H.REXS,32
H.REXS,32
6.2
7.2
6.2
7.2
Get Terminal
Function Definition
M.GETDEF
M_GETDEF
2,X'7A'
2,X'7A'
H.TSM,15
H.TSM,15
6.2
7.2
Get TSA Start
Address
M.GTSAD
M_GTSAD
2,X'7D'
2,X'7D'
H.REXS,91
H.REXS,91
6.2
7.2
Get User Context
M_GETCTX
2,X'70'
H.EXEC,41
7.2
Include Memory
Partition
M.INCLUDE
2,X'40'
H.REMM,12
6.2
Include Shared
Image
M_INCLUDE
2,x'40'
H.REMM,12
7.2
Load and Execute
Interactive Debugger
M.DEBUG
M_DEBUG
1,X'63'
I,X'63'
H.REXS,29
H.REXS,29
6.2
7.2
Load Overlay Segment
Load and Execute
Overlay
M.OLAY
1,X'50'
1,X'5l'
H.REXS,13
H.REXS,14
6.2
6.2
Log Resource
or Directory
M.LOGR
M_LOGR
2,X'29'
2,X'29'
H.VOMM,lO
H.YOMM,lO
6.2
7.2
Memory Address
Inquiry
M.ADRS
M_ADRS
1,X'44'
1,X'44'
H.REXS,3
H.REXS,3
6.2
7.2
Memory Dump
Request
M.DUMP
M_DUMP
I,X'4F'
1,x'4F'
H.REXS,12
H.REXS,12
6.2
7.2
Modify Descriptor
M.MOD
M_MOD
2,x'2A'
2,X'2A'
H.YOMM,ll
H.VOMM,11
6.2
7.2
Modify Descriptor
User Area
M.MODU
M_MODU
2,X'31'
2,X'3l'
H.YOMM,26
H.YOMM,26
6.2
7.2
Mount Volume
M.MOUNT
M_MOUNT
2,X'49'
2,X'49'
H.REMM,17
H.REMM,17
6.2
7.2
Move Data to
User Address
M.MOYE
M_MOYE
2,x'62'
2,X'62'
H.REXS,89
H.REXS,89
6.2
7.2
No-wait I/O Endaction Return
M.xIEA
M_XIEA
I,X'2C'
N/A
H.IOCS,34
N/A
6.2
7.2
Open File
M.FILE
I,X'30'
H.IOCS,l
6.4
f-'
,-
I~_"_//
C
(,
8-24
System Services Cross-Reference
....)
Alphabetic Listing
('
("
(0-
Volume I
Ref.Manual
Section
Description
Macro
SYC
Module,
E.P.
Open Resource
M.OPENR
M_OPENR
2,X'42'
2,X'42'
H.REMM,21
H.REMM,21
6.2
7.2
Parameter Task
Activation
M.PTSK
M_PTSK
I,X'SF'
1,X'SF'
H.REXS,40
H.REXS,40
6.2
7.2
Permanent File
Address Inquiry
M.FADD
I,X'43'
H.MONS,2
6.4
Permanent File Log
M.LOG
I,X'73'
H.MONS,33
6.4
Physical Device
Inquiry
M.PDEY
I,X'42'
H.MONS,1
6.4
Physical Memory
Read
M.OSREAD
M_OSREAD
2,X'7E'
2,X'7E'
H.REXS,93
H.REXS,93
6.2
7.2
Physical Memory
Write
M.OSWRIT
M_OSWRIT
2,X'AP'
2,X'AP'
H.REXS,94
H.REXS,94
6.2
7.2
Program Hold
Request
M.HOLD
M_HOLD
I,X'S8'
I,X'S8'
H.REXS,2S
H.REXS,2S
6.2
7.2
Put User Context
M_PUTCTX
2,X'71'
H.EXEC,42
7.2
Read Descriptor
M.LOC
M_READD
2,X'2C'
2,X'2C'
H.YOMM,13
H.YOMM,13
6.2
7.2
Read Record
M.READ
M_READ
I,X'31'
I,X'31'
H.IOCS,3
H.IOCS,3
6.2
7.2
Read/Write
Authorization File
N/A
N/A
H.YOMM,2S
6.3
Receive Message
Link Address
M.RCVR
M_RCVR
I,X'6B'
I,X'6B'
H.REXS,43
H.REXS,43
6.2
7.2
Reconstruct
Pathname
M.PNAM
M_CONSTRUCTPATH
2,X'2F'
2,X'2F'
H.YOMM,16
H.YOMM,16
6.2
7.2
Reformat RRS Entry
M.NEWRRS
2,X'S4'
H.REXS,76
6.2
Reinstate Privilege
Mode to Privilege
Task
M.PRIY
M_PRIYMODE
2,X'S7'
2,X'S7'
H.REXS,78
H.REXS,78
6.2
7.2
Release Channel
Reservation
M.RRES
M_RRES
1,X'3B'
1,X'3B'
H.IOCS,13
H.IOCS,13
6.2
7.2
Release DUal-ported
Disc/Set Dual-channel
ACMMode
M.RELP
M_RELP
I,X'27'
I,X'27'
H.IOCS,27
H.IOCS,27
6.2
7.2
Release Exclusive
File Lock
M.FXLR
1,X'22'
H.FISE,23
6.4
Release Exclusive
Resource Lock
M.UNLOCK
M_UNLOCK
2,X'4S'
2,X'4S'
H.REMM,24
H.REMM,24
6.2
7.2
MPX-32 Reference
8-25
Alphabetic Listing
I"~
Volume I
Ref.Manual
Section
Oescription
Macro
SVC
Module,
E.P.
Release FHD Port
N/A
I,X'27'
H.IOCS,27
6.3
Release FHD PortBase Mode
N/A
I,X'27'
H.IOCS,27
7.3
Release
Synchronization
File Lock
M.FSLR
I,X'24'
H.FISE,25
6.4
Release Synchronous
Resource Lock
M.UNSYNC
M_UNSYNC
2,X'47'
2,X'47'
H.REMM,26
H.REMM,26
6.2
7.2
Rename File
M.RENAM
M_RENAME
2,X'20'
2,X'20'
H.VOMM,14
H.VOMM,14
6.2
7.2
Replace
Pennanent File
M.REPLAC
M_REPLACE
2,X'30'
2,X'30'
H.VOMM,23
H.VOMM,23
6.2
7.2
Reserve Channel
M.RSRV
M_RSRV
l,X'3A'
I,X'3A'
H.IOCS,12
H.IOCS,12
6.2
7.2
Reserve Dual-ported
Oisc/Set Single-channel
ACMMode
M.RESP
M_RESP
I,X'26'
I,X'26'
H.IOCS,24
H.IOCS,24
6.2
7.2
Reserve FHD Port
N/A
1,X'26'
H.IOCS,24
6.3
Reserve FHD PortBase Mode
N/A
I,X'26'
H.IOCS,24
7.3
Reserved for
Interactive
Oebugger
N/A
2,X'56'
H.REXS,30
N/A
Reserved for
Rapid File
Allocation:
Zero MDT
Locate/Read MDT Entry
Update/Create MDT Entry
Delete MDT Entry
N/A
Reset Option Lower
i:,"..
'J"-f
N/A
2,X'AA'
2,X'AB'
2,X'AC'
2,X'AD'
H.MDT,1
H.MDT,2
H.MOT,3
H.MDT,4
M.ROPL
M_ROPL
2,X'78'
2,X'78'
H.TSM,14
H.TSM,14
6.2
7.2
Resource Inquiry
M.INQUIRY
M_INQUIRER
2,X'48'
2,X'48'
H.REMM,27
H.REMM,27
6.2
7.2
Resourcemark Lock
M.RSML
M_RSML
I,X'19'
I,X'19'
H.REXS,62
H.REXS,62
6.2
7.2
Resourcemark Unlock
M.RSMU
M_RSMU
I,X'IA'
I,X'IA'
H.REXS,63
H.REXS,63
6.2
7.2
C
8-26
System Services Cross-Reference
Alphabetic Listing
(
(
Volume I
Ref.Manual
Section
Description
Macro
SVC
Module,
E.P.
Resume Task
Execution
M.SUME
M_SUME
I,X'53'
I,X'53'
H.REXS,16
H.REXS,16
6.2
7.2
Rewind File
M.RWND
M_REWIND
I,X'37'
I,X'37'
H.IOCS,2
H.IOCS,2
6.2
7.2
Rewrite Descriptor
M.REWRIT
M_REWRIT
2,X'2B'
2,X'2B'
H.VOMM,12
H.VOMM,12
6.2
7.2
Rewrite Descriptor
User Area
M.REWRTU
M_REWRTU
2,X'32'
2,X'32'
H.VOMM,27
H.VOMM,27
6.2
7.2
Scan Terminal
Input Buffer
M.TSCAN
M_TSCAN
I,X'5B'
I,X'5B'
H.TSM,2
H.TSM,2
6.2
7.2
Send Message to
Specified Task
M.SMSGR
M_SMSGR
I,X'6C'
I,X'6C'
H.REXS,44
H.REXS,44
6.2
7.2
Send Run Request
to Specified Task
M.SRUNR
M_SRUNR
I,X'6D'
I,X'6D'
H.REXS,45
H.REXS,45
6.2
7.2
Set Asynchronous
Task Interrupt
M.ASYNCH
M_ASYNCH
I,X'IC'
I,X'IC'
H.REXS,68
H.REXS,68
6.2
7.2
Set Exception
Handler
M_SETEXA
2,X'5C'
H.REXS,83
7.2
Set Exception
Return Address
M_SETERA
2,X'79'
H.REXS,81
7.2
Set Exclusive
File Lock
M.FXLS
I,X'2l'
H.FISE,22
6.4
Set Exclusive
Resource Lock
M.LOCK
M_LOCK
2,X'44'
2,X'44'
H.REMM,23
H.REMM,23
6.2
7.2
Set IPU Bias
M.IPUBS
M_IPUBS
2,X'5B'
2,X'5B'
H.REXS,82
H.REXS,82
6.2
7.2
Set Option Lower
M.SOPL
M_SOPL
2,X'77'
2,X'77'
H.TSM,13
H.TSM,13
6.2
7.2
Set Synchronization
File Lock
M.FSLS
I,X'23'
H.FISE,24
6.4
Set Synchronous
Resource Lock
M.SETSYNC
M_SETSYNC
2,X'46'
2,X'46'
H.REMM,25
H.REMM,25
6.2
7.2
Set Synchronous
Task Interrupt
M.SYNCH
M_SYNCH
I,X'IB'
I,X'IB'
H.REXS,67
H.REXS,67
6.2
7.2
Set Tabs in UDT
N/A
I,X'59'
H.TSM,5
N/A
MPX-32 Reference
B-27
Alphabetic Listing
8-28
Description
Macro
SVC
Module,
E.P.
Volume I
Ref.Manual
Section
Set User Abort
Receiver Address
M.SUAR
M_SUAR
I,X'60'
I,X'60'
H.REXS,26
H.REXS,26
6.2
7.2
Set User Status
Word
M.SETS
M_SETS
I,X'48'
I,X'48'
H.REXS,7
H.REXS,7
6.2
7.2
Share Memory with
Another Task
M.SHARE
I,X'71'
H.ALOC,12
6.4
Submit Job from
Disc File
M.CDJS
I,X'61'
H.MONS,27
6.4
Suspend/Resume
M.SURE
M_SURE
5,X'OO'
5,x'OO'
N/A
N/A
6.2
7.2
Suspend Task
Execution
M.SUSP
M_SUSP
1,x'54'
I,X'54'
H.REXS, I 7
H.REXS,17
6.2
7.2
System Console Type
M.TYPE
M_TYPE
I,X'3F'
I,X'3F'
H.IOCS,14
H.IOCS,14
6.2
7.2
System Console Wait
M.CWAT
M_CWAT
I,X'3D'
1,X'3D'
H.JOCS,26
H.IOCS,26
6.2
7.2
Task CPU Execution
Time
M.xTIME
M_XTIME
I,X'2D'
I,X'2D'
H.REXS,65
H.REXS,65
6.2
7.2
Task Option
Doubleword Inquiry
M.PGOD
M_OPTIONDWORD
2,X'CO'
2,X'CO'
H.REXS,95
H.REXS,95
6.2
7.2
Task Option Word
Inquiry
M.PGOW
M_OPTIONWORD
1,x'4C'
I,X'4C'
H.REXS,24
H.REXS,24
6.2
7.2
Terminate Task
Execution
M.EXIT
M_EXIT
I,X'55'
I,X'55'
H.REXS,18
H.REXS, I 8
6.2
7.2
Test Timer Entry
M.TSTT
M_TSTI
1,x'46'
I,X'46'
H.REXS,5
H.REXS,5
6.2
7.2
Test User Status
Word
M.TSTS
M_TSTS
I,X'49'
I,X'49'
H.REXS,8
H.REXS,8
6.2
7.2
Time-of-Day Inquiry
M.TDAY
M_TDAY
I,X'4E'
I,X'4E'
H.REXS, 11
H.REXS, 11
6.2
7.2
Trap On-line User's
Task
M.TBRKON
M_TBRKON
1,X'5C'
I,X'5C'
H.TSM,6
H.TSM,6
6.2
7.2
Truncate File
M.TRNC
M_TRUNCATE
2,x'26'
2,x'26'
H.VOMM,7
H.VOMM,7
6.2
7.2
TSM Procedure
Call
M.TSMPC
M_TSMPC
2,X'AE'
2,X'AE'
H.TSM,17
H.TSM,17
6.2
7.2
TSM Task Detach
N/A
I,X'20'
H.TSM,3
N/A
Unlock and Dequeue
Shared Memory
M.SMULK
1,x'IF'
H.ALOC,19
6.4
System Services Cross-Reference
("
",
\
~./
"
"
C
Alphabetic Listing
('
Volume I
Ref.Manual
Section
Description
Macro
SVC
Module,
E.P.
Upspace
M.UPSP
M_UPSP
I,X'tO'
I,X'IO'
H.lOCS,20
H.lOCS,20
6.2
7.2
User Name
Specification
M.USER
1,x'74'
H.MONS,34
6.4
Validate Address
Range
M.VADDR
M_VADDR
2,X'59'
2,X'59'
H.REXS,33
H.REXS,33
6.2
7.2
Wait for Any
No-wait Operation
Complete, Message
Interrupt, or Break
Interrupt
M.ANYW
M_ANYWAIT
I,X'7C'
I,X'7C'
H.REXS,37
H.REXS,37
6.2
7.2
Wait 1/0
M.WAIT
M_WAIT
I,X'3C'
1,x'3C'
H.lOCS,25
H.lOCS,25
6.2
7.2
WriteEOF
M.WEOF
M_WRlTEEOF
I,X'38'
I,X'38'
H.lOCS,5
H.lOCS,5
6.2
7.2
Write Record
M.WRIT
M_WRITE
I,X'32'
1,x'32'
H.IOCS,4
H.IOCS,4
6.2
7.2
("'
MPX-32 Reference
8-29
SVC Listing
()
''"-
B.3 SVC Listing
SVC
8-30
Module,
E.P.
Macro
Volume I
Ref.Manual
Section
I,X'nn'
Description
OO-OA
Reserved
OB
Reserved for
Vector Processor
OC
Reserved
OD
Eject/Purge
Routine
H.lOCS,22
N/A
6.3
Eject/Purge
Routine - Base Mode
H.lOCS,22
N/A
7.3
OE
Get Real
Physical Address
H.REXS,90
M.RADDR
M_RADDR
6.2
7.2
OF
Reserved for
Vector Processor
N/A
N/A
10
Upspace
M.UPSP
M_UPSP
6.2
7.2
11
Reserved
H.IOCS,20
,~'"
12
Disable User
Break Interrupt
H.REXS,73
M.DSUB
M_DSUB
6.2
7.2
13
Enable User
Break Interrupt
H.REXS,72
M.ENVB
M_ENUB
6.2
7.2
14
Get Device Mnemonic
or Type Code
H.REXS,71
M.DEVID
M_DEVID
6.2
7.2
15
Date and Time
Inquiry
H.REXS,70
M.DATE
M_DATE
6.2
7.2
16
ADlMaximum
IOCBs
N/A
M.ADIMAX
N/A
17
ADI I/O
N/A
M.ADIO
N/A
18
ADIEAI
N/A
M.ADIEAI
N/A
19
Resourcemark
Lock
H.REXS,62
M.RSML
M_RSML
6.2
7.2
IA
Resourcemark
Unlock
H.REXS,63
M.RSMU
M_RSMU
6.2
7.2
1B
Set Synchronous
Task Interrupt
H.REXS,67
M.SYNCH
M_SYNCH
6.2
7.2
lC
Set Asynchronous
Task Interrupt
H.REXS,68
M.ASYNCH
M_ASYNCH
6.2
7.2
System Services Cross-Reference
\--/
C
SVC Listing
('
(~~
Macro
Volume I
Ref. Manual
Section
H.EXEC,40
M.EAWAIT
M_AWAITACTION
6.2
7.2
Activate Program
at Given Time of Day
H.REXS,66
M.TURNON
M_TURNON
6.2
7.2
IF
Unlock and
Dequeue Shared Memory
H.ALOC,19
M.SMULK
6.4
20
TSM Task Detach
H.TSM,3
N/A
N/A
21
Set Exclusive
File Lock
H.FISE,22
M.FXLS
6.4
22
Release
Exclusive File Lock
H.FISE,23
M.FXLR
6.4
23
Set Synchronization
File Lock
H.FISE,24
M.FSLS
6.4
24
Release
Synchronization
File Lock
H.FISE,25
M.FSLR
6.4
25
Execute Channel
Program
H.lOCS,lO
N/A
6.3
Execute Channel
Program - Base Mode
H.lOCS,lO
N/A
7.3
ReservePHD Port
Reserve PHD Port Base Mode
Reserve Dualported Disc/Set
Single-channel
ACMMode
H.lOCS,24
N/A
N/A
6.3
7.3
M.RESP
M_RESP
6.2
7.2
Release FHD Port
Release PHD Port Base Mode
Release Dualported Disc/Set
Dual-channel
ACMMode
H.IOCS,27
N/A
N/A
6.3
7.3
M.RELP
M_RELP
6.2
7.2
28
Convert ASCII
Decimal to Binary
H.TSM,7
M.CONADB
M_CONADB
6.2
7.2
29
Convert ASCII
Hex to Binary
H.TSM,8
M.CONAHB
M_CONAHB
6.2
7.2
SVC
I,X'nn'
Description
Module,
E.P.
ID
End Action Wait
IE
26
27
("MPX·32 Reference
8·31
SVC Listing
SVC
l,X'nn'
Description
Module,
E.P.
Macro
Volume I
Ref.Manual
Section
2A
Convert Binary
to ASCII Decimal
H.TSM,9
M.CONBAD
M_CONBAD
6.2
7.2
2B
Convert Binary
to ASCII Hex
H.TSM,lO
M.CONBAH
M_CONBAH
6.2
7.2
2C
No-wait I/O End-action
Retmn
H.IOCS,34
M.XffiA
6.2
2D
Task CPU Execution
Time
H.REXS,65
M.XTIME
M_XTIME
6.2
7.2
2E
Disable Message
Task Interrupt
H.REXS,57
M.DSMI
M_DSMI
6.2
7.2
2F
Enable Message
Task Interrupt
H.REXS,58
M.ENMI
M_ENMI
6.2
7.2
30
Open File
H.IOCS,l
M.FILE
6.4
31
Read Record
H.IOCS,3
M.READ
M_READ
6.2
7.2
32
Write Record
H.IOCS,4
M.WRIT
M_WRITE
6.2
7.2
33
Advance Record
H.IOCS,7
M.FWRD
M_ADVANCE
6.2
7.2
34
Advance File
H.IOCS,8
M.FWRD
M_ADVANCE
6.2
7.2
35
Backspace Record
H.IOCS,9
M.BACK
M_BACKSPACE
6.2
7.2
36
Backspace File
H.IOCS,19
M.BACK
M_BACKSPACE
6.2
7.2
37
Rewind File
H.lOCS,2
M.RWND
M_REWIND
6.2
7.2
38
WriteEOF
H.lOCS,5
M.WEOF
M_WRlTEEOF
6.2
7.2
39
Close File
H.lOCS,23
M.CLSE
M_CLSE
6.2
7.2
3A
Reserve Channel
H.lOCS,12
M.RSRV
M_RSRV
6.2
7.2
3B
Release Channel
Reservation
H.lOCS,13
M.RRES
M_RRES
6.2
7.2
0
~-'
o
8-32
System Services Cross-Reference
SVC Listing
(-
(-
Macro
Volwne I
Ref.Manual
Section
H.IOCS,25
M.WAIT
M_WAIT
6.2
7.2
System Console
Wait
H.IOCS,26
M.CWAT
M_CWAT
6.2
7.2
Erase or Punch
Trailer
H.IOCS,21
N/A
6.3
Erase or Punch
Trailer - Base Mode
H.IOCS,21
N/A
7.3
3F
System Console
Type
H.IOCS,14
M.TYPE
M_TYPE
6.2
7.2
40
Allocate File or
Peripheral Device
H.MONS,21
M.ALOC
6.4
41
Deallocate File
or Peripheral Device
H.MONS,22
M.DALC
6.4
42
Physical Device
Inquiry
H.MONS,1
M.PDEV
6.4
43
Permanent File
Address Inquiry
H.MONS,2
M.FADD
6.4
44
Memory Address
Inquiry
H.REXS,3
M.ADRS
M_ADRS
6.2
7.2
45
Create Timer
Entry
H.REXS,4
M.SETT
M_SETT
6.2
7.2
46
Test Timer Entry
H.REXS,5
M.TSTT
M_TSTT
6.2
7.2
47
Delete Timer
Entry
H.REXS,6
M.DLTT
M_DLTT
6.2
7.2
48
Set User Status
Word
H.REXS,7
M.SETS
M_SETS
6.2
7.2
49
Test User Status
Word
H.REXS,8
M.TSTS
M_TSTS
6.2
7.2
4A
Change Priority
Level
H.REXS,9
M.PRIL
M_PRIL
6.2
7.2
4B
Connect Task to
Interrupt
H.REXS,lO
M.CONN
M_CONN
6.2
7.2
4C
Task Option Word
Inquiry
H.REXS,24
M.PGOW
M_OPTIONWORD
6.2
7.2
SVC
I,X'nn'
Description
Module,
E.P.
3C
Wait I/O
3D
3E
(~
MPX-32 Reference
8-33
SVC Listing
("
SVC
I,X'nn'
Description
Module,
E.P.
Macro
Volume I
Ref.Manual
Section
4D
Arithmetic
Exception Inquiry
H.REXS,23
M.TSTE
M_TSTE
6.2
7.2
4E
Time-of-Day Inquiry
H.REXS,ll
M.TDAY
M_TDAY
6.2
7.2
4F
Memory Dump
Request
H.REXS,12
M.DUMP
M_DUMP
6.2
7.2
50
Load Overlay Segment
H.REXS,13
M.OLAY
6.2
51
Load and Execute
Overlay
H.REXS,14
M.OLAY
6.2
52
Activate Task
H.REXS,15
M.ACTV
M_ACTV
6.2
7.2
53
Resume Task
Execution
H.REXS,16
M.SUME
M_SUME
6.2
7.2
54
Suspend Task
Execution
H.REXS,17
M.SUSP
M_SUSP
6.2
7.2
55
Terminate Task
Execution
H.REXS,18
M.EXIT
M_EXIT
6.2
7.2
56
Abort Specified
Task
H.REXS,19
M.BORT
M_BORT
6.2
7.2
57
Abort Self
H.REXS,20
M.BORT
M_BORT
6.2
7.2
58
Program Hold
Request
H.REXS,25
M.HOLD
M_HOLD
6.2
7.2
59
Set Tabs in UDT
H.TSM,5
N/A
N/A
5A
Delete Task
H.REXS,31
M.DELTSK
M_DELTSK
6.2
7.2
5B
Scan Terminal
Input Buffer
H.TSM,2
M.TSCAN
M_TSCAN
6.2
7.2
5C
Trap On-line
User's Task
H.TSM,6
M.TBRKON
M_TBRKON
6.2
7.2
5D
Disconnect Task
from Interrupt
H.REXS,38
M.DISCON
M_DISCON
6.2
7.2
5E
Exit from
Message Receiver
H.REXS,39
M.XMSGR
6.2
5F
Parameter Task
Activation
H.REXS,40
M.PTSK
M_PTSK
6.2
7.2
G
'!
C
8-34
System Services Cross-Reference
"
SVC Listing
(
,
.
Macro
Volume I
Ref.Manual
Section
H.REXS,26
M.SUAR
M_SUAR
6.2
7.2
Submit Job from
Disc File
H.MONS,27
M.CDJS
6.4
62
Abort With
Extended Message
H.REXS,28
M.BORT
M_BORT
6.2
7.2
63
Load and Execute
Interactive Debugger
H.REXS,29
M.DEBUG
M_DEBUG
6.2
7.2
64
Get Task Number
H.REXS,32
M.ID
M_ID
M.MYID
M_MYID
6.2
7.2
6.2
7.2
65
Get Address
Limits
H.REXS,41
M.GADRL
6.2
66
Debug Link
Service
H.REXS,42
N/A
6.3
Debug Link
Service - Base Mode
H.REXS,42
N/A
7.3
67
Get Dynamic Task
Execution Space
H.REMM,lO
M.GE
6.2
68
Free Dynamic
Task Execution Space
H.REMM,ll
M.PE
6.2
69
Get Dynamic
Extended Data Space
H.REMM,8
M.GD
6.2
6A
Free Dynamic
Extended Indexed
Data Space
H.REMM,9
M.FD
6.2
6B
Receive Message
Link Address
H.REXS,43
M.RCVR
M_RCVR
6.2
7.2
6C
Send Message to
Specified Task
H.REXS,44
M.SMSGR
M_SMSGR
6.2
7.2
Send Run Request
Specified Task
H.REXS,45
M.SRUNR
M_SRUNR
6.2
7.2
6E
Breakffask
Interrupt
Link/Unlink
H.REXS,46
M.BRK
M_BRK
6.2
7.2
6F
Activate Task
Interrupt
H.REXS,47
M.INT
M_INT
6.2
7.2
SVC
(.
I,X'nn'
Description
60
Set User Abort
Receiver Address
61
6D
Module,
E.P.
to
(
MPX-32 Reference
8-35
SVC Listing
Macro
Volume I
Ref.Manuai
Section
H.REXS,48
M.BRKXIT
M.XBRKR
6.2
6.2
Share Memory
with Another Task
H.ALOC,12
M.SHARE
6.4
72
Get Shared Memory
H.ALOC,13
M.INCL
6.4
73
Permanent File Log
H.MONS,33
M.LOG
6.4
74
User Name Specification
H.MONS,34
M.USER
6.4
75
Create Permanent File
H.FISE,12
M.CREATE
6.4
76
Change Temporary
File to Permanent
H.FISE,13
M.PERM
6.4
77
Delete Permanent File
or Non-SYSGEN
Memory Partition
H.FISE,14
M.OELETE
6.4
78
Reserved
79
Free Shared Memory
H.ALOC,14
M.EXCL
6.4
7A
Get Message Parameters
H.REXS,35
M.GMSGP
M_GMSGP
6.2
7.2
SVC
1,X'nn'
Description
70
Exit from Task
Interrupt Level
71
Module,
E.P.
7B
Get Run Parameters
H.REXS,36
M.GRUNP
M_GRUNP
6.2
7.2
7C
Wait for Any
No-wait Operation
Complete, Message
Interrupt, or Break
Interrupt
H.REXS,37
M.ANYW
M_ANYWAIT
6.2
7.2
70
Exit Run Receiver
H.REXS,49
M.XRUNR
6.2
7E
Exit from Message
End-action Routine
H.REXS,50
M.XMEA
6.2
7F
Exit from Run
Request End-action
Routine
H.REXS,51
M.XREA
6.2
80-FFF
Available for
customer use
('
L:
/ ' -',
c
8-36
System Services Cross-Reference
SVC Listing
('
(~
Macro
Volume I
Ref.Manual
Section
H.YOMM,1
M.CPERM
M_CREATEP
6.2
7.2
Create Temporary
File
H.YOMM,2
M.TEMP
M_CREATET
6.2
7.2
22
Create Memory
Partition
H.YOMM,3
M.MEM
M_MEM
6.2
7.2
23
Create Directory
H.YOMM,4
M.DIR
M_DIR
6.2
7.2
24
Delete Resource
H.YOMM,5
M.DELR
M_DELETER
6.2
7.2
25
Extend File
H.YOMM,6
M.EXTD
M_EXTENDFILE
6.2
7.2
26
Truncate File
H.YOMM,7
M.TRNC
M_TRUNCATE
6.2
7.2
27
Change Defaults
H.YOMM,8
M.DEFT
M_DEFT
6.2
7.2
28
Change Temporary
File to Permanent File
H.YOMM,9
M.TEMPER
M_TEMPFILETOPERM
6.2
7.2
29
Log Resource or
Directory
H.YOMM,lO
M.LOGR
M_LOGR
6.2
7.2
2A
Modify Descriptor
H.YOMM,11
M.MOD
M_MOD
6.2
7.2
2B
Rewrite
Descriptor
H.YOMM,12
M.REWRIT
M_REWRIT
6.2
7.2
2C
Read Descriptor
H.YOMM,13
M.LOC
M_READD
6.2
7.2
2D
Rename File
H.YOMM,14
M.RENAM
M_RENAME
6.2
7.2
2E
Convert Pathname
to Pathname Block
H.YOMM,15
M.PNAMB
M_PNAMB
6.2
7.2
2F
Reconstruct
Pathname
H.YOMM,16
M.PNAM
M_CONSTRUCTPATH
6.2
7.2
30
Replace
Permanent File
H.YOMM,23
M.REPLAC
M_REPLACE
6.2
7.2
31
Modify Descriptor
User Area
H.YOMM,26
M.MODU
M_MODU
6.2
7.2
SYC
2,X'nn'
Description
~O-IF
Reserved
20
Create Permanent
File
21
Module,
E.P.
(MPX·32 Reference
8·37
SVC Listing
SVC
2,X'nn'
Description
32
Rewrite
Descriptor User Area
33
DBX Interface to
H.PfRAC
34
Reserved
forH.PfRAC
35-3F
Reserved
40
Include Memory
Partition
Macro
Volume I
Ref.Manual
Section
H.VOMM,27
M.REWRTU
M_REWRTU
6.2
7.2
N/A
N/A
N/A
H.REMM,12
M.INCLUDE
6.2
M_INCLUDE
7.2
M.EXCLUDE
6.2
M_EXCLUDE
7.2
Module,
E.P.
Include Shared
Image
41
Exclude Memory
Partition
H.REMM,14
Exclude Shared
Image
42
Open Resource
H.REMM,21
M.OPENR
M_OPENR
6.2
7.2
43
Close Resource
H.REMM,22
M.CLOSER
M_CLOSER
6.2
7.2
44
Set Exclusive
Resource Lock
H.REMM,23
M.LOCK
M_LOCK
6.2
7.2
45
Release Exclusive
Resource Lock
H.REMM,24
M.UNLOCK
M_UNLOCK
6.2
7.2
46
Set Synchronous
Resource Lock
H.REMM,25
M. SETS YNC
M_SETSYNC
6.2
7.2
47
Release
Synchronous
Resource Lock
H.REMM,26
M.UNSYNC
M_UNSYNC
6.2
7.2
48
Resource Inquiry
H.REMM,27
M.INQUIRY
M_INQUIRER
6.2
7.2
49
Mount Volume
H.REMM,17
M.MOUNT
M_MOUNT
6.2
7.2
4A
Dismount Volume
H.REMM,19
M.DMOUNT
M_DISMOUNT
6.2
7.2
4B
Get Memory in
Byte Increments
H.REMM,28
M.MEMB
M_GETMEMBYTES
6.2
7.2
nU
/"
,
.".
',,-/I
()
8-38
System Services Cross-Reference
SVC Listing
(SVC
2,X'nn'
(
Description
4C
Free Memory in
Byte Increments
4D-4E
Reserved
4F
Reserved
50
Acquire Current
Date/fime in
ASCII Format
Acquire Current
Date/fime in
Binary Format
Acquire Current
Date/fime in
Byte Binary Format
Acquire System
Date/fime in
Any Format
Get Current
Date and Time
51
52
Convert ASCII
Date/fime to
Byte Binary Format
Convert ASCII
Date/fime to
Standard Binary
Convert Binary
Date/fime to
ASCII Format
Convert Binary
Date/fime to
Byte Binary
Convert Byte
Binary Datc/fime
to ASCII
Convert Byte
Binary Date{fime
to Binary
Convert System
Date{fime Format
Convert Time
Assign and
Allocate Resource
Macro
Volume I
Ref.Manual
Section
H.REMM,29
M.MEMFRE
M_FREEMEMBYTES
6.2
7.2
H.REXS,74
M.QATIM
M_QATIM
6.2
7.2
H.REXS,74
M.BTIM
M_BTIM
6.2
7.2
H.REXS,74
M.BBTIM
M_BBTIM
6.2
7.2
H.REXS,74
M.GTIM
M_GTIM
6.2
7.2
H.REXS,74
M_GETIIME
7.2
H.REXS,75
M.CONABB
M_CONABB
6.2
7.2
H.REXS,75
M.CONASB
M_CONASB
6.2
7.2
H.REXS,75
M.CONBAF
M_CONBAF
6.2
7.2
H.REXS,75
M.CONBBY
M_CONBBY
6.2
7.2
H.REXS,75
M.CONBBA
M_CONBBA
6.2
7.2
H.REXS,75
M.CONBYB
M_CONBYB
6.2
7.2
H.REXS,75
M.CTIM
M_CTIM
M_CONVERTTIME
6.2
7.2
7.2
M.ASSN
M_ASSIGN
6.2
7.2
Module,
E.P.
H.REXS,75
H.REXS,21
(
MPX-32 Reference
B-39
SVC Listing
-r---',
SVC
2,X'nn'
Description
Module,
E.P.
Macro
Volume I
Ref.Manual
Section
53
Deassign and
Deallocate Resource
H.REXS,22
M.DASN
M_DEASSIGN
6.2
7.2
54
Reformat RRS
Entry
H.REXS,76
M.NEWRRS
6.2
55
Batch Job Entry
H.REXS,27
M.BATCH
M_BATCH
6.2
7.2
56
Reserved for
Interactive Debugger
H.REXS,30
N/A
N/A
57
Reinstate
Privilege Mode
to Privilege Task
H.REXS,78
M.PRIV
M_PRIVMODE
6.2
7.2
58
Change Task to
Unprivileged Mode
H.REXS,79
M.UPRIV
M_UNPRIVMODE
6.2
7.2
59
Validate Address
Range
H.REXS,33
M.VADDR
M_VADDR
6.2
7.2
5A
Reserved
5B
Set IPU Bias
H.REXS,82
M.IPUBS
M_IPUBS
6.2
7.2
5C
Set Exception
Handler
H.REXS,83
M_SETEXA
7.2
5D
Get Base Mode
Task Address Limits
H.REXS,84
M_LIMITS
7.2
5E
Get Task
Environment
H.REXS,85
M.ENVRMT
M_ENVRMT
6.2
7.2
5F
Exit With Status
H.REXS,86
M_EXTSTS
7.2
60
Reserved
61
Get Command Line
H.REXS,88
M.CMD
M_CMD
6.2
7.2
62
H.REXS,89
M.MOVE
M_MOVE
6.2
7.2
63-6F
Move Data to
User Address
Reserved
70
Get User Context
H.EXEC,41
M_GETCTX
7.2
71
Put User Context
H.EXEC,42
M]UTCTX
7.2
72-74
Reserved for Symbolic
Debugger/X32
75
Reserved for MPX-32
'L/
(~,
8-40
System Services Cross-Reference
SVC Listing
(~
(
(
Volume I
Ref.Manual
Section
2,X'nn'
Description
Module,
E.P.
76
Allocate Shadow Memory
H.sHAD
N/A
N/A
77
Set Option Lower
H.TSM,13
M.SOPL
M_SOPL
6.2
7.2
78
Reset Option Lower
H.TSM,14
M.ROPL
M_ROPL
6.2
SVC
Macro
7.2
79
Set Exception
Return Address
H.REXS,81
M_SETERA
7.2
7A
Get Terminal
Function Definition
H.TSM,15
M.GETDEF
M_GETDEF
6.2
7.2
7B
Get Address Limits
H.REXS,80
M.GADRL2
6.2
7C
Get Dynamic
Extended Discontiguous
Data Space
H.MEMM,9
M.GDD
6.2
7D
Get TSA Start
Address
H.REXS,91
M.GTSAD
M_GTSAD
6.2
7.2
7E
Physical Memory Read
H.REXS,93
M.OSREAD
M_OSREAD
6.2
7.2
7F
Get Extended
Memory Array
H.MEMM,14
N/A
6.3
Get Extended
Memory Array Base Mode
H.MEMM,14
N/A
7.3
N/A
N/A
80-9F
Reserved for ACX-32
AO-A3
Reserved for Swapper
A4-A9
Reserved for Ada
AA-AD
Reserved for Rapid
File Allocation:
Zero MDT
Locate/Read MDT Entry
Update/Create MDT
Entry
Delete MDT Entry
H.MDT,1
H.MDT,2
H.MDT,3
AE
TSM Procedure Call
H.TSM,17
M.TSMPC
M_TSMPC
6.2
7.2
AF
Physical Memory Write
H.REXS,94
M.OSWRIT
M_OSWRIT
6.2
7.2
BO-BE
Reserved for RMS S
BF
Reserved
MPX-32 Reference
H.MDT,4
8-41
SVC Listing
SYC
2,X'nn'
Description
Macro
Volume I
Ref.Manual
Section
H.REXS,95
M.PGOD
M_OPTIONDWORD
6.2
7.2
Module,
E.P.
CO
Task Option
Doubleword Inquiry
CI-C7
Reserved
N/A
Allocate File
Space
H.YOMM,19
N/A
6.3
N/A
Allocate
Resource Descriptor
H.YOMM,17
N/A
6.3
N/A
Create File
Control Block
N/A
N/A
M.DFCB
M_CREATEFCB
5.9.1
7.2
N/A
Create Temporary
File
H.YOMM,24
N/A
6.3
N/A
Deallocate File
Space
H.YOMM,20
N/A
6.3
N/A
Deallocate
Resource Descriptor
H.YOMM,18
N/A
6.3
N/A
Execute Channel
Program File
Control Block
N/A
M_CHANPROGFCB
7.2
Read/Write
Authorization File
H.YOMM,25
N/A
0
,/
SYC
5,X'nn'
Description
Module,
E.P.
00
Suspend/Resume
N/A
N/A
6.3
Macro
Volume I
Ref.Manual
Section
M$URE
M_SURE
6.2
7.2
c
8-42
System Services Cross-Reference
c
C.1
MPX-32 Abort and Crash Codes
AC - Accounting
ACOI
INSUFFICIENT SLO SPACE FOR ACCOUNTING LISTING
C.2 AD - Address Specification Trap Handler (H.lPOC)
ADOI
ADDRESS SPECIFICATION ERROR OCCURRED WITHIN THE
OPERATING SYSTEM
AD02
ADDRESS SPECIFICATION ERROR OCCURRED WITHIN THE
CURRENT TASK
AD03
TRAP OCCURRED WHILE NO TASKS WERE IN ACTIVE STATE
AD04
TRAP OCCURRED WITHIN ANOTHER INTERRUPT TRAP ROUTINE
C.3 AL - Allocator (H.ALOC) (Compatibility Mode Only)
(
(--
ALOI-AL06
Reserved
AL07
THE COMBINED FILE ASSIGNMENTS FOR A TASK EXCEEDS
NUMBER SPECIFIED. THE CATALOGED ASSIGNMENTS ARE
COMBINED WITH THOSE DEFINED BY $ASSIGN STATEMENTS.
SEE CATALOGER FILES DIRECTIVE AND RECATALOG IF
NEEDED.
AL08
AN ASSIGNED PERMANENT FILE IS NONEXISTENT
AL09
AN ASSIGNED DEVICE IS NOT CONFIGURED IN THE SYSTEM.
AN ASSIGNED DEVICE IS OFF-LINE.
ALIO-ALII
Reserved
AL12
UNABLE TO LOAD PROGRAM BECAUSE OF I/O ERROR OR
ADDRESSING INCONSISTENCIES IN LOAD MODULE PREAMBLE
ALl3
AN UNRECOVERABLE I/O ERROR HAS OCCURRED DURING THE
READ OF THE TASK PREAMBLE INTO THE TSA
ALl4
Reserved
AL15
AN ASSIGNED DEVICE TYPE IS NOT CONFIGURED IN THE
SYSTEM
AL16
A RESIDENT REQUEST HAS BEEN ISSUED FOR A TASK
REQUIRING AN SLO, SBO, SGO OR SYC FILE. RESIDENT
TASKS CANNOT USE SYSTEM FILES.
AL17-AL18
Reserved
MPX·32 Reference
C-1
AL - Allocator (H.ALOC) (Compatibility Mode Only)
C-2
AL19
A FILE CODE TO FILE CODE ASSIGNMENT (ASSIGN4) HAS
BEEN MADE TO AN UNDEFINED FILE CODE. A FILE CODE
MUST BE DEFINED BEFORE A SECOND FILE CODE CAN BE
EQUATED BY AN ASSIGN4.
AL20
USER ATTEMPTED DEALLOCATION OF TSA
AL21
DESTROYED TASK MIDL WAS DETECTED WHILE ATTEMPTING TO
ALLOCATE DYNAMIC EXECUTION SPACE
AL22
A SOFTWARE CHECKSUM ERROR HAS OCCURRED DURING TASK
LOADING
AL23
AN INVALID USER NAME IS CATALOGED WITH THE TASK. THE
USER NAME IS NOT CONTAINED IN THE M.KEY FILE OR A
VALID KEY IS NOT SPECIFIED.
AL24
ACCESS TO AN ASSIGNED PERMANENT FILE IS BY PASSWORD
ONLY, AND A VALID PASSWORD WAS NOT INCLUDED ON THE
CATALOGED ASSIGNMENT OR JOB CONTROL STATEMENT
ASSIGNMENT
AL25
UNDEFINED RESOURCE REQUIREMENT SUMMARY (RRS) TYPE
(INTERNAL FORMAT OF AN ASSIGNMENT STATEMENT IS
WRONG)
AL26
THE TASK HAS REQUESTED MORE BLOCKING BUFFERS THAN
WERE SPECIFIED DURING CATALOG. SEE CATALOGER BUFFER
DIRECTIVE AND RECATALOG IF NEEDED.
AL27
THERE ARE NO FREE ENTRIES IN SHARED MEMORY TABLE FOR
GLOBAL, DATAPOOL, CSECT, OR OTHER SHARED AREAS
AL28
TASK IS ATTEMPTING TO SHARE AN UNDEFINED GLOBAL OR
DATAPOOL MEMORY PARTITION
AL29
TASK IS ATTEMPTING TO EXCLUDE UNDEFINED MEMORY
PARTITION
AL30
THE REQUESTED DEVICE IS ALREADY ASSIGNED TO THE
REQUESTING TASK VIA ANOTHER FILE CODE. USE ASSIGN4
OR DEALLOCATE BEFORE REALLOCATING.
AL31
LOGICAL FILE CODE ALREADY ALLOCATED BY CALLER (E.G.,
A CARD READER MAY BE ASSIGNED TO LFC 'IN' AND A
MAGNETIC TAPE CANNOT BE ASSIGNED TO THE SAME FILE
CODE). USE ASSIGN4 OR DEALLOCATE BEFORE
REALLOCATING.
AL32
DYNAMIC COMMON BLOCK MAY NOT BE ASSIGNED VIA ASSIGNl
DIRECTIVE
AL33
SHARED MEMORY DEFINITION CONFLICTS WITH CALLER'S
ADDRESS SPACE
AL34
SHARED MEMORY PARTITION NOT DEFINED IN DIRECTORY
AL35
ATTEMPT TO SHARE A DIRECTORY ENTRY THAT IS NOT A
MEMORY PARTITION
MPX-32 Abort and Crash Codes
c
AL - Allocator (H.ALOC) (Compatibility Mode Only)
(
(
AL36
INVALID PASSWORD SPECIFIED FOR SHARED MEMORY
PARTITION
AL37
ATTEMPT TO EXCLUDE UNDEFINED SHARED MEMORY PARTITION
AL38
ATTEMPT TO ACTIVATE A PRIVILEGED TASK BY
UNAUTHORIZED OWNER
AL39
SHARED MEMORY ENTRY NOT FOUND
AL40
PARTITION DEFINITION NOT FOUND IN DIRECTORY
AL41
DIRECTORY DEFINITION NOT A DYNAMIC PARTITION
AL42
INVALID PASSWORD FOR A MEMORY PARTITION
AL43
TASK HAS ATTEMPTED TO ALLOCATE AN UNSHARED RESOURCE
THAT WAS NOT AVAILABLE DURING TASK ACTIVATION IN A
MEMORY-ONLY ENVIRONMENT
AL44
UNABLE TO RESUME 'SYSBUILD' TASK DURING INITIAL TASK
ACTIVATION IN A MEMORY-ONLY ENVIRONMENT
AL45
UNABLE TO DEALLOCATE INPUT DEVICE AFTER DYNAMIC TASK
ACTIVATION IN A MEMORY-ONLY ENVIRONMENT
AL46
TASK HAS ATTEMP'l'ED TO SHARE MEMORY VIA A DYNAMIC
MEMORY PARTITION IN A MEMORY-ONLY ENVIRONMENT
AL47
DYNAMIC MEMORY PARTITIONS CANNOT BE GREATER THAN 1
MEGABYTE
AL48
THE USER HAS ATTEMPTED TO EXCLUDE A SHARED PARTITION
WHOSE ASSOCIATED MAP BLOCKS ARE NOT DESIGNATED AS
BEING SHARED IN THE TASK'S TSA
AL49
THE TASK'S DSECT SPACE REQUIREMENTS OVERLAP THE
TASK'S TSA SPACE REQUIREMENTS
AL50
THE TASK'S DSECT SPACE REQUIREMENTS OVERLAP THE
TASK'S CSECT SPACE REQUIREMENTS, OR IF NO CSECT,
LOAD MODULE IS TOO LARGE TO FIT IN USER'S ADDRESS
SPACE
AL51
DESTROYED TASK MIDL DETECTED WHILE ATTEMPTING TO
ALLOCATE SYSTEM BUFFER SPACE
AL52
AN ERROR CONDITION PERTAINING TO FILE SYSTEM
STRUCTURES HAS OCCURRED. THIS ERROR IS NOT A
FUNCTION OF THE COMPATIBILITY INTERFACE.
AL53
DES'rROYED TASK MIDL WAS DETECTED WHILE ATTEMPTING TO
ALLOCATE EXTENDED INDEXED DATA SPACE
AL54
INVALID COMPATIBLE RRS TYPE
AL55
ACCESS MODE IS NOT ALLOWED
MPX-32 Reference
C-3
AT - ANSI Labeled Tapes
C.4 AT - ANSI Labeled Tapes
ATOl
INCORRECT OR NO RUN PARAMETERS RECEIVED
AT02
INCORRECT STATUS RETURNED FROM J.ATAPE RUN REQUEST
AT03
AN ERROR OCCURRED
AT04
I/O ERROR OCCURRED ON TAPE
C.s AU - Auto-Stan Trap Processor
AUOl
TRAP OCCURRED ON AUTO-START
C.6 BT - Block Mode Timeout Trap
BTOl
BLOCK MODE TIMEOUT TRAP
C.7 CM - Call Monitor Interrupt Processor (H.lP27 and H.lPOA)
CMOl
CALL MONITOR INTERRUPT PROCESSOR CANNOT LOCATE THE
'CALM' INSTRUCTION
CM02
EXPECTED 'CALM' INSTRUCTION DOES NOT HAVE CALM
(X'30') OPCODE
CM03
INVALID 'CALM' NUMBER
CM04
'CALM' NUMBER TOO LOW (OUT OF BOUNDS)
CMOS
'CALM' NUMBER TOO BIG (OUT OF BOUNDS)
./\
\
;
"'--/
C.S CP-Cache
CPOl
CACHE PARITY ERROR OCCURRED WITHIN THE OPERATING
SYSTEM
CP02
CACHE PARITY ERROR OCCURRED IN TASK BODY
CP03
TRAP OCCURRED WHILE NO TASKS WERE IN ACTIVE STATE
CP04
TRAP OCCURRED IN ANOTHER INTERRUPT TRAP ROUTINE
o
C-4
MPX·32 Abort and Crash Codes
EX - Exit/Abort
(
c.g EX - Exit/Abort
EXOl
AN ABORT HAS OCCURRED IN THE TASK EXIT SEQUENCE
EX02
AN ABORT HAS OCCURRED DURING THE TASK ABORT SEQUENCE
AND HAS BEEN CHANGED TO A DELETE (KILL) TASK
SEQUENCE
EX03
USER ATTEMPTED TO GO TO AN ANY WAIT STATE FROM AN
END-ACTION ROUTINE
C.10 FS - File System (H.MONS)(Compatibility Mode Only)
(
FSOl
UNRECOVERABLE I/O ERROR TO THE DIRECTORY
FS02
UNRECOVERABLE I/O ERROR TO FILE SPACE ALLOCATION MAP
FS03
ATTEMPT TO ADD A NEW FILE, BUT THE DIRECTORY IS FULL
FS04
A DISC ALLOCATION MAP CHECKSUM ERROR WAS DETECTED
FS05
ATTEMPT TO ALLOCATE DISC SPACE THAT IS ALREADY
ALLOCATED
FS06
ATTEMPT TO DEALLOCATE DISC SPACE THAT IS NOT
ALLOCATED
FS07
USER HAS CALLED AN ENTRY POINT IN H.FISE THAT NO
LONGER EXISTS
C.11 HE - Online Help Facility
HEOl
ABNORMAL TERMINATION WHILE TRANSLATING HELP FILES
(HELPT)
C.12 HT - Halt Trap Processor (H.lPHT)
HTOl
AN ATTEMPT WAS MADE TO EXECUTE A HALT INSTRUCTION IN
USER'S PROGRAM
HT02
AN ATTEMPT WAS MADE TO EXECUTE A HALT INSTRUCTION IN
AN INTERRUPT TRAP ROUTINE
HT03
AN ATTEMPT WAS MADE TO EXECUTE A HALT INSTRUCTION
WHEN NO TASKS WERE IN AN ACTIVE STATE
HT04
Reserved
HT05
AN ATTEMPT WAS MADE TO EXECUTE A HALT INSTRUCTION
WHEN USER WAS UNMAPPED
MPX-32 Reference
C-5
HT - Halt Trap Processor (H.lPHT)
,~,
C.13 10 - Input/Output Control Supervisor (HJOCS)
C-6
I001
Reserved
I002
AN UNPRIVILEGED TASK IS ATTEMPTING TO READ OR WRITE
DATA INTO AN UNMAPPED ADDRESS
I003
AN UNPRIVILEGED TASK IS ATTEMPTING TO READ DATA INTO
PROTECTED MEMORY
I004-I005
Reserved
I006
INVALID BLOCKING BUFFER CONTROL CELLS IN BLOCKED
FILE ENCOUNTERED. PROBABLE CAUSES: (1) FILE IS
IMPROPERLY BLOCKED, (2) BLOCKING BUFFER IS
DESTROYED, OR (3) TRANSFER ERROR DURING FILE INPUT.
1007
THE TASK HAS ATTEMPTED TO PERFORM AN OPERATION WHICH
IS NOT VALID FOR THE DEVICE TO WHICH THE USER'S FILE
IS ASSIGNED(E.G., A READ OPERATION SPECIFIED FOR A
FILE ASSIGNED TO THE LINE PRINTER) .
I008
DEVICE ASSIGNMENT IS REQUIRED FOR AN UNPRIVILEGED
TASK TO USE THIS SERVICE
1009
ILLEGAL OPERATION ON THE SYC FILE
1010-I014
Reserved
I015
A TASK HAS REQUESTED A TYPE OPERATION AND THE TYPE
CONTROL PARAMETER BLOCK(TCPB) SPECIFIED INDICATES
THAT AN OPERATION ASSOCIATED WITH THAT TePB IS
ALREADY IN PROGRESS
I016
INVALID BLOCKING BUFFER CONTROL CELL(S) ENCOUNTERED
DURING WRITE OF BLOCKED FILE. THIS ERROR IS USUALLY
CAUSED BY A USER SPECIFIED BLOCKING BUFFER THAT HAS
BEEN DESTROYED.
I017
OPEN ATTEMPTED ON A FILE AND FPT HAS NO MATCHING
FILE CODE. PROBABLE CAUSE: (1) BAD OR MISSING RRS IN
PREAMBLE (2) LFC IN FCB HAS BEEN DESTROYED.
I018
Reserved
I019
AN ERROR HAS OCCURRED IN THE REMM CLOSE PROCEDURE
I020
AN ERROR HAS OCCURRED IN THE REMM OPEN PROCEDURE
I021
IOCS HAS ENCOUNTERED AN UNRECOVERABLE I/O ERROR IN
ATTEMPTING TO PROCESS AN I/O REQUEST ON BEHALF OF A
TASK
I022
AN ILLEGAL IOCS ENTRY POINT HAS BEEN ENTERED BY A
TASK
1023
A H.VOMM DENIAL HAS OCCURRED IN READING THE RESOURCE
DESCRIPTOR TO GET MORE SEGMENT DEFINITIONS
\lj
/
.MPX-32 Abort and Crash Codes
c
10 - Input/Output Control Supervisor CHJOCS}
(
(
1024
ILLEGAL ADDRESS, TRANSFER COUNT OR TRANSFER TYPE
(I.E., IMPROPER BOUNDING FOR DATA TYPE) SPECIFIED IN
THE FCB
1025-1027
Reserved
1028
ILLEGAL OPERATION
OR DEVICE
1029
Reserved
1030
ILLEGAL OR UNEXPECTED VOLUME NUMBER OR REEL ID
ENCOUNTERED ON MAGNETIC TAPE
1031
Reserved
1032
CALLING TASK HAS ATTEMPTED TO PERFORM A SECOND READ
ON A '$' STATEMENT THROUGH THE SYC FILE
1033
READ WITH BYTE GRANULARITY REQUEST MADE WITH
NEGATIVE BYTE OFFSET
1034
READ WITH EYTE GRANULARITY REQUEST MADE WITHOUT
SETTING RANDOM ACCESS BIT IN FCB
1035
READ WITH BYTE GRANULARITY REQUESTS ARE VALID FOR
UNBLOCKED FILES ONLY
1036-1037
Reserved
1038
WRITE ATTEMPTED ON UNIT OPENED IN READ-ONLY MODE. A
READ-WRITE OPEN WILL BE FORCED TO READ-ONLY IF TASK
HAS ONLY READ ACCESS TO UNIT.
1039
Reserved
1040
INVALID TRANSFER COUNT. TRANSFER COUNT TOO LARGE
FOR TRANSFER TYPE, TRANSFER COUNT NOT AN EVEN
MULTIPLE OF TRANSFER TYPE, OR DATA ADDRESS NOT
BOUNDED FOR TRANSFER TYPE.
1041
BLOCKING ERROR DURING NON-DEVICE ACCESS
1042
BLOCKED DATA MANAGEMENT MODULE (H.BKDM)
CONFIGURED IN THE SYSTEM
1043
INPUT/OUTPUT CONTROL LIST (IOCL) OR DATA ADDRESS NOT
IN CONTIGUOUS 'E' MEMORY (GPMC DEVICES ONLY)
1044
NON-DEVICE ACCESS I/O ERROR. THIS ERROR MAY BE THE
RESULT OF CHANNEL/CONTROLLER INITIALIZATION FAILURE.
1045
MULTIVOLUME MAGNETIC TAPE MODULE (H.MVMT) IS NOT
CONFIGURED IN THE SYSTEM
1046
Reserved
1047
CLASS 'E' DEVICE TCW IS NOT IN CLASS 'E' MEMORY.
THIS TYPE OF ERROR INDICATES A MAP FAILURE.
MPX·32 Reference
ATTE~~TED
ON AN OUTPUT ACTIVE FILE
IS NOT
C-7
10 - Input/Output Control Supervisor (H.lOCS)
c
r04 8- r04 9
Reserved
r050
AN UNPRIVILEGED USER ATTEMPTED TO EXECUTE A PHYSICAL
CHANNEL PROGRAM
r051
A 'TESTSTAR' COMMAND WAS USED IN A LOGICAL CHANNEL
PROGRAM
r052
A LOGICAL CHANNEL WAS TOO LARGE TO BE MOVED TO
MEMORY POOL
r053
A 'TIC' COMMAND FOLLOWS A 'TIC' COMMAND IN A LOGICAL
CHANNEL PROGRAM
r054
A ' TIC' COMMAND ATTEMPTED TO TRANSFER TO AN ADDRESS
WHICH IS NOT WORD BOUNDED
r055
ILLEGAL ADDRESS IN LOGICAL IOCL. ADDRESS IS NOT IN
USER'S LOGICAL ADDRESS SPACE.
r056
A READ-BACKWARD COMMAND WAS USED IN A LOGICAL
CHANNEL PROGRAM
r057
ILLEGAL IOCL ADDRESS. IOCL MUST BE LOCATED IN THE
FIRST 128K WORDS OF MEMORY.
r058-r060
Reserved
r061
INVALID LFC IN FCB
r062
ERROR OCCURRED ON IMPLICIT OPEN
r063-r076
Reserved
r077
ATTEMPT TO USE DATA FLOW CONTROL (OTHER THAN WISM),
THAT IS NOT SUPPORTED BY THE CURRENTLY INSTALLED
CONTROLLER
r078
ATTEMPT TO ISSUE AN EXECUTE CHANNEL PROGRAM TO A
WRITE SUB-CHANNEL AND THE SUB-CHANNEL WAS NOT IN
DUAL CHANNEL MODE
r 079
Reserved
r080
ILLEGAL ACCESS MODE FOR VOLUME RESOURCE
r081-r097
Reserved
r098
H.VOMM DENIAL HAS OCCURRED ON IOCS AUTOMATIC FILE
EXTENSION REQUEST FOR THE LFC SPECIFIED IN THE ABORT
MESSAGE
r099
INTERNAL SYSTEM ERROR DETECTED AT THE ADDRESS
RELATIVE TO IOCS WHICH IS SPECIFIED IN THE ABORT
MESSAGE
c
c-a
MPX-32 Abort and Crash Codes
IP -IPU
(~
C.14 IP -IPU
IPOI
ABNORMAL TASK TERMINATION IN IPU
C.15 LD - Task Activation Loading (H.TAMM)
LDOI
LOAD CODE SECTION ERROR
LD02
CODE SECTION CHECKSUM ERROR
LD03
BIAS CODE ERROR
LD04
CODE MATRIX CHECKSUM ERROR
LD05
LOAD DATA SECTION ERROR
LD06
DATA SECTION CHECKSUM ERROR
LD07
BIAS DATA ERROR
LD08
DATA MATRIX CHECKSUM ERROR
LD09
GCF R/O RELOCATION ERROR
LDIO
GCF R/W RELOCATION ERROR
C.16 MC - Machine Check Trap
MeOl
MACHINE CHECK TRAP
C.17 MF - Map Fault Trap
MFOI
A MAP FAULT TRAP HAS OCCURRED. THIS IS THE RESULT OF
A BAD MEMORY REFERENCE OUTSIDE OF THE USER'S
ADDRESSABLE SPACE.
C.18 MM - Memory Disk
MMOI
MPX·32 Reference
REQUEST FOR MEMORY DISC I/O TO A LOCATION OUTSIDE
THE MEMORY DISC BOUNDARIES
e-9
MP - Memory Parity Trap (H.lP02)
C.19 MP - Memory Parity Trap (H.lP02)
MPOl
MEMORY ERROR OCCURRED IN A TASK'S LOGICAL ADDRESS
SPACE. THIS IS AN INTERNAL OR CPU FAILURE. RERUN
TASK.
MP02
MEMORY ERROR OCCURRED IN ANOTHER INTERRUPT TRAP
ROUTINE (NESTED TRAPS, CONTEXT LOST)
MP03
MEMORY ERROR OCCURRED WHILE NO TASKS WERE IN THE
ACTIVE STATE
MP04
MEMORY ERROR OCCURRED IN A MAP BLOCK RESERVED FOR
THE O/S
MP05
ERROR OCCURRED WHILE CURRENT TASK WAS IN THE
UNMAPPED MODE
C.20 MS - System Services (H.MONS) (Compatibility Mode Only)
MSOl
PERMANENT FILE ADDRESS INQUIRY SERVICE FOUND A
NUMBER OF ALLOCATION UNITS IN THE UNIT DEFINITION
TABLE THAT DO NOT CORRESPOND TO ANY KNOWN DISC.
MS02-MS08
Reserved
MS09
TASK HAS ATTEMPTED TO CONNECT A TASK TO AN INTERRUPT
LEVEL NOT DEFINED FOR INDIRECTLY CONNECTED TASKS
MS10-MSll
Reserved
MS12
OVERLAY IS PASSWORD PROTECTED
MS13-MS15
Reserved
MS16
TASK HAS REQUESTED DYNAMIC ALLOCATION WITH AN
INVALID FUNCTION CODE
MS17
FILE NAME CONTAINS CHARACTERS OUTSIDE RANGE OF X'20'
TO X'5F', INCLUSIVELY
MS18-MS20
Reserved
MS21
MULTIVOLUME MAGNETIC TAPE ALLOCATION REQUEST MADE TO
SCRATCH (SCRA) TAPE
MS22
MULTI-VOLUME MAGNETIC TAPE ALLOCATION REQUEST MADE
ON SHARED TAPE DRIVE
MS23
TASK HAS ISSUED A 'MOUNT MESSAGE ONLY' ALLOCATION
REQUEST TO A NON-ALLOCATED DRIVE OR TO A DEVICE
WHICH IS NOT A MAGNETIC TAPE
c
C-10
MPX·32 Abort and Crash Codes
MS - System Services (H.MONS) (Compatibility Mode Only)
(~
C.21
MS24
TASK HAS SPECIFIED AN ILLEGAL VOLUME NUMBER (ZERO IF
TAPE IS MULTIVOLUME, NONZERO IF TAPE IS SINGLE
VOLUME)
MS25-MS27
Reserved
MS28
A PERMANENT FILE LOG HAS BEEN REQUESTED, BUT THE
ADDRESS SPECIFIED FOR STORAGE OF THE DIRECTORY ENTRY
IS NOT CONTAINED WITHIN THE CALLING TASK'S LOGICAL
ADDRESS SPACE
MS 2 9
Reserved
MS30
TASK HAS ATTEMPTED TO OBTAIN A PERMANENT FILE LOG IN
A MEMORY-ONLY ENVIRONMENT
MS31
USER ATTEMPTED TO GO TO THE ANY-WAIT STATE FROM AN
END-ACTION ROUTINE
MS 3 2
Reserved
MS33
ALLOCATION ERROR IN RTM M.ALOC CALL
MS34-MS86
Reserved
MS87
NO DENIAL RETURN ADDRESS SPECIFIED ON CALM M.ALOC
EMULATION
NM - Nonpresent Memory Trap
NMOI
A NONPRESENT MEMORY TRAP ERROR CONDITION HAS
OCCURRED.
C.22 OC - Operator Communications
oeOI
THE OPERATOR HAS REQUESTED THAT THE TASK BE ABORTED
C.23 PT - Task Activation (J.TSM)
PTOI
INVALID ATTEMPT TO MULTICOPY A UNIQUE TASK
PT02
FILE SPECIFIED IS NOT IN DIRECTORY
PT03
UNABLE TO ALLOCATE FILE
PT04
FILE IS NOT A VALID LOAD MODULE OR EXECUTABLE IMAGE
PT05
DQE IS NOT AVAILABLE
PT06
READ ERROR ON RESOURCE DESCRIPTOR
MPX-32 Reference
C-11
PT - Task Activation (J.TSM)
PT07
READ ERROR ON LOAD MODULE
PT08
INSUFFICIENT LOGICAL/PHYSICAL ADDRESS SPACE FOR TASK
ACTIVATION
PT09
CALLING TASK IS UNPRIVILEGED
PTIO
INVALID PRIORITY
PTII
INVALID SEND BUFFER ADDRESS OR SIZE
PTl2
INVALID RETURN BUFFER ADDRESS OR SIZE
PTl3
INVALID NO-WAIT MODE END ACTION ROUTINE ADDRESS
PTl4
MEMORY POOL UNAVAILABLE
PTl5
DESTINATION TASK RECEIVER QUEUE FULL
PTl6
INVALID PSB ADDRESS
PTl7
RRS LIST EXCEEDS 384 WORDS
PTl8
INVALID RRS ENTRY IN PARAMETER BLOCK
C.24 PV - Privilege Violation Trap
PVOI
PRIVILEGE VIOLATION TRAP
C.2S RC - Record Manager
C-12
RCOI
LESS THAN ONE BLOCK ON READ
RC02
NOT A MULTIPLE NUMBER OF BLOCKS READ
RC03
NO MORE IOC'S AVAILABLE
RC04
ERROR CONDITION ON READ
RC05
PREMATURE END-OF-FILE
RC06
END-OF-MEDIUM ON OUTPUT FILE
RC07
WRITE ATTEMPTED ON UNOPENED FILE
RC08
USER RECORD SIZE TOO LARGE
RC09
READ NOT ALLOWED AFTER WRITE
RCIO
ERROR ON WRITE
RCII
END-OF-MEDIUM ON OUTPUT FILE
I
MPX-32 Abort and Crash Codes
RC - Record Manager
(
RC12
INTERNAL FILE POSITION ERROR
RC13
RESOURCE CANNOT BE OPENED
RC14
INTERNAL FILE POSITION ERROR
RC15
INVALID BLOCKING BUFFER CELL
C.26 RE - Restart
RE01
RESTART IS INVALID IN BATCH OR COMMAND FILE MODE
C.27 RF - Rapid File Allocation
(
RF01
INVALID PATHNAME
RF02
PATHNAME CONSISTS OF VOLUME ONLY
RF03
VOLUME NOT MOUNTED
RF04
Reserved
RF05
FILE IS NOT A PERMANENT FILE
RF06
Reserved
RF07
RESOURCE DOES NOT EXIST
RF08
RESOURCE NAME IN USE
RFO 9
Reserved
RF10
MDT ENTRY UNAVAILABLE
RF 11-RF 14
Reserved
RF15
VOLUME MUST BE MOUNTED PUBLIC
RF16-RF59
Reserved
RF60
INVALID MODE
RF 61- RF 9 8
Reserved
RF99
WARNING, INPUT ERRORS ENCOUNTERED, CHECK SLO OUTPUT
C.28 RM - Resource Management (H.REMM)
RM01
UNABLE TO LOCATE RESOURCE
RM02
ACCESS MODE NOT ALLOWED
MPX-32 Reference
C-13
RM - Resource Management (H.REMM)
C-14
RM03
TOO MANY ASSIGNMENTS
RM04
BLOCKING BUFFER SPACE NOT AVAILABLE OR INVALID
BUFFER ADDRESS
RM05
SHARED MEMORY TABLE (SMT) ENTRY NOT FOUND
RM06
TOO MANY MOUNT REQUESTS
RM07
STATIC ASSIGN TO DYNAMIC COMMON
RM08
UNRECOVERABLE I/O ERROR
RM09
INVALID USAGE SPECIFICATION
RMl0
INVALID PARAMETER ADDRESS
RMll
INVALID RESOURCE REQUIREMENT SUMMARY (RRS) ENTRY
RM12
INVALID LFC TO LFC ASSIGNMENT
RM13
DEVICE NOT IN SYSTEM OR OFF-LINE
RM14
RESOURCE ALREADY ALLOCATED BY TASK
RM15
INVALID SYC/SGO ASSIGNMENT
RM16
COMMON CONFLICTS WITH TASK ADDRESS SPACE
RM17
DUPLICATE LFC ASSIGNMENT
RM18
INVALID DEVICE SPECIFICATION
RM19
INVALID RESOURCE ID (RID)
RM20
VOLUME UNASSIGNED OR ACCESS NOT ALLOWED
RM21
UNABLE TO MOUNT.
RM22
RESOURCE MARKED FOR DELETION
RM23
ASSIGNED DEVICE IS MARKED OFF-LINE
RM24
UNABLE TO LOCATE MOUNTED VOLUME TABLE(MVT) ENTRY
RM25
RANDOM ACCESS NOT ALLOWED
RM26
ATTEMPT TO WRITE ON SYC
RM27
RESOURCE ALREADY OPENED IN DIFFERENT MODE
RM28
INVALID ACCESS SPECIFICATION AT OPEN
RM29
INVALID FILE CONTROL BLOCK(FCB) ADDRESS OR
UNASSIGNED LFC IN FCB
RM30
INVALID ALLOCATION INDEX
J.MOUNT RUN REQUEST FAILED
c
MPX-32 Abort and Crash Codes
RM - Resource Management (H.REMM)
RM31
RESOURCE NOT OPEN
RM32
LOCK NOT OWNED BY THIS TASK
RM33
RESOURCE IS NOT ALLOCATED IN A SHARABLE MODE
RM34
SYSTEM ADMINISTRATOR ATTRIBUTE IS REQUIRED TO MOUNT
A PUBLIC VOLUME
RM35
RESOURCE IS NOT A SHARED IMAGE
RM36
PHYSICAL MEMORY ALREADY ALLOCATED
RM37
ATTEMPT TO ALLOCATE NONPRESENT PHYSICAL MEMORY
RM38
TIME OUT WAITING FOR RESOURCE
RM39
UNABLE TO PERFORM WRITE BACK
RM40
INVALID LOAD MODULE
RM41
INVALID PHYSICAL ADDRESS SPECIFIED
RM42
USER REQUESTED ABORT OF MOUNT PROCESS
RM43
USER REQUESTED HOLD ON MOUNT PROCESS
RM44
WRITEBACK REQUESTED AND SHARED IMAGE HAS NO
WRITEBACK SECTION
RM45
LOADING ERROR DURING INCLUSION OF READ ONLY SECTION
OF SHARED IMAGE
RM46
UNABLE TO OBTAIN RESOURCE DESCRIPTOR LOCK (MULTIPORT
ONLY)
RM47
LOADING ERROR DURING INCLUSION OF READ/WRITE SECTION
OF SHARED IMAGE
RM48
INCOMPATIBLE LOAD ADDRESSES FOR SHARED IMAGE
RM49
TASK HAS REQUESTED EXCESSIVE NUMBER OF MULTICOPIED
SHARED IMAGES WITH NO READ ONLY SECTION
RM50
RESOURCE IS LOCKED BY ANOTHER TASK
RM51
SHAREABLE RESOURCE IS ALLOCATED BY ANOTHER TASK IN
AN INCOMPATIBLE ACCESS MODE
RM52
VOLUME SPACE IS NOT AVAILABLE
RM53
ASSIGNED DEVICE IS NOT AVAILABLE
RM54
UNABLE TO ALLOCATE RESOURCE FOR SPECIFIED USAGE
RM55
ALLOCATED RESOURCE TABLE (ART) SPACE IS NOT
AVAILABLE
MPX-32 Reference
C-15
RM - Resource Management (H.REMM)
C-16
RM56
TASK REQUIRES SHADOW MEMORY AND NONE IS CONFIGURED
RM57
VOLUME IS NOT AVAILABLE FOR MOUNT WITH REQUESTED
USAGE
RM58
SHARED MEMORY TABLE (SMT) SPACE IS NOT AVAILABLE
RM59
MOUNTED VOLUME TABLE (MVT) SPACE IS NOT AVAILABLE
RM60
RESOURCE DESCRIPTOR SPACE DEFINITION CONFLICT
RM61
UNABLE TO LOCATE OR RETRIEVE RESOURCE DESCRIPTOR
RM62
INVALID OPTION IN CNP
RM63
SEGMENTED TASK SUPPORT NOT PRESENT.
RM64
THE TASK'S DSECT SPACE REQUIREMENTS OVERLAP THE
TASK'S TASK SERVICE AREA (TSA) SPACE REQUIREMENTS
RM65
THE TASK'S DSECT SPACE REQUIREMENTS OVERLAP THE
TASK'S CSECT SPACE REQUIREMENTS, OR IF NO CSECT,
LOAD MODULE IS TOO LARGE TO FIT IN USER'S ADDRESS
SPACE
RM66
SOFTWARE CHECKSUM.
RECATALOGING.
RM67
EXCESSIVE MEMORY REQUEST
RM68
EXCESSIVE VOLUME SPACE REQUESTED
RM69
INVALID USERNAME SPECIFIED
RM70
INVALID PRIVILEGED ACTIVATION
RM71
Reserved
RM72
UNABLE TO RESUME SYSINIT ON TAPE ACTIVATION
RM73
FILE OVERLAP HAS OCCURRED. PLEASE CHECK THE SYSTEM
CONSOLE
RM74
LOADING ERROR
RM75
INVALID WORK VOLUME/DIRECTORY
RM76
USER ATTEMPTED DEALLOCATION OF TSA
RM77
A TASK HAS DESTROYED THE ALLOCATION LINKAGES IN ITS
DYNAMIC EXPANSION SPACE
RM78
UNABLE TO LOAD TASK DEBUGGER WITH TASK
RM79
INVALID CALLER NOTIFICATION PACKET (CNP) ADDRESS
RM80
SHARED IMAGE VERSION LEVEL IS NOT COMPATIBLE WITH
EXECUTABLE IMAGE
ERROR MAY BE FIXED BY
MPX-32 Abort and Crash Codes
RM - Resource Management (H.REMM)
(
RM81
INVALID ACTIVATION OF A BASE MODE TASK ON A SYSTEM
CONFIGURED FOR NON-BASE TASK EXECUTION.
RM82
INVALID ACTIVATION OF AN ADA TASK ON A SYSTEM
CONFIGURED WITHOUT ADA SUPPORT.
RM83
INSUFFICIENT LOGICAL ADDRESS SPACE TO ACTIVATE TASK
RM84
INVALID LOGICAL POSITION FOR EXTENDED MPX
RM85
PTRACE DEBUG REQUESTED AND H.PTRAC NOT CONFIGURED
RM86
CANNOT DISMOUNT THE SYSTEM VOLUME.
RM87
PUBLIC VOLUME DISMOUNT DENIED DUE TO COMPATIBLE MODE
PUBLIC DISMOUNT OPTION SET FOR THIS SYSTEM.
RM88
PUBLIC DISMOUNT DENIED. SYSTEM ADMINISTRATOR
ATTRIBUTE REQUIRED FOR THIS OPERATION.
RM89
PUBLIC DISMOUNT DENIED DUE TO MISSING OPTION FOR
PUBLIC VOLUME IN THE DISMOUNT REQUEST
RM90
GCL LOADMODULE OR SHIM CANNOT BE RELOCATABLE
RM91
UNABLE TO ACCESS VOLUME DUE TO PENDING PHYSICAL
DISMOUNT.
RM92
READ ONLY OR READ WRITE LOAD ADDRESS IS INVALID
RM93
UNABLE TO PERFORM PHYSICAL MOUNT DUE TO SYSTEM
SHUTDOWN IN PROGRESS.
RM94
J.MOUNT ATTEMPTED TO MOUNT AN UNFORMATTED DISC
VOLUME.
RM95
AN UNBIASED TASK REQUIRES SHADOW MEMORY ON A SYSTEM
WITH NO OVERLAPPING CPU/IPU SHADOW REGION
RM96
A BIASED TASK REQUIRES SHADOW MEMORY THAT DOES NOT
EXIST ON THE SPECIFIED PROCESSOR
RM97
Reserved
RM98
THE TASK REQUIRES MORE SHADOW MEMORY THAN EXISTS
C.29 RX - Resident Executive Services (H.REXS)
RXOl
Reserved
RX02
INVALID FUNCTION CODE SPECIFIED FOR REQUEST TO
CREATE A TIMER ENTRY. VALID CODES ARE ACP (1), RSP
OR RST (2), STB (3), RSB (4) AND RQI (5).
RX03
TASK ATTEMPTED TO SET/RESET A BIT OUTSIDE OF A
STATIC PARTITION OR THE OPERATING SYSTEM.
MPX-32 Reference
C-17
RX - Resident Executive Services (H.REXS)
RX04
THE REQUESTING TASK IS UNPRIVILEGED OR HAS ATTEMPTED
TO CREATE A TIMER ENTRY TO REQUEST AN INTERRUPT WITH
A PRIORITY LEVEL OUTSIDE THE RANGE OF X'12' TO
X'7F', INCLUSIVELY
RX05
INVALID FUNCTION CODE HAS BEEN SPECIFIED FOR REQUEST
TO SET USER STATUS WORD
RX06
UNPRIVILEGED TASK ATTEMPTED TO RESET A TASK PRIORITY
LEVEL, OR A PRIVILEGED TASK ATTEMPTED TO RESET A
TASK PRIORITY TO A LEVEL OUTSIDE THE RANGE OF 1 TO
64, INCLUSIVELY
RX07
CANNOT LOAD OVERLAY SEGMENT DUE TO SOFTWARE CHECKSUM
OR DATA ERROR
RX08
OVERLAY IS NOT IN THE DIRECTORY
RX09
ReselVed
RXI0
OVERLAY HAS AN INVALID PREAMBLE
RXll
AN UNRECOVERABLE I/O ERROR HAS OCCURRED DURING
OVERLAY LOADING
RX12
ReselVed
RX13
FUNCTION CODE SUPPLIED TO A DATE/TIME SERVICE IS OUT
OF RANGE
RX14
DESTINATION BUFFER ADDRESS IS INVALID OR PROTECTED
RX15
ATTEMPT TO SET EXCEPTION RETURN ADDRESS WHEN
ARITHMETIC EXCEPTION NOT IN PROGRESS
RX16-RX24
ReselVed
RX25
OPERATOR HAS ABORTED TASK IN RESPONSE TO MOUNT
MESSAGE
RX26-RX28
ReselVed
RX29
TASK HAS ATTEMPTED TO LOAD THE INTERACTIVE TASK
DEBUGGER OVERLAY IN A MEMORY-ONLY ENVIRONMENT
RX30-RX31
ReselVed
RX32
INVALID DQE ADDRESS
RX33
OVERLAY LINKAGES HAVE BEEN DESTROYED BY LOADING A
LARGER OVERLAY
RX34
TASK HAS MADE A BREAK RECEIVER EXIT CALL WHILE NO
BREAK IS ACTIVE
RX35
ReselVed
;~\
I,-~/
o
C-18
MPX-32 Abort and Crash Codes
RX - Resident Executive Services (H.REXS)
RX36
STATUS IN REGISTER ZERO IS NOT A ZERO OR A VALID
ABORT CODE
Rx37-RX85
Reserved
Rx86
TASK HAS MADE AN END ACTION ROUTINE EXIT WHILE END
ACTION WAS NOT ACTIVE
RX87
Reserved
Rx88
RESERVED FOR DEBUG LINK SERVICE
RX89
AN UNPRIVILEGED TASK HAS ATTEMPTED TO REESTABLISH AN
ABORT RECEIVER (OTHER THAN M.IOEX)
Rx90
TASK HAS MADE A RUN REQUEST END ACTION ROUTINE EXIT
WHILE THE RUN REQUEST INTERRUPT WAS NOT ACTIVE
RX91
TASK HAS ATTEMPTED NORMAL EXIT WITH A TASK INTERRUPT
STILL ACTIVE
RX92
TASK HAS ATTEMPTED NORMAL EXIT WITH MESSAGES IN ITS
RECEIVER QUEUE
RX93
AN INVALID RECEIVER EXIT BLOCK (RXB) ADDRESS WAS
ENCOUNTERED DURING MESSAGE EXIT
Rx94
AN INVALID RECEIVER EXIT BLOCK (RXB) RETURN BUFFER
ADDRESS WAS ENCOUNTERED DURING MESSAGE EXIT
RX95
TASK HAS MADE A MESSAGE EXIT WHILE THE MESSAGE
INTERRUPT WAS NOT ACTIVE
Rx96
AN INVALID RECEIVER EXIT BLOCK (RXB) ADDRESS WAS
ENCOUNTERED DURING RUN RECEIVER EXIT
Rx97
AN INVALID RECEIVER EXIT BLOCK (RXB) RETURN BUFFER
ADDRESS WAS ENCOUNTERED DURING RUN RECEIVER EXIT
RX98
TASK HAS MADE A RUN RECEIVER EXIT WHILE THE RUN
RECEIVER INTERRUPT WAS NOT ACTIVE
Rx99
TASK HAS MADE A MESSAGE END-ACTION ROUTINE EXIT
WHILE THE MESSAGE INTERRUPT WAS NOT ACTIVE
C.30 SB - System Binary Output
SBOl
AN I/O ERROR HAS BEEN ENCOUNTERED ON THE DEVICE
ASSIGNED AS THE SYSTEM BINARY (PUNCHED) OUTPUT
DEVICE
SB02
THE SYSTEM OUTPUT PROGRAM HAS ENCOUNTERED AN
UNRECOVERABLE I/O ERROR IN ATTEMPTING TO READ A
PUNCHED OUTPUT FILE FROM DISC
SB03
DENIAL OF FILE CODE TO FILE CODE ALLOCATION FOR
J.SOUT2 INDICATES LOSS OF SYSTEM INTEGRITY
(
MPX-32 Reference
C-19
SB - System Binary Output
SB04
SYSTEM BINARY OUTPUT ABORTED BY OPERATOR
SB05
NO TIMER ENTRY FOR SYSTEM BINARY OUTPUT (SYSTEM
FAULT)
SB06
FIVE ECHO CHECK ERRORS DETECTED WHILE ATTEMPTING TO
PUNCH A SINGLE CARD
C.31 SC - System Check Trap Processor
seOl
SYSTEM CHECK TRAP OCCURRED AT AN ADDRESS LOCATED
WITHIN THE OPERATING SYSTEM
se02
SYSTEM CHECK TRAP OCCURRED WITHIN THE CURRENT TASK'S
SPACE
se03
SYSTEM CHECK TRAP OCCURRED AT A TIME WHEN THERE WERE
NO TASKS CURRENTLY BEING EXECUTED (C.PRNO EQUALS
ZERO)
se04
SYSTEM CHECK TRAP OCCURRED WITHIN ANOTHER TRAP
(C.GINT DOES NOT EQUAL '1')
C.32 SO - SCSI Disk
SDOO
NO ADDITIONAL SENSE INFORMATION
5001
NO INDEX/SECTOR SIGNAL
5002
NO SEEK COMPLETE
SD03
WRITE FAULT
5004
DRIVE NOT READY
5005
DRIVE NOT SELECTED
5006
NO TRACK ZERO FOUND
5007
MULTIPLE DRIVES SELECTED
5008
LOGICAL UNIT COMMUNICATIONS FAILURE
S009
TRACK FOLLOWING ERROR
5010-5015
Reserved
5016
ID CRC OR ECC ERROR
SD17
UNRECOVERED READ ERROR OF DATA BLOCKS
5018
NO ADDRESS MARK FOUND IN ID FIELD
.-~
l(,
~/
C-20
MPX-32 Abort and Crash Codes
50 - SCSI Oisk
(
SD19
NO ADDRESS MARK FOUND IN DATA FIELD
SD20
NO RECORD FOUND
SD21
SEEK POSITIONING ERROR
SD22
DATA SYNCHRONIZATION MARK ERROR
SD23
RECOVERED READ DATA WITH TARGET'S READ RETRIES (NOT
WITH ECC)
SD24
RECOVERED READ DATA WITH TARGET'S ECC CORRECTION
(NOT WITH RETRIES)
SD25
DEFECT LIST ERROR
SD26
PARAMETER OVERRUN
SD27
SYNCHRONOUS TRANSFER ERROR
SD28
PRIMARY DEFECT LIST NOT FOUND
SD29
COMPARE ERROR
SD30
RECOVERED ID WITH TARGET'S ECC CORRECTION
SD31
Reserved
SD32
INVALID COMMAND OPERATION CODE
SD33
ILLEGAL LOGICAL BLOCK ADDRESS. ADDRESS GREATER THAN
THE LBA RETURNED BY THE READ CAPACITY DATA WITH PMI
BIT NOT SET IN CDB
SD34
ILLEGAL FUNCTION FOR DEVICE TYPE
SD35
Reserved
SD36
ILLEGAL FIELD IN CDB
SD37
INVALID LUN
SD38
INVALID FIELD IN PARAMETER LIST
SD39
WRITE PROTECTED
SD40
MEDIUM CHANGE
SD41
POWER ON OR RESET OR BUS DEVICE RESET OCCURRED
SD42
MODE SELECT PARAMETERS CHANGED
SD43-SD47
Reserved
SD48
IMCOMPATIBLE CARTRIDGE
MPX-32 Reference
I
I
I
I
I
I
I
I
I
I
I
C-21
so -
SCSI Disk
SD49
MEDIUM FORMAT CORRUPTED
SD50
NO DEFECT SPARE LOCATION AVAILABLE
SD51-SD63
Reserved
SD64
RAM FAILURE
SD65
DATA PATH DIAGNOSTIC FAILURE
SD66
POWER ON DIAGNOSTIC FAILURE
SD67
MESSAGE REJECT ERROR
SD68
INTERNAL CONTROLLER ERROR
SD69
SELECT/RESELECT FAILED
SD70
UNSUCCESSFUL SOFT RESET
SD71
SCSI INTERFACE PARITY ERROR
SD72
INITIATOR DETECTED ERROR
SD73
INAPPROPRIATE/ILLEGAL MESSAGE
C.33 SG - System Generator (SYSGEN)
C-22
SGOl
INVALID LOADER FUNCTION CODE IN BINARY OBJECT MODULE
FROM THE SYSTEM RESIDENT MODULE (OBJ) FILE
SG02
INVALID BINARY RECORD READ FROM SYSTEM RESIDENT
MODULE (OBJ) FILE (BYTE 0 MUST BE X'FF' OR X'DF')
SG03
SEQUENCE ERROR IN MODULE BEING READ FROM TEMPORARY
FILE
SG04
CHECKSUM ERROR IN MODULE BEING READ FROM TEMPORARY
FILE
SG05
UNABLE TO FIND CDT AND/OR UDT FOR I/O MODULE LOAD
SG06
UNABLE TO OBTAIN ADDITIONAL MEMORY REQUIRED FOR
RESIDENT SYSTEM IMAGE MODULE LOADING
SG07
UNABLE TO OBTAIN MEMORY REQUIRED FOR RESIDENT SYSTEM
IMAGE CONSTRUCTION
SG08
NON-RELOCATABLE BYTE STRING ENCOUNTERED IN BINARY
MODULE BEING PROCESSED FROM TEMPORARY FILE
SG09
UNABLE TO ALLOCATE TEMPORARY FILE SPACE
SGIO
OVERRUN OF SYSGEN ADDRESS SPACE BY SYSTEM BEING
GENERATED. PROBABLE ERRONEOUS SIZE SPECIFICATION IN
PATCH OR POOL DIRECTIVE.
MPX-32 Abort and Crash Codes
c
SG - System Generator (SYSGEN)
(
(
SGll
SEQUENCE ERROR WHILE READING OBJECT MODULE FROM FILE
ASSIGNED TO 'OBJ'
SG12
CHECKSUM ERROR WHILE READING OBJECT MODULE FROM FILE
ASSIGNED TO 'OBJ'
SG13
UNABLE TO ALLOCATE DISC SPACE FOR SYMTAB FILE.
POSSIBLE CAUSES ARE INSUFFICIENT DISC SPACE OR
ACCESS RIGHTS DENIAL.
SG14
UNABLE TO ALLOCATE DISC SPACE FOR SYSTEM IMAGE FILE.
POSSIBLE CAUSES ARE INSUFFICIENT DISC SPACE, ACCESS
RIGHTS DENIAL, OR ATTEMPTING TO SYSGEN OVER CURRENT
DEFAULT IMAGE.
SG15
MAXIMUM NUMBER (240) OF SYMBOL TABLE/PATCH FILE
ENTRIES EXCEEDED
SG16
MISSING SYSTEM OR SYMTAB DIRECTIVE
SG17
INVALID IPU INTERVAL TIMER PRIORITY. MUST NOT BE
BETWEEN X'78' AND X'7F'.
SG18
MAXIMUM SIZE OF 88K FOR TARGET SYSTEM HAS BEEN
EXCEEDED
SG19
ATTEMPT TO DEFINE INTERRUPT VECTORING ROUTINE AS
SYSTEM REENTRANT. ONLY DEVICE HANDLERS MAY BE SYSTEM
REENTRANT.
SG20
UNABLE TO FIND "LINK" DEVICE IN UDT
SG21
INSUFFICIENT ROOM IN MEMORY POOL FOR DOWNLOAD FILE
LIST
SG22
Reserved
SG23
SHARE DIRECTIVE SPECIFIED WITHOUT ENOUGH SMT
ENTRIES. ENTRIES MUST EXCEED OR BE EQUAL TO THE
NUMBER OF PARTITIONS PLUS MEMORY DISCS.
SG24
ATTEMPT TO DEFINE PARTITION STARTING MAPBLOCK NUMBER
IN OPERATING SYSTEM AREA
SG25
ATTEMPT TO DEFINE PARTITION STARTING MAPBLOCK NUMBER
IN NON-CONFIGURED PHYSICAL MEMORY
SG26
ATTEMPT TO USE A MODULE INCOMPATIBLE WITH THE TARGET
MACHINE TYPE. THE OFFENDING MODULE NAME IS THE LAST
ENTRY ON THE LISTING FOLLOWED BY THREE ASTERISKS
(***) .
SG27
THE DEVICE SPECIFIED IN EITHER THE SWAPDEV, SID, LOD
OR POD DIRECTIVE IS NOT INCLUDED IN THE
CONFIGURATION BEING BUILT
SG28
THE NULL DEVICE SPECIFICATION WHICH IS REQUIRED TO
BE INCLUDED IN EVERY CONFIGURATION IS MISSING
MPX·32 Reference
C-23
SG - System Generator (SYSGEN)
SG29
SYSINIT OBJECT MODULE MISSING ON SYSGEN OBJECT INPUT
FILE (OBJ).
IT MUST BE THE LAST MODULE.
SG30
THE FILE ASSIGNED TO FILE CODE OBJ DOES NOT CONTAIN
VALID OBJECT CODE
SG31
THE GENERATED IMAGE CONTAINS UNSATISFIED EXTERNAL
REFERENCES. SEE THE SLO OUTPUT FOR MORE DETAILS.
THIS IS NOT A FATAL ABORT AND THE SYSTEM IMAGE IS
PRODUCED.
SG32
ONE OR MORE REQUESTED OBJECT MODULES COULD NOT BE
LOCATED ON THE INPUT OBJECT FILE. SEE THE SLO
OUTPUT FOR MORE DETAILS.
THIS IS NOT A FATAL ABORT
AND THE SYSTEM IMAGE IS PRODUCED.
SG33
EVENT TRACE HAS BEEN ENABLED WITH NO MEMORY
PARTITION RESERVED FROM X'78000' TO X'80000'
SG34
Reserved
SG35
INSUFFICIENT MEMORY POOL FOR STATIC PARTITION
SG36
UNMAPPED DEBUG MODULE (H.DBUG2) IS MISSING ON SYSGEN
OBJECT INPUT FILE. IT MUST BE THE LAST MODULE IF THE
SYSTEM DEBUGGER IS TO BE CONFIGURED.
SG37
COMMUNICATION REGION + DSECT + ADAPTIVE REGION
EXCEEDS 16KW
SG38
MPX EXTENDED CODE AREA EXTENDS PAST LOGICAL LIMIT
SG39
INVALID MPX EXTENDED CODE AREA LOGICAL MAP START
SG40
DIRECTIVE ERRORS ENCOUNTERED.
SG41
H.IPPF COULD NOT BE LOCATED ON THE INPUT OBJECT
FILE. MODULE IS NECESSARY FOR DEMAND PAGE.
SG42-SG97
Reserved
SG98
ERROR ENCOUNTERED DURING OBJECT PROCESSING PRECEDED
BY MESSAGE DESCRIBING THE ERROR CONDITION
SG99
DIRECTIVE ERRORS ENCOUNTERED
IMAGE PRODUCED.
C.34 SH - Shadow Memory (J.SHAD)
SHOl
J.SHAD ABORTED. SEE OUTPUT (UT IF INTERACTIVE OR SLO
IF BATCH), FOR ACTUAL ERROR DESCRIPTION(S).
C.35 SN - System Input Task (J.SSIN)
SNOO
C-24
INVALID RUN REQUEST PARAMETERS
MPX-32 Abort and Crash Codes
SS - Sort/Merge (FSORT2)
(
C.36 SS - Sort/Merge (FSORT2)
SSOl
CTL NOT ALLOCATED
SS02
HEADER DIRECTIVE MISSING
SS03
CONTROL FILE EMPTY
SS04
DIRECTIVE CODE NOT VALID
SS05-S806
Reserved
S807
OUTPUT FILE CODE (OUT) NOT ALLOCATED
SS08
RECORD LENGTH NOT DIVISIBLE INTO INPUT PHYSICAL
RECORD LENGTH
8809
RECORD LENGTH EXCEEDS INPUT PHYSICAL RECORD LENGTH
SS10
INPUT RECORD LENGTH EXCEEDS MAXIMUM ALLOWED (4095)
S811
RECORD LENGTH NOT DIVISIBLE INTO OUTPUT PHYSICAL
RECORD LENGTH
SS12
RECORD LENGTH EXCEEDS OUTPUT BLOCK LENGTH
8S13
OUTPUT PHYSICAL RECORD LENGTH EXCEEDS MAXIMUM
ALLOWED (4095)
SS14
.. 1 PRESENT BUT NOT A DISC FILE
SS15
.. 2 PRESENT BUT NOT A DISC FILE
SS16
COMPARISON INDICATOR NOT VALID
S817
Reserved
8818
WK1 HAS BEEN ALLOCATED BY THE USER
SS19
WK2 HAS BEEN ALLOCATED BY THE USER
SS20
FIELD DIRECTIVE ERROR: STARTING POSITION IS GREATER
THAN FIELD ENDING POSITION
8S21
FIELD DIRECTIVE ERROR: STARTING POSITION EXCEEDS
RECORD LENGTH
SS22
FIELD DIRECTIVE ERROR: ENDING POSITION EXCEEDS
LOGICAL RECORD LENGTH
S823-SS27
Reserved
SS28
INAPPROPRIATE COMBINATION OF TOURNAMENT PARAMETERS
EXCEEDS MEMORY POOL LIMITS
SS29
DISC SPACE CANNOT BE ALLOCATED FOR WORK FILE 1
MPX-32 Reference
C-2S
SS - Sort/Merge (FSORT2)
SS30
DISC SPACE CANNOT BE ALLOCATED FOR WORK FILE 2
SS31
FILE TO FILE ALLOCATION FOR WORKFILE HAS FAILED
S532
SORT BUFFER TOO SMALL
5533-5539
Reserved
5540
INPUT FILES ARE EMPTY: NO RECORD INPUT OR SORTED
5S41
WKl OR WK2 FILES TOO SMALL
5542
MERGE ONLY SELECTED BUT NO MERGE FILES (MG1-MG8) ARE
ASSIGNED
5543-5547
Reserved
5S48
SORT ATTEMPTED WITHOUT GOOD CALL TO SORT:HDR
5549-5557
Reserved
5558
INAPPROPRIATE COMBINATION OF BUFFER PARAMETERS
DETECTED DURING OUTPUT PHASE
5S59
END OF MEDIUM DETECTED ON THE OUT FILE
5S60-5568
Reserved
5569
COMPARE TABLE TYPE DESTROYED: SORT PROBLEM
5S70-5597
Reserved
S598
ERROR OPENING FILE LO
SS99
ERROR OPENING FILE OUT
(/
C.37 ST - System Output Task (J.SOUT)
ST01
UNRECOVERABLE WRITE ERROR TO DESTINATION DEVICE
ST02
UNABLE TO PERFORM ALLOCATION OF SEPARATOR FILE CODE
ST03
UNABLE TO ISSUE MAGNETIC TAPE MOUNT MESSAGE VIA
ALLOCATION SERVICE
Whenever a system output task aborts, the task may be restarted with the OPCOM
REPRINT or REPUNCH commands.
C.38 SV - SVC Trap Processor (H.lP06)
SV01
UNPRIVILEGED TASK ATTEMPTING TO USE M.CALL
SV02
INVALID SVC NUMBER
'-'"
(' J
I,
I,' "
C·26
MPX-32 Abort and Crash Codes
'
SV - SVC Trap Processor (H.lP06)
(
SV03
UNPRIVILEGED TASK ATTEMPTING TO USE A 'PRIVILEGEDONLY' SERVICE
SV04
INVALID SVC TYPE
SV05
UNPRIVILEGED TASK ATTEMPTING TO USE M.RTRN
SV06
INVALID MODULE NUMBER OR ENTRY POINT
SV07
ATTEMPTING TO USE A SVC WHICH IS INVALID FOR BASE
REGISTER OPERATIONS
SV08
SVC 0, 1 OR 2 ATTEMPTED THAT WOULD RESULT IN A TSA
STACK OVERFLOW (I.E. T.REGP GREATER THAN T.LASTP)
SV09
ATTEMPT TO USE A COMPATIBLE MODE SERVICE WITH NOCMS
SPECIFIED IN SYSGEN
C.39 SW - Swap Scheduler Task (J.SWAPR)
SWOl
I/O ERROR ON INSWAP OR OUTSWAP
SW02
EOM DETECTED ON SWAP FILE
SW03
CAN NOT CREATE SWAP FILE SPACE DIRECTORY IN MEMORY
POOL
SW04
SWAP FILE SPACE DIRECTORY IS FULL
SW05
TASK HAS REQUESTED INSWAP BUT WAS NEVER OUTSWAPPED
C.40 SX - System Output Executive (J.SOEX)
C.41
SXOI
INVALID RUN REQUEST HEADCELL COUNT
SX02
LOAD MODULE J.SOUT DOES NOT EXIST
SY - System Initialization (SYSINIT)
SYOI
SYSTEM HALT OCCURRED DURING SYSINIT PHASE ONE
PROCESSING
SY02
SYSTEM HALT DUE TO MEMORY PARITY ERROR BEING
DETECTED IN THE OPERATING SYSTEM
(
MPX-32 Reference
C-27
TO - Terminal Type Set/Reset Utility (J.TSET)
C.42 TO - Terminal Type Set/Reset Utility (J.TSET)
TD01
ATTEMPTED TO RUN J.TSET IN BATCH MODE
TD02
J.TSET WAS UNABLE TO OPEN UT FOR PROCESSING
·C.43 TS - Terminal Support
TS01
USER REQUESTED REMOVAL FROM A BREAK REQUEST
TS02
USER REQUESTED REMOVAL FROM A RESOURCE WAIT STATE
QUEUE
TS03
TASK RUNNING FROM SPECIFIED TERMINAL WAS ABORTED
WHEN THE TERMINAL DISCONNECTED
TS04
REMovAL OF A JOB WAS REQUESTED
C.44 UI - Undefined Instruction Trap
UI01
UNDEFINED INSTRUCTION TRAP
UI02
UNEXPECTED DEBUGX32 BREAKPOINT FOUND AND DEBUGX32
NOT ATTACHED
C.4S VF - Volume Formatter (J.VFMT)
VF01
ERROR HAS OCCURRED. SEE SLO FILE FOR EXPLANATION.
VF02
OPEN FAILURE ON AUDIT TRAIL DEVICE/FILE
VF03
EOF/EOM ON AUDIT TRAIL DEVICE/FILE
VF04
I/O ERROR ON AUDIT TRAIL DEVICE/FILE
C.46 VM - Volume Management Module (H.VOMM)
In some cases, H.VOMM displays H.REMM abort conditions. If a user calls an
H.VOMM service which in tum calls an H.REMM service for processing and an abort
condition occurs within the H.REMM processing, the abort condition is returned to
H. VOMM which displays it to the user in the format 1 Oxx where xx is the specific
H.REMM abort condition. For example, abort condition 10 2 6 indicates H.REMM
error 26 has occurred. The TSM $ERR command can be used to determine the reason
for the error, i.e., $ERR RM26.
C-28
VM01
INVALID PATHNAME
VM02
PATHNAME CONSISTS OF VOLUME ONLY
MPX-32 Abort and Crash Codes
VM - Volume Management Module (H.VOMM)
(
(
VM03
VOLUME NOT MOUNTED
VM04
DIRECTORY DOES NOT EXIST
VM05
DIRECTORY NAME IN USE
VM06
DIRECTORY CREATION NOT ALLOWED AT SPECIFIED LEVEL
VM07
RESOURCE DOES NOT EXIST
VM08
RESOURCE ALREADY EXISTS
VM09
RESOURCE DESCRIPTOR UNAVAILABLE
VMIO
DIRECTORY ENTRY UNAVAILABLE
VMll
REQUIRED FILE SPACE UNAVAILABLE
VM12
UNRECOVERABLE I/O ERROR READING DMAP
VM13
UNRECOVERABLE I/O ERROR WRITING DMAP
VM14
UNRECOVERABLE I/O ERROR READING RESOURCE DESCRIPTOR
VM15
UNRECOVERABLE I/O ERROR WRITING RESOURCE DESCRIPTOR
VM16
UNRECOVERABLE I/O ERROR READING SMAP
VM17
UNRECOVERABLE I/O ERROR WRITING SMAP
VM18
UNRECOVERABLE I/O ERROR READING DIRECTORY
VM19
UNRECOVERABLE I/O ERROR WRITING DIRECTORY
VM20
PROJECTGROUP NAME OR KEY INVALID
VM21
Reserved
VM22
INVALID FILE CONTROL BLOCK(FCB) OR LFC
VM23
PARAMETER ADDRESS SPECIFICATION ERROR
VM24
RESOURCE DESCRIPTOR NOT CURRENTLY ALLOCATED
VM25
PATHNAME BLOCK OVERFLOW
VM26
FILE SPACE NOT CURRENTLY ALLOCATED
VM27
'CHANGE DEFAULTS' NOT ALLOWED
VM28
RESOURCE CANNOT BE ACCESSED IN REQUESTED MODE OR
DEFAULT SYSTEM IMAGE FILE CANNOT BE DELETED
VM29
OPERATION NOT ALLOWED ON THIS RESOURCE TYPE
(RESOURCE IS NOT CORRECT TYPE)
VM30
REQUIRED PARAMETER WAS NOT SPECIFIED
MPX-32 Reference
C-29
VM - Volume Management Module (H.VOMM)
C-30
VM31
FILE EXTENSION DENIED. SEGMENT DEFINITION AREA FULL.
VM32
FILE EXTENSION DENIED. FILE WOULD EXCEED MAXIMUM
SIZE ALLOWED.
VM33
I/O ERROR OCCURRED WHEN RESOURCE WAS ZEROED
VM34
REPLACEMENT FILE CANNOT BE ALLOCATED
VM35
INVALID DIRECTORY ENTRY
VM36
DIRECTORY AND FILE ARE NOT ON THE SAME VOLUME
VM37
AN UNIMPLEMENTED ENTRY POINT HAS BEEN CALLED
VM38
REPLACEMENT FILE IS ALLOCATED BY ANOTHER TASK AND
BIT 0 IN THE CNP OPTION FIELD IS NOT SET, OR FILE IS
ALLOCATED BY OTHER CPU IN MULTI-PORT ENVIRONMENT
VM39
OUT OF SYSTEM SPACE
VM40
CANNOT ALLOCATE FAT/FPT WHEN CREATING A TEMPORARY
FILE
VM41
DEALLOCATE ERROR IN ZEROING FILE
VM42
RESOURCE DESCRIPTOR DESTROYED OR THE RESOURCE
DESCRIPTOR AND THE DIRECTORY ENTRY LINKAGE HAS BEEN
DESTROYED
VM43
INVALID RESOURCE SPECIFICATION
VM44
INTERNAL LOGIC ERROR FROM RESOURCE MANAGEMENT MODULE
(H.REMM). ABORT TASK, TRY A DIFFERENT TASK AND IF IT
FAILS, REBOOT SYSTEM.
VM45
ATTEMPTED TO MODIFY MORE THAN ONE RESOURCE
DESCRIPTOR AT THE SAME TIME OR ATTEMPTED TO REWRITE
A RESOURCE DESCRIPTOR PRIOR TO MODIFYING IT
VM46
RESOURCE DESCRIPTOR IS LOCKED BY ANOTHER CPU
(MULTI-PORT ONLY)
VM47
DIRECTORY CONTAINS ACTIVE ENTRIES AND CANNOT BE
DELETED
VM48
A RESOURCE DESCRIPTOR'S LINK COUNT IS ZERO
VM49
ATTEMPTING TO DELETE A PERMANENT RESOURCE WITHOUT
SPECIFYING A PATHNAME OR PATHNAME BLOCK VECTOR
VM50
RESOURCE DESCRIPTOR CONTAINS UNEXPECTED RESOURCE
DESCRIPTOR TYPE
VM51
DIRECTORY ENTRY DELETED BUT FAILED TO RELEASE FILE
SPACE
MPX·32 Abort and Crash Codes
o
VM - Volume Management Module (H.VOMM)
(
VM52
AN ATTEMPT WAS MADE TO DEALLOCATE FREE SPACE OR TO
ALLOCATE SPACE THAT IS CURRENTLY ALLOCATED ON A
VOLUME OTHER THAN SYSTEM DISC
VM53
THE FILE SPACE CREATED IS LESS THAN THE SPACE
REQUESTED
VM54-VM98
Reserved
VM99
AN ATTEMPT WAS MADE TO DEALLOCATE FREE SPACE OR TO
ALLOCATE SPACE THAT IS CURRENTLY ALLOCATED ON THE
SYSTEM VOLUME
C.47 VO - Volume Manager (VOLMGR)
VOOI
ERROR HAS OCCURRED. SEE SLO FILE FOR EXPLANATION.
V002
OPEN FAILURE ON AUDIT TRAIL DEVICE/FILE
V003
EOF/EOM ON AUDIT TRAIL DEVICE/FILE
V004
I/O ERROR ON AUDIT TRAIL DEVICE/FILE
V005
Reserved
V006
I/O ERROR ON THE TAPE DURING SAVE OPERATION. TAPE
HAS BEEN BACKSPACED TO THE END OF THE LAST SAVED
FILE. ALL FILES ON THE IMAGE PRIOR TO THE TAPE I/O
ERROR ARE SAVED ON THE TAPE.
MPX-32 Reference
C-31
Crash Codes
C.48 Crash Codes
When system crash occurs as a result of a trap handler entry, the CPU halts with the
registers containing the following information:
Register
o
1
2
3
4
S
Contents
PSD Word 0 (when trap generated)
PSD Word 1 (when trap generated)
Real address of instruction causing trap
Instruction causing trap
CPU status word (from trap handler)
Crash code:
MP01=X'4DS03031,
NMOl=X'4E4D3031,
UIOl=X'SS493031,
PV01=X'SOS6303I'
MCOI=X'4D433031,
SCOl=X'S3433031,
MF01=X'4D463031,
CPOl=X'43S03031,
SWOl=X'S3S73031,
6
7
(See H.IP02 Codes)
(Nonpresent Memory - H.IP03)
(Undefined Instruction - H.IP04)
(Privilege Violation - H.IPOS)
(Machine Check - H.IP07)
(System Check - H.IP08)
(Map Fault - H.IP09)
(Cache Parity Error - H.IPlO) 32/67, 32/87 and 32/97
(See SWAPR codes)
Real address of register save block
C'TRAP'=X'S4S241S0'
For further description, see Volume I, Chapter 2.
o
C-32
MPX-32 Abort and Crash Codes
D
(
Numerical Information
2n
n
-
2- n
1
2
4
8
0
1
2
3
1.0
0.5
0.25
0.125
16
32
64
128
4
5
6
7
0.0625
0.03125
0.015625
0.0078125
256
512
1024
2048
8
9
10
11
0.00390625
0.001 953 125
0.000 976 562 5
0.000 488 281 25
4096
8192
16384
32768
12
13
14
15
0.000244140 625
0.000 122 0703125
0.00006103515625
0.000030517578125
65536
131 072
262144
524288
16
17
18
19
0.000 015 258 789 062 5
0.000007629394531 25
0.000003814697265625
0.000001 9073486328125
1048576
2097152
4194 304
8388 608
20
21
22
23
0.00000095367431640625
0.000000476837158203125
0.000 000 238 418 579 101 562 5
0.000000 119209289 550781 25
16777216
33554432
67108864
134217728
24
25
26
27
0.000 000 059 604 644 775 390 625
0.000000029802322 387 695 312 5
0.000000014901161 19384765625
0.000 000 007450 580 596 923 828 125
268435456
536870912
1 073741824
2147483 648
28
29
30
31
0.000000003725290298461 9140625
0.000000001 862645149230957031 25
0.000000000931 322 574 615 478 515 625
0.000000000465661 2873077392578125
87D13C01
(
MPX-32 Reference
0-1
Numerical Information
2 -n
2 n
n
4294967296
8589934592
17 179869 184
34 359 738 368
32
33
34
35
0.000 000 000 232 830 643 653 869628906 25
0.000000 000 116415321826934814453125
0.000 000 000 058 207 660 913 467 407 226 562 5
0.000000000029 103830 456733703613281 25
68 719 476 736
137438953 472
274877 906 944
549755 813 888
36
37
38
39
0.000 000 000 014 551 915 228 366 851 806 640 625
0.000 000 000 007 275 957 614183 425 903 320 312 5
0.000 000 000 003 637 978 807091 712951 660 15625
0.000 000 000 001 818989403 545 856 475 830 078125
1099511627776
2 199 023 255 552
4398046511104
8796 093 022 208
40
41
42
43
0.000 000 000 000909494 701 772 9282379150390625
0.000000 000 000 454747350 886 464118 957 519 53125
0.000 000 000 000 227 373 675 443 232 059 478 759 765 625
0.000 000 000 000 113686 8377216160297393798828125
17592 186044 416
35 184 372 088 832
70368 744 177 664
140737488355 328
44
45
46
47
0.000 000 000 000 056843 418860 808 014 86968994140625
0.000000 000 000 028 421 709 430 404 007 434 844 970 703125
0.000 000 000 000 014210 854 715 202 003 717 422 485 351562 5
0.000000 000 000 007105 427357601 001 858711 242 675 781 25
281 474976710656
562949953 421 312
1 125 899 906 842 624
2251799813685248
48
49
50
51
0.000 000 000 000 003 552 713 678 800 500 929 355 621 337 890 625
0.000 000 000 000 001776356839400 250 464 677 810 668 945 312 5
0.000 000 000 000 000 888178 419 70012523233890533447265625
0.000000000000 000 444 089 209 850 062 616 169452667236328 125
4 503 599 627 370 496
9007199 254 740 992
18014398509481984
36 028797018 963 968
52
53
54
55
0.000000 000 000 000 222 044 604 925031 308 084 726 333618164 062 5
0.000 000 000 000000 111 022 302 462 515 654042 363166 809082 03125
0.000000000000000055511151231257827021181583404541015625
0.000 000 000 000 000 027 755 575 615 628 913 510 590 7917022705078125
72 057 594 037 927 936
144115188 075855872
288230376151711744
576460 752 303 423 488
56
57
58
59
0.000000 000 000 000 013877 787 807814456755 295 395 851135 253 90625
0.000 000 000 000 000 006 938 893 903 907 228 377 647697925567626953 125
0.000 000 000 000 000 003 469 446951953 614188 823 848 962 783 813 476562 5
0.000 000 000 000 000 001 734 723 475 976 807 094 411 924481 391 906738281 25
1152921504606 846 976
2 305 843009 213 693 952
4611 686 018 427 387 904
9223 372 036 854 775 808
60
61
62
63
0.000 000 000 000 000 000 867 361 737988403 547 205 962 240 695 953 369 140 625
0.000000 000 000 000 000 433680 868 994 201773602981 120 347 976 684 570 312 5
0.000 000 000 000 000 000 216840 434 497100886 801490 560 173 988 342 28515625
0.000 000 000 000 000 000108420 217 248 550 443 400 745 380 086 994171142 578125
//
0
".
87013001
o
0·2
Numerical Information
1
(,
E
Powers of Integers
E.1 Powers of Sixteen in Decimal
160
1
16
256
-
1
4
72
152
1
17
281
503
057
921
4
68
099
592
474
599
594
504
1
16
268
294
719
511
186
976
627
037
606
4
65
048
777
435
967
476
627
044
710
370
927
846
096
536
576
216
456
296
736
776
416
656
496
936
976
-
16-0
n
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
0.10000
0.62500
0.39062
0.24414
0.15258
0.95367
0.59604
0.37252
0.23283
0.14551
0.90949
0.56843
0.35527
0.22204
0.13877
0.86736
00000
00000
()()()()()
00000
00000
00000
25000
06250
53906
46191
53869
83668
72928
08080
80050
25031
78144
88403
50000
06250
78906
43164
64477
90298
06436
91522
47017
41886
13678
46049
78780
17379
00000 x 10
00000 x 10- 1
00000 x 10-2
00000 x 10-3
00000 x 10-4
00000 x 10-6
25000 x 10-7
40625 x 10-8
62891 x 10-9
51807 x 10- 10
23792 x 10- 11
14870 x 10-13
09294 x 10- 14
30808 x 10-15
56755 x 10- 16
54721 x 10- 18
("
(
MPX-32 Reference
E-1
Powers of Ten in Hexadecimal
0
E.2 Powers of Ten in Hexadecimal
IOn
3
23
163
OFO
8AC7
E·2
2
17
E8
918
5AF3
807E
86F2
4578
B6B3
2304
1
F
98
5F5
3B9A
540B
4876
D4A5
4E72
107A
A4C6
6FCI
508A
A764
89E8
I
A
64
3E8
2710
86AO
4240
9680
ElOO
CAOO
E400
E800
1000
AOOO
4000
8000
0000
0000
0000
0000
-n01
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
10·n
1.0000
0.1999
0.28F5
0.4189
0.680B
0.A7C5
0.IOC6
0.IAD7
0.2AF3
0.44B8
0.60F3
O.AFEB
0.1197
0.IC25
0.2009
0.480E
0.734A
0.B877
0.1272
0.ID83
0000
9999
C28F
374B
8BAC
AC47
F7AO
F29A
10C4
2FAO
7F67
FFOB
9981
C268
3700
BE7B
CASF
AA3
5001
C94F
0000
0000
9999
5C28
C6A7
710C
IB47
BSEO
BCAF
6118
9B5A
5EF6
CB24
20EA
4976
4257
9058
6226
36A4
D243
B6D2
999A
F5C3
EF9E
B296
8423
8037
4858
73BF
52CC
EADF
AAFF
1119
81C2
3604
5660
FOAE
B449
ABAI
AC35
x
x
X
X
X
X
X
X
X
X
x
X
x
X
X
X
X
X
16-1
16-2
16-3
16-4
16-4
16-5
16-6
16-7
16-8
16-9
16-9
16- 10
16-11
16- 12
16- 13
16- 14
16- 14
16- 15
Powers of Integers
/' " .
\
~I
(
F
ASCII Interchange Code Set
Row
Col
o
2
3
4
5
6
7
0
0
0
1
0
0
1
0
0
0
1
1
0
1
0
0
0
1
0
1
0
1
1
0
0
1
1
1
NlL
12-0-9-8-1
OLE
12-11-9-8-1
SP
No Punch
0
0
@
P
11-7
I
SOH
DCl
11-9-1
!
12-9-1
12-8-7
1
1
A
12-1
STX
12-9-2
DC2
11-9-2
8-7
2
2
B
12-2
ETX
12-9-3
DC3
11-9-3
#
8-3
3
3
C
12-3
EOT
9-7
DC4
9-8-4
$
11-8-3
4
4
ENQ
0-9-8-5
NAK
9-8-5
"10
ACK
0-9-8-6
SYN
9-2
BEL
0-9-8-7
ETB
0-9-6
Bit Positions
4
Iii;
0000
0001
0010
0011
0100
0101
0110
0111
1000
1001
1010
1011
1100
1101
1110
1111
0- ~o
1 -f-O
2 - ~O
3
0
0
1
2
3
4
5
6
7
8
9
A
B
C
0
E
F
8-4
P
12-11-7
a
a
q
11-8
12-0-1
12-11-8
R
b
r
11-9
12-0-2
12-11-9
S
0-2
c
12-0-3
s
11-0-2
0
12-4
T
0-3
d
t
12-0-4
11-0-3
5
5
E
12-5
U
0-4
9
u
12-0-5
11-0-4
6
6
F
12-6
V
0-5
f
12-0-6
v
12
7
7
G
12-7
W
9
w
8-5
0-6
12-0-7
11-0-6
(
12-8-5
8
8
H
X
h
x
12-8
0-7
12-0-8
11-0-7
Y
0-8
i
12-0-9
Y
j
12-11-1
z
k
12-11-2
{
12-0
I
12-11-3
:
m
I
.
0-8-4
&
.
BS
CAN
11-9-6
11-9-8
Hf
12-9-5
EM
11-9-8-1
)
11-8-5
9
9
I
12-9
LF
SUB
9-8-7
*
11-8-4
:
J
Z
0-9-5
8-2
11-1
0-9
VT
12-9-8-3
ESC
+
12-8-6
;
11-8-6
K
11-2
[
0-9-7
12-9-8-4
F5
11-9-8-4
0-8-3
<
12-8-4
L
11-3
CA
GS
-
12-9-8-5
11-9-8-5
=
8-6
M
11-4
1
11
SO
12-9-8-6
AS
11-9-8-6
12-8-3
>
0-8-6
N
11-5
11-8-7
51
12-9-8-7
US
11-9-8-7
I
0-1
?
0
0-8-7
11-6
FF
8-1
12-8-2
\
0-8-2
11-8-5
12-11-4
A
n
12-11-5
0
0-8-5
12-11-6
11-0-5
11-0-8
11-0-9
12-11
11-0
-
11-0-1
DEL
12-9-7
87013BOl
MPX-32 Reference
F-1
ASCII Interchange Code Set
Some positions in the ASCII code chart may have different graphic representation on various devices as:
ASCII
o
IBM 029
I
¢
I
1\
>
Control Characters:
NUL
-
SOH STX
ETX
EOT
-
ENQ
-
ACK
BEL
BS
-
HT
LF
vr
FF
CR
SO
SI
DLE
-
DCl
DC2
-
Null
Start of Heading (CC)
Start of Text (CC)
End of Text (CC)
End of Transmission (CC)
Enquiry (CC)
Acknowledge (CC)
Bell (audible or attention signal)
Backspace (FE)
Horizontal Tabulation (punch card skip) (FE)
Line Feed (FE)
Vertical Tabulation (FE)
Form Feed (FE)
Carriage Return (FE)
Shift Out
Shift In
Data Link Escape (CC)
Device Control 1
Device Control 2
DC3
DC4
NAK
-
SYN
ETB
-
CAN
-
EM
SS
ESC
FS
-
GS
AS
US
DEL
SP
(CC)
(FE)
(IS)
-
Device Control 3
Device Control 4 (stop)
Negative Acknowledge (CC)
Synchronous Idle (CC)
End of Transmission Block (CC)
Cancel
End of Medium
Start of Special Sequence
Escape
File Separator (IS)
Group Separator (IS)
Record Separator (IS)
Unit Separator (IS)
Delete
Space (normally nonprinting)
Communication Control
Format Effector
Information Separator
87D13C02
o
F·2
ASCII Interchange Code Set
(
(
G
IOP/MFP Panel Mode Commands
AS
Clear address stop
AS=xxxxxxxx
Set address stop at address xxxxxxxx
BAS
Read base registers
BASn=xxxxxxxx
Write base register n (0-7) with xxxxxxxx
C'LE
Clear memory
CRMD=xxxxx:xxxx.xx:x
=xxxx.nxxxxxx
Load CRAM with ~
Load CRAM with data and increment address
CS
Read control switches
CS=xxxxxxxx
Set control switches to xxxxxxxx
EA
Read effective address
EXEC
Execute CRAM
GPR
Read general purpose registers
GPRn=xx:x::xxxxx
Write general purpose register n (0-7) with xxxxxxxx
HALT
Halt
IPL
IPL from default address
IPL=xxxx
IPL from channeVsubaddress xux
IS
Clear instruction stop
IS=xxxxxxxx
Set instruction stop at address xxxxxxxx
MA=.:a:x:ax
Read physical memory address location xxxxxx
Increment and read memory address
MAV=.:a:x:ax
Read virtual memory address location xxxxxx
Increment and read memory address
MD=xxxxxxxx
Write memory data xxxxxxxx into last location addressed
Increment and write memory data xxxxxxxx
Increment and write previous data
MSGE
Message between primary and secondary panels (lOP only)
OVR
Toggle clock override
=xxxxxxxx
MPX-32 Reference
G-1
IOP/MFP Panel Mode Commands
PC=xxxxxx
Load program counter with address xxxxxx
PRIP
Set primary panel (master; lOP only)
PSD
Read program status doubleword (1 and 2)
PSD=.nxxxxxx
Write program status word (2) with nxxxxxx
PSW
Read program status word (1)
PSW=.nxxxxxx
Write program status word (1) with nxxxxxx
RS
Clear read operand stop
RS=nxxxxxx
Set read operand stop at address nxxxxxx
RST
Reset
RUN
Run
SECP
Set secondary panel (master and slave; lOP only)
STEP
Instruction step
Continuation of instruction step
WS
Clear write operand stop
WS=.nxxxxxx
Set write operand stop at address xxxxxxxx
@@C
Enter console mode
@@P
Enter panel mode
(LF)
Repeat command
Notes:
1.
2.
Press the return key «ret» after each command.
LOCK ON and LOCK OFF are not supported by the CRT panel.
Console Mode
To change from panel mode to console mode, enter @@C.
Upon receipt of the following the @@C command, the firmware moves the
cursor on the CRT to the extreme left margin of the next line.
To return to the panel mode, enter@@P. When the panel mode is selected, II is
the prompt.
o
G·2
IOP/MFP Panel Mode Commands
H
Standard Date and Time Formats
H.1 Description
With the advent of the new MPX-32 file system, proper maintenance of the system
date and time becomes more important than ever before as all file system resources
will be time stamped to aid in management. It is vital the date and time be kept in a
manner that is at once useful in this application and also convenient to convert into
other fonnats that the user might require.
System date and time are kept in standard binary fonnat. This fonnat consists of two
words: the first word contains the date and the second word contains the time. The
date is maintained as the number of days since January I, 1960 and the time is
maintained as the binary count of system time units since midnight, adjusted to 100
microsecond granularity.
For the convenience of the user, monitor service calls are provided to convert the date
and time between any of three standard fonnats. These are:
1.
2.
3.
Binary Fonnat (described above)
Byte Binary Fonnat
ASCII Fonnat (sometimes referred to as quad ASCII fonnat)
Byte binary format time consists of two words: the first word contains date
information and the second word contains time information. In byte binary format, the
date is kept as four distinct values instead of one. Byte 0 of the date word is the
binary century, byte 1 is the binary year in that century, byte 2 is the binary month
and byte 3 the binary day of the month. Time is kept in a similar manner with byte 0
being the hour, byte 1 the minute, byte 2 the second, and byte 3 the number of clock
ticks.
ASCII fonnat consists of four words of information. The first two words contain the
ASCII century. year, month. and day in successive halfwords. The second two words
contain the hour, minutes. seconds, and clock ticks in a similar fashion. In ASCII
format, use of a 120-hertz clock can cause truncation of the clock tick fields, allowing
for only two ASCII digits.
MPX·32 Reference
H·1
Date/Time Standard Formats
H.2 Date/Time Standard Formats
Binary
Date
Time
Days since 1/1/60
Clock ticks since midnight
Word 1
Word 2
Byte Binary
Time
Date
Bin
Cent.
Bin
Year
Bin
Month
Bin
Day
Bin
Hour
Word 1
Bin
Min.
Bin
Sec.
Bin
Ints.
Word 2
Quad ASCII
Date
Century
Year
Month
Word 1
Day
Word 2
Time
Hour
Minute
Word 3
Second
Interrupt
Word 4
, (',-,'
,
j
H·2
Standard Date and' Time Formats
(
I
Compressed Source Format
Compressed source fIles are blocked fIles that consist of 120 byte records. The last
record may be less than 120 bytes and has a data type code of 9F. The structure of a
compressed record is described below.
Each record contains 6 control bytes:
1 byte
1 byte
2 bytes
2 bytes
data type code, BF (9F indicates last record)
byte count, number of data bytes in record
checksum, halfword sum of data bytes
sequence number, record sequence number starting at zero
Data is recorded as follows:
1 byte
1 byte
n-bytes
blank count, number of blanks before data
data count, number of data bytes
actual ASCII data
. (this sequence is repeated until the end of a line is
1 byte
reached~
EOL character, FF
(
MPX·32 Reference
1-1/1-2
o
o
J
(
Map Block Address Assignments
Map Block #
DecimallHex
Page #
Decimal/Hex
Address Range
Hexadecimal
00/00
01/01
02/02
03/03
04/04
05/05
06/06
07/07
08/08
09/09
1O/0A
11/0B
I2/OC
13/0D
14/0E
I5/0F
16/10
17/11
18/12
19/13
20/14
21/15
22/16
23/17
24/18
25/19
26/1A
27/lB
28/lC
29/lD
30/lE
3l/1F
32/20
33/21
34/22
35/23
36/24
37/25
00/00
04/04
08/08
12/OC
16/10
20/14
24/18
28/1C
32/20
36/24
40/28
44/2C
48/30
52/34
56/38
6O/3C
64/40
68/44
72/48
76/4C
80/50
84/54
88/58
92/5C
96/60
100/64
104/68
108/6C
ll2nO
l16n4
l20n8
00000 - 01FFF
02000 - 03FFF
04000 - 05FFF
06000 - 07FFF
08000 - O9FFF
OAOOO - OBFFF
OCOOO - ODFFF
OEOOO - OFFFF
10000 - lIFFF
12000 - 13FFF
14000 - 15FFF
16000 - 17FFF
18000 - 19FFF
lAooo - lBFFF
lCooo - IDFFF
lEOOO - IFFFF
20000 - 2IFFF
22000 - 23FFF
24000 - 25FFF
26000 - 27FFF
28000 - 29FFF
2AOOO - 2BFFF
2COOO - 2DFFF
2EOoo - 2FFFF
30000 - 31FFF
32000 - 33FFF
34000 - 35FFF
36000 - 37FFF
38000 - 39FFF
3AOoo - 3BFFF
3COOO - 3DFFF
3FOOO - 3FFFF
40000 - 41FFF
42000 - 43FFF
44000 - 45FFF
46000 - 47FFF
48000 - 49FFF
4AOOO - 4BFFF
124nC
128/80
132/84
136/88
140/8C
144/90
148/94
("
MPX-32 Reference
J-1
Map Block Address Assignments
Map Block #
DecimaVHex
Page #
DecimaVHex
Address Range
Hexadecimal
38/26
39/27
40/28
41/29
42/2A
43/2B
44/2C
45/2D
46/2E
47/2F
48/30
49/31
50/32
51/33
52/34
53/35
54/36
55/37
56/38
57/39
58/3A
59/3B
6O/3C
61/3D
62/3E
63/3F
152/98
156/9C
160/AO
164/A4
168/A8
172/AC
176/B0
180/B4
184/B8
188/BC
192/C0
196/C4
200/C8
204/CC
208/00
212/04
216/08
220/OC
224/E0
228/E4
232/E8
236/EC
240/F0
244/F4
248/F8
252/FC
4COOO - 4DFFF
4EOoo - 4FFFF
50000 - 51FFF
52000 - 53FFF
54000 - 55FFF
56000 - 57FFF
58000 - 59FFF
5AOOO - 5BFFF
5COOO - 5DFFF
5Eooo - 5FFFF
60000 - 61FFF
62000 - 63FFF
64000 - 65FFF
66000 - 67FFF
68000 - 69FFF
6AOOO - 6BFFF
6C000 - 6DFFF
6EooO - 6FFFF
70000 - 71FFF
72000 - 73FFF
74000 - 75FFF
76000 - 77FFF
78000 - 79FFF
7AOoo - 7BFFF
7COOO - 7DFFF
7Eooo - 7FFFF
Extended Memory 128KW to 256KW - 1B
64/40
256/100
80000 - FFFFF
Extended Memory 256KW to 384KW - 1B
128/80
512/200
100000 - 17FFFF
Extended Memory 384KW to 512KW - IB
192/CO
768/300
180000 - IFFFFF
Extended Memory 512KW to 1024KW - IB
256/100
1024/400
200000 - 3FFFFF
Extended Memory 1024KW to 2048KW - 1B
512/200
2048/800
400000 - 7FFFFF
Extended Memory 2048KW to 4096KW - 1B
1024/400
4096/1000
800000 - FFFFFF
C
"'-•...~/
r~
'-.J"
J-2
Map Block Address Assignments
K
Control Switches
While rebooting the system, various initialization processes can be inhibited or
enabled by setting the appropriate control switches. The switch assignments are:
Switch
Function if Set
o
Inhibits volume clean-up by J.MOUNT.
SYSINIT enters the system debugger before processing patches.
Inhibits patch processing (see Reference Manual, Volume III,
Chapter 9, Entry Conditions).
Inhibits terminal initialization.
Inhibits accounting functions including the M.KEY, M.PRJCT,
M.ACCNT, and M.ERR files.
Inhibits processing of the sequential task activation table at IPL time.
If J .MOU NT encounters an invalid resource descriptor due to
an invalid resource descriptor type field or space definition,
it branches and links to the system debugger (if present) with
R2 pointing to the resource descriptor.
J.MOUNT prereads the file space bit map (SMAP) or the resource
descriptor allocation bit map (DMAP). J.MOUNT will not perform file
overlap protection.
Delete spooled output files instead of resubmitting them for processing.
Inhibits activating LOADACS during IPL or RESTART operations.
Enables faster memory initialization by checking only one location
per map block to determine if that map block is present. It is not
recommended that this switch be set on the first IPL after power up.
Inhibits initialization of the memory descriptor table (MDT).
For RMSS: inhibits booting of nodes while J.BOOT executes.
1
2
3
4
5
6
7
(
8
9
10
11
12
The control switches can be accessed by the console. The proper time to set the
switches is while the system is waiting for the date and time to be entered. To set, for
example, switch 3, the following must be entered on the IOPjMFP console:
ENTER DATE AND TIME: @@P
/ /CS=10000000
Tenninal Initialization Inhibited
//@@c
INVALID DATE FORMAT=MM/DD/XX
ENTER DATE AND TIME:
Refer to the CONCEPT 32/2000 Operations manual for instructions for setting control
switches on the Amiga console.
During power up, control switches are prezeroed if the proper firmware revision level
has been installed. Power up without prezeroing can cause unexpected system
responses due to incorrect control settings.
All control switch settings are preserved during system reboots not involving system
power up (i.e., online restart and IPL).
MPX-32 Reference
K-1/K-2
o
(
L
Data Structures
L.1 Introduction
This appendix contains some of the more frequently used data structures. Below is a
list of those structures.
(
Caller Notification Packet (CNP)
Controller Definition Table (COT)
Dispatch Queue Entry (DQE)
File Control Block (FCB), 16 Word
File Control Block (FCB), 8 Word
File Control Block (FCB), High Speed Data
File Pointer Table (FPT)
Parameter Task Activation Block (PTASK)
TSM Procedure Call Block (PCB)
Pathname Blocks (PNB)
Post Program-Controlled Interrupt Notification Packet (PPCI)
Parameter Receive Block (PRB)
Parameter Send Block (PSB)
Resource Create Block (RCB)
Resource Identifiers (RID)
Resource Logging Block (RLB)
Resource Requirement Summary (RRS) Entries
Receiver Exit Block (RXB)
Type Control Parameter Block (TCPB)
Unit Definition Table (UDT)
(
MPX-32 Reference
L-1
Caller Notification Packet (CNP)
((-~,
L.2 Caller Notification Packet (CNP)
\,-/,
The caller notification packet (CNP) is the mechanism used by the Resource
Management Module (H.REMM) and the Volume Management Module (H. VOMM)
for handling abnonnal conditions that may result during resource requests. All or part
of this structure can be used by a particular service being called. The CNP must be
on a word boundary.
o
Word 0
1
2
3-4
5
7
8
15
16
23
24
31
Time-out value (CP.TIMO)
r---------~----~------------------------------~
Abnormal return address (CP.ABRET)
Option field (CP.OPTS). See Note 1.
I Status field (CP.STA1). See Note 2.
Reserved (See Note 3.)
Automatic open FCB address (CP.FCBA)
Notes:
1.
2.
3.
A bit sequence and/or value used to provide additional information that can be
necessary to fully define the calling sequence for a particular service.
A right-justified numeric value identifying the return status for this call.
Refer to the individual system service description in the MPX-32 Reference
Manual Volume I for interpretation of these words.
c
L·2
Data Structures
Controller Definition Table (COT)
(
L.3 Controller Definition Table (COT)
The controller definition table (eDT) is a system resident structure used to identify
information required by handlers and the I/O processor for a specific controller. The
eDT is built by the SYSGEN process, one for each controller configured on the
system. The eDT identifies devices (UDTs) associated with the controller, the
handler address associated with the controller, and defines other pertinent controller
information.
o
Word 0
7
8
15
16
23
24
31
String forward address (CDT.FIOQ)
1
String backward address (CDT.BIOQ)
2
Link priority
(CDT.LPRI).
See Note 1.
3
Class (CDT.CLAS).
See Note 3.
Flags (CDT.FLG2).
See Note 4.
CDT index (CDT.INDX)
Device type code
(CDT.DTC)
See Note 5.
Interrupt priority
level
(CDT.IPL)
4
Number units
on controller
(CDT.NUOC)
Number requests
outstanding
(CDT.IORO)
Channel number
(CDT.CHAN)
Subaddress of
first device
(CDT.SUBA)
5
Program number
if reserved
(CDT.PNRC)
Interrupt handler address (CDT.SlHA) or controller
information block (CDT.CIF)
6
Flags
(CDT.FLGS).
See Note 6.
UDT address of first device on controller
(CDT.UDTA)
7
I/O status
(CDT.IOSn.
See Note 7.
TI address (CDT.TIAD)
or
SI address if extended I/O (CDT.SIAD)
8
9-23
Number of
entries in list
(CDT.IOCT).
See Note 2.
UDT address unit 0* (CDT.UTO)
UDT address unit 1* (CDT.UTI) through
UDT address unit 15* (CDT.U1F)
*Initialized by SYSGEN
Notes:
1.
2.
Always zero (head cell)
Number of entries in list (zero if none)
MPX-32 Reference
L-3
Controller Definition Table (COT)
,
3.
Values in CDT.CLAS are assigned as follows:
Value
X'OD'
X'OE'
X'OF'
4.
Meaning
TCW type with extended addressing capability
TCW type
extended I/O
Bits in CDT.FLG2 are assigned as follows:
Bit
o
1-7
Meaning if Set
SCSI device (CDT.SCSI)
reselVed for future use
5.
For example, 01 for any disk, 04 for any tape, etc. Valid device type codes are
listed in Appendix A.
6.
Bits in q:n.FLGS are assigned as follows:
--IDL
o
1
2
3
4
5
6
7
7.
Meaning if Set
extended I/O device (CDT.FCLS)
I/O outstanding (set by handler, reset by IOCS)
(CDT.IOU1)
GPMC device (CDT.GPMC)
initialization (INC) needs to be performed for this
controller (CDT.FINT)
D-class (CDT.xGPM)
used only when IOQs are linked to the CDT. Set when
SIO is accepted by the controller. Reset when IOQ is
unlinked from the CDT or when I/O is reported complete
to IOCS in the case of operator intervention type errors
(CDT.IOU5).
lOP controller (CDT.IOP)
controller malfunction (CDT.MALF)
Bits in CDT.IOST are assigned as follows:
--IDL
o
1
2
3
4
5
6
7
Meaning if Set
IOQ linked to UDT (CDT.NIOQ)
multiplexing controller (CDT.MUXC)
use standard XIO interface
16MB GPMC (CDT.xGPS)
cache controller (CDT.CAC)
H.F8XIO has determined if the controller is
pre-8512-2 or not (CDT.CKFL)
controller not pre-8512-2 (CDT.FLOW)
reselVed for FMS
(
'"
i)
L·4
,
"'--/
Data Structures
Dispatch Queue Entry (DQE)
L.4 Dispatch Queue Entry (DQE)
The dispatch queue entry (DQE) contains all of the core-resident infonnation required
to describe an active task to the system. It is always linked to the CPU scheduler
state chain that describes the current execution status of the associated task.
Word No.
(Decimal)
0
1
2
3
4-5
6-7
8-9
10
11
(--
(~
Byte
(Hex)
-- o
0
4
8
C
10
18
20
28
2C
30
34
38
3C
40
15 16
23 24
31
DQE.SF
DQE.SB
DQE.CUP
DQE.BUP
DQE.IOP
DQE.US
DQE.NUM/DQE.TAN
DQE.ON
DQE.LMN
DQE.PSN
DQE.USW
DQE.USHF
12
13
14
IS
16
17
18
19
20
21
22
23
44
DQE.SH
48
4C
50
54
58
5C
DQE.UTSI
Reserved
24
60
DQE.PSSF
25
26
27
28
29
30
31
32
33
34
64
DQE.PSSB
68
DQE.PSPR
6C
DQE.nSF
70
74
78
7C
80
DQE.TISB
DQE.RRPR
84
DQE.MRSF
88
DQE.MRSB
MPX-32 Reference
7 8
DQE.MSD
DQE.KCTR
DQE.MMSG
DQE.MRUN
DQE.MNWI
DQE.GQFN
DQE.UF2
DQE.IPUF
DQE.NWIO
DQE.SOPO
DQE.SHF
DQE.TIFC
DQE.RILT
DQE.TSKF
DQE.MSPN
DQE.MST
DQE.PSCT
DQE.ll..N
DQE.RESU
DQE.TICT
DQE.SWIF
DQE.UBIO
DQE.RRCT
DQE.NSCT
DQE.CQC
DQE.UTS2
DQE.DSW
DQE.PRS
DQE.PRM
DQE.TIPR
DQE.RRSF
DQE.RRSB
L-5
Dispatch Queue Entry (DQE)
,{-"\
Word No.
(Decimal)
L·6
U
Byte
(Hex)
o
7
8
15
16
23
24
31
35
8C
DQE.MRPR
DQE.MRCT
DQE.NWRR
DQE.NWMR
36
90
DQE.RTI
DQE.NWLM
DQE.ATI
Reserved
37
94
DQE.SAlR/DQE.TAD
38-40
98
DQE.ABC
41
A4
DQE.TSAP
42-43
A8
DQE.SRID/DQE.PGOL
AC
DQE.SRID/DQE.PGOC
44-51
BO
DQE.CDIR/DQE.CVOL
52
DO
DQE.GID
53
D4
DQE.ACX2
54
D8
55
DQE.SRID/Reserved
Reserved
DQE.ASH
DQE.MRQ
DQE.MEM
DQE.MEMR
DC
DQE.MRT
Reserved
DQE.RMMR
56
EO
DQE.MAPN
DQE.CME
57
E4
DQE.CMH
DQE.CMS
58-63
FC
Reserved
Byte
(Hex)
Symbol
Description
o
DQE.SF
String forward linkage address;
Field length = IW;
Standard linked list format;
Contains address of next (top-to-bottom) entry in chain.
4
DQE.SB
String backward linkage address;
Field length =IW;
Standard linked list format;
Contains address of next (bottom-to-top) entry in chain.
8
DQE.CUP
Current user priority;
Standard linked list format;
This priority is adjusted for priority migration based on
situational priority increments. Situational priority
increments are based on the base level priority
(DQE.BUP) of the task.
DQE.BUP
Base priority of user task;
Field length = IB;
Used by scheduler to generate DQE.CUP (current priority)
based on any situational priority increments.
DQE.IOP
I/O priority;
Field length = IB;
Initially set from base priority;
Used for I/O queue priority.
o
Data Structures
Dispatch Queue Entry (DQE)
(-
Byte
(Hex)
S~mbol
DQE.US
(-
MPX·32 Reference
DescriQtion
State chain index for this user task;
Field length = IB;
Range: zero through X'lE';
Indicates current state of this task, such as ready-to-run
priority, I/O wait, resource block, etc.
Label
Index
Task descriQtion
FREE
PREA
CURR
00
01
02
SQRT
SQ55
SQ56
SQ57
SQ58
SQ59
SQ60
SQ61
SQ62
SQ63
SQ64
SWTI
SWIO
SWSM
SWSR
SWLO
SUSP
03
04
05
06
07
08
09
OA
OB
DQE is available (in free list)
activation in progress
currently executing task or is pre-empted
time-distribution task in quantum stage one
ready to run (priority level 1 to 54)
ready to run (priority level 55)
ready to run (priority level 56)
ready to run (priority level 57)
ready to run (priority level 58)
ready to run (priority level 59)
ready to run (priority level 60)
ready to run (priority level 61)
ready to run (priority level 62)
ready to run (priority level 63)
ready to run (priority level 64)
waiting for terminal input
waiting for I/O
waiting for message complete
waiting for run request complete
waiting for low speed output
waiting for timer expiration, resume
request, or message interrupt
waiting for timer expiration, or run request
waiting for a continue request
waiting for timer expiration, no-wait I/O
complete, no-wait message complete, no-wait
run request complete, message interrupt,
or break interrupt
waiting for disk space
waiting for device allocation
waiting for file system
waiting for memory
waiting for memory pool
waiting in general wait queue
current IPU task in execution
IPU requesting state
OC
OD
OE
OF
10
11
12
13
RUNW
HOLD
ANYW
14
15
16
SWDC
SWDV
SWFI
MRQ
SWMP
SWGQ
CIPU
RIPU
17
18
19
1A
IB
1C
ID
IE
L·7
Dispatch Queue Entry (DQE)
1'"
0
:
Byte
(Hex)
C
S~bol
Description
OQE.NUM
OQE entry number;
Field length = IB;
Used as an index to OQE address table (OAT);
Range: one through "N"(for MPL index compatibility);
Used by scheduler to set C.PRNO to reflect
the currently executing task. This value is also
used as the MPL index. It is used by the scheduler
to initialize the CPIX in the PSO before loading the
map for this task.
OQE.TAN
Task activation sequence number;
Field length = 1W;
This number is assigned by the activation service
and uniquely identifies a task.
Note: The most significant byte of this value
is the OQE entry number and is accessible as
OQE.NUM.
10
OQE.ON
Owner name;
Field length = 10.
18
OQE.LMN
Load module name;
Field length = 10.
20
OQE.PSN
Pseudonym associated with task;
Field length = 10;
This parameter is an optional argument accepted by the
pseudo task activation service. It can be used to
uniquely identify a task within a subsystem, such as
multibatch. It contains descriptive infonnation useful
to the system operator or to other tasks within a
subsystem. Conventions used to generate a pseudonym
are detennined by the associated subsystem.
A system-wide convention should be used to establish
pseudonym prefix conventions to avoid confusion
between subsystems.
28
OQE.USW
User status word;
Field length = 1W.
2C
OQE.USHF
Scheduling flags;
Field length = 1W;
Used by the scheduler to indicate special status
conditions.
""
.,,-_./
o
L·8
Data Structures
Dispatch Queue Entry (DQE)
(
Byte
(Hex)
Symbol
Description
Bit
00
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
(
19
20
21
22
23
24
25
26
27
28
29
30
31
(
MPX·32 Reference
Meaning When Set
load protection image requested (DQE.LPI)
single copy load module (DQE.SING)
task is indirectly connected (DQE.INDC)
task is privileged (DQE.PRIV)
task has message receiver (DQE.MSGR)
task has break receiver (DQE.BRKR)
task quantum stage one expired (DQE.QSIX)
task quantum stage two expired (DQE.QS2X)
in-swap I/O error (DQE.INER)
wait I/O request outstanding (DQE.WIOA)
wait I/O complete before in-progress notification
(DQE.WIOC)
inhibit message pseudointerrupt (DQE.lNMI)
batch origin task (DQE.BAOR)
running in TSM environment (DQE.TMOR)
task abort in progress (DQE.ABRT)
task is in pre-exit state (DQE.PRXT)
run receiver mode (DQE.RRMD)
wait send message outstanding (DQE.WMSA)
wait message complete before link to wait
queue (DQE. WMSC)
wait mode send run request outstanding
(DQE.WRRA)
wait mode send run request complete before
link to wait queue (DQE.WRRC)
debug associated with task (DQE.DBAT)
real-time task (DQE.RT)
time-distribution task initial dispatch (DQE.TDID)
Set by:
• H.ALOCI on activation of TID task.
• S.EXEC51 when task is linked to wait state.
• H.EXEC7 on completion of inswap or other
memory request.
Reset by:
• S.EXEC20 on initial dispatch of task after
activation
• Wait state termination
• In-swap
task delete in progress (DQE.DELP)
task abort (with abort receiver) in progress
(DQE.ABRA)
abort receiver established (DQE.ABRC)
asynchronous abort/delete inhibited
(DQE.ADIN)
asynchronous delete deferred (DQE.ADDF)
task is inactive (DQE.INAC)
asynchronous abort deferred (DQE.AADF)
activation timer in effect (DQE.ACTT)
L·9
Dispatch Queue Entry (DQE)
Byte
(Hex}
S~bol
Description
30
DQE.MSD
Physical address of MIDL in TSA;
'
Field length = lW.
34
DQE.KCfR
KiWabort timer;
Field length = 1W.
38
DQE.MMSG
Maximum number of no wait messages
allowed to be sent by this task;
Field length = lB.
DQE.MRUN
Maximum number of no-wait run requests allowed
to be sent by this task;
Field length = IB.
DQE.MNWI
Maximum number of no-wait I/O requests allowed
to be concurrently outstanding for this task;
Field length = lB.
DQE.GQFN
Contains the generalized queue (SWGQ)
function code;
Field length = IB;
Function codes are queued as follows:
Code
Meaning
01
02
volume resource (QVRES)
ART space (QART)
mount in progress (QMNT)
resourcemark lock (QRSM)
reserved for eventmark (QEVM)
read wait for writer (QGEN)
shared memory table (QSMf)
synchronous resource lock (QSRL)
mounted volume table (QMVT)
dual-port lock (QDPLK)
suspend dual-port lock (QSUSP)
debug wait (QDBGW)
remote message area (QMSG)
remote message event (QSER)
remote allocate area (QASMP)
remote deallocate area (QDSMP)
remote abort area (QAMSG)
remote enable/disable area (QOMSG)
wait for TSM (QWTSM)
03
04
05
06
07
08
09
OA
OB
OC
OD
OE
OF
10
11
12
13
c
L-10
Data Structures
Dispatch Queue Entry (DQE)
(-
Byte
(Hex)
S~bol
Description
3C
DQE.UF2
Scheduling flags;
Field length = IB;
Bit
Meaning if Set
0
enable debug mode break. (DQE.EDB)
generalized wait queue time-out (DQE.GQTO)
task interrupts are synchronized (DQE.SYNC)
task is part of a job (DQEJOB)
ACX-32 task flag (DQE.ACX)
special arithmetic function requested (DQE.AF)
reserved
run request terminated (DQE.RRT)
1
2
3
4
5
6
7
DQE.IPUF
IPU flag byte;
Field length = IB;
Bit
0
1
2
3
(
4
5
6
7
Meaning if Set
IPU inhibit flag (DQE.IPUH)
IPU bias flag (DQE.IPUB)
CPU only (DQE.IPUR)
OS execution direction flag (set when PSD
is in user area) (DQE.OSD)
base register task (DQE.BASE)
Ada task (DQE.ADA)
PTRACE debugger task (DQE.PDBG)
H.PTRAC task association control bit
(DQE.PTRA)
DQE.NWIO
Number of no-wait I/O requests;
Field length = lB.
DQE.SOPO
Priority bias only swapping control flags;
Field length = lB;
Bit
0
1
2
3
4
5-7
Meaning if Set
SWGQ state priority-based swapping
(DQE.GQPO)
swap inhibit due to bit map access
(DQE.BMAP)
inhibit swap device while accessing MDT
(DQE.MDTA)
user swap inhibit flag (DQE.USWI)
user swap on priority only flag (DQE.USPO)
reserved
(-MPX·32 Reference
L·11
Dispatch Queue Entry (DQE)
~.--'\
'1:
Byte
(Hex)
Symbol
Description
40
DQE.CQC
Current quantum count;
Field length = 1W;
Used by the scheduler to accumulate elapsed execution
time for the task to compare the level unique
stage one and stage two time-distribution values.
44
DQE.SH
Used by 1.SWAPR to swap shadow memory;
Field length = lB.
DQE.SHF
Shadow memory flag;
Field length = 1B;
.,-~
DQE.TIFC
Bit
Meaning if Set
0
1
2
task requests shadow memory (DQE.SHAD)
IPU shadow memory requested (DQE.SHI)
IPU/CPU Common Shadow Memory
requested (DQE.SHB).
Timer function code;
Field length = 1B;
Value
Meaning
00
not active
request intenupt
resume program from
queue
resume program from
queue
resume program from
(RUNW) queue
resume program from
(SWGQ) queue
resume program from
(SWDV) queue
resume program from
queue
01
02
03
04
05
06
07
48
/,<""
\ ...., -~ .,'
suspend (SUSP)
any-wait (ANYW)
run-request-wait
generalized
peripheral device
disk space (SWDC)
DQE.RILT
Request Intenupt (RI) level for timer;
Field length = 1B;
Identifies the intenupt level to be requested upon
timer expiration.
DQE.UTSI
User timer slot word 1;
Field length = lW;
Current timer value;
Contains negative number of timer units before
time out.
0
L·12
Data Structures
Dispatch Queue Entry (DQE)
,4
Byte
(Hex)
~j
S,Ymbol
DescriQtion
DQE.MSPN
TSA maps required to span MIDLs and MEMLs;
Field length = lB.
DQE.MST
Static memory type specification;
Field length = IB;
Value
01
02
03
04
05
06
Memory Qass
E
H
S
HI
H2
H3
This field is used to specify the type
of memory required for in-swap.
L-14
60
DQE.PSSF
Pre-emptive system service head cell string
forward linkage address;
Standard head cell fonnat;
Field length = IW;
Contains address of next (top-to-bottom) entry in chain.
64
DQE.PSSB
Pre-emptive system service head cell string
backward linkage address;
Standard head cell fonnat;
Field length = IW;
Contains address of next (bottom-to-top) entry in chain.
68
DQE.PSPR
Pre-emptive system service head cell dummy
priority (always zero);
Standard head cell fonnat;
Field length = lB.
DQE.PSCT
Pre-emptive system service head cell number of
entries in list;
Standard head cell fonnat;
Field length = lB.
DQE.ILN
Interrupt level number;
Field length = IB;
Identifies associated interrupt level for interrupt
connected tasks.
DQE.RESU
Reserved usage index;
Field length = lB.
Data Structures
,f""""
"'-,
Dispatch Queue Entry (DQE)
(
Byte
(Hex)
Symbol
Description
6C
DQE.TISF
Task interrupt head cell string forward linkage address;
Standard head cell format;
Field length = 1W;
Contains address of next (top-to-bottom) entry in chain.
70
DQE.TISB
Task interrupt head cell string backward linkage address;
Standard head cell format;
Field length = lW;
Contains address of next (bottom-to-top) entry in chain.
74
DQE.TIPR
Task interrupt head cell dummy priority (always zero);
Standard head cell format;
Field length = lB.
DQE.TICf
Task interrupt head cell number of entries in list;
Standard head cell format;
Field length = lB.
DQE.SWIF
Swapping inhibit flags;
Field length = IB;
(
Bit
Task Meaning if Set
0
1
2
resident (DQE.RESP)
locked in memory (DQE.LKIM)
unbuffered I/O in progress (DQE.IO)
outswapped (DQE.OTSW)
leaving system (DQE.TLVS)
forced unswappable during terminal output
(DQE.FCUS)
forced unswappable because swap file has
not been allocated for it (DQE.FCRS)
imbedded in the operating system
(DQE.INOS)
3
4
5
6
7
DQE.UBIO
Number of unbuffered I/O requests currently outstanding;
Field length = lB.
78
DQE.RRSF
Run receiver head cell string forward linkage address;
Standard head cell format;
Field length = IW;
Contains address of next (top-to-bottom) entry in chain.
7C
DQE.RRSB
Run receiver head cell string backward linkage address;
Standard head cell format;
Field length = lW;
Contains address of next (bottom-to-top) entry in chain.
80
DQE.RRPR
Run receiver head cell dummy priority (always zero);
Standard head cell format;
Field length = lB.
("
MPX-32 Reference
L-15
Dispatch Queue Entry (DQE)
f""~,
"~
Byte
(Hex)
,,~./
Symbol
Description
DQE.RRCf
Run receiver head cell number of entries in list;
Standard head cell fonnat;
Field length = lB.
DQE.NSCf
Number of map blocks outswapped;
Field length = IH.
84
DQE.MRSF
Message receiver head cell string forward
Linkage address;
Standard head cell fonnat;
Field length = IW;
Contains address of next (top-to-bottom) entry in chain.
88
DQE.MRSB
Message receiver head cell string backward
Linkage address;
Standard head cell fonnat;
Field length = I W;
Contains address of next (bottom-to-top) entry in chain.
8C
DQE.MRPR
Message receiver head cell dummy priority (always zero);
Standard head cell fonnat;
Field length = lB.
DQEMRCf
Message receiver head cell number of entries in list;
Standard head cell fonnat;
Field length = lB.
90
DQE.NWRR
Number of no-wait mode run requests outstanding;
Field length = lB.
DQE.NWMR
Number of no-wait mode message requests outstanding;
Field length = lB.
DQE.RTI
Requested task interrupt flags;
Field length = IB;
Bit
o
1
2
3
4
5
6-7
L-16
Meaning if Set
reserved
priority one end action request. Used for
pre-emptive system services. (DQE.EAIR)
debug break request (DQE.DBBR)
user break request (DQE.UBKR)
priority two end action request (DQE.EA2R)
message interrupt request (DQE.MSlR)
reserved
Data Structures
/'
"\
"',",,""",/
Dispatch Queue Entry (OQE)
(
Byte
(Hex)
Symbol
Description
DQE.NWLM
No-wait run request limit.
Field length = 1B.
DQE.ATI
Active task interrupt flags;
Field length = 1B;
Bit
0
1
2
3
4
5
6-7
94
Meaning if Set
reserved
priority one active end action (DQE.AEAl)
active debug break (DQE.ADM)
active user break (DQE.AUB)
priority two active end action (DQE.AEA)
active message interrupt (DQE.AMI)
reserved
= lB.
Reserved
Field length
DQE.SAIR
System action task interrupt request;
Bit
0
1
2
(
3
4
5
6
7
Meaning if Set
request for delete of this task (DQE.DELR)
reserved
hold task request (DQE.HLDR)
abort task request (DQE.ABTR)
exit task request (DQE.EXTR)
suspend task request (DQE.SUSR)
run receiver mode request (DQE.RRRQ)
reserved
DQE.TAD
TSA address (logical);
Field length = 1W;
Byte zero contains DQE.SAIR.
98
DQE.ABC
Abort code;
Field length = 3W.
A4
DQE.TSAP
Physical address of the TSA
A8-AC
DQE.SRID
If DQE.DPG is reset;
DQE.PGOL
DQE.PGOC
Reserved
(
MPX-32 Reference
Used swap space linked list;
Field length = 2W.
If DQE.DPG is set;
Forward pointer to MPTL (MAP.SF);
Field length = 1HW
Backward pointer to MPTL (MAP.SB)
Field length = IHW
Number of pages queued for pageout
Field length = IHW
Field length = IHW
L-17
Dispatch Queue Entry (DQE)
Byte
(Hex)
Symbol
Description
BO
DQE.CDIR
Load module RID at activation;
Field length = 8W.
DQE.CVOL
Current working volume at activation;
Field length = 8W.
DO
DQE.GID
Group swap identification;
Field length = lB.
Dl
Reserved
1 Byte
D2
DQE.ASH
Number of shadow memory blocks currently allocated
Field length = 1H.
D4
DQE.ACX2
Advance communication word;
Field length = 1W.
D8
DQE.MRQ
Memory request double word;
Reserved field length = lB.
DQE.MEM
Type of memory requested;
Field length = 1B;
Value
DC
Memory Gass
01
02
E
H
03
S
DQE.MEMR
Number of memory blocks required;
Field length = 1H.
DQE.MRT
Memory request type code;
Field length = lB;
Value
00
01
02
03
04
05
06
07
Meaning
in-swap only
preactivation request
activation request
memory expansion request
IOCS buffer request
shared memory request
system buffer request
release swap file space
If DQE.MRT equals 05, the next three bytes will
contain the address of the shared memory table entry.
L-18
= lB.
Reserved
Field length
DQE.RMMR
Map register for requested memory;
Field length = 1H.
Data Structures
Dispatch Queue Entry (DQE)
(
Byte
(Hex)
Symbol
Description
EO
DQE.MAPN
Inclusive span of maps in use;
Field length = 1H.
DQE.CME
Number of swappable class E map blocks
currentl y allocated;
For resident tasks, if not zero, reflects the
total number of map blocks in use.
Field length = IH.
DQE.CMH
Number of swappable class H map
blocks currently allocated;
For resident tasks, if not zero, reflects the
total number of map blocks in use.
Field length = IH.
DQE.CMS
Number of swappable class S map blocks
currently allocated;
For resident tasks, if not zero, reflects the
total number of map blocks in use.
Field length = lH.
Reserved
Reserved for MPX-32
E4
E8
(
MPX-32 Reference
L-19
File Control Block (FCB), 16 Word
(f-\,
L.S File Control Block (FCB), 16 Word
12 13
7 8
Wcrd 0
'-./
31
Logical file code (FCBLFC)
1
2
5
6
7
8
9
10
11
12
13
No-wait I/O nonnal end-action service address (FCB.NWOK)
14
No-wait I/O error end-action service address (FCB.NWER)
15
Number of
buffers
(FCB.BBN)
Address of blocking buffer (FCB.BBA)
Shaded areas are set by the system.
TlFCB
Word 0
Bit 0
Bits 1-7
Bits 8-31
Reserved
Operation code (FCB.OPCD) - type of function requested of the device
handler. This field is set by IOCS as a function of the executed service.
Logical file code (FCB.LFC) - any combination of three ASCII
characters is allowed. The LFC must match the previously assigned LFC
of the I/O resource being accessed.
Word 1
Bits 0-31
Reserved
Word 2
Bits 0-7
L·20
General control flags (FCB.GCFG) - these eight bits enable the user to
specify the manner in which an operation is to be performed by IOCS.
The interpretation of these bits is shown as follows:
Data Structures
C',
File Control Block (FeB), 16 Word
(~
Bit
0
(
1
NER
2
DFI
3
NST
4
RAN
5
6
7
EXP
IEC
Bits 8-12
Bits 13-31
Bit
13
(
MPX-32 Reference
Meaning
if Set
NWT
Definition
10CS returns to the user immediately after the
I/O operation is queued. If reset, 10CS exits to the
calling program only when the requested operation
has been completed.
error processing is not perfonned by either the device
handler or 10CS. An error return address is ignored
and a normal return is taken to the caller; however,
the device status is posted in the FCB unless bit
3 is set. If reset, normal error recovery is
attempted. Nonnal error processing for disk and
magnetic tape is automatic error retry. Error
processing for unit record devices except the
system console is accomplished by 10CS typing
the message INOP to the console, which allows
the operator to retry or abort the I/O operation.
If the operator aborts the I/O operation, or if
automatic error retry for disk or magnetic tape is
unsuccessful, an error status message is typed
to the console and the error return address is
taken if provided. Otherwise, the task is aborted.
data formatting is inhibited. Otherwise, data
formatting is performed by the appropriate device
handler. See Table L-l for more explanation.
device handlers perform no status checking and no
status information is returned. An I/O appears
to complete without error. Otherwise, status
checking is perfonned and status information
is returned as necessary.
file accessing occurs in the random mode.
Otherwise, sequential accessing is perfonned.
Note: This bit is set if word 2 bit 12 is set.
reserved (M.FILE)
must be 1 for 16-word FCB.
this bit is reserved for internal 10CS use.
Special Control Specification (FCB.SCFG). - This field
contains device control specifications unique to certain devices.
Interpretation and processing of these specifications are performed
by the device handlers. A bit setting is meaningful only when a
particular type of device is assigned as indicated in Table L-l.
reserved for extended control specifications
Meaning
if Set
RXON
Definition
software read flow control required
for 8-Line ACM (FCB.RXON)
L-21
File Control Block (FeB), 16 Word
Table L-1
Special Control Flags
Device
Line
Printer
(LP)
Discs,
(DM,DF,
FL)
8-Line
Asynchronous
Communications
Multiplexer
(TY)
Device
Line Printer (LP)
Bit 2:::0
Bit 2=1
Interpret first
character as
carriage
control
Report EOF if
X'OFEOFEOF'
encountered
in word 0 of
1st block
during read
of unblocked
file
M.READ
Interpret first
character as
data
See bit 8
X 'OFEOFEOF ,
in word 0
not
recognized
as EOF
Form
control
No form
control
M.READ
M.READ
M.READ
M.READ
M.READ
No special
character
formatting
ASCII control
passed as
data
ASCII control
character
detect
Echo by
controller
No echo by
controller
M.WRIT
Interpret first
character as
data
SVC I,X'3E'
Stop
transmitting
break
SVC I,X'3E'
Start
transmitting
break
M.WRIT
Normal
write
M.WRIT
Initialize
device (load
UART
parameters)
Perform
special
character
formatting
M.WRIT
Interpret first
character as
carriage
control
Bit 10=0
Reserved
Bit 10=1
Reserved
Bit 8=0
Bit 11=0
Reserved
Bit 8=1
Bit 11=1
Reserved
Discs,
(DM,DF,
FL)
8-Line
Asynchronous
Communications
Multiplexer
(TY)
Bit 9=0
Bit 12=0
Bit 9=1
Bit 12=1
Reserved
Reserved
Normal read
Read with byte
granularity
(word 2 bit
4 set)
M.READ
M.READ
M.READ
M.READ
M.READ
M.READ
(If bit 2=0)
convert lower
case
character
to upper case
Inhibit
conversion
No special
character
detect
Special
character
detect
Do not purge
type ahead
buffer
Purge type
ahead buffer
M.WRIT
M.WRIT
M.WRIT
Normal write
M.WRIT
Write with
input subchannel
monitoring
plus software
flow control
M.WRIT
M.WRIT
Continued on next page
L·22
Data Structures
File Control Block (FCB), 16 Word
(
Table L-1
Special Control Flags (Continued)
Device
ALIM
(Asynchronous
Line
Interface
Module)
Terminals
(TY)
(Bit 2=0)
Read:
receive
data
(bytes)
defined
for
transfer
count
Write:
formatted
MPX-32 Reference
(Bit 2=1)
Bit 8
Bit 9
Bit 2
Bit 8
Bit 9
Read
On Read:
0
0
1
0
=Blind mode reset
=Echo on read
=Receive data
=Receive data
Write
=Formatted write
=Initialize device
=Unformatted write
1= Inhibit
conversion
of lower
case
characters
to upper
case
0= Convert
1
N/A
0
0
0
1
N/A
0
0
0
1
N/A
N/A
N/A
0
1
N/A
Bit 10
Bit 11
L-23
Bit 12
File Control Block (FCB), 16 Word
Word 3
Bits 0-31
Status word (FCB.SFLG) - 32 indicator bits are set by IOCS to
indicate the status, error, and abnonnal conditions detected
during the current or previous operation. The assignment of
these bits is shown as follows:
Bits
Meaning
if Set
0
OP
1
2
ERR
BB
3
4
5
PRO
INOP
BOM
6
7
EOF
EOM
8-9
10
TIME
11-15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
ECHO
INT
LEN
PROG
DATA
CTRL
INTF
CHAI
BUSY
ST
CTR
ATTN
CHA
DEV
CHK
EXC
Definition
operation in progress. Request has
been queued. (Note: Reset after post I/O
processing complete.)
error condition found
invalid blocking buffer control pointers
have been encountered during file blocking
or unblocking
write protect violation
device inoperable
beginning-of-medium (BOM) (load point)
or illegal volume number (multivolume
magnetic tape)
end-of-file
end-of-medium (end of tape, end of
disk file)
reserved
last command exceeded time-out value
and was tenninated
reserved
echo
post program-controlled interrupt
incorrect length
channel program check
channel data check
channel control check
interface check
chaining check
busy
status modified
controller end
attention
channel end
device end
unit check
unit exception
Word 4
Bits 0-31
L·24
Record length (FCB.RECL) - this field is set by 10CS to indicate the
actual number of bytes transferred during read/write operations.
Data Structures
'"
File Control Block (FCB), 16 Word
WordS
Bits 0-7
ReseIVed
Bits 8-31
I/O queue address (FCB.IOQA) - this field is used by 10CS to point
to the I/O queue for an I/O request initiated from this FCB
Word 6
Bits 0-7
Special status bits (FCB.SPST). The interpretation
of these bits is shown below:
Bits
Definition
o
no-wait normal end action not taken
no-wait error end action not taken
1
2
3
4
5-7
Bits 8-31
(
request killed, I/O not issued
if set, exceptional condition has occurred in the
I/O request
if set, software read flow control required
reseIVed
Wait I/O error return address (FCB.ERRT) - this field is set by the
user and contains the address to which control is to be transferred
in the case of an unrecoverable error when control bits 1 and 3
of word 2 are reset. If this field is not initialized and an
unrecoverable error is detected under the above conditions, the
requesting task is aborted.
Word 7
Bits 0-7
Index to FPT (FCB.FPTI) - this field is set by 10CS to index into the
associated entry in the file pointer table (FPT)
Bits 8-31
FAT address (FCB.FATA) - this field is set by 10CS to point to the
associated file assignment table (FAT) entry.
Word 8
Bits 0-7
ReseIVed
Bits 8-31
Data buffer address (FCB.ERWA) - start address of data area
for read or write operations. (24 bit pure address)
Word 9
Bits 0-31
Quantity (FCB.EQTY}-- number of bytes of data to be transferred
(
MPX-32 Reference
L-25
File Control Block (FCB), 16 Word
Word 10
Bits 0-31
Random access address (FCB.ERAA) - this field contains a
block number (zero origin) relative to the beginning of the
disk file. It is the start address for the current read or
write operation with word 2 bit 4 set and word 2 bit 12 reset.
or
For disk read requests with word 2 bits 4 and 12 set (read with
byte granularity), this word defines the byte offset relative to the
beginning of the file. Note: Ifword 9 is zero, the file retains
its position prior to the call.
Word 11
Bits 0-31
Status word one (FCB.ISTl) - these are the first 32 bits
of status returned by the sense command
Word 12
Bits 0-31
Status word two (FCB.IST2) - these are the second 32 bits
of status returned by the sense command
Word 13
Bits 0-7
Reserved
Bits 8-31
No-wait I/O (FCB.NWOK) - normal completion return address.
This user routine must be exited by calling the M.xIEA service.
Word 14
Bits 0-7
Reserved
Bits 8-31
No-wait I/O (FCB.NWER) - error completion return address.
This user routine must be exited by calling the M.xIEA service.
Word 15 (Applicable only to volume resource.)
Bits 0-7
(FCB.BBN) - Number of 192 word buffers for user supplied blocking
buffers. A value of one or zero in this field specifies one
blocking buffer.
Bits 8-31
Blocking buffer address (FCB.BBA) - starting address
of a contiguous area of memory FCB.BBN buffers long
c
L·26
Data Structures
File Control Block (FCB), 16 Word
Table L-2
Device Functions (Standard Devices)
IOCS
Op
Code
Operation
Line
Printer
(LP)
Mag Tape
(M9/MT)
Disk
(DM/DF/
DC/Floppy)
Handler=F8XIO
(8-Line)
Open
(M.FILE)
0
IOCS
opens
IOCS opens
IOCS opens
Initialize lOP
channel if
necessary
Rewind
(M.RWND)
1
Eject,set
BOMbit
word 3 bit 5
inFCB
Rewind Tape
Set current
block address
to zero (FAT)
SENSE operation
Read Record
(M.READ)
2
Spec error
Read to data
buffer
Read to data
buffer
Read to data
buffer
Write record
(M.WRIT)
3
Write from
data buffer
Write from
data buffer.
If blocked
writes n
data buffers
to blocking
buffer before
output
Write from
data buffer.
If blocked IOCS
writes n
data buffers
to blocking
buffer before
output
Write record to
terminal
Write EOF
(M.WEOF)
4
NOP*
WriteEOF
If blocked,
IOCS writes
EOF. If
unblocked
writes
X'OFEOFEOF'
NOP*
Execute
Channel
5
Spec error
Execute
Channel
Program
Execute
Channel
Program
Execute channel
Program
(
*NOP - No operation performed
Continued on next page
MPX-32 Reference
L-27
File Control Block (FCB), 16 Word
Table L-2
Device Functions (Standard Devices) (Continued)
IOCS
Op
Operation
Code
Line
Printer
(LP)
MagTape
(M9/MT)
Disk
(DM/DF/
DC/Floppy)
Handler=F8XIO
(8-Line)
Advance
Record
(M.FWRD)
6
Spec error
Advance
record
If blocked,
advance
record. If
unblocked,
advance one
192W block.
Set data tenninal
ready
Advance
File
(M.FWRD)
7
Spec error
Advance file
(past EOF)
Spec error
Reset data
tenninal ready
Backspace
Record
(M.BACK)
8
Spec error
Backspace
record
If blocked,
backspace
record. If
unblocked
backspace
one 192W
block
Used by J.TINIT to
initialize tenninals
Backspace
File
(M.BACK)
9
Spec error
Backspace
file to
previous
EOF
Spec error
Reset request to
send
command
Upspace
(M.UPSP)
A
Upspace
Multivolume
only. If BOT,
writes volume
record. If
EOT, perfonns
ERASE, writes
EOF, and
issues MOUNT
message.
Spec error
on F-class
disks. For
floppy only:
format
diskette.
New diskettes
must be
formatted
prior to
nonnal usage.
Set request to send
command
Erase or
Punch
Trailer
Not user
IOCS/handler
provides call
automatically
B
NOP
Multivolume
only. Same
as upspace
above.
Erases 4" of
tape before
writing
NOP
Set/reset break
(depends on flags
in FCB)
o
Continued on next page
L·28
Data Structures
File Control Block (FCB), 16 Word
(
Table L-2
Device Functions (Standard Devices) (Continued)
Operation
IDCS
Op
Code
Line
Printer
(LP)
Mag Tape
(M9/MT)
Disk
(DM/DF/
DC/Floppy)
Handler=F8XID
(8-Line)
Eject!
Punch
Leader
(M.EJECT)
C
Eject to
top of
form
Write
dummy
record
with eject
control
character
as first
character
NDP
Define special
character
Close
(M.CLSE)
D
IDCS
closes
IDCS
closes
IDCS
closes
NDP
Reserve
FHD
Port
E
Spec error
Spec error
Reserve
port-4MB
disk only.
Else, spec
error
Reserve
Dual
Ported
Disk
Set single-channel
operation (default)
command
Release
FHD
Port
F
Spec error
Spec error
Release
port-4MB
disk only.
Else, spec
error
Reserve
Dual
Ported
Disk
Set dual-channel
operation
(~
MPX·32 Reference
L·29
File Control Block (FCB), 16 Word
,(--~\
Table L-3
Device Functions (Terminals, Handler Action Only)
Operation
IOCS
Op
Code
o
Handler = H.ASMP
(ALIM)
Open
M.FILE
0
NOP*
Rewind
M.RWND
1
NOP*
Read record
M.READ
2
Read to data buffer
Write record
M.WRIT
3
Write record to terminal
Write EOF
M.WEOF
4
NOP*
Execute channel
5
Execute channel
Advance record
M.FWRD
6
Connect communications channel
Advance file
M.FWRD
7
Disconnect communications channel
Backspace record
M.BACK
8
Initialize device and set time-out value
Backspace
file M.BACK
9
Clear break status flag word
Upspace
M.UPSP
A
Spec error**
Erase/punch
trailer
B
Transmit break
Eject/punch
leader
M.EJECT
C
Spec error**
Close
M.CLSE
D
NOP*
ReserveFHD
port
E
Spec error**
ReleaseFHD
port
F
Spec error**
* NOP =No operation performed
** Spec Error =Illegal operation code
c
L-30
Data Structures
File Control Block (FCB), 16 Word
(
Table L-4
Standard Carriage Control Characters and Interpretation
Result on Directly
Allocated Printer
(Serial or parallel)
Single space
before print
SLO
Single space
before print
Double space
before print
Double space
before
Page eject (slew)
before print
Page eject (slew)
before print
Control
Character
Blank
Hexadecimal
Value
20
0
30
1
31
+
2B
No linefeed.
no carriage
return before
write (line
append)
No space before
print (overprint)
No space before
print (overprint)
-
2D
Five linefeeds.
one carriage
return before
write
Single space
before print
Page eject. save
and print
up to three user
supplied title lines.
See Note 1.
<
3C
One linefeed.
one carriage
return before
write
Single space
before print
Set inhibit spooler
title line in this file.
>
3E
One linefeed.
one carriage
return before
write
Single space
before print
Set enable spooler
title line in this file.
=
3D
One linefeed.
one carriage
return before
write
Single space
before print
Page eject and clear
up to three usersupplied title lines
in this file.
(
Result on
a Terminal
One linefeed.
one carriage
return before
write
Two linefeeds.
one carriage
return before
write
Five linefeeds.
one carriage
return before
write
Notes:
1.
User-supplied title lines have the same effect as this character. Supplying a
fourth title line clears the first three. but only one page is ejected. User-supplied
titles are retained by the spooler and are repeated at the top of each page until
cleared or the spool file ends.
MPX-32 Reference
L-31
File Control Block, Compatible Mode 8 word (FCB)
L.6 File Control Block, Compatible Mode 8 word (FCB)
12
Logical fIle code (FCB.LFC)
WOld
o
1
Transfer control word (FCB.TCW)
2
General control
flags
(FCB.GCFG)
Special flags
(FCB.SCFG)
Random access address
'(FCB.CBRA)
3
4
5
6
7
Shaded areas are set by the system.
A.LSW.FCB
/""
Word 0
Bit 0
Reserved
Bits 1-7
Opemtion code (FCB.OPCD) - type of function requested of
the device handler. This field is set by IOCS as a function of the
requested service.
Bits 8-31
Logical file code (FCB.LFC) characters is allowed.
any combination of three ASCII
Word 1 (FCB.TCW)
This word supplies a transfer control word (TCW) that describes a data buffer
and transfer quantity. If no TCW definition is supplied, the transfer buffer
defaults to location zero of the task's logical address space and is 4096 words
long.
Bits 0-11
Quantity - 12 bit field specifying the number of data
items to be transferred. This quantity must include the
carriage control character, if applicable. The transfer quantity
is in units detennined by the address in bits 12 to 31.
o
L·32
Data Structures
File Control Block, Compatible Mode 8 word (FCB)
(
Bits 12-31
Fonnat code and buffer address- bits 12, 30 and 31
specify byte, halfword, or word quantities for data transfers.
They are interpreted as follows:
Type of
Transfer
Byte
Halfword
Word
F
(12)
I
o
o
C
(30,31)
xx
xl
00
Address
13-31
13-30
13-29
Word 2
Bits 0-7
General control flags (FCB.GCFG) - these eight bits enable the user to
specify the manner in which an operation is to be perfonned by IOCS.
The interpretation of these bits is shown below:
(
(MPX·32 Reference
L·33
File Control Block, Compatible Mode 8 word (FCB)
Bit
Meaning
if Set
o
NWT
1
NER
2
DFI
3
NST
4
RAN
5
6
EXP
7
IEC
Bits 8-12
Bits 13-31
Definition
laCS returns to the user immediately after the
I/O operation is queued. If reset, laCS exits to the
calling program only when the requested operation
has been completed.
error processing is not perfonned by either the device
handler or laCS. An error return address is ignored
and a nonnal return is taken to the caller, however,
the device status is posted in the FCB unless bit
3 is set. If reset, nonnal error recovery is
attempted. Nonnal error processing for disk and
magnetic tape is automatic error retry. Error
processing for unit record devices except the
system console is accomplished by lacs typing
the message INOP to the console, which allows
the operator to retry or abort the I/O operation.
If the operator aborts the I/O operation, or if
automatic error retry for disk or magnetic tape is
unsuccessful, an error status message is typed
to the console and the error return address is
taken if provided. Otherwise, the task is aborted.
data fonnatting is inhibited. Otherwise, data
fonnatting is perfonned by the appropriate device
handler. See Table L-5 for more explanation.
device handlers perfonn no status checking and no
status information is returned. All I/O appears
to complete without error. Otherwise, status
checking is perfonned and status infonnation
is returned as necessary.
file accessing occurs in the random mode.
Otherwise, sequential accessing is perfonned.
reserved (M.FILE)
must be 0 for 8 word FCB.
this bit is reserved for internal lacs use.
Special Control Specification (FCB.SCFG). - This field
contains device control specifications unique to certain devices.
Interpretation and processing of these specifications are perfonned
by the device handlers. A bit setting is meaningful only when a
particular type of device is assigned as indicated in Table L-2.
Random access address (FCB.CBRA) - This field contains
a block number (zero origin) relative to the beginning of the disk
file, and specifies the base address for read or write operations.
c
L-34
Data Structures
File Control Block, Compatible Mode 8 word (FCB)
Table L-5
Special Control Flags (8 Word FCB)
Device
Line
Printer
(LP)
Discs,
(DM,DP,
PL)
8-Line
Asynchronous
Conununications
Multiplexer
(TY)
(
Device
Line Printer (LP)
Bit 8:0
Bit 8=1
Bit 9::0
Bit 2=0
Bit 2=1
Interpret first
character as
carriage
control
Report EOP if
X'OFEOPEOP'
encOlU1tered
in word 0 of
1st block
during read
of unblocked
file
M,READ
Interpret first
character as
data
See bit 8
X'OFEOFEOP'
in word 0
not
recognized
as EOP
Ponn
control
No faun
control
M,READ
M.READ
M.READ
M.READ
M.READ
No special
character
formatting
ASCII control
passed as
data
ASCII control
character
detect
Echo by
controller
No echo by
controller
M.WRlT
Interpret first
character as
data
SVC 1,X'3E'
Stop
transmitting
break
SVC 1,X'3E'
Start
transmitting
break
M.WRIT
M.WRIT
Initialize
device (load
UART
parameters)
Perfonn
special
character
fonnatting
M.WRIT
Interpret first
character as
carriage
control
Bit 10:0
Bit 10=1
Bit 11:0
Bit 11=1
Normal
write
Bit 12=0
Bit 9=1
Bit 12=1
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
M.READ
M.READ
M.READ
M.READ
M.READ
M.READ
(If bit 2=0)
convert lower
case
character
to upper case
Inhibit
conversion
No special
character
detect
Special
character
detect
Do not purge
type ahead
buffer
Purge type
ahead buffer
M.WRIT
M.WRlT
M.WRIT
M.WRIT
M.WRIT
M.WRIT
Normal write
Write with
input subchannel
monitoring
plus software
flow control
Discs,
(DM,DP,
PL)
8-Line
Asynchronous
Conununications
Multiplexer
(TY)
Continued on next page
MPX-32 Reference
L-35
File Control Block, Compatible Mode 8 word (FCB)
10
'lJ'
Table L-5
Special Control Flags (8 Word FCB) (Continued)
Device
ALIM
(Asynchronous
Line
Interface
Module)
Terminals
(TY)
(Bit 2=0)
Read:
receive
data
(bytes)
defined
for
transfer
count
Write:
formatted
L-36
(Bit 2=1)
Bit 8
Bit 9
Bit 2
BitS
Bit 9
0
0
1
0
1
0
0
1
N/A
N/A
0
0
0
0
1
N/A
N/A
N/A
0
1
N/A
Bit 10
Read
On Read:
=Blind mode reset
=Echo on read
=Receive data
=Receive data
1= Inhibit
conversion
of lower
case
characters
to upper
case
0= Convert
Write
=Formatted write
=Initialize device
=Unformatted write
Bit 11
Data Structures
Bit 12
File Control Block, Compatible Mode 8 word (FCB)
Word 3
Bits 0-31
(
Status word (FCB.SFLG) - 32 indicator bits are set by 10CS to
indicate the status, error, and abnonnal conditions detected
during the current or previous operation. The assignment of
these bits is shown as follows:
Bits
Meaning
if Set
0
OP
1
2
ERR
BB
3
4
5
PRO
INOP
BOM
6
7
EOF
EOM
8-9
MPX·32 Reference
10
TIME
11-15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
ECHO
INT
LEN
PROG
DATA
CTRL
INTF
CHAI
BUSY
ST
erR
ATTN
CHA
DEV
CHK
EXC
Definition
operation in progress. Request has
been queued. (Note: Reset after post I/O
processing complete.)
error condition found
invalid blocking buffer control pointers
have been encountered during file blocking
or unblocking
write protect violation
device inoperable
beginning-of-medium (BOM) (load point)
or illegal volume number (multivolume
magnetic tape)
end-of-file
end-of-medium (end of tape, end of
disk file)
reserved
last command exceeded time-out value
and was tenninated
reserved
echo
post program-controlled interrupt
incorrect length
channel program check
channel data check
channel control check
interface check
chaining check
busy
status modified
controller end
attention
channel end
device end
unit check
unit exception
L·37
File Control Block, Compatible Mode 8 word (FCB)
i!
Word 4
Bits 0-31
'~j
Record length (FCB.RECL) - this field is set by IOCS to indicate the
actual number of bytes transferred during read/write operations.
Word 5
Bits 0-7
Reserved
Bits 8-31
I/O queue address (FCB.IOQA) - this field is used by IOCS to point
to the I/O queue for an I/O request initiated from this FCB
Word 6
Bits 0-7
Special status bits (FCB.SPST). The interpretation
of these bits is shown below:
Bits
Definition
o
no-wait normal end action not taken
no-wait error end action not taken
kill command, I/O not issued
if set, exceptional condition has occurred in the
I/O request
if set, software read flow control required
reserved
1
2
3
4
5-7
Bits 8-31
Wait I/O error return address (FCB.ERRT) - this field is set by the
user and contains the address to which control is to be transferred
in the case of an unrecoverable error when control bits 1 and 3
of word 2 are reset. If this field is not initialized and an
unrecoverable error is detected under the above conditions, the
user is aborted.
Word 7
L-38
Bits 0-7
Index to FPT (FCB.FPTI) - this field indexes into the appropriate
entry in the file pointer table (FPT)
Bits 8-31
FAT address (FCB.FATA) - this field points to the file assignment
table (FAT) entry associated with all I/O performed for this
FCB. This field is supplied by 10CS.
Data Structures
File Control Block (FeB), High Speed Data
(
L.7 File Control Block (FCB), High Speed Data
The following section details the 16 words that make up the FCB for the HSD.
wont 0
o
7 8
15 16
23 24
31
Logical fIle code (FCB.LFC)
1
2
3
4
5
6
7
8
9
(
10 ~------------------------------------------------~
11
12
13
14
15
Shaded areas are set by the system.
Word 0
Bit 0
T2FCB
Reserved
Bits 1-7
Contain the operation code, set by IOCS that specifies the type of
function requested of H.HSDG.
Bits 8-31
Contain the logical file code associated with the device for the I/O
operation.
Word 1
This word is reserved and should be set to zero.
MPX-32 Reference
L-39
File Control Block (FCB), High Speed Data
/f\
Word 2
d'
)
'---"I
Bits 0-7
Contain control flags that enable the user to specify how an operation
is to be performed by 10CS. Following is the meaning of these bits
when they are set:
Bit
0
1
2
3
Meaning When Set
10CS returns to the user immediately after the
1/0 operation is queued (no wait I/O). If reset,
10CS exits to the calling program only when the
HSD completes the requested operation (wait I/O).
H.HSDG and 10CS do not perform error processing.
10CS ignores the error return address and takes
a normal return to the caller. H.HSDG posts
device status in the FCB (unless bit 3 is set).
If reset, H.HSDG and 10CS perform error processing.
specifies physical execute channel program. If
reset, specifies logical channel program or nonexecute channel program I/O request
10CS performs no status checking and does not
return status information. Ali I/O appears to complete
without error. If reset, 10CS performs status checking
and returns status information.
6
Reserved, should be zero.
specifies 16 word FCB. Must be set to 1.
7
reserved for internal 10CS use.
4,5
i'" -"',
i
",""--j
o
L·40
Data Structures
File Control Block (FeB), High Speed Data
(~
Bits 8-23
contain the following special flags:
Bit
(
Meaning When Set
8
specifies request device status after a transfer.
H.HSDG adds an 10CB to the 10CL to retrieve
device-specific status after the data transfer completes.
9
specifies send device command prior to data transfer.
H.HSDG prefixes the transfer with an 10CB that sends
a device command word to the device. The value sent
is the 32-bits contained in word 10 of the FCB.
10
specifies disable time out for this request. This
bit indicates the operation will take an indeterminable
period of time. In most cases this applies only to
read operations.
11
specifies set UDDCMD from the least significant
byte of word 2. This bit indicates that the UDDCMD
byte in the data transfer 10CB must be set to the least
significant byte of FCB word 2. This allows the user
to pass additional control information to the device
without modifying the device driver.
12
specifies disable asynchronous status notification
during no-wait I/O.
13
specifies the execute channel program request INIT.
By setting this bit, all preliminary I/O data structures
are set up based on the I/O command list address provided in
word 8 of the FCB. When set, this bit prepares for future
cyclic I/O requests but does not issue any I/O.
14
specifies the execute channel program request GO. This
bit issues an SIO for the most recently processed INIT
execute channel program request (see bit 13).
15-23
reserved
Note:
For further information on the HSD FCB please see the H.HSDG
section in the MPX-32 Technical Manual Volume II.
Bits 24-31 if bit 11 is set, these bits defme the UDDCMD field of the generated
IOCB, overriding the default value from a handler table. This field
applies only to FCB format.
MPX-32 Reference
L-41
File Control Block (FCB), High Speed Data
Word 3
IOCS uses this word to indicate status, error, and abnonnal conditions detected
during the current or previous operation. Following is the meaning of the bits
when they are set:
Bit
o
1
2, 3
4
5-15
16
17, 18
19
20
21
22
23
24
25
26
27
28
29
30,31
Meaning When Set
operation in progress. Request has been queued.
This bit is reset after post I/O processing completes.
error condition found
not applicable, should never be returned
device inoperable, HSD not present or offline
not applicable, should never be returned
a time-out occurred and a CD tenninate was
issued.
not applicable, should never be returned
there was data remaining in the HSD fifo when
the transfer count equaled zero.
a parity error occurred during the current data
transfer.
a non-present memory error occurred during
the current data transfer.
program violation. An invalid operation code
was detected.
device inoperative
HSD data buffer overflow. Some data from the
device was lost.
external tennination
IOCB address error
error on TI address fetch
device EOB
Non-device access errors precluded request queuing.
For a list of the errors, see word 12.
non-execute channel program type of 10CB in
error as follows:
Value
00
01
10
Meaning
data transfer
device status
command transfer
Word 4
This word specifies the record length. For non-execute channel program I/O,
lacs sets this word to indicate the number of bytes transferred during read or
write operations.
L·42
Data Structures
File Control Block (FCB), High Speed Data
(
WordS
Bits 0-7
Bits 8-31
Word 6
Bits 0-7
reserved
specify the 10Q address. IOCS sets this field to point to the IOQ
entry initiated from this FCB.
specify special status as follows:
Bit
o
1
2
3
4
5-7
Bits 8-31
(
Word 7
Bits 0-7
Bits 8-15
Meaning When Set
no-wait normal end action not taken
no-wait error end action not taken
kill command, I/O not issued
an exception condition has occurred in the I/O request
not used
reserved
contain the wait I/O error return address. The user sets this field to
the address where control is to be transferred for unrecoverable errors
when bits 0, 1, and 3 of word 2 are reset. If this field is not
initialized and an unrecoverable error is detected under the above
conditions, the user task is aborted.
set by the I/O control system (lOCS), contains an index to the file
pointer table (FPT) entry for this I/O operation.
supplied by the 10CS, points to the file assignment table (FAT) entry
associated with this FCB.
(
MPX-32 Reference
L-43
File Control Block (FCB), High Speed Data
Word 8
Bits 0-7
Bits 8-31
reserved
these bits are used as the data address, a logical IOCL address, or a
physical IOCL address as follows:
Data address - This is the starting address of the data area for FCB
format I/O operations. This address must be a word address.
Logical IOCL address - This is a logical, doubleword address that
points to a user-supplied IOCL for SIO format I/O operations. For
more information about SIO format, refer to Reference Manual
Volume I, Chapter 3. The execute channel program entry point
(H.IOCS, to) must be used and bit 2 of word 2 of the FCB is reset.
All addresses within the IOCL are assumed to be logical and map
block boundary crossings need not be resolved.
Physical IOCL address - This is a physical, doubleword address that
points to a user-supplied IOCL for SIO format I/O operations. The
execute channel program entry point (H.IOCS,tO) must be used and
bit 2 of word 2 of the FCB is set. All addresses within the IOCL are
assumed to be physical and all map block boundary crossings are
assumed to be resolved.
Word 9
This word specifies the number of bytes of data to be transferred.
Word to
For nonexecute channel program format, this word defines a device command.
Word 11
Reserved -
'"
/
should be set to zero.
Word 12
This word contains status sent from the user's device or if bit 29 of word 3 is set,
this word defines the opcode processor (EP5) detected errors as follows:
Value
I
2
3
4
5
6
7
8
9
to
L·44
Explanation
request made with non-expanded FCB
FCB format transfer count was zero
FCB format, byte transfer count was not
a multiple of 4 bytes
SIO format with a physical JOCL request
by an unprivileged caller
SIO format with a physical 10CL request
by a nonresident caller
first 10CB in caller's IOCL is a transfer in channel
caller's 10CL not on a doubleword boundary
SIO format 10CL contains an 10CB with a
zero transfer count
infinite transfer in channel loop
consecutive SOBNZ's in 10CL
Data Structures
c
File Control Block (FeB), High Speed Data
(
11
12
13
14
15
16
Word 13
Bits 0-7
Bits 8-31
Word 14
Bits 0-7
Bits 8-31
Word 15
Reserved -
MPX-32 Reference
SOBNZ target is not in the 10CL
the transfer address is not on a word
boundary
unprivileged caller's input buffer includes
protected locations
unprivileged caller's input buffer is unmapped
either in MPX-32 or below DSECf
cyclic I/O request was made for which no cyclic
10Q is current
cyclic I/O request was made and permanent 10Q
support was not sysgened into the system
reserved
contain the address of the user-supplied routine to branch to for nowait I/O normal completion. This routine must be terminated by
calling H.IOCS,34 (no-wait I/O end action return). If word 2 bit 12
is reset, this address plus one word is the location where control is
transferred on asynchronous status notification.
reserved
contain the address of the user-supplied routine to branch to for nowait I/O error completion. This routine must be terminated by
calling H.IOCS,34 (no-wait I/O end action return).
should be set to zero.
L-45
File Pointer Table (FPT)
.(---\
L.S File Pointer Table (FPT)
"L.J
The file pointer table (FPT) provides the linkage between the file control block (FCB)
and the file assignment table (FAn. It also allows for multiple logical file code
assignments to be made equivalent to the same FAT. The linkage to the FAT is
perfonned at assignment. The linkage to the FCB is perfonned at open and is reestablished if necessary for every operation at opcode processing time. The FPT
resides in the task's service area.
FPT entries one to six are reserved for the system as follows:
Entry 1 - System LFC *s*
Entry 2 - Load module LFC *LM
Entry 3 - H.VOMM resource descriptor LFC (1)
Entry 4 - H.VOMM directory LFC (2)
Entry 5 - H.VOMM DMAP/SMAP LFC (3)
Entry 6 - H.VOMM modify resource descriptor LFC X'FFFEE'
Each FPT entry has the following fonnat:
o
Word 0
7
8
15
16
Reserved
Logical file code (FPT.LFC)
1
Flags (FPT.FLGS).
See Note l.
FCB address (FPT.FCBA)
2
Reserved
FAT address (FPT.FATA)
23
24
31
',._,
Notes:
1.
Bits in FPT.FLGS are assigned as follows:
Bit
o
1
2
3
4
5
6
7
Meaning if Set
reserved
multiple FPT entries exist that point to the same FAT
(Le .• $ASSIGN4 or $ASSIGN lfc TO LFC = lfc statements)
FPT busy flag
FPT open
this FPT entry is not in use
pseudo-SYC assignment (used by TSM)
pseudo-FPT for unassigned tempory file
reserved
o
L-46
Data Structures
Parameter Task Activation Block
(
L.9 Parameter Task Activation Block
The following is the structure of the expanded parameter task activation block:
Word
0
4
8
0
1
2-3
4-5
6-7
8-9
10
PTA. VAT
10
(~
o
Byte
7
PTA.FLAG
PTA.NBUF
16
PTA.ALLO
PTA.MEMS
PTA.PRIO
PTA.SEGS
PTA.FLG2
PTA.EXTD
23
24
31
PTA.NAME
PTA.PSN
18
20
28
2C
30
34
38
3C
40
16-19
Reserved (zero)
50-nn
20-nn
RRS List
PTA.ON
PTA.PROJ
11
PTA.PGOW
12
PTA.TSW
13
PTA.RPTR
14
PTA.PG02
PTA.FSIZ
15
15
8
PTA.NRRS
PTA.NFll..
PTA.RSIZ
Byte
(Hex)
Symbol
Description
0
PTA FLAG
contains the following:
Bit
0
1
2
3
4
5
6
7
Contents
reserved
job oriented (PTAJOB)
terminal task (PTATERM)
batch task (PTABTCH)
debug overlay required (PfA.DOLY)
resident (PfARESD)
directive file active (PfADFIL)
SLO assigned to SYC (PTASLO)
For unprivileged callers, bits 0-3 are not
applicable. These characteristics are inherited
from the parent task.
1
PTA.NRRS
number of resource requirements or zero if same as
summary entries in the load module or executable image
preamble
(~
MPX·32 Reference
L-47
Parameter Task Activation Block
,1'\
,-J
Byte
(Hex)
Symbol
Description
2
PfA.ALLO
memory requirement: number of 512-word pages
exclusive of TSA, or zero if same as the preamble
3
PfA.MEMS
memory class (ASQI E, H or S) or zero if memory
class is to be taken from the preamble. If the memory
class is to be taken from the preamble, the caller has
the option of specifying the task's logical address space
in this field as follows:
Bits
Contents
0-3
hexadecimal value 0 through F representing
the task's logical address space in megabytes
where zero is 1MB and F is 16MB
zero
4-7
4
PfA.NBUF
the number of blocking buffers required or
zero if same as the preamble
5
PfA.NFIL
the number ofFAT/FPT pairs to be reserved or
zero if same as the preamble
6
PfA.PRIO
the priority level at which the task is to be activated
or zero for the cataloged load module priority. See
the Parameter Send Block section in Chapter 2
of the MPX-32 Reference Manual Volume I,
for more details.
7
PfA.SEGS
the segment definition count or reserved (zero)
8
PfA.NAME
contains the load module or executable image name,
left justified and blank filled, or word 2 is zero and
word 3 contains a pathname vector or RID vector
10
PfA.PSN
contains the 1- to 8-character ASCII pseudonym, left
justified and blank filled, to be associated with the task
or zero if no pseudonym is desired. For unprivileged
callers, this attribute is inherited from the parent task
if zero is supplied or the parent is in a terminal or
batch job environment.
18
PfA.ON
contains the 1- to 8-character ASCII owner name,
left-justified and blank-filled, to be associated with the
task or zero if the task to default to the current owner name.
Valid only when task has system administrator attribute.
20
PfA.PROJ
contains the 1- to 8-character ASCII project name,
left-justified and blank-filled, to be associated with files
referenced by this task, or zero if same as LMIT
28
PfA.VAT
the number of volume assignment table (V AT) entries
to reserve for dynamic mount requests or zero if same
as the preamble
''\
\,'-,
0
L·48
Data Structures
/
Parameter Task Activation Block
(
Byte
(Hex)
Symbol
Description
29
PTAFLG2
contains the following flags:
Bit
0
1
2
3
4
5
6
7
2A
PTAEXTD
-1
-2
0
n
2C
30
34
PTAPGOW
PTATSW
PTA.RPTR
38
3C
PTAPG02
PTA FSIZ
3E
PTARSIZ
40
Reserved
debug activating task (PT ADBUG)
Command Line Recall and Edit is in
effect for the task (PTACLRE)
NOTSA option (PTANTSA)
TSA option (PI'ATSA)
expanded PTASK block flag (must
be set to use options 33-64) (PTAEBLK)
reserved (zero)
enables NOMAPOUT option (PT ANMAP)
enables MAPOUT option (PTA MAP)
contains the following values:
Bit
(
Meaning if Set
Meaning if Set
maxaddr of extended MPX-32 and TSA
minaddr of extended MPX-32 and TSA
invalid with PT ATSA or PTANTSA option
a positive number representing a
map block of MPX-32 and TSA
contains the initial value of the task option word or zero
contains the initial value of the task status word or zero
contains a pointer to the resource requirement summary
list or, if an expanded PT ASK block is not used, the RRS
list begins here (see resource requirement summary list
description below)
contains the initial value of the second task option word
contains the length of the fixed portion of
the PTASK block in bytes
contains the number of bytes of the resource
requirement summary
(
MPX-32 Reference
L-49
Parameter Task Activation Block
/(-\
Byte
(Hex)
'~j
Symbol
Description
resource requirement summary list. Each entry contains
a variable length RRS. The RRS list has up to 384 words.
Each entry must be doubleword bounded. Each entry is
compared with the RRS entries in the LMIT. If the
logical file code currently exists, the specified
LFC assignment will override the cataloged assignment,
otherwise the special assignment will be treated
as an additional requirement and merged into the
list. If MPX-32 Revision 1.x fonnat of the
.
RRS is specified, it is converted to the format acceptable
for assignment processing by the Resource Management
Module (H.REMM). See MPX-32 Revision 1.x
Technical Manual for fonnat of the RRS.
50
L.10 TSM Procedure Call Block (PCB)
The PCB contains the infonnation necessary for the seIVice to complete a procedure
call. The fonnat of the PCB is as follows:
o
Word 0
78
15 16
23 24
31
ISend buffer address (pcB.SBA)
-
1 Send quantity (pCB.SQUA)
2
IReturn buffer address (PCB.RBA)
3 Actual return length (pcB.ACRP)
Send buffer address
Send quantity
Return buffer address
Actual return length
Return buffer length
L.11
fReturn buffer length (pCB.RPBL)
is the address of a character string that represents a valid
TSM procedure call directive
contains the length in bytes of the TSM procedure call
directive
is the address of a buffer to contain either valid return
information or an error message if CCI is set and R7
contains a value of 1
is the number of bytes returned from the procedure call
is the size in bytes of the supplied return buffer
Pathname Blocks (PNB)
The pathname block (PNB) is an alternative fonn of a pathname that can be used
interchangeably with pathnames. Because of its structure, it can be parsed faster than
a pathname. The PNB is a double word bounded, variable length ASCII character
string which H. VOMM can distinguish from a pathname since the PNB always starts
with an exclamation point.
L-50
Data Structures
I
Pathname Blocks (PNB)
(
H. VOMM provides a service to convert a patbname to a PNB. The examples which
follow illustrate common patbnames and their corresponding PNB.
Example 1
@VOLl(DIRl)FILEl
Word 0
1
2
3
4
! VOL
blank
VOL 1
blank
blank
blank
5
6
7
8
9
! D I R
ROO T
D I R 1
blank
blank
blank
10
11
12
13
14
15
16
17
! RES
blank
F I L E
1
¥> ¥> ¥>
blank
blank
(
Example 2
FILEl
Word 0
1
! v o L
W0 R K
2
3
! D I R
W0 R K
4
! RES
blank
5
6
7
8
9
MPX·32 Reference
F I L E
1
16 16 16
blank
blank
L-51
Pathname Blocks (PNB)
Example 3
(DIRECTORY) MYFILE
Word 0
! VOL
1
W 0 R K
2
3
! D I R
R 0 o T
4
D I R E
C TOR
Y }6 }6 }6
blank
5
6
7
8
9
! RES
blank
11
12
13
M Y F I
L E }6 }6
blank
blank
Word 0
1
! VOL
S Y S T
2
3
4
5
! D I R
S Y S T
6
7
8
9
LOA D
MOD }6
blank
blank
10
Example 4
@SYSTEM(SYSTEM) LOADMOD
! RES
blank
()
L-52
Data Structures
Post Program-Controlled Interrupt Notification Packet (PPCI)
(
L.12 Post Program-Controlled Interrupt Notification Packet
(PPCI)
If a task sets up a PPC! end-action receiver to check status during execution of its
channel program, the status is returned in a notification packet. The address of the
notification packet is contained in register three upon entering the task's PPC! endaction receiver. The notification packet is described below.
o
7 8
15 16
23 24
31
Word 0 String forward address (NOT.SFA)
1 String backward address (NOT.SBA)
2 Link priority
(NOT.PRI)
NOT.TYPE
See Note 1.
Reserved
3 FCB address (NOT.CODE)
4 PSD 1 of task's PPCI receiver (NOT.PSDl)
5 PSD 2 of task's PPCI receiver (NOT.PSD2)
6 Number of PPCIs received
since last buffer clear
(NOT. STAR)
(
Number of status
doublewords in status buffer
(NOT.STAS)
7 Address of PPCI status buffer (NOT.STAA)
8 Address of buffer storing next status doubleword (NOT.S1PT)
9 Reserved
10-n PPCI status buffer
Notes:
1.
2.
NOT.TYPE - Set to I for asynchronous notification.
Words 0-9 are updated by the operating system and must not be changed by the
user.
MPX-32 Reference
L-53
Parameter Receive Block (PRB)
if "
L.13 Parameter Receive Block (PRB)
~j
The parameter receive block (PRB) is used to control the storage of passed parameters
into the receiver buffer of the destination task. The same fonnat PRB is used for
message and run requests. The address of the PRB must be presented when the
M.GMSGP or M.GRUNP services are invoked by the receiving task.
o
78
Word 0 Status (PRB.ST)
15 16
2324
31
Iparameter receiver buffer address (PRB.RBA)
1 Receiver buffer length (PRB.RBL)
Number of bytes actually received
(pRB.ARQ)
2 Owner name of sending task, word one (pRB.OWN)
3 Owner name of sending task:, word two
4 Task number of sending task (PRB.TSKN)
Notes:
1.
Status (PRS.ST) contains the status-value encoded status byte:
Code
o
1
2
3
4
2.
3.
4.
S.
6.
Definition
nonnal status
invalid PRB address (pRB.EROl)
invalid receiver buffer address or size detected during
parameter validation (pRB.RBAE)
no active send request (PRB.NSRE)
receiver buffer length exceeded (PRB.RBLE)
Parameter receiver buffer address (pRB.RBA) contains the word address of the
buffer where the sent parameters are stored.
Receiver buffer length (pRB.RBL) contains the length of the receiver buffer (0 to
768 bytes).
Number of bytes received (PRB.ARQ) is set by the operating system and is
clamped to a maximum equal to the receiver buffer length.
Owner name of sending task (PRB.OWN) is a doubleword that is set by the
operating system to contain the owner name of the task that issued the parameter
send request.
Task number of sending task (pRB.TSKN) is set by the operating system to
contain the task activation sequence number of the task that issued the parameter
send request.
c
L-54
Data Structures
Parameter Send Block (PSB)
L.14 Parameter Send Block (PSB)
The parameter send block (PSB) describes a send request issued from one task to
another. The same PSB format is used for both message and run requests. The
address of the PSB (word bounded) must be specified when invoking the M.SMSGR
or M.SRUNR services, but is optional when invoking the M.PTSK service.
When a load module name is supplied in words 0 and 1 of the PSB, the operating
system searches the system directory only. For activations in directories other than
the system directory, a pathname or RID vector must be supplied.
When activating a task with the M.SRUNR or M.PI'SK service, the value specified in
byte 0 of PSB word 2 (pSB.PRI) is used to detennine the task's execution priority.
This value overrides the cataloged priorities of the sending and receiving tasks and the
priority specified in the PTASK block. However, priority clamping is used to prevent
time-distribution tasks from using this value to execute at a real-time priority, and
real-time tasks from executing at a time-distribution priority. Values that can be
specified in PSB.PRI are 1-64 (to be the task priority), zero (to use the base priority of
the sending task), and X'FF' (to ignore the PSB priority field).
A PSB can be specified as a parameter for the M.PTSK service, along with the
required task activation (PI'ASK) block. The PTASK block also contains a priority
specification field. The PSB priority value always overrides the PTASK block priority
value.
(
o
Word 0
7
8
15
16
23
24
Load module or executable image name (pSB.LMN) or zero if activation
(or task number (pSB.TSKN) if message or run request to multicopied task)
1
Load module or executable image name, pathname vector, or RID vector
if activation (or zero if message or run request to multicopied task)
2
Priority
(pSB.PRI)
Reserved
Send buffer address (pSB.SBA)
Number of bytes to be sent (pSB.SQUA)
3
Reserved
4
Return parameter buffer length
in bytes (pSB.RPBL)
5
Reserved
Return parameter buffer address (pSB.RBA)
6
Reserved
No-wait request end action address (pSB.EAA)
7
Completion
status (pSB.CSn
Processing
start status
(pSB.ISn
MPX-32 Reference
31
Number of bytes actually
returned (pSB.ACRP)
User status
(pSB.USn
Options
(pSB.OPT)
L-55
Parameter Send Block (PSB)
Word 0
Bits 0-31
Load module or executable image name - contains characters 1
through 4 of the name of the load module or executable image to
receive the run request or
Task number - contains the task number of the task to receive
the message or the task number of the multicopied load module
or executable image to receive the run request.
Word 1
Bits 0-31
Load module or executable image name - contains characters 5
through 8 of the name of the load module or executable image to
receive the run request, or zero if the message or run request is
sent to multicopied load module or executable image.
Word 2
Bits 0-7
Contains the priority at which the receiver task is expected to be
activated. Valid values are 1-64, zero, (for base priority of the
sending task) and X'FF', which generates activation priority
based on a combination of values that can be specified during
task activation.
The following tables show how'the priority of a receiver task is detennined when
activated with M.SRUNR or with M.PfSK.
When Activating with M.SRUNR
Cataloged
Priority of
Send Task
Receive task
1-54
1-54
55-64
55-64
*
*
*
*
*
*
Priority
in PSB
1-54
55-64
1-54
55-64
1-54
1-54
55-64
55-64
0
0
0
0
1-54
55-64
1-54
55-64
*
X'FF'
Activates
Receive task at
Send task cat. priority
55 (time-dist. clamp)
54 (real-time clamp)
Send task cat. priority
PSB priority
54 (real-time clamp)
55 (time-dist. clamp)
PSB priority
Receive task cat. priority
not specified
o
L·56
Data Structures
Parameter Send Block (PSB)
When Activating with M.PTSK
Cataloged
Priority of
Send
Receive
Task
task
1-54
1-54
1-54
1-54
55-64
55-64
55-64
55-54
(
*
*
*
*
*
*
*
*
*
*
*
1-54
55-64
*
*
1-54
55-64
Priority in
PfASK
block
PSB
0
0
1-54
55-64
0
0
0
0
0
0
0
0
*
*
1-54
55-64
0
1-54
1-54
55-64
55-64
0
1-54
55-64
1-54
55-64
1-54
55-64
X'FF'
1-54
55-64
X'FF'
X'FF'
*
*
*
*
*
*
*
0
0
0
1-54
1-54
1-54
55-64
55-64
55-64
0
0
Activates
Receive task at
Send task cat. priority
55 (time-dist. clamp)
Send task cat. priority
55 (time-dist. clamp)
54 (real-time clamp)
Send task cat. priority
54 (real-time clamp)
Send task cat. priority
PSB priority
54 (real-time clamp)
55 (time-dist.clamp)
PSB priority
PSB priority
54 (real-time clamp)
PTASK block priority
55 (real-time clamp)
PSB priority
PTASK block priority
Receive task cat. priority
* not specified
Bits 8-15
reserved
Bits 16-31
Number of bytes to be sent - specifies the number of bytes to
be passed (0 to 768) with the message or run request.
Word 3
Bits 0-7
reserved
Bits 8-31
Send buffer address - contains the word address of the buffer
containing the parameters to be sent.
Word 4
Bits 0-15
Return parameter buffer length - contains the maximum number
of bytes (0 to 768) that may be accepted as returned parameters.
Bits 16-31
Number of bytes actually returned - set by the send message or
run request service upon completion of the request.
MPX-32 Reference
L-57
Parameter Send Block (PSB)
WordS
Bits 0-7
reserved
Bits 8-31
Return parameter buffer address - contains the word address of
the buffer where any returned parameters are stored.
Word 6
Bits 0-7
reserved
Bits 8-31
No-wait request end-action address - contains the address of a
user routine to be executed at a software interrupt level upon
completion of the request.
Word 7
Bits 0-7
Completion status - contains completion status information
posted by the operating system as follows:
Bit
o
1
2
3
4
5
6-7
Meaning if Set
operation in progress (PSB.OIP)
destination task was aborted before completion of
processing for this request (pSB.DTA)
destination task was deleted before completion of
processing for this task (pSB.DTD)
return parameters truncated - attempted return
exceeds return parameter buffer length (PSB.RPT)
send parameters truncated - attempted send exceeds
destination task receiver buffer length (pSB.SPT)
user end-action routine not executed because of
task abort outstanding for this task (can be examined
in abort receiver to determine incomplete operation)
(pSB.EANP)
reserved
.('."
'/
L-58
Data Structures
Parameter Send Block (PSB)
(c
Bits 8-15
Processing start (initial) status - contains initial status
infonnation posted by the operating system as follows:
Bit
0
1
2
3
4
5
6
7
8
(
9
10
11
12
13
14
15
Bits 16-23
MPX-32 Reference
Meaning if Set
nonnal initial status (pSB.IST)
message request task number invalid (pSB.TSKE)
run request load module or executable image name not
found (PSB.LMNE)
reserved
file associated with run request load module or
executable image name does not have a valid
load module or executable image fonnat (pSB.LMFE)
dispatch queue entry (DQE) space is unavailable for
activation of the load module or executable image
specified by a run request (pSB.DQEE)
an I/O error was encountered while reading the
directory to obtain the file definition of the
load module or executable image specified in a run
request (PSB.SMIO)
an I/O error was encountered while reading the
file containing the load module or executable image
specified in a run request (pSB.LMIO)
memory unavailable
invalid task number for run request to module
or executable image in RUNW state
invalid priority specification. An unprivileged
task can not specify a priority which is higher than
its own execution priority (pSB.PRIE).
invalid send buffer address or size (pSB.SBAE)
invalid return buffer address or size (pSB .RBAE)
invalid no-wait mode end action routine address
(pSB.EAE)
memory pool unavailable (pSB.MPE)
destination task receiver queue is full (pSB.DTQF)
User status -
defined by the destination task.
L-59
Parameter Send Block (PSB)
Bits 24-31
Options -
contains user-request control specification as follows:
Bit
Meaning if Set
24
25
request is to be issued in no-wait mode (pSB.NWM)
do not post completion status or accept return
parameters. This bit is examined only if bit 24 is
set. When this bit is set, the request was issued
in the no call back mode. (pSB.NCBM).
,t(-\
'~-)
L.15 Resource Create Block (RCB)
Each H.VOMM entry point that creates a permanent file, a temporary file, a memory
partition, or a directory may receive a resource create block (RCB) in order to fully
define the attributes of the resource that is created. RCB formats are described in the
next three tables. RCBs must be doubleword bounded.
If an RCB is not supplied by the caller, the resource is created with the default
attributes described in the MPX-32 Reference Manual Volume I, Chapter 4.
Permanent and Temporary File Resource Create Block (RCB)
o
Word 0
7
8
15
16
23
24
31
File owner name (RCB.OWNR)
1
2
3
File project group name (RCB.USER)
4
Owner rights specifications (RCB.OWRI). See Note 1.
Project group rights specifications (RCB.UGRI). See Note 1.
Other's rights specifications (RCB.OTRI). See Note 1.
5
6
7
8
9
Resource management flags (RCB.SFLG). See Note 2.
Maximum extension increment (RCB.MXEI). See Note 3.
Minimum extension increment (RCB.MNEI). See Note 4.
11
Maximum file size (RCB.MXSZ). See Note 5.
Original file size (RCB.OSIZ). See Note 6.
12
File starting address (RCB.ADDR). See Note 7.
13
14
File RID buffer (RCB.FAST). See Note 8.
Option flags (RCB.OPTS). See Note 9.
Default override (RCB.FREE). See Note 10.
10
15
o
L-60
Data Structures
Resource Create Block (RCB)
(
Notes:
1.
Rights specifications are optional:
Bit
o
1
2
3
4
9
2.
Bit
Description
0-7
resource type, equivalent to file type code, interpreted
as two hexadecimal digits, 0 - FF (RCB.FfYP)
reserved
file EOF management required (RCB.EOFM)
fast access (RCB.FSTF)
do not save (RCB.NSA V)
reserved for MPX-32 usage
file start block requested (RCB .SREQ)
file is executable (RCB.EXEC)
owner ID set on access (RCB.OWID)
project group ID set on access (RCB.UGID)
reserved
maximum file extension increment is zero. System
default value not used. (RCB.MXEF)
minimum file extension increment is zero. System
default value not used (RCB.MNEF)
reserved
zero file on creation/extension (RCB.ZERO)
file automatically extendible (RCB.AUTO)
file manually extendible (RCB.MANU)
file contiguity desired (RCB.CONT)
shareable (RCB.SHAR) (owner rights spec only)
link access (RCB .LINK)
reserved
file data initially recorded as blocked (RCB.BLOK)
12
13
14
15
16
(
17
18
19
20
21
22
23
24
25
26
27
28
29-30
31
3.
Maximum extension increment is the desired file extension increment specified in
blocks (optional). Default is 64 blocks.
4.
Minimum extension increment is the minimum acceptable file extension
increment specified in blocks (optional). Default is 32 blocks.
5.
Maximum file size is the maximum extendible size for a file specified in blocks
(optional).
Original file size is the original file size specified in blocks (optional). Default
is 16 blocks .
6.
.
.
...
read access allowed (RCB.READ)
write access allowed (RCB. WRIT)
modify access allowed (RCB.MODI)
update access allowed (RCB.UPDA)
append access allowed (RCB.APPN)
delete access allowed (RCB.DELE)
Resource management flags. For any bit not set, system defaults apply and, in
some cases, the default is the equivalent of the bit being set (optional):
8-10
11
(
Description
MPX·32 Reference
L-61
Resource Create Block (RCB)
7.
8.
9.
File starting address is the disk block where the file should start, if possible. If
the space needed is currently allocated, an error is returned (optional).
File RID buffer is the address within the file creator's task where the eight word
resource identifier (RID) is to be returned. If this parameter is not supplied (Le.,
is zero), the RID for the created file is not returned to the creating task.
Option flags bits are as follows:
Bit
o
1
2
Description
owner has no access rights (RCB.OWNA)
project group has no access rights (RCB.USNA)
others have no access rights (RCB.OTNA)
10. Default override - If set, these bits override any corresponding bit set in
RCB.SFLG and the system defaults (optional):
Bit
0-7
8-10
11
12
13
14-22
23
24
25
26
27
28-30
31
L-62
Description
must be zero
reserved
file EOF management not required
fast access not required
resource can be saved
reserved
do not zero file on creation/extension
file is not automatically extendible
file is not manually extendible
file contiguity is not desired
resource is not shareable
reserved
file data initially recorded as unblocked
Data Structures
Resource Create Block (RCB)
("
Directory Resource Create Block (RCB)
o
7
8
15
16
23
24
31
11
Directory owner name (RCB.OWNR)
Directory project group name (RCB.USER)
Owner rights specifications (RCB.OWRI). See Note 1.
Project group rights specifications (RCB.UGRI). See Note 1.
Other's rights specifications (RCB.OTRI). See Note 1.
Resource management flags (RCB.SFLG). See Note 2.
Reserved
Directory original size (RCB.OSIZ). See Note 3.
12
Directory starting address (RCB.ADDR). See Note 4.
13
14
Directory RID buffer (RCB.FASl). See Note 5.
Option flags (RCB.OPI'S). See Note 6.
Default override (RCB.FREE). See Note 7.
Word 0-1
2-3
4
5
6
7
8-10
15
Notes:
1.
Rights specifications bits are as follows:
Bit
o
8
9
10
11
2.
Description
read access allowed (RCB.READ)
directory may be traversed (RCB.TRAV)
directory may be deleted (RCB.DELE)
directory entries may be deleted (RCB.DEEN)
directory entries may be added (RCB.ADEN)
Resource management flags are optional:
Bit
Description
13
27
do not save (RCB.NSAV)
shareable (RCB.SHAR)
3.
4.
Directory original size is the number of entries required (optional).
Directory starting address is the disk block number where the directory should
start, if possible. If the space needed is currently allocated, an error is returned
(optional).
5.
Directory RID buffer is the address within the directory creator's task where the
eight word resource identifier (RID) is to be returned. If this parameter is not
supplied (Le., is zero), the RID for the created directory is not returned to the
creating task.
MPX·32 Reference
L·63
Resource Create Block (RCB)
6.
~-~,
Bit
Description
o
owner has no access rights (RCB.OWNA)
project group has no access rights (RCB.USNA)
others have no access rights (RCB.OTNA)
1
2
7.
,-J
Option flags are as follows:
If default override is set, these bits override any corresponding bit set in
RCB.SFLG and the system defaults (optional).
Bit
Description
0-7
13
27
must be zero
resource can be saved
resource is not shareable
•
Memory Partition Resource Create Block (RCB)
o
Word 0-1
2-3
4
5
6
7
8-9
10
11
12
13
14
15
7
8
15 16
Partition owner name (RCB.OWNR)
23
24
31
Partition project group name (RCB.USER)
Owner rights specifications (RCB.OWRl). See Note 1.
Project group rights specifications (RCB.UGRI). See Note 1.
Other's rights specifications (RCB.OTRI). See Note 1.
Resource management flags (RCB.SFLG). See Note 2.
Reserved
Starting word page number (RCB.PPAG)
Partition original size (RCB.OSIZ). See Note 3.
Partition starting address (RCB.ADDR). See Note 4.
Partition RID buffer (RCB.FAST). See Note 5.
Option flags (RCB.OPTS). See Note 6.
Default override (RCB.FREE). See Note 7.
Notes:
1.
Rights specifications are optional:
Bit
o
1
9
Description
read access allowed (RCB.READ)
write access allowed (RCB. WRIT)
delete access allowed (RCB.DELE)
o
L·64
Data Structures
Resource Create Block (RCB)
(
2.
Resource management flags are optional:
Bit
Description
13
do not save (RCB.NSAV)
3.
4.
Partition's original size is the number of protection granules required.
Partition's starting address is a Sl2-word protection granule number in the user's
logical address space where the partition is to begin.
5.
Partition's RID buffer is the address within the partition creator's task where the
eight word resource identifier (RID) is to be returned. If this parameter is not
supplied (Le., is zero), the RID for the created partition is not returned to the
creating task.
Option flags are optional:
6.
Bits
o
1
2
9
24-31
Description
owner has no access rights (RCB.OWNA)
project group has no access rights (RCB.USNA)
others have no access rights (RCB.OTNA)
defines a static partition (RCB.STAT)
define memory class (RCB.MCLA). Values are:
Value
Memory Class
o
S (default)
E
H
1
2
3
7.
S
If set, these bits override any corresponding bit set in RCB.SFLG and the system
defaults (optional):
Bits
0-7
13
MPX-32 Reference
Description
must be zero
resource can be saved
L-65
Resource Identifiers (RID)
L.16 Resource Identifiers (RID)
The fastest means of locating a volume resource (once created) is by its resource
identifier (must be on a doubleword boundary). The resource identifier has the
following format:
o
Word 0-3
4
5
6
7
7
15
8
16
23
24
31
Volume name
Creation date
Creation time
Volume address of resource descriptor
Must contain zero
Resource type
I
Since the resource identifier contains the volume address of the resource descriptor,
the resource descriptor (which points to and describes the resource) can be accessed
directly without going through the various directories which would otherwise have to
be traversed.
Given a valid patbname defining a resource, the corresponding resource descriptor
may be retrieved by the H. VOMM locate resource seIVice. The first eight words of a
resource descriptor consist of the resource identifier.
o
L-66
Data Structures
Resource Logging Block (RLB)
(
L.17 Resource Logging Block (RLB)
The resource logging block (RLB) is a word-bounded data structure used to pass
infonnation between H.VOMM and the caller. The infonnation is used to locate a
directory entry and resource descriptor for a single resource or for all resources
defined in a particular directory.
o
7 8
15 16
23 24
31
Word 0 Pathname vector or RID address (RLB.TGn
1 Resource directory buffer address (192W) (RLB.BVFA). See Note l.
2 Associated mounted volume table entry address (RLB.MVlE)
3 Parent directory RD block address (RLB.RDAD)
4 Type (RLB.TYPE).
Buffer offset (RLB.BOFF)
See Note 2.
5 Length.
See Note 3.
Return buffer address (RLB.DIRA)
6 User FCB address (RLB.FCB)
Reserved (RLB.INT)
7 Flags.
See Note 4.
Notes:
1.
Optional. If not specified, a resource directory is not returned.
2.
Bits in RLB.TYPE are assigned as follows:
Bits
o
1-7
Meaning if Set
indicates recall (RLB.RECA)
reseIVed
3.
This word contains the address of a buffer and its length in words (the buffer can
be up to 16 words long).
4.
Bits in the flags byte are assigned as follows:
Bits
Meaning if Set
0-1
2
reseIVed
directory entry and resource descriptor for specified
directory are returned
root directory
resource is located
reseIVed
3
4
5-7
MPX·32 Reference
L-67
Resource Requirement Summary (RRS) Entries
L.18 Resource Requirement Summary (RRS) Entries
The resource requirement summary (RRS) is a doubleword bounded data structure
used to identify the resources required by a task to the resource manager. Resources
are statically allocated using the information in the RRS entry. The RRS is generally
built by processors requiring static allocation of resources, such as TSM, cataloger,
etc., or supplied as an argument for dynamic allocation.
For compatibility purposes, revision l..x RRS formats can be used. The details of these
formats can be found in Chapter 2 of a revision l..x Technical Manual.
Type 1 • Assign by Pathname
o
7
8
15
16
Zero
Logical file code (RR.LFC)
1
Type
(RR.TYPE).
See Note 1.
Size
(RR.SIZE)
2
Access (RR.ACCS). See Note 3.
3
Options (RR.OPTS). See Note 4.
Ward 0
4-n
23
Plength
(RR.PLEN)
24
31
Reserved.
See Note 2.
Pathname (variable length) (RR.NAME1)
Type 2 . Assign to Temporary File
o
Ward 0 Zero
1 Type
(RR.TYPE).
See Note 1.
7 8
15 16
23 24
31
Logical file code (RR.LFC)
Size
(RR.SIZE)
Initial file size
(RR.PLEN)
2 Access (RR.ACCS). See Note 3.
3 Options (RR.OPTS). See Note 4.
4-7 Volume name (16 characters; left-justified, blank-filled) (RR.NAMEl)
(Volume name is optional)
o
L·68
Data Structures
Resource Requirement Summary (RRS) Entries
Type 3 • Assign to Device
o
Word 0
7 8
Zero
1 Type
(RR.TYPE).
See Note 1.
23 24
15 16
31
Logical file code (RRLFC)
Size
(RR.SIZE)
Density
(RR.DENS).
See Note 5.
Zero
Channel number
See Note 7.
(RR.CHN3)
Subchannel
number
(RR.SCHN3)
2 Access (RR.ACCS). See Note 3.
3 Options (RR.OPTS). See Note 4.
4 Device type
(RR.DTI).
See Note 6.
Volume
number
(RR.VLNUM)
5 Unformatted ID (1-4 characters) (RRUNFlD)
Type 4 • Assign to LFC
o
8
15
16
Zero
Logical file code (RR.LFC)
1
Type
(RR.TYPE).
See Note 1.
Size
(RR.SIZE)
2
Zero
Logical file code (RR.SFC)
3
Options (RR.OPTS). See Note 4.
Word 0
(
7
23
24
23
24
31
Zero
Type 5 • Assign by Segment Definition
o
7
8
15
16
Zero
Logical file code (RR.LFC)
1
Type
(RR.TYPE).
See Note 1.
Size
(RR.SIZE)
2
Access (RR.ACCS). See Note 3.
3
Options (RR.OPTS). See Note 4.
4
Starting block number (RR.STBLK)
5
Number of blocks (RR.NBLKS)
Word 0
UDT index
(RR.UDTI)
31
Reserved
('
MPX·32 Reference
L-69
Resource Requirement Summary (RRS) Entries
Type 6 - Assign by Resource 10
o
15 16
7 8
Word 0 Zero
23 24
31
Logical file code (RR.LFC)
1 Type (RR.TYPE).
See Note 1.
Size (RR.SIZE)
Zero
Reserved
2 Access (RR.ACCS). See Note 3.
3 Options (RR.OPTS). See Note 4.
4-7 Volume name (16 characters; left-justified, blank-filled)
(RR.NAMEl)
8 Binary creation date (RR.DATE)
9 Binary creation time (RR.TIME)
10 Resource descriptor block address (RR.DOFF)
11 Reserved
Resource type (RR.RTYPE)
Type 7 - Reserved for Future Use
Type 8 - Reserved for Future Use
Type 9 - Mount by Device Mnemonic
o
Ward 0
7
8
15
16
23
24
Zero
System ID (RR.SYSID). See Note 11.
1
Type
(RR.TYPE).
See Note 1.
Size (RR.SIZE)
2
Access (RR.ACCS). See Note 3.
3
Options (RR.OPTS). See Note 4.
4-7
31
Zero
Volume name (16 characters; left-justified, blank-filled)
(RR.NAMEl)
8
Device type
(RR.DT9).
See Note 8.
9
Zero
Reserved
Channel number
(RR.CHN9).
See Note 9.
Subchannel
number
(RR.SCHN9)
c
L-70
Data Structures
Resource Requirement Summary (RRS) Entries
Type 10 - Assign to ANSI Tape
o
15 16
7 8
23 24
31
Logical file code (RR.LFC)
Word 0 Zero
1 Type (RR.TYPE).
See Note 1.
Size (RR.SIZE)
Format (RR.FORM)
/Protect
(RR.PROT)
2 Access (RR.ACCS). See Note 3.
3 Options (RR.OPTS). See Note 4.
4 Record length (RR.RECL)
Block size (RR.BSIZE)
5 Generation nwnber (RR.GENN)
6 Generation version nwnber (RR.GENV)
7 Absolute termination date (RR.EXPIA)
8 Relative termination date
Logical volume identifier (RR.LVID)
(RR.EXPIR)
9 RR.LVID (cont.)
10-13 17-character file identifier (RR.AFID)
14 RR.AFID (cont.)
Reserved
15 Reserved
Type 11 - Assign to Shadow Memory
o
Word 0
7
8
15 16
23
24
31
Zero
1 Type (RR.TYPE)
See Note 1.
Size
(RR.SIZE)
2
Start address (RR.SADD)
3
End address (RR.EADD)
Shadow flags
(RR.SHAD). See Note 10.
Notes:
1.
Bits in RR.TYPE are assigned as follows:
Value
1
2
3
4
5
6
7
8
9
10
11
12-255
MPX·32 Reference
Meaning
assign by pathname (RR.PATH)
assign to temporary file (RR.TEMP)
assign to device (RR.DEVC)
assign to secondary LFC (RR.LFC2)
assign to segment definition (RR.SPACE)
assign by resource ID (RR.RID)
reserved for future use
reserved for future use
mount by device mnemonic (RR.MTDEV)
assign to ANSI labeled tape (RR.ANS)
assign to shadow memory (RR.SHTYP)
reserved
l-11
Resource Requirement Summary (RRS) Entries
,I "
2.
3.
Byte 3 is zero. This field is used by MPX-32 for big blocking buffers.
Bits in RR.ACCS are assigned as follows:
Bits
o
1
2
3
4
5-15
16
17
18
19-31
4.
Meaning if Set
read access allowed (RR.READ)
write access allowed (RR. WRITE)
modify access allowed (RR.MODFY)(not valid for ANSI
tapes)
update access allowed (RR.UPDAT)
append access allowed (RR.APPND)
reserved
explicit shared use requested (RR.SHAR)
exclusive use requested (RR.EXCL)
assign as volume mount device (RR.MNT)
reserved
Bits in RR.OPTS are assigned as follows:
Bits
o
1
2
3
4
5
6
7
8
9
10-11
12
13
14
15
16
17-31
5.
,,-,,/
Meaning if Set
treat as SYC file (RR.SYC) (TSM/JOB only)
treat as SGO file (RR.SGO) (TSM/JOB only)
treat as SLO file (RR.SLO)
treat as SBO file (RR.SBO)
explicit blocked option (RR.BLK)
explicit unblocked option (RR.VNBLK)
inhibit mount message (RR.NOMSG)
reserved for system use
automatic open requested (RR.OPEN)
user-supplied blocking buffer address in FCB (RR.BUFF)
reserved for system use
mount with no-wait (RR.NOWT)
mount as public volume (RR.PUBLC)
set by H.VOMM for special case handling of VOMM
assignments (RR.VOMM)
file is spooled when deallocated (RR.SEP)
ANSI labeled tape on RRS type 3 (RR.ANSI)
reserved
RR.DENS contains the density specification for XIO high speed tape units.
When specified, this field has the following bit significance:
Bits
o
1
6
Meaning if Set
indicates 800 bpi nonretum to zero inverted (NRZI)
indicates i 600 bpi phase encoded (PE)
indicates 6250 bpi group coded recording (GCR)
If this field is zero, 6250 BPI is set by default.
C"'''
:
L·72
Data Structures
_'I
Resource Requirement Summary (RRS) Entries
6.
RR.DT3 specifies whether or not a channel is present and specifies the device
type:
Bits
o
1-7
7.
RR.CHN3 specifies whether or not a subchannel is present and specifies the
channel number:
Bits
o
1-7
8.
Meaning if Set
subchannel is present. Examined only if bit zero of
RR.DT3 is set.
channel number
RR.DT9 specifies whether or not a channel is present and specifies the device
type:
Bits
o
1-7
9.
Meaning if Set
channel present
device type
Meaning if Set
channel present
device type
RR.CHN9 specifies whether or not a subchannel is present and specifies the
channel number:
Bits
o
1-7
Meaning if Set
subchannel is present. Examined only if RR.DT9 is set.
channel number
10. RR.SHAD contains the shadow flags that qualify the start and end addresses, or
specify what portions of the task are to be shadowed:
Bits
0-7
8
9
10
11
12
13
14
15
Meaning if Set
reserved
shadow the task (RR.SHTSK)
shadow the TSA (RR.SHTSA)
shadow the stack (RR.SHST)
shadow memory is required (RR.SHRQ)
shadow the entire task (RR.SHALL)
absolute address (RR.ABS)
relative to the code section origin (RR.CREL)
relative to the data section origin (RR.DREL)
11. RR.SYSID is the ID for mounting a multiprocessor volume. Valid IDs are:
Multiported (MP) 0 through F
Dual Ported (DP) 0 or 1
For more infonnation on mounting multiprocessor volumes see the MPX-32
Reference Manual Volume I, Chapter 4, Mounting Multiprocessor Volumes.
MPX-32 Reference
L-73
Receiver Exit Block (RXB)
/("--'\
'~,/
L.19 Receiver Exit Block (RXB)
The receiver exit block (RXB) is used to control the return of parameters and status
from the destination (receiving) task to the task that issued the send request. It is also
used to specify receiver exit options. The same fonnat RXB is used for both
messages and run requests. The address of the RXB must be presented as an
argument when either the M.XMSGR or M.XR.UNR services are called.
o
Word 0 Return status
(RXB.S1)
1 Options
15 16
23 24
7 8
Return parameter buffer address (RXB.RBA)
Reserved
(RXB.OP1)
31
Number of bytes to be returned
(RXB.RQ)
Notes:
1.
2.
3.
Return status (RXB.ST) contains status as defined by the receiver task. Used to
set the user status byte in the parameter send block (PSB) of the task which
issued the send request.
Return parameter buffer address (RXB.RBA) contains the word address of the
buffer containing the parameters which are to be returned to the task which issued
the send request.
Options (RXB.OPT) contains receiver exit control options. It is encoded as
follows:
o
Exit Type
M.XRUNR
M.xMSGR
Meaning
wait for next run request.
return to point of task interrupt.
1
M.xRUNR
exit task, process any additional
run requests. If none exist,
perfonn a standard exit.
N/A
Value
M.xMSGR
4.
Number of bytes to be returned (RXB.PQ) contains the number of bytes (0 to
768) of infonnation to be returned to the sending task.
o
L·74
Data Structures
Type Control Parameter Block (TePB)
(
L.20 Type Control Parameter Block (TCPB)
The type control parameter block (TCPB) allows I/O to and from the system console
by setting up task buffer areas for messages output by a task and optional reads back
from the console. If no input is desired, word one of the TCPB must be zero.
See the MPX-32 Reference Manual Volume I, Chapter 5 for further details on the
TCPB.
o
12
13
Output quantity
(TCP.OQ)
See
Note 1.
Output data address
(TCP.OTCW)
1
Input quantity
(TCP.IQ)
See
Note 1.
Input data address
(TCP.ITCW)
2
Console Teletype Flags
(TCP.FLGS). See Note 2.
Word 0
11
31
Notes:
1.
Bit 12 is set to 1.
2.
Bits in TCP.FLGS are assigned as follows:
(
Bits
o
31
MPX-32 Reference
Meaning if Set
no-wait I/O
operation in progress. This bit is reset after post-I/O
processing completes.
L-75
Type Control Parameter Block (TCPB)
o
Type Control Parameter Block (TCPB) using 24-bit address:
o
Word 0
7
8
15
16
23
24
Output
quantity
(TCP.OQ)
Output data buffer address (TCP.OTCW)
1
Input
quantity
(TCP.IQ)
Input data buffer address (TCP.ITCW)
2
Console device flags (TCP.FLGS) See Note l.
31
Notes:
1.
Bit intetpretations for TCP.fl.GS are:
Bits
o
1
31
Meaning if Set
no-wait I/O
data buffer addresses are 24-bit addresses (TCP.LAD)
Note: This bit must be set.
operation in progress. This bit is reset after
post-I/O processing completes.
o
L-76
Data Structures
Unit Definition Table (UDT)
(
L.21
Unit Definition Table (UDT)
The unit definition table (UDT) is a system resident structure that identifies devicedependent information required by a handler for a specific device. The UDT is built
by the SYSGEN process, one for each device configured in the system. During
SYSGEN, each UDT is linked to its corresponding controller definition table (eDT)
and its associated controller and handler.
Word 0
1
2
3
4
(
5
6
7
8
9
10
11
12
13
14
15
15
16
23
24
o
7 8
31
UDT index (UDT. UDT!)
CDT index (UDT.CDT!)
Unit status
Device type code
Logical
Logical
(UDT.STAT).
(UDT.DTC).
channel number
subaddress
See Note 1.
(UDT.CHAN)
(UDT. SUB A)
See Note 2.
Reserved
Address of dispatch queue entry of task which has
device allocated if device is not shared (UDT.DQEA)
Sectors per block
Physical channel
Physical
Sectors per
number
subaddress
(UDT.SPB)
allocation unit
(UDT.PCHN)
(UDT.PSUB)
or
(UDT.SPAU)
or
number of
characters
number of lines per
per line
screen (DDT.LINE).
(DDT.CHAR).
See Note 4.
See Note 3.
Flags
Number of sectors
Maximum byte transfer
(UDT.FLGS).
per track on
(UDT.MBX)
See Note 5.
disk or global
line counter if a
terminal (UDT.SPT)
Number of sectors on disk or tab setting if a terminal (UDT.SECS)
Sector size, on disk or a tab
Number of heads on disk or a tab
setting if a terminal (UDT.NHDS)
setting if a terminal (UDT.SSIZ)
Serial number if tape or removable disk (UDT.SERN). See Note 6.
Peripheral time-out value (UDT.PTOV)
Reserved
Address of device context area (UDT.DCAA)
or handler name at initialization (UDT.HNAM)
Bit flags (UDT.BIT2). See Note 7.
Associated allocated resource
table index if assigned (UDT.ART!)
Service interrupt handler address (UDT.SIHA)
Reserved
Secondary flags
Reserved
Reserved
(UDT.CXR)
(UDT.BIT3)
(UDT.DQEN)
(UDT.SHFL)
See Note 8.
See Note 9.
or UDT.RIST. See Note 10
Address of first IOQ linked to this device (UDT.FIOQ)
Address of last IOQ linked to this device (UDT.BIOQ)
Link Priority
Unit Status byte 2 (UDT.STA2).
Link Count
(UDT.LPR1)
(UDT.lOCT)
See Note 11.
(
MPX-32 Reference
L-77
Unit Definition Table (UDT)
Notes:
1.
Bits in UDT.STAT are assigned as follows:
Bit
Meaning if Set
o
online (UDT.ONLI)
1
dual-portd XIO disk (UDT.DPDC)
2,allocated (UDT.ALOC)
3
terminal in use and not in wait (UDT.USE)
4
system output unable to allocate (UDT.NOAL)
5
shared device (UDT.SHR)
6
premounted (UDT.PREM)
7
terminal (TSM) device (UDT.TSM)
2.
For example, 01 for any disk, 04 for any tape, etc. Valid device type codes are
listed in Appendix A.
3.
For disks, contains the number of sectors per block (UDT.SPB). For terminals,
contains the number of characters per line (UDT.CHAR).
4.
For disks, contains the number of sectors per allocation unit (UDT.SPAU). For
SLO or terminals, contains the number of lines per page or screen (UDT.LINE).
Bits in UDT.FLGS are assigned as follows:
5.
Bit
o
1
2
3
4
5
6
7
6.
7.
extended I/O device (UDT.FCLS)
I/O outstanding (UDT.IOUT)
removable disk pack (UDT.RMDV)
a break has been requested for this device (UDT.LOGO)
autoselectable for batch SLO (UDT.BSLO)
autoselectable for batch SBO (UDT.BSBO)
autoselectable for real-time SLO (UDT.RSLO)
autoselectable for real-time SBO (UDT.RSBO)
If the device is a terminal or console, the first halfword is the current terminal
type for TERMDEF (UDT.crDp) and the second halfword is the default
terminal type (UDT.DTDp).
Bits in UDT.BIT2 are assigned as follows:
Bits
o
1
2
3
4
5
6
7
8
9
10
L-78
Meaning if Set
Meaning if Set
port is private; else switched (UDT.DIAL)
port is connected to modem (UDT.MODM)
port has graphic capability (UDT.GRFC)
port is full duplex (UDT.FDUX)
port is configured multidrop (UDT.MDRA)
volume mounted on device (UDT.VOL)
echo by computer (UDT.ECHO)
device has failed. Log off TSM (UDT.DEAD)
cache device (UDT.CAC)
inhibit automatic line wrap (UDT.NRAP)
spool device requires form feed after printing rather
than before; initial form feed is inhibited (UDT.PEOP)
Data Structures
c
Unit Definition Table (UDT)
Bits
11
12
13
14
15
8.
9.
Meaning if Set
quarter inch cartridge tape drive (UDT.QITD)
software read flow control required (UDT.RXON)
software write flow control required (UDT. WX:ON)
hardware read flow control required (UDT.RHWF)
hardware write flow control required (UDT.WHWF)
For switched port, contains the value specified in the LOGONFLE CXR = option
(UDT.CXR)
Bits in UDT.BIT3 are assigned as follows:
Bits
o
1-7
Meaning if Set
SCSI device (UDT.SCSI)
reseIVed
to. UDT.HIST is used as an address save area by pseudo device handlers, such as
ON.IPXIO
11. Bits in UDT.STA2 are assigned as follows:
Bits
0
1
2
3
4
5
6
7
8
(
9
to
11
l2
13
14
15
Meaning if Set
IOQ linked from UDT (UDT.IOQ)
lOP device (initialized by SYSGEN) (UDT.lOP)
device malfunction (UDT.MALF)
operator inteIVention applicable (UDT.lNTV)
use standard XIO interface
floppy disk
cartridge module drive
moving head disk with fixed head option
if software read flow control enabled, use
DTR line; otherwise, use RTS line. (UDT.RDTR)
memory disk (UDT.MD) or valid command line recall and
edit device (UDT.CLRE)
memory allocated for memory disk (UDT.MDAL)
start address of memory disk specified at SYSGEN (UDT.MDST)
multiport device is shared with an MPX-32 Revision 3.2C
or earlier version (UDT.PPV)
device is exclusive ANSI (UDT.ANSI)
serial printer (UDT.SLPR)
port is switched and CXR=N option has been specified
(UDT.DCXR)
(
MPX-32 Reference
L-79/L-80
(
Glossary
access method
A software package that provides the ability to access fields
within records, to classify or order records according to the
contents of fields, and to perform other such functions.
access mode
Defines the range of operations to be performed on a
resource.
aged page
A page which has not been referenced within a predetermined
frame of time during demand page processing. This page is
no longer considered a part of the task's working set.
allocated resource table (ART)
A system resident table with an entry for each currently
allocated resource in the system.
allocation
The process of securing a resource for a specific usage and
access mode for a task.
allocation unit
A mechanism for grouping more than one block on a
formatted disc, or other mass medium, at one time. Usually
specified in multiples of 192-word disc blocks. See disc
block.
argument
A value (string or integer) that is assigned to a parameter.
assign
To associate a resource with a logical file code used by a
process.
. assignment
The process of associating a logical file code with a system
resource. Does not guarantee the resource for a specific use
or access mode for a task.
asynchronous
Implies one entity does not wait for or otherwise
acknowledge another entity when it performs an operation.
asynchronous notification
A process does not stop execution waiting for notification. It
receives a software interrupt when an asynchronous operation
is complete.
base mode
Implies the base register instruction set that allows executable
programs of up to 4096KW (16MB).
blocked I/O
The process of packing records equal to or less than 254
bytes so that more than one record is stored in a 192-word
disc block.
blocking buffers
Buffers used for packing records for blocked I/O. See
blocked I/O.
MPX-32 Reference
GL-1
Glossary
caller notification packet (CNP)
A structure used to supply additional calling parameters and
to control the handling of abnonnal conditions that may occur
during resource requests.
classes of users
A three-level grouping of users into OWNER,
PROJECI'GROUP and OTHER. Used to pennit or limit
access to a resource by 'class'.
command file
A file containing commands known to a particular operating
system or process.
CONCEPT/32
A tenn which implies the entire line of CONCEPT/32
computers; for example, the 32/67.
configuration
Hardware: the physical hardware related to a CPU. Software:
adapting the operating system to a hardware configuration
with the SYSGEN processor.
data files
Files containing data or· transactions that have been processed
or will be processed by a task.
data management
The ability to structure data into records using buffers.
Datapool
An area of memory that contains the same functionality as
Global Common but with the added flexibility of symbolic
references being independent of the actual positioning of data
within the memory area. See Global Common.
deallocate
To detach a resource from a process.
deassign
To remove the association between a logical file code and a
resource and deallocate the resource.
dequeue
To remove from a prioritized list.
demand page
Allocation of memory when the logical page is referenced by
the task on demand. The process of allocating physical
memory when pages are referenced and de allocating physical
memory when pages are no longer active. Pages that are no
longer active are considered aged and removed from the
task's working set.
device
A peripheral unit such as a card reader, a printer, a disc drive,
or a tape drive. Distinguished from media used with devices.
device access
Levels are physical I/O, logical device I/O, and logical file
I/O.
device-dependent I/O
Tasks perfonn operations to a specified device with minimal
10CS overhead.
device-independent I/O Tasks perfonn I/O operations through the use of operating
system calls which are independent of the device used to
perfonn the operation.
GL·2
Glossary
o
Glossary
direct I/O
Tasks perfonn operations bypassing IOCS and handler
functions by coding its own handler and attaching it to a
specific channel.
directory
A list of file names and/or memory partition names. Stored
on disc like a regular file. Located via a resource descriptor
for the directory. Directory names are 1 to 16 characters in
length and valid characters for names are A to Z, 0 to 9, dot
(.) and underscore ( _ ).
directory descriptor
The resource descriptor for a directory.
disc block
A common unit of measurement (some number of words)
used to measure file space on fonnatted media throughout a
system. The number of words in a block is oriented to the
most common sector size on discs used with the system.
DMAP
See resource descriptor allocation map.
dynamic assignment
The association of a logical file code with a system resource
during task execution.
enqueue
To put into a list ordered by software priority.
exclusive use
A resource is not available for use by any other task until that
resource is deallocated by the using task. Guarantees access
to a resource, within the access limitations imposed by the
resource creator, when logical I/O is initiated.
executable image
A file of object code produced by the LINKER/X32.
explicit shared use
A resource can be used concurrently by more than one task.
Each task maintains resource integrity by establishing its own
synchronization and locking mechanisms. Each task is
guaranteed access to the resource, within access limitations
imposed by the resource creator, when logical I/O is initiated.
extended code
That part of the operating system that has been modified to
run in the extended execution space.
extended file control block
A file control block set up by the user which contains more
infonnation than the standard file control block. See file
control block.
file
A set of information stored on a mass medium such as disc or
tape that is given a unique identity (number and often name)
and treated as a single entity for processing.
file control block (FeB)
Set up by the user to describe logical files within a task.
Describes attributes of logical I/O operation.
file descriptor
MPX-32 Reference
A resource descriptor for a file.
Gl-3
Glossary
file identifier
A unique identifier stored in the resource descriptor for a file
when the file is created. Used to access the resource
descriptor without a directory search.
file segment
Set of contiguous allocation units on a volume identifying the
space associated with a file. Each file segment definition
contains the absolute 192-word block volume segment
address and the segment length in 192-word blocks
(maximum of 32 file segment definitions per file).
file space allocation map (SMAP)
A bit map used to allocate space on a volume.
filename
A 1- to 16-character name supplied for a permanent file when
it is created on a mass medium. Used in most cases thereafter
to identify the file. Valid characters for filenames are the
upper-case letters A to Z, the decimal numbers 0 to 9, and the
special characters dot (.) and underscore (_). Filenames to
be used with the compatible interfaces, for example Editor,
File Manager, and Media, are limited to 1 to 8 characters.
format
Standard organization of information.
formatted volume
A disc pack or floppy disc that contains standard volume
system structures established by the Volume Formatter utility.
Global Common
An area of memory accessible by using symbolic names to
identify specific storage cells. Programs belonging to many
independent tasks can freely access the same data and
exchange control information within the Global Common
area.
implicit shared use
A resource is available for concurrent use by other tasks in a
compatible access mode. Does not guarantee access when
logical I/O is initiated. Resource integrity is automatically
maintained by the system.
job file
A command file designed to run in the batch or interactive
environment.
library file
Object modules or source modules identified by name that are
output to a single file. Modules on library files can be used
separately and repeatedly. For example, object modules can
be retrieved by name during cataloging and inserted with
existing code. The ability to edit the contents of library files
by name is also normally available.
load module file
A file of object code produced by the Cataloger that is ready
to relocate from disc into memory and execute as a process.
Load module files can be activated by name and are
controlled by name or task number.
o
GL-4
Glossary
Glossary
[
logical device I/O
I/O where the physical characteristics of a device are not
determined automatically by the file management system
(device and data formatting are inhibited), allowing the user
to exert control over a particular physical device or device
medium.
logical dismount
The action taken by W.tPX-32 to disassociate a volume from
the requesting task. A TSM logical dismount disassociates
the volume from the requesting context.
logical file code (LFC) User defined 1- to 3-character ASCII codes identifying logical
files within tasks.
(~
logical file I/O
I/O where the physical characteristics of a device and device
medium (device format control, data conversion, data
formatting) are performed automatically for the user so that
he gains a degree of device independence.
logical mount
The action taken by MPX-32 to associate a physically
mounted volume to a task. A TSM logical mount associates
the volume to the TSM context requesting the mount.
logical resource
Any entity existing only because of a mechanism provided by
software. The primary logical resources are: disc volumes,
directories, files, and memory partitions.
map block
A 2048-word unit of memory allocation. In demand page
processing, a page is a map block.
medium (singular)
media (plural
A contiguous source of input or output that is used for a
particular peripheral device. For example, a disc pack is the
medium mounted on a disc drive; a tape is the medium
mounted on a tape drive; paper is the medium used on a
printer; a deck of cards is the medium used on a card reader.
The operating system distinguishes use of media from use of
devices.
memory descriptor
The resource descriptor for a memory partition.
memory partitions
Named areas of physical memory that can be shared by
concurrently executing tasks.
modular
Construction in independent layers. Each higher level layer
builds on the layer beneath it and provides its own standard
interfaces to the levels above and below it.
mounted volume table (MVT)
A system resident table with an entry for each physically
mounted volume. Each entry contains information used by
the system to maintain volume accounting information.
MPX-32 Reference
GL-5
Glossary
multi copied tasks
Tasks with the same name and the same concurrent load
module activity, owned by a single owner or several owners.
This is accomplished by cataloging a task as multicopy. Task
numbers must be used to communicate with multicopied
tasks. See task number.
multiprocessor volume A specially mounted user volume that allows tasks operating
in separate system environments to concurrently access any
volume resource.
multivolume magnetic tape
A set of 1 through 255 maximum physical reels of magnetic
tape processed as a continuous reel.
nonbase mode
Implies the nonbase register instruction set which allows
executable programs of up to 128KW.
nonpublic volume
A volume assigned specifically to the tasks that mount it.
Remains physically mounted until use and assign counts
equal O.
object file
A file of assembled or compiled code that can be cataloged or
linked into a task.
owner
The user who has possession of and can control access to a
file, device, memory partition, or directory. Usually the
owner of a resource is the user who created its resource
descriptor.
owner name
A 1- to 8-character name supplied at logon which remains
unchangeable through logoff. The following characters
cannot be used in owner names: blanks, commas, semicolons,
equal signs, line feeds, dollar signs, percent signs,
exclamation points, and left or right parentheses. All other
characters are valid. Owner names are associated with any
task or process activated on the system and noted by any
process that acts in the owner's behalf. Owner name is also
associated with any resources a user creates unless the user
specifies otherwise. Specifying a different owner when
creating a resource definition does not change the user's
owner name; it only specifies the owner name associated with
the resource.
page
A 512-word unit of memory protection. Also referred to as a
protection granule. Four pages compose a map block.
For demand page processing, a page is a map block brought
into memory and removed from memory during the life of a
demand page task.
page fault
The reference of a page within the logical address space
which is not currently a part of the task's working set.
o
GL·6
Glossary
Glossary
(
(
page in
Bringing into logical memory a page needed to satisfy an
address referenced by a task.
page out
The removal of aged pages from the task's logical address
space.
parameter
A symbolic name in a process or directive file that can be
assigned an argument.
pathname
Variable length ASCII character strings which uniquely
identify a volume resident resource by explicitly or implicitly
describing the volume, one or more directories, and the
resource name.
pathname block
Doubleword bounded variable length ASCII character string
beginning with "!" which uniquely identifies a volume
resident resource by explicitly or implicitly describing the
volume, one or more directories, and the resource name.
permanent files
Files that remain defined on a volume until explicitly deleted.
physical dismount
The action taken by MPX-32 to disassociate a volume from
an assigned mount device and deallocate the device.
physical mount
The action taken by MPX-32 to allocate a mount device and
associate that device to the assigned volume name.
physical resource
Any physical hardware that MPX-32 supports. Tasks access
the resource to perform their functions. The primary physical
resources are: the CPU, computer memory (main storage),
and input/output devices.
portable
Can be used on any compatible device in a single system
configuration. Can also be carried to a compatible device on
a different system hardware configuration. Usually describes a
volume.
post program-controlled interrupt receiver
User supplied end-action receiver entered when a hardware
post program-controlled interrupt is encountered.
process
A body of code scheduled for CPU time as a single entity. A
load module is a process, in load able form, stored on disc.
Same as task.
project group name
A name that is specified at logon and can also be changed.
Identifies a group of users that have a defined set of rights
when they access a resource.
protect
To limit access to a resource. See classes of users.
protection granule
A 512-word unit of memory protection. Also referred to as a
page in a non-demand page context. Four protection granules
compose a map block.
(MPX-32 Reference
GL-7
Glossary
public volume
A volume available for resource assignments by all tasks
activated in the system.
real time task
Synonymous with time critical process.
requestor
The process which requests a function. Each process on a
system has an associated owner name. The system process
that requests a function for a user (e.g., in the interactive
environment) keeps track of the owner name so that the user
thinks of himself as the 'requestor'.
resource
Any source of support that exists external to a task and that
the task needs to perform its function. A resource can be
physical or logical.
~. .
"'L
resource create block (RCB)
Defines access attributes for permanent files, temporary files,
memory partitions, and directories when the particular
resource is created. If not supplied at resource creation,
system default attributes are assumed.
resource descriptor (RD)
Contains access, accounting, and space definition information
pertaining to mounted volume resources, permanent files,
temporary files, directories and partitions.
resource descriptor allocation map (DMAP)
A bit map used for the allocation of resource descriptors on a
voiume.
resource identifier (RID)
The fastest way to locate an already created volume resource.
The RID is in the first eight words of a resource descriptor
and contains the volume address of the resource descriptor,
which points to and describes the resource.
resource logging block (RLB)
A parameter block used as input to the M.LOGR service for
logging resources.
Resource Management Module (H.REMM)
Performs allocation and assignment of all system resources
and maintains access compatibility and usage rights for these
resources. Also contains synchronization mechanisms for
concurrent access to shared resources.
resource requirement summary (RRS)
Defines assignment requirements of a resource. Entries are
variable length. doubleword bounded. There are 9 types of
entries.
GL-8
root directory
The directory of all directories defined on a volume.
SMAP
See file space allocation map.
o
Glossary
Glossary
(
source file
A file of source code to be assembled or compiled into object
code.
static assignment
The association of a logical file code with a system resource
during task activation.
status posting
The process of returning information that indicates whether a
service was completed successfully, with errors, or denied.
swap volume
A volume used as the primary medium for swap file
allocations.
symboJic
A representation of a physical resource, e.g., a name that
represents an entity but is not the entity itself.
synchronous notification
A process waits on further processing until it is notified that
an operation is done or that there is something inhibiting the
operation (e.g., a resource is not available or other processes
are in contention for the resource).
system administrator attribute (SA)
Gives an unprivileged user the ability to execute privileged
SVC's, allows a user to mount public volumes, and allows a
user to change his owner name. A user with the system
administrator attribute is, however, restricted to resource
access limitations imposed by the resource creator.
system directory
Special directory on the system volume which contains
volume resources necessary for system operation.
system volume
A volume containing the system and bootstrap images from
which the current system was IPLed. This volume is
automatically mounted by the SYSINIT task at system
initialization.
task
Synonymous with process.
task name
The name supplied when a task is cataloged or linked.
task number
An 8-digit hexadecimal number assigned to a task by
MPX-32 when the task is activated. The task number is
unique and identifies a particular copy or sharer of a task.
temporary files
Unnamed files that are referenced by resource identifiers.
They are automatically deleted from the system and their
volume space made available when the last task assigned to
them terminates execution.
time critical process
A process which has time constraints. Same as a real time
task.
traverse
To pass through a directory on the way to another directory
or resource.
MPX-32 Reference
GL-9
Glossary
type control parameter block (TCPB)
Set up by the user for sending and receiving messages
to/from the system console.
unformatted media
A medium (magnetic tape, disc pack or floppy disc) that does
not contain valid volume format information, but must be
mounted before initiation of I/O operations.
usage mode
Defines the degree to which multiple tasks can concurrently
allocate a resource. Usage modes are: exclusive use, explicit
shared, and implicit shared.
user
A person who uses a system. Processes and commands that
activate processes are either initiated by a user or initiated on
behalf of a user.
volume
A medium that has a standard format. Disc packs can be
formatted as volumes.
volume assignment table (V AT)
A task resident table with an entry for each non-public
volume currently assigned to the task.
Volume Management Module (H.VOMM)
Manipulates volume resident and related memory resident
structures in order to allow for creation, deletion, and
maintenance of user and system resources which reside on
volumes; for example, provides space management for all
currently mounted volumes in the system.
working set
GL-l0
The pages (map blocks) of a task that are actively being
referenced within a predetermined frame of time.
Glossary
(
Index
- A-
(
(
Abort a Task, (Vl)2-46, (Vl)6-16, (Vl)6-50,
(Vl)7-21, (Vl)7-59, (V2)2-6
Abort Codes, C-l
display description, (V2)1-58
system files, (V3)10-18
Abort Receiver, (Vl)2-34, (Vl)6-166,
(Vl)7-170
Abort Self Service, (Vl)6-17, (Vl)7-22
Abort Specified Task Service, (Vl)6-16,
(Vl)7-21
Abort with Extended Message Service,
(Vl)6-18, (Vl)7-23
ACM/MFP
controller record
defaults, (V3)10-33
syntax, (V3)1O-33
initialization fonnat, (V3)1O-35
set dual-channel mode, (Vl)6-142,
(Vl)7-145
set single-channel mode, (Vl)6-145,
(Vl)7-148
true full-duplex operation, (V3)1O-37
Acquire Current Date(fime in ASCII Fonnat
Service, (Vl)6-138, (Vl)7-139
Acquire Current Date(fime in Binary
Fonnat Service, (Vl)6-20, (Vl)7-25
Acquire Current Date(fime in Byte Binary
Fonnat Service, (Vl)6-15, (Vl)7-20
Acquire System Date(fime in Any Fonnat
Service, (Vl)6-85, (Vl)7-88
ACS
CONCEPT 32/67 usage, (V3)12-2
description, (V3) 12-1
directive summary, (V3)12-5
DUMPACS
description, (V3)12-5
directive summary, (V3)12-5
directives
CHECKSUM, (V3)12-6
COMPARE, (V3)12-6
DUMP, (V3)12-8
EXIT, (V3)12-9
MODE, (V3)12-1O
REVISION, (V3)12-12
errors, (V3)12-16
finn ware file, (V3)12-2
LOADACS
description, (V3) 12-4
directive file (M.ACS), (V3)12-1
MPX-32 Reference
directive summary, (V3)12-5
directives
COPY, (V3)12-7
ENABLE, (V3)12-8
LOAD, (V3)12-9
PATCH, (V3)12-11
VERIFY, (V3) 12-13
errors, (V3)12-14
M.ACS, (V3)12-1
sample file, (V3)12-13
Activate a Task, see Task, execution
Activate Job, (VI )6-226
also see Task, execution
Activate Load Modules, (V3)7-lO, (V3)7-50
Activate Program at Given Time-of-Day
Service, (Vl)6-185, (Vl)7-187
Activate Task Interrupt Service, (VI )6-97,
(Vl)7-101
Activate Task Service, (Vl)6-5, (Vl)7-7
Add
new users to the system, (V3) 10-4
project group names to the system,
(V3)1O-12
Advance Record or File Service, (Vl)6-74,
(Vl)7-9
AIDDB, (Vl)1-16
ALIM
initialization fonnat, (V3) 10-26
tenninal record
defaults, (V3)1O-25
syntax, (V3)10-25
Allocate. resource, (Vl)5-1, (Vl)5-2, (V1)5-3,
(Vl)6-8, (Vl)7-12
Allocate File or Peripheral Device Service,
(Vl)6-222
Allocate File Space Service, (VI )6-206
Allocate Resource Descriptor Service, (Vl)6-208
Allocated Resource Table (ART)
display, (V4 )2-15
specify size, (V3)7 -11
Allocation Unit, (Vl)5-55
Alterable Control Store, see ACS
Analyze, system tables and queues, (V4)2-3
ANSI Labeled Tapes
assign
LFC, (V2)1-38
RRS, (Vl)5-12
dismount, (V2)7-8
display, (V2)7-10, (V2)7-I1
exanaples, (V2)7-6
IN-1
exclude support, (V3)7-40
file records
fixed-length, (V2)7-2
spanned, (V2)7-3
variable-length, (V2)7-3
implementation levels, (V2)7-5
interchange with other systems, (V2)7-4
labels, (V2)7-4
LVID, (V2)7-1
messages, (V2)7-5
mount, (V2)7-9
overview, (V2)7-1
tape drives, (V2)7-3
usage, (V2)7-2
utilities
ADMOUNT, (V2)7-8
AMOUNT, (V2)7-9
ASTAT, (V2)7-10
AVOLM, (V2)7-11
J.LABEL, (V2)7-13, (V3)10-62
VID, (V2)7-2
write header labels, (V2)7-13
Archive, floppy disk, (V4)2-42
Arithmetic Exception Handling, (VI)2-34
Arithmetic Exception Inquiry Service,
(VI)6-182, (VI)7-184
ASCII Date!fime to Binary Conversion,
(Vl)6-28, (VI)7-34
ASCII Decimal to Binary Conversion,
(VI )6-26, (VI)7 -32
ASCII Files, display two, (V4)2-24
ASCII Hex to Binary Conversion,
(VI)6-27, (VI)7-33
ASCII Interchange Code Set, F-I
ASMX32, (Vl)I-17
ASSEMBLE, (VI)I-16
Assembler/X32, (VI)I-17
Assembly Source Code Flowchart Tool
(V4)2-28
'
Assign
arithmetic result to a parameter,
(V2)1-96
integer value to a parameter, (V2)1-96
logical file codes, (V2)1-36
resource, (VI)5-2, (V1)5-3, (V1)6-8,
(Vl)7-12
~tring value to a parameter, (V2)1-94
ASSIgn and Allocate Resource Service,
(VI)6-8, (Vl)7-12
Asynchronous Task Interrupt Service,
(VI)6-10, (Vl)7-14
Automatic Batch Job Submission on
Boot-up, (V4)2-15
Automatic IPL, (V3 )6-4
Automatic Mounting of Public Volumes,
(VI)4-20, (V3)9-11
IN-2
- BBackspace Record or File Service
(Vl)6-11, (VI)7-16
'
Backspace magnetic tape, (V2)3-22
Bad Blocks, (VI)5-64
Base Mode
exclude support, (V3)7-40
nonshared tasks, (VI )2-3
system services, (VI)7-1
Batch Environment
accessing, (V2)1-12
example, (V2)I-109
Batch Job Entry Service, (Vl)6-13, (VI)7-18
Batch Processing
activate job, (VI)6-13, (Vl)7-18
(V2)1-45, (V2)1-59, (V2)1-102,
(V2)2-8
change job priority, (V2)1-103
continuous processing, (V2)2-31,
(V3)7-36
example, (V2)1-I09, (V2)1-110
maximum number of active jobs,
(V3)7-32
overview, (Vl)1-14
specify priority level, (V3)7-11
terminate input stream, (V2)1-106
Batch Stream Memory Pool Interaction,
(V2)1-115
Binary Date!fime to ASCII Conversion
(VI)6-30, (Vl)7-36
'
Binary Date!fime to Byte Binary
Conversion, (Vl)6-33, (Vl)7-39
Binary to ASCII Decimal Conversion,
(Vl)6-29, (Vl)7-35
Binary to ASCII Hexadecimal Conversion,
(Vl)6-31, (VI)7-37
Blocked I/O, (VI)3-4, (Vl)3-15, (VI)5-34
Blocking Buffers, (Vl)3-IS
Boot Block, (Vl)4-22
Booting the System
from Master SDT, (V3)2-12
control switches, (V3)2-21, K-l
from User SDT, (V3)4-4
Bootstrap program, (V3)5-1
Bootstrapping, (V3 )5-1
philosophy, (V3)2-22
Branch
backward, (V2)1-62
conditional, (V2)1-64, (V2)1-66,
(V2)1-69
forward, (V2)1-63
Break Key, (Vl)6-60, (VI)6-65, (VI)7-68,
(V1)7-71, (V2)1-19
Break{fask Interrupt Link/Unlink
Service, (Vl)6-19. (Vl)7-24
Index
(
Building SYSGEN Input File
COMPRESS task, (V3)3-2
directive input file, (V3 )3-1
object input file, (V3)3-1
Byte Binary Daterrime to ASCII
Conversion, (Vl)6-32, (Vl)7-38
Byte Binary Daterrime to Binary
Conversion, (Vl)6-34, (Vl)7-40
-c-
(
(
C.TRACE, (V3)7-64
Caller Notification Packet, see CNP
Carriage Control Characters, L-31
Case Sensitivity, TSM, (V2)1-20
CATALOG
overlays, (Vl)1-16
privilege, (Vl)1-15
COOT array, specify size, (V3)7-12
COT, L-3
Central Processing Unit, see CPU
Change
current working directory, (VI)6-46,
(Vl)7-56, (V2)1-48, (V2)1-104
default system input device, (V2)2-56
default system output device, (V2)2-56
directories, (V2)l-11
key, (V2)1-9
owner attributes, (V3) 10-7
password, (V2)1-lO
project group, (Vl)6-46, (Vl)7-56,
(V2)l-11, (V2)1-48
project group name key, (V3)lO-13
SBO device, (V2)2-37
SLO device, (V2)2-37
tabs, (V4)2-56
task priority, (Vl)6-131, (Vl)7-131
Change Defaults Service, (Vl)6-46, Vl)7-56
Change Priority Level Service, (VI )6-131,
(Vl)7-131
Change Task to Unprivileged Mode Service,
(Vl)6-192, (Vl)7-192
Change Temporary File to Permanent File
Service, (Vl)6-175, (Vl)6-248,
(Vl)7-177
Channel Configuration, (V3)7 -13
Channel Reservation, (Vl)6-153, (Vl)7-156
Channel Reservation Release, (Vl)6-149,
(Vl)7-153
Channel Status, display, (V2)2-46
Check TERMDEF Additions, (V4)2-19
Clear
break receiver, (Vl)6-19, (Vl)7-24
M.KEY file, (V3) 10-9
M.PRJCT file, (V3)lO-14
options, (V2)l-81
TSM directives, (V2)l-49
MPX-32 Reference
Close File Service, (Vl)6-23, (Vl)7-29
Close Resource Service, (Vl)6-21 (Vl)7-27
CNP
'
description, (Vl)5-15
PPCI receiver, (Vl)5-44, (Vl)5-47, L-53
return conventions, (VI )5-16
status posting, (Vl)5-16, (Vl)5-58
structure, L-2
Command Line, (Vl)6-24, (Vl)7-30, (V2)1-85
(V2)1O-1
'
Command Line Recall and Edit
disable, (V2)lO-8
edit, (V2)1O-2
enable, (V2)lO-8
introduction, (V2) 10-1
MPX.PRO file, (V2)lO-6
recall, (V2) 10-4
Common Area, see Memory Partition
Communicating
with another task, (V2)1-14, (V2)2-22,
(V2)2-42
with other terminals, (V2)1-14
Communication
internal, (Vl)1-12
intertask, (Vl)l-ll, (VI)2-22, (V2)2-42
Communications Facilities, (Vl)l-ll
Compare Program Source Files,
(V4)2-25
Compatibility Mode Services
exclude support, (V3)7-40, (V3)7-61
COMPRESS
accessing, (V2)4-1
at SYSGEN, (V3)7-1
description, (V2)4-1, (V3)3-2
error messages, (V2)4-3
example, (V2)4-4
logical file codes, (V2)4-2, (V2)4-3
Compressed Source Format, I-I
CONCEPT/32
interrupts and traps, (Vl)1-5
machine type, (V3)7-34
Conditional Branch, (V2)1-64, (V2)1-66,
(V2)1-69
Conditional Processing, (V2)1-29
Configuration Module, (V4)2-18
Connect Task to Interrupt Level, (V2)2-1O
Connect Task to Interrupt Service, (VI )6-35
•
(Vl)7-41
Console
configuration, (V3 )2-1, (V3)7 -34
device definition, (V3)7-21
Context S witch Timing for M.SURE,
(V4)2-20
Continue Task Execution, (V2)1-20,
(V2)2-11
Control Switches, (V3)2-21, K-l
IN-3
Controller Definition Table (COT), L-3
Controller Status, display, (V2)2-46
Convert
ASCII date/time to binary, (VI)6-28,
(VI)7-34
ASCII decimal to binary, (VI )6-26,
(VI)7-32
ASCII hex to binary, (VI)6-27, (VI)7-33
binary date/time to ASCII, (VI)6-30,
(VI)7-36
binary date/time to byte binary,
(VI)6-33, (VI)7-39
binary to ASCII decimal, (VI)6-29,
(VI)7-35
binary to ASCII hexadecimal, (VI)6-3I,
(VI)7-37
byte binary date/time to ASCII, (VI)6-32,
(VI)7-38
byte binary date/time to binary, (VI)6-34,
(VI)7-40
date and time formats, (VI)7-43
pathname to pathname block, (VI)6-129,
(VI)7-129
Convert ASCII Dateffime to Byte Binary
Format Service, (VI)6-25, (VI)7-31
Convert ASCII Dateffime to Standard
Binary Service, (VI)6-28, (VI)7-34
Convert ASCII Decimal to Binary Service,
(VI)6-26, (VI)7-32
Convert ASCII Hexadecimal to Binary
Service, (VI)6-27, (VI)7-33
Convert Binary Dateffime to ASCII Format
Service, (VI)6-30, (V1)7-36
Convert Binary Dateffime to Byte Binary
Service, (VI)6-33, (VI)7-39
Convert Binary to ASCII Decimal Service,
(VI)6-29, (VI)7-35
Convert Binary to ASCII Hexadecimal
Service, (VI)6-31, (VI)7-37
Convert Byte Binary Dateffime to ASCII
Service, (VI)6-32, (Vl)7-38
Convert Byte Binary Dateffime to Binary
Service, (VI)6-34, (VI)7-40
Convert Pathname to Pathname Block
Service, (VI)6-129, (VI)7-129
Convert System Dateffime Format Service,
(Vl)6-39, (Vl)7-50
Convert Tape to MPX-32 2.x, (V2)3-23
Convert Time Service, (VI)7-43
Copy a File, (V2)3-25
CPU
dispatch queue area, (VI)2-42
execution of IPU tasks, (VI)2-16
scheduling, (VI)1-7, (Vl)2-10
execution priorities, (VI)2-10
real-time priority levels, (VI)2-10
IN-4
state chain management, (VI)2-12
time-distribution priority levels,
(VI)2-11
CPU Execution Time
display, (V2)1-99
for the task, (VI)6-204, (VI)7-206
Crash Codes, (VI)2-51, C-32
Crash Dump Analyzer, (V4)2-3
Create
directory, (VI)4-26, (Vl)6-53,
(VI)7-61, (V2)3-32
FCB, (VI)5-39, (VI)7-45
file, (VI )4-32, (VI )6-37, (VI )6-228,
(VI)7-46, (V2)1-50, (V2)3-34
memory partition, (VI)4-43, (VI)6-108,
(VI)7-111, (V2)3-29
shared image, (VI )4-45
temporary file, (VI)4-41, (VI)6-173,
(VI)6-209, (VI)7-48
timer entry, (Vl)6-159, (VI)7-163
timer table, (V2)2-58
Create Directory Service, (VI)6-53,
(VI)7-61
Create File Control Block Service, (VI)7-45
Create Memory Partition Service,
(VI)6-108, (VI)7-11I
Create Permanent File Service, (VI)6-37,
(VI )6-228, (VI)7-46
Create Temporary File Service, (VI)6-173,
(VI)6-209, (VI)7-48
Create Timer Entry Service, (VI)6-159,
(VI)7-163
CSECT, (VI)2-3, (VI)3-21
Current Working Directory
change, (VI)6-46, (VI)7-56, (V2)1-48,
(V2)1-104
description, (VI )4-6
- 0Datapool, (VI)1-12, (Vl)3-19, (VI)3-20,
(V3)7-39
Datapool Editor, (V1)I-17
Date and Time
conversion
any format, (VI)6-39, (VI)7-43, (VI)7-50
ASCII to binary, (VI)6-28, (VI)7-34
ASCII to byte binary, (VI)6-25,
(VI)7-31
binary to ASCII, (Vl)6-30, (VI)7-36
binary to byte binary, (VI)6-33,
(VI)7-39
byte binary to ASCII, (Vl)6-32,
(VI)7-38
byte binary to binary, (VI)6-34,
(V 1)7-40
display, (V2)2-57
Index
f- '\
\,\._
;I
(
formats, H-I
inquiry
any format, (VI)6-85, (VI)7-84,
(VI)7-88
in ASCII, (VI)6-44, (VI)6-138,
(V1)7-52, (VI)7-139
in binary, (VI)6-20, (VI)7-25
in byte binary, (VI)6-15, (VI)7-20
system update, (V2)2-20
Date and Time Inquiry Service, (VI )6-44,
(VI)7-52
Deallocate File or Peripheral Device Service,
(V 1)6-23 I
Deallocate File Space Service, (VI)6-211
Deallocate Resource Descriptor Service,
(VI)6-212
Deassign and Deallocate Resource Service,
(VI)6-42, (VI)7-53
Debug Link Service, (VI)6-123, (VI)7-207
Debugger
execute, (VI )6-45, (VI)7 -55
system, see System Debugger
task
AIDDB, (VI)I-16
specify default, (V3)7-16
transfer control to, (VI)6-213,
(VI)7-207
unsupported, (V4 )2-44
DEBUGX32, (VI)1-18
Decrease File Size, (V2)3-65
Default
SBO device, (V3)7-45
SID device, (V3)7-51
SLO device, (V3)7 -63
task debugger, (V3)7-16
user directory, (V3) I 0-4
user project group, (V3)10-4
user volume, (V3)10-4
Define FCB Macro, (VI)5-39
Define Parameters, (V2)1-51
Delete
directory, (V2)3-38
file, (Vl)4-41, (Vl)6-232, (V2)1-53,
(V2)3-39
memory partition, (VI)4-44, (VI)6-232,
(V2)3-37
owner from system, (V3)10-9
project group name from system,
(V3)10-13
resources, (VI )6-48, (Vl)7 -57
SBO file, (V2)2-14
SLO file, (V2)2-13
task, (Vl)6-50, (Vl)7-59, (V2)1-20
from dispatch queue, (V2)2-25
timer entry, (VI)6-56, (Vl)7-66
MPX-32 Reference
Delete Permanent File or Non-SYSGEN
Memory Partition Service, (Vl)6-232
Delete Resource Service, (Vl)6-48, (VI)7-57
Delete Task Service, (Vl)6-50, (Vl)7-59
Delete Timer Entry Service, (Vl)6-56,
(Vl)7-66
Deliverable Software for MPX-32, (V3)2-3
Demand Page
define environment, (V3)7-10, (V3)7-12,
(V3)7-17, (V3)7-28
description, (VI )3-17
inhibit support, (V3)7-40
support, (VI)3-17, (V3)7-1O, (V3)7-12
(V3)7-17, (V3)7-28
Demonstration
MPX-32, (V4)1-1
TERMDEF, (V4)2-28, (V4)2-31
TSM scanner, (V4)2-59
Detect File Overlap, (V4)2-27
Device
access, (Vl)5-21, (Vl)5-28, A-I
formatting, (VI)5-47
functions, (Vl)5-41, (Vl)5-44, L-27, L-30
handlers, (V3)7-15
information display, (V4)2-24
inquiry, (Vl)6-246
mnemonics, (Vl)6-52, (VI)7-60, A-6
specification, (Vl)5-28, A-I
status display, (V2)2-46
type codes, (VI)6-52. (Vl)7-60, (V3)7-15,
A-6, L-3, L-77
Device Initializer/Loader, see DEVINITL
Device-Dependent I/O, (VI)5-43
Device-Independent I/O, (Vl)5-1, (Vl)5-32
DEVINITL
activate, (V3)11-6
directive file, (V3)11-1
directive summary, (V3)1l-7
directives
DEV_CNTRL, (V3)11-8
DEVICE, (V3)11-9
IDENT, (V3)11-9
OPTION, (V3)11-1O
REREAD, (V3) 11-11
RETRY, (V3)11-11
WCS_FILE, (V3)1l-12
errors, (V3) 11-13
example, (V3)11-12
firmware file, (V3)11-3
messages, (V3)11-13
Dial-up Port Protection, (V4)2-43
Direct I/O, (Vl)5-34
Directive Files
chaining, (V2)1-27
errors, (V2)1-28. (V2)1-29
examples, (V2)1-111
IN-5
executing tasks, (V2)1-27
macros, (V2)1-30
nesting, (V2)1-28
read from, (V2)1-89
transfer control, (V2)1-46
Directives, read from a file, (V2)1-89
Directory
access attributes, (Vl)3-9
change current working, (Vl)6-46,
(Vl)7-S6, (V2)1-48, (V2)I-I04
create, (VI)4-26, (Vl)6-S3, (V1)7-61,
(V2)3-32
current working, (Vl)4-6
delete, (V2)3-38
description, (VI )4-24
display, (V2)3-44
log information, (Vl)6-103, (VI)7-106
protection, (Vl)4-24, (Vl)4-28
RCB, (Vl)S-62, L-63
root, (Vl)4-6, (Vl)4-26
size allocation, (V2)3-14, (V2)3-IS
structure, (VI)4-6, (VI)4-26
system, (Vl)S-21
usage, (VI )4-28
user default, (V2)1-1l, (V3)10-4
Disable, 10gons, (V2)1-S4
Disable Channel Interrupt (DCI or DI),
(V2)2-IS
Disable Message Task Interrupt Service,
(VI)6-59, (VI)7-67
Disable User Break Interrupt Service,
(VI )6-60, (VI)7 -68
Disconnect Task from Interrupt Level,
(V2)2-15
Disconnect Task from Interrupt Service,
(VI)6-5S, (V1)7-63
Disk Descriptions, (VI )5-27
Disk Device Codes, (V3)7-21
Disk Dump by File, (V4)2-23
Disk Dump by Sector, (V4)2-22
Disk Error History, display, (V4)2-24
Disk Space Usage, (V4)2-26
Disks, device definitions, (V3)7-19
Dismount a Volume, (Vl)4-1S, (Vl)6-57,
(VI)7-64, (V2)1-55, (V2)2-16
Dismount Volume Service, (VI)6-57,
(VI)7-64
Dispatch Queue, (VI )2-42
number of entries, (V3)7-26
Dispatch Queue Entry (DQE), L-5
Display
abort code description, (V2)1-58
active SWAPPER time, (V4)2-53
allocated resource table, (V4)2-1S
ANSI labeled tape information, (V2)7-1O,
(V2)7-11
IN-6
channel status, (V2)2-46
communications region, (V4)2-55
controller status, (V2)2-46
CPU execution time, (V2)1-99
date and time, (V2)2-57
device information, (V4)2-24
device status, (V2)2-46
directories, (V2)3-11, (V2)3-44
disk error history, (V4)2-24
disk space usage, (V4)2-26
file contents, (V2)1-76
file listing, (V2)3-8, (V2)3-9, (V2)3-42,
(V2)3-44, (V2)3-46
GPRs, (Vl)6-61, (Vl)7-69
inswaps, (V4)2-54, (V4)2-55
IPU status, (V2)2-46
IPU traps, (V2)2-26
job accounting file, (V2)1-33, (V2)2-26
job queue, (V2)1-99
load module information, (V4)2-35
logged on users, (V2)1-99, (V2)1-106
MDT, (V4)2-35
memory, (V2)2-46
memory address and contents, (V2)2-4I
memory limits, (VI)6-61, (VI)7-69
memory partitions, (V2)3-12, (V2)3-13,
(V2)3-44
outswaps, (V4)2-54, (V4)2-55
owners and attributes, (V3) 10-9
project group names, (V3)1O-13
PSD, (Vl)6-61, (Vl)7-69
rapid file allocation MDT, (V4)2-35
resources, (V2)3-8, (V2)3-44
saved files, (V2)3-43
shared memory includes, (V4)2-54,
(V4)2-55
system configuration, (V4 )2-18
system dispatch queue, (V2)2-26
system output queues, (V2)2-26
system patch file, (V2)2-26
tabs, (V4)2-56
task exit status, (Vl)7-78
task identification, (VI)6-88, (Vl)7-91
task status, (V2)2-26, (V2)2-46
two ASCII files, (V4)2-24
UDT entry, (V4 )2-60
volume status, (V2)2-46
word locations, (V2)2-18, (V2)2-45
DMAP, (VI)5-51, (V1)6-208, (Vl)6-212
DPEDIT, (Vl)I-17
DQE, L-5
DRAM, (Vl)3-16, (V3)7-52, (V3)7-54, (V3)7-55
DSECT, (Vl)3-21
Dual-Ported Disk
release, (Vl)6-142, (Vl)7-145
reserve, (VI)6-145, (Vl)7-148
Index
c
(
Dump, see Display
Dump Disk File, (V4)2-23
Dump System-Configured Disk, (V4)2-22
DUMPACS, see ACS
Duplicate Floppy Disk, (V4)2-42
Dynamic Memory Allocation, (Vl)1-8,
(Vl)3-19
- E-
(
(
EDIT, (Vl)1-17
Eight-Line Asynch, see ACM
Eight-Line Serial Printer, device definition,
(V3)7-21
Eject/Purge Routine Service, (Vl)6-214,
(Vl)7-208
Enable, logons, (V2)1-57
Enable Channel Interrupt (ECI or EI),
(V2)2-19
Enable Message Task Interrupt Service,
(Vl)6-64, (VI)7-70
Enable User Break Interrupt Service,
(Vl)6-65, (Vl)7-71
End Action Wait Service, (Vl)6-63,
(Vl)7-15
End-Action Receivers, (Vl)2-22
End-of-Job Designation, (V2)1-58
ENTER CR FOR MORE, (V2)1-21, (V2)1-83,
(V3)7-22
Environments, operating, (V2)1-1l,
(V2)1-13
EOF, write, (Vl)6-23, (Vl)6-193, (Vl)6-196,
(Vl)6-197, (Vl)6-214, (Vl)6-215,
(Vl)7-29, (Vl)7-195, (VI)7-198,
(VI)7-199, (VI)7-208, (Vl)7-209
EOF Management, (VI)3-12, (VI)4-49,
(VI )5-36, (VI )5-37
EOM Management, (VI)4-S0, (Vl)S-36,
(Vl)S-37
Erase or Punch Trailer Service, (VI)6-215,
(VI)7-209
Error Codes, unsupported software, (V4)2-60
Establish a Label, (V2)1-52
Exception Handler, (VI)7-158
Exception Return Address, (Vl)7-1S7
Exclude Memory Partition Service, (Vl)6-67
Exclude Shared Image Service, (Vl)7-73
Exclusive File Lock
release, (VI )6-240
set, (VI)6-241
EXCPM, (Vl)S-43, (Vl)5-46
Execute a Task, see Task, execution
Execute Channel Program, (VI)S-48, (Vl)7-26
Execute Channel Program (EXCPM),
(VI)S-43, (Vl)S-46
Execute Channel Program File Control
Block Service, (Vl)7-26
MPX-32 Reference
Execute Channel Program Service,
(Vl)6-216, (Vl)7-210
Exit
J.MDT!, (V2)5-4
message end-action routine, (Vl)6-200,
(Vl)7-202
message receiver, (Vl)6-201, (Vl)7-203
no-wait I/O end-action routine, (Vl)6-199,
(Vl)7-201
OPCOM, (V2)2-22
run receiver, (VI)6-203, (Vl)7-20S
run request end-action routine, (Vl)6-202,
(Vl)7-204
task execution, see Task, execution
TSM, (V2)1-59
VOLMGR, (V2)3-40
Exit from Message End-Action Routine
Service, (V1)6-200, (Vl)7-202
Exit from Message Receiver Service,
(Vl)6-201, (VI)7-203
Exit from Run Request End-Action Routine
Service, (V1)6-202, (Vl)7-204
Exit from Task Interrupt Level Service,
(Vl)6-19, (Vl)6-198, (VI)7-24, (Vl)7-200
Exit Run Receiver Service, (VI)6-203,
(VI)7-20S
Exit With Status Service, (VI)7-78
Expand Task's Logical Address Space,
(V2)1-101
Extend File Service, (VI)6-70, (Vl)7-76
Extended Memory, array, (VI)6-217,
(VI)7-211
Extended MPX-32
aborts and errors, (VI )3-29
CATALOG, (Vl)3-32
create system, (Vl)3-29
description, (VI )3-23
designate location, (VI)3-23
macro assembler, (VI)3-24
move the non-base TSA, (V2)1-60
performance, (Vl)3-23
physical memory, (VI)3-2S
program flow control, (VI )3-27
relocate, (Vl)3-31
resident modules, (Vl)3-26, (V3)2-4
SYSGEN, (VI )3-27, (VI )3-28,
(V3)7-28
task's logical address space, (Vl)3-31
TSM, (VI)3-33, (V2)1-60
Extended TSA, (VI )3-34
Extendibility, (Vl)4-30
-FFast Access, (Vl)3-13, (Vl)4-29
FAT, (VI)S-20, (VI)5-51
Faults, (VI )2-51
IN-7
FCB
create, (VI )5-48, (Vl)7-45
define, (Vl)5-39
description, (Vl)5-2, (Vl)5-38
structure
16-word, L-20
compatible (8-word), L-32
high speed data, L-39
FHDPort
release, (Vl)6-219, (Vl)7-212
reserve, (Vl)6-220, (Vl)7-212
File
access attributes, (VI )3-1 0
access methods, (Vl)4-34
access modes, (Vl)4-36
address inquiry, (Vl)6-234
allocation, (Vl)6-222
append mode, (Vl)4-39
assign temporary, (Vl)4-41, (Vl)5-14
assignment, (Vl)4-29, (Vl)4-33
attachment, (Vl)4-29, (Vl)4-33
attributes, (VI )4-29
backspace, (Vl)6-11, (Vl)7-16
block, (Vl)4-30
blocked I/O, (Vl)3-15
close, (Vl)4-40, (Vl)6-23, (Vl)7-29
contiguous space, (Vl)4-30
copy, (V2)3-25
create permanent, (Vl)4-32, (Vl)6-37,
(Vl)6-228, (Vl)7-46, (V2)1-50, (V2)3-34
create temporary, (Vl)4-41, (Vl)6-173,
(Vl)6-209, (Vl)7-48
deallocate, (Vl)6-231
delete permanent, (VI)4-41, (Vl)6-232.
(V2)1-53, (V2)3-39
delete temporary, (VI)4-42
description, (Vl)4-29
detach permanent, (V 1)4-41
detach temporary, (Vl)4-42
display contents, (V2) 1-76
display listing, (V2)3-42, (V2)3-44,
(V2)3-46
EOF management, (Vl)3-12
extension
automatic, (Vl)3-11, (Vl)4-31
contiguous, (Vl)3-11
manual, (Vl)3-11, (VI)4-31
maximum, (Vl)3-12
minimum, (VI)3-12
fast access, (Vl)3-13, (VI)4-29,
(Vl)4-31
granularity, (Vl)4-30
increase size, (V2)3-41
log information, (Vl)6-103, (Vl)6-244,
(Vl)7-106
management, see File Management
IN·8
modify mode, (VI )4-38
multiprocessor, (Vl)1-9
names, (Vl)4-31
no-save, (Vl)3-14
open permanent, (Vl)4-29, (Vl)4-34,
(Vl)6-236
open temporary, (Vl)4-42
operations, (VI )4-34
permanent, (Vl)1-8, (Vl)4-29, (Vl)4-32
positioning
absolute, (Vl)4-36
relative, (Vl)4-36
print, (V2)1-84
protection, (Vl)1-9, (Vl)4-32
random access, (Vl)I-9, (Vl)4-35
rapid allocation, (V2)5-1
RCB, (Vl)5-59, L-60
read mode, (Vl)4-37
rename, (Vl)6-143, (Vl)7-146, (V2)1-87,
(V2)3-47
replace contents, (Vl)6-144, (Vl)7-147
restore from tape, (V2)3-48, (V2)3-53
rewind, (Vl)6-154, (Vl)7-149
save, (V2)3-54, (V2)3-57
segment definition, (VI )5-55
sequential access, (Vl)4-35
shared, (VI)3-12, (VI)4-40
size allocation, (VI)3-12, (Vl)4-30,
(Vl)4-31, (Vl)5-55, (V2)3-14.
(V2)3-15, (V2)3-65
size extension, (Vl)4-30, (VI)6-70,
(VI)7-76
sort contents. (V2)8-1
space, (Vl)4-30, (Vl)4-31
space allocation, (VI)6-206, (Vl)6-211
system, (VI) 1-9
temporary, (Vl)1-9, (VI)4-29, (VI)4-41,
(Vl)5-14
temporary to permanent, (Vl)4-42,
(Vl)6-175, (Vl)6-248, (Vl)7-177
truncate, (Vl)6-177, (Vl)7-179
types, (Vl)3-14
update mode, (VI )4-39
write mode, (Vl)4-38
zeroing, (VI )3-13
File Assignment Table (FAT), (Vl)5-20,
(Vl)5-51
File Control Block, see FCB
File Management
disk file protection, (Vl)1-9
multiprocessor files, (Vl)1-9
permanent files, (VI) 1-8
random access files, (Vl)I-9
system files, (Vl)1-9
temporary files, (Vl)1-9
File Overlap Detection Utility, (V4)2-27
Index
c
(~
File Pointer Table (FPT), L-46
Firmware
display, (V3)12-5
load (ACS/WCS), (V3)12-4
load (DEVINITL), (V3)11-3
Fixed Head Disk, see FHD
Flag
reset (false), (V2)1-88
set (true), (V2)1-95
Floppy Disk
archive, (V4)2-42
duplication, (V4 )2-42
fonnat, (V4 )2-42
media initialization (J.FORMF),
(V3) 10-42
Fonnat
floppy disk, (V3) I 0-42
memory disk, (V3)10-59
FPT, L-46
Free Dynamic Extended Indexed Data Space
Service, (VI )6-72
Free Dynamic Task Execution Space Service,
(VI)6-73
Free Memory in Byte Increments Service,
(VI)6-111, (VI)7-79
Free Shared Memory Service, (VI)6-233
FSORT2
access, (V2)8-8
directives
field, (V2)8-14
header, (V2)8-13
usage notes, (V2)8-15
examples, (V2)8-12, (V2)8-17
extra memory, (V2)8-7
fannat
blocked, (V2)8-5
direct access blocked, (V2)8-6
direct access unblocked, (V2)8-6
special blocked, (V2)8-6
special unblocked, (V2)8-6
unblocked, (V2)8-6
input data elements, (V2)8-5
introduction, (V2)8-1
logical file codes, (V2)8-1, (V2)8-5
options, (V2)8-7
subroutines
SORT:FLD, (V2)8-11
SORT:HDR, (V2)8-1O
SORT:PAR, (V2)8-9
SORT:X, (V2)8-12
-G -
('
Get Address Limits Service, (VI)6-76,
(Vl)6-77
Get Base Mode Task Address Limits
Service, (VI)7 -103
MPX-32 Reference
Get Command Line Service, (VI)6-24,
(VI)7-30
Get Current Date and Time Service,
(VI)7-84
Get Definition for Tenninal Function
Service, (VI)6-81, (VI)7-81
Get Device Mnemonic or Type Code
Service, (VI)6-52, (VI)7-60
Get Dynamic Extended Data Space
Service, (VI )6-78
Get Dynamic Extended Discontiguous Data
Space Service, (VI )6-79
Get Dynamic Task Execution Space Service,
(VI)6-80
Get Extended Memory Array Service,
(VI)6-217, (VI)7-211
Get Memory in Byte Increments Service,
(VI)6-11O, (Vl)7-83
Get Message Parameters Service, (Vl)6-83,
(VI)7-86
Get Real Physical Address Service,
(VI)6-139, (VI)7-140
Get Run Parameters Service, (VI )6.,.84,
(VI)7-87
Get Shared Memory Service, (VI)6-242
Get Task Environment Service, (VI )6-66,
(VI)7-72
Get Task Number Service, (VI )6-88,
(Vl)6-118, (VI)7-91, (VI)7-120
Get TSA Start Address Service, (VI)6-86,
(VI)7-89
Get User Context Service, (VI)7-80
Global Common, (Vl)l-ll, (Vl)3-19,
(Vl)3-20, (V3)7-39
GPMC Devices, specification, (Vl)5-28
Granularity, (VI)4-30
-HH.ALOC, (VI )5-50
H.BKDM, (Vl)5-34
H.DBUG 1, see System Debugger
H.DBUG2, see System Debugger
H.ICP, (V4)2-32
H.MDT, (V3)7-35
H.MDXIO, (V3)10-58
H.MONS, (Vl)5-49
H.MVMT, (VI)5-22
H.REMM, (Vl)5-1, (VI)5-4, (Vl)5-50
status codes, (VI )5-17
H.REXS, (VI)5-49
H.VOMM, (Vl)5-20, (Vl)5-51
status codes, (VI )5-57
system services, (VI )5-65
Handlers, device, (V3)7-15
Hardware
channel configuration, (V3)7 -13
IN-9
device characteristics, (V3)10-19
disk descriptions, (VI )5-27
I/O device definitions, (V3)7-18
machine type configuration, (V3)7-34
memory disk configuration, (V3)7-13
minimum configuration, (VI)I-22
shadow memory configuration,
-(V3) 10-56
starter system addresses, (V3)2-1
Hardware Interrupts/fraps, (VI)I-5
Hardware Priorities, (VIR-5
HELP, (V2)9-1
Help, online, see Online Help
HELP, VOLMGR, (V2)3-41
Help Files
description, (V2)9-9
oftline, (V2)2-35
online, (V2)2-36
specify location, (V3)7-30
HELPT, (V2)9-1, (V2)9-14
HSD Interface, FCB settings, L-39
-I Identify a Job, (V2)1-72
Implicit Mount Management, (V3)7-13
Include Memory Partition Service, (VI)6-90
Include Shared Image Service, (VI)7-93
Increase File Size, (V2)3-41
Increase Memory Allocation, (V2)1-35
Indicate Object Records, (V2)1-80
Indirectly Connected Interrupt Response
Timing Module, (V4)2-32
Indirectly Connected Task Linkage Block
(ITLB), (V3)7-32
Inhibit
banner page, (V2)2-31, (V3)7-33,
(V3)7-36
demand page, (V3)7-40
mount message, (V2)1-77, (V2)2-31,
(V2)2-33, (V3)7-36
operator intervention, (V2 )2-31 ,
(V3)7-36, (V3)10-44
public volume dismount, (V3)7-13
INIT
description, (V3)10-19
errors, (V3)10-39
LOGONFLE, see LOGONFLE
Initial Program Load (IPL), (V3)6-1
Initialize
ACM, (V3)10-19
ACM/MFP, (V3)10-35
ALIM, (V3)1O-19, (V3)10-26
devices (DEVINITL), (V3)11-1
disks online, (V3)13-20
DP II, (V3)13-12, (V3)13-21
floppy disk, (V3)10-42
IN-10
non-TSM devices, (V3)10-20
SCSI disk, (V3)13-12, (V3)13-23
TSM devices, (V3)10-20
UDP, (V3)13-12, (V3)13-21
Input/Output, see I/O
Input/Output Control System (IOCS), (VI)I-IO,
(VI)5-1, (Vl)5-38
Install
a starter system, (V3)2-1
a user SOT, (V3)4-3
INSTALLSOT, (V3)2-17, (V3)2-18
Instruction Sequence Timing Tool, (V4)2-38
Integers, powers of, E-I
Interactive Environment
accessing, (V2)1-12
sample task, (V2)1-107
priority level, (V3)7-62
Interactive String Search, (V4)2-52
Interactive Task, (V2)1-25
Internal Processing Unit, see IPU
Interrupt Processors, (VI)2-51, (V3)7-46
Interrupt, task, see Task, interrupt
Intertask Communication, (Vl)l-ll, (Vl)2-22,
(Vl)2-23, (VI)6-162, (Vl)7-166
run requests, (Vl)l-ll
user status word, (Vl)6-155, (Vl)6-183,
(Vl)7-159, (Vl)7-185
I/O
blocked, (Vl)5-34
device definitions, (V3)7 -18
device-dependent, (VI )5-43
device-independent, (Vl)l-lO, (Vl)5-1,
(Vl)5-32
direct, (Vl)l-IO, (Vl)5-34
direct channel, (VI)5-43
file access, (V1)I-ll
IOCS, (Vl)l-lO
logical, (Vl)5-1
logical file codes, see LFC
no-wait, (VI )5-33
processing, (Vl)l-lO, (Vl)5-32, (VI)5-38
scheduling, (Vl)2-42
status, (Vl)5-38
terminate in process, (V2)1-19, {V2)1-27
wait, (VI)5-32
IOCS, (Vl)l-lO, (VI)5-1, (Vl)5-38
IOQ Memory Pool, specify size, (V3)7-31
IPL, automatic, (V3 )6-4
IPU
accounting, (VI)2-17
configuration, (V3)7-32
CPU execution of tasks, (Vl)2-16
display status, (V2)2-46
display traps, (V2)2-26
executable system services, (Vl)2-18
base, (V1)7-5
Index
o
nonbase, (Vl)6-3
general description, (Vl)2-15
offiUne, (V2)2-35
online, (V2)2-36
options, (Vl)2-15
priority versus biasing, (Vl)2-17
scheduling, (VI )2-18
set bias, (Vl)6-98, (Vl)7-102
task prioritization
biased, (VI )2-15
nonbiased, (Vl)2-16
task selection, (Vl)2-16
IPU/CPU Scheduler, (VI)2-16
selection, (V3)7 -17
-J J.DSCMP
description, (V3)14-1
disk status report, (V3)14-3
error messages, (V3) 14-6
logical file codes, (V3)14-2
performance, (V3)14-2
segment report, (V3)14-3, (V3)14-4
usage, (V3)14-3
J.DTSAYE, (V3)7-27, (V3)1O-44
J.FORMF, (V3)1O-42
J.lll-P, (V2)9-1, (V3)7-30
J.INIT
conventions, (V3)9-2
dedicated names, (V3)9-2
directive summary, (V3)9-3
directives
Change Contents of
Memory Location, (V3)9-3
Comments, (V3)9-8
Conditional, (V3)9-6
Define Base Address, (V3)9-3
Define Named Value, (V3)9-4
Define Patch Area, (V3)9-6
Enter Value into Patch Area, (V3)9-7
Exit, (V3 )9-4
Go to Patch Area, (V3)9-5
Return from Patch Area, (V3 )9-6
Select Patch Options, (V3)9-5
entry conditions, (V3)9-8
examples, (V3)9-1O
exit conditions, (V3 )9-8
external references, (V3 )9-9
Untroduction, (V3 )9-1
J.LABEL, (V3)1O-62
J.MDREST, (V3)1O-58, (V3)10-61
J .MDSAYE, (V3) 10-58, (V3) 10-60
J.MDTI
access, (V2)5-2
contents, (V2)5-1
description, (V2)5-1
MPX-32 Reference
errors, (V2)5-8
examples, (V2)5-6
exit, (V2)5-4
input files, (V2)5-4
logical file codes, (V2)5-3, (V2)5-4
programming considerations, (V2)5-7
J.MOUNT, (Vl)l-13
J.SHAD
accessing, (V2)6-1
directives
EXIT, (V2)6-3
SHADOW, (V2)6-3
errors, (V2)6-4
examples, (V2)6-5
introduction, (V2)6-1
logical file codes, (V2)6-2
J.SHUTD
error messages, (V3)1O-48
using, (V3)1O-45
J.TDEFI Program, (V2)11-4
J.TSET Utility. (V2)11-21
J.UNLOCK, (V2)2-58, (V3)1O-53
J.VFMT, (Vl)I-17, (V3)13-1
access, (V3)13-4
CONFIRM option, (V3)13-4
directive syntax, (V3)13-3
directives
COPY, (V3)13-5
EDITFMAP, (V3)13-7
EXIT, (V3)13-9
FORMAT, (V3)13-9
INITIALIZE, (V3)13-12
NEWBOOT, (V3)13-16
REPLACE, (V3) 13-17
errors, (V3)13-18
examples, (V3)13-18
introduction, (V3) 13-1
logical file codes, (V3)13-1
media management, see Media
Management
usage, (V3)13-2
JCL
conditional processing, (V2)1-29
directive files, (V2) 1-27
directive summary, (V2)1-2
directive syntax, (V2)1-33
directives, see TSM, directives
introduction, (V2) 1-1
macro looping, (V2) 1-29
parameter passing, (V2)1-29
parameter replacement, (V2)1-30
spooled input control, (V2)1-30
Job Accounting File, display, (V2)1-33,
(V2)2-26
Job Accounting Program (M.ACCNT),
(V3)10-15
IN-11
Job Activation, (Vl)6-226
also see Task, execution
Job Control Language, see JCL
Job Identification, (V2) 1-72
Job Number, (V2)2-5
Job Processing
data flow, (V2)1-31
terminating conditions, (V2)1-32
Job Queue, display, (V2)1-99
-KKey, (V2)1-9, (V3)l0-4
KEY, (VI)1-20, (V3)lO-2
directive summary, (V3) 10-4
directives
ADD, (V3)1O-4
CHANGE, (V3)1O-7
DEFAULTS, (V3)1O-8
DELETE, (V3)1O-9
LOG, (V3) 10-9
NEWFILE, (V3) 10-9
X, (V3)1O-1O
examples, (V3)lO-10
M.KEY file, (V3)1O-3
usage, (V3)1O-3
KEYWORD Task, (V2)1-9
Kill a Task, (V2)2-25
-l Label, establish, (V2)1-52
Label ANSI Tape Utility (J.LABEL),
(V3)lO-62
Large Buffers, (Vl)3-15
Laser Printer Utility, (V4)2-34
LFC
assignments, (V2)1-21, (V2) 1-36
in FCB, (Vl)5-38
overview, (Vl)5-2
UBED, (Vl)l-17
Libraries
scientific subroutine, (VI) 1-21
subroutine, (VI)1-21
system macro, (Vl)l-21
user group, (VI)I-21
Linker/X32, (Vl)I-18
UNKX32, (VI)I-18
List, see Display
LMIT, (Vl)2-7
Load and Execute Interactive Debugger
Service, (Vl)6-45, (VI)7-55
Load Module Information, (V4)2-35
Load Module Information Table (LMIT),
(Vl)2-7
Load Overlay Segment Service, (Vl)6-121
Load Shared Image into Memory, (V2)2-24
IN·12
LOADACS, see ACS
Log Contents of Rapid File Allocation MDT
(V4)2-35
'
Log Off the System, (V2)1-14, (V2)1-59
Log On the System, (V2)1-8
multiple logons, (V2)1-8, (V3)7-33
Log Resource or Directory Service,
(Vl)6-103, (V1)7-106
Logged on Users, display, (V2)1-106
Logical Address
task boundaries, (VI)6-76, (Vl)6-77
verify, (Vl)6-194, (Vl)7-196
Log~cal Channel Program, (Vl)5-43, (Vl)5-44
LogICal Dismount, (Vl)4-18
Logical File Codes, see LFC
Logical I/O, (VI)5-1
Logical Mount, (VI)4-18
Logoff, remote terminal, (V4)2-37
Logon
disable, (V2)1-54
enable, (V2)1-57
multiple, (V2)1-8, (V3)7-33
SYSTEM, (V3)7-33, (V3)7-61
Logon Attempt Counter, (V3)1O-22
Logon Timeout Counter, (V3)1O-23
LOGONFLE, (V2)11-17, (V3)IO-20
format, (V3)lO-20
sample, (V3)10-38
security counters, (V3) 10-22
security examples, (V3)10-24
- MM.ACCNT File, (V3)1O-11, (V3)1O-15
delete contents, (V2)2-37
M.ACS, see ACS
M.ACTV, (VI)2-7, (Vl)6-5
M.ADRS, (VI )6-6
M.ALOC, (VI )6-222
M.ANYW, (Vl)2-25, (Vl)6-7
M.ASSN, (Vl)6-8
M.ASYNCH, (VI)6-10
M.BACK, (VI)6-11
M.BATCH, (VI)6-13, (V4)2-17
M.BBTIM, (Vl)6-15
M.BORT, (VI)2-46, (VI)6-16
M.BRK, (VI)2-21, (Vl)6-19
M.BRKXIT, (VI)2-21, (Vl)6-19
M.BTIM, (Vl)6-20
M.CDJS, (Vl)6-226
M.CLOSER, (Vl)6-21
M.CLSE, (VI)6-23
M.CMD, (V1)6-24
M.CNTRL File, (V3)1O-17
M.CONABB, (VI)6-25
M.CONADB, (VI)6-26
M.CONAHB, (VI)6-27
Index
(
M.CONASB, (Vl)6-28
M.CONBAD, (VI )6-29
M.CONBAF, (Vl)6-30
M.CONBAH, (Vl)6-31
M.CONBBA, (Vl)6-32
M.CONBBY, (Vl)6-33
M.CONBYB, (Vl)6-34
M.CONN, (Vl)6-35
M.CPERM, (Vl)6-37
M.CREATE, (VI)6-228
M.CTIM, (Vl)6-39
M.CWAT, (Vl)6-41
M.DALC, (VI )6-231
M.DASN, (Vl)6-42
M.DATE, (VI )6-44
M.DEBUG, (Vl)6-45
M.DEFT, (Vl)6-46
M.DELETE, (Vl)6-232
M.DELR, (Vl)6-48
M.DELTSK, (Vl)2-46, (VI)6-50
M.DEVID, (Vl)6-52
M.DIR, (VI)6-53
M.DISCON, (Vl)6-55
M.DLTT, (VI )6-56
M.DMOUNT, (Vl)6-57
M.DSMI, (VI )6-59
M.DSUB, (VI )6-60
M.DUMP, (Vl)6-61
M.EAWAIT, (VI)2-25, (Vl)6-63
M.ENMI, (Vl)6-64
M.ENUB, (Vl)6-65
M.ENVRMT, (Vl)6-66
M.ERR File, (V3)10-18
M.EXCL, (Vl)6-233
M.EXCLUDE, (Vl)3-20, (Vl)6-67
M.EXIT, (Vl)2-24, (Vl)2-46, (Vl)6-69
M.EXTD, (Vl)6-70
M.FADD, (Vl)6-234
M.FD, (VI)2-43, (Vl)3-19, (Vl)6-72
M.FE, (Vl)2-43, (Vl)3-19, (Vl)6-73
M.FILE, (VI )6-236
M.FSLR, (Vl)6-237
M.FSLS, (VI )6-238
M.FWRD, (Vl)6-74
M.FXLR, (VI )6-240
M.FXLS, (VI)6-241
M.GADRL, (Vl)6-76
M.GADRL2, (VI )6-77
M.GD, (VI)2-43, (VI)3-I9, (Vl)6-78,
M.GDD, (VI )6-79
M.GE, (VI)2-43, (VI)3-I9, (Vl)6-80
M.GETDEF, (Vl)6-81, (V2)1l-18
errors, (V2)1l-19
.
M.GMSGP, (Vl)2-22, (Vl)2-24, (Vl)6-83
M.GRUNP, (Vl)2-22, (Vl)2-24, (VI)6-84
M.GTIM, (Vl)6-85
MPX·32 Reference
M.GTSAD, (VI )6-86
M.HOLD, (VI)6-87
M.lD, (VI)6-88
M.INCL, (VI)6-242
M.INCLUDE, (VI)3-20, (VI)6-90
M.INQUIRY, (VI)6-93
M.INT, (VI)6-97
M.IPUBS, (VI)6-98
M.KEY Editor, see KEY
M.KEY File, (Vl)4-13, (V3)1O-3
M.LOC, (Vl)6-99
M.LOCK, (Vl)6-101
M.LOG, (Vl)6-244
M.LOGR, (Vl)6-103
M.MACLIB, (VI)1-21
M.MEM, (VI )6-1 08
M.MEMB, (Vl)2-43, (Vl)3-19, (Vl)6-11O
M.MEMFRE, (Vl)2-43, (Vl)3-19, (Vl)6-111
M.MOD, (Vl)6-112
M.MODU, (Vl)6-114
M.MOUNT, (Vl)6-115
M.MOUNT File, (V3)1O-43
M.MOVE, (Vl)6-117
M.MPXMAC, (Vl)1-21
M.MYID, (Vl)6-118
M.NEWRRS, (Vl)6-119
M.OLAY, (Vl)6-121
M.OPENR, (Vl)6-122
M.OSREAD, (Vl)6-124
M.OSWRIT, (Vl)6-125
M.PDEV, (Vl)6-246
M.PERM, (Vl)6-248
M.PGOD, (Vl)6-126
M.PGOW, (Vl)6-127
M.PNAM, (Vl)6-128
M.PNAMB, (Vl)6-129
M.PRIL, (VI )6-131
M.PRIV, (Vl)6-132
M.PRJCT File, (V3)1O-11
M.PTSK, (Vl)2-7, (Vl)6-133
M.QATIM, (Vl)6-138
M.RADDR, (Vl)6-139
M.RCVR, (Vl)2-22, (Vl)2-23, (V1)6-140
M.READ, (Vl)6-141
M.RELP, (Vl)6-142
M.RENAM, (Vl)6-143
M.REPLAC, (Vl)6-144
M.RESP, (Vl)6-145
M.REWRIT, (Vl)6-146
M.REWRTU, (Vl)6-147
M.ROPL, (Vl)6-148
M.RRES, (Vl)6-149
M.RSML, (VI )6-150
M.RSRV, (Vl)6-153
M.RWND, (Vl)6-154
M.SETS, (Vl)6-155
IN-13
M.SETSYNC, (VI)6-157
M.SETT, (VI)6-159
M.SHARE, (VI )6-250
M.SMSGR, (VI)2-25, (VI)6-162
M.SMULK, (VI)6-252
M.SOPL, (VI)6-163
M.SRUNR, (VI)2-26, (VI)6-164
M.SUAR, (VI)2-34, (VI)6-166
M.SUME, (Vl)6-167
M.SURE, (VI)6-168
context switch timing, (V4)2-20
M.SUSP, (Vl)2-25, (Vl)6-169
M.SYNCH, (Vl)6-170
M.TBRKON, (Vl)6-171
M.TDAY, (Vl)6-172
M.TEMP, (Vl)6-173
M.TEMPER, (Vl)6-175
M.TRNC, (Vl)6-177
M.TSCAN, (Vl)6-178
M.TSMPC, (Vl)6-179
M.TSTE, (VI)6-182
M.TSTS, (Vl)6-183
M.TSTT, (Vl)6-184
M.TURNON, (Vl)6-185
M.TYPE, (Vl)6-187
M.UNLOCK, (Vl)6-188
M.UNSYNC, (Vl)6-190
M.UPRIV, (Vl)6-192
M.UPSP, (Vl)6-193
M.USER, (Vl)6-253
M.VADDR, (Vl)6-194
M.WAIT, (Vl)6-195
M.WEOF, (Vl)6-196
M.WRIT, (Vl)6-197
M.xBRKR, (Vl)6-198
M.xIEA! (Vl)2-22, (VI)6-199
M.xMEA, (Vl)2-22, (Vl)2-26, (Vl)6-200
M.xMSGR, (VI)2-22, (Vl)2-24, (Vl)6-201
M.xREA, (Vl)2-22, (Vl)2-26, (Vl)6-202
M.xRUNR, (Vl)2-22, (Vl)2-24, (V1)6-203
M.xTIME, (VI )6-204
M_ACTV, (VI)7-7
M_ADRS, (Vl)7-8
M_ADVANCE, (Vl)7-9
M_ANYWAIT, (Vl)7-11
M_ASSIGN, (VI)7-12
M_ASYNCH, (Vl)7-14
M_AWAITACTION, (Vl)7-15
M_BACKSPACE, (Vl)7-I6
M_BATCH, (VI)7 -18
M_BBTIM, (Vl)7 -20
M_BORT, (VI)7-21
M_BRK, (Vl)7-24
M_BRKXIT, (Vl)7-24
M_BTIM, (Vl)7-25
M_CHANPROGFCB, (Vl)7-26
IN-14
M_CLOSER, (VI)7-27
M_CLSE, (VI)7-29
M_CMD, (Vl)7-30
M_CONABB, (Vl)7-31
M_CONADB, (VI)7-32
M_CONAHB, (VI)7-33
M_CONASB, (VI)7-34
M_CONBAD, (VI)7-35
M_CONBAF, (Vl)7-36
M_CONBAH, (Vl)7-37
M_CONBBA, (Vl)7-38
M_CONBBY, (Vl)7-39
M_CONBYB, (VI)7-40
M_CONN, (Vl)7-41
M_CONSTRUCTPATH, (Vl)7-42
M_CONVERTTIME, (Vl)7-43
M_CREATEFCB, (Vl)7-45
M_CREATEP, (Vl)7-46
M_CREATET, (Vl)7-48
M_CTIM, (Vl)7-50
M_CWAT, (Vl)7-51
M_DATE, (Vl)7 -52
M_DEASSIGN, (VI)7-53
M_DEBUG, (Vl)7-55
M_DEFT, (Vl)7-56
M_DELETER, (VI)7 -57
M_DELTSK, (Vl)7-59
M_DEVIO, (VI)7-60
M_DIR, (Vl)7-61
M_DISCON, (V1)7-63
M_DISMOUNT, (Vl)7-64
M_DLTT, (VI)7-66
M_DSMI, (VI)7 -67
M_DSUB, (Vl)7-68
M_DUMP, (Vl)7-69
M_ENMI, (Vl)7-70
M_ENUB, (Vl)7-71
M_ENVRMT, (Vl)7-72
M_EXCLUDE, (Vl)7-73
M_EXIT, (Vl)2-46, (Vl)7-75
M_EXTENDFILE, (VI)7-76
M_EXTSTS, (Vl)7-78
M_FREEMEMBYTES, (Vl)7-79
M_GETCTX, (VI)7 -80
M_GETDEF, (Vl)7-81
M_GETMEMBYTES, (Vl)7-83
M_GETTlME, (VI)7-84
M_GMSGP, (Vl)7-86
M_GRUNP, (Vl)7-87
M_GTIM, (Vl)7-88
M_GTSAD, (VI)7-89
M_HOLD, (VI)7-90
M_ID, (Vl)7-91
M_INCLUDE, (Vl)7-93
M_INQUIRER, (Vl)7-96
M_INT, (Vl)7-101
c
Index
(
M_IPUBS, (V1)7-102
M_LIMITS, (V1)7-103
M_LOCK, (V1)7-104
M_LOGR, (V1)7-106
M_.MEM, (V1)7-111
M_MOD, (V1)7-113
M_MODU, (Vl)7-115
M_MOUNT, (V1)7-116
M_MOVE, (V1)7-118
M_MYID, (V1)7-120
M_OPENR, (Vl)7-121
M_OPTIONDWORD, (V1)7-124
M_OPTIONWORD, (V1)7-125
M_OSREAD, (Vl)7-126
M_OSWRIT, (Vl)7-127
M_PNAMB, (V1)7-129
M_PRIL, (V1)7 -131
M_PRIVMODE, (V1)7-132
M_PTSK, (V1)7-133
M_PUTCTX, (Vl)7-138
M_QATIM, (Vl)7-139
M_RADDR, (V1)7-140
M_RCVR, (V1)7 -141
M_READ, (Vl)7-142
M_READD, (Vl)7-144
M_RELP, (V1)7-145
M_RENAME, (Vl)7-146
M_REPLACE, (Vl)7-147
M_RESP, (VI)7-148
M_REWIND, (V1)7-149
M_REWRIT, (Vl)7-150
M_REWRTU, (Vl)7-151
M_ROPL, (Vl)7-152
M_RRES, (Vl)7-153
M_RSML, (Vl)7-154
M_RSMU, (Vl)7-155
M_RSRV, (Vl)7-156
M_SETERA, (Vl)2-37, (Vl)7-157
M_SETEXA, (Vl)2-37, (Vl)7-158
M_SETS, (V1)7-159
M_SETSYNC, (Vl)7-161
M_SETT, (V1)7-163
M_SMSGR, (VI)7-166
M_SOPL, (Vl)7-167
M_SRUNR, (Vl)7-168
M_SUAR, (Vl)7-170
M_SU.ME, (VI)7-l7l
M_SURE, (VI)7-172
M_SUSP, (Vl)7-173
M_SYNCH, (Vl)7-174
M_TBRKON, (Vl)7-175
M_TDAY, (Vl)7-176
M_TEMPFILETOPERM, (VI)7 -177
M_TRUNCATE, (V1)7-179
M_TSCAN, (V1)7 -180
M_TSMPC, (Vl)7-181
MPX·32 Reference
M_TSTE, (Vl)7 -184
M_TSTS, (Vl)7-185
M_TSTT, (VI)7-186
M_TURNON, (Vl)7-187
M_TYPE, (Vl)7-189
M_UNLOCK, (Vl)7-190
M_UNPRIVMODE, (Vl)7-192
M_UNSYNC, (Vl)7-193
M_UPSP, (Vl)7-195
M_VADDR, (Vl)7-196
M_WAIT, (Vl)7-197
M_WRITE, (Vl)7 -198
M_WRITEEOF, (Vl)7-199
M_XBRKR, (VI)7 -200
M_XIEA, (VI)7-201
M_XMEA, (Vl)7-202
M_XMSGR, (VI)7 -203
M_XREA, (VI)7-204
M_XRUNR, (VI)7 -205
M_XTIME, (Vl)7-206
Machine Type, (V3)2-27, (V3)7-34
MACLIBR, (Vl)I-16
Macro Assembler, (VI)1-16
Macro Directive Files, (V2)1-30
Macro Librarian/X32, (VI)l-17
Macro Libraries, (VI)1-21
Macro Library Editor, (Vl)1-16
Macro Looping, (V2)1-29
MACX32, (VI)1-17
Magnetic Tape
advance, (VI)6-74, (VI)7-9, (V2)3-64,
(V2)3-65
backspace, (V2)3-22
convert, (V2)3-23
multivolume
description, (VI )5-22
write EOF, (Vl)6-193, (Vl)6-196,
(Vl)6-197, (Vl)6-214, (Vl)6-215,
(V1)7-195, (Vl)7-198, (Vl)7-199,
(Vl)7-208, (Vl)7-209
write volume record, (Vl)6-193, (Vl)6-196,
(Vl)6-197, (V1)6-214, (Vl)6-215,
(VI)7-195, (Vl)7-198, (Vl)7-199,
(VI)7-208, (VI)7-209
restore files, (V2)3-48, (V2)3-53
rewind, (V2)3-53
Map Block, (VI)3-16
address assignments, J-l
Mapped Out, (Vl)3-37
Mapped Programming Executive, see MPX-32
Master System Distribution Tape. see SDT
MDT, (V3)7-35
.MEDIA, (Vl)1-19
Media, unformatted, (V1)5-25
Media Conversion, (Vl)1-19
Media Flaw Data. (V3)13-21
IN·15
Media Flaw Map, (V3)13-23
Media Management
during SDT boot, (V3)13-22
edit media flaw data, (V3)13-21
EDITFMAP directive, (V3)13-7
INITIALIZE directive, (V3)13-12
initialize media, (V3)13-20
media flaw map, (V3)13-23
SCSI disks, (V3)13-23
terDlinolo!r.Y, (V3)13-19
Memory
deallocate, (Vl)6-111, (Vl)7-79
display, (V2)2-46
physical read, (Vl)6-124, (VI)7-126
physical write, (Vl)6-125, (Vl)7-127
search, (V2)2-41
shadow, (V2)1-98, (V3)10-54
Memory Address
display, (V2)2-41
get physical, (VI)6-139, (Vl)7-140
inquiry, (VI )6-6, (Vl)7-8
Memory Address Inquiry Service, (VI )6-6,
(Vl)7-8
Memory Allocation
blocked I/O, (VI)3-15
deallocate map block, (Vl)6-72,
(VI)6-73
demand page, (VI)3-17
dynamic, (Vl)I-8, (VI)3-19
expand, (VI)6-80, (VI)6-110, (VI)7-83
extended area, (Vl)6-78, (Vl)6-79
extended data space, (VI )3-20
increase, (V2)1-35
map block, (VI )3-16
MPX-32, (V1)3-15
static, (Vl)3-18
task, (Vl)3-16
Memory Classes, (VI)3-16, (V3)10-56
Memory Disk
abort cases, (V3)10-59
access, (V3)1O-59
configuration, (V3)7-13, (V3)1O-59
dismount, (V3)10-59
errors, (V3)1O-60
format, (V3)10-59
mount, (V3) I 0-59
overview, (V3)1O-58
restore task (J.MDREST), (V3)1O-61
save task (J.MDSAVE), (V3)1O-60
usage, (V3)1O-59
Memory Dump Request Service, (V1)6-61,
(Vl}7-69
Memory Partition, (VI )3-20
access, (VI )4-44
access attributes, (Vl)3-10
attach, (VI )4-44
IN·16
create, (Vl)4-43, (Vl)6-108, (Vl)6-250,
(Vl)7-111, (V2)3-29
Datapool, see Datapool
define static, (V3)7 -39
delete, (VI)4-44, (VI)6-232, (V2)3-37
detach, (VI)4-44
display, (V2)3-44
dynamic, (Vl)3-18
exclude, (VI )6-67
extended common, (VI )3-19
global common, see Global Common
include, (Vl)6-90, (Vl)6-242
nonbase addressing, (VI )4-43
protection, (Vl)3-10, (VI)3-20,
(VI)4-43
RCB, (Vl)5-63, L-64
share, (Vl)4-45
static, (Vl)3-18
unlock, (Vl)6-252
Memory Pool, (V2)1-1l5
IOQ size, (V3)7-31
MSG size, (V3)7-38
size, (V3)7-46
system, (VI )3-15
Memory Pool Monitor, (V4)2-42
Memory Resident Descriptor Table (MDT),
(V2)5-1, (V2)5-7, (V3)7-35
Memory Size, (V3)7-51
Memory Types, (VI)3-16, (V3)1O-56
Memory Word, reset, (V2)2-32
Message
end-action processing, (Vl)2-26
inhibit batch, (V3)7-11
maximum no-wait, (V3)7-36
receive from other tasks, (V1)2-23,
(VI)6-140, (Vl)7-141
send to console, (Vl)6-187, (VI)7-189,
(V3)7-11
send to task, (Vl)2-25, (Vl)6-162,
(Vl)7 -166, (V2)2-42
send to terminal, (V2)1-80, (V2)1-101,
(V3)7-II
system files, (V3)1O-18
Message End-Action Routine Exit,
(Vl)6-200, (VI)7-202
Message Parameters, (VI )2-24, (VI )6-83,
(Vl)7-86
Message Receiver
establish, (VI )2-23
exit, (Vl)2-24, (VI)6-201, (VI)7-203
Minimum Hardware Configuration, (Vl)1-22
Modify
page size, (V2)1-83, (V3)7-21
screen width, (V2)1-75, (V3)7-21
Modify Descriptor Service, (Vl)6-112,
(Vl)7-113
Index
!".~.
\"
--
./
'· .
C
.
.
(
(
Modify Descriptor User Area
Service, (VI )6-114, (V1)7 -115
Modify Swap Parameters, (V4)2-53
Mount
memory disk, (V3)1O-59
multiprocessor volume, (VI )4-49
public volume, (V3 )9-11
volume, (V1)4-49, (V1)6-115, (V1)7-116,
(V2)1-77, (V2)2-33
volume (M.MOUNT), (V3)10-43
Mount Volume Service, (V1)6-115, (VI)7-I16
Move Data to User Address Service,
(V1)6-1l7, (V1)7-118
Move Non-base TSA, (V1)3-28, (V1)3-32,
(V2)1-60
MPX-32
batch processing, (V1)1-14
build, (V3)1-l, (V3)3-1
command processors, (V1)1-3
communications facilities, (VI) I-II
CPU scheduling, (V1)1-7
data transfers between revisions,
(V1)5-22
delimiters, (V2)1-26
deliverable software, (V3)2-3
demonstration package, (V4) 1-4
extended, see Extended MPX-32
features, (V1)1-3
file management, (V1)1-8
input/output operations, (VI) I-I 0
installation, (V3 )2-1
introduction, (V1)1-1
maintenance, (V3) I-I
mapped in, (V2)1-79
mapped out, (VI)3-37, (V2)1-76
memory allocation, (VI)I-8, (VI)3-15
priority levels, (VI) 1-7
recovery, (V3 )6-1
restart, (V3)5-1
shutdown, (V3)10-45
software intenupt system, (V1)1-7
system administration, (VI )4-13, (V3) I 0-1
system description, (VI) 1-1
system services, (Vl)l-1O, (VI)6-1,
(V1)7-1
test, (V3 )3-1
time management, (Vl)1-12
timer scheduler, (V1)1-12
trap processors, (Vl)l-12
utilities, see Utilities
MPX.PRO
customizing, (V2)1O-7
description, (V2)1O-6
errors, (V2) 10-9
predefined functions, (V2)1O-6
sample file, (V2)1O-1O
MPX·32 Reference
TSM special keys, (V2)1-15
MPXDEMO, (V4)1-4
MSG Memory Pool, specify size, (V3)7-38
Multicopied Tasks, (V1)2-3
Multiprocessor, recovery, (V2)2-58, (V3)1O-53
Multiprocessor Lock, (VI)4-47
Multiprocessor Recovery Task (J.UNLOCK),
(V3)1O-53
Multiprocessor Resource, (VI)4-47, (V1)4-51,
(V3)7-27
Multiprocessor Shared Memory, (VI)3-22,
(V3)7-52, (V3)7-55
Multiprocessor Shared Volume, (VI)4-47,
(VI)4-49
Multiprocessor User Volume, (VI)4-16
MVT, (VI )5-51
- NNo-Wait I/O, (VI)5-33
No-Wait I/O End-Action Return Service,
(Vl)6-199, (Vl)7-201
No-Wait I/O Requests, maximum number,
(V3n~6
.
No-Wait Messages, maximum number, (V3)7-36
No-Wait Run Requests, maximum number,
(V3)7-38
Nonpublic Volume, (Vl)4-16
NULL Device, specification, (Vl)5-28, (V3)7-25
Numerical Information, D-1
- 0Object Librarian/X32, (VI) 1-18
Object Records, indicate. (V2)I-80
OBJX32, (V1)1-I8
Offline
device, (V2)2-35
help files, (V2)2-35
IPU, (V2)2-35
Online
device, (V2)2-36
help files, (V2)2-36
IPU, (V2)2-36
Online Disk Media Management, (V3)13-19
also see Media Management
Online Help
access, (V2)9-3
choices within, (V2)9-5
components, (V2)9-I
description, (V2)9-1
display sample, (V2)9-2
errors, (V2)9-15
help files
description, (V2)9-9
offline, (V2)2-35
online, (V2)2-36
IN-17
specify location, (V3)7-24
translate, (V2)9-14
help key, (V2)9-3
HELPT, (V2)9-1, (V2)9-14
J.HLP, (V3)7-30
keywords, (V2)9-2, (V2)9-12
modify information, (V2)9-8
print help screen, (V2)9-6
sample
display, (V2)9-2
topic entry, (V2)9-11
topic entries, (V2)9-2, (V2)9-10
translate files, (V2)9-14
Online Restart, (V3 )5-1
Online System Patch Facility, see J .!NIT
OPCOM, (Vl)I-14, (V2)2-1
activate, (V2)2-3
batch jobs, (V2)2-5
directive abort, (V2)2-6
directive summary, (V2)2-1
directive syntax, (V2)2-5
directives
ABORT, (V2)2-6
ACTNATE, (V2)2-7
BATCH, (V2)2-8
BREAK, (V2)2-9
CONNECT, (V2)2-1O
CONTINUE, (V2)2-11
DEBUG, (V2)2-12
DELETETIMER, (V2)2-12
DEPRINT, (V2)2-13
DEPUNCH, (V2)2-14
DISABLE, (V2)2-15
DISCONNECT, (V2)2-15
DISMOUNT, (V2)2-16
DUMP, (V2)2-18
ENABLE, (V2)2-19
ENTER, (V2)2-20
ESTABLISH, (V2)2-21
EXCLUDE, (V2)2-22
EXIT, (V2)2-22
HOLD, (V2)2-23
INCLUDE, (V2)2-24
KILL, (V2)2-25
LIST, (V2)2-26
MODE, (V2)2-31
MODIFY, (V2)2-32
MOUNT, (V2)2-33
OFFLINE, (V2)2-35
ONLINE, (V2)2-36
PURGEAC, (V2)2-37
REDIRECT, (V2)2-37
REPRINT, (V2)2-38
REPUNCH, (V2)2-39
REQUEST, (V2)2-40
RESUME, (V2)2-40
IN-18
SEARCH, (V2)2-41
SEND, (V2)2-42
SETTIMER, (V2)2-44
SNAP, (V2)2-45
STATUS, (V2)2-46
SYSASSIGN, (V2)2-56
TIME, (V2)2-57
TURNON, (V2)2-58
UNLOCK, (V2)2-58
WAIT, (V2)2-60
exit, (V2)2-22
functionality, (V2)2-1
job numbers, (V2)2-5
owner names, (V2)2-4, (V2)2-5
restrict directives, (V2)2-3
set system operations, (V2)2-31
system console, (V2)2-4
system task restrictions, (V2)2-4
task names, (V2)2-4
task numbers, (V2)2-4
Open, resource, (Vl)5-3
Open File Service, (Vl)6-236
Open Resource Service, (Vl)6-122,
(Vl)7-121
Operating Environments, (V2) 1-11,
(V2)1-13
Operator Communications, see OPCOM
Operator Console, see Console
Operator Intervention Inhibit, (V3)10-44
Option Word Inquiry, (Vl)6-126, (Vl)6-127,
(Vl)7-124, (Vl)7-125
Options
TSM, see TSM, options
VOLMGR, see VOLMGR, options
Others, (Vl)3-6, (Vl)4-40, (V3)7-42
Overlay, load, (Vl)6-121
Owner, (V3)7-43, (V3)1O-3
Owner Name, (V2)1-8, (V2)2-4, (V3)10-4
validation, (Vl)6-218
- pPage Size, (V2)1-83, (V3)7-21
Panel Mode Commands, G-l
Parameter, assign a value, (V2)1-94
Parameter Passing, (V2)1-29
Parameter Receive Block (PRB), (Vl)2-32, L-54
Parameter Replacement
append a value, (V2)1-30
macro files, ('12)1-30
Parameter Send Block (PSB), ('11)2-27, L-55
Parameter Task Activation Block (PTASK),
(Vl)6-134, ('11)7-134, L-47
Parameter Task Activation Service,
('11)6-133, (Vl)7-133
Password, ('12)1-9, ('13)7-44, (V3)1O-4
for terminal ports, (V4)2-43
Index
c
(~
(
PASSWORD Task, (V2)1-1O, (V3)7-49
Patch Area, (V3)7-45
Patch Facility, see J.INIT
Patch File, (V3)7-45
Pathname,
execution, (Vl)4-7
fully qualified, (Vl)4-8, (Vl)4-10
partially qualified, (Vl)4-9, (Vl)4-11
reconstruct, (VI )6-128
syntax check, (Vl)6-129, (Vl)7-129
with VOLMGR, (V2)3-15
Pathname Block (PNB), (Vl)5-52, L-50
PCB, (Vl)6-180, (Vl)7-182, L-50
Peripheral Device
allocate, (Vl)6-222
deallocate, (VI )6-231
Permanent File Address Inquiry
Service, (VI )6-234
Permanent File Log Service, (Vl)6-244
Permanent Files, see File, permanent
Physical Channel Program, (Vl)5-43, (Vl)5-44
Physical Device Inquiry Service, (VI )6-246
Physical Dismount, (Vl)4-19
Physical Memory Read Service, (Vl)6-124,
(Vl)7-126
Physical Memory Write Service, (VI)6-125,
(VI)7-127
Physical Mount, (VI )4-17
PNB, (V1)5-52, L-50
Port Protection, (V4)2-43
Post Program-Controlled Interrupt (PPCI),
caller notification packet, (VI )5-47, L-53
end-action receiver, (VI)5-44
Powers of Integers, E-l
PPCI, (VI)5-44, (Vl)5-47, L-53
PRB, (Vl)2-32, L-54
Print a File, (V2) 1-84
Printers
device definition, (V3)7-21, (V3)7-25
laser support, (V4)2-34
serial, formatter/spooler, (V4)2-51
Priority
change batch job, (V2)1-103
change task, (Vl)6-131, (Vl)7-131
increments, (Vl)2-11
levels, (VI) 1-7
batch jobs, (V3)7-11
interactive tasks, (V3)7 -62
migration, (V 1)2-11
task execution, (Vl)2-10
Privilege Mode, (Vl)6-132, (Vl)7-132
Privilege Task, (Vl)6-132, (Vl)7-132
Process a Different Directive File, (V2)1-46
Program Development Utilities, (Vl)I-15
Program Hold Request Service, (VI)6-87,
(VI)7-90
MPX-32 Reference
PROJECT
directive summary, (V3)1O-12
directives
ADD, (V3)1O-12
CHANGE, (V3)10-13
DELETE, (V3)10-13
LOG, (V3)10-13
NEWFILE, (V3)10-14
X, (V3)1O-14
examples, (V3)10-14
M.PRJCf file, (V3)10-11
usage, (V3)10-1l
Project Group, (V2)1-1l, (V3)7-48, (V3)10-1l
change, (VI)6-46, (Vl)7-56, (V2)1-48
user default, (V3) 10-4
validate, (VI)6-218
Protection Granule, (VI)3-16
PSB, (VI)2-27, L-55
PseUdonym, (V2)2-27
PTASK Block, (Vl)6-134, (Vl)7-134, L-47
Public Volume
automatic mount, (V3)9-11
description, (VI )4-16
dismount, (V2)1-55, (V2)2-16
mount, (V2)1-77, (V2)2-33
Purge, (Vl)6-214, (VI)7-208
Put User Context Service, (Vl)7-138
-RRandom Access, (VI)I-9, (Vl)4-35
Rapid File Allocation Utility, see J.MDT!
RCB
description, (VI )5-59, L-60
directory, (VI )5-62, L-63
file, (V1)5-59, L-60
memory partition, (VI )5-83, L-64
RDTR, (V2)3-6
read from tape, (V2)3-46
Read Descriptor Service, (VI)6-99,
(Vl)7-144
Read Directives, from a file, (V2)1-89
Read RDTR from Tape, (V2)3-46
Read Record Service, (Vl)6-141, (VI)7-142
Read/Lock Write/Unlock (RLWU), (V3)7-48
Read/Write Authorization File Service,
(Vl)6-218
Real-Time Clock
interrupts per second, (V3)7-39
interrupts per time unit, (V3)7-42
Real-Time Environment, accessing, (V2)1-12
Real-Time Task Accounting, (Vl)2-53,
(V2)2-31, (V3)7-36
Realtime Debugger, (V4)2-44
Recall Command Lines, (V2)1-85, (V2)10-4
Receive Message Link Address Service,
(Vl)6-140, (Vl)7-141
IN-19
Receiver Exit Block (RXB), (Vl)2-33, L-74
Reconstruct Pathname Service, (Vl)6-128,
(Vl)7-42
Records
backspace, (Vl)6-11, (Vl)7-16
read, (Vl)6-141, (Vl)7-142
write, (Vl)6-197, (Vl)7-198
Recover Multiprocessor, (V2)2-58, (V3)10-53
Recovering the System, (V3 )6-1
Redirect SLO/SBO Output, (V2)2-37
Reflective Memory System Software (RMSS).
(Vl)4-15, (V3)7-41
Reformat RRS Entry Service, (Vl)6-119
Reinstate Privilege Mode to Privilege Task
Service, (Vl)6-132, (Vl)7-132
Release Channel Reservation Service,
(Vl)6-149, (Vl)7-153
Release Dual-Ported Disk/Set Dual-Channel
ACM Mode Service, (Vl)6-142,
(Vl)7-145
Release Exclusive File Lock Service,
(Vl)6-240
Release Exclusive Resource Lock Service,
(Vl)6-188, (Vl)7-190
Release FHD Port Service, (Vl)6-219,
(Vl)7-212
Release Synchronization File Lock Service,
(Vl)6-237
Release Synchronous Resource Lock
Service, (Vl)6-190, (Vl)7-193
Remote Terminal Logoff, (V4)2-37
Remove a Job, (V2)1-86
Remove Shared Image from Memory,
(V2)2-22
Rename
file, (Vl)6-143, (Vl)7-146, (V2)1-87,
(V2)3-47
volume, (V4 )2-44
Rename File Service, (Vl)6-143, (Vl)7-146
Replace Permanent File Service, (Vl)6-144,
(Vl)7-147
Reprint SLO, (V2)2-38
Repunch SBO, (V2)2-39
Request Interrupt (RI), (V2)2-40, (V2)2-44
Reserve Channel Service, (Vl)6-153,
(Vl)7-156
Reserve Dual-Ported Disk/Set SingleChannel ACM Mode Service,
(VI)6-145, (Vl)7-148
Reserve FHD Port Service, (VI )6-220,
(Vl)7-212
Reset a Flag. (V2)1-88
Reset a Memory Word. (V2)2-32
Reset Option Lower Service. (Vl)6-148.
(Vl)7-152
IN-20
Resident Executive Services (H.REXS),
(Vl)5-49
Resident Shared Image
load, (V2)2-24
remove, (V2)2-22
Resource Control, (VI)4-4
Resource Create Block, see RCB
Resource Descriptor (RO)
allocation map, (Vl)6-208, (Vl)6-212
description, (VI )4-1, (VI )4-22, (VI )5-20,
(Vl)5-51
modify, (Vl)6-112, (VI)7-113
modify user area, (VI)6-114, (Vl)7-115
read, (Vl)6-99, (VI)7-144
rewrite, (VI)6-146, (Vl)7-150
rewrite user area, (Vl)6-147, (VI)7-151
Resource Descriptor Tape Record, see ROTR
Resource Identifier (RID), (Vl)4-31, (VI)5-1O,
(VI)5-55, L-66
Resource Inquiry Service, (Vl)6-93,
(Vl)7-96
Resource Logging Block (RLB). (VI)6-105,
(VI)7-lOS, L-67
Resource Management, (V1)3-1, (VI)4-1
dynamic, (Vl)4-1
static, (VI)4-1
Resource Management Module, see H.REMM
Resource Requirement Summary (RRS),
(Vl)5-4, L-68
Resourcemark Lock Service, (VI)6-150,
(Vl)7-154
Resourcemark Table, increase size, (V3)7-49
Resourcemark Unlock Service, (Vl)7-155
Resources
access, (Vl)3-3
blocked I/O, (Vl)3-4
execute channel program, (Vl)3-3
logical device, (V 1)3-4
logical file, (VI )3-4
access attributes
directories, (Vl)3-9
files, (VI)3-lO
memory partitions, (VI)3-10
volumes, (VI )3-S
allocate, (Vl)5-1, (Vl)5-2, (Vl)5-3,
(Vl)6-8, (Vl)7-12
dynamic, (V1)3-3
static, (Vl)3-3, (VI)3-IS
assign, (VI)5-1, (Vl)5-2, (VI)5-3,
(Vl)5-4, (VI)6-8, (Vl)7-12
attach, (Vl)3-2, (Vl)5-2
attributes, (Vl)3-6
modify, (VI )3-5
protection, (VI )3-6
classes, (Vl)4-2
conflicts, (Vl)5-15
Index
c
(':
create, (VI)3-2
deadlock, (Vl)4-50
deallocate, (Vl)6-42, (Vl)7-53
deassign, (Vl)6-42, (VI)7-53
define, (Vl)3-2
delete, (Vl)3-2, (VI)6-48, (VI)7-57
dequeue, (VI )4-4
detach, (VI )3-4
directory structure, (Vl)4-6
disk structure, (VI)4-6
display listing, (V2)3-44
enqueue, (VI )4-4
error handling, (Vl)5-15
exclusive allocation, (VI )6-101,
(Vl)6-188, (Vl)7-104, (Vl)7-190
extension, (VI )3-11
functions, (Vl)3-2
I/O, (Vl)5-1
inquiry, (Vl)3-5, (Vl)6-93, (Vl)7-96
log information, (VI)6-103, (VI)7-106,
(V2)3-42, (V2)3-43, (V2)3-44
logical, (VI )3-1
modify attributes, (Vl)3-5
multiprocessor, (Vl)4-47
nonshareable, (Vl)4-2
open, (Vl)5-3, (Vl)5-14, (Vl)6-122,
(Vl)7-121
other, (Vl)3-6, (VI)4-2, (V3)7-42
owner, (V1)3-6, (Vl)4-2, (V3)7-43
pathnames, (VI )4-7
physical, (VI )3-1
print, (Vl)5-38
project group, (Vl)3-6, (Vl)4-2, (V3)7-48
protection, (VI )4-13
punch, (Vl)5-38
shareable, (Vl)3-6, (VI)4-2
access control, (Vl)4-5
exclusive, (VI)3-7, (VI)4-3
explicit, (VI)3-7, (Vl)4-3
implicit, (VI)3-8, (Vl)4-3
terminate operations, (Vl)6-21, (Vl)7-27
types, (Vl)3-1, (Vl)4-1
unformatted media, (Vl)5-25
user classes, (Vl)3-6, (Vl)4-2
Restart, (V3 )5-1
Restore files from tape, (V2)3-48, (V2)3-53
Restrictions, user, (V3)10-4
Resume Task Execution, (VI )6-167, (VI)7 -171
(Vm~
,
Resume Task Execution Service, (Vl)6-167,
(Vl)7-171
Return Pathname String, (Vl)6-128,
(VI)7-42
Rewind File Service, (VI)6-154, (VI)7-149
Rewind Magnetic Tape, (V2)3-53
MPX·32 Reference
Rewrite Descriptor Service, (VI)6-146,
(VI)7-150
Rewrite Descriptor User Area Service,
(VI)6-147, (VI)7-151
RID, (VI)4-31, (VI)5-1O, (Vl)5-55, L-66
RLB, (Vl)6-105, (VI)7-108, L-67
RMSS, (VI)4-15, (V3)7-41
Root Directory, (VI )4-6
RRS, (VI)5-4, L-68
RTOM Interval Timer, (V3)7-32
Run Receiver, (VI)2-22, (Vl)2-23
establish, (VI)2-23
exit, (VI)2-24, (VI)6-203, (VI)7-205
Run Request, (VI)I-11
end-action processing, (VI )2-26
exit, (VI)6-202, (VI)7-204
parameters, (VI)2-24, (Vl)6-84, (VI)7-87
send to task, (VI)2-26, (VI)6-164,
(Vl)7-168
RXB, (Vl)2-33, L-74
- SSave Files, (V2)3-54, (V2)3-57
display, (V2)3-43
Save Image, directory, (V2)3-4
Save Tape, (V2)3-1, (V2)3-2
SBO
change default device, (V2)2-56
delete file, (V2)2-14
logical file code assignment, (V2)1-22,
(V2)1-36
output, redirect, (V2)2-37
repunch files, (V2)2-39
specify default device, (V3)7-45
Scan Terminal Input Buffer Service,
(Vl)6-178, (Vl)7-180
Scanner Demo, (V4)2-59
Scheduler, select IPU/CPU, (V3)7-17
Scheduling
CPU, see CPU scheduling
I/O, (Vl)2-42
IPU, «Vl)2-18
swap, see Swap Scheduling
task interrupt, (Vl)2-20
Scratchpad, (V3)7-36
Screen Logic, TSM, (V2)1-21
Screen Width, (V2)1-75
SCSI Disk
device definition, (V3)7-13
media management, (V3)13-23
utility, (V4)2-50
SDT
master
boot from, (V3)2-12
contents, (V3)2-3
create, (V2)3-60
IN·21
install, (V3)2-1
magnetic tape, (V3)2-10
utility tape, (V3 )2-10
user
boot from, (V3 )4-4
create, (V2)3-58, (V3)4-1
install, (V3)4-3
Search Memory for a Value, (V2)2-41
Search
within a file or files, (V4)2-38
within a source file,
(V4)2-30, (V4)2-52
Security, (V3)10-22
limit logon time, (V3)10-23
limit terminalI/O inactivity, (V3)10-23
LOGONFLE examples, (V3)10-24
restrict logon attempts, (V3)10-22
Select Initial Input Source, (V2)1-93
Select Records
from a device, (V2)1-90
from a file, (V2) 1-91
from initial input source, (V2) 1-93
library format
from a device, (V2)1-92
from a file, (V2)1-93
Send a Message
to a task, (Vl)6-162, (Vl)7-166,
(V2)2-42
to terminal users, (V2)1-101
to the console, (Vl)6-187, (Vl)7-189,
(V3)7-11
to user's terminal, (V2)1-80, (V3)7-11
Send Message to Specified Task Service,
(VI)6-162, (Vl)7-166
Send Run Request to Specified Task
Service, (Vl)6-164, (Vl)7-168
Sequential Access, (Vl)4-35, (Vl)5-38
Serial Printer Formatter/Spooler,
(V4)2-51
Set Asynchronous Task Interrupt Service,
(Vl)6-lO, (Vl)7-14
Set Exception Handler Service, (Vl)7-158
Set Exception Return Address Service,
(VI)7-157
Set Exclusive File Lock Service, (Vl)6-241
Set Exclusive Resource Lock Service,
(Vl)6-101, (Vl)7-104
Set Flag
false, (V2)1-88
true, (V2) 1-95
Set IPU Bias Service, (Vl)6-98, (Vl)7-102
Set Option Lower Service, (Vl)6-163,
(Vl)7-167
Set Synchronization File Lock Service,
(Vl)6-238
IN·22
Set Synchronous Resource Lock Service,
(Vl)6-157, (Vl)7-161
Set Synchronous Task Interrupt Service,
(Vl)6-170, (Vl)7-174
Set Timer, (V2)2-44
Set User Abort Receiver Address Service,
(Vl)6-166, (Vl)7-170
Set User Status Word Service, (Vl)6-155,
(Vl)7-159
SGO, logical file code assignment, (V2)1-22,
(V2)1-36
Shadow Memory
access, (V3)lO-57
allocate task space, (V2)1-98
assign by RRS, (V1)5-13
configurations, (V3)lO-54, (V3)10-56
error messages, (V3)lO-57
memory classes, (V3)10-56
overview, (V3)10-54
SYSGEN error messages, (V3)7-56
Shadow Utility, see J.SHAD
Share Memory with Another Task Service,
(Vl)6-250
Shared Image
access, (VI )4-46
attach, (Vl)4-46
create, (VI )4-45
description, (VI)l-ll, (VI)4-45
detach, (Vl )4-46
exclude, (VI)7 -73
include, (VI)7 -93
load into memory, (V2)2-24
protection, (VI )4-45
remove from memory, (V2)2-22
Shared Memory. (Vl)3-21, (V3)7-51
deallocate, (VI )6-233
dynamic partitions, (Vl)3-18
multiprocessor, (VI )3-22
static partitions, (VI )3-18
SYSGEN error messages, (V3)7-51
Shared Memory Table (SMT), (V3)7-51
Shared Tasks, (Vl)2-3
SHUTDOWN Macro
error messages, (V3)10-49
introduction, (V3)1O-45, (V3)10-46
modify, (V3)I0-47
usage, (V3)10-46
SID
change the default, (V2)2-56
specify default device, (V3)7-51
SJ.SWAPR2, (V3)10-49
SJ.XX.ER, (V3)lO-18
SLO
change default device, (V2)2-56
delete file, (V2)2-13
Index
c
logical file code assignment, (V2)1-22,
(V2)1-36
output, (V2)1-103
redirect, (V2)2-37
reprint files, (V2)2-38
specify default device, (V3)7-33
SYSGEN, title, (V3)7-63
Small Computer System Interface,
see SCSI Disk
SMAP, (V1)5-51, (Vl)6-206, (Vl)6-211
Software, unsupported, (V4 )2-1
Software Interrupt System, (VI)1-7
Software Priorities, (VI) 1-5
Sort/Merge, see FSORT2
Source Compare Program, (V4)2-25
Source Search Tool, (V4)2-30
Space Allocation, (VI )6-206
Special Keys, TSM, (V2)1-15
Split Image, see Extended MPX-32
Spool Batch Records
from a device, (V2) 1-90
from a file, (V2)1-91
library format
from a device, (V2)1-92
from a file, (V2)1-93
Spooled Input
control, (V2)1-30
terminating conditions, (V2)1-32
Spooled Output, see SLO
Starter System, (V3)2-1
State Chain
head cell, (VI )2-12
queue, (VI )2-12
State Chain History, (V4)2-27
State Queues, (V1)2-13
Static Memory Allocation, (V1)3-18
Status Codes
H.REMM, (V1)5-17
H.VOMM, (VI)S-S7
String Search, (V4)2-38
Submit Batch Job, (V2)1-4S, (V2)1-102
Submit Batch Job on Boot-up, (V4)2-15
Submit Job from Disk File Service,
(V1)6-226
Subroutine Libraries, (V1)1-21
Subroutine Library Editor, (VI) 1-17
Suspend Task Execution Service, (V1)6-169,
(V1)7-173
Suspend/Resume Service, (VI)6-168,
(VI)7-172
SVC Type I Table, (V3)7-58
Swap Device, (V3)7-S8
Swap File Size, (V3)7-46
Swap Monitor Program, (V4)2-54, (V4)2-55
Swap Parameter Modifier Program, (V4)2-53
Swap Quantum, (V3)7-S9
MPX-32 Reference
Swap Scheduler
algorithms, (V3)10-S0
call back swap-on priority only (CB.SOPO),
(V3)10-51
description, (V3) 10-49
errors, (V3)10-53
swap thrash control, (V3)10-51
task group outswap limits, (V3)10-52
user set inhibit flag (US.SWIF),
(V3)10-S1
user set swap-on priority only (US.SOPO),
(V3)1O-51
wait state ordering, (V3)10-50
wait state swap-on priority only (SOPO),
(V3) 10-5 I
Swap Scheduling, (Vl)2-43
entry conditions, (VI )2-43
exit conditions, (V1)2-44
inswap process, (VI)2-45
outswap process, (VI )2-45
selection of inswap and outswap
candidates, (VI )2-44
structure, (VI)2-43
Swapper Percentage Active Monitor, (V4)2-53
SYC
description, (V2)1-16
I/O input limitations, (V2)1-23
logical file code assignment, (V2)1-21,
(V2)1-36
parameter replacement, (V2)1-30
terminal I/O, (V2)1-23
Symbol Table File Name, (V3)7 -60
Symbolic Debugger/X32, (Vl)I-18
Synchronization File Lock
release, (VI)6-237
set, (VI )6-238
Synchronized Access, (VI)6-157,
(VI)6-190, (V1)7-161, (VI)7-193
SYSGEN, (Vl)1-20, (V3)3-1, (V3)7-1
access, (V3)7-4
description, (V3)7-1
directive input file, (V3 )3-1
directive summary, (V3)7-4
directives
ACTIVATE, (V3)7-1O
AGE, (V3)7-1O
ARTSIZE, (V3)7-11
BATCHMSG, (V3)7-11
BATCHPRI, (V3)7-11
BEGPGOUT, (V3)7-12
CDOTS, (V3)7-12
/CHANNELS, (V3)7-13
CMIMM, (V3)7-13
CMPMM, (V3)7-13
CONTROLLER, (V3)7-13
DBGFILE. (V3)7-16
IN-23
DEBUGlLC, (V3)7-16
DELTA, (V3)7-17
DEMAND, (V3)7-17
DEVICE, (V3)7-18
DISP, (V3)7-26
D~O, (V3)7-27
DPTRY, (V3)7-27
DTSAVE, (V3)7 -27
/~~, (V3)7-28
ENDPGOUT, (V3)7-28
EXTDMPX, (Vl)3-28, (V3)7-28
/FILES, (V3)7-30
FLTSIZE, (V3)7-30
//HARDWARE, (V3)7-30
HELP, (V3)7-30
/INTERRUPTS, (V3)7-31
IOQPOOL, (V3)7-31
IPU, (V3)7-32
ITIM, (V3)7-32
ITLB, (V3)7-32
JOBS, (V3)7 -32
KTIMO, (V3)7-33
LOD, (V3)7 -33
LOGON, (V3)7-33
MACHINE, (V3)7-34
MAPOUT, (V3)7-35
MDT, (V3)7-35
/MEMORY, (V3)7-35
MMSG, (V3)7-36
MNWI, (V3)7-36
MODE, (V3)7-36
MODULE, (V3)7-37
/MODULES, (V3)7-38
MRUN, (V3)7-38
MSGPOOL, (V3)7-38
MTIM, (V3)7-39
NAME, (V3)7-39
NOANSI, (V3)7-40
NOBASE, (V3)7-40
NOCMS, (V3)7-40
NODEMAND, (V3)7-40
NOLACC, (V3)7-41
NOMAPOUT, (V3)7-41
NOSYSVOL, (V3)7-41
NOTDEF, (V3)7-41
NOTSMEXIT, (V3)7-42
NTIM, (V3)7-42
OTHERS, (V3)7-42
/OVERRIDE, (V3)7-43
OWNER, (V3)7-43
OWNERNAME, (V3)7-44
/PARAMETERS, (V3)7-44
/PARTITION, (V3)7-44
PASSWORD, (V3)7-44
PATCH, (V3)7-45
PCHFILE, (V3)7-45
IN-24
POD, (V3)7-45
POOL, (V3)7-46
PRIORITY, (V3)7-46
PROGRAM, (V3)7-47
PROJECT, (V3)7-48
RLWU, (V3)7-48
/RMSTABLS, (V3)7-49
RMTSIZE, (V3)7-49
SAPASSWD, (V3)7-49
/SECURITY, (V3)7-49
SEQUENCE, (V3)7-50
SGOSIZE, (V3)7-50
SHARE, (V3)7-51
SID, (V3)7-51
SIZE, (V3)7-51
SMD, (V3)7-57
IISOFTWARE, (V3)7-57
SVC, (V3)7-58
SWAPDEV, (V3)7-58
SWAPLIM, (V3)7-59
SWAPSIZE, (V3)7-59
SWP, (V3)7-60
SYCSIZE, (V3)7-60
SYMTAB, (V3)7-60
/SYSDEVS, (V3)7-60
SYSMOD, (V3)7-61
SYSONLY, (V3)7-61
SYSTEM, (V3)7-61
SYSTRAP, (V3)7-62
/TABLES, (V3)7-62
TERMPRI, (V3)7-62
TIMER, (V3)7-62
TITLE, (V3)7-63
TQFULL, (V3)7-63
TQMIN, (V3)7-63
TRACE, (V3)7-64
/TRAPS, (V3)7-64
TSMEXlT, (V3)7-64
USERPROG, (V3)7-65
/vp, (V3)7 -65
VP, (V3)7-65
VPID, (V3)7-65
logical file code summary, (V3)7-3
logical file codes, (V3)7-2
object input file, (V3 )3-1
options, (V3)7-3
running, (V3)3-3
SYSINIT, (V3)2-23
System
build, (V3)1-1, (V3)3-1
maintenance, (V3)1-1
new default image, (V3)5-3
recovery, (V3)6-1
restart, (V3)5-1
shutdown, (V3) 10-45
test, (V3)3-1, (V3)3-4
(-,
'-'
C
'~''"'
"I
Index
)
(
System Administrator, (V1)4-13
System Administrator Services
abort codes and messages, (V3) 10-18
ACM/MFP initialization, (V3)1O-35
ALIM initialization, (V3)1O-26
ANSI tape label utility (J.LABEL),
(V3)10-62
device initialization, (V3) 10-19
floppy disk initialization (J.FORMF),
(V3)10-42
INIT, (V3)1O-20
introduction, (V3)10-1
job accounting (M.ACCNT), (V3)1O-15
KEY program, see KEY
LOGONFLE, (V3)1O-20
M.CNTRL, (V3)lO-17
M.ERR and xx.ERR files, (V3)10-18
M.KEY, (V3)1O-3
M.PRJCT, (V3)1O-11
memory disk partition, (V3)1O-58
multiprocessor recovery (J.UNLOCK),
(V3)10-53
operator intervention inhibit, (V3)10-44
password control, (V3)7-49
PROJECT program, see PROJECT
security, (V3)1O-22
shadow memory, (V3)1O-54
swap scheduler control, (V3)1O-49
system console messages, (V3) 10-41
system date/time backup (J .DTSAVE),
(V3) 10-44
system date/time update, (V2)2-20
system shutdown, (V3) 10-45
terminal initialization, (V3) 10-19
volume mount (M.MOUNT), (V3)l0-43
SYSTEM as Ownemame, (V3)7-33, (V3)7-61
System Binary Output, see SBO
System Builder, (V3)2-23
System Console, (V2)2-4
configuration, (V3)2-1
device definition, (V3)7-21
device specification, (Vl)5-28
messages, (V3)10-41
System Console Type Service, (V1)6-187,
(Vl)7-189
System Console Wait Service, (VI )6-41,
(Vl)7-51
System Control File, see SYC
System Date and Time, update, (V2)2-20
System Daterrime Backup Program
(J.DTSAVE), (V3)1O-44
System Debugger (H.DBUG I, H.DBUG2)
accessing, (V3 )8-6
arithmetic operators, (V3)8-2
attach, (V2)2-12
base characters, (V3 )8-4
MPX·32 Reference
bases, (V3 )8-4
breakpoints, (V3)8-3
console address for stand-alone I/O,
(V3)7-16
directive list example, (V3)8-32
directive summary, (V3)8-7
directives
AB (Absolute), (V3)8-9
AD (Address), (V3)8-9
AR (Arithmetic), (V3)8-10
AS (Assemble Instruction), (V3)8-1O
BA (Base), (V3)8-10
BR (Breakpoint), (V3)8-11
BY (Bye), (V3)8-11
CB (Change Base Register), (V3)8-12
CD (Display Command List), (V3)8-12
CE (Zero Command List), (V3)8-12
CH (Display Controller Definition
Table Entry), (V3)8-12
CL (Terminate Build Directive List
Mode), (V3)8-13
CM (Change Memory), (V3)8-13
CO (Continue), (V3)8-13 _
CR (Change Register), (V3)8-14
CS (Build Directive List), (V3)8-14
CT (Continue then Terminate),
(V3)8-14
CX (Execute Directive List), (V3)8-14
DB (Display Base Register), (V3)8-15
DE (Delete), (V3)8-15
01 (Display Instruction), (V3)8-15
OM (Display Memory), (V3)8-15
DQ (Display Dispatch Queue Entry),
(V3)8-16
DR (Display Register), (V3)8-16
OS (Display Symbolic), (V3 )8-16
DT (Display Event Trace), (V3 )8-17
DU (Dump), (V3)8-17
EC (Echo), (V3)8-17
ET (Enter Event Trace Point),
(V3)8-17
GO (Go), (V3)8-18
HC (Display Dispatch Queue Head
Cell), (V3)8-18
LB (List Breakpoint), (V3)8-19
LP (Line Printer), (V3)8-19
LT (List Mobile Event Trace Point),
(V3)8-19
MR (Map Register), (V3 )8-19
MS (Modify CPU Scratchpad
Location), (V3)8-20
PO (Display Patch List), (V3)8-20
PE (Zero Patch List), (V3)8-20
PR (Terminate Build Patch
List Mode), (V3)8-21
PS (Program Status), (V3)8-21
IN·25
PT (Build Patch List), (V3)8-21
PV (Convert Physical Address to
Virtual Address), (V3)8-21
PX (Execute Patch List), (V3)8-21
RB (Reset Bases), (V3)8-22
RE (Remap), (V3)8-22
RT (Remove Event Trace Point),
(V3)8-22
SE (Search Equivalent), (V3)8-23
SM (Set Mask), (V3)8-23
SP (Scratchpad Dump), (V3)8-23
SY (Symbolic), (V3)8-23
TB (Trace Back), (V3)8-24
TE (Terminate), (V3)8-24
TR (Trace), (V3 )8-24
TS (Trace Stop), (V3)8-25
TY (Terminal), (V3)8-25
UD (Display Unit Definition Table
Entry), (V3)8-25
VP (Convert Virtual Address to
Physical Address), (V3)8-26
display a program, (V3)8-29
display memory, (V3)8-27
execution breakpoints, (V3)8-3
expressions, (V3)8-5
indirection, (V3)8-5
introduction, (V3)8-1
operator restrictions, (V3 )8-5
parts of, (V3 )8-1
patch list example, (V3)8-33
practice session, (V3)8-26
registers, (V3)8-5
special functions, (V3)8-3
special operators, (V3)8-2
System Dispatch Queue, display, (V2)2-26
System Distribution Tape, see SDT
System General Output, see SGO
System Generation, see SYSGEN
System Halt Analysis, (V3)6-2
System Image
build a new default, (V3 )5-3
filename, (V3)7-61
System Input Device, see SID
System Listed Output, see SLO
System Modules
replace, (V3)7-61
specify, (V3)7-65
System Nonresident Media Mounting
Task, (VI)l-13
System Output Queues, display, (V2)2-26
System Patch File, display. (V2)2-26
System Protection, (V3)3-5
System Recovery, (V3)6-1
System Restart, (V3)5-1
IN·26
System Services
base mode, (Vl)7-1
IPU executable, (Vl)7-5
syntax rules, (Vl)7-2
cross reference, B-1
H.VOMM macros, (Vl)5-65
nonbase mode, (Vl)6-1
IPU executable, (Vl)6-3
overview, (Vl)1-10
return conventions, (Vl)5-16
status posting, (Vl)5-16
System Shutdown
error messages, (V3)10-48
J.SHUTD. (V3)10-45
overview, (V3) 10-45
SHUTDOWN, (V3)1O-45, (V3)1O-46
volume clean-up, (V3)1O-46
System Start-up, Generation, and
Installation, see SYSGEN
System Task Restrictions, (V2)2-4
System Volume, (Vl)4-15, (V3)S-S
-T Tab Settings, TSM, (V2)1-20
Tabs, (V4)2-S6
Tape Drive, device definition, (V3)7 -23
Task
abort dump, (V3)7-36
abort, see Task, execution, abort
base nonshared, (Vl)2-3
base shared, (V 1)2-6
change priority, (Vl)6-131, (Vl)7-131
connect to interrupt level, (Vl)6-35,
(Vl)7-41, (V2)2-10
create timer, (Vl)6-1S9, (Vl)7-163
delete timer, (V1)6-56, (VI)7-66,
(V2)2-12
demand page, (V1)3-17
disconnect from interrupt level,
(V2)2-15
display status, (V2)2-26, (V2)2-46
environment, (VI )6-66, (VI)7-72
execution, (Vl)2-7
abort, (Vl)2-46, (Vl)6-16,
(Vl)6-S0, (VI)7-21, (VI)7-59,
(V2)1-19, (V2)2-6
return control, (Vl)6-166,
(Vl)7-170
attach debugger, (V2)1-19, (V2)2-12
continue, (V2)1-19, (V2)1-20,
(V2)1-49, (V2)2-11
delete task, (V2) 1-20
from directive files, (V2)1-27,
(V2)1-89
from system service, (Vl)6-5,
(Vl)7-7
Index
(
hold, (VI)6-87, (VI)7-90,
(V2)I-I9, (V2)2-23
kill, (V2)2-25
phase I of activation, (VI)2-7
phase 2 of activation, (V 1)2-8
priorities, (VI)2-10
resume, (Vl)6-167, (Vl)6-185,
(Vl)7-171, (Vl)7-187, (V2)2-1O,
(V2)2-40, (V2)2-44, (V2)2-58
suspend, (VI)6-41, (VI)6-169,
(Vl)7-51, (Vl)7-173
suspend/resume, (VI )6-168,
(Vl)7-172
termination, (Vl)2-46, (Vl)2-47,
(Vl)6-69, (Vl)7-75
TSA, (VI )2-8
under OPCOM, (V2)2-7, (V2)2-21,
(V2)2-44
under TSM, (V2)1-16, (V2)1-34,
(V2)1-45, (V2)1-59, (V2)1-88,
(V2)1-102
exit status, (VI)7 -78
hold, (V2)2-23
identification, (VI )2-1, (VI )6-88,
(VI)7-91
interactive, characteristics, (V2)1-25
interrupt, (V2)1-19
context storage, (VI)2-21
level gating, (Vl)2-21
levels, (VI)2-20
OPCOM, (V2)2-6, (V2)2-9,
(V2)2-25
receivers, (Vl)2-20
scheduling, (VI)2-20
system services (VI)2-20, (Vl)6-19,
(Vl)6-55, (Vl)6-59, (VI)6-64,
(Vl)6-97, (Vl)6-170, (Vl)6-171,
(Vl)6-198, (Vl)7-24, (VI)7-63,
(Vl)7-67, (Vl)7 770, (Vl)7-101,
(Vl)7-I74, (VI)7-175, (Vl)7-200
system services summary, (Vl)2-35
user break receivers, (Vl)2-21
limits of base mode, (VI)7-103
multicopied, (Vl)2-3
name, (VI )2-1
nonbase mode vs. base mode, (VI )2-2
nonbase nonshared, (VI)2-3, (V1)2-5
nonbase shared, (VI )2-6
number, (Vl)2-1
obtain status, (VI)6-118, (Vl)7-120
option word inquiry, (Vl)6-126,
(VI)6-127, (V1)7-124, (VI)7-125
override parameters, (VI)6-133, (VI)7-133
priorities, (VI)2-10
priority levels, (VI) 1-7
privileged, (Vl)6-132, (VI)7-132
MPX·32 Reference
shared, (VI)2-3
specify user name, (Vl)6-253
state, (Vl)2-12, (VI)2-13, (V2)1-20,
(V2)2-28, (V2)2-52
structure, (VI)2-2
swap scheduling, (V3)1O-49
termination, see Task, execution,
termination
test timer, (VI)6-184, (Vl)7-186
unique, (VI )2-3
unprivileged, (VI )6-192, (VI)7 -192
Task Cataloger, see CATALOG
Task CPU Execution Time Service,
(VI )6-204, (Vl)7 -206
Task Debugger, (Vl)1-16
Task Identification, (VI )2-1
Task Interrupt, see Task, interrupt
Task Name, (VI )2-1, (V2)2-4
Task Number, (VI)2-1, (V2)2-4
Task Option Doubleword Inquiry Service,
(Vl)6-126, (VI)7-124
Task Option Word Inquiry Service,
(VI)6-127, (VI)7-125
Task Service Area, see TSA
Task Structure, (VI )2-2
Task-Synchronized Access to Common
Resources, (VI )2-49
TCPB, (Vl)5-41, L-75
TCW, (Vl)5-37
TDEFLIST File, (V2)11-5
Temporary Files, see File, temporary
TERMDEF
access with M.GETDEF, (VI)6-81,
(V2)11-18
access with ~GETDEF, (Vl)7-81
components
J.TDEFI, (V2)11-4
J.TSET, (V2)11-21
LOGONFLE, (V2)11-17
M.GETDEF, (V2)11-18
TDEFLIST, (V2)1l-5
TERMDEF file, (V2)1l-8
TERMPART, (V2)11-3
demo, (V4)2-28, (V4)2-31
exclude support, (V3)7-41
file
booieans, (V2)11-9
control strings, (V2)1l-9
cursor addressing, (V2)11-10
sample, (V2)11-12
illustration, (V2)11-2
information block, (V2)11-18
utility, (V4)2-19
Terminal Definition Facility, see TERMDEF
Terminal I/O
close, (V2)1-24
IN·27
example session, (V2)1-108
exit, (V2)1-14, (V2)1-59
input limitations, (V2)1-23
open, (V2) 1-24
reads, (V2)1-23
rewind scanner, (V2)1-24
scan input buffer, (Vl)6-I78, (Vl)7-180
SYC, (V2)1-23
type identification, (V2) 11-8, (V2) 11-17,
{V2)11-21
wait state, (Vl)6-195, (Vl)7-197,
(V2)1-105, (V2)2-60
wakeup, (V2)1-8, (V2)1-20
writes, (V2)1-24
Tenninal Initialization, (V3)3-5, (V3)10-19
Terminal lnitializer/Loader, (V4)2-56
Tenninal Services Manager, see TSM
Terminal Timeout Counter, (V3)1O-23
Terminal, user, see UT
Tenninate a Directive File. (V2)1-58
Terminate Processing. (V2)1-49
Terminate Task Execution Service,
{Vl)6-69, (Vl)7-75
TERMPART, (V2)11-3
Test Timer Entry Service, (Vl)6-184,
(Vl)7-186
Test User Status Word Service, (Vl)6-183,
(V1)7-185
Testing a SYSGENed System, (V3)3-4
Text Editor, (Vl)1-17
Time and Date Formats, H-l
Time Instruction Sequences, (V4)2-38
Time Management, (Vl)1-12
Time-of-Day Inquiry Service, (VI )6-172,
(Vl)7-176
Time Quantum
controls, (V 1)2-11
maximum, (V3)7-63
minimum, (V3)7 -63
Time Units, (V3)7-39, (V3)7-42
Timer Entry
create, (Vl)6-159, (V1)7-163
delete, (VI )6-56, (Vl)7 -66
test, (Vl)6-184, (Vl)7-186
Timer Scheduler, (Vl)1-12
Timer Table Entries, (V3)7-62
Trap Handlers, (Vl)2-51, (V3)7-47
override defaults, (V3)7 -62
Trap Online User's Task Service, (Vl)6-171,
(V1)7-175
Trap Processors, (Vl)I-12, (Vl)2-51,
(V3)7-47
Truncate File Service, (Vl)6-177, (Vl)7-179
TSA
description,. (VI )2-8
extended (VI )3-34
IN-28
move, (VI)3-28, (Vl)3-32, (V2)1-60
pushdown stack area, (VI )2-10
starting address, (VI )6-86, (VI)7 -89
structure, (Vl)2-1O
TSM, (Vl)1-13, (V2)1-1
break key, (V2)1-19
break processor, (V2)1-27
case sensitivity, (V2)1-20
conditional processing, (V2)1-29
device initialization, (V3)1O-19
directive syntax, (V2)1-33
directives
$$, (V2)1-106
$$$, (V2)1-106
$ACCOUNT, (V2)1-33
$ACTIVATE, (V2)1-34
$ALLOCATE, (V2)1-35
$ASSIGN, (V2)1-36
$ASSIGNl, (V2)1-41
$ASSIGN2, (V2) 1-42
$ASSIGN3, (V2)1-43
$ASSIGN4, (V2)1-44
$BATCH, (V2)1-45
$CALL, (V2)1-46
$CHANGE, (V2)1-48
$CLEAR, (V2)1-49
$CONTINUE, (V2) 1-49
$CREATE, (V2)1-50
$DEBUG, (V2)1-50
$DEFM, (V2)1-51
$DEFNAME, (V2)1-52
$DELETE, (V2)1-53
$DIRECTORY, (Vl)6-179, (Vl)7-181
$DISABLE (V2)1-54
$DISMOUNT, (V2)1-55
$ENABLE (V2)1-57
$END, (V2)1-58
$ENDM, (V2)1-58
$EOJ, (V2)I-58
$ERR, (V2)1-58
$EXECUTE, (V2)1-59
$EXIT, (V2)1-59
$EXTDMPX, (Vl)3-33, (V2)1-60
$GETPARM, (Vl)6-181
$GOBACK, (V2) 1-62
$GOTO, (V2)1-63
$IFA, (V2)1-64
$IFF, (V2)1-66
$IFP, (V2)1-64
$IFT, (V2)1-69
$INIT PRO, (V2)10-7
$JOB, (V2)1-72
$LINESlZE, (V2)1-75
$LIST, (V2)1-76
$MAPOUT, (V2)1-76
$MOUNT, (V2)1-77
Index
(-
(
$NOMAPOUT, (V2)1-79
$NOTE, (V2)1-80
$OBJECf, (V2)1-80
$OPTION, (V2)1-81
$PAGESIZE, (V2)1-83
$PRINT, (V2) 1-84
$PROJECT, (VI )6-179, (V1)7 -181
$RECALL, (V2) 1-85
$REMOVE, (V2)1-86
$RENAME, (V2) 1-87
$RESETF, (V2)1-88
$RESTART, (V3)5-2
$RRS, (Vl)6-181
$RUN, (V2)1-88
$SELECf, (V2) 1-89
$SELECID, (V2)1-90
$SELECTF, (V2)1-91
$SELECfLD, (V2)1-92
$SELECfLF, (V2)1-93
$SELECfS, (V2)1-93
$SET, (V2)1-94
$SETF, (V2)1-95
$SETI, (V2)1-96
$SHADOW, (V2)1-98
$SHOW, (V2)1-99
$SIGNAL, (V2)1-101
$SPACE, (V2)1-101
$SUBMIT, (V2)1-102
$SYSOUT, (V2)1-103
$TABS, (V1)6-179, (V1)7-181
$URGENT, (V2)1-104
$USERNAME, (V2)1-104
$VOLUME, (V1)6-179, (V1)7-181
$WAIT, (V2)1-105
$WHO, (V2)1-106
%label, (V2)1-52
exit, (V2)1-59
exit when inactive, (V3)7-42
interactive tasks, (V2) 1-25
introduction, (V2) 1-1
JCL directive summary, (V2)1-2
macro looping, (V2) 1-29
options, (V2)1-17, (V2)1-24, (V2)1-81
abort, (V2)1-18, (V2)1-81
clear, (V2)1-17, (V2)1-81
command, (V2)1-17, (V2)1-81
cpuonly, (V2)1-18, (V2)1-81
dump, (V2)1-19, (V2)1-81
error, (V2)1-18, (V2)1-81
ipubias, (V2)1-19, (V2)1-81
1/c, (V2)1-19, (V2)1-81
lower, (Vl)6-148, (Vl)6-163,
(Vl)7-152, (Vl)7-167, (V2)1-17,
(V2)1-81
noabort, (V2)1-18, (V2)1-81
nocommand, (V2) 1-17, (V2) 1-81
MPX·32 Reference
noerror, (V2)1-18, (V2)1-81
nowrap, (V2)1-18, (V2)1-81
prompt, (V2)1-17, (V2)1-81
quiet, (V2)1-18, (V2)1-81
retain, (V2)1-17, (V2)1-81
text, (V2)1-17, (V2)1-81
u/c, (V2)1-19, (V2)1-81
unquiet, (V2)1-18, (V2)1-81
wrap, (V2)1-18, (V2)1-81
parameter passing, (V2) 1-29
procedure call block, (Vl)6-180, (Vl)7-182, L-50
procedure call directive strings, (Vl)6-179,
(Vl)7-181
scanner, (V2)1-25
screen logic, (V2)1-21
set options, (V2) 1-81
special keys, (V2)1-15
tab settings, (V2)1-20
TSM Procedure Call Block (PCB), (Vl)6-180,
(Vl)7-182, L-50
TSM Procedure Call Service, (Vl)6-179,
(Vl)7-181
TSM Scanner Demo, (V4)2-59
Type Control Parameter Block (TCPB),
(Vl)5-41, L-75
-UUDT, (V2)11-4, (V2)11-17, (V2) 11-21 , L-77
UDT Display, (V4 )2-60
Unfonnatted Media, (V1)5-25
Unique Tasks, (Vl)2-3
Unit Definition Table (UDT), (V2)1l-4,
(V2)11-17, (V2)11-21, L-77
Unlock and Dequeue Shared Memory
Service, (V1)6-252
Unsupported Software, (V4)2-1
UPDATE, (V1)1-19
Upspace Service, (Vl)6-193, (Vl)7-195
User Context
overwrite, (Vl)7 -138
store values, (Vl)7-80
User Modules, (V3)7-37
User Name, (V1)6-253
User Name Specification Service, (Vl)6-253
User Status Word, (Vl)6-155, (Vl)6-183,
(Vl)7-159, (Vl)7-185
User Tenninal, see UT
User Volume, (Vl)4-15
UT
device definition, (V3)7-21
exit, (V2)1-59
I/O input limitations, (V2)1-23
logical file code assignment, (V2)1-21
wait state, (V2)1-105, (V2)2-60
wakeup, (V2)1-8, (V2)1-20, (V3)10-20
IN·29
Utilities
AIDDB, (Vl)I-16
~S~32, <"1)1-17
C~T~LOG, see C~T~OG
DEBUGX32, <"1)1-18
DPEDIT, (Vl)I-17
EDIT, (Vl)I-17
illustration, ("1)1-3
J.VFMf, see J.VFMT
KEY, see KEY
LIBED, <"1)1-17
LINKX32, (Vl)I-18
~CLEBIl, ("1)1-16
~CX32, ("1)1-17
MED~, ("1)1-19
OBJX32, <"1)1-18
SYSGEN, see SYSGEN
UPDATE, <"1)1-19
"OLMGIl, see "OLMGIl
-V "alidate Address Ilange Service, <"1)6-194
(Vln-l%
'
"ector Processor Configuration,
<"3)7-65, <"3)7-66
"OLMGIl, <"1)1-17, <"2)3-1
access, ("2)3-14
BRIEF option, (V2)3-8
clear options, <"2)3-23
directive summary, <"2)3-7
directive syntax, <"2)3-18
directives
BACKSPACE FILE, <"2)3-22
BACKSPACE IMAGE, <"2)3-22
CLEM, <"2)3-23
CON'fERT, <"2)3-23
COPY, <"2)3-25
CIlEATE COMMON, <"2)3-29
CREATE DIIlECTORY, <"2)3-32
CIlEATE FILE, <"2)3-34
DELETE COMMON, <"2)3-37
DELETE DIIlECTORY, <"2)3-38
DELETE FILE, <"2)3-39
EXIT, ("2)3-40
EXTEND, ("2)3-41
HELP, <"2)3-41
LOG FILE, ("2)3-42
LOG IMAGE, <"2)3-43
LOG RESOUIlCE, ("2)3-44
LOG SA'fEFILE, <"2)3-46
IlENAME, ("2)3-47
IlESTOIlE DmECTORY, <"2)3-48
IlESTOIlE POSITION, <"2)3-53
IlEWIND, <"2)3-53
S~'fE, <"2)3-54
S~'fE INCIlEMENT~, <"2)3-57
IN·30
SOT, (V2)3-58
SOT MASTEIl, (V2)3-60
SET, (V2)3-61
SKIP END, (V2)3-64
SKIP FILE, (V2)3-64
SKIP IMAGE, (V2)3-65
TIlUNCATE, (V2)3-65
errors, (V2)3-66
global options, <"2)3-18, (V2)3-19
help, <"2)3-41
introduction, ("2)3-1
local options, (V2)3-18, (V2)3-19
logical file code assignments, (V2)3-16
options, ("2)3-17
BIlIEF, ("2)3-8
clear, <"2)3-23
global, ("2)3-18, ("2)3-19
local, <"2)3-18, <"2)3-19
set, ("2)3-61
time, <"2)3-20
resource descriptor tape record. <"2)3-6
save image, <"2)3-3
save tape format, <"2)3-1
save tape structure, <"2)3-2
set options, ("2)3-61
temporary files, ("2)3-17
time options, <"2)3-20
wild card characters, <"2)3-15, <"2)3-17
"olume, <"1)4-14
access attributes, <"1)3-8, <"1)4-16
automatic public mount, <"3)9-11
boot block, ("1 )4-22
descriptor, ("1)4-22
dismount, <"1)4-14, <"1)4-18, <"1)6-57,
<"1)7-64, <"2)1-55, <"2)2-16
explicit, ("1 )4-19
implicit, <"1)4-19
logical, ("1 )4-18
physical, (Vl)4-19
formatted, (Vl)4-14
mount, (Vl)4-14. ("1)4-17, ("1)6-115,
(Vl)7-116, ("2)1-77, <"2)2-33
explicit,
I u
I
C
,
I
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.6 Linearized : No Create Date : 2016:10:26 17:58:00-08:00 Modify Date : 2016:10:26 19:02:08-07:00 XMP Toolkit : Adobe XMP Core 4.2.1-c041 52.342996, 2008/05/07-21:37:19 Metadata Date : 2016:10:26 19:02:08-07:00 Producer : Adobe Acrobat 9.0 Paper Capture Plug-in Format : application/pdf Document ID : uuid:7a31d320-90d0-8345-99f5-84e0715e57d8 Instance ID : uuid:abfb0985-b582-034a-9842-251b2ebd872b Page Layout : SinglePage Page Mode : UseNone Page Count : 540EXIF Metadata provided by EXIF.tools