DH18 03_GCOS_8_OS_System_Startup_Aug87 03 GCOS 8 OS System Startup Aug87
DH18-03_GCOS_8_OS_System_Startup_Aug87 DH18-03_GCOS_8_OS_System_Startup_Aug87
User Manual: DH18-03_GCOS_8_OS_System_Startup_Aug87
Open the PDF directly: View PDF 
.
Page Count: 1216
| Download | |
| Open PDF In Browser | View PDF |
Large Systems
GCOS80S
System Startup
Honemell Bull
(
(
(
LARGE SYSTEMS
GCOS80S
SYSTEM STARTUP
SUBJECT
Initialization of Honeywell Bull Large Information Processing Systems Operating Under General Comprehensive Operating Supervisor 8 (GCOS 8) Software
SPECIAL INSTRUCTIONS
This revision supersedes DH18-02, dated December 1985. Change bars in the
margins indicate technical additions and changes, and asterisks indicate deletions. Refer to the Software Release Bulletin (SRB) for this product release for a
synopsis of technical changes.
SOFTWARE SUPPORTED
GCOS 8 OS Software Release 3000
ORDER NUMBER
DH18-03
August 1987
Hone~ell
Bull
(
PREFACE
The GCOS 8 OS System Startup manual describes software-related procedures for
starting up a newly installed system and for restarting that system. This
manual is directed at site personnel who must prepare the Startup job stream
and at operations personnel who must interface with the Startup program via the
system console.
Hardware operating procedures that are necessary to System Startup (e.g.,
and peripheral switch settings) are not included in this manual.
Refer to the appropriate hardware reference manuals for description of switch
settings.
main~rame
In, addition, this ~an~al does not define Startup procedures for the Front-end
Network Processors. Refer to the appropriate communications manuals for this
information.
The major sections of this manual are:
o
Section 1 presents an overview of the Startup program and the Startup job
stream.
/
\
o
Section 2 describes techniques for bootloading the system and the
opera~or (console) interface with the Startup program.
o
Section 3 describes procedures for recovery from error conditions that
occur during the system startup pr~cess.
o
Section 4 describes the procedure for loading Integrated Software and for
modifying default parameters for Integrated Software.
o
Section 5 describes the various statements that can be included in each
section of the Startup job stream.
In this document, multiple vertical braces and brackets should be assumed to be
a single brace or bracket; for example:
{
{
{
}
}
}
and
[
[
[
]
]
]
represent [
]
The information and specifications in this document are subject to change
without notice.
·Consult your Honeywell Bull Marketing Representative for
product or service availability.
Copyright «D.Honeywell Bull Inc., 1985, 1987
File No.: 1V13
DH18-03
(
CORRECTING MANUALS VIA PASS
Required corrections to this version of the manual will be
entered on the Problem Analysis Solution System (PASS) data
base. Query PASS periodically via the procedures described in
the Problem Analysis Solution System (PASS) manual, Order
Number DW95. Corrections documented on PASS, if applicable to
the next release of the software, will be incorporated into the
next update of the manual.
1ii
DH18-03
LISTING OF MliUlLS
A list of large system software manuals is available to all Honeywell Bull
users with access to an ASCII terminal. The manuals list is updated regularly
to facilitate the ordering of manuals. Manual ordering instructions are
printed on the listing. Use the following instructions to obtain a listing.
1. Dial the appropriate telephone number to connect your terminal to the
Multics system in Phoenix.
300-baud &
1200-baud
(602) 249-5356
249-6430
150-baud
249-7554
Multics will respond with a computer system identification banner.
2. Enter the login command "login Sam" (without the quote marks).
carriage return key.
Press the
Multics will respond with a request for the password.
3. Enter the password "Multics" (without the quote marks) and press the
carriage return key.
Multics will respond with a welcome message followed by a ready message.
Example:
Welcome to the Multics system
For services available online type:
:list
r1111.7 Thu
(ready message)
4. Enter ":list" (without the quote marks) to obtain a list of commands.
Press the carriage return key.
Multics will list the commands available for specific topics and then
display the ready'message.
5. Enter the command selected and press the carriage return key.
6. Enter "logout" (without the quote marks) and press the carriage return
key to log off the Multics system.
Multics will respond with a logout message.
iv
DH18-03
CONTENTS
Page
SECTION 1 SYSTEM STARTUP OVERVIEW •••••••••••••••••••••••••••••••••••
1-1
Bootload Startup Program •••••••••••••••••••••••••••••••••••••••••••••
Establish System Environment •••••••••••••••••••••••••••••••••••••••••
Execute Startup Job Stream •••••••••••••••••••••••••••••••••••••••••••
1-1
1-2
1-2
1-3
1-3
$CONFIG Sect ion ••••••••••••••••••••••••••••••••••••••••••••••••••••
$INITIALIZE Section .........•.....•................•...••..........
$EDIT Section ......................••...................•..........
$FILES Section .................•..................•....••...•......
1-4
$PATCH Sect ion ..................................................... .
$LOAD Section ••••••••••••••••••••••••••••••••••••••••••••••••••••••
1-4
1-4
1-4
SECTION 2 BOOTLOADING THE SySTEM ••••••••••••••••••••••••••••••••••••
2-1
DPS 88 And DPS 90 Firmware And Startup Bootloading •••••••••••••••••••
DPS 8 Systems With IMU Controllers •••••••••••••••••••••••••••••••• '•••
2-1
2-2
2-2
2-3
2-4
2-4
2-5
2-6
Bootloading .........................................•................
Power-up Operation •••••• ' •••••••••••••••••••••••••••••••••••••••••••
Cold Boot .............................................••..........•
Warm Boot ............................•..................•..........
Fast Boot .••••••.•••••.••••••.••••' •.••.••••• ·••••••••••••••••••••.••
Fast Boot With FASTBT File •••••••••••••••••••••••••••••••••••••••••
Bootload Procedures ................................................ .
Bootload From Mass Storage •••••••••••••••••••••••••••••••••••••••
AUTOLOAD File Not On Default Device Number (DPS 8 And DPS 8000'
Only) ............................•....•..•.•••..•••••..•..•..•.
DPS 8 And DPS 8000 Operator Procedure For Disk Boatload ••••••••
Bootload From Magnetic Tape On DPS 8 Or DPS 8000 •••••••••••••••••
Modification of Startup Job Stream •••••••••••••••••••••••••••••••••
Modifying Content Of AUTOLOAD File •••••••••••••••••••••••••••••••
Modifying Content Of Site-Specific Boot Tape •••••••••••••••••••••
Startup Resilience •••••••••••••••••••••••••••••••••••••••••••••••••••
Startup-Operator Interface •••••••••••••••••••••••••••••••••••••••••••
Startup Console Editor •••••••••••••••••••••••••••••••••••••••••••••
MSU3380 And MSU3381 Disk Device Survey Messages ••••••••••••••••••••
Startup Questions ••••••••••••••••••••••••••••••••••••••••••••••••••
*REPLACE? Question •••••••••••••••••••••••••••••••••••••••••••••••••
.CHANGE? Question ••••••••••••••••••••••••••••••••••••,••••••••••••••
*RETAIN CONFIGURATION? Question •••••••••••••••••••••••••
*RESTART? Question •••••••••••••••••••••••••••••••••••••••••••••••••
*SYSOUT RECOVERY? Question •••••••••••••••••••••••••••••••••••••••••
*SCF CONTINUATION? Question ••••••••••••••••••••••••••••••••••••••••
*SYSTEM CONTROLLER CLOCK AND .CRDAT MISMATCH Message •••••••••••••••
*DATE mmddyy TIME hh.mmm Information Message •••••••••••••••••••••••
v
2-7
2-7
2-8
2-9
2-10
2-11
2-11
2-12
2-12
2-14
2-14
2-16
I
2-17
2-18
2-20
2-20
2-21
2-21
2-22
2-23
2-23
DH18-03
I
I
CONTENTS (cont)
Page
.CHANGE SYSTEM CONTROLLER CLOCK? Question ••••••••••••••••••••••••••
.CHANGE DATE? Question •••••••••••••••••••••••••••••••••••••••••••••
.CHANGE TIME? Question •••••••••••••••••••••••••••••••••••••••••••••
.ENTER TIME OR ENTER A CORRECTION FACTOR? Question •••••••••••••••••
*DATE? Question ••••••••••••••••••.•••••••••••••••••••.•••• _" •..••••••
*TIME? Question ••••••••••••••••••••••••••••••••••••••••••• ~ ••••••••
.CHANGE> 5 MIN, YES TO ACCEPT? Question •••••••••••••••••••••••••••
.INITIALIZE? Question ••••••••••••••••••••••••••••••••••' ••••••••••••
Operator Controls During Initialization ••••••••••••••••••••••••••
MPC Bootloading (DPS 8 And DPS 8000 Only) ••••••••••••••••••••••••
Permanent -AUTO
~
)
where is the logical name of the operating system (GCOS 8) as
established by the site through the SMAS configuration facility (ICON).
The DPS 90 command to boot from mass storage is
BOOT OPSY AUTO.
Once the AUTOLOAD file has been established, the Startup program maintains a
pointer to the AUTOLOAD file so that a disk boot is always possible, provided
that the AUTOLOAD file is readable, and provided that the AUTOLOAD file
represents the configuration and options that are desired. Several additional
steps are necessary if a boot load is initiated via offline T&D. Those steps
are described under "AUTOLOAD File Not On Default Device Number (DPS 8 And
DPS 8000 Only)", which follows.
If a read error is encountered reading the AUTOLOAD file the system will halt
with a DIS and the AUTOLOAD file will have to be rebuilt.
2-7
DH18-03
AUTOLOAD File Not On Derault Device Number (DPS 8 And DPS 8000 Only)
The following procedure is required to establish information for using the
AUTOLOAD file to bootload directly from mass storage only if the AUTOLOAD file
is not on device number one (the default). Note that DSC500 firmware revision
A1 (or later) must be loaded to perform this bootload.
(
1. Examine the $ AUTOLD statement to determine the logical device name of
the mass storage device on which the AUTOLOAD file resides.
2. Examine the input/output controller statements. Determine the physical
device number of the mass storage device on which the AUTOLOAD file
resides. The device can be determined by matching the logical device
name (from 11) with the physical device number.
NOTE:
The default addressing executed by firmware is DEVICE-1.
3. Use the same input/output controller statement (from 12) to determine the
channel number over which the AUTOLOAD device is to be accessed.
4. Examine the $ MPC statements.
Determine both the PSI number and the
associated channel number over which the AUTOLOAD device is to be
accessed.
5. Convert the device number (from 12) to hexadecimal.
6. Create RHEX correction statements that identify the channel and the
device over which bootloading is to occur. The following depicts the
information that must be included on these statements.
,(
MPC CORRECTIONS:
Columns
1-4
Columns
16-17
Columns
18-19
04FE
04FF
(0) dd
(2) dd
(1)
(3)
dd
dd
where:
dd - Device number
0-3 - PSI numbers, which are defined by the columns in which the
device number is specified
DAU(MSP800) CORRECTIONS:
Columns
1-4
Columns
16-17
02BO
02CO
02DO
02EO
(0)
(1)
(2)
(3)
dd
dd
dd
dd
(
2-8
DH18-03
where:
dd - Device number
0-3 - PSI numbers, i.e., Patch 02BO for PSI-O, 02CO for PSI-1, etc.
7. Insert the RHEX correction statements into the $INITIALIZE section of the
Startup job stream. The RHEX statement immediately precedes the $ DKEND
statement of the associated mass storage MPC firmware deck.
B. Examine all $ XBAR statements and go back to step 3 for each of the XBAR
channels that may access a different MPC or PSI connection.
9. Patch the firmware tape with the RHEX correction statements. Refer to
the offline Test and Diagnostics listing for program OBF for patching
procedures. This step is required so that the firmware on the AUTOLOAD
file reflects the same bootload device and channel information as the
bootload deck in the $INITIALIZE section of the Startup job stream.
10. Bootload the system. The following must be performed during the bootload
process: (1) reboot the MPC, (2) include a $ READIN statement in the
$INITIALIZE section of the Startup job stream, and (3) respond YES to the
CLEAR AND OVERWRITE EXISTING DECKFILE? question issued to the console.
11. Issue the console verb, TEST IFAD when the system becomes operational, to
install the patched firmware in the online T&D extension file so that the
correct device numbers will be restored i f online ITRs are run and the
firmware is rebooted online.
DPS 8 And DPS 8000 Operator Procedure For Disk Bootload
The procedure to boot GCOS from an IMU is described in the IMU Hardware
Operations Manual.
The following operator procedures are required to execute a disk bootload to
boot GCOS from an 10M, once the firmware is active in the controller.
1. Set the BOOTLOAD SOURCE TAPE/CARD switch to TAPE (even though disk will
actually be used) on any IOM/1HU/1MX that can access the AUTOLOAD
device. Also, set the channel number code switches to identify the
channel connected to the AUTOLOAD device as the bootload channel.
2. Press, in sequence, the INITIALIZE and BOOTLOAD push buttons on the
system console or the IOM/IMU/IMX.
3. At this point, the Startup program issues the -REPLACE? question to the
first system console configured on the bootload IOM/IMU/IMX (as recorded
on the AUTOLOAD file which was written on the previous boot). If no such
console was configured, the default console (IMU channel 30 or 10M
channel 31 of the prior boot lMU/IOM or as specified on a MASK for
location 3) is used. This boot will define the console for the next
boot. (Refer to ".REPLACE Question" in this section for operator
responses to this question.)
2-9
DH18-03
BOOTLOAD FROM MAGNETIC TAPE ON DPS 8 OR DPS 8000
The Reset Out (RSO) hardware option must be included with MPC-driven magnetic
tape subsystems to allow primitive mode operation for DPS 8 and DPS 8000
systems. In primitive mode, the subsystem can process a Read Tape Binary
command, which is required for reading the first record on the boot tape. For
MPC-driven magnetic tape subsystems, the MPC switches must be set as follows:
Switch
Setting
o
Down (reset)
2
Controls bootloading of the MPC firmware
Up (set)
- Bootload firmware via Line Adapter 1
Down (reset) - Bootload firmware via Line Adapter 0
5-7
MPC port number to which the magnetic tape controller is connected
Before initiating the bootload, set the BOOTLOAD SOURCE TAPE/CARD switch on the
input/output controller to TAPE. MPC switches must reflect the density of the
boot tape (556, 800, or 1600 bpi), the number of tracks (seven-track or
nine-track tape handler), and the magnetic tape handler (1-15) on which the
boot tape is mounted. If the tape device is controlled by an IMU or IMX, refer
to the Hardware Operations Manual to:
1. Configure the MCA
2. Initialize the IMU by loading the IMU firmware
3. Start the GCOS bootload process.
I
I
I
After mounting the boot tape on the tape handler specified by the MPC SWitches,
and, if a cold boot is necessary, after mounting the total system software
tapes on the magnetic tape handlers defined by logical device name on $ FILDEF
statements in the $EDIT section of the Startup job stream, press the INITIALIZE
and BOOTLOAD push buttons on the system console in sequence to initiate the
bootload process. If no changes are to be made to the content of the Startup
job stream between the boot tape and the AUTOLOAD file, respond NO to the
*REPLACE? question.
If changes are' to be made to the content of the Startup job stream between the
boot tape and the AUTOLOAD file, via the Startup Console Editor, respond
PREPASS to the .REPLACE? question (see ".REPLACE? Question", later in this
section, for details).
If changes are to be made to the content of the Startup job stream between the
boot tape and the AUTOLOAD file, via the card reader, respond YES to the
.REPLACE? question (see "Startup-Operator Interface", later in this section,
for details). The Startup job stream is read from the boot tape through the
section header (e.g., $EDIT section) for the section that is to be replaced.
At that point, the cards in the card reader are read, and then used to overlay
(replace) the existing section on the AUTOLOAD file. After skipping the
replaced section on the boot tape, the procedure is repeated for any other
section(s) to be replaced, and then the tape is read to completion.
2-10
DH18-03
)
Note that the preceding process modifies only the AUTOLOAD file. The boot tape
is unaffected. (Refer to "Modifying Content Of Site-Specific Boot Tape", later
in this section,. for tape modification procedures.)
During the bootload process, the operator may be prompted to identify the card
reader to be used for reading the changes via one of the messages:
.NEED READER PORT, IOM, CHANNEL PICCC
or
.NEED READER IOM, CHANNEL ICCC
I
The operator response is in the form piccc or iCcc, where p = SCU-O port number
to which the IOM or lMU initiating the bootload process is cabled, i = IOM or
IMU number, and ccc = channel number. (Refer to ".REPLACE? Question" later in
this section and to n.BOOT SOURCE: AUTO OR REPL? Question" in Section 3 for
additional information.)
If the card reader becomes inoperable while reading cards, the operator can
press the REQUEST push button and respond to the ??? prompt with
READER piccc
or READER iccc
to cause Startup to switch to an operable card reader.
If the bootload is successful, the boot tape is automatically rewound and
programmatically dismounted. If the bootload is unsuccessful, the message
.ABORT BOOT FROM TAPE is issued to the system console. Check all switch
settings, the tape handler, and the tape during the error correction process.
(Refer to the GCOS 8 OS System Operating Techniques manual for magnetic tape
media-inspection procedures~)
Modification of Startup Job Stream
Execution of the Startup program causes the Startup job stream to be read from
one of two sources. The job stream may be read from the boot tape, in which
case it is copied to the AUTOLOAD file, or it may be read directly from the
AUTOLOAD file. Techniques are available for indirectly modifying the contents
of the AUTOLOAD file, and also for producing or modifying the site-specific
boot tape.
MODIFYING CONTENT OF AUTOLOAD FILE
The content of the boot tape is written to the AUTOLOAD file when the tape is
used to bootload the system, to ensure that the AUTOLOAD file always contains
the current copy of the Startup job stream.
On an AUTOLOAD boot, the Startup program and card images are read from the
AUTOLOAD file. At the end of processing each section after the $INITIALIZE
section, the Start~p program and current card images are re-written to the
AUTOLOAD file.
2-11
DH18-03
I
The Startup Console Editor can be used to modify the contents of memory (and
thus the AUTOLOAD file) while the Startup program is executing. Refer to
"Startup Console Editor" later in this section.
(
The XCAF (Extract Card Images From AUTOLOAD File) program can be used to
extract the various sections of the Startup job stream into user-defined
files. Refer to the GCOS 8 OS Service Routines manual for a description of the
XCAF program.
Another way of modifying the contents of the AUTOLOAD file is by responding YES
or PREPASS to the *REPLACE? question. Refer to "*REPLACE? Question" later in
this section.
MODIFYING CONTENT OF SITE-SPECIFIC BOOT TAPE
In the GCOS environment, the RSBT (Read Startup Boot Tape) program can be used
to convert the site-specific boot tape into a permanent file in standard system
format, for use as an updating master. The *C Editor (SCED) program can then
be used for updating this permanent file, after which the permanent file can be
converted back to the boot tape format via the WSBT (Write Startup Boot Tape)
program. Refer to the GCOS 8 OS Service Routines manual for descriptions of
the *C Editor, RSBT, and WSBT programS:--Note that although Time Sharing
techniques can be used instead of the *C Editor for updating the permanent
file, the job stream may include binary records which must be preserved.
If the Startup Console Editor has been used to modify the AUTOLOAD file, a new
site-specific boot tape can be built by using the XCAF (Extract Card Images
From AUTOLOAD File) program. Refer to "Startup Console Editor" later in this
section, and to the GCOS 8 OS Service Routines manual for a description of the
XCAF program.
STARTUP RESILIENCE
This feature allows the system to be rebooted following an interruption
requiring units to be deconfigured without changing switches and without
altering the Startup job stream to reflect the deconfiguration. This is
achieved by allowing Startup to release input/output controllers and by
allowing Startup to operate with "holes" in memory.
With this feature, systems can be split and split systems can be recombined
with minimal modification to the Startup job stream. (See the GCOS 8 OS System
Operating Techniques manual for a description of System Resiliency, i.e.,
splitting systems.)
Areas of defective memory are marked, hence can be assigned later when the
system is fully operational. This is preferable to releasing defective memory
(and all memory above it), thereby rendering it useless to the system until the
next boot.
The communication region word .CRIRL is used as follows:
(
2-12
DH18-03
Bit
0
)
=1
A mismatch exists between the size of the configured and
physical memory. POPM is required to perform a memory survey
during rollcall.
Bits 1-29
Reserved
Bit 32
=1
Input/output controller 3 released
Bit 33
=1
Input/output controller 2 released
Bit 34
=1
Input/output controller 1 released
Bit 35
=
Input/output controller 0 released
The following Startup messages are pertinent:
.Iyy-n NOT RESPONDING - YES TO CONTINUE OR R TO RETRY
where Iyy may be IMU, IMX, 10M, lOP, or lOX.
~\
This message indicates that the input/output controller specified as "n" did
not respond to a connect. An operator response of YES permits Startup to
continue with the specified input/output controller released. A NO response
aborts Startup. A RETRY response causes Startup to send another connect to the
same input/output controller to see if it will respond. This allows for a
delay in case firmware is not yet loaded into an IMU. After the IMU firmware
loading process has completed, the RETRY should be made and then the IMU should
respond. This message can be suppressed by using a $ ANSWER IOMERROR/NO
statement or a $ ANSWER IOMERROR/YES statement.
~
*MPC-n CHECK SWITCHES:
2{UP }
{DOWN}
5{UP }
{DOWN}
This message indicates that the PSI through which firmware for this MPC is
normally booted is connected to a released input/output controller. The
operator should confirm that the switches are in the correct positions to
enable the MPC to be booted with firmware. This message does not apply to
those MPCs having no switches; with these, the firmware handles the situation.
··XXXXXXXX ••••• xxx
This message is from either the $ CHAN or the $ UNIT statement. Messages of
this form are site-specific usually indicative of the action that should be
taken to move peripherals or media from a released input/output controller.
The operator should follow the specific site procedure •
• DEPRESS EOM WHEN READY TO CONTINUE
This message indicates that the operator is allowed time to follow instructions
given, then, upon completion, pressing EOM reenables activity.
2-13
DH18-03
*Iyy-n RELEASED
where Iyy may be IMU, IMX, IOM, lOP, or lOX.
(
This message indicates that Startup released the specified input/output
controller.
The following pertinent message is given by POPM:
MEMORY SURVEY:
nnn PAGES FOUND DEFECTIVE
where nnn is the total number of configured pages found to be nonexistent
during rollcall.
The control statements $ CHAN, $ UNIT, and $ BASE apply to Startup Resilience.
STARTUP-OPERATOR INTERFACE
The operator interface to Startup allows the site to select desired or
desirable approaches to several processing functions. For example, jobs in
process can be restarted or reentered in their entirety, statistical collection
can be resumed at the point of interruption or can begin anew, or mass storage
device content can be modified.
These alternatives are presented to the operator in the form of questions,
which are directed to the system console by the Startup program. Each of the
questions, the responses that can be made, and the ramifications of each
alternative are discussed below.
Note that by the time the question-and-answer sequence has begun, Startup has
read the $CONFIG section of the Startup job stream. Therefore, any questions
that have been answered via the $ ANSWER statement do not require an operator
response unless one is desired. (Refer to "$ ANSWER Statement" in Section 5
for a description of the $ ANSWER statement and a list of the Startup quest.ions
that can be answered.)
Startup Console Editor
The Startup console editor is an edit facility that allows the Startup job
stream to be edited from the console. The edited job stream becomes the
AUTOLOAD file, which may be used for subsequent boots. The console editor is
called into execution during Startup as follows:
Enter the word TEXT in response to any question asked by Startup, or
Enter the word TEXT in response to the ??? prompt after pressing the REQUEST
push button
2-14
DH18-03
The console edit function operates on the Startup BCD card images in memory.
The following commands are available within the editor:
(F)ind:/string/
- Search the deck image in a cyclic fashion, starting with
the current card image plus one and terminating on the
current card image.
(F)orward
- Forward space one card image.
(F)orward;n
- Forward space n card images.
(F)orwardj*
- Forward space to end of deck.
(P}rint
- Print the current card image.
(P)rint;n
- Print n card images starting at the current card image.
(P)rint;*
- Print all card images from the current card image to the
end of the deck.
(P)rint:/string/ - Print the card image containing the specified string.
)
(I)nsert
- Insert card images(s) after current card image.
IB
- Insert card images(s) before current card image.
(D)elete
- Delete the current card image.
(D)elete;n
- Delete n card images starting at the current card image.
(D)elete;*
- Delete all card images from the current card image to the
end of the deck.
(C)hange
- Change the current card image; delete current card image
and insert new card image(s).
(C)hange:/string1/:/string2/ - Change string1 with string2.
(B)ackup
- Backup to the start of the deck.
(B)ackupjn
- Backup n card images.
(R)ead
- Reinstate Startup (including BCD card images) from
AUTOLOAD file.
(Q)uit
- Exit from the editor.
PO
- SWitch the output stream to a printer.
CO
- Switch the output stream back to the console.
(V)er1ty
- Verify editor operators.
2-15
This is a toggle.
DH18-03
x
- Repeat the last command.
X;n
- Repeat the last command n times.
=
- Print the current card image number.
(T)ab x
- Set tab character to x (default is :).
(H)elp
- Print a summary of the editor commands.
(
Commands are denoted by their first letter with the exception of PO, CO, and
lB.
Multiple commands are permitted on a line. A command is delimited by the next
command or by a space. Leading spaces are tolerated. Any character is
accepted as a string delimiter.
If an error is encountered, the rest of the command line is ignored.
On card input (insert/replace), colon is interpreted as a tab character.
are set to: 8,16,32,73.
Tabs
On exit from the editor, an AUTO boot is automatically performed.
If the output stream is a printer, the print command prefixes card images with
their relative card number.
Binary card images (firmware) are treated in a totally transparent manner.
Output from the Print command may be terminated by hitting the request key.
MSU3380 And MSU3381 Disk Device Survey Messages
The MSU3380 and MSU3381 disk device survey verifies that the sector size and
device type of each MSU3380 and MSU3381 device configured in the Startup job
stream agrees with the actual hardware configuration. Unlike the tape survey,
the MSU3380 and MSU3381 disk survey is done in the $CONFIG section. The
input/output controllers with MSU3380 orMSU3381 capability interrogate each
device and pass this information to the Startup program for comparison. Errors
are reported in the following mesages:
DEVICE TYPE MISMATCH ON i-ccc-dd
CONFIG = type, IPC = type
DEVICE RELEASED
where:
type = device type, such a'S MSC1A, MSC1B, MSD1A, or MSD1B
or UNKNWN
IPC
= Integrated Programmable Controller
2-16
DH18-03
This message appears if the $CONFIG device type doesn't match the IPC
device type, for example,
CONFIG
= MSC1A,
IPC
= MSC1B.
In this case, Startup aborts at the end of $CONFIG Section processing.
If IPC = UNKNWN, Startup does not abort.
DEVICE FORMAT MISMATCH ON i-ccc-dd
CONFIG = type, IPC = UNFMTD
DEVICE RELEASED
This message appears for unformatted MSU3380 and MSU3381 devices. If the
device is removable (RMVBL on the input/output controller statement), it
will be marked as a stranger device. If it is not removable, the
following message will appear and Startup will abort at the end of
$CONFIG processing.
UNFORMATTED DEVICE MUST BE "RMVBL"
DEVICE STATUS MISMATCH ON i-ccc-dd
CONFIG = type, IPC = NOTONL
DEVICE RELEASED
This message appears if the device is not online, i.e., powered off, not
ready, or not there.
)
Startup Questions
Questions that would otherwise be directed to the system console can be
answered in two other ways. Questions can be answered by using the $ ANSWER
statement in the $CONFIG section of the Startup job stream, as described in
"$ ANSWER Statement" in Section 5. In addition, any question that may be
issued several times during the bootload procedure can be answered once by the
operator, by appending an asterisk (.) to the first answer given to the
specific question. Subsequently, issuance of that question is bypassed and the
answer given to the first question is applied. For example, if three MPCs are
to be bootloaded, the operator can respond YES. to the first .xxxMPC ON iccc
BOOTLOAD? question to answer this question for the second and third MPCs.
(Refer to ".PROCESS $ READIN? Question" later in this section.)
While the sequence in which questions are issued to the console frequently is
the same, some operator responses can cause the sequence to vary from boot load
to bootload. Therefore, the sequence in which the Startup questions are
described in this section may be different from that in which they are issued
to the console. In addition, the following informational message may be issued
prior to any of these questions being displayed:
• WARNING - SCU IN MANUAL MODE
The ope~ator must decide whether to continue processing in this mode or to
reset the SCU.
2-17
DH18-03
I
The general sequence of Startup questions is as follows:
I
(
*REPLACE?
*CHANGE?
*RETAIN CONFIGURATION?
*RESTART?
*SISOUT RECOVERY?
*SCF CONTINUATION?
*DATE?
*TlME?
*DATE mmddyy TIME hh.mmm
*CHANGE SYSTEM CONTROLLER CLOCK?
*CHANGE DATE?
*CHANGE TIME?
*ENTER TIME OR ENTER A CORRECTION FACTOR?
*CHANGE > 5 MIN, YES TO ACCEPT?
*INITIALIZE?
*EDIT?
*SYSTEM SCHEDULER CLEAR?
One or more additional (secondary) questions may be issued during the
initialization (*INITIALIZE?) and editing (*EDIT?) phases of System Startup.
These questions are detailed below. (Note that use of the asterisk by the
operator to answer subsequent questions is effective with these secondary
questions.)
Throughout this section it must be understood that an end-of-message (EOM)
response to a question is equivalent to a NO response.
It is recommended that the operator respond NO to a question during the Startup
question-and-answer sequence when the correct answer to the question is not
apparent. The effects of a NO response are less severe than those of a YES
response, which may have undesirable results. For example, a YES response to
the *INITIALIZE? question can result in a time-consuming re-editing process
involving all configured mass storage devices.
*REPLACE? Question
The *REPLACE? question allows the operator to selectively replace one or more
sections of the Startup job stream on the AUTOLOAD file.
A YES response results in the replacement of one or more sections via the card
reader. If the replacement section(s) is (are) not in the card reader at the
time the YES response is made, the console message:
*BOOTLOAD DEVICE ERROR icccdd: xxxxxx OPERATE WHEN READY
is issued (where i = IOM/IOX/IOP/IMU/IMX number, ccc
device number, and xxxxxx = error status).
2-18
= channel
number, dd
=
DH18-03
If more than one section is being replaced, the sections must be loaded by
their order of appearance in the Startup job stream. For example, if the
$CONFIG and $INITIALIZE sections are being replaced, the $INITIALIZE section
cannot precede the $CONFIG section. If sections are nonsequential, the
message:
-EXPECT s ••• s ccccc FIX TYPE GO
is issued to the console (where s ••• s = name of the section that is out of
sequence and ccccc = image of the last statement read). The operator can enter
BOOT via the system console to halt the bootload, place the Startup sections in
the correct sequence, and initiate a warm boot.
The last two statements in the Startup job stream must be ---EOF statements
(regardless of the number of sections being replaced). If the job stream does
not conclude with two ---EOF statements, the message BOOTLOAD DEVICE ERROR is
issued to the system console.
Note that the message:
-NEED READER PORT, Iyy, CHANNEL {PICC }
{PICCe}
)
may be issued during this procedure. An operator response is required to
inform Startup which card reader is being used to load the new section(s). The
response is in the form piccc (where p = IOMlIOX/IOP/lMU/IMX port number, i =
IOM/IOX/IOP/lMU/IMX number, and ccc = channel number (0 - 127) or cc = channel
number (0 - 63».
A NO response to the -REPLACE? question indicates that no changes are desired
to the Startup job stream that resides on the site-customized boot tape.
A PREPASS response to the -REPLACE? question permits the later use of the
Startup Console Editor to make changes in the $CONFIG, $EDIT, $FILES, and
$PATCH sections.
After the PREPASS response has been entered, the MASK section of the Startup
job stream is read and processed normally. All of the $CONFIG statements are
read from tape. After they have all been read from tape, they are processed as
card images being read from memory. If an error is encountered, or if Startup
aborts, the Startup Console Editor can be called and used to make corrections.
See "Startup Console Editor", earlier in this section. Each time the Startup
Console Editor is exited, the first section (MASK or $CONFIG) is reprocessed
with the card images being made available from memory.
)
2-19
DH18-03
When the $CONFIG section is error free, Startup proceeds to read and process
the $INITIALIZE section from tape in the normal manner. The $EDIT, $FILES, and
$PATCH sections are read from the tape without being processed •. After these
sections have been read in, processing resumes at the $EDIT section with the
card images being read from memory. If an error is encountered, all of the
card images are available in memory and corrections can be made using the
Startup Console Editor. After the $PATCH section has been successfully
processed, card images are once again read and processed directly from the
tape. If a $LOAD section is present on tape, it is read and processed directly
from the tape without "prepass" intervention.
I
(
The replacement procedure can also be initiated via a REPL response to the
.BOOT SOURCE: AUTO OR REPL? question.
-CHANGE? Question
If any $ ANSWER statements are included in the $CONFIG section of the Startup
job stream, the .CHANGE? question is issued to allow the operator to override
or accept all of the $ ANSWER statements.
A YES response indicates that the operator desires to override $ ANSWER
statement content. All $ ANSWER statements are ignored for the duration of
this bootload. (Note, however, that this override applies only to the current
bootload and that the $ ANSWER statements are reinstated during the next
bootload.) The operator then must answer all bootload questions via the system
console, regardless of the bootload media (i.e., mass storage, magnetic tape,
or punched cards).
A NO response indicates that all $ ANSWER statement content is acceptable.
Startup executes the response(s) from the $ ANSWER statement(s).
-RETAIN CONFIGURATION? Question
-.------
The .RETAIN CONFIGURATION? question allows the operator to request that the
system attempt to retain the status of the hardware configuration at the time
the system was last interrupted.
A YES response causes the system to attempt to recover the "assigned/dedicated
/released" state of each device.
A NO response causes each device to be returned to its initial state as defined
in the Startup job stream. A NO response should be given if any Test and
Diagnostio (T&D) jobs were running in the system prior to the last system
interrupt. The T&D jobs may have changed the state of various hardware
components. These states would be restored on the next boot and could cause
problems in the system.
A NO response should also be given whenever a YES response was previously
attempted and problems, especially hardware configuration problems, were
encountered in the system.
2-20
DH18-03
(
~
-RESTART? Question
~
~
The operator's answer (YES or NO) to the -RESTART? question determines whether
or not the system will attempt to restart - near the point of interruption all jobs/activities that were in progress at the time of the system failure. A
response of NO causes the system be cleared of all active jobs.
The response to the -RESTART? question has an impact on the response to the
-SYSTEM SCHEDULER CLEAR? question. Startup does not permit a YES response to
both questions. If the operator responds YES to -RESTART?, Startup
automatically provides a NO response to the -SYSTEM SCHEDULER CLEAR? question.
(The effect of YES responses to both questions would be to release job-related
system files that are needed for restart of those jobs.)
A YES response to the -RESTART? question
time of the failure to be restarted from
that existed prior to the failure). The
restart process for jobs that are in the
of restart:
\
)
allows all jobs in progress at the
a known condition (i.e., a condition
following briefly identifies the
various processing phases at the time
o
Jobs that were in allocation, execution, or termination will be restarted
when the operator enters the RUN REST console verb. The SNUMBs of jobs
that cannot be restarted are identified in a system console message.
o
Jobs that were in the input or scheduling phases, but not yet cataloged
on the System Scheduler's SSFILE file, may be automatically restarted if
the jobs were saved in the SD.INJ table. Jobs that cannot be restarted
are identified in a list of job numbers (SNUMBs) following the console
message JOBS THAT SYS SCHED CANNOT RECOVER ARE.
o The system scheduling function will be resumed when the operator enters
the JRUN REST console verb. Jobs that were cataloged on the SSFILE file,
but not in allocation, execution, or termination, are restarted.
Once restart has been permitted at the system level, individual program restart
procedures are invoked for each job at the user level.
A NO response to the -RESTART? question causes all jobs to be restarted from
the catalog entry on the SSFILE file when the operator subsequently enters the
JRUN REST console verb.
A NO response ensures that the -SYSTEM SCHEDULER CLEAR? question will be issued
later during the question-and-answer sequence.
-SYSOUT RECOVERY? Question
The question -SYSOUT RECOVERY? permits system output to be recovered regardless
of the answer to the -RESTART? question.
2-21
DH18-03
A YES response speoifies that all job output and job output speoia1s known to
system output are to be reoovered. Blinks marked in error are marked as
unusable. A ,NO response speoifies that none of the above output is to be
reooveredand' 'that blinks marked in error are not to be marked as unusable.
NOTE: Blinks for jobs in exeoution are either kept or released depending on the
response to the *RESTART question.
To inorease system output reliability, the segments shown in the following list
are oleanpointed if the $ INFO CLENPT statement is ino1uded in the $CONFIG
seotion of the Startup job stream. The segments are:
DP.JOT
DP.JOS
DP.SBT
DP.BDI
-
Job Output Table
Job Output Speoia1s
SYSOUT Blink Table
Baokdoor Information
DP.JOT and DP.SBT c1eanpoints are taken when a new job oompletes queue entry
and blinks and jobs are released. DP.JOT and DP.BDI oleanpoin"ts are taken when
a baokdoor job queue entry is prooessed and when baokdoor files and jobs are
released. DP.JOS oleanpoints are taken eaoh time a speoial is added to or
removed from that segment. Also, DP.SBT is oleanpointed in BRT6 upon aotivity
termination if the job has oaused modifioation to that segment •
• SCF CONTINUATION? Question
The .SCF CONTINUATION? question allows the operator to oontinue or restart data
oolleotion on the Statistioa1 Col1eotion File (SCF).
A YES response results in data oolleotion resuming from the point of
interruption.
A NO response results in SCF data oolleotion beginning anew. If the SCF
resides on mass storage, this response results in the olearing of all
previously written information. This information oannot be reoovered. If the
SCF resides on magnetic tape, restart does not affeot information written to
the SCF. The tape oontaining the SCF must be rewound and a new tape mounted
before oollection is resumed. Note that rewinding of the tape is automatioa11y
effeoted if a site-option patch is applied to the .MPOPM module (Memory
Allocation program). (Refer to "Memory Allocator Options" in Section 5 for the
format of this site-option patch to .MPOPM.)
If a system failure prevents the Master Mode Dump (.MDUMP) program from closing
the SCF, system restart will not prooeed. The .MPOPM module aborts and the
existing SCF is not closed. The system must be rebooted and the operator must
respond NO to the *SCF CONTINUATION? message. Data colleotion then resumes on
a new SCF.
2-22
DH18-03
(
.SYSTEM CONTROLLER CLOCK AND .CRDAT MISMATCH Message
~
v
This message is issued when Startup detects a difference in the date calculated
from the system controller clock and the date recovered from .CRDAT on an
autoboot with CHANGE? NO. Startup also issues this message if a difference of
one minute or more is determined when the time calculated from the system
controller clock is compared to time calculated from .CRDAT+1 and .CRDAT+2.
The *DATE question is output and the response values input are used to set the
system controller clock and .CRDAT.
*DATE mmddyy TIME hh.mmm Information Message
This message informs the operator of the date/time, and is issued when the
"*CHANGE?" question is answered YES •
• CHANGE SYSTEM CONTROLLER CLOCK? Question
The *CHANGE? question was answered YES. A YES response causes the .CHANGE
DATE? and .CHANGE TIME? questions to be issued •
• CHANGE DATE? Question
The .CHANGE? question was answered YES.
question to be issued.
A YES response causes the *DATE?
)
·CHANGE TIME? Question
The *CHANGE? question was answered YES. A YES response causes the *ENTER TIME
OR ENTER A CORRECTION FACTOR? question to be issued •
• ENTER TIME OR ENTER A CORRECTION FACTOR? Question
If the *CHANGE TIME? question was answered YES, the operator can issue one of
two responses:
1. Enter the time in one of the formats of the *TIME? question (e.g.,
01:20).
2. Enter a time correction factor using the format of the *TIME? question,
except that a plus (+) or minus (-) sign must precede the correction
factor. This allows the operator to correct or change the time of day in
increments (e.g., -01:00 would be entered to change a system time to
standard time from daylight savings time).
2-23
DH18-03
*DATE? Question
(
Startup detected one of the following conditions:
1. The clock contains a value earlier than the Startup assembly date.
2. The clock contains a value greater than 100 years.
3. A YES response was given to the -CHANGE DATE? question.
Enter the current date (i.e., the date of this bootload) via the system console
in the mmddyy format (where mm = month, dd = day, and yy = year). Startup
validates the date entered (e.g., non-numeric date, invalid month or day). If
the date entered is invalid, the -DATE? question is reissued.
*TIME? Question
Startup detected one of the following conditions:
1. The clock contains a value earlier than the Startup assembly date.
2. The clock contains a value greater than 100 years.
Enter the current time (i.e., the time of this bootload) via the system
console. Startup validates the entry (e.g., the time cannot exceed 2400 hours
or contain non-numeric characters). If the time is invalid, the -TIME?
question is reissued.
The time can be entered in one of three formats:
o
- where hh = 00-23 hours and mm = 00-59 minutes
hh:mm
o hht or hh.t - where hh
0-9)
*CHANGE
>5
= 00-23
hours and t
= tenths
of one hour (i.e.,
MIN, YES TO ACCEPT? Question
The operator attempted to change the clock time by more than 5 minutes, thus,
this message gives the operator the opportunity to reenter the ,time.
A YES response causes the system to accept the new time. A NO response causes
the *ENTER TIME OR ENTER A CORRECTION FACTOR? to be reissued.
*INI~IALIZE?
Question
The *INITIALIZE? question allows mass storage devices to be reformatted or
"initialized ft • The initialization process provides a clean basis for
re-establishing tables, pointers, and files on the mass storage device. It is
recommended that initialization be performed on each cold boot. (Refer to
"Cold Boot" earlier in this section for additional information.)
2-24
DH18-03
~
~\
v'
Initialization destroys existing tables and pointers on the device prior to
rebuilding them. The rebuilding process draws upon information in main memory
and included in the $INITIALIZE section of the Startup job stream.
Among the tables rebuilt are those that compose the device header and define
the physical attributes of the device in terms of usable space (i.e., that
space which has been allocated or which is available for allocation) and
defective space. (Refer to the GCOS 8 as System Operating Teohniques manual
for device header information.)
A console message may be issued, warning of allocation table problems following
the initialization process. The message:
ST1 AND SMCDUP INITED BUT NOT ALL OTHERS, FILE SPACE WILL BE LOST
is issued if device ST1, containing the System Master Catalog (SMe) , and the
device containing the duplicate SHC are initialized, but one or more other
permanent mass storage devices are not initialized. (This condition may arise
as the result of omitting $ INIT statements in the $INITIALIZE section for all
permanent mass storage devices, or as the result of selective initialization
via a PARTIAL response to the -INITIALIZE? question.)
While allocation tables on the devices that were not initialized continue to
identify allocated space on those devices, the FMS catalog structure no longer
reflects the assigned space. Therefore, the space is lost to the system (i.e.,
it is unassignable). To correct this condition, all permanent mass storage
devices must be initialized.
)
While data files are not cleared from the initialized mass storage device,
destruction (clearing) of the pointers and tables during the initialization
process makes it impossible to subsequently access these files. Following
device initialization, any write operation to that device overwrites the
existing data. Therefore, any data files that are to be retained must be saved
on magnetic tape prior to device initialization and then restored to the device
following initialization. (Refer to the GCOS 8 as File Management Supervisor
manual for save and restore information.)
In addition to the reformatting process, Startup performs several other
functions during initialization including:
1. Volume sets, and their characteristics, can be defined. Volume sets are
multi-volume structured removable devices. Refer to "$ VSET Statement"
and "$ VOPT Statement" in Section 5.
2. Mass storage, magnetic tape, and unit record MPCs are checked to
determine if they have been boot loaded with firmware. If they have not,
the operator is given the option of bootloading the controllers. MPC
verification and bootloading is bypassed during a fast boot. (Refer to
"MPC Bootloading" for additional information.)
2-25
DH18-03
I
3. Printer character set and VFC images are loaded from the Startup
programts internal copy (i.e., buffer) of the PRINTIMAGE file for all
qualifying, configured printers. (Note that if a print image is added to
the PRINTIMAGE file on mass storage via the rVIM program, the internal
Startup copy does not contain that image.) As with MPC bootloading,
loading of character set and VFC images is bypassed during a fast boot.
(Refer to nCharacter Set And VFC Image Loading n in this section for
additional information.)
4. Permanent mass storage devices are verified by comparing each mass
storage device label with information in the in-memory device name
table. The device name table is created from $CONFIG section information
and from the device directory, which occupies several contiguous llinks
in the SMC on device ST1. (Refer to npermanent Mass Storage Device
Verification n later in this section for additional information.)
5. All controller-driven (such as an MPC) magnetic tape handlers are
surveyed. The density and track-type attributes of each configured
device are compared with information specified in the $CONFIG section.
If the comparison fails, the device is unconditionally released (i.e.,
without querying the operator). (Refer to "Magnetic Tape Handler Surveyn
in this section for additional information.)
OPERATOR CONTROLS DURING INITIALIZATION
The initialization function is controlled to a great extent by the operator,
who can enter one of several responses to the -INITIALIZE? question.
Therefore, the operator must be aware of the consequences of each response.
The following describes the ramifications of the NO, YES, TOTAL, and PARTIAL
responses to the -INITIALIZE? question.
Response
Description of Initialization Process
NO
A response of NO indicates that initialization is not desired.
All mass storage device information is to remain intact and
mass storage information previously defined in the $INITIALIZE
section of Startup still is valid. However, Startup performs
all five other functions that accompany initialization (i.e.,
volume set definition, MPC verification and bootloading,
character set and VFe image loading, mass storage device
verification, and magnetic tape handler surveying).
YES or TOTAL
A response of YES or TOTAL initializes all configured mass
storage devices. Information included on the $ INIT
statements in the $INITIALIZE section of Startup is executed
to recreate tables and pointers on mass storage devices. A
response of YES or TOTAL automatically provides a YES answer
to all MPC-related questions. (Refer to "MPC Bootloading ll in
this section for additional information.)
I
2-26
DH18-03
(
Response
Description of Initialization Process
A response of TOTAL: (1) provides a YES answer to the -EDIT?
question; (2) provides a NO answer to the -FORMAT/LABEL
QUESTIONS? question; and (3) results in execution of $EDIT
section content. Startup assumes that all mass storage
devices were previously formatted. Under these circumstances,
a $ INIT statement must be included in the$INITIALIZE section
of Startup for each mass storage device.
It is recommended that the bootload medium be magnetic tape
when a YES or TOTAL response is made. This ensures that the
AUTOLOAD file will contain current information.
PARTIAL
A response of PARTIAL allows the operator to selectively
initialize mass storage devices on a device-by-device basis
(as opposed to a YES or TOTAL response, which initializes all
devices). This response also provides an audit trail of the
initialization process, which can prove valuable when
debugging initialization problems.
If the operator responds PARTIAL, one of the following
additional (secondary) questions is issued to the console.
\
I
)
-INIT DEVICE.ddd?
-INIT RMVBL DEVICE ddd?
-INIT SHARED DEVICE ddd?
Each of these messages queries the operator as to whether mass
storage device ddd (where ddd = logical device name) is to be
initialized. In the message:
-INIT RMVBL DEVICE ddd?
device ddd is configured as a removable (RMVBL) device.
the message:
In
-INIT SHARED DEVICE ddd?
device ddd is configured as a shared device; i.e., shared with
NPS. See ft$ Shared Statement ft in Section 5.
A response of NO to these questions indicates that device ddd
is not to be initialized (except for any automatic secondary
initialization as described below). A response of YES
indicates that device ddd is to be initialized. In addition,
subsequent questions are issued regarding mass storage device
formatting. (Refer to ft-FORMAT/LABEL QUESTIONS? Questionft in
this section for additional information.)
2-27
DH18-03
Response
Description of Initialization
Proce~~
__ _ ,--_.- - - - -.' .._--
~
--- -
The system allows the operator to respond SECONDARY to one of
the secondary questions following a PARTIAL response when
circumstances may require an operator-initiated secondary
initialization (e.g., the device encounters a temporary
descriptor table (TDT) overflow condition). Otherwise, under
normal operating conditions, secondary initialization is
automatically performed as follows:
1. During System Startup, when the NIAST (No In-Memory
Available Space Table) option is in effect, a secondary
initialization is performed automatically for each
permanent device whose last operating mode was not NIAST.
This action establishes a current Available Space Table
(AST) on the device. This automatic secondary
initialization occurs for both shared and unshared
permanent devices. It is not dependent on the response to
the INITIALIZE? question or its subsidiary -INIT ••• ddd?
questions. (The AST resided in memory during non-NIAST
operation; therefore, either no AST exists on the device,
or it is obsolete.)
2. For removable mass storage devices in the NIAST mode, a
secondary initialization is performed automatically
whenever a structured disk pack is mounted at Startup. If
it is mounted later, the AST rebuilding occurs during
system operation. This action is not dependent on the
response to the INITIALIZE? question or its subsidiary
-INIT ••• ddd? questions.
I
3. When processing D, 0, A, L, and Y data (YES response to
PROCESS DIRECTORY CARD FOR DEVICE ddd? message) on devices
whose last operating mode was NIAST, at least a secondary
initialization is required.
A SECONDARY response to one of the secondary questions
following a PARTIAL response is logically ignored when NIAST
mode is not in effect.
In contrast to an initialization, a secondary initialization
releases no permanent file space and uses the device
allocation unit table on the device to rebuild a current AST
on the device. For permanent devices, the empty TDT is als,o
rebuilt., This action synchronizes both tables containing mass
storage space allocation information (i.e., the device
allocation unit table and the AST) and, for permanent devices,
returns all temporary file space to the system. Note that
temporary f~les do not exist on removable devices.
NOTE: Recovery may not be performed on protected files if a
secondary initialization is performed.
2-28
DH18-03
(
MFC BOOTLOADING (DPS 8 AND DPS 8000 OBLY)
\
)
MPC firmware must be functional to perform system startup. Separate firmware
data decks are used to boatload the magnetic tape and mass storage
controllers. These deck images can reside on mass storage, magnetic tape, or
punched cards. In addition, the $INITIALIZE section must contain the MPC
boot load (MPCB) program deck image, which permits loading of the data decks.
(Refer to "$INITIALIZE Section" in Section 1 for additional information.)
Several console questions may be issued by the MPCB program to ensure that all
MPC firmware is loaded and operational:
o
Startup automatically provides a YES answer to all MPC-related questions
if the operator responds YES or TOTAL to the -INITIALIZE? question. As a
result, all MPCs are bootloaded from firmware on the deckfile.
If firmware for a specific device type is absent from the deckfile,
Startup bypasses bootloading of the MPC in question and completes the
bootloading process for all other MPCs. All devices associated with the
bypassed MPC are released during the device rollcall function. Messages
are issued during the rollcall function to identify released devices. No
message is issued when MPC bootloading is bypassed.
To subsequently bootload the MPC while the system is operational, the
operator can call the MOLTS subsystem of the Total Online Test System
(TOLTS) via the console entry:
TEST MPC icc
\
)
(where i = 10M number and cc = channel number). The console entry ASGN
iccdd then can be used to reassign each released device to the system
(where i = 10M number, cc = channel number, and dd = device number).
Use of the PARTIAL response to the .INITIALIZE? question during a cold
boot can prevent the bypass of MPC bootloading. The PARTIAL response
ensures that all bootloading occurs and that all configured devices are
activated.
o
Startup automatically provides a NO answer to all MPC-related questions
if the operator responds NO to the .INITIALIZE? question and if Startup
determines that all MPCs are loaded with firmware.
The following question is issued to the console if the operator responds
NO to the *INITIALIZE? question and if Startup determines that one or
more MPCs are not loaded with firmware or are not operational.
*xxxMPC ON icc NOT RESPONDING PROPERLY
TYPE (B)OOT, (S)KIP, OR (R)ETRY
2-29
DH18-03
The following console entries can be made to correct or to circumvent the
condition:
B - Load firmware into MPC xxx from the deckfile.
recommended response.
This is the
S - Bypass (skip) bootloading MPC xxx. All devices associated with this
MPC are released during the device rollcall function. To
subsequently bootload the MPC and reassign released devices, enter
the TEST MPC icc and ASGN iccdd console entries as previously
described.
R - Retry the MPC firmware verification function. If Startup again
determines that the firmware is not loaded or that the MPC is not
operational, the preceding message is reissued.
o
If the operator responds PARTIAL to the *INITIALIZE? question, one or
more of the following questions is issued to the console:
*MPC ON icc PRE-INITIALIZE?
*xxxMPC ON icc BOOTLOAD SYS ID NAME "y ••• y" REV.zz?
*xxxMPC ON icc APPEARS OK, BOOTLOAD?
The PRE-INITIALIZE? question is issued only if a DAU Disk Controller is
recognized, and asks if the operator wishes to run concurrent self
tests. Answering YES saves time (20 seconds per device), and also
requires a YES answer to the BOOTLOAD? question because self tests
destroy firmware. Answering NO to the PRE-INITIALIZE? question will add
time to the bootloading of firmware if YES is entered in response to the
BOOTLOAD? query later on.
The *xxxMPC on icc BOOTLOAD SYS ID NAME "y ••• y" REV.zz? question is
issued for each configured MPC. A YES response results in bootloading of
MPC xxx with firmware revision level zz from the deckfile. A NO response
bypasses bootloading of MPC xxx. To subsequently bootload the MPC and
reassign released devices, enter the TEST MPC icc and ASGN iccdd console
entries as previously described.
Only the *xxxMPC ON icc APPEARS OK, BOOTLOAD? question is issued if
firmware does not exist in non shared MPC xxx. AYES response results in
bootloading of MPC xxx from the deckfile. A NO response bypasses
bootloading of MPC xxx. If the MPC is not bootloaded, all devices
associated with the MPC are released during the device rollcall
function. To subsequently bootload the MPC and reassign released
devices, enter the TEST MPC icc and ASGN iccdd console entries as
previously described.
2-30
DH18-03
c
PERMANENT MASS STORAGE DEVICE VERIFICATION
All permanent mass storage devices - especially device ST1 and the device that
is to contain the (optional) duplicate System Master Catalog (SMC) - are
verified to ensure that logical device labels are accurate. Any inconsistency
between logical device label information and system control data in the device
directory in the System ttaster Catalog causes a console message to be issued.
The message will be:
-EXPECTED PACK NAME xxx FOUND yyy YES TO ACCEPT CHANGE
or:
-ddd EXPECTED PACK NUMBER xxx FOUND yyy YES TO ACCEPT CHANGE
where ddd = logical device name. (Refer to "Verification Of All Permanent Mass
Storage Devices" in this section for a description of these messages and
operator responses.)
Tables used during the verification process include the in-memory device name
table, created from $CONFIG section data, and the device directory, which
occupies several contiguous llinks in the SMC on device ST1.
Normally, this verification procedure is performed with no errors encountered
and Startup continues on to the magnetic tape handler survey procedure.
\)
ST1 And SMCDUP Device Name Verification
/
Startup determines whether the correct disk packs are mounted on device ST1 and
on the device containing the duplicate SMC. If the comparison of logical
device label and device name table information fails, the console message:
-ddd ST1/SMCDUP DEVICE WRONG PACK MOUNTED
is issued (where ddd
= logical
device name).
To correct the condition, power off the device and visually verify the pack
serial number, which is stamped on the pack by the manufacturer. If the serial
number does not identify the correct disk pack, mount the proper pack on device
ddd. It is recommended that the system be restarted via a warm boot to ensure
that any erroneous in-memory tables are corrected and rebuilt.
SMCDUP Device And Option Verification
Startup determines whether the device for which the SMCDUP option was specified
actually contains the duplicate SMC. If the device does not contain the
duplicate SMC, Startup aborts. The console message:
-ddd CAN'T CHANGE SMCDUP WITHOUT INIT
2-31
DH18-03
is issued (where ddd = logical device name). Remove the $ INFO ••• SMCDUP
statement, which identifies device ddd, from the $CONFIG section of the Startup
job stream and perform a warm boot to restart the system. (As a result of
removing the $ INFO ••• SMCDUP statement, a duplicate SMC is not created. To
provide a duplicate SMC, the device on which the duplicate is to reside must be
defined on the $ INFO ••• SMCDUP statement and the operator must respond YES to
the *INITIALIZE? and .EDIT? questions during the bootload.)
(
Verification Of All Permanent Mass Storage Devices
Following the preceding verification process, which specifically applies to
device ST1 and to the device that contains the duplicate SMC, Startup performs
a series of tests that applies to .all permanent mass storage devices. As in
the previous verification functions, logical device label information is
compared with data contained in the device name table and in the device
directory.
The following verification sequence is performed for each device:
1. If a Startup statement (e.g., $ FILDEF or $ GCOSFIL) includes a logical
device name (ddd) not defined on a $ Iyy statement, the console message:
.DEVICE ddd UNDEFINED
is issued and Startup aborts. While this message also applies to
magnetic tape and unit record devices, it is more often associated with
mass storage devices.
2. If Startup determines that a device is offline and cannot be accessed,
the following console message is issued:
.DISK PACK ERROR icccdd s ••• s EOM TO COtITINUE
THE DEVICE
'RLSE' TO RELEASE
where:
i
IOM/IOX/IOP/IMU/IMX number
ccc
- channel number
dd
- device number
s ••• s - status message).
The operator can (1) release the device via the console entry RLSE or
(2) correct the error defined in the status message. The EOM push button
on the system console is then pressed to retry the verification function.
If the released device contains any system files, the system aborts.
NOTE: If a $ INFO ••• RLSDSK statement is present in the $CONFIG section of
the Startup job stream, the RLSE answer is automatically applied to
the preceding message. The device is automatically released during
a fast boot and no message is issued.
(
2-32
DH18-03
3. Startup compares the device name (i.e., pack name) contained in the
)
logical device label with the device name contained on the $ Iyy
statement for the device. If the comparison fails, the console message:
-EXPECTED PACK NAME xxx FOUND yyy YES TO ACCEPT CHANGE
is issued (where xxx = device name contained on the $ Iyy statement and
yyy = device name contained in the logical device label).
The operator has the following options:
a.
Power off the device and visually inspect the pack name, which
normally is written by site operations personnel on an external pack
label. If the wrong pack is mounted, mount the correct pack and
perform a warm boot to restart the system.
b.
Respond YES to the message. As a result, Startup writes the pack
name, contained in the logical device label (yyy) , into the device
name table and continues with the verification process.
c.
Respond NO to the message. Startup aborts. Rebuild the logical
device label via the procedure specified under "2."
4. Startup compares the pack serial number contained in the logical device
label with the pack serial number contained in the device directory. If
the comparison fails, the console message:
-ddd EXPECTED PACK NUMBER xxxxx FOUND yyyyy YES TO ACCEPT CHANGE
)
is issued (where ddd = logical device name, xxxxx = pack serial number in
the device directory, and yyyyy = pack serial number in the logical
device label). The operator has the following options:
a.
Power off the device and visually inspect the pack serial number
stamped on the pack by the manufacturer. If the pack serial number
is not the one identified in the console message, mount the correct
pack and perform a warm boot to restart the system.
b.
Respond YES to the message. As a result, Startup writes the pack
serial number, contained in the logical device label (yyyyy), into
the device directory and continues with the verification process.
c.
Respond NO to the message. Startup aborts.
via the procedure specified under "2."
Rebuild the pack label
5. If Startup encounters a device whose status has been changed from
removable (RMVBL) to permanent (PERM), the console message:
-ddd PRIOR DEVICE STATUS WAS RMVBL CHANGED TO PERM YES TO CONTINUE
is issued to verify that the status change is correct (where ddd =
logical device name). The following two console entries are valid:
2-33
DH18-03
YES - Startup changes the device status from removable to permanent on
the device directory and continues the verification procedure.
(Once the device status has been changed from removable to
permanent, the only means of returning the status to removable is
to initialize and edit the device during a bootload procedure.)
NO
- Startup aborts. Modify the $ Iyy statement to reflect the correct
status for device ddd. Perfor.m a warm boot to restart the system.
6. Startup performs four tests, comparing the logical device label
information to data in the device directory, to determine if:
a. A $ SHARED statement indicates that the device is shared with NPS.
b. A $ INIT ••• CAT statement enables FMS creation of catalogs on the
device.
c. A $ Iyy ••• NOFMS statement disables FMS creation of catalogs or files
on the device.
d. The device status was changed from permanent to removable via the
$ Iyy statement.
If any of the preceding tests fail, the following console message is
issued and Startup aborts:
*ddd CAN'T CHANGE DEVICE STATUS FROM xxx TO NONxxx
where:
ddd - logical device name
xxx - NPS, FMS, CATALOGABLE, or PERM/RMVBL
Correct the error condition by (1) inspecting the $ SHARED, $ INIT, and
$ Iyy statements for accuracy, or (2) initializing device ddd or the
entire mass storage subsystem during a cold boot.
7. Startup aborts if it does not encounter a $ INFO ••• SMCDUP statement, but
does encounter a device whose label indicates that the device was
initialized as the device on which the duplicate SMC is to reside. The
following console message is issued:
*ddd CAN'T CHANGE SMCDUP WITHOUT INIT
where ddd = logical device name. Insert a $ INFO ••• SMCDUP statement,
which identifies the correct device, into the $CONFIG section of the
Startup job stream and perform a warm boot to restart the system.
2-34
DH18-03
c
MAGNETIC TAPE HANDLER SURVEY
The magnetic tape handler survey is designed to verify the density (bpi) and
track type (seven or nine) attributes of each configured magnetic tape
handler. Each magnetic-tape-oriented controller, such as an MPC or IPC,
contains an internal table that reflects this information for each tape handler
associated with the controller. Startup compares the controller table
information with data specified in the $CONFIG section of the Startup job
stream.
If controller table and $CONFIG section unit number information do not match,
the tape handler is released by Startup. The console message:
-UNIT NUMBER MISMATCH ON icccdd: CONFIG
is issued (where i = Iyy number, ccc
conflicting unit numbers).
= nn,
= channel
MPC
= nn
number, dd
DEVICE RELEASED
= device
number, nn
=
If controller table and $CONFIG section density information do not match, the
tape unit will remain assigned and the following console message is issued:
-DENSITY MISMATCH ON icccdd: CONFIG
= ,
MPC
= ,
ASSIGNED
=
(where i = same as above, ccc = same as above, dd = same as above, cdens =
configured density, mdens = MPC density, adens = assigned density). No
operator action is required. The operator subsequently can reassign the
released device by correcting the $CONFIG section data and performing a warm
boot.
If an error is encountered during the magnetic tape handler survey while
bootloading from magnetic tape, the console message:
-TAPE ERROR, icccdd s ••• s MAY BE RECOVERABLE FIX, TYPE GO OR STOP OR TYPE
CONT FOR CONTINUE
is issued (where s ••• s
= error
status condition).
The operator can:
1. Correct the error and enter GO via the system console to resume the
bootload;
2. Enter STOP via the system console to abort Startup; or
3. Enter CONT to release all magnetic tape handlers configured on this MPC
subsystem and to resume the bootload. (To subsequently bootload the MPC
and reassign released devices, enter TEST MPC iecc and ASGN icccdd as
described under "MPC Bootloading" in this section.)
Processing is identical on a fast boot, but no message is issued to the
console.
2-35
DH18-03
CHARACTER SET AND VFC IMAGE LOADING
Information from the $CONFIG section of the Startup job stream is compared with
information contained, in Startup's internal copy (i.e., buffer) of the
PRINTIMAGE file during loading of the character set and Vertical Format Control
(VFC) image. If $CONFIGsection and PRINTIMAGE file information do not match,
a console message is issued defining the problem.
If any of the following error conditions is encountered during a fast boot., the
device is released and no console message is issued.
1. If Startup attempts to load a character set or VFC image into a printer
that is not in a Ready status, the console message:
.PRINTER ERROR icccdd s ••• s FIX TYPE GO OR STOP OR RLSE
is issued (where i = Iyy number, ccc
number, and s ••• s = status message).
= channel
number, dd = device
The operator has three options:
a. Place the device in a Ready status and enter GO via the system
console. Startup attempts to load the character set or VFC image.
b. Enter STOP via the system console, causing Startup to abort.
Deconfigure the device, or bootload the MFC. Then perform a warm boot
to restart the system.
c. Enter BLSE via the system console to release the device. (If a
$ INFO RLSPNT statement is included in the $CONFIG section of the
Startup job stream, the RLSE answer is automatically applied to the
preceding message.)
2. If Startup encounters an error condition (as defined in the status
portion of the following message), the device is released.
message:
Th~
console
.PRINTER ERROR icccdd s ••• s DEVICE RELEASED
is issued. The operator subsequently can correct the error condition
while the system is inoperable and perform a warm boot, or correct the
condition while the system is operational and reassign the device to the
system via the console entry ASGN icccdd.
3. If Startup fails to find the character set defined in the $CONFIG section
in its intern~l table, the device is released and the console message:
.TRAIN ID UNKNOWN TO STARTUP DEVICE RELEASED
is issued. The character set subsequently can be loaded onto the
PRINTIMAGE fj,.le via the TVIM program while the system is operational.
The device can be reassigned to the system via the console entry ASGN
icccdd.
2-36
DH18-03
4. If Startup determines that printer paper is missing or requires
realignment, the console message:
.POSITION PAPER IN PRINTER icccdd FIX TYPE GO OR STOP OR RLSE
is issued. After loading or realigning the paper, the operator can enter
GO, STOP, or RLSE via the system console to get the same results as
described under "1".
5. If Startup determines that a character set exists but is not defined in
the $CONFIG section, the device is released and the console message:
.MOUNTED TRAIN ID xxx REQUESTED TRAIN ID yyy DEVICE RELEASED
is issued.
The operator can:
a. Correct the $CONFIG section and perform a warm boot to restart the
system;
b. Mount the correct print train or belt (yyy) on the printer and perform
a warm boot to restart the system;
c. Reassign the device via the ASGN icccdd console entry when the system
is operational.
SUPPLEMENTAL QUESTIONS DURING INITIALIZATION
)
A series of supplemental (secondary) questions is issued regarding formatting
of mass storage deVices, clearing of defective space information from logical
device labels, and re-editing the deckfile. The following describes the
ramifications of responses to these questions.
Discrepancies During Mass Storage Device Verification
Two console messages are issued during the logical device initialization
process if Startup determines that logical device label information differs
from data contained on a $ Iyy statement. One message is issued if logical
device names (i.e., pack names) differ, while the other message is issued if
the pack serial numbers do not agree.
The console message:
.icccdd xxx CHANGING TO yyy YES TO INITIALIZE PACK
is issued if Startup determines that the logical device name contained on the
logical device label (xxx) is different from the logical device name on the
$ Iyy statement (yyy). The operator can respond YES or NO to this message.
A YES response indicates that the correct disk pack is mounted, but the label
contains erroneous information. Startup writes the logical device name on the
$ Iyy statement to the logical device label and initialization continues.
2-37
DH18-03
A response of NO indicates that the wrong disk pack is mounted. As a result,
Startup aborts. The operator can mount the correct disk pack and reboot the
system.
If the logical device label was destroyed before Startup compared the logical
device label with the $ Iyy statement, no console message is issued (even if
the wrong disk pack is mounted).
The console message:
*icccdd: ddd EXPECTED PACK NUMBER xxxxx FOUND yyyyy YES TO ACCEPT CHANGE
is issued if Startup determines that the pack serial number on the logical
device label (yyyyy) is different from that on the $ Iyy statement (xxxxx).
Note that this comparison is made only if the S-xxxxx option is included on the
$ Iyy statement (where xxxxx = pack serial number).
The operator can respond YES or NO to this message.
A YES response indicates that Startup is to continue the device initialization
process. The operator subsequently can change the pack serial number that is
contained in the logical device label to match that on the $ Iyy statement.
This modification can be effected during the pack serial number verification
procedure that is performed i f the operator responds YES to the -FORMAT/LABEL
QUESTIONS? question.
A response of NO indicates that the wrong disk pack is mounted. As a result,
Startup aborts. The operator can mount the correct disk pack and reboot the
system.
FORMAT/LABEL QUESTIONS? Question
A YES response to the question -INIT DEVICE ddd causes Startup to initialize a
device, and occurs when a $ DIRECT statement is encountered for device "ddd lf or
at the end-of-file for the $INITIALIZE section, whichever comes first. Startup
begins initialization by reading the following disk sectors:
o
Sector 0 - Label
o
Sector 1 - Defective llink directory
o
Sector 3 - Alternate track table (except MSU0500, MSU3380, and MSU3381)
o
Sector 4 - Defective space history table (except MSU0500, MSU0501,
MSU3380 and MSU3381)
MSU0500, MSU0501, MSU3380 and MSU3381 disks have neither a defective space
history table nor an alternate track table; therefore, Startup does n-ot attempt
to read these sectors when processing such devices.
2-38
DH18-03
(
If no $ DIRECT ddd/CLEAR statement is processed and if one or more of the reads
result in nonready status, incorrect checksum, or invali.d table format, Startup
issues the following console message:
.ddd LLINK 0 BAD, MUST TEST/FORMAT/RTHDRS, YES TO CONTINUE
A NO response causes Startup to abort. A YES response causes Startup to
continue the initialization process. At this point, two sets of snaps will
have been written to the printer: one before and one after the label sector has
been built. Snaps are taken of disk sectors 0-4, associated flags and
counters, and the disk I/O trace buffer.
If a $ DIRECT ddd/CLEAR statement is present and was processed by responding
YES to the following console message:
PROCESS DIRECTORY CARD FOR DEVICE ddd?
Startup issues the following console message:
.ddd LLINK 0 CLEARED, MUST TEST/FORMAT/RTHDRS, YES TO CONTINUE
A NO response causes Startup to abort. A YES response causes Startup to
continue the initialization process. Again, if any of the sectors read were
bad, printer snaps will have been written.
I
/
Startup then zeros the bad sectors (or clears sectors 1, 3, and 4 if using
$ DIRECT ddd/CLEAR) and, i f the defective space history table was cleared,
builds an empty history table.
Startup now issues the following message:
.FORMAT/LABEL QUESTIONS?
If the pack number is 00000, the following message is given regardless of the
response to the message above:
.icccdd:
ENTER PACK INNNNN?
The operator responds by entering the desired pack number.
If the response to the .FORMAT/LABEL QUESTIONS? message was YES, the .following
messages are issued:
.icccdd:
CHG PACK Innnnn?
.icccdd:
FMT PACK Innnnn?
.icccdd:
TEST PACK Innnnn?
(except MSU0500, MSU0501, MSU3380 and MSU3381)
(MSU0500 and MSU0501 only)
2-39
DH18-03
The operator responds to the *icccdd: CHG PACK Innnnn? message as follows:
NO - pack number is not changed
nnnnn - new pack number
The operator responds to the *icccdd:
FMT PACK Innnnn? message as follows:
NO
- No formatting will be done
YES
- Startup attempts to format (write track headers on) all tracks,
except those in the defective space history table, as GOOD. Those
tracks in the history table as well as those which cannot be
formatted GOOD are formatted DEFECTIVE/NO ALTERNATE and entered
into the defective llink directory.
RTHDRS - Startup issues a "read track header" command to all tracks on the
disk. Tracks with track indicator (TI) bits specifying
DEFECTIVE/NO ALTERNATE and tracks that cannot be successfully read
are entered into the defective 11 ink directory. Tracks with TI
bits specifying DEFECTIVE/ALTERNATE ASSIGNED are entered into the
alternate track table.
The operator responds to the *icccdd:
NO
TEST PACK f/nnnnn? message as follows:
- No testing will be done
YES
- Startup issues a "read track header" command to all tracks on the
or
disk. Tracks with track indicator (TI) bits specifying
RTHDRS
DEFECTIVE/NO ALTERNATE and tracks that cannot be successfully read
are entered into the defective llink directory. Tracks with TI
bits specifying DEFECTIVE/ALTERNATE ASSIGNED are entered into the
alternate track table. MSU0500/0501 disks do not have alternate
track tables; therefore, tracks marked DEFECTIVE/ALTERNATE ASSIGNED
are treated as if they were marked GOOD.
NOTE: The FMl' and TEST options do not apply to the MSU3380 and MSU3381. The
FTAR program does the formatting of the devices on-line. In addition,
if any defective tracks are encountered they must be assigned to an
alternate track or be deallocated by using the $ DIRECT statement in
the $INITIALIZE secton of the Startup job stream.
Note that Startup does not aSSign alternate tracks. If alternate track
assignment is desired, the Removable Storage Initialization Program (RSIP) must
be used. Refer to the GCOS 8 OS System Operating Techniques manual for RSIP
information.
At the end of the format/test process, Startup equates the defective llink
directory with the defective space history table (if one exists).
2-40
DH18-03
(
One result of this is that each entry in the defective llink directory defines
a single track's worth of defective space. Startup continues with the
initialization of the disk. Sectors 0-4 of the disk are written and the device
allocation unit table is created. Defective space in the defective llink
directory is marked unavailable in the device allocation unit table.
Initialization is now complete.
If a $ DIRECT ddd JCL statement containing D, 0, A, L, and Y data is processed
(YES response to PROCESS DIRECTORY CARD FOR DEVICE ddd? message), Startup adds
the D, 0, A, L, and Y space to the defective llink directory, makes the
defective llink directory agree with the history table, rewrites sectors 0-4,
and marks defective space as unavailable in the device allocation unit table.
Note that the $ DIRECT ddd is allowed even if the disk ddd is not being
initialized. However, a secondary initialize is necessary when the disk ddd
last mode of operation was NIAST.
I
Printer snaps of disk sectors 0-4 and associated flags and counters can be
forced by inserting a $ BUGON statement in the $INITIALIZE section of the
Startup job stream. A $ BUGOFF statement disables the forced printer snaps.
Printer snaps of the Startup disk I/O interval trace table can be forced by
inserting a $ DBGON statement in the $INITIALIZE section of the Startup job
stream. A $ DBGOFF statement disables the forced printer snaps.
The following console messages may be issued prior to an abort of Startup
during disk initialization:
\
)
·ddd LLINK ZERO BAD, MUST INIT
Startup detected invalid disk sectors 0, 1, and (or) 4 and one of the
following conditions:
1. A NO response was made to the INIT DEVICE ddd? question;
2. No $ INIT ddd JCL statement was present;
3. $ DIRECT ddd D, 0, A, L, and Y input was being processed.
The pack must be initialized.
·DISK PACK ERROR icccdd (status) TRACK ZERO BAD
Startup was unable to format track 0 GOOD. This pack cannot be used by
GCOS unless this condition is due to a site error.
.DISK PACK ERROR icccdd PSEUDO ALT AREA ALL DEFECTIVE
The area to be used for pseudo alternate tracks (MSU3380 and MSU3381) is
defective. The pack must be reformatted.
2-41
DH18-03
I
*ddd BLOCK 0 DEFECTIVE MUST REFORMAT DEVICE
Track zero on the disk couldn't be read successfully (channel ready
status), or TI bits did not show a GOOD track. The disk must have track
zero reformatted as GOOD and the pack must be reinitialized.
(
*ddd ERROR DETERMINING ALTERNATE TRACK MUST REFORMAT DEVICE
The track was found marked DEFECTIVE/ALTERNATE ASSIGNED and the alternate
track was not in the alternate track table or it was already assigned to
another defective track. The pack must be reformatted.
Some general guidelines for initializing/formatting/testing of mass storage
devices are:
1. Use a $ DIRECT ddd/CLEAR statement whenever the status of the defective
llink directory, alternate track table, and (or) the defective space
history table sectors is unknown or questionable. Note that whenever a
$ DIRECT ddd/CLEAR statement is processed, a YES response should be given
to the *FORMAT/LABEL QUESTIONS? message and formatting or testing should
be invoked to rebuild the alternate track table.
This recommendation does not apply to MSU0500/0501 disks as they have' no
alternate track table. If formatting or testing is not done after a
$ DIRECT ddd/CLEAR statement is processed, a $ DIRECT ddd (D, 0, A, L,
and Y) statement must be processed to withdraw all known defective space.
2. The only reason for reading track headers is to rebuild the alternate
track table and to build a defective llink directory containing all
tracks marked DEFECTIVE/NO ALTERNATE. Since reading track headers takes
a relatively small amount of time (less than five minutes for MSU0451 and
MSU0500 and about six minutes for an MSU0501), it is recommended that
this be done each time a mass storage device is initialized. Reading of
track headers is not necessary if the correct D, 0, A, L, and Y
statements for all tracks formatted DEFECTIVE/NO ALTERNATE are processed.
,
I
3. The recommended procedure for initializing mass storage devices is to
answer "PARTIAL" to the ".INITIALIZE?" question and never use the "."
when answering any $INITIALIZE section questions. Use of the "*" not
only eliminates the details of what has been done, but can lead to
problems (e.g., "NO" to "FORMAT/LABEL QUESTIONS" prevents asking TEST/FMT
questions when "DDD LLINK-O BAD .•• " - if LLINK-O is unexpectedly bad and
needs TEST/FMT, Startup must be aborted and the "INITIALIZE?" redone).
A further recommendation is to use a $ DIRECT ddd/CLEAR statement, answer
YES or RTHDRS to the TEST/FMT question, and process a $ DIRECT ddd
statement followed by D statements. These D statements should be a set
defining all bad space that the pack manufacturer has identified, bad
space found during RSIP/MTAR/FTAR formatting, and any bad space found
during system operation.
(
2-42
DH18-03
4. Disk formatting during Startup is not a replacement for the disk test
functions in RSIP and MTAR. Disk formatting during Startup must be
complemented with a $ DIRECT ddd statement and the necessary D, 0, A, L,
and Y statements to identify all known marginal or defective space.
CLEAR AND OVERWRITE EXISTING DECKFILE? Question
The CLEAR AND OVERWRITE EXISTING DECKFILE? question introduces the first step
in a two-part function that edits new firmware onto the deckfile. This
function normally is requested by site techniques personnel when new firmware
is to be edited onto the deckfile. The CLEAR AND OVERWRITE EXISTING DECKFILE?
question is issued only if a deckfile exists (i.e., only if the file was not
cleared earlier in the initialization sequence as a result of a YES or TOTAL
response to the *INITIALIZE? question).
A NO response indicates that the file is to remain intact. A YES response
clears the file preparatory to rebuilding it from data contained on another
firmware tape/deck. This tape/deck is read during processing of the .PROCESS
$ READIN? question.
NOTE: On DPS 88 and DPS 90 systems, Startup creates an empty deckfile to edit
the IFAD tape. Therefore, Startup provides for clearing of the deckfile
for DPS 88 and DPS 90 systems.
On DPS 8 and DPS 8000 systems, Startup is required to boatload MPC
firmware. A copy of the MPCB program must be available. Since MPCB is
not saved on the AUTOLOAD file, the deckfile is accessed during an AUTO
boot to obtain the MPCB program deck. If a CLEAR AND OVERWRITE EXISTING
DECKFILE is performed during an AUTO boot, Startup cannot load MPCB and a
Startup abort occurs. Therefore, a TAPE boot or a REPLace of the
$INITIALIZE section with a copy of the MPCB deck is required to perform a
clear and overwrite of the deckfile.
·PROCESS $ READIN? Question (DPS 8 And DPS 8000 Only)
The .PROCESS $ READIN? question signals the second step in editing new firmware
onto the deckfile. This question permits the contents of a firmware tape/deck
to be written to the deckfile. (This question is immediately followed by an
image of the $ READIN statement.)
A NO response indicates there is no firmware tape/deck to be read (i.e., the
operator responded NO to the CLEAR AND OVERWRITE EXISTING DECKFILE? question).
A YES response indicates that a firmware tape/deck is to be read and its
contents are to be written to the deckfile. (This firmware tape/deck normally
is supplied by site techniques personnel or by the site's Honeywell Bull
Customer Service Division (CSD) representative.)
One of two questions, which query the operator as to whether firmware is to be
loaded, may be issued to the system console following a YES response to the
·PROCESS $ READIN? question, or following a response of PARTIAL to the
.INITIALIZE? question.
2-43
DH18-03
The questions are:
-xxxMPC·ON iccc BOOTLOAD SYS ID NAME "y ••• y" REV.zz?
-xxxMPC ON iccc APPEARS OK, BOOTLOAD?
where:
xxx
i
ccc
y ••• y
zz
=
=
=
=
=
subsystem type (e.g., 450)
inp4t/output controller number
channel number
system name from $ SYID statement
firmware rev~s~on level from the $ DKEND statement that delimits the
firmware deck
o
If the data images reside on punched cards, one of the preceding
questions is issued when the firmware deck image is encountered.
o
If the da~a images reside on magnetic tape, one
questions is issued when the $ READIN statement
$INITIALIZE section of the Startup job stream.
identifies the magnetic tape handler from which
be .read.
o
If the data images reside on mass storage, one of the preceding questions
is issued when boot loading is to occur.
of the preceding
is encountered in the
The $ READIN statement
the firmware tape is to
-EDIT? Question
The -EDIT? question allows GCOS system files to be edited to mass storage
(i.e., either created for the first time or content restored following mass
storage device initialization or following a severe system problem).
The -EDIT? question is issued only when a $EDIT section is encountered in the
Startup job stream. With one exception, this question is independent of the
-INITIALIZE? question. The exception occurs when the operator responds TOTAL
to the -INITIALIZE? question. Under these conditions, the -EDIT? question is
automatically answered YES by Startup and $EDIT section contents are executed.
The operator can respond NO, YES, or PARTIAL to the -EDIT? question.
Response
Description of Edit Process
NO
A response of NO is applicable when (1) the -INITIALIZE? question
was answered NO, (2) no system files were affected during the
initialization function, (3) no new system files are to be added,
or (4) no existing system files are to be modified.
YES
A response of YES is required to initially create and/or to
restore all system files.
2-44
DH18-03
Response
Description of Edit Process
If a single magnetic tape handler is being used to edit the
system, Startup rewinds the edit tape whenever it encounters a
valid tape name on a $ FILDEF statement. The operator must
dismount the old edit tape and mount the new one before replying
"YES" to the EDIT question.
When a YES response is entered, Startup expects the total system
software tape(s) to already be mounted on one or more magnetic
tape handlers. (The $ FILDEF statements in the $EDIT section
define the device(s) on which the total system software tapes are
to be mounted.) If the tapes are not already mounted, the
message:
·TAPE ERROR icccdd: ATT I ssssss OPERATE WHEN READY
is issued directing the operator to do so (where i = Iyy number,
ccc = channel number, dd = device number, and ssssss = device
standby code). (Refer to the GCOS 8 OS 1/0 Programming manual
for standby code definitions.)
(Because several reels constitute the total system software tape,
the editing process can be expedited by allocating two tape
handlers and mounting two reels. When reading of one reel
completes, reading of the second reel can begin while the first
reel is automatically rewound. The operator then can mount
another reel on the free tape handler.)
Once the total system software tape is mounted, Startup verifies
the reel serial number and issues the informational message REEL
NO. nnnnnn (where nnnnnn = reel serial number). The tape then is
read. This verify-and-read sequence occurs for each tape reel.
If the reel number in the message REEL NO. nnnnnn identifies the
wrong reel, the operator can press the REQUEST push button on the
console to halt the read function, enter BOOT via the console,
mount the correct tape reel, and reboot the system.
If the file name on a $ FILDEF statement differs from that of the
file being read from the total system software tape, the console
message .FILE IS aaaaaa, SHOULD BE bbbbbb SCFR? is issued (where
aaaaa = name of the file being read and bbbbbb = name of the file
specified on the $ FILDEF statement that should be read). The
operator can respond with one of the following console entries.
S - Abort the Startup program. The console message STARTUP
ABORTED LOC mmmmmm PICK ONE DUMP:ALL,NONE,NORMAL is issued.
The operator can elect to print a main memory dump or to
bypass the dump. (Refer to "Initiating Memory Dump" in
Section 3 for additional information.)
C - Accept the error condition and continue processing the
current file (aaaaaa).
2-45
DH18-03
Response
Description of Edit Process
F - Find the required file (bbbbbb) by searching the tape forward
from the current position.
(
R - Rewind the tape and search forward for the required file
(bbbbbb) •
If (following a YES or PARTIAL response to the *EDIT? question)
the end of the tape is reached without encountering the required
file, the console message:
.END OF TAPE ENTER FILE NAME
is issued. In addition, names of all files on the tape also are
generated at the system console. The operator can (1) enter via
the console the name of another file to be searched for and then
enter R, or (2) mount another tape reel and enter F to search for
the required file.
PARTIAL
A response of PARTIAL is required to (1) selectively. add new
system files and (2) selectively modify the content of one or
more existing system files. Startup queries the operator
regarding the disposition of each file that is identified on a
$ FILDEF statement. The query is via the *EDIT ffffff? question
(where ffffff = file name).
The *EDIT ffffff? question is issued when a $ FILDEF statement is
encountered in the $EDIT section. A response of NO indicates
that the file is not to be edited. A response of YES indicates
that the file is to be modified or added using information from
the $ FILDEF statements in the $EDIT section.
If the file to be added or modified is not the first file that
Startup encounters on the total system software tape, the console
message -FILE IS aaaaaa, SHOULD BE bbbbbb SCFR? is issued. A
response of F results in the forward search of the tape for the
file.
One additional question may be issued during the editing function
that occurs following a response of PARTIAL. This question is
·PROCESS SSFILE CARD AND SYSTEM SCHEDULER CLEAR?
A response of
NO indicates that existing $ SSFILE statement parameters are
still valid. A response of YES indicates that the existing
$ SSFILE statement parameters are to be modified and that the new
parameters exist either on the total system software tape or on a
$ SSFILE statement in the $EDIT section. (A response of YES
requires that the operator respond NO to the .RESTART?
question.) As a result of the YES response, the informational
message:
(
2-46
DH18-03
-SYSTEM SCHEDULER CLEAR FORCED DUE TO PRIOR $ SSFILE CARD
PROCESS
is issued to the system console.
-SYSTEM SCHEDULER CLEAR? Question
The -SYSTEM SCHEDULER CLEAR? question allows the operator to attempt restart of
those jobs that were cataloged on the System Scheduler program's SSFILE file
(catalog). In general, however, clearing of the SSFILE file is not necessary
because jobs in the scheduling phase have not been allocated system resources
(i.e., memory or peripheral devices) and have not entered the execution phase.
A response of YES to the -SYSTEM SCHEDULER CLEAR? question removes all entries
from the SSFILE file (including jobs that were scheduled for running on a
cyclic basis). All jobs that were cataloged on the SSFILE file at the time the
system became inoperable must be reentered.
As previously indicated, Startup does not permit a YES response to both the
-RESTART? and -SYSTEM SCHEDULER CLEAR? questions. If the operator responds YES
to .RESTART?, Startup pre-answers the -SYSTEM SCHEDULER CLEAR? question NO.
A response of NO to the .SYSTEM SCHEDULER CLEAR? question retains all jobs that
were cataloged on the SSFILE file at the time the system became inoperable and
allows restart to be attempted for those jobs. The operator must enter JRUN
REST via the system console to activate the scheduling function following
restart. (Refer to "-RESTART? Question" in this section for additional
information.)
If a system malfunction occurs before System Startup is complete, clearing of
the SSFILE file may be incomplete. To ensure that the file is cleared, respond
YES to the .SYSTEM SCHEDULER CLEAR? question during the ensuing bootload.
2-47
DH18-03
c
(
c
SECTION 3
STARTUP RECOVERY PROCEDURES
The System Startup process can be interrupted by two types of error conditions.
One type of error aborts the Startup process and requires that the operator
reinitiate the entire bootload procedure. The second type of error results in
temporary interruption of the bootload procedure and allows the operator to
correct the problem and resume System Startup at the point of interruption.
In addition to these two types of error conditions, the operator can
intentionally render the system inoperable and reinitiate a system bootload.
Each of these conditions, and techniques to recover from them, are discussed in
this section. Also included are procedures for obtaining dumps following a
Startup program abort and for patching the Startup program. Descriptions of
system aborts that may occur after the system has been bootloaded and is
operational are not included in this section.
BOOTLOADER PROGRAM ERRORS
The Bootloader program loads the Startup program into memory. The Bootloader
program must be entered in its entirety before Startup program loading can
begin.
Once the Bootloader program completes, the Startup program can be loaded into
memory. Any error encountered during this loading process results in a console
message. No dump can be taken when an error is detected before the Startup
program is completely loaded.
Startup assumes the system console is configured on channel 31 of IOM-O, or
channel 30 of IMU-O (for DPS B), or channel 30 of the boot IMX (for DPS BODO),
and attempts to direct the error messages to a console at that location. If
the system console is configured on any other input/output controller or
channel, the following MASK correction statement must be inserted immediately
following the last statement (a ***EOF statement) of the Bootloader program.
3-1
DH18-03
I
1
8
1
3
000003 MASK 31cccctOOOip
where:
I
31
- Console type (EKc/seC)
cccc - PUB (channel) number times 4 (octal)
t
- Type of input/output controller - 10M = 0
IMU/IMX
i
- IOMlIMU/IMX number
p
- IOMlIMU/IMX port number
=4
NOTE: On the DPS 88, the console emulator is logically connected to channel 31
of.IOX-O. On the DPS 90, the console location is passed to Startup via
reserved memory_ Ther~fore, in both of these cases, the MASK statement
will be rejected.
The type of controller specifies the console I/O protocol.
be determined as follows:
The defaults will
1. If there is no console MASK, the hardware-set flags (IOM/1MU/1MX) will
determine the protocol.
2. If a MASK is used and specifies an IOMlIMU/IMX that is not the bootload
IOM/IMU/IMX, the MASK specified protocol will be used.
3. If a MASK is used and specifies the bootload IOM/IMU/IMX, and if 10M
protocol is specified (t=O) but· the controller is an IMU/IMX (hardware
flagged), then the IMU/IMX protocol will be used. However, if the
bootload controller is an 10M but the MASK specifies IMU/1MX protocol
(t=4), the MASK will be ignored and flagged as an error as follows:
a. If the erroneous MASK was applied to the Startup program before the
transfer record to cards or tape, the Startup program will halt with a
DIS identified in the instruction as 400020616203.
b. If the erroneo~s MASK was input via REPL (in response to BOOT SOURCE:
AUTO OR REPL?), it will be identified in the following message:
ILLEGAL MASK CARD BELOW IGNORED
(mask card image)
I
Only one console message is issued if a Startup program error is encountered
while bootloading the program from magnetic tape. This message is STATS/RESIDU
= x ••• x ABORT BOOT FROM TAPE (where x ••• x = 12-digit (octal) magnetic tape
error status). Correct the error and reinitiate the bootload by rewinding the
tape, and pressing the INITIALIZE and BOOTLOAD push buttons on the DPS 8 system
console, or by following the DPS 8000 IMX Service Processor procedures. (Refer
to the GCOS 8 OS I/O Programming manual for a description of magnetic tape
status codes.)
3-2
DH18-03
Several console messages are associated with Startup program errors encountered
while bootloading the program from punched cards. These messages include the
following:
\
)
I
Error Message
Description
STATS/RESIDU= x ••• x
-FIX,EOM
A status error was detected. Correct the error
and press the EOM push button on the system
console to resume the bootload. (Refer to the
GCOS 8 OS I/O Programming manual for a description
of card reader status codes.)
ILLEGAL BIN. -FIX,EOM
The Startup program includes an invalid binary
card. Remove the card and press the EOM push
button on the system console to resume the
bootload.
CRD CHECKSUM -FIX,EOM
The Startup program contains a statement with a
checksum error. Correct the error and press the
EOM push button on the system console to resume
the bootload.
CARD CHECKSUM ERROR
FIX TYPE GO OR TYPE DUMP
The Startup program contains a statement with a
checksum error. Correct the error and enter GO,
or enter DUMP and follow the standard dump
procedure.
CRD SEQUENCE -FIX,EOM
A card is out of sequence in the Startup program.
Resequence the cards and press the EOM push button
on the system console to resume the bootload.
CARD SEQUENCE ERROR
FIX TYPE GO OR TYPE DUMP
A card appeared out of sequence. Resequence the
cards correctly and enter GO, or enter DUMP and
follow the standard dump procedure.
MISSING/EXTRA CARDS
-FIX,EOM
Either a required statement is miSSing from or an
unrecognized statement is included in the Startup
deck. Include the required statement or remove
the invalid statement and press the EOM push
button on the system console to resume the
bootload.
ILLEGAL HOL. -FIX,EOM
The Startup program includes an
or an erroneous MASK correction
Correct the statement and press
button on the system console to
bootload.
ILLEGAL BCD CARD FIX
TYPE GO OR TYPE DUMPGO
The Startup program includes an illegal BCD
statement. Correct illegal statement and enter GO
or enter DUMPGO.
3-3
invalid BCD card
statement.
the EOM push
resume the
DH18-03
Errort-fessage
Description
DUPED MASKS -FIX,EOM
The Startup program includes duplicate MASK
correction cards. Remove one of the cards and
press the EOM push button on the system console to
resume the bootload.
ILLEGAL OCT. -FIX,EOM
The Startup program includes a MASK correction
card that contains non-octal data. Correct the
card and press the EOM push button on the system
c.onsole to resume the bootload.
(
RECOVERABLE STARTUP PROGRAM ERRORS
When the Startup program completes loading into memory, it begins processing
Startup job stream contents. A variety of error conditions can be encountered
during this processing phase. With few exceptions, it is possible for the
operator to correct the error condition and continue the bootload.
Most of the errors are device-oriented and dependent upon the medium (i.e.,
magnetic tape or mass storage) on which the Startup job stream resides. The
following defines several console messages that are commonly issued during this
portion of the bootload. The messages are defined on a device basis. In each
of the messages, i = I/O controller number, ccc = channel number, dd = device
number, and s ••• s = status condition. (Refer to the GeOS 8 OS I/O Programming
manual for a description of error statuses.)
The following console messages are issued when errors are encountered while
processing a Startup job stream that resides on punched cards, which are being
entered via the card reader:
Error Message
Description
.BOOTLOAD DEVICE ERROR,
icccdd: s ••• s OPERATE
WHEN READY
The card reader is not in a ready condition. The
status of the device is identified via s ••• s.
Correct the condition defined by s ••• s and resume
input •
• BOOTLOAD DEVICE ERROR,
icccdd: s ••• s BACKSPACE
OPERATE WHEN READY
An error condition was encountered while reading
the last card. This condition is defined by
s ••• s. Clear any cards from the reader, backspace
the reader, and resume input •
• CARD CHAR ILLEGAL,
icccdd: BACKSPACE,
OPERATE WHEN READY
The last card read contained an invalid character.
Correct the card, clear any cards from the reader,
backspace the reader, and resume input.
(
3-4
DH18-03
1
The following console messages are issued when errors are encountered while
processing a mass storage device:
II
Error Message
Description
.DISK PACK E.RROR, icccdd: An error condition was encountered while reading
s ••• s EOM WHEN READY
from or writing to mass storage. This condition
is defined by s ••• s. Correct the condition and
press the EOM push button on the system console to
resume the bootload •
• DISK PACK ERROR, icccdd: An error condition was encountered while reading
s ••• s FIX, TYPE GO OR
from or writing to mass storage. This condition
STOP OR RLSE
is defined by s ••• s. Correct the condition and
enter GO via the system console to resume the
bootload or STOP to abort Startup. If STOP is
entered, the messages .STARTUP ABORTED LOC mmmmmm
and .PICK ONE DUMP: ALL,NONE,NORMAL are issued.
(Refer to "Memory Dump Following Startup Abort" in
this section for the dump procedure.) Enter RLSE
to release the device and continue the bootload.
The device subsequently can be reassigned via the
console entry ASGN icccdd.
The following console message is issued when errors are encountered while
processing a magnetic tape device:
\
)
Error Message
.TAPE ERROR,
s ••• s MAY BE
FIX, TYPE GO
TYPE CONT TO
Description
icccdd:
RECOVERABLE
OR STOP OR
CONTINUE
An error condition defined by s ••• s was
encountered. The operator can (1) correct the
condition and enter GO via the system console to
resume the bootload; (2) enter STOP via the system
console to abort Startup; or (3) enter CONT via
the system console to release all magnetic tape
handlers configured on this MPC subsystem and,
subsequently, to resume the bootload.
If STOP is entered, the messages .STARTUP ABORTED
LOC mmmmmm and .PICK ONE DUMP: ALL ,NONE ,NORMAL are
issued. (Refer to "Memory Dump Following Startup
Abort" in this section for the dump procedure.)
3-5
DH18-03
The following console messages are issued when printer-related errors are
encountered while processing the Startup job stream. Refer to "Character Set
And VFC Image Loading" in Section 2 for a description of the recovery procedure
associated with each message.
-PRINTER ERROR icccdd s ••• s FIX TYPE GO OR STOP OR RLSE
-PRINTER ERROR icccdd s ••• s DEVICE RELEASED
-TRAIN ID UNKNOWN TO STARTUP DEVICE RELEASED
-POSITION PAPER IN PRINTER icccdd FIX TYPE GO OR STOP OR RLSE
.MOUNTED TRAIN ID xxx REQUESTED TRAIN ID yyy DEVICE RELEASED
STARTUP PROGRAM ABORTS
If the Startup program aborts during the bootload procedure, a console message
is issued defining the reason for the abort. Following issuance of this
message, an informational message is issued defining the main memory location
at which the abort occurred. A third message then is issued giving the
operator several dump-related options. (Refer to "Memory Dump Following
Startup Abort" in this section for a discussion of the dump procedure.)
After the operator has responded to the dump options and after any dump output
has been printed, the question *BOOT SOURCE: AUTO OR REPL? is issued to the
console. This question gives the operator the opportunity to reinitiate the
bootload procedure. (Refer to "*BOOT SOURCE: AUTO OR REPL? Question" in this
section for a discussion of the various restart options.)
The following console messages are commonly issued when Startup aborts.
Error Message
Description
-DISK PACK ERROR, icccdd: An attempt was made to access file fffff beyond
ACCESS BEYOND FILE fffff the file boundary. Startup aborts under this
CANNOT PROCEED
condition. This message is followed by the
messages -STARTUP ABORTED LOC mmmmm and -PICK ONE
DUMP: ALL,NONE,NORMAL. (Refer to "Memory Dump
Following Startup Abort" for the dump procedure.)
Increase the file size on the $ FILDEF statement
in the $EDIT section and reinitiate the bootload.
If this does not correct-the error, contact the
site's CSD representative.
3-6
DH18-03
C
Error Message
Description
*DISK PACK ERROR, icccdd: An error condition defined by s ••• s was
s ••• s CANNOT PROCEED
encountered. Startup aborts under this
condition. This message is followed by the
messages *STARTUP ABORTED LOC mmmmm and *PICK ONE
DUMP: ALL,NONE,NORMAL. (Refer to "Memory Dump
Following Startup Abortft for the dump procedure.)
Correct the condition defined by s ••• s and
reinitiate the bootload.
-FATAL I/O ERROR ON
icccdd: s ••• s
An error defined by s ••• s was encountered.
Startup aborts under this condition.
*TAPE ERROR, icccdd:
s ••• s CANNOT PROCEED
An error condition defined by s ••• s was
encountered. Startup aborts under this condition.
OPERATOR-INITIATED STARTUP AND SYSTEM ABORTS
The console entries BOOT and DUMP immediately render the system inoperable.
These entries can be made in response to any Startup question during the
boot load sequence. The operator also can press the REQUEST push button on the
console while the system is operational and, in response to the console message
???, can enter either BOOT or DUMP.
\
)
In addition to the BOOT and DUMP entries, the operator can create an error
condition and abort the system or the bootload procedure by placing the EXECUTE
SWITCHES/EXECUTE FAULT switch on the processor maintenance panel in the EXECUTE
FAULT position. (Refer to "Dumps Initiated From A VIP Maintenance Terminal" in
this section for a discussion of this procedure.)
The BOOT and DUMP entries often are useful when Startup program/job stream or
bootload changes are desirable. For example, BOOT can be entered to reinitiate
the bootload sequence if the operator wishes to change a response to a Startup
question (e.g., to change a response of YES to the *INITIALIZE? question).
Each of the preceding techniques results in the system becoming inoperable, in
the saving of system restart data, and in the question *BOOT SOURCE: AUTO OR
REPL? being issued to the console. In addition, the DUMP entry and use of the
EXECUTE SWITCHES/EXECUTE FAULT switch result in a series of dump-related
questions and messages being issued to the console prior to the *BOOT SOURCE:
AUTO OR REPL? question. (Refer to "Memory Dump Following Startup Abort" in
this section for a discussion of the dump process.)
As a result of the DUMP entry, portions or all of the Startup job stream are
printed on a printer that is not dedicated.
3-7
DH18-03
o
If the system was being boot10aded from a Startup job stream residing on
punched cards or magnetic tape, only the statement images that were read
prior to the malfunction are printed.
o
If the system was being boot10aded from a Startup job stream residing on
mass storage (i.e., the AUTOLOAD file), the entire Startup job stream is
printed.
The contents of the $LOAD section are not printed in either of these cases. In
addition, none of the Startup job stream is printed if the operator requests a
dump or if Startup aborts while the $LOAD section is being loaded into main
memory.
-BOOT SOURCE AUTO OR REPL? QUESTION
The -BOOT SOURCE: AUTO OR REPL? question is issued when a system failure occurs
or when the operator deliberately renders the system inoperable (e.g., to
perform system maintenance). As previously indicated, the system becomes
inoperable when the operator enters BOOT or DUMP via the system console.
The following responses can be made to this question:
AUTO - The Startup program residing on the AUTOLOAD file is to be used to
effect the boot1oad. This response is not acceptable if the AUTOLOAD
file was destroyed by the system failure or is incomplete. Under
these Circumstances, the message MUST REPLACE FROM s ••• s is issued
(where s ••• s = Startup section that must be replaced). The *BOOT
SOURCE message is reissued. The operator must respond REPL and enter
the required section via the card reader. Once the AUTOLOAD file is
modified, file content is used to bootload the system.
HEPL - The operator can selectively replace one or more sections of the
Startup job stream which exists on the AUTOLOAD file. The section(s)
must be entered in their entirety via the card reader. Selective
replacement of individual statements is not permitted. The entire
section is written to the AUTOLOAD file to overlay (replace) the
existing section.
Only the affected sections require loading. For example, if the
$INITIALIZE section is being replaced, the replacement section need
not be preceded by the $CONFIG section or followed by the $EDIT and
$FILES sections.
If more than one section is being replaced, the sections must be
loaded in their order of appearance in the Startup job stream. For
example, if the $CONFIG and $INITIALIZE sections are being replaced,
the $INITIALIZE section cannot precede the $CONFIG section.
3-8
DH18-03
(
If sections are nonsequential, the message *EXPECT s ••• s ccccc FIX
TYPE GO is issued to the console (where s ••• s = name of the section
that is out of sequence and ccccc = image of the last card read). To
correct a sequencing problem, the operator can enter BOOT via the
system console to render the system inoperable. After placing the
sections in the proper sequence, the operator can enter REPL or GO to
resume the bootload.
When the operator responds AUTO to the *BOOT SOURCE question, the deckfile
cannot be rebuilt because the $ READIN statement is excluded from the
$INITIALIZE section existing on the AUTOLOAD file. To rebuild the deckfile via
the $ READIN statement, the $INITIALIZE section can be entered via the card
reader following a REPL response to the *BOOT SOURCE question.
Modules included in the $LOAD section are saved on the loadfile if a $ LOADFIL
statement is included in the Startup job stream. Under these Circumstances,
these modules are automatically loaded when the system is restarted. If a
loadfile is to be replaced, the $LOAD section can be entered via the card
reader following a REPL response to the *BOOT SOURCE question.
PATCHING STARTUP PROGRAM
The Startup program can be patched via MASK correction statements. These
statements are written to the AUTOLOAD file and are applied to the Startup
program each time the system is bootloaded. A copy of the patched location's
original content is saved on the file. If the applicable MASK statement is
removed, the copy is applied on the next bootload to restore original data to
the location.
MASK statements must immediately precede the transfer statement which is the
last statement in the Startup program. (Exceptions to this are (1) the MASK
statement that defines the input/output controller and channel on which the
system console is configured and (2) MASK statements that are to be applied to
the Bootloader program. These statements immediately follow the Bootloader
program. Refer to "Bootloader Program Errors" in this section for a discussion
of this statement.)
Modification, deletion, or addition of one or more MASK statements requires
that all applicable MASK statements be loaded via the card reader during the
bootload. The operator can respond using one of the following methods:
1. Respond REPL to the question:
*BOOT SOURCE:
AUTO OR REPL?
2. At the end of the MASK section, insert:
***EOF
instead of a TRANSFER statement.
DH18-03
The format of the MASK correction statement follows. Fields beginning in
columns 1, 8, and 13 must be completed. ' If they are not,bootloading halts and
the console message ILLEGAL OCT. -FIX,EOM is issued. Correct the statement and
press the EOM push button on the system console to resume the bootload.
1
1
8
3
2
6
7
3
aaaaaa MASK dddddddddddd cccccc
.MINIT
where:
aaaaaa - Absolute address (octal) of the location to be patched in the
Startup program. This address must contain six digits (i.e.,
leading zeros must be included if the address is fewer than six
digits).
d ••• d
- Patch correction data (octal) to be applied to location aaaaaa.
This data must contain 12 digits (i.e., leading zeros must be
included if the data is fewer than 12 digits).
cccccc - Patch-related comments optionally can be included in columns 26-72 •
•MINIT - An optional Startup program identifier.
DEBUGGING AIDS
Three techniques can be employed to generate main memory and mass storage dumps
during System Startup. These include an operator-initiated dump and use of
$ SNAP and $ DUMP statements in the Startup job stream.
Memory Dump Following Startup Abort
There are several conditions under which a memory dump can be effected and
which subsequently require the system to be bootloaded. Among these are the
occurrence of an abort during System Startup, an operator-initiated malfunction
via the console entry DUMP, occurrence of an unrecoverable system error, and
setting of a switch on the processor maintenance panel.
Described below is the procedure to obtain a dump when the Startup program
aborts during bootloading and how master mode dumps can be initiated from the
processor maintenance panel. Other dump procedures are described in the GCOS 8
OS System Operating Techniques manual.
INITIATING MEMORY DUMP
When an abort occurs during System Startup, two messages are issued. One
message defines the main memory location (mmmmmm) at which the abort occurred.
The second message allows the operator to dump main memory, to dump only buffer
areas and the communication region, or to forego any dump.
3-10
DH18-03
All dump output is directed to an undedicated printer (i.e., dumping to
magnetic tape or to mass storage is not available during System Startup). If
printer PR1 is available, the dump is directed to that device. If PR1 is not
available, the dump is directed to any available undedicated printer.
-STARTUP ABORTED LOC
mmmmmm
-PICK ONE DUMP: ALL,NONE,NORMAL
The following responses can be made via the system console:
NORMAL - Dump only Startup buffer areas and all of the communication
region. Under most conditions (i.e., except those cited with the
ALL response), this response provides adequate debugging
information. The date nd time of the dump are printed in the dump
banner and in a console message.
ALL
- Dump all of main memory. This response is necessary only when
illegal procedure, memory, or parity faults are encountered. The
date and time of the dump are printed in the dump banner.
NONE
- Do not take a dump.
If the Startup program aborts before the $CONFIG section of the Startup job
stream has been processed, the printer to which the dump is to be directed (in
response to an entry of NORMAL or ALL) is unknown to Startup (i.e., the printer
is defined in the $CONFIG section). The console message:
-NEED PRINTER PORT,Iyy,CHAN,MPC/CPI,TRAIN(PICCCS [TTTT])
is issued. The operator must identify the printer via a console entry in the
format picccstttt,
where:
p
i
ccc
s
- input/output controller port number
input/output controller number
- Channel number
- Printer type:
M - Printer is connected to an MPC
C - Printer is not connected to an MPC
tttt - Character set identification number. Startup recognizes only the
following character set identification numbers:
764 - Standard BCD character set for PRU1200/1600 printers
1130 - Standard ASCII character set PRU1200/1600 printers
If the printer is connected to an MPC that was not bootloaded, a dump cannot be
taken. An informational message is issued to the console indicating a device
power off status. The operator can load the firmware from punched cards,
magnetic tape, or mass storage. (Refer to nMPC Bootloading (DPS 8 And DPS 8000
Only)n in Section 2 for additional information.)
3-11
DH18-03
DUMPS
~NITIATED
FROM A VIP MAINTENANCE TERMINAL (DPS 8 ONLY)
Master mode dumps can be initiated from a VIP maintenance terminal using the
following p~ocedure:
1. Set the Maintenance Panel mode switch to TEST, thus enabling the
Processor Maintenance Panel.
2. Press the RESET CONSOLE push button on the system console to reset the
console (if necessary).
3. At the maintenance VIP terminal, enter EX4 to execute the fault.
If the preceding procedure does not generate the dump, perform the following:
1. Enter ST CU, ST VU to stop the processor (i.e., Control Unit and
Virtual Unit).
2. Enter TXA 002000 to enter the transfer address (i.e., the
address referenced by module .CRSBT from which the dump will execute).
3. Enter GO to execute the dump.
NATIVE STAND-ALONE DUMP PROGRAMS
There are three Native Stand-Alone (NSA) dump programs that can be used to
obtain a physical memory dump when all normal methods of obtaining a system
dump have been unsuccessful. NSAR is used for the DPS 8000, NSA8 for the
DPS 88, and NSAD for the DPS 8. (No corresponding program is provided for the
DPS 90 because the necessary functions are provided by MSOS.) These programs
write the contents of the physical memory connected to their respective systems
to a magnetic tape. The tape should then be processed by the Depy (Dump CoPY)
program described below.
For NSAD (DPS 8) this tape contains the binary image of the program (currently
two binary card image records), followed by a two-record set for each 41 (4096)
words of physical memory.
For NSA8 (DPS 88) this tape contains the binary image of the program (currently
two binary card image records), followed by a 41 record for each 41 (4096)
words of physical memory.
For NSAR (DPS 8000) this tape contains the binary image of the program
(currently four binary card image records), followed by a two-record set for
each 41 (4096) words of physical memory_
3-12
DH18-03
The first record of each set contains information used by the DCPY program to
determine the phYSical memory address of the data in the second record of the
set. If the NSA program encounters a tape write error, it retries the current
write sequence until the write is successful or until the end of the magnetic
tape has been reached. If the NSA program succeeds in writing all of the
memory to the magnetic tape before reaching the end-of-tape marker, it writes
an end-of-file (EOF) mark on the tape prior to issuing a rewind and standby
(REWS) command. If the end of the tape is reached prior to reaching the end of
memory, the NSA program writes an EOF mark, but does not issue any rewind
command; the system operator must manually rewind the tape before resuming
normal system operations.
The NSA programs can be booted into memory from either a non-FIPS or FIPS tape
controller. If a non-FIPS tape controller is used, a 9-track tape written at
1600 BPI is recommended. (Note: A 7-track tape written at 800 BPI can be used;
however, a significantly smaller amount of physical memory will be written to
the tape.) For FIPS tape controllers, a 9-track tape written at either 1600
BPI or 6250 BPI can be used.
'
The NSA programs can write more than 8 MW (megawords) of physical memory to the
dump tape at 1600 BPI. This amount of memory should be sufficient to allow a
systems techniques person to determine the cause of the system failure.
Creating Bootable NSA Tapes
\
)
After the GCOS 8 system is operational, the following JCL can be used to create
a bootable dump tape containing the appropriate NSA program.
DH18-03
1
1
8
6
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
IDENT
FILEDIT
LIMITS
TAPE
PRMFL
DATA
LIST
ENDEDIT
ENDCOPI
GMAP
LOWLOAD
PRMFL
FILE
PROGRAM
FILE
FILE
DATA
CHANGE
CHANGE
ENDCOPI
PROGRAM
FILE
TAPE9
ENDJOB
site option
SOURCE,NOBJECT
100,48K,,5000
M*,X1D"IIIII"VS-PRIMARY
*7,W,S,source program file
*C"COPI
xxxx,COMDK
$
(
DECK,NSAF,ON5
G*,R,S,source program file
C*,X1S,25L
SCED
IN,X1D
OT,X2S,25L
A*"COPI
1,1
See NOTE
5,5
See NOTE
WSBT
I1,X2D
OT,X3D""RAWDUMP"DEN16
where xxxx on the $ LIST statement is
NSAR for the DPS BOOO
NSA8 for the DPS 88
NSAD for the DPS 8
NOTE: For NSAR, the $ CHANGE statements should be
$
$
CHANGE
CHANGE
1, 1
7,7
Dumps Initiated At The DPS 8 MCA
The following procedure can be used at the DPS B MCA (Maintenance Computer
Adapter) to boot the NSAD program into DPS B memory.
1. Enter lnn where nn is the MCA number (e.g., 01). This allows the
next line of input to be processed by the MCA, and not by GCOS B. The
MCA will display the 'greater than' character ('>') to prompt for input.
2. The NSAD boot/dump tape should be mounted on the tape handler selected by
the device switches of the Tape MPC. The Tape MPC does not allow writes
to be issued to the dump tape i f the RSO signal has been received.
DH1B-03
3. Enter the IBOOT command to reinitialize the system hardware.
The
reinitialization of the hardware takes several minutes. When it
completes, the two boot records from the NSAD boot/dump tape will" be
booted into memory and NSAD will write 4 MW (megawords) of memory per
minute to the boot/dump tape. The configuration file used must have the
RSO REQ variant set to N for the tape channel used to boot the NSAD dump
tape.
Dumps Initiated At The 10M Maintenance Panel (DPS 8 Only)
The following procedure can be used at the 10M maintenance panel to boot the
NSAD program into DPS 8 memory.
1. Press the SYSTEM INITIALIZE button on the 10M maintenance panel.
2. Wait for the console to become ready.
3. The NSAD boot/dump tape should be mounted on the tape handler selected by
the device switches of the Tape MPC. The Tape MPC does not allow writes
to be issued to the dump tape if the RSO signal has been received.
4. Push the RESET/BRANCH button on the Tape
HEX dial is set 480 first.
~~C
being used.
Ensure that the
5. Push the BOOT button on the 10M maintenance panel.
)
6. The two boot records from the NSAD boot/dump tape will be booted into
memory and NSAD will write 4 MW (megawords) of memory per minute to the
boot/dump tape.
Dumps Initiated At The Console (DPS 8 Only)
The following procedure can be used at the DPS 8 console to boot the NSAD
program into DPS 8 memory.
1. Enter ! to initialize the hardware.
2. Wait for the console to become ready.
3. The NSAD boot/dump tape should be mounted on the tape handler selected by
the device switches of the Tape MPC. The Tape MPC does not allow writes
to be issued to the dump tape i f the RSO Signal has been received.
4. Push the RESET/BRANCH button on the Tape MPC being used.
Ensure that the
HEX dial is set 480 first.
5. Enter B to boot the hardware.
6. The two boot records from the NSAD boot/dump tape will be booted into
memory and NSAD will write 4 MW (megawords) of memory per minute to the
boot/dump tape.
3-15
DH18-03
Dumps Initiated Via DPS 8000 Service Processor
In order to boot the NSAR program into DPS 8000 memory, the system operator
must be able to communicate with the service processor attached to the system.
At the service processor the operator should enter
(
ISP
to inform the service processor that the next input is to be processed by it
and not GCOS 8. The service processor responds with a greater than ('>')
character to prompt forinp~t.
Sample Console Dialog For DPS 8000 Dump
Figure 3-1 shows a console log from a tandem DPS 8000 system. The system
operator used the RLOAD command to inform the service processor that both IMUs
configured were to be reloaded. IMU 10 was loaded before IMU 11.
Approximately three minutes later, the operator entered the IBOOT command to
boot the NSAR boot/dump tape into memory_ Approximately two minutes after the
IBOOT command was entered, the NSA tape moved off the load point. NSAR writes
approximately 4 MW (megawords) of memory per minute to the boot/dump tape.
The configuration file used to boot the NSAR boot/dump tape must have the
RSO REQ variant set to N in order for the NSAR program to function correctly.
NSAR writes to the boot tape after all four of the binary card images have been
loaded into memory and placed in execution. The tape MPC does not allow writes
to be issued to the dump tape if the RSO signal is sent to the tape MPC.
The configuration file used in Figure 3-1 could be listed via the LISTCFIG
command. To do this, the operator enters the pound sign character 'I' followed
by the characters '00'. The MCA responds with a greater than character '>'.
The operator may now enter the LISTCFIG command to display the current
configuration file.
3-16
DH18-03
(
~
D50)MCA 01 RLOAD IMU .Cfilename
150)MCA 00 RLOAD IMU .Cfilename
I CONSOLE SELF TEST SUCCESSFUL I
1 IPC CONSOLE READY (F/W TAB 003) I
# MULTIDROP ENABLED #
100(STATE status
100( •••
100( •••
100(Please set new date & time with the command:
100(TIME mmddyy,hhmmss
ISP)IBOOT
SCU 0 CONFIGURATION LOADED
SCU 1 CONFIGURATION LOADED
CPU 0 LOADED CONFIGURATION
l/
CPU 1 LOADED CONFIGURATION
«0000»
- LOAD APPLICATION - NORMAL TERMINATION
«0000»
BOOT SENT - BOOT NORMAL TERMINATION
«0000»
INIT - NORMAL TERMINATION
100/SYS -OPTIONAL
-- •••• THE 'Q.' LIBRARY IS THE PRIMARY SEARCH FILE
-- ALLOCATE -LIBRARY .Q -PATHNAME USER-BACKUP/LIBRARY -OPTIONAL
•••• THE '.Q' LIBRARY IS THE SECONDARY SEARCH FILE ••••
1
2
3
4
5
6,10
7
(See NOTES 8 through 10)
I
END DEFAULTS
ALLOCATE -DIRECTIVES -PATHNAME SYS_SOFTWARE/yyyy/DATA/SHARD.CHGS
10
NOTES:
1. Site-defined content (nnnnn) for the $ IDENT statement; replaces the
default user identification provided in OPNSUTIL. If this statement is not
included, system software provides a default $ IDENT statement.
2. This $ RUN statement points to a run unit that loads Integrated Software
into memory for execution.
3. Required to execute this process.
4. Specifies the defaults for allocation of virtual memory space (VSPACE) and
for initial allocation of real memory (RSPACE) for Integrated Software.
These values can be increased to meet site requirements.
5. The $ DATA BP file contains SDLD directives to explicitly define a buffer
pool (i.e., CREATE BUFFER POOL and ASSIGN PRIVATE BP FILE directives). An
ALLOCATE -BPDIRECTIVES directive may be used instead-of the $ DATA BP file.
4-4
DH18-03
6. Identifies the primary search library (Q.) from which Integrated Software
domains are loaded.
7. Identifies the secondary search library (.Q) from which Integrated Software
domains are loaded if the primary search library is unavailable. To use,
remove the initial characters (n __ n) and supply a pathname.
8. The following Integrated Software domains reside on the SHARD.SPWN file:
INCLUDE DOMAIN
INCLUDE-DOMAIN
INCLUDE-DOMAIN
INCLUDEDOMAIN
INCLUDE-DOMAIN
INCLUDEDOMAIN
INCLUDE-DOMAIN
INCLUDE-DOMAIN
INCLUDE-DOMAIN
INCLUDE-DOMAIN
INCLUDE-=DOMAIN
INCLUDE DOMAIN
INCLUDE-DOMAIN
INCLUDE-DOMAIN
.MUTTR
.MUTFH
.MUTOR
.MUTTD
.MUT01
.MPFIO
.MBJDO
.MIMOO
.MCCOO
.MHLOG
.MCKJM
.MBMGT
.MDMGL
.MAJAC
-LIBRARY
-LIBRARY
-LIBRARY
-LIBRARY
-LIBRARY
-LIBRARY
-LIBRARY
-LIBRARY
-LIBRARY
-LIBRARY
-LIBRARY
-LIBRARY
-LIBRARY
-LIBRARY
Q.
Q.
Q.
Q.
Q.
Q.
Q.
Q.
Q.
Q.
Q.
Q.
Q.
Q.
-REQUIRED
-REQUIRED
-REQUIRED
-REQUIRED
-REQUIRED
-REQUIRED
-REQUIRED
-REQUIRED
-REQUIRED
-REQUIRED
-REQUIRED
-REQUIRED
-REQUIRED
-REQUIRED
INCLUDE DOMAIN .MAJIO -LIBRARY Q. -REQUIRED
INCLUDE DOMAIN .MDMCS -LIBRARY Q. -REQUIRED
INCLUDE DOMAIN
INCLUDE-DOMAIN
INCLUDE-DOMAIN
INCLUDE-DOMAIN
INCLUDE-DOMAIN
.MDZPC
•MMC01
•MWCMI
•Ml'MOO
.MWMAN
-LIBRARY
-LIBRARY
-LIBRARY
-LIBRARY
-LIBRARY
Q.
Q•
Q•
Q•
Q.
-REQUIRED
-REQUIRED
-REQUIRED
-REQUIRED
-REQUIRED
Trace
Shared Fault Handler
Output Report
Trace Display
Termination Wrapup
Protected File 1/0
Before Journal Management
Integrity Management
Concurrency Control
Historical Log
Checkpoint Journal Management
Buffer Management
Global Data Management
After Journal Access and
Reconstruction
After Journal Shared lID
Support
Data Management Control
System
Data Base Procedures
Session Control
Automatic Enable
Tenant Management
Workstation Management.
9. The following default parameters are assembled in UTOR for Integrated
Software and reside on the SHARD.SPWN file. For more information on these
default parameters, refer to nIntegrated Software Default Parameter
Modification", later in this section, and to the GCOS 8 OS Protected Files
Administrator's Guide and the GCOS 8 OS Integrity Control manual.
~
ASSIGN SITE PARAMETER -AJ USERID USERID$PASSWD
ASSIGN-SITE-PARAMETER -AJ-SAVE RESTORE •• FILE SYS SOFTWARE//SYS
(See NOTE 10) - ASSIGN SITE PARAMETER -MAX NUMBER JOURNALS 20
ASSIGN-SITEPARAMETER -JOURNAL DIRECTORY CISIZE 2
ASSIGN-SITE-PARAMETER -AJ NFIELDS 8
ASSIGN-SITE-PARAMETER -AJ-IDENT nACCOUNT,GUESS-WHon
ASSIGN-SITE-PARAMETER -BJ-CISIZE 2816
ASSIGN-SITE-PARAMETER -BJ-MIN CI 1000
ASSIGN-SITE-PARAMETER -BJ-MAX-CI 0-- ZERO MEANS UNLIMITED
ASSIGN-SITE-PARAMETER -BJ-HEADER WRITE PERIOD 30
ASSIGN-SITE-PARAMETER -RS-DUP NOASSIGN-SITE-PARAMETER -RSDEVICE 000000 (See NOTE 10)
4-5
DH18-03
. ASSIGN SITE PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SIT~PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN SITE PARAMETER
ASSIGN SITE PARAMETER
ASSIGN SITE PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SIT~PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIG~SITE=PARAMETER
ASSIGN-SIT~PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SIT~PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITg-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITE-PARAMETER
ASSIGN-SITg-PARAMETER
.-RS .DUP DEVICE 000000 (See NOTE 10)
-CC-PROCESS PAGES 25900
.
-BM:PARAMETER CHECK YES
-BM-COMPRESSED JOURNAL YES
-BI-SUPPRESSION ENTRIES a
-MOVE MODE MAX BUF 10
-DEFAULT BP BUFFERS 40
-PFIO OPEN BUFFERS 2
-PFIO-INTERNAL TRACE NO
-wcc 1 STAR FILE SYS SOFTWARE/yyyy/DATA/WCC-1STR
(See NOTE 10)
-wce 6 STAR FILE SYS_SOFTWARE/yyyy/DATA/WCC-6STR
(See NOTE 10)
-WD FILE
SYS_SOFTWARE/yyyy/DATA/WS-DB
(See NOTE 10)
-SC VIRTUAL BUFFER SIZE 1000
-SC-INTERNAL TRACE-NO
-TM-INTERNAL-TRACE NO
-W~INTERNAL-TRACE NO
-HISTORICAL LOG NO
-HL CISIZE 2048
-HL-NUM CI 1000
-HL-DUP-NO
-HL-DEVICE 000000 (See NOTE 10)
-HL-DUP DEVICE 000000 (See NOTE 10)
-CKPT InENT "ACCOUNT,GUESS-WHO"
-CKPT-USERID USERID$PASSWD
-CKPT-FILE SIZE 40000
-CKPT-FIL~DEVICE 000000 (See NOTE 10)
-CKPT-DUMP-FILL 60
-CKPT-DUMP-TIME a -- NO DEFAULT
-CKPT-COLLECT ALL
-CKPT-FILE CONTROL NONE
-CKPT-MAX ACTIVITIES 200
-CKPT-FILE RMVBL 000000,000000
-- ANY DEVICE,PACK
-ISSTAT ENABLE NO
-ISSTAT-ABNORMAL TERM NO
-ISSTAT-FILE CODE J*
-ISSTAT-REPORT CODE 74
-ISSTAT-ALL SYS LEVEL NO -PRINT ZERO NO
-I SST AT-ALL-P ROC LEVEL YES -PRINT ZERO NO
-ISSTAT-BM SYS LEVEL NO -PRINT ZERO NO
-I SST AT-DM-SY S-LE VEL NO -PRINT-ZERO NO
-ISSTAT-AJ-SYS-LEVEL NO -PRINT-ZERO NO
-ISSTAT-CC-SYS-LEVEL NO -PRINT-ZERO NO
-ISSTAT-HL-SYS-LEVEL NO -PRINT-ZERO NO
-ISSTAT-PFIO SYS LEVEL NO -PRINT ZERO NO
-ISSTAT-BM PROC LEVEL YES -PRINT-ZERO NO
-ISSTAT-DM-PROC-LEVEL YES -PRINT-ZERO NO
-ISSTAT-BJ-PROC-LEVEL YES -PRINT-ZERO·NO
-I SST AT-AJ-PRO C-L EVEL YES -PRINT-ZERO NO
-ISSTAT-PFIO PROC LEVEL YES -PRINT ZERO NO
-ISSTAT-IDS2PROC~·tEVEL YES -PRINT-ZERO NO
4-6
DH18-03
~
ASSIGN SITE PARAMETER -I SST AT BATCH PROCESSES YES
ASSIGN-SIT~PARAMETER -ISSTAT-WS PROCESSES NO
ASSIGN-SITE-PARAMETER -ISSTAT-TP-PROCESSES NO
ASSIGN-SITE-PARAMETER -ISSTAT-TDS PROCESSES NO
ASSIGN-SITE-PARAMETER -ISSTAT-TSa-PROCESSES NO
ASSIGN-SITg-PARAMETER -CKPT FILE DUP NO
ASSIGN-SITE-PARAMETER -CKPT-FILE-DUP DEVICE 000000 -- NO DEFAULT
ASSIGN-SITE-PARAMETER -HL IGNORg-ERRORS YES
ASSIGN-SITE-PARAMETER -HL-COMMITMENT ENTRY YES
ASSIGN-SIT~PARAMETER -HL-FILE OPEN ENTRY YES
ASSIGN-SIT~PARAMETER -HL-FILE-CLOSE ENTRY YES
ASSIGN-SIT~PARAMETER -TRACE BUFFER SIZE 1 -- ONE 4K BUFFER
10. 000000 (Six zeros) - Any device
yyyy - Current Software Release
sti - Software Technical Identifier (see the appropriate SRB for the STI
name)
INTEGRATED SOFTWARE DEFAULT PARAMETER MODIFICATION
Integrated Software is assembled with parameters that provide controls over
specific processing conditions (see note 9 above for a list of parameters).
Assembled parameter values are default values, which are defined in the
following files (where yyyy = software release identifier, such as 3000) and
described below.
\
)
o SYS_SOFTWARE/yyyy/JCL/SHARD.SPWN
o SYS_SOFTWARE/yyyy/DATA/SHARD.CHGS
Each default value can be modified to meet installation processing
requirements. It is recommended that any modification be applied to the
SHARD.CHGS file. This approach leaves the default parameters unchanged in the
SHARD.SPWN file, which provides a point of reference for determining default
values.
Modification of a parameter in either the SHARD.SPWN or SHARD.CHGS file applies
changes to Integrated Software spawned either from the OPNSUTIL/SHARD file or
during System Startup.
A two-step procedure can be used to apply parameter modifications to either the
SHARD.SPWN file or the SHARD.CHGS file. First, use the time sharing system
CONVER subsystem to copy the file (e.g., SHARD.CHGS) into the current file;.
then, use the time sh~ring system EDIT command to modify the value in question.
The following usage rules apply to SDLD directives.
1. If a syntax error is encountered in the parameter definition, either the
default is applied or - if a previous aSSignment was made for the
parameter - the existing value is used.
)
4-7
DH18-03
2. If an ASSIGN SITE PARAMETER directive is duplicated, the last iteration
encountered is applied.
3. A literal string is permitted only in an argument field.
4. Quotation marks (n) serve as beginning and ending delimiters of a literal
string. Use of these delimiters permits embedded blanks within the
string.
5. If a quotation mark is embedded within a literal string, it must be
immediately preceded by another quotation mark. For example, "a""b n is
interpreted as anb.
6. If the directive is misspelled (e.g., ASSIGN-SITE-PARAMETER), SDLD cannot
recognize the directive as valid, which causes SHARD to abort.
Site Parameters
This section describes the valid parameters that can be used with the SDLD
directive ASSIGN SITE PARAMETER.
SITE PARAMETERS FOR ARCHIVED BEFORE/AFTER/ACCOUNTING JOURNALING
Maximum Number of Journals
The -MAX NUMBER JOURNALS parameter is used to specify the maximum number of
journals:
ASSIGN SITE PARAMETER -MAX NUMBER JOURNALS n
where:
n - Maximum number of journals.
default value is 10.
This value may range from 1-20.
The
Journal Directory Control Interval Size
The -JOURNAL DIRECTORY CISIZE parameter is used to specify the journal
directory control interval size:
ASSIGN SITE PARAMETER -JOURNAL DIRECTORY CISIZE c
where:
c - Control interval size, specified in K (while other control interval size
parameters are specified in bytes). This value may range from 1-16 (K).
The default ,value is 2 (K).
4-8
DH18-03
(
SITE PARAMETERS FOR AFTER JOURNALING
~
V
After Journaling is a means by which data bases can be protected against media
failure (usually disk) and erroneous data base modifications. Any data base
file created or modified with the FMS RDERR/JOURNAL/ option is protected by
After Journaling. The following parameters instruct the After Journaling
software with the site's selection of options.
After Journal $ IDENT Statement
A $ IDENT statement is assembled into a job stream that is spawned by the After
Journal domain to interface with the File Management Supervisor (FMS) save
and/or restore process. Columns 16-80 must be redefined by each site via the
-AJ_IDENT parameter:
ASSIGN SITE PARAMETER -AJ IDENT x
where:
x - 1-65 alphanumeric characters to be placed in columns 16 to 80 of the
$ IDENT statement. Blank is a valid character in this field, provided
that the field is enclosed with quotes (e.g., "b c"). ACCTI,GUESS-WHO
is used as the default.
)
After Journal $ USERID Statement
A $ USERID statement is assembled into a job stream that is spawned by the
After Journal domain to interface with the File Management Supervisor (FMS)
save and/or restore process. Columns 16-80 must be redefined by each site via
the -AJ_USERID parameter:
ASSIGN SITE PARAMETER -AJ USERID y
where:
y - 1-65 alphanumeric characters to be placed in columns 16 to 80 of the
$ USERID statement. USERID$PASSWD is used as the default.
After Journal Save/Restore •• File Pathname
A default pathname is provided for this file. There may be some circumstances,
however, under which pathname modification is desirable. For example, before
installing a new version of a file, the system administrator may wish to test
file content; by modifying the pathname of the new (test) version, the file can
be accessed without interrupting system processing that uses the existing
version. The pathname can be modified via the -AJ SAVE RESTORE •• FILE
parameter:
ASSIGN SITE PARAMETER -AJ_SAVE_RESTORE_••_FILE P
4-9
DH18-03
I
where:
p - File pathname.
(
SIS SOFTWARE/W2SI00842000/SIS is the default.
SITE PARAMETERS FOR BEFORE JOURNALING
Before Journaling provides a means by which files are protected from incomplete
updating due to process abort or system failure. A Before Journal is created
and maintained for each process accessing a file for which the FMS
ABORT/ROLLBACK/ file option has been specified. The following parameters
instruct the Before'Journaling software with the sitets selection of options.
Before Journal Control Interval Size
The -BJ CISIZE parameter is used to specify the before journal control interval
size:
ASSIGN SITE PARAMETER -BJ CISIZE c
where:
c - Control interval size", in bytes, ranging from 256-66536. The default is
2816 bytes (704 words) which accommodates two 320-word control intervals
for a file with ABORT/ROLLBACK protection and supporting header
information.
Minimum Number Of Before Journal CIs Per Commitment Unit
The -BJ MIN CI parameter is used to specify the minimum number of before
journal-control intervals per commitment unit:
ASSIGN SITE PARAMETER -BJ MIN CI n
where:
n - Minimum number of before journal control intervals per commitment unit,
ranging from 5-100000. The default is 1000.
Maximum Number Of Before Journal CIs Per Commitment Unit
The -BJ MAX CI parameter is used to specify the maximum number of before
journal-control intervals per commitment unit:
ASSIGN SITE PARAMETER -BJ MAX CI n
where:
n - Maximum number of before journal control intervals per commitment unit,
ranging from 5-100000. The default is unlimited.
4-10
DH18-03
(
Before Journal Control Interval Writes Between Header Writes
~
~
A header record containing control information is periodically written to the
before journal. The header record occupies one control interval and is always
the first control interval in the file. The number of before journal control
intervals written between header records can be modified via the
-BJ_HEADER_WRITE_PERIOD parameter:
ASSIGN SITE PARAMETER -BJ HEADER WRITE PERIOD n
where:
n - Number of before journal control intervals written between header
records, ranging from 1-1000. The default value is 30. A larger value
of n reduces the number of run-time I/O operations. However, a longer
recovery period is required in the event of a system failure.
FMS Protection For Before Journal Recovery Structure
The -RS DUP parameter is used to specify whether the RDERR/DUP/ FMS protection
option should be applied to the recovery structure (before journals and PAT
image files):
ASSIGN SITE PARAMETER -RS DUP x
where:
x - 0 or NO or OFF applies RDERR/NONE/.
I
This is the default.
1 or YES or ON applies RDERR/DUP/.
Before Journal Device Specification
The -RS DEVICE parameter is used to assign a specific device or devices on
which all before journals and PAT image files will be created:
ASSIGN SITE PARAMETER -RS DEVICE ddd,dde,ddf, ••. ddm
where:
ddd,dde,ddf, ••• ddm - Device codes. 1-10 may be specified. If a specific
device is not assigned, FMS will create'the before
journals and PAT image files on a device of its
choosing. If more than one device is specified, the
before journals and PAT image files will be placed on
the devices in a round robin manner. Note that these
devices must be configured as permanent FMS devices.
4-11
DH18-03
Before Journal Duplicate Device Specification·
The -RS DUP DEVICE parameter assigns a specific device or devices (up to 10) on
which all duplicate before journals and PAT image files will be created:
ASSIGN SITE PARAMETER -RSDUP DEVICE ddd,dde,ddf, ••• ddm
where:
I
ddd,dde,ddf, ••• ddm - Device codes. 1-10 may be specified. If a specific
device is not assigned, FMS will create the duplicate
before journals and PAT image files on a device of its
choosing. If more than one device is specified, the
duplicate files will be placed on the devices in a
round robin manner. Note that these devices must be
configured as permanent FMS devices. They must be
different physical devices from the devices specified
with the -RS DEVICE parameter.
SITE PARAMETERS FOR CHECKPOINT JOURNALING
Checkpoint Journaling $ IDENT Statement
A $ IDENT statement is assembled into a job stream that is spawned by the
Checkpoint Journal Manager domain to dump the checkpoint journal to the
checkpoint journal archive (i.e., to tape). Columns 16-80 must be redefined by
each site via the -CKPT_IDENT parameter:
ASSIGN SITE PARAMETER
~CKPT
IDENT x
where:
x - 1-65 alphanumeric characters to be placed in columns 16 to 80 of the
$ IDENT statement. Blank is a valid character in this field, provided
that the field is enclosed with quotes (e.g., "b c"). ACCTI,GUESS-WHO
is used as the default.
Checkpoint Journaling $ USERID Statement
A $ USERID statement is assembled into a job stream that is spawned by the
Checkpoint Journal Manager domain to dump the checkpoint journal to the
checkpoint journal archive (i.e., to tape). Columns 16-80 must be redefined by
each site via the -CKPT_USERID parameter:
where:
y - 1-65 alphanumeric characters to be placed in columns 16 to 80 of the
$ USERID statement.
USERID$PASSWD 1s used as the default.
4-12
DH18-03
(
Default Checkpoint File For Checkpoint Journaling
The -CKPT FILE CONTROL param~ter is considered the master checkpoint Journal
parameter. It-determines the type of file on which process snapshots are
collected, unless an activity statement option is used to override this value.
The file used for process snapshot collection may be either the system-wide
checkpoint journal or a user-specific checkpoint file (e.g., QX file used for
I-D-S/I and Indexed Sequential Processor (ISP) data base management programs).
Values for this parameter are NONE, USER, JOURNAL, and SYSTEM.
The -CKPT_FILE_CONTROL parameter is specified as follows:
ASSIGN SITE PAHAMETER -CKPT FILE CONTROL {NONE!USER!JOURNAL!SYSTEM}
where:
NONE
- The checkpoint journal is not used. No process snapshots are
collected on the checkpoint journal. User-specific checkpoint
files may be used on a per-process basis to collect the process
snapshot from the most recent commitment. This is the default.
USER
- Process snapshots from the most recent commitment are maintained
on user-specific checkpoint files. Activity statement options
CHKPT/{ARCHIJRNLIDEFER} can be used to override the effects of
this SDLD directive on a per-process basis.
JOURNAL - Process snapshots are maintained on the checkpoint journal, which
is a cataloged, permanent file under the user identifier
SYS RECOVERY. Activity statement option CHKPT/USERI can be used
to override the effects of this SDLD directive on a per-process
basis.
SYSTEM
- Produces the same results as specifying JOURNAL (i.e., process
snapshots are maintained on the checkpoint journal). In addition,
SYSTEM imposes a security restriction by preventing the use of the
CHKPT/USERI activity statement option to override the collection
of checkpoints to the checkpoint journal (i.e., use of the
activity option CHKPT/USER is invalid).
Checkpoint Journaling Collection Of Historical Process Snapshots
The -CKPT COLLECT parameter specifies the extent of checkpoint information to
be collected when -CKPT FILE CONTROL JOURNAL or -CKPT FILE CONTROL SYSTEM has
been specified:
ASSIGN SITE PARAMETER -CKPT COLLECT {ALLINONE}
4-13
DH18-03
where:
ALL
- Specifies that all process snapshots for processes using protected
files are to be collected. In addition, activity start and
termination are registered for these processes. ALL is the default.
For processes that do not use protected files, no checkpoint
information is collected unless use of the checkpoint journal is
requested via activity statement options, or required via
-CK~T FILE CONTROL SYSTEM.
Collection of all process snapshots can
be selectively suppressed for an individual process using activity
statement options. (Refer to the GCOS 8 OS Integrity Control manual
for more information.)
-
NONE - Specifies that no process snapshots are to be collected for processes
using protected files (i.e., only activity start and termination are
registered). The two most recent snapshots are maintained on the
checkpoint journal, but deleted if the activity terminates normally.
The most recent checkpoint is maintained if the process terminates
abnormally. For processes that do not use protec.ted files, no
checkpoint information is collected unless use of the checkpoint
journal is requested via activity statement options, or required via
-CKPT FILE CONTROL SYSTEM. Collection of all process snapshots ,can
be selectively enabled for an individual process using activity
statement options. (Refer to the GCOS 8 OS Integrity Control manual
for more information.)
Checkpoint Journal Size
The -CKPT FILE SIZE parameter specifies the maximum size of the checkpoint
journal:
ASSIGN SITE PARAMETER -CKPT FILE SIZE s
where:
s - Maximum size (in llinks) of the checkpoint journal.
1000-131071 llinks. The default value is 40000.
The valid range is
Maximum Number Of Activities Using Checkpoint Journal
The -CKPT MAX ACTIVITIES parameter defines the maximum number of activities
that will-write process snapshots to ,the checkpoint journal:
ASSIGN SITE PARAMETER -CKPT MAX ACTIVITIES n
'4-14
DH18-03
where:
n - Maximum number of activities. The range for this parameter is 5-2200,
with a default value of 200. This value is used in a file control block
to reserve space for the process snapshots. It can be detenmined by
using the following formula:
nnnn
= (Number
of activities taking commitments)
• (No. of times activities are run before journal is dumped)
For example, if an installation has 20 activities taking commitments and
each activity is run 5 times before the checkpoint journal is dumped to
the checkpoint journal archive (i.e.,tape), then the
-CKPT MAX ACTIVITIES parameter should be aSSigned a value of 100.
Checkpoint Journal Dump Frequency (Percent Filled)
The -CKPT DUMP FILL parameter specifies the percentage full requirement for
dumping the checkpoint journal to archive (i.e., tape):
ASSIGN SITE PARAMETER -CKPT DUMP FILL p
where:
\
)
\
p - Percent (0-100). The default value is 60 percent. For example, if this
value is 70, the checkpoint journal is dumped to archive when it has
been filled to 70 percent of its capacity.
If this parameter is used in conjuntion with the -CKPT_DUMP_TIME
parameter, then whichever condition is met first determines when the
journal is dumped.
Checkpoint Journal Dump Frequency (Time)
The -CKPT DUMP TIME parameter indicates a specific time interval for dumping
the checkpoint-journal to the checkpoint archive (i.e., tape):
ASSIGN SITE PARAMETER -CKPT DUMP TIME t
where:
t - Time interval (0-1440) minutes. There is no default; a value must be
supplied if the parameter is used.
DH18-03
Duplicate Checkpoint Journal
The -CKPT FILE DUP parameter is used to specify whether the protection option
RDERR/DUp7 is applied to the checkpoint journal:
(
ASSIGN SITE PARAMETER -CKPT FILE DUP x
where:
x - 0 or NO or OFF applies ROERR/NONE/.
This is the default.
1 or YES or ON applies RDERR/DUP/. This FMS protection option maintains
a duplicate checkpoint journal, thus protecting against loss of 'the
primary checkpoint journal.
Checkpoint Journal Device Specification
The -CKPT FILE DEVICE parameter is used to assign a specific device on which to
create the checkpoint journal:
ASSIGN SITE PARAMETER -CKPT FILE DEVICE d
where:
d - Device code. If a specific device is not aSSigned, FMS will create the
checkpoint journal file on a device of its choosing.
Duplicate Checkpoint Journal Device Specification
The -CKPT FILE DUP DEVICE parameter is used to assign a specific device on
which to create the duplicate checkpoint journal:
ASSIGN SITE PARAMETER -CKPT FILE DUP DEVICEd
where:
d - Device code. If a specific device is not aSSigned, FMS will create the
duplicate checkpoint journal file on a device of its choosing.
Removable Device For Checkpoint Journal
The -CKPT FILE RMVBL parameter is used to assign a removable device o~ which to
create the checkpoint journal. If this parameter is not used, the file is
created on PERM device.
ASSIGN SITE PARAMETER -CKPT FILE RMVBL t,x
(
4-16
DH18-03
where:
t - Device type.
C1BPK.
Valid values are 400PK, 450PK, 500PK, 501PK, C1APK,and
x - Pack serial number.
Five alphanumeric characters.
SITE PARAMETERS FOR HISTORICAL LOG
The Historical Log is a chronological record of activity for processes
accessing protected files and processes that use journals.
Create Historical Log
The -HISTORICAL LOG parameter specifies whether or not the historical log is to
be created:
ASSIGN SITE PARAMETER -HISTORICAL LOG x
where:
x - 0 or NO or OFF.
The historical log
will~ot
be created (default).
1 or YES or ON. The historical log will be created. Specifying YES is
recommended if an installation is processing with protected files and is
using the checkpoint journal service to collect all process snapshots
during the life of a process.
Number
or
Historical Log Control Intervals
The -HL NUM CI parameter defines the number of control intervals for the
historical log:
ASSIGN SITE PARAMETER -HL NOM CI n
where:
n - Number of control intervals. The valid range for this value is
5-100000. The default value is 1000. Multiplying the value of this
parameter by the value of the control interval size parameter
(-HL_CISIZE) determines the size of the historical log.
4-17
DH18-03
I
Historical Log Control Interval Size
The -HL·CISIZE parameter defines the size (in bytes) of the control interval
for the-historical log:
ASSIGN SITE PARAMETER -HL CISIZE c
where:
c - Control interval size, in bytes. The valid range is 256-65536.
default value is 2048 bytes (512 words).
The
Ignore Errors When Writing To Historical Log
The -HL IGNORE ERRORS parameter specifies whether errors that occur when a
process-is writing to the historical log are ignored:
ASSIGN-SITE-PARAMETER -HL IGNORE ERRORS x
where:
x - 0 or NO or OFF will cause processes to abort when they encounter an
error writing to the historical log.
1 or YES or ON (default) will cause processes to ignore errors that
occur when writing to the historical log~
Duplicate Historical Log
The -HL DUP parameter specifies whether a duplicate historical log will be
created:
ASSIGN SITE PARAMETER -HL DUP x
where:
I
x - 0 or NO or OFF.
The duplicate historical log will
no~
be created
(default) •
1 or YES or ON.
The duplicate historical log will, be·created.
Historical Log Device
The -HL DEVICE parameter is used to define a specific device upon which to
create the historical log:
ASSIGN SITE PARAMETER -HL DEVICE ddd
4-18
DH18-03
where:
ddd - Device code. Any configured three-character logical device name is a
valid argument. If a specific device is not assigned, FMS will create
the historical log file on a device of its choosing.
Historical Log Duplicate Device
The -HL DUP DEVICE parameter defines a specific device upon which to create the
duplicate hIstorical log, if one was specified.
ASSIGN SITE PARAMETER -HL DUP DEVICE ddd
where:
ddd - Device code. Any configured three-character logical device name is a
valid argument. If a specific device is not assigned, FMS will create
the historical log file on a device of its choosing.
Historical Log Commitment Entry
The -HL COMMITMENT ENTRY parameter determines whether a historical log entry is
made each time a commitment is taken:
ASSIGN SITE PARAMETER -HL COMMITMENT ENTRY a
)
/
where:
a - 0 or NO or OFF prevents a historical log entry from being made each time
a commitment is taken.
1 or YES or ON (default) causes a historical log entry to be made each
time a commitment is taken.
Historical Log Entry For Each Protected File Open
The -HL FILE OPEN ENTRY parameter determines whether a historical log entry is
made each t~e a protected file is opened:
ASSIGN SITE PARAMETER -HL FILE OPEN ENTRY a
where:
a - 0 or NO or OFF prevents a historical log entry from being made each time
a protected file is opened.
1 or YES or ON (default) causes a historical log entry to be made each
time a protected file is opened.
4-19
DH18-03
Historical Log Entry For Each Protected File Close
The -HL FILE CLOSE ENTRY parameter determines whether a historical log entry is
made each time a protected file is closed:
c
ASSIGN SITE PARAMETER -HL FILE CLOSE ENTRY a
where:
a - 0 or NO or OFF prevents a historical log entry from being made each time
a protected file is closed~
1 or YES or ON (default) causes a historical log entry to be made each
time a protected file is closed.
SITE PARAMETER FOR CONCURRENCY CONTROL
Maximum Reservations Retained For One Process
The -CC PROCESS PAGES parameter specifies the maximum number of concurrency
control-reservations (i.e., data base pages and files) retained for a single
process:
ASSIGN SITE PARAMETER -CC PROCESS PAGES r
(
where:
I" -
Maximum number of reservations per process. The valid range for this
value is 1-25900 reservations. The default is 25900. (One reservation
requires five words of memory for each record and five words for each
file. )
SITE PARAMETERS FOR BUFFERING
Maximum Number Of Buffers In Default Buffer Pools
The -DEFAULT BP BUFFERS parameter specifies the maximum number of buffers that
can exist in-each buffer pool:
ASSIGN SITE PARAMETER -DEFAULT BP BUFFERS b
where:
b - Maximum number of buffers in each buffer pool. The value can range from
1 to 512. By default, 40 buffers exist in each buffer pool.
(
4-20
DH18-03
This parameter does not necessarily specify the actual number of buffers
assigned to each buffer pool. For example, if the buffer pool limit is 20 and
a process requests 12 buffers, then 12 buffers are assigned~ However, if the
buffer pool limit is 20 and a process requests 24 buffers, an error status will
be returned.
Note that the number of buffers in a buffer pool is reduced for each open file
by the value of the PFIO OPEN BUFFERS parameter. For example, if the
DEFAULT BP BUFFERS value-is 40 and the PFIO OPEN BUFFERS value is 10, 30
buffers-are available from the buffer pool after-one file has been opened.
Buffers Allocated To Protected Files
The -PFIO OPEN BUFFERS parameter specifies the number of buffers allocated to
each protected-file at file-open time in a batch or TPE processing environment:
ASSIGN SITE PARAMETER -PFIO OPEN BUFFERS b
where:
b - Number of buffers allocated to each protected file at file-open time.
This value can range from 1 to 512. The default is 2.
Buffer Management Parameter And Descriptor Consistency Checks
\
)
The -BM PARAMETER CHECK parameter specifies whether buffer management parameter
and descriptor consistency checks are to be performed:
ASSIGN SITE PARAMETER -BM PARAMETER CHECK c
where:
c - 0 or NO or OFF causes the consistency checks to be bypassed, so that
Buffer Management will execute faster.
1 or YES or ON (default) causes the consistency checks to be performed.
If a problem arises while the consistency check is bypassed, reinstate the
check; then rerun the process to verify parameters and descriptors before
attempting to analyze the problem.
)
DH18-03
Compressed And Full Control Interval Journalization
(
The -BM COMPRESSED JOURNAL parameter provides a choice between compressed
journalization and-full control interval journalization:
ASSIGN SITE PARAMETER -BM COMPRESSED JOURNAL c
where:
c - 0 or NO or OFF causes full control interval journalization, so that
entire control intervals (i.e., the modified record(s) and all
unmodified records for that control interval) are written to the
appropriate journal(s).
1 or YES or ON (default) causes compressed journalization, so that when
,modifying a file with ABORT/ARCHIVE/, ABORT/ROLLBACK/, and/or
RDERR/JOURNAL/ protection, only the modified control interval portions
of the file are journalized. '(An algorithm divides each file control
interval into partitions containing a minimum of 64 words per
partition. A maximum of 16 partitions is created.)
Number Of Modifications Before Control Interval Written
The -AJ NFIELDS parameter defines the maximum number of times a specific
control-interval can be modified before the entire control interval is written
to the after journal:
ASSIGN SITE PARAMETER -AJ NFIELDS f
where:
f - Maximum number of times a specific control interval can be modified
before the entire control interval is written to the after journal.
valid range for this value is 1-16. The default value is 8.
The
Minimize Before Image Journalization
The -BI'SUPPRESSION ENTRIES parameter is used to modify the number of internal
entries-used to minimize before image journalization:
where:
g -
Number of internal entries. The valid range for this value is 0-280.
The default value is 0 (i.e., before image journalization is not
minimized).
4-22
DH18-03
Maximize Butters For Access Methods
~
~
The -MOVE MODE MAX BUF parameter is used to modify the maximum number of
buffers for each fIle open that a particular access method (e.g., Relational
File Manager (RFM» can allocate:
ASSIGN SITE PARAMETER -MOVE MODE MAX BUF m
where:
m - Maximum number of buffers.
default value is 10.
The valid range for this value is 1-50.
The
SITE PARAMETER FOR WIRED REAL MEMORY FOR INTEGRATED SOFTWARE
The -SET MAX WIRED PAGES parameter allows the site to exercise some control
over system performance by allowing the Shared Domain Loader (SnSHARD) to wire
the desired number of pages:
ASSIGN SITE PARAMETER -SET MAX WIRED PAGES n
where:
\
)
n - Maximum number of pages to be wired for Integrated Software. The value
specified can range from 40 to 16384 pages (1K). If a value is not
specified, the GCOS 8 default of 511 is applied.
I
If too many pages are wired, other jobs may swap in and out of memory,
degrading system performance. If too few pages are wired, jobs that access
protected files may abort. For more information about determining memory
requirements, refer to "Determining Minimum Wired Real Memory Page
Requirements" later in this section.
SITE PARAMETER FOR VIRTUAL MEMORY
The -SC VIRTUAL BUFFER SIZE parameter is used to specify the size of the
Virtual-memory buffer used by Session Control:
ASSIGN SITE PARAMETER -SC VIRTUAL BUFFER SIZE m
where:
m - Number of pages. The valid range is 16-4080 pages (1K). The default is
1000. If m > 1000, the value of the VSPACE parameter on the $ RESOURC
statement must be increased.
)
4-23
DH18-03
SITE PARAMETERS FOR TRACES
(
Integrated Software Trace Buffer Size
The -TRACE BUFFER SIZE parameter specifies the size of the buffer used for
Integrated-Software trace event information:
ASSIGN SITE PARAMETER -TRACE BUFFER SIZE n
where:
n - Number of buffers. The valid range is 1 to 4. Each buffer has a size
of 4K words. Thus the total buffer size may be 4K, 8K, 12K, or 16K
words.
Increasing the default size during debugging sessions may be useful. For more
information on Integrated Software trace, refer to the GCOS 8 OS Protected File
Administration Guide.
Internal Traces For Specific Domains
Site parameters are provided to cause generation of internal traces in the
following specific domains, to collect trace-event information that might
otherwise be overwritten in the Integrated Software trace:
o Session Control (SC)
. 0
Tenant Management (TM)
o Workstation Management (WM)
o Protected File 1/0 (PFIO)
These parameters are:
ASSIGN SITE PARAMETER -SC INTERNAL TRACE t
ASSIGN SITE PARAMETER -TM INTERNAL TRACE t
ASSIGN SITE PARAMETER -WM INTERNAL TRACE t
ASSIGN SITE PARAMETER -PFIO INTERNAL TRACE t
where:
t - 0 or NO or OFF (default) turns off the internal trace in the specified
domain.
1 or YES or ON enables the internal trace in the specified domain.
4-24
DH18-03
SITE PARAMETERS FOR INTEGRATED SOFTWARE STATISTICS
Statistical information provided by Integrated Software can be extremely useful
to the site for system-tuning purposes. The printing of both process-level and
system-level Integrated Software statistics can be controlled through use of
the following parameters. The site can specify file code(J* or P*), report
code, and whether or not each group of statistics should be printed.
Process-level statistics are available for the Buffer Management, Global Data
Management, Before Journaling, After Journaling, Protected File IIO, and
I-D-S/II domains. System-level statistics are available for Buffer Management,
Global Data Management, After Journaling, Concurrency Control, Historical
Logging, and Protected File IIO domains. Refer to the GCOS 8 OS System
Operating Techniques manual for more information on these parameters, as well
as a description of their output.
Print Integrated Software Statistics (Normal Termination)
The -ISSTAT ENABLE parameter determines whether Integrated Software statistics
are to be printed if a process terminates normally:
ASSIGN SITE PARAMETER -ISSTAT ENABLE x
where:
x - 0 or NO or OFF (default) inhibits printing of statistics if a process
terminates normally.
I
1 or YES or ON enables printing of statistics if a process terminates
normally.
I
\
/
Print Integrated Software Statistics (Abnormal Termination)
The -ISSTAT ABNORMAL TERM parameter determines whether Integrated Software
statistics are to be-printed if a process terminates abnormally:
ASSIGN SITE PARAMETER -ISSTAT ABNORMAL TERM x
where:
x - 0 or NO or OFF (default) inhibits printing of statistics if a process
terminates abnormally.
1 or YES or ON enables printing of statistics if a process terminates
abnormally.
4-25
DH18-03
I
I
Integrated Software Statistics Output File Code
The -ISSTAT FILE CODE parameter defines the output file code for Integrated
Software statistics:
ASSIGN SITE PARAMETER -ISSTAT FILE CODE c
where:
c - Output file code. Valid file codes are J* (default) or P*. If the p*
file code is selected, a report code must also be specified via the
-ISSTAT REPORT CODE parameter.
Integrated Software Statistics Report Code
If the p* file code is selected via the -ISSTAT FILE CODE parameter, the
-ISSTAT REPORT CODE parameter must be used to define-a report code for
Integrated Software statistics:
ASSIGN SITE PARAMETER -ISSTAT REPORT CODE r
where:
r - Report code.
code is 74.
Valid report codes are 0-77 (octal).
The default report
Print All Integrated Software System-Level Statistics
The -ISSTAT ALL SYS LEVEL parameter specifies whether all system-level
statistics (i.e:, Buffer ~~nagement, Global Data Management, After Journal,
Concurrency Control, Historical 'Log', and Protected File 1/0 domains) are to be
printed:
ASSIGN SITE PARAMETER
~~SSTAT
ALL SYS_LEVEL x -PRINT ZERO Y
where:
I
x - 0 or NO or OFF inhibits printing of all system-level statistiCS,
regardless of the values of any of the individual system-level
statistics parameters.
1 or YES or ON causes printing of all system-level statistics,
regardless of the values of any of the individual system-level
statistics parameters.
If a value is not specified for x, the printing of system-level
statistics for one or more individual domains may be enabled by the
value of the individual system-level statistics parameter.
·4;...26
DH18-03
y - 0 or NO or OFF suppresses printing of zero-valued system-level
statistical fields, regardless of the value of any PRINT ZERO parameter
used with individual system-level statistics parameters.1 or YES or ON causes printing of zero-valued system-level statistical
fields, regardless of the value of any PRINT ZERO parameter used with
individual system-level statistics parameters.
I.
I
If a value is not specified for y, the printing of zero-valued
system-level statistical fields for individual domains may be controled
by the value of the PRINT ZERO parameter used with the individual
system-level statistics parameter.
Print Buffer Management Domain System-Level Statistics
The -ISSTAT BM SYS LEVEL parameter specifies whether system-level Buffer
Management Domain statistics are to be printed. This parameter is ignored if a
value has been specified (YES or NO) for the -ISSTAT ALL SYS LEVEL parameter.
ASSIGN SITE PARAMETER -ISSTAT BM SYS LEVEL xxx -PRINT ZERO yyy
where:
x - 0 or NO or OFF inhibits printing of system-level Buffer Management
Domain statistics (default).
\
)
\
1 or YES or ON causes printing of system-level Buffer Management Domain
statistics.
y - 0 or NO or OFF suppresses printing of zero-valued fields (default).
1 or YES or ON causes printing of zero-valued fields.
I
I
I
I
Print Global Data Management Domain System-Level Statistics
The -ISSTAT DM SYS LEVEL parameter specifies whether system-level Global Data
Management Domain statistics are to be printed. This parameter is ignored if a
value has been specified (YES or NO) for the -ISSTAT_ALL_SYS_LEVEL parameter.
ASSIGN SITE PARAMETER -ISSTAT DM SYS LEVEL xxx -PRINT ZERO yyy
where:
x - 0 or NO or OFF inhibits printing of system-level Global Data Management
Domain statistics (default).
1 or YES or ON causes printing of system-level Global Data Management
Domain statistics.
4-27
DH18-03
I
I
y - 0 or NO or OFF suppresses printing of zero-valued fields (default).
1
or YES or ON causes printing of zero-valued fields.
Print After Journal Domain System-Level Statistics
The -ISSTAT AJ SYS LEVEL parameter specifies whether system-level After Journal
Domain statistics are to be printed. This parameter is ignored if a value has
been specified (YES or NO) for the -ISSTAT_ALL_SYS_LEVEL parameter.
ASSIGN SITE PARAMETER -ISSTAT AJ SYS LEVEL xxx -PRINT ZERO yyy
where:
I
or NO or OFF inhibj,ts printing of system-level After Journal Domain
statistics (default).
x - 0
I
1 or YES or ON causes printing of system-level After Journal Domain
statistics.
I
y - 0 or NO or OFF suppresses printing of zero-valued fields (default).
I
1
or YES or ON causes printing of zero-valued fields.
Print Concurrency Control Domain System-Level Statistics
The -ISSTAT CC SYS LEVEL parameter specifies whether system-level Concurrency
Control Domain-statistics are to be printed. This parameter is ignored if a
value has been specified (YES or NO) for the -ISSTAT_ALL_SYS_LEVEL parameter.
ASSIGN SITE PARAMETER -ISSTAT CC SIS LEVEL xxx -PRINT ZERO yyy
where:
I
I
I
I
x - 0 or NO or OFF inhibits printing of system-level Concurrency Control
Domain statistics (default).
1 or YES or ON causes printing of system-level Concurrency Control
Domain statistics.
y - 0 or NO or OFF suppresses printing of zero-valued fields (default).
1
or YES or ON causes printing of zero-valued fields.
Print Historical Log Domain System-Level Statistics
The -ISSTAT HL SYS LEVEL parameter specif-ies whether system-level Historical
Log Domain statistics are to be printed. This parameter is ignored if a value
has been specified '(YES or NO) for the -ISSTAT ALL SIS LEVEL parameter.
4-28
DH18-03
(
ASSIGN SITE PARAMETER -ISSTAT HL SYS LEVEL xxx -PRINT ZERO yyy
where:
x - 0 or NO or OFF inhibits printing of system-level Historical Log Domain
statistics (default).
1 or YES or ON causes printing of system-level Historical Log Domain
statistics.
y - 0 or NO or OFF suppresses printing of zero-valued fields (default).
1 or YES or ON causes printing of zero-valued fields.
I
I
I
I
Print Protected File I/O Domain System-Level Statistics
The -ISSTAT PFIO SYS LEVEL parameter specifies whether system-level Protected
File IIO Domain statistics are to be printed. This parameter is ignored if a
value has been specified (YES or NO) for the -ISSTAT_ALL_SYS_LEVEL parameter.
ASSIGN SITE PARAMETER -ISSTAT PFIO SYS LEVEL xxx -PRINT ZERO yyy
where:
x - 0 or NO or OFF inhibits printing of system-level Protected File IIO
Domain statistics (default).
\
)
1 or YES or ON causes printing of system-level Protected File IIO Domain
statistics.
y - 0 or NO or OFF suppresses printing of zero-valued fields (default).
1 or YES or ON causes printing of zero-valued fields.
I
I
I
I
Print All Integrated Software Process-Level Statistics
The -ISSTAT ALL PROe LEVEL parameter specifies whether all process-level
statistics Ti.e~, Buffer Management, Global Data Management, Before Journal,
After Journal, Protected File IIO, and I-D-S/II domains) are to be printed:
ASSIGN SITE PARAMETER -ISSTAT ALL PROe LEVEL x -PRINT ZERO Y
where:
I
x - 0 or NO or OFF inhibits printing of all process-level statistics,
regardless of the values of any of the individual process-level
statistics parameters.
I
1 or YES or ON causes printing of all process-level statistics,
regardless of the values of any of the individual process-level
statistics parameters.
4-29
DH18-03
If a value is not specified for x, the printing of process-level
statistics for one or more individual domains may be enabled by the
value of the individual process-level statistics parameter.
y - 0 or NO or OFF suppresses printing of zero-valued process-level
statistical fields, regardless of the value of any PRINT ZERO parameter
used with individual process-level statistics parameters~
1 or YES or ON causes printing of zero-valued process-level statistical
fields, regardless of the value of any PRINT ZERO parameter used with
individual process-level statistics parameters.
If a value is not specified for y, the printing of zero-valued
process-level statistical fields for individual domains may be controled
by the value of the PRINT ZERO parameter used with the individual
process-level statistics parameter.
Print Butter Management Domain Process-Level Statistics
The -ISSTAT BM PROe LEVEL parameter specifies whether process-level Buffer
Management Domain statistics are to be printed. This parameter is ignored if a
value has been specified (YES or NO) for the -ISSTAT ALL_PROe_LEVEL parameter.
ASSIGN SITE PARAMETER -ISSTAT BM PROe LEVEL xxx -PRINT ZERO yyy
where:
x - 0 or NO or OFF inhibits printing of process-level Buffer Management
Domain statistics.
1 or YES or ON causes printing of process-level Buffer Management Domain
statistics (default).
y - 0 or NO or OFF suppresses printing of zero-valued fields (default).
1 or YES or ON causes printing of zero-valued fields.
Print Global Data Management Domain Process-Level Statistics
The -ISSTAT DM PROe LEVEL parameter specifies whether process-level Global Data
Management Domain statistics are to be printed. This parameter is ignored if a
value has been specified (YES or NO) for the -ISSTAT ALL PROe LEVEL parameter.
ASSIGN SITE PARAMETER -ISSTAT DM PROe LEVEL xxx -PRINT ZERO yyy
where:
x - 0 or NO or OFF inhibits printing of process-level Global Data Management
Domain statistics.
4-30
DH18-03
(
1 or YES or ON causes printing of process-level Global Data Management
Domain statistics (default).
y -
0 or NO or OFF suppresses printing of zero-valued fields (default).
1 or YES or ON causes printing of zero-valued fields.
Print Before Journal Domain Process-Level Statistics
The -ISSTAT BJ PROe LEVEL parameter specifies whether process-level Before
Journal Domain-statistics are to be printed. This parameter is ignored if a
value has been specified (YES or NO) for the -ISSTAT ALL PROe LEVEL parameter.
ASSIGN SITE PARAMETER -ISSTAT BJ PROC LEVEL xxx -PRINT ZERO yyy
where:
x - 0 or NO or OFF inhibits printing of process-level Before Journal Domain
statistics.
1 or YES or ON causes printing of process-level Before Journal Domain
statistics (default).
y -
0 or NO or OFF suppresses printing of zero-valued fields (default).
1 or YES or ON causes printing of zero-valued fields.
Print After Journal Domain Process-Level Statistics
The -ISSTAT AJ PROC LEVEL parameter specifies whether process-level After
Journal Domain-statistics are to be printed. This parameter is ignored if a
value has been specified (YES or NO) for the -ISSTAT_ALL_PROC_LEVEL parameter.
ASSIGN SITE PARAMETER -ISSTAT AJ PROC LEVEL xxx -PRINT ZERO yyy
where:
x - 0 or NO or OFF inhibits printing of process-level After Journal Domain
statistics.
y -
I
1 or YES or ON causes printing of process-level After Journal Domain
statistics (default).
I
0 or NO or OFF suppresses printing of zero-valued fields (default).
I
1 or YES or ON causes printing of zero-valued fields.
I
4-31
DH18-03
Print Protected File 110 Domain Process-Level Statistics
The -ISSTAT PFIO PROe LEVEL parameter specifies whether process-level Protected
File I/O Domain statistics are to be printed. This parameter is ignored if a
value has been specified (YES or NO) for the -ISSTAT_ALL_PROC_LEVEL parameter.
ASSIGN SITE PARAMETER -ISSTAT PFIO PROe LEVEL xxx ,-PRINT ZERO yyy
where:
x - 0 or NO or OFF inhibits printing of process-level Protected File I/O
Domain statistics.
1 or YES or ON causes printing of process-level Protected File I/O
Domain statistics (default).
y - 0 or NO or OFF suppresses printing of zero-valued fields (default).
1 or YES or ON causes printing of zero-valued fields.
Print I-D-S/II Domain Process-Level Statistics
The -ISSTAT IDS2 PROe LEVEL parameter specifies whether process-level I-D-S/II
Domain (Shared Dat q Base Control System (SDBCS» statistics are to be printed.
This parameter is ignored if a value has been specified (YES or NO) for the
-ISSTAT_ALL_PROC_LEVEL parameter.
ASSIGN SITE PARAMETER -ISSTAT IDS2 PROC LEVEL xxx -PRINT ZERO yyy
where:
x - 0 or NO or OFF inhibits printing of process-level I-D-S/II Domain
statistics.
1 or YES or ON causes printing of process-level I-D-S/II Domain
statistics (default).
y - 0 or NO or OFF suppresses printing of zero-valued fields (default).
1 or YES or ON causes printing of zero-valued fields.
Print Statistics For Batch Processes
The ~ISSTAT BATCH PROCESS parameter specifies whether Integrated Software
statistics for batch processes are to be printed:
ASSIGN SITE PARAMETER -ISSTAT BATCH PROCESS x
where:
x - 0 or NO or OFF inhibits printing of statistics for batch processes.
4-32
DH18-03
c
)
1 or YES or ON causes printing of statistics for batch processes
(default).
I
2 or ISSTAT causes printing of statistics for batch processes that
specified the ISSTAT option on the JCL activity definition statement.
I
Print Statistics For Workstation Processes
The -ISSTAT WS PROCESSES parameter specifies whether Integrated Software
statistics for-workstation processes are to be printed:
ASSIGN SITE PARAMETER -ISSTAT WS PROCESSES x
where:
x - 0 or NO or OFF inhibits printing of statistics for workstation processes
(default).
1 or YES or ON causes printing of statistics for workstation processes.
2 or ISSTAT causes printing of statistics for workstation processes that
specified the ISSTAT option on the JCL activity definition statement.
I
I
I
Print Statistics For DM-IV/TP Processes
\
)
The -ISSTAT TP PROCESSES parameter specifies whether Integrated Software
statistics for-DM-IV/TP processes are to be printed:
ASSIGN SITE PARAMETER -ISSTAT TP PROCESSES x
where:
x - 0 or NO or OFF inhibits printing of statistics for DM-IV/TP pr'ocesses
(default).
1 or YES or ON causes printing of statistics for DM-IV/TP processes.
2 or ISSTAT causes printing of statistics for DM-IV/TP processes that
specified the ISSTAT option on the JCL activity definition statement.
Print Statistics For TDS Prooesses
The -ISSTAT_TDS_PROCESSES parameter specifies whether Integrated Software
statistics for TDS processes are to be printed. Specifying a value of YES for
the parameter indicates that the statistics are to be printed. Valid arguments
are YES or NO. NO is the default value. The directive containing this
parameter is as follows:
ASSIGN SITE PARAMETER -ISSTAT TDS PROCESSES x
4-33
DH18-03
I
I
I
where:
I
(
x - 0 or NO or OFF inhibits printing of statistics for TDS processes
(default).
I
1 or YES or ON causes printing of statistics for TDS processes.
I
2 or ISSTAT causes printing of statistics for TDS processes that
specified the ISSTAT option on the JCL activity definition statement.
Print Statistics For TS8 Processes
The -ISSTAT TS8 PROCESSES parameter specifies whether Integrated Software
statistics for TS8 processes are to be printed:
ASSIGN SITE PARAMETER -ISSTAT TS8 PROCESSES x
where:
x - 0 or NO or OFF inhibits printing of statistics for TS8 processes.
1 or YES or ON causes printing of statistics for TS8 processes
(default).
2 or ISSTAT causes printing of statistics for Ts8 processes that
specified the ISSTAT option on the JCL activity definition statement.
SITE PARAMETERS FOR WORKSTATIONS
Default pathnames for three Integrated Software files are provided. There may
be some circumstances, however, under which pathname modification is
desirable. For example, before installing a new version of a file, the system
administrator may wish to test file content; by modifying the pathname of the
new (test) version, the file can be accessed without interrupting system
processing that uses the existing version.
Pathnames are provided for the following files:
o Workstation definition data base (WS-DB)
I
0
Workstation management schema file (WCC-1STR)
o Workstation management subschema file (WCC-6STR)
c
4-34
DH18-03
Pathnames for these files are defined via the directives:
ASSIGN SITE PARAMETER -WD_FILE P
where:
p -
File pathname.
The default 1s SYS_SOFTWARE/yyyy/DATA/wC-DB
yyyy - Software Release identifier, such as 3000
where:
File pathname.
p -
The default is SYS_SOFTWARE/yyyy/DATA/WCC-1STR
yyyy - Software Release identifier, such as 3000
where:
p -
File pathname.
The default is SYS_SOFTWARE/yyyy/DATAIWCC-6STR
yyyy - Software Release identifier, such as 3000
\
1
)
Buffer Pools
The CREATE BUFFER POOL directive creates buffer pools for protected files.
Each buffer pool must be assigned a name and a control interval size using this
directive. Other parameters that can be aSSigned specify:
o Minimum and maximum number of buffers comprising the buffer pool
o Number of internal table entries used to minimize before image
journalization
o Whether the buffer pool is public or private
o When the buffer pool is created.
- When Integrated Software is loaded
- When protected files are accessed
4-35
DH18-03
If the CREATE BUFFER POOL directive declares a buffer pool private, the
directive:
c
ASSIGN -PRIVATE BUFFER POOL FILE
must be used to define the pathname (i.e., catalog/file string) of the file
assigned to the pool and the buffer pool name when a process opens the file.
The GCOS 8 OS Integrity Control manual provides a detailed discussion of buffer
pools.
The following directives can be used to define buffer pools and to modify
parameter values. The abbreviated format of the directive or keyword is in
parentheses.
CREATE BUFFER POOL (CBP) aaaaa &
-BUFFER SIZE (-BS or -CI SIZE) bbbbb &
[option\s)]
where option(s) = one or more of the following keyword-argument fields:
[-TYPE ttttt]
[-MIN NUMBER BUFFERS (-MNNB) cccc]
[-MAX-NUMBER-BUFFERS (-MXNB) dddd]
[-POOL ALLOCATION (-PA) eeeee]
[-BI SUPPRESSION ENTRIES (-BSE) fff]
I
ASSIGN -PRIVATE BP FILE &
-BUFFER POOL-NAME (-BPN) aaaaa &
-PATH NAME (~PN or -PATHNAME) ggggg &
-NUMBER BUFFERS (-NB) hhhhh
where:
&
Continuation character, which is required when a directive extends
to more than one line.
aaaaa - Buffer pool name, which can contain from 1 to 12 alphanumeric
characters. No blanks are permitted.
bbbbb - Size of the buffer or control interval, specified in bytes or words,
as indicated by a "B" (default) or "W", respectively, following the
value. The size can range from 256 to 65536 bytes, in increments of
256 bytes. Values that are not multiples of 256 bytes are rounded
up to the next 256-byte increment.
cccc
- Minimum number of buffers in the buffer pool.
from 0 to 4096; the default is O.
This value can range
dddd
- Maximum number of buffers in the buffer pool. This value can range
from 1 to 4096; the default is 40 or the MIN NUMBER BUFFERS value if
cccc i~ greater than 40.
DH18-03
ttttt - Literal identifying the buffer pool type:
PRIVATE = private buffer pool
PUBLIC
= public
buffer pool
eeeee - Literal identifying when the buffer pool is created:
IMMEDIATE
DEFERRED
fff
= Created
= Created
when Integrated Software is loaded
when protected files are accessed
Number of entries used to suppress before images.
default is O.
Range is 0-280,
I
ggggg - Pathname of the protected file assigned to the private buffer pool
bbbbb. The pathname cannot contain passwords.
hhhhh - Number of buffers to be assigned when a process opens the file
(0-1024; default is 0). When this parameter has a value of 0, the
value specified for ASSIGN SITE PARAMETER -PFIO OPEN BUFFERS
(buffers allocated at file-open) is used. When-a value other than 0
is specified, it overrides the value specified for
-PFIO OPEN BUFFERS.
TERMINATING INTEGRATED SOFTWARE
Integrated Software must be explicitly aborted to terminate execution. The
operator must enter an ABORT SHARD console command. This makes Integrated
Software unavailable for starting any new processes; however, no negative
effects result on any processes currently executing, as enough SHARD facilities
remain active to continue processing until all processing completes. Thus, any
attempt to terminate SHARD prematurely is delayed.
If SISHARD hangs in termination, use the following procedure:
1. Enter "WORKST LIST" at the console to determine the active workstations.
Then abort each workstation by entering "WORKST ABORT xxxx" for each of
the active workstations (where xxxx is the workstation id).
2. Run SHRNM to determine if jobs are still tied to SHARD, then abort them.
3. Wait until all abort messages for requested jobs have been typed on the
console log.
SISHARD will then terminate.
To restart Integrated Software after it terminates, execute the privileged
slave program that loads the software into memory. (Refer to "Loading
Integrated Software For Execution" earlier in this section for additional
information. )
)
4-37
DH18-03
*
ENSURING SUFFICIENT MEMORY FOR INTEGRATED SOFTWARE EXECUTION
Integrated Software memory requirements are of the following categories.
1. Virtual memory for all Integrated Software domains, Session Control
buffers, and data base buffers. The $ RESOURC statement that is
incorporated into the Honeywell Bull-supplied job stream which loads
Integrated Software into memory requests 3800K of virtual memory. This
value is normally sufficient for most sites.
2. Wired real memory pages for all buffers reserved for all batch and
workstation processes executing portions of Integrated Software. The
maximum number of real memory pages that Integrated Software can wire is
defined via the -SET_MAX_WIRED_PAGES parameter.
NOTES: a. Every 1000K of virtual memory requires 1K of table space in
wired real memory pages. Therefore, if less than the default
allocation of virtual memory (3800K) is required, some real
memory space can be saved by reducing the default allocation
via the $ RESOURC statement.
b. Real memory requirements for Integrated Software are initially
defined via the RSPACE filed on the $ RESOijRC statement in the
job stream that spawns Integrated Software into execution. By
default, 100K of real memory is reserved for Integrated
Software. However, if this value is understated or overstated,
the GCOS 8 System Dynamic Memory Manager program dynamically
modifies allocated real memory for Integrated Software to meet
the immediate demand. Integrated Software's working set is
dynamically increased to reduce page faults during peak periods
of processing. Conversely, memory is returned to the pool of
available space for other uses during low-processing periods.
If the $ RESOURC statement specifies insufficient space for the VSPACE, which
Integrated Software is to load, Integrated Software aborts and an abort code of
VF is issued.
The SDLD directive ASSIGN SITE PARAMETER -SET MAX WIRED PAGES establishes the
maximum number of real memory pages that Integrated ~oftware may wire. The
default for this parameter is 511(K). The range for the parameter value ·is
40-16384(K). If this parameter value is set too low, processes attempting to
wire memory will abort. If the parameter value is set too high, performance of
other applications run on the system may be impacted.
Processes encountering an Integrated Software memory allocation problem may
abort with the error message:
UFAS ERR TYPE 8 - ERR' 015:
UNABLE TO RECOGNIZE 10 STATUS 477702000000 ON FILE ff
or:
IMG/WSM ERROR RETURN
issued to the Execution Report (where ff = file code).
4-38
DH18-03
&
~
Determining Minimum Wired Real Memory Page Requirements
Determining the number of wired real memory pages for Integrated Software may
require some experimentation. The following formula yields a value that may be
used as a starting point for determining a value for the -SET MAX WIRED PAGES
parameter (i_e., maximum number of real memory pages that Integrated Software
may wire). This wired real memory is used for executing Integrated Software
and for other job-related functions (e.g., journalizing after images). When
using this formula, it is recommended that each variable value specified
represent the maximum expected during the load of Integrated Software.
The recommended approach for setting a final value for -SET MAX WIRED PAGES is
to determine a value such that if all memory wired for Integrated Software
(i.e., SNUMB of SHARD) were used, sufficient memory would still be available to
support remaining system functions.
minimum value for -SET MAX WIRED PAGES
Variable
S
=S
+
P + B+ J + A + H
Description
Integrated Software domain wired pages.
14 + (4
* n)
where n is the value specified via the site parameter
-TRACE BUFFER SIZE n
which determines the number of 4K trace buffers.
\
P
Wired real memory pages for system-wide protected file services.
This value is required any time one or more executing jobs access
protected flIes (i.e., files created with the ACCESS/MONITOR/,
ABORT/ROLLBACK/, ABORT/ARCHIVE/, ACCESS/CONCURRENT/, and/or
RDERR/JOURNALI option specified).
This value is determined via the formula
(3
* F)
+ 5
where:
F-Number of different control interval sizes for all jobs
accessing protected. files at anyone time. For example, if a
total of 10 jobs access protected files at one time or another
but only 3 jobs access the files at anyone time and if control
interval sizes are 256 and 512 (words), specify 2.
Consequently, the number of wired pages-required for system-wide
protected file service is
(3
*
2) + 5
= 11
(K)
4-39
DH18-03
Variable
B
Description
Wired real memory pages for buffer space required for protected
files accessed by executing jobs. Determine this value via the
formula
F
*C•
N
where:
F-Number of allocations to protected files of the same control
interval size (C) for all executing jobs concurrently accessing
those files.
C - Control interval size (in words) of the protected files.
is the page size for the files.
N - Default value is 2.
parameter:
This
Other values may be specified via the site
-PFIO OPEN BUFFERS bbb.
Repeat this formula for each different control interval size and
derive a cumulative RSPACE value from the totals; then divide by
1024 to get the number for wired pages. Round the result upward to
the nearest integer.
For example, three executing jobs access nine protected files with
varying control interval sizes. Four files have 256-word control
interval Sizes, four files have 512-word control interval Sizes, and
one file has a 1024-word control interval size. The value for B
would be:
[(4*256*2) + (4*512*2) + (1*1024*2)]/1024
J
= 8(K)
Wired real memory for journalizing before images. If any file
accessed by a process was created with the ABORT/ROLLBACK/ option,
this value is required. Determine the value via the formula
3 + (3 * C * P)/1024
where:
C - Value for parameter -BJ CISIZE (in words).
words.
Default is 704
P - Maximum number of processes using before journals at anyone
time. For example, i f a total of four batch processes use
before journals at one time or another, but only two processes
are executing at anyone time, specify 2. Consequently, the
amount of wired pages required for before journals (assuming the
default value of 704 words is in effect for -BJ_CISIZE) is:
4-40
DH18-03
~
Variable
Description
--------------------------------------------------------
3 + 3*704*2
1024
=8
(K)
Refer to the GCOS 8 OS TP8 Administrator's Guide for information
on the additional wired memory pages required for TP8
workstation processing.
A
Wired real memory pages for system-level journals (i.e., archived
before journals, after journals, and checkpoint journal). Specify
18K for the first (or only) journal implemented. For each
additional journal created, add the following:
2
*B
where:
B - Control interval size (in K words) of the journal (i.e., value
for BLKSIZ option of Create Journal (CRJR) command)
For example, assuming that an installation has one archived
before journal and one after journal and that both journals are
created with a BLKSIZ value of 2 (K), the value for A would be
18 + (2 • 2) = 22 (K)
~
j
H
Wired real memory pages for the historical log. If this feature is
implemented (i.e., SDLD parameter -HISTORICAL LOG has a value of
YES), this value is required. Determine the value via the formula
(C • 3)/1024
where:
C - Control interval size of historical log (SDLD parameter
-HL CISIZE) in words.
Round the result upward to the nearest integer.
For example, if -HL CISIZE has a value of 2816 bytes (704 words)
the value for H is (704
* 3)/1024 = 3
4-41
DH18-03
The following example approximates the minimum wired real memory pages required
at an installation where (1) -TRACE BUFFER SIZE parameter has a value of 1
(default); (2) there are two control interval sizes for protected files; (3)
four files have a control interval size of 256-words and four files have a
control interval size of 512 words; (4) a maximum of two processes journalize
before images at anyone time and the before journal has a control interval
size of 2816 bytes (704 words); (5) one after journal and one archived before
journal have been created; and (6) historical log is implemented with a control
interval size of 28816 bytes (704 words).
S
P
B
=
=
=
J =
A =
H=
18
11
6
8
22
3
(K)
(K)
(K)
(K)
(K)
(K)
14 + (4 • 1)
(3 • 2) + 5
[(4 • 256 • 2) + (4 • 512 • 2)]/1024
3 + (3 • 704 • 2)/1024
18 + (2 • 2)
(704 • 3)/1024
68 (K)
EXAMPLES APPROIIMATING WIRED REAL MEMORY PAGES REQUIREMENTS
The following examples suggest minimum wired real memory page reqUirements when
batch processes access protected files. As previously indicated, these
requirements represent a starting point for determining a value for the
-SET_MAX_WIRED_PAGES parameter.
,1. The following examples assume one 4K trace buffer.
additional 4K trace buffer.
Add 4 for each
2. The following examples assume PFIO OPEN BUFFERS is 2.
3. Each additional data base file having the same control interval size as
those files already considered in the wired pages computation creates a
requirement for additional wired real memory pages. The following formula
needs to be evaluated for each such additional data base file:
B = (F • C •
N) /
1024
where:
B = the number of wired real memory pages required for this file
F = the number of processes accessing this file concurrently
C = control interval Size, in words
N = 2 open buffers
If B is not an integer it should be increased to the next larger integer.
4. The value of B should be increased by 3 for each additional control interval
size that is different from those already considered in the wired pages
computation, to represent the overhead of each buffer pool.
4-42
DH18-03
Accessing One Protected File
~
J
NOTE: The value of B should be increased by 1 for each additional process
accessing the data base file.
1. A minimum of 36 wired real memory pages is required when two batch processes
access one data base file having the following characteristics:
o
I
The file is allocated with Write/Concurrent permission.
o The file control interval size is 512 words •
o
.
ACCESS/MONITOR/ and/or ABORT/ROLLBACK/ protection is specified.
2. A minimum of 54 wired real memory pages is required when two batch processes
access one data base file having the following characteristics:
o
The file is allocated with Write/Concurrent permission.
o
The file control interval is 512 words.
o
ACCESS/MONITOR/, ABORT/ROLLBACK/, and RDERR/JOURNAL/ permissions are
specified.
I
*
Accessing Multiple Protected Files Of Same Control Interval Size
)
NOTE: The value of B should be increased by 2 for each additional process
accessing the data base files.
I
1. A minimum of 38 wired real memory pages is required when two batch processes
access two data base fj.les, each of which has the following characteristics:
I
o
The files are allocated with Write/Concurrent perruission.
o The file control interval size is 512 words.
o
ACCESS/MONITOR/ and/or ABORT/ROLLBACK/ protection is specified.
DH18-03
I
2. A minimum ef 56 wired real memery pages is required when two. batoh preoesses
acoess two. data base files, eaoh ef whioh has the fellewing characteristios:
0.
The files are alleoated with Write/Cenourrent permissien.
0.
The file centrel interval size is 512 werds.
0.
ACCESS/MONITOR/, ABORT/ROLLBACK/, and RDERR/JOURNAL/ pretections are
specified.
*
Aocessing Multiple Protected Files Of Different CI Size
I
NOTE: The value ef B sheuld be increased by 2 fer each additienal precess
accessing the data base files.
I
1. A minimum ef 41 wired real memery pages is required when two. batoh precesses
access two. data base files, which have the fellewing charaoteristios:
I
*
0.
The files are allecated with Write/Cenourrent permissien.
0.
One file has a centrel interval size of 320 werds; the ether file has
a centrel interval size of 512 werds.
0.
ACCESS/MONITOR/ and/o.r ABORT/ROLLBACK/ preteotien is specified fer
each file.
2. A minimum ef 59 wired real memory pages is required when two. batch precesses
access two. data base files, which have the fellewing oharaoteristios:
0.
The files are allecated with Write/Cencurrent perrulssien.
0.
One file has a control interval size o.f 320 words; the other file has
a oentrol interval size of 512 werds.
0.
ACCESS/MONITOR/, ABORT/ROLLBACK/, and RDERR/JOURNAL/ pretectiens are
speoified for eaoh file.
4-44
DH18-03
(
Executing Only Unpurge
The minimum number of wired real memory pages required to execute only the
Unpurge program (i.e., no other processing is occurring in the system) is 15.
If the Unpurge program is executing with any other programs in the product set,
use the preceding formula to determine the wired pages requirement.
The SDLD directives specify configuration information for the load of the
Integrated Software shared domains such as files to be allocated, domains to be
included or excluded, domain patches, start and end of defaults or changes,
comments, and the assignment of a shared space name.
The SDLD directives are initially read from the I* filecode. The "ALLOCATE
-DIRECTIVES" diverts the input to the specified input file. When an EOF is
found in the directives file, processing of input continues from I-.
The SDLD directives syntax is a subset of Honeywell Bull Control Language (RCL)
with the following restrictions:
CHARACTER-SET:
BCD for the I* file ($ DATA limitation); BCD or ASCII for
"Allocate Directives" files.
DELIMITER:
SPACE is a field delimiter. Multiple or leading spaces are
treated as one or ignored, except leading spaces cannot be
used for continuation. The PATCH directive has a fixed
format.
CONTINUATION:
Ampersand (&) specifies input continuation to the next input
statement. DATA after the n&" is ignored (see NOTE).
comments/remarks:
The three-character escape sequence of "-- " (2 hyphens,
space) indicates the beginning of a comment field. Data
following the comment sequence is ignored (see NOTE).
line-numbers:
Line numbers are not allowed;
use $$STRIP on ASCII files.
NOTE: The SDLD LOAD-MAP generator checks arguments for a valid domain name; if
found, the input line is listed in the Load Map for the specified domain.
4-45
DH18-03
SDLD Directives Format
The format of SDLD directives is:
I
•••
where:
= SDLD directive name
= Positional argument,
= SDLD keyword and the
as required
keyword argument (as required).
All keywords must begin with "-" (hyphen) (e.g.,
-LIBRARY, -PATHNAME).
NOTE: phrases may appear in any order. Abbreviated
and forms are valid as described later, under "Directives
Syntax (Specific)".
Share~
Loader Domain Directives Description
The Shared Loader Domain directives specify the actions the SDLD performs and
are described, alphabetically, as follows:
Directive
Description
ALLOCATE
Specifies a dynamically allocated file for SDLD
execution. File options available are:
~--~-----------------
(
-LIBRARY, for virtual domain Q* library
-DIRECTIVES, for diverting the input stream to a
directives file
-BACKDOOR, for a backdoor print of LOAD-t~P
-BPDIRECTIVES, for Buffer Pool directives file
ASSIGN SITE PARAMETER
Assigns site parameter values.
END CHANGES
Specifies the end of the CHANGE directives.
END DEFAULTS
Specifies the end of the DEFAULTS directives.
EXCLUDE DOMAIN
Specifies a virtual domain not to be loaded (i.e.,
excludes a domain specified by the DEFAULT directives).
INCLUDE DOMAIN
Specifies a virtual domain to load.
PATCH or OCTAL
Patches a virtual domain. Either format is fixed and
consistent with the Startup PATCH directives format.
The word PATCH is conventionally used for patches for
Integrated Software.
(
4-46
DH18-03
Directive
Description
Remarks:
Remarks are specified by "-- " in columns 1-3. SDLD
inserts "REMARKS" images in the Load Map when a valid
domain-id is found in columns 73~78.
START CHANGES
Specifies the beginning of the CHANGE directives.
START DEFAULTS
Specifies the beginning of the DEFAULT directives.
NOTE:
The START and END directives specify a block of directives with
consistent usage (i.e., an END DEFAULTS must follow the START DEFAULTS
and precede START CHANGES). Also, MOST directives must be preceded by a
START block directive. An exception is "ALLOCATE -DIRECTIVES", which
may precede the START block directives.
Directives Syntax (Specific)
The general syntactical format for the directives was described earlier, under
"SDLD Directives Syntax (General)". The specific format for each directive is
described alphabetically below, with any valid abbreviations enclosed within
parentheses "()".
ALLOCATE Directive (ALLO)
ALLOCATE
where:
= -LIBRARY (-LIB is the
library-code reference used on the INCLUDE DOMAIN directive
and is two alphanumeric characters. Library code ".Q" is
reserved for the DEFAULT search library.
-BACKDOOR (-BD is ".B".
-DIRECTIVES (~DIRE is ".D".
The default
The default value for
-BPDIRECTIVES (-BPDIRE is "BP".
= -PATHNAME
(cat-string> (-PN is the catalog file string (e.g.,
UMC/CAT1/CAT2/FILE).
DH18-03
= -REQUIRED
(-R)
To specify SDLD fatal abort control if allocation fails.
is the default.
This
-OPTIONAL ( -0 )
To specify SDLD non-fatal abort control if allocation fails.
Examples:
ALLOCATE -LIBRARY AA -PATHNAME UMC/CAT1/CAT2/FILE -REQUIRED
or ALLO -LIB AA -PN UMC/CAT1/CAT2/FILE -R
ALLOCATE -BACKDOOR -PATHNAME UMC/LOAD-MAP -OPTIONAL
or ALLO -BD -PN UMC/LOAD-MAP -0
ALLOCATE -DIRECTIVES -PATHNAME UMC/CHANGES (-REQUIRED is default)
or ALLO -DIRE -PN UMC/CHANGES
ALLOCA.TE -BPDIRECTIVES -PATHNAME umc/BP-DIRE
or ALLO -BPDIRE -PN umc/BP-DIRE
ASSIGN SITE PARAMETER Directive
ASSIGN SITE PARAMETER
where:
is one of the allowed site parameter keywords.
Parameters", earlier in this section.
See "Site
is the value associated with the keyword.
NOTE: Only one site parameter is allowed per ASSIGN_SITE_PARAMETER
directive.
END CHANGES Directive
END CHANGES
This directive specifies the end of the CHANGES directives and must appear
as shown.
END DEFAULTS Directive
END DEF AUL TS
This directive specifies the end of the DEFAULTS directives and must appear
as shown.
4-48
DH18-03
EXCLUDE DOMAIN Directive (EXCL)
EXCLUDE DOMAIN
where:
= Name
of the domain to exclude.
Examples:
EXCLUDE DOMAIN .MZZZZ
or EXCL-.MZZZZ
INCLUDE DOMAIN Directive (INCL)
INCLUDE DOMAIN -LIBRARY
where:
= Name
-LIBRARY
=
= -REQUIRED
of the domain to be included.
specifies the library-code from which the domain is to
be loaded (-LIB is not located,
library n.Q" is searched.
(-R)
To specify SDLD FATAL "ERROR" if the domain search fails.
This is the default.
-OPTIONAL (-0)
To specify a SDLD NON-FATAL nERRORn if the domain search
fails.
Examples:
INCLUDE DOMAIN .MZZZZ -LIBRARY XX -REQUIRED
or -INCL .MZZZZ -LIB XX -R
or -INCL .MZZZZ -LIB XX
PATCH Or OCTAL Directive
The PATCH and OCTAL directives have fixed formats as follows:
4-49
DH18-03
Position Description
1-6
The 1-6 positions of the OCTAL location to patch.
8-12
ftPATCHft or ftOCTALft.
ftPATCH" is used by convention.
The 1-12 positions of the octal value for PATCH or OCTAL
16-27
Comments may be entered. There must be at least one space between
a comment and the preceding field.
n-72
The domain-id to patch.
73-78
This field is required.
Examples:
1
1
8
123
PATCH
000123 OCTAL
6
1234 Set location 123:0 ••• 1234
000000001234 Set location 123:00 ••• 1234
.MZZZZ
.MZZZZ
START CHANGES Directive
ST~RT
CHANGES
This directive specifies the beginning of the CHANGES directives and must
appear as shown. This directive must not precede the START DEFAULTS •••
END DEFAULTS directives. See Figure 4-1, ftOrder Of SDLD Directives".
START DEFAULTS Directive
START DEFAULTS
This directive specifies the beginning of the DEFAULTS directives and must
appear as shown. This directive must precede the START CHANGES directive.
See Figure 4-1, "Order Of SDLD Directives".
Remarks:
The SDLD remarks line is specified by "-- " in columns 1-3 of any directive and
causes all data on that line to be ignored. However, if a valid domain-id is
specified in columns 73-78, the remarks line is displayed in the Load Map
domain-id section.
(
4-50
DH18-03
Examples:
7
3
1
1
8
6
-- THIS IS A "REMARKS" LINE WITH NO DOMAIN-ID
-- THIS IS A "REMARKS" LINE THAT WILL APPEAR IN DOMAIN
-- 0123 PATCH 007777001001 THIS DELETES A PATCH FROM
NOTE:
PATCH directives may be deleted by placing "-in columns 1-3.
.MUTTD
.MZZZZ
n
(dash, dash, space)
START DEFAULTS
-- allocate all DEFAULT library files
ALLOCATE -LIBRARY AA -PATHNAME path-name
ALLOCATE -LIBRARY ZZ -PATH NAME path-name
ALLOCATE -LIBRARY .Q -PATHNAME path-name
-- specify DEFAULT DOMAINS to be loaded
INCLUDE DOMAIN .MUTTR -LIBRARY AA
INCLUDE DOMAIN .MZZZZ -LIBRARY ZZ
END DEFAULTS
-- allocate CHANGE directive file
ALLOCATE -DIRECTIVES -PATHNAME change/path/name
-- directives read from "change/path/name"
START CHANGES
ALLOCATE -LIBRARY AA -PATH NAME test/lib/aa
EXCLUDE DOMAIN .MZZZZ -- don't load .MZZZZ
0123 PATCH 123412341234 patch loc 123
.MUTTR
ASSIGN SHARED NAME XYZ
ALLOCATE -BACKDOOR -PATH NAME test/backdoor/file
END CHANGES
(EOF on directive file)
(EOF on I*)
Figure 4-1.
Order Of SDLD Directives
4-51
DH18-03
Shared Domain Loader Configuration
The Shared Domain Loader (SDLD) configuration is controlled by the ALLOCATE
directive, which dynamically allocates the SDLD input and output files. The
dynamic allocation facility provides the ability to bypass the allocation of
files that cannot be allocated when the -OPTIONAL control argument is
specified. This allows non-fatal references to missing files (e.g., during
cold boot).
The dynamic feature also provides configuration of Integrated Software options
not ordered, without causing a fatal error during loading.
The ALLOCATE directive specifies the pathname which SDLD uses to attempt
dynamic allocation. Allocation errors are controlled by SDLD instead of GEIN
or PALe.
INPUT FILE ALLOCATION
Library Files
The SDLD Library files are searched to load specified domains using a library
code specifying unique files. The default value is ".Q".
Directive Files
SDLD input Directive files can be dynamically allocated to allow for bypassing
of CHANGE directive files during cold boot or any time a Directives file is
missing.
OUTPUT FILE ALLOCATION
Backdoor 'File
Backdoor file allocation is done dynamically to prevent fatal aborts if the
Backdoor file is unavailable; thus, preventing the listing of the Load Map via
the Backdoor facility. A Backdoor file is not all,oc'ated in the DEFAULT
directives, where, normally, no Backdoor Load Map is generated. The user may
allocate the Backdoor file as desired.
4-52
DH18-03
(
JCL REQUIREMENTS
SDLD is executed as a native mode batch process. The required virtual domains
are loaded with the SNUMB "SHARD" and started during System Startup ROLLCALL.
SDLD may be restarted with a set of JCL in a TSS JRN file or through the card
reader. JCL reqUirements to load Integrated Software are:
1
8
1
$
$
$
$
$
$
$
6
IDENT
USERID
RUN
RUFILE=SYSTEM,RUNAME=.VSDLD,OPTION=DUMP
RESOURC VSPACE=3800K
PRIVITY
DATA
r- SDLD Directives (see Figure 4-1)
ENDJOB
NOTES:
(1 )
(2)
I
1. The $ RUN JCL Statement invokes the SDLD loader from the
installed set of system run units taken from the seed workspace
image file.
2. The $ RESOURC JCL Statement has the virtual space limits for
Integrated Software loading.
/
LOADING REQUIREMENTS FOR INTEGRATED SOFTWARE DOMAINS
The SDLD directives are processed by SDLD from the I- file, normally, by using
the "$ DATA I-" JCL statement. The directives usually specify DEFAULT and,
optionally, CHANGE directives.
The best method of configuring SDLD into the system uses the "ALLOCATE
-DIRECTIVES" directive for DEFAULT and CHANGE file allocation. This method
provides dynamic allocation of the directives files and documents the files
used on the SDLD reports.
Example:
1
1
8
6
$
DATA
IALLOCATE -DIRECTIVES -PATHNAME UMC/DEFAULTS
ALLOCATE -DIRECTIVES -PATHNAME UMC/CHANGES
$
ENDJOB
4-53
DH18-03
The directives files may be allocated using GCOS allocation ' via a "$ SELECT"
JCL statement. The previous example can thus be restated as:
1
8
$
$
$
$
DATA
SELECT
SELECT
ENDJOB
1
6
I-
UMC/DEFAULTS
UMC/CHANGES
SDLD Standard DEFAULTS File
Notes 8-10 of "Loading Integrated Software for Execution" (earlier in this
section) illustrate a load of all available domains for standard DEFAULTS and
CHANGES directives using the SI4.2 virtual domain •
.The CHANGES directives file normally contains replacements or additions to the
DEFAULT directives to form a loader task block used for domain loading. The
CHANGES directives replace matching DEFAULTS directives or add the task block
entries when a match is not found.
The resulting task block directives are used in the domain load. An internal
line number is assigned to each CHANGE and DEFAULT directive. The Load Map
report displays the internal line number for each task block directive to
provide reference to the DEFAULTS or CHANGES line number.
OPNSUTIL/SHARD FILE REQUIREMENT FOR CONSOLE SPAWN OF "SHARD"
The OPNSUTIL/SHARD file needs the following JCL statement to support the "SPAWN
SHARD" console request:
1
8
$
6
SELECTD SYS_SOFTWARE/yyyy/JCL/SHARD.SPWN
where yyyy is the Software Release identifier, such as 3000.
SDLD Reports
SDLD output is Report Code 01 on the SYSOUT file and contains. four sections:
1. The directives
2. The virtual domain load-map
3. Buffer Pool directives
4. The loader summary
4-54
DH18-03
(
All sections have a page header line containing:
o The SNUMB assigned to the SDLD activity
o The date and time of the SDLD execution
o The report title - "INTEGRATED SOFTWARE DOMAIN LOADER"
o
The report type - Directives, Load Map, Summary,
o
SDLD version (8SI4.2) and the SDLD assembly date
o
Report/page number
or BPDirectives
DIRECTIVES LIST
The Directives list is divided into DEFAULT and CHANGE Sections, with the
directives listed in each block as assigned by their internal line number,
which is carried with the directive into the load task block. During the
domain load, each directive used is displayed in the Load Map and the
respective DEFAULT or CHANGE line number to ease cross-referencing to the input
directive.
The Directives list shows the exact content of each input line and the line
number assigned to that line. Syntax errors are shown as they occur.
\
)
LOAD MAP LIST
The Load Map list consists of a domain Load Map for each domain loaded.
domain Load Map block contains:
o
The domain subtitle line with the domain-id
o
The INCLUDE DOMAIN directive for the domain-id
o
The ALLOCATE -LIBRARY directive used to load the domain-id
o
The domain memory allocation values
Each
SEG address
ISR descriptor
Initializatton entry
Patch Table Space
STI offset
STI value
Software protection notice
4-55
DH18-03
o
Module Information
-
(
Module name
Module number
Load offset
Assembly date
Title date
Transmittal logs
o
Patch directives applied
o
Remarks directives with domain-id in columns 73-78.
o
Fatal or non-fatal error messages
LOAD MAP SUMMARY
The Load Map Summary Section is produced after the last domain has been loaded,
and contains the status for the following items:
o
Number of fatal errors
o
Number of non-fatal errors
o
Number of domains loaded
o
Number of pages required to load shared software
o
Number of buffer pool commands
o
Number of buffer pool command errors
o
Maximum wired pages allowed
o
Shared software or
o
ASSIGN SHARED NAME
BACKDOOR REPORTS
I
The "ALLOCATE -BACKDOOR" directive is required if the user wants a Backdoor
Load Map report. This report duplicates the SDLD report code 01 and is
released to SYSOUT at the end of the domain-load sequence. Report Code 01 is
not available until the SDLD activity is aborted.~, SDLD normally does not
terminate.
4-56
DH18-03
SDLD Error And Warning Messages
SDLD issues fatal and conditionally fatal (warning) error messages.
controlled as follows:
Errors are
o When possible, the loading procedure continues until all directives are
processed (the first fatal error does not stop the load process).
o At the end of directive processing, if any fatal errors were encountered,
processing terminates.
o The Load Map Summary displays the count of fatal and non-fatal errors
encountered.
FATAL ERRORS
MESSAGE:
*** FATAL ERROR *** SYNTAX ERROR
CAUSE:
Any directive syntax error is treated as fatal.
«reason» indicates where the error occurred.
MESSAGE:
•• * FATAL ERROR
CAUSE:
The START and END directives do not match.
The erroneous field
.** SYNTAX ERROR -- DEFAULT/CHANGE CONFLICT
The correct sequence is:
START DEFAULTS
END DEFAULTS
START CHANGES
END CHANGES
NOTE: The CHANGE block is optional.
The DEFAULT block is required.
MESSAGE:
*** FATAL ERROR ***
CAUSE:
Any PATCH statement error causes processing to abort; check all
fields for:
-
Invalid PATCH value
Long field
Non-octal characters (8 or 9)
PATCH location out of bounds
Invalid domain
Non-applied patches; i.e., the domain needing to be patched was
not loaded.
4-57
DH18-03
I
CORDITIONALLY FATAL ERRORS
The abort-control field determines if an error message is fatal or
non-fatal by the use of the -REQUIRED/-OPTIONAL conditions. The following
conditional errors are FATAL when issued in conjunction with a -REQUIRED option
and NON-FATAL when issued in conjunction with an -OPTIONAL option:
MESSAGE:
••• ERROR •••
CAUSE:
Allocate directive condition incorrect.
MESSAGE:
••• error ••• domain NOT FOUND IN LIBRARY
CAUSE:
INCLUDE DOMAIN directive contains incorrect value(s).
NOTE: All error messages contain the term "FATAL" to provide an easy
method to find loader errors using the TSS JOUT scan facility.
Example:
If the SDLD activity aborts, the scan output shows all errors and includes
them in the Summary Report, as follows:
JOUT SNUMB
SCAN 01 D Y
PS:/FATAL/j·
SDLD Abort Codes
The SDLD abort codes are documented in the GCOS 8
Abort Codes manual.
OSProgramme!_Mes~~ge~_~nd
MODIFYING INTEGRATED SOFTWARE ERROR MESSAGES
Integrated Software error messages that are issued to an Execution Report
reside within the .MUTOR domain. These messages can be modified to revise
message text and/or change the language in which message text is issued (e.g.,
from English to French).
Message modifications can be effected using the following procedure.
1. Review the existing messages. The following Time Sharing System command
can be executed to generate a listing of all messages.
JRN
SYS_SOFTWARE/yyyy/JCL/UTOR.CMPL
where yyyy
= Software
Release identifier, such as 3000.
2. Create a file on which installation-specific message modifications will
reside.
4-58
DH18-03
3. Prepare $ ALTER statements identifying all message modifications.
Incorporate these statements into the file created in step 2.
Note that the content of this alter file can be modified and applied to
the .MUTOR domain when subsequent system software releases are installed.
4. Incorporate a $$SELECT statement that identifies the pathname for the
alter file created in step 2 into the JCL residing on the file pointed to
by pathname,
SYS_SOFTWARE/yyyy/JCL/UTOR.CMPL
where yyyy
= Software
Release identifier, such as 3000.
Modify the $ IDENT statement to site specifications.
JCL file at a site-created pathname.
Store the resulting
5. Execute the following Time Sharing System command to rebuild the .MUTOR
domain.
JRN
fffff
where fffff is the pathname of the file created in the last step.
The next time GCOS 8 system software is booted with "RESTART NO",
installation-specific message modifications will be issued to Execution
Reports.
~
J
In conjunction with message modification, the following may prove beneficial:
o
Review the Load Map generated the next time Integrated Software (SNUMB of
SHARD) executes. Verify that the UTOR module shows the assembly date on
which the message modifications were bound in.
o
Retain the alter file prepared in steps 2 and 3 to use in rebuilding the
UTOR module when a subsequent GRR is restored.
4-59
DH18-03
c
'il\
i
I
SECTION 5
ST ARTUP JOB STREAM
The Startup job stream comprises six sections in the following fixed sequence:
$CONFIG
$INITIALIZE
$EDIT
$FILES
$PATCH
$LOAD
Each of the six sections serves a distinct purpose. For example, one section
defines the site's hardware configuration, while another section applies patch
corrections to GCOS programs. The purpose of each section and the control
statements required and permitted in each section are described below.
If a section is not in the proper position, the console message *EXPECT s ••• s
FIX TYPE GO, OR TYPE STOP is issued (where s ••• s = name of the section that is
out of sequence). The operator can enter BOOT via the system console to halt
the bootload, place the section in the proper position, and initiate a warm
boot.
Only two of the sections ($CONFIG and $FILES) are required to be processed.
For various reasons, processing of the other sections may be bypassed. For
example, processing of the $INITIALIZE and $EDIT sections can be bypassed if
the operator enters NO in response to the *INITIALIZE? and *EDIT? questions
when issued to the system console; the $PATCH section can be omitted if there
are no patches to apply via this section; and the $LOAD section is required
only to load qualifying modules into main memory.
Each section is delimited by a section identification statement and a ••• EOF
statement. The section identification statement specifies the section name,
which begins in column 1 (e.g., $CONFIG). Following the ***EOF statement
delimiting the last section in the Startup job stream, another •• *EOF statement
must be included to denote the end of the Startup job stream.
A section identification statement and •• *EOF statement are not required if a
section is not included in the Startup job stream.
Duplicate statements are invalid and can cause the Startup program to abort.
In other instances, the duplicate statements are ignored by Startup and
identified via a console message.
5-1
DH18-03
COMMENTS IN STARTUP JOB STREAM
Comments can be included on any statements, including section identification
statements, in the Startup job stream. Any comment included on a *.*EOF
statement is ignored. At least one blank space must separate a comment from
Startup data. Comments cannot be continued to another statement. A statement
with ** in character positions 1 and 2 contains nothing but a comment.
Comments are printed on a dump report when a dump is requested. In addition,
quotation marks (" ") cause the enclosed comment to be printed at the system
console. For example, the comment on each of the following statements is
printed at the console when the statement is processed:
1
8
1
$CONFIG
$
6
"DEFINING MS0450 SYSTEM "
INIT
ST1,DS1
"DESTROY PERM FILES?"
An exception to printing comments at the console is when the operator responds
NO to either the *INITIALIZE? or the *EDIT? question. If the operator responds
NO to .INITIALIZE?, only comments on the $INITIALIZE section identification
statement are printed. Comments on all other statements in the $INITIALIZE
section are ignored. If the operator responds NO to *EDIT?, only comments on
the $EDIT statement are printed. Comments on all other statements in the $EDIT
section are ignored.
RULES FOR NOTATION
The following rules apply to the notations used in the descriptions of the
Startup statements:
1. Parameters enclosed in brackets, [ ], are optional and may be included or
omitted, as required by the user. Optional fields can appear in any
sequence following the required fields unless a requirement for a
specific sequence is stated in the description of the statement.
2. When parameters are enclosed in braces, { }, one, and only one, of the
enclosed parameters must be chosen.
3. An ellipsis, ••• , indicates that the preceding parameter may be
repeated.
4. The vertical bar "In indicates that a choice among the parameters
separated by vertical bars must be made.
5. All text printed entirely in uppercase letters must be typed as is,
unless the portion of the general form containing it is itself optional.
6. Any spaces, semicolons, commas, dashes, parentheses, etc., shown in the
general form are required punctuation.
5-2
DH18-03
(
• ETC STATEMENT
r'
In most cases, data can be continued from a Startup statement onto a $ ETC
statement. (Those instances in which a $ ETC statement cannot be used are
identified in the descriptions of the statements, later in this section.) A
comma must terminate the statement preceding each $ ETC statement. The $ ETC
statement must reflect the format of the statement that it is continuing. For
example, a $ lOX statement might be continued as follows:
1
1
8
6
$
$
$
lOX
ETC
ETC
CH-14,MS0450,UNITS-2,
UNIT-1,MS1,
UNIT-2,MS2
NOTE: In this example, the use of "CH-14" to assign channel 14 is equivalent
to "PUB-14". Both are valid designations and are interchangeable.
$CONFIG SECTION
The $CONFIG section defines system software and system hardware parameters.
The $CONFIG section is one of two sections required in the Startup job stream
(the other is the $FILES section). Control statements in this section define
device connections, device characteristics, shared mass storage devices, and
the maximum hardware configuration. This section is preceded by MASK
statements and followed by the $INITIALIZE section in the Startup job stream.
Internal configuration and device control tables are derived from $CONFIG
section information. When a device rollcall is performed during the
initialization portion of the bootload, connections are verified and the status
of peripheral devices is determined. Inoperable devices at System Startup time
are released, but the entries remain within internal tables so that the devices
may be restored (i.e., assigned) to the system at a later time.
Startup also performs a survey of processors and initializes .CRCMC for each
processor during $CONFIG section processing. (Refer to "Processor Release And
Assignment At Startup" in Section 3 for additional information and to the
GCOS 8 OS System Tables manual for the .CRCMC format.)
5-3
DH18-03
Startup issues the following questions, described in Section 2 under nStartupOperator Interface n , to the system console during $CONFIG section processing:
o
o
o
o
o
o
o
o
o
o
*RETAIN CONFIGURATION?
*RESTART?
*SCF CONTINUATION?
*DATE?
*TIME?
*DATE mmddyy TIME hh.mmm
*CHANGE DATE?
*CHANGE TIME?
*ENTER TIME OR ENTER A CORRECTION FACTOR?
*CHANGE > 5 MIN. YES TO ACCEPT?
System configurations vary greatly depending upon the choice of configuration
options in the $CONFIG section. Peripheral device options permit the system to
be tailored to the needs of the site. For this reason, it is recommended that
preparing the $CONFIG section be closely coordinated, so that the configuration
described in the Startup job stream accurately reflects the physical
configuration of devices.
The following are requirements for the $CONFIG section control statement
sequence:
1. Several options on the $ INFO statement (e.g., MIXED, RLSDSK, RLSPNT) and
the $ BASE statement must precede the $ MCT and any input/output
controller (i.e., $ IOM/IOX/IOP/IMU/IMX) statements.
2. The $ MCT/$ CIU statement must precede all input/output controller
statements.
3. The input/output controller statements must precede $ XBAR statements,
which, in turn, must precede the $ MPC statement.
4. The $ IMAGE statement(s) must precede any $ TRAINS statement(s).
5. The $ GCOSFIL statement must follow the mass storage $ Iyy statement(s).
The following statement types, described later in this section, are accepted by
the $CONFIG'section of Startup for DPS 8, DPS 8000, DPS 88, and DPS go systems,
unless a system type (DPS xx) follows the statement type. In that case, the
statement is valid only in the system(s) indicated.
$
$
$
$
$
$
$
$
$
$
ANSWER
AUTOLD
BASE
CHAN
CIU (DPS 88, DPS 8000)
DECKFIL
DUP
FILCREA
GCOSFIL
GROUP
$ IMAGE
$ IMU (DPS
$ IMX (DPS
$ INFO
$ 10M (DPS
$ lOP (DPS
$ lOX (DPS
$ LOADFIL
$ MCT (DPS
5-4
$ MPC
8)
8000)
8)
90)
88)
8, DPS 90)
$
$
$
$
$
$
$
$
$
MPCFIG
SECURE
SHARED
SYID
TRACE
TRAINS
UNIT
URP
XBAR
DH18-03
(
$ ANSWER Statement
The $ ANSWER statement allows site personnel to provide answers, in the Startup
J..?b1str;am ,_,~s> .~ti.Qn~t1:u~~___2~!l~,r!!~,~"",,,e,,r.:~~.g.!.!:~,2~!J:.C?...!:~e syst eniconsOIe-- ....
dur ng ystem Startup or dump operations. Any System Start'Ui>''''or~''amrrp''Qile'itions
With answers aefinea"vI'a tUe $ ANSwER statement are not issued to the console.
Conversely, questions without predefined answers are issued to the console and
require operator response via a console entry.
The $ ANSWER statement normally is used to expedite warm and fast boots (i.e.,
to circumvent console questions requiring operator responses).
Answers to System Startup and dump questions are specified in the format
qqqqqqq/aaaaa (where qqqqqqq = parameter denoting a specific question, and
aaaaa = answer). The question parameters and related answers can be specified
in any sequence (e.g., the SSCLEAR parameter and answer can precede the RESTART
parameter and answer).
Answers to multiple questions can be defined on one $ ANSWER statement, using
the comma as a separator. If one statement does not accommodate all responses,
information can be continued onto additional $ ANSWER statements or onto $ ETC
statements. Some sites have found that one question parameter and its related
answer per $ ANSWER statement simplifies maintenance of the Startup job stream
when only one answer is to be changed or removed.
If at least one $ ANSWER statement is encountered, Startup issues the .CHANGE?
question to the console during the bootload sequence. If the operator responds
YES, the $ ANSWER statements are ignored for that bootload.
The format for the $ ANSWER statement is:
1
8
1
6
$
ANSWER
qqqqqqq/aaaaa, •••
Tables 5-1, 5-2, and 5-3 indicate which System Startup and dump questions can
be answered on the $ ANSWER statement, along with the format for the parameter
denoting the question and the format for the answer. (Refer to
"Startup-Operator Interface" in Section 2 for additional information on system
Startup questions.) Table 5-2 indicates additional Startup questions for which
answers can be defined; however, because these questions are issued only under
speCial Circumstances, $ ANSWER should not be used for these questions.
It is not possible to guarantee that a mass storage device will be fully
initialized when using $ ANSWER statements to answer Startup questions.
DH18-03
Table 5-1.
I
Frequently Used $ ANSWER Responses To Startup Questions
Startup Question
To Be Answered
$ ANSWER Parameter
(qqqqqqq/aaaaa)
*RETAINCONFIGURATION?
RETCONFIG/YES
RETCONFIG/NO
·RESTART?
RESTART/YES
RESTART/NO
.SCF CONTINUATION?
SCF/YES
SCF/NO
·TIME?
TIME/NO
·INITIALIZE?
INITIALIZE/YES
INITIALIZE/TOTAL
INITIALIZE/PARTIAL
INITIALIZE/NO
·EDIT?
EDIT/YES
EDIT/PARTIAL
EDIT/NO
.SYSTEM SCHEDULER CLEAR?
SSCLEAR/YES
SSCLEAR/NO
.PROCESSOR ON PORT p
DOESN'T ANSWER CONNECT
PROCERROR/YES
(See note 3.)
.SYSOUT RECOVERY?
SYSOTRCVY/YES
SYSOT RCVY/NO
(See note 4.)
, (See note 1.)
(See note 2.)
(See note 1.)
NOTES: 1. If the .RESTART? question is answered RESTART/YES on the $ ANSWER
statement, Startup automatically answers the .SYSTEM SCHEDULER
CLEAR? question NO.
·2. Once the time has been established via an operator entry, Startup
continually updates the time. Use of this option ensures that the
most recent time saved by Startup is used to answer the -TIME?
question.
3. A PROCERROR/YES response indicates that a warm or fast boot is
desired following release of the slave processor. A PROCERROR/NO
response aborts the Startup program and is invalid on the $ ANSWER
statement. (Refer to "Processor Release And Assignment At
Startup", in Section 3 tor additional information.)
4. A SYSOTRCVY/YES answer allows for recovery of system output
regardless of answers to RESTART questions.
5-6
DH18-03
Table 5-2.
Speeial $ ANSWER Responses To Startup Questions
$ ANSWER Parameter
(qqqqqqq/aaaaa)
Startup Question To Be Answered
-FORMAT/LABEL QUESTIONS?
LABEL/YES
LABEL/NO
-FORMAT/LABEL QUESTIONS?
FORMAT/YES
FORMAT/NO
-INIT DEVICE ddd?
INIT/YES
INIT/SECONDARY
INIT/NO
-INIT SHARED DEVICE ddd?
SINIT/YES
SINIT/SECONDARY
SINIT/NO
-INIT RMVBL DEVICE ddd?
RINIT/YES
RI NIT / SECONDARY
RINIT/NO
MPC ON iee PRE-INITIALIZE?
INITDAU/YES
INITDAU/NO
SHARED MPC ON ice PRE-INITIALIZE?
INITSHRDAU/YES
INITSHRDAU/NO
PROCESS DIRECTORY CARD FOR DEVICE ddd?
DIRECT/YES
DIRECT/NO
PROCESS DIRECTORY CARD FOR SHARED DEVICE ddd?
SDIRECT/YES
SDIRECT/NO
-SHARED MPC on ieee APPEARS OK, BOOTLOAD?
SBOOTLOAD/YES
SBOOTLOAD/NO
*xxxMPC ON ieee BOOTLOAD SYS ID NAME "y ••• y"
REV.zz?
BOOTLOAD/YES
BOOTLOAD/NO
-xxxMPC ON ieee APPEARS OK, BOOTLOAD?
BOOTLOAD/YES
BOOT LOAD/NO
-CLEAR AND OVERWRITE EXISTING
~CKFILE?
oc)
LFt('j'JW/iN::
-Iyy-n NOT RESPONDING - YES TO CONTINUE OR
R TO RETRY
DECKCLEAR/YES
DECK CLEAR/NO
IOMERROR/YES
IOMERROR/NO
NOTE: The SYSTEMMAP/NO response inhibits printing of a system map and a file
map. There is no eonsole message offering this option.
5-7
DH18-03
Table 5-3.
$ ANSWER Responses To Dump Questions
Dump Question To Be Answered
$ ANSWER Parameter
(qqqqqqq/aaaaa)
SELECT DEVICE: (PRINT), (DISK),
PRINTER NAME (PR1), (DDD/TAPEI,DENSITY),
(NONE)
DUMPON/PRINT
DUMPON/(ttt/rrrr,dddd)
DUMPON/DISK
DUMPON/NONE
ADDITIONAL OPTIONS: ALL, HCM , SOFT ,SLV,W/XX ,
P/XX,REAL,NPURE,NONE,DEVICE,DUMPO,(-)SD.XXX,
.MXXXX,PH.XXX,PSH,SSF,HIS,TRC,COM,PTW,ONLY,
EXEC ,FLTKPX,CACHE,SDC ,AUTO,PAED,RES,END
DUMP/ALL
DUMP/HCM.
DUMP/SOFT
DUMP/SLV
DUMP/Wxxx-yyy (W/xxx-yyy)
DUMP/ppp (P/ppp)
DUMP/REAL
DUMP/NPURE
DUMP/NON
DUMP/OPTS
DUMP/SD.sss
DUMP / •Mmmmm
DUMP/PH.sss
DUMP/PSH
DUMP/SSF
DUMP/HIS
DUMP/TRC
DUMP/COM
DUMP/PTW
DUMP/ONLY
DUMP/SDC
DUMP/EXEC
DUMP/FLTKPX
DUMP/AUTO
DUMP/PAED
DUMP/RES
DUMP/CACHE
.BOOT SOURCE: AUTO OR REPL?
BOOT/AUTO
BOOT/REPL
*
where:
ttt
rrrr
dddd
xxx-yyy
ppp
sss
mmmm
-
Logical device name of the magnetic tape handler
Tape reel number
Tape density
Dump working spaces
Dump known process index
Segment ,identification
Module identifier
5-8
,
DH18-03
~
1/)'
The following example specifies that job restart (RESTART/YES) is desired, that
system restart is to occur from the Startup job stream residing on the AUTOLOAD
file (BOOT/AUTO), that statistical collection is to resume at the point of
interruption (SCF/YES), that neither the initialization nor the edit function
is desired (INITIALIZE/NO and EDIT/NO), that the SSFILE is not to be cleared
(SSCLEAR/NO), that a warm or fast boot is desired following release of the
slave processor (PROCERROR/YES), and to use the most recent time saved by
Startup to answer the -TIME? question (TIME/NO).
1
1
8
6
$
$
ANSWER
ANSWER
RESTART/YES,BOOT/AUTO,SCF/YES
INITIALIZE/NO,EDIT/NO,SSCLEAR/NO,PROCERROR/YES,TIME/NO
$ AUTOLD Statement
The $ AUT OLD statement ~i\,gYstems used by
Network Processors for CXI mode). The value y can
should be equal to n in the FNP/n parameter of the
There is no default value.
mode plus any
the site (exclude
range from 0-16 and
$ INFO statement.
The following example specifies that memory is to be allocated in
memory-resident tables for four IOMs and four network processors. Note that
the same type of statement can be used in a DPS 88 environment by specifying
IOX-2 (maximum of 2 IOXs) instead of IOM-4, and in a DPS 90 environment by
specifying IOP-4 instead of IOM-4.
1
1
8
6
$
BASE
IOM-4,DN-4
5-10
DH18-03
$ CHAN Statement
The format for the $ CHAN statement is:
1
1
8
6
$
CHAN
Iyy-a, {PUB-b},Iyy-c, {PUB-d},message
{CH-b }
{CH-d }
where:
Iyy-a,{PUB-b} - A channel previously configured on a $ lyy or $ XBAR
{CH-b}
statement (Iyy = lHU, IMX, lOM, lOP, or lOX).
Iyy-c,{PUB-d} - A channel not previously configured.
{CH-d }
If Iyy-a has been released by Startup, all references to Iyy-a,PUB/CH-b are
changed to reference Iyy-c,PUB/CH-d (assuming they have not been released).
The system operates as though the devices configured on Iyy-a,PUB/CH-b have
been configured on Iyy-c,PUB/CH-d.
The user specified nmessage n in the control statement is issued to the system
console if Iyy-a has been released and Iyy-c has not been released. If lyy-a
has not been released or if both Iyys have been released, the control statement
is ignored.
The example below indicates that PUB-20 on IOM-2 has been previously conCigured
and that PUB-16 on IOM-3 has not been previously configured.
1
1
8
6
$
CHAN
IOM-2,PUB-20,IOM-3,PUB-16,NOTIFY SITE OPS
If IOM-2 is released during Startup, the following message is displayed on
the system console:
NOTIFY SITE OPS
5-11
DH18-03
$ CIU Statement
For the DPS 88 the $ CIU statement defines the memory size, number of
processors, and 10Xs connected totheCIU. For the DPS 8000 the $ CIU
statement defines the memory size, number of processors, and IMXs connected to
the SCU. The $ CIU statement must precede all $ lOX or $ IMX statements. Only
one $ CIU statement may be specified. For DPS 8 and DPS 90, see "$ MeT
Statement", later in this section. The $ MCT statement cannot be used for
DPS 88 and DPS 8000.
The fields of the $ CIU statement can be arranged in any order; however, CPUs
and IOXs or IMXs must be configured contiguously, beginning with O.
1
1
8
6
$
CIU
[MEM/sss,]PRO-n,{IMX-mIIOX-m}
where:
MEM/sss - The number of blocks of lK words of memory configured into the
system. The maximum value is the total available memory size;
however, it need not be set to that value.
If this field is omitted, the available memory is determined via a
survey of reserved memory by the SSF or service processor.
PRO-n
- Required for every CPU configured into the system (maximum = 4).
CPUs must be configured contiguously, beginning with O.
IMX-m
IOX-m
- Required for every 1M! or lOX configured into the system.
IOXs must be configured contiguously, beginning with O.
IMXs or
The following example defines a system with 2048 lK blocks of memory, two CPUs,
and two IOXs:
1
1
8
6
$
CIU
PRO-O,PRO-1,IOX-0,IOX-l,MEM/2048
The minimum memory size required to support GeOS 8 is 4MB. If less than this
is specified, Startup will issue the following error message and abort:
GCOS-8 REQUIRES AT LEAST 1024K OF MEMORY
$ DECKFIL Statement
The $ DECKFIL statem.ent specit~tl§ tll~,,,ame gt, the file to ¥h~ca th~ I:iPf~
Bootload (MPCB) .and firmware data decks are. wri1;1iGg. ; The file also contains
t'fle11PcC''seariCnlng~'\>rolf'~I"
$"CUNF!Cf"sectroo·a:nd"""·'$E'jjiT section files, Starfiip""ci'tie'cks only devices identified
on the $ GCOSFIL statement(s).
The format for the $ GCOSFIL statement follows.
1
6
1
8
$
GCOSFIL ddd[,ddd] •••
where:
ddd
- Logical device name.
A maximum of 63 devices can be identified.
The following example indicates that system files are permitted on devices DP3,
DP4, DP5, and DP6. Other devices in the configuration (e.g., DP2, DP7, and
DP8) are reserved for other uses. For example, one device may be reserved for
recovery purposes, another may be defined as removable (RMVBL) - system files
cannot reside on removable devices - and another may be reserved for user data
base purposes.
1
)
6
1
8
$
GCOSFIL ST1,DP3,DP4,DP5,DP6
$ GROUP Statement
The $ GROUP statement identifies the physical channels of the IMU/IMX/IOP/IOX
to wh~ch_ ~~ .MSU31.~jt1-J:l~1!3l[r;:~:lIm,[~V~,:::,~~r .;~~'~~~:::~~~~;s'~em,c'~"i~"",ph:ye'teac£,j:y."-~'''''''''''Y;:'.~
eenrret!tea. ~'-$-GROUP statement also identif~es tHe !<5g:1'Ca'i""''*eharm'ri'''S'Ml(~\!i!>~
'~soVCiSted with those physical channels. The $ GROUP statement is required for
MSU3380, MSU3381, MSS8080, and MTS8200 subsystems and is optional for other
devices. A separate $ GROUP statement is required for each subsystem. The
$ GROUP statement has the following format:
<
1
186
$
GROUP
Iyy-m,{PUB-p-q}[,{PUB-p-q}] ••• [,
{CH-p-q }[ {CH-p-q}]
[
$
ETC
Iyy-n,{PUB-r-s}[,{PUB-r-s}] ••• ] •••
{CH-r-s }[ {CH-r-s}]
]
5-15
DH18-03
where:
(
Iyy
- IMU, IMX, lOP, or lOX.
m,n
- Number (0-3) of the Iyy to which the MSU3380, MSU3381, MSS8080, or
MTS8200 subsystem is connected.
.
p,q,r,s - Iyy channel (CH/PUB) number.
IMU
IMX
lOP
lOX
Permissible values are:
8-63
0-127
8-63
0-127
Channel number p (and r) must be the primary channel. Channel
number q (and s) must be the last logical channel number in the
group to which the subsystem is connected. Logical channels for
the same physical channel are specified using the hyphen (-) as a
separator indicating consecutive channels. Channels on a
different subsystem are specified using another $ GROUP statement.
Physical channels to a subsystem are specified using a comma as a
separator on the $ GROUP statement. Each physical channel number
on $ Iyy and $XBAR statements for MSU3380, MSU3381, MSS8080, and
MTS8200 must be specified on a $ GROUP statement.
Example:
(
1
1
8
6
$
GROUP
IMU-1,CH-40-43,CH-50-53
Channels 40 and 50 are physical channels; channels 41, 42, 43, 51, 52, and 53
are logical channels.
$ IMAGE Statement
The $ I~~GE statements provide a logical representation of the characters on a
physical belt. Each position in the image corresponds to the graphic character
on the belt at that position. Placement of a particular internal code in that
position on the image causes that internal code to print as the graphic
character at that position on the belt. The image defined on $ IMAGE
statements replaces the standard ASCII or BCD image. The $ IMAGE statement
defines the image of a printer belt to replace the default image associated
with a specific printer type. The default images are defined in an internal
buffer of the Startup program.
In addition, the first six 64-word sectors of the PRINTIMAGE file, containing
the print train catalog and the VFC catalog, are overwritten with information
from the $ IMAGE statement. Overwriting of the catalogs on the PRINTIMAGE file
destroys existing file content.
c
5-16
DH18-03
If Startup detects a difference in the content of the PRINTIMAGE file and the
$ IMAGE statements, the following error message will result:
.CHECKSUM ERROR, FILE PRINTIMAGE
• ANSWER YES TO IGNORE ERROR AND CONTINUE
* ANSWER NO TO ABORT, & THEN EDIT PRINTIMAGE.
If the file contained any images other than standard printer belt and vertical
format control (VFC) images, the TVIM program must be used to rebuild the
images on the file. (Refer to "Printer Belt Characters/Codes" in the GCOS 8 OS
System Operating Techniques manual for PRINTIMAGE file information and for
procedures to use the TVIM program.)
Default printer belt images can be restored to both the internal Startup buffer
and the PRINrIMAGE file during a bootload from punched cards or magnetic tape.
Re-edit the PRINTIMAGE file by defining the file on a $ FILDEF statement in the
$EDIT section of the startup job stream and responding YES to the ·EDIT?
question during the bootload procedure.
All $ IMAGE statements must precede the $ TRAINS statement (or its related
$ ETC statement) in the Startup job stream. If the $ IMAGE statements follow
the $ TRAINS statement, Startup aborts. (Refer to the $ TRAINS, $ Iyy, and
$ FILDEF statements in this section for additional printer-related
information.)
,
\
)
Each printer belt has 240 character positions to be defined. Multiple $ IMAGE
statements are used (15 for ASCII belts, 5 for BCD belts) for this purpose.
Continue the printer belt definition from one $ IMAGE statement to another. Do
not use a $ ETC statement to continue the definition. Startup aborts if a
$ ETC statement is used for this purpose.
Startup also aborts if information in the printer belt identification number
(nnnn) or $ IMAGE statement sequence number (s) field is incorrect.
The format for the $ IMAGE statement is:
1
186
$
IMAGE
ppp,ccc,nnnn,s,x ••• x
where:
ppp
- Printer type number:
4nn
where nn
ccc
= any
numerical value
- Printer belt being replaced:
BCD - Replacing standard BCD printer belt
ASC - Replacing standard ASCII printer belt
5-17
DH18-03
I
nnnn
- Printer belt identification number (octal) of the standard belt
being replaced. The software identification of any belt is obtained
by converting the belt number (given in decimal) into its octal
equivalent (e.g., for the PRB0500 belt, 0500 (decimal) = 764
(octal), so the software identification is 764). For PR54 printer
belts the first digit (3) should be dropped before conversion (e.g.,
PRB3600 is converted by dropping the 3, and then converting 600
(decimal) to 1130 (octal».
PRB Number
(decimal)
0500 or 3500
0600 or 3600
s
(
(octal)
-----764
1130
- $ IMAGE statement sequence number, one or two digits, starting with
1 (or 01) and incrementing by 1, up to 15 for ASCII belts or 5 for
BCD belts. Within a range of sequence numbers (1-15 or 1-5),
Startup will abort if the ppp, ccc, and nnnn fields do not remain
constant.
x ••. x - When ccc = ASC this field defines a sequence of 16 of the 240
character positions of the printer belt replacing the standard
printer belt for this device. Each position is specified by three
octal digits.
When ccc = BCD this field defines a sequence of 48 of the 240
character positions of the printer belt replacing the standard
printer belt for this device. Each position is specified by one BCD
character.
(
The following example shows the fifteen statements required to define a
nonstandard ASCII printer belt for PRU1200/1600 printers:
1
2
1
8
6
9
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
IMAGE
IMAGE
IMAGE
IMAGE
IMAGE
IMAGE
IMAGE
IMAGE
IMAGE
400,ASC,1130,01,102104106107110112147123060101103105111116117122
400,ASC,1130,02,114124141142143144145146113150151152153154155115
400,ASC,1130,03,060120121125126127130131132072073077041045067170
400,ASC,1130,04,171156157160162163164167060172061062063064065066
400,ASC,1130,05,043070071056054050051100044075046057047134136137
400,ASC,1130,06,060042074076133135147123176101103105111116117122
400,ASC,1130,07,173124141142143144145146060150151152153154155175
400,ASC,1130,08,174140055052053161165166102104106107110112067170
400,ASC,1130,09,060156157160162163164167114172061062063064065066
400,ASC,1130,10,113070071056054050051115060120121125126127130131
400,ASC,1130,11,132072073077041045147123171101103105111116117122
400,ASC,1130,12,060124141142143144145146043150151152153154155100
400,ASC, 1130,13, 04407504605704713413613706004207407613 3135067170
400,ASC,1130,14,176156157160162163164167173172061062063064065066
400,ASC, 1130, 15,06007007105605405005117517414005505205 3161165166
I~AGE
IMAGE
IMAGE
IMAGE
IMAGE
IMAGE
7
9
c
5-18
DH18-03
~
~
The following example shows the five statements necessary to define the
nonstandard BCD print belt, PRB 3513/0513. (Refer to the GCOS 8 OS System
Operating Techniques manual).
1
2
1
8
6
9
$
IMAGE
IMAGE
IMAGE
IMAGE
IMAGE
400,BCD,0764,01,=5678GHIJKL\0.-*/MNOPQR:&(9),STUVWX[01234YZ$@I+!
400,BCD,0764,02,?5678ABCDEF O.-+/GHIJKL<>(9),MNOPQR[01234STUVWX;
400,BCD,0764,03,'5678YZ$@I% 0.-*/ABCDEF"=(9),GHIJKL\01234MNOPQR:
400,BCD,0764,04,&5678STUVWxTo.-*/YZ$@I+I?(9),ABCDEF 01234GHIJKL<
400,BCD,0764,05,>5678MNOPQR[O.-*/STUVWX;'(9),YZ$@#%_01234ABCDEF"
$
$
$
$
7
9
A
A
$ INFO Statement
The $ INFO statement defines a variety of operating system parameters.
Multiple parameters can be included on one $ INFO statement, or they can be
continued onto as many $ INFO or $ ETC statements as required.
The format for the $ INFO statement is:
1
1
/
8
6
INFO
parameter[,parameter] •••
The following parameters can be included on the $ INFO statement(s):
$ INFO Parameter
inn }
ACALL/
{TSS}
{TPE}
{TSx}
Description
Automatically execute an ACALL instruction following a
restart via fast boot. -- Thea:ssoc1:a'tecf" parameters
'
InOlca-£e-thai the' specified network processor is to be
reconnected (where nn = processor number 0-16) and/or the
Time Sharing System (TSS parameter) or the Transaction
Processing System Executive (TPE parameter) is to be
restarted (if either was executing at the time the system
malfunctioned) upon system restart.
The TSx parameter (where x = 1-4) identifies the copy of
Time Sharing that is to be restarted in a multicopy
configuration. For example, TS2 indicates that only the
second copy of Time Sharing is to be restarted if a
system failure occurs. More than one TSx parameter can
be specified; each must be preceded by ACALL/ (e.g.,
ACALL/TS1, ACALL/TS2).
If more than one parameter is specified, ACALL must be
included for each (e.g., $ INFO ACALL/2,ACALL/TSS).
5-19
DH18-03
$ INFO Parameter
Description
ASCII
A printer with ASCII capabilities (i.e., with an ASCII
printer belt) is configured and can be allocated to print
ASCII output.
NOTE: This is not a SYSOUT parameter. If online ASCII
printer output is collected by SYSOUT, periodic
attempts are made to allocate an ASCII printer
(MGEOT INFO (025) -- ASCII PRINTER NEEDED) •. This
continues until an ASCII printer becomes available,
or until the output is disposed of via REDRC (REDRe
APRONL BPRONL), NOPRO or other SYSOUT console verb.
CATDUP
Duplicate all File Mana ement Su ervisor (FMS) oa a
s
File con en ~s no duplicated. This parameter ensures
file availability in the event of a hardware failure on
the device containing the original catalog structure.
The following conditions apply to this parameter:
1. Original and duplicate catalogs are written to mass
storage devices for which the CAT parameter is
specified on the $ INIT statement. If the CAT
parameter is not specified, Startup assigns the
original and duplicate FMS catalogs to the same
devices on which the original and duplicate System
Master Catalogs (SMCs) reside. Startup ensures that
the original and duplicate catalogs are not on the
same device.
2. The CATDUP parameter is not activated unless the
SMCDUP parameter also is specified on the $ INFO
statement. If the CATDUP parameter is specified and
the SMCDUP parameter is not, Startup aborts.
CATFNC/n
Startup defined files will be allocated at or above llink
number "n"(decimal) on devices containing FILSYS
catalogs. The purpose is to preserve the lower address
range for FILSYS catalog growth. The minimum value of n
= 0; the maximum value of n = 51200 (decimal); the
default value of n = 30000. A message:
.UPPER LIMIT FOR CATALOG FENCE IS 51200
is issued indicating that the value for n entered
exceeded the allowable maximum for the $ INFO CATFNC/n
statement.
5-20
DH18-03
(
$ INFO Parameter
Description
CCACHE/nnn
Main memory buffers are reserved in support of the FMS
catalog cache feature. The value nnn can range from
0-400 (0 is equivalent to not specifying the parameter).
Each buffer is 320 words.
NOTE: This is a Priced Software Product that requires
KEY3 to be loaded.
CHKSUM
Checksum all modules during the module-load process.
not specified, modules are not checksummed.
CLENPT
Enable the cleanpoint function for system restart. The
cl~angoint facility a~.t~Ets ~~~d-~~ which were
i ..n •proce.s~,",,!:t _tff~-I!m~~~.§1~".J:ilj...l!lr~~_j!,tw~~ned
po~nt (i.e., at a cleanpo~nt).
If cleanpo~nt recovery-!s
~essful, restart is from the beginning of each job
that was in process.
If
Recovery/restart is vitally important to system output.
For this reason, and to increase reliability, the
segments shown in the following list are cleanpointed if
the $ INFO CLENPT statement is included in the $CONFIG
section. The segments are:
DP.JOT
DP.JOS
DP.SBT
DP.BDI
)
-
Job Output Table
Job Output Specials
SYSOUT Blink Table
Backdoor Information
DP.JOT and DP.SBT cleanpoints are taken after a new job,
which has completed queue entry, is processed and when
blinks and jobs are released. DP.JOT and DP.BDI
cleanpoints are taken when a backdoor job queue entry is
processed and when backdoor files and jobs are released.
DP.JOS cleanpoints are taken each time a special is added
to or removed from the current segment. Also, DP.SBT is
cleanpointed in BRT6 upon activity termination if the job
modified that segment.
NOTES: Cleanpoint cannot be used on a single pack system.
If a $ INFO SMCDUP is also specified, the
cleanpoint control file is also duplicated on
another device to be used in the event the primary
control file on STl is destroyed.
CNTDCW
This parameter causes the number of words transferred by
an activity when doing disk 1/0 to be counted and
collected with other accounting information. Enabling of
this option may adversely affect I/O overhead
constraints.
5-21
DH18-03
I
$ INFO Parameter
Description
DENxx/DENyy
The default high and low densities for the site's
MPC-driveri""magnet{c tape BuE'syst'em "are '''spe'C1ried -by the
values xx and yy, respectively. If the option is not
specified, default high and low densities for NRZI
devices are 800 bpi and 556 bpi, respectively. Note that
if a tape density is not specified on the $ ACCOUNT or
$ FILDEF statements, the default high density of 800 bpi
is used.
(
8
The following density specifications are valid:
DEN2
DEN5
DEN8
DEN16
DEN62
-
200 bpi
556 bpi
800 bpi
1600 bpi
6250 bpi
If PE (1600 bpi) and GCR (6250 bpi) subsystems/devices
are configured, a $ INFO statement must be included in
the Startup job stream to activate the default-density
feature. Both parts of the option contain the same
numeric identifier in these cases (e.g., DEN16/DEN16 for
PE devices).
If default densities are not specified and if no other
subsystem/device is configured with the standard
(800/556) default density capabilities, Startup aborts.
The console message NO HANDLERS CAPABLE OF DEFAULT
HIGH/LOW DENSITY is issued.
DPSE
This parameter must be present if a DPS 8/50 or 8/70
processor is configured. It allows the operator to
dynamically assign (i.e., place online) the processor, if
it is currently offline, via the ASGNP console entry.
ENCRYP
Activate password encryption so that
S~~~~~
~~.re~:ili:::mm::dlr~:C!ji~i!!!~~TM~~nd"-~!5~~,,~e
~gQded. This secur1ty feature pro~ec~s aga~
unauthorized examination and disclosure of passwords.
Immediately before the first installation of password
encryption, the site must run the encryption utility
program ENCRYP. (Refer to GCOS 8 OS System Operating
Techniques manual.) As soon as password encryption has
been installed for the first time, the MDDMAS file
created by the ENCRYP utility must be entered into the
system via a $ FILSYS activity.
Once the ENCRYP option has been activated, the $ INFO
ENCRYP statement must be included in the $CONFIG section
for all subsequent Startups.
5-22
DH18-03
(
$ INFO Parameter
Description
EXTTDS/xxx,yyy
Thi
r defines the amount of memory available to
~£e~a:s:~~
is i ye~i~~~~~v;ai'~eI~i!ff~1~~~~~~he
_'Ol. .,__II<="....~~''''~~,:..ki),.'M,.''''\;;;r"U\~~treit_
p
number of auxiliary instruction segments assigned to TDS
and the value yyy specifies the maximum number of pages
assigned. The maximum limit on xxx is 61. There is no
maximum limit on, yyy. There is no default for xxx. The
default for yyy is 64.
EXTT sst xxx t yyy [ , zz z ]
T~!.~w'",P,~~~Pl~~.~!:,,,.,~~.t!!l~!,,,<~~,,,q~~iJJll.Q,ijQ.,t,,",,J~(~,,m~~,~H'Y;';T-!!,~,!.!,~21~.",~.?
the Time Sh~£1.ng~·st;-. The value xxx specifies the
number of auxiliary instruction segments assigned to Time
Sharing and the value yyy specifies the maximum number of
pages assigned. The maximum limit on xxx is 61 (61 is
the maximum capacity of a page table). There is no
maximum limit on yyy. There is no default for xxx. The
default for yyy is 64. (The value zzz is a literal
assigned to the value of the work space.) THIS IS A
REQUIRED STATEMENT -- SYSTEM WILL ABORT IF THE $ INFO
EXTTSS STATEMENT IS NOT INCLUDED AND TIME SHARING IS
CONFIGURED ON THE SYSTEM.
pNe.;;,'.~\,.,..'W', ~1M.'"'·Jl'lIlIM~_~Y"'1... ,:n~ _"OIt'l;'·;riI....
,JI..
FASTBT
Enable the fast boot function for automatic system
restart.:., Th{s'parameter'1s-equ1varentto'th'eF~"'BT ON
console entry. If the FASTBT option is specified,
rollcall messages are suppressed. However, operator
interface messages are suppressed during the Startup
question-and-answer sequence only if $ ANSWER statements
are present in the Startup job stream.
FMSCT/n
The value n specifies the maximum percentage (%) of the
FMS catalog area of a CAT DISK device that may be used
for file content in FMS file create and restore. The
value of n may range from 0 to 100. The default value is
100.
FMSDT/n
The value n specifies a descriptor threshold (maximum
number of space descriptors) for a selected disk device
in FMS file create and restore. When the threshold is
exceeded, a different device is selected. The value of n
may range from 0 to 127. A value of 0 indicates an
unlimited number of descriptors. The default value is 8.
FMSST/n
The value n specifies a space threshold (% of size of the
selected device) for file content in FMS file create and
restore. When the threshold is exceeded a different
device is selected. The value of n may range from 1 to
100. The default value is 50.
5-23
DH18-03
*
I
$ INFO Parameter
Description
FMSTAT
Accumulate statistics for File Management Supervisor
(FMS) program functions (e.g., the number of times a
function is used, the number of I/O operations for a
function, and the average amount of time required to
perform a function).
FNP/n
The value n identifies the number of network processors
for DNET/ROUT mode (exclude network processors for eXI
mode and include any configured On Line Page Processing
Systems) configured on an input/output controller. The
$ INFO ••• FNP/n statement directs Startup to establish the
Network Processor mailbox descriptor and is required if
any Network Processors for DNET/ROUT mode and/or On Line
Page Processing Systems are configured. This statement
must precede the $ MeT or $CIU statement. The value n
can range from 0-16 and should be equal to y in the DN-y
parameter of the $ BASE statement. There is no default
value.
GENSYS
Generalized Tape Management System (GTMS). The system is
to execute with tape management enabled. Module .MKEY7
(SPS element), and the files 'GSYSDATABASE' and 'GSYSAJ'
must be edited onto the system. If this parameter is not
specified, GTMS cannot be invoked, even with the presence
of the .MKEY7 module. This parameter sets bit 30 in
.CROPT and may be referenced by the symbol .FGSYS.
GEOTRC[/n]
Enable GEOT trace for more thorough SYSOUT delivery
trouble analysis. The optional octal mask, which limits
enabling to selected traces, is normally omitted unless
requested by a Honeywell Bull CSD Representative.
HEX/
The HEX/ON option results in acceptance of MME GMODES
requests for setting HEX floating point mode. This
option is valid only if all online processors have
hexadecimal capability. The console message HEX mDE
ENABLED is issued if Startup encounters a $ INFO ••• HEX/ON
statement and determines that all online processors have
hexadecimal capability.
{ON}
{OFF}
(
(
The console message:
.NO HEX CAPABILITY ON CPU-n HEX OPTION DISABLED
is issued if a $ HEX/ON statement is included in the
Startup job stream, but processor n is incapable of
running in HEX mode. As a result, the HEX option is
disabled while Startup continues processing.
The HEX/OFF option results in denial of MME GMODES
requests to enter HEX mode. HEX/OFF is the default.
5-24
DH18-03
(
$ INFO Parameter
Description
INTERRUPT/xxx
This parameter selects the interrupt processing type for
multiprocessor systems.
xxx - ALL allows all processors.to receive interrupts
- ONE selects the control processor to receive
interrupts (default for DPS 8 and DPS 88)
For DPS 90 systems this parameter is not valid, and ONE
is used. For DPS 8000 systems this parameter is not
valid, and ALL is used. If this parameter is present on
a DPS 90 or a DPS 8000 system, an error message is given
and Startup attempts to process the remainder of the
$CONFIG section, after which Startup aborts.
Native mode memory management parameters KLFTH, KLMIW, KMMWP, KLMWS, KLWPR, and
KLWSW can be varied to obtain better performance for different situations.
However, the system is effectively self-adjusting for a variation of load.
Except for very extreme cases, optimal performance will be obtained without
varying these parameters, because the adjustment mechanisms are sufficient to
cope with considerable load variations. Refer to the GCOS 8 OS System
Operating Techniques manual for more information.
KLFTH/n
This native mode memory management parameter designates
the number of pages for the system free-chain low
threshold. The value n is placed in the upper half of
.KLFTH. The default value is 18.
KLMIW/ssss
This native mode memory management parameter designates
minimum window time for a shared workspace in
16-microsecond units. The value ssss is placed in
.KLMIW. The default value is 1875.
KLMWP/ssss
This native mode memory management parameter designates
maximum window time for a process workspace in
16-microsecond units. The value ssss is placed in
.KLMWP. The default value is 625000.
KLMWS/ssss
This native mode memory management parameter designates
maximum window time for a shared workspace in
16-microsecond units. The value ssss is placed in
.KLMWS. The default value is 2097152.
KLWPR/xxxx
This native mode memory management parameter designates
the initial number of missing page faults which will
constitute a window for a process workspace and can be
considered as the "Page Fault Window Delimiter". The
value xxxx will be placed in the upper half of .KLWPR.
The default value is 35.
5-25
DH18-03
$ INFO Parameter
Description
KLWSW/xxxx
This native mode memory management parameter designates
the initial number of missing page faults which will
constitute a window for a shared workspace and can be
considered as the "Page Fault Window Delimiter". The
value xxxx will be placed in the upper half of .KLWSW.
The default value is 35.
LIMITS
When a program exceeds its SYSOUT record or processor
time limit, rather than aborting, the operator is asked:
-----------------------------
(
Slsssss aa SYSOUT LINES EXHAUSTED CONTINUE OR ABORT CIA?
or
Slsssss aa RUN TIME EXHAUSTED CONTINUE OR ABORT CIA?
where:
sssss - Snumb.
aa
- Activity number.
When the ~p.~!:a.~?,~resE,.9.!l.~,e iii~. ,"g~1h~~ . . J9b Ja~, granted
i~~ditional lin~s9fSYSOUT, or another ~ minutes
or ··pf'l56essOrt1iife;$and'''~omrnues-prOCe;s1nEt~
nen .~ne'''''o'perafOr'''''re8~ponse is A, the job is aborted with
the appropriate abort code.
LINES/n
The value n establishes the maximum number of lines per
page of output. This value must be a minimum of 6. The
default number of lines per page is 55.
LOGON
The $ INFO LOGON parameter sets appropriate flags in
system software to recognize that LOGON may be
operational. If TS8 is configured (via the $ INFO T88
statement), and this statement is not included, GCOS 8
system initialization proceeds. However, the following
error message is displayed at the console when the $LOAD
section is processed. (TS8 is also deconfigured as a
result of this error.)
(
TS8 - COMMON LOGON REQUIRED ($ INFO LOGON), CAN'T
CONFIGURE Ts8
MCPTSS/n
The value n specifies the configured number of Time
Sharing System copies. This value can range from 1-4.
The default value is 1.
(
5-26
DH18-03
$ INFO Parameter
Description
MEMORY/n
The value n specifies the sieve limit for the maximum
memory size allowed for anyone activity in a job. The
number, n, is specified in 1024(lK) blocks. There is no
maximum value for n (other than the constraint imposed by
the system's memory size). The default value is 511K if
this parameter is not specified. The operator can modify
the value n via the console entry LIMIT SIZE nK.
MIGRAT
Specifies that Startup is to attempt to migrate SR 4/JS3
Startup-defined files for use with a GCOS 8 release.
The following message is given on the system console to
indicate successful migration of a file:
4JS3 FILE filename MIGRATED
No message is given if a file cannot be migrated.
Migrated files cannot be released or grown.
NOTE: When executing 4/JS3-DPS1.3 software release and
software release 2000, 2300, or 2500 mixed systems,
individual disk packs containing Startup defined
files must be initialized via 4/JS3-DPS1.3 .MINIT,
because no procedure exists in software releases
2000, 2300, or 2500 to remove the space contained
in the 4/JS3-DPS1.3 Startup master catalog.
Initializing the disk under 4/JS3-DPS1.3 clears the
pointer to the SR 2000/2300/2500 Startup master
catalog.
"\
)
Examples of such mixed operating systems include:
o Migration testing when the site is using unique files
for each release
o Production environments when the site is cycling
between releases
This restriction applies whether or not the $ INFO MIGRAT
option or unique file names are used.
MIXED
CPL and NPL peripheral device types coexist within the
same configuration for a single-system. If a device is
unavailable for allocation, the MIXED parameter allows
substituting its equivalent device type to satisfy the
request (e.g., if a CPL PRT401 printer is unavailable for
allocation, its NPL counterpart (PRU1200) could be
allocated) •
5-27
-~-
DH18-03
-~---------------------------
$ INFO Parameter
Description
MODULE/.mmmmm
One or more modules (.mmmmm) can be specified to reside
in main memory, thereby avoiding the system overhead
resulting from the module-load function. For example,
several FMS modules are high-use modules and loading
these modules into main memory via the MODULE/.mmmmm
option can prove beneficial.
(
Modules that are not reentrant are loaded in the Hard
Core Monitor (HCM). A memory-to-memory transfer is then
executed when the module is called.
Multiple modules can be specified on one $ INFO statement
by repeating the MODULE/.mmmmm option for each module; or
each module can be identified on a separate $ INFO
statement ..
MODULE/.MSDCB ,.
Same as above; required for use of Rapid Access Data
System (RADS). This parameter activates all RADS
runct~ons.
RADS remains dormant until the .MSDCC control
program utilizes the cache memory and issues an enable
request. If .MSDCB is unknown to the system, RADS is
inoperable.
NDFMAP
The deckfile map is not to be printed. If this parameter
is not specified, the deckfile map is printed.
NIASTI
{ALLIn }
lRMVBL/n}
No In-memory Availa.ble Space Table.
For-each remOVable (RMVBL) mass storage device on which a
structured removable disk pack is mounted, and for each
permanent device, several tables are used to maintain
control of disk space allocation to files.
(
The device allocation unit table maintains a current
record of whether or not each allocation unit (AU) is
allocated for permanent file usage. For each device,
this table is maintained on the device itself.
The system builds an available space table (AST) from the
device allocation unit table information whenever the
operator requests an initialization or secondary
initialization. This same action is also triggered
. automatically whenever one of several circumstances occur
(described under "Other NIAST Considerations" below).
The system maintains the AST with a record of whether or
not each AU is allocated for file use (including both
permanent and temporary file use, without distinction).
The temporary file space considered is only the space
allocated since the AST was built.
(
5-28
DH18-03
$ INFO Parameter
Description_
NOTE: The NIAST option is implied when the $ SHARED
Startup statement is specified. Devices that are
connected to shared mass storage controllers and
not specified as removable can be shared with the
Network Processing Supervisor (NPS).
The parameters available for use with the NIAST option
are:
ALL
- Specifies maintaining the AST on the device,
rather than in memory, for each removable device
on which a structured removable disk pack is
mounted and for each permanent device.
RMVBL - Specifies maintaining the AST on the device for
each removable mass storage device on which a
structured removable disk pack is mounted.
(Typically, removable devices have less space
allocation activity than permanent devices.
Therefore, for some sites, the best memory and
I/O utilization may occur by using the RMVBL
option. Resource trade-off is discussed in
detail below.)
n
- Specifies the number of I/O buffers required to
read from or write to the ASTs. The default
value reserves one buffer for every four NIAST
devices.
Other NIAST Considerations
The AST resides on the device when NIAST is specified.
(Although the maintained AST is on the device, the site
sets the number of memory buffers (n) used to manage the
entire group of ASTs for all devices operating in NIAST
mode.) In addition to the AST and the device allocation
unit table, a third table, the temporary descriptor table
(TDT), resides on each permanent device when NIAST is
specified. The TDT is rebuilt automatically whenever the
AST is rebuilt. The availability of the ASTs and TDTs on
the devices enables reallocation of a temporary file
after a system bootload (e.g., for restart purposes),
unless the device is initialized or given a secondary
initialization during the bootload.
5-29
DH18-03
$ INFO Parameter
Description
Because the AST resides on the device when NIAST is
specified, the AST can be read and modified by sources
external to the system that built it. This mode is
invoked automatically when the $ SHARED statement
specifies that the device is shared with a network
processor using the Network Processor Supervisor (NPS)
software. The NIAST option enables the system and
network processor to have direct access to a common,
current source of space allocation information located on
the device.
(
The AST resides in memory when NIAST is not specified or
implied (i.e., neither $ SHARED nor $ INFO NIAST are
specified in the Startup job stream). When the NIAST
option is not in effect, the AST is rebuilt automatically
from the device allocation unit table whenever the system
is bootloaded. Thus, reallocation of a temporary file is
not guaranteed after a system bootload for a device when
NIAST is not specified. As a result, jobs may need to be
reentered to reestablish file space and data previously
resident on temporary files. (If a job is unsuccessful
in its attempt at such a reallocation, it is deleted from
the system. The operator is then notified.)
The following circumstances cause the system to rebuild
the device's AST:
1. When NIAST is specified, the AST is automatically
rebuilt on permanent mass storage devices whenever the
system is bootloaded and the device was last operating
without the NIAST option activated.
2. When NIAST is not specified, the AST is rebuilt
automatically in memory for permanent mass storage
devices whenever the system is bootloaded.
3. In either case, the AST is rebuilt automatically for
removable mass storage devices whenever a structured
disk pack is mounted at Startup, or if i t is mounted
later, the AST rebuilding occurs during system
operation.
The site's decision to use the NIAST option involves the
following trade-off considerations as to the availability
of memory versus the need for I/O resources (except when
$ SHARED is used, which automatically invokes the NIAST
option) •
1. The NIAST option requires less memory because there
are fewer memory buffers than there are devices.
c
5-30
DH18-03
$ INFO Parameter
Description
2. When NIAST is not specified, memory space is required
for each AST. Also, increased Startup time for 1/0
activity results from generating the in-memory AST
whenever the system is bootloaded.
3. The NIAST parameter requires more run-time 1/0
activity, because, unless it is already present in one
of the I/O buffers, the AST must be read into memory
each time it is modified.
The "Mass Storage Operations n section in the GCOS 8 OS
System Operating Techniques manual contains instructional
information on this subject.
NPCHSZ/nnn
This parameter enables the application of virtual mode
patches from the Startup job stream $PATCH section. The
value nnn specifies the size (in words) of the system
segment holding the patch card images. A value of 256 is
recommended; this may be inoreased or decreased,
depending on site patch requirements. There is no
default for this parameter. If a size is not specified,
a segment of zero size is provided.
Virtual mode patches are in GCL-style format, which is a
free form format beginning with a PATCH RU directive and
followed by a positional parameter and keyword
parameters. If a virtual mode patch included in the
$PATCH section of the Startup job stream is in error and
is not applied, Startup gives an error message sequence
to flag this condition. For example:
)
erroneous patch statement image
•• PATCH RUN UNIT COMMAND HAS INCORRECT COMMAND SYNTAX.
erroneous patch statement image
•• KEYWORDS ARE REQUIRED FOR THE PATCH COMMAND.
erroneous patch statement image
•• A PATCH VALUE IS REQUIRED FOR A PATCH DIRECTIVE.
erroneous patch statement image
•• THERE IS NOT ENOUGH INFORMATION TO PERFORM PATCH.
Report the ocourrence of any unapplied patches to the
Honeywell Bull Response Center.
NPRINT
No printer is available to the Startup program8 Any
print routines encountered during System Startup are
ignored and no output is generated. If a printer becomes
inoperable during a dump operation, the operator can
respond SKIP to the message DUMP nnn FROM ddd TO TAPE
(where nnn = file name and ddd = logical device name of a
mass storage device), which permits the system to be
rebooted with the NPRINT option active.
5-31
DH18-03
$ INFO Parameter
Description
This parameter prevents Startup from doing any printing,
to prevent destroying preprinted forms which may be
mounted in printers following a system crash. If Startup
aborts, or is directed to abort via the DUMP command, and
this option is in effect, Startup will ask for a printer
via the NEED PRINTER message. If no printer is
available,press the EOM push button on the system
console and the dump will be skipped (lost).
NPUNCH
No card punch is configured for local punch output.
If a CCU0401 card reader/card punch is configured, the
NPUNCH option makes the card punch unusable but permits
use of the card reader.
If the NPUNCH parameter is specified, bit 2 is set in
.CROPT to indicate that no card punch is configured. If
an activity includes a $ PUNCH statement, the Peripheral
Allocator program deletes the job.
NPUNCH instructs SYSOUT to collect local card punch
output (PNCONL), without delivering it. Such output
remains in SYSOUT space until the system is rebooted with
"SYSOUT RECOVERY=NO", or until one of the following
console verbs is applied to it: NOPRO, PURGE, or REDRC
(e.g., NOPRO PNCONL).
NSYASC
No SYOT ASCII Space Compression. ASCII print line
records Tmedia-codes-7 and 15) are normally edited by
SYOT to reduce disk storage requirements. Editing
consists of replaCing sequences of three or more spaces
with an equivalent two-character, unit-separator control
sequence. The NSYASC option disables ASCII space
compression.
NSYBSC
No SYOT BCD Space Compression. BCD print line records
Tmedia codes-3 and-'1) are similarly edited by replacing
sequences of nine or more spaces with an equivalent
two-character escape sequence. As with ASCII space
compression, the escape sequence is recognized by the
printer hardware (or network processor software). It is
therefore unnecessary to expand compressed records at the
time they are printed. The NSYBSC option disables BCD
space compression.
5-32
DH18-03
c
Description
NSYSAV
No SYOT Seek Address
the-Seek-address for
This is accomplished
number for the write
correct ownership of
the job aborts after
Validation. SYOT normally validates
every write operation it initiates.
by mapping the referenced link
back to the blink table to ensure
the blink. If an error is detected,
taking the following SNAPS:
1 The .MSYOT module itself (with trace table)
Slave being serviced (or at least the GFRC buffer)
3 Slave's collection control segment (PH.SYT)
4 Slave's SSA segment (PH.SSA)
5 GCOS corr~unication region segment (SD.CR)
6 SYSOUT blink table segment (SD.SBT)
7 SYSOUT collection area segment (SD.SCA)
2
The NSYSAV parameter disables the seek address validation
procedure.
NSYTRC
No SYOT TRaCe. SYOT normally maintains a circular trace
of the last-100 key processing events which took place.
The table is an invaluable aid for problem analysis
purposes but, of necessity, requires some processor and
memory resources to maintain. For the benefit of sites
which feel this overhead is prohibitive, the NSYTRC
parameter may be employed to disable the trace mechanism.
OWNID/xxxxxxxxxxxx
Default value for FIPS-79 Owner-ide Fills the
communication region locations, beginning with .CROID,
with up to 12 ASCII characters used by FIPS-79 UFAS tape
labels. The first blank character encountered terminates
the string.
PASSWD/nnn
Password expiration interval. The value nnn specifies
tne maxrmtim-~nuinOer of days ""'for which a user password can
remain valid, and ranges from 1 through 365. This
statement is optional; if it is included, it applies to
the Time Sharing System (TSS) as well as TS8, and keeps
the password expiration interval consistent between the
two time sharing systems. When the interval is exceeded,
a user trying to log on is prompted to change the
password before being allowed to continue.
)
If the value for nnn is zero, or if this statement is not
included, there is no expiration interval for user
passwords (i.e., passwords do not have to be changed).
5-33
DH18-03
$ INFO Parameter
Description
If the value for nnn is nonnumeric, the following message
is output to the system console, and Startup aborts:
.CONFIG CARD BELOW CONTAINS AN ERROR NEAR COLUMN 23.
$
INFO
PASSWD/xxx
where xxx is the nonnumeric value.
If nnn is greater than 365, the following message is
output to the system console:
VALUE FOR PASSWORD EXPIRATION INTERVAL
> MAXIMUM
Startup continues, using the maximum of 365 as a default.
I
PROEXT
Process Extension. Required to enable the Six-Processor
functionality. When this statement is included, Startup
expects the processor number to be in bits 9-11 of the
Fault Base Switches. This parameter is not valid on
DPS 8000, DPS 88, and DPS 90 systems.
PSUM/nnn
The value nnn specifies the maximum number of processes
to be allowed (cataloged) in the system.
The value nnn must be in the range of 63 to 487. These
values are applied by Startup if less than the minimum
(e.g., 62) or more than the maximum (e.g., 488) is
specified. The value nnn must be an odd-numbered value
(e.g., 65 or 67). If it is not, the specified number
plus 1 is substituted by Startup (e.g., 66 becomes 67).
The default value of nnn is 127. A maximum of 487
processes, including the number of Ts8 users who will be
concurrently logged on, can be cataloged.
5-34
DH18-03
(
$ INFO Parameter
Description
PT1SIZ/nnnn
The value nnnn specifies the size of the page table for
working space 1. The default size of this page table is
2048 words, which is sufficient for most software
configurations. When the default is not sufficient, it
will be detected and reported by POPM immediately after
it receives control from Startup. When the condition is
detected, the normal START ROLL CALL message to the
operator's console will be followed by
···ERR
••• ERR WORK SPACE 1 PAGE TABLE IS TOO SMALL •
••• ERR USE $ INFO PT1SIZ/nnnn AND REBOOT.
·**ERR
where nnnn is the needed page table size, in words, as
determined by POPM. The operator should do a warm boot
using the AUTOLOAD file for input, and using the Startup
console editor to add the $ INFO PT1SIZ/nnnn.
PTCHSZ/nnn
\
)
The value nnn specifies the maximum number of patches
that can be included in the $PATCH section. The default
value is 256.
It is recommended that consideration be given to
subseque~t additions of patches via the system console
when establishing the patch limit.
If the number of patches included in the $PATCH section
exceeds the number specified with the $ INFO PTCHSZ
parameter, Startup accepts only the number of patches
specified with the PTCHSZ parameter. All patches
exceeding this number are ignored and the message:
TOO MANY PATCHES USE $ INFO PTCHSZ/N
is issued to the system console.
5-35
DH18-03
$ INFO Parameter
Description
(
RESVID/FORMS,id1[,id2, ••• ,idn]/
The RESVID/FORMS parameter provides a means to reserve
certain station ids for use as collection nodes for
special forms. No remote connection will be allowed to
these reserved ids, which will be class supported. At
least one id must be specified if the parameter is used;
a maximum of 512 ids may be declared. Each id must
consist of a two-character identifier. The identifiers
00, space-space, and II are not permitted. A space is
not permitted as part of an identifier. Segment DP.RID
is allocated for the reserved id list and is organized as
follows:
Word 0:
TALLY 1,n (n = number of ids)
Word 1-n: VFD 2/1,22/0,H12/xx (xx=BCI id)
RESVID/{PPSOFL},id1[,id2, ••• ,idn]/
{PPSONL}
The RESVID/PPSOFL and RESVID/PPSONL parameters provide a
means to reserve certain station ids for use as
collection nodes for the Page Processing System (PPS) in
offline and online modes, respectively. No remote
connection will be allowed to these reserved ids, which
will be class supported. At least one id must be
specified if the parameter is used; a maximum of 512 ids
may be declared. Each id must consist of a two-character
identifier. The identifiers 00, space-space, and !I are
not permitted. A space is not permitted as part of an
identifier.
PPSOFL - Required parameter to enable offline PPS
functionality; either the offline or online PPS
software must be available to the system when
PPSOFL is specified. Any output for PPS
reserved ids is spooled to tape for subsequent
input to the Page Processor.
PPSONL - Required parameter to enable both online and
offline functionality; the online PPS software
must be available to the system when PPSONL is
specified. User jobs may assign output to the
reserved ids for subsequent transfer directly to
the Page Processor, as well as spooling to a PPS
tape.
Destination ides) for the PPS correspond to remote
station ides) used for standard remote output. They are
reserved ides) and are included in the reserved id table
within memory.
5-36
DH18-03
,
,
$ INFO Parameter
Description
The PPSOFL and PPSONL parameters and reserved ides) on
the $ INFO RESVID statement do not represent a one-to-one
correspondence with Page Processors actually configured
on a system. Two or more Page Processors may utilize the
same reserved ides) and one system may be configured
online while another is configured offline.
Multiple $ INFO RESVID statements can be used to assign
more reserved ids than can be contained on one statement;
however, the same processing mode (i.e., PPSOFL or
PPSONL) must be specified on each statement.
RLSDSK
Startup is to release any mass storage devices that are
offline during System Startup. If the released device
contains any GeOS system files, Startup aborts. If the
device is online at System Startup, it is not released.
RLSPNT
Startup is to release any printer that is offline during
System Startup. If the released printer is that which is
used by the Startup program, the NPRINT parameter is
automatically invoked. A released printer can be
reassigned to the system via the console entry ASGN
icccdd (where i = input/output controller number, ccc =
channel number, and dd = device number). If the device
is online at System Startup, it is not released.
ROLLCALL/ddd
Rollcall messages, which are issued during System
Startup, are directed to printer ddd instead of to the
system console (where ddd = logical device name of the
printer). Use of this parameter interrupts a fast boot
process, which otherwise bypasses the rollcall function.
5-37
DH18-03
$ INFO Parameter
Description
SAVDMP/list
The list defines the set of default options used to
control what is dumped to system-controlled space (i.e.,
a save dump) at the time a process (slave) dump is
taken. The options specified on this statement are
augmented with options specified on the SAVDMP= option of
the $ DMPOPT JCL statement associated with the activity
in which the dump is taken. The options are specified
after the "I", and are separated by commas. The
underlined option is the default:
ALL7
- Dump the entire contents of dynamically
allocatable space behind WSR7.
ANY
- Utilize default options, which means to dump OS
control segments behind WSR7.
NODUMP - Produce no save dump of any kind. If the site
desires that the activity definer SSDUMP option
be effective, or allow the use of the SAVDMP
option on the $ DMPOPT JCL statement to be
effective, a $ INFO SAVDMP option must be used
to specify a value other than NODUMP.
PSDUMP or
W4DUMP - Dump the entire dynamically allocatable contents
of WSR4 (private shared space).
SSDUMP or
W5DUMP - Dump the entire dynamically allocatable contents
of WSR5 (integrated software space). This is
the same as specifying SSDUMP on the activity
definer.
WSDUMP or
W6DUMP - Dump the entire dynamically allocatable contents
of WSR6 (workstation space).
C4DUMP - Dump the OS control segments behind WSR4.
C5DUMP - Dump the OS control segments behind WSR5.
C6DUMP - Dump the OS control segments behind WSR6.
SCFPRG
The SCF purge-to-disk option is enabled, so that SCF data
will be collected on permanent files instead of on
magnetic tape. Refer to the GCOS 8 OS Accounting manual
for details.
5-38
DH18-03
$ INFO Parameter
Description
SCHSAV
All job input is saved. This feature protects against
the loss of jobs followIng a system malfunction. The
duration of the save period is dependent upon System
Scheduler program parameters (i.e., the size of the class
catalog and the amount of processing activity within the
job class). All saved jobs are placed in a temporary
status (i.e., "saved"). Rerunning a saved job is
initiated via the console entry JRERUN sssss (where sssss
= SNUMB).
If this parameter is active, the 15 oldest saved jobs
that have completed execution are removed from the System
Scheduler's SSFILE file as space for a class approaches
exhaustion (i.e., approaches the class maximum as
specified on the $ SSFILE statement in the $EDIT
section) •
Errors within the job stream (i.e., JeL statements),
which cause fatal processing errors, override the save
function and job input is not saved.
SDCOL/n
The value n specifies the number of additional pages
be allocated to the SD.COL segment, which is used by
and ECOL to store and retrieve type 3 GEPR records.
default size of SD.COL is two pages. If three pages
deSired, specify the value of n as 1. If four pages
deSired, specify the value of n as 2.
to
lOS
The
are
are
If the value of n is not 0, 1, or 2, the following error
message is issued to the console:
CONFIG CARD BELOW CONTAINS AN ERROR NEAR cc
$ INFO SDCOL/n
where cc is the JCL statement column number.
SLAVE/n
The value n specifies the maximum size of the slave
Instruction Segment (i.e., the largest slave job in
execution) in 1K blocks. The default value is 255.
value exceeding the default is truncated to 255.
*
Any
SLINKS/n
The value n specifies the sieve limit for the number of
mass storage links requested for any temporary file.
There is no default value set.
SLTAPE/n
The value n specifies the sieve limit for the number of
magnetiC tape files requested by any activity in a job.
There is no default value set.
5-39
DH18-03
$ INFO Parameter
Description
SLTlME/hhmm
The value hhmm specifies the maximum amount (i.e., sieve
limit) of processor time that can be allocated to one job
(where hh = hours and mm = hundredths of one hour). The
maximum value that can be specified is 9999. The default
time limit is 9.99 hours. The time specified must not be
less than 0.01 hours.
SMCDUP/ddd
The System Master Catalog (SMC) is to be duplicated on
mass storage device ddd (where ddd = logical device
name). Device ddd must not be device ST1, which contains
the SMC. If ST1 is defined with the SMCDUP parameter,
Startup aborts.
(
SMCDUP status can be added or deleted only when the
operator responds YES to both .INITIALIZE? and ·EDIT?
during a bootload. If an attempt is made to change the
status by adding or deleting the parameter to/from the
$ INFO statement, except during a bootload sequence,
Startup aborts.
I
Startup also aborts if an attempt is made to assign the
SMC and the duplicate SMC to two logical devices on the
same physical unit.
SPN,umc_1[/cat-or-file-1],umc_2[/cat-or-file-2]
The system path name (SPN) replacement parameter replaces
the actual TIMc
UMC/cat-or-file specified in the first
argument (umc 1/cat-or-file-1) with that specified in the
second argument (umc 2/cat-or-file-2) whenever FMS
accesses umc 1/cat-or-file-1. The rules for replacement
follow:
(
or
1. SYS CAT cannot be specified as umc 1 or umc 2.
2. Commas must separate SPN, the first argument, and the
second argument.
3. umc 1 must either begin with SYS or be OPNSUTIL.
,4. umc 2 must begin with SYS if umc 1 begins with SYS ,
or umc_2 must be a replacment for-a umc 1 of OPNSUTIL.
5. Default UMCs do not exist (i.e., umc 1 and umc 2
cannot be null).
6. If a slash delimiter follows umc 1 or umc 2,. it must
follow both, and a cat-or-file (either catalog name or
quick access file name) must follow both.
(
5-40
DH18-03
$ INFO Parameter
Des~ription
~
'I
V
7. The UMC/cat-or-file arguments are limited, as the
format shows, to two levels.
8. Multiple replacement sets are allowed. Each
replacement set must be contained on one $ INFO SPN
statement (i.e., $ ETC is not supported with the SPN
parameter).
The specified replacements are made for all FMS accesses
(e.g., JCL statements (including $ USERID statements),
Time Sharing accesses, and FILSYS directives (including
USERID but excluding RESTORE, SAVE, RESTOREMAST, and
SAVEMAST».
Error messages that apply to the SPN parameter are listed
below. The rules violated are denoted in parentheses
(and are not part of the message).
•
•
•
•
•
•
•
\
SPN
SPN
SPN
SPN
SPN
SPN
SPN
ERR
ERR
ERR
ERR
ERR
ERR
ERR
SYS CAT CANNOT BE CHANGED
(1)
EXPECT , OR /
(2)
(2)
"OLD" FIELD NOT FOLLOWED BY COMMA
(4)
"NEW" NOT SYS OR REPL FOR OPNSUTIL
BLANK USERID FIELD INVALID
(5)
BLANK CATALOG, FIELD INVALID
(5)
ONLY ONE SET PER INFO CARD
(8)
J
/
SSAOVL/n
The value n specifies the number of real pages allocated
to Slave Service Area (SSA) cache. The default value is
8. The minimum value is 4 and the maximum value is 64.
SYBDI/n
Size of backdoor information segment. The default value
of 1024 allows for approximately 50 backdoor jobs in the
system.
SYBRT/n
GEOT blink release threshold. This parameter defaults to
a value of 20. This parameter should be used by a site
wanting to discard output more rapidly after delivery is
complete.
SYJOS/n
Size of job output special segment. The default value of
64 allows for 15 output specials. Note: because of the
reduced use of the specials table, this should probably
be sufficient for most sites.
SYJOT/n
Size of job output table segment (SNUML). The default
value of 1024 allows for 146 jobs with one output type
and destination. A reasonable value for sites requiring
space for 500 jobs with more than one output type or
destination is 4096.
5-41
~H18-03
$ INFO Parameter
Description
SYSOUT/n
ttleM!;¥Q~~~~P,~~~~~JJm~ t~~~~~ lI~a:cimum
SYSTEMMAP/NO
~um~t~~~t.~l~~A~~fi&Q~.Na~~tg~~tl.~~, ~nIY ~he
Job $ LIMITS statement 1S cons1aered 1r~'rt-Ts present;
otherwise, the value considered is the sum of the limits
specified for the individual activities by a $ LIMITS
statement, if present; or by the default value for the
activity type. There is no default value set.
Do not print the map of the GCOS file structure. The
default is for this map to be printed. Inclusion of this
parameter reduces the time required for starting the
system.
TAPDEN/xxxx
The xxxx field override.s the system default value used
when processing the DEN9 field of the $ TAPE control
statement (see the GCOS 8 OS Job Control Language manual
for further details). The xxxx parameter can include the
following codes:
Code
Description
ABCD
ABC
BCD
BC
CD
DE
D
200, 556, 800, 1600 bpi
200, 556, 800 bpi
556, 800, 1600 bpi
556, 800 bpi
800, 1600 bpi
1600, 6250 bpi
1600 bpi
6250 bpi
E
TIMEZ/zzz
Universal date/time is automatically set from the local
date/time entry by the operator when the system is
booted. This is done from a time zone entry which must
be included on the $ INFO TIMEZ statement. The
$ INFO TIMEZ must be included in the Startup job stream.
If this statement is not included, Startup will abort
with the following message:
·MANDATORY $ INFO TIMEZ CARD WAS NOT FOUND
The value zzz specifies the local time zone identifier.
The following Ii.st defines the time zone identifiers
recognized by Startup:
5-42
DH18-03
c
$ INFO Parameter
Description
ZONE
IDENT
NT
AHST
YST
PST
MST
PDT
CST
MDT
EST
CDT
AST
EDT
NST
GST
ADT
AT
WAT
UT
Z
GMI'
CET
MET
BST
SWT
FWT
EET
SST
FST
BT
ZP4
ZP5
1ST
ZP6
ZP7
JT
CCT
JST
SAST
ZP10
ZP11
NZT
)
TS8
OFFSET
DESCRIPTION
NOME TIME
ALASKA-HAWAII STANDARD TIME
YUKON STANDARD TIME
PACIFIC STANDARD TIME
MOUNTAIN STANDARD TIME
PACIFIC DAYLIGHT TIME
CENTRAL STANDARD TIME
MOUNTAIN DAYLIGHT TIME
EASTERN STANDARD TIME
CENTRAL DAYLIGHT TIME
ATLANTIC STANDARD TIME
EASTERN DAYLIGHT TIME
NEWFOUNDLAND STANDARD TIME
GREENLAND STANDARD TIME
ATLANTIC DAYLIGHT TIME
AZORES TIME
-2
WEST AFRICA TIME
-1
UNIVERSAL TIME
+0
+0
ZERO ("ZULU")
GREENWICH MEAN TIME
+0
CENTRAL EUROPEAN TIME
+1
MIDDLE EUROPE TIME
+1
BRITISH SUMMER TIME
+1
SWEDISH WINTER TIME
+1
FRENCH WINTER TIME
+1
EASTERN EUROPEAN TIME
+2
SWEDISH SUMMER TIME
+2
+2
FRENCH SUMMER TIME
BAGDAD TIME
+3
Universal time +4 HOURS
+4
Universal time +5 HOURS
+5
+5:30 INDIAN STANDARD TIME
Universal time +6 HOURS
+6
Universal time +7 HOURS
+7
+7:30 JAVA TIME
CHINA COAST TIME
+8
JAPAN STANDARD TIME
+9
+9:30 SOUTH AUSTRALIA STANDARD TIME
Universal time +10 HOURS
+10
Universal time +11 HOURS
+11
+12
NEW ZEALAND TIME
-11
-10
-9
-8
-7
-7
-6
-6
-5
-5
-4
-4
-3:30
-3
-3
This statement requires that Ts8 module .MTSVC be edited
onto the system. If this module is not present, system
initialization proceeds but the following error message
is displayed when the $LOAD section is processed:
5-43
DH18-03
$ INFO Parameter
De_~~l2!ption
TS8 - REQUIRED MODULE .MTSVC NOT FOUND, CAN'T CONFIGURE
Ts8
The presence of this message indicates that the required
module was not part of the tapes comprising the Software
Release media. The Honeywell Bull Response Center should
be contacted immediately.
USRDMP flist
The list defines the set of default options used to
control what is dumped to the destination specified for
the process (by default to the SYSOUT p. file) at the
time a process (slave) dump is taken. The options
specified on this statement are augmented with options
specified on the USRDMP= option of the $ DMPOPT JCL
statement associated with the activity in which the dump
is taken. The options are specified after the "In, and
are separated by commas. The underlined option is the
default. Those marked with asterisks (*) apply only to
processes with privity.
ALL7
- Along with active domains, dump the entire
contents of dynamically allocatable space behind
WSR7.
ANY
- Utilize default options, which means for all
active domains to dump OS control segments
behind WSR7 and writeable segments behind other
workspace registers 2-6.
*
*
C4DUMP - Dump the OS control segments behind WSR4.
•
•
C6DUMP - Dump the OS control segments behind WSR6 •
C5DUMP - Dump the OS control segments behind WSR5.
INHIBD - Include domains Whose property keys say to
inhibit dump as active domains.
MINI
- Produce a dump including only summary
information, history registers, and the dump
causing the safe-store frame.
NODUMP - Produce no user dump of any kind.
NOSHR
- Do not dump segments in shared workspaces, even
if they exist in active domains.
OSEXT
- Dump OS control segments not normally· useful in
analyzing process dump problems. This includes
most notably SYSOUT control segments.
5-#4
DH18-03
C
$ INFO Parameter
•
•
PSDUMP or
W4DUMP - Dump the entire dynamically allocatable contents
of WSR4 (private shared space).
SHRRW
•
•
- Dump all segments in active domains, even if
they are read-only.
SSDUMP or
W5DUMP - Dump the entire dynamically allocatable contents
of WSR5 (integrated software space).
/
WSSIZE/2,s2,b2
WSSIZE/3,s3,b3
"1
)
/
•
STACKS - Dump tJfe content, including residual, of stack
segments PH.ADS, PH.AP, and PH.SS.
*
*
WSDUMP or
W6DUMP - Dump the entire dynamically allocatable contents
of WSR6 (workstation space).
•
WSROl
- Dump segments behind WSRO and WSR1 for active
domain.s.
These statements can be used to set the virtual sizes and
backing store file coverage of system shared workspacesc
The s2 value is ignored.
future use.
This field is reserved for
The b2 value is used to specify the percentage of virtual
memory for which backing store file space is to be
allocated for the standard WSR2 (Workspace 4). The value
is specified in percent, with 20% being the default.
The s3 value is used to establish the size of the
standard WSR3 (Workspace 10) virtual memory size, in
megawords. The default is 1M.
The b3 value is used to specify the percentage of virtual
memory for which backing store file space is to be
allocated for the standard WSR3 (Workspace 10). The
value is specified in percent, with 50% being the
default. The virtual size for WSR3 is taken from the s3
parameter. The b3 value can be omitted, even if the s3
value is specified.
5-45
------
DH18-03
-------------------------------------------------
Input/Output Controller Statements
T.h.~.,.lPJt!LtLa':;l*~El!t... Q.,~~~,§,tfl,k"E~J!l~JltWj,Jt:'1~~.J", ,i!OP, ?~v~~ m 10:;)
~~_~\llt~,g<",."~~_,S~"(J:,,~~,,,,,~l!~",,~~i t~:' s . . £~!,Rn~~):t.p.",~~S~~,; Each per~pnerartna t ~S
assigneo to a specific~cnann'eI' \lIH/PUB of an input/output controller must be
identified. If a device is not specified on such a statement, the Startup
program does not consider that device a part of the system configuration, even
though the device may be referred to on other statements in the Startup job
stream.
Once the system has been initialized, the operator cannot deconfigure a
permanent device via a console entry or by removing the $ Iyy statement from
the Startup job stream. However, a permanent device can be released via the
console entry RLSE icccdd (where i = input/output controller number, ccc =
channel number, and dd = device number). If a device is released, the Startup
or FMS program may abort if required files and/or catalogs were assigned to the
device.
If the mass storage hardware configuration is to change, all jobs in the system
must first run to termination before the modification can be effected. After
all jobs have terminated, the $ Iyy statement (images) can be modified to
reflect the new configuration. During the bootload sequence, the operator must
respond NO to the *RESTART? question and YES to the .SYSTEM SCHEDULER CLEAR?
question.
The DEDICATED option can be used to reserve (restrict) use of the specific
device to only those programs that request the device by its logical device
name (ddd field). If the device is not requested by its logical device name,
it is not allocated - even if the device is not busy at allocation time. It is
not a good practice to dedicate ST1.
This feature frequently is used to avoid repeated printer form or magnetic tape
reel changes. For example, a job that requires a special form can have its
output directed via the $ PRINT JCL statement to a dedicated printer, which
contains the special form.
The DEDICATED option cannot apply to the system console.
A device also can be dynamically dedicated via the console entry DEDCAT. The
dedicated status - either Startup or console assigned - can be dynamically
removed via the console entry UNDED. (Refer to the GCOS 8 OS System Operator
Messages manual for a description of the DEDCAT and UNDED entries.)
*.
In addition to the DEDICATED option, the following comments apply to the
logical device name (ddd) field. A logical device name comprises three
alphanumeric characters. The first character must be nonzero, the second
character must be alphabetic, and the third character can be alphabetic or
numeric.
5-46
DH18-03
(
With the exception of mass storage devices, which can have only one logical
device name, each device can be assigned multiple logical device names. Each
peripheral must have at least one logical device name and each logical name
must be unique. A maximum of 2048 logical device names can be assigned via the
Startup job stream. (Two additional names are reserved for assignment via the
system console.)
Logical device names also can be assigned via the console entry NAME icccdd nnn
(where i = input/output controller number, ccc = channel number, dd = device
number, and nnn = logical device name). Logical device names also can be
removed from the name table via the console entry UNAME nnn (where nnn =
logical device name). Note, however, that neither of these entries can be used
in conjunction with mass storage devices.
Logical device names TY1-TY4 (console) and ST1 (mass storage) must be specified
at System Startup. If device names ST1 and TY1 are J,)~Q.t .. defined, the console
message
-DEVICE xxx UNDEFINED is issued and Startupaborts'
TY 1 ) •
.. .---- ... --------.....
. (where xxx~ST1 or
One $ Iyy statement is required for each console configured as a system control
device, while a separate $ Iyy statement is required to configure a System
Control Center (SCC) that is to be used by the VIDEO program.
NOTE: The choice of the input/output controller statement type ($ lMU, $ IMX,
$ 10M, $ lOP, $ lOX) is dependent on the hardware platform (DPS 8,
DPS 8000, DPS 88, or DPS 90) and the peripheral subsystem (in the DPS 8
platform). A DPS 8 system may use either $ 10M or $ lMU statements or
both. A DPS 8000 system may use only $ I~~ statements. A DPS 88 system
may use only $ lOX statements. P. DPS 90 system may use only $ lOP
statements. Channels can be specified interchangeably either as 'CH' or
'PUB', regardless of the statement type.
Throughout the rest of this section, $ Iyy is used to represent $ lMU/$ IMX/
$ IOM/$ IOP/$ lOX in the text and examples. Substitution of the proper
statement type should be based upon the rules previously outlined. Any
additional restrictions are noted in reference to the affected statement type.
$ 1yy STATEMENT FOR SYSTEM CONTROL DEVICES
The four system console names TY1, TY2, TY3, and 1Y4 m,,!st be as~ign~d"'I"~~,,,$,.,,,+I¥.,
state~~nt~ tt~~J!!!r.~elfi:915!!If~f'~"·CJ'e,~'~9~.s (i 7e,., cons9,~es). (GCOS software
issues system messages to the consoles on the basis of the four console
names. ) These
foul',~ !l.~m~s .Il!J,~,s~, J>,e ass?-gned eY. .~~~.""~.,.,f,::. c..",,?,. p
. ,,,,,,t.\,,.X.,,,.)?n~, ci,~y...ig,. ~. .r;;~'C',.:"
.
con f 19ure •
o
d~ ~~t:;'ll'il;I<.~:~;"~'<::..o<:',~x'(I,"~
".>......i:~,'1-:.'{v{·~b·;...··"''-,...... ·,~~~i.t·.'t~.':-¥"':':"".,,\:,,~>;;'-..&"';~
When multiple consoles are configured, the four required console names can be
aSSigned to any of the consoles in any manner (e.g., one name can be assigned
to one console and three names can be aSSigned to another console). However,
all four names must be specified.
5-47
DH18-03
The format for $ 1yy statements defining system control devices is:
1
1
8
6
$
Iyy-m
{PUB-p},tttttt,nnn, ••• ,nnn
{CH-p }
where:
m
- Number of the 1yy to which the system control device (i.e.,
console) is connected. The value of m can be 0-3.
p
- Iyy channel (CH/PUB) number.
1MU
IMX
10M
lOP
lOX
Permissible values are:
8-63
0-127
8-31
8-63
0-127
tttttt - Device type as follows:
nnn
Code
Description
CS66/RMC66
CS6001
CS6002
CS6602
CS6604
CS6605
CSU6601
CSU6001
CSU6002
CSU6602
CSU6604
CSU6605
console
console
console
console
console
console
- Name of the system console assigned to this lyy and channel.
console name can only be TY1, TY2, TY3, and TY4.
The
The following example shows the logical device names assigned to the CSU6601
console (CS66) configured on channel 31 (CH-31) of lyy-O.
1
186
$
Iyy-O
CH-31,CS66,TY1,TY2,TY3,TY4
The following example indicates use of two $ lyy statements to configure
logical devices TY1-TY4 on two CSU6601 consoles (CS66). Note that these
devices may be connected to one or two Iyys and that the channel number must be
different on each $ 1yy statement.
1
1
8
6
$
$
1yy-0
1yy-0
CH-30,CS66,TY1,TY2
CH-31,CS66,TY3,TY4
5-48
DH18-03
$ Iyy STATEMENT FOR VIDEO DEVICE
The logical device name TY5 can be assigned to a CSU6001, CSU6601, or CSU6602
if reserving one of the devices for use as a VIDEO device. The reserved device
(for VIDEO purposes) is a CRT output-only device, and cannot be used for
general input purposes. The device can be used to enter VIDEO-related
commands.
The format for the $ Iyy statements defining a VIDEO device follows. The
variables m, p, and tttttt are the same as those for defining system control
devices.
1
186
$
Iyy-m
{CH-p }
{PUB-p},tttttt,TY5
VIDEO operations change when the Console Manager software option is to be used
or when GCOS 8 is executing on the DPS 88 system. In both of these instances,
the VIDEO facility must be run on a terminal configured on a Front-end Network
Processor. Refer to the GCOS 8 OS VIDEO manual for instructions for using
VIDEO on a terminal.
$ Iyy STATEMENT FOR REMOTE MAINTENANCE CORSOLE
The Remote Maintenance Console is used primarily for the support of Customer
Service maintenance and is configured in the Startup job stream as follows:
1
186
$
Iyy-m
{CH-p }
{PUB-p},RMC66,TR1
where:
RMC66 - The Remote Maintenance Console device mnemonic
TR1
- The Remote Console Device name
The variables m and p are the same as those defined under ft$ Iyy Format For
System Control Device ft on the preceding pages in this section.
The RMC66 resides on the remote port of the CSU6601 console channel adapter
when the adapter is configured for two channels. It consists of a Diagnostic
Processor Unit (DPU) with its on site console and remote port which has dial-in
capability for Honeywell Bull Response Center usage.
The CSU6601 console in this mode requires that the channel for the Master
Console have an even number. The channel for the Remote Console must have a
contiguous odd number.
5-49
DH18-03
A second RMC66 channel may be configured as the odd-numbered channel on another
channel adapter board, but is not given a device name. Access through the
second channel to the RMC66 is accomplished by use of the MOVE console verb.
The following is a recoramended Local/Remote system initialization procedure
using TY1 and the RMC66 where TY1 and the RMC66 are configured on the same
CSU6601 channel adapter board. The TY1 operator enables the RMC66 at that
point via the ENABLE verb, and either the TY1 or RMC66 operator enters the
RELINQUISH console verb. Then, either the TY1 orRMC66 operator places their
keyboard in control (by pushing the RETURN or End Of Message key) and responds
to system initial~zation dialog.
$ IMU OR $ IMX STATEMENT FOR THE MAINTENANCE CONSOLE
Every IMU or IMX in a system configuration bas a maintenance console adapter
(MCA) channel. It is fixed on channel 3 traditionally in the overhead channel
group. It is configured in the Startup job stream as follows:
1
8
6
{IMU-m} {CH-p },MCA[,ddd][,DEDICATED][,RLSE]
{IMX-m} {PUB-p}
$
where:
or IMX II
m
- IMU
p
- Channel # (Must be equal to 3)
ddd
Logical device name. A logical device name comprises three
alphanumeric characters. The first character must be nonzero, the
second character must be alphabetiC, and the third character oan be
alphabetiC or numeric.
Example:
1
$
8
6
IMU-1
CH-3,MCA,IvlC1
For each configured IMU or IMX, for which no MeA is configured in the Startup
job stream, Startup builds an entry at the end of the device SCT area, as
though the following statement were included in the Startup job stream:
1
$
8
{IMU-m}
{IMX-m}
1
6
CH-3,MCA
5-50
DH18-03
where:
m - IMU or IMX /I
$ Iyy STATEMENT FOR MASS STORAGE SUBSYSTEMS
The same basic $ Iyy statement format applies for all mass storage devices.
The format for these $ Iyy statements follows. (If more than one device is
defined on a single $ Iyy statement, the UNIT-u and ddd fields must be repeated
for each mass storage device configured within the devioe type (tttttt field)
specified. )
1
1
8
$
Iyy-m
{CH-p }
{PUB-p},tttttt,UNITS-n[,NONSEQ],
$
ETC
{UNIT-uu } {ddd }
{UNIT-uu.s},{SPARE}[,vvvvvv][,S-xxxxx][,AU-a][,RMVBL][,
$
ETC
6
I
DEDICATED][,NOFMS][,RLSE]
where:
m
- Number of the Iyy to which this mass storage subsystem is
oonneoted. The value of m can be 0-3.
p
- Iyy channel (CH/PUB) number.
IMU
IMX
10M
lOP
lOX
tttttt
Permissible values are:
8-63
0-127
B-31
8-63
0-127
Devioe type for all units except those for which vvvvvv is
specified. Refer to Table 5-4 for valid device types.
NOTE: The I-1SU33BO, MSU33B1, and MSS80Bo subsystems have the
following configuration restriotions:
I
1. These subsystems may not be specified on a $ 10M
statement.
*
2. These subsystems may not be used for NPS sharing
environment.
3. The MSSBOBO may only be specified on a $ IMX statement.
5-51
DH18-03
I
Table 5-4.
Mass Storage Subsystem Parameters
(
Device
Type Code
(tttttt)
MS0400
MS0402
MS0450
MS0500
MS0501
MSC1A
MSC1B
MSD1A
MSD1B
MSM1A
MSM1B
MSM1E
•••
n
Description
Maximum
Physical
Devices
Maximum
Logical
Devices
(UNITS-n)
MSU0400
MSU0402
MSU0451
MSU0500
MSU0501
MSU3380 •
MSU3380 ••
MSU3381
MSU3381 ••
MSS8080 •
MSS8080
MSS8080
32
32
32
63
63
32
32
32
32
64
64
64
32
32
32
63
63
32
64
64
96
64
128
64
•
••
••
Logical
Device
Number
(UNIT-uu)
1 - 32
1 - 32
1 - 32
1 - 63
1 - 63
0 - 31
0.0 - 31.1
0.0 - 31.1
0.0 - 31.2
o - 63
0.0 - 63.1
o - 63
64-word sector rormat
512-word sector rormat
- Number or logical devices on this channel (CH/PUB) ror this
device type (tttttt field). If the value n is not the same as
the total number of logical devices defined by UNIT-u fields,
Startup aborts. For example, if there are three UNIT-u fields,
n must be 3 (UNITS-3). (Refer to Table 5-4 for the maximum
number or logical devices that can be specified for each device
type. )
When defining MSC1B, MSD1A, MSD1B. and MSM1B subsystems, UNIT
applies to a logical device. One MSC1B, MSD1A, or MSM1B
comprises two logical devices. One MSD1B comprises three
logical devices. Each logical device must be separately defined
by a UNIT-u field.
NONSEQ
- The logical devices that are defined by UNIT-u fields are not
necessarily in numeric sequence. For example, the devices may
be defined in the sequence UNIT-2, UNIT-3, UNIT-1, and UNIT-4
rather,than in the sequence UNIT-1, UNIT-2, UNIT-3, and UNIT-4.
Because mass storage devices are allocated in the same sequence
that devices are defined on $ Iyy statements, the NONSEQ
parameter can be used to influence the order of allocation.
uu
uu.s
- Logical device identification number. The logical device name
(ddd rield) immediately following this field is associated with
this logical device identification number. The subunit portion
(.s) of this field is only valid for the device types in Table
5-4 that show subunits in the Logical Device Number column.
(Refer to Table 5-4 for the valid form for each device type.)
5-52
DH18-03
ddd
- Logical device name, comprised of three alphanumeric characters.
The first character must be nonzero, the second character must
be alphabetic, and the third character can be alphabetic or
numeric. One device on the system must be named ST1. If ST1 is
not defined, the console message DEVICE ST1 UNDEFINED is issued
and Startup aborts. For mirrored pairs of devices, "SPARE" must
be used as the logical device name for the secondary device.
vvvvvv
- Device type, for logical device ddd, immediately preceeding.
Valid codes are the same as for tttttt. vvvvvv defaults to the
value specified for tttttt.
xxxxx
- Five-character alphanumeric identifier (device label) of the
logical device named ddd.
a
- Number of llinks per allocation unit (AU). If this AU size is
not the same as that used to initialize the logical device
(i.e., via the $ INIT statement in the Startup job stream,
Re
ra e Initialization Program (RSIP), or Removable
Disk Initialization Program
e
ce will be released
when there is an attempt to allocate space on the device.
I
I
It is recommended that AU size always be specified in
conjunction with a released or removable device. Startup passes
this value to the Mass Storage Allocation program, which builds
in-memory allocation tables.
If a device is to have an AU size other than the default value,
the value must be specified in this field. Otherwise, Startup
assigns the default value, which is one for all devices except
the MSU0501, MSC1B, MSD1B, MSM1B, and MSM1E. Those devices have
a default value of eight.
For any volume formatted in 512-word sectors, that is to be a
member of a volume set, the AU size must be eight or a multiple
of eight.
The AU size may also be specified via the $ INIT statement in
the $INITIALIZE section. If the size specified on the $ Iyy
statement and the size specified on the $ INIT statement are
different, the smaller size is used.
In addition, if' the $ SHARED statement defines a logical device
as being shared with NPS, the AU size for that logical device
must be 12. (NPS allocates mass storage space in one-link
(12-llink) increments.) If the device does not have an AU size
of' 12, NPS aborts.
RMVBL
- This logical device is a removable device. (System files cannot
reside on a device defined as RMVBL.) Any device that is to be
a member of a volume set must be declared as RMVBL.
DEDICATED - This is a dedicated device.
5-53
DH18-03
I
- The FMS catalog and permanent file structure is not permitted on
this device. All space on this mass storage device is temporary
file space. NOFMS cannot be used with RMVBL. If NOFMS is
specified for device ST1, the console message:
NOFMS
c
ST1/SMCDUP/GCOS FILE/CAT DEVICES CAN'T DEFINE FMS
is issued and Startup aborts.
Startup also aborts if the CAT option is specified on the $ INIT
st~tement for a device for which a $ Iyy ••• NOFMS statement is
included.
RLSE
This device is configured and released at Startup.
The following example indicates that four (UNITS-4) MSU0451 mass storage
devices (MS0450) are configured on channel 14 (CH-14) of IOM-O. One device
(UNIT-1, logical device name MS1) contains permanent space and has a default
allocation unit size of 1. The second device (UNIT-2, logical device name MS2)
is a removable (RMVBL) device with an allocation unit size of 1 (AU-1). The
third device (UNIT-3, logical device name MS3) is a dedicated (DEDICATED)
permanent mass storage device with a default allocation unit size of 1.
Programs using UNIT-3 must request this device by its logical device name. The
fourth device (UNIT-4, logical device name MS4) contains only temporary space
(NOFMS) and has a default allocation unit size of 1.
1
8
1
6
$
$
$
$
$
IOM-O
ETC
ETC
ETC
ETC
CH-14,MS0450,UNITS-4,
UNIT-1,MS1,
UNIT-2,MS2,RMVBL,AU-1,
UNIT-3,MS3,DEDICATED,
UNIT-4,MS4,NOFMS
~
The next example indicates that two physical MSU0500 mass storage devices are
configured on channel 15 (CH-15) of IOX-O. The logical device definitions for
each physical device must be in odd/even pairs. UNIT-1 and UNIT-2 refer to one
physical device and have logical device names ST1 and DSl respectively. UNIT-5
and UNIT-6 refer to a second physical device and have logical device names DS5
and DS6 respectively.
Space is allocated on logical device DS5 in two-llink allocation units (AU-2).
AU size on all other logical devices defaults to one llink. Use of this field
exemplifies that each logical device is independent of the others and that
parameters can be assigned on an individual logical device basis.
5-54
DH18-03
~
~
1
1
8
6
$
IOX-O
ETC
ETC
ETC
ETC
CH-15,MS0500,UNITS-4,
UNIT-l,ST1,
UNIT-2,DS1,
UNIT-5,DS5,AU-2,
UNIT-6,DS6
$
$
$
$
The next example indicates two physical MSC1B mass storage devices configured
on channel 56 (CH-56) of IMU-2. The UNIT-OO.O and UNIT-OO.l logical device
designators refer to the same physical device and have logical device names MSA
and MSB. The UNIT-01.0 and UNIT-Ol.1 logical device designators refer to the
second physical device and have logical device names MSC and MSD. (Refer to
the GCOS 8 OS System Operating Techniques manual for information about physical
and logical device characteristics for each device type.)
\
)
1
8
1
6
$
$
$
$
$
IMU-2
ETC
ETC
ETC
ETC
CH-56,MSC1B,UNITS-4,
UNIT-OO.O,MSA,
UNIT-01.0,MSC,
UNIT-OO.1,MSB,
UNIT-01.1,MSD
I
The next example indicates two physical devices configured on channel 44
(CH-44) of IMU-O. The logical device designators for one physical device are
UNIT-04.0 and UNIT-04.1, with logical device names of MS4 and MS6,
respectively. The other physical device has only one logical device
designator, UNIT-05, with a logical device name of MS5. Note that this device
is an exception to the attributes defined for the subsystem since it has only
one logical device name for the physical device.
1
1
8
6
$
IMU-O
ETC
ETC
ETC
CH-44,~mC1B,UNITS-3,NONSEQ,
$
$
$
I
UNIT-04.0,MS4,
UNIT-05,MSC1A,MS5,
UNIT-04.1,MS6
The MSU0501, MSC1B, MSD1B, MSM1B, and MSM1E devices are formatted into 512-word
sectors which are transparent to software.
Device assignment and release functions for Startup are on the basis of logical
devices. When one logical device is released the other logical device on the
same spindle may still be assigned (not released). The release/assign
condition of the other logical device should be interrogated using the PSTATS
command. For the PSTATS, ASGN, or RLSE verbs, the following message is output
to indicate the device release/assignment condition:
5-55
DH18-03
I
{ RLSE }
{ ASGN }
DEV icccdd
I
(
MSU0501, MSU3380, MSU3381, and MSS8080 logical devices cannot be exchanged via
the EXCHG console verb or the X response to an Exception Processing message.
MSU0501 logical devices can be mixed with MSU0451 and MSU0500 logical devices
on the same subsystem (subject to the Startup rules for mixed configurations).
$ Iyy STATEMENT FOR MAGNETIC TAPE SUBSYSTEMS
The same basic $ Iyy statement format can be used to define MTS0400/0500,
MTS0600/0610, MTS500, and MTS8200 magnetic tape subsystems. The format for
this $ Iyy statement follows. (If more than one device is defined on a single
$ Iyy statement, the UNIT-u and ddd fields must be repeated for each configured
magnetic tape device within the device type (tttttt field) specified.)
1
1
8
6
$
$
Iyy-m
ETC
{CH-P }
{PUB-p}, tttttt ,aaaa, UNITS-n[ , NONSEQ] ,UNIT-u,ddd [,
zzzzz] [ , CLASS-c] [ ,RESERVED] [ ,DEDICATED] [ ,RLSE]
where:
m
- Number (0-3) of the Iyy to which this magnetic tape subsystem is
connected.
p
- Iyy channel (CH/PUB) number.
IMU
IMX
10M
lOP
lOX
tttttt
Permissable values are:
8-63
0-127
8-31
8-63
0-127
- Device type:
Code
Description
----~-----------------------------
TAPE*500*7
TAPE*500*9
TAPE*500*7
TAPE*500*9
TAPE*600*7
TAPE*600*g
TAPE*610*7
TAPE*610*9
TAPE*FIPS*9
NOTE:
MTS500 seven-track magnetic tape
MTS500 nine-track magnetic tape
MTS0400/0500 seven-track magnetic tape
MTS0400/0500 nine-track magnetiC tape
MTS0600 seven-track magnetic tape
MTs0600 nine-track magnetic tape
MTS0610 seven-track magnetic tape
MTS0610 nine-track magnetic tape
MTS8200 nine track magnetic tape
TAPE*FIPS*9 may not be specified on a $ rOM statement.
5-56
DH18-03
aaaa
- Density code. This code represents the density capabilities of
most of the devices (ddd) that are specified for this device
type (tttttt). Valid density codes are:
Code
Description
ABCD
ABC
BCD
BC
CD
DE
D
E
200, 556, 800, and 1600 bpi
200, 556, and 800 bpi
556, 800, and 1600 bpi
556 and 800 bpi
800 and 1600 bpi
1600 and 6250 bpi
1600 bpi
6250 bpi
For example, i f the UNITS-n field specifies four units are being
defined for this device type and three of the units have density
capabilities of 200, 556, 800, and 1600 bpi, the aaaa field
would contain ABCD.
Exceptions to the entry in the aaaa field (i.e., any device that
has density capabilities that differ from those defined by the
density code) are defined in the zzzzz field.
n
- Number of magnetic tape units on this channel (CH/PUB) for this
device type (tttttt field). (Refer to Table 5-5 for the maximum
number of units that can be specified for each device type.) If
the value n does not equal the combined number of magnetic tape
units defined in the UNIT-u fields, startup aborts. For
example, i f there are three UNIT-u fields, n must be 3
(UNITS-3).
NONSEQ
- The units (devices) defined in the UNIT-u field are not
necessarily in numeric sequence. For example, the devices may
be defined in the sequence UNIT-2, UNIT-3, UNIT-1, and UNIT-4
rather than in the sequence UNIT-1, UNIT-2, UNIT-3, and UNIT-4.
Because magnetic tape handlers are allocated in the same
sequence that devices are defined on $ Iyy statements, the
NONSEQ parameter can be used to influence the order of
allocation.
u
- Unit identification number.
that immediately follows the
this unit number. (Refer to
for each device type.) Note
as a valid unit number.
ddd
- Logical device name. A logical device name comprises three
alphanumeric characters. The first character must be nonzero,
the ~econd character must be alphabetic, and the third character
can be alphabetic or numeric.
)
5-57
The logical device name (ddd field)
UNIT-u field is associated with
Table 5-5 for valid unit numbers
that FIPS devices can have UNIT-O
DH18-03
zzzzz
I
- Magnetic tape characteristics (i.e., tape density and number of
tracks) for individual magnetic tape units that are exceptions
to information specified in the tttttt and aaaa fields. For
each exception device, the zzzzz field must immediately follow
the UNIT-u,ddd fields for the exception device:
UNIT-u,ddd,zzzzz
The last character of the zzzzz field represents the magnetic
tape track type (i.e., 7 or 9). The preceding characters
represent the tape density capabilities. Valid exception codes
are:
Code
Description
ABC7
BC7
ABCD9
BCD9
CD9
DE9
D9
E9
Seven track, 200/556/800 bpi
Seven track, 556/800 bpi
Nine track, 200/556/800/1600 bpi
Nine track, 556/800/1600 bpi
Nine track, 800/1600 bpi
Nine track, 1600/6250 bpi
Nine track, 1600 bpi
Nine track, 6250 bpi
For ease of reference, it is recommended that each exception
device be defined on a separate $ ETC statement.
c
- Allocation class for logical device ddd. This parameter allows\
\
the site to reserve devices for specific uses based on
site-defined considerations. For example, speed and transfer
rate are two device attributes that can be considered when
defining magnetic tape allocation classes. Physical location of
devices also may be a consideration. Valid class codes are:
Code
3
2
1
o
Description
Most preferred
Preferred
Ordinary
J '" J...
f} .J-J _
Subordina te (unclassified) ~~ ~
If no allocation class is specified, class code 0 is assigned by
default.
Based on the site-defined classes, the user programmer can
indicate on the $ TAPE JCL statement which device and/or class
is required for a specific application. (Refer to the GCOS 8 OS
Job Control Language manual for a description of the $ TAPE JCL
statement.)
5-58
DH18-03
c
RESERVED
- The designated tape unit may be allocated only when the
associated class is requested via the $ TAPE JCL statement. If
the class is not specified on the $ TAPE statement, the tape
unit is not allocated.
DEDICATED - This is a dedicated device.
RLSE
- This device is configured and released at Startup.
Table 5-5.
Magnetic Tape Subsystem Parameters
Device Type Code
(tttttt Field)
Maximum Number
of Units
(UNITS-n Field)
Unit Number
(UNIT-v Field)
TAPE*500*7
TAPE*500*9
TAPE*600*7
TAPE*600*9
TAPE*61 0*7
TAPE*61 0*9
TAPE*FIPS*9
16
16
16
16
16
16
17
1-16
1-16
1-16
1-16
1-16
1-16
0-16
NOTE: The device type codes TAPE*500*7 and TAPE*500*9 apply to
seven-track and nine-track MTS500 and MTU0400/0500 devices.
)
The following example indicates that six (UNITS-6) MTU0600 magnetic tape
handlers (TAPE*600*9) are configured on logical channel 16 (CH-16) of IOX-O. A
majority of the six tape units are nine-track (*9) handlers with density
capabilities of 800 bpi and 1600 bpi (CD). All six units are defined on $ ETC
statements. One unit (TB6) is an exception to the attributes defined for the
subsystem (i.e., 800 bpi and 1600 bpi density capabilities and nine-track
handlers). TB6 is a seven-track handler with 200, 556, and 800 bpi density
capabilities (ABC7).
In addition, TB4 is assigned to class 2 (CLASS-2) and will be allocated
(RESERVED) only when that class is specified on the $ TAPE JCL statement.
is dedicated (DEDICATED) and will be allocated only when requested by its
logical device name.
1
8
1
6
$
$
$
$
$
$
$
IOX-O
ETC
ETC
ETC
ETC
ETC
ETC
CH-16,TAPE*600*9,CD,UNITS-6,
UNIT-1,TB1,
UNIT-2,TB2,
UNIT-3,TB3,
UNIT-4,TB4,CLASS-2,RESERVED,
UNIT-5,TB5,DEDICATED,
UNIT-6,TB6,ABC7
TB5
~
J
5-59
DH18-03
An equivalent set of Startup statements can be used on a system using any of
the other input/output controller types.
The next example indicates that six units (UNITS-6) of Ml'S8200 magnetic tape
handlers (TAPE*FIPS*9) are configured on channel 40 (CH-40) of IMU-1. All
units are defined on a separate $ ETC statement for clarity. UNIT-2 is an
exception to the attributes defined for the subsystem since it has a density
capability of 800/1600 bpi.
1
1
8
6
$
IMU-1
ETC
ETC
ETC
ETC
ETC
ETC
CH-40,TAPE*FIPS*9,DE,UNITS-6,NONSEQ,
UNIT-O,FO,
UNIT-1, 1F1,
UNIT-2,CD9,1F2,
UNIT-8,1F8,
UNIT-9,1F9,
UNIT-10,1FA
$
$
$
$
$
$
5-60
DH18-03
(
r;;yy
~'I
,;
STATEMENT FOR PRINTERS)
The following statement format is used to specify a printer. Note that printer
belt and vertical format control (VFC) image files must be created and
initialized via a $ FILDEF statement in the $EDIT section of the Startup job
stream for all printers except the PRU1100. Only one 'printer is permitted per
logical Iyy channel (i.e., per $ 1yy statement).
The format for the $ Iyy statements for defining printers is:
1
1
8
$
lyy-m
ETC
$
6
{CH-p }
{PUB-p},tttttt,UNITS-1,UNIT-1,
TRAIN-nnnn,ccc,ddd[,DEDICATED][,RLSE]
where:
m
- Number (0-3) of the Iyy to which this printer subsystem is
connected.
p
- lyy channel (CH/PUB) number.
IMU
IMX
10M
lOP
lOX
)
tttttt
Permissible values are:
8-63
0-127
8-31
8-63
0-127
- Device type:
Code
Description
DPS 8
DPS 8000
DPS 88
DPS 90
PR1100
PR0901
PR0901
PR1100
PR0901
PR0901
PR1100
PR0901
PR0901
NIA
NIA
NIA
PR1200
PR1201
PR1201
PR1200
PR1201
PR1201
PR1200
PR1201
PR1201
NIA
NIA
NIA
NIA
NIA
PR1600
PR1600
PR1600
PR1600
PR1600
NIA
NIA
NIA
PR1200
PR1200
PRU1100
PRU0901
PRU0903
PRU0908
PRU1200
PRU1201
PRU1203
PRU1208
PRU1600
printer
printer
printer
printer
printer
printer
printer
printer
printer
NOTE: On a DPS 88, the configuration of the PRU0901, PRU1201,
PRU0903, or PRU1203 may require an upgrade to the lOX for
this capability. Contact your Honeywell Bull
representative for more details concerning this upgrade.
UNITS-1
- Number of printers on this channel (CH/PUB) for this device type
(tttttt). (Only one printer can be configured on each channel.)
5-61
DH18-03
UNIT-1
- Unit identification number.
nnnn
-Printer belt code. The printer belt number is imprinted in
decimal on the carriage and ~ust be converted to octal for this
field. This field does not apply to PRU1100 printers. Valid
codes are:
Code
Description
1130
Standard ASCII printer belt
Standard BCD printer belt
·764
ccc
(
- Print line width. This field does not apply to PRU1100
printers. Valid entries in this field are:
136 - Standard 136-character print line
160 - Extended print line of 160 characters
ddd
- Logical device name. A logical device name comprises three
alphanumeric characters. The first character must be nonzero,
the second character must be alphabetic, and the third character
can be alphabetic or numeric.
DEDICATED - This is a dedicated device. The Startup program prints only on
a printer that is not dedicated. If output is desired during
System Startup, there must be at least one printer which is not
dedicated.
RLSE
~$ Iff
This device is configured and released at Startup.
STATEMENT FOR FRONT-END
PR~CESSORSJ
There are two methods of communicating with a DATANET 8 Front-End Processor
running DNS. The first of these, called FEP Gateway (DNET/ROUT mode), is an
interrupt driven interface using traditional GeOS remote communication
protocol. The second method is standard DSA Common Exchange Interface (eXI), a
,time driven queued interface used only for native mode Geos 8 communications.
There are three-different $ Iyy formats to configure the DATANET 8 Front-End
Processor, one for each of the above methods and one for a combination of both.
Network Prooessor Using FEP Gateway (DHET/ROUT Mode)
The $ Iyy statement defines the configuration of aDATANET Network Processor
for DNET/ROUT mode on a logical channel of an input/output controller. Only
one DATANET Processor can be defined per logioal input/output controller
channel (i.e., per $ Iyy statement). The format for the $ Iyy statement which
defines a DATANETProcessor for DNET/ROUT mode is:
c
5-62
DH18-03
~
1
1
8
$
lyy-m
v
6
{PUB-p},tttt-n,LlNES-xxx
{CH-p }
where:
m
p
Number (0-3) of the Iyy to which the DATANET Processor is connected.
- lyy channel (CH/PUB) number.
IMU
Permissible values are:
8-63
0-127
8-31
8-63
0-127
I~~
10M
lOP
lOX
tttt - DATANET Network Processor identification (i.e., 6616, 6624, 6632,
6670, FNP)
\
n
- DATANET Network Processor number. Processors must be sequentially
numbered. The value of the processor number can range from 0-7.
xxx
- Maximum number of lines (i.e., terminals) configured on DATANET
Network Processor tttt that can be connected to the central system at
the same time. Only the number of lines specified in this field are
available, even though additional lines may be configured. This is a
required field.
I
J
If multiple $ Iyy statements are used to define several DATANET Processors, the
statements must be in processor number sequence (i.e., the $ Iyy statement for
DATANET Processor 1 must precede the $ Iyy statement for DATANET processor 2).
If the statements are not in the correct sequence, the console message:
*CARD BELOW IS OUT OF ORDER
is issued and Startup aborts. This message is immediately followed by an image
of the statement out of sequence.
The following example indicates that one DATANET 6616 Network Processor
(DNET/ROUT interface) is configured on channel 24 (CH-24) of IOM-1. The
configured processor is processor number O. A maximum of 50 terminals
(LINES-50) can be connected to the central system.
1
1
8
6
$
IOM-1
CH-24,6616-0,LINES-50
An equivalent statement can be used for a system configured with lMUs, IMXs,
lOPs, or lOIs.
5-63
DH18-03
DSA Common Exchange Interface (CII Mode)
The DATANET 8 Network Processor in Common Exchange Interface (CXI) mode must be
configured on an Input/Output Controller Direct Interface Adapter (DIA) port
under a device type of UNCP. This configuration is reflected in the following
$ Iyy statement in the GCOS 8 Startup job stream:
(
1
186
$
Iyy-m
{CH-p }
{PUB-p},tttt,ddd
where:
m
p
Number of the Iyy serving the DATANET 8 processor
- Iyy channel (CH/PUB) number.
IMU
IMX
10M
8-63
0-127
8-31
lOP
lOX
Permissible values are:
8-63
0-127
tttt - Device type
UNCP - DATANET 8 network processor
SSF - System Support Facility
ddd
Logical device name. A logical device name comprises three
alphanumeric characters. The ~irst character must be nonzero, the
second character must be alphabetic, and the third character can be
alphabetic or numeric. Recommended names are FEO, FE1, FE2, ••• , FE9,
FEA, FEB, ••• , FEF.
The logical device names- FEO, FE1, FE2, FE3, FE~, FE5, FE6, FE7, FEB, FE9, FEA,
FEB, FEC, FED, FEE, and FEF and the default values for eXI communications are
defined in the standard workstation definition data base (WO) file in the
SYS SOFTWARE structure. If other names or values are' used, the site
administrator must make the appropriate changes in the WD file. New names must
be chosen using the device naming conventions discussed under the input/output
controller statements earlier in this section.
Note that Network Processors for CXI mode must be configured independently of
Network Processors for DNET/ROUT mode. The GCOS 8 Startup process sees the
following differences between the configurations:
o Device types for the two modes are different, even when the physical
device is the same. For eXI mode, the device type is UNCP and the
following field of the configuration statement contains the Network
Processor name (e.g., FEn, where n = 0 - F). For DNET/ROUT mode, the
device type is 66xx-n, where xx is the specific device type and n is the
device number in the configuration.
5-64
DH18-03
(
o Network Processors for eXI mode must be numbered starting from device 0
(e.g., FED, FE1, ••. FE9 ,FEA ,FEB, ••• FEF) and need not be in any
particular number sequence. Network Processors for DNET/ROUT mode must
be numbered sequentially (e.g., 6670-0 - 6670-7) and must be defined in
processor number order in the $CONFIG 'section of the Startup job stream.
While the configuration statements may be inter-mingled in the startup job
stream, the two numbering sequences must not be mixed.
o Network Processors for eXI mode are not included in the FNP count on the
$ INFO FNP/n statement in the Startup job stream. The n value must
include only the Network Processor configured for DNET/ROUT mode.
o Mailbox address switches for all Network Processors in CXI mode are BF8
(hexadecimal). Mailbox addresses for Network Processors in DNET/ROUT
mode are based on input/output controller mailbox addresses and vary with
the number of input/output controllers and Network Processors in the
configuration.
For example, if location 3000 (octal) defines the beginning of the
mailbox area for the (first and) last input/output controller configured,
the mailbox area for the first DATANET Processor (Processor 0) begins at
location 5400 (octal). The mailbox area for each additional DATANET
processor is obtained by incrementing the mailbox address of the
predecing DATANET Processor by 100 (octal).
The need to change mailbox address switches when splitting a large system
configuration into two smaller configurations can be avoided by using the
$ BASE statement.
$ lOX Statement For DPS 88 System Support Facility
The DPS 88 System Support Facility is configured as a DATANET 8 Network
Processor in Common Exchange Interface (CXI) mode. Refer to "DSA Common
Exchange Interface (eXI Mode)" above, for the definition of the Startup job
stream statement to configure the System Support Facility.
Both DIET/ROUT Mode And eXI Mode
This format is used for a DATANET 8 processor that is used for both DNET/ROUT
mode and CXI mode over the same input/output controller channel. The format is
as follows:
1
186
$
Iyy-m
{CH-p }
{PUB-p},DDIA-n,ddd,LINES-xxx
5-65
DH18-03
where:
m
p
Number (0-3) of the Iyy to which -the DATANET processor is connected.
- Iyy channel (CH/PUB) number.
I.,IU
IMX
n
Permissible values are:
8-63
0-127
101-1
B-31
lOP
lOX
8-63
- 0-127
- DATANET processor number. n must be sequentially consistent
(0,1,2,3, ••• ) with all other DATANET processors that use DNET/ROUT
mode (including On-Line PPSs)
ddd - Logical device name. A logical device name comprises three
alphanumeric characters. The first character must be nonzero, the
second character must be alphabetic, and the third charaoter can be
alphabetic or numeric. Recommended names are FEO, FE1, FE2, ••• , FE9,
FEA, FEB, ••• , FEF
xxx - Maximum number of lines that can be connected at the same time on this
DATANET processor. This is a required parameter for this format. It
has significance in the DNET/ROUT mode but not in the CXI mode.
The logical device names FEO, FE1, FE2, FE3, FE4, FE5, FE6, FE7, FEB, FE9, FEA,
FEB, FEC, FED, FEE, and FEF and the default values for CXI communications are
defined in the standard workstation definition data base (WO) file in the
SYS SOFTWARE structure. If other names or values are used, the site
administrator must make the appropriate changes in the WD file. New names must
be chosen using the device naming conventions discussed under the input/output
controller statements earlier in this section.
The following example illustrates the configuration of a DATANET B processor
with the capability of using both DNET/ROUT mode and eXI mode over the same
channel.
1
$
B
6
IOP-O
PUB-53,DDIA-0,FEO,LINES-200
This is functionally equivalent to the following example, which requires the
DATANET 8 processor to be physically connected to two channels.
1
1
8
6
$
$
IOP-O
IOP-O
PUB-53,UNCP,FEO
PUB-54,6632-0,LINES-200
5-66
DH18-03
~
Page Processing System
r'
A Page Processing System directly connected to an Iyy is specified to the
Startup program via a $ Iyy statement. The format is:
1
8
$
6
Iyy-m
{PUB-p},PPS*FEP-n,LINES-1
{CH-p }
where:
m
- Number (0-3) of the Iyy to which the Page Processing System is
connected.
p
- Iyy channel number (CH/PUB).
PPS*FEP - PPS device type code.
n
- Network Processor number.
LINES-1 - Number of lines which may be connected to the PPS.
always 1.
;
I
This value is
The PPS is configured as a network processor (for DNET/ROUT mode), and the
parameters required are analogous to those used to configure a DATANET Network
Processor (for DNET/ROUT mode). The network processor number must be
sequentially consistent (e.g., 0,1,2, ••• ) with other PPSs and DATANET
Processors (for DNET/ROUT mode) included in the system configuration.
A Page Processing System which is connected remotely to a DATANET Processor
does not require this statement.
Examples Of Front-End Processor Configuration Formats
1
$
$
$
$
$
$
$
8
6
BASE
INFO
10X-O
IOX-O
10X-O
10X-O
IOX-O
IOX-2,DN-3
FNP/3
PUB-60,SSF,FEO
PUB-61,UNCP,FE1
PUB-62,DDIA-0,FE2,LINES-100
PUB-63,6632-1,L1NES-50
PUB-64,PPS*FEP-2,LlNES-1
--------------------------------------------SYSTEM SUPPORT FACILITY
CXI MODE
eXI & DNET/ROUT
DNET/ROUT MODE
ON-LINE PPS
NOTES: 1. With the $ BASE statement included, the $ INFO FNP statement is
redundant; however, if the statements do not agree on the number
of FNPs, Startup will use the larger of the two numbers.
5-67
DH18-03
2. The number of FNPs in the $ INFO FNP/n statement and the $ BASE
statement includes only the FNPs that use DNET/ROUT mode, PUBs 62,
63, and 64.
3. The devices on the three CXI mode channels are assigned logical
device names FEO, FE1, and FE2. Although the $ lOX statements
were presented in logical device name sequence in this example, no
particular sequence is required for CXI mode.
4. The Network Processor number for DNET/ROUT mode device types are
sequentially numbered 0, 1, and 2. It is required that statements
be presented in that sequence for DNET/ROUT mode.
$ Iyy STATEMENT FOR HYPERCHANNEL COMMUNICATIONS ADAPTER
One $ Iyy statement is required per HYPERchannel (HYPERchannel is a trademark
of the Network Systems Corporation) adapter to define the primary channel for
the device. Additional logical channels on the same Peripheral Subsystem
Interface Adapter (PSIA) may be used and are defined via a $ XBAR statement. A
logical device should be defined for each use of the physical adapter by
different communications protocols (e.g., DSA, MASSNET). The logical device,
in conjunction with the HYPER channel adapter logical device capabilities,
separates I/O using the HYPERchannel into "logical streams" containing
different protocols. The format for these $ Iyy statements is shown below.
1
8
$
6
Iyy-m
{CH-p }
{PUB-p},HYPER,UNITS-n,UNIT-u,ddd[,DEDICATED][,RLSE]
where:
m
p
Number (0-3) of the Iyy to which this HYPERchannel adapter is
connected.
- Iyy channel (CH/PUB) number.
ItvlU
8-63
IMX
0-127
ION
lOP'
lOX
8-63
0-127
Permissible values are:
8-31
HYPER
- HYPERchannel device type.
n
- Number of logical devices on this channel (CH/PUB) for this
HYPERchannel adapter. If value 11 does not equal the number of
logical devices defined in the UNIT~u fields, Startup 'aborts.
5-68
DH18-03
(
u
- Logical device identification number. The logical device name
(ddd field) that immediately follows the UNIT-u field is
associated with this device number.
ddd
- Logical device name. A logical device .name comprises three
alphanumeric characters. The first character must be nonzero,
the second character must be alphabetic, and the third character
can be alphabetic or numeric.
DEDICATED - Specifies a dedicated device.
RLSE
- Specifies a device that is configured and released at Startup.
$ Iyy STATEMENT FOR DATABASE COMPUTER
The $ Iyy statement defines the configuration of channels between the main
frame and the database computer. A database computer includes two or more
Interface Processors (IFPs), each of which is configured as two devices (one
for input, the other for output).
A maximum of eight IFPs, or 16 devices, can be configured per physical channel.
A separate $ Iyy statement is required for each physical channel. If there are
multiple physical channels, they may be connected to one or more input/output
controllers.
The format for the $ Iyy statement defining database computer connections is:
1
1
8
$
$
$
Iyy-m
ETC
ETC
ETC
$
6
{PUB-p}
{CH-p },DBC,UNITS-n,
UNIT-O,ddd,
UNIT-1 ,ddd, •••
UNIT-n-1 ,ddd
I
where:
m
- Number (0-3) of the Iyy to which the channel is connected.
p
- Iyy channel (CH/PUB) number of the first of the four logical channels
assigned to the FlPS channel connected to the database computer.
Permissible values are:
lMU
lMX
10M
lOP
lOX
DBC
8-63
0-127
8-31
8-63
'0-127
- Symbol for database channel
5-69
DH18-03
I
n
- Number of devices (twice the number of IFPs configured on this
channel)
ddd
- Logical device name. A logical device name comprises three
alphanumeric characters. The first character must be nonzero, the
second character must be alphabetic, and the third character can be
alphabetic or numeric. These may be DBO, DB1, ••• , DB9, DBA, ••• ,
DBF corresponding to UNIT-O, ••• , UNIT-15, respectively.
I
I
I
A separate UNIT-u phrase is provided for each of the n devices configured on
the channel. Each phrase gives the name for that device. One or more $ ETC
statements may be used to contain these phrases. Only unit numbers from 0
through 15 may be used. Unit numbers must appear in pairs. The first number
in each pair must be even, and the second number in each pair must be one
greater than the first. Numbering must start with zero.
Each physical channel is usually configured with two or four logical channels.
To indicate logical channel usage, a $ XBAR statement is required. See "$ XBAR
Statement", later in this section. A $ GROUP statement must be used to show
that the logical channels can be used interchangeably. See "$ GROUP
Statement", earlier in this section.
In the following example, two physical channels are connected to the database
computer, and each is connected to four IFPs or eight devices. Four logical
channels are provided for each physical channel.
1
1
8
6
$
10X-O
ETC
ETC
XBAR
GROUP
IOX-O
ETC
ETC
XBAR
GROUP
CH-12,DBC,UNITS-8,
UNIT-O ,DBO, UNIT-1 ,DB1 , UNIT-2 ,DB2, UNIT-3 ,DB3,
UNIT-4,DB4,UNIT-5,DB5,UNIT-6,DB6,UNIT-7,DB7
10X-O,CH-12,CH-13,CH-14,CH-15
IOX-O,CH-12-15
CH-16,DBC,UNITS-8,
UNIT-O,DB8,UN1T-1,DB9,UNIT-2,DBA,UNIT-3,DBB,
UNIT-4,DBC,UNIT-5,DBD,UNIT-6,DBE,UNIT-7,DBF
IOX-O,CH-16,CH-17,CH-18,CH-19
IOX-O,CH-16-19
$
$
$
$
$
$
$
$
$
CIYY
-------------~----.------~----------------~
STATEMENT FOR CARD READERS AllD CARn PUNCHES
The same basic $'Iyy statement format can be used to define card readers and
card punches. Only one device can be defined per logical Iyy channel (i.e.,
per $ Iyy statement). The format for the $ Iyy statement defining card readers
and card punches is:
1
8
$
Iyy-m
1
6
{CH-p }
{PUB-p},tttttt,UNITS-1,UNIT-1,ddd[,DEDICATED][,510PT][,RLSE]
5-70
DH18-03
- Iyy channel (CH/PUB) number.
p
Permissible values are:
IMU ,8-63
IMX
0-127
10M
8-31
lOP
8-63
lOX
0-127
- Device type:
tttttt
Code
Description
READER·MPC31
CC0401
CR0501
CR1050
PUNCH·200
PUNCH·300
PUNCH*MPC30
PC0120
PC0121
PC0300
CRU1050 card reader
CCU0401 card reader/card punch
CRU0501 card reader
CRU1050 card reader
CPZ201 card punch
CPZ300 card punch
CPZ300 or PCU0120/0121 card punch
PCU0120 card punch
PCU0121 card punch
CPZ300 card punch
- Number of card readers or card punches on this channel (CH/PUB)
for this device type (tttttt). (Only one card reader or card
punch can be configured on each channel.)
UNITS-1
UNlT-l
Unit identification number.
I
/
- Logical device name.
ddd
DEDICATED
510PT
This is a dedicated device.
- This parameter applies only to CRU1050 card readers and
indicates that the device defined in the logical device name
(ddd) field has the capability of reading 51-column cards.
RLSE
This device is configured and released at Startup.
The following example defines one CRU1050 card reader (CR1050) with a logical
device name of CR1. The device is configured on logical channel 10 (CH-l0) of
Iyy-O. This device can read 51-column cards (510PT) and is dedicated
(DEDICATED) to programs that request the device by its logical device name.
1
1
8
6
$
lyy-O
CH-l0,CR1050,CR1,510PT,DEDICATED
5-71
DH18-03
$ LOADFIL Statement
The $ LOADFIL statement defines the mass storage device and the file onto which
the tLO~~ s~~t?-oP~~$2,t:",tlh.~, [t~it~~:diSih:::itiiiiii:li . :ID:l?&::iit~t5. "~(~ne ~mtou* ...
sec€~on contains modules in object deck format that are to be loaded into main
memory.) A response of AUTO or REPL to the Startup message *BOOT SOURCE: AUTO
OR REPL? during the bootload sequence results in the $LOAD section being read
from the mass storage file (as opposed to loading the section from punched
cards or magnetic tape).
.
The format for the $ LOADFIL statement is:
1
6
1
8
$
LOADFIL ddd,fffff,sss
where:
ddd
- Logical device name of the mass storage device on which a file is
created to contain the $LOAD section of the Startup job stream.
fffff - Name of the load file (maximum of 12 characters) to which the $LOAD
section is to be written. The file name cannot contain an embedded
hyphen (" -") •
sss
- Size (in llinks) of the load file. There is no default size;
therefore, this field must be defined.
The following example indicates that file LOADFILE is to be allocated 500
llinks of space on mass storage device DS2.
1
6
1
8
$
LOADFIL DS2,LOADFILE,500
$ MCT Statement
The $ MCT statement d,~fin~,s. ~hero P~;:Y~~7~1 uC}~,~i\,ib~~~ll,,,,,1h~,,:k~~ory size and port
c2!1nect!.g!l-sJ~eaQ1L~.x§.tell'k~.C'p.JltJ:91-Jn!Lt~S!!"t for DPS S and l)~O'sySt'ems~:"'"'"O><~'"
~ee "$ CIU Statement", earlier in this section for DPS 88 and DPS 8000.
This
statement must precede all $ Iyy statements.
Below is the format for the $ MCT statement. The optional fields (i.e., those
enclosed in brackets) can be repeated to define a maximum of eight SCU port
connections.
1
1
8
6
$
MCT-n
ssss[,PORT-p,mmmmm/OFF]
5-72
DH18-03
c
where:
n
- SCU number.
ssss
- Memory size of this SCU. This value is specified as the number of
1K (1024 words) blocks. For DPS 90 the entire SCU configuration
should be described on one $ MCT statement.
p
- SCU port number (0-7).
mmmmm - Type code of the hardware module that is connected to the specified
SCU port (p). The following codes are valid:
Code
Module
------------------------------------------------
Iyy-x
Input/output controller (IMU/IOM/IOP) number x
PRO-x
Physical processor number x (x=0-5) (DPS 8 only)
EPU-x
Physical processor number x (x=0-3) (DPS 90 only)
NOTES: 1. Whichever device is configured here must be used
throughout the Startup job stream or an error message
will be displayed.
2. Refer to the "$ CIU Statement", earlier in this
section, for DPS 88 and DPS 8000 systems.
3. In a DPS 8 system with a mixture of 10M and IMU
input/output controllers, the input/output controller
number must be unique among both controller types
(i.e., specifying IMU-O and IOM-O is not valid).
/OFF
- Defines the processor not currently assigned, but which may be
assigned (activated) in the future. (Refer to "Processor Release
And Assignment At Startup" in Section 3 for additional information.)
The following example defines two ports (0 and 1) on SCU 0, which has a memory
size of 1024K. Processor 0 is connected to port O. rOM 0 is connected to
port 1.
1
1
8
6
$
MCT-O
1024,PORT-1,IOM-0,PORT-0,PRO-0
The minimum memory size,reguired to support GCOS 8 is 4MB •• If less than this
amount is specified, Startup will issue the following error message and abort:
GCOS-B REQUIRES AT LEAST 1024K OF MEMORY
:;\
5-73
DH18-03
DPS 90 CONSIDERATIONS
Figure 5-1 shows the hardware (physical) port assignments for a DPS 90 system.
EPU-O
I
I EPU-1
I
I
EPU-2
--.--
I
I EPU-3
I
I
-I-
•I
I
I
--'----:--"- ,~•
PO
-I'
P2
P1
SCU-O
P3
SCU-1
P4
P6
P5
P7
I
I
__
II
I
I IOP-1 I
I--.--
I
••
--I
I
I IOP-O I
I----
IOP-2
Figure 5-1.
IOP-3
DPS 90 Hardware Port Assignments
Only one $ MCT statement should be used, even though two SCUs are physically
present. The port assignments on the $ MCT statement must be made as shown
under the appropriate columnar heading for "TWO SCUs" or "ONE SCUll.
Port-O
Port-1
Port-2
Port-3
Port-4
Port-5
Port-6
Port-7
TWO
SCUs
-.
ONE
SCU
EPU-O
EPU-1
EPU-2
EPU-3
IOP-O
IOP-1
IOP-2
IOP-3
EPU-O
EPU-1
IOP-O
IOP-1
In order to avoid configuring more memory than is available, the entire SCU
configuration should be described on a single $ MCT statement (with appropriate
$ ETC statements).
5-74
DH18-03
(
Example 1
The logical EPU/IOP number is derived from the $ MCT
system the logical EPU/IOP number can be the same as
number. The following control statements define the
configuration available on a two-SCU system (i.e., 4
statement. For a dual SCU
the physical EPU/IOP
maximum DPS 90
EPUs and 4 lOPs):
1
1
8
6
$
$
MCT-O
ETC
ssss,PORT-O,EPU-O,PORT-1,EPU-1,PORT-2,EPU-2,PORT-3,EPU-3,
PORT-4, IOP-O, PORT-5 ,IOP-1 , PORT-6, lOP-2,PORT-7 ,IOP-3
where:
ssss - The total amount of memory configured to the system.
Example 2
However, on a single SCU, dual rop, dual EPU system, the logical EPU/IOP
numbers cannot be the same as the physical EPU/IOP numbers. In this case the
following control statement should be used to define the configuration:
1
1
8
6
$
MCT-O
ssss,PORT-O,EPU-O,PORT-2,EPU-1,PORT-4,IOP-O,PORT-5,IOP-1
where:
ssss - The total amount of memory configured to the system.
In example 2, physical rop number 2 is logical lOP number 1, and physical EPU
number 2 is logical EPU number 1. It should also be noted in this example that
logical IOP-1 is defined oh PORT-5, even though PORT-5 is not physically
present on a single SCU system. This is due to the fact that the port numbers
specified on the $ MCT statement for IOPs are used in the following manner:
For every logical lOP defined in the IOPMPS configuration, MSOS builds a
connect table entry in Reserved Memory Space (RMS). If two logical IOPs are
defined, then two connect entries will be built. These entries contain the
true seu port number to which the lOPs are connected. The port number
specified on the $ MCT statement is used as an index into the RMS connect
table as follows:
connect table index
= MCT
port number -4
(The first entry in the table is accessed with an index of zero.)
So, in example 2, lOP-1 is defined on PORT-5 on the $ MCT statement in order to
obtain the correct index value of 1. The connect table entry at position 1
will contain the true SCU port number of 6.
)
5-75
DH18-03
$ MPC Statement
The $ MPC statement defines each_confi ured
Control~er (MPC), URP0600 Unit Record Processor, or
parameter, MPC is use
or eJ. er an .
URP0600, or PPU. Definition of the PSI logical channel includes identifying
each associated input/output controller (i.e., iMU/IMX/IOM/IOP/IOX) and each
logical channel (CH) on the input/output controller.
The format for the $ MPC statement is:
1
1
8
6
$
MPC-m
parameter-1,parameter-2, ••• ,parameter-n
where:
m - MPC number (0-63). Each configured MPC must be assigned a logical
number and defined via the $ MPC statement. If an MPC is not defined on
this statement, the Startup program aborts or the MPC and its associated
PSI configuration is ignored.
The following parameters can be included on the $ MPC statement(s):
$ MPC Parameter
Description
SIZE-s
The value s (default s = 4) specifies the size of the MPC
read/write memory in 1K (1024 words) blocks. The value may
be:
l-lPC
PPU
PPU
TAPE·URC
4
4 (TAPE)
16 (DISK)
Required only when a magnetic tape-unit record MPC is
configured.
PSI logical channel number (0-3). The PSI that is used to
bootload the MPC must be the first defined on the $ MPC
statement. Thereafter, PSIs can be defined in any sequence
(e.g., 0, 1, 3, 2).
SDB
The SDB (shared data base) parameter indicates that this PSI
is being shared with NPS. This option is required to
prevent Startup from bootloading the MPC firmware each time
the system is bootloaded.
5-76
DH18-03
$ MPC Parameter
Description
BOOT
The use of the BOOT parameter following the PSI-p parameter
allows the site to specify an alternate PSI logical channel
over which bootloading can be perfqrmed. If BOOT is
specified, the MPC Bootload program (MPCB) determines which
PSI channel to use as the primary PSI channel, and which to
use as the alternate channel. The MPCB program is not
supported on the DPS 88 and DPS go systems. The following
example specifies that bootloading should occur over PSI
logical channel 0 (primary) or PSI logical channel 1
(alternate).
1
1
8
6
$
$
MPC-O
ETC
SIZE-4,PSI-0,IOM-0,CH-8,IOM-0,CH-9,
PSI-1,IOM-1,BOOT,CH-10,CH-11
It is recommended that the BOOT parameter be used only with
MTS0610 magnetic tape sUbsystems. If BOOT is specified for
any other subsystem, bootloading problems may occur.
PORT-u
Unit record MPC controller port number associated with the
preceding channel number. Port and channel numbers are
assigned on a one-to-one basis. Startup assigns port
numbers by default (1) if they are not specified on the
$ MPC statement; or (2) if they are not specified
sequentially beginning with PORT-O. Port numbers are not
applicable on the DPS 88 system. On TAPE.URe controllers
only ports 4-7 may be used, if specified.
Iyy-i
(Iyy = IMU, IMX, 10M, lOP, or lOX). The value assigned to i
ranges from 0 to 3 and corresponds to the Iyy to which the
PSI is connected.
CH-c
Base Iyy channel (CH/PUB) number.
The base channel number is the lowest channel number in a
particular application. Due to a hardware requirement, the
base channel number must be defined with a modulo 2, 4, or 8
value, as follows:
Number of Channels
In Application
1
2
3-4
-5-8
Legal Base
Channel Numbers
8 to 31
8,10,12,14,16,18,20,22,24,26,
28, 30
8 , 12, 16, 20, 24, 28 •••
8, 16, 24 •••
5-77
DH18-03
$ MPC Parameter
De~cription
----_._----------------
Logical channels for unit record MPCs must be sequentially
defined in one-digit increments (e.g., 8, 9, 10 and not 8,
10, 12). Each Iyy channel number that is included on a
$ Iyy statement must be defined on $ MPC statements.
Permissible values are:
IHU
IMX
10M
lOP
lOX
8-63
0-127
8-31
8-63
0-127
The following briefly depicts the hierarchical structure that must be defined
on $ MPC statements and associated $ ETC statements:
Defines the first MPC configured. After all subordinate
PSI-p, Iyy-i, and CH-n have been defined, this is followed
by other lofFCs.
MPC-m
PSI-p
Iyy-i
CH-n
Defines the first PSI to which this MPC is connected. After
all subordinate Iyy-i and CH-n have been defined, this is
followed by other PSIs on this same MPC.
Defines the input/output controller to which this PSI is
connected.
Defines the lowest logical channel number on the input/
output controller to which this PSI is connected, followed
in numerical order by other logical channel numbers on the
input/output controller to which this PSI is connected.
This sequence is repeated until (1) all logical channels (CHs) are defined for
the input/output controller, (2) the input/output controller is defined for its
corresponding PSI, (3) all PSIs are defined for the MPC, and (4) all configured
MPCs are defined. The MPCs can be defined in any sequence; however, for ease
of reference, they should be defined sequentially.
EXAMPLES
MPC
Examples
The following example defines three PSI logical channels (0-2) on MPC-O, which
has 4K of read/write memory. PSI-O is connected to Iyy-O, which has four
logical channels (CH-8 through CH-11). PSI-1 is shared (SDB) with NPS. PSI-2
is connected to four logical channels (CH-16 through CH-19) on Iyy-1.
5-78
DH18-03
1
8
1
6
$
$
MPC-O
ETC
SIZE-4,PSI-O,Iyy-O,CH-8,CH-9,CH-10,CH-11,
PSI-1,SDB,PSI-2,IYY-1,CH-16,CH-17,CH-18,CH-19
PPU Example
The following example defines two PPU logical channels (0 and 3) on MPC-1,
which has 16K of memory. PSI-O is connected to Iyy-O, channels 14 and 15.
PSI-3 is connected to Iyy-1, channels 42 and 43.
1
1
8
6
$
MPC-1
SIZE-16,PSI-O,Iyy-0,PUB-14,PUB-15,PSI-3,Iyy-1,PUB-42,PUB-43
$ MPCFIG Statement
)
The $ MPCFIG statement permits identification of the firmware revision level to
bootload to a specific Microprogrammable Per'iph;ral CoritrorreI""«'tRPC1':-i~rs'-"~'
~fif'orm~rtroil'=!s~·wri'ft·en"'lo~""'t:t't~tbre"·!·ort·the";'''aErckfire"~'''''''''~i'f-'a''''fIrmware''''~~vi sion
level is not specified for an MPC, startup bootloads the MPC with the first
firmware that it encounters on the deckfile. To ensure that all MPCs are
bootloaded with the correct firmware, it is recommended that a $ MPCFIG
statement be included for each configured MPC.
It is required that only one logical channel be defined per $ MPCFIG
statement. If multiple $ MPCFIG statements are required, it is recommended
that the statements be grouped at the end of the $CONFIG section to facilitate
scanning by the MPC Bootload (MPCB) program.
The format for the $ MPCFIG statement is:
1
$
8
6
MPCFIG
icc,pppp,REV.rr[,U-nndnn]
where:
i-Input/output controller number (0-3).
cc
- Logical channel number that is used to bootload the MPC.
pppp - Four-character object deck (program) identification from columns
73-76 of the $ OBJECT statement in the firmware deck.
rr
- Two-character revision level from columns 71 and 72 of the $ DKEND
'statement in the firmware deck.
5-79
DH18-03
I
nn
- Device codes. These codes are used in conjunction with Microcoded
Device Routines (MORs) for precise definition of the devices for
which MDRs are to be executed. It is recommended that the site's
Customer Services Division (CSD) representative be consulted when
defining the parameters in this field. Depending upon the device,
the following codes apply:
00
- All devices are affected
01-32 - Mass storage or magnetic tape devices
00-07 - Controller ports (or devices) for unit record MPC
01-08 - Same as 00-07
01-02 - Link Adapter or Controller Adapter 0 and 1, respectively
d
- Delimiters for the nn field
Blank
- End of field
Comma (,)
- Continuation of the field (e.g., 01, 03)
Hyphen (-) - Separates a string of devices (e.g., 01-03)
The following example indicates that the MPC connected to Iyy-O and to logical
channel 16 is to be bootloaded with revision E1 of firmware deck M601.
1
1
8
6
$
MPCFIG
016,M601,REV.El
------_._--------_._--_._-------------
$ SECURE Statement
The GCOS 8 Multi-Level Security Manager (Security) R£PYso~g~"%L.s~,veral J e¥el~t.Q.f
system security. A site may choose the options which provide the level of
security required. The $_~ECURlt st'!tem~.nt _i~ u~ed'¥~.iL.~Qe.cj.f'.¥,_wb,!,~llom,§~,9~~y
options are to be actTv'8:ted. The format for 'tne $- SECURE statement is:
......,. .,._---.
n-~~_oc-~.~r!lillll711'fi111111_AM-4iII_
1
1
8
6
$
SECURE
[option[ -arg] ••• [;option[ -arg] ••• ] ••• ]
The valid options and their respective valid arguments are:
5-80
DH18-03
ACCESS -TRYS n 1
-COM a1
The ACCESS option activates the security authentication process,
which requires the user to specify a valid userid and password for
all remote system accesses. The ACCESS option also allows the system
console operator to use the SECUR console verb to manually lock out a
registered userid. The effect of the ACCESS option is modified by
the PID option and the ALL option.
SCC
-TRYS n1
-COM a 1
The SCC option turns on the ACCESS option and, in addition, allows
classi.ficati.on of userids and files by means of Security"
~lassificatiQn . . ~de§ 'S~~sLr so that access to riles can be limited
cased on the SCC. The SCC option also activates security breach
processing, so that occurrence of a security breach locks the use rid
out of the system. The effect of the SCC option is modified by the
PID option and the ALL option.
SYSTEM -TRYS n1
-COM a1
-MINLVL x
-MAXLVL y
The SYSTEM option turns on the ACCESS and SCC options, and also
~~~!i~e;o;h~f~:x{~e~t~~~~~
seaafCrtY1:evera~rOWed to access the system, and can be specified to
disallow non-classified users and work units. The maximum security
level defines the highest security level allowed to access the
system.
PID
-TRYS n1
-COM a 1
-RANGE n2 n3
The PID option turns on the ACCESS option, and requires all remote
users to use a person id and a Personal Identification Code (PIC)
instead of a ~(t"~asswor'tr"in"'tB~""'~l'0g6n""'it€~limi'1i'"!\rB'tt·,.,,~~
functions of the ACCESS option. When the PID option is active, the
term nuserid n is not used, replaced by nproject name n , and the
password for the project is not used. Only person ids that are
registered on a project are allowed to gain access-to that project.
The PID option also allows the system console operator to use the
SECUR console verb to manually lock out the Person Profile
corresponding to a registered person ide The PID option causes the
person id to be used in place of the-use rid for the functions of the
SCC option if the SCC option is active.
5-81
DH18-03
PIC
-TRYS n1
-COM a1
-RANGE n2 n3
The PIC option turns on the PIn and ACCESS options, and has the same
arguments as the PID option. The PIC option requires a Personal
Identification Code (PIC) on the $ SECURTY (JCL) statement, along
with the person_id, for all card reader, IMCV, and remote batch jobs.
ALL
-TRYS n1
-COM a1
-MINLVL ·x
-MAXLVL y
-RANGE n2 n3
The ALL option provides a convenient method of turning on all of the
Security options.
where:
n1 - The number of unsuccessful logon attempts allowed before the remote
line is disconnected and the project profile or person profile is
locked. (0 to 63, default = 2)
n2 - The minimum number of characters for PIC generation (4 to 11, default
4).
=
n3 - The maximum number of characters for PIC generation (4 to 11, default =
4).
x
- One character representing the minimum security level allowed to access
the system (0 to 9, A to Z, no default).
y
- One character representing the maximum security level allowed to access
the system (0 to 9, A to Z, no default).
a1 - Comment string to be displayed by Startup. This string must be a
protected string delimited by either quotes (") or apostrophes ('),
with a maximum length of 55 characters, including delimiters. The null
string is the default. If a delimiter must be displayed in the
message, two adjacent delimiters will yield one delimiter in the
output. For example,
-COM "AB""CD"
yields AB"Cn
-COM "A""BCn""" yields A"BCn"
Another way to do the same thing is to delimit the protected strings
using apostrophes: 'AB"CD' or 'A"BCD"'.
5-82
DH18-03
"\
A $ SECURE statement option and associated argument(s) are separated from other
options and associated argument (s) by a semicolon (;). For example:
1
$
8
6
SECURE
SCC -TRYS 4 -COM "ALLOW 4 LOGON ATTEMPTS"; PID -RANGE 5 6
The $ SECURE statement can be continued to a $ ETC statement by using an
ampersand (&) at the end of a line to indicate the continuation. For example:
1
1
8
6
$
$
SECURE
ETC
ETC
SCC -TRYS 4 &
-COM "ALLOW 4 LOGON ATTEMPTS";&
PID -RANGE 5 6
$
$ SHARED Statement
The $ SHARED statement allows the site to define permanent mass storage devices
to be shared with the Network Processor Supervisor (NPS).
I
If one or more $ SHARED statements are included with the Startup job stream,
the No In-memory Available Space Table (NIAST) option is activated for all mass
storage devices configured on that system. (Refer to the NIAST parameter under
"$ INFO Statement" in this section.)
/
Devices described as removable (i.e., RMVBL) on the $ INFO NIAST statement
cannot be shared.
When identifying one or more permanent mass storage devices on a central system
as corr~on with NPS, the $ SHARED statement defines the amount of mass storage
space to initially reserve on each device for NPS use. The format for the
$ SHARED statement is:
1
1
8
6
$
SHARED
MPC-m/PRIMARY,ddd/LI ..1IT-xxxxx
--------------------------
where:
m
- Number (0-63) of the MPC controlling the common storage devices.
Only one MPC can be shared with NPS.
PRIMARY - Must be specified to indicate mass storage devices are shared with
NPS.
\
)
5-83
DH18-03
~
ddd
xxxxx
- Logical device name of the permanent mass storage
shared with NPS. If multiple devices are shared,
ddd/LIMIT-xxxxx fields must be specified for each
maximum of two devices can be shared with NPS and
configured on the same MFC.
device on MPC-m
the
device. A
all must be
- Number of llinks initially reserved on device ddd for acos 8
software allocation. As previously stated, i f more than one
device is specified by the ddd field, the /LIMIT-xxxxx field must
be repeated for each device. Note that this value defines the
amount of space initially allocated for GCOS 8 software.
Additional space can be requested by and allocated to NPS as
required for processing by the system.
The following example illustrates reserving a total of 6000 llinks of mass
storage space for GCOS 8 use on permanent mass storage devices NP1 and NP2
(i.e., 3000 llinks are reserved for each device). Both devices are connected
to MPC-O.
1
8
1
6
$
SHARED
MPC-O/PRIMARY,NP1/LIMIT-3000,NP2/LIMIT-3000
$ SYID Statement
The $ SlID statement identifies the system being bootloaded. This statement
frequently identifies the Software Release on 'wEicn the system is operating.
Data included on the $ SYID statement is printed in the banner of all dumps and
job output. (Refer to "Dump Banner" in Section 3.)
The format for the $ SYID stateDlent is:
1
1
8
6
$
SYID
nnnnnn
where:
nnnnnn - A maximum' of six alphanumeric characters identifying the system
being bootloaded. The name must be acceptable to the File
Management System (FMS), as the Error Logging and Analysis System
(ELAN) uses the system-id as part of its collection file name.
5-84
(
$ TRACE Statement
)
The $ TRACE statement specifies which internalnExste~ trag~~~~ to activate
for the purRose of ,assisting in system failure analysis. The trace~~on
provides ~ history of-";ysremoPeratrngev=en~cede a malfunction).
These events are recorded in a trace table, which is maintained as a circular
list (i.e., the most recent trace entries overlay the oldest entries when the
table fills). Table content can be written to magnetic tape and then printed
to assist in debugging efforts.
Each bit position in the four control words (a ••. a, b ••• b, c •.. c, d .•• d)
corresponds to a trace type. Setting a bit (=1) indicates that the
corresponding trace function is not desired. (A common error is to set the bit
to indicate that the trace is desired.) Each value specified in columns 16-64
of the $ TRACE statement is an octal number representing the bit configuration
for the desired traces. For example, the octal number 7 (binary 111) indicates
that none of the three traces represented by the bits is desired; the octal
number 4 indicates that only the trace type represented by the first bit (1) is
not desired. A $ TRACE statement containing all 7s in the four control words
bypasses the trace routine.
The console entries TRACE ON and TRACE OFF override $ TRACE statement content
for the duration of the current bootload. $ TRACE statement definitions are
reinstated with the next bootload. The TRACE ON entry activates all system
traces, while the entry TRACE OFF deactivates all system traces. Note that the
TRACE ON entry is not effective unless at least one trace type was activated
via the $ TRACE statement at System Startup.
I
)
The $ TRACE statement has no impact on Time Sharing System traces. All Time
Sharing System traces are active when received with the Software Release unless
changed via a site-option patCh to the .MTIMS module at System Startup.
The format for the $ TRACE statement is:
1
1
8
6
$
TRACE
aaaaaaaaaaaa,bbbbbbbbbbbb,cccccccccccc,dddddddddddd
where:
a ••• a - First control word, which defines trace types 0-35. At least one
and as many as twelve octal characters must be specified.
b ••• b - Second control word, which defines trace types 36-71. At least one
and as many as twelve octal characters must be specified.
c ••• o - Third control word, which defines trace types 72-107. At least one
and as many as twelve octal characters must be specified.
d ••• d - Fourth control word, which defines trace types 108-143. At least
one and as many as twelve octal characters must be specified.
)
5-85
DH18-03
NOTE: Each of the control words is zero-filled (i.e., if a control word
contains a single zero, all trace types for that control word are
desired) •
The $ TRACE statement in. the following example activates trace types 0-5
(represented by the two leading zeros in the first word), 36-71 (represented by
all zeros in the second word), and 76 (represented by the octal number 6 in the
third word).
1
8
1
6
$
TRACE
007777777777,0,767777777777,777777777777
Table 5-6 defines each trace type and its associated trace number.
that creates the trace entry is identified in parentheses.
Table 5-6.
Octal
Trace
Number
000
I
I
I
I
001
002
003
004
005
006
007
010
011
012
013
014
015
016
017
020
021
022
023
024
025
026-027
030
031
032-043
Trace
The module
System Trace Types
Typ~~e~~rip~ion
Exit a module and return through a 64-word safe-store frame.
( .MDISP)
Call a module via .CALLX or .CALLY. (.MDISP)
Call a module from SSA/PRC via .CALL or .CALLA. (.MDISP)
Process switch and dispatch to a process. (.MDISP)
Not used. Was end of courtesy call.
Processing GPR, SWAP, or ABORT. (.MDISP)
Enable execution of a process. (.MDISP)
Exit a module and return to SSA or PRC. (.MDISP)
Occurrence of a fault other than a MME. (.MFALT)
Transfer (ooTO) to a module. (.MDISP)
The processor is idle. (.MDISP)
Master Mode Entry (MME) fault occurred. (.MFALT)
Memory parity error occurred. (.MFALT)
Privileged MME (PMME) fault request. (.MPMME)
Marks start of courtesy call. (.MDISP)
Identifies the start of a system event for exception processing,
process swap, or process abort. (.MDISP)
Marks end of activity for a process or end of job. (.MBRT6)
T&D trace entry (COLTS on/off trace or TOLTS termination trace.
(T&D)
Call an HCM module. (.MDISP)
Exit a module and return to HCM. (.MDISP)
Entry to domain exception processing. (.MFALT)
OCLIMB from domain exception processing. (.MFALT)
Not used.
OCLIMB type dispatch. (.MDISP)
LDP/TRA type dispatch. (.MDISP)
Not used.
5-86
DH18-03
Table 5-6 (cont). System Trace Types
Octal
Trace
Number
044
045
046
047
050
051
052
053
054
055
056
057
060
061
062
063
064
065
066
067-107
110
111
112
113
114
115
116
117
120
121
122
123
124
125
126
127
130
131-153
154
155
156
157-17.7
Trace Type Description
Execute CIOC to start I/O. (.MIOSO)
Connect to a specified Front-end Network Processor (FNP).
( .MDNET)
A call was made to entry point 2 of the specified channel module.
( .MIOSO)
The specified I/O status was sent to the Exception Processor.
( .MGEPR)
Link a request in channel queue. (.MIOSO)
10M fault occurred on a channel. (.MIOSO)
Not used. Was accept marker.
Interrupt other than a marker interrupt, special interrupt, or
terminate interrupt was processed. (.MIOSO)
Process special interrupt. (.MIOSO)
Terminate interrupt or initiate interrupt was processed. (.MIOSO)
Relinquish broken for a process. (.MIOSO)
Roadblock broken for a process. (.MIOSO)
Accept special interrupt. (.MIOSO)
Start status return action. (.MIOSO)
A fault or marker interrupt occurred. (.MIOSO)
Terminate interrupt or initiate interrupt accepted. (.MIOSO)
MPC controller special interrupt. (.MIOSO)
An lOX interrupt (DPS 88) was accepted. (.MIOSO)
A Rapid Access Data System (RADS) data move occurred. (.HSDCB)
Not used.
Specified activity sent to memory allocator. (.~~LC1)
Specified peripheral device could not be allocated. (.MALC1)
Completion of SYSOUT printing for specified job. (.MGEOT)
Start of SYSOUT printing for specified job. (.MGEOT)
Completion of SYSOUT punching for specified job. (.MGEOT)
Start of SYSOUT punching for specified job. (.MGEOT)
Job to Peripheral Allocator. (.MSCHD)
Process number assigned. (.MSCHD)
Start of FLINKER activity. (.MFLKR)
Start of GElN. (.MGEIN)
End of FLlNKER activity. (.MFLKR)
SYSOUT notified of end-of-job. (.MSYOT)
SCT type specific allocation. (.MALC5)
DEVICE type specific allocation. (.MALC6)
DEVICE space deallocation. (.MALC9)
PERM file space allocation. (.MAS06)
User trace entry.
Not used.
Start of swap operation. (.MPOP4)
Start a nel-l process. ( •MPOP5)
Process swap complete. (.MPOP3)
Not used.
5-87
DH18-03
I
I
$ TRAINS Statement
The $ TRAINS statement defines the sitets standard printer belts (i.e., those
that support the GCOS system character set, but which may differ in character
sequence). The Startup program uses these parameters to initialize the Table
of Print Train Standards, which resides in main memory and which is a catalog
into the PRINTlMAGE file. (Refer to the GCOS B OS System Operating Techniques
manual for character set and PRINTIMAGE file information.)
(
Multiple character sets can be defined on one $ TRAINS statement or they can be
continued on one or more $ ETC statements. Note that the printer type,
character set identification number, and character set name fields are
considered a single entity and are separated by slashes. These three fields
are separated from the next trio of character set parameters by a comma.
ASCII character set definitions must be preceded by the word LONG. Any ASCII
character set definition must follow the last BCD character set definition.
If information provided in the three fields is incompatible (e.g., the
character set identification number and the printer type are inconsistent), the
printer is released and the console message:
TRAIN ID UNKNOWN TO STARTUP DEVICE icccdd RELEASED
is issued (where i = input/output controller number, ccc
dd = device number).
= channel
number, and
~
The format for the $ TRAINS statement is:
1
6
1
8
$
$
TRAINS ppp/nnnn/tttttt, •.• ,ppp/nnnn/tttttt,
ETC
LONG,ppp/nnnn/tttttt, ••. ,ppp/nnnn/tttttt
where:
ppp
- Printer type number:
4nn
where
nnnn
n~
= any
numerical value
- Standard print train identification number:
1130 - Standard ASCII character set
764 - Standard BCD character set
tttttt - Character set name:
GCOS
- BCD character set (764)
ASCII4 - ASCII character set (1130)
5-88
(
DH18-03
LONG
- Must precede definitions of long-character (i.e., nine-bit
character) character sets to include in the Table of Print Train
Standards. While this identifier can be appended to the BCD
character set definitions on the $ TRAINS statement, it often is
less confusing to define ASCII character s~ts on a separate $ ETC
statement.
The following example defines one BCD (i.e., short-character) character set and
one ASCII (i.e., long-character) character set.
1
1
8
6
$
TRAINS
402/764/GCOS,LONG,402/1130/ASCII4
$ UNIT Statement
!,.he $ UNIT statement Re.,rm~~H:!..tcheble ~2-2x.eit.het oo!~~.!.e.R..C!;rat~
d~vic~~ t~ b~..,""~,r.~~§P-,Q,~g ..,~,,~'U~,,..,§sm§J,~&~£!l~E2-.!.~""~!:Mf.~~,,_.~~:'~~E,",~~E:,g,}:~~,~_~,,!,
~....ne...£ont,rQ.l,Le..r..,Jn .. u~
Any number of $ UNIT statements can be included in the
Startup job stream.
The format for the $ UNIT statement is:
1
'\
1
8
6
$
UNIT
aaa,bbb,message
)
/
where:
aaa
- A previously configured logical device name.
bbb
- A previously configured logical device name on an input/output
controller other than the one to which aaa is assigned.
message - Any user-specified message not exceeding 24 characters.
If device aaa is on a released input/output controller and device bbb is on an
input/output controller that has not been released, the references to the two
devices are interchanged and the "message" specified by the user in the control
statement is given on the system console.
If device aaa is on an input/output controller that has not been released or i f
both devices aaa and bbb are on released input/output controllers, the control
statement is ignored.
~,
The following example indicates that devices TB2 and TB6 have been previously
configured and that TB6 will assume the device name TB2 if the input/output
controller for TB2 is released during Startup. The message TB6 NOW TB2 will be
given on the system console when the input/output controller for TB2 is
released.
)
DH18-03
5-89
4MYi.§#.M • .
;Z; $i;;JNAlMMQ¥;m\C4UM4JiilWW
1
1
8
6
$
UNIT
TB2,TB6,TB6 NOW TB2
(
--------------.--.-------
$ URP Statement
The $ URP statement defines each URP800n Unit Record Processor (URP0600 must be
defined on the $ MPC statement) and all active unit record peripherals
controlled by that URP800n.
The format for the $ URP statement is:
1
8
$
URP-m
1
6
Iyy-i,[PORTS-p],{PUB-n}
{CH-n }
where:
m - MPC/URP number (0-63). Each configured URP800n must be assigned a
logical number and specified on the $ URP statement. See the $ MPC
statement for specifications for the value of m.
i-The number (0-3) of the input/output controller to which the URPaDOn is
attached.
p - The number of ports the URP800n controls.
1 and 4.
The value of p may be between
n - The input/output controller channel (CH/PUB) number of Port-O.
must be configured on this channel.
A device
The following example indicates that logical Unit Record Processor (URP) number
5 is configured in IOM-1, and its four ports, Port-O is connected to 10M
channel 24.
1
1
8
6
$
URP-5
IOM-1,PORTS-4,CH-24
The following example is identical to the preceding example, except it is used
with a system configured with an lOX:
1
1
8
6
$
URP-5
IOX-1,PORTS-4,CH-24
5-90
DH18-03
~
$ XBAR Statement
~
V
Component redundancy allows a site to employ the crossbarring technique, which
is the physical and logical connecting of system components so that data can
flow across channels through the system even though one or more components
become inoperable. A channel is a data path between the peripheral device and
the processor. Crossbarring configures data channels to provide two distinct
paths. These pathways allow system software to route data along whichever
channel is available without requiring reconfiguration of system components.
While hardware crossbarring considerations center on the physical
interconnection (i.e., cabling) of components, software relationships between
crossbarred input/output controllers and data channels (CH/PUBs) are defined
via the $ XBAR statement.
The $ XBAR statement has two formats for each type of input/output controller.
The first of the following formats is used to crossbar logical channels on the
same input/output controller. The second format is used to crossbar logical
...--.
channels from one input/output controller to another •
.........
To crossbar logical channels on the same input/output controller:
1
'\
)
1
8
6
$
XBAR
{PUB-a} {PUB-b}
Iyy-m,{CH-a },{CH-b }
where:
Iyy -
IMU, IMX, 10M, lOP, or lOX.
m
Iyy number (0-3)
a,b -
Channel number.
Permissible values are:
8-63
IMU
IMX
10M
lOP
lOX
0-127
8-31
8-63
0-127
To crossbar logical channels from ,one input/output controller to another:
1
1
8
6
$
XBAR
Iyy-m,CH-a,lyy-n,CH-b
5-91
DH18-03
where:
(
Iyy - lHO, IMX, 10M, lOP, or lOX.
m,n - Iyy number (O-3).
a
- Channel number of Iyy-m.
above.
Permissible values are the same as a,b,
b
-
Channel number of Iyy-n.
above.
Permissible values are the same as a,b,
In each of the preceding formats, the first channel (eH) defined is the primary
channel and the channel number following an Iyy field applies to the preceding
Iyy number. (The $ XBAR statement must follow the $ Iyy statement describing
the primary channel identified on the $ XBAR statement.) A channel number
cannot be defined on more than one $ XBAR statement.
Multiple logical channels (CHs/PUBs) can be crossbarred on the same $ XBAR
statement. The sequence in which the channels are identified on the $ XBAR
statement reflects the sequence in which the channels will be serviced. For
optimum service, logica.l channel identifications should be alternated from one
input/output controller to the other. If two channels from the same
input/output controller are identified in sequence, the second channel is not
serviced until I/O has completed on the first channel.
The following examples indicate a variety of crossbarring techniques within one
subsystem. (Two or more subsystems cannot be crossbarred to each other.)
1. This example defines a single cable (one PSIA) with two logical channels
crossbarred.
1
8
6
$
XBAR
Iyy-O,PUB-12,PUB-13
or
$
XBAR
Iyy-O,CH-12,CH-13
2. This example defines dual cables (two PSIAs) with logical channels
crossbarred. Logical channel identifications are alternated between the
PSIAs to optimize service. Logical channels 12 and 13 are on one PSIA
and 20 and 21 are on another PSIA.
1
8
1
6
$
$
or
$
$
XBAR
ETC
Iyy-O,PUB-12,PUB-20,
Iyy-O,PUB-13,PUB-21
XBAR
ETC
Iyy-O,CH-12,CH-20
Iyy-O,CH-13,CH-21
-----.
5-92
DH18-03
3. This example expands example 2 to include two input/output controllers.
~
1
~
1
8
6
$
$
$
$
or
$
$
$
$
XBAR
ETC
ETC
ETC
Iyy-O,PUB-12,Iyy-1,PUB-20,
Iyy-O,PUB-13,Iyy-1,PUB-21,
Iyy-O,PUB-14,Iyy-1,PUB-22,
Iyy-O,PUB-15,Iyy-1,PUB-23
XBAR
ETC
ETC
ETC
Iyy-O,CH-12,Iyy-1,CH-20,
Iyy-O,CH-13,Iyy-1,CH-21,
NOTE:
XBARed devices cannot be channelled across two different
subsystems.
Iyy-O,CH-1~,Iyy-1,CH-22,
Iyy-O,CH-15,Iyy-1,CH-23
The $INITIALIZE section has four essential functions in the System Startup
process. Each of these functions is peripheral device-oriented. (Refer to
"*INITIALIZE? Question" in Section 2 for discussions of each of these
functions.)
\)
First, the $INITIALIZE section identifies, via $ INIT statements, the mass
storage devices to be initialized. To accomplish the initialization, the
operator must make a positive response to the *INITIALIZE? question during the
bootload procedure. The first $ INIT statement should name the device on which
. the AUTOLOAD file will reside.
Defective space existing on configured mass storage devices is identified in
this section, via $ DIRECT statements and related D, 0, A, L, and Y
statements. This information is written to each applicable disk or fixed
device during the initialization process.
If a device is not defined on a $ INIT statement, the device 1s not
initialized. If the operator responds NO to the -INITIALIZE? question during
the bootload procedure, the entire $INITIALIZE section is ignored and no mass
storage devices are initialized.
Second, the $INITIALIZE section provides a facility for defining volume sets
and their associated characteristics.
Third, the $INITIALIZE section performs a rollcall function during which the
peripheral device configuration is confirmed. Mass storage devices are
verified; magnetic tape handlers are surveyed; character set images and VFC
images are loaded.
Fourth, the $INITIALIZE section is used to write firmware to the deckfile and
to read firmware from that file for DPS 8 and DPS 8000 systems.
5-93
DH18-03
I
Importance
or
Sequence In $INITIALIZE Section
(
The following statements can be included in the $INITIALIZE section:
$
$
$
$
$
$
$
$
DEKSAV
DIRECT
DKEND
INIT
OBJECT
READIN
VOPT
VSET
Although the following descriptions are presented in alphabetic order, the
actual sequence of statements in the $INITIALIZE section of the Startup job
stream must be as shown in Table 5-7 to ensure that it will be possible to
start up a system
o
from a power-up condition (where no controller has firmware), or
o with an INIT of the AUTOLOAD device, or
o with the change of the AUTOLOAD device (causing the deckfile to become
undefined), or
o with the deckfile cleared to install a new revision of the Integrated
Firmware And Diagnostic (IFAD) tape.
Any other sequence may lead to failure under some conditions.
With a production system bootload tape set up as defined in Table 5-7,
successful controller initialization is always possible, except for hardware
failure of a controller. A $INITIALIZE section without the firmware decks can
then be used to selectively initialize devices, or to add $ DIRECT or D, 0, A,
L, or Y statements following a bootload with a REPL response to the -EDIT?
question.
5~4
DH18-03
Table 5-7.
Required Sequence In $INITIALIZE Section
1
1
8
6
$INITIALIZE
$
INIT
All $ INIT statements to be processed.
$
DIRECT
With related D, 0, A, L, and Y statements to define
defective space for the device on which the AUTOLOAD
file is configured.
$
$
OBJECT
DEKSAV OFF
MPCB program
To prevent writing of firmware to the deckfile
before the firmware to support that operation has
been loaded.
$
OBJECT
AUTOLOAD device controller firmware
Caution: If the system configuration includes two or more
mass storage controllers that require different
firmware, each of those firmware decks should be put
here to ensure that there will be firmware for the
AUTOLOAD device, no matter which device is
configured as the AUTOLOAD device.
$
OBJECT
$ READIN device controller firmware
Caution: If the system configuration includes two or more
tape controllers that require different firmware,
each of those firmware decks should be put here to
ensure that there will be firmware for the $ READIN
device, no matter which device is configured as the
$ READIN device.
$
DEKSAV
ON
$
$
READIN
DIRECT
$
$
VSET
VOPT
\1
)
To allow writing of subsequent firmware to the
deckfile after firmware to support that operation
has been loaded.
With related D, 0, A, L, and Y statements to define
defective space for all remaining mass storage
devices. The $ DIRECT statements must be in the
same sequence as the devices are configured on $ Iyy
statements in the $CONFIG section.
} For each volume set.
}
._IEOF
5-95
DH18-03
$ DElS!V Statement
The $ DEKSAV statement allows a
stream ttle, which reside?s~o~n~t~h~e~~~~~~~~~~;;~~~-:~~~~~~~·
$ DECKFIL statement. Two options
OFF -
The firmware job stream{s) following this $ DEKSAV OFF statement in
the card reader is not to be written to the deckfile.
ON
The firmware job stream(s) following this $ DEKSAV ON statement in
the card reader is to be written to the deckfile.
-
The OFF option remains in effect until a $ DEKSAV ON statement
A $ DEKSAV ON statement is needed only to turn off (reset) the
allow subsequent firmware job streams to be written to the job
Therefore, two $ DEKSAV statements must enclose a firmware job
not to be saved.
is encountered.
OFF option and
stream file.
stream that is
The following example indicates that the first group of firmware deck images is
not to be written to the deckfile, while the second group of firmware deck
images is to be saved.
1
1
8
$
DEKSAV OFF
6
Firmware deck images that are not to be written to the
deckfile.
$
DEKSAV ON
Firmware deck images that are to be written to the deckfile.
$ DIRECT Statement
1. The $ DIRECT statement identifies a mass storage device (ddd) and
introduces a series of space-definition statements containing defective
space information applicable to the device. Information from these
statements, referred to as the D, 0, A, L, and Y card images, is written
to the defective llink directory and the defective space history table on
device ddd.
2. The /CLEAR parameter can be included on the $ DIRECT statement to clear
the defective llink directory and the defective space history table of
information.
5-96
DH18-03
c
Defective space, which is not available for allocation, normally is defined on
a list provided by the manufacturer of the pack. This data must then be
written to the defective llink directory and the defective space history table
via the D, 0, A, L, and Y card images before the pack is used.
As a result of encountering a $ DIRECT ••• /CLEAR statement during disk pack
initialization (after pack formatting has occurred), Startup issues the console
message PROCESS DIRECTORY CARD FOR DEVICE ddd?, allowing the operator to clear
or retain defective space in the pack header. If the operator responds YES,
the defective llink directory and defective space history table are cleared.
To avoid accidental clearing of defective space information from a pack header,
it is recommended that, following the initial system bootload, the $ DIRECT and
D, 0, A, L, and Y card images be removed from the Startup job stream.
When a disk pack is moved from one device to another, a $ DIRECT statement and
its related space-definition statements must reflect this change. For example,
if a disk pack is moved from device DS1 to device DS5, the $ DIRECT statement
must indicate that the pack (i.e., the defective space) is on DS5.
The $ DIRECT statement for the AUTOLOAD device must always - regardless of the
options included on the statement - precede the $ OBJECT statement. In
addition, the $ DIRECT statements for all other devices must be in the same
sequence that the devices are defined on $ Iyy statements.
The format for the $ DIRECT statement is:
)
1
1
8
6
$
DIRECT
ddd[/CLEAR]
where:
ddd
- Logical device name of the mass storage device on which the pack
containing defective space resides.
/CLEAR - The pack header is cleared of defective space data, thereby
indicating that all space on the pack is available for allocation.
Defective space data can be reestablished via D, 0, A, L, and Y
card images.
If using the $ DIRECT ddd/CLEAR option, a $ DIRECT ddd statement specifying the
same device must be included as the next statement, preceding any D, 0, A, L,
or Y card images of that device.
5-97
DH18-03
The D, 0, A, L, and Y card images must immediately follow the $ DIRECT ddd
statement identifying the mass storage devj.ce for which they are defining
defective space. (The space-definition statements must not immediately follow
a $ DIRECT ••• /CLEAF statement.) Each statement defines defective space in
different quantitie&: cylinder/head, sectors, llinks, and links. The statement
defining the contiguous defective space in the most efficient manner can be
used. For example, if defective space occupies three contiguous llinks, the Y
statement best defines the space.
The Defective LlinkDirectory Print (DLDP) program can be used to punch D, 0,
A, L, and Y card images from the defective llink directory for a specific
device. Subsequently, these statements can be used to reestablish defective
space infoI"mation in the pack label. A listing of all tracks composing the
defective llinks also is printed. (Refer to "Executing RSIpn in the GCOS 8 OS
System Operating Techniques manual for a description of this program.)
The formats for the D, 0, A, L, and Y card images are:
1
DOaaaOObb,ppppp,tttttt[,mmddyy] [,zzzzz]
OOOcccccc-OOdddddd,ppppp,tttttt[,mmddyy][,zzzzz]
Aeeeeeeee-ffffffff,ppppp,tttttt[,mmddyy] [,zzzzz]
Lgggggggg-hhhhhhhh,ppppp,tttttt[,mmddyy] [,zzzzz]
Yiiiiiiii-jjjjjjjj,ppppp,tttttt[,mmddyy][,zzzzz]
where:
aaa
- Cylinder number (decimal).
bb
- Head number (decimal).
c ••• d
- Beginning (c) and ending (d) sector number (octal) in a series of
contiguous defective sectors. If only one sector contains
defective space, enter only OOcccccc.
e ••• f
- Beginning (e) and ending (f) word numbers (octal) of defective
space within a sector or within a series of contiguous defective
sectors.
g ••• h
- Beginning (g) tink number (octal) and number (h) of links (octal)
in a series of contiguous defective links. If only one link
contains defective space, enter only gggggggg.
i ••• j
- Beginning (i) llink number (octal) and number (j) of llinks (octal)
in a series of contiguous defective llinks. If only one llink
contains defective space, enter only iiiiiiii.
5-98
DH18-03
ppppp
11-\
I
,;
- Pack serial number of the pack on which the defective space
resides. (Logical device identifier if this is an MSU0500,
MSU0501, MSU3380, MSU3381, or MSS8080 device.)
tttttt - Device type:
Code
Description
Code
Description
MS0400
MS0402
MS0450
MS0500
MS0501
MSC1A
MSU0400
MSU0402
MSU0451
MSU0500
MSU0501
MSU3380
MSC1B
MSD1A
MSD1B
MSM1A
MSM1B
MSM1E
MSU3380
MSU3381
MSU3381
MSS8080
MSS8080
MSs8080
mmddyy - Optional field specifying today's date in the format month (mm),
day (dd), and year (yy).
z ••• z
)
- Optional field containing any desired comments.
The following example causes the defective llink directory and the defective
space history table for the disk pack (pack serial number A1665) residing on
MSU0451 mass storage device DS3 to be cleared of information (/CLEAR).
Subsequently, the directory and table entries that define defective space in
sectors 1253-1255 and 1271-1278 and in llinks 3560-3575 of pack A1665 are to be
recreated from information included on the 0 and Y space-definition card images
and written to the defective llink directory and defective space history table
on device DS3.
1
1
8
6
$
DIRECT
DS3/CLEAR
$
DIRECT DS3
000001253-00001255,A1665,MS0450
000001271-00001278,A1665,MS0450
Y00003560-00000015,A1665,MS0450
$ INIT Statement
The $ INIT statements identify: the mass s~.Q~g~t_(l~yj...Q.§,a..M,,,."b~_..mlt1a:u:..~~
during a bootload. (The statement does not apply to magnetic tape or unit
reCOrd'devices.)""" Any positive response (i.e., YES, TOTAL, or PARTIAL) to the
.INITIALIZE? question during the Startup question-and-answer sequence may
affect each device specified on a $ INIT statement. (Refer to ".INITIALIZE?
Question" in Section 2 for additional information.)
)
5-99
DH18-03
If a device is not defined on a $ INIT statement or if the $ INIT statement has
been removed, a positive response to the ·INITIALIZE? question has no effect on
the device. Unless a pu~ge of all files on all devices is intended, it is
recommended that all $ INIT statements be removed from the Startup job stream
following the initial bootload (i.e., after the system has been installed).
It is recommended that all mass storage devices be defined on $ INIT statements
and initialized when performing a cold boot. This technique helps ensure that
required pointers and tables are reestablished on each device.
Finally, it is recommended that all permanent mass storage devices.be
initialized if the device named ST1 and/or the device for which the SMCDUP
parameter applies are initialized. (The SMCDUP parameter is specified via the
$ INFO statement.) Initializing in this manner also helps ensure that pointers
and tables on all devices are synchronized. Failure to perform this type of
initialization results in the warning message .ST1 AND SMCDUP INITED BUT NOT
ALL OTHERS, FILE SPACE WILL BE LOST being issued to the system console.
However, Startup does not abort.
All $ INIT statements must immediately follow the section-identifier statement
($INITIALIZE) and precede all other statements and job streams in this
section. When Startup encounters a $ INIT statement, allocation control
information is written to the pack label portion of the device (ddd) defined on
the statement.
The format for the $ INIT statement is:
1
8
1
6
$
INIT
ddd[,AU-a][,CAT]
where:
ddd
- Logical device name of the mass storage device to be initialized.
AU-a - Number of llinks (a) per allocation unit (AU) for this device.
value can be 1, 2, 4, 8, 12, 24, 36, 48, or 60.
This
NOTE: If device ddd is shared with NPS, the AU value must be 12,
otherwise, NPS aborts.
If the AU size is not specified on the $ INIT statement, the size
specified on the $ Iyy statement or the default size for this device
is written to the Available Space Table (AST) in main memory. If
both statements define an AU size and the sizes differ, the smaller
value is used. An error condition could result on a subsequent warm
boot. The message:
CANNOT BUILD IN-CORE TABLE ON ddd DUE TO
TBLSIZ s ••• s DEVICE RELEASED
5-100
DH18-03
C
is issued (where ddd = logical device name of the mass storage device
on which the AST resides and s ••• s = status word). (Refer to the
GCOS 8 OS System Operating Techniques manual for available space
values for each mass storage device type. Refer to the $ INFO
statement in this section for a description of the No In-memory
Available Space Table (NIAST) option.)
The $ INIT statement initializes disk packs. Startup uses the AU
value of the initialized pack to establish the size of allocation
tables in memory. If a disk pack is not available at System Startup,
Startup uses the AU size from the $ Iyy statement to establish
allocation table size. To help prevent overlap problems between disk
pack and in-memory tables whereby the in-memory tables are
overwritten with and destroyed by information from the device tables,
either the AU values on the two statements must be the same or the AU
size must be greater on the $ INIT statement.
For any volume that is to be a member of a volume set, the AU size
must be a multiple of eight i f the volume is formatted in 512-word
sectors.
CAT -
Allows FMS to create catalogs on this device. This parameter can be
specified for a maximum of 20 mass storage devices. If the parameter
applies to more than 20 devices, the console message:
.ONLY 20 CATALOGABLE/SMC/SMCDUP DEVICES ALLOWED
is issued and Startup aborts.
If the CAT parameter is not specified for any device, Startup assigns
the parameter to device ST1.
If the CATDUP parameter is specified on the $ INFO statement, but the
CAT parameter is not specified on the $ INIT statement for the
device, Startup assigns the duplicate catalogs to the device
containing the duplicate SMC.
Startup aborts i f the CAT parameter is specified on the $ INIT
statement for a device for which the NOFMS parameter was specified on
the $ Iyy statement. The following console message is issued:
CAN'T BE CAT AND NOFMS
The CAT option should not be specified for any volume that is
configured as RMVBL. Catalog volumes for volume sets are specified
via the $ VOPT statement; a Structured RMVBL volume is always a
catalog volume.
)
5-101
DH18-03
The following example indicates that FMS can create catalogs (CAT) on mass
storage device DS5. Space is allocated on the device in one-llink increments
(AU-1).
1
8
6
INIT
DS5,AU-1,CAT
Firmware Deck Images
As previously indicated, the $INITIALIZE
must contain the MPC Bootload (MPCB) job
f'C>rmass storage and magnetic tape MPCs.
provided as a package with each Software
section forDPS 8 and DPS 8000 systems
stream and the firmware data images
These are-'''1lf~ 00 JecC-forma€"~>an(r a're
Release.
The MPCB and firmware data images are written to the deckfile, which resides on
the same device as the AUTOLOAD file. Unless overridden by a boot load using
punched cards or a firmware tape, MPC firmware is loaded from the job stream
file during subsequent warm boots. (If an MPC firmware job stream is not to be
written to thedeckfile, a $ DEKSAV statement containing the OFF parameter must
precede the set of images. Refer to the $ DEKSAV statement description in this
section for additional information.)
Only one MPCB job stream, which permits loading of the firmware data decks, is
required regardless of the number of firmware data images included in the
$INITIALIZE section.
One set of data images contains the firmware for the mass storage subsystem
controller (MPC). A second set of data images contains the firmware for the
magnetic tape subsystem controller (only required if processing a $ READIN for
tape). Neither the mass storage subsystem nor the magnetic tape subsystem is
operational until the applicable MPC is bootloaded via MPCBand a set of data
images.
If more than one type of mass storage subsystem is configured (e.g., an MSU0500
subsystem and an MSU0451 subsystem), the only required firmware data images are
those for the subsystem on which the AUTOLOAD device is configured. Firmware
for the remaining MPCs is loaded from the deckfile.
The format for each firmware deck is:
5-102
DH18-03
Content
Description
$ OBJECT
Preface statement
This statement is in standard relocatable format, with
BOOT and DECK the primary SYMDEFs at location O.
Data images
These images are in standard relocatable format and
include MPC micro-instructions and data.
Identification block
statement
This statement contains the following 10 words of
data in standard relocatable format. This is the last
binary data image.
Word 0 - Name identifying type of firmware (e.g., unit
record or mass storage firmware)
1 - Revision level
2 - Purpose of job stream
3 - Zeros
4 - Bits 0-17 contain the size of the first part
of the job stream, which is the control
store; bits 18-35 are unused.
5-8 - Zeros
9 - BCI constant MPCBOT
$ DKEND
)
$ OBJECT AND $ DKEND STATEMENTS
Each firmwar
deck is delimited by $ OBJECT and $ DKEND statements. While
he data decks and the delimiter statements are provided with the Software
Release, the formats for the $ OBJECT and $ DKEND statements are repeated here
in case the card images are lost or damaged and must be re-created.
1
8
6
3
5
6
7
7
3
$
$
OBJECT
DKEND
HMPCJ1
DAT
REV.rr
REV.rr
nnnnOOOO
nnnnssss
1
where:
1'1'
-
Revision level of the firmware, which differentiates between
different versions of firmware. This level also must be defined on
the $ MPCFIG statement in the $CONFIG section of the Startup job
stream. The revision level is saved from the $ MPCFIG statement in a
change table on the deckfile and defines the firmware that is to
bootload each MPC. It must also match the ID block data word 1.
5-103
DH18-03
nnnn - Level of the job stream
ssss - Deck sequence number. The $ DKEND statement sequence should be the
number of the last binary statement plus 1.
PATCHING MPCB AND FIRMWARE DATA IMAGES
The MPCB job stream and the firmware data images can be modified or extended
via patching procedures. The following briefly defines these processes.
o The MPCB job stream can be modified via OCTAL correction statements,
which must immediately precede the $ DKEND statement in the MPCB job
stream. (Refer to "$PATCH Section", later in this section, for the
format of the OCTAL correction statement.)
NOTE:
Patches to .MMPCB must be applied in this manner. They should not
be included in the $PATCH section or patch edited.
o The firmware data images can be modified via CHEX (control store) and
RHEX (read/write memory) correction statements, which must immediately
precede the $ DKEND statement in the firmware job stream. It is
recommended that corrections to firmware data images be made under the
direction of the site's CSD representative.
In each of the preceding cases, the operator must respond YES to the CLEAR AND
OVERWRITE EXISTING DECKFILE? question to rebuild the ~WCB or firmware data
images on the deckfile for TOLTS subsystem usage. The entire MPCB job stream
and firmware data job streams must be loaded via the card reader and the
firmware tape must be mounted on the magnetic tape handler identified on the
$ READIN statement. (Refer to "CLEAR AND OVERWRITE EXISTING DECKFILE?
Question" elsewhere in this manual for additional information.)
$ READIN Statement (DPS 8 And DPS 8000 Only)
The $ READIN statement directs the Startup program to read t1PC f j mW2PG ~om
the firmware taDe. The tape and its contents are cataloged on the deckfile,
residing on the AUTOLOAD device.
It is recommended that-the $ READIN statement be included in the Startup job
stream only when a cold boot is performed, when the AUTOLOAD device is
initialized, and when new firmware is written to the deckfile. When these
functions are completed,remove the $ READIN statement from the job stream. If
the statement is left in the deck and the operator responds YES to the
-INITIALIZE? question, Startup unsuccessfully attempts to read the firmware.
To circumvent the problem, the operator must oause Startup to fail (i.e., enter
BOOT via the system console) and remove the $ READIN statement.
NOTE: The $ READIN statement is not recognized on DPS 88 Systems. The firmware
is loaded by SHAS. Refer to the DPS 88 System Maintainability
Availability Software (SHAS) manual for SMAS procedures.
5-104
DH18-03
The format for the $ READIN statement is:
1
1
8
6
$
READIN
ddd[""tttt]
where:
ddd
- Logical device name of the magnetic tape handler on which the
firmware tape is mounted.
tttt - Density of the firmware tape:
DEN2
DEN5
DEN8
-
DEN16 - 1600 bpi
DEN62 - 6250 bpi
200 bpi
556 bpi
800 bpi
This parameter is required only if the density of the firmware tape
is different from the site's default high density, which is specified
on the $ INFO DENxx/DENyy statement. If no default high density has
been specified, DEN16 is the default value.
The following example indicates that the firmware tape is mounted on magnetic
tape handler 1T7 with a density of 556 bpi.
1
186
$
READIN
1T7""DEN5
$ VOPT Statement
The $ VOPT statement is used to specify the characteristics and options for a
The $ VbPT stateme~~~~~~t
wnrc~rrnes the volume set.
Exactly one $ VOPT statement is required for
every $ VSET statement.
vol~e set.
The format for the $ VOPT statement is:
1
1
8
6
$
$
VOPT
ETC
vs name,VSMC/pack1[,pack2]/[,CAT/packx[,packy[, ••• ]]/][,
FDUPINOFDUP]
where:
vs name Volume set name. Must be the same as the vs name on the immediately
preceding $ VSET statement.
5-105
DH18-03
VSMC
Volume Set Master Catalog. The VSMC specification is required. One
or two pack numbers (device labels) must be provided. The volumes
must have been defined as members of the volume set via the
preceding $ VSET statement. If two volumes are specified, they must
be on different physical units. The first will be used for the
original VSMC; the second will be used for the duplicate VSMC.
If catalog duplication is elected (i.e., two volumes are specified
with VSMC), the VSMC and all catalogs on the volume set will be
duplica~ed.
If one volume is speCified, neither will be duplicated.
CAT
The CAT option specifies the volumes on which catalogs are to be
placed. The logical devices must be members of the volume set. If
the CAT option is not speCified, the VSMC volume(s) are used by
default.
If catalog duplication is elected (i.e., two volumes are specified
with VSMC), the number of catalog volumes must be evenly divisible
by two and the list of catalog volumes must include more than one
physical unit. (If this requirement is not met, then any attempt to
create a catalog on the volume set will return the error message
"NO SPACE FOR-CATALOG ON DEVICE".)
A volume may appear only once in the list of CAT volumes.
volume may also be a CAT volume.
A VSMC
FDUP
The files on the volume set may be duplicated. FDUP may be
specified only if the volume set includes at least two physical
units.
NOFDUP
The files on the volume set may not be duplicated.
$ VSET Statement
The $ VSET stateDlent is used to identify tn.eili~~Ptber.srq~fi! ~ ivolpm~ s~. The
$ VSET statement must be ~mmed~aEely followed by the $ VOPT statement for the
same volume set. The volumes specified must all be mass storage, but may be of
mixed types. The minimum number of volumes in a volume set is one; the maximum
number is 100. All volumes in a volume set must be configured as RMVBL (see
"$ Iyy Format For Mass storage Subsystems" earlier in this section).
The format for the $ VSET statement is:
1
1
8
6
$
VSET
vs~ame,pack1[,pack2[,pack3 •••
'i-106
]]
DH18-03
~,
where:
I
II
"
vs name
Volume set name, 1-12 characters. Allowable characters are
A-Z, 0-9, dash (-) and underscore (). The first character
must be from the set A-Z. The volume set name must be unique.
pack1 (etc.) The alphanumeric device label of a member of the volume set.
The order of the device labels is not important. A volume may
not be a member of more than one volume set.
$EDIT SECTION
The $EDIT section establishes acos sistem files on the mass storage subsystem
and is closely affiliated with the $FILES and $INITIALIZE sections.
o The $EDIT section establishes the content of all system files that the
site may wish to use during the current and subsequent bootloads. The
$FILES section selectively identifies which of these files the site
intends to use during the current bootload.
o
The $INITIALIZE section recreates tables and pointers on each disk drive
(i.e., disk pack) involved in the initialization procedure.
(Initialization destroys existing tables and pointers on a disk pack,
thereby rendering associated files inaccessible.) The $EDIT section,
along with the total system software tapes, permits restoration of the
files that were destroyed during the initialization procedure.
The $EDIT section also allows:
o Creation of new system files. In addition, this section is the means by
which these files are released and the space they occupied returned to
the pool of available space.
o
Sites to edit data files for both site-options and JCL, rather than
hard-coding them into memory, and provides default workstation JCL via
the $ DTFILE/$ ENDTF statements.
If the content of a mass storage device that was initialized (i.e., the
operator made a positive response to the .INITIALIZE? question) is to be
restored, (1) the $EDIT section must contain information pertaining to that
file, (2) the total system software tape containing file data must be mounted,
and (3) the operator must respond YES or PARTIAL to the .EDIT? question during
the bootload procedure. (Refer to ".INITIALIZE? Question" and ".EDIT?
Question" in Section 2 for additional information.)
If the operator responds TOTAL to the .INITIALIZE? question, Startup forces a
YES answer to the .EDIT? question. No console entry is required. The $EDIT
section must be loaded via the card reader or magnetic tape and the total
system software tapes must be mounted to effect the restoration.
5-107
DH18-03
If a file is not defined on a $ FILDEF or $ SSFILE statement, file content is
not restored. If the operator responds NO to the -EDIT? question during the
bootload procedure, the entire $EDIT section is ignored and no files are
restored.
Files established within the $EDIT section cannot be dynamically modified via
console entries. Modification must be performed during subsequent bootloads
(e.ge, manually changing statement content or adding and removing statements).
The following statements can be included in the $EDIT section:
$
$
$
$
DTFILE
ENDTF
FILDEF
SSFILE
The $ FILDEF and $ SSFILE statements can be in any sequence, while the $ DTFILE
statement must always precede the $ ENDTF statement, when used.
$ DTFILE And $ ENDTF Statements
The $ DTFILE Startup statement is used with a $ ENDTF Startup statement. Every
card image enclosed between these statements is written to the Startup-defined
file ffffff on device ddd. This file is a system standard format card image
file with block control words (BCWs) and record control words (RCWs).
The advantages of using the $ DTFILE Startup statement are:
o Users are given the ability to edit data files for both site options and
JeL, rather than hard-coding them into memory_
o Default workstation initiation JCL is provided (under SYS_SOFTWARE).
The formats for the $ DTFILE and $ ENDTF statements are:
1
186
$
$
DTFILE
ENDTF
ddd,ffffff,sss[/O]
[ffffff]
where:
ddd
- The device name of the mass storage device, named on the $ GCOSFIL
Startup statement, where the file is to be created and written.
ffffff - File name (e.g., SYSPN).
characters.
A maximum of 12 non-blank, alphanumeric
sss
- Size, in llinks.
(Code places 25 card images per llink.)
/0
- Overwrite option recommended (letter 0).
5-108
DH18-03
The following sample Startup job stream uses the $ DTFILE and $ ENDTF
statements with sample SYSPN JCL for SHARD and CWS.
1
1
8
6
$
DTFILE DT1,SYSPN,12/0
RUN
RUFILE=SYSTEM,RUNAME=SYSPN,OPTION=DUMP,NJREST
RESOURC VSPACE=100K,SSDUMP
PRIVITY
$
DATA
I.
SPAWN -PATHNAME SYS SOFTWARE/nnnn/JCL/SHARD.SPWN -SNUMB SHARD
SPAWN -PATHNAME SYS-SOFTWARE/nnnn/JCL/CMGROO.SPWN -SNUMB CMGRO
$
$
$
$
$
ENDJOB
ENDTF
SYSPN
where: nnnn is the software release (i.e., 3000)
NOTE: For details on SYSPN and SYS SOFTWARE refer to the GCOS 8 OS System
Operating Techniques manual.$ FILDEF Statement
The $ FILDEF statement defines a GCOS system file and assigns i t to a specific
mass storage dey; c e . All GCOS system files must be' defined via $ Flr::DEFj
statements. The $ FILDEF statement also defines the magnetic tape device from
which the file is to be copied. A separate $ FILDEF statement is required for
each file.
The $ FILDEF statement gives the site the opportunity to balance system files
across permanent mass storage devices. Often, different combinations must be
tried to determine which best fits the site's operating environment. The
purpose of this effort is to balance assignment of high-use and low-use system
files across all configured devices so that files can be accessed faster and
more efficiently.
The System Master Catalog (SMC) always resides on device ST1. Because these
are high-use system files, it is recommended that several low-use system files
be assigned to ST1 and that other high-use system files be assigned to other
devices (thereby reducing device contention on ST1). Among the low-use system
files are System Scheduler files, the Time Sharing Subsystem Library, the
AUTOLOAD file, the deckfile, the load file, the DUMPO and DUMP1-9 files, and
the Integrated Firmware and Diagnostics (IFAD) file.
If the following files are not defined on a $ FILDEF statement, Startup creates
the files and assigns them to ST1. The file sizes can be increased via a
$ FILDEF statement ·and a device other than the default system device can be
specified.
5-109
DH18-03
File Name
Default Size
(llinks)
DUMPO
100
LUMP
24
Description
------~------------------------------------
Used by the Master Mode Dump (.MDUMP) program for
storing the contents of the memory area used
during swap operation. To enable .MDUMP program
snaps, the size should be set to 200 llinks.
Contains dump information and pushdown space.
The format for the $ FILDEF statement is:
1
1
8
6
$
FILDEF
ddd,fffff,sss[/O][,xxx][,ttt][,LABEL/nnnnn][,yyyy]
where:
*
ddd
- Logical device name of the mass storage device on which to create
file fffff. This device must be defined on a $ Iyy statement in the
$CONFIG section and must be a permanent mass storage device. If
this device is a magnetic tape unit or is defined as a NOFMS or
RMVBL device, Startup aborts and the console message:
*ddd fffff CAN'T BE xxxxx
is issued (where xxxxx = NOFMS, REMOVABLE, or NON-STORAGE).
maximum of 78 Startup files can be assigned to one device.
A
fffff - File name (1-12 alphanumeric characters). Note that use Gf the
dump-to-disk feature requires that one or more files (DUMP1-DUMP9)
be specified.
sss
- File size (in llinks). If the file is not created large enough to
accommodate the file that is being copied from magnetic tape handler
ttt, Startup aborts. To correct the problem, re-edit the file from
magnetic tape.
Special consideration must be given to the specification of the file
size for .CRACF (accounting file), which must not exceed 16,383
llinks.
It is recommended that the DUMP1-DUMP9 files be created 'with an
initial file size of 3500 llinks and then re-edited when dump
requirements are known. Actual space used on these files is
identified in the console message WROTE xxxxx LLINKS, which is
issued following a dump. (Refer to the GCOS 8 OS System Operating
Techniques manual for additional information on dumping to disk.)
5-f10
DH18-03
/0
- Filegrow (overwrite) option (letter 0). If a file was defined for a
previous boot and that file has since grown, the use of a new
$ FILDEF statement that includes the /0 option and the new filesize
requirement replaces the old file to accommodate the new, larger
file.
xxx
- Code indicating the format for writing file fffff on device ddd.
ttt
\
)
Code
Description
SYS
Copy the file in system-loadable format. The file must be
defined on a $ SYSTEM statement in the $FILES section.
RDM
Copy the file in random format (i.e., not in
system-loadable format). The file must be defined on a
$ LIBRARY statement in the $FILES section.
RUP
Copy the file in run unit update file format. The file
must be defined on a $ SYSTEM statement in the $FILES
section.
SWI
Copy the file in Seed Workspace Image format. At least one
such file must be defined on a $ SYSTEM statement in the
$FILES section.
- Logical device name of the magnetic tape handler from which file
fffff is to be copied. If ttt is not specified, file fffff will be
created, but no data will be written to that file. When a magnetic
tape device is specified on a preceding $ FILDEF statement, that
same device can be referred to in the field via an asterisk (*).
nnnnn - This field is required for tape label verification and must contain
the name of the file being copied from magnetic tape to file fffff
(if file name fffff is different from the file name in the tape
label)~
yYYY
- Density of the MPC-driven magnetic tape handler ttt from which file
fffff is being edited. This field is required if the density of
device ttt is other than 800 bpi. DEN8 is the default density. (If
this field is included for a device that is not MPC driven, Startup
aborts.)
Code
Description
DEN2
DEN5
DEN8
DEN16
DEN62
200
556
800
1600
6250
bpi
bpi
bpi
bpi
bpi
5-111
DH18-03
The following example shows a 2000-llink file (DUMP1) being created on device
ST1. No data is being written to the file from an existing file on magnetic
tape. Instead, information is written by the system after file creation.
1
8
1
6
$
FILDEF
ST1,DUMP1,2000
The following example shows a 1400-llink file (GC1) being created on device
ST1. This file overwrites (/0) any existing file named GCl on device ST1.
Information is being written to this file in system-loadable format (SYS) from
a file named VS-PRIMARY (LABEL/VS-PRIMARY), which exists on the l600-bpi
(DEN16) total system software tape that is mounted on magnetic tape handler
1T2.
1
1
8
6
$
FILDEF
ST1,GC1,1400/0,SYS,1T2,LABEL/VS-PRIMARY,DEN16
$ SSFILE Statement
The $ SSFILE statement defines the size of each job class from which the System
Ssheduler program assignS" wor!L.~,9~~e, ~yst.e..!!l".t In addition, . the $ SSFILE ".
statement performs two functions with respect to the System Scheduler program's
SSFILE file that are similar to those performed by the $ FILDEF statement for
other system files.
o The sum of the job class sizes specified on the $ SSFILE statement is the
amount of space that Startup assigns to the SSFILE file. Each job is
cataloged in the SSFILE file by the System Scheduler.
o The device on which the SSFILE file resides must be defined on the
$ SSFILE statement.
Definition of class sizes on the $ SSFILE statement - as well as the parameters
specified on the $ SSLOAD statement in the $FILES section - indicates the
relative importance of each job class to the System Scheduler program. The
number of llinks specified for each job class defines the number of jobs within
the class that can be waiting for scheduling. Each llink of SSFILE file space
can accommodate 39 jobs. (Each job requires an eight-word entry on the
SSFILE.) Therefore, the number of jobs that can be cataloged for one class is
derived by multiplying the number of llinks specified times 39.
Each job that is saved following execution (see $ INFO SCHSAV) a'lso occupies
eight words of SSFILE file space. It is recommended that this be taken into
account when defining the size of each class.
The $ SSFILE statement must be present in the Startup job stream. If it is not
present, Startup aborts. However, only one $ SSFILE statement is permitted.
5-112
DH18-03
Three job classes must be defined. The required classes are .EXPRS, .HOLD, and
• useI::- TE,~2_~~i,"i.~~:~p'~~!,~~<,,~any name--ror-.~~~~~~~·~e"r"···c!ii'ss·~·"'·'·'··'(rreq'uentlf,~··"':user~
-n§ defined as • USER. ) If tl1l'fSlr"jotJ"tnasses' 'are 'nof,"""'sffeci'tied, Startup aborts.
Based on any parameter that the site selects, the .user class can be expanded
to multiple classes. A maximum of 49 (02-50) .user classes can be specified in
the optional .userx field(s). Note that definition of more than one .user
class requires a .MSCAN module to evaluate the site-specified parameters and to
direct jobs into the various classes.
The site can specify any names for the optional .userx classes. All names
assigned must be defined on both the $ SSFILE and $ SSLOAD statements. The
names assigned to optional .userx classes have no significance in their
sequence of processing (e.g., class .USER04 is not necessarily processed before
class .USER05). Priority processing by class is controlled by the maximum
number of jobs within a class that can be scheduled for processing at one time,
which is specified on the $ SSLOAD statement.
The special job classes .TASK and .TRANS should not be specified on the
$ SSFILE statement, even though they may be specified on the $SSLOAD
statement. Specification of these classes on the $ SSFILE statement may cause
erroneous incrementing of class numbers, resulting in processing problems.
However, all other job classes specified on the $ SSLOAD statement must also be
specified on the $ SSFILE statement.
The format for the $ SSFILE statement follows. All classes must be defined in
the specified sequence; otherwise, Startup aborts.
1
8
1
6
$
SSFlLE
ddd,.EXPRS/n,.HOLD/n,.user/n[,.userx/n]
where:
ddd
- Logical device name of the mass storage device on which the SSFILE
file resides.
n
- Number of llinks assigned to this class •
• userx - Optional site-defined classes.
specified.
5-113
A maximum of 49 classes can be
DH18-03
The following example indicates that the SSFILE file resides on device ST1.
The .EXPRS class is assigned seven llinks, the .HOLD class is assigned five
llinks, and the required .user class (.USER1) is assigned three llinks. Five
optional site-defined classes also are defined. These include .USER2 (three
llinks), .USER3 (four llinks), .USERlJ (one llink), .USER5 (one llink), and
.USER6 (one llink). The .TSS class is assigned two llinks. Based on these
definitions, Startup will assign 30 llinks of space on ST1 to the SSFILE file,
assuming ST1 has one llink per allocation unit (AU). (That is, five llinks
more than the sum of the llinks specified for each job class. If the AU size
is greater than 1, the SSFILE size is further adjusted upward to be evenly
divisible by the AU size.)
1
1
S
6
$
$
SSFILE
ETC
ST1,.EXPRS/7,.HOLD/5,.USER1/3,.USER2/3,.USER3/4,.USER411,
.USER5/1,.USER6/1,.TSS/2
5-114
DH18-03
$FILES SICTIOR
The $FILES section identifies th!....!l~tem files t~~ut th~,_~ration
of the curren~b£2~ The $FILES section is one of two sections requ1re&in
the Startup jOb stream. Only system programs residing on files defined in this
section are identified in main memory tables. Therefore, a system program is
not available during system operation if the file on which it resides is not
identified in this section.
Each file identified in the $FILES
section. Identification of a file
process. Some files identified in
therefore, can be omitted from the
section must be defined in the $EDIT
in the $FILES section is a selective
the $EDIT section may not be required and,
$FILES section.
For example, a total of 25 system files may be defined in the $EDIT section and
created on mass storage devices. However, if the site requires only 20 files,
only those 20 need identification in the $FILES section.
Two errors are commonly associated with the $FILES section.
1. If a file is identified in the $FILES section but not in the $EDIT
section, the console message -FILE fffff UNDEFINED is issued and Startup
aborts (where fffff = file name).
2. Any references to system programs residing on files not defined in the
$FILES section result either in an error condition or in the request
being ignored.
The following statements can be included in the $FILES section.
statements can be in any sequence:
$
$
$
$
$
$
$
$
$
$
$
These
ACCBUF
ACCOUNT
DFILES
LIBRARY
PFILES
SAVE
SCFBUF
SCFDSP
SSLOAD
SYSOUT
SYSTEM
5-115
DH18-03
$ ACCBUF Statement
The $ ACCBUF statement is used to:
o Specify those record types buffered before being written to the
Statistical Collection File (SCF).
o Specify those record types whose buffering disposition (i.e., buffer or
delete) can be changed by operator request.
o Identify the maximum record type buffered.
If the $ ACCBUF statement is not present, record types 1-23 are buffered (by
default) and can have their dispositions changed.
The format for the $ ACCBUF statement is:
1
186
-----------------------
$
ACCBUF
xxxxxxxxxxxx,yyyyyyyyyyyy,nn
where:
x ••• x - Twelve-character (octal) field identifying the record types to be
buffered. Each bit
defines record type
defines record type
bit = 1, the record
corresponds to a record type (i.e., bit 0
1, bit 1 defines record type 2, ••• bit 22
23). If a bit = 0, the record is buffered; if a
is deleted.
The operator subsequently can enter ACCEPT nn to specify that record
type nn is buffered and written to the Statistical Collection File
(SCF). Conversely, the entry IGNORE nn specifies that record type
nn is deleted and not written to the SCF.
y ••• y -Twelve-character (octal) field identifying the record types that
cannot have their dispositions changed by operator request. If the
bit is set (=1), the record's disposition cannot be changed. If the
bit is not set (=0), the record's disposition can be changed.
nn
- One-digit Qr two-digit number (0-36) specifying the maximum record
type that can be buffered. The default value is 23. Any record
specified in the x ••• x and y ••• y fields that exceeds the value nn is
deleted and cannot have its disposition changed.
The following example indicates that all record types are to be buffered and
that all record types can have their buffering dispositions changed. By
default, record type 23 is the maximum record type that can be buffered (i.e.,
the nn field is null).
5-116
DH18-03
~
1
186
$
ACCBUF
0,0
When more than 36 accounting types are required, the $ SCFBUF and the $ SCFDSP
statements may be used in place of the $ ACCBUF statement.
$ ACCOUNT Statement
The $ ACCOUNT statement defines
File (SCF) is to reside~
t~e., deyice
on which the Statistical Collection
.',.' 'i""","""",.~';,;""",.";""",,',,
1
6
1
8
$
ACCOUNT {RDM,fffff,ggggg}
{RMV,ddd[,DENxx]}[,IDS
$
ETC
[,BUFSIZ/sss][,RETENT/rrr][,CONCUR][,JMAP]]
where:
RDM
- The SCF resides on a mass storage device. Note that the maximum
accounting file size is 16,383 llinks. (Refer to the "$ FILDEF
Statement" definition, earlier in this section).
fffff
- File name of the SCF.
ggggg
- File name of the alternate SCF, used for data overflow.
RMV
- The SCF resides on a magnetic tape device (ddd).
ddd
- Logical device name of the magnetic tape unit on which the SCF
resides.
DENxx
- Tape density for magnetic tape units.
DEN2
DEN5
DEN8
DEN16
DEN62
200
556
- 800
- 1600
- 6250
-
I
bpi
bpi
bpi
bpi
bpi
The density must be the same as the density specified on the $ Iyy
statement for the device defined in the ddd field.
If a density is not specified, the system default high density is
assumed (as specified on the $ INFO DENxx/DENyy statement in the
$CONFIG section).
IDS
- I-D-S/I journal is to be configured.
5-117
DH18-03
sss
- Buffer size. The minimum and maximum sizes are 320 and
respectively. The default is 320 words.
rrr
lou~ "~_
Retention period (in days) for SCF records. The maximum retention
period value is 999, indicating permanent retention. The default
value is O. The retention value is specified in decimal.
CONCUR - Specified only if the SCF is to be concurrently accessed.
JMAP
- Specified only if a data base execution report is desired.
The following example shows the SCF residing on magnetic tape utilizing the
maximum available buffer space available:
1
6
1
8
$
ACCOUNT RMV,1T1,DEN16,IDS,BUFSIZ/1604
The following example indicates that the files STATS and STATS1 are the SCF
files, which reside on mass storage.
1
6
1
8
$
ACCOUNT RDM,STATS,STATS1
$ DFILES Statement
The $ DFILES st~~~1~~~!!~~~'~!!?;~:b.J;!t,~t~J~,~:U}4~~ct:!:J,e"'C1,l;,~~"J2'~~~&~~~~~~~w!~~
s~9u~l.ltia:t.r~le \lD.~~rS~~ ~A'r.. It allows GEIN to read $ DTFILE related JCL
statements', 'as' 'de'scribec{'Tn"';"n"$ DTFILE/$ ENDTF Statements" earlier in this
section.
The format for the $ DFILES statement is:
1
8
1
6
$
DFILES
ffffff
"'e:
References the file name of the DTFILE described in the $EDIT
~t1on (e.g., SYSPN).
5-118
DH18-03
,
)
$ LIBRARY Statement
The $ LIBRARY statement identifies one or two files to use as system
lib~. They are searche'd-by'tne··"tfenera'I,,·t'oa:aer'''hpr6gram'~aurl''iig'')iilrogram
roading. One file defines the System Subroutine Library (L*); the second file
is optional and defines the User Subroutine Library (*L), also referred to as
the Secondary Subroutine Library.
The L* file contains high-use subroutines required for execution of major
software packages. The *L file usually contains smaller, less frequently used
subroutines. Consequently, the L* file normally is configured on a faster
device than the *L file. If configured, the *L file is searched before the L*
file.
File sizes and the device on which each file resides must be specified on the
$ FILDEF statement in the $EDIT section. If the L* and *L files are
configured, they must reside on the same type of storage medium (i.e., both
files must reside on mass storage or both must reside on magnetic tape).
The format for the $ LIBRARY statement is:
1
6
1
8
$
LIBRARY RDM,fffff[,RDM,ggggg]
where:
fffff - File name of the System Subroutine Library (L* file).
ggggg - File name of the optional User Subroutine Library (*L file).
RDM
- Must precede the file name (fffff and ggggg) to identify the file as
a random file.
5-119
DH18-03
The following example indicates that a one-llink system subroutine library
named SYSTEMLIB is to be created on mass storage device DS5. In addition, a
one-llink user library named USERLIB is created on mass storage device Ds6.
1
1
8
6
FILDEF
FILDEF
DS5,SYSTEMLIB,1,RDM
DS6,USERLIB,1,RDM
$EDIT
$
$
$FILES
$
LIBRARY RDM,SYSTEMLIB,RDM,USERLIB
-5-120
DH18-03
c
$ MODOPT Statement
The $ MODOPT statement provides a means for specifying parameters for
initialization of GCOS modules:"Th'e"parameters"'~>r'rom"'"<€n"e"'$"'NC)T)'On-S't'atement(s)
are'-passe'a"to"-eaC'Fi"'ae8!ilrfat'~~d" module at module initialization time so that the
module can verify the parameters and perform initialization according to the
parameters.
The format for the $ MODOPT statement is:
1
1
8
6
$
MODOPT
.Mxxxx{,keyword[={value
}]}
{
[ {(value, ••• )}] ••• }
{/{type}
}
}
{ {(type,name)}
where:
.Mxxxx
- The GECALL name of the module, used to generate the module
number. The symbol .Mxxxx must have been previously defined by a
system macro such as .MDDEF.
keyword - Keyword identifying a parameter to be initialized. Tte valid
keywords, and associated values for each module are listed below.
value
- May have one of the following forms, and may be further limited by
the module being initialized.
string
- Any sequence of characters except space, quote (n),
equal, left parenthesis, right parenthesis, or
comma. Note: slash is allowed.
nD_Q_stringn - Any sequence of characters. A quote (n) may be
contained within D Q string by using two successive
quotes (nn).
--
5-121
DH18-03
type
- { 000000
}
{ [R][P]{HSSAIFSSAISSSAIGHCMISHCM} }
{{NULL!RIPIRPIPRIAPRGINPRGISPRG} }
000000 - Octal value for module entry information, SD.MDD bits
0-17
- Required
R
P
- Privileged
NULL
- To reset required and privileged modes
- Half SSA (512 words)
HSSA
FSSA
- Full SSA (1024 words)
SSSA
- Shared SSA
GHCM
- Grouped HCM
- Segmenting HCM
SHCM
APRG
- GCOS-type program
- RU-type program
NPRG
SPRG
- Shared program
name
A new GECALL name to put in the GECALL name table instead of the
macro generated name. If this option is used, no patch card or
later $ MODOPT references can be made to the old name; it will
cease to exist as far as the system is concerned for accesses by
module name. Note that any macro generated calls will have been
assembled and will be executed by the module number and not the
GECALL name.
INITIALIZATION PARAMETERS FOR .MDNET
1
186
$
MODOPT
.MDNET,{TRACE_TYPESITRACE}={OFFIONlbbbbbl({OFF(ON}[,n ••• ])}
where:
OFF
- No trace.
ON
- Enable all trace types.
bbbbb
- Disable trace types 1 thru 13 (i.e., 47204 bit mapped equals
100111010000100 which would disable trace types
1,4,5,6,8,13). (Format of the old patch card).
Memory for trace is released.
Default.
OFF,n[,n ••• ] - Turn off trace type n, where n = 1 thru 13.
OH,n[,n ••• ]
- Turn on trace type n, where n = 1 thru 13.
5-122
DH18-03
$
HODOPT
.HDNET,{NUMBER_TRACE_ENTRIES I TRCSZ}=nnnn
\
)
where:
nnnn - Specifies the number of entries (decimal) in the trace table.
Default/Minimum = 80; Maximum = 1023. (If TRACE=OFF is used, there
will be no trace table.)
MODOPT
$
.MDNET,{MAX_CONCURRENT_REMOTE_INQUIRIES I RMIQT}=nnn
where:
nnn - Specifies the number of entries (decimal) in the Remote Inquiry Name
Table (N.AME). Default/Minimum = 40; Maximum = 255.
MODOPT
$
.MDNET,{MAX_GENERAL_STATUS_PROGRAMS I GENSTS}=nnn
where:
nnn - Specifies the number of entries (decimal) in the General Status
Inquiry Table (GE.STS). Default = 40; Minimum = 0; ~Aximum = 255.
$
MODOPT
.MDNET,{RESERVE_MAILBOX_7
RSMB7}={YESINO}
where:
YES - Reserve mailbox 17 for Front-end Network Processor (FNP).
NO
- Defaul t •
$
MODOPT
.MDNET,{RECONNECT TSS AFTER SLAVE DISCONNECT
RECDIS}={YESINO}
-
where:
YES - Indicates that the automatic reconnect to TSS upon Disconnect Request
(MME GEROUT 17) from a DAC process is desired. If the line originated
from a TSS copy, an attempt will be made to return the line to that
originating TSS copy and UST for continued service. If the
originating copy is not available or if the line did not originate
from TSS, the line will be disconnected.
NO
- Disconnect the line when a DAC program issues a GEROUT 17.
Default.
\
/
5-123
DH18-03
$
MODOPT
.MDNET,{TSS_LOAD_FACTOR
TSSLF}=n
c
where:
n - Specifies a value from 0-9 (decimal) representing the load factor that
will cause additional users (i.e., logons) to be assigned to another
executing copy of Time Sharing. The default value is 6.
A value of 0 indicates that users are to be assigned to all executing
copies of Time Sharing on a round robin basis.
$
MODOPT
.MDNET,{CHECK_FOR_DNET_BUSY I CKBSY}={ONIOFF}
where:
ON
- Enables scan of the line table for an FNP at the end of interrupt
processing. Search is made for GS.DBS (DNET Busy Bit) left on any
line on the FNP. If found, system will abort. USED FOR DIAGNOSTIC
PURPOSES ONLY.
OFF - Default.
MODOPT
$
.MDNET,{I/O_TRACE
IOTRC}={OFFION}
where:
ON
- Enables the trace of changes in .SRQCT, which is a count of I/O
requests and requests in transmission for a process. USED FOR
DIAGNOSTIC PURPOSES ONLY.
OFF - Default.
INITIALIZATION PARAMETERS FOR .MDSX6
1
186
$
MODOPT
.MDSX6[,TMPFIL=(xxx,xxx[,xxx] ••• )[,SYSFIL=(xxx,xxx[,xxx] ••• )
where:
xxx
- Each element in the lists is a logical device name. Each device
name may appear in one or both lists. All devioes speoified must
be mass storage devioes configured as PERM. None of the devices
may be configured as RMVBL. At least two physical units must be
included in eaoh list.
5-124
DH18-03
TMPFIL - The devices in the TMPFIL list are used to satisfy requests for
disk space for temporary files ($ FILE or MMEGEMORE), Test Mode
collection space, Remote Job Input (RGIN) space, backing store
files, swap files, and pushdown ($8) files. If the TMPFIL list is
specified, it must include at least two physical units. If the
TMPFIL list is not specified, the TMPFIL pool will consist of all
PERM devices.
SYSFIL - The devices in the SYSFIL list are used to satisfy requests for J*
and *J files and for the GEIN $ SELECT pushdown file (i.e., any
request for temp space that originates from .MGEIN) plus the J$ and
$J files, system recovery and cleanpoint files and System Scheduler
Unpurge (SSUP) work space.
The devices in the SYSFIL list are also used during file grow. If
a MME GEMORE to grow a permanent file requires crossing to another
device (because the current device has insufficient unused llinks),
AS06 allocates space from a device in the SYSFIL list selected by a
round robin algorithm. SD.MSD contains an index to the next device
to be tried for allocation. After each try, whether successful or
not, the index is advanced to point to the next device in the list.
The catalog thresholds ($ INFO FMSST, FMSCT, and FMSDT) are in
effect only when a file is created or restored. During file grow
these thresholds are ignored.
It is recommended that the devices in the SYSFIL list not be
designated as $ INFO CAT so that FMS will not build catalogs on
those devices. The $ 10M/lOX NOFMS option may be specified for
devices in the SYSFIL list; thus those devices would contain
temporary file space, but would not contain FMS catalog or
permanent file structure.
If the SYSFIL list is specified, it must include at least two
physical units. If the SYSFIL list is not specified, the SYSFIL
pool will consist of all TMPFIL volumes.
The TMPFIL and SYSFIL pools may overlap; a PERM device may be in the TMPFIL
pool, the SYSFIL pool, both, or neither.
A temporary file may be placed on a PERM device not in the TMPFIL pool by
requesting that specific device on the $ FILE JCL record.
$ PFILES Statement
The $ PFILES statement igent,i:fj.es.
Star,1tuR-Q-r:ei,~;Ul,§~g"l>J~!-2a~alOj:;d ~y !:~e
~~iro~f~a~~~~~~$~'~~!6~t~~~17n!*ss*-r.~:snm ~
Startup-created files are identified on the $ PFILES statement, they cannot be
accessed. (Exceptions are all DUMP Files, which are automatically cataloged.)
5-125
DH18-03
A maximum of 79 files can be created by Startup via $ PFILES statements. If an
attempt is made to create more than 79 files, Startup aborts. The message:
-UNABLE TO PFILE (file name)
-MORE THAN 79 PFILES AND DFILES
or
-UNABLE TO AUTOMATICALLY PFILE DUMPn
-MORE THAN 79 PFILES AND DFILES
will be output when the main.PFILE routine detects an overflow condition.
message:
The
FATAL ERROR IN $FILES SECTION CARD BELOW CONTAINS AN ERROR NEAR COLUMN xx
is issued to the console (where xx
= statement
column number).
The format for the $ PFILES statement is:
1
1
8
6
$
PFILES
ffffff
--------------------------------------
where:
ffffff - File name.
The following example identifies dump files to be used in dump-to-disk
opera.tions.
1
1
8
6
$
PFILES
DUMP',DUMP2
$ SAVE Statement
The logical device name of the mass storage device on which this file is to
reside and the file size may be specified on the $ FILDEF statement. This file
~t be_alJ.QQated Lminimum, 0t:. 24 l"~F.i§,
1
5-126
DH18-03
The format for the $ SAVE statement is:
1
1
8
6
$
SAVE
ffffff
where:
ffffff - File name (one-six characters).
The $ SAVE statement is needed only if the site wishes to move the save file
from ST1 or increase the file size to more than 24 llinks.
$ SCFBUF Statement
The $ SCFBUF statement is used in lieu of the $ ACCBUF statement and is found
in the $FILES section; this prov~des "extend~Q, aQcounting capabIIity.--Tt'·--........
o:efI'ile's"whrch-acc~unting record' types to buffer. The '$ SCFBUF'"'statemelit is
ToIIOweaon~SCFDSP S€atement'~
When operating under the Tape Management System (GTMS), up to 72 accounting
type records may be specified, including tape mount trace records written to
the SCF. This record is produced only when the privileged slave prosram $GSYS
is executing in debug mode. The record type created is 28 (octal 34).
The $ SCFBUF statement format is:
1
8
1
6
$
or
$
SCFBUF
nnn,ALL
SCFBUF
nnn,REC/X(1),X(2) - X(n)
where:
nnn - Three-digit number defining the maximum accounting record type for
which buffering is done. The range of nnn is from 1-288.
ALL - Buffering for all record types (O-max.) has been selected.
5-127
DH18-03
REC - Selected accounting record types are to be provided buffering.
X(1), ••• X(n) are the record types which have been selected and are to
be stated in decimal. For example:
1
1
8
6
$
$
SCFBUF
SCFBUF
SCFBUF
36,ALL
36,REC/1-10,12,14,17-19,21,30-36
288,ALL
$
$ SCrDSP Statement
The formats for the $ SCFDSP statement are:
1
8
1
6
$
or
$
SCFDSP
nnn,ALL
SCFDSP
nnn,REC/X(1),X(2), - X(n)
where:
nnn -
Three-digit number defining the maximum accounting record type whose
status can be changed from the console. This must match nnn of the
$ SCFBUF statement.
ALL -
All accounting record types can have their status changed via the
console.
REC -
Accounting record types X(1), ••• X(n) have been selected for console
status change capability. X(1), etc., are decimal values. For
example:
5-128
DH18-03
$ SSLOAD Statement
The $ SSLOAD statement further ....~~!~ne~ ~~~e,var~ou~ Syste~_ '"~_~~~~~t-.p.rg£~-i.~~='"
classes initially intrggyQe.a:_,-in,_.,.tb,~:I@Ir; . }?~.~~ion on' the' $ SSFILE stat.~m,~,~t.
Tha$ ssr,C)Ai)""stitement specifies the maxim\iD·"'numbe'r>~·of·~Jobft'tlia"'£-c;art'"·b·;;'\~·'~" .;o"w"",.".~
scheduled from each class at one time. This statement also specifies the
maximum and minimum number of jobs from all job classes that can compete for
system resources (i.e., peripheral devices, memory, and processor time) at any
one time.
The site can influence its processing workload and job scheduling through
judicious use of $ SSLOAD statement parameters. Values specified for these
parameters are unique to each site. No one value can be suggested as a norm
for each parameter and no default values are assigned by Startup. Two
recommendations can help establish parameters that best apply to each site.
1. Site techniques personnel must have a good working knowledge of the
site's processing profile.
2. Site techniques personnel can experiment with the three types of
parameters (i.e., system maximum, system minimum, and class maximums) to
determine the combination of values that provides optimum throughput.
Manipulation of these values - especially manipulation of the system
maximum value - can produce favorable results.
The format for the $ SSLOAD statement follows. Note that definition of
parameters is not required for the .HOLD class.
1
1
8
6
$
$
SSLOAD
ETC
MAX/xx,MIN/yy[,.TASK/nn][,.TRANS/nn],.EXPRS/nn,
.user/nn[,.cccc/nn],.TS8/nn
where:
MAXI xx
- Maximum number (xx) of program numbers available for processing
jobs from all classes at one time. This value specifies the
number of jobs the System Scheduler program will pass to the
Peripheral Allocator program to compete for resources at anyone
time.
MIN/yy
- Minimum number (yy) of jobs that can be active before the System
Scheduler program invokes individual class maximum values in the
scheduling algorithm. If the total number of active jobs is
less than this value, scheduling is based on the following:
1. Schedule any available job in the express class.
2. If there is no available express class job, schedule a job regardless of its user class - on a first-in, first-out
basis.
5-129
DH18-03
3. Return to the express class to schedule any available job.
When establishing this value (yy), consider the following:
1. Do not set the value so high that if the number of large jobs
available is equal to the system minimum value, all resources
would be assigned to those jobs (thereby denying resources to
any other jobs entering the system).
2. ,If the value is 0, the class maximums for all jobs are
strictly enforced. There is no override of class maximums
and only the number of jobs specified by the class maximum
values are run •
•TASK/nn
- Maximum number (nn) of jobs that can be aSSigned at anyone time
via DRL TASK directives in the Time Sharing System. This field
is requir.ed only if the site has Time Sharing System
capabilities •
•TRANS/nn - Maximum number (nn) of Transacti'on Processing Applications
Programs (TPAPs) that the Transaction Processing Executive
program can have spawned at anyone time. This field is
required only if the site has Transaction Processing
capabilities •
•EXPRS/nn -Maximum number (nn) of jobs that can be active at anyone time
from the express class •
•user/nn
- Maximum number (nn) of jobs that can be active at anyone time
from the required site-defined class (.user) •
•cccc/nn
- Maximum number (nn) of jobs that can be active at anyone time
from the optional site-defined class (.cccc). A maximum of 49
optional classes can be defined (on the $ SSFILE statement).
This field must be specified for each class defined on the
$ SSFILE statement •
•TS8/nn
- Maximum number of jobs that can be active at anyone time from
the .TSS class. The value nn should be the same as the value
specified for the TS8 Initialization file directive MAXIMUM
USERS.
The following example indicates that a maximum of 10 jobs (MAX/10) from all
defined job classes can be scheduled (i.e., compete for system resources) at
anyone time. A minimum of five jobs (MIN/5) from all defined job classes can
be active at anyone time before the System Scheduler program invokes
individual class maximum values in the scheduling algorithm. The maximum
number of jobs that can be assigned from the various job classes are: .TASK
(10); .TRANS (10); .EXPRS (5); required user class .USER1 (1); and optional
user classes •USER2 (3), • USER3 (1), • USER4 (1), •USER5 (1), and •USER6 (1).
5-130
DH1S-03
1
1
8
6
$
$
SSLOAD
ETC
MAX/10,MIN/5,.TASK/10,.TRANS/10,.EXPRS/5,
.USER1/1,.USER2/3,.USER3/1,.USER4/1,.USER5/1,.USER6/1
$ SYSOUT statement
The $ SISOUT statement sp~ft-i.J1,~~_j;,J}~",.P~e.~"",of"."t~.lg~<~~;;~~tJ9,t"J;;Jt~,"9",2il~ion
(i.e., spooling) "~f","~J.:~~~_~,,,--~~~P~tM~.~,,~~P,~.=~.~~e. A-.maximum of 64 files can
be se,E!.cified.
All files_,,§hR'tl-d b~~~. .~~~. .e. The logical device name of the mass
storage device on which the file is to reside and the file size are defined via
the $ FILDEF statement. If the sizes of all. files named in the $ SISOUT
statement are not the same, the smallest value specified on a $ FILDEF
statement is allocated on each device. For example, ·if 100 llinks are
specified for all devices except one on whioh 50 llinks are specified, only 50
llinks are used on all devices.
Specification of SYSOUT collection space requirements allows site management to
define its particular needs according to the site's processing environment.
The format for the $ SYSOUT statement follows:
1
186
$
SYSOUT
ffffff,ffffff, ••• ,ffffff
where:
ffffff
File name (one-six characters). A maximum of 64 files can be
identified for SYSOUT collection purposes. These are all defined
in one $ SYSOUT statement or a $ ETC continuation of that
statement.
$ SYSTEM Statement
The $ SYSTEM statement id,entlfies each file containing.system modules and
fU1:.Wt.e.m-:sha~~~&t,L~..~~.!!:~~"!!!~§.;!lli~ferat·~on~. -Thes'e'"'7iIe' "namesare
written to in-memory tables. The sJ.ze of e~ defined on the $ SYSTEM
statement and the device on which the file resides must be specified on a
$ FILDEF statement in the $EDIT section. The RUP, SWI, or SYS parameter. must
be included on the $ FILDEF statement for each of these system or shared
software library files.
)
5-131
DH18-03
A maximum of 32 system files can be defined. If more than 32 files are
specified, Startup aborts. While the $ SYSTEM statement normally identifies
the names of all files specified on a $ FILDEF ••• SYS statement, this is not
always the case. Some sites may have more than one version of system
software. In,these instances, $ SYSTEM statement definitions may not include
all files specified in the $EDIT section.
Multiple file names can be specified on one $ SYSTEM statement.
the $ SYSTEM statement is:
The format for
1
$
8
6
SYSTEM
fffff
where:
fffff - System file name.
The $ SYSTEM statement can also be used either to replace existing system
modules, or to add system modules to the content of the existing system file by
employing a technique called an insert-edit. This technique expediently
updates one or more software modules resident on the system files and, because
it is an alter only update, eliminates the need to re-edit the entire system.
Although the number of program executions is no fewer than when performing a
total edit, the selectivity of the insert-edit reduces the scope of the edit by
minimizing the number of modules involved in the editing process.
A replacement file can have a unique file name, or it can retain the name of
the file being replaced or modified. In addition, all other files containing
system programs and remaining in effect must also be specified on the $ SYSTEM
statement for the insert-edit.
The sequence in which the new or replacement files and the existing files are
defined on the $ SYSTEM statement(s) is important so that Startup can identify
and replace an existing file with the replacement file, or insert a new file.
Systems statements defining new system files should appear first. Replacement
file names should immediately precede the preexisting system file name being
replaced. This allows site personnel to easily identify the system files
involved in modification.
If it appears that the Startup program has not inserted a new file or replaced
an old file following an insert-edit, check the order of appearance of system
file names on the output list of the $ SYSTEM statement(s). If improperly
sequenced, rearrange them as required to produce the desired results and
reboot.
In the following example, replacement file NEW-SOFT contains system programs
that are to replace programs residing on existing file, VS-PRlMARY. Other
files containing system programs that are not involved in the replacement
procedure are identified on $ ETC statements.
5-132
DH18-03
1
1
8
6
$
$
$
$
SYSTEM
SYSTEM
SYSTEM
SYSTEM
NEW-SOFT
VS-PRIMARY
TSS-SUB-SYS
SOFTW-PART1
$PATCH SECTION
The $PATCH section r vides a means by which corrections can be a
pro rams and to software programs that were edited by Startup onto the sys em.
Corrections canno
e app ied via the $PATCH section to programs added to the
system via a File Management Supervisor (FMS) restore function. (Refer to the
GCOS 8 OS File Management Supervisor manual for a description of restore
procedures.)
Four types of patch corrections can be applied via the $PATCH section:
o OCTAL correction statements to replace the contents of specific module
locations
I
o OCTAL correction statements to add to the contents of a module
o OCTAL correction statements which are site-option patches. Site-option
patches allow the site to select specific operating parameters for its
system software modules and programs. Each of the valid site-option
patches is described later in this section, under "Site-Option Patches".
o
PATCH RUN UNIT statements which are applied as corrections to run units
that are part of the Seed Workspace Image (SWI)
Corrections applied via the $PATCH section do not affect the content of the
total system software tape. Patches can be edited onto an unpatched total
system software tape via the Patch Editor (PAED) program. (Refer to the GCOS 8
OS Service Routines manual for PAED program procedures.)
Corrections to the Startup program and the Startup job stream content are not
applied via the $PATCH section. Among these types of corrections are:
o
MASK statements that correct the Startup module (.MINIT).
"Patching Startup Program" in Section 3)
(Refer to
o OCTAL statements that correct the MPC Bootload module (.MMPCB).
to "$INITIALIZE Section" earlier in this section.)
(Refer
o HEX statements that correct firmware data decks. These statements are
CHEX (control store) and RHEX (read/write memory) statements. (Refer to
"$INITIALIZE Section" earlier in this section.)
o
OCTAL statements that correct modules loaded via the $LOAD section of the
Startup job stream. (Refer to "$LOAD Section" later in this section.)
5-133
DH18-03
I
Application of Patches
Patch corrections included in the $PATCH section are written to a main memory
table during system bootloading. This table is accessed each time a GCOS or
software program/module, for which patches exist, is loaded into memory from
system storage. All applicable patches are applied to the program/module while
it is in memory.
Programs/modules eligible for patching via the $PATCH section are identified in
either the Module Directory Table or the Module Name Table. (These tables are
pointed to by the SD.MDD and the SD.MNT segment descriptors, respectively.)
Table info~ation includes the address of the program/module loaded from system
storage and an indicator denoting whether any patches exist in the patch table
for the program/module.
I
The patch table is initialized each time the system is bootloaded. Only the
content of the $PATCH section for that bootload is written to the table.
Therefore, only current corrections exist in the table. Also, any OCTAL
correction statements or PATCH RUN UNIT statements that were removed from the
$PATCH section are eliminated from-the table.
There is no limitation to the number of patches that this table can
accommodate. However, it is recommended that the site consider the following
when determining the number of patches to include in the $PATCH section (i.e.,
in the patch table):
1. The entire patch table is scanned each time a system program is called
into memory. An abundance of patches could impact system performance if
a significant amount of time is required to complete this scan.
2. Each patch correction occupies two words of main memory.
Slave Service Area (SSA) modules are limited in size. This limitation must be
considered when applying add-on patches that expand the size of the module.
Each main memory (HCM) module contains space for patches and patches must not
overflow this space, or an error condition may result (e.g., the module may not
execute properly).
Note that if the job calling for a program/module includes a $ EXTEND control
statement in its job control language, patches from an E* file also must be
applied while the program/module is in main memory. If patches for the same
program/module location exist in both the $PATCH section and on the E* file,
the E* file patches override 'PATCH section corrections for that location. In
addition, programs on a ** file can be patched only via the E* file. (Refer to
the GCOS 8 as Service Routines manual for procedures to create an E* file and
for the E* file format.)
5-134
DH18-03
OCTAL Statement Format
~
I
The name of the program/module to be patched, the location at which to apply
the correction, and the correcting data are specified on an OCTAL correction
statement. Only the fields containing this information - as well as the field
containing the OCTAL identifier - are recognized by Startup. While other
information can be included on the statement, it is for documentation purposes
only, and ignored by Startup.
The format for the OCTAL statement is:
3
2
7
6
vvvvvvvvvvvv
cccccc
nnnnnn
1
1
8
aaaaaa OCTAL
3
where:
aaaaaa - Module/program address (octal) at which to apply this correction.
This value must be left-justified and cannot exceed six digits. If
more than six digits are specified, patch data may be applied to
the wrong location.
Patches must be floatable. The address in field aaaaaa (as well as
an address in field v ••• v) must not require relocation prior to
execution of the module. For example, if patching location 12122
(the offset begins at location 12000), the address specified must
be 12122 and not relative address 122.
v ••• v
- Patch correction data (octal) to be applied at module/program
location aaaaaa. A maximum of 12 digits can be specified. If more
than 12 digits are specified, erroneous data may be applied at
location aaaaaa.
A single' OCTAL correction statement can contain more than one patch
correction. However, each correction on the statement is counted
as one patch occupying two words in main memory_
Inclusion of leading zeros in the above fields is optional.
cccccc - Patch-related comments. These comments can extend from column 32
through column 72. Information often specified in this area
includes comments describing the code or patch function, the number
of the SER describing the error, the library number, the edit name
of the module being corrected, the TTL date, and the number of the
transmittal describing the correction.
nnnnnn - Program/module name. If this is a GCOS program/module, nnnnnn is
the BCD catalog name in the format .Mmmmm (where mmmm = edit name
of the module). For example, .MALC1 defines the ALC1 (Peripheral
Allocator program) module.
\I
V
5-135
DH18-03
If this is not a GCOS program/module, nnnnnn is the MME GECALL name
(e.g., a System program/module such as COBOL, GELOAD). The maximum
length of this name is six characters.
In both cases, the name nnnnnn must be the same as the name used
when the file containing the program/module was created in
system-loadable format. (This name is specified in the CATALOG=
field of the $ SYSLD JCL statement for the System Library Editor to
use when editing the program/module onto system storage.)
The following OCTAL correction statement defines patch information that is to
be applied to location 23562 of the Peripheral Allocator program (.MALC1
module).
8
1
23562 OCTAL
1
6
5
4
3
2
10604004
TMI TRYCH 1 ,$
'---'
~
\.
Octal
Address
Octal
Data
Patch-Related
Comment
I
I
"'"1
I
7
3
101071ALC140918122E.MALC1
'---'
)
SERI
'-.-J~,---,
I
1
Edit TTL
Name Date
Library
Number
I
Catalog
Name
Transmittal
Log Number
Four errors are commonly associated with use of the OCTAL correction statement:
1. Attempting to apply two OCTAL statements containing different patch
information to the same program/module location. Startup ignores the
second OCTAL statement encountered and issues the informational message:
.OVER-PATCH CARD BELOW IGNORED
to the system console.
message.
An image of the ignored statement follows the
2. Attempting to apply two OCTAL statements containing the same patch
information to the same program/module location. Startup ignores the
second OCTAL statement encountered and issues the informational message:
.DUPLICATED PATCH CARD BELOW IGNORED
to the system console.
message.
An image of the ignored statement follows the
3. Specifying a non-existing module name in either the Module Directory
Table or in the Module Name Table. Startup ignores the statement and
issues the informational message:
.PATCH CARD BELOW CONTAINS UNDEFINED PROGRAM NAME
5-136
DH18-03
C
to the system console.
message.
An image of the ignored statement follows the
4. Failing to begin the octal address or patch data in columns 1 and 16,
respectively, or including non-octal data in these fields. Startup
ignores the statement and issues the informational message:
.PATCH CARD BELOW CONTAINS ERROR NEAR COLUMN nn
to the system console (where nn = column in which the error begins).
image of the ignored statement follows the message.
An
Upon completion of $PATCH section processing by Startup, if any errors are
encountered, the operator is given the opportunity to either continue with or
abort the bootload. The message:
.ANSWER YES TO CONTINUE WITHOUT ABOVE PATCHES
is issued to the console. If the operator responds YES, Startup ignores the
statements in question and continues the bootload. If the operator responds
NO, Startup aborts. Remove or correct the statements in question before
reinitiating the bootload.
Another format of the OCTAL statement allows a contiguous sequence of
data-words to be given on one statement; i.e.,
22
OCTAL
0,0,0,0
means patch four contiguous words starting at address 22.
PATCH RUN UNIT Statements
PATCH RUN UNIT (or PATCH RU) statements in the Startup job stream are only
1. The run unit to be patched is part of the Seed Workspace Image (SWI); and
2. A non-empty segment to contain these patches is provided via
$ INFO NPCHSZ/nnn.
Advantages And Disadvantages To $PATCH Section Use
In addition to the $PATCH section, patch corrections can be applied to GCOS
programs and software programs via the Patch Editor (PAED) program. As
previously indicated, the PAED program applies the patches to the total system
software tape. The following summarizes some of the advantages and
disadvantages to using the $PATCH section rather than the PAED program. (Refer
to the GCOS 8 OS Se,rvice Routines manual for PAED program procedures.)
5-137
DH18-03
ADVANTAGES OF USING $PATCH SECTION
The advantages of applying patches via the $PATCH section include its
flexibility and compatibility features.
1. Patch corrections are easy to insert into and remove from the Startup job
stream. For example, applicable patches can be manually inserted into or
removed from the $PATCH section to meet various configuration and
operational requirements. Corrections that are applied via the PAED
program are of a more permanent nature and, once applied, lose their
immediate visibility.
Because patch corrections are easily inserted and removed, the $PATCH
section approach is a good method for validating new patches. Once
validation is complete, the patches can be removed from the $PATCH
section and applied via the PAED program.
Temporary patches that are applied only once or for a short period of
time usually are applied via the $PATCH section. It also is recommended
that local patches be applied via the $PATCH section. Local patches are
patches generated by a site and are neither Honeywell Bull-generated
site-options nor officially released corrections.
2. All patches generated for use in the $PATCH section are fully compatible
with PAED program requirements (i.e., the patches are interchangeable).
With few exceptions, the patching results are the same under each
approach. (These exceptions are the specific programs/modules that
cannot be patched via the PAED program. If an attempt to do so is made,
the patches are rejected and the programs/modules are identified on a
report generated by the PAED program. The patches must be removed from
the PAED job stream and inserted into the $PATCH section.)
3. Some patches, primarily those that cannot be edited onto the total system
software tape via the PAED program, must be applied via the $PATCH
section. In addition, the $PATCH section must be used to apply patches
if the total system software tape has been patched. (The total system
software tape can be patched only once and cannot be used as input to
another PAED program edit.)
Also included among the patches that cannot be applied via the PAED
program are add-on patches, which are applied below the Lower Address
Limit (LAL) of the module being patched, and patches applied from a
common patch area. Patches included in a common patch area are below the
LAL of the individual modules.
Note that use of common patch space is more economical if the module
defines one or more common patch areas in the main overlay at the
lower-address end of memory. This common patch area can be in addition
to patch space within each overlay. All other overlays also can use this
space for needed add-on patches.
5-138
DH18-03
DISADVANTAGES OF USING $PATCH SECTION
The disadvantages of applying patches via the $PATCH section include the fact
that they encourage oversights, are time consuming, and corrections may be
misplaced.
1. Because this approach is easy to use, patch corrections often are not
well-planned. Inefficiencies or errors can result.
2. Each time the affected program/module is loaded into main memory for
execution, a series of events must occur before patches are applied.
(The Module Directory Table and the Module Name Table are searched, a
determination is made as to whether there are applicable patches, the
patch table is searched for the applicable patches, and patches are
applied to the program/module.) This consumes resources and increases
load time.
3. Because patch corrections are incorporated into a card deck that is
frequently used, cards often are lost, damaged, or inadvertently moved
outside of the $PATCH section. A patch residing outside the $PATCH
section may result in an error condition.
Changing_PAED-Applied Patches Via $PATCH Section
The $PATCH section can be used to modify/add/delete an existing patch that was
applied via the PAED program. It is recommended that this approach be used
only as an emergency procedure and for testing purposes. If the $PATCH section
is used for this purpose, conflicts may arise between the patches in the $PATCH
section and in the PAED job stream. Therefore, tight control must be
maintained and the replacement patches must be clearly defined.
The *C Editor (SCED) program provides an alternative to use of the $PATCH
section for the purpose of modifying/adding/deleting PAED-applied patches.
(Refer to the GCOS 8 OS Service Routines manual for *C Editor program
procedures.)
o To modify an existing patch via the $PATCH section, create an OCTAL
correction statement containing the correct information and insert the
statement into the $PATCH section. The correcting patch will override
the erroneous patch that was applied via the PAED program.
o To delete an existing patch via the $PATCH section, prepare an OCTAL
correction statement for the affected location. (The original image can
be obtained from the ORIG. CONTENTS field of the most recent PAED run
report.) This statement resets the contents of the location to their
value prior to the PAED run. Then, insert the OCTAL correction statement
into the $PATCH section.
o To add a new patch via the $PATCH section, create an OCTAL correction
statement containing the desired patch information and insert the
statement into the $PATCH section.
5-139
DH18-03
S1te-opt1o~.!~tche8
A site can selectively apply special operating system parameters via OCTAL
correction statements. These statements and parameters are referred to as
site-option patches and are applied to GeOS system programs (modules) via the
$PATCH section. Applicable OCTAL correction (patch) statements for site-option
patches are defined below.
DISPATCHER OPTIONS
The site can manipulate certain parameters (factors) within the Dispatcher
algorithm to help meet processing objectives. The following site-option patch,
applied to location 100 of the .MDISP module, allows the site to adjust the job
urgency and 1/0 priority parameters.
7
1
100
8
6
OCTAL
wOOOxxyOOOOz
------------------------------------------)-----.MDISP
where:
w - Octal value that expands to:
Bit
0 =1, 1/0 ratio priority enabled
1 =1, Urgency priority control enabled
xx - Bits 14-17 specify the consecutive subdispatch count
y
- Octal value that expands to:
Bit
z
18 =1, Class B priority enabled
19 =1, Class A priority enabled
- Reserve an entry in the Dispatcher's queue (i.e., job priority table)
for a job that is to be given Class A priority via the console entry
APRIOR sssss (where sssss = SNUMB). The value z is the priority level
that is to be assigned to job sssss and can range from 1-5. If the
value specified is 0, the operator cannot assign Class A priority via
the console. '
Variations in the Dispatcher algorithm are:
1. Bits 0 and 1 can be varied to control dispatching.
o
1
Description
o
0
Dispatch according to the order in which programs are placed in
the Dispatcher queue (i.e., first-in, first-out basis).
o
1
Dispatch according to the adjusted urgency value for each
program, found in the process status (PST) segment.
5-140
DH18-03
o 1
1
Description
o
Dispatch according to the ratio of channel time to processor
time.
1
Dispatch according to the adjusted urgency value, found in the
process status (PST) segment, weighted by ratio of channel time
to processor time.
2. If bit 18 =1, Class B priority programs receive preference in main level
dispatches, subject only to the number of nonpriority dispatches
specified.
3. If bit 19 =1, Class A priority programs are dispatched according to their
priority level. The priority level ranges from 1-5 (1 is the highest).
Class A programs are given preference in courtesy calls and main level
dispatches. Total system throughput may be Significantly slowed in that
all other processing halts when this option is in effect. For this
reason, it is recommended that Class A priority be used only for programs
of extreme urgency.
Applying Class A Priority
)
A maximum of three Class A priority entries can
queue for specific SNUMBs. To reserve an entry
program must be identified via separate patches
respectively, of the .MDISP module. The format
be reserved in the Dispatcher
in this priority table, each
to locations 104, 105, and 106,
for these patches is:
1
8
6
7
3
aaa
OCTAL
ssssssssssOp
.MDISP
1
where:
aaa
- 104, 105, or 106.
s ••• s - SNOMB of the program being given Class A priority.
p
- Priority level (1-5).
Inclusion of a SNUMB in locations 4-6 (OCTAL) of .MDISP does not necessarily
invoke Priority A. The presence of a SNUMB only causes DISP initialization to
include the job in the priority job table. Its pOSition in the table is
determined by the value of bits 30-35.
To assign Priority A, call wDISP,22n either through program initiation via
• CALL , or by the operator issuing an APRIOR console verb. The APRIOR verb can
only be used, however, if location 0 of .MDISP contains 01-05 (OCTAL) in bits
30-35. These bits -should differ from the value of bits 30-35 in words 4-6, as
this level indicates the position of the operator entry into the priority
table, of which there is only one.
5-141
DH18-03
If a job with a SNUMB in locations 4-6 does not generate a .CALL DISP,22, an
APRIOR console verb must be used to initiate Priority A, as APRIOR uses the
reserved operator entry. Inclusion of a SNUMB in locations 4-6 is only
necessary with TSS or TDS, neither of which call DISP,22.
NOTE: The APRIOR DELETE console verb only affects those jobs executing with A
Priority as a result of the operator entering an APRIOR console verb. A
job which calls DISP,22 cannot be removed via the APRIOR console verb.
The call must be made within the job.
Applying Class B Priority
A maximum of three programs, which can include Transaction Driven System (TDS),
Transaction Processing System (TPS), and Time Sharing System programs, can be
given Class B priority. (The patCh format for TSS and TDS applications is
given below under "Assigning Class B Priority To Time Sharing Copies And
TDS.") Each of these programs must be identified via separate patches to
locations 101-103, respectively, of the .MDISP module. The format for the TPS
patch is:
1
8
6
7
3
aaa
OCTAL
ssssssssssdt
.MDISP
1
where:
aaa
- 101, 102, or 103.
s ••• s - SNUMB of the program being given Class B priority.
d
- Number of dispatches permitted to jobs without Class B status
(between dispatches to jobs with Class B status). The default value
is 7.
t
- Time quantum (i.e., time slice), in 32-millisecond units, for each
job with Class B status. If this value is 0, a standard time
quantum is applied. The default value is 92 milliseconds.
Class B priority is given to a program only when that program calls entry point
21 of .MDISP. Time Sharing System, TPS, and TDS programs issue this call
during their initialization.
5-142
DH18-03
Assigning Class B Priority To Time Sharing Copies And TDS
The following site-option patch can be used to assign Class B priority:
1. To all configured copies of Time Sharing and/or
2. To all Transaction Driven System (TDS) and DM-IV Transaction Processing
programs. Separate patches are required if Class B priority is applied
to Time Sharing as well as TDS and DM-IV Transaction Processing.
If multicopy Time Sharing is configured, this patch must be applied.
priority is assigned to all copies.
Class B
1
7
1
8
6
3
aaa
OCTAL
xxxxxxOOOOOO
.MDISP
where:
aaa
- 101, 102, or 103.
xxxxxx - 632462 for TDS and 636262 for TSS.
WRAPUP CONTROL
The following site-option patch to the .MBRT1 module can be used to
enable/disable a wrapup request after an abort caused by an SSA module:
44
1
7
8
6
3
OCTAL
n
.MBRT1
where:
n
n
= Zero
= Nonzero
- Disable wrapup request if abort was caused by SSA (default).
- Enable wrapup request if abort was caused by SSA.
NOTE: Enabling the wrapup request may make file-system-related sensitive
information such as userids, passwords, etc., available to unauthorized
slave processes.
5-143
DH18-03
PERIPHERAL ALLOCATOR OPTIONS
A site can alter the disposition of several Peripheral Allocator functions by
applying the following site-option patch to the .MALC1 module:
1
7
1
8
6
3
100
OCTAL
nnnnnnnnnnnn
•MALe 1
The nnnnnnnnnnnn field is a 12-character octal code defining the following
functions. If a bit is set (=1), the corresponding function is enabled:
Bits
o
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17-25
26-29
30-31
32-35
Function
No GET message is issued to the system console for magnetic tapes.
No GET message is issued to the system console for local batch jobs.
No HOLD/LIMBO/REST/SIEVE messages are issued to the system console.
No OVERDUE message is issued to the system console.
No GET message is issued to the system console for a print train.
No activity restart is performed.
Nine-track magnetic tapes are standard.
No circular allocation of magnetic tape handlers is to be performed.
No job sieve limits are to be applied.
No BMC spinoff is to occur; BMC activities are run in sequence.
No print banners are to be printed on output generated on the device
defined on a $ PRINT statement.
Peripheral Allocator program debug mode. If the Peripheral
Allocator initiates a fault, a system failure occurs and a master
mode dump is taken.
No GET messages are issued to the system console for disk packs.
No automatic restart from checkpoints is to be performed.
No "GRANT" command required for privity job.
Used by GCOS for $ SHRNM.
User wants "-n" appended to SYSPN SELECT filename, where n = system
number.
Reserved for GCOS.
This field is used for information only. It contains the system
high-density code for magnetic tape, obtained from .CROPT, which is
initialized at System Startup (from $ INFO DENxx). Any data
included on the site-option patch in this field is ignored.
Reserved for GCOS.
This field is used for information only. It contains the system
low-density code for magnetic tape, obtained from .CROPT, which is
initialized at System Startup (from $ INFO DENyy). Any data
included on the site-option patch in this field is ignored.
The system denSity codes for magnetic tape are:
01 02 04 -
200 bpi (bits per inch)
556 bpi
800 bpi
11 - 1600 bpi
14 - 6250 bpi
5-144
DH18-03
SUPPRESS CONSOLE MESSAGES AT REEL SWITCH TIME
If a multireel tape file is being written via GFRC and an alternate tape drive
is in use, this option can suppress the "LOCATE SCRATCH ••• " and "VERIFY
SCRATCH" messages, provided that the tape mounted on the alternate drive has a
proper header label.
The format for this site-option patch is:
1
7
1
8
6
3
1
OCTAL
777777625012
.GLLMO
NOTE:
The use of this option will remove all operator interaction at reel
switch time, provided that the tape mounted on the alternate drive
has a readable header label. If the wrong tape was accidently
mounted, it will be overwritten unless it generates an "OHLR ••• "
message for unexpired retention, etc.
RELEASE DISK SPACE
The site can check the Master Available Space Table (BIT MAP) for temporary
space to be released or to release space on any descriptor, AST, or BIT MAP
error with the following patch:
1
1
8
6
7
3
7
OCTAL
uuuuuullllll
.MALC9
where:
uuuuuu -
O. Requests temporary BITMAP check. Temporary space is to be
released providing it is not marked as permanent space in the
Master Available Space Table (BIT MAP).
111111 -
~
~
O.
ZOP any descriptor error, AST error, or BITMAP error.
5-145
DH18-03
FMS TABLE SPACE FOR DUPLICATED FILE OR TEST MODE ALLOCATIONS
The site can modify the default size (5K) of the table that is used for
duplicate file control or test mode allocations by applying the following
patch.
1
8
6
7
3
36
OCTAL
'OOOOnnOOOOOO
.MFSEX
1
where:
nn - Number of 1K (1024 word) blocks of memory to be reserved. Requests for
greater than 31K will be reduced to that value. In general, eight
allocations can be made in each 1K block.
36 - Symbolic location CMBLK.
MEMORY ALLOCATOR OPTIONS
Several site-option patches can be applied to the .MPOPM module to control such
functions as magnetic tape positioning, trace table size, mass storage device
preference, or change the $ IDENT, $ SELECT, or $ USERID images for console
spawned jobs. These functions and the patch card formats are described below.
Magnetic Tape Disposition At .MPOPM Rollcall
The site can control the positioning of magnetic tapes during the .MPOPM
module's rollcall function. If no site-option patch is applied, tapes are
rewound and placed in a ready condition. If the following site-option patch is
applied to location 27 of the .MPOPM module, tapes are rewound and placed in a
standby condition:
7
1
1
8
6
27
OCTAL
720000020001
3
.MPOPM
Statistical Collection Tape Disposition At .MPOPM Rollcall
The site can control the positioning of the statistical collection tape (SCT)
during the .MPOPM module's rollcall function. SCT positioning also may be
dependent upon the operator's response to the .SCF CONTINUATION? question
during Startup's question-and-answer sequence. The following optional
approaches are available:
1. A response of NO to the .SCF CONTINUATION? question overrides any
site-option patch to location 26 of .MPOPM. The SCT is rewound and left
in a standby condition.
5-146
DH18-03
\
2. A response of YES to the .SCF CONTINUATION? question and application of
the following site-option patch to location 26 of .MPOPM results in the
SCT being left in a ready condition and available to continue statistical
collection. (Note that the tape is not rewound.)
8
6
7
3
OCTAL
400000020001
.MPOPM
1
26
3. A response of NO to .SCF CONTINUATION? and no site-option patch to
location 26 of .MPOPM results in the SCT being rewound during the .MPOPM
rollcall function. The tape is left in a ready condition and is
repositioned to continue statistical collection.
Trace Tables
A site can maintain both a primary and a secondary trace table.
entry in these tables comprises four words.
Each trace
The primary trace table by default accommodates 511 entries. The following
site-option patch can be applied to modify the number of trace entries the
table can accommodate:
1
7
1
8
6
3
24
OCTAL
OOOOOOOnnnnn
•MPOPM
where:
nnnnn - Number of entries the primary trace table can accommodate.
maximum of 4096 (10000 octal) entries can be specified.
A
A secondary trace table can be specified when trace entries are written to
magnetic tape. By configuring two trace tables, a double-buffer effect
results. While a trace entry is being written into one of the tables, another
trace entry is being read from the other table and written to magnetiC tape.
Under these circumstances, both the primary and secondary tables must
accommodate 1024 entries (i.e., a total of 2048 entries).
7
1
1
8
6
25
OCTAL
OOOOOOOnnnnn
3
•MPOPM
where:
nnnnn - Number of entries that the secondary trace table can accommodate. A
maximum of 4096 (10000 octal) entries can be specified. The default
value is 0 (zero).
5-147
DH18-03
Mass Storage Device Type Preference List
The following site-option patch, when applied to location 31 of the .MPOPM
module, permits a site with multiple types of mass storage devices to specify
its own preference list of device types for device allocation. The patch
contains a preference-ordered list for allocating the different types of mass
storage devices. (This list is similar to a user's device type request on a
$ FILE statement.)
The variable field can specify up to six device codes. The position of a
device code in the variable field determines the order of preference (i.e., the
most desirable device type is specified in field aa, followed by device types
bb, cc, dd, ee, and ff). If fewer than six fields are used, unused fields
(i.e., low-order fields) must be zero-filled.
1
8
6
7
3
31
OCTAL
aabbccddeeff
.MPOPM
1
where:
aa, bb, cc, dd, ee, ff - Device codes (octal).
Device
Code
Device Type
MSU0400 or MSU0402
MSU0451
MSU0500
MSU0501
MSC1A (64-word sector format)
MSC1B (512-word sector format)
MSD1A (64-word sector format)
MSD1B (512-word sector format)
MSM1A (64-word sector format)
MSM1B (512-word sector format)
MSM1E (512-word sector format)
64
65
66
67
73
53
75
55
42
41
74
This patch to .MPOPM ~oes not take effect unless round robin device allocation
is bypassed via the following patch to .MALC6:
1
8
6
7
3
16
OCTAL
1
.MALC6
1
5-148
DH18-03
IDENT Image For Console Spawned Jobs
~
~)
If the site needs to change the $ IDE NT image for console spawned jobs, patches
are required to the location(s) described below, in the following format:
aa
1
7
8
6
3
OCTAL
bbccddeeffgg
•MPOPM
where:
aa
- 33-45 (OCTAL). At least one, and as many of these locations as
required, may be specified.
bb ••• gg - The octal values representing the codes for the BCD characters of
the $ IDENT image desired, beginning with the data for card column
16. Note that the last statement should end with the octal value
"20" (blank), as this position is ignored.
Maximum Number Of DRL TASK Jobs Allowed
The maximum number of DRL TASK jobs allowed by default is 10 (decimal).
site-option patch can change that default value.
1
\,
This
1
8
6
7
3
47
OCTAL
OOOOOOOOnnnn
•MPOPM
/
where:
nnnn - The maximum number (octal) of DRL TASK jobs permitted.
DH18-03
5-149
-
...
USE RID Image For Console Spawned Jobs
If the site needs to change the $ USERID image for console spawned jobs,
patches are required to the location(s) described below, in the following
format:
1
8
6
7
3
aa
OCTAL
bbccddeeffgg
.MPOPM
1
where:
aa
- 50-62 (octal). At least one, and as many of these locations as
required, may be specified.
bb ••• gg - The octal values representing the codes for the BCD characters of
the $ USERID image desired, beginning with that data for card
column 16. The image must be in the form: userid$password. Note
that the last statement should end with the octal value "20"
(blank), as this position is ignored.
USE RID Image Of Select File For Console Spawned Jobs
If the site needs to change the $ SELECT image for console spawned jobs,
patches are required to the location(s) described below, in the following
format:
1
8
6
7
3
aa
OCTAL
bbccddeeffgg
•MPOPM
1
where:
aa
- 64-76 (octal) at least one, and as many of these locations as
required, may be specified.
bb ••• gg - The octal values representing the codes for the BCD characters of
the $ SELECT image desired, beginning with the data for card
column 16. The image must be in the format: userid.
Note that the last statement should end with the octal value
"6120" (slash blank).
Bypass Post-Mortem Data
The site can elect to bypass the recovery of Post-Mortem data in module .MPOPM
for Restart, SYSOUT Recovery, and Phase-1 Recovery processing. Cleanpoint data
must be used when this patch is applied to ensure that Restart, SYSOUT
Recovery, and Phase-1 Recovery processing do not fail.
5-150
DH18-03
The format for this patch is:
~\
;
1
8
1
6
7
3
101
OCTAL
n
.MPOPM
;I
where:
n - Any non-zero octal value.
Urgency Assignment
This site-option patch can be applied to define the maximum urgency available
to an operator through the URGe verb. The maximum urgency permitted is
63 (77 octal). The default is 40 (50 octal).
7
1
1
8
6
20
OCTAL
nn
3
.MPOPN
where:
nn - Any non-zero octal value up to 77.
MEMORY RELEASE OPTION
This site-option patch is applicable to DPS 8 and DPS 8000 only. It specifies
the limit for the number of MEMREL spawns when attempting to release memory.
If the requested release has not been accomplished when this limit is reached,
POR5 is notified to shut down the memory release process and to return any
memory already released back to the system.
1
7
1
8
6
3
121
OCTAL
OOOOOnOOOOOO
.MRASE
where:
n - Retry value (default
= 3).
)
5-151
DH18-03
I
VIRTUAL MODE MEMORY MANAGEMENT PARAMETER
This virtual mode memory management parameter designates the initial value for
the target page fault rate. It is used in conjunction with the other native
mode memory management parameters supplied via $ INFO statements. Refer to the
GCOS 8 as System Operating Techniques manual for more information about native
mode memory management parameters. The default value is 31 (25 decimal).
1
1
8
6
7
3
23
OCTAL
nn
.MDMM1
FAULT PROCESSING OPTIONS
The site can control several fault processing functions by applying the
following site-option patches to the .MFALT module. A patch containing all
zeros is ignored; only a patch that contains a nonzero value is accepted.
Abort On Master Mode Faults
The following site-option patch causes a system abort on all master mode faults
except MME, Timer Runout, Connect, Overflow, and Divide Check.
1
8
1
6
7
3
100
OCTAL
7
.MFALT
Disable Instruction Retry
The following site-option patch disables the Instruction Retry function and
releases the memory (approximately 1/2 K) allocated to this feature.
1
1
8
6
7
3
107
OCTAL
7
.MFALT
Abort On Faults Outside MME GELBAR Limits
The following site-option patch causes a system abort if any system program
(program numbers 1-10) faults in slave mode outside of MME GELBAR limits
(except MME, Timer Runout, Connect, Overflow, and Divide Check faults).
1
7
1
8
6
3
102
OCTAL
7
.MFALT
5~152
DH18-03
Processor Error Record Buffers
The following site-option patch specifies the number of processor error record
buffers to allocate:
1
8
6
7
3
103
OCTAL
n
.MFALT
1
where:
n - Number of processor error record buffers desired. The default value is
2 or the number of processors configured plus 1 (whichever value is
greater). If the value specified on this statement is less than the
default value, the default is applied. A maximum of seven buffers can
be specified.
One buffer is required for processing each fault that locks a history
register.
System Lockup Fault Control Value
The following site-option patch can be applied to override the standard system
lockup fault control value. The value must be specified in bits 34 and 35.
1
7
1
8
6
3
106
OCTAL
n
.MFALT
where:
n - Fault control value (1, 2, 3, or 4). The value 4 indicates that 0 is
desired (a zero value is rejected). The default value is 3.
EXCEPTIOI PROCESSING STATISTICS COLLECTIOI
Inhibit Automatic Start Of EeOL
The following site-option patch inhibits the automatic start of ECOL during
Startup.
1
8
1
6
3
2
7
3
121
OCTAL
o
DON'T START ECOL
.MSCHD
5-153
DH18-03
ECOL Communications Words
The default parameters in the ECOL communications words can be modified by
applying the following site-option patches to the .MFALT module:
1
8
6
7
3
111
OCTAL
OtttttiOOOcc
.MFALT
1
where:
ttttt - MaS error message time threshold (in minutes, expressed in octal).
Right-justify this value in bits 4-17. The default is 10 minutes.
i - B i t s used to permit/inhibit fault logging and reporting functions.
BIT
18
must be zero
19 = 1, inhibit logging of memory faults.
this function (i.e., bit 19 =0).
The default is to permit
20 = 1, inhibit logging of illegal procedure (IPR) faults.
default permits this function (i.e., bit 20 =0).
cc
- MOS error message count threshold.
31-35. The default value is 25.
The
Right-justify this value in bits
1
8
6
7
3
112
OCTAL
ppppeeeeOOOt
.MFALT
1
where:
pppp - MPC sample period in 0.1-minute increments (expressed in octal).
This value can range from 0-4095. If the value is 0, sampling is
disabled. The default value is 600 (60 minutes). Right-justify this
value in bits 0-11.
eeee - MPC error threshold in 0.01 percent increments (expressed in octal).
This value can range from 1-4095. The default value is 1 (0.01
percent). If the value is 0, the error threshold message reporting
function is disabled. Right-justify this value in bits 12-23.
t
- If bit 33 =1, inhibit monitoring of the magnetic tape MPC threshold.
The default permits monitoring (i.e., bit 33 =0).
5-154
DH18-03
I
~
1
8
6
7
3
113
OCTAL
OOOOOOggssOO
.MFALT
1
where:
gg - ECOL MME GEWAKE time in 0.1-minute increments. This value can range
from 0-77 octal (0-6.3 minutes). The default value is 50 decimal (5
minutes). Right-justify this value in bits 18-23.
ss - Automatic retry summary logging period in 0.1-hour increments. This
value can range from 0-77 octal. If the value is 0, automatic retry
summary logging is inhibited. The default value is 10 decimal (1.0
hour). Right-justify this value in bits 24-29.
1
1
8
6
7
3
114
OCTAL
1
.MFALT
The patch above disables the logging of exception processing records.
default is to log these records.
The
CACHE MEMORY CONTROL OPTIONS
By default, the ECOL module assumes control of cache memory when it is enabled,
unless the following site-option patch is used to place cache memory under
operating system control. (Details on cache control and any associated console
verbs are described in the GCOS 8 OS Distributed Maintenance Services Tools
Reference M a n u a l . ) 1
8
6
7
3
105
OCTAL
1
.MFALT
1
The following patch, optionally, directs GCOS to control cache memory until
ECOL is enabled. If the ECOL program is subsequently enabled, it assumes
control of cache memory_
8
1
6
7
1
105·
OCTAL
2
.MFALT
3
5-155
DH18-03
ECFILE Creation Patch
The Error Collection File (ECFILE) size is set to 1200 llinks for both minimum
and default when created by the ECOL module, unless a file size value is
entered at site-patch location 257 (octal) of the ECOL program.
The file size range that can be requested is 1200 to 262143 llinks (i.e.,
2260 - 777777 octal). A request outside of this range results in the display
of one of the following messages upon the console:
'FYI ECOL - FILE SIZE REQUEST> 262143, WILL ATTEMPT TO GET 1200 LLINKS
'FYI ECOL - FILE SIZE REQUEST WAS nnnn LLINKS, WILL ATTEMPT TO USE 1200
LLINKS
A request for file space in excess of 12000 llinks results in issuance of the
following message:
'FYI ECOL - REQUESTED COLLECTOR FILE SIZE OF nnnnnn LLINKS IS VERY LARGE
The requested file space (either by request or by default) can be denied by the
system if not enough space is available. When this occurs, ECOL generates a
request for 100 llinks of space less than the requested amount, and continues
to decrement the file space request by 100 llinks until either the file space
request is accepted by the system, or the file space requested is smaller than
800 llinks, which causes ECOL to abort with an HU MME GEBORT. One of the
following messages is issued in either case:
'FYI ECOL - COULD NOT OBTAIN AT LEAST 800 LLINKS PERM FILE SPACE,
PLEASE RESTART ECOL WHEN ADEQUATE SPACE IS AVAILABLE
'FYI ECOL - PERM FILE SPACE NEEDED WAS nnnnnn LLINKS,
SPACE OBTAINED WAS nnnnnn LLINKS
The file is created as a sequential file with read and write concurrency
permitted. Specific read permission is given to SY ELAN userid for ELAN report
production. The format for this patch is:
1
8
6
7
3
257
OCTAL
OOOOOOnnnnnn
.MECOL
1
where:
nnnnnn - 2260-777777 (octal). This value specifies the number of 11 inks
requested to execute ECOL. This value must be right-justified.
5-156
DH18-03
Shared Controller/Device I/O Statistics Collection
\
j
Because of the differences in the collection processes of controller or device
I/O statistics between ECOL and its predecessor, the HEALS program, ELAN I/O
methods will not accurately collect statistics when devices are shared between
two systems with different releases, unless the older HEALS module does the
collection. The site option patch, described below, defines these
circumstances for ECOL and allows the HEALS module to assume the task of
statistical collection for shared devices between systems. Non-standard device
statistics collection is performed normally for each of the other devices on
each of the systems involved.
Site-option patch location 261 (octal) of .MECOL (bit 31) is used to cqntrol
access of shared device statistics. Setting bit 31 to 1 in this location
initializes bit 31 of .CREC1. (The default value is zero for both bits.)
After initializing .CREC1, ECOL checks for one of the following conditions:
1. If bit 19 of the channel data within that entry of the Controller
Information Table (pointed to by .CReST) is 1, then the devices on this
channel are considered shared. (Details of the Controller Information
Table are described in the GCOS 8 OS System Tables manual.)
2. If bit 19 is set (as in step 1) and bit 31 of .CREC1 is 1 (per ECOL
initialization, above), ECOL collects statistics for all devices on this
channel.
\
j
3. If bit 19 is set (as in step 1) and bit 31 of .CREC1 = 0 (per ECOL
initialization, above), ECOL does not collect statistics for any device
on this channel.
4. If bit 19 is not set (as in step 1), this channel is considered unshared
and no consideration is given to the content of bit 31 of .CREC1.
Statistics are collected for all devices on this channel.
The format for this patch is:
1
7
1
8
6
3
261
OCTAL
OOOOOOOOOOnO
.MECOL
where:
n - 2 or 0 (the default is 0). The status of n detenmines the control
access to shared device statistics and is checked by ECOL. If n = 2, a
bit is set in a communication region cell for the MPCD program to
check. MPCD uses the same criteria used by ECOL to determine whether to
read firmware statistics or not.
\I
;
5-157
DH18-03
NOTE:
MPCD also checks bit 31 of .CREC1 to determine the status of ECOL
. statistics collection on the system shared devices. If bit 31 = 1, ECOL
and MPCD assume that ECOL will collect statistics for all configured
shared (and non-shared) devices. If bit 31 = 0, any statistical
collecting between shared devices on one channel is done by the other
system, and any statistical collecting between unshared devices or
channels is done by the ECOL module in this system.
ECS Error Thresholds
The site-option patch for location 267 (octal) can be used to set ECS processor
time andlor ECS error count thresholds. The format for this patch is:
7
1
1
8
6
267
OCTAL
OmmmmmOOOccc
3
.MECOL
where:
mmmmm - 0 to 37777 (octal).
This is the ECS error threshold time interval.
The default value is 12 (octal).
ccc
- 0 to 777 (octal). This is the ECS error count threshold.
default value is 31 (octal).
The
SYSTEM INPUT OPTIONS
Site-option patches can be applied tO,the .MGEIN module to modify and/or
control several System Input program functions. The patches described below
can be applied to the locations specified.
*J And J* File Space Allocation
The following patch can be applied to the .MGEIN module to modify the number of
320-word llinks initially allocated for *J subfiles and the J* file.
I
1
7
1
8
6
3
114
OCTAL
xxxxxxyyyyyy
.MGEIN
where:
xxxxxx - Number of llinks, expressed in octal, initially requested for *J
subfiles. The default initial allocation size is 144 llinks.
yyyyyy - Number of llinks (modulo 12), expressed in octal, initially
requested for the J* file for each job. The default initial
allocation size is 12 llinks.
5-158
DH18-03
JCL Statement Examination And Modifioation
Several patches can be applied to the .MGEIN module to define the extent of the
.MSCN1 module's responsibilities when examining and/or modifying JCL statements
encountered during program execution. The .MGEIN module can be patched to
specify examination and/or modification of JCL statements as defined by Figure
5-2. One bit is set for each JCL statement that the .MSCN1 module is to
examine and/or modify.
For Resource Control Words statement types:
1
1
8
6
7
3
116
OCTAL
OCTAL
nnnnnnnnnnnn
nnnnnnnnnnnn
.MGEIN
.MGEIN
117
I
where:
n ••• n - Octal value to expand to a binary value. A set bit (=1) specifies
examining and/or modifying the corresponding JCL statement type from
the Resource Control Words 1 and 2 list by .MSCN1.
For Activity Control Word 1 statement types:
1
1
8
6
7
3
120
OCTAL
nnnnnnnnnnnn
.MGEIN
I
where:
n ••• n - Octal value to expand to a binary value. A set bit (=1) specifies
examine and/or modify the corresponding JCL statement type from the
Activity Control Word 1 statement list by .MSCN1.
For Activity Control Word 2 statement t.ypes:
1
8
6
7
3
121
OCTAL
nnnnnnnnnnn
.MGEIN
1
Same as Activity Control Word 1 except Activity Control Word 2 list is
applicable.
5-159
DH18-03
I
For Activity Control Word 3 statement types:
8
6
7
3
OCTAL
nnnnnnnnnnn
.MGEIN
1
1
I
Same as Activity Control Word 1 except Activity Control Word 3 list is
applicable.
Stranger Statement Examination And Modification
The following site-option patch can be applied to the .MGEIN module to examine
and/or modify JCL statements other than those listed in Figure 5-2. Each of a
maximum of ten locations of the .MGEIN module can be patched with a
six-character BCD representation of the statement type to be examined or
modified and can be applied to either standard or site-unique statements. One
card type can be identified in each of these locations. Further discussion of
stranger options is included in the GCOS 8 OS System Programming Guide.
1
7
1
8
6
3
aaa
OCTAL
xxxxxxxxxxxx
.MGEIN
where:
I
aaa
- Location (124-135 octal) in the System Input program to be patched.
Addresses cannot be duplicated.
x •.• x - 12-character octal representation of the BCD statement type.
5-160
DH18-03
Bit Definitions for:
Resource Control Word 1 (RESOR1)
Resource Control Word 2 (RESOR2)
Patch Location 116
Patch Location 117
Bit(s)
Bit(s)
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
JeL Statement
Reserved for GCOS
$ FORM
$ FFILE
$ FILE
$ PPS
$ PRINT
$ DATA
$ PUNeH
$ READ
$ eONSL
$ eONSLA
$ TYPE
$ SYSOUT
$ REMOTE
$ REPORT
$ REPTL
$ REPTR
$ PRMFL
$ DAe
$ TAPE
$ TAPE9
$ NTAPE
$ A1APK
$ A2APK
$ A1BPK
$ A2BPK
$ FILGP
$ GENFIL
$ 190PK
$ TAPE7
$ 191PK
Reserved for GCOS
$ 400PK
$ TAPE27
$ TAPE29
$ 450PK
Figure 5-2.
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
11
JCL Statement
$ DBASE
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
for
I
GeOS
Geos
GeOS
GeOS
Geos
GeOS
Geos
GCOS
GCOS
GeOS
GeOS
GeOS
Geos
GeOS
Geos
GCOS
Geos
Geos
GeOS
GeOS
GeOS
GCOS
GCOS
GeOS
Geos
GeOS
Geos
GCOS
GCOS
Geos
GCOS
Geos
GCos
Geos
GCOS
.MSeN1 Function Words
5-161
DH18-03
Bit Definitions for:
Activity Control Word 1 (ACTIV1)
Patch Location 120
Bit(s)
I
I
I
I
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
JCL Statement
Activity Control Word 2 (ACTIV2)
Patch Location 121
Bit(s)
Reserved for GeOS
$ FORTY
$ GMAP
:I> COBOL
$ ADA
$ PL6
$ IDS
$ PSM
$ CONVER
$ UTILITY
$ RUN
$ RERUN
$ SYSEDIT
$ EXTEDIT
$ S2PROG
$ FILEDIT
$ FILSYS
$ GMAPV
$ ADLIB
$ 355HAP
$ 355SIM
$ PROGRAM
$ EXECUTE
$ PL1
$ CBL74
$ LINKER
$ GENSYS
$ UTL2
$ CBL68
$ IDS2
$ CBL85
$ SReLIB
$ LODLIB
$ OBJLIB
$ RPG2
$ FORTRA
Figure 5-2 (cont).
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
JCL Statement
$ FORT77
F77V
GMAP66
FORTV
LKED
SHRUE
$ UTL8
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved· for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
Reserved for
:I>
$
$
$
$
GCOS
GeOS
Geos
GeOS
GeOS
Geos
GeOS
GeOS
GeOS
GeOS
GCOS
GeOS
GeOS
GeOS
GCOS
GeOS
GeOS
GeOS
GeOS
GeOS
GeOS
GeOS
GCOS
GCOS
Geos
GeOS
GCos
GeOS
GeOS
.MSeN1 Function Words
5-162
DH18-03
Activity Control Word 3 (ACTIV3)
Patch Location 123
Bit(s)
Bit(s)
JCL Statement
$ IDENT
$ SNUMB
$ LIMITS
$ NEED
$ PRIVITY
$ RESOURC
Reserved for GCOS
$ STRANGER 11
$ STRANGER #2
0
1
2
3
4
5
6-25
26
27
Figure 5-2 (cont).
28
29
30
31
32
33
34
35
JCL Statement
$
$
$
$
$
$
$
$
STRANGER
STRANGER
STRANGER
STRANGER
STRANGER
STRANGER
STRANGER
STRANGER
'3
14
15
16
17
18
19
$10
.MSCN1 Function Words
Execution Report Message File
Site-option patches can be applied to the .MGEIN module to help control access
to and security for the site-defined Execution Report message file. (Unless
modified, the name of this file is MSG.)
The following patches can be applied to .MGEIN to change the default user
identification.
1
7
1
8
6
3
136
137
OCTAL
OCTAL
xxxxxxxxxxxxx
xxxxxxxxxxxxx
.MGEIN
.MGEIN
where:
x ••• x - Octal codes for six BCD chara.cters of the user identification (i.e.,
catalog name) for the MSG file. A maximum of 12 BCD characters can
be specified (i.e., if the identifier is more than six characters,
the excess is specified in the second location). The default user
identification is OPNSUTIL.
5-163
DH18-03
I
The following patch can be applied to .MGEIN to define a new name for the
Execution Report mess~ge file.
8
1
1
6
7
3
140
OCTAL
yyyyyyyyyyyy
.MGEIN
where:
y ••• y - Octal codes for six BCD characters of the name of the file that
contains the Execution Report message. A maximum of six BCD
characters can be specified. The default file name is MSG.
The following patch can be applied to .MGEIN to suppress the GEIN SPAWN •••
console message.
1
8
6
7
3
141
OCTAL
n
.MGEIN
1
where:
n - Any non-zero octal value
DEBUG OPTIONS AND SPECIAL ACTIONS
Location 144 of .MGEIN is reserved for special actions, and is patched as
follows:
I
1
7
1
8
6
3
144
OCTAL
n
.MGEIN
where:
n - A binary value such that a set bit (=1) implies a special action is to
take place.
I
Bits 0-33
Bit
34
Bit
35
= currently unused
= force scan of all
= abort the system
jobs
5-164
DH18-03
FLUSHING SYSOUT COLLECTION SPACE
Refer to $ INFO SYBRT/n parameter for flushing of SYSOUT collection space.
INPUT/OUTPUT SUPERVISOR (lOS) OPTION
The following site-option patch can be applied to significantly reduce the
overhead associated with I/O interrupt processing. The patch ensures a return
to an interrupted program whenever an I/O interrupt occurs (unless the
terminating I/O operation requested a courtesy call and the interrupted program
is executing at main level). Without this patch, the interrupted program is
removed from execution to allow redispatching of the processor following
interrupt processing.
1
8
6
7
3
60
OCTAL
o
.MIOS
1
TEMPORARY DISK FILE GROWTH
The amount of disk space is calculated by the system for a GROW request for a
temporary file if the amount of space requested is O(zero). The calculation is
made as follows:
Growth amount
= (current
file size / ddd) + aaa
where ddd is a constant divisor and aaa is a constant adder, both expressed in
octal. The default value for ddd is 4 and for aaa is 8. The default values
may be changed via the following site-option patches:
1
12
13
14
8
6
7
3
OCTAL
OCTAL
OCTAL
ddd
aaa
fff
.MM)RE
.MMORE
.MMORE
If fff is non-zero, the number of links in the GROW request is ignored and the
system calculates the growth amount as above. The default value for fff is
zero.
MME GEMORE RETRIES
If a MME GEMORE request is denied for an internal GCOS Operating System reason,
i.e., .RBRT or some other appropriate bit is set in the .SRQST or .STATE words,
this site-option patch allows the site to determine the number of times the
request is to be retried (default is 20) before returning the denial status
code to the process.
5-165
DH18-03
1
8
6
7
3
50
OCTAL
nnnnnnOOOOOO
.MPMME
1
where:
nnnnnn - Octal value of the number of retries to be attempted before taking
the denial return.
NOTE: Each retry results in a .CALLI to .MDISP entry point 16, which takes the
process out of execution and puts it back in the dispatcher queue to wait
for the next dispatch. On a busy system this could result in enough
delay (even with the default value of 20) to allow the condition to be
cleared by GCOS and allow the MME GEMORE request to continue. During
periods when the system is relatively idle, each retry will be almost
instantaneous. Thus the Site Administrator should use discretion in
choosing the value for nnnnnn.
MME GESNUM AND PMME GENSNB-OPTIONS
This site-option patch allows the range of SNUMBs generated by MME GESNUM and
PMME GENSNB to be extended by using a selected sequence of characters of the
English alphabet (excluding A, E, I, O,U, Y, and non-alphanumeric characters)
in character position 1 and/or in character positions 2 - 4 of the generated
SNUMB.
47
1
7
8
6
3
OCTAL
OOOOmmOOOOnn
.MPMME
where:
mm - Octal value in the range 01 - 36, representing (see below) the last
character to be used in character position 1 of the generated SNUMB
(default mm = 12).
nn - Octal value in the range 01 - 36, representing (see below) the last
character to be used in character positions 2 - 4 of the generated
SNUMB (default nn = 12).
o0
0 0 0 0 0 1 1 1 1 1 1 1 122 2 2 2 2 223 3 3 3 333
1 234 5 670 1 2 3 4 5 670 1 234 5 670 1 2 3 4 5 6
o
1 2 3 4 5 6 7 8 9 BCD F G H J K L M N P Q R S T V W I Z
For example, 000012000013 would allow a B to be generated in character
positions 2 - 4 of the generated SNUMBs in addition to the normal numerics.
NOTE: SNUMBs of site-spawned jobs should be considered when setting the above
values, since there is a possibility of duplicate SNUMBs.
5-166
DH18-03
TIME SHARING SYSTEM OPTIONS
Several Time Sharing System functions can be controlled via site-option patches
to the Time Sharing Executive program (.MTIMS). These functions and their
patch formats are defined below. Note that the absolute location specified in
the format is equated to a symbolic location.
Processor Time For DRL TASK Job
The following patch specifies the maximum allowable time for DRL TASK jobs:
8
1
1
7
6
3
113
OCTAL
nnnnnnnnnnnn
.MTIMS
where:
n ••• n - Maximum processor time (octal), in increments of
for a job using DRL TASK
113
1/6~
millisecond,
- Symbolic location .TTPRC.
Maximum Number Of Keyboard-Display Terminals
The following site-option patch specifies the maximum number of keyboard
display terminals (VIP type) permitted on the Time Sharing System at anyone
time.
1
1
8
6
116
OCTAL
00 OmmmO Onnnn
7
3
.MI'IMS
where:
mmm
- Maximum number (octal) of keyboard-display terminals permitted at any
one time. This value cannot exceed the number of Time Sharing System
users. The default value is O.
nnnn - The size of the input buffer which a VIP type terminal is allocated.
The default value is 512 (1000 octal) words.
116
- Symbolic location .T760
5-167
DH18-03
Maximum Number Of Terminals
The following site-option patch specifies the maximum number of terminals
allowed on the system (including keyboard-display terminals and the statistical
record (TSRI) accounting file):
1
8
6
7
3
117
OCTAL
OOOOOOOOOnnn
.MI'IMS
1
where:
nnn'- Maximum number of terminals permitted (octal value, right-justified).
The default value is 18 (decimal).
117 - Symbolic location .TFMAX.
Time Interval For TSRI Data Issue To SCF
The following patch changes the time interval for writing Time Sharing
accounting data to the Statistical Collection File (SCF). If the Time Sharing
System Statistical Record (TSRI) accounting records are required, this patch
must be applied. If there is no patch to this location, no TSRI data is
written to the SCF.
1
1
8
6
7
3
120
OCTAL
OOOOOOnnnnnn
.MI'IMS
where:
nnnnnn - Number of seconds (octal) in the interval between data issues to
the SCF. This value is right-justified in the variable field.
120
- Symbolic location .TSTAT.
5-168
DH18-03
Memory Allocation For DRL TASK Job
The following patch specifies the amount of memory that can be allocated to a
batch job using a DRL TASK.
8
1
6
7
OCTAL
nnnnnnOOOOOO
.MTIMS
3
where:
nnnnnn - Number (octal) of words of memory desired plus one additional
word. The default value is (64*1024)+1.
127
- Symbolic location .TTCOR.
Urgency For DRL TASK Job
The following patch specifies the maximum urgency permitted for batch jobs
using a DRL TASK:
1
\
)
1
8
6
7
3
130
OCTAL
OOOOOOnnOOOO
.MTIMS
where:
nn
- Maximum urgency (octal) for a job using a DRL TASK.
is 51 (octal).
130 -
The default value
Symbolic location .TTURG.
DRL T.CMOV Users
The following patch identifies the type of Time Sharing System users that can
examine portions of GeOS memory via a DRL T.CMOV.
7
1
1
8
6
131
OCTAL
OOOOOnOOOOOO
3
5-169
DH18-03
where:
n
- Numeric code identifying the category of users that can examine
portions of GCOS memory. The following codes are valid:
1 - All users
2 - Master users (the default)
3 - Master users or users with LaDS permission
131 - Symbolic location .TCMOV.
Permanent File User Identifier
The following patches specify the user identifier employed when allocating a
permanent deferred queue file, primary or secondary file or swap file:
1
132
133
8
6
7
3
OCTAL
OCTAL
xxxxxxxxxxxx
xxxxxxxxxxxx
.MI'IMS
.MI'IMS
where:
x ••• x - User identifier (octal code for six BCD characters). A maximum of
12 characters can be specified (left-justified with trailing
blanks). The default user identifier is SYS CAT
132
- Symbolic location .TUSER.
133
- Symbolic location .TUSER+1.
Master User Identification
The following patches identify the userid for master users:
1
1
8
6
7
3
134
135
OCTAL
OCTAL
xxxxxxxxxxxx
xxxxxxxxxxxx
.Ml'IMS
•Ml'IMS
where:
x ••• x - Master user identifier (octal code for six BCD characters). The
default identifier is MASTER. A maximum of 12 characters can be
specified (left-justified with trailing blanks).
134
- Symbolic location .TMAST.
135
- Symbolic location .TMAST+1.
,5-170
DH18-03
Status Message Time Interval
The following patch changes the frequency of Time Sharing System status
messages issued to the system console:
7
1
1
8
6
160
OCTAL
nnnnnnnnnnnn
3
.MTlMS
where:
n •.• n - Time interval, in 1/64-millisecond increments (octal) between status
message outputs. The default value is 15 minutes.
160
- Symbolic location .TATYl.
Class B Priority Dispatches
Use of the Class B priority feature (GCOS priority dispatching and control) by
the Time Sharing System permits the system to control the number of dispatches
permitted to jobs without Class B priority between dispatches to Class B
priority jobs. The following patch allows the site to control the frequency of
these dispatches as well as their duration. (Refer to "Dispatcher Options" in
this section for a discussion of Class B priority and for a discussion of
Dispatcher options that apply to multicopy Time Sharing operations.)
1
1
8
6
176
OCTAL
OOOOxxOOOOyy
7
3
.MTl~
where:
xx
- Number (octal) of 32-millisecond quantums per dispatch.
value is 4.
The default
yy
- Number (octal) of non-Time Sharing System dispatches between
dispatches to the Time Sharing System. The default value is 1.
176 - Symbolic location .TAGPP.
)
5-171
DH18-03
Maximum Memory Size
The following patch can be applied to modify the default maximum amount of
memory allocated to the Time Sharing System. If this size must be changed
while the system is operational, the TSS SIZE nnn console entry can be used.
1
8
6
7
3
200
OCTAL
OOOnnnOOOOOO
.MI'IMS
1
where:
nnn - Maximum number (octal) of 1K blocks of memory to be allocated to the
Time Sharing System (1K = 1024 words). The default value is 80K.
200 - Symbolic location .TAMMS.
Minimum Memory Size
When the Time Sharing System is lightly loaded and no longer needs all of the
memory allocated to it for loading subsystems, memory can be released to GCOS
until the default minimum of 40K is reached. The following patch can be
applied to modify this default minimum:
1
1
8
6
7
3
201
OCTAL
nnnnnnOOOOOO
.MI'IMS
where:
n ••• n - Minimum amount of memory allocated to Time Sharing for loading time
sharing subsystems. This value (octal) is specified in pages (lK
increments) •
201
- Symbolic location .TASMS.
5-172
DH18-03
Memory Allocation Delays
Large jobs, whose memory requirements exceed the default limitation of 36K,
frequently must wait four times as long as smaller jobs for memory allocation.
The following patch modifies this default priority threshold value:
1
1
8
6
7
3
202
OCTAL
OOOnnnOOOOOO
• MrIMS
where:
nnn - Memory-requirement level at which a job is assigned a low-priority
classification by the Time Sharing System. This value (octal) is
expressed in terms of 1K blocks.
202 - Symbolic location .TAMIS.
Request And Release Memory
The Time Sharing System automatically requests and releases memory in minimum
increments of 7K and 5K, respectively. The following patches adjust these
default values.
\
1
7
1
8
6
3
203
204
OCTAL
OCTAL
OOOOxxOOOOOO
OOOOyyOOOOOO
•MrlMS
•MrlMS
where:
xx
- Minimum number (octal) of 1K pages of memory to be requested.
default value is 7.
yy
- Minimum number (octal) of pages of memory to be released.
value is 5.
The
The default
203 - Symbolic location .TAMIl.
204 - Symbolic location .TASH!.
)
5-173
DH18-03
Memory Reserved for Urgent Jobs
When the Time Sharing System is heavily loaded, the delay in memory allocation
for a job may exceed the time limit parameter. Asa result, the job is given
an "urgent" status. When urgent jobs exist, the memory allocation algorithm
favors those jobs that have awaited allocation for the longest time by
reserving a portion of available memory for exclusive use by the jobs. The
following patch controls the amount of memory reserved for exclusive use by
urgent jobs.
1
7
1
8
6
3
213
OCTAL
OOOOOOOOOOOn
.MTIMS
where:
n
- Reserve the amount of memory equal to the result of the algorithm x/y
(where x = total space available and y = a value greater than 1). The
default value for n is 2. If n is specified as 0, only memory
required by the urgent job(s) that has waited the longest for
allocation is reserved.
213 - Symbolic location A.URMD.
Deferred Processing Parameters
The following three patches control the maximum number of scheduled and active
DRUNs, processor time limit, and preferred execution time for deferred
processing.
Maximum scheduled and active DRUNs:
1
7
1
8
6
3
271
OCTAL
xxxxxxyyyyyy
.MTI~
where:
xxxxxx - Maximum number (octal) of deferred sessions that can be scheduled
at anyone time. When this value is zero (0) or exceeds the limit
imposed by the size of the deferred queue file, DRUN permits
scheduling of as many sessions as possible.
yyyyyy - Maximum number (octal) of combined online and deferred-session
users that can be active at anyone time. When this maximum is
reached, no additional deferred sessions are initiated. When this
field is zero, deferred processing is disabled. The default value
is 264 (octal).
271
- Symbolic location .TSDHX
5-174
DH18-03
Deferred processing time limit:
1
8
6
7
3
272
OCTAL
nnnnnnnnnnnn
.Ml'IMS
1
where:
n ••• n - Octal value specifying maximum amount of processor time (in
1/64-millisecond increments) allowed for a single deferred session.
The default value is zero, which indicates there is no time limit.
272
- Symbolic location .TSDPT.
Preferred time-of-day to run deferred job:
1
7
1
8
6
3
273
OCTAL
nnnnnnnnnnnn
.Ml'IMS
where:
n ••• n - Octal value specifying the preferred time-of-day (in
1/64-millisecond increments past midnight) to initiate deferred
sessions that do not request a specific start time. The default
value is zero, which indicates that these sessions will be initiated
as soon as possible.
273
- Symbolic location .TSDDT.
Line-Hold Interval Following Disconnect
When a terminal disconnects for any reason other than the BYE sequence, the
Time Sharing System holds that line for a short time to give the terminal an
opportunity to reconnect. The following patch modifies the hold interval:
1
1
8
6
7
3
326
OCTAL
OOOnnnnnnnnn
•Ml'IMS
where:
n ••• n - Octal value specifying the amount of time (in 1/64-millisecond
intervals) that a line is held before it is released following a
terminal disconnect. The default value is equivalent to two
minutes.
326
- Symbolic location .TIMER.
5-175
DH18-03
Memory Limit
A maximum memory limitation can be established for Time Sharing subsystems via
the following site-option patch. If the object program exceeds this
limitation, the subsystem aborts.
1
I
1
8
6
7
3
367
OCTAL
nnnnnn
.MTIMS
where:
nnnnnn - Memory limitation in pages (octal, left-justified).
default value.
I
367
There is no
- Symbolic location .TASSZ.
Processor Time Limit
A maximum processor time limit can be established for Time Sharing subsystems
via the following site-option patch. If the object program exceeds this
limitation, the subsystem aborts.
1
I
1
8
6
7
3
370
OCTAL
nnnn
.MTI~
~
where:
I
nnnn - Processor time limit in 1/64-millisecond increments (octal).
is no default value.
370
There
- Symbolic location .TASTM.
Enable Measurement Record
The following site-option patch enables the Time Sharing System measurement
record (SCF record type 19), used primarily in system tests and measurements.
7
1
I
1
8
6
377
OCTAL
OOOOOOOOOOOn
3
.MTIMS
where:
I
n
- Enable the measurement record if this value is nonzero.
377 - Symbolic location .TSSAS.
5-176
DH18-03
~
SWap File Parameters
A series of patches can modify or establish parameters for Time Sharing System
swap files. The following three patches can be used to:
o Modify the default number of swap files allocated at System Startup.
o Identify the growth factor to use when the swap files are created too
small or too large. File sizes are dynamically adjusted by this factor.
o Define the size of the swap files.
Minimum swap file size:
1
7
1
8
6
3
402
OCTAL
OOOOOOnnnnnn
.MrIMS
where:
I
nnnnnn - Swap file size (octal) in llinks. To determine this size, multiply
the growth factor from the patch to symbolic location .TSGRW by 48.
402
I
- Symbolic location .TSFS.
Swap file growth factor:
1
7
1
8
6
3
403
OCTAL
nnnnnnOOOOOO
•MrIMS
where:
I
nnnnnn - Minimum number (octal) of llinks to be requested or released to
adjust the file size. This value can be determined via the formula
(u*3s)/f (where u = maximum number of users configured, s = file
size (in llinks), and f = number of swap files configured).
403
I
- Symbolic location .TSGRW.
Number of active swap files:
1
8
1
6
1
3
404
OCTAL
OOOOOOOOOOOn
.MrIMS
5-171
DH18-03
I
where:
n
- Number (octal) of swap files to be active. The maximum number of swap
files is 16. Default allocation values are:
Number
of users
Number
of files
1-31
32-47
48-180
2
3
4
404 - Symbolic location .TSSF.
Permanent File Identification
The following patches can be applied for two purposes.
o The site can define file names for the deferred queue file, primary and
secondary program files, and swap files (if the swap files are permanent
files). In this case,the specified file is created on a system-assigned
mass storage device.
o The site can selectively assign these files to specific mass storage
devices. Because these files are heavily used by the Time Sharing
System, system performance is often improved via the device-assignment
technique.
8
1
6
7
1
aaa
OCTAL
bOOOOOnnnnnn
.MTIMS
3
where:
aaa
- Absolute octal address of the location in .MrIMS containing either
the file name or the device name specified in the nnnnnn field.
The addresses, corresponding symbolic identifications, and file
identifications are described in Table 5-8.
b
- Flag indicating whether nnnnnn is a file name or a logical device
name. If bit 0 in this field =0, field nnnnnn contains the logical
device name (in BCD) of the mass storage unit on which the file
resides. If bit 0 in this field =1, field nnnnnn contains the file
name (in BCD) of the permanent file defined at this location.
nnnnnn - Logical device name of the mass storage device on which this file
resides, or the file name (1-3 characters) of this file. (nnnnnn is
the octal code for three BCD characters.)
NOTE: If bit 17 is set in the ID allocation patch, and multicopy Time
Sharing is configured, a common deferred queue file is used.
5-178
DH18-03
Table 5-8.
Permanent File Address Descriptions
Octal
Address (aaa)
Symbolic
Identification
405
406
407
412
413
414
415
416
417
420
421
422
423
424
425
426
427
430
431
•TSFDV
•TSFDV+ 1
•TSFDV+2
•TSFDV+5
•TSFDV+6
•TSFDV+7
•TSFDV+8
•TSFDV+9
.TSFDV+10
.TSFDV+11
.TSFDV+12
.TSFDV+13
.TSFDV+14
.TSFDV+15
.TSFDV+16
.TSFDV+17
.TSFDV+18
.TSFDV+19
.TSFDV+20
File
Code
ID
IP
IQ
IS
IT
IU
IV
IW
IX
IY
IZ
+S
+T
+U
+V
+W
+X
+Y
+Z
File Description
Deferred Queue
Primary Program
Secondary Program
Swap
Swap
Swap
Swap
Swap
Swap
Swap
Swap
Swap
Swap
Swap
Swap
Swap
Swap
Swap
Swap
Program Logic Error Processing
The following patch can be applied to control the manner in which the Time
Sharing System performs program logic error processing. If bits 0-17 contain a
nonzero value, Time Sharing error recovery is attempted; if bits 0-17 are zero,
error recovery is not attempted. If recovery is not attempted or is
unsuccessful, bits 18-35 are inspected to determine how to terminate the Time
Sharing System. If bits 18-35 are zero, the GCOS system aborts; if bits 18-35
contain a nonzero value, only the Time Sharing System aborts.
1
1
8
6
7
3
1124
OCTAL
OOOOOxOOOOOy
.MI'IMS
where:
x
- If zero, error recovery is not attempted. If nonzero, error recovery
is attempted on the basis of error counts, timer data, and macro
expansions.
y
- If zero, the GCOS system aborts when recovery is not attempted or
fails. If nonzero, the Time Sharing System aborts with a reason code
of 74.
I
I
1124 - Symbolic location .TPLES
5-179
DH18-03
Time Sharing Prooessors
The following patch specifies the number of processors that can execute
subdispatch processes.
I
1
8
1
6
7
3
1744
OCTAL
OOOOOnOOOOOO
.MI'IMS
where:
n
I
- Number of processors on which Time Sharing subsystems can execute.
The default value is 6.
1744 - Symbolic location .QPROC.
Dispatching Time Slice
The following patch specifies the dispatching quantum (i.e., time slice) for
one Time Sharing subsystem subdispatch.
I
1
7
1
8
6
3
1746
OCTAL
OOOOOOnnnnnn
•Ml'IMS
where:
nnnnnn - Dispatch quantum expressed in 1/64-millisecond increments.
default value is 20 milliseconds (002400 octal).
I
1746
The
- Symbolic location .• QQTM
Additional PAT Space For Time Sharing
If the number of Time-Sharing System users exceeds 90, the .MPOPA module must
be patched to provide additional Peripheral Assignment Table (PAT) space for
the Time Sharing System. One additional page is required for every 18 users
over 90 (e.g., 105 users requires one additional page). Apply one patch for
each copy of Time Sharing in a multicopy Time Sharing environment. The format
for this patch is:
1
7
1
8
6
3
aa
OCTAL
562xxx756yyy
.• MPOPA
5-180
DH18-03
where:
aa
- Address to apply this patch. The following addresses are associated
with the various copies of Time Sharing:
25
30
33
36
-
The
The
The
The
first, or only, copy of Time Sharing (TS1)
second copy of Time Sharing (TS2)
third copy of Time Sharing (TS3)
fourth copy of Time Sharing (TS4)
562 - Module number of .MTIMS, containing related Time Sharing System
patches.
xxx - Number (octal) of 1024-word pages allocated for the Time Sharing
Executive program. The default is 69 decimal (105 octal) pages.
75
- Urgency level (octal) of the Time Sharing Executive program.
6
- The Time Sharing System is a privileged slave program and is in
accommodation mode.
yyy - Peripheral Assignment Table (PAT) segment size (in 512-word pages,
expressed in octal). The default is 6 •
•MDNET OPTIONS
Use of octal patches as the means for selecting site options in .MDNET has been
eliminated. See "$ MaDOPT Statement" in the $FILES Section.
I
*
MULTI COpy TIME SHARING CLASS B PRIORITY
A site-option patch must be applied to the .MDISP module to activate Class B
priority in a multicopy Time Sharing environment. Refer to "Apply Class A and
Class B Priorities" for a discussion of this patch.
DH18-03
TIME SHARING LOGON MESSAGE
Three ,$ite-option patches can be applied to the .TSNEW subsystem of the Time
Sharing System to provide system resource information in,the logon message.
Display System Identifier
The following patcQ includes the system identifier in the, logon message. (The
system identifier is specified on a $ SYID statement in the $CONFIG section.)
1
8
6
7
3
152
OCTAL
n
• TSNEW
1
where:
n
- Any nonzero value places the system identifier at the beginning of the
logon message. The default value is O.
152 - Symbolic location NEWSID.
Identity Remaining File Space
The following site-option patch issues a logon message identifying the amount
of file space remaining for the user.
1
7
1
8
6
3
153
OCTAL
n
•TSNEW
where:
n
- Any positive, nonzero value activates the message; any negative,
nonzero value suppresses the message. The default value is 0, which
results in issuance of the message:
nn LLINKS AVAILABLE
when more than 85J of the user's maximum file space is occupied (where
nn = number of llinks available).
153 - Symbolic location NEWBLK
5-182
DH18-03
J
Aotivate Logon LOAD Message
The following site-option patch activates the logon LOAD message, which
displays the current number of users, the amount of memory allocated to the
Time Sharing System, the percentage of Time Sharing System memory in use, the
number of users waiting for memory allocation, and the total amount of memory
required by all waiting users.
1
1
8
6
7
3
154
OCTAL
n
•TSNEW
where:
n
- Any nonzero value activates the LOAD message.
The default value is O.
154 - Symbolic location NEWLOD.
Logon Security
This site-option patch can invoke an optional security feature, whereby,
password changes are required the first time a user logs on following
implementation of this option and, thereafter, every n days from the last
change date.
1
1
8
6
303
OCTAL
yyydddOOOnnn
7
3
•TSNEW
where:
YYy - The three-digit octal equivalent of the year 1n which the password
change becomes a requirement.
ddd - The three-digit octal equivalent of the day of the year in which the
password becomes a requirement.
nnn - The three-digit octal equivalent of the number of days between
required password changes (must be less than 365 decimal).
DH18-03
TIME SHARING ACCOUNTING
A site can specify uniqu~ accounting parameters by applying site-option patches
to locations 176-210 (octal) of the,.TSLOG subsystem. Note that tl+e values
included on patches to locati<;>ns17Q-206 can be specified as fl:-oating-point
numbers.'
. '
.
Elapsed Time Charge Rate
The following patch changes the hourly charge rate for elapsed time:
7
3
1
1
8
176
OCTAL
6
•TSLOG
.000000nnnnnn
where:
nnnnnn - Elapsed time hourly rate. This value represents cents per hour and
is expressed in octal. The default value is 600 (octal).
176
- Symbolic location ELPPR.,
Memory-Usage Rate
The following patCh changes the hourly rate per 512-word block of memory used:
1
1
8
6
7
3
177
OCTAL
OOOOOOnnnnnn
.TSLOG
where:
nnnnnn - Hourly rate for each 512-word block of memory used. This value
represents cents per block per hour and is expressed in octal. The
default value is 1000.
177
- Symbolic location" PPH
5-184
DH18-03
Mass Storage File I/O Rate
The following patch modifies the charge rate for mass storage file I/O:
1
1
8
6
7
3
200
OCTAL
OOOOOOnnnnnn
.TSLOG
where:
nnnnnn - Hourly rate for mass storage file I/O. This value represents cents
and is expressed in octal. The default value is 2400.
- Symbolic location DISCPR.
200
Keyboard I/O Rate
The following patch modifies the charge rate per page for keyboard IIO
(typewriter or keyboard-display terminals).
1
7
1
8
6
3
201
OCTAL
OOOOOOOOOOnn
.TSLOG
where:
nn
- Cents per page for mass storage file I/O.
octal. The default value is 02.
This value is expressed in
201 - Symbolic location PPP
Service Rate Factor
The following patch changes the multiplication factor that varies the rate for
services:
7
1
1
8
6
202
OCTAL
OOOOOOOOOOnn
3
•TSLOG
where:
nn
- Multiplication factor (octal).
The default value is 1.
202 - Symbolic location K5
5-185
DH18-03
Average Disk 1/0 Time Value
The following patch changes the average disk I/O time value used for
calculating disk I/O charges.
1
7
1
8
6
3
203
OCTAL
OOOOOOOOOOOn
.TSLOG
where:
n
- Average disk I/O time (octal) in 1ll0-second increments.
value is 3.
The default
203 - Symbolic location AVDIO
Keyboard 1/0 Characters Per Page
The following patch changes the average number of characters per page of
keyboard I/O:
1
204
8
'OCTAL
1
6
7
3
OOOOOOnnnnnn
.TSLOG
where:
nnnnnn - Average nUmber (octal) of characters per page of keyboard 1/0.
default value is 3720.
204
The
- Symbolic location AVNOCR.
5-1-86
DH18-03
Deferred Session Rate
;
In some cases, deferred sessions may be charged at a reduced rate when the
sessions begin within a specified time frame. The following patch can be
applied to specify the reduced rate, which is expressed as a percentage of the
normal rate.
1
1
8
6
7
3
205
OCTAL
OOOOOOOOOnnn
.TSLOG
where:
nnn - Percentage (octal) of the normal rate that defines the reduced-rate.
For example, 120 defines 80% of the normal rate. The default value is
144, which is 100% of the normal rate.
205 - Symbolic location RR
Deferred Session Elapsed Time Rate
The following patch specifies the hourly rate for elapsed time of deferred
sessions:
)
206
8
1
6
7
3
OCTAL
OOOOOOnnnnnn
.TSLOG
where:
nnnnnn - Hourly rate for elapsed time of a deferred session. This value
represents cents per hour and is expressed in octal. The default
value is 600.
206
- Symbolic location DELPH
/
5-187
DH18-03
Starting And Ending Times For Reduoed Rates
The following patches specify the times of day at which the reduced rates for
deferred sessions begin and end.
1
1
8
6
7
3
207
OCTAL
nnnnnnnnnnnn
.TSLOG
210
OCTAL
mmmmmmmmmmmm
.TSLOG
where:
n ••• n - Starting time (in 1/64-millisecond increments, expressed in octal)
·of the reduced-rate period. The default value is -1, which
indicates there is no reduced rate.
m••• m - Ending time (in 1/64-millisecond increments, expressed in octal) of
the reduced-rate period. The default value is 0, which indicates
there is no reduced rate.
207
- Symbolic location RRLL
210
- Symbolic location RRUP
Additional Control Over Save Dumps (.MBRT8)
The site's use of $ INFO SAVDMP and/or the use of the SAVDMP= option on the
user's $ DMPOPT JCL statement may cause save dumps (information dumped to
system-controlled space when a user dump is taken) to be placed on the SCF.
Though not recommended (for security reasons), it is possible for the site to
cause save dumps to go to the user's p* file instead of the SCF.
The format for this site-option patch is:
1
1
8
6
6
OCTAL
n
7
3
.MBRT8
where:
n = 0 - Direct Save Dumps to the SCF when specified in JCL
(by $ DMPOPT SAVDMP= option) or by $ INFO SAVDMP option.
2 - Direct Save Dumps to pi when specified in JCL (by $ DMPOPT SAVDMP=
option) or by $ INFO SAVDMP option.
5-188
DH18-03
(
Time Sharing Initialization File
t/I,
I
~,!
The Time Sharing initialization file is described in detail in the GCOS 8 OS
Time Sharing Administration Guide. Following is a general description to state
its purpose.
A site can establish parameter data on an initialization file during Time
Sharing initialization in lieu of applying site-option patches to the Time
Sharing System. Use of this technique is optional. However, if the
initialization file is allocated, the following requirements apply:
o One initialization file must be created for each copy of Time Sharing.
The file name must be that of the corresponding SNUMB (i.e., TS1-TS4) so
that the file can be attached.
o The file is cataloged as a quick-access file with no password and is
subordinate to the user identification specified in .TUSER cells within
the TSSA communication region.
o The file may be created in either ASCII or BCD format. Several different
subsystems can be used to create the file (e.g., EDITOR, $CONVER, or
TSCONV) •
o The file is composed of logical records.
one parameter.
Each logical record comprises
Parameters (i.e., logical records) are defined in either the $INFO section or
the $PATCH section of the Time Sharing initialization file. These sections
perform essentially the same functions as their counterparts (of the same
names) in the GCOS Startup deck. The following describes use of the two
sections.
$INFO SECTION
The purpose of the $INFO section of the Time Sharing initialization file is to
eliminate the need for a site to use site-option patches to invoke various time
sharing options. The $INFO section makes it much easier for site personnel to
activate the options. Because of the impact of file-activated options, it is
recommended that this feature be used only by site personnel who are familiar
with the, format and content of Time Sharing site-option patches.
$PATCH SECTION
The $PATCH section of the Time Sharing initialization file can include Time
Sharing System Executive or subsystem patches for application du~ing Time
Sharing initialization. With few exceptions, the $PATCH section of the
initialization file is the same as the $PATCH section of the GCOS Startup job
stream. However, the initialization file section allows a site to modify the
Time Sharing System'without rebooting GCOS.
5-189
DH18-03
$LOAD SECTION
The $LOAD section of the Time Sharing initialization file provides a mechanism
for loading site modified TSS subsystems and editing the subsystems into the
program descriptors, command list, and primitives. The user subsystems must be
built in H* format and be loaded for access by the executive in one of two
places:
1. Subordinate to the Master use rid or
2. Subordinate to the CMDLIB userid
$LOAD SECTION
The $LOAD section of the Startup job stream can be used to load modules in~o
main memory for execution without affecting total system software tape
con en
ny mo ule loaded viat61:SseCf'rOff:ov~erridEi"s~N'runtrr"'thEtriext
ootload) the version of the module existing on the total system software tape.
The $LOAD section can prove beneficial under several circumstances.
example, it provides a way to:
For
o Load modules not contained on the total system software tape into memory.
o Test new or corrected modules - especially those with extensive
modifications - before they are edited onto the total system software
tape.
o Load object decks of any Slave Service Area (SSA) modules that are
site-prepared. Among these modules are •MSCAN, .MGNAT, and .MSCN1.
(These types of modules can also be loaded via an insert edit.)
Use of the $LOAD section is optional. If there are no modules requiring
loading in this manner, the $LOAD section can be excluded from the Startup job
stream. If the $LOAD section is not included, insert the *.*EOF statement that
marks the end of the Startup job stream after the ***EOF statement that marks
the end of the $PATCH section.
Each module included in the $LOAD section must be an object deck in binary
format and must be delimited by $ OBJECT and $ DKEND control statements. Any
relocation references within the code are ignored. Each module must specify a
primary SYMDEF. If a primary SYMDEF is not included, the module is ignored and
not written to the $LOAD file. In addition, if more than one copy of a module
is included in the $LOAD section, only the first copy encountered is written to
the $LOAD file; all other copies are ignored.
NOTE: Some modules cannot be loaded via the $LOAD section. Among these are
non-system software (e.g., applications programs) and GeOS system modules
that are assembled as programs (e.g., the System Input program).
5-190
DH18-03
(
1\
pi
As the $LOAD section is entered via magnetic tape during a cold boot, the
Startup program writes each module included in the section to the load file on
mass storage. This file and the mass storage device on which it resides must
be defined on the $ LOADFIL statement in the $CONFIG section.
Any change in $LOAD section content (i.e., modifying existing module content,
adding to an existing module, deleting an existing module, or adding an entire
new module) requires that the entire $LOAD section be entered via the card
reader. The operator must respond YES to the *REPLACE? question or REPL to the
*BOOT SOURCE: AUTO OR REPL? question during the bootload sequence. Existing
load file contents are replaced by the current $LOAD section.
If patched modules are loaded via the $LOAD section, all OCTAL correction
statements must immediately precede the $ DKEND statement of the module.
Patches contained in the $PATCH section of the Startup job stream are not
applied to modules included in the $LOAD section.
Modules modified via alter corrections can be loaded via the $LOAD section by
(1) generating a compressed deck (COMDK) of the module; (2) using the COMDK and
all applicable alters to compile the module; and (3) inserting the resulting
binary deck (delimited by $ OBJECT and $ DKEND statements) into the $LOAD
section.
Because $LOAD section modules are resident in main memory during system
operation until the next bootload, it is recommended that discretion be used
when specifying a module to be included in this section. A block of memory
equal to the size of the module is dedicated to module storage.
)
$ GHCM And $ SHCM Statements
Most GCOS 8 system modules a~e sh~~~__modq~~§ and are loaded into the Segmented
Hard Core ~onitor (SHCM) portion of memory. Each shared module is assigned its
own segme-;t-'~rnthe HC~r:Shared modules include those which are identified as Segmented HCM (SHCM) and
Shared Slave Service Area (SSSA) modules. When loading SHCM and SSSA modules
via the $i~CtIon;'~th~odules must be preceded by a $ SHCM statement.
The format for the $ SHCM statement is:
1
8
$
SHCM
Some system modules are not shared modules and must co-exist with other
modul;,eJi. These modules must be loaded in'tOthatj)OrtiOriO?''''memory'''''kDOWn as the
Grouped Hard Core Monitor (GHCM).
/
n
4~,_~AoI
~
Nonshared modules include those which are categorized as Grouped HCM (GHCM),
Full SSA (FSSA), and Half SSA (HSSA). When loading GHCM, FSSA, and HSSA
modules via the $LOAD section, the modules must be preceded by a $ GHCM
statement.
5-191
DH18-03
The format for the $ GHCM statement is:
1
8
$
GHC~
(
If Startup encounters a module erroneously situated following a $ SHCM or
$ GHCM statement, the message:
.OBJECT DECK CARD nnnnmmmm IS NOT hhhh TYPE, DECK SKIPPED
(where nnnn
issued.
= statement
number, mmmm
= module
name, and hhhh
= SHCM
or GHCM) is
NOTE: Modules loaded into GHCM via the $LOAD section are loaded and initialized
in the order in which they appear in the $LOAD section, and before any
other modules that would normally reside in GHCM. DNET and ROUT both
reside in GHCM, and it is a system requirement that DNET be initialized
before ROUT. Therefore, ROUT must not be placed in the $LOAD section
unless DNET is also placed there, and DNET must come first. If only ROUT
is to be replaced, use the $ FILDEF and $ SYSTEM statements, not the
$LOAD section.
(
5-192
DH18-03
APPENDIX A
STARTUP JOB STREAM EXAMPLE
The Startup job stream in this appendix is for example purposes only and is not
to be construed as a working job stream. Comments regarding statement formats
and specific data on individual statements are minimized. Refer to Section 5
for a complete description of the statement formats and for annotated examples.
1
1
8
6
$CONFIG "SYS-C1 SR3000 OSI TEST SYSTEM"
$
SYID
SYC1
$
BASE
IOM-4,DN-8
$
ANSWER RETCONFIG/NO
$
ANSWER INITIALIZE/NO,EDIT/NO,SSCLEAR/YES
$
ANSWER RESTART/NO,SYSOTRCVY/NO,SCF/NO,TlME/NO
$
ANSWER DUMPON/TAPE,DUMP/ALL
$
ANSWER PROCERROR/YES
$
INFO
SCHSAV
$
INFO
LOGON
$
INFO
TS8
$
INFO
SA VDMPIANY
$
INFO
FNP/2
$
INFO
RLSPNT
$
INFO
ACALL/1
$
INFO
ACALL/2
$
INFO
ASCII
$
INFO
ACALL/TS1
$
INFO
CATFNC/5000
$
INFO
CATDUP,SMCDUP/ST2
$
INFO
CCACHE/30
$
INFO
CHKSUM
$
INFO
CLENPT
$
INFO
DEN16/DEN16
$
INFO
DPSE
$
INFO
EXTTDS/12,230
$
INFO
EXTTSS/61,512,1
$
INFO
EXTTSS/61,512,2
$
INFO
EXTTSS/61,512,3
$
INFO
EXTTSS/61,512,4
$
INFO
PSUMl487
$
INFO
FMSCT/100
$
INFO
FMSTAT
$
INFO
GEOTRC/777777
A-1
DH18-03
1
1
8
6
$
INFO
INFO
INFO
INFO
INFO
INFO
INFO
INFO
INFO
INFO
INFO
INFO
INFO
INFO
INFO
INFO
INFO
INFO
INFO
INFO
INFO
INFO
TRACE
MCT-O
IOM-O
IMU-1
IOM-O
IOM-O
ETC
ETC
ETC
ETC
ETC
ETC
ETC
ETC
IOM-O
ETC
ETC
ETC
ETC
IMU-1
ETC
ETC
ETC
ETC
ETC
ETC
ETC
ETC
HEX/ON
INTERRUPT/ALL
LIMITS
MCPTSS/4
MEMORY/240
MODULE/.MSDCB
MIXED
NDFMAP
NIAST/RMVBL
PSHWSN/15
PT1SIZ/2048
RESVID/PPSONL,P1,P2,P3/
RESVID/PPSONL,P4,P5,P6,P7,P8,P9/
RESVID/FORMS,F1,F2,F3,F4,F5,F6,F7,F8,F9/
SLINKS/4000
SSAOVL/16
SYBRT/200
SYJOT/5000
SYSOUT/50000
SYSTEMMAP/NO
TAPDEN/DE
TIMEZ/MST
0,0,0,0
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
4096,~ORT-3,IOM-O,PORT-2,IMU-1,PORT-4,PRO-O,PORT-5,PRO-1
PUB-30,CS66,TY1,TY2,TY3,TY4
CH-30, CS66, TY5
PUB-31,RMC66"TR1
PUB-12,MS0450,UNITS-08,NONSEQ,
UNIT-11,ST1,S-H304,AU-1,
UNIT-12,ST2,S-C413,AU-1,
UNIT-13,ST3,S-C443,AU-1,
UNIT-14,ST4,S-C730,AU-1,
UNIT-15,ST5,S-C885,AU-1,NOFMS,
UNIT-16,RP1,S-C544,RMVBL,
UNIT-17,RP2,RMVBL,
UNIT-18,RP3,RMVBL
PUB-14,MS0501,UNITS-04,NONSEQ,
UNIT-57,NM1,S-S543,
UNIT-58,NM2,S-S544,
UNIT-59,NM3,NOFMS,S-S545,
UNIT-60,NM4,NOFMS,S-S546
CH-44,MSC1B,UNITS-10,NONSEQ,
UNIT-1.0,DP1,AU-1,
UNIT-1.1,DP2,NOFMS,AU-1,
UNIT-2.0,DP3,
UNIT-2.1,DP4,
UNIT-16.0,ET1,MSD1B,
UNIT-16.1,ET2,MSD1B,NOFMS,
UNIT-16.2,ET3,MSD1B,
UNIT-17.0,ET4,MSD1B,
DH18-03
1
S
1
6
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
***EOF
ETC
ETC
IOM-O
ETC
ETC
ETC
ETC
ETC
ETC
ETC
ETC
IOM-O
IMU-1
IMU-1
IOM-O
IOM-O
IMU-1
IMU-1
IMU-1
IMU-1
ETC
ETC
ETC
ETC
ETC
ETC
XBAR
XBAR
XBAR
XBAR
GROUP
XBAR
GROUP
MPC-O
ETC
MPC-1
MPC-2
ETC
URP-4
URP-5
URP-7
URP-8
TRAINS
FILCREA
AUT OLD
LOADFIL
DECKFIL
GCOSFIL
UNIT-17.1,ET5,MSD1B,RMVBL,
UNIT-17.2,ET6,MSD1B,RMVBL
PUB-1S,TAPE*610*9,CD,S2000,UNITS-OS,NONSEQ,
UNIT-01,DE9,1T1,CLASS-3,
UNIT-02,DE9,1T2,CLASS-3,
UNIT-03,DE9,1T3,CLASS-3,
UNIT-04,CD9,1T4,CLASS-2,
UNIT-05,BCD9,1T5,
UNIT-06,BC7,1T6,
UNIT-07,BC7,1T7,
UNIT-OS,DE9,1TS,CLASS-3
PUB-24,PR1600,UNITS-1,UNIT-1,TRAIN-0764,136,PR3,DEDICATED
PUB-24,CR1050,UNITS-1,UNIT-1,CR2,510PT
PUB-25,PC0120,UNITS-1,UNIT-1,PU2
PUB-2S,6632-0,LINES-200
DNSI9911 DIOCOO NODENAME=SYC1
PUB-29,6632-1,LINES-200
DN810365 DIOA80 NODENAME=SC1S
PUB-29,UNCP,FE2
DNSI0365 DIOCOO NODENAME=SC1X
PUB-16,PR1600,UNITS-1,UNIT-1,TRAIN-1130,136,PR1
CH-32,PR1201,UNITS-1,UNIT-1,TRAIN-1130,136,PR2,DEDICATED
PUB-52,TAPE*FIPS*9,DE,UNITS-6,NONSEQ,
UNIT-OO,DE9,2TO,CLASS-3,
UNIT-01,DE9,2T1,CLASS-3,
UNIT-02,CD9,2T2,CLASS-2,
UNIT-03,DE9,2T3,CLASS-2,
UNIT-04,CD9,2T4,CLASS-2,
UNIT-05,DE9,2T5,CLASS-2
IOM-O,PUB-14,PUB-15
IOM-O,PUB-12,IMU-1,PUB-40,PUB-41,IOM-O,PUB-13
IOM-O,PUB-1S,IMU-1,PUB-20,PUB-21,IOM-O,PUB-19
lMU-1,CH-44,CH-45,CH-46,CH-47
IMU-1,CH-44-47
lMU-1,CH-52,CH-53,CH-54,CH-55
IMU-1,CH-52-55
SIZE-4,PSI-O,IOM-O,PUB-12,PUB-13,
PSI-2,IMU-1,PUB-40,PUB-41
SIZE-16,PSI-O,IOM-O,PUB-14,PUB-15
SIZE-4,PSI-O,IOM-O,PUB-18,PUB-19,
~~p610 3252
PSI-3,IMU-1,PUB-20,PUB-21
IMU-1,PORTS-2,PUB116
IOM-O,PORTS-2,PUB-24
IMU-1,PORTS-2,CH-32
IMU-1,PORTS-2,CH-24
402/764/GCOS,LONG,402/1130/ASCII4
FASTBT,ST2,FASTBOOT
ST1,SOO LLINKS
ST3,SR2LOAD,500
DECKFILE,1900/0
ST1,ST2,ST3,ST4,NM1,ET1,DP1
A-3
DH1S-03
8
1
1
6
(
$INITIALIZE
"SR3000 INITIALIZE"
$
INIT
ST1,CAT,ST2,CAT,ST3,CAT,ST4,CAT,ST5
$
INIT
NM1,CAT,NM2,CAT,NM3,NM4
$
IN IT
ET1,CAT,ET2,ET3,CAT,ET4,ET5,ET6
$
INIT
DP1,CAT,DP2,DP3,DP4
$
INIT
RP1
$
OBJECT HTND DU MPCB
CON
G
861028MPCBOOOO
$
DKEND
15.330102886MPCB0107
$
READIN 2T0""DEN16
···EOF
$EDIT
"SR3000 S8.19 I G8.20 I N8.17"
$
FILDEF ST2,SYSLIB,1500/0,RDM,1T2,DEN16,LABEL/SOFTW-SYSLIB
$
FILDEF ST3,VS-PRlMARY,8000/0,SYS,.,LABEL/VS-PRIMARY
$
FILDEF ST4,TSS,1200/0,SYS,·,LABEL/TSS-SUB-SYS
$
FILDEF NM1,SOFTW-P1,2000/0,SYS,.,LABEL/SOFTW-PART1
$
FILDEF ET1,SOFTW-P2,2800/0,SYS,*,LABEL/SOFTW-PART2
$
FILDEF DP1,SOFTW-P3,2100/0,SYS,.,LABEL/SOFTW-PART3
$
FILDEF NM1,SWI-30,4700/0,SWI,1T3,DEN16,LABEL/SWI-3000
$
DTFILE ST1,SYSPN 3000,15/0
$ *M*
SYSPNC.SPWN ••*SYSTEM SPAWN FILE FOR - SYSPN (COLD BOOT)
$
MODULE: SYSPNC.SPWN
$
FILSYS DUMP
$
PRIVITY
USERID SYS SOFTWARE
RESTORE SYS SOFTWARE,RESET/DEVICE/,RESET/RFILES/,RESET/DENIEDI
CM SYS SOFTWARE,MODIFY/OPNSUTIL,SYS CATI
$
-SYSOUT ER
$
TAPE9 PR,P1D"99999,,SYS SAVES
$
MSG2
1,PLEASE MOUNT THE-LATEST SYS SOFTWARE SAVE TAPE.
$
~ll
$
UTILITY
$
FUTIL IN,OT,REW/IN,OT/,COPY/1FI
$
PRMFL IN,Q,L,SYS SOFTWARE/3000USERDATA/SYSPN.PRE
$
PRMFL OT,W,L,SYS SOFTWARE/3000USERDATA/SYSPN.DIRECT
$
RUN
RUFILE~SYSTEM,RUNAME=SYSPN,OPTIONS=DUMP,SSDUMP,NJREST
$
PRIVITY
$
LIMITS 10
$
RESOURC RSPACE=100K
$
PRMFL I*,R,S,SYS SOFTWARE/3000/DATA/SYSPN.COLD
$
ENDJOB
$
ENDTF
$
DTFILE ST2,SYS_MEMREL,2/0
$
IDENT P23GFA,MCDONALD,STA-AX
$
PROGRAM MEMREL,DUMP,NJREST
$
LIMITS 10,100K
$
PRIVITY
$
ENDJOB
$
ENDTF
.C.
DH18-03
~
1
1
8
6
,
,
,
,
,
,
,
,
,
,
,
$
,
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
FILDEF
SSFILE
ETC
DP1,BRT7-3000,20/0,SYS,1T3,DEN16,LABEL/BRT7-3000
ST3,ASC-SOFTW,2700/0,SYS,1Tl,DEN16
"56702"
ST1,COBOL-74,1100/0,SYS,lT8,DEN62
42701
ST4,PDQ,10/0,SYS,.
NM1,IDS2,3500/0,SYS,.
ST1,8DS2.2-S0FTW,300/0,SYS,.
ST4,8FT2.1-S0FTW,700/0,SYS,.
ST4,8F77-S0FTW,1000/0,SYS,.
ST2,DMS-SOFTW,1800/0,SYS,.
ST2,MENU,50/0,SYS,.
ST4,PCF-SOFTW,200/0,SYS,.
DP1,8PL3.3,1500/0,SYS,.
ST3,PDQ-SYS,5300/0,SYS,.
ST1,RPG2,20010,SYS,.
ST1,PSPSW-SYSLIB,1300/0,RDM,.
ST2,IFAD,1000/0,SYS,1T4,DEN16,LABEL/30-IFAD-QS06
ST2,ELAN,1200/0,SYS,1T2,DEN16,LABEL/W2ELN0830040
ST3,8FM3.0,400/0,SYS,1T3,LABEL/8FM3.0
TAPEI37390
NM1,ACCNTO,1200
ET1,ACCNT1,1200
ST2,LUMPO,150
ST1,DUMPO,100010
ET1,DUMP1,26500/0
ET1,PRINTIMAGE,85
ET1,SYSOUTO,19000
DP1,SYSOUT1,19000
ET1,SYSOUT2,19000
DP1,SYSOUT3,19000
ST2,TANDFILE,7000
ST1,.EXPRS/100,.HOLD/09,.NORM/100,
.IMCV/l00,.NNNNT/100,.NNNNZ/100
$
,
,
$
,
$
$
$
$
$
~/
$
$
$
$
$
$
$
$
···EOF
,FILES "SR3000 FILES"
$
SYSTEM SWI-30
$
PFILES SWI-30
$
DFILES SYSPN 3000
,
DFILES SYS MEMREL
,
LIBRARY RDM~SYSLIB,RDM,PSPSW-SYSLIB
$
SYSTEM ELAN
$
PFILES ELAN
$
SYSTEM VS-PRIMARY
$
PFILES VS-PRIMARY
$
SYSTEM TSS
$
PFILES TSS
$
SYSTEM SOFTW-Pl
$
PFILES SOFTW-P1
$
SYSTEM SOFTW-P2
$
PFILES SOFTW-P2
$
SYSTEM SOFTW-P3
$
PFILES SOFTW-P3
A-5
DH18-03
1
1
8
6
$
$
$
$
$
SYSTEM
SYSTEM
PFILES
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
SYSTEM
PFILES
PFILES
PFILES
SAVE
PFILES
PFILES
PFILES
ACCOUNT
SCFDSP
SCFBUF
SYSOUT
SSLOAD
ETC
BRT7-3000
IFAD
IFAD
8FM3.0
PCF-SOFTW
PDQ-SYS
COBOL-74
8PL3.3
PDQ
IDS2
8DS2.2-S0FTW
8FT 2. 1-S0FTW
8F77-S0FTW
ASC-SOFTW
DMS-SOFTW
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$
···EOF
$PATCH
MENU
RPG2
AUTOLOAD
DECKFILE
TANDFILE
LUMPO
DUMP 0
DUMP 1
PRINT IMAGE
RDM,ACCNTO,ACCNT1,IDS
288,ALL
288,ALL
SYSOUTO,SYSOUT1,SYSOUT2,SYSOUT3
MAX/400,MIN/5,.TASK/10,.EXPRS/50,.NORM/40,.IMCV/5,
.NNNNT/20,.NNNNZ/20
~
"PATCH SECTION"
OCTAL patch corrections
···EOF
$LOAD "SR3000 LOAD SECTION"
SHCM
$
.
$
Modules that are loaded into Shared HCM
GHCM
Modules that are loaded into Grouped HCM
···EOF
···EOF
A-6
DH18-03
APPEIDI! B
FUNCTIONAL CHECKLISTS
The purpose of this appendix is to provide a series of quick-reference,
functional checklists that should be reviewed when installing a new system or
whenever Startup job stream modification is required. For example, the
checklist of statement and operator procedures should be reviewed when
re-creating the AUTOLOAD file.
So that the checklist or "cookbook" concept is maintained, detailed statement
formats and operator procedures are not included in this appendix. Refer to
Section 5 for statement formats and for descriptions of individual statements
and to Section 2 for detailed operator procedures.
STARTUP JOB STREAM - NEW INSTALLATIOR
J
The following discussion concentrates on statements that either are required in
or should be considered for inclusion in the Startup job stream when installing
a new system.
Startup Statements
Discussion
----------------------------.----------------------------
$CONFIG Section
Reflects the site's gross software and hardware
configuration.
$ SYID
Can be used to specify
the dump banner. This
systems. In addition,
Release is useful when
offsite Honeywell Bull
$ TRACE
All system traces normally are active when installing a
new system. This assists in isolating initialization
problems. However, this statement can be used to
selectively deactivate traces that are not to be used.
B-1
the system name that is to print in
is helpful if the site has multiple
identification of the Software
the site is communicating with
personnel.
DH18-03
Startup Statements
Discussion
------------------------------------------------------
$ ANSWER
Messages that otherwise are issued to the system console
and that require an operator response can be
pre-answered. It is recommended that the following
responses be included on the $ ANSWER statement at this
time. Additional responses (e.g., dump-related responses)
can be included at site discretion.
TIME/NO
EDIT/NO
INITIALIZE/NO
SCF/YES
SSCLEAR/NO
RESTART/YES
It is recommended that a system map be printed during
system installation to assist in problem analysis.
Thereafter, the SYSTEMMAP/NO response can be included on
the $ ANSWER statement to forego printing of the system
map.
$ INFO
It is recommended that the following parameters be
specified. Additional parameters can be included at site
discretion.
SMCDUP - Provides a duplicate System Master Catalog (SHC).
DENxx/DENyy - Defines the default high and low densities
of an MPC-driven magnetic tape subsystem.
It is recommended that the NDFMAP parameter not be
included during initial installation procedures (i.e.,
that a deckfile map be printed to assist in problem
analysis). Thereafter, the NDFMAP parameter can be
included on the $ INFO statement to forego printing of the
deckfile map.
The FNP/n parameter or the $ BASE statement is required if
any Network Processors (DNET/ROUT mode) are configured.
I
The GENSYS parameter is required if the system is to
execute the Generalized Tape Management System.
The MIGRAT parameter is required to migrate a 4/JS3 system
to execute under GCOS 8.
When a Page Processing System is configured into the
system, either the RESVID/PPSOFL,id1[id2 ••• ]/ or the
RESVID/PPSONL,id1[,id2 ••• ]/ parameter must be specified but not both. A maximum of 64 ids can be specified.
The NIAST ALL option is implied for all shared systems.
B-2
DH18-03
c
Startup Statements
Discussion
The EXTTSS/xxx,yyy,zzz option must be specified for all
Time Sharing systems.
The OWNID/xxxxxxxxxxxx option must be specified when
processing FIPS-79 tape labels.
PROEXT must be specified when the six processor
functionality is to be utilized.
$ BASE
Can define the maximum site mainframe configuration (i.e.,
number of input/output controllers, network processors
(DNET/ROUT mode» and the maximum amount of space
allocated to memory-resident tables (e.g., ASTs). The
$ BASE statement must precede any $ Iyy or $ MCT
statements.
$ MCT
Defines the memory-processor-input/output controller
configuration and connectability relationships for DPS 8
and DPS 90.
$ CIU
Defines the memory-processor-input/output controller
configuration and connectability relationships for DPS 88
and DPS 8000.
$ Iyy
A series of input/output controller statements must be
included to define the system's peripheral and
communications configuration: mass storage subsystem,
magnetic tape subsystem, unit record devices, consoles,
and remote processors.
$ URP
Define each Unit Record Processor (URP800n) and all active
unit record peripherals controlled by that URP800n. Unit
record devices can also be specified on $ Iyy statements.
$ MPC
Defines the physical configuration of the MPC (i.e., the
physical connection of the MPC and PSI channel to the
input/output controller (Iyy) channel). Consult with the
site's CSD representative for the exact physical
relationship of these components.
There is a direct relationship between the $ Iyy and $ MPC
statements. Each input/output controller channel (CH/PUB)
number specified on $ Iyy statements must also be
identified on $ MPC statements. The following example
defines 10M channel 8.
B-3
DH18-03
Startup Statements
Discussion
c
1
$
8
IOM-O
PUB-8,MS~450,UNITS-4
$
MPC-1
SIZE-4,PSI-O,IOM-O,PUB-8
1
6
$ CHAN
A tool which allows channel switching for devices during
the Startup process. No limit is set on the number of
$ CHAN statements that can be used in a Startup job
stream.
$ UNIT
Allows a switchable device or either of two separate
devices to be referenced by the same logical name during
startup. Any number of $ UNIT statements are permissible.
$ GCOSFIL
Identifies devices on which files that are defined in the
$EDIT section can reside.
$ XBAR
Defines the crossbar configuration (i.e., multichannel
access) of the mass storage and/or magnetic tape
sUbsystems.
$ LOADFIL
Identifies the mass storage device on which the $LOAD
section of the Startup job stream (i.e., the load file) is
to reside.
$ IMAGE
Defines the character set to replace'the default character
set.
If used, the $ IMAGE statement must precede the $ TRAINS
statement and must be continued by using successive
$ IMAGE statements (i.e., $ ETC statements are not
, permitted). If the conditions are not adhered to, Startup
aborts~
$ TRAINS
Defines the character sets that are available on
high-speed printers.
$ SHARED
Defines permanent mass storage devices on a specific
system' to be shared with the Network Processor Supervisor
(NPS). Removable devices cann'ot be shared., The NIAST
option of t'he $ INFO statement is automatically activated
when $ SHARED is specified.
$ AUTOLD
Defines the size of the AUTOLOAD file, which accommodates
the Startup program and job stream and is used when
rebooting the system, and the mass storage device on which
the file resides.
B-4
DH18-03
Startup Statements
Discussion
--------------------------------------------------------
$ DECKFIL
Identifies the size of the deck file (which resides on the
AUTOLOAD device).
$ MPCFIG
Should be included to identify the firmware revision level
that is to be bootloaded to a specific MPC. Consult with
the site's CSD representative for the correct firmware
revision identifier.
$INITIALIZE Section
Provides the basis for mass storage device initialization
and is the means by which firmware is written to and read
from the deckfile.
$ INIT
Identifies each mass storage device to be initialized
(i.e., existing pointers and tables on the device are
cleared and rebuilt). Any special parameters associated
with a device (e.g., allocation unit size or device
availability for FMS catalogs) also must be included.
It is recommended that $ INIT statements be removed from
the Startup job stream after the system is initialized.
Removal prevents accidental initialization of mass storage
devices (i.e., an operator response of YES to the
-INITIALIZE? question). The statements can be replaced in
the Startup job stream when initialization is desired.
MPCB Deck
Bootloads the MPC firmware.
Mass Storage
Firmware
Bootloads the mass storage controller.
(This deck enables mass storage initialization.)
Magnetic Tape
Firmware
Bootloads the magnetic tape controller. (This deck
enables reading of the tape that contains MPC firmware.)
$ READIN
Defines the device on which the firmware tape is mounted.
D, 0, A, L, Y
Space-definition statements that are used to identify
defective space on mass storage devices. If these
statements are included in the Startup job stream, also
include $ DIRECT ••• /CLEAR and $ DIRECT statements. D, 0,
A, L, and Y statements define defective space on the
following bases.
D - Cylinder and head numbers
0 - Beginning and ending sector numbers (octal)
A - Beginning and ending word numbers (octal)
L - Beginning link and number of links (octal)
y - Beginning llink and number of llinks (octal)
B-5
DH18-03
I
Startup Statements
Discussion
$EDIT Section
Each device identified in this section also must be
defined on a $ Iyy statement in the $CONFIG section.
$ FILDEF
Defines all system files and the devices on which the
files are to reside. Some specific files must be
created. (Note that the files for which the RDM option is
included must be identified on a $ LIBRARY statement in
the $FILES section and files for which the SYS option-is
included must be identified on a $ SYSTEM statement in the
$FILES section.)
DUMPO - This file is used by .MDUMP to store overlays and
swapped memory. If DUMPO is 200 llinks it will also be
used to store an error snap of .MDUMP. This file can
be created on a specific device or can be assigned to a
device by Startup.
DUMP1-DUMP9 - Used to store dump information.
nine files can be defined.
From one to
SYSOUT Files - Files to which system output is spooled.
The device on which each file resides must also be
specified. It is recommended that each file be
assigned to a different device, and - to avoid further
contention problems - that no SYSOUT files be assigned
to device ST1.
All SYSOUT files must be the same size. If the files
have different sizes, the smallest size specified is
assigned by default to all files.
All SYSOUT files also must be identified on $ SYSOUT
statements in the $FILES section.
PRINTIMAGE - Startup writes all printer character set and
VFC images to this file, which is used to reload and
re-create these images during subsequent bootloads.
*
SCF - Define the mass storage device to which the
Statistical Collection File (SCF) is assigned. The
file also must be defined on the $ ACCOUNT statement in
the $FILES section.
B-6
DH18-03
~
Startup Statements
Discussion
--------------------------------
$ SSFILE
Defines System Scheduler job classes and class sizes.
Additional parameters are specified on the $ SSLOAD
statement in the $FILES section.
$ DTFILE/$ ENDTF
The $ DTFILE cues Startup that the statements following it
are user-oriented directives. The directives that follow
give users the ability to edit files for both site options
and JCL, rather than hard-coding them into memory. This
feature also provides default workstation initiation JCL
for SYS SOFTWARE. The $ ENDTF statement is required to
terminate this function.
$FILES Section
Identifies files that are to be used for the duration of
the current bootload. Each of these files also must be
identified in the $EDIT section.
$ ACCOUNT
Identifies the device on which the Statistical Collection
File (SCF) resides and specifies file-related
characteristics (e.g., buffer size).
$ ACCBUF
Specifies record types buffered before being written to
the SCF, whose buffering disposition cantbe changed via an
operator request, and identifies the maximum record type
buffered. The $ ACCBUF statement cannot be used when more
than 36 accounting record type are required (use $ SCFBUF
instead) •
$ SCFBUF
Provides extended processing capabilities for a maximum of
288 accounting record types (compare to $ ACCBUF
statement). This statement must be used when operating
under the Tape Management System (GTMS) and must precede
any $ SCFDSP statement.
$ SCFDSP
Defines the accounting record types which can have their
status changed from the console. The $ SCFDSP statement
must be preceded by a $ SCFBUF statement.
$ SYSTEM
-------.- .. -----
Identifies files containing system programs that are
necessary to site operations. A maximum of 32 files can
be defined.
File sizes and the device on which each file resides must
be specified on $ FILDEF statements in the $EDIT section.
(The $ FILDEF statements must include the SYS option.)
$ LIBRARY
Identifies a maximum of two random program files that also
were specified on $ FILDEF statements in the $EDIT
section. (The $ FILDEF statements must include the RDM
option. )
B-7
DH18-03
I
Startup Statements
Discussion
--------------------------------~----------------------
$ SSLOAD
Defines System Scheduler job class parameters (e.g.,
maximum number of jobs that can be scheduled from one job
clas's) •.
$ SAVE
Def~nes
$ SYSOUT
Defines all SYSOUT collection files.
$ DFILES
the Save file (i.e., a file named LUMP).
. Causes the referenced file to be cataloged as a linked
'sequential file und,er SYS CAT and allows GEIN to read
$ DTFILE related JCL statements.
$ PFILES
Identifies Startup-created files that are to be cataloged
by FMS for subsequent access by users.
$PATCH Section
Contains OCTAL correction statements that are to be
applied .to GCOS programs and to software programs that
were edited by Startup onto the system.
$LOAD Section
Allows object deck images of modules to be loaded directly
into main memory. Each module included in this section
also is written,to the load file on mass storage. This
section often is used to add new or to replace existing
operating system programs.
Refer to "Bootload Phases" in Section 2 for operator procedures to bootload the
system.
B-B
DH18-03
MASS STORAGE SUBSYSTEM - INITIAL CONFIGURATION
The following statements require special attention when initially configuring
the site's mass storage subsystem.
Startup Statements
Discussion
--------------------------------------------------------
$ !MU, $ IMX, $ 10M, Defines each mass storage device and its physical and
$ lOP, or $ lOX
logical relationship to other components in the
subsystem. The following fields deserve particular
attention.
UNITS - The number of units specified in this field must
equal the combined number of mass storage units defined
in the UNIT fields.
AU - The default AU value is 1 for all devices except
MSU0501, MSC1B, and MSD1B, which have a default value
of 8.
RMVBL - There are two advantages to defining several mass
storage devices as removable (RMVBL). First, only
permanent (PERM) devices must be initialized during a
total system initialization. Second, the procedure for
redefining a mass storage device is much easier when
changing the definition from RMVBL to PERM than from
PERM to RMVBL. (Refer to "Redefining A Mass Storage
Device" in this appendix for additional information.)
)
The RMVBL parameter cannot be used for a device defined
as shared.
Logical Device Name - Each device must be uniquely
identified by a logical device name. One mass storage
device must be named ST1.
CH/PUB - The CH/PUB number must agree on $ Iyy, $ MPC,
and $ XBAR statements. If multiple device types (e.g.,
MSU0402 and MSU0451) are configured on the same PSI,
each CH/PUB (string) is defined on a separate $ Iyy
statement.
$ MPC
All CH/PUB numbers that are included on $ Iyy statements
must be defined on $ MPC statements.
The first PSI specified on this statement is the PSI over
which bootloading occurs.
$ XBAR
If the mass storage subsystem is crossbarred, all
channel (CH/PUB) numbers that are identified on $
statements must be included on $ XBAR statements.
or CH number included on the $ Iyy statement must
first defined on the associated $ XBAR statement.
B-9
Iyy
MPC
The PUB
be the
DH18-03
Startup Statements
Discussion
-----------------------------------------------------A CH/PUB number cannot be defined on more than one $ XBAR
statement.
c
The following example reflects the relationship among
$ 10M, $ MPC, and $ XBAR statements.
1
$ INIT
1
8
~
$
$
$
$
$
IOM-O
IOM-O
PUB-B,MS0400,
PUB-9,MS0450,
SIZE-4,IOM-O,PUB-B,PUB-9,PUB-10,PUB-11
IOM-O,PUB-B,PUB-10
IOM-O,PUB-9,PUB-11
~C
XBAR
XBAR
A $ INIT statement must be included in the Startup job
stream for each configured mass storage device during
initial installation. The following fields deserve
particular attention.
CAT - FMS catalogs can be created on this device. It is
recommended that several devices be made available for
this purpose. This approach allows expansion of the
FMS catalog structure. In addition, if FMS catalogs
are not allowed on any devices, catalogs are restricted
to device ST1. This practice can impact system
efficiency.
AU - The default AU value is 1 for all devices except
MSU0501, MSC1B, and MSD1B, which have a default value
of B.
$ INFO
A configured mass storage device can be released via the
RLSDSK option (e.g., the device must be released for
maintenance).
B-10
DH18-03
(
MAGNETIC TAPE SUBSYSTEM - INITIAL CONFIGURATION
11\I
The following statements require special attention when initially configuring
the site's magnetic tape subsystem.
,J
Startup Statements
Discussion
----------~
--- ...
~. ~~---
$ lMU, $ IMX, $ 10M, Define each magnetic tape device and its physical and
$ lOP, or $ lOX
logical relationship to other components in the
subsystem.
attention.
The following fields deserve particular
CH/PUB - The Iyy channel number must agree on $ Iyy,
$ MPC, and $ XBAR statements.
Logical Device Name - Each device must be uniquely
identified by a logical device name.
UNITS - The number of units specified in this field must
equal the combined number of magnetic tape units
defined in the UNIT fields.
Subsystem Component Characteristics - Three fields (device
type, density code, and magnetic tape characteristics)
combine to define the physical characteristics of
magnetic tape subsystem components.
"- \
The device type and density fields define characteristics
of most of the devices in the sUbsystem. The magnetic
tape characteristics field defines individual magnetic
tape units that are exceptions to information specified in
the other two fields.
I
/
For example, if six MTS0500 units have nine-track and
800/1600 bpi capabilities and two MTS0500 units have
seven-track and 556/800 bpi capabilities, the following
fields must be included on a $ Iyy statement.
TAPE*500*9,CD
UNIT-5,BC7
UNIT-6,BC7
$ MPC
All CH/PUB numbers included on $ Iyy statements must be
defined on $ MPC statements.
$ XBAR
If the magnetic tape subsystem is crossbarred, all Iyy
channel (eH/PUB) numbers that are identified on $ MPC
statements must be included on $ XBAR statements. The
CH/PUB number included on the $ Iyy statement must be the
first defined on the associated $ XBAR statement.
A CH/PUB number cannot be defined on more than one $ XBAR
statement.
B-11
DH18-03
c
The\'.T(jl'l~owlrtg': statein~htts re:4tiir·e·~ ,speclal LS.l'teiiti6n-s when initially' conri~tlt"ing
the site's unit record d e v i c e s . ' ·
Startup Statements
'"L;,·.
.
,"
<,.'
"
C,l
Discussion
----------~--~~~~==~~~~~~~---
$ lHO ';"$::lMX,:;.:,~$:'IOM:f·,,'Der-1ne's;Je;acb unit l'"·e~6rd·:~,;4ev1ce ;ti-~e';"~ p~iriters}',card,
$ lOP, or $ i:OX ~'.
.'punobe,s:;and i ca'l"d ;readers);:"ana its! pflysical and logical I"
~~:\:r.e:latiQhshi'P .to::' otbe't"r componel1'ts:? 1ft \ t,he configuration.
One $ lyy statement is required1fdi'>}each device. The
following fiel~s deserve,particu~ar attention.
'"
Logicalt~Devj;ce;::Name:I':~YEacn"device
must be uniquely
identified by a logical device name.
.. ",-:~
. ';(1.
CH/PUB·i;';'lThe·':[yy.:,cbai'inel.
$ MPC statements.
~) '... c·'''~ ~~.
.,:'~. ~
r
/
numbEd~imust
agree on $ Iyy and
~~1
". LTR:AJ:N:;";-'~(WhelF:defih'ing(a':'prin~er;;:ithe character. set code
must be;::ldentiried'" irithiif"'riele,.numt>e~~d:~.~equel'ltially (i.e., 0, 1, 2
and' not ,0 .. ,2,., 3) ,.:~ ."
. ., ,
.
.
~
-'"
2. $ Iyy statements must· s~qu~ntially,~.define DJ),TtNET,.,Network Processors in
the Startup job stream.
For example,
1
8
" 6
---------.- ... --1
,. IOH~'"
PUB~p ,6620-0,'
';IOM~1.PUB-p,6620""1
IOM-1
PUB-p.6620~2
" ,$:'
,$
$
and not
."
1
8
$,
IOM~1
$
IQM-'1
IOM-1
1
",6:,
~~~--~~------------~--.------------------
$,,'
:"
"
...
"
~
,"
_---------------------
PUB~p,6620~2,
~UB-p" 66~O-0,
PUB-p, 6620.-1
I,
However, channel (PUB-p) numbers do not
,Ila~e
to :;b,ein sequence.
,3,.,%p.e, value §pecifi~d~inth~: Ll~ES-x field,defines,the,:max~~l(l number 'of;: .
u:;ser's ithat ",oan,.be con~~ct~q,'J~.t., anYQne time.
,l'
Therefore, if the value x is less than the number of lines configured and
available, the undefined lines are not available for use. For example,
if 50 lines are configured but LINES-20 is specified on the $ Iyy
statement, only 20 users can be connected at one time.
DH18-03
If the value x is greater than the number of lines configured and
available, no more lines than are configured can be used. For example,
if 50 lines are configured but LlNES-60 is specified on the $ Iyy
statement, only 50 users can be connected at one time.
MODln/ADD -SYSTEM FILE
The following statements should be reviewed and operator procedures followed
when modifying an existing system file (e.g., increasing the file size) or when
adding a new system file.
Startup Statements
Discussion
--------------------------------------------------------
$ FILDEF
It a new file is being added, the file name and size and
the device on which, the file is to reside must be
identified.
If the size of an existing file is being increased, .it is
recommended that a new file name be assigned and that the
file size be increased. (In addition, the appropriate
changes on the $ SYSTEM and $ LIBRARY statements must be
made. Note that the replaced file continues to exist
after the new file is created.)
If the file merely is being aSSigned to a different
device, identify the device in the logical device name
field. Retain the same file size and name.
$ GCOSFIL
Identify the device to which the file is being aSSigned.
Startup searches devices in the sequence in which they
appear on the $ GCOSFIL statement.
$ lMU, $ IMX, $ IOM, Verify that the mass storage device to which the file is
$ lOP, or $ lOX
assigned is defined.
$ SYSTEM
If a new file is being added, the file must be identified
on a $ SYSTEM statement. Files are searched in the order
in which $ SYSTEM statements are encountered. Therefore,
if the file is to override the content of an existing
file, the $ SYSTEM statement that identifies the new file
must precede the $ SYSTEM statement that identifies the
existing file.
The operator must edit the system file. Respond PARTIAL to the -EDIT? question
that is issued to the system console and respond YES to the -EDIT fffff?
question (where fffff = name of the system file).
B-14
DH18-03
AUTOLOAD FILE AND DECIFILE MODIFICATION
The following statements should be reviewed and operator procedures followed
when modifying either the AUTOLOAD file or the deckfile (e.g., increasing the
size of the deckfile).
Although the AUTOLOAD file and deckfile are not directly related in function,
the deckfile is always created on the same device as the AUTOLOAD file.
Therefore, moving either of the files from one device to another affects both
files.
Startup Statements
Discussion
$ AUTOLD
The size of the AUTOLOAD file normally will not require
modification (i.e., the default size of 600 11 inks is
sufficient). However, moving the AUTOLOAD file from one
device to another automatically moves the deck file from
one device to another. The new d'evice must be identified
on the $ DECKFIL statement.
$ DECKFIL
Changing the size of the deckfile requires that either the
file be assigned to another device or the file remain on
the same device and be renamed. 1£ the deckfile is moved
to another device, the AUTOLOAD file also must be assigned
to the new device.
------------------------------------------------------
As a result of redefining the two files, space that
previously was assigned to the files is lost to the
system.
$ GCOSFIL
Identifies the device to which the files are being
assigned.
$ lMU, $ IMX, $ 10M, Verifies that the mass storage device to which the files
$ lOP, or $ lOX
are assigned is defined.
$ READIN
To re-edit the deckfile, a $ READIN statement is included
in the $INITIALIZE section of the Startup job stream.
The operator must re-edit the deckfile. Respond'PARTIAL to the -INITIALIZE?
question that is issued to the system console. Then, respond YES to the CLEAR
AND OVERWRITE EXISTING DECKFILE? question and YES to the .PROCESS $ READIN?
question.
B-15
DH18-03
LOAD FILE MODIFICATIOI
s~~rr~ga~~a~Im~?5~::j,,·;.D~'7~r.~~Qn:::iit ;:-'~.:J
'3:
i:'jpf';cf:' I: ' j " : ' ,. J.:Y :'1,'.',,;;',.'<; " " J
~1 4~~
$ . ;~o\.,,~.,Df,~~.~:;!::' "G}":·~,~;"~~:·~';::ch~ti~~ij~:,}~h~::~~i~~J;~~kl.~f:~~~~~1~4j~ii~ ",~~q~it~~ ;;1;.~Jt ::~;~~~'Re~\\,:,
J,~..!""., ,>:,,··tn~ filtr'previously"was;':'assigried- ,to
:yU:
:.J,h:: -l:JJ~i:cz~~I~,\,t~ t'?~~O~qAt~~ :,s¥gt~~.':::~
_',J.F
' .. l',t
'0".'
",
$:,~;qRo~r~~n
:~~.}~~~: .. <\.>."~
"'tJ,,:'
t
n,::~~~o·,~,::::.,,;.;~,eRK~r¥~'~~;~,~~c:·4.~l~~?~/~£o ~·:¥§~g~·~t~e.···:file
;,~ ,"':)t':{'ii'\
""'t~";
~~lt'·i.l~'JJ~t:
\1 r,;." S;~··"'» ~ ,,!l::>.,f,: . . _
. .'~Vf:.~;
,:,-~~~,.(; .(~/").:.. ~j:.~
is being assigned.
':''.::j,'~'''~
":'
~.)t~ ;,q};:~~';''' t,~Rf.1"",'-.'V~t!,f;~~'lp~t"lti~ ..~lJlaij~r~~Or:~g~',~eV;~c,e to which the file is
$" IOp';"or'$'"'rox """ ""a~s!gnea is:deJ~1ri~a"~;""~' .',< ' ,,' " ' .. ",
t
..
i'
i·,,~·l.,_.:.;'; '"Y :v~
•.•,.;.;
. ~.
(,th~~~,;'~p~lp~i~~:;,~f~t~~~~~~<,,, s~~Ala:.;:.~~ r~~!~w.~a~.:~A~d;:;qper~~gr':,.procedures
followed
'wh~'rl"modLtyirig"'the' save,wrile" (e~g':', "fhcri~~;p~ ~Q~" fi,le,$ize).
(The Save file
frequently is referred to as the LUMP file': 'However'~" any file name can be
assignep.,. tO"e, ~1l1~': fi~~ • )'i';t
e
,,' ~...... '
'", ......,
'j, ,.
~
.: ,,),' ... ' ".
I f the ~ size of the
~xi§,ting<,\fil~ is being increaseg,:,,~he
file (with" the 's~lIne" file name.):~ ~bQ~~d be assigned' to "a
different device. The new dev1'oe'on the $ GCOSFIL
i".~~a,~~m,~p~.,1P¥:~t .1,!1)e:;,i9~pti.f,i.~d",be~9.~e~, id;~nti.ryiQg, the. 9;~vige
, Oi1 wbfctl' tne" ri,+~';9~rfeil~ly,:;re~~d~~~ Thispreatel~ a.p~w;:'
file of the same'name:" Irow~ver~ the space 'that is
")',
~~;~g,p.~d,::, tp tl1~; ..Q~~,rent,tfile"i~\",.lo.$t to the system. ',:
.L
J .... I.,\,~.,::r,.o<·, ..,.
.:t';:
'> .',,';'.
,.. ,,',,z
','"
"~!j
;.~ "-.-
'I,
~!
.••..•. ,
,. . .
~.,'...
J..,.,.:' :,,,,'1..•
.,~ .",/~.'-;":
~:";"'1'
,,~ .•,.3·
\ .. '.-',.
T~·
,;
;.>..",;.y
t;?'
':
",""'.'
~
- ,.• ,
....,'
.
,',
",
'.,
. """ll' the ril'e }'me~e1y ''iftSEd.ng iissigned to a different
d,'Yf.r:~,~\.'i t:~~\:i~~~~ce<*,~); ~Sl~:lltif,ied ~ in.:".;',. ':>?:'.~:~~~:_~'
Identifies the device
t'C)
>~,_r:~ ';,;;.::. :"
J.~". :~~;
_.~ ',L>f';,'r'" ':"
. J <~,:,.:'
which the file is being a,s~~~~~:fncrea~~riif;';the "::f,i1~ siz~)";;'oi- when
adding another SYSOUT file~~ i:'/" u~':~,\:'1 . 'J:'i,.;- e>,;' :,~::,<",':;.:. '~i": :<1 ~
':"'.::':,J~7'1(:,"'\,,~
,i
$ FILDEF
,,;'
"I~ a ne~ i'ri~«5.',,~s.,:b~~~e; aqd~g";J11~,,t;~:l~nf:la~e ,:~nd}~iz~ ~ran~
the' device on'·~hich·;the' fil'fr,-:rs"t()"res:[q~·'Nis"~deritified.
To avoid device contentiort;'>: :it"''is' t~'c6mm~rid:~d ~ thcii ' StSOUT
,ri~~s,~~,,~~~~g~~~ ~o" . ~,~p~~~t~~:~e~i1~s
,;;,,;;:,;
, It:fhe' ·SiZ~;:'\~f.~~~~;,,~~i~~iqg,~/;i.~';::~$,,~~i~g;·~lrJ9~~a~~~:~,';:~'~;'he
file (with"'~he'~a:mf:('f:t1e' na:m~1"~hoi1r'a b'E"J"'ass:tgned t6"a
.d~fferert?~y,~c~,~,\., T~~.\n~~ '1?ei~ce o~ ~t~~ ~"lqc9~~~~, \," ',;" ,"',
. st~tetne~~,~m1l,~~,~;~~"*qe~~,;r~~d"F~~,f9~~,J~~~n~,~rY;~Qg~~,~,~e:,,?~Y~c;~
onwhiclf'the'fil~ currently ~$s~des."'1h1S creat'es ::i"rtew'
rile or the same name. However, the space that is
assigned to the current fil~'::th~o~~g~~, h~~F~~~" ~Y~~,T~);:':
~fC?n~ ~~~q~'r ,~fi~~,,<~i~~ ,J~;}~,~~~E$.e9, ~]J;i~l~Qy;T ,J=H;e,s ;. ,'\ '
be' cha'
"e~b. g~~:·;~~iiq~~:, . 4~x~qe;':n4~~·~~~*~i~;'~ The
,Identir~~·~':~.t~~'1~~'~Xf.~~(~~6';;·~~i.~hii:,~~·~:::~tfl~:~J~,<'~lj~f;~~\>1~e~gn~d.
$ GCOSF!L
ti~:
:rr~fb~ rOM 'J::~~i!:~)~:~~t,~;~r~~,:s::~~ge 36 record types required 5-117
time interval for writing Time
Sharing accounting data 5-168
Time Sharing accounting parameters
5-184
5-52
5-52
5-52
5-52
510PT
CRU1050 51 column option
ACTIVITY CONTROL WORDS
.MSCN1 ACTIV1 and ACTIV2 5-162
.MSCN1 ACTIV3 5-163
JCL examination and modification by
.MSCN1 5-159
5-174
ABORT
$ IMAGE after $ TRAINS 5-17
ABORT SHARD console verb 4-37
abort Startup 3-5
ABORT/ARCHIVE/ 4-22
ABORT/ROLLBACK/ 4-22
CATDUP without SMCDUP 5-20
fast boot 2-6
Integrated Software memory
allocation abort error message
4-38
memory dump following Startup abort
3-10
operator-initiated 3-7
SDLD abort codes 4-58
site-option patch to abort on faults
outside MME GELBAR limits 5-152
site-option patch to abort on master
mode faults 5-152
Startup abort messages 3-6
Startup aborts 2-34, 2-45,3-1,
3-6,3-21,3-24,5-40,5-47,5-54,
5-76, 5-101, 5-110, 5-112, 5-113,
5-132, 5-137
system abort 5-152
Time Sharing System aborts 5-179
TSS causes GCOS abort 5-179
ACALL
$ INFO option
ADAPTER
controller adapter 5-80
CSU6601 console channel adapter
5-49
Direct Interface Adapter (DIA) 5-64
line adapter 2-10
ADDRESS
Lower Address Limit (LAL)
AIDS
debugging
3-10
ALGORITHM
Time Sharing memory allocation
algorithm 5-174
ALL
$ SECURE ALL option
5-82
ALLOCATION
ALLOCATE directive syntax
5-116
i-9
---
5-138
AFTER JOURNAL
After journal save and/or restore -file pathname 4-9
management domain 4-1
print After Journal Domain
system-level statistics 4-28
print After Journal process-level
statistics 4-31
5-19
ACCEPT
ACCEPT console verb
5-81
- -
4-47
DH18-03
----------------------------------------
ALLOCATION (cont)
allocation table problems 2-25
allocation tables 5-53, 5-101
circular 5-144
controlling disk space allooation
5-28
default virtual memory for
Integrated Software 4-38
influencing the order of magnetic
tape allooation 5-57
influencing the order of mass
storage allocation 5-52
Integrated Software memory
allocation abort error message
4-38
magnetic tape allocation class 5-58
Mass Storage Allocation program
5-53
memory allocation 2-22
memory allocation delays in Time
Sharing 5-173
memory allocation for DRL TASK job
5-169
memory allooator 1-5
preferenoe list for mass storage
device allooation 5-148
reallocation of temporary file
5-29, 5-30
SDLD oonfiguration 4-52
SDLD input file allooation 4-52
SDLD output file allooation 4-52
site-option patoh .J and J. initial
size 5-158
Time Sharing memory allocation
algorithm 5-174
ANSWER (oont)
answering Startup and dump questions
in the Startup job stream 5-5
appended • by console operator
2-17, 2-18
override $ ANSWER 2-5
override $ ANSWER via YES response
to .CHANGE? 2-20
questions for whioh $ ANSWER should
not be used 5-7
ALLOCATION UNIT
$ INIT 5-100
$ Iyy' 5-53
default value 5-53
devioe allooation unit table
5-28
ASSIGN
ASSIGN -PRIVATE BUFFER POOL FILE
directive 4-36
ASSIGN SITE PARAMETER direotive
syntax 4=-48
assign TY5 to CSU6001, CSU6601, or
CSU6602 for VIDEO 5-49
assigning olass B priority 5-143
assigning GCOS system files to mass
storage 5-109
dynamio processor assignment 5-22
pathname of file assigned to buffer
pool 4-36
processor assignment at Startup
3-24
ALTER
alter oorreotions
5-191
ALTERNATE TRACK TABLE
MSU0500 2-38
MSU0501 2-38
ANSWER
$ ANSWER
2-41,
APPLICATION
Transaotion Processing Applications
Programs 5-130
APRIOR
console verb
5-140, 5-142
AREA
catalog area threshold
5-23
ASCII
ASCII 5-88
ASCII $ INFO option 5-20
disable ASCII space compression
5-32
printer belt 5-18, 5-20
ASGN
ASGN 2-29
console verb 2-36, 2-37, 5-55
printer 5-37
AS GNP
console verb
3-24, 5-22
1-3, 2-4, 2-6, 2-17
i-10
DH18-03
(
ASSIGN SITE PARAMETER
ASSIGN SITE PARAMETER directive
syntax 4-=48
AVNOCR
site-option patch
AST
AU size 5-100
building available space table 5-28
establishing Available Space Table
2-28
master available space table 5-145
rebuilding 5-30
5-186
BACKDOOR
Backdoor Information 5-21
DP.DBI - Backdoor Information 2-22
SDLD Backdoor Load Map report 4-56
size of back door information segment
5-41
BANNER
dump
3-20
AU
$ Iyy 5-53
AU size 5-100
default value 5-53
device allocation unit table
AUDIT
audit trail of initialization
BATCH
print Integrated Software statistics
for batch processes 4-32
5-28
2-27
AUTOLOAD
AUTOLOAD device 2-7, 5-9, 5-96,
5-97, 5-102, 5-104
AUTOLOAD file 1-2, 1-4, 2-2, 2-4,
2-5, 2-7, 2-8, 2-14, 2-18, 2-27,
3-8, 5-9, 5-13, 5-102, 5-109, B-4
AUTOLOAD file destroyed 3-8
AUTOLOAD file modification B-15
AUTOLOAD file not on default device
2-8
AUTOLOAD file size 5-9, B-15
change of the AUTOLOAD device 5-94
defective space on AUTOLOAD device
5-95
file not accessible for power-up
bootload 2-3
file update 2-3
initialize the AUTOLOAD device 5-94
modifying content of AUTOLOAD file
2-11
overlaying 3-8
reboot via AUTOLOAD file 3-8
Startup job stream written to
AUTOLOAD file 5-9
AVAILABLE SPACE TABLE
building 5-28
establishing 2-28
master available space table
AVDIO
site-option patch
5-145
BCD
BCD 5-88
disable BCD space compression
invalid BCD card 3-3
printer belt 5-18
5-32
BEFORE JOURNAL
control interval size 4-10
define before journal device 4-11
define duplicate before journal
device 4-12
management domain 4-1
number of before journal control
intervals for commitment unit
4-10
number of before journal control
intervals written between header
records 4-11
print Before Journal process-level
statistics 4-31
request duplication of before
journals and PAT images 4-11
BELT
logical representation of characters
on belt 5-16
BINARY
invalid binary card
3-3
BLINK
DP.SBT - SYSOUT Blink Table 2-22
GEOT blink release threshold 5-41
SYSOUT Blink Table 5-21
5-186
i-11
DH18-03
BMC
BMC spinoff
5-144
BOOT
$ ANSWER 5-8
$ ANSWER example
5-9
BOOTLOAD
$ INFO ROLLCALL interrupts fast boot
5-37
abort of fast boot 2-6
acceleration via $ ANSWER 2-4
BOOT console verb 2-45, 3-7, 3-8,
3-9, 5-1, B-18
BOOTLOAD push button 3-2
Bootload Startup Program 1-1
Bootloader program errors 3-1
bypass bootloading of MPC 2-29
clears system tables 2-3
cold boot 2-2, 2-4, 2-24, 2-34,
5-100, 5-104, 5-191
date and time 1-2
definition 2-1
direct boot load from mass storage
1-2
DPS 88 and DPS 90 2-1
expedite warm and fast boots via $
ANSWER 5-5
Extract Card Images from AUTOLOAD
File (XCAF) 2-12
fast boot 1-2, 2-5, 2-32, 2-35,
5-23
fast boot with FASTBT file 2-2
fast boot without FASTBT file 2-2
FASTBT option 2-6
from mass storage 2-7, 3-8
halt the boot load 2-19
identifying system 5-84
inhibit fast boot 2-6
initiate a warm boot 2-19
initiating bootload from magnetic
tape 2-10
10M BOOTLOAD SOURCE TAPE/CARD switch
2-9
magnetic tape controller B-5
mass storage controller B-5
modifying content of site-specific
boot tape 2-12
MPC 5-76
MPC Bootload (MPCB) 2-4, 2-6, 2-29,
5-12, 5-102, 5-133
MPC firmware 2-43, B-5
BOOTLOAD (cont)
MPC verification and bootloading
2-25
operator control 1-3
power-up bootload 2-2
PSI B-9
Read Startup Boot Tape (RSBT) 2-12
replacing section of Startup job
stream 2-10
restart via fast boot 5-19
site-customized boot tape 2-1
site-specific boot tape 2-1, 2-4
techniques 2-1
unsuccessful 2-11
warm boot 2-2, 2-4, 2-31, 2-34,
2-35
warm boot from mass storage 2-7
warm boot with GCOS functioning in
main memory 2-5
without card reader 2-1
Write Startup Boot Tape (WSBT) 2-12
BOUNDARY
file boundary
3-6
BUFFER
buffer pool control interval size
4-36
buffer size for Integrated Software
trace 4-24
define buffer pool for Integrated
Software 4-4
Dump only Startup buffer areas 3-11
number of buffers allocated to each
protected file at file-open time
4-21
site-option patch for number of
processor error record buffers
5-153
Startup file system buffers 3-21
BUFFER MANAGEMENT
domain 4-1
parameter and descriptor consistency
checks 4-21
print Buffer Management Domain
process-level statistics 4-30
print Buffer Management Domain
system-level statistics 4-27
BUFFER POOL
ASSIGN -PRIVATE BUFFER POOL FILE
directive 4-36
DH18-03
BUFFER POOL (cont)
create 4-35
create buffer pools for protected
files 4-35
maximum number of buffers in default
buffer pools 4-20
pathname of file assigned to buffer
pool 4-36
CACHE
site-option patches for cache memory
control 5-155
CARD
invalid binary card 3-3
out of sequence 3-3
CARD PUNCH
$ Iyy for card punch 5-70
CCU0401 reader/punch 5-32
configuring 5-70
dedicated 5-71
No card punch configured 5-32
releasing configured card punch at
Startup 5-71
unit identification number 5-71
CARD READER
$ Iyy for card reader 5-70
CCU0401 reader/punch 5-32
configuring 5-70
dedicated 5-71
not ready 3-4
releasing configured card reader at
Startup 5-71
unit identification number 5-71
CAT
$ INIT CAT parameter
2-34, 5-20,
5-101
CATALOG
catalog area threshold 5-23
catalog into PRINTIMAGE file 5-88
class catalog 5-39
disable FMS creation of catalogs
2-34
dump System Master Catalog (SMC)
3-23
duplicate 5-20, 5-101
duplicate System Master Catalogs
5-20, '5-40, B-2
enable catalog creation 2-34, 5-101
CATALOG (cont)
FMS catalog and permanent file
structure 5-54
FMS catalogs B-10
inconsistency between logical device
label and SMC 2-31
SMC password encryption 5-22
specifying the maximum number of
cataloged processes 5~34
system master catalog 2-25, 5-109
system path name replacement 5-40
unaSSignable space 2-25
CATDUP
$ INFO option
5-20, 5-101
CATFNC
$ INFO option
5-20
CCACHE
$ INFO option
5-21
CCU0401
$ Iyy format
reader/punch
5-71
5-32
CENTRAL INTERFACE UNIT
defining physical attributes
5-12
CHANGE
END CHANGES directive syntax 4-48
START CHANGES directive syntax 4-50
CHANNEL
$ XBAR 5-91
assigning peripheral devices to
channels 5-46
crossbarring 5-91
CSU6601 console channel adapter
5-49
equivalent to PUB 5-3
multiple logical channels 5-92
primary channel 5-92
PSI logical channel 5-76
switching peripheral device channels
during Startup 5-11
use of CH for channel 5-47
use of PUB for channel 5-47
CHARACTER SET
ASCII 5-88
BCD 5-88
GCOS character set
i-13
5-88
DH18-03
CHARACTER SET (cont)
high-speed printer character set
B-4
identification number 5-88
invalid character 3-4
loading 1-3, 2-26, 2-36, 5-93
modify/add printer character set
B-19
name 5-88
printer character set B-4
CHECKPOINT
checkpoint file for process
snapshots 4-13
checkpoint journal device 4-16
checkpoint journal dump frequency
4-15
Checkpoint Journal Manager domain
4-1
checkpoint journal size 4-14
duplicate checkpoint journal device
4-16
duplicate checkpoint journal file
4-16
extent of checkpoint collection
4-13
number of activitie.s using
checkpoint journal 4-14
removable checkpoint journal device
4-16
restart from checkpoints 5-144
CHECKSUM
checksum error
3-3
CHEX
CHEX correction statement
5-133
CHKSUM
$ INFO option
5-104,
CLASS A PRIORITY
enabled 5-140
site-option patch
CI
5-141
CLEANPOINT
$ INFO CLENPT 2-3
cleanpoints 2-22, 5-150
CLEAR
$ DIRECT 2-42
$ DIRECT parameter
$ DIRECT statement
CLENPT
$ INFO option
5-96
2-39
2-3, 5-21
CODE
magnetic tape density code 5-57
printer belt code 5-62
report code for Integrated Software
statistics 4-26
SDLD abort codes 4-58
system high-density code 5-144
system low-density code 5-144
2-2, 2-4
COMMENT
comments in Startup job stream
4-10
CIU
defining physical attributes
5-130
CLASS B PRIORITY
assigning 5-143
class B priority dispatches 5-171
enabled 5-140
multicopy Time Sharing class B
priority 5-181
site-option patch 5-142
TDS class B priority 5-142
TPS class B priority 5-142
TSS class B priority 5-142
COLD BOOT
cold boot
5-21
see Control Interval
CLASS (cont)
required site-defined class
5-12
CLASS
job class 5-39, 5-129
job class sizes 5-112
optional .user classes 5-113
optional site-defined class 5-130
5-2
COMMITMENT
historical log entry for each
commitment taken 4-19
number of before journal control
intervals for commitment unit
4-10
i-14
DH18-03
COMMON EXCHANGE INTERFACE
$ Iyy statement for CXI mode 5-64
DSA Common Exchange Interface (CXI)
5-62
COMMUNICATION REGION
initialize 1-2
COMMUNICATIONS
configuration
B-3
COMPONENT
adding mainframe components 5-10
configuring system component B-17
deconfiguring system component B-18
reconfiguration 5-91
redundancy 5-91
CONCURRENCY CONTROL
domain 4-1
maximum concurrency control
reservations retained for one
process 4-20
print Concurrency Control Domain
system-level statistics 4-28
CONFIGURATION
-RETAIN CONFIGURATION? 2-20
assumed channel for console 3-1
card punch 5-70
card reader 5-70
configuration file 5-10
configuration restrictions MSU3380
MSU3381 MSS8080 5-51
configuring system component B-17
configuring System Control Center
(SCC) 5-47
CPU and lOX or IMX contiguous
configuration 5-12
crossbar configuration B-4
DATANET network processor 5-62,
5-64
DPS 90 configuration considerations
5-74
magnetic tape - initial
configuration B-11
mass storage - initial configuration
B-9
mass storage hardware configuration
change 5-46
maximum site mainframe configuration
5-10
MPC B-3
CONFIGURATION (cont)
multicopy time sharing restart 5-19
multiple consoles 5-47
options 5-4
Page Processing System 5-67
panel switch settings 5-10
peripheral and communications B-3
reconfiguration 5-91
remote Page Processing System (PPS)
5-67
SDLD configuration 4-52
software and hardware B-1
ST1 must be defined 5-53
tables 5-3
unit record devices - initial
configuration B-12
CONSOLE
$ Iyy statement for remote
maintenance console 5-49
assigning TY5 to csU6001, CSU6601,
or CSU6602 for VIDEO 5-49
assumed channel 3-1
configuring multiple consoles 5-47
console emulator 3-2
CSD customer support via remote
maintenance console 5-49
CSU6001 5-48
CSU6002 5-48
CSU6601 5-48, 5-49
CSU6602 5-48
CSU6604 5-48
csu6605 5-48
ident image for console spawned jobs
5-149
remote maintenance console 5-49
required system console names 5-47
resetting the console 3-12
tab settings 1-2
TY1-TY4 5-47
USE RID image for console spawned
jobs 5-150
USE RID image of select file for
spawned jobs 5-150
CONSOLE EDITOR
modifying content of AUTOLOAD file
2-12
Startup Console Editor 2-14
CONSOLE MANAGER
running VIDEO with Console Manager
5-49
1-15
DH18-03
CONSOLE MESSAGE
*ABORTBOOT FROM ,TAPE 2-11
*ANSWER YES TO CONTINUE WITHOUT
ABOVE PATCHES 5-137
*BOOT SOURCE: AUTO OR REPL? 2-20,
3-6, 3-8, 3-9, 5-8, 5-72, 5-191
*BOOT SOURCE: TAPE, AUTO, OR REPL?
1-2
*BOOTLOAD DEVICE ERROR 2-18, 3-4
.CARD BELOW IS OUT OF ORDER 5-63
*CARD CHAR ILLEGAL 3-4
*CHANGE > 5 MIN, YES To ACCEPT?
2-24
*CHANGE DATE 2-23
*CHANGE TIME 2-23
*CHANGE? 2-5, 2-20, 5-5
.DATE mmddyy TIME hh.mmm? 2-23
*DATE? 2-24
*ddd CAN'T CHANGE DEVICE STATUS •••
2-34
*ddd CAN'T CHANGE SMCDUP WITHOUT
INIT 2-31, 2-34
*ddd EXPECTED PACK NUMBER xxxxx
FOUND yyyyy YES TO ACCEPT CHANGE
2-33
*ddd fffff CAN'T BE xxxxx 5-110
*ddd PRIOR DEVICE STATUS WAS RMVBL
CHANGED TO PERM 2-33
*ddd ST1/SMCDUP DEVICE WRONG PACK
MOUNTED 2-31
*DENSITY MISMATCH ON icccdd 2-35
*DEPRESS EOM WHEN READY TO CONTINUE
2-13
*DEVICE ddd UNDEFINED 2-32, 5-47
*DISK PACK ERROR icccdd (status)
TRACK ZERO BAD 2-41
*DISK PACK ERROR icccdd ••• B-18
*DISK PACK ERROR icccdd PSEUDO ALT
AREA ALL DEFECTIVE 2-41
*DISK PACK ERROR icccdd S ••• 5 EOM TO
CONTINUE -- 'RLSE' TO RELEASE THE
DEVICE 2-32
*DISK PACK ERROR, icccdd:ACCESS
BEYOND FILE fffff CANNOT PROCEED
3-6
*DISK PACK ERROR, icccdd: S •• ~5
CANNOT PROCEED 3-7
*DISK PACK ERROR, icccdd: 5 ••• 5 EOM
WHEN READY 3-5
*DISK PACK ERROR, icccdd: S ••• 5 FIX,
TYPE GO OR STOP OR RLSE 3-5
*DUPLICATED PATCH CARD BELOW IGNORED
5-136
CONSOLE MESSAGE (cont)
*EDIT? 1-4, 2-27, 2-32, 2-44, 2-46,
3-22, 5-2, 5-6, 5-17, 5-40, 5-107,
B-14, B~16, B-17, B-20
*END OF TAPE ENTER FILE NAME 2-46
*ENTER TIME OR ENTER A CORRECTION
FACTOR? 2-23
*EXPECT 5 ••• 5 ccccc FIX TYPE GO
2-19, 3-9
*EXPECTED PACK NAME xxx FOUND yyy
YES TO ACCEPT CHANGE 2-31, 2-33
*EXPECTED PACK NUMBER xxx FOUND yyy
YES TO ACCEPT CHANGE 2-31
*FATAL I/O ERROR ONicccdd: s ••. s
3-7
-FILE fffff UNDEFINED 5-115
*FILE IS aaaaaa, SHOULD BE bbbbbb
SCFR? 2-46
-FORMAT/LABEL QUESTIONS? 2-27,
2-38, 2-39
*FYI ECOL - COULD NOT OBTAIN AT
LEAST 800 LLINKS PERM FILE SPACE
5-156
*FYI ECOL - FILE SIZE REQUEST >
262143, WILL ATTEMPT TO GET 1200
LLINKS 5-156
*FYI ECOL - FILESIZE REQUEST WAS
nnnn LLINKS, WILL ATTEMPT TO USE
1200 LLINKS 5-156
*FYI ECOL - PERM FILE SPACE NEEDED
WAS nnnnnn LLINKS, SPACE OBTAINED
WAS.. • 5-156
*FYI ECOL - REQUESTED COLLECTOR FILE
SIZE OF nnnnnn LLINKS IS VERY
LARGE 5-156
*ILLEGAL xxxxxx CARD BELOW IGNORED
3-22
*INIT DEVICE 2-27, 2-38
*INIT RMVBL DEVICE 2-27, 5-7
.INIT SHARED DEVICE 2-27
*INITIALIZE? 1-3, 2~18, 2-24, 2-25,
2-26, 2-29, 2-30, 2-32, 2-42,
2-43, 3-22, 5-2, 5-6, 5-13, 5-40,
5-93, 5-99, 5-104, 5-107, B-15,
B-19
*Iyy-n RELEASED 2-14
*MOUNTED TRAIN ID xxx REQUESTED
TRAIN ID yyy 2-37, 3-6
*MPC ON icc PRE-INITIALIZE? 2-30
*NEED PRINTER PORT,
Iyy,CHAN,MPC/CPI,TRAIN 3-11
.NEED READER PORT, Iyy, CHANNEL
PICCC 2-11, 2-19
i-16
DH18-03
CONSOLE MESSAGE (cont)
.NO HEX CAPABILITY ON CPU-n HEX
OPTION DISABLED 5-24
.OBJECT DECK CARD nnnnmmmm IS NOT
hhhh TYPE, DECK SKIPPED 5-192
.ONLY 20 CATALOGABLE/SMC/SMCDUP
DEVICES ALLOWED 5-101
.OVER-PATCH CARD BELOW IGNORED
5-136
.PATCH CARD BELOW CONTAINS ERROR
NEAR COLUMN nn 5-137
.PATCH CARD BELOW CONTAINS UNDEFINED
PROGRAM NAME 5-136
.PICK ONE DUMP: ALL,NONE,NORMAL
3-5, 3-6, 3-11, 3-20
.POSITION PAPER IN PRINTER 2-37,
3-6
·PRINTER ERROR 2-36, 3-6
.PRINTER ERROR icccdd s ••• s DEVICE
RELEASED 2-36
-PROCESS $ READIN 2-43
.PROCESS SSFILE CARD AND SYSTEM
SCHEDULER CLEAR? 2-46, B-20
.PROCESSOR n RELEASED 3-24
.PROCESSOR ON PORT P DOESN'T ANSWER
CONNECT 3-24, 5-6
.REPLACE? 2-10, 2-18, 2-19, 5-191
-RESTART? 2-21, 2-46, 2-47, 5-6,
5-46, B-17, B-18
-RETAIN CONFIGURATION? 2-20, 5-6
-SCF CONTINUATION? 2-22, 5-6, 5-146
.STARTUP ABORTED LOC mmmmmm 3-5,
3-6, 3-11
.SYSOUT RECOVERY? 2-21, 5-6
.SYSTEM CONTROLLER CLOCK AND .CRDAT
MISMATCH 2-23
*SYSTEM SCHEDULER CLEAR FORCED 2-47
.SYSTEM SCHEDULER CLEAR? 2-6, 2-21,
2-47, 5-6, 5-46, B-17, B-18
-TAPE ERROR icccdd: ATT I ssssss
OPERATE WHEN READY 2-45
-TAPE ERROR, icccdd s ••• s MAY BE
RECOVERABLE 2-35, 3-5
.TAPE ERROR, icccdd: s ••• s CANNOT
PROCEED 3-7
-TIME? 2-24, 5-6
-TRAIN ID UNKNOWN TO STARTUP DEVICE
RELEASED 2-36, 3-6
.UNIT NUMBER MISMATCH 2-35
-xxxMPC ON icc APPEARS OK, BOOTLOAD?
2-30,.2-44
.xxxMPC ON icc BOOTLOAD SYS ID
NAME ••• 2-30, 2-44
CONSOLE MESSAGE (cont)
.xxxMPC ON icc NOT RESPONDING
PROPERLY 2-29
4JS3 FILE filename MIGRATED 5-27
ADDITIONAL OPTIONS:
ALL,HCM,SOFT,SLV,W/XX, ••• 5-8
BLOCK 0 DEFECTIVE MUST REFORMAT
DEVICE 2-42
BOOTLOAD DEVICE ERROR 2-19
CAN'T BE CAT AND NOFMS 5-101
CAN'T DEFINE FMS 5-54
CANNOT BUILD IN-CORE TABLE ON ddd
DUE TO TBLSIZ s .•• s 5-100
CARD CHECKSUM ERROR 3-3
CARD SEQUENCE ERROR 3-3
CHANGING TO yyy YES TO INITIALIZE
PACK 2-37
CHG PACK Innnnn? 2-39, 2-40
CLEAR AND OVERWRITE EXISTING
DECKFILE? 2-43, 5-7, 5-13, 5-104,
B-15
CRD CHECKSUM -FIX,EOM 3-3
CRD SEQUENCE -FIX,EOM 3-3
DUMP nnn FROM ddd TO TAPE 5-31
DUPED MASKS -FIX,EOM 3-4
ENTER PACK INNNNN? 2-39
ERROR DETERMINING ALTERNATE TRACK
MUST REFORMAT DEVICE 2-42
EXPECTED PACK NUMBER xxxxx FOUND
yyyyy YES TO ACCEPT CHANGE 2-38
FATAL ERROR IN $FILES SECTION CARD
BELOW CONTAINS AN ERROR NEAR
COLUMN xx 5-126
FMT PACK Innnnn? 2-39, 2-40
FORMAT/LABEL QUESTIONS? 2-42, 5-7
GCOS-8 REQUIRES AT LEA.ST 1024K OF
MEMORY 5-73
GET 5-144
HEX MODE ENABLED 5-24
ILLEGAL BCD CARD 3-3
ILLEGAL BIN. -FIX,EOM 3-3
ILLEGAL HOL. -FIX,EOM 3-3
ILLEGAL OCT. -FIX,EOM 3-4
INIT DEVICE ddd? 2-41, 5-7
INIT SHARED DEVICE ddd? 5-7
Iyy-n NOT RESPONDING 2-13, 5-7
LLINK
BAD, MUST
TEST/FORMAT/RTHDRS ••• 2-39
LLINK
CLEARED, MUST
TEST/FORMAT/RTHDRS ••• 2-39
LLINK ZERO BAD, MUST INIT 2-41
MEMORY SURVEY: nnn PAGES FOUND
DEFECTIVE 2-14
i-17
°
°
DH18-03
CONSOLE MESSAGE (oont)
MISSING/EXTRA CARDS 3-3
MPC ON ioc PRE-INITIALIZE? 5-7
MPC ON iccc APPEARS OK, BOOTLOAD?
5-7
MPC ON iccc BOOTLOAD SYS ID NAME
5-7
MPC-n CHECK SWITCHES: 2-13
NO HANDLERS CAPABLE OF DEFAULT
HIGH/LOW DENSITY 5-22
PRIOR DEVICE STATUS WAS RMVBL
CHANGED TO PERM ••• B-19
PROCESS DIRECTORY CARD FOR DEVICE
ddd? 2-39, 5-7, 5-97
PROCESS DIRECTORY CARD FOR SHARED
DEVICE ddd? 5-7
RUN TIME EXHAUSTED 5-26
SCU IN MANUAL MODE 2-17
SELECT DEVICE: (PRINT), (DISK)",
PRINTER NAME (PR1),
(DDD/TAPEI,DENSITY), (NONE) 5-8
SHARED MPC ON icc PRE-INITIALIZE?
5-7
SHARED MPC on iccc APPEARS OK,
BOOTLOAD? 5-7
site-option patch to suppress GEIN
SPAWN message 5-164
ST1 AND SMCDUP INITED BUT NOT ALL
OTHERS, FILE SPACE WILL BE LOST
2-25
STARTUP ABORTED LOC mmmmmm •• PICK
ONE DUMP ••• 2-45
STATS/RESIDU = x ••• x -FIX,EOM 3-3
STATS/RESIDU = x ••• x ABORT BOOT FROM
TAPE 3-2
SYSOUT LINES EXHAUSTED 5-26
TEST PACK Innnnn? 2-39, 2-40
TOO MANY PATCHES USE $ INFO PTCHSZ/N
5-35
TRAIN ID UNKNOWN TO STARTUP DEVICE
icccdd RELEASED 5-88
CONSOLE VERB
ABORT SHARD 4-37
ACCEPT 5-116
APRIOR 5-142
ASGN 5-55
ASGNP 5-22
BOOT 3-7, 3-9, 5-1, B-18
DEDCAT 5-46
DUMP 3-7, B-18
ENABLE 5-50
EXCHG 5-56
CONSOLE VERB (cont)
FASTBT ON/OFF 2-6
IGNORE 5-116
MOVE 5-50
NAME 5-47
PSTATS 5-55
RELINQUISH 5-50
RLSE 5-46, 5-55, B-18
RLSEP 3-20
RUN REST 2-21
SPAWN SHARD 4-3
UNAME 5-47
UNDED 5-46
CONTIGUOUS
contiguous defective sectors 5-98
contiguous defective space 5-98
CONTINUATION
$ ETC 5-3
CONTROL
control store
5-104, 5-133
CONTROL INTERVAL
Before Journal control interval size
4-10
buffer pool control interval size
4-36
compressed journalization 4-22
full control interval journalization
4-22
number of before journal control
intervals for commitment unit
4-10
number of control intervals for
historical log 4-17
number of modifications before
control interval written 4-22
site parameter for journal directory
control interval size 4-8
size of control interval for
historical log 4-18
CONTROLLER
$ Iyy input/output controller
statements 5-46
controller adapter 5-80
magnetic tape handler survey 2-35
mass storage 5-95
i-18
DH18-03
CORRECTION STATEMENT
common OCTAL correction statement
errors 5-136
duplicate MASK 3-4
erroneous MASK 3-3
illegal MASK 3-4
MASK 1-2, 3-9
MASK for console channel 3-1
OCTAL correction statements 5-104,
5-133, 5-134, 5-140, 5-191, B-8
PATCH RUN UNIT statement 5-133
RHEX -2-8CPL
peripheral device type
CPZ201
$ Iyy format
CPZ300
$ Iyy format
5-71
5-71
CRU0501
$ Iyy format
5-71
CRU1050
$ Iyy format
5-71
CS6001
console
5-48
CS6002
oonsole
5-48
CS66/RMC
console
CS6602
oonsole
5-27
CSU6001
assigning TY5 for VIDEO
console 5-48
CSU6002
console
5-49
5-48
csu6601
assigning TY5 for VIDEO 5-49·
console 5-48
CSU6601 console channel adapter
5-49
csu6602
assigning TY5 for VIDEO
console 5-48
CSU6604
console
5-48
CSU6605
console
5-48
5-49
CXI
default eXI communications values
5-64, 5-66
device type 5-64
DSA Common Exchange Interface (CXI)
5-62
Network Processor CXI mode mailbox
address switches 5-65
Network Processor numbering 5-64
CXI MODE
$ Iyy statement
5-64
5-48
CYCLIC JOBS
System Scheduler
2-47
5-48
D, 0, A, L, Y
CS6604
console
5-48
CS6605
console
5-48
CSD
CSD 3-6, 3-20, 5-13, 5-24, 5-80,
5-104
customer support via remote
maintenance console 5-49
Honeywell Bull Customer Service
Division 2-43
defective space 5-96, 5-98, B-5
secondary initialization 2-28, 2-41
DATA
firmware data decks
5-12
DATA BASE
Data Base Procedure domain 4-1
shared 5-76
Shared Data Base Control System
domain 4-1
workstation definition data base
pathname 4-34
i-19
DH18-03
DEDICATED
$ Iyy 5-53
card reader or card punch
dynamic device dedication
magnetic tape 5-59
DATA MANAGEMENT CONTROL SYSTEM
domain 4-1
DATABASE COMPUTER
$ Iyy format 5-69
DATANET
$ Iyy statement for CXI mode 5-64
$ Iyy statement for DNET/ROUT mode
5-62
DATANET 6616 example 5-63
DATANET Network Processor number
5-63
maximum number of lines 5-63
PPS 5-67
DATE
date and time of bootload
DDIA
$ Iyy DDIA
1-2
5-65
DEBUG
$ TRACE 5-85
debug site-option patch 5-164
Peripheral Allocator program debug
mode 5-144
DECKFILE
cannot be rebuilt 3-9
clearing 2-43
create empty deckfile for IFAD 2-43
deckfile 5-13, 5-96, 5-102, B-5
editing new firmware 2-43
firmware 5-93
firmware revision level 5-79
inhibit printing of deckfile map
5-28
modification B-15
overwrite existing deckfile 2-43,
5-13
re-edit 2-37, B-15
specifying firmware data deckfile
name 5-12
DECONFIGURATION
deconfiguration 2-12
deconfiguring system component
permanent device 5-46
DEDCAT
console verb
5-46
B-18
5-71
5-46
DEFAULT
END DEFAULTS directive syntax 4-48
START DEFAULTS directive syntax
4-50
DEFECTIVE
contiguous defective sectors 5-98
contiguous defective space 5-98
DEFECTIVE LLINK DIRECTORY
$ DIRECT ddd/CLEAR 2-42
building 2-42
clear 5-96
defective llink directory
5-99
update 2-40
5-96,
DEFECTIVE LLINK DIRECTORY PRINT
PROGRAM (DLDP)
Defective Llink Directory Print
program 5-98
DEFECTIVE SPACE
clearing 2-37
defective space B-5
defective space information 5-96
definition of defective space on
AUTOLOAD device 5-95
DEFECTIVE SPACE HISTORY TABLE
$ DIRECT ddd/CLEAR 2-42
defective space history table
2-40, 5-96, 5-99
2-38,
DEFERRED PROCESSING PARAMETERS
maximum scheduled and active DRUNs
5-174
preferred time-of-day 5-175
processor time limit 5-175
site-option patches 5-174
DEFERRED QUEUE
Time Sharing deferred queue file
5-178, 5-179
USE RID for permanent deferred queue
file 5-170
i-20
DH18-03
DEFERRED SESSION
deferred session elapsed time rate
5-187
deferred session rate 5-187
max number active 5-174
max number scheduled 5-174
DEFINITION
$ ACCBUF 5-116
$ ACCOUNT 5-117
$ ANSWER 5-5
$ AUTOLD 5-9
$ BASE 5-10
$ CHAN 5-11
$ CIU 5-12
$ DECKFIL 5-12
$ DEKSAV 5-96
$ DFILES 5-118
$ DIRECT 5-96
$ DTFILE 5-108
$ DUP 5-14
$ ENDTF 5-108
$ ETC 5-3
$ FILCREA 5-14
$ FILDEF 5-109
$ GCOSFIL 5-15
$ GHCM 5-192
$ GROUP 5-15
$ IMAGE 5-16
$ INFO 5-19
$ INIT 5-99
$ Iyy for both DNET/ROUT mode and
CXI mode 5-65
$ Iyy for card punch 5-70
$ Iyy for card reader 5-7D
$ Iyy for database computer 5-69
$ Iyy for DNET/ROUT mode 5-62
$ Iyy for Front-End Processors 5-62
$ Iyy for HYPERchannel 5-68
$ Iyy for magnetic tape subsystems
5-56
$ Iyy for mass storage subsystems
5-51
$ Iyy for Page Processing System
5-67
$ Iyy for printers 5-61
$ Iyy for remote maintenance console
5-49
$ Iyy for system control devices
5-47
$ Iyy for VIDEO device 5-49
$ LIBRARY 5-119
$ LOADFIL 5-72
DEFINITION (cont)
$ MCT 5-72
$ MODOPT 5-121
$ MPC 5-76
$ MPCFIG 5-79
$ PFILES 5-125
$ READIN 5-104
$ SAVE 5-126
$ SCFBUF 5-127
$ SCFDSP 5-128
$ SECURE 5-80
$ SHARED 5-83
$ SHCM 5-191
$ SSFILE 5-112
$ SSLOAD 5-129
$ SYID 5-84
$ SYSOUT 5-131
$ SYSTEM 5-131
$ TRACE 5-85
$ TRAINS 5-88
$ UNIT 5-89
$ UHP 5-90
$ VOPT 5-105
$ VSET 5-106
$ XBAR 5-91
mass storage device for $LOAD
section 5-72
shared devices 5-83
standard printer belts 5-88
system bootload 2-1
System Scheduler classes 5-129
unit record devices B-12
Unit Record Processor URP8DOn 5-90
workstation definition data base
pathname 4-34
DELPR
site-option patch 5-187
DENSITY
$ INFO DENxx/DENyy option 5-22
1600 bpi 5-57, 5-58
6250 bpi 5-57, 5-58
800 bpi 5-57, 5-58
firmware tape 5-105
magnetic tape density code 5-57
specifying magnetic tape density
capabilities 5-42
system default high density 5-117
system high-density code 5-144
system low-density code 5-144
tape density 5-58
verify tape density 2-35
i-21
DH18-03
DENxx
$ INFO option
DEVICE (cant)
magnetic tape logical device name
5-22
5-57
mass storage device initialization
DESCRIPTION
Startup error messages 3-3, 3-5
Startup printer error messages 3-6
DESCRIPTOR
space descriptor threshold
5-100, B-5
mass storage device label 5-53
mass storage device verification
5-93
5-23
mass storage logical device name
5-53
mass storage subsystem/device
initialization 5-93
Microcoded Device Routines 5-80
multiple logical device names 5-47
NPL peripheral device type 5-27
NRZI devices 5-22
PE devices 5-22
peripheral device options 5-4
permanent mass storage device
verification 2-26, 2-31
permanent mass storage devices 2-25
preference list for mass storage
device allocation 5-148
printer logical device name 5-62,
prior device status 2-33
reassign released devices 2-30
redefining mass storage device B-19
release 2-32, 2-36, 3-5, 5-46
release offline ma~s storage devices
DEVICE
$ Iyy for system control devices
5-47
$ Iyy for VIDEO device 5-'49
$LOAD mass storage device B-4
AUTOLOAD device 2-7, 5-9, 5-96"
5-97, 5-102, 5-104
can't change device status 2-34
change from removable to permanent
2-34
checkpoint journal device 4-16
CPL peripheral device type 5-27
deconfiguring a permanent device
5-46
dedicated device 5-46, 5-53
defective space on AUTOLOAD device
5-95
define before journal device 4-11
define duplicate before journal
device 4-12
defining mass storage device for
$LOAD section 5-72
defining peripheral devices, 5-46
defining shared devices 5-83
device allocation unit table 2-41,
5-37
removable checkpoint journal device
4-16
removable device 5-53
required logical device names 5-47
rollcall 1-3, 2-29, 2-30, 5-3
shared controller/device I/O
statistics collection 5-157
shared with NPS 2-34
SMCDUP device and option
verification 2-31
ST1 and SMCDUP device name
verification 2-31
status of peripheral devices 5-3
survey of unit record devices 1-3
switching peripheral device channels
during Startup 5-11
unit record devices - initial
configuration B-12
verification of all permanent mass
storage devices 1-3, 2-32
5-28
device control tables 5-3
device directory 2-32, 2-33, 2-34
device is off line 2-32
device name table 2-26,2-31,2-33
device type 5-52, 5-53
device type for CXI mode 5-64
device type for DNET/ROUT mode 5-64
duplicate checkpOint journal device
4-16
duplicate historical log device
4-19
GCR devices 5-22
historical log device 4-18
initialization 1-3, 2-25, 2-34
label 2-26
logical device name 5-46, B-9,
B-11, B-12
DIA
Direct Interface Adapter
i-22
5-64
DH18-03
DIAGNOSTIC PROCESSOR UNIT
DPU 5-49
use 3-20
DIRECT INTERFACE ADAPTER
DIA 5-64
DIRECTIVE
ALLOCATE directive syntax 4-47
ASSIGN -PRIVATE BUFFER POOL FILE
4-36
ASSIGN SITE PARAMETER directive
syntax 4=48
CREATE BUFFER POOL 4-35
define-buffer-pool for Integrated
Software 4-4
description of SDLD directives 4-46
description of SDLD output 4-54
END CHANGES directive syntax 4-48
END-DEFAULTS directive syntax 4-48
EXCLUDE DOMAIN directive syntax
4-49
INCLUDE DOMAIN directive syntax
4-49
OCTAL directive syntax 4-49
PATCH directive syntax 4-49
SDLD abort codes 4-58
SDLD Backdoor Load Map report 4-56
SDLD configuration 4-52
SDLD directive syntax 4-47
SDLD directives 4-7, 4-45
SDLD Directives List output 4-55
SDLD error and warning messages
4-57
SDLD fatal error messages 4-57
SDLD input file allocation 4-52
SDLD Load Map list output 4-55
SDLD Load Map Summary output 4-56
SDLD output file allocation 4-52
SDLD remarks description 4-50
START CHANGES directive syntax 4-50
START-DEFAULTS directive syntax
4-50
DIRECTORY
building defective llink directory
2-42
clear the defective llink directory
5-96
defective llink directory 2-40,
2-42, 5-96, 5-99
Defective Llink Directory Print
program 5-98
DIRECTORY (cont)
device directory 2-32, 2-33, 2-34
Module Directory Table 5-134
site parameter for journal directory
control interval size 4-8
DISCONNECT
line-hold interval
DISCPR
site-option patCh
5-175
5-185
DISK
activating Rapid Access Data System
(RADS) 5-28
average disk IIO time value 5-186
controlling disk space allocation
5-28
invalid sectors 2-41
release disk space 5-145
snap of disk IIO interval trace
table 2-41
DISK BOOTLOAD
procedure for disk bootload
2-9
DISK PACK
discrepencies during mass storage
device verification 2-37
formatting 2-37
initializing 2-24, 2-26, 2-38
label 2-37
logical device label 2-31
re-creation of labels 1-3
reformatting 2-24
selective initialization 2-27
structured 2-28
wrong disk pack mounted 2-38
DISPATCHER
algorithm variations 5-140
Dispatcher's queue 5-140
site-option patches 5-140
DLDP
Defective Llink Directory Print
program 5-98
DM-IV/TP
print Integrated Software statistics
for DM-IV/TP processes 4-33
i-23
DH18-03
DNET/ROUT
$ Iyy statement for Front-End
Processors 5-62
device type 5-64
Network Processor DNET/ROUT mode
mailbox address switches 5-65
Network Processor numbering for
DNET/ROUT mode 5-64
DOMAIN
After Journal Management 4-1
Automatic Workstation Enable 4-1
Before Journal Management 4-1
Buffer Management 4-1
Checkpoint Journal Manager domain
4-1
Concurrency Control 4-1
Data Base Procedure domain 4-1
Data Management Control System 4-1
description of SDLD directives 4-46
description of SDLD output 4-54
EXCLUDE DOMAIN directive syntax
4-49 Global Data Management 4-1
historical log domain 4-1
INCLUDE DOMAIN directive syntax
4-49 Integrated Software domains 4-1
Integrated Software domains on
SHARD.SPWN file 4-5
Integrated Software Output Report
4-1
Integrated Software Termination 4-1
Integrated Software Trace 4-1
Integrated Software Trace and Load
Map Display 4-1
Integrity Management 4-1
Protected File I/O 4-1
requirements for loading Integrated
Software domains 4-53
SDLD abort codes 4-58
SDLD Backdoor Load Map report 4-56
SDLD configuration 4-52
SDLD directive syntax 4-47
SDLD directives 4-45
SDLD Directives List output 4-55
SDLD error and warning messages
4-57
SDLD fatal error messages 4-57
SDLD input file allocation 4-52
SDLD Load Map list output 4-55
SDLD Load Map Summary output 4-56
SDLD output file allocation 4-52
DOMAIN (cont)
SDLD remarks description 4-50
Session Control domain 4-1
Shared Data Base Control System
domain 4-1
Shared Domain Loader 4-3
Shared Fault Handler domain 4-1
Tenant Management 4-1
TP8 Command Executive domain 4-1
Transaction Queuer Support domain
4-1
Workstation Management 4-1
DP.BDI
Backdoor Information
DP.BDI 5-21
DP.JOS
DP.JOS 5-21
Job Output Specials
DP.JOT
DP.JOT 5-21
Job Output Table
DP.RID
DP.RID
2-22
2-22
2-22
5-36
DP.SBT
DP.SBT 5-21
SYSOUT Blink Table
2-22
DPS 8
$ READIN 5-104
bootload 2-2
DPS 8; $ IOM, $ IMU 5-47
DPS 8; $ MCT 5-73
MPC bootloading 2-29, 2-43
PROCESS $ READIN 2-43
DPS 8000
$ READIN 5-104
bootload 2-2
DPS 8000; $ IMX
MPC bootloading
5-47
2-29, 2-43
DPS 88
bootload 2-2
create empty deckfile for IFAD 2-43
DPS 88; $ lOX 5-47
firmware 2-1
running VIDEO on DPS 88 system 5-49
i-24
DH18-03
DPS 90
bootload 2-2
create empty deckfile for lFAD 2-43
DPS 90 configuration considerations
5-74
DPS 90; $ lOP 5-47
DPS 90; $ MCT, EPU 5-73
DPS 90; $ MCT, lOP 5-73
firmware 2-1
DPSE
$ INFO option
5-22
DPU
diagnostic processor unit 3-20,
5-49
initiating dump from DPU 3-20
DRL T.CMOV
type of users permitted
5-169
DRL TASK
maximum number allowed 5-149
memory allocation for DRL TASK job
5-169
site-option patch for maximum
processor time 5-167
urgency 5-169
DSA
DSA Common Exchange Interface (CXI)
5-62
DUMP
$ ANSWER 5-8
$ ANSWER responses to dump questions
5-8
$ DUMP in Startup job stream
3-22
ADDITIONAL OPTIONS:
ALL,HCM,SOFT,SLV,W/XX, ••• 5-8
all of main memory 3-11
analysis by PERSUE 8 3-18
banner 3-20
cannot be taken 3-11
checkpoint journal dump frequency
4-15
console verb 3-7, 3-8, 3-10, B-18
contiguous llinks/links 3-22
creating boatable dump tape for NSA
program 3-13
Depy program 3-13
Depy p~ogram copies dump tapes to
disk file 3-18
DUMP (cant)
default options for save dumps 5-38
default options for user dumps 5-44
dump control file 5-126
dump of system software 2-5
dump options 2-45, 3-6
dumping file content 3-22
dumps from VIP maintenance terminal
3-12
following Startup abort 3-10
generating dump of main memory 3-21
initiating 3-10
initiating from DPU 3-20
last resort dump procedure 3-12
llinks/links 3-22
main memory 3-21
main memory and mass storage 3-10
Master Mode Dump 1-2, 2-3, 2-22,
3-10, 5-110
Native Stand-Alone dump programs
3-12
none before Startup is completely
loaded 3-1
NSA8 for DPS 88 3-12
NSAD for DPS 8 3-12
NSAD program 3-14, 3-15
NSAR for DPS 8000 3-12
NSAR program 3-16
PR1 3-11
responses to dump question 3-11
size of DUMP1-DUMP9 files 5-110
SSFILE file 3-23
Startup buffer areas 3-11
Startup snapshot dump 3-21
Startup-created file 3-23
System Master Catalog (SMC) 3-23
via $ SNAP 3-21
with no printer 5-31
DUMPO
$ FILDEF 5-110
DUMPO B-6
DUMP1-DUMP9
DUMP1-DUMP9
DUMP ON
$ ANSWER
B-6
5-8
DUPLICATE
define duplicate before journal
device 4-12
i-25
DH18-03
DUPLICATE (cont)
duplicate'checkpoint journal. device
4-16
duplicate checkpoint journal file
4-16
duplicate historical log 4-18
duplicate historical log device
4-19
request duplication of before
journals and ·PAT images 4-11
DYNAMIC
processor assignment
5-22
ECFILE
site-option patch for ECFILE size
5-156
ECOL
shared controller/device I/O
statistics collection 5-157
site-option patch for ECFILE size
5-156
site-option patch for ECOL MME
GEWAKE time 5-155
site-option patch to disable logging
exception processing records
5-155
site-option patch to inhibit
automatic start of ECOL 5-153
site-option patches for cache memory
control 5-155
site-option patches for ECOL
parameters 5-154
ECS
site-option patch for ECS error
thresholds 5-158
EDIT
$ ANSWER 5-6
$ ANSWER example 5-9
editing new firmware onto the
deckfile 2-43
insert edit 5-190
re-edit the PRINTlMAGE file B-19
re-editing the deckfile 2-37
Startup deck image edited from
console 2-14
TOTAL provides YES answer to the
• EDIT? question 2-27
EDITOR
*C Edi,tor 2-12
Patch Editor (PAED) progr~ 5-133,
5-137,5-138
Startup Console Editor 2-14
System Library Editor 5-136
ELAN
shared controller/device I/O
statistics collection 5-157
system identification 5-84
ELAPSED TIME
deferred session elapsed time rate
5-187
elapsed time charge rate 5-184
ELPPR
site-option patch
5-184
EMULATOR
console emulator 3-2
ENABLE
console verb
5-50
ENCRYP
$ INFO option
5-22
ENCRYPTION
SMC passwords
5-22
END CHANGES
END CHANGES directive syntax
END DEFAULTS
END DEFAULTS directive syntax
4-48
4-48
EOM
response to .DISK PACK ERROR message
2-32
EPU
DPS 90; $ MCT, EPU 5-73
ERROR
$FILES errors 5-115
Bootloader program 3-1
checksum error 3-3
common OCTAL correction statement
errors 5-136 .
ignore errors when writing to
historical log 4-18
i-26
DH18-03
ERROR (cont)
Integrated Software memory
allocation abort error message
4-38
mass storage read/write error 3-5
modify Integrated Software error
messages 4-58
printer 3-6
recoverable 3-4
SDLD error and warning messages
4-57
SDLD fatal error messages 4-57
site-option patch for ECS error
thresholds 5-158
site-option patch for MOS error
message count threshold 5-154
site-option patch for MPC error
threshold 5-154
site-option patch for number of
processor error record buffers
5-153
Startup error messages 3-3, 3-5
Startup file system 3-21
Startup printer error messages 3-6
status error 3-3
TSS program logic error processing
and recovery 5-179
unrecoverable system error 3-10
EXAMPLE (cont)
$ Iyy magnetic tape subsystem
statement (example) 5-59
$ Iyy mass storage subsystem
statement 5-54
$ LIBRARY 5-120
$ MCT 5-73
$ MPC 5-77, 5-78
$ MPCFIG 5-80
$ PFILES 5-126
$ READIN 5-105
$ SCFBUF 5-127
$ SCFDSP 5-128
$ SSFILE 5-114
$ SSLOAD 5-130
$ SYSTEM 5-132
$ TRACE 5-86
$ TRAINS 5-89
$ UNIT 5-89
$ URP 5-90
$ XBAR 5-92
OCTAL correction statement 5-136
using $ ANSWER to answer Startup and
Dump questions 5-9
ERROR LOGGING AND ANALYSIS SYSTEM
system identification 5-84
EXCHG
console verb
EXAMPLE
$ ACCBUF 5-116
$ ACCOUNT 5-118
$ AUTOLD 5-9
$ BASE 5-10
$ CHAN 5-11
$ CIU 5-12
$ DECKFIL 5-13
$ DEKSAV 5-96
$ DIRECT 5-99
$ DTFILE 5-109
$ ENDTF 5-109
$ FILDEF 5-112
$ GCOSFIL 5-15
$ IMAGE 5-18
$ INIT 5-102
$ Iyy card reader statement 5-71
$ Iyy DATANET processor statement
5-63
$ Iyy for system control devices
5-48
EXCLUDE
EXCLUDE DOMAIN directive syntax
4-49 -
EXCEPTION PROCESSING
site-option patches for statistics
collection 5-153
5-56
EXECUTION REPORT
execution report message file
5-163
EXECUTIVE
site-option patches to Time Sharing
Executive 5-167
Time Sharing System Executive 5-189
EXPRESS CLASS
$ SSLOAD parameter 5-130
EXTTDS
$ INFO option 5-23
EXTTSS
$ INFO option
1-27
5-23
DH18-03
FAST BOOT
$ FILCREA FASTBT 2-6
$ INFO ROLLCALL interrupts fast boot
5-37
abort 2-6
automatic device release 2-32
bypasses load of character set and
VFC 2-26
bypasses MPC verification and MPC
bootload 2-25
enable 5-23
expedite warm and fast boots via $
ANSWER 5-5
fast boo t 2-5
fast boot with FASTBT file 2-2
fast boot without FASTBT file 2-2
FASTBT option 2-6
inhibit fast boot 2-6
magnetic tape handler survey 2-35
option 1-2
restart 5-19
FEP GATEWAY
$ IY1 statement for Front-End
Processors 5-62
FILE
**
file 5~134·
*L file 5-119
accounting file size 5-110
adding new system files 2-46
ASSIGN -PRIVATE BUFFER POOL FILE
directive 4-36
assigning GeOS system files to mass
storage 5-109
AUTOLOAD file 1-2, 1-4, 2-2, 2-4,
2-5, 2-7, 2-8, 2-14, 2-18, 2-27,
3-8, 5-9, 5-13, 5-102, 5-109, B-4
AUTOLOAD file and DECKFILE
modification B-15
AUTOLOAD file destroyed 3-8
AUTOLOAD file device 5-9
AUTOLOAD file size 5-9, B-15
AUTOLOAD file update 2-3
balance system files 5-109
catalog into PRINTlMAGE file 5-88
create buffer pools for protected
files 4-35
deckfile 2-30, 2-43, 5-109
defective space on AUTOLOAD device
5-95
defining GCOS system files 5-109
dump control file 5-126
dump the SSFILE file 3-23
dumping file content 3-22
dumping Startup-created file 3-23
E* file 5-134
ensure file availability 5-20
execution report message file 5-163
file boundary 3-6
file dump banner 3-20
File Management Supervisor 1-3
file map banner 3-20
FMS catalog and permanent file
structure 5-54
GCOS system files 1-4, 5-37
high-use system files 5-109
identification of Time Sharing
system files 5-178
identify remaining file space 5-182
identifying $CONFIG section file
residency 5-15
identifying $EDIT section file
residency 5-15
FASTBT
$ ANSWER 5-23
$ INFO option 5-23
FASTBT file 2-2, 5-14
FASTBT ON/OFF 2-5, 2-6
FATAL
SDLD fatal error messages
(
4-57
FAULT
executing a fault 3-12
illegal procedure fault 3-21
process workspace page fault window
delimiter 5-25
Shared Fault Handler domain 4-1
shared workspace page fault window
delimiter 5-26
site-option patch to abort on faults
outside MME GELBAR limits 5-152
site-option patch to abort on master
mode faults 5-152
site-option patch to inhibit fault
logging and reporting 5-154
site-option patch to inhibit logging
of memory faults 5-154
site-option patch to override lockup
fault control value 5-153
site-option patches for fault
processing 5-152
i-28
DH18-03
(
\
I
J
FILE (cont)
identifying required system module
file 5-131
identifying Startup-created files
5-125
identifying system files 5-115
Integrated Software default
parameters on SHARD.SPWN file 4-5
L* file 5-119
load file 1-4, 5-72, 5-191, B-16
low-use system files 5-109
mass storage file I/O rate 5-185
minimum Time Sharing swap file size
5-177
modify/add SYSOUT file B-17
modifying content of AUTOLOAD file
2-11
modifying files 2-46
modifying Integrated Software file
pathnames 4-34
moving the SSFILE file B-20
MSG file 5-163
no files are restored 5-108
number of active swap files 5-177
number of buffers allocated to each
protected file at file-open time
4-21
overlaying the AUTOLOAD file 3-8
pathname of file assigned to buffer
pool 4-36
PRINTIMAGE file 2-26, 2-36, 5-16
purge all files 5-100
re-edit the deckfile 2-37, B-15
re-edit the PRINTlMAGE file B-19
reallocation of temporary file
5-29, 5-30
reboot via AUTOLOAD file 3-8
recovery files 2-3
save file 5-126, B-8, B-16
SDLD input file allocation 4-52
SDLD output file allocation 4-52
SHARD spawn file 4-3, 4-4
site-option patch *J and J* initial
size 5-158
size of deckfile B-15
size of DUMP1-DUMP9 files 5-110
size of the load file B-16
specifying files for spooling 5-131
specifying firmware data deckfile
name 5-12
specifying MPC Bootload (MPCB) file
name 5-12
FILE (cont)
SSFILE file 2-21, 2-47,5-39,
5-112, B-20
Startup file system 3-21
Startup job stream written to
AUTOLOAD file 5-9
Statistical Collection File 2-22
SYSOUT files B-6
system files 2-32, 2-44, 5-53,
5-132, B-6
System Scheduler files 5-109
temporary file space 5-54
Time Sharing deferred queue file
5-178
Time Sharing initialization file
5-189
Time Sharing permanent file address
descriptions 5-179
Time Sharing primary and secondary
program files 5-178
Time Sharing swap file growth factor
5-177
Time Sharing swap file parameters
5-177
Time Sharing swap files 5-178
USERID for permanent deferred queue
file 5-170
USERID for permanent primary or
secondary file 5-170
USERID for permanent swap file
5-170
USERID image of select file for
spawned jobs 5-150
workstation definition data base
(WO) file 5-64, 5-66
workstation management schema file
pathname 4-34
workstation management subschema
file pathname 4-34
FILE CODE
define output file code for
Integrated Software statistics
4-26
FILE MANAGEMENT SUPERVISOR
$ PFILES 5-125
$PATCH 5-133
catalog and permanent file structure
5-54
catalogs B-10
disable FMS creation of catalogs
2-34
)
i-29
--
---
DH18-03
-------------------------------------------------
FILE MANAGEMENT SUPERVISOR (cont)
duplicate catalogs 5-20
enable catalog creation on device
5-101
enable FMS creation of catalogs
2-34
Startup Master Catalog 1-3
statistics 5-24
system identification 5-84
unassignable space 2-25
FILE MAP
inhibit printing
5-7
FILEGROW
$ FILDEF option
5-111
FIPS-79
UFAS tape label
5-33
FIRMWARE
absent firmware 2-29
bootloading MPC firmware B-5
cold boot loads MPC firmware 2-4
data deck and delimiters 5-103
deckfile 5-93
density of firmware tape. 5-105
DPS 88 and DPS 90 ~-1
editing new firmware onto the
deckfile 2-43
firmware deck 5-12, 5-79, 5-95,
5-102
firmware for DPS 88 loaded by S~ffiS
5-104
firmware revision level 5-79
firmware tape B-5
format of firmware decks 5-102
IMU controller 2-2
installing the IFAD tape 5-13
load 3-11
mass storage B-5
MPC 2-29
MPC firmware data decks 2-4
MPC firmware not loaded 2-29
MPC firmware tape 2-4
MPC firmware verification 2-30
patching MPCB and firmware data
images 5-104
power-up 2-3
read MPC firmware 5-104
revision level 2-30, B-5
save.MPC firmware job stream 5-96
FIRMWARE (cont)
specifying firmware data deckf1le
name 5-12
FMS
$ PFILES 5-125
$PATCH 5-133
catalog and permanent file structure
5-54
catalogs B\"'"10
disable FMS creation of catalogs
2-34
duplicate catalogs 5-20
enable catalog creation on device
5-101
enableFMS creation of catalogs
2-34
Startup Master Catalog 1-3
statistics 5-24
system identification 5-84
unassignable space 2-25
FMSCT
$ INFO option
5-23
FMSDT
$ INFO option 5-23
FMSST
$ INFO option
5-23
FMSTAT
$ INFO option
5-24
FNP
$ INFO option
5-24
FORMAT
$ ACCBUF 5-116
$ ACCOUNT 5-117
$ ANSWER 5-5
$ AUTOLD 5-9
$ BASE 5-10
$ CHAN 5-11
$ CIU 5-12
$ DECKFIL 5-13
$ DEKSAV 5-96
$ DFILES 5-118
$ DIRECT 5-97
$ DIRECT D, 0, A, L, Y 5-98
$ DKEND 5-103
$ DTFILE 5-108
$ DUP 5-14
i-30
DH18-03
FORMAT (cont)
$ ENDTF 5-108
$ ETC 5-3
$ FILCREA 5-14
$ FILDEF 5-110
$ GCOSFIL 5-15
$ GHCM 5-192
$ GROUP 5-15
$ IMAGE 5-17
$ lMU for maintenance console 5-50
$ IMX for maintenance console 5-50
$ INFO 5-19
$ INIT 5-100
$ Iyy for both DNET/ROUT mode and
CXI mode 5-65
$ Iyy for card punch 5-70
$ Iyy for card reader 5-70
$ Iyy for CXI mode 5-64
$ Iyy for database computer 5-69
$ Iyy for DNET/ROUT mode 5-62
$ Iyy for HYPERchannel 5-68
$ Iyy for magnetic tape subsystems
5-56
$ Iyy for mass storage subsystems
5-51
$ Iyy for Page Processing System
5-67
$ Iyy for printers 5-61
$ Iyy for remote maintenance console
5-49
$ Iyy for system control device
5-47
$ Iyy for system control devices
5-47
$ Iyy for VIDEO device 5-49
$ LIBRARY 5-119
$ LOADFIL 5-72
$ MCT 5-72
$ MODOPT 5-121
$ MPC 5-76
$ MPCFIG 5-79
$ OBJECT 5-103
$ PFILES 5-126
$ READIN 5-105
$ SAVE 5-127
$ SCFBUF 5-127
$ SCFDSP 5-128
$ SECURE 5-80
$ SHARED 5-83
$ SHCM 5-191
$ SSFILE 5-113
$ SSLOAD 5-129
$ SYID 5-84
FORMAT (cont)
$ SYSOUT 5-131
$ SYSTEM 5-132
$ TRACE 5-85
$ TRAINS 5-88
$ UNIT 5-89
$ URP 5-90
$ VOPT 5-105
$ VSET 5-106
$ XBAR 5-91
firmware decks 5-102
mass storage device 2-37
OCTAL 5-135
RSIP/MTAR/FTAR formatting 2-42
vertical format control 5-17
FREE-CHAIN
free-chain low threshold
5-25
FRONT-END PROCESSORS
$ Iyy statement for Front-End
Processors 5-62
FTAR
formatting
2-42
FUNCTION WORDS
.MSCN1 ACTIV1 and ACTIV2
.MSCN1 RESOR1 and RESOR2
5-162
5-161
GCOS
character set 5-88
defining GCOS system files 5-109
establishing GCOS system 5-107
Gces system files 5-37
GCOS system modules 5-190
Gces system programs 1-4, 5-137
Gces system software 2-4
system files 1-4
TSS causes GCOS abort 5-179
GCR
GCR devices
5-22
GEIN SPAWN
site-option patch to suppress GEIN
SPAWN console message 5-164
GENERAL LOADER
use of system libraries
5-119
GENERALIZED TAPE MANAGEMENT SYSTEM
$ INFO GENSYS 5-24
1-31
DH18-03
GENSYS
$ INFO option
5-24
GEOT
blink release threshold 5-41
enabling GEOT trace 5-24
GEOTRC
$ INFO option
5-24
GLOBAL DATA MANAGEMENT
domain 4-1
print Global Data Management
process-level statistics 4-30
print Global Data Management
system-level statistics 4-27
GROUP
$ GROUP required
5-15
GTMS
$ INFO GENSYS 5-24
Tape Management System 5-127, B-7
HARD CORE MONITOR
hard core monitor
B-17, B-18
HARDWARE
configuration B-1
crossbarring 5-91
environment 1-1
failure 5-20
loss of critical component 2-6
mass storage hardware configuration
change 5-46
Reset Out (RSO) hardware option
2-10
system hardware parameters 1-3, 5-3
HCM
HCM B-17, B-18
patches to HCM modules
5-134
HEADER
device header 2-25
number of before journal control
intervals written between header
records 4-11
HEX
$ INFO option 5-24
HEX ON/OFF 5-24
HEX statements 5-133'
HISTORICAL LOG
create 4-17
duplicate historical log 4-18
duplicate historical log device
4-19
entry for each commitment taken
4-19
entry for each protected file close
4-20
entry for each protected file open
4-19
historical log device 4-18
historical log domain 4-1
ignore errors when writing to
historical log 4-18
number of control intervals 4-17
print historical log domain
system-level statistics 4-28
size of control interval 4-18
HISTORY
defective space history table 5-96,
5-99
faults that lock a history register
5-153
history register 3-21
HYPER
$ Iyy statement for HYPERchannel
5-68
HYPE RCHANNEL
HYPERchannel adapter
5-68
I-D-S/II
print I-D-S/II Domain process-level
statistics 4-32
I/O
average disk I/O time value 5-186
I/O priority parameters 5-140
mass storage file I/O rate 5-185
NIAST I/O activity 5-31
Protected File I/O domain 4-1
shared controller/device I/O
statistics collection 5-157
site-option patch to reduce
interrupt processing overhead
5-165
snap of disk I/O interval trace
table 2-41
i-32
DH18-03
IDENT
IDE NT image for console spawned jobs
5-149
modifying $ IDENT for After Journal
4-9
modifying $ IDENT for Checkpoint
Journaling 4-12
IDENTIFICATION BLOCK
$ OBJECT identification block
5-103
IFAD
create empty deckfile for IFAD
installing 5-13, 5-94
2-43
IGNORE
console verb
5-116
ILLEGAL PROCEDURE FAULT
site-option patch to inhibit logging
5-154
IMAGE
$ IMAGE 5-16
IDENT image for console spawned jobs
5-149
VFC images 2-36
lMU
$ lMU statement for maintenance
console 5-50
$ Iyy for eXI mode 5-64
$ Iyy for DNET/ROUT mode 5-62
assigning peripheral devices to
channels 5-46
DPS 8; $ 10M, $ lMU 5-47
release by Startup 2-12
lMU CONTROLLER
firmware 2-2
INITIALIZATION
audit trail 2-27
AUTOLOAD device 5-104
debugging 2-27
device 1-3, 2-25, 2-34
INITIALIZE push button 3-2
Local/Remote system initialization
(example) 5-50
mass storage device 2-38
mass storage devices 2-24, 2-26,
5-93, 5-99, 5-100, B-5
operator controls 2-26
Removable Storage Initialization
Program (RSIP) 2-40
responses to the *INITIALIZE?
question 2-26
secondary 2-28
selective 2-27
supplemental questions 2-37
Time Sharing initialization 5-189
INITIALIZATION FILE
Time Sharing 5-189
INITIALIZE
$ ANSWER 5-6
$ ANSWER example
5-9
INPUT
job input saved via $ INFO SCHSAV
5-39
SDLD input file allocation 4-52
site-option patches for System Input
5-158
INPUT/OUTPUT
$ Iyy statements
5-46
INPUT/OUTPUT CONTROLLERS
crossbarring 5-91
release by Startup 2-12
IMX
$ IMX statement for maintenance
console 5-50
$ Iyy for eXI mode 5-64
$ Iyy for DNET/ROUT mode 5-62
assigning peripheral devices to
channels 5-46
DPS 8000; $ IMX 5-47
INPUT/OUTPUT SUPERVISOR
site-option patch 5-165
INSTALLATION
IFAD tape 5-13
installing a new system B-1
Startup job stream -new
installation B-1
INCLUDE
INCLUDE DOMAIN directive syntax
4-49
i-33
DH18-03
INSTRUCTION RETRY
site-option patch to disable
instruction retry. 5~l52
INTEGRATED FIRMWARE AND DIAGNOsr!C
TAPE
in~talling
5-13
INTEGRATED SOFTWARE
automatic restart 4-3
default paramete~ modification 4-7
default parameters on the SHARD.SPWN
file 4-5
default RSPACE and VSPACE values for
Integrated Software 4-4
define output file code for
Integrated Software statistics
4-26
domains 4-1
domains on SHARD.SPWN file 4-5
ensuring sufficient memory 4-38
formula for minimum wired real
memory page requirements for
Integrated Software 4-39
installing 4-2
insufficient space 4-38
INTEGRATED SOFTWARE LOADED
SUCCESSFULLY message 4-3
Integrated Software Output Report
domain 4-1
Integrated Software process-level
statistics 4-29
Integrated Software system-level
statistics 4-26
Integrated Software Termination
domain 4-1
Integrated Software Trace domain
4-1
job stream to load Integrated
Software 4-53
loading 4-2, 4-3
memory allocation abort error
message 4-38
message reports maximum wired pages
for Integrated Software 4-2
modifiable parameters 4-2
modify Integrated Software error
messages 4-58
modifying file pathnames 4-34
primary search library 4-5
print After Journal Domain
system-level statistics 4-28
INTEGRATED SOFTWARE (cont)
print After Journal process-level
statistics 4-31
prin t -. Be~ore Journal process-level
statistics 4-31
print Buffer Management Domain
process-level statistics 4-30
print Buffer Management Domain
system-level statistics 4-27
print Concurrency Control Domain
system-level statistics 4-28
print Global Data Management
process-level statistics 4-30
print Global Data Management
system-level statistics 4-27
print historical log domain
system-level statistics 4-28
print I-D-S/II Domain process-level
statistics 4-32
print Protected File I/O Domain
process-level statistics 4-32
print Protected File I/O Domain
system-level statistics 4-29
print statistics at abnormal
termination of process 4-25
print statistics at normal
termination of process 4-25
print statistics for batch processes
4-32
print statistics for DM-IV/TP
processes 4-33
print statistics for TDS processes
4-33
print statistics for TS8 processes
4-34
print statistics for workstation
processes 4-33
real memory requirements 4-2
report code for Integrated Software
statistics 4-26
requirements for loading Integrated
Software domains 4-53
restart 4-37
secondary search library 4-5
successful load message 4-2
terminating 4-37
Trace and Load Map Display domain
4-1
virtual memory 4-38
wired pages 4-38
wired real memory for Integrated
Software 4-23
i-34
DH18-03
Iyy (cont)
$ Iyy for printers 5-61
$ Iyy for system control devices
5-47
$ Iyy for VIDEO device 5-49
INTEGRITY MANAGEMENT
domain 4-1
INTERRUPT
$ INFO option
5-25
INTERRUPT PROCESSING
selecting interrupt processing type
5-25
10M
$ Iyy for CXI mode 5-64
$ Iyy for DNET/ROUT mode 5-62
assigning peripheral devices to
channels 5-46
BOOTLOAD SOURCE TAPE/CARD switch
2-10
DPS 8; $ 10M, $ lMU 5-47
release by Startup 2-12
\
JCL
examination and modification by
.MSCN1 5-159
examine and modify stranger
statement 5-160
JOB
job scheduling 5-129
job sieve limit 5-144
job stream to load Integrated
Software 4-53
job urgency 5-140
maximum number of jobs 5-113, 5-129
modifying job class parameters B-20
lOP
$ Iyy for CXI mode 5-64
$ Iyy for DNET/ROUT mode 5-62
assigning peripheral devices to
channels 5-46
DPS 90; $ lOP 5-47
DPS 90; $ MCT, lOP 5-73
release by Startup 2-12
JOB CLASS
$ SSLOAD 5-129
job class 5-39
job class sizes 5-112
System Scheduler B-7
three job classes required
lOS
site-option patch
JOB OUTPUT TABLE
$ INFO CLENPT 5-21
DP.JOT 2-22
size of job output table segment
(SNUML) 5-41
/
5-165
lOX
$ Iyy for CXI mode 5-64
$ 1yy for DNET/ROUT mode 5-62
assigning peripheral devices to
channels 5-46
DPS 88; $ lOX 5-47
release by Startup 2-12
IPR
site-option patch to inhibit logging
5-154
Iyy
$ Iyy for CXI mode 5-64
$ Iyy for DNET/ROUT mode 5-62
$ Iyy for magnetic tape subsystems
5-56
$ Iyy for mass storage subsystems
5-51
$ Iyy for Page Processing System
5-67
5-113
JOT
size of job output table segment
(SNUML) 5-41
JOURNAL
After Journal Management domain 4-1
After journal save and/or restore ••
file pathname 4-9
Before Journal control interval size
4-10
Before Journal Management domain
4-1
checkpoint journal device 4-16
checkpoint journal dump frequency
4-15
Checkpoint Journal Manager domain
4-1
checkpoint journal size 4-14
1-35
DH18-03
JOURNAL (cont)
duplicate checkpoint journal device
4-16
duplicate checkpoint journal file
4-16
number of activities using
checkpoint journal 4-14
number of before journal control
intervals for commitment unit
J~-10
removable checkpoint journal device
4-16
site parameter for journal directory
control interval size 4-8
site parameter for maximum number of
journals 4-8
JOURNALIZATION
compressed journalization 4-22
full control interval journalization
4-22
JRERUN
JRERUN
5-39
JRUN REST
console verb
2-21, 2-47
K5
site-option patch
5-185
KEYBOARD I/O
characters per page 5-186
keyboard I/O rate 5-185
KEYBOARD-DISPLAY TERMINAL
site-option patch for maximum number
5-167
KLFTH
$ INFO option
5-25
KLMIW
$ INFO option
5-25
KLMWP
$ INFO option
5-25
KLMWS
$ INFO option
5-25
KLWPR
$ INFO option
5-25
KLWSW
$ INFO option
L* FILE
$ LIBRARY
(
5-26
5-119
LABEL
device label 2-26
FIPS-79 UFAS tape label 5-33
inconSistency between logical device
label and SMC 2-31
mass storage device label 5-53
mass storage logical device 2-31,
2-34, 2-37
re-creation of mass storage device
labels 1-3
rebuild logical device label 2-33
tape label verification 5-111
LANGUAGE
modify Integrated Software error
messages 4-58
LIBRARY
identifying system libraries 5-119
Integrated Software primary search
library 4-5
Integrated Software secondary search
library 4-5
Secondary Subroutine Library 5-119
System Library Editor 5-136
System Subroutine Library 5-119
Time Sharing Subsystem Library
5-109
User Subroutine Library 5-119
LIMIT
$ INFO MEMORY 5-27
deferred processing time limit
5-175
job sieve limit 5-144
sieve limit for mag tape files 5-39
sieve limit for max memory size
5-27
sieve limit for maximum number of
SYSOUT records per job 5-42
sieve limit for temporary file links
5-39
single job processor time sieve
limit 5-40
site-option patch to abort on faults
outside MME GELBAR limits 5-152
TSS subsystem memory limit 5-176
DH18-03
LIMIT (cont)
TSS subsystem processor time limit
5-176
LIMITS
$ INFO option
5-26
LINE ADAPTER
bootload firmware
LOCKUP FAULT
site-option patch to override lockup
fault control value 5-153
2-10
LINE-HOLD
line-hold interval following
disconnect 5-175
LINES
$ INFO option 5-26
number of lines per page
5-26
LINK
contiguous defective links 5-98
dumping 3-22
dumping contiguous links 3-22
LINK ADAPTER
link adapter
5-80
LINKS
sieve limit for temporary file links
5-39
LLINK
building defective llink directory
2-42
contiguous defective llinks 5-98
defective llink directory 2-40,
2-42, 5-96
Defective Llink Directory Print
program 5-98
dumping 3-22
dumping contiguous llinks 3-22
LOAD
job stream to load Integrated
Software 4-53
requirements for loading Integrated
Software domains 4-53
LOAD FILE
$LOAD section 5-191
load file 1-4, 5-72
modification B-16
replacement 3-9
size B-16
LOAD MAP
Integrated Software Trace and Load
Map Display domain 4-1
SDLD Backdoor Load Map report 4-56
SDLD Load Map list output 4-55
SOLD Load Map Summary output 4-56
LODS
LODS permission
5-170
LOG
create historical log 4-17
duplicate historical log 4-18
duplicate historical log device
4-19
historical log device 4-18
historical log domain 4-1
ignore errors when writing to
historical log 4-18
number of control intervals for
historical log 4-17
print historical log domain
system-level statistics 4-28
size of control interval for
historical log 4-18
LOGIC
TSS program logic error processing
and recovery 5-179
LOGICAL
logical device name
B-9
LOGICAL CHANNEL
multiple logical channels
5-92
LOGICAL DEVICE
logical device name 5-46, B-11,
B-12
magnetic tape logical device name
5-57
mass storage logical device name
5-53
multiple logical device names 5-47
printer logical device name 5-62
required logical device names 5-47
LOGON
$ INFO option
i-37
5-26
DH18-03
LOGON (cont)
activate logon LOAD message 5-183
logon security requires password
changes 5-183
Time Sharing logon message ,5-182
LOWER ADDRESS LIMIT
patches below LAL
5-138
LUMP
$ FILDEF 5-110
LUMP B-8
save file modification B-16
MAGNETIC TAPE
$ Iyy for magnetic tape subsystems
5-56
allocation class 5-58
bootloading the controller B-5
cold boot 2-4
dedicating 5-59
default densities 5-22
firmware 5-95
handler released 2-35
influencing the order of magnetic
tape allocation 5-57
initial configuration B-11
initiating bootload 2-10
magnetic tape density code 5-57
magnetic tape disposition at .MPOPM
rollcall 5-146
magnetic tape logical device name
5-57
magnetic tape unit identification
number 5-57
maximum number of magnetic tape
units 5-59
MPC firmware tape 2-4
number of magnetic tape units 5-57
reserving a tape unit 5-59
SCF 2-22
sieve limit for mag tape files 5-39
site-customized boot tape 2-1
site-option patch to inhibit
monitoring mag tape MPC threshold
5-154
site-specific boot tape 2-1, 2-4
specifying density capabilities
5-42
tape handler survey 1-3, 2-26,
2-35, 5-93
MAILBOX
mailbox switches 5-10
Network Processor CXI mode mailbox
address switches 5-65
Network Processor DNET/ROUT mode
mailbox address switches 5-65
MAINFRAME
adding mainframe components 5-10
maximum site mainframe configuration
5-10
MAINTENANCE CONSOLE
$ IMU statement 5-50
$ IMX statement 5-50
MAP
inhibit printing of deckfile map
5-28
inhibit printing of file map 5-7
inhibit printing of system map 5-7
system map banner 3-20
system maps B-2
MASK
duplicate MASK 3-4
erroneous MASK 3-3
for console channel 3-1
MASK correction statement
1-2, 3-4,
3-9, 3-10, 5-3, 5-133
rejection 3-2
MASS STORAGE
$ Iyy statement 5-51
$LOAD mass storage device B-4
assigning GeOS system files to mass
storage 5-109
bootload 2-7, 3-8
bootloading the mass storage
controller B-5
controller 2-4
defining defective space 5-93
device initialization 5-100, B-5
device verification 5-93
direct boot load from mass storage
1-2
dumps 3-10
firmware 5-95, 5-102
influencing the order of mass
storage allocation 5-52
initial configuration B-9
logical device identification number
5-14, 5-52
i-38
DH18-03
MASS STORAGE (cont)
logical device name 5-53
Mass Storage Allocation program
5-53
mass storage file I/O rate 5-185
mass storage subsystem parameters
5-52
number of mass storage devices 5-52
permanent mass storage device
verification 2-26, 2-31
permanent mass storage devices 2-25
preference list for mass storage
device allocation 5-148
procedure for disk bootload 2-9
read/write error 3-5
redefining mass storage device B-19
release offline mass storage devices
5-37
SCF 2-22
sieve limit for temporary file links
5-39
subsystem/device initialization
5-93
verification of all permanent mass
storage devices 1-3, 2-32
warm boot from mass storage 2-7
~R
Microcoded Device Routines
MEASUREMENT RECORD
enable TSS measurement record
1-2, 2-3, 2-22,
MASTER USER
use rid 5-170
MAXIMUM
message reports maximum wired pages
for Integrated Software 4-2
process workspace maximum window
time 5-25
shared workspace maximum window time
5-25
MCA
Maintenance Console Adapter channel
5-50
MCPTSS
$ INFO option
5-176
MEmn
MASTER MODE
site-option patch to abort on master
mode faults 5-152
MASTER MODE DUMP
$ FILDEF 5-110
Master Mode Dump
3-10, 5-110
5-80
$ INFO option 5-27
allocation 2-22
bootload clears system tables 2-3
default allocation of virtual memory
for Integrated Software 4-38
default RSPACE and VSPACE values for
Integrated Software 4-4
defective memory 2-12
defining memory size 5-72
dump 3-10, 3-21
dump all of main memory 3-11
dump following Startup abort 3-10
ensuring sufficient memory for
Integrated Software execution
4-38
examples of wired real memory page
requirements 4-42
formula for minimum wired real
memory page requirements for
Integrated Software 4-39
generating dump of main memory 3-21
holes 2-12
in-memory tables 5-131
in-memory tables overwritten 5-101
initiating dump- 3-10
Integrated Software memory
allocation abort error message
4-38
Integrated Software real memory
requirements 4-2
Integrated Software virtual memory
4-38
Integrated Software wired pages
4-38
load modules into main memory 1-4,
5-190
main memory 3-8, 3-21
main memory modification 3-21
main memory tables 1-4, 5-115
maximum memory size of Time Sharing
5-172
memory allocated to the Time Sharing
System 5-183
memory allocation delays in Time
Sharing 5-173
5-26
i-39
DH18-03
MEMORY (cont)
memory allocation for DRL TASK job
5-169
memory allocator 1-5
memory available to Time Sharing
System 5-23
memory available to Transaction
Driven System 5-23
message reports maximum wired pages
for Integrated Software 4-2
MPC read/write memory 5-76
NIAST memory requirement 5-31
percentage of Time Sharing System
memory in use 5-183
read/write memory 5-104, 5-133
resident in main memory 5-191
site-option patch to inhibit logging
of memory faults 5-154
site-option patches for cache memory
control 5-155
specifying modules to reside in main
memory 5-28
Time Sharing memory allocation
algorithm 5-174
Time Sharing memory reserved for
urgent jobs 5-174
Time Sharing memory usage rate
5-184
Time Sharing minimum memory size
5-172
Time Sharing request and release of
memory space 5-173
TSS subsystem memory limit 5-176
verify size 1-2
wired real memory for Integrated
Software 4-23
zero all main memory 1-2
MESSAGE
activate logon LOAD message 5-183
INTEGRATED SOFTWARE LOADED
SUCCESSFULLY message' 4-3
message reports maximum wired pages
for Integrated Software 4-2
modify Integrated Software error
messages 4-58
rollcall messages 5-37
rollcall messages suppressed 5-23
SDLD error and warning messages
4-57
SDLD fa tal error message.s 4-57
site-option patch for MOS error
message count threshold 5-154
MESSAGE (cont)
Startup abort messages 3-6
Startup error messages 3-3, 3-5
Startup printer error messages 3-6
Time Sharing logon message 5-182
Time Sharing status message
frequency 5-171
MICROPROGRAMMABLE PERIPHERAL
CONTROLLER
$ MPC 5-76
firmware revision level 5-79
MIGRAT
$ INFO option
5-27
MIGRATION
4/JS3 to GCOS 8 5-27
MINIMUM WINDOW SPACE
shared workspace minimum window
space 5-25
MIRRORED DISK
$ DUP 5-14
logical device name for secondary
device 5-53
MIXED
$ INFO option
mixed systems
5-27
5-27
MME GELBAR
site-option patch to abort on faults
outside MME GELBAR limits 5-152
MME GEMORE
site-option patch for number of
retries 5-165
MME GESNUM
site-option patch to extend range of
generated SNUMBs 5-166
MME GEWAKE
site-option patch for ECOL MME
GEWAKE time 5-155
MODE
Common Exchange Interface (exI) mode
5-64
device type for CXI mode 5-64
device type for DNET/ROUT mode 5-64
1-40
DH18-03
MODE (cont)
Network Processor CXI mode mailbox
address switches 5-65
Network Processor numbering for CXI
mode 5-64
Network Processor numbering for
DNET/ROUT mode 5-64
MODIFY
AUTOLOAD file and DECKFILE file
B-15
Integrated Software default
parameter modification 4-7
Integrated Software file pathnames
4-34
Integrated Software modifiable
parameters 4-2
JCL examination and modification by
.MSCN1 5-159
load file B-16
loading site modified TSS subsystems
5-190
main memory modification 3-21
modify Integrated Software error
messages 4-58
modify the Time Sharing System
5-189
modify/add printer character set
B-19
modify/add SYSOUT file B-17
modifying $ IDENT for After Journal
4-9
modifying $ IDENT for Checkpoint
Journaling 4-12
modifying $ USERID for After Journal
4-9
modifying $ USERID for Checkpoint
Journaling 4-12
modifying content of AUTOLOAD file
2-11
modifying content of site-specific
boot tape 2-12
modifying files 2-46
modifying job class parameters B-20
save file modification B-16
Startup job stream modification B-1
stranger JCL statement 5-160
stranger statement modification
5-160
MODULE
$ INFO option 5-28
.MALC1 site-option patches
5-144
MODULE (cont)
.MALC9 site-option patches 5-145
.MDISP Class A priority 5-141
.MDISP Class B priority 5-142
.MDISP site-option patches 5-140,
5-181
.MFALT site-option patches 5-152
.MFSEX site-option patches 5-146
.MGEIN site-option patches 5-158
.MPOPM 1-5, 2-22
.MPOPM site-option patches 5-146
.MSCAN 5-113
.MTIMS 5-85
GCOS system modules 5-190
identifying required system module
file 5-131
JCL examination and modification by
.MSCN1 5-159
load modules into main memory 1-4,
5-190
module-load function 5-28
MODULE/.MSDCB $ INFO option 5-28
not reentrant 5-28
patched modules 5-191
patches to HCM modules 5-134
patches to Slave Service Area (SSA)
modules 5-134
site-prepared modules 1-4
specifying modules to reside in main
memory 5-28
system modules 5-131
MODULE DIRECTORY TABLE
$PATCH 5-134
MODULE NAME TABLE
$ PATCH 5-134
MOLTS
MOLTS 5-12
to bootload MPC
2-29
MOS
site-option patch for MOS error
message count threshold 5-154
MOVE
console verb
5-50
MPC
bootload 5-76
bootloading firmware B-5
bypass bootloading 2-29
i-41
DH18-03
MPC (cont)
cold boot loads MPC·firmware 2-4
configuration ,B-3
firmware 2-29, 5-102
firmware not loaded 2-29
firmware revision level 5-79
firmware verification 2-30
Microprogrammable Peripheral
Controller 5-76
MPC Bootload (MPCB) 2-4, 2-6, 2-29,
5-12, 5-102, 5-133
MPC firmware 5-102
MPC firmware data decks 2-4
MPC firmware tape 2-4
MPC number 5-76
MPC read/write memory 5-76
MPC switches 2-10
MPC verification and bootloading
2-25
read MPC firmware 5-104
save MPC firmware job stream 5-96
site-option patch for MPC error
threshold 5-154
site-option patch for MPC sample
period 5-154
site-option patch to inhibit
monitoring mag tape MPC threshold
5-154
specifying MPC Bootload (MPCB) file
name 5-12
test MPC 2-29, 2-30
MPCB
MPC Bootload 2-4, 2-29, 5-12, 5-102
MPCB deck 5-95, B-5
MPCB program 2-43, 5-77
patching MPCB and firmware data
images 5-104
size of MPCB 5-13
specifying MPC Bootload (MPCB) file
name 5-12
MS0400
$ Iyy device code 5-52
maximum number of devices
5-52
MS0402
$ Iyy device code 5-52
maximum number of devices
5-52
MS0450
$ Iyy device code 5-52
maximum number of devices
MS0500
$ Iyy device code 5-52
maximum number of·devices
5-52
MS0501
$ Iyy device code 5-52
maximum number of devices
5-52
MSC1A
$ Iyy device code 5-52
device preference 5-148
maximum number of devices
parameters 5-52
MSC1B
$ Iyy device code 5-52
device preference 5-148
logical devices 5-52
maximum number of devices
parameters 5-52
MSD1A
$ Iyy device code 5-52
device preference 5-148
logical devices 5-52
maximum number of devices
parameters 5-52
MSD1B
$ Iyy device code 5-52
device preference 5-148
maximum number of devices
parameters 5-52
MSM1A
$ Iyy device code 5-52'
device preference 5-148
maximum number of devices
parameters 5-52
MSM1B
$ Iyy device code 5-52
device preference 5-148
logical devices 5-52
maximum number of devices
parameters 5-52
MSM1E
$ Iyy device code 5-52
device preference 5-14&
maximum number of devices
parameters 5-52
5-52
5-52
5-52
5-52
5-52
5-52
5-52
5-52
i-42
DH18-03
MSS8080
$ GROUP required 5-15
$ Iyy device type 5-52
configuration restrictions 5-51
device preference 5-148
logical devices cannot be exchanged
5-56
MSM1A 5-99
MSM1B 5-99
MSM1E 5-99
parameters 5-52
MSU0400
$ Iyy device type 5-52
bootload from mass storage
device preference 5-148
MS0400 5-99
2-7
MSU0402
$ Iyy device type 5-52
bootload from mass storage
device preference 5-148
MS0402 5-99
2-7
MSU0451
$ Iyy device type 5-52
bootload from mass storage
device preference 5-148
MS0450 5-99
MSU0451 2-42, 5-56, 5-102
2-7
MSU0500
$ Iyy device type 5-52
alternate track table 2-38
bootload from mass storage 2-7
device preference 5-148
MS0500 5-99
MSU0500 2-40, 2-42, 5-40, 5-56,
5-102
test pack question 2-39
MSU0501
$ Iyy device type 5-52
alternate track table 2-38
bootload from mass storage 2-7
device preference 5-148
logical devices cannot be exchanged
5-56
MS0501 5-99
MSU0501 2-40, 2-42
test pack question 2-39
MSU3380
$ GROUP required 5-15
$ Iyy device type 5-52
bootload from mass storage 2-7
configuration restrictions 5-51
device preference 5-148
logical devices cannot be exchanged
5-56
MSC1A 5-99
MSC1B 5-99
parameters 5-52
survey messages 2-16
MSU3381
$ GROUP required 5-15
$ Iyy device type 5-52
bootload from mass storage 2-7
configuration restrictions 5-51
device preference 5-148
logical devices cannot be exchanged
5-56
MSD1A 5-99
MSD1B 5-99
parameters 5-52
MTAR
disk test 2-43
formatting 2-42
MTS0400
$ Iyy statement for magnetic tape
subsystems 5-56
nine-track 5-56
seven-track 5-56
MTS0500
$ Iyy statement for magnetic tape
subsystems 5-56
nine-track 5-56
seven-track 5-56
MTS0600
$ Iyy statement for magnetic tape
subsystems 5-56
nine-track 5-56
seven-track 5-56
MTS0610
$ Iyy statement for magnetic tape
subsystems 5-56
nine-track 5-56
seven-track 5-56
i-43
DH18-03
MTS8200
$ GROUP required 5-15
$ Iyy statement for magnetic tape
subsystems 5-56
nine track 5-56
NIAST (cont)
NIAST 5-101
NIAST option parameters 5-29
secondary initialization 2-28, 2-41
tradeoffs 5-30
MULTI COpy
multicopy Time Sharing 5-143, 5-180
multicopy Time Sharing class B
priority 5-181
time sharing restart 5-19
NINE-TRACK
MTS0400/0500 5-56
MTS0500 5-56
MTS0600 5-56
MTS0610 5-56
MTS8200 5-56
NAME
console verb
5-47
NAME TABLE
device name table
NDFMAP
$ INFO option
NOF~1S
$ Iyy NOFMS
5-110
2-34,5-54,5-101,
2-26,2-31,2-33
NOTATION
rules for notation
5-2
5-28
NETWORK PROCESSOR
$ INFO FNP 5-24
$ Iyy statement for CXl mode 5-64
$ Iyy statement for DNET/ROUT mode
5-62
Network Processor mailbox address
switches 5-65
Network Processor numbering for CXl
mode 5-64
Network Processor numbering for
DNET/ROUT mode 5-64
reconnect 5-19
NPCHSZ
$ INFO option
NPL
peripheral device type
NPRINT
$ INFO option 5-31
automatic $ INFO NPRINT
NEWLOD
site-option patch
5-27
5-37
NPS
$ SHARED B-4
common resources between central
system and NPS 5-83
device shared with NPS 2-34
shared devices 5-29
NETWORK PROCESSOR SUPERVISOR
$ SHARED B-4
shared devices 5-29
NEWBLK
site-option patch
5-31
NPUNCH
$ INFO option
5-32
5-182
NRZI
NRZI devices
5-22
5-183
NEWSID
site-option patch 5-182
NIAST
$ INFONIAST option 2-28
$ SHARED 5-83
ALL and RMVBL $ INFO options
1/0 activity 5-31
memory requirement 5-31
5-28
NSA
creating bootable dump tape for NSA
program 3-13
DCPY program copies dump tapes to
disk file 3-18
Native Stand-Alone dump programs
3-12
NSA8 for DPS 88 3-12
NSAD for DPS 8 3-12
NSAD program 3-14, 3-15
i-44
DH18-03
NSA (cont)
NSAR for DPS 8000 3-12
NSAR program 3-16
NSYASC
$ INFO option
5-32
NSYBSC
$ INFO ;option
5-32
NSYSAV
$ INFO option
5-33
NSYTRC
$ INFO option
5-33
OBJECT DECK
$LOAD section
3-20
OPERATOR
circumvention of intervention 2-6
communication 2-1
fast boot bypasses intervention 2-5
intervention 2-1,2-4
operator controls during
initialization 2-26
operator interface 2-14
operator-initiated aborts 3-7
operator-initiated malfunction 3-10
OPNSUTIL
use rid
(cont)
Load Map list output 4-55
Load Map Summary output 4-56
output file allocation 4-52
OVERHEAD
site-option patch to reduce I/O
interrupt processing overhead
5-165
OVERLAY
common patch space 5-138
specifying number of SSA overlays
5-41
OWNID
$ INFO option
5-33
5-190
OCTAL
common OCTAL correction statement
errors 5-136
OCTAL correction statements 1-4,
5-104,5-133,5-134,5-140,5-191,
B-8
OCTAL directive syntax 4-49
OCTAL statement format 5-135
ONLINE/OFFLINE
system testing
OUTPUT
SDLD
SDLD
SDLD
5-163
OUTPUT
description of SDLD output 4-54
DP.JOS - Job Output Specials 2-22
DP.JOT - Job Output Table 2~22
Integrated Software Output Report
domain 4-1
Job Ou~put Specials 5-21
SDLD Directives List output 4-55
PACK
change pack serial number 2-38
device header 2-25
discrepencies during mass storage
device verification 2-37
expected pack name 2-31
expected pack number 2-31
formatting 2-37
inconsistency between logical device
label and SMC 2-31
initializing 2-24, 2-26, 2-38
logical device label 2-31,2-34,
2-37
pack header 5-96
pack name 2-33
pack serial number 2-33, 2-38
re-creation of mass storage device
labels 1-3
rebuild logical device label 2-33
reformatting 2-24
selective initialization 2-27
serial number 2-37
structured 2-28
TEST PACK Innnnn? 2-40
verify pack serial number 2-31
wrong pack mounted 2-33, 2-38
PAED
changing PAED-applied patches via
$PATCH 5-139
Patch Editor (PAED) program 5-133,
5-137, 5-138
i-45
DH18-03
PAGE
additional SD.COL segment pages
5-39
examples of wired real memory page
requirements 4-42
formula for minimum wired real
memory page requirements for
Integrated Software 4-39
message reports maximum wired pages
for Integrated Software 4-2
process workspace page fault window
delimiter 5-25
shared workspace page fault window
delimiter 5-26
PARAMETER (cont)
Time Sharing swap file parameters
5-177
PAGE PROCESSING SYSTEM
$ Iyy statement 5-67
configuring remote PPS 5-67
reserved destination ids 5-36
PAT
additional PAT space for Time
Sharing 5-180
request duplication of before
journals and PAT images 4-11
PARAMETER
$ INFO CATDUP 5-20
$ INFO SMCDUP 5-20
$ IN!T CAT 5-20, 5-101
$ Iyy NOFMS 5-101
ASSIGN SITE PARAMETER directive
syntax 4=48
defining operating system parameters
5-19
I/O priority parameters 5-140
Integrated Software default
parameter modification 4-7
Integrated Software default
parameters on SHARD.SPWN file 4-5
Integrated Software modifiable
parameters 4-2
mass storage subsystem parameters
5-52
maximum number of magnetic tape
units 5-59
modifying job class parameters B-20
NIAST option parameters 5-29
parameter and descriptor consistency
checks 4-21
redefining System Scheduler
parameters B-20
site-option patches for ECOL
parameters 5-154
software and hardware parameters
1-3, 5-3
Time Sharing accounting parameters
5-184
PARTIAL
response to -EDIT? 2-46, 5-107
response to -INITIALIZE? 2-25,
2-27, 2-29, 2-30, 2-43, 5-13
PASSWD
$ INFO option
5-33
PASSWORD
expiration interval
5-33
PATCH
$INFO section of Time Sharing
initialization file 5-189
.MALe1 site-option patches 5-144
.. MALC9 si'te-option patches 5-145
.MDISP site-option patches 5-140,
5-141,5-142
.MFALT site-option patches 5-152
.MFSEX site-option patches 5-146
.MGEIN site-option patches 5-158
.MPOPM site-option patches 5-146
add-on patches 5-138
application of patches 5-134
changing PAED-applied patches via
$PATCH 5-139
common patch area 5-138
debug site-option patch 5-164
local patches 5-138
maximum number of patches 5-35
number of patches 5-134
patch corrections 1-4, 5-135
PATCH directive syntax 4-49
PATCH Run Unit directive 1-4
patch-table 5-134
patch types 5-133
patched modules 5-191
patching MPCB and firmware data
images 5-104
patching Startup 3-1,3-9
patching total system software tape
5-133
replacement patches 5-139
i-46
DH18-03
PATCH (cont)
site-option patch for ECFILE size
5-156
site-option patch for target page
fault rate 5-152
site-option patches 1-4, 5-85,
5-133, 5-140, 5-189
temporary patches 5-138
too many patches 5-35
virtual mode patches 5-31
PATCH EDITOR
Patch Editor (PAED) program
5-133,
5-131', 5-138
PATHNAME
after journal save and/or restore **
file 4-9
file assigned to buffer pool 4-36
modifying Integrated Software file
pathnames 4-34
workstation definition data base
4-34
workstation management schema file
4-34
workstation management subschema
file 4-34
PCU0120
$ Iyy format
5-71
PCU0121
$ Iyy format
5-71
PERMANENT FILE
identification of Time Sharing
system files 5-178
Time Sharing permanent file address
descriptions 5-179
PIC
$ SECURE PIC option
5-82
PID
$ SECURE PID option
5-81
PMME GENSNB
site-option patch to extend range of
generated SNUMBs 5-166
POINTER
$INITIALIZE recreates tables and
pointers 5-107
POOL
define buffer pool for Integrated
Software 4-4
PORT
defining port connections
SCU port number 5-73
5-72
POST-MORTEM
bypass recovery of post-mortem data
5-150
POWER-UP
bootload
2-2, 2-3, 5-94
PE
PE devices
5-22
PERIPHERAL
configuration B-3
CPL and NPL peripheral device types
5-27
defining peripheral devices 5-46
PERIPHERAL ALLOCATOR
program debug mode 5-144
site-option patches 5-144
PERIPHERAL ASSIGNMENT TABLE
additional PAT space for Time /
Sharing 5-180
PPH
site-option patch
5-184
PPP
site-option patch
5-185
PPS
$ Iyy statement 5-67
configuring remote PPS 5-67
reserved destination ids 5-36
PPSONL
$ INFO RESVID
5-36
PPU
$ MPC PPU example
5-79
PERIPHERAL SUBSYSTEM INTERFACE
logical channels 5-76
1-47
DH18-03
PR0901
$ Iyy statement
PR1
dump to PR1
PRINTER (cont)
load character set 2-26
modify/add printer character set
B-19
no printer available 5-31
print line width 5-62
printer belt code 5-62
printer logical device name 5-62
printer snaps 2-39
printer type number 5-17, 5-88
PRU1200 3-11
PRU1600 3-11
release offline printer 5-37
releasing a configured printer at
Startup 5-62
restoring image of default printer
belt 5-17
Startup printer error messages 3-6
unit identification number 5-62
5-61
3-11
PR1100
$ Iyy statement
5-61
PR1200
$ Iyy statement
5-61
PR1201
$ Iyy statement
5-61
PR1600
$ Iyy statement
5-61
PREPASS
response to -REPLACE question
2-12, 2-19
2-10,
PRIMARY FILE
Time Sharing primary program file
5-178, 5-179
USERID for permanent primary file
5-170
PRINT
banners
inhibit
5-28
inhibit
inhibit
5-144
printing of deckfile map
printing of file map 5-7
printing of system map 5-7
PRINT IMAGE
see PRINTlMAGE
2-36
PRINT TRAIN
loading 2-6
Table of Print Train Standards
PRINTER
$ Iyy statement 5-61
banner 3-20
character set B-4
character set and VFC 1-3
dedicated 5-62
defining standard printer belts
5-88
errors 3-6
high-speed printer character set
5-88
PRINTER BELT
$ IMAGE 5-17
ASCII 5-18, 5-20
BCD 5-18
logical representation of characters
on belt 5-16
printer belt 5-17
printer belt code 5-62
restoring default image 5-17
PRINTlMAGE
catalog into PRINTIMAGE file 5-88
PRINTlMAGE file 2-26, 2-36, 5-16,
B-6
re-edit the PRINTlMAGE file B-19
PRIORITY
applying class A priority 5-141
applying class B priority 5-142
assigning class B priority 5-143
class A priority enabled 5-140
class B priority dispatches 5-171
class B priority enabled 5-140
I/O priority parameters 5-140
multicopy Time Sharing class B
priority 5-181
TDS class B priority 5-142
TPS class B priority 5-142
TSS class B priority 5-142
PRO
DPS 8; $ MCT 5-13
B-ll
i-48
DH18-03
«
PROCERROR
$ ANSWER 5-6
$ ANSWER example
PROGRAM LOADING
system libraries
5-9
PROCESS
checkpoint file for process
snapshots 4-13
maximum concurrency control
reservations retained for one
process 4-20
PROCESS EXTENSION
$ INFO PROEXT 5-34
PROCESS WORKSPACE
process workspace maximum window
time 5-25
process workspace page fault window
delimiter 5-25
PROCESSOR
Diagnostic Processor Unit (DPU)
5-49
dynamic assignment 5-22
enabling the Maintenance Panel 3-12
granting additional processor time
5-26
illegal procedure fault 3-21
logical processor number 3-24
maintenance panel 3-10
Network Processor mailbox address
switches 5-65
physical processor numbers 3-24
registers 3-21
release 3-24
release and assignment at Startup
3-24
release of slave processor 5-6
Single job processor time sieve
limit 5-40
site-option patch for DRL TASK
maximum processor time 5-167
site-option patch for number of
processor error record buffers
5-153
Time Sharing processors 5-180
TSS subsystem processor time limit
5-176
PROEXT
$ INFO option
5-119
5-34
PROGRAMS
GCOS system programs
1-4
PROTECTED FILE
create buffer pools for protected
files 4-35
domain 4-1
historical log entry for each
protected file close 4-20
historical log entry for each
protected file open 4-19
number of buffers allocated to each
protected file at file-open time
4-21
print Protected File 1/0 Domain
process-level statistics 4-32
print Protected File 1/0 Domain
system-level statistics 4-29
Protected File lID domain internal
trace 4-24
PRU0901
$ Iyy statement
5-61
PRU0903
$ Iyy statement
5-61
PRU0908
$ Iyy statement
5-61
PRU1100
$ Iyy statement
5-61
PRU1200
$ Iyy statement
PRU1200 printer
5-61
3-11
PRU1201
$ Iyy statement
5-61
PRU1203
$ Iyy statement
5-61
PRU1208
$ Iyy statement
5-61
PRU1600
$ Iyy statement
PRU1600 printer
5-61
3-11
f,;
i-49
DH18-03
PSI
bootload B-9
Peripheral Subsystem Interface
PSI logical channel 5-76
PSTATS
console verb
5-76
5-34
PT1SIZ
$ INFO option
5-35
PTCHSZ
$ INFO option
5-35
PUB
equivalent to CH 5-3
use of PUB for channel
PURGE
purge all files
4
1\1)5\
-~~rt
I)
RAPI:-:::ESS DATA SYSTEJQ
activating 5-28
5-55
PSUM
$ INFO option
PURPOSE
Startup
QUEUE
Time Sharing deferred queue file
RATE
deferred session elapsed time rate
5-187
deferred session rate 5-187
elapsed time charge rate 5-184
keyboard I/O rate 5-185
mass storage file I/O rate 5-185
starting and ending times for
reduced rates 5-188
RDERR/JOURNAL/
RDERR/JOURNAL/
4-22
5-47
RDM
$ FILDEF option
5-111
5-100
RE-ENTRANT
modules that are not reentrant
5-28
1-1
PUSH BUTTON
REQUEST 2-45, 3-7
PUSH DOWN FILE
$ SAVE 5-126
QUESTION
$ ANSWER 2-4, 2-6, 2-17
$ ANSWER responses to dump questions
5-8
answering -PROCESSOR ON PORT P
DOESN'T ANSWER CONNECT 3-24
answering questions via $ ANSWER
1-3
questions for which $ ANSWER should
not be used 5-7
responses to dump question 3-11
responses to the -INITIALIZE?
question 2-26
sequence of Startup questions 2-18
supplemental questions during
initialization 2-37
TOTAL provides YES answer to the
-EDIT? question 2-27
REAL MEMORY
default RSPACE value for Integrated
Software 4-4
examples of wired real memory page
requirements 4-42
formula for minimum wired real
memory page requirements for
Integrated Software 4-39
wired real memory for Integrated
Software 4-23
REBOOT
reboot via AUTOLOAD file
RECONFIGURATION
reconfiguration
3-8
2-12
RECORD TYPE
accounting record type
B-7
RECOVERY
recovery files 2-3
saving recovery data 2-3
Startup recovery procedures
SYSOUT recovery 2-21
i-50
3-1
DH18-03
REDUNDANCY
component redundancy
5-91
REEL
verification of reel serial number
2-45
REFORMAT
mass storage devices
REMOTE MAINTENANCE CONSOLE
$ Iyy format for remote maintenance
console 5-49
2-24
REGISTER
faults that lock a history register
5-153
history register 3-21
processor registers 3-21
transfer register 3-21
RELEASE
device 2-32, 2-36, 3-5, 5-46
GEOT blink release threshold 5-41
input/output controllers 2-12
offline mass storage devices 5-37
offline printer 5-37
processor release at Startup 3-24
reassign released devices 2-30
release disk space 5-145
releasing a configured mass storage
device at Startup 5-54
releasing a configured printer at
Startup 5-62
releasing a configured tape at
Startup 5-59
releasing configured card punch at
Startup 5-71
releasing configured card reader at
Startup 5-71
site-option patch for memory release
5-151
slave processor 5-6
tape handler 2-35
Time Sharing request and release of
memory space 5-173
RELINQUISH
console verb
5-50
RELOCATION
relocation references
REMOTE
configuring remote PPS 5-67
CSD customer support via remote
maintenance console 5-49
Local/Remote system initialization
(example) 5-50
REMOVABLE STORAGE INITIALIZATION
PROGRAM
see RSIP 2-40
REPLACE
PREPASS response to .REPLACE
question 2-19
REPORT
report code for Integrated Software
statistics 4-26
SDLD Backdoor Load Map report 4-56
REQUEST
push button
2-45, 3-7
RESERVATION
maximum concurrency control
reservations retained for one
process 4-20
RESET OUT
Reset Out (RSO) hardware option
2-10
RESILIENCE
Startup 2-12, 2-14
RESOURCE CONTROL WORDS
.MSCN1 RESOR1 and RESOR2 5-161
JCL examination and modification by
.MSCN1 5-159
RESOURCES
common resources between central
system and NPS 5-83
5-190
REMARK
SDLD remarks description
4-50
RESPONSE CENTER
Honeywell Bull Response Center
3-20, 5-31
RMC66 dial-in capability 5-49
TS8 module .MTSVC not found 5-44
i-51
DH18-03
RESPONSE CENTER (cont)
unapplied patches 5-31
RLSE (cont)
RLSE console verb
RESTART
$ ANSWER 5-6
$ ANSWER example 5-9
activity restart 5-144
enable cleanpoint- 5-21
fast boot 2-6, 5-19, 5-23
from checkpoints 5-144
Integrated Software 4-3, 4-37
jobs 2-47
jobs/activities 2-21
program restart 2-21
RLSEP
console verb
RESTORE
$PATCH5-133
After journal save and/or restore ••
file pathname 4-9
no files are restored 5-108
RESTRICTIONS
configuration restrictions MSU3380
MSU3381 MSS8080 5-51
RESVID
$ INFO RESVID/FORMS option 5-36
$ INFO RESVID/PPSOFL option 5-36
$ INFO RESVID/PPSONL option 5-36
RETCONFIG
$ ANSWER
RLSPNT
$ INFO option
RMC66
RMC66
B-18
3-20
2-36, 5-37
5-49
RMVBL
$ Iyy removable device
RMVBL 5-101, 5-110
5-53
ROLLCALL
$ INFO option 2-6, 5-37
$INITIALIZE 5-93
device rollcall 1-3, 2-29, 2-30,
5-3
magnetic tape disposition at .MPOPM
rollcall 5-146
messages suppressed 5-23
rollcall 3-24
rollcall messages 5-37
statistical collection tap~
disposition at .MPOPM rOilcall
5-146
RR
5-6
RETRY
site-option patch for automatic
retry summary logging period
5-155
site-option patch for number of MME
GEMORE retries 5-165
RHEX
RHEX correction statement
5-104, 5-133
RLSDSK
$ INFO option
site-option patch
5-187
RRLL
site-option patch
5-188
RRUP
site-option patch 5-188
RSBT
Read Startup Boot Tape (RSBT)
2-12
2-8,
5-37
RLSE
console verb 5-46, 5-55
response to .DISK PACK ERROR message
2-32
response to FIX TYPE GO OR STOP OR
RLSE message 2-36
RSIP
allocation unit 5-53
disk test 2-43
formatting 2-42
Removable Storage Initialization
Program 2-40
RSPACE
default RSPACE value for Integrated
Software 4-4
RSPACE 4-38
i-52
DH18-03
RULES
rules for notation
RUN REST
console verb
5-111
2-12, 5-139
SCF
$ ANSWER 5-6
$ ANSWER example 5-9
device 5-117
on magnetic tape 2-22
on mass storage 2-22
purge-to-disk option 5-38
save dumps 5-188
SCF 5-116, B-6, B-7
Statistical Collection File 2-22
statistical collection tape
disposition at .MPOPM rollcall
5-146
time interval for writing TSRI data
5-168
SCHEDULING
job scheduling
$ MCT 5-72
SCU port number
5-73
SD • COL SEGMENT
additional SD.COL segment pages
5-39
5-38
SCC
$ SECURE SCC option 5-81
configuring System Control Center
(SCC) 5-47
SCFPRG
$ INFO option
5-39
SCU
SAVE
After journal save and/or restore ••
file pathname 4-9
job input saved via $ INFO SCHSAV
5-39
rerunning a saved job 5-39
save file 5-126, B-8
save file modification B-16
save period 5-39
SCED
*C Editor
SCHSAV
$ INFO option
2-21
RUP
$ FILDEF option
SAVDMP
$ INFO option
5-2
5-38
5-129
SD .INJ
table
2-21
SD.MDD
SD.MOD
5-134
SD.MNT
SD.MNT
5-134
SDCOL
$ INFO option 5-39
$ INFO SDCOL 5-39
SDLD
ALLOCATE directive syntax 4-47
ASSIGN SITE PARAMETER directive
syntax 4::48
description of SDLD directives 4-46
description of SDLD output 4-54
END CHANGES directive syntax 4-48
END-DEFAULTS directive syntax 4-48
EXCLUDE DOMAIN directive syntax
4-49
INCLUDE DOMAIN directive syntax
4-49
job stream to load Integrated
Software 4-53
OCTAL directive syntax 4-49
PATCH directive syntax 4-49
SDLD 4-3
SDLD abort codes 4-58
SDLD Backdoor Load Map report 4-56
SDLD configuration 4-52
SDLD directive syntax 4-47
SDLD directives 4-7, 4-45
SDLD Directives List output 4-55
SDLD error and warning messages
4-57
SDLD fatal error messages 4-57
SDLD input file allocation 4-52
SDLD Load Map list output 4-55
SDLD Load Map Summary output 4-56
i-53
DH18-03
SDLD (cont)
SDLD output file allocation 4-52
SDLD remarks description 4-50
START CHANGES directive syntax 4-50
START-DEFAULTS directive syntax
4-50
SECONDARY
initialization
2-28
SECONDARY FILE
Time Sharing secondary program file
5-178, 5-179
USERID for permanent secondary file
5-170
SECONDARY SUBROUTINE LIBRARY
$ LIBRARY 5-119
SECTION
$CONFIG 1-3, 2-26, 2-31, 2-36,
3-11, 5-1, 5-3, 5-21, B-6
$CONFIG sequence requirements 5-4
$EDIT 1-4, 2-4, 2-27, 2-44, 2-45,
3-6, 5-1, 5-17, 5-107, 5-115, B-4,
B-6, B-7
$EDIT ignored 5-108
$FILES 1-4, 5-1, 5-107, 5-115, B-6,
B-7
$FILES errors 5-115
$INFO section of Time Sharing
initialization file 5-189
$INITIALIZE 1-3, 2-4, 2-25, 2-26,
2-29, 3-9, 5-1, 5-93
$LOAD 1-4, 3-8, 3-9, 3-21, 5-1,
5-190, B-8
$LOAD section of Time Sharing
initialization file 5-190
$PATCH 1-4, 5-1, 5-35, 5-104,
5-133, B-8
$PATCH section of Time Sharing
initialization file 5-189
identifying $CONFIG section file
residency 5-15
identifying $EDIT section file
residency 5-15
replace one or more sections 2-18,
3-8
Startup job stream sections 5-1
SECTOR
contiguous defective sectors
invalid 2-41
5-98
SECURITY
$ SECURE ACCESS option 5-81
$ SECURE ALL option 5-82
$ SECURE PIC option 5-82
$ SECURE PID option 5-81
$ SECURE see option 5-81
$ SECURE statement 5-80
$ SECURE SYSTEM option 5-81
logon security requires password
changes 5-183
Multi-Level Security Manager 5-80
SMC password encryption 5-22
SEEK ADDRESS
disable seek address validation
5-33
SEGMENT
maximum slave instruction segment
size 5-39
size of backdoor information segment
5-41
size of job output speCial segment
5-41
size of job output table segment
(SNUML) 5-41
SEQUENCE
card out of sequence 3-3
importance of sequence in
$INITIALIZE section 5-94
of sections 5-1
SERVICE RATE
service rate factor
SESSION CONTROL
domain 4-1
internal trace
5-185
4-24
SET
character set loading
2-36
SEVEN-TRACK
MTS0400/0500 5-56
MTS0600 5-56
MTS0610 5-56
SHARD
ABORT SHARD console verb
SHARD spawn file 4-3
SPAWN SHARD console verb
i-54
4-37
4-3
DH18-03
SHARD.CHGS
modification of parameter
SIEVE LIMIT (cont)
maximum number of SYSOUT records per
job 5-42
single job processor time sieve
limit 5-40
4-7
SHARD.SPWN
Integrated Software default
parameters on SHARD.SPWN file
Integrated Software domains on
SHARD.SPWN file 4-5
modification of parameter 4-7
SHARD.SPWN file 4-4
4-5
SHARED
description of SDLD directives 4-46
description of SDLD output 4-54
device shared with NPS 2-34
SDLD abort codes 4-58
SDLD Backdoor Load Map report 4-56
SDLD configuration 4-52
SDLD directive syntax 4-47
SDLD directives 4-45
SDLD Directives List output 4-55
SDLD error and warning messages
4-57
SDLD fatal error messages 4-57
SDLD input file allocation 4-52
SDLD Load Map list output 4-55
SDLD Load Map Summary output 4-56
SDLD output file allocation 4-52
SDLD remarks description 4-50
shared controller/device I/O
statistics collection 5-157
shared data base 5-76
Shared Data Base Control System
domain 4-1
shared data base control system
statistics 4-32
Shared Domain Loader 4-3
Shared Fault Handler domain 4-1
SHARED WORKSPACE
shared workspace maximum window time
5-25
shared workspace minimum window
space 5-25
shared workspace page fault window
delimiter 5-26
SIEVE LIMIT
$ INFO MEMORY 5-27
job sieve limit 5-144
mag tape files 5~39
mass storage links for temporary
files 5-39
SIX-PROCESSOR
enabling six-processor functionality
5-34
SIZE
AUTOLOAD file 5-9, B-15
back door information segment 5-41
checkpoint journal size 4-14
job output special segment 5-41
job output table segment (SNUML)
5-41
maximum slave instruction segment
5-39
maximum Time Sharing memory 5-172
minimum Time Sharing memory 5-172
minimum Time Sharing swap file
5-177
sieve limit for max memory 5-27
site parameter for journal directory
control interval size 4-8
TSS SIZE console entry 5-172
verify memory size 1-2
SLAVE
$ INFO option
5-39
SLAVE INSTRUCTION SEGMENT
maximum size 5-39
SLAVE PROCESSOR
release 5-6
SLAVE SERVICE AREA
load site-prepared SSA modules
5-190
patches to SSA modules 5-134
speCifying number of SSA overlays
5-41
SLINKS
$ INFO option
5-39
SLTAPE
$ INFO option
5-39
SLTIME
$ INFO option
5-40
i-55
DH18-03
SMAS
firmware loaded by SMAS
5-104
SMC
dump 3-23
dump duplicate SMC 3-23
duplicate 2-34
inconsistency between logical device
label and SMC 2-31
password encryption 5-22
system master catalog 2-25
SMCDUP
$ INFO option 5-40
$ INFO SMCDUP 2-32, 2-34, 5-20,
5-100
SMCDUP 3-23
SMCDUP device and option
verification 2-31
ST1 and SMCDUP device name
verification 2-31
SNAP
dump via $ SNAP
3-21
SNAPSHOT
checkpoint file for process
snapshots 4-13
Startup snapshot dump 3-21
SNUML
size of job output table segment
(SNUML) 5-41
SOFTWARE
cold boot rebuilds system software
2-4
configuration B-1
dump of system software 2-5
environment 1-1
GCOS system software 2-4
identifying software release 5-84
Integrated Software 4-1
system software parameters 1-3, 5-3
SOFTWARE RELEASE
identifying software release
SPACE
additional PAT space for Time
Sharing 5-180
available space table 5-100
5-84
SPACE (cont)
building available space table (AST)
5-28
clearing of defective space
information 2-37, 5-96
contiguous defective space 5-98
controlling disk space allocation
5-28
defective llink directory 5-96,
5-99
defective space 2-25, 5-93, 5-96,
B-5
defective space history table 2-38,
2-40, 2-42, 5-96, 5-99
disable ASCII space compression
5-32
disable BCD space compression 5-32
establishing Available Space Table
(AST) 2-28
identify remaining file space 5-182
insufficient space for Integrated
Software 4-38
master available space table 5-145
release disk space 5-145
site-option patch *J and J* initial
size 5-158
space descriptor threshold 5-23
space threshold 5-23
SSFILE file space 5-112
SYSOUT collection space 5-131
temporary file space 5-54
SPARE
logical device name for secondary
device 5-53
SPAWN
IDENT image for console spawned jobs
5-149
SHARD spawn file 4-3
USE RID image for console spawned
jobs 5-150
USE RID image of select file for
spawned jobs 5";150
SPAWN SHARD
console verb
4-3
SPINOFF
BMC spinoff
5-144
SPN
$ INFO option
i-56
5-40
SPN (cont)
system path name replacement
SPOOLING
specifying files for spooling
5-40
5-131
SSA
load site-prepared SSA modules
5-190
patches to Slave Service Area (SSA)
modules 5-134
specifying number of SSA overlays
5-41
SSAOVL
$ INFO option
5-41
SSCLEAR
$ ANSWER 5-6
$ ANSWER example
SSF
$ Iyy SSF
5-9
5-64
SSFILE
dump 3-23
incomplete clearing 2-47
moving the SSFILE file B-20
SSFILE 2-47, 5-9, 5-39, B-20
SSFILE file space 5-112
System Scheduler' 2-21
ST1
inconsistency between logical device
label and SMC 2-31
logical device name 5-47
recovery files 2-3
ST1 2-25, 5-54, 5-100, 5-101
ST1 and SMCDUP device name
verification 2-31
ST1 must be defined 5-53
system master catalog 5-109
START
START CHANGES directive syntax 4-50
START-DEFAULTS directive syntax
4-50'
STATEMENT
$ ACCBUF 5-115, B-7
$ ACCBUF definition 5-116
$ ACCOUNT 5-115, B-7
$ ACCOUNT definition 5-117
STATEMENT (cont)
$ ANSWER 1-3, 2-4, 2-5, 2-13, 2-14,
2-20, 3-24, 5-6, 5-23, B-2
$ ANSWER definition 5-5
$ ANSWER override 2-20
$ ANSWER responses to dump questions
5-8
$ AUTOLD 2-2, 2-7, 2-8, B-4
$ AUT OLD definition 5-9
$ BASE 2-14, 5-4, 5-65, B-3
$ BASE definition 5-10
$ BUGOFF 2-41
$ BUGON 2-41
$ CHAN 2-13, 2-14, B-4
$ CHAN definition 5-11
$ CIU 3-24, 5-24, B-3, B-18, B-19
$ CIU definition 5-12
$ DBGOFF 2-41
$ DBGON 2-41
$ DECKFIL 5-9, B-5, B-15
$ DECKFIL definition 5-12
$ DEKSAV 5-94, 5-102
$ DEKSAV definition 5-96
$ DFILES 5-115, B-8
$ DFILES definition 5-118
$ DIRECT 2-38, 2-39, 2-41, 2-42,
5-94, B-5
$ DIRECT D, 0, A, L, Y formats 5-98
$ DIRECT definition 5-96
$ DKEND 2-9, 2-44, 5-79, 5-190,
5-191
$ DKEND definition 5-103
$ DTFILE 5-108, B-7
$ DTFILE definition 5-108
$ DUMP in Startup job stream 3-10,
3-22, 3-23
$ DUP definition 5-14
$ ENDTF 5-108, B-7
$ ENDTF definition 5-108
$ ETC 5-5, 5-17, 5-19» 5-58
$ ETC definition 5-3
$ EXTEND 5-134
$ FILCREA definition 5-14
$ FILCREA FAsrBT 2-6
$ FILDEF 2-45, 2-46, 3-6, 5-17,
5-108, 5-119, 5-131, B-6, B-7,
B-14, B-16, B-17, B-19
$ FILDEF definition 5-109
$ GCOSFIL 2-2, 5-4, 5-9, B-4, B-14,
B-15, B-16, B-17, B-20
$ GCOSFIL definition 5-15
$ GHCM definition 5-192
$ GROUP definition 5-15
i-57
DH18-03
STATEMENT (cont)
$'IDENT for console spawned jobs
5-149
$ IMAGE 5-4, 5~17, B-4
$ IMAGE definition 5-16
$ lMU 5-46, B~3, B-9, B-11, B-12,
B-13, B-15, B-16, B-17, B-18,
B-19, B-20
$ lMU for maintenance console 5-50
$ IMX 5-46, B-9, B-11, B-12, B-15,
B-16, B-17, B-18, B-19, B-20
$ IMX for maintenance console 5-50
$ INFO 5-4, 5-105, B-2, B-4, B-10
$ INFO ACALL 5-19
$ INFO ASCII 5-20
$ INFO CATDUP 5-20
$ INFO CATFNC 5-20
$ INFO CCACHE 5-21
$ INFO CHKSUM 5-21
$ INFO CLENPT 2-3, 2-22, 5-21
$ INFO definition 5-19
$ INFO DENxx/DENyy 5-22, 5-144
$ INFO DPSE 5-22
$ INFO ENCRYP 5-22
$ INFO EXTTDS 5-23
$ INFO EXTTSS 5-23
$ INFO FASTBT 2-5, 5-23
$ INFO FMSCT 5-23
$ INFO FMSDT 5-23
$ INFO FMSST 5-23
$ INFO FMSTAT 5-24
$ INFO FNP/n 5-24
$ INFO GENSYS 5-24
$ INFO GEOTRC 5-24
$ INFO HEX 5-24
$ INFO INTERRUPT 5-25
$ INFO KLFTH 5-25
$ INFO KLMIW 5-25
$ INFO'KLMWP 5-25
$ INFO KLMWS 5-25
$ INFO KLWPR 5-25
$ INFO KLWSW 5-26
$ INFO LIMITS 5-26
$ INFO LINES 5-26
$ INFO LOGON 5-26
$ INFO MCPTSS 5-26
$ INFO MEMORY 5-27
$ INFO MIGRAT 5-27
$ INFO MIXED 5-27
$ INFO MODULE 5-28
$ INFO NDFMAP 5-28
$ INFO NIAST 5-28, 5-83
$ INFO NPCHSZ 5-31
STATEMENT (cont)
$ INFO NPRINT 5-31
$ INFO NPUNCH 5-32
$ INFO NSYASC 5-32
$ INFO NSYBSC 5-32
$ INFO NSYSAV 5-33
$ INFO NSYTRC 5-33
$ INFO OWNID 5-33
$ INFO PASSWD 5-33
$ INFO PROEXT 5-34
$ INFO PSUM 5-34
$ INFO PT1SIZ 5-35
$ INFO PTCHSZ 5-35
$ INFO RESVID 5-36
$ INFO RLSDSK 5-37, B-18
$ INFO RLSPNT 2-36, 5-37
$ INFO ROLLCALL 2-6, 5-37
$ INFO SAVDMP 5-38
$ INFO SCFPRG 5-38
$ INFO SCHSAV 5-39
$ INFO SDCOL 5-39
$ INFO SLAVE 5-39
$ INFO SLINKS 5-39
$ INFO SLTAPE 5-39
$ INFO SLTlME 5-40
$ INFO SMCDUP 2-32, 2-34, 5-40,
5-100
$ INFO SPN 5-40
$ INFO SSAOVL 5-41
$ INFO SYBDI 5-41
$ INFO SYBRT 5-41
$ INFO SYJOS 5-41
$ INFO SYJOT 5-41
$ INFO SYSOUT 5-42
$ INFO SYSTEMMAP 5-42
$ INFO TAPDEN 5-42
$ INFO TlMEZ 5-42
$ INFO TS8 5-43
$ INFO USRDMP 5-44
$ INFO WSSIZE 5-45
$ INIT 2-25, 2-26, 5-53, 5-93,
5-94, B-5, B-10
$ INIT CAT 2-34
$ INIT definition 5-99
$ 10M 5-46, B-3, B-9, B-11, B-12,
B-13, B-15, B-16, B-17, B-18,
B-19, B-20
$ lOP 5-46, B-3, ,B-9, B-11, B-12,
B-13, B-15, B-16, B-17, .B-18 ;
B-19, B-20
$ lOX 5-46, B-3, B-9, B-11, B-12,
B-13, B-15, B-16, B-17, B-18,
B-19, B-20
i-58
DH18-03
c
STATEMENT (cont)
$ Iyy 2-32, 2-33, 2-37, 2-38, 5-46,
5-92, 5-95, 5-100, 5-110
$ Iyy definition for both DNET/ROUT
mode and CXI mode 5-65
$ Iyy definition for card punch
5-70
$ Iyy definition for card reader
5-70
$ Iyy definition for CXI mode 5-64
$ Iyy definition for database
computer 5-69
$ Iyy definition for DNET/ROUT mode
5-62
$ Iyy definition for Front-End
Processors 5-62
$ Iyy definition for HYPERchannel
5-68
$ Iyy definition for magnetic tape
subsystems 5-56
$ Iyy definition for mass storage
subsystems 5-51
$ Iyy definition for Page Processing
System 5-67
$ Iyy definition for printers 5-61
$ Iyy definition for remote
maintenance console 5-49
$ Iyy definition for system control
devices 5-47
$ Iyy definition for VIDEO device
5-49
$ Iyy NOFMS statement 2-34
$ LIBRARY 5-111, 5-115, B-6, B-7,
B-14
$ LIBRARY definition 5-119
$ LOADFIL 3-9, 5-191, B-4, B-16
$ LOADFIL definition 5-72
$ MCT 3-24, 5-4, 5-24, B-3, B-18,
B-19
$ MCT definition 5-72
$ MODOPT definition 5-121
$ MPC 2-8, 5-4, B-3, B-9, B-11,
B-18
$ MPC definition 5-76
$ MPC hierarchical structure 5-78
$ MPCFIG 5-103, B-5
$ MPCFIG definition 5-79
$ OBJECT 5-79, 5-103, 5-190, 5-191
$ OBJECT definition 5-103
$ OBJECT identification block 5-103
$ OBJECT preface '5-103
$ PFILES 5-13, 5-115, B-8
$ PFILES definition 5-125
STATEMENT (cont)
$ PRINT banners 5-144
$ PUNCH 5-32
$ READIN 2-9, 2-43, 2-44, 3-9,
5-94, 5-104, B-5, B-15
$ READIN definition 5-104
$ SAVE 5-115, B-8, B-16
$ SAVE definition 5-126
$ SCFBUF 5-115, 5-117, B-7
$ SCFBUF definition 5-127
$ SCFDSP 5-115, 5-117, B-7
$ SCFDSP definition 5-128
$ SECURE definition 5-80
$ SELECT 5-150
$ SHARED 2-34, 5-29, 5-53, 5-83,
B-4
$ SHARED definition 5-83
$ SHCM definition 5-191
$ SNAP 3-10, 3-21
$ SSFILE 2-46, 5-39, 5-108, 5-129,
5-130, B-7, B-20
$ SSFILE definition 5-112
$ SSLOAD 5-112, 5-113, 5-115, B-7,
B-8, B-20
$ SSLOAD definition 5-129
$ SYID 2-44, 3-20, 5-182, B-1
$ SYID definition 5-84
$ SYSLD 5-136
$ SYSOUT 5-115, B-8, B-17
$ SYSOUT definition 5-131
$ SYSTEM 5-111, 5-115, B-6, B-7,
B-14
$ SYSTEM definition 5-131
$ TAPE 5-42
$ TAPE allocation class 5-59
$ TRACE B-1
$ TRACE definition 5-85
$ TRAINS 5-4, 5-17, B-4
$ TRAINS definition 5-88
$ UNIT 2-13, 2-14, B-4
$ UNIT definition 5-89
$ URP B-3
$ URP definition 5-90
$ USERID for console spawned jobs
5-150
$ VOPT 5-94
$ VOPT definition 5-105
$ VSET 5-94
$ VSET definition 5-106
$ XBAR 5-4, B-4, B-9, B-11, B-18,
B-19
$ XBAR definition 5-91
comments 5-2
i-59
DH18-03
STATEMENT (cont)
duplicates 5-1
HEX 5-133
invalid BCD statement 3-3
JCL examination and modification by
.MSCN1 5-159
MASK 3-9
MASK correction statement 1-2, 3-9,
3-10, 5-3, 5-133
missing 3'-3
multiple $ Iyy statements 5-63
OCTAL correction statement 1-4,
5-104, 5-133, 5-134, 5-135, 5-140,
5-191, B-8
optional fields 5-2
PATCH RUN UNIT statement 5-133
remove $ READIN 5-104
RHEX correction statement 2-8
stranger statement examination and
modification 5-160
unrecognizable 3-3
use of multiple $ IMAGE statements
5-17
STATION ID
reserving station ids
5-36
STATISTICAL COLLECTION FILE
$ ANSWER 5-6
device 5-117
on magnetic tape 2-22
on mass storage 2-22
purge-to-disk option 5-38
save dumps 5-188
SCF 2-22, 5-116, B-6, B-7
statistical collection tape
disposition at .MPOPM rollcall
5-146
time interval for writing TSRI data
5-168
STATISTICAL COLLECTION TAPE
statistical collection tape
disposition at .MPOPM rollcall
5-146
STATISTICS
define output file code for
Integrated Software statistics
4-26
FMS statistics 5-24
Integrated Software process-level
statistics 4-29
STATISTICS (cont)
Integrated Software system-level
stati~tics
4-26
print After Journal Domain
system-level statistics 4-28
print After Journal process-level
statistics 4-31
print Before Journal process-level
statistics 4-31
print Buffer Management Domain
process-level statistics 4-30
print Buffer Management Domain
system-level statistics 4-27
print Concurrency Control Domain
system-level statistics 4-28
print Global Data Management
process-level statistics 4-30
print Global Data Management
system-level statistics 4-27
print historical log domain
system-level statistics 4-28
print I-D-S/II Domain process-level
statistics 4-32
print Integrated Software statistics
at abnormal termination of process
4-25
print Integrated Software statistics
at normal termination of process
4-25
print Integrated Software statistics
for batch processes 4-32
print Integrated Software statistics
for DM-IV/TP processes 4-33
print Integrated Software statistics
for TDS processes 4-33
print Integrated Software statistics
for TS8 processes 4-34
print Integrated Sortware statistics
for workstation processes 4-33
print Protected File I/O Domain
process-level statistics 4-32
print Protected File I/O Domain
system-level statistics 4-29
report code for Integrated Software
statistics 4-26
Statistical Collection File 2-22
STATUS
can't change device status 2-34
change from removable to permanent
2-34
frequency of Time Sharing status
messages 5-171
i-60
DH18-03
STATUS (cont)
peripheral devices 5-3
prior device status 2-33
status error 3-3
SUBDISPATCH
consecutive subdispatch count
execute subdispatch processes
SWI
$ FILDEF option
5-140
5-180
SUBROUTINE LIBRARY
$ LIBRARY 5-119
SUBSYSTEM
$ Iyy for magnetic tape subsystems
5-56
$ Iyy statement for mass storage
subsystems 5-51
defining magnetic tape subsystem
5-56
loading site modified TSS subsystems
5-190
mass storage subsystem parameters
5-52
mass storage subsystem/device
initialization 5-93
maximum number of magnetic tape
units 5-59
MSU0400 5-148
MSU0402 5-148
MSU0451 5-102, 5-148
MSU0500 5-102, 5-148
MSU0500 subsystem 5-40
Peripheral Subsystem Interface (PSI)
5-76
Time Sharing Subsystem Library
5-109
SURVEY MESSAGES
MSU3380 disk device
2-16
SWAP FILE
minimum Time Sharing swap file size
5-177
number of active swap files 5-177
Time Sharing swap file growth factor
5-177
Time Sharing swap file parameters
5-177
Time Sharing swap files 5-178
USERID for permanent swap file
5-170
5-111
SWITCH
configuration panel switoh settings
5-10
EXECUTE 3-7
10M BOOTLOAD SOURCE TAPE/CARD switch
2-9, 2-10
mailbox switches 5-10
MPC switches 2-10
Network Processor CXI mode mailbox
address switches 5-65
Network Processor DNET/ROUT mode
mailbox address switches 5-65
SYBDI
$ INFO option
5-41
SYBRT
$ INFO option
5-41
SYJOS
$ INFO option
5-41
SYJOT
$ INFO option
5-41
SYMDEF
primary SYMDEF
5-190
SYOT
disable SYOT trace
5-33
SYS
$ FILDEF format option
5-111
SYS CAT
default userid 5-170
Startup Master Catalog
SYS CAT 5-125
1-3
SYS SOFTWARE
default CXI communications values
5-64, 5-66
SYS SOFTWARE 4-7, B-7
SYSOTRCVY
$ ANSWER
5-6
SYSOUT
$ INFO option
i-61
5-42
DH18-03
SISOUT (cont)
granting additional SYSOUT lines
5-26
modify/add SISOUT file B-17
recovery 2-21
sieve limit for maximum number of
SISOUT records per job 5-42
SISOUT files B-6
SYSOUT BLINK TABLE
$ INFO CLENPT 5-21
DP.SBT - SISOUT Blink Table
2-22
SISOUT COLLECTION SPACE
$ SYSOUT 5-131
SYSPN
example SYSPN JCL for SHARD and CWS
5-109
SYSTEM
$ SECURE SYSTEM option 5-81
adding new system files 2-46
assumed channel for system console
3-1
automatic restart of processes 2-6
automatic system restart 5-23
balance system files 5-109
bootload clears system tables 2-3
bootloading techniques 2-1
cold boot rebuilds system software
2-4
common resources between central
system and NPS 5-83
configuring system component B-17
deconfiguring system component B-18
defining GCOS system files 5-109
defining operating system parameters
5-19
DPS 88 2-43
DPS 90 2-43
dump of system software 2-5
dump System Master Catalog (SMC)
3-23
establish system environment 1-2
establishing GeOS system 5-107
failure 2-3, 3-8
GeOS character set 5-88
GeOS system files 5-37
GeOS system programs 1-4, 5-137
GeOS system software 2-4
hardware and software parameters
1-3
SISTEM (cont)
high-use system files 5-109
history of system operating events
5-85
identifying required system module
file 5-131
identifying system 5-84
identifying system files 5-115
identifying system libraries 5-119
installing a new system B-1
Local/Remote system initialization
(example) 5-50
loss of critical component 2-6
low-use system files 5-109
malfunction 2-47
memory available to Time Sharing
System 5-23
mixed systems 5-27
multiple systems B-1
online/offline testing 3-20
operator-initiated aborts 3-7
patching total system software tape
5-133
reconfiguration 5-91
running VIDEO on DPS 88 system 5-49
software and hardware parameters
5-3
split systems 2-12
Startup file system 3-21
system console names 5-47
system failure analysis 5-85
system files 2-32, 2-44, 5-53,
5-132, B-6
system map banner 3-20
system modules 5-131
system programs B-7
system trace 5-85
Time Sharing System copies 5-26
Time Sharing System traces 5-85
total system software tape 1-4,
2-4, 2-10, 2-45, 2-46, 5-107,
5-137, 5-138
trace types 5-86
unrecoverable system error 3-10
SYSTEM CONTROL DEVICE
$ Iyy for system control device
5-47
SYSTEM CONTROL UNIT
$ MCT 5-72
i-62
DH18-03
SYSTEM IDENTIFIER
display it 5-182
SYSTEM LIBRARY EDITOR
program/module name
SYSTEM MAP
inhibit printing
system map B-2
5-136
5-7
SYSTEM MASTER CATALOG
duplicate 2-31, 2-34, 5-20, 5-40,
B-2
inconsistency between logical device
label and SMC 2-31
password encryption 5-22
ST1 5-109
SYSTEM PATH NAME
replacement (SPN)
5-40
SYSTEM SCHEDULER
defining classes 5-129
job class parameters B-8
job class size 5-112
job classes B-7
job input saved via $ INFO SCHSAV
5-39
redefining System Scheduler
parameters B-20
restart jobs 2-21, 2-47
System Scheduler files 5-109
TAC
contact the Honeywell Bull Response
Center 5-49
SYSTEM SUBROUTINE LIBRARY
$ LIBRARY 5-119
SYSTEMMAP
$ ANSWER SYSTEMMAP/NO parameter
$ INFO option 5-42
TABLE (cont)
device allocation unit table 5-28
device name table 2-26, ~-31, 2-33
DP.JOT - Job Output Table 2-22
DP.SBT - SYSOUT Blink Table 2-22
in-memory tables 5-131
in-memory tables overwritten 5-101
Job Output Table 5-21
magnetic tape handler survey 2-35
main memory tables 1-4, 5-115
master available space table 5-145
Module Directory Table 5-134
Module Name Table 5-134
MSU0500 alternate track table 2-38
MSU0501 alternate track table 2-38
Peripheral Assignment Table (PAT)
5-180
primary trace table 5-147
print train standards 5-88
re-create tables and pointers 2-26
required pointers and tables 5-100
SD.INJ 2-21
secondary trace table 5-147
snap of disk I/O interval trace
table 2-41
SYSOUT Blink Table 5-21
temporary descriptor table (TDT)
5-29
trace table 5-85
track table 2-42
TAPDEN
$ INFO option
5-42
5-7
TABLE
$INITIALIZE recreate tables and
pointers 5-107
allocation table problems 2-25
allocation tables 5-53, 5-101
alternate track table 2-42
available space table 2-28, 5-28,
5-100
bootload clears system tables 2-3
configuration and device control
tables 5-3
defective space history table 2-38,
2-42, 5-96, 5-99
TAPE
$ Iyy for magnetic tape subsystems
5-56.
1600 bpi 5-22, 5-42, 5-57, 5-58,
5-111
200 bpi 5-22, 5-111
556 bpi 5-22, 5-111
6250 bpi 5-22, 5-42, 5-57, 5-58,
5-111
800 bpi 5-22, 5-42, 5-57, 5-58,
5-111
cold boot 2-4
default densities 5-22
density 5-58
density of firmware tape 5-105
i-63
DH18-03
TAPE (cont)
device type codes 5~59
Extract Card Images from AUTOLOAD
File {XCAF} 2-12
FIPS-79 UFAS tape label 5-33
firmware 5-95
firmware tape B-5
Generalized Tape Management System
5-24
handler released 2-35
influencing the order of magnetic
tape allocation 5-57
initial configuration B-11
initiating boot load 2-10
installing the IFAD tape 5-13
magnetic tape allocation class 5-58
magnetic tape density code 5-57
magnetic tape disposition at .MPOPM
rollcall 5-146
magnetic tape logical device name
5-57
magnetic tape unit identification
number 5-57
maximum number of magnetic tape
units 5-59
modifying content of site-specific
boot tape 2-12
MPC firmware tape 2-4
MTS0400/0500 nine-track 5-56
MTS0400/0500 seven-track 5-56
MTS0500 nine-track 5-56
MTS0600 nine-track 5-56
MTS0610 nine-track 5-56
MTS0610 seven-track 5-56
MTs8200 nine track 5-56
patching total system software tape
5-133
Read Startup Boot Tape (RSBT) 2-12
releasing a configured tape at
Startup 5-59
replacing section of Startup job
stream 2-10
reserving a tape unit 5-59
SCF 2-22
sieve limit for mag tape files 5-39
site-customized boot tape 2-1
site-specific boot tape 2-1, 2-4
specifying density capabilities
5-42
statistical collection tape
disposition at .MPOPM rollcall
5-146
TAPE (cont)
tape handler survey 1-3, 2-26,
2-35, 5-93
tape label verification 5-111
total system software tape 1-4,
2-4, 2-10, 2-45, 2-46, 5-107,
5-137, 5-138, 5-190
verify 7 or 9 track type 2-35
verify density 2-35
Write Startup Boot Tape (WSBT) 2-12
TAPE DENSITY
1600 bpi 5-22, 5-42, 5-111
200 bpi 5-22, 5-111
556 bpi 5-22, 5-111
6250 bpi 5-22, 5-42, 5-111
800 bpi 5-22, 5-42, 5-111
default high and low densities
default high density 5-105
5-22
TAPE MANAGEMENT SYSTEM
GTMS 5-127, B-7
TAPE/CARD SWITCH
10M BOOTLOAD SOURCE TAPE/CARD switch
2-9
TARGET PAGE FAULT RATE
site-option patch 5-152
TDS
assigning class B priority 5-143
memory available to Transaction
Driven System 5-23
print Integrated Software statistics
for TDS processes 4-33
TDS class B priority 5-142
TDT
temporary descriptor table
5-29
TEMPORARY DESCRIPTOR TABLE
$ INFO NIAST 5-29
TERMINAL
dumps from VIP maintenance terminal
3-12
Front-end Network Processor 5-49
maximum number of keyboard-display
terminals 5-167
maximum number of terminals 5-168
terminal disconnects 5-175
i-64
DH18-03,.
TERMINATION
Integrated Software 4-37
Integrated Software Termination
domain 4-1
print Integrated Software statistics
at abnormal termination of process
4-25
print Integrated Software statistics
at normal termination of process
4-25
TEST
online/offline system testing 3-20
test MPC 2-29, 2-30
TEST PACK Innnnn? question 2-40
TEXT
TEXT
2-14
THRESHOLD
catalog area threshold 5-23
free-chain low threshold 5-25
space descriptor threshold 5-23
space threshold 5-23
TIME
$ ANSWER 5-6
$ ANSWER example 5-9
date and time of bootload 1-2
deferred processing time limit
5-175
single job processor time sieve
limit 5-40
site-option patch for DRL TASK
maximum processor time 5-167
time interval for TSRI data issue to
SCF 5-168
time interval for writing Time
Sharing accounting data 5-168
time zones 5-42
TSS subsystem processor time limit
5-176
TIME SHARING
$INFO section of Time Sharing
initialization file 5-189
accounting 5-184
additional PAT space for Time
Sharing 5-180
assigning class B priority 5-143
automatic restart 2-6
dispatching time slice 5-180
enable TSS measurement record 5-176
TIME SHARING (cont)
frequency of status messages 5-171
initialization file 5-189
loading site modified TSS subsystems
5-190
memory allocated to Time Sharing
5-172, 5-183
memory available 5-23
memory reserved for urgent jobs
5-174
minimum memory size when lightly
loaded 5-172
modify the Time Sharing System
5-189
multicopy 5-143, 5-180
multicopy Time Sharing class B
priority 5-181
number of copies 5-26
percentage of Time Sharing System
memory in use 5-183
processors 5-180
program logic error processing and
recovery 5-179
restart 5-19
restart which copy 5-19
site-option patches 5-167
subsystem memory limit 5-176
subsystem processor time limit
5-176
.swap file parameters 5-177
time interval for writing Time
Sharing accounting data 5-168
Time Sharing initialization 5-189
TimeSharing logon message 5-182
Time Sharing Subsystem Library
5-109
Time Sharing System 5-130
Time Sharing System Executive 5-189
trace 5-85
TSS class B priority 5-142
TIMEZ
$ INFO option
5-42
TOLTS
to boot load MPC 2-29
TOLTS 5-12, 5-104
TOTAL SYSTEM SOFTWARE TAPE
$EDIT section 5-107
$LOAD section 5-190
-EDIT? question 2-45
bootload 2-10
i-65
DH18-03
TOTAL SYSTEM SOFTWARE TAPE (cont)
cold boot 2-4
partial edit 2-46'
patches 5-138
patching TSST 5-133
patching via PAED 5-137
TOTAL SYSTEM TAPE
$LOAD section 1-4
total system software 'tape
TRACK (cont)
track table 2-42
verify tape 7 or 9 track type
TRAIN
loading
2-35
2-6
TRANSACTION DRIVEN SYSTEM
memory available 5-23
1-4
TP8
TP8 Command Executive domain
4-1
TPS
automatic restart 2-6
class B priority 5-142
Transaction Processing System
restart 5-19
TRANSFER REGISTER
transfer register
TRACE
activating system trace entries
5~85
buffer size for Integrated Software
trace 4-24
bypass the trace routine 5-85
disable SYOT trace 5-33
enabling GEOT trace 5-24
Integrated Software Trace and Load
Map Display domain 4-1
Integrated Software Trace domain
4-1
OFF or ON 5-85
Protected File I/O domain internal
trace 4-24
Session Control internal trace 4-24
Tenant Management internal trace
4-24
Time Sharing System traces 5-85
trace types 5-85, 5-86
Workstation Management internal
trace 4-24
TRACE TABLE
primary trace table 5-147
secondary trace table 5-147
snap of disk I/O interval trace
table 2-41
TRACK
alternate track table 2-42
MSU0500 alternate track table
MSU0501 alternate track table
TRANSACTION PROCESSING SYSTEM
automatic restart 2-6
restart 5-19
Transaction Processing Applications
Programs 5-130
3-21
TS8
$ INFO option 5-43
configuration 5-26
print Integrated Software statistics
for Ts8 processes 4-34
TSRI
time interval for TSRI data issue to
SCF 5-168
TSS
automatic restart 2-6
class B priority 5-142
loading site modified TSS subsystems
5-190
TSS CONVER 4-7
TSS SIZE console entry 5-172
TSST
total system software tape
2-4, 2-10, 2-45, 2-46
TVIM
TVIM program
1-4,
2-26, 2-36, 5-17
TY1-TY4
logical device names
5-47
TY5
assign TY5 to CSU6001, CSU6601, or
csu6602 for VIDEO 5-49
2-38
2-38
UFAS
FIPS-79 UFAS tape label
1-66
5-33
DH18-03
UMC
system path name replacement
UNANE
console verb
UNCP
$ Iyy UNCP
5-40
5-47
5-64
UNDED
console verb
5-46
UNIT RECORD
defining Unit Record Processor
URP800n 5-90
initial configuration B-12
survey of devices 1-3
URGENCY
for DRL TASK job 5-169
job urgency 5-140
site-option patch for job urgency
5-151
Time Sharing memory reserved for
urgent jobs 5-174
URP0600
URP0600
5-90
URP800N
defining Unit Record Processor
URP800n 5-90
URP800n B-3
USERID
modifying $ USERID for After Journal
4-9
modifying $ USERID for Checkpoint
Journaling 4-12
USERID image for console spawned
jobs 5-150
USE RID image of select file for
spawned jobs 5-150
USRDMP
$ INFO option
5-44
VERB
ABORT SHARD console verb 4-37
ACCEPT console verb 5-116
APRIOR console verb 5-142
ASGN console verb 5-55
ASGNP console verb 5-22
VERB (cont)
BOOT console verb 3-7, 3-9, 5-1,
B-18
DEDCAT console verb 5-46
DUMP console verb 3-7, B-18
ENABLE console verb 5-50
EXCHG console verb 5-56
IGNORE console verb 5-116
MOVE console verb 5-50
NAME console verb 5-47
PSTATS console verb 5-55
RELINQUISH console verb 5-50
RLSE console verb 5-46, 5-55, B-18
RLSEP console verb 3-20
RUN REST console verb 2-21
SPAWN SHARD console verb 4-3
UNAME console verb 5-47
UNDED console verb 5-46
VERIFICATION
all permanent mass storage devices
1-3, 2-32
discrepencies during mass storage
device verification 2-37
MPC firmware 2-30
MPC verification and bootloading
2-25
pack serial number 2-31
permanent mass storage device
verification 2-26, 2-31
reel serial number 2-45
retry 2-32
SMCDUP device and option
verification 2-31
ST1 and SMCDUP device name
verification 2-31
tape 7 or 9 track type 2-35
tape density 2-35
tape label verification 5-111
VERTICAL FORMAT
vertical format control
5-17
VFC
load VFC image 2-26, 2-36
VFC 5-17
VFC images 5-93
. VIDEO
$ Iyy for VIDEO device 5-49
assign TY5 to CSU6001, CSU6601, or
CSU6602 for VIDEO 5-49
Front-end Network Processor 5-49
i-67
DH18-03
VIDEO (cont)
running VIDEO on DPS 88 system 5-49
running VIDEO with Console Manager
5-49
VIDEO program 5-47
VIP
dumps from VIP maintenance terminal
3-12
VIRTUAL MEMORY
default allocation for Integrated
Software 4;;.38
default VSPACE value for Integrated
Software 4-4
Integrated Software 4-38
VOLUME SET
AU size 5-101
definition 2-25
devices must be RMVBL
5-53
VSPACE
default VSPACE value for Integrated
Software 4-4
VSPACE 4-38
WARM BOOT
expedite warm and fast boots via $
ANSWER 5-5
warm boot 2-2, 2-4
with GCOS functioning in main memory
2-5
WIRED (cont)
formula for minimum wired realmemory page requirements for
Integrated Software 4-39
Integrated Software wired pages
4-23, 4-38
message reports maximum wired pages
for Integrated Software 4-2
WORKSTATION
Automatic Workstation Enable domain
4-1
print Integrated Software statistics
for workstation processes 4-33
workstation definition data base
(WD) file 5-64, 5-66
workstation definition data base
pathname 4-34
WORKSTATION MANAGEMENT
domain 4-1
internal trace 4-24
WSBT
Write Startup Boot Tape (WSBT)
WSSIZE
$ INFO option
2-12
5-45
XCAF
Extract Card Images from AUTOLOAD
File (XCAF) 2-12
WARNING
SDLD error and warning messages
4-57
.
WD FILE
workstation definition data base
(WD) file 5-64, 5-66
WINDOW DELIMITER
process workspace page fault window
delimiter 5-25
shared workspace page fault window
delimiter 5-26
WIRED
examples of wired real memory page
requi~ements
4-42
i-68
DH18-03
HONEYWELL BULL
Technical Publications Remarks Form
TITLE
LARGE SYSTEMS
Geos 8 OS SYSTEM STARTUP
ORDER NO.
DATED
IL....D_H_l_8_-0_3_ _ _ __
IAUGUST 1987
ERRORS IN PUBLICATION
SUGGESTIONS FOR IMPROVEMENT TO PUBLICATION
Your comments will be investigated by appropriate technical personnel
and action will be taken as required. Receipt of all forms will be
acknowledged; however. If you require a detailed reply. check here.
0
PLEASE FILL IN COMPLETE
ADDRESS BELOW.
FROM: NAME ___________________________________________
TITLE _______________________________________
COMPANY _______________________________________
ADDRESS _____________________________________
DATE __________
c
PLEASE FOLD AND TAPENOTE: U.S. Postal Service will not deliver stapled forms
II
NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES
BUSINESS REPLY MAIL
FIRST CLASS
PERMIT NO. 39531
WALTHAM, MA
POSTAGE WILL BE PAID BY ADDRESSEE
Honeywell Bull Inc.
200 Smith Street MS486
P.O. Box 9199
Waltham, Massachusetts, 02254-9832
111 ••••• 1.1 •• 1.1.1.1 •• 1•• 11.1 •• 1•• 1••• 11 ••• 1.1.1.1.1
Hone~ell Bull
Hon~eUBull
Corpo.... Headquarte..:
3800 West BOth St., Minneapolis, MN 55431
U.S.A.: 200 Smith St., MS486, Waltham, MA02154
Cenada: 155 Gordon Baker Rd., North York, ON M2H 3P9
Mexico: Av. Constituyentes 900, 11950 Mexico, D.F. Mexico
U.K.: Great West Rd., Brentford, Middlesex TWa 9DH Italy: 32 Via Pirelli, 20124 Milano
Australia: 124 Walker St.. North Sydney, N.S.W. 2060 S.E. A8ia: Mandarin Plaza, Tsimshatsui East, H.K.
49660, 7.5C1087, Printed in U.S.A.
DH18-03
Large Systems
/
/
,,"'"'
/
//
, '<:"
t
.'~,
"
~,
. If'
I
~_"
',.
GCOS80S
System Operator Messages
HoneMell Bull
LARGE SYSTEMS
GCOS80S
SYSTEM OPERATOR MESSAGES
SUBJECT
System Console Conventions, and Operator Input and System Output Messages
SPECIAL INSTRUCTIONS
This document supersedes the previous edition, DH13-03, dated December 1985.
Refer to the Software Release Bulletin (SRB) for this product release for a synopsis of technical changes.
SOFTWARE SUPPORTED
GeOS 8 OS Software Release 3000
ORDER NUMBER
DH13-04
September 1987
Hone:Mell Bull
PREFACE
This manual contains the operator input and system output messages that apply
to the system console. It also contains supporting material necessary in
interpreting many of the messages.
Due to changes in Honeywell Bull support policies, the terms nfield engineer n ,
nfield engineering", "Honeywell representative", etc., used in this manual
refer to the "Honeywell Bull Response Center".
All material contained in this manual is applicable to all Honeywell Bull large
systems.
Section 1 contains introductory matter.
Section 2 contains INPUT messages arranged in alphabetical order.
Sections 3-27 contain OUTPUT messages arranged in alphabetical order.
Messages contained herein include the actual message line as given at the
console, a description, comments regarding conditions pertinent to message
issuance, and recommended operator action.
The information and specifications in this document are subject to change
without notice.
Consult your Honeywell Bull Marketing Representative for
product or service availability.
Copyright
(2)
Honeywell Bull Inc., 1985, 1987
File No.: 1V13
DH13-04
In this document, multiple vertical braces and brackets should be assumed to be
a single brace or bracket; for example:
{
{
{
}
}
}
represent
{}
and
[
[
[
]
]
]
represent
[ ]
CORRECTING MANUALS VIA PASS
Required corrections to this version of the manual will be
entered on the Problem Analysis Solution System (PASS) data
base. Query PASS periodically via the procedures described
in the Problem Analysis Solution System (PASS) manual, Order
Number DW95. Corrections documented on PASS, if applicable
to the next release of the software, will be incorporated
into the next update of the manual.
iii
DH13-04
LISTING OF MANUALS
A list of large system software manuals is available to all Honeywell Bull
users with access to an ASCII terminal. The manuals list is updated regularly
to facilitate the ordering of manuals. Manual ordering instructions are
printed on the listing. Use the following instructions to obtain a listing.
1. Dial the appropriate telephone number to connect your terminal to the
Multics system in Phoenix.
300-baud &
1200-baud
(602) 249-5356
249-6430
150-baud
249-7554
Multics will respond with a computer system identification banner.
2. Enter the login command "login Sam" (without the quote marks).
carriage return key.
Press the
Multics will respond with a request for the password.
3. Enter the password "Multics" (without the quote marks) and press the
carriage return key.
Multics will respond with a welcome message followed by a ready message.
Example:
Welcome to the Multics system
For services available online type:
:list
r1111.7 Thu
(ready message)
4. Enter ":list" (without the quote marks) to obtain a list of commands.
Press the carriage return key.
Multics will list the commands available for specific topics and then
display the ready message.
5. Enter the command selected and press the carriage return key.
6. Enter "logout" (without the quote marks) and press the carriage return
key to log off the Multics system.
Multics will respond with a logout message.
iv
DH13-04
CONTENTS
Page
SECTION 1 INTRODUCTION ••••••••••••••••••••••••••••••••••••••••••••••
1-1
Device Types •••••••••••••••••••••••••••••••••••••••••••••••••••••••••
1-2
Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2
Standard Abbreviations •••••••••••••••••••••••••••••••••••••••••••••••
1-3
SECTION 2 OPERATOR INPUT MESSAGES •••••••••••••••••••••••••••••••••••
2-1
System Verbs.........................................................
2-2
Remote Maintenance Console Verbs •••••••••••••••••••••••••••••••••••••
Console Verbs Limitations ••••••••••••••••••••••••••••••••••••••••••
2-3
2-3
SECTION 3 GENERAL INFORMATION ON OUTPUT MESSAGES ••••••••••••••••••••
3-1
Messages Of Record •••••••••••••••••••••••••••••••••••••••••••••••••••
Peripheral Device And 10M Messages •••••••••••••••••••••••••••••••••••
3-1
3-2
SECTION 4 OUTPUT MESSAGES BEGINNING WITH THE LETTER A•••••••••••••••
4-1
SECTION 5 OUTPUT MESSAGES BEGINNING WITH THE LETTER B•••••••••••••••
5-1
SECTION 6 OUTPUT MESSAGES BEGINNING WITH THE LETTER C•••••••••••••••
6-1
SECTION 7 OUTPUT MESSAGES BEGINNING WITH THE LETTER D•••••••••••••••
7-1
SECTION 8 OUTPUT MESSAGES BEGINNING WITH THE LETTF.F
8-1
F., (
< •
,. •
•
•
•
•
•
•
• •
•
SECTION 9 OUTPUT MESSAGES BEGINNING WITH THE LETTER F •••••••••••••••
9-1
SECTION 10 OUTPUT MESSAGES BEGINNING WITH THE LETTER G•••••••••••••• 10-1
SECTION 11
OUTPUT MESSAGES BEGINNING WITH THE LETTER H•••••••••••••• 11-1
SECTION 12 OUTPUT MESSAGES BEGINNING WITH THE LETTER I •••••••••••••• 12-1
SECTION 13 OUTPUT MESSAGES BEGINNING WITH THE LETTER
J ••••••••••••••
13-1
SECTION 14 OUTPUT MESSAGES BEGINNING WITH THE LETTER K•••••••••••••• 14-1
SECTION 15
OUTPUT MESSAGES BEGINNING WITH THE LETTER L•••••••••••••• 15-1
SECTION 16 OUTPUT MESSAGES BEGINNING WITH THE LETTER M•••••••••••••• 16-1
SECTION 17
OUTPUT MESSAGES BEGINNING WITH THE LETTER N•••••••••••••• 17-1
v
DH13-04
CONTENTS (CONT)
Page
SECTION 18 OUTPUT MESSAGES BEGINNING WITH THE LETTER 0 •••••••••••••• 18-1
SECTION 19 OUTPUT MESSAGES BEGINNING WITH THE LETTER P •••••••••••••• 19-1
SECTION 20 OUTPUT MESSAGES BEGINNING WITH THE LETTER Q•••••••••••••• 20-1
SECTION 21
OUTPUT MESSAGES BEGINNING WITH THE LETTER R•••••••••••••• 21-1
SECTION 22 OUTPUT MESSAGES BEGINNING WITH THE LETTER S •••••••••••••• 22-1
SECTION 23 OUTPUT MESSAGES BEGINNING WITH THE LETTER T•••••••••••••• 23-1
SECTION 24
OUTPUT MESSAGES BEGINNING WITH THE LETTER U•••••••••••••• 24-1
SECTION 25
OUTPUT MESSAGES BEGINNING WITH THE LETTER V•••••••••••••• 25-1
SECTION 26
OUTPUT MESSAGES BEGINNING WITH THE LETTER W•••••••••••••• 26-1
SECTION 27
OUTPUT MESSAGES BEGINNING WITH THE LETTERS X, y, Z..••... 27-1
APPENDIX A PERIPHERAL INSTRUCTION CODES •••••••••••••••••••••••••••••
A-1
APPENDIX B MPC STATUS CODES (OCTAL) ••••••••••••••.••••••••••••••••••
B-1
Major Status Code - MPC Device Attention, Code 12 ••••••••••••••••••••
Major Status Code - MPC Device Data Alert, Code 13 •••••••••••••••••••
Major Status Code - MPC Command Reject, Code 15 ••••••••••••••••••••••
B-1
B-1
B-2
APPENDIX C DEVICE TyPES •••••••••••••••••••••••••••••••••••••••••••••
C-1
APPENDIX D PERIPHERAL OCTAL SUBSTATUS CODES •••••••••••••••••••••••••
D-1
INDEX ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
i-1
ILLUSTRATIONS
Page
Figure
2-1
CARCL Syntactical Displays •••••••••••••••••••••••••••••••••••••
vi
2-23
DH13-03
~
SECTION 1
INTRODUCTION
This manual is provided as an operating aid for console operators and for
programmers of Honeywell Bull Large Information Processing Systems.
Messages are generated on the system console to inform the operator of one of
the following conditions.
1. The system has performed some action of which the operator should be
aware.
2. A specific action is to be performed by the operator to allow further
processing. (Refer to the GeOS 8 OS System Startup manual.)
Every message that can appear on the system console while operating in a GeOS 8
-environment is included; although it is possible that, at a particular site,
some of the messages may never occur.
Three types of messages are produced at the console.
o
Operator input to the system
o
System output messages for information only
o
System output messages requiring operator action
Section 2 contains descriptions of operator input messages and possible system
replies. Section 3 presents general information concerning conventions
followed in the construction and formatting of output messages. The output
messages, contained in alphabetical order, beginning with Section 4 through 27.
When a message begins with a variable (job sequence number, device name, etc.),
the message is sequenced according to the first fixed element of the message.
1-1
DH13-04
Messages are output at the console in accordance with the following
conventions.
o All messages from the system are displayed in uppercase characters on all
consoles including CRrs. Operator input is in uppercase on the CRT
consoles and in lowercase on all others.
o The maximum line length is 80 characters.
o Most output messages that require a response from the operator terminate
without a carriage return. This allows the response to appear on the
same line as the original message.
DEVICE TYPES
Descriptions of the device types as coded in several system messages are listed
in Appendix C.
VARIABLES
Variable values for both operator input and system output messages are shown in
the messages as lowercase alphabetic characters. Nonstandard variable
designators are defined in the explanation of the applicable message. Standard
variable designators are defined in the following list and are not defined with
individual messages.
Abbreviation
Meaning
aa
ccc or cc
dd
dd
fc
Activity Number
Channel (PUB) Number
Device Number
Day
File Code
Input/output controller number
Identification
Month
Reel Number
Job Sequence Number (SNUMB)
Station Identification
Time in Hours and Minutes
Time in Hours and Thousandths of an Hour
Time in Thousandths of an Hour
Time in Hours and Hundredths of an Hour
Job Urgency
Alternate iccdd
Year
Front-End Network Processor Number
i
id
mm
rrrr or rrrrr
sssss
sid
tt:tt
tt.ttt
ttt
ttt,t.tt, or tt.tt
uuu
xyyzz
yy
FNP-n
1-2
DH13-04
STANDARD ABBREVIATIONS
The following abbreviations are used in various messages throughout the manual.
Abbreviation
Meaning
ATT
BSY
Attention Major Status
Channel Busy Major Status
Channel
Character Interface Unit
Card Punch
Card Reader
Deleted
Dismount
Disk Pack Subsystem
Disk Subsystem
File Management Supervisor
For Your Information
Input/Output Multiplexer: includes (i.e., IMX,
IHO, 10M, lOX, lOP, CBU, CAUl
Input/Output Supervisor
Known Process Index
Data Alert Major Status
Mount
Magnetic Tape Subsystem
Card Punch
Printer Subsystem
Processor
Print Train Sector Loader
Peripheral Unit Buffer
Ready
System Control Center
System Configuration Table
Transaction Processing Application Program
Transaction Processing Executive
Time Sharing System
Console
CH
CIU
CP
CR
DLT
DMI'
DP
DS
FMS
FYI
10M
lOS
KPX
LRT
MNT
MI'
PN
/
PR
PRC
PRLC
PUB
RDY
SCC
SeT
TPAP
TPE
TSS
TY
1-3
DH13-04
SECTION 2
OPERATOR INPUT MESSAGES
Operator input messages to the system are initiated by pressing the request
button on the console. The system replies with three question marks (111),
after which one of the messages described in this section may be entered.
The one-character optional operator replies to system initiated messages are
preceded by a single question mark. The option is to be entered without a
space before the entry. These system messages will be repeated every 30
seconds until a reply is made.
The procedure for operator reply and input is as follows:
1. Once the operator has initiated a request or the system has issued a
message requiring a response, a programmed READ command is issued to the
console and the keyboard is enabled.
2. The operator enters the input verb or required response, then presses the
end-of-message button. The console is then disabled for operator input.
3. To correct an incorrect input to the console before pressing the
end-of-message button, the operator presses the operator error button,
then enters the correct response, followed by an end-of-message.
If the operator presses end-of-message before detecting an incorrect reply and
the reply is acceptable to the system, it will be interpreted by the system as
being a valid response.
NOTES: 1. The request button on the CSU6001/6002 consoles is labeled REQ. The
request function on the CSU6601 console is the carriage return key.
2. The end-of-message button on the CSU6001/6002 consoles is labeled
EOM. The end-of-message function on the CSU6601 console is the
carriage return key.
3. The operator error button on the CSU6601/6602 consoles is labeled OPR
ERR. The operator error function on the CSU6601 console is enabled
by pressing Control X.
2-1
DH13-04
SYSTEM VERBS
A significant element of each Input Message is the VERB. This verb can be
modified by certain "arguments", "control fields", and "options". A list which
contains current system verbs as well as those that have been recently replaced
is as follows:
ABORT
ACALL
ACCEPT
ACCNT
ACHNL
ACSTAT
ADDVL
APRIOR
ASGN
ASGNC
ASGNI
ASGNP
AUDIT
BOOT
BPRIOR
CANCL
CHANGE
CHANGF
COpy
CSTATS
DATE
DCHNL
DDT APE
DEDCAT
DELETE
DELEVL
DLINK
DUMP
DUPBAD
DUPER
ECOL
ELAN
ESTATS
EXCHG
FASTBT
FMS
GENSYS
GRANT
HAPS
HIST
HISTRE
HOLD
IDE NT
IGNORE
IMCV
IMCV7
IMCV9
LOOK
LSTAL
LSTCR
LSTCT
LSTPR
LSTQ
LSTRT
MASFG
MC
MOVE
MSG
MVALL
NAME
NCALL
NOI
NOPRO
JCHGCY
JCLASS
JCLGEN
JDELCY
JEND
JLIST
JLSTCY
JORDER
JOUST
'JPURGE
JRERUN
JRUN
JSCHED
JSTRT
PPS
PSTATS
PTRAIN
PURGE
LAUTO
LDTAPE
LIMIT
LINES
LIST
LISVL
LISVS
LKRMl'
LKSAC
SECUR
SNAP
SNUMB
SPAWN
SRM
SSA
STATS
REDRC
REMOV
REPRO
RLSE
RLSEC
RLSEI
RLSEP
RMl'ST
RUN
2-2
STMPVL
SYSOP
SYSOUT
TAPFG
TCALL
TCLASS
TEST
TIME
TOGCOL
TP
TRACE
TSS
TS8
TYPFG
UDTAPE
ULSAC
UNAME
UNDED
UNJOUT
URGC
VFC
VIDEO
VOCAB
VOCABU
VOID
WORKST
DH13-04
REIIlTE MAINTBNANCE CORSOLE VERBS
A designated remote maintenance console is restricted to the use of only the
following verbs. All other verbs in this section are limited to the ftlocal ft
console.
CSTATS
DLIN!{
ESTATS
HIST
JLIST
LINES
LIST
LOOK
LSTCR
LSTCT
LSTPR
LSTQ
LSTRE
LSTRT
LSTWT
MASFG
SNUMB
STATS
SYSOUT
TAPFG
TEST
TYPFG
VOCAB
VOCABU
All other console verbs entered from a remote console channel will be rejected
with the message:
DOES NOT APPLY TO THE SYSTEM REMOTE MAINTENANCE CONSOLE
The remote console may use the restricted verbs (other than the above) after
the local console issues the IRELinquish verb. The IREL verb is described in
this section.
Console Verbs Limitations
'\
/
A number of console verbs related to remote maintenance which are intercepted
by and responded to the console channel adapter. These verbs all begin with
the pound sign (I) character, are found in the Operator Input Message, and are
listed alphabetically by the first character following the I sign. All
operator output messages relative to remote maintenance input messages are
prefixed and appended with the same I sign in order to distinguish them from
GCOS messages. These verbs are not seen by GCOS and are not valid on either
DPS 88 or DPS 90 systems.
~
'\
;/
2-3
DH13-04
A
A
INPUT MESSAGES
INPUT MESSAGES
ABORT
(
aaaaa option
GPOP Message. Operator requests that a specific job be terminated, in
accordance with the specific option specified. The "option" entry can be one
of the following.
Option
Meaning
DUMP or D
Produce a slave dump, regardless of user-specified options.
The dump will not be made if the job is waiting for memory in
a new activity.
NODUMP or ND
No dump required
NOSYOT or NS
No dump required and no SYSOUT to be produced.
SCHED or S
Release job from System Scheduler. If the job was already
executed and has a finished or save status, or if job is
already in execution, it will not be terminated.
iccdd
The input/output controller, channel, and device numbers are
entered to terminate a particular IMCV job. This option is
valid only if the sssss entry is $IMCV.
~
(
Produce a slave dump according to the option specified on the
$ EXECUTE statement.
TYPE2 or T2
Abort a job even if it is executing in a TYPE-2 critical
section. This option may be used only in extreme cases, as it
may cause GCOS crashes or process disasters.
NOTES: 1. Use tpe verb PPS TERM when aborting the Page Processing System.
2. If the sssss value is $IMCV, the only option available is iccdd.
For ABORT $IMCV iccdd, the following error messages are possible:
ILLEGAL 10M I i
ILLEGAL CHANNEL I cc
NO SET FOR iccdd
ILLEGAL DEVICE I dd
iccdd NOT IMCVs
$IMCV NOT KNOWN
3. If sssss is blank, a tutorial message is issued.
(
2-4
DH13-04
A
A
INPUT MESSAGES
INPUT MESSAGES
System Replies Possible:
Slsssss NOT IN QUEUE
SYSTEM IS BUSY, PLEASE RETRY
.ABT sssss-aa tt.ttt OPER REQ ABORT
{ NO DUMP }
}
{ DUMP
{blank
}
.DLT Slsssss (X1)
INVALID SNUMB
ILLEGAL OPTION
sssss NOT FOUND
sssss IS SHARED SOFTWARE - CAN'T T2
Also, refer to verb NOPRO.
ACALL
{FNP-n}
{ blank }
'\
n - FNP number (0-7)
GPOP Message. Operator requests that previous NCALL or TCALL entries be
cancelled and that Front-end Network Processor (FNP) n start accepting calls.
If FNP-n is not specified, all processors configured are affected.
System Replies Possible:
FNP NOT AVAILABLE
BMX BUSY, TRY AGAIN
{A}
CORRECT FORM OF REQUEST IS "{H} CALL FHP-#
I CANT ASGN - xxxxxx ERROR IN BLDG TABLE
xxxxxx - Error condition as follows:
NOTNPS - The pack label and the SCT do not agree that the device is an
NPS-shared device.
SEEKAD - An invalid seek address was generated during available space
table initialization.
STATUS - An input/output error was encountered.
CHKSUM - A bad checksum occurred on either the pack label or the
device's available space table.
TBLSIZ - The amount of memory reserved for the available space table
was inadequate; normally because the pack allocation unit
size was smaller than the size defined on the $ 10M
statement.
NSTRUC - A non-structured pack is mounted on a spindle configured as
permanent.
2-11
DH13-04
;\#4# " Pl!Q&; &#£44 ,':;;£\$ ;. .m 4,
:~4t
,Mil. ;,.,
,.,,£1 ffi
A
INPUT MESSAGES
A
INPUT MESSAGES
(
ASTIM - The available space table image on a device has a bad
checksum. A secondary initialization is required.
The -INIT option will be denied and the device left released if any temporary
space is currently in use on the device. In this case, the following console
message is issued:
POP2>{ xxx }CAN'T 2ND INIT, BUSY TEMP FILES
{iccdd}
xxx = device name
In a NIAST or CFF environment, the following console message indicates ALCD has
denied the request because temporary space descriptors are present in the
Temporary Descriptor Table (TDT):
POP2>{ xxx }CAN'T ASGN- BZ TMP ERR IN BLDG TABLE
{iccdd}
xxx = device name
(
Additional console messages that may be issued are as follows:
POP2>{ xxx } option - INVALID OPTION
{iccdd}
where:
xxx
option
= device name
= invalid option
entry (i.e., misspelled -INIT)
If the device being assigned is an MTS500, MTU0400/MTU0500, or MTU0600, this
entry results in the device density capability being obtained from the drive
via a REQUEST DEVICE STATUS command (50 - octal). If the density capability
cannot be obtained, the tape drive is not assigned and one of the following
messages is displayed.
INOP - TAPE DEVICE IS INOPERABLE
iccdd DEN MISMATCH - DEV RLSD
DEV I INVLD
(
2-12
DH13-04
A
INPUT MESSAGES
A
INPUT MESSAGES
If the tape drive is configured but not physically connected to the MPC,
powered off, or has channel/lOP errors, the following message will be
displayed.
POP2) xxxxxx CAN'T ASGN-DEVICE INOPERABLE S=ssssssssssss
where xxxxxx is the device address/name and ssssssssssss is
the status of the device returned via a REQS command.
ASGNC nnnnn bbbbb
GPOP Message. The operator requests the assignment of memory space to GCOS
from TOLTS or memory previously released by the operator.
nnnnn - Starting address (modulo-1000 octal and must be even)
bbbbb - Number of 512 decimal word (1000 octal must be even) blocks to be
released
System Replies Possible: If the memory-assign mechanism is busy at the time of
the request, the following message is printed:
RE ASGNC BUSY --TRY AGAIN
If each of the variable fields (nnnnn bbbbb) is not followed by a blank, the
following message is printed:
RE ASGNC INVALID FORM
2-13
DH13-04
A
A
INPUT MESSAGES
INPUT MESSAGES
If either of the variable fields is an odd number, the following message is
printed:
HE ASGNC INVALID-MUST BE EVEN
If any of the variables (nnnnn bbbbb) are not octal digits, the following
message is printed:
HE ASGNC INVALID-MUST BE OCTAL
If the last block of memory described in a ASGNC request is outside of
configured memory, the following message is printed:
RE ASGNC INVALID-NOT CONFIGURED
If the above error conditions are passed, an attempt is made to satisfy the
request. Regardless of the success of the attempt, the system will print to
the console the same formatted data given by the ASGNC LIST verb to indicate
which portion of the request was satisfied.
When pages have been given to memory test program and is not returned the
following message is printed:
POP3-ASGNC REQUEST CONTAINED MAINTENANCE PAGES
When pages are not available to the operating system the following message is
printed:
POP3-ASGNC REQUEST CONTAINED NON-EXISTENT PAGES
nnnnn - Non-existent pages. The ASGNC request contains pages not
configured during Startup
ASGIC LIST
GPOP Message. This verb allows the operator to determine which areas of memory
have been released.
System Replies Possible:
RE RLSEC - JOB CAN'T SWAP
HE RLSEC - SWAP IN PROGRESS
RE RLSEC - WS 11 PAGE IN RANGE
2-14
DH13-04
A
A
IRPUT MESSAGES
IRPUT MESSAGES
(followed by)
RLSEC LIST
(HCM) 00000 Oxxxx
RLSEC xxxxx xxxxx
"n
"
"
"
"
RLSEC LIST -CONTINUEDRLSEC xxxxx xxxxx
where:
JOB CAN'T SWAP - This memory area belongs to a job that cannot swap.
This may be a temporary condition.
SWAP IN PROGRESS - This memory area is currently occupied by a program and
an unsatisfied RLSEC request is waiting for this
program to swap out so that release processing can
continue.
WS 11 PAGE IN RANGE - Indicates this memory page belongs to Working Space
Quarter 11 (HCM, I/O buffer, hardware parameter stack,
etc.) and cannot swap. This may be a temporary
condition.
xxxxx - Memory address (modulo-512 decimal)
(HCM) - Memory is in use by GCOS
RLSEC - Released memory range
ASGII n
n - 0, 1, 2, or 3
lOS Message. Operator requests logical assignment of input/output controller n
to the system.
2-15
DH13-04
A
INPUT MESSAGES
A
INPUT MESSAGES
For information concerning operator actions necessary before assigning
components to the system, refer to one of the following manuals:
GCOS 8 OS System Reconfiguration Guide For DPS go
GCOS 8 OS System Reconfiguration Guide For DPS 88
GCOS 8 os System Reconfiguration Guide For DPS 8
System Replies Possible:
is output:
.IOM n
If the request can be honored, the following message
IS ASSIGNED
If the request cannot be honored, one of the following replies is made:
CAN'T
CAN'T
CAN'T
CAN'T
ASGNP
ASGNI
ASGNI
ASGNI
ASGNI
n
n
n
n
NOT CONFIGURED (IOM n was not configured in Startup)
INPUT INVALID (10M n is not in 0--3 range)
S~IN~~~
ALREADY ACTIVE
p
GPOP Message.
Operator requests that processor be aSSigned to the system.
p - To simplify processing, the ASGNP/RLSEP console verbs may specify either
a processor number or a port number, providing no ambiguity exists
between the processor number and a port number. The ASGNP/RLSEP module
(IOS2) first examines the configuration for a port that matches the
input argument to which a processor is connected. If one is found, the
argument is assumed to be a port number. If no such port is located,
the configuration is examined for a processor number matching the
argument. If found, the argument is assumed to be a processor number.
If neither a port number nor a processor number matches the assignment,
an error response is displayed on the console.
For information concerning operator actions necessary before assigning
components to the system, refer to one of the following manuals:
GCOS 8 OS System Reconfiguration Guide For DPS go
GCOS 8 OS System Reconfiguration Guide For DPS 88
GCOS 8 os System Reconfiguration Guide For DPS 8
2-16
DH13-04
A
A
INPUT MESSAGES
INPUT MESSAGES
System Replies Possible:
will be printed:
If the request can be honored, the following message
.PROC P IS ASSIGNED
If the request cannot be honored, one of the following replies will be made:
.CANT ASGNP P -ALREADY DONE
- The processor was not released •
• CANT ASGNP P -BUSY
- The processor is unassignable or an
ASGNP/RLSEP request is being executed •
• CANT ASGNP P -INPUT INVALID
- The assign request contained an error •
• CANT ASGNP P
NOT CONFIGURED - The specified processor is not configured
in the system •
• CANT ASGNP P -REQUEST ACTIV
- Duplicate previous request outstanding •
• CANT ASGNP P -SCU IN MANUAL
- The SCU Program/Manual switch is in manual
mode •
• CANT ASGNP P -UNRESPONSIVE
- The processor does not respond to requests •
• PROC P NO RESPONSE
- The processor port is inactive; possibly
released at startup time.
ASGNP p TEST
p - Port assignment of processor to be assigned.
GPOP Message. Operator requests that a processor, which was offline, be
assigned for online testing.
NOTE:
The "TEST" request does not apply to DPS 88 processors.
Before making the ASGNP p TEST request, and ensuring that the processor power
is on, the operator must take the following steps:
1. Push the INITIALIZE/CLEAR button on that processor's configuration panel.
2. Turn on the PORT ENABLE and INITIALIZE ENABLE switches on that
2-17
processor~
DH13-04
A
INPUT MESSAGES
A
INPUT MESSAGES
3. Ensure that the processor number switches agree with the $ MCT statement.
Following the ASGNP p TEST request, dispatches of that processor will be
restricted to the T&D processor test programs.
When the online testing was completed, the processor can be restored to full
usage via the ASGNP p request, or it can be released for additional maintenance
via the RLSEP p request.
System Replies Possible:
will be output:
If the request can be honored, the following message
.PROC P IS ASSIGNED
If the request cannot be honored, one of the following replies will be made:
.CANT ASGNP P
• CANT ASGNP P
• CANT ASGNP p
-INPUT INVALID
- The assign request contained an error •
NOT CONFIGURED - The specified processor is not configured
in the system •
-REQUEST ACTIV
• PROC P NO RESPONSE
- Duplicate previous request outstanding •
- The processor port is inactive; possibly
released at startup time.
AUDIT
Statistical Collection File (SCF) Message. Provides installations with an
audit trail, maintained on the system SCF, of significant events that reflect
system status and performance (e.g., hardware malfunctions). A type 12 record
is created on the SCF.
System Replies Possible: When ready for input, • ENTER DATA is entered on the
console. The operator can then enter SCF record (72 characters maximum).
Input text is written verbatim to the system SCF.
2-18
DH13-04
B
B
INPUT MESSAGES
INPUT MESSAGES
BOOT
Startup Message. Operator requests a reboot of the system when GCOS is in
memory. If initialization is successful and a $ AUTOLD statement was in the
Startup deck from the previous boot, a BOOT SOURCE: CARDS, AUTO OR REPL? is
issued. If no $ AUTOLD statement is used, the Startup deck must be read into
reboot.
NOTE: No other text is permitted with this verb; if text is encountered, the
following message is issued:
BOOT: NO INPUT OPTIONS ALLOWED.
BOOT SOURCE: AUTO OR REPL?
Startup Message. Following a system abort (and dump) the operator is asked to
specify whether the source for rebooting the system is to be from the AUTOLOAD
file or whether sections of the startup job stream are to be selectively
replaced.
NOTE:
This message does not apply to DPS 88 systems.
Operator Action:
Enter AUTO - The Startup program residing on the AUTOLOAD file is to be used
to effect the bootload.
Enter REPL - The operator can selectively replace one or more sections of
the Startup program that exists on the AUTOLOAD file. The
section(s) must be entered in their entirety via the card
reader. The entire section is written to the AUT OLD file to
overlay (replace) the existing section. (Refer to the GCOS 8
OS System Startup manual for additional information.)
If, during the restart procedure, an error occurs that prevents rebooting the
system from the Startup program and job stream that reside on the AUTOLOAD
file, an informational message is issued to the console. The message directs
the operator to reboot the system using the storage medium on which the Startup
program and job stream originally resided.
o
If the Startup program originally resided on magnetic tape, the console
message AUTOLOAD ABORT, BOOT FROM TAPE is issued.
2-19
DH13-04
B
B
INPUT MESSAGES
INPUT MESSAGES
BPRIOR DELET sssss
GPOP Message. Operator requests removal of the B priority status from the
specified job. The B priority status can be restored by changing the frequency
ratio only or the frequency ratio and the time quantum.
System Replies Possible: If the indicated SNUMB does not exist or if the
specified job was not assigned a class B priority at startup, the following
message is printed.
-BPRIOR (text repeated) REQUESTED DENIED
BPRIOR sssss TnnRmm
GPOP Message. Operator requests change in both time and ratio for a priority B
job. (Refer to messages BPRIOR sssss Tnn and BPRIOR sssss Rmm.)
BPRIOR sssss Tnn
GPOP Message. Operator requests a change in the time quantum in the timer for
priority B job sssss. One unit of time is 32 milliseconds.
nn - One or two digits indicating the number of time units (32 milliseconds
each) for the time quantum desired.
System Replies Possible: If the indicated SNUMB does not exist or if the
specified job was not assigned a class B priority at startup, the following
message is printed.
-BPRIOR (text repeated) REQUEST DENIED
When the SNUMB is known but the SSA may not be accessed due to system activity,
the following message will be printed.
*BPRIOR (text repeated) request denied SSA busy - try again.
2-20
DH13-04
B
B
INPUT MESSAGES
INPUT MESSAGES
BPRIOR sssss Rmm
GPOP Message. Operator requests a change in the dispatch ratio for a class B
priority job. The dispatch ratio is the number of dispatches to nonpriority
jobs for each time quantum used by the priority B job. A dispatch ratio of 1
is the highest possible dispatch frequency for a priority B job.
mm - One or two digits indicating the requested dispatch ratio.
System Replies Possible: If the indicated SNUMB does not exist or if the
specified job was not assigned a class B priority at startup, the following
message is printed.
*BPRIOR (text repeated) REQUEST DENIED
When the SNUME is known but the SSA may not be accessed due to system activity,
the following message will be printed.
*BPRIOR (text repeated) request denied SSA busy - try again.
2-21
DH13-04
C
INPUT MESSAGES
C
INPUT MESSAGES
CANCL
SYSOUT Message. The CANCL verb deletes an entry from the Job Output Specials
Table. CANCL has no effect on jobs to which the "special" was already
applied. This verb must precede the verbs COPY, NOPRO, PURGE, REDRC, and
REPRO. These secondary verbs may be followed with the entry of certain control
fields and options.
If the sequence of verbs "CANeL COpy" or "CANeL PURGE" is used without a
control field, the system interprets this as a request to dismount the current
copy or purge tape. If the COPY or PURGE verb being cancelled did not contain
a control field, the COPY or PURGE will continue on a new reel.
An example of the CANCL verb usage is:
CANCL NOPRO ONLPNC
System Replies Possible:
CAN'T DO (verb): SYSTEM ERROR xxxxxx AT LOC. xxx xxx OF .MPOP7
MPOPF INFO (001) - ERROR RETRIEVING CONSOLE TEXT - PLEASE REENTER
MPOPF INFO (002) - ERROR DELETING CREATED SEGMENT
MPOPF INFO (003) - ILLEGAL CANCL REQUEST - PLEASE REENTER
MPOPF INFO (005) - ILLEGAL OPTION IN FIRST CONTROL FIELD
MPOPF INFO (007) - CONFLICTING OPTIONS IN FIRST CONTROL FIELD
MPOPF INFO (008) - ILLEGAL SYSOUT VERB ENCOUNTERED
MPOPF INFO (012) - GEOT QUEUE FULL, PLEASE TRY LATER
xxxxxx REQUEST ALREADY OUTSTANDING FROM THIS CONSOLE
Control field for output types are:
ALL - All print and punch
APR
APN
BPR
BPN
PRT
PNC
ASC
BeD
-
ASCII print
ASCII punch
BCD print
BCD punch
All print
All punch
All ASCII print and punch
All BCD print and punch
2-22
DH13-04
C
C
INPUT MESSAGES
INPUT MESSAGES
A syntactical display of valid combinations is shown in Figure 2-1.
The destination portion of the control field may be:
Txx - Remote ID
RMl' - All remote
ONL - All online
-BLANKET or -B used to indicate all jobs in SYSOUT.
2-23
DH13-04
C
C
INPUT MESSAGES
INPUT MESSAGES
VERB
VERB
[{CANCL~}] REDRC~
[{REMOV»}]
OLD FIELD
TYPE DEST
{[{APR}] [{lid}]}
{[{BPR}] [{RMT}]}~
{
[{ONL}]}
DEVdev
}
{
{[{APR}] [{lid}]} [{~SNB=SSSSS}]
{[{BPR}] [{ONL}]} [{~SID=sid }]
{
} [{-BLANKET }]
{
DEVdev
}
{[{APN}] [{lid}]}
{[{BPN}] [{RMT}]}~
{
[{ONL}]}
DEVdev
}
{
{[{APN}] [{lid}]}
{[{BPN}] [{ONL}]} [{~SNB=sssss}]
{
} [{~SID=sid }]
{
DEVdev
} [{-BLANKET }]
[{CANCL~}] REDRC~
[{REMOV»}]
[{CANCL~}] REDRC~
[{REMOV»}]
{COpy }
] {PURGE}
[{REMOW} ] {REPRO}
{NOPRO}
[{CANCL~}
NEW FIELD
TYPE DEST
{[{PRT}]
}
{[{PNC}] [{lid}]}
{[{ASC}] [{RMT}]}~
{[{BCD}] [{ONL}]}
{
}
{
DEVdev
}
~
{
{lid}}
{
{ONL}}
{
}
{DEVdev
}
}
{[{ALL}]}
}
{[{APR}]}
}
{[{APN}]}
{[{BPR}]} [{lid}] }
{[{BPN}]} [{RMr}]}
{[{PRT}]} [ {ONL} ]}
}
{[{PNC}]}
}
{[{ASC}]}
}
{[{BCD}]}
{
{
DEVdev
[{~SNB=sssss}]
[{~SID=sid
}]
[{-BLANKET
}]
[{~SNB=sssss}]
[{~SID=sid
}]
[{-BLANKET
}]
}
}
[optional]
{select one}
SNB/SID FIELD IS NOT VALID WITH CANCL
REPRO VERB IS NOT VALID WITH CANCL
VALID COMBINATIONS, VERBS/CONTROL FIELDS/OPTIONS FOR SYSOUT VERBS
~
SPACE REQUIRED, ALL OTHERS CAN BE RUN TOGETHER
Figure 2-1. CANCL Syntactical Displays
2-24
DH13-04
c
C
INPUT MESSAGES
C
INPUT MESSAGES
CHANGE
Operator Interface Message. This verb modifies the contents of a specified
location after a validity check of the contents was made.
CHANGE:
ENTER (PXXX SSS, MXXX, H6XXX) OFFSET OLDVAL NEWVAL
where:
P MH6 XXX SSS -
Process
Module
HCM segment
Process number (three digit maximum)
Module number (identified via .ENTRY macro)
Segment identification as defined in system linkage segment
Within the process PUSH segment, the index of the descriptor of the
segment that is to be modified
OFFSET - Location within the segment or module that is to be modified
OLDVAL - Expected contents of OFFSET location
NEWVAL - New contents to replace OLDVAL
System Replies Possible:
•• ILLEGAL PI, MI, OR HI
OFFSET FIELD MUST BE 6 CHAR OR LESS
•• ILLEGAL OLD VALUE
.·ILLEGAL NEW VALUE
•• NOT IN CORE/SYSTEM
•• INSUFFICIENT ARGUMENTS
OFFSET IS OUTSIDE SEGMENT
BAD DESCRIPTOR
ILLEGAL SEGMENT SELECTED
2-25
DH13-04
C
C
INPUT MESSAGES
INPUT MESSAGES
CHANGF
Operator Interface Message. This verb modifies the contents of a specified
location. No content validity check is made.
CHANGF:
ENTER (PXXX SSS, MXXX, H6XXX) OFFSET NEWVAL
where:
P MH6 XXX SSS -
Process
Module
HCM segment
Process number (three digit maximum)
Module number (identified via .ENTRY macro)
Segment identification as defined in system linkage segment
Within the process PUSH segment, the index of the descriptor of the
segment that is to be modified
OFFSET - Location within the segment or module that is to be modified
NEWVAL - New contents to replace previous contents
System Replies Possible:
••ILLEGAL PI, MI, or HI
OFFSET FIELD MUST BE 6 CHAR OR LESS
•• ILLEGAL NEW VALUE
•• NOT IN CORE/SYSTEM
•• INSUFFICIENT ARGUMENTS
OFFSET IS OUTSIDE SEGMENT
BAD DESCRIPTOR
NOT ENOUGH ROOM IN PATCH TABLE
ILLEGAL SEGMENT SELECTED
2-26
---------------~"
---,,---
DH13-04
----------------------
C
INPUT MESSAGES
C
INPUT MESSAGES
COpy (ent) (SHB=snumb or SID=nnnnnn)
SYSOUT Message. In this format the "cnt" represents the control field which
specifies the output type and/or the destination. The COPY is not applied to
any report that had a previous Special Request (e.g., REDRC, PURGE, COpy by ID
or SNUMB, or JOUT DIRECT command).
System Replies Possible:
CAN'T DO (verb): SYSTEM ERROR xxxxxx AT LOC. xxxxxx OF .MPOP7
ERROR RETRIEVING CONSOLE TEXT - PLEASE REENTER
ERROR DELETING CREATED SEGMENT
ILLEGAL OPTION IN FIRST CONTROL FIELD
CONFLICTING OPTIONS IN FIRST CONTROL FIELD
GEOT QUEUE FULL, PLEASE TRY LATER
ILLEGAL KEYWORD ON LAST OPTION
INVALID NUMBER
xxxxxx REQUEST ALREADY OUTSTANDING FROM THIS CONSOLE
NOTE: Refer to the syntactical display in Figure 2-1 for valid combinations.
CSTATS icc
GPOP Message.
Operator requests status of a particular PUB (channel).
System Replies Possible:
.CHicc @tt.ttt ICON=nnnnnn IERR=nnnnnn
bbbbbb (XBAR)(PSIA) (STPD) (RSRVD-T&D) (ITR)
*CHicc 10M INVALID
.CHicc CHI INVALID Error Messages
.CHicc NOT CONFIGURED
bbbbbb
ICON
IERR
XBAR
PSIA
STPD
RSRVD
ITR
-
Bel device type
Number of connects to this channel since last boot
Number of errors on the channel since last boot
Channel cross-barred
PSIA channel
Channel stopped
T&D - Channel reserved for T&D
Online isolation test routines in progress
2-27
DH13-04
D
D
INPUT MESSAGES
IIPUT MESSAGES
DATE mmddyy
GPOP Message. Operator sets the GCOS date (which can be different from System
Controller Clock date).
System Replies Possible.
No system reply occurs unless an error is detected.
DCHNL icc
lOS Message. Operator requests that the specified PUB (channel) be
deactivated. (Refer to ACHNL icc.) This message is used by the operator when
a crossbarred PUB is experiencing a high error rate, and the operator wants
offline T&D performed on the PUB.
System Replies Possible: If deactivation cannot or should not be effected, the
system replies with one of the following messages.
*RE DCHNL icc FNP CHANNEL - INVALID INPUT
Operator requested deactivation of a PUB that is on an FNP device.
to RLSEI 14 •
Refer
*RE DCHNL icc INVALID REQUEST DENIED
Operator requested deactivation of a PUB that was not configured.
*RE DCHNL icc NO XBAR EXISTS REQUEST DENIED
Operator requested deactivation of a non-crossbarred PUB.
*RE DCHNL icc NO XBAR AVAILABLE REQUEST DENIED
Operator requested deactivation of a channel that is the last physical
path remaining in the crossbarred configuration to a peripheral
subsystem.
*RE DCHNL icc SUSPENDED REQUEST DENIED
Operator requested deactivation of a PUB that was suspended.
*RE DCHNL icoc SHARED ACCESS REQUESTED DENIED
Operator requested deactivation of a channel to a shared device/MPC.
*RE DCHNL iccc 10M IS RELEASED REQUESTED DENIED
Operator requested deactivation of a channel on an input/output
controller (10M) that is released.
*RE DCHNL iccc ALREADY INACTIVE, REQUEST DENIED
Operator requested deactivation of a channel already deactivated.
2-28
DH13-04
~
D
INPUT MESSAGES
D
INPUT MESSAGES
When a deactivation request was successfully executed, the system outputs the
following reply.
*RE DCHNL icc DEACTIVATED AT tt.ttt
DDT APE sssss ddd fc
Operator Interface Message. Operator requests that the magnetic tape device
named ddd be assigned to the SNUMB sssss for the given file code (fc). Three
constraints apply:
~
1. The device may not be assigned for files which request an alternate
device in the program's $ TAPE control statement.
2. The maximum number of tape devices that can be assigned at anyone time
is 30.
3. The device may be assigned only to jobs in execution.
System Replies Possible:
DDTAPE: SNUMB NOT FOUND
The snumb which was entered is incorrect or the job is not in execution.
DDT APE: WRONG DEVICE NAME
The device name entered is not correct.
DDTAPE: DEVICE UNAVAILABLE
The device which was requested is not currently available.
DDTAPE: DEVICE NAME NOT FOUND
The device name table does not contain the device name entered with the DDT APE
verb.
DDTAPE: TABLE SIZE EXCEEDED
The table size of 30 entries was reached.
2-29
DH13-04
D
D
INPUT MESSAGES
INPUT MESSAGES
DDT APE: ILLEGAL FORMAT - SIB SNUMB DEV-NAME FC
The system recognized an improper format; the format must be-as indicated by
the above message (snumb, device name, file code).
DDTAPE: INVALID FILE CODE
The system recognized an improper file code. This is commonly caused by a file
code entry which was left blank or made zero.
DEDCAT xxx
Peripheral Allocator Message.
device name).
Operator dedicates a peripheral device (xxx -
System Replies Possible: No system reply occurs unless an error is detected.
Appearance of one of the following messages indicates an error in the request,
or that the request cannot be granted immediately.
MPOPE ERROR(102) - xxx NAME NOT FOUND
MPOPE ERROR ( 103) - xxx MULT. NAMED CANT DEDCAT
DELETE Sin
Common Files Facility (CFF) Message. In the multiple system cluster of a CFF
environment, one or more of the systems may suffer a catastrophic failure
(i.e., go down with out a terminating series of messages ending with the BOOT
SOURCE: AUTO OR REPL? message). If at least one system remains up, the mass
storage controller must not be rebooted, but the mass storage controller lock
bytes must be reset for each of the systems that went down. Reset the lock
bytes for a down system, whose system number is n, by issuing a DELETE Sin
console message from the console of a surviving system. Issue this message
before attempting startup for the down system.
System Replies Possible: Hone.
2-30
DH13-04
\
I
f
D
D
INPUT MESSAGES
INPUT MESSAGES
DELEVL
File Management Supervisor Message.
a volume from a volume set.
This allows the console operator to delete
DELEVL vol set name -SER volume id
Rules:
1. VSMC or catalog volumes can not be deleted from a volume set.
2. This command does not check for the existence of files on the volume.
is the site's responsibility to ensure the volume is empty before
deleting it from the volume set.
System Replies Possible:
It
None.
'DISABLE INITIALIZE ('DIS INI)
/
/
Remote Maintenance Interface Command. This command verb can be entered only at
the local console and will prevent an Initialize (ESC,CNT-I) and Boot
(ESC,CNT-B) command from being entered at the remote console.
System Replies Possible:
None.
'DISABLE MD ('DIS MD)
Remote Maintenance Interface Command. This command verb can be entered at the
local console only and will cause the console, if it is a multi-drop master, to
cease polling and revert to a "normal" (non multi-drop master) console. The
multi-drop master console controls the maintenance interface of the Maintenance
MCAs. This command must be entered at the current multi-drop master console
prior to entering lENA MD at the new multi-drop master console.
System Replies Possible:
, MULTIDROP DISABLED I - Transmitted to the local console.
,
)
2-31
DH13-04
1M;'
4U
$.
,.4r,,%.
D
D
INPUT MESSAGES
IRPUT MESSAGES
(
'DISABLE MONITOR ('DIS MOl)
Remote Maintenance Interface Command. This command verb can be entered from
the local console onl'y, and is v~ig_2!l1L!!!l<:E J~.h~....£.!l~..E!!,,.,,.!~!:£~,~,!:._is
. . ...
configured for twochann~~cal console monitoring of block data transfers
re.g., dUmps~~paE'chesrtothe remote console is disabled. Input from the
remote console will continue to be sent to the local console.
System Replies Possible:
None.
'DISABLE PRINTER ('DIS PRI)
This command verb can be entered at the local console only and is used to
disable the slave printer from the local console.
System Replies Possible:
'PRINTER DISABLEDI - Transmitted to the local console when the slave
printer is disabled.
(
'DISABLE REMOTE ('DIS REM)
Remote Maintenance Interface Message. This command verb can be input from
either the local or remote console. Any transaction that was in process on the
remote channel is aborted.
System Replies Possible:
IREMOTE DISCONNECTI - Transmitted to both local and remote consoles.
DLINK iccdd
GPOP Message. Operator requests a console listing of the directory of
unavailable llinks for the specified mass storage device.
System Replies Possible:
10M INVALID
CHII INVALID
DEV INVALID
INPUT INVALID
c
2-32
DH13-04
D
INPUT MESSAGES
D
INPUT MESSAGES
DEVICE RLSED
NON-STRUCTURED DEVICE
CANT READ LLINK DIRECTORY
NO ENTRIES IN DIRECTORY
If any llinks are unavailable the following message is output:
LLINKI nnnnnn ILLINKS xxxxxx
In the message, nnnnnn is the starting llink number marked unavailable and
xxxxxx is the number of llinks in the string. The maximum number of llink
strings unavailable is 62 (decimal).
Mass Storage Responses:
AVAIL/nnnnn - Number of llinks available
-RESV/nnnnn - Number of llinks reserved
-DLINK/nnnnn- Number of llinks marked unavailable for allocation in the
device llink directory
-DLINK/CLR - Directory cleared because at system rollcall time an error was
encountered while processing the device llink directory
IPLS/nnnnn - Usage count
DUMP
Dump Message.
Operator requests system to perform a master mode dump.
System Replies Possible:
---DUMP (O)PTION/(D)EFAULT/(N)ONE?
DUMP: NO OPTIONS ALLOWED
Enter 0 or EOM - permits the operator to select the various DUMP device
options.
Enter D
- indicates the .MDUMP module is to take the default options
entered on the $ ANSWER statement(s).
Enter N
- discontinues the dump and allows the startup program to be
read into the system.
2-33
DH13-04
D
INPUT MESSAGES
D
INPUT MESSAGES
DUPBAD iccdd
Mirrored Disk Message. The operator may choose to set one device of mirrored
pair BAD. This may be done because of excessive transient errors or for any
reason which suggests that device repair may be in order. The device is set
BAD by the DUPBAD console verb.
=
iccdd
The device address of the specific device to be set BAD. A device
can only be set BAD if both devices of the pair are currently GOOD
and ASGN'd and not currently under repair (mirrored device copy
utility) or.busy with exception processing.
Following a successful DUPBAD, an automatic PSTATS is done on the device to
show the current state of both devices.
The following console dialog may occur during DUPBAD processing.
Operator Input:
DUPBAD iccdd
Console Replies (if device set BAD):
Dliccdd device type- device name(s)- status info
MIRRORED DEVICE nnn xxx xx (sss) - yyyyy (ttt)
where:
nnn
xxxxx
yyyyy
sss, ttt
NOTE:
-
device name
Input/output controller/channel/device of Primary
Input/output controller/channel/device of Secondary
GD for remaining good device
BAD for device set bad
This is an automatic PSTATS of the device.
Console Replies: (if DUPBAD processing is denied):
iccdd
iccdd
iccdd
iccdd
iccdd
iccdd
NOT MIRRORED
ALREADY BAD
ALT DEVICE ALREADY BAD
BUSY, CANNOT SET BAD
ALT DEVICE BUSY, CAN'T SET BAD
MIRRORED DEVICE RELEASED
2-34
DH13-04
D
D
INPUT MESSAGES
INPUT MESSAGES
DUPER
Mirrored Disk Message. This command is used to invoke the copy/compare utility
MDUPR. Once the utility is started, a series of console questions and answers
is used to identify the task to be performed and certain characteristics of the
run. The .MDUPR program cannot be invoked if mirrored devices are not
currently configured.
The following console dialog may occur during a "device copy" execution of this
utility.
Operator Input:
DUPER
The console replies:
DUPER - NO MIRRORED DEVICES CONFIGURED
or
•••• nnnnD •••• • SRT nnnnD-01 @hh.hhh DUPR KPX kkk
•••• nnnnD •••• ENTER DUPER COMMAND:
Operator Input:
COpy ddd -T t
The console replies:
•••• nnnnD •••• ENTER SOURCE DEVICE ICCDD
Operator Input: iccdd
2-35
DH13-04
E
INPUT MESSAGES
E
INPUT MESSAGES
ECOL CSHSTS
ECOL Message.
Operator queries processors to determine status of cache.
System Replies Possible: The status of the assigned processors is displayed
and followed by a message as shown.
Example of display and message:
PRO I - 1 PORT 6 CSH1-ON,
PRO' - 0 PORT 7 CSH1-0N,
CSH2-0N,
CSH2-ON,
LUF-3
LUF-3
MR
MR
= 744003
= 744003
MR - Cache mode register (bits 18-35)
LUF - Lockup fault timer register
CACHE MONITORING BY - (ECOL or GCOS Operating System)
ECOL CSHMOF
ECOL Message.
message:
This verb allows the operator to disable the cache informative
.CACHE ERROR, FLT REG BITS 32-46 = xxxxxx, PORT n.
NOTE:
ECOL default has this message disabled.
System Replies Possible:
ECOL REQUEST DENIED; INVALID
ECOL CSHMON
ECOL Message.
message:
This verb allows the operator to enable the cache informative
.CACHE ERROR, FLT REG BITS 32-46
NOTE:
= xxxxxx,
PORT n.
ECOL default has this message disabled.
2-36
DH13-04
E
INPUT MESSAGES
E
INPUT MESSAGES
System Replies Possible:
ECOL REQUEST DENIED; INVALID
NOTE: If the CSHON or CSHOF verb is entered when ECOL is not in execution,
the status bits in .CRCMM+3 are altered without further action by
ECOL. When ECOL is placed in execution, the cache status is then set
to the requested status. (Refer to use of ECOL CSHSTS verb to obtain
current status of cache memory.)
ECOL CSHOFn
n - 0-7
ECOL Message. This input allows the operator to disable cache on a specific
processor port on SCU-O.
System Replies Possible: If the requested action was successfully completed,
the following message is output:
•• CACHE STATUS ••
If cache is already disabled, the system responds with:
ECOL REQUEST DENIED; CSH DISABLED
If the request was improperly entered, the system responds with:
ECOL REQUEST DENIED; INVALID
NOTE: If the CSBON or CSHOF verb is entered when ECOL is not in execution,
the status bits in .CRCMM+3 are altered without further action by
ECOL. When ECOL is placed in execution, the cache status is then set
to the requested status. (Refer to the use of ECOL CSHSTS verb to
obtain current status of cache memory.)
2-37
DH13-04
E
INPUT MESSAGES
E
INPUT MESSAGES
ECOL CSHOln
n -
0-7
ECOL Message. This input allows the operator to enable cache on a specific
processor port on SCU-O.
System Replies Possible: If the requested action was successfully completed,
the following message is printed:
•• CACHE STATUS ••
If cache is already enabled, or partially enabled, the system responds with:
ECOL REQUEST DENIED; CSH ENABLED
To fully enable a partially enabled Cache:
1. Disable cache (ECOL CSHOFn)
2. Enable cache (ECOL CSHONn)
If the request was improperly entered, the system responds with:
ECOL REQUEST DENIED; INVALID
ECOL CSHSTS
ECOL Message. This verb allows the operator to determine if cache memory is
enabled or disabled.
System Replies Possible:
None.
ECOL DLYxx
ECOL Message. Allows installations to change the MME GEWAKE delay in ECOL,
which governs the frequency of execution.
xx - One or two decimal digits that specify the delay in 0.1-minute
increments
o = Continuous
execution with no delay
every 5 minutes (default)
63 = Execute every 6.3 minutes (maximum)
50
= Execute
2-38
DH13-04
--
-----
-~~~-------~~-.-
E
E
INPUT MESSAGES
INPUT MESSAGES
EeOL GPR (option)
ECOL Message. Operator requests system to take a specific action pertaining to
Exception Processing records.
System Replies Possible:
option -
L - Log Exception Processing records to the ECOL file.
DL - Disable logging of Exception Processing records, except for
extended status records as defined by bits 15-17 of the
Exception Processing communication word.
ECOL MPC ETxxxx
ECOL Message. Operator sets the ECOL MPC error threshold (also called abnormal
statistics threshold).
xxxx - One to four decimal digits that specify the error threshold in 0.01
percent increments (range - 0001'to 4095).
o-
Disable all threshold reporting
1 - Enter threshold message if abnormal statistics rate is at
least 0.01 percent (default)
4095 - Enter threshold message if abnormal statistics rate is at
least 40.95 percent (maximum)
System Replies Possible: If no reply, the requested action was performed.
the request was improperly entered, the system responds with ECOL REQUEST
DENIED, and the error threshold remains unchanged.
2-39
If
DH13-04
E
INPUT MESSAGES
E
INPUT MESSAGES
ECOL MPC SPxxxx
ECOL Message.
Operator sets the ECOL MPC statistics sample period.
xxxx - One to four decimal digits that specify the sample period in
0.1-minute increments.
o - Disable periodic sampling
600 - Sample every 60 minutes (default)
4095 - Sample every 6.8 hours (maximum)
To disable MPC statistics sampling, the operator enters ECOL MPC SPO.
To resume MPC statistics logging, the operator enters ECOL MPC SPxxxx.
To temporarily suspend MPC statistics sampling, the operator enters ECOL MPC
SPO after the ECOL program has started.
System Replies Possible: If no reply, the requested action was performed. If
the request was input improperly formatted, the system responds ECOL REQUEST
DENIED, and the sample period remains unchanged.
ECOL PTLOFn
n - 0 to 3
ECOL Message. This input allows the operator to disable PATROL on a specific
processor (DPS 8/20 and 8/44 systems only).
System Replies Possible: If the requested action was successfully completed,
the system responds with:
.PATROL DISABLED, PRCI n PORTI n
If PATROL is already disabled, the system responds with:
ECOL REQUEST DENIED; PTL DISABLED
2-40
DH13-04
E
E
INPUT MESSAGES
INPUT MESSAGES
If the request was improperly entered, the system responds with:
ECOL REQUEST DENIED; INVALID
NOTE: If the PTLONn or PTLOFn verb is entered when ECOL is not in execution,
the status bits in .CRCMM are altered without further action by ECOL.
When ECOL is placed in execution, the PATROL status is then set to the
requested status.
ECOL PTLONc
n - 0 to 3
ECOL Message. This input allows the operator to enable PATROL on a specific
processor (DPS 8/20 and 8/44 systems only).
System Replies Possible: If the requested action was successfully completed,
the system will respond with:
.PATROL ENABLED, PRCI n PORTI n
If PATROL is already enabled, the system responds with:
ECOL REQUEST DENIED; PTL ENABLED
If the request was improperly entered, the system responds with:
ECOL REQUEST DENIED; INVALID
NOTE: If the PTLONn or PTLOFn verb is entered when ECOL is not in execution,
the status bits in .CRCMM are altered without further action by ECOL.
When ECOL is placed in execution, the PATROL status is then set to the
requested status.
ECOL START
ECOL Message. Operator requests to start ECOL on a system that has the ECOL
automatic start inhibited.
System Replies Possible: If there is no system reply, the requested action was
performed. If no system problems occur, an informative ECOL executing message
is issued.
2-41
DH13-04
E
E
INPUT MESSAGES
INPUT MESSAGES
If the ECOL Program is already in execution, the system responds:
ECOL REQUEST DENIED; IN EXECUTION
If the request was entered improperly, the system responds:
ECOL REQUEST DENIED; INVALID
EeOL STOP
ECOL Message.
Operator requests to stop ECOL.
EeOL TCOMM
ECOL Message.
Operator requests to see the ECOL communication region words.
System Replies Possible:
responds:
When the requested action was completed, the system
.CRCMM - xxxxxxxxxxxx x ••• x
.CREC1 - xxxxxxxxxxxx x ••• x
x ••• x
x ••• x
x ••• x
x ••• x
(octal)
(octal)
If the request was improperly entered, the system responds:
ECOL REQUEST DENIED; INVALID
ELAN
The ELAN verb invokes the Error Logging and Analysis (ELAN) report program
which produces diagnostic reports on system operating conditions. If ELAN is
present on the system, the following reports are output on the system printer:
o System Summary Report - Overall view of system performance startup (i.e.,
system aborts, cache and other faults; processor System Control Unit
(SCU) and memory faults; Exception Processing type 3 1/0 data errors;
tape and disk MPC statistical error counts).
2-42
DH13-04
E
E
INPUT MESSAGES
INPUT MESSAGES
o Detailed Error Report - In depth report including failing elements
definitions down to ORU level in some cases.
System Replies Possible:
ELAN NOT AVAILABLE
- ELAN has not been installed.
ELAN REQUESTS PRIVITY - A normal privity request where $ELAN rather than a
numeric statement is given as the SNUMB. This
message will be issued by the system upon start of
ELAN report/analysis program. The operator response
should be to RUN the program.
'ENABLE CHANNEL (lENA CHA)
Remote Maintenance Interface Command. This command verb can be entered from
either the local or remote console and is valid only when the channel adapter
is configured for two channels and the IRELINQUISH command has been executed.
This command returns the system to two channel operation. The IENAble
Initialize state will be disabled if enabled.
System Replies Possible:
None.
'ENABLE CONSOLE (lENA CON)
Remote Maintenance Interface Command. This command verb can be entered from
either the local or remote console and results in the Maintenance or Text mode
of operation being disabled and a return to the normal operational state.
System Replies Possible:
I TEXT DISABLED I
- Transmitted to the local or remote console (when
command entered at remote console) when exiting from
Text Mode.
I CONSOLE ENABLED I - Transmitted to the local or remote console (when
command entered at remote console) when exiting from
Maintenance Mode.
2-43
DH13-04
E
INPUT MESSAGES
E
INPUT MESSAGES
IENABLE INITIALIZE (lENA INI)
Remote Maintenance Interface Command. This command verb can be entered at the
local console only and is required to permit an Initialize (ESC,CNT-I) and Boot
(ESC,CNT-B) command from a remote console. The command will not be
acknowledged unless the console is in Relinquish mode.
System Replies Possible:
'ILLEGAL COMMAND' - Transmitted to the local console if Relinquish mode not
active.
ICMD REJECTED'
- Transmitted to the remote console if an attempt to enter
an ESC, CNT-I or ESC, CNT-B from the remote console is
made without 'Enable Initialize true.
IENABLE MAINTENANCE (lENA MAl)
Remote Maintenance Interface Command. This command verb can be entered from
either the local or remote console. If IALLow MAIntenance permission was not
granted by entering 'ALL MAl at the local console or if the ELS/DPU is not
operational, the command from the remote console will be rejected with a
IILLEGAL COMMANDI message. It places the channel in Maintenance Mode which
provides Remote Maintenance Interface control of maintenance, diagnostic, test,
and operator panels. Any system commands are executed between operator and
Diagnostic Processor Unit (DPU) messages. Maintenance Mode is maintained until
an IENABLE CONSOLE command is sent from either the local or remote console.
System Replies Possible:
'ILLEGAL COMMAND' - Transmitted to the console through which the IENABLE
MAINTENANCE command was entered if the Diagnostic
Processor Unit (DPU) is not operational
OR
- Transmitted to the remote console (when the command is
entered from the remote console) if IALLow MAIntenance
permission was not granted.
2-44
DH13-04
E
E
INPUT MESSAGES
INPUT MESSAGES
IENABLE MCA I (lENA MCAI)
Remote Maintenance Interface Command. This command verb may be entered at
either the local or remote console and is the same as the DENA MCA command
except that the console will be "dedicated" to a specific MCA rather than
"shared" with the rest of the console duties. This mode should be used only
when conversing with the MCA(s) and the operating system is NOT running. If a
connect 1/0 is received from the Operating System while in MCA dedicated mode,
the console will revert to MCA "shared" mode.
System Replies Possible:
All messages as specified for lENA MCA as well as the following:
D MCAxx DEDICATED MODE D - Transmitted to either the local or remote
console (if command entered at remote console)
when entering dedicated mode. (xx is the MCA
addressed).
IMCAxx NOT RESPONDING #
I CONSOLE ENABLED #
- Transmitted to either the local or remote
console (if command entered at remote console)
if MCAxx is not answering.
tENABLE MeA (lENA MCA)
Remote Maintenance Interface Command - This command verb may be entered at
either the local or remote console and is used to establish a maintenance mode
with the MCA(s). The command will be rejected when requested from a remote
console and IALL MAl permission was not granted at the local console. When the
MCA is enabled, the console will be in a "shared" mode with the rest of the
console duties. That is, the normal conversation with the Operating System
(OS) will continue, with messages between the MCA and console, and the OS and
console all being displayed. If necessary, the messages will be interleaved on
the console display on a line-by-line basis. The OS may prevent the operator
from entering messages to the MCA(s) with a "lock" command. The MCA(s) will
remain "locked" until an 'unlock' command is received from the OS. This
command is applicable to consoles configured on lMUs only.
2-45
DH13-04
E
INPUT MESSAGES
E
INPUT MESSAGES
System Replies Possible:
I ILLEGAL COMMAND I
- Transmitted to either the local or remote
console (when command entered at the remote
console) when it is not the master console or
the MCA addressed is not valid.
I MCA ACTIVE I
- Transmitted to either the local or remote
console (when command entered from the remote
console) when enabled.
I MCAxx NOT RESPONDING I
- Transmitted to either the local or remote
console (when command entered from the remote
console) if the MCA is not answering.
IENABLE MD (lENA MD)
Remote Maintenance Interface Command. This command verb can be entered at the
looal console only and is used to establish the console at which it is entered
as the multi-drop master oonsole. (The multi-drop master console controls the
maintenance interfaoe of the MeA(s).) This command would be used when moving
the multi-drop master from one console to another or if, for some reason, the
MCA had not established a master multi-drop console.
AlDIS MD command must have been previously entered at the console that was the
multi-drop master if one had been established. This oommand is applicable to
consoles configured on IMUs only.
System Replies Possible:
I MULTIDROP ENABLED I
- Transmitted to local console when it has been
made the multi-drop master.
, MULTIDROP ACTIVE I
- Transmitted to local console when the
multi-drop is already active.
The following are SECUR options that may be selected:
STATUS
CHANGE
LOCK
UNLOCK
USER
System Replies Possible:
None.
{Ssssss,nnDnnnl(nK)}
{Pppp
}
{Pppp,nnnnnnl(nK) }
SlAP {Hmmm ,nnnnDn I (d) }
{H6hhh
}
{H6hhh,nnnnnnl(nK) }
{Ww
}
{Ww,oooooo,kk
.{LIlES
}
}
GPOP Message. Allows the operator to initiate a snapshot dumR from the system
console. If PR2 is assigned, dedicated, and not allocated, the dump is printed
to this printer; otherwise, the dump 1s written to the Statistical Collection
File.
sssss
ppp
nnnnnn
mmm
6hhh
w
o
-
SNUMB
Process number (0-511)
Number of words (decimal)
Module number
Segment identification
Working-space number (0-511)
Offset location (decimal words)
nk - Number of 1K blocks of words
k - Number of 1K pages
SNAP Pppp - Dump process number ppp in its entirety, including
its control segments and registers.
2-111
DH13-04
S
(
S
INPUT MESSAGES
IIPOT MESSAGES
SNAP Ssssss,{nnnnnn}
InK
}
---
- Beginning at location zero of SNUMB sssss, dump
nnnnnn words, or nK blocks of words, including
control segments.
SNAP Pppp,{nnnnnn}
{(nK)
}
- Beginning at location zero of ~q£~~J1~~r ppp,
dump nnnnnn (dec) number of words, or nK blocks of
words, including control segments.
SNAP Mmmm,{nnnnnn}
{(n!{)
}
- Beginning at location zero of module number mmm,
dump nnnnnn (dec) number of words, or nK blocks of
words.
SNAP H6hhh - Dump all of the segment identified by segment
identification 6hhh.
SNAP H6hhh,{nnnnnn}
{(nK) }-
Beginning at location zero of the segment
identified by segment identification 6hhh, dump
nnnnnn (dec) number of words or nK blocks of words.
(
SNAP Ww - Dump the first 1K words of working-space w. The
working-space number identified by "w" may be 1 to
3 digits in length.
SNAP Ww,o,k - Beginning at location 0, dump k pages of
working-space w. The combination of input
parameters, the "W" and comma(s), cannot,exce~d 12
characters. The working-sapce number idientified
by "w" and the number of lK pages identified by "k"
may be 1 to 3 digits in length. The offset
location identified by "0" may be 1 t06 digits in
length.
All fields are considered to be right-justified.
While individual fields are right-justified, the
entire entry is left-justified in AQ register, and
any right-most characters beyond character 12 are
truncated.
For example, SNAP W20,12345,24 is a combination of
input parameters that uses the maximum of 12
char~cters.
(
2-112
DH13-04
S
INPUT MESSAGES
S
INPUT MESSAGES
SNAP LINES - Snap DNET internal lines table
NOTE: 1. The SNAP request may be terminated through the use of the "An
option in response to any related line printer GEPR message.
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
SNAP
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
ERROR:
TOO MANY INPUT CHARS. (Lxxxxxx Dxxxxxx)
FIELD MUST BE OCTAL (Lxxxxxx Dxxxxxx)
FIELD MUST BE NUMERIC (Lxxxxxx Dxxxxxx)
NON-NUMERIC K FIELD (Lxxxxxx Dxxxxxx)
TOO MUCH INPUT (Lxxxxxx Dxxxxxx)
TOO MANY FIELDS (Lxxxxxx Dxxxxxx)
MISPLACED COMMA (Lxxxxxx Dxxxxxx)
LAST FIELD TOO LONG (Lxxxxxx Dxxxxxx)
MUST GIVE PI' (Lxxxxxx Dxxxxxx)
PROG , TOO BIG (Lxxxxxx Dxxxxxx)
ILLEGAL MODULE I (Lxxxxxx Dxxxxxx)
MODULE NOT LOADED (Lxxxxxx Dxxxxxx)
MUST SAY , LOCS (Lxxxxxx Dxxxxxx)
, LOeS TOO BIG (Lxxxxxx Dxxxxxx)
SEGID TOO BIG (Lxxxxxx Dxxxxxx)
CAN'T SNAP SD.SSM (Lxxxxxx Dxxxxxx)
SEGID MUST BE 6xxx (Lxxxxxx Dxxxxxx)
SEG DESC. NOT TYPE 0 OR 1 (Lxxxxxx Dxxxxxx)
NULL SEGMENT (Lxxxxxx Dxxxxxx)
MISSING SEGMENT (Lxxxxxx Dxxxxxxx)
WSR NOT 0 OR 1 (Lxxxxxx Dxxxxxx)
NO SUCH WSN (Lxxxxxx Dxxxxxx)
NOT DIRECTORY F TYPE (Lxxxxxx Dxxxxxx)
STARTING OFFSET ILLEGAL (Lxxxxxx Dxxxxxx)
PROGRAM BUSY (Lxxxxxx Dxxxxxx)
START WITH H,P,N,W, OR S (Lxxxxxx Dxxxxxx)
JOB BUSY - TRY AGAIN (Lxxxxxx Dxxxxxx)
JOB OUT OF MEMORY (Lxxxxxx Dxxxxxxx)
JOB UNKNOWN (Lxxxxxx Dxxxxxx)
SYSTEM ERROR-NOTIFY FED (Lxxxxxx Dxxxxxx)
INVALID WS QTR I (Lxxxxxx Dxxxxxx)
SNUMB IS NOT IN SYSTEM (Lxxxxxx Dxxxxxx)
The Land D fields are for use by the field engineers where further diagnosis
is necessary. All replies indicate an error in the request and the request is
ignored.
2-113
DH13-04
S
S
INPUT MESSAGES
SlUMS
88888 -
(
INPUT MESSAGES
8ee
STATS
{filename
}
SPAWN { filename,uu }
GPOP Message. Operator requests that a spawn job be entered into the system.
The job must have already been placed on a permanent file, as described in GCOS
8 OS System Operating Techniques manual.
filename - Five-character name that was used in the FCREAT directive
uu - Urgency level (decimal) of the job (1-60)
System Replies Possible: If the file cannot be spawned, or if errors exist,
the following message is output:
.SPAWN ABT reason
{ OFF }
SRM {
{ON
}
}
lOS Message.
Operator requests the status return modifier
--, to be turned OFF/ON.
System Replies Possible:
--
.SRM xxx INVLD
SSA
Operator Interface Message. Operator requests a console display of information
concerning SSA (Slave Service Area) module activity.
System Replies Possible:
.SSA: xx PAGES, xxxxx FINDS, xxx xx LOADS, xxxxx RELOADS, xx% HIT RATIO
(
2-114
S
S
INPUT MESSAGES
INPUT MESSAGES
STArs snumb
The "STATS sssss" reports the first occurrence of a sssss SNUMB, while
searching the execution, SYSOUT and Scheduler tables, in that order. If a
multiple occurrence of the SNUMB is found, the operator is informed of that
fact with the message
.sssss-DUPLICATES FOUND
- USE -ALL TO PRINT ALL
following the normal STATS output for the job. The operator input of "STATS
SSBSS -All" forces the display of all jobs with that SNUMB that are found in
those tables.
Example:
???STATS SHARD
.SHARD-1/0 U05 PRCSSI17 V EXEC
PROC{TU-OO.OOO TR-00.0490 ELP-00.041 USERID=SYS SOFTWARE
CORE (PFI-45 WS-003K) STATE-000000101200 09.957.SHARD-DUPLICATES FOUND - USE -ALL TO PRINT ALL
???STATS SHARD -ALL
.SHARD-1/0 U05 PRCSS'17 V EXEC
PROC(TUOO.OOO TR-00.049) ELP-00.044 USERID=SYS SOFTWARE
CORE (PF#-45 WS-003K) STATE-000000101200 09.960
·SHARD IN SYSOUT @ 09.960 URG=62 SID=11 LLINKS=63
ELP=00.041 FLAGS=.R ••••• USERID=SYS SOFTWARE
BPRIXX
•••• D••••
If the status is in SYSOUT, the following two lines will appear:
·sssss IN SYSOUT @ HH.TTT Uuu SID BLINKS=BBBBB
ELP = HH.TTT FLAGS = FF.FFF USERID = iiiiiiiii
where:
SID - SNUMBs unique system ID
BBBBBB - SYSOUT BLINK space
FF.FFF - SYSOUT status
·sssss-aa/nn uu PRCSSHkkk m xxx •••• xxx
2-115
DH13-04
S
S
IIPUT MESSAGES
IlfPUTMESSAGES
where:
aa nn uu kkk mSID bbbbb FF.FFF -
current activity number
number of remaining activities
urgency
KPX (Known Process Index)
mode - R is real (accommodation) and V is virtual (native)
SNUMBs unique system ID
SYSOUT BLINK space
SYSOUT status
xxx •••• xxx - any of the following:
REMOTE PHASE ONE
CARD GEIN READING
INCV GEIN READING
REMOTE PHASE TWO
WAITING ALLOC
HOLD
LIMBO
EXEC
SWAPPED
WAITING MEDIA
SIEVE
REST
TERMINATION
The following interim message may be issued:
sssss
STATUS CHANGING
If the status is SWAPPED or WAITING CORE, and if core is being requested, the
following is appended to the initial response message:
CORE REQ ccck
where:
ccc - the amount of core requested.
k representing thousands.
2-116
DH13-04
S
INPUT MESSAGES
S
INPUT MESSAGES
If the status is not EXEC nor TERMINATION, the initial response message is
appended with one of the following:
HH.TTT
or
DDD+HH.TTT
where:
HH.TTT - The time in hours and thousandths of hours
DDD
- The number of days (only displayed if DDD>1)
If the status is EXEC or
TERY~NATION,
a second line is added which appears as:
PROC (DDD+TU-DDD+HH.TTT TR-DDD+HH.TTT)
ELP-DDD+HH.TTT USERID = iiiiiiiiiiii
where:
HH.TTT - The time in hours and thousandths of hours
DDD - The number of days (only displayed if DDD>1)
iiiiiiiiiiii - The 12-character user id
Also, a third line is appended to the initial message formatted as follows:
CORE (PFI-xxxxxx WS-kkkK)
STATE-ssssssssssss
where:
xxxxxx - The number of page faults
kkk - The current workspace size
ssssssssssss - The octal representation of .STATE word.
If the value kkk is followed by an asterisk, it is an extended memory job.
If any I/O requests are outstanding, the third line (above) is appended with:
IQ(REQ-nnn TRN-xxx CCALL-yyy)
where:
nnn - total request count
xxx - number in transmission
yyy - number of oourtesy calls
2-117
DH13-04
S
S
(
INPUT MESSAGES
INPUT MESSAGES
Then, the third line is ended with:
HH.TTT
where:
HH.TTT - The time in hours and thousandths of hours
*sssss-aa Uuu KPXlkkk xxx •••• xxx
where:
all above are previously defined in this message's description and
xxx •••• xxx - one of the following:
JUST STARTED, RE-ENT STATS
STATUS CHANGING, RE-ENT STATS
or any indicated combination of the following:
(
-HOLD REQ.
{PRMFL BUSY
}
[-DELAY][-SAVES] {WTNG nnn dddddd [LINKS]}
[FLNK PASS-Ol]
-CWF
[ -SAVES]
-NACT [ -SA VES]
where:
dddddd - one of the following:
DSS190
MS0400
MS0500
TAPE
TAPE9
MPC9
CPZ200
CONSLE
CPZ300
PRT303
PRT203
MSU3380
FIPS*TAPE9
DSS191
MS0450
MS0501
TAPE7
MPC7
READER
eCU401
PRT300
see
READER
PRT401
ess
FIPS*TAPE7
(
2-118
DH13-04
S
S
INPUT MESSAGES
INPUT MESSAGES
Following any messages to the system console by GPOP, the System Scheduler is
queried as to the SNUMBs status within the Scheduler's catalogues.
System Replies Possible:
sssss
sssss
sssss
sssss
sssss
sssss
NOT FOUND
- specified SNUMB not known to Scheduler
- specified SNOME has been sent to Peripheral Allocator
- SAVED JOB
(id) IS IN .class WAITING TO BE PURGED
(id) IS IN .class WAITING FOR RUN .IDS
(id) IS IN .HOLD WILL ENTER .class,Pxx ON mm/dd/yy AT hh.mm
(id) IS IN .HOLD WILL ENTER .class,Pxx ON mm/dd/yy AT hh.mm (CYCLIC JOB)
Where:
sssss
id
.class
Pxx
mm/dd/yy
hh.mm
-
Specified snumb
Two character remote station identification
Scheduler class name
Two digit priority code
Month, Day, Year
Hour, Minutes
The following special definitions apply to System Scheduler messages:
,
o
Active job
- Job in the System Scheduler that has not been given to the
Peripheral Allocator for execution.
o
Saved job
- Job thats given to the Peripheral Allocator for execution.
o
Finished Job - Job for which the Peripheral Allocator has given an
End-of- Job (EOJ) to the System Scheduler.
'STATUS
This command may be entered through the local or remote console. In response
to this command, the channel adapter will print the current console status to
the requesting device. This command is applicable to consoles configured on
IHUs only.
)i:
2-119
DH13-04
(
S
S
INPUT MESSAGES
INPUT MESSAGES
SYSOP
GPOP Message. This verb requests current state of "system operational bit".
Possible system replies are:
••• SYSOP: SYS OP BIT NOW ON
••• SYSOP: SyS-OP BIT NOW OFF
SYSOP OFF
GPOP Message. This verb requests that the SYS-Op bit be reset. This prevents
further scheduling of jobs by the System Scheduler until the system is rebooted
or the SYSOP ON and JRUN verbs are used to resume normal scheduling.
System Replies Possible:
••• SYSOP: SYS-Op BIT NOW OFF
*•• SYSOP: ILLEGAL ARGUMENT
*** SYSOP: CAN'T SWITCH - TRY LATER
(
SYSOP ON
SYSOUT Message. This verb requests that the SYS-Op bit be set. This verb in
conjunction with the JRUN verb will allow the System Scheduler to resume normal
job scheduling.
System Replies Possible:
••• SYSOP: SYS-oP BIT NOW ON
••• SYSOP: ILLEGAL ARGUMENT
••• SYSOP: CAN'T SWITCH - TRY LATER
(
2-120
DH13-04
S
S
INPUT MESSAGES
INPUT MESSAGES
{BLINKS}
{cnt
}
{FORMS }
SYSOUT
{JOUT
{PPS
{RSVID
{SPEC
{TOTAL
}
}
}
}
}
SYSOUT Message. This verb replaces the former LSTRE and LSTWT verbs. When it
is entered with no following modifier, the system provides online help.
SYSOUT BLINKS - Reports SYSOUT blink space.
SYSOUT cnt
- Displays jobs for specified set; "cnt" represents control
field and must specify an output type and/or destination.
Control fields for Output Types are:
ALL
APR
APN
BPR
BPN
PRT
PNC
ASC
BCD
-
All print and punch
ASCII print
ASCII print
BCD print
BCD punch
All print
All punch
All ASCII print and punch
All BCD print and punch
The destination portion of the control field may be:
Ixx - Remote ID
RMT - All remote
ONL - All online
SYSOUT FORMS
- Lists jobs which require forms.
SYSOUT JOUT
- Displays jobs waiting for JOUT.
SYSOUT PPS
- Lists jobs destined for PPS.
SYSOUT RSVID
- Lists jobs on reserved IDS.
SYSOUT SPEC
- ,Displays Job Output Specials in effect.
2-121
DH13-04
S
INPUT MESSAGES
SYSOUT TOTAL
S
INPUT MESSAGES
- Displays BLINKS, SPEC, JOUT, and a control field specifying
ALL.
System Replies Possible:
MPOPJ
MPOPJ
MPOPI
MPOPI
MPOPI
MPOPJ
. MPOPJ
MPOPJ
MPOPJ
MPOPJ
MPOPJ
INFO(001)
INFO(002)
INFO(007)
INFO(008)
INFO(012)
INFO(014)
INFO(015)
INFO(016)
INFO(017)
INFO(019)
INFO(020)
-
ERROR RETRIEVING CONSOLE TEXT; RE-ENTER
ERROR DELETING CONSOLE TEXT SEGMENT; RE-ENTER
NO RESERVED IDs CONFIGURED
PPS NOT CONFIGURED
JOB OUTPUT TABLE BUSY
CONTROL FIELD TOO LONG
UNKNOWN OPTION
ILLEGAL OPTION COMBINATION
TOO MANY CONTROL FIELDS
INVALID SPECIAL
JOB OUTPUT TABLE BUSY
CAN'T DO (verb): SYSTEM ERROR xxxxxx AT LOC. xxxxxx OF .MPOP7
xxxxxx REQUEST ALREADY OUTSTANDING FROM THIS CONSOLE
Also, the following system responses will occur, if requested:
.BLINKS:
nnnnn UNFINISHED, nnnnn FINISHED, nnnnn FREE, nnnnn ERRORS
·JOUT:
sssss
•• NO JOBS WAITING FOR DELIVERY
sssss (online)
sssss/ID (remote)
.sssss (online tape)
.sssss/ID (remote tape)
•• NO JOBS WAITING FOR FORMS
•• NO JOBS WAITING FOR JOUT
•• NO JOBS WAITING FOR PPS
•• NO SPECIALS CURRENTLY
I~
·EFFECT
·SPECIALS:
vvvvv 1st FIELD 2nd FIELD
2-122
DH13-04
,
T
TUDTl'r ..... ~~An1t~
TAPFG
GPOP Message. Operator requests a listing of the current tape configuration of
the system, along with the status of each tape device. Crossbarring is
indicated.
System Replies Possible:
10M NO.
PUB-cc
i
TAPES
(Device I)
PUB-cc
Output is a list in the following format:
(type)-(status)
X-BARRED WITH PRIM. PUB-cc.
IOM-n
{FNP-n }
TeALL {Sid
- - . {Tid
}
}
{blank }
GPOP Message. Operator requests that calls from the Front-end Network
Processor (FNP) specified be terminated. If FNP-n, Sid (stations identifier),
or Tid (terminal identifier) is not specified, all FNPs configured are
affected.
S is followed by a two-character terminal ide
T must be followed by the octal equivalent of the Terminal ide
Where:
n - FNP number (0-7)
2-123
DH13-04
\
T
l
T
IIPUT MESSAGES
INPUT MESSAGES
System Replies Possible:
FNP NOT AVAILABLE
BMX BUSY, TRY AGAIN
{A}
CORRECT FORM OF REQUEST IS "{N} CALL FNP-I
I:
1 = PRO
2 = MEM
3 = 10M (input/output controller)
4 = DISK
5 = TAPE
6 = PRINT
7 = FNP
8 = PROCES
9 = TSS
10 = SCHD
11 = SYSTEM
12 = FAULT
13
=
MME
14 = PMME
15 = DMIVTP
16 = WORK
17 = TS8
18 = OPTION
{OR}
TP BOMB {
}
{OFF}
TPE Message. Operator requests the system to set/reset the indicator to print
(ON) or not print (OFF) the aborted transaction numbers (and reasons) at the
operator's console. The format and reasons are as follows:
•• TRAX I 11iii LINE SWITCH ERR.
TPAP ABORT ERR.
TOO MNY LID ERR.
INVLD •••MSG ERR.
(
2-126
DH13-04
T
T
INPUT MESSAGES
INPUT MESSAGES
OUTBUF HDR ERROUTPUT SIZE ERRINPT TRNSLT ERROTPT TRNSLT ERRRETRVE JI ERRRETRVE JO ERRINTERACT MSG ERRTP DETL
TPE Message. Operator requests a detailed report of activities to date, and
issues a list of all active or used TPAPs and the transaction that was accepted
and completed for each.
TP MESS
TPE Message. Operator informs the TPE to send an all-points bulletin to all
associated remote terminals. When ready for input, TP MESS? is output on the
console. This message is sent to all current and future terminal users until
it is nullified by a new message or until the operator responds to TP MESS? by
pressing the End-of-Message (EOM) control button.
TP HEW
TPE Message. Operator informs the TPE to start acceptj.ng new transaction
requests. This message is used to cancel a previous TP NONEW request.
TP IONEW
TPE Message. Operator informs the TPE not to accept any new transaction
requests. The TPE continues processing requests that are already in the queue,
and any terminal that is already connected is not disconnected.
2-127
DH13-04
(
T
T
INPUT MESSAGES
INPUT MESSAGES
{lid}
TP OUT
{ALL}
(hhxx)
TPE Message. Operator requests that the output specified by lid (losical
identification) or ALL be formatted, identified, and output at the central site
printer. An optional time can be specified, but it must be expressed in hours
and hundredths of hours (hhxx), and must be preceded by a blank.
System Replies Possible:
TPE TPE TPE TPE TPE TPE:
INVALID REQUE:ST. OUTPUT DISENABLED
DUPLICATE OUTPUT REQUEST
OUTPUT REQUEST TABLE FULL
NO OUTPUT PER REQUEST
INVALID TIME FORMAT
NO OUTPUT FOR LID=xxx
TP REDI tft+++
TPE Message. Operator informs the TPE to redirect output from the first to the
second logical terminal.
(.
fff - First logical terminal
+++ - Second logical terminal
lid }
TP BEST
{***}
TPE Message. Operator informs the TPE to respawn the TPAP as indicated by the
option, and to start accepting tr·ansaction requests for that slave. This·
message is used to cancel a previous TP TERM request. Option *.* spawns all
TPAPs with appropriate flags and sends a .** STRT message to each.
TP SICT
TPE Message. Operator requests the printing of a report of the counts of
threshold error conditions. Refer to *TPE THRSHLD ••• output message for system
replies.
TP STAF
TPE Message. Operator requests that statistics be written to the statistical
collection file.
2-128
DH13-04
(
T
T
INPUT MESSAGES
INPOT MESSAGES
TP STAT
TPE Message. Operator informs the TPE to display a brief summary of
transaction activities to date. The summary includes the following:
Number
Number
Number
Number
Number
Number
of
of
of
of
of
of
transactions accepted
transactions rejected
transactions completed
physical terminals allowed and connected
physical terminals rejected
logical terminals in use
TP STAT 1d
TPE message. Operator requests the status of a specific TPAP identified in the
id field. The report includes:
Program number
Number of transactions completed and accepted
Number of spawns
Program flags
TP STRT
TPE Message.
Operator requests that the TPE be started.
TP TERM
TPE Message. Operator informs the TPE not to accept any new transaction
requests, but to continue processing those that are already in the queue. As
Transaction Processing Application Programs (TPAPs) become inactive, they are
to be terminated. When all TPAPs have been terminated, all terminals are to be
disconnected and the TPE is to be terminated.
...
{ }
TP TERM {id}
TPE Message. Operator informs the TPE to terminate the TPAP, as indicated by
the option, as soon as the current transaction is complete. Option --- causesa ---TERM to be sent to each TPAP that has the appropriate flags set.
2-129
DH13-04
- - - - _ . ._--__
T
(
T
INPUT MESSAGES
INPUT MESSAGES
{ON}
TRACE
{OFF}
GPOP Message.
Operator requests that the system trace be turned on or off.
System Replies Possible:
TRACE NOT CONFIG
INPUT INVLD
T88 ABORT
Time Sharing 8 Message. The operator requests TS8 to abort the TS8
Administrative Program (SNOMB of TS8AD) and all TS8 processes. The following
output is produced:
o A dump of the TS8 Administrative Program to SYSOUT.
o A dump to SYSOUT for each Ts8 process. This dump includes the last five
commands executed and an interpretive dump of the last 100-word trace.
f
~
System Replies Possible:
Ts8 - TIMESHARING SYSTEM NOT UP FOR ABORT
VERB NOT FOUND FOR (text entered)
UNABLE TO ABORT (number of) PROCESSES
.END $TS8-01 @tt.ttt
TS8 CANCEL
Time Sharing 8 Message.
the message buffers.
The operator requests TS8 to cancel all messages in
System Replies Possible:
TS8 - TIMESHARING SYSTEM NOT UP FOR CANCEL
VERB NOT FOUND FOR (text entered)
(
2-130
DH13-04
T
T
IIP07 MESSAGES
INPUT MESSAGES
TS8 DEBUG (01 OFF)
Time Sharing 8 Message. The operator requests that the TS8 debug switch be
turned on or off. When this switch is on, it is possible to debug portions of
the TS8 System. After the necessary debugging has been performed, the operator
must turn the switch off.
System Replies Possible:
TS8 - TIMESHARING SYSTEM NOT UP FOR DEBUG
VERB NOT FOUND FOR (text entered)
INVALID SETTING FOR TS8 DEBUG
TS8 LAST
Time Sharing 8 Message. The operator requests TS8 to print at the console the
last set of messages that were issued to all TS8 users. (A set of messages
consists of the last six messages sent to TS8 users via the TS8 MESS console
verb. If less than six messages have been sent, only those messages are
printed.) Messages are printed starting with the most recently issued.
System Replies Possible:
TS8 - TIMESHARING SYSTEM NOT UP FOR LAST
VERB NOT FOUND FOR (text entered)
TS8 MASTER (01 OFF TIME)
Time Sharing 8 Messages. The operator requests an override of the Ts8 master
user logon time interval. This verb is disabled, partially enabled, or fully
enabled by the TS8 Initialization file directive MASTER TIME OVERRIDE. (Refer
the GCOS 8 OS Time Sharing 8 Administrator's Guide for' addjt:ional information
on this directive.)
When the verb is disabled (i.e., MASTER TIME OVERRIDE=DISABALE), the master
user logon time interval cannot be overriden. Entering the TS8 MASTER verb
with any option produces the following system response:
MASTER VERB DISABLED FOR TS8 MASTER (ON OFF TIME)
When the verb is partially enabled (i.e., MASTER TIME OVERRIDE=ENABLE), the
master user logon time may be overriden. TS8 MASTER ON allows the master user
to log on, and T88 MASTER OFF prohibits the master user from logging on.
2-131
-,_..
,---------------------------------------
...
,--",
DH13-04
T
IIPUT MESSAGES
INPUT
T
MESSAGES
(
Ts8 MASTER TIME is the default value of the verb. This value turns off the
override, allowing the master user to log on only during the master user logon
time interval.
Abbreviated forms of this verb include TS8 MSON for TS8 MASTER ON and TS8 MSOF
for TSB MASTER OFF.
System Replies Possible:
Ts8 - TIMESHARING SYSTEM NOT UP FOR MASTER
VERB NOT FOUND FOR (text entered)
MASTER VERB DISABLED FOR TS8 MASTER (ON OFF TIME)
Ts8 MESS
Time Sharing 8 Message. The operator requests TS8 to prompt for a message
which will be sent to all TS8 users. When the system is ready for operator
input, the following message is output to the system console:
TS8 MESS-The operator then enters the message. It will be sent to all current and
future TS8 users until it is nullified by a new message or the TS8 CANCEL verb.
System Replies Possible:
TS8 - TIMESHARING SYSTEM NOT UP FOR MESS
Ts8 - VERB NOT FOUND FOR (verb entered)
Ts8 QUEUE FULL, TRY LATER
TS8 NEW
Time Sharing 8 Message. The operator requests that Ts8 accept new users. This
command is used to cancel a previous TS8 NONEW request, as well as to accept
new users if the TS8 Initialization file directive AUTOMATIC NEW does not
contain the default value "YES".
System Replies Possible:
TsB - TIMESHARING SYSTEM NOT UP FOR NEW
TsB - VERB NOT FOUND FOR (verb entered)
(
2-132
DH13-04
T
T
INPUT MESSAGES
INPUT MESSAGES
TS8 NOHEW
Time Sharing 8 Message. The operator requests that TS8 not accept new users.
(The status of current users is not affected.)
System Replies Possible:
TS8 - TIMESHARING SYSTEM NOT UP FOR NONEW
TS8 - VERB NOT FOUND FOR (verb entered)
Ts8 RESTRT
Time Sharing 8 Message. The operator requests TS8 to restart the Ts8 System.
This verb is appropriate for use after the entry of TS8 TERM or TS8 STOP
console verbs to terminate TS8 processing (without an intervening system
failure and no change desired to Ts8 parameterization, as established via the
TS8 Initialization file). Following a failure of the GCOS 8 System or Ts8
shared software, TS8 START must be used to reinitiate TS8 processing.
System Replies Possible:
Ts8
TS8
TS8
TS8
TS8
- TIMESHARING SYSTEM NOT UP FOR RESTRT
- VERB NOT FOUND FOR (verb entered)
INITIALIZATION BYPASSED
HAS ALREADY BEEN STARTED
IS OPERATIONAL AT hh:mm:ss PROC nnn
Ts8 SNAP xx
Time Sharing 8 Message. The operator requests that a snapshot dump of the
applicable Ts8 common data areas. The dump is output to dedicated printer PR2,
if it was configured; otherwise, the dump is written to the Statistical
Collection File (SCF). Values for xx are COM (C) for the TS8 Common Data
Segment and PRG (P) for the Ts8 Program Descriptors. If a value is not
specified (default), a snapshot of both common data areas is produced.
System Replies Possible:
Ts8 - TIMESHARING SYSTEM NOT UP FOR SNAP
TS8 - VERB NOT FOUND FOR (verb entered)
2-133
DH13-04
T
T
INPUT MESSAGES
INPUT MESSAGES
TS8 START (TS8 STRT)
Time Sharing B Message. The operator requests initiation of the TS8 System
and/or the TSB Administrative Program.
The abbreviated form of this verb is TS8 STRT.
System Replies Possible:
TS8
Ts8
TS8
Ts8
Ts8
Ts8
TS8
TS8
TS8
TS8
Ts8
TS8
TS8
Ts8
TS8
TS8
TS8
TS8
" TS8
TSB
Ts8
TS8
TSB
TsB
TS8
TSB
TsB
TS8
TS8
TS8
Ts8
TS8
TS8
TS8
TS8
IS OPERATIONAL AT hh:mm:ss PROC nnn
HAS ALREADY BEEN STARTED
- 256K IS MAX SIS CACHE SIZE
- BAD STATUS DURING SUBSYSTEM LOADING FC=xx
- CANNOT ACCESS INIT FILE (SMC BUSY) - START TS8 AGAIN
- COMMENT LOG FILE WRITE ERROR- ERROR DURING GEMORE ATTACH OF $LOAD FILE ppp xxx
- ERROR DURING GERSTR OF $LOAD FILE ppp - CHECK FILE FORMAT
- FILE: xx - MODE NOT RANDOM
- FILE SPACE GEMORE DENIED DURING SUBSYSTEM LOADING FC=xx
- FMS UNABLE TO ATTACH INIT FILE - F~~ STATUS=xxx
- FMS UNABLE TO ATTACH xx FILE: FMS STATUS =xxx
- FORMAT ERROR FOR PATCH CONTAINED IN INIT FILE (rrr)
- GEMORE MEMORY REQUEST DENIED DURING LOAD OF ROUTINE ppp
- I/O ERROR DURING READ OF INIT FILE
- IN!T FILE BLOCK SERIAL NUMBER ERROR
- INIT FILE CONTENTS NOT ASCII OR BCD
- INIT FILE NOT PRESENT
- INIT FILE REQUIRE:D SECTION LABEL NOT PRESENT
- INIT FILE TOO MANY SUBSYSTEM PATCHES, NONE APPLIED
- INIT FILE $INFO ARGUMENT LENGTH BAD
- INIT FILE $INFO ARGUMENT INVALID
- INIT FILE $INFO ARGUMENT OUT OF RANGE
- INIT FILE $INFO DIRECTIVE NOT SUPPORTED
- INIT FILE ,INFO ERROR ON CACHE SET/RESET FOR (sss)
- INIT FILE $INFO TABLE FULL FOR {GENERAL ACCESS USERID/TS8 RESTRICTED
USERID}
- INIT FILE $INFO TEXT DOES NOT CONTAIN "="
- INIT FILE $INFO TEXT LENGTH IN ERROR
.
- INIT FILE $LOAD CMDLIB NAME DUPLICATED ppp
- INIT FILE $LOAD CMDLIB SYNTAX ERROR FOR- ppp CHECK LENGTH/CONTENT
- INIT FILE $LOAD FILE NAME NOT FOUND IN DESCRIPTORS ppp
- INIT FILE ,LOAD FILE NAME SYNTAX ERROR ppp
- INIT FILE ,LOAD NAME HAS ILLEGAL PERMISSIONS ppp
- INIT FILE $LOAD PROCESSING, NO DESCRIPTOR SPACE FOR ppp
- INIT FILE ,LOAD SECTION HAS TOO MANY ELEMENTS
(
2-134
DH13-04
T
T
INPUT MESSAGES
Ts8
TS8
Ts8
Ts8
TS8
TS8
Ts8
Ts8
Ts8
TS8
Ts8
Ts8
-
INPUT MESSAGES
INIT IMAGE FILE WRITE ERROR
NEED AT LEAST 6K OF SIS CACHE
SUBSYSTEMS NOT LOADED
SUBSYSTEM xxx TOO LARGE TO LOAD
UNABLE TO ACCESS COMMON DATA SEGMENT: STATUS=ssssss
UNABLE TO ACCESS SERVICES RU INIT ENTRY: STATUS=ssssss
UNABLE TO ACCESS PROGRAM DESCRIPTOR SEGMENT: STATUS=ssssss
UNABLE TO CREATE TEMP FILE
UNABLE TO LINK SUBSYSTEM CACHE SEGMENT: STATUS=ssssss
UNABLE TO RELEASE START-UP MEMORY
UNABLE TO WIRE SUBSYSTEM CACHE SEGMENT
VERB NOT FOUND FOR (verb entered)
Explanation of these system replies may be found in the GCOS 8 as Time Sharing
8 Administrator's Guide.
Ts8 STAT
Time Sharing 8 Message. The operator requests that the status of the TS8
System be displayed on the console.
The TS8 status message printed is as follows:
*TS8 yy-mm-dd hh-mm-ss
nn users
Swaps:
pp Processes
Memory:
cc Current
Processor: hh:mm:ss subsystem, hh:mm:ss executive
where:
yy-mm-dd - Date expressed in year (yy), month (mm), and day (dd)
hh-mm-ss - Time expressed in hours (hh), minutes (mm), and seconds (ss).
The first occurrence of this field represents the current time
(i.e., time of the status message). The second occurrence (i.e.,
hh:mm:ss subsystem) represents the total processor time used by
all subsystems since Ts8 was last started. The third occurrence
(i.e., hh:mm:ss executive) 1s the total processor time for the
Ts8 Command Executive since TS8 was last started.
"'"
)
'\
2-135
DH13-04
T
T
IIPUT MESSAGES
INPUT MESSAGES
(
nn - Total number of users who are currently logged on
pp - Total number of processes that have been swapped since TS8 was
last started
cc - Amount of TS8 process local memory (in K words) currently in use
System Replies Possible:
TS8 - TIMESHARING SYSTEM NOT UP FOR STAT
TS8 - VERB NOT FOUND FOR (verb entered)
TS8 QUEUE FULL, TRY LATER
TS8 STOP (TS8 TERM)
Time Sharing 8 Message. The operator requests that the TS8 System be
terminated. All Ts8 processes and the TS8 Administrative Program (SNUMB of
TS8AD) are aborted with the NDUMP option (i.e., no snapshot dump of TS8 to
SYSOUT will occur).
System Replies Possible:
(
TS8 TIMESHARING SYSTEM TERMINATED
T88 - TIMESHARING SYSTE~ NOT UP FOR TERM/STOP
TS8 - VERB NOT FOUND FOR (verb entered)
Ts8 TERM eTS8 STOP)
Time Sharing 8 Message. The operator requests that the TS8 System be
terminated. All TS8 processes and the TS8 Administrative Program (SNUME of
TS8AD) are aborted with the NDUMP option (i.e., no snapshot dump of TS8 to
SYSOUT will occur).
System Replies Possible:
TS8 TIMESHARING SYSTEM TERMINATED
TS8 - TIMESHARING SYSTEM NOT UP FOR TERM/STOP
TS8 - VERB NOT FOUND FOR (verb entered)
(
2-136
DH13-04
T
T
INPUT MESSAGES
INPUT MESSAGES
TS8 TRACE (ON OFF)
Time Sharing 8 Message. The operator requests that the Ts8 terminal traces be
turned on or off. When this switch is on, the TS8 commands TDRL and TCMD can
be entered at the terminal to enable a trace of TS8 derails and TS8 Command
Executive events, respectively. (Refer to the GCOS 8 OS Time Sharing 8
Administrator's Guide for more information on the TDRL and TCMD commands.)
After the necessary tracing has been performed, the operator should turn the
switch off.
System Replies Possible:
TS8 - TIMESHARING SYSTEM NOT UP FOR TRACE
TS8 - VERB NOT FOUND FOR (verb entered)
TS8 - INVALID SETTING FOR TS8 TRACE
Ts8 TYPE26 (ON OFF)
Time Sharing 8 Message. The operator requests that the Statistical Collection
File (SCF) type 26 record collection switch be turned on or off. When this
switch is turned on, an SCF type 26 record is written each time a TS8 subsystem
terminates. When the switch is turned off, no type 26 records are written.
(The value for the TS8 Initialization file directive SUBSYSTEM ACCOUNTING
determines whether the SCF type 26 record collection switch is on or off when
Ts8 is started.)
System Replies Possible:
T38 - TIMESHARING SYSTEM NOT UP FOR TYPE26
TS8 - VERB NOT FOUND FOR (verb entered)
TS8 - INVALID SETTING FOR TS8 TYPE26
TS8 VOCAB
Time Sharing 8 Message. The operator requests a list of all TS8 input verbs
(messages). A list of all TS8 input verbs is printed at the console.
System Replies Possible:
TS8 - TIMESHARING SYSTEM NOT UP FOR VOCAB
TS8 - VERB NOT FOUND FOR (verb entered)
(List of all TS8,verbs)
DH13-04
2-137
_ ,..._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _"""""'"'"..........
....u_:
___________
""""""'o"""'o_"""",.m""""',~"""
~
T
(
T
INPUT MESSAGES
INPUT MESSAGES
T88 WARN tt.ttt
Time Sharing 8 Message. The operator requests TS8 to issue a message to all
users that the TS8 System will be down at tt.ttt (where tt.ttt = time in hours
and thousandths of an hour). (If tt.ttt=O is input, the previous warning
message is nullified.)
System Replies Possible:
Ts8 - TIMESHARING SYSTEM NOT UP FOR WARN
TS8 - VERB NOT FOUND FOR (verb entered)
Ts8 QUEUE FULL, TRY LATER
TS8 WHO
Time Sharing 8 Message. The operator requests Ts8 to list the status of all
TS8 processes at the console. For each TS8 process, the following is provided:
uuuuu
dddd
ssss
yymmdd
hh:mm:ss
zzzzz
xxx
ccc
(
where:
User identifier (up to 12 characters)
Station identifier (BCD)
Subsystem being executed
Login-date expressed in year (yy), month (mm), and day (dd)
Login-time expressed in hours (hh), minutes (mm), and seconds
(ss).
zzzzz - SNUMB of process
xxx - Known Process Index (KPX)
ccc - Current subsystem
uuuuu
dddd
ssss
yymmdd
hh:mm:ss
-
System Replies Possible:
TS8
TS8
TS8
TS8
- TIMESHARING SYSTEM NOT UP FOR WHO
- VERB NOT FOUND FOR (verb entered)
QUEUE FULL, TRY LATER
- NO USERS
2-138
DH13-04
......JY
T
T
INPUT MESSAGES
INPUT MESSAGES
TSn EXTEND nn
Time Sharing System Message. When a line connected to TSS is disconnected in
any manner other than typing "BYE" or "LOGOFF", TSS will hold the User Status
Table (UST) (preserve the state of the user's session) for a site-defined
length of time in anticipation of a reconnect request. This value defaults to
2 minutes, but can be changed via the INIT file. Use of this verb increments
the UST preservation time, for all USTs which are currently in hold, by nn
minutes (note that it does not change the global preservation time). The
generic usage scenario addressed by this verb is one in which most or all of
the lines connected to TSS are disconnected abruptly (e.g., an FNP failure
followed by an FNP reboot) and operations needs to override the existing UST
preservation time parameter to permit the affected users to log back in and
reconnect.
n - 1
Standard Time Sharing
n - 1,2,3, or 4 Multicopy Time Sharing
n - S
All copies of Time Sharing in execution
TSn 1901
190FF
Time Sharing System Message. These options control the generation of type 19
TSS statistical records. This switch can be set via the IN!T file as well.
n - 1
Standard Time Sharing
n - 1,2,3, or 4 MulticoPY Time Sharing
n - S
All copies of Time Sharing in execution
TSn KILL
Time Sharing System Message. Operator requests that the Time Sharing System be
terminated. TSn is snapped to the Accounting File or PR2, if dedicated.
n - 1
Standard Time Sharing
n - 1,2,3, or 4 Multicopy Time Sharing
n - S
All copies of Time Sharing in executjor!
System Replies Possible:
TSS PRGM NOT FOUND
}t'OH
KILL
2-139
DH13-04
T
T
IIPUT MESSAGES
(
INPUT MESSAGES
TSn LAST
Time Sharing System Message. Operator requests that the message being sent to
all Time Sharing System users at log-on time be output on the oonsole.
n - 1
Standard Time Sharing
n - 1,2,3, or 4 Multioopy Time Sharing
n - S
All oopies of Time Sharing in exeoution
TSn MESS
Time Sharing System Message. Operator requests an interrupt of the Time
Sharing System so that a message may be sent to the remote terminals.
n - 1
Standard Time Sharing
n - 1,2,3, or 4 MultiooPY Time Sharing
n - S
All oopies of Time Sharing in execution
-
System Replies Possible:
TSS QUEUE FULL
TSS TEXT ERR, error TRY AGAIN
When ready for input, TSn MESS-- 1s output on the oonsole. Enter the message
to be sent. The message is sent to all ourrent and future terminal users until
it is nullified by a new message or until the operator responds to TSn MESS-by pressing the END OF MESSAGE oontrol.
TSn MIl
8
Time Sharing System Message. Operator sets the minimum size of the Time
Sharing Subsystem Spaoe to s times 1024 words.
n - 1
Standard Time Sharing
n - 1,2,3, or 4 Multioopy Time Sharing
n - s
All oopies of Time Sharing in execution
System Replies Possible:
TSS QUEUE FULL
TSS TEXT ERR, error TRY AGAIN
(
2-140
DH13-04
T
T
INPUT MESSAGES
INPUT MESSAGES
TSn MSON
Time Sharing System Message.
user identifier to log on.
The operator requests TSS to permit the master
n - 1
Standard Time Sharing
n - 1,2,3, or 4 Multicopy Time Sharing
System Replies Possible:
TSS QUEUE FULL
TSS TEXT ERR, error TRY AGAIN
TSn MSOF
Time Sharing System Message. The operator requests TSS to deny the master user
identifier permission to log on.
~
n - 1
Standard Time Sharing
n - 1,2,3, or 4 Multicopy Time Sharing
System Replies Possible:
TSS QUEUE FULL
l'SS TEXT ERR, error TRY AGAIN
TSn NEW
Time Sharing System Message. Operator requests the Time Sharing System (TSS)
to accept new users. It is used only to cancel a previous TSS NONEW request.
n - 1
Standard Time Sharing
n - 1,2,3, or 4 Multicopy Time Sharing
System Replies Possible:
TSS QUEUE FULL
TSS TEXT ERR, error TRY AGAIN
)
2-141
DH13-04
M¥iP.Tf4f.%(,i.2I!l",f.iliA\tlii\Wt!fuIi&uAA,;:;r,bGlJItllfu,GfMlt.&G3iiiliiiidWlWE
T
T
INPUT MESSAGES
INPUT MESSAGES
(
TSn NOREW
Time Sharing System Message. Operator specifies that the Time Sharing System
~ill not accept new users.
The status of current users is not affected.
~-
.........
n - 1
Standard Time Sharing
n - 1,2,3, or 4 Multicopy Time Sharing
System Replies Possible:
'I'SS QUEUE FULL
TSS TEXT ERR, error TRY AGAIN
TSn - NO PGM NUMBERS AVAILABLE
Time Sharing System. An attempt has been made to start a copy of TSS.
However, there are no KPI numbers available. The startup of TSS will not be
attempted.
(
n - 1
Standard Time Sharing
n = 1,2,3, or 4 MulticoPY Time Sharing
TSn
SIZE
8
Time Sharing System Message. Operator sets the maximum size of the Time
Sharing Subsystem Space to s times 1024 words. if s isqnot specified, a status
message of the TSS copy is output.
n - 1
Standard Time Sharing
n - 1,2,3, or 4 Multicopy Time Sharing
n - s
All copies of Time Sharing in execution
System Replies Possible:
TSS QUEUE FULL
TSS TEXT ERR, error TRY AGAIN
(
2-142
DH13-04
T
INPUT MESSAGES
T
IIPOT MESSAGES
TSn SPEC
n - 1
Standard Time Sharing
n - 1,2,3, or 4 MulticoPY Time Sharing
n - S
All copies of Time Sharing in execution.
Time Sharing System Message. The operator requests an interrupt of the Time
Sharing system so that a message can be sen.t to a specific user or station.
When Time Sharing interrupt is made, and the system-is ready for operator
input, the system outputs the following message at the console.
TSn SPEC
The operator then enters one of the following messages.
uuuuu}Smessage
=dddd}Smessage
=cclSmessage
(EOM)
where:
message
uuuuu
=dddd
=cc
(EOM)
-
Specific message to be sent
User identifier (up to 12 characters)
Station identifier (octal)
Station identifier (BCD)
EOM key, used to nullify sending of previous SPEC message
The message is sent to all terminal users with the specified user or station
identification until it is nullified by the operator with either a new specific
message or by entering this message with the EOM option.
n - 1
Standard Time Sharing
n - 1,2,3, or 4 Multicopy Time Sharing
n - S
All copies of Time sharing in execution
System Replies Possible:
TSS QUEUE FULL
TSS TEXT ERR, error TRY AGAIN
specific text ERR
2-143
DH13-04
T
T
INPUT MESSAGES
INPUT MESSAGES
(
TSn STAT
Time Sharing System Message. Operator requests that the Time Sharing System
(TSS) be displayed on the master console.
n - 1
Standard Time Sharing
n - 1,2,3, or 4 MulticoPY Time Sharing
n - S
All copies of Time Sharing in execution
System Replies Possible:
.T/S QUEUE FULL, TRY LATER PLEASE
.T/S TEXT ERR error TRY AGAIN
.TSn
.TSn
-TSn
*TSn
mmddyy
MEMORY
URGENT
USAGES
tt.ttt uuu USERS
SIZES cccK=CUR.nnnK=CHG. mmmK=MAX.sssK=SWAP.1111K=LGST.
USERS xxx=URG. iiii STA.ID. www=SEC. yyyK=SIZE
tt.tt=PROC TIME qqqqK NEEDED BY zzz USERS aaa=%USED
(Refer to Output Messages for explanation of .T/S ••• and *TSn mmddY •••• )
(
TSn STH!
Time Sharing System Message.
System.
n - 1
Operator requests initiation of the Time Sharing
Standard Time Sharing
n - 1,2,3, or 4 Multicopy Time Sharing
n - S
All copies of Time Sharing configured (via $ INFO MCPTSS/n)
System Replies Possible:
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TBn
TSn
TSn
-TSS B-PRIORITY NOT DEFINED
-SUBSYSTEMS NOT LOADE:D
-TSS MAXIMUM IUSERS SET TO 999
-DEFERRED CATALOG INITIALIZED
-DEFERRED CATALOG CHECKSUM ERROR - (A)BT, (C)ONT, OR (I)NIT
-DF;FERRED CATALOG FORMAT ERROR - (A)BT OR (I)NIT
-DEFERRED CATALOG I/O ERROR
-DEFERRED FILE SPE:GIF'IES INVALID DEVICE TYPE
-UNABLE TO INITIALIZE SUB-DISPATCH QUEUE
-FMS UNABLE TO ATTACH PRMFL-xxx FMS STATUS=yy
-FILE SPACE DENIED FOR SY •• FILES
-FILE SPACE DENIED FOR FILE - xx
-TSS FILE (xx) WON'T FIT ON UNIT(yyy) WILL USE (zzz)
(
2-144
DH13-04
T
INPUT MESSAGES
T
INPUT MESSAGES
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TSn
TSn
-SUBSYSTEM xxx TOO LARGE TO LOAD
-NO PGM NUMBERS AVAILABLE
-.MPOPM QUEUE FULL
_. NO FNP AVAILABLE CHECK CONFIG
-BAD STATUS DURING SUBSYSTEM LOADING FC=xx
-FILE SPACE GEMORE DENIED DURING SUBSYSTEM LOADING FC=xx
-FMS UNABLE TO ATTACH INIT FILE-FMS STATUS=xx
-FORMAT ERROR FOR PATCH CONTAINED IN INIT FILE (rrr)
-1/0 ERROR DURING READ OF INIT FILE
-INIT FILE NOT PRESENT
-INIT FILE REQUIRED SECTION LABEL NOT PRESENT
-INIT FILE CONTENTS NOT ASCII OR BCD
-INIT FILE $INFO TEXT DOES NOT CONTAIN "="
-INIT FILE $INFO TEXT LENGTH IN ERROR
-INIT FILE $INFO TEXT ERROR
-INIT FILE $INFO PARAMETER LENGTH ERROR
-INIT FILE BLOCK SERIAL NUMBER ERROR
-INIT FILE TOO MANY SUBSYSTEM PATCHES, NONE APPLIED
-INIT $INFO "FILE" SYNTAX BAD - xxxxx
Explanation of these system replies may be found in Section 3 of this manual.
TSn TCAL
n - 1
Standard Time Sharing
n - 1,2,3, or 4 Multicopy Time Sharing
n - S
All copies of Time sharing in execution
Time Sharing System Message. The operator requests an interrupt of the Time
Sharing System so that a user or users can be terminated. When the interrupt
has been made, the system asks the operator to identify the user(s) to be
terminated by outputting the following message:
TSn TCAL -to which, the operator responds with one of the following options:
uuu ••• u
the user identifiers to be terminated
=dddd
octal station identifier of user to be terminated
=cc
BCD station identifier of user to be terminated
.ALL
terminates all users
2-145
DH13-04
T
c
T
INPUT MESSAGES
A station code of =2020 or
INPUT MESSAGES
=~~
is ignored.
n - 1
Standard Time Sharing
n - 1,2,3, or 4 Multicopy Time Sharing
n - S
All copies of Time Sharing in execution
System Replies Possible:
TSS PRGM NOT FOUND FOR TCAL
TSS QUEUE FULL
TeALL BUSY TRY LATER
TCALL TEXT ERR
TSn TERM
Time Sharing System Message. Operator requests that the Time Sharing System be
terminated. No snap of TSn to the Accounting File or dedicated PR2 will occur.
n - 1
Standard Time Sharing
n - 1,2,3, or 4 Multicopy Time Sharing
n - S
All copies of Time Sharing in execution
System Replies Possible:
TSS PRGM NOT FOUND FOR TERM
TSn WARN tt.ttt
Time Sharing System Message. Operator warns Time Sharing System users that the
system will go off the air at tt.ttt. A tt.ttt=O input n~llifies any previous"
warning
message.
n - 1
Standard Time Sharing
n - 1,2,3, or 4 Multicopy Time Sharing
n - S
All copies of Time Sharing in execution
System Replies Possible:
TSS QUEUE FULL
TSS TEXT ERR, error TRY AGAIN
2-146
DH13-04
T
T
INPUT MESSAGES
INPUT MESSAGES
TYPFG
GPOP Message. Operator requests a listing of the current configuration of the
system, along with the status of each peripheral unit. Crossbarring is
indicated and the number of available llinks for each mass storage device is
shown. There is one entry for each PUB used.
System Replies Possible:
Output is a list in the following format:
*T-Y-P-F-G*
xxxx-K 1-PRC
1-08-14 MS0450 PACKI-C155
1-08-15 MS0450 PACKI-H612
AVAIL-73895
AVAIL-86157
1-09
1-10
1-28-01
1-30-00
X-BARRED WITH PRIMARY 1-08
X-BARRED WITH PRIMARY 1-08
MPC9
CLS-O DENS-DE
SCC
ASGN- VIDEO
1-60-01
1-61-01
1-62-01
1-63-01
PRT401
PRT401
CRZ301
CP300
DLINK-8 USAGE-40
DLINK-9 USAGE-34
RELEASED
2-147
DH13-04
U
U
IIIPUT MESSAGES
INPUT MESSAGES
UDTAPE ddd
Operator Interface Message. Operator requests that magnetic tape device ddd,
previously assigned to a program by the DDTAPE verb, be released back to the
system.
System Replies Possible:
UDTAPE: DEVICE NAME NOT ASSIGNED
The activity has already terminated.
UDTAPE: DEVICE NAME NOT FOUND
The device name table does not contain the device named with the UDTAPE
verb.
ULSAC
Allows the console operator to unlock the specified SAC.
System Replies Possible:
None.
URAKE xxx
GPOP Message. Operator requests that a name be removed from the name table.
TY1 - TY4 cannot be removed and permanent mass-storage devices cannot be
removed.
xxx - Device name
System Replies Possible:
NAME INVLD
NAME NOT FOUND
CANT NAME/UNAME MASS ST
2-148
DH13-04
U
U
INPUT MESSAGES
INPUT MESSAGES
UNDED xxx
GPOP Message. Operator undedicates the named device so that it may be
reassigned by device type as well as by name.
xxx - Device name
System Replies Possible:
MPOPE ERROR(102) -xxx NAME NOT FOUND
{SNB=sssss}
UNJOUT {SID=s1d }
SYSOUT Message. Operator requests that a job in SYSOUT, being held for JOUT,
no longer be held for JOUT.
System Replies Possible:
MPOPF INFO(001) - ERROR RETRIEVING CONSOLE TEXT - PLEASE
REENTER
MPOPF INFO(002) - ERROR DELETING CREATED SEGMENT
MPOPF INFO(012) - GEOT QUEUE FULL, PLEASE TRY LATER
MPOPF INFO(014) - INVALID NUMBER
MPOPF INFO(017) - ILLEGAL REQUEST FORMAT
URGe sssss uu aa
GPOP Message. Operator requests to either change the urgency or display the
existing urgency.
uu - The new urgency desired, in decimal. If the uu value is greater than
40, the urgency is reset to 40. Urgencies greater than 40 are possible
only through the application of a site option patch.
aa - Current activity number, in decimal. If the activity field contains an
S, the SNUMB field contains the SID of a SNUMB in SYSOUT.
2-149
DH13-04
U
U
INPUT MESSAGES
INPUT MESSAGES
To change the urgency for the current activity only, the operator uses the
entire message. If the activity number of the job agrees with the actj,vity
number input by the operator, the urgency is changed for the acti vi.ty only and
the old urgency applies for each activity after the current one. If the
activity number of the job differs from the one input by the operator, the
request is denied and the operator' is notified.
To change the urgency of the entire job, the operator inputs the message,
leaving the activity number blank.
To request a display of the existing urgency of a job, the operator inputs the
message, leaving both the urgency and the activity fields blank. If the job is
in the .CRSNB table, or in SYSOUT the system returns the followj,ng infor1!lati.ve
message.
URGC sssss aa
System Replies Possible:
.URGC sssss uu
sssss uu aa ACT I INVLD
sssss uu aa SNUMB INVLD
sssss uu aa URGC INVLD
sssss uu aa SIn INVALID
SSSBS CANT FIND SNUME
URGC REQUEST APPLIED TO
nnnn JOBS
-
Statement of existing urgency of job
Invalid activity number
Invalid Job sequence number
Invalid urgency
Invalid SYSOUT request
Job not found in .CRSNB table
Job found in SYSOUT and there were nnnn
undelivered jobs with SNUMB sssss
NOTE: For a job in SYSOUT, an urgency of 00 means "hold this job".
will not be delivered until it is given a non-zero urgency.
2-150
The job
DH13-04
V
V
IIPUT MESSAGES
INPUT MESSAGES
VFe 1ccdd name
GPOP Message.
Allows the operator, to load a specific VFC image.
name - three- to six-character VFC image name. The first character
must be alphabetic and special characters are not allowed.
System Replies Possible:
10M INVALID
CHI INVALID
DEV INVALID
INVLD VFC/PTRAIN FORMAT
VFC REQ FOR 300/303 ILLEGAL
NOT TRN PRTR
ASGND CANT LD BFR
*{iccdd} RLSED
{sssss}
{name
}
CHECKSUM ERROR {TRAIN} {identifier}
{VFC } {block no. }
*{iccdd}
{identifier}
{sssss} RLSED {name
} NOT ON CATALOG
*{iccdd}
{sssss} RLSED
SECTORI
nnnnnn INVALID
*{iccdd} RLSED {TRAIN} ILLEGAL REQUEST FOR THIS PRINTER TYPE
{sssss}
{VFC}
{name
}
*{iccdd} RLSED {identifier} I/O ERROR ON CATALOG/IMAGE FILF.:
{ssssa}
{block no. }
*{iccdd}
{sssss} RLSED
{TRAIN}
ERROR ON {VFC } LOAD
*{iccdd}
{sssss} RLSED
TRAIN MOUNTED xxxxxx REQUESTED ID WAS yyyyyy
*{iccdd}
{sssss} RLSED
I/O ERROR ON' READ STATUS COMMAND
2-151
D813-04
V
V
INPUT MESSAGES
INPUT MESSAGES
VIDEO
GPOP Message. Operator restores VIDEO program display after the TI5 has been
returned to the VIDEO mode. Data display appears on the screen. This applies
only if VIDEO was previously running on TY5, then TY5 temporarily used as an
operator console.
System Replies Possible:
VIDEO CANT START - NO TY5 OR DtlP SeT ADDR
VOCAB
GPOP Message. Operator requests a list of all input system messages (except
those which are suppressed). A list of all input system messages known to the
system is typed out on the console.
VOCABU
GPOP Message. Operator requests a list of all user input messages. A list of
all input messa.ges that were implemented by the user is printed on the
console. If none have been implemented the following message is printed:
NO USER VERBS.
VOID
XlCC:X:X
GEOT Message. Operator on one system requests that VERB xxxxx be voided on
another system. The systems must be running full Common File Facility or be
shared.
System Replies Possible:
MPOPF INFO(012) - GEOT QUEUE FULL, Pl.EASE TRY LATER
MPOPF INFO (018) - ILLEGAL REQUEST IN A NONSHARED SY STEM
2-152
DH13-04
c
W
W
INPUT MESSAGES
IRPUT MESSAGES
---,----_.
{LIST
{--
{blank
}
{ALL
}
{workstation name}
{
{ABORT
{
}
}
}
}
{ALL
}
{WORKSTATION NAME}
{T2
}}
fnPE2}}
{
WORKST
Operator Interface Message. Operator requests to list or abort known
workstati.ons in the system. The first option must be either LIST or ABORT.
LIST is requested, the second option may be:
If
blank - List the names of all workstations in the system
ALL - List the names of all workstations in the system
workstation name - List all the SNUMBs in the specified workstation
If ABORT is requested, the second option may be:
ALL - All workstati.oDs in the system are aborted.
workstation name - Only the specified workstation is aborted.
If ABORT is requested, the third option may be:
T2 or TYPE2 - Normally, an abort request is not honored for a process
executing in a TYPE2 critical section. This option allows the
operator to override this constraint. This option can only be
used in extreme cases, as it may cause GCOS crashes or process
disasters.
NOTES: 1. The second and third options may be reversed.
2. "ALL" is a keyword in the WORKST command syntax and must not be used
as a workstation name.
System Replies Possible:
For LIST - KNOWN WORKSTATIONS: w••• w •••••
or
- SNUMBS FOR WORKSTATION w••• w: sssss •••••
2-153
DH13-04
W
,; ,INPtn:MESSAGES
W
·'I,.PUT,MESSAGES
Error Messages:
1ST WORKST OPTION ~ruST BE LIST OR ABORT
xxxxxxx IS AN ILLEGAL OPTION FOR WORKST
:xxxxx DUPLICATE OPTION
CAN ''1' DO wOEKS'r: SySTE .... ERROR
Peripheral Allocator Message. Protected file recovery was provided, but SHARD
will be spawned again to refresh its entry in the system scheduler file because
the scheduler was cleared.
Operator Action:
None •
• ABT sssss-aa ttt.ttt (abort reason)
Termination Message. Activity aa was aborted by the system for the reason
stated. Further explanation concerning the abort reason may be found by
referencing the GCOS ~ OS Programmer Messages And Abort Codes manual.
Operator Action:
None.
4-2
DH13-04
A
A
OUTPUT MESSAGES
OUTPUT MESSAGES
*ABT S888S-88 @tt.ttt (abort reason)
ROLLBACK?
Termination Message. An abnormal termination condition exists that affects job
sssss, and the JROLL option was specified in the JCL. Operator is asked if a
rollback to the nearest checkpoint is desired.
Operator Action: Enter YES to affect the rollback if the abort reason code
indicates the error condition is operational in nature (i.e., hardware
problems, operator error), as opposed to programming errors.
Enter NO to continue termination activities. The message is repeated without
the "ROLLBACK?" to verify the termination of the activity. Any other response
causes the message to be repeated every 30 seconds until a YES or NO entry is
made.
$ ACCBUF CARD WAS REJECTED-ASSUME DEFAULT
Startup Message. The $ ACCBUF statement was rejected for one or more of the
following reasons:
1. Nonoctal digits in the first two numeric fields
2. Nondecimal characters in the third field
3. Field not proper size
The same default values that are used when no $ ACCBUF statement is present
will be assumed.
Operator Action:
None.
ACCRra CONTIN PROCESSING BAD
GPOP Message.
Statistical accounting continuation could not be done.
Operator Action:
None.
4-3
DH13-04
c
1
A
OUTPUT MESSAGES
OUTPUT MESSAGES
.lCCOUITIRG FILE FATAL ERROR
Rollcall Message.
An unrecoverable 1/0 error occurred on the accounting file.
Operator Action: If tape accounting is being used, reboot, using a different
tape andlor tape unit. If disk accounting is being used re-edit the accounting
files to a different location •
• ACCT FILE COMPLETED
{DMr i ccc dd}
{RDY i ccc dd}
••••ERROR OR OLD lCer FILE-mmmmmm GOOD RECORDS (Y1Y) (optional)
GPOP Message. An accounting tape switch identified a completed tape and
notifies the operator of any errors.
Number of good records on the file
yyy - Type of trailer label attempted when error occurred (EOR or EOF)
mmmmmm -
Operator Action:
Save completed tape for accounting function •
• ACCT FILE COMPLETED-FILE1(name1), STARTING Slsssss CURRENT-FILE2(name2)
••••ERROR OR OLD ACer FILE-nnnnnn GOOD RECORDS. (optional)
GPOP Message. A disk system statistical collection file was closed. The SNUMB
of the automatically generated purge job to dump the completed file is
identified.
name1 - 12-character BCD name as shown on $ ACCOUNT statement.
name2 - 12-character BCD secondary name as shown on $ ACCOUNT statement.
nnnnnn - Number (decimal) of good records. Block serial number if error
encountered.
Operator Action:
sssss.
When the SNOMB identified asks for privity, respond RUN
4-4
DH13-04
A
OUTPUT MESSAGES
A
OUTPUT MESSAGES
• ACCTNG BUFSZ TOO BIG
Startup Message.
1604 words.
The buffer size on the $ ACCOUNT statement is greater than
Operator Action:
Correct the $ ACCOUNT statement and continue •
• ACTlVE BOOTLOAD TAPE SPECIFIED ON FOLLOWING CARD
Startup Message. The bootload tape device cannot be specified because it is
used during all of the startup operation.
Operator Action:
None •
• ACTlVE READING TAPE SPECIFIED ON FOLLOWING CARD
Startup Message.
The reading tape device is reserved during startup operation.
Operator Action:
None.
ADDITIONAL OPTIONS: ALL,HCM,SOFT,SLV,W/II,P/II,REAL,HPURE,NOHE
DEVICE,DUMPO,(-)SD.IXX,.MXIXX,PH.IIX,PSH,SSF,
HIS,TRC,COM,PTW,OILY,EXEC,FLTIPX,CACHE,SDC,
AUTO,PAED,RES,END
Dump Message. If the DATA CAPTURE OPTION is ALL, the additional options
selected override the ALL option; otherwise, it is used to supplement the DCAF
option.
(U)SE causes DUMP to use the options specified on the $ANSWER statement.
(N)ONE should be used if a dump should not be taken.
The following list of options affect the amount of data written to the dump
device, and should be used when dumping to tape, disk, or prianter. Options
which have changed are preceeded by a single asterisk (.); new options are
preceeded by a double asterisk ( •• ).
ALL
- Dumps all known workspaces from 1 to 777.
4-5
DH13-04
A
OUTPUT MESSAGES
A
OUTPUT MESSAGES
HCM
- Dumps workspace 1.
SOFT
- Dumps all workspaces from 4 to 27.
SLV
- Dumps all workspaces from 30 to 777.
*W/xx
- Dumps workspace xx.
*W/xx-yy - Dumps workspaces xx through yy.
*P/xx
- Dumps (PX xx (DUMP internally converts the (PX number to a
workspace number).
**FLT(PX - Dumps the faulting KPX or program at the time of the system
interruption.
**EXEC
- Dumps all the (PXs in execution on an active processor at the
time of the system interruption. The number of programs selected
should range from one to six, depending upon the number of
processors in use.
NONE
- Display the SELECT DEVICE: message.
DEVICE
- Display the SELECT DEVICE: message.
END
- Causes dump to go to restart.
ONLY
- Only dumps the option specified.
The following options can be used to print a portion of selected working
spaces, and should be used when the amount of data to be captured is small
enough to be printed quickly on any configured printer, such as PR1. Several
of the options may be preceeded by a hyphen to indicate "not". For example,
HCM -SD.CR would dump all of HCM, except the CR segment; -PH.SSA would dump all
the known workspaces without the SSA segment.
NOTE:
These options can ONLY be used for dumping to printer.
REAL
- Prints real memory pages only.
NPURE
- Prints the modified real memory pages
**DUMP 0
- Prints the .MDUMP abort snap contained in file DUMPO.
4-6
DH13-04
A
A
OUTPUT MESSAGES
OUTPUT MESSAGES
(-)SD.xxx - Prints the specified GCOS 8 system segment.
(-).Mxxx
- Prints the specified GCOS 8 module.
(-)PH.xxx - Prints the specified segment for one or more workspaces.
PSH
- Prints all the process control segments for all selected
workspaces.
SSF
- Prints information about all programs known to the system.
(-)HIS
- Prints the formatted history register segment, SD.HDP.
(-)TRC
- Prints the formatted system trace segments, SD.TTO and SD.TT1.
COM
- Prints the system communications segment, SD.COM.
PTW
- Prints the page table segment (PH.PTO) for all selected
workspaces.
CACHE
- Prints the contents of CACHE memory for the DPS 8 or the DPS
8000.
SDC
- Prints the contents of various RADS (Rapid Access Data System)
segments (SD.CCH, etc.)
(-)AUTO
- Prints the contents of the system AUTOLOAD file.
(-)PAED
- Prints the contents of the .GPAED portion of all $SYSTEM files
used for the current boot.
(-)RES
- Prints the contents of the reserved memory for the DPS 88 or DPS
90 processors.
The default options, which are underscored, are automatically printed when
options other than NON are selected from the console. They can be specifically
excluded by the delete feature (-) or by the ONLY option. Except for
exclusions, they need not be entered on the console.
A line ending with a comma indicates that a continuation line is requested.
If the operator enters an invalid option name (either an invalid name or a
misspelled name), .MDUMP will issue the following message to the console:
INVALID OPTION "OPTION"
INPUT ERROR, RE-INPUT
4-7
DH13-04
A
A
OUTPUT MESSAGES
OUTPUT MESSAGES
The operator must then reenter response.
When the options specified for the dump have been executed, the following
message is issued on the console:
ADDITDIONAL OPTIONS:
The operator can respond with any of the valid options for the dump message.
This allows the operator to specify additional dump options. A response of END
or EOM (End of Message) causes .MDUMP to proceed to the Restart Operation.
The $ ANSWER statement in the System Startup job stream can be used to
pre-answer the .MDUMP options message for a dump to printer operation. In
preparing the Startup statements, the options that can be entered from the
console can be specified on $ ANSWER statements. When these are specified, the
options message will not be issued to the console. The specified options will
be invok~d automatically when a dump to the printer is requested. Note that
the default options need not be specified unless they are to be deleted from
the dump.
-ADDRESS TO BE PATCHED IS TOO HIGH ON CARD
Startup Message. The address of the program to be patched, shown in columns
1-6 of the OCTAL statement, is above the limits of the program.
Operator Action:
Correct the OCTAL statement and resubmit.
AFTER COMPLETION OF GESEP, RETURN INPUT TAPES TO OPERATIONS
FOR DISPOSITION
Summary Edit Program Message.
the tapes to operations.
Operator Action:
After Summary Edit Program has finished return
Return the tapes.
4-8
DH13-04
A
OUTPUT MESSAGES
A
OUTPUT MESSAGES
-AGAIN message
Pheripheral Allocator Message. The "MNT", "ROY", and "RNG" forms of the .MEDIA
message are reissued, after two minutes if the operator has not performed the
requested action. When reissued, the meaning and the requested action are the
same, but the -MEDIA is replaced with -AGAIN.
-_. sssss: ALL BUT ONE PROCESSOR IS CURRENTLY RELEASED
Memory Release Message. MEMREL program spawned by RELSEC request. The MEMREL
program normally temporarily releases all except one active processor; in this
case, there were multiple processors configured, but only one was active.
Operator Action:
None.
--- sssss: ALL BUT OlE PROCESSOR WILL BE TEMPORARILY RELEASED
AND REACTIVATED WHEN ME!IlRY RELEASE IS COMPLETED
Memory Release Message. MEMREL program spawned by RLSEC request. This message
is informative and occurs when there are multiple active processors at the time
of the RLSEC request.
Operator Action:
None.
ALL WILL BE USED AS DUMP OPTION.
Dump Message. A DCAF error has occured.
default DCAF option.
Operator Action:
The ALL option will overwrite the
None.
ALLOCATIOI IMPOSSIBLE - devioe name
Peripheral Allocator Message. An attempt was made to allocate more devices
than are configured, or more space on a device than allowed.
Operator Action:
Refer to Appendix C for device descriptions.
4-9
DH13-04
A
A
OUTPUT MESSAGES
OO:TPUT MESSAGES
-ALTERNATE Acer FILEn PURGE NOT COMPLETED, Acer REQUEST DENIED
GPOP Message.
progress.
The ACCNT request was denied because purge is already in
n - number of the file now being purged
Operator Action: Try ACCNT when current purge is complete.
-ALTERNATE ICer FILEn PURGE NOT COMPLETED, WAIT OR IGRORE •• W/I?
GPOP Message. The previous purge was not completed, but a second purge
forced. The operator must inform the system whether to wait (losing incoming
statistical collection data until purge completes) or to ignore the switch
files (possibly destroying the first purge data).
n - number of the file already purging
W - wait
I - ignore
Operator Action:
Enter W - Statistical collection data will be lost until current purge is
completed.
Enter I - Data will be collected but it will be written in current purge
file, possibly destroying the currently purging file.
-ALTERNATE TRACIe TABLE CHECICSUM ERROR
Startup Message.
being read.
A bad checksum was found while the alternate track table was
Operator Action:
None.
4-10
DH13-04
A
A
OUTPUT MESSAGES
OUTPUT MESSAGES
-ALTERNATE TRACKS ASSIGNED OR DEVICE SPECIFIED ON FOLLOWING EDIT
CARD
Startup Message. The Removable Store Initialization Program (RSIP) assigned
alternate tracks on the device specified on the indicated $ EDIT statement.
Startup does not edit such devices.
Operator Action:
pack.
Either reformat the pack through Startup or process a new
-ATT lIT ssxx pp 1coodd sssss (s.a.
(operator response)?
= S88888888888
to= nn)/(pppppppppppp dn)
Exception Processor Message. An Attention status, with a substatus of ss,
occurred on the specified device pp during attempt to execute the instruction
indicated by the code xx.
r~ 1-tJff{ A~ IIV1E'!;fr
-...~'1 RM t WA'ft
where:
liT
ss
xx
pp
{N r«1.JIl \
-
Status was returned on an Initiate/Terminate interrupt.
Octal substatus code (refer to Appendix D).
Instruction code (refer to Appendix A).
Indicates one of the following device types:
CP = Card Punch
CR = Card Reader
DP = Disk Pack
DS = Disk
MT = Magnetic Tape
PR = Printer
TY = Console
i-Input/output controller number
ccc - Channel (PUB) number
dd - Device number
sssss - SNUMB
dn - Magnetic tape density from word 0 of the SCT
p ••• p - Magnetic tape position data from word 1 of the SCT
Operator Action: One or more of the following explicit responses may be
available. These are punctuated with a question mark (?) and the keyboard is
enabled to allow operator input.
R - Retry I/O.
4-11
DH13-04
A
OUTPUT MESSAGES
(
A
OUTPUT MESSAGES
U - Return status to the user.
B - Manually backspace the device and retry I/O.
S - Type the disk seek address. The Attention message will then be
repeated.
M - Move all messages from the failing device to an alternate console.
The following implicit options are not printed on the console by the Exception
Processor, but are always available:
A - Abort the job.
X - Exchange the device for another device (may be combined with the R or B
option).
If the message is not punctuated by a question mark (?) the keyboard will not
be enabled. In this case, an interrupt from the device is required after
correcting the existing condition. The following options may be seen:
RDY - Ready the device.
BSP - Manually backspace and then ready the device.
U - Status is sent to the user program. Ready the device.
A variety of conditions may have caused the Attention message to be printed,
depending on the device type. The activity required before responding at the
console may involve various attempts to power on, ready devices, correct device
malfunctions, or respond to device empty conditions.
EXAMPLE:
-ATT T 4025 DP 0-08-26 1304Z RU?
An Attention condition exists on a terminate interrupt to the disk pack on
IOM-O, channel 08, device 26, while running SNOMB 1304z •. While executing a
write-continuous (25) instruction, the system found the device to be offline
(40). After correcting any malfunction, if possible, the device should be
placed online and in a ready condition. The options available are to retry the
I/O (R), let the user program try to recover (U), abort the job (A), or switch
to another device if device 26 is inoperable (X).
-ATTEMPTED ACCESS BEYOND FILE LIMITS
Startup Message.
Access was attempted at a location beyond the file limit.
Operator Action:
Increase the file size for this file.
c
4-12
DH13-04
A
A
OUTPUT MESSAGES
OUTPUT MESSAGES
{ACCNT}
ATTI {DUMP} TAPE 1-ooo-dd, EOM FOR RETRY, 0 FOR OPTIOllS
{JRNL }
Dump Message. An Attention status was detected on a I/O operation involving
the device to which the tape aocounting or the dump is directed.
Operator Action: Ready the device and press EOM or enter 0 and DUMP will
repeat the Dump device option message:
SELECT DEVICE:
-AUTOBOOT NOT POSSIBLE, LOADFILE NOT DEFINED
Startup Message.
The $LOAD section is not acceptable.
Operator Action:
Replace the $LOAD section from the card reader.
{ FM CARD READER }
-AUTOLOAD ABORT, BOOT {
}
}
{ FROM TAPE
Dump Message. The attempt to load Startup card images from the device
indicated on the $ AUTOLOAD statement was unsuccessful.
o If the Startup program originally resided on punched cards, the console
message AUTOLOAD ABORT, and BOOT FM CARD READER is issued.
o If the Startup program originally resided on magnetic tape, the console
message AUTOLOAD ABORT, and BOOT FROM TAPE is issued.
Operator Action: Determine whether a hardware problem exists.
from the original storage medium.
If not, boot
\I
)
4-13
DH13-04
A
OUTPUT MESSAGES
A
OUTPUT MESSAGES
-AUTOLOAD DEVICE UNDEFINED NO SUITABLE DEFAULT
Startup Message. The autoload device was not defined on the $ 10M statement
and there is no suitable alternate device.
Operator Action:
Change the $ 10M statement to define autoload device.
-AUTOLOAD FILE DEVICE NOT SUITABLE
Startup Message. Device selected by user is not usable, or startup cannot find
a usable device, for autoload file on a FIPS disk device. The autoload file
device, if a FIPS mass storage device, must be the name of the device with the
lowest logical device of the physical device. The device name must also be
specified on a $ GCOSFIL record.
Operator Action:
reboot.
Change $CONFIG section to follow the above criteria and
-AUTOLOAD/LOADFILE MOST BE OR GCOSFILE DEVICE
Startup Message. The autoload and/or loadfile device was not indicated on the
$ GCOSFILE statement.
Operator Action:
Change the $ GCOSFILE statement and reboot.
4-14
DH13-04
SBCTIOI 5
OUTPUT MESSAGES BEGIDIIG WITH THE LETTER B
-BAD BLOCK: 0 01 SSFILE. MUST EDIT SSFILE CARD lGAII
GPOP Message. An error occurred when Startup processed the $ SSFILE statement,
causing an invalid block 0 on the System Scheduler file.
Operator Action: Check the $ SSFILE statement for errors.
statement, if necessary, and reboot.
Revise the
-BAD CARD TYPE ERBOR: BACK:SPACE TO RETRY OR EID MESSAGE TO IGIORE
Startup Message. A BCD statement other than EOF, OCTAL correction, OBJECT, or
DKEND was in the $LOAD section; or the next statement read after $ OBJECT was
not $ DKEND.
Operator Action: Determine the situation; then remove, correct, or reorder the
statements as required. Enter B. Press EOM to ignore.
-BAD CLASS BEADERS 01 SSFILE. MUST EDIT SSFILE CARD lGAII
GPOP Message. An error occurred when Startup processed the $ SSFILE statement,
causing invalid class headers on the System Scheduler file.
Operator Action: Check the $ SSFILE statement for errors.
statement, if necessary, and reboot.
Revise the
-BAD DATA FORMAT 01 IMCV TAPE
System Input Message.
wrong format.
Operator Action:
The magnetic tape is a bad tape or was created with a
None.
5-1
DH13-04
c
B
B
OUTPUT MESSAGES
OUTPUT MESSAGES
-BAD DEC( 01 AUTOLOAD
Startup Message. It booting is from cards, the bootload deck used in Startup
is not the same version as Startup itself. If booting is from Autoboot, there
is a Startup error in memory.
Operator Action:
Reboot.
-BAD DECIFILE BCD CARD CHECKSUM
Startup Message.
The job stream file was destroyed.
Operator Action: Reinitialize the job stream file by one of the four following
methods. Always answer PARTIAL to INITIALIZE and YES to PROCESS $ READIN.
o Change the file name on the $ DECKFILE statement in the $CONFIG section.
o Change the autoload device.
o Initialize the autoload device.
o Answer YES to CLEAR AND OVERWRITE EXISTING DECKFILE.
-BAD J- DATA FOR sssss - CAN'T RELEASE SPACE
System Scheduler Message. Scheduler found a zero device name on J* record for
job sssss and must bypass space release invocation. Informative message only.
Operator Action:
None.
-BAD NAME ON SSLOAD, ONLY THE FOLLOWING ALLOWED:
Startup Message.
The $ SSLOAD statement contains an illegal entry.
Operator Action: Revise the $ SSLOAD statement in accordance with allowable
entries, and reboot.
5-2
DH13-04
B
B
OUTPUT MESSAGES
OUTPUT MESSAGES
BAD STATUS READING MCA
STATUS WAS: xxxxxxxxxxxx xxxxxxxxxxxx
YYTrIYTrIyyy
zzzzzzzzzzzz
Startup Message. Startup reads the MCA configuration files for all lMU/IMXs.
An error was encountered reading this file over channel 3. The xxxx field will
be the octal status return and DCW residue from the I/O.
The yyyy field will be one of the following interpreted status messages:
CHANNEL POWER OFF,
LOST INTERRUPT,
ILLEGAL,
CHANNEL READY, NORMAL TERMINATION
CHANNEL READY, ADAPTER FAILURE
CHANNEL READY, ILLEGAL
ATTENTION (DISKETTE), WRITE INHIBIT
ATTENTION (DISKETTE), SEEK INCOMPLETE
ATTENTION (DISKETTE), DEVICE NOT PRESENT
ATTENTION (DISKETTE), DEVICE INOPERABLE
ATTENTION (DISKETTE), DEVICE IN STANDBY (DOOR OPEN)
ATTENTION (DISKETTE), ILLEGAL
DATA ALERT, TRANSMISSION PARITY ALERT
DATA ALERT, CHECK CHARACTER ALERT
DATA ALERT, ILLEGAL
COMMAND REJECT, INVALID OPERATION CODE
COMMAND REJECT, ILLEGAL
ATTENTION (MCA) , MCA EXECUTIVE F/W ERROR
ATTENTION (MCA), MCA OVERLAY F/W ERROR
ATTENTION (MCA), CONNECT TIME OUT
ATTENTION (MCA), ILLEGAL
DATA ALERT (MCA), DATA OVERFLOW ON LOAD
DATA ALERT (HCA), DATA UNDERFLOW ON LOAD
DATA ALERT (HCA), ILLEGAL
COMMAND REJECT (MCA) , INVALID SEQUENCE
COMMAND REJECT (MCA), INVALID PATH NAME
COMMAND REJECT (HCA), INVALID REQUEST FORMAT
COMMAND REJECT (HCA), CONTINUE BIT ERROR
COMMAND REJECT (MCA) , INVALID BLOCK HEADER
COMMAND REJECT (MCA), ILLEGAL
UNEXPECTED HAIIT. SESSION CONTINUATION
UNEXPECTED MCA RESPONSE DATA
MISMATCHED MCA BlTE COUNT
~
)
5-3
DH13-04
B
OUTPUT MESSAGES
B
OUTPUT MESSAGES
UNEXPECTED MAINT. SESSION NORMAL TERM.
UNEXPECTED MAINT. SESSION ABNORMAL TERM.
UNEXPECTED 10M STATUS xx
where the xx field is the octal lMU/IMX central or channel status error
code.
UNEXPECTED DCW RESIDUE
UNEXPECTED SERVICE PROCESSOR STATUS:
ssssssssssss
where the s field is a message in the form of:
«xxxx»
lMU OR SERVICE PROCESSOR INFORMATIVE MESSAGE
where the xxxx field is defined by the lMU/IMX or DPS 8000 service
processor. If no lMU/IMX or service processor status is received when
expected, then the following status message is substituted:
«9999»
NO SERVICE PROCESSOR STATUS RETURNED
The only acceptable service processor status value (xxxx) 1s the one for
"READY" - noooon, otherwise it is treated as an error.
The zzzz field is a retry question in one of the following forms depending on
whether a diskette was being used as a result of the command:
RETRY, ABORT/RETRY, EXCHANGE DRIVE/RETRY, QUIT (RAXQ)?
RETRY, ABORT/RETRY, QUIT, (RAQ)?
Operator Action: NOTE: A command to the MCA may require more than one I/O to
complete.
Enter R to indicate a retry of the current I/O which may have encountered
an error.
A to indicate a retry of the entire command sequence and not just the
I/O entry.
Q to indicate that Startup should not try to continue with this MeA
command but return an error statuB to the calling routine which may
or may not be acceptable (the calling routine will indicate with an
appropriate message if Startup will continue with the error or
abort).
5-4
DH13-04
B
B
OUTPUT MESSAGES
OUTPUT MESSAGES
X to indicate a desire to change the drive in which the MCA PHX or
PRO diskette is being read. Startup will wait for the RyR before
continuing (i.e., when the operator responds with "Y" then Startup
will abort the current MCA command and retry the entire command
using the alternate drive) and issue the following message:
EXCHANGE DISKETTE DRIVES, RESPOND Y WHEN READY
-BAD TAPE LABEL
Startup Message.
files.
A labeled edit tape has an invalid or missing label between
Operator Action:
Retry with a correctly labeled edit tape.
-. BASE CARD MOST PRICEED • MCT 1$ CIU CARDS
Startup Message.
Misplaced $ BASE statement.
Operator Action:
Correct the $ BASE card placement and reboot Starup.
-BCR Mr i-occ-dd sssss-aa L=,F=, CEA
File and Record Control Message. The block count in the trailer label does not
agree with the block count in the file control block.
L - Trailer label block count
F - File control block count
Operator Action: Enter C to continue execution, ignoring the label check;
enter E to force an end-of-file condition; enter A to abort the job.
-BCR sssss-aa Mr i-ccc-dd L=nnnn F=mmmm CEA
Standard COBOL-68 1/0 System Message. The block count in the trailer label of
an input reel does not agree with the block count of the blocks processed.
nnnn - Block count from trailer label
mmmm - Block count from file's programmed block counter
Operator Action: Enter C to continue execution; Enter E to force the
end-of-file condition for this file; enter A to terminate the activity.
5-5
DH13-04
B
B
OUTPUT MESSAGES
••• 8888S:
OUTPUT MESSAGES
BEGIDIIG MEII)RY RELEASE PROGlllM
Memory Release Message. MEMREL program spawned by RLSEC request.
is informative and identifies the memory release program SNUMB.
Operator Action:
This message
None •
• BINARY CAE II PATCH SBCTIOI
Startup Message.
There is a binary statement in the octal patch section.
Operator Action:
Remove the statement and reboot •
• BIIARY DEC[ TOO BIG
Startup Message. A binary program or program combination (job stream followed
by the data file) input to the Startup $INITIALIZE section is too big for the
buffer area assigned. This situation is very improbable.
Operator Action:
Delete the deck combination •
••BLOc[ SERIAL NO. ERROR, TAPE BSI xxxxxx SHOULD BE yyyrn
{A)BORT, {C)OHTlIUE
Restore Message. While reading a save file, the restore program found block
serial number = xxxxxx and expected block serial number = yyyyyy.
Operator Action: Enter A to abort the program or C to continue.
will cause the program to accept the BSN xxxxxx and continue •
The C option
• i-ccc-dd: BLOC[ SERIAL lUMBER ERROR
Startup Message. An error occurred on the tape during processing of the
$ READIN statement.
Operator Action:
Correct tape, then restart.
5-6
DH13-04
B
B
OUTPUT MESSAGES
OUTPUT MESSAGES
-BOTH SCU'S ARE CONFIGURED AS LOW MEII>RY
Startup Message. the DPS 8000 SCU configuration registers were read and both
SCUs appear to contain low memory.
Operator Action: Correct the DPS 8000 service processor configuration file and
reboot from switches.
-BOOT lOP RELEASED, CAl HOT CONTINUE
Startup Message. This pertains to DPS go systems only. The boot IOP has been
released; therefore, Startup cannot issue an I/O. The $ MCT statement has
specified an incorrect port assignment for the boot IOP.
Operator Action:
Correct the $ MCT statement and reboot.
-BOOTLOAD DEVICE ERROR i-ccc-dd eeeee
FIX TYPE GO
Startup Message. A read device error occurred and the device may not be
capable of continued operation without operator intervention.
eeeee - Error status
Operator Action:
Fix the device; enter GO.
-BOOTLOAD DEVICE ERROR i-ccc-dd: eeeee
OPERATE WHER READY
Startup Message.
A
read was attempted on a device that is not in Ready status.
eeeee - Error status
Operator Action:
Correct the error condition and ready the device.
-BOOTLOAD DEVICE HOT COIFIGURED 01 • 10M
Startup Message. The device currently being used for bootloading was not
configured on the $ IOM statement.
Operator Action:
Correct the $ IOM statement and reboot.
5-7
DH13-04
B
OUTPUT MESSAGES
B
OUTPUT MESSAGES
BOOTLOAD FROM PUSHBOTTOIS
Dump Message. A unrecoverable error was detected while reading Startup from
disk to memory. The Startup program is on tape, not cards.
Operator Action:
Bootload from the console by pressing INIT, then BOOTLOAD.
BOOT SOURCE: AUTO OR REPL?
Startup Message. Following a system abort (and dump) the operator is asked to
specify whether the source for rebooting the system is to be from the AUTOLOAD
file or whether sections of the startup job stream are to be selectively
replaced.
NOTE:
This message does not apply to DPS 88 systems.
Operator Action:
Enter AUTO - The Startup program residing on the AUTOLOAD file is to be used
to effect the bootload.
Enter REPL - The operator can selectively replace one or more sections of
the Startup program that exists on the AUTOLOAD file. The
section(s) must be entered in their entirety via the card
reader. The entire section is written to the AUTOLOAD file to
overlay (replace) the existing section. (Refer to the GeOS 8
OS System Startup manual for additional information.)
If, during the restart procedure, an error occurs that prevents rebooting the
system from the Startup program and job stream that reside on the AUTOLOAD
file, an informational message is issued to the console. The message directs
the operator to reboot the system using the storage medium on which the Startup
program and job stream originally resided.
o It the Startup program originally resided on punched cards, the console
message AUTOLOAD ABORT, BOOT FM CARD READER is issued.
o It the Startup program originally resided on magnetic tape, the console
message AUTOLOAD ABORT, BOOT FROM TAPE is issued.
5-8
DH13-04
~
B
B
OUTPUT MESSAGES
OUTPUT MESSAGES
BOOT SOURCE: TAPE, DISIC, AUTO OR REPL?
Startup Message. Following a system abort (and dump), the operator is asked to
specify whether the source for rebooting the system is to be from tape, disk,
the AUTOLOAD file, or whether sections of the startup job stream are to be
selectively replaced.
Operator Action:
Enter TAPE - Permissible only on DPS 8000 and DPS 88 systems and causes the
following message to be issued:
-READY BOOT TAPE ON icccdd, TYPE GO WHEN READY
i-lOX number
ccc - Channel number
dd - Device number
Mount the boot tape and enter nGOn when ready.
Enter DISK - The Startup program residing on the AUTOLOAD file is to be used
to effect the bootload. (A new image is read into memory.)
Enter AUTO - The Startup program is re-initialized from the memory image of
the AUTOLOAD file.
Enter REPL - The operator can selectively replace one or more sections of
the Startup program existing on the AUTOLOAD file. The
section(s) must be entered in their entirety via the card
reader. The entire section is written to the AUTOLOAD file to
overlay (replace) the existing section. (Refer to the GCOS 8
OS System Startup manual for additional information.)
If, during the restart procedure, an error occurs that prevents rebooting the
system from the Startup program and job stream that reside on the AUTOLOAD
file, an informational message is issued to the console. The message directs
the operator to reboot the system using the storage medium on which the Startup
program and job stream originally resided.
o If the Startup program originally resided on magnetic tape, the console
message AUTOLOAD ABORT, and BOOT FROM TAPE is issued.
)
I
5-9
DH13-04
B
B
OUTPUT MESSAGES
OUTPUT MESSAGES
-BOOT SOURCE MUST BE CARDS
Startup Message.
The bootload must be done from the card reader.
Operator Aotion:
Load the bootload deck into the card reader and reboot.
-BPRIOH (input text) REQUEST DENIED
GPOP Message.
following:
A
BPRIOR verb request is rejected.
May be caused by one of the
o Specified SNUMB not in execution
o Format of parameters in error
o Specified SNUMB not a class B priority process
o Class B priority option not speoified
Operator Action:
Correct the condition.
-BRING DEVICE ON CARD BELOW ONLINE FOR TAPE SURVEY
END MESSAGE WHEN READY
Startup Message. An MTS500, MTU0400/0500, or MTUo600 tape device was specified
on the indicated $ READIN, $ FILDEF, or $ ACCOUNT statement, and it was either
in an offline condition or powered off during tape survey.
Operator Action: Bring the device online or power it up so that survey can be
done; or abort Startup, select another device on the card, and restart Startup.
- BRT6 {.CRSLQ} CLEANPOINT ERROR FDR sssss
{SD.SBT}
Termination Message. An error oocurred when termination attempted to
cleanpoint a system table for the specified cell or segment.
NOTE: This message only occurs when the CLENPT option is specified on the
$ INFO statement of the Startup program.
Operator Action:
Notify the Honeywell Bull Response Center.
5-10
DH13-04
B
OUTPUT MESSAGES
B
OUTPUT MESSAGES
-BS! I/T SS%% ppp i ccc dd sssss seek address (disk only)
(operator response) (?)
Exception Processor Message. A channel or devioe busy status, with a substatus
of ss, ooourred on the devioe ppp during an attempt to exeoute the instruotion
indicated by the code xx.
I/T
ss
xx
ppp
-
Status returned on an Initiate/Terminate interrupt.
Octal substatus oode (refer to Appendix D)
Instruction code (refer to Appendix A)
Indicates one of the following devioe types:
CP - Card Punch
CR - Card Reader
DP - Disk Paok
DS - Disk
MT - Magnetio Tape
PR - Printer
TY - Console
i-Input/output oontroller number
coc - Channel (PUB) number
dd - Devioe number
sssss - SNUMB
Operator Aotion: One or more of the following explioit responses may be
available. These are punctuated with a question mark (?) and the keyboard is
enabled to allow operator input.
Enter R - Retry I/O. Clear or reset the device before responding.
Enter U - Returns status to the user program.
Enter S - Type the seek address (disk only). The message will then be
repeated.
The implicit option A is available to abort the program as a last resort.
EXAMPLE:
-BSY I 0025 DP 0 08 026 5840Z RUS?
A ohannel busy status exists on an initiate interrupt to the disk pack on
IOM-O, ohannel 08, device 26, while running SNUMB 5840Z. While executing a
write-continuous (25) instruction the system found the device to be hung in a
ohannel busy oondition (00). The devioe should be reset and plaoed in a ready
state. Cheok the data in the disk looation where the device was hung by
entering S. After the message is repeated, the options are to retry the I/O
(R), let the user program try to reoover (U), or abort the job (A).
5-11
DH13-04
B
B
OUTPUT MESSAGES
-BTIH Mr i
000
OUTPUT MESSAGES
dd sssss-aa Hl
File and Record Control Message. A tape file was opened as input and the first
physioal record read is either blank tape or not a label.
BTIH - Blank tape on input header
NA - Operator reply
Operator Action:
Enter N to try a new reel. The I/O system will dismount the present reel
to facilitate mounting another reel.
Enter A to abort the activity.
-BTIR sssss-aa Hr i
000
dd NA
Standard COBOL-68 I/O System Message. A blank tape was encountered when the
system attempted to read an input header label.
Operator Aotion:
Enter N to try a new reel (the I/O system will dismount the present reel to
facilitate mounting another reel).
Enter A to abort the activity.
-BTIT Mr i
000
dd sssss-aa E
File and Record Control Message.
or unreoognizable.
The input trailer label was blank, invalid,
BTIT - Blank tape on input trailer
E - End-of-file condition
Operator Action:
None.
5-12
DH13-04
B
B
OUTPUT MESSAGES
-BTIT
88888-&8
OUTPUT MESSAGES
Mr i
000
dd E
Standard COBOL-68 I/O System Message. A blank tape was encountered when the
system attempted to read an input trailer label. The file is considered to be
at the end, and end-of-file processing takes place.
Operator Action:
None.
BUFFER IS TOO BIG IN WD FOR DDIA, SET AS 128K
Session Control Message. Informative Message. This is issued each time the
HNAD workstation is executed if a -BUFFER SIZE value of 256,000 (128K) is
explicitly defined via the workstation control language command
CREATE CHANNEL. (System software assignes a default -BUFFER SIZE value of
133,072 (128K».
Operator Action:
None.
BUFFER IS TOO SMALL IN WD FOR DDI1, SET AS 321{
Session Control Message. Informative Message. This is issued each time the
HNAD workstation is executed if a -BUFFER SIZE value of 32,768 (32K) or more is
not explicitly defined via the workstation control language command
CREATE CHANNEL. (System software assignes a default -BUFFER SIZE value of
32,768') •
Operator Action:
None.
-BURST OF SI ON ieee NOTIFY MAINTENANCE
Interrupt Handler Message.
on a peripheral device.
Operator Action:
A burst of special interrupts (SI) was encountered
Contact the Honeywell Bull Response Center.
5-13
DH13-04
SKCTIOK 6
OUTPUT MESSAGES BEGIRRIHG WITH THE LETTER C
-CACHE ERROR, FLT REG BITS 32-46
= %%xxx,
PORT n
ECOL Message. ECOL detected cache associated error(s) conditions reflected in
bits xxxxx octal.
Operator Action: None. This message is normally disabled, but will occur upon
error-detection following a previously entered input message: ECOL CSHMON.
Information in this message may be used by the Honeywell Bull Response Center
to note unexpectedly high cache error incidents or to note a pattern of errors
that could lead to high cache error incidents.
-CACHE ERROR,PORT-xx,CORE=cccooooooooo,caohe=bbbbbbbbbbbb
ADDRESS=aaaaa
ECOL Message. EeOL detected a difference between the comparative contents of
cache and core memory. This is a serious error and ECOL has disabled cache.
xx - System Controller port to which the erring processor is
connected
cccccccccccc - Core contents in octal
bbbbbbbbbbbb - Cache contents in octal
aaaaa - Octal core address of data being compared
Operator Action: Contact supervisory personnel to determine if system
availability necessitates continuing to run without Cache. If not, two options
are available. The operator can dynamically release the malfunctioning
processor (if multi-processing) and notify the Honeywell Bull Response Center
of its availability for repair. A second option involves placing the processor
briefly in a STEP condition, disabling the Cache switches, and manually cycling
the processor back into operating mode. This should be done only by Honeywell
Bull Response Center personnel. This process may be reversed following
removal, repair, and replacement of bad Cache boards. ECOL will reassign good
Cache Memory automatically upon discovering its availability.
6-1
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
.CACHE READ FAILED CPU-Ix
Dump Message. Processor x failed to complete the reading of the hardware cache
in the allowed time and that the cache from processor x will not be saved by
Dump.
Operator Action:
None •
• CALCULATED BAD SEEK ADDRESS FOR GPAED
Startup Message. When reading one of the files containing patch-edited
patches, Startup received a seek address error.
Operator Action:
None.
The patch listing on a dump may not be correct.
sssss CAN NOT BE RUN NOW. CYCLIC JOB
System Scheduler Message. Insufficient catalog space was available to allow a
cyclic job to be a candidate for allocation. The job will be moved to a normal
class, for allocation, when space becomes available.
Operator Action:
None.
CANNOT BUILD IN-CORE TABLE ON ddd DUE TO rrrrrr ssssssssssss
DEVICE RELEASED
GPOP Message. The .MALCD module returned an error condition to .MPOPM when
attempting to initialize the in-memory AST image on device ddd.
rrrrrr - Error condition as follows:
NOTNPS - The pack label and the SCT do not agree that the device
is a NPS-shared device.
AST 1M - Bad in core AST image. AST image on a shared device has
a bad checksum. A secondary IN!T of the device is
required.
NOTNPS - The pack label and the SCT do not agree that the device
is a NPS-shared device.
6-2
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
SEEK AD - An invalid seek address was generated during available
space table initialization.
STATUS - An input/output error was encountered.
CHKSUM - A bad checksum occurred on either the pack label or the
device's available space table.
BZ TMP - A temporary space descriptor is currently busy in another
system. The other system needs to be inactive and a
secondary init of the device performed.
TBLSIZ - The amount of memory reserved for the available space
table was inadequate because the pack allocation unit
size was different from the AU size defined on the $ 10M
statement.
NSTRUC - A non-structured pack is mounted on a spindle configured
as permanent.
ssssssssssss - The Q register indicated STATUS, which is stored in the A
register. This entry shows contents of the A register in
octal.
Operator Action:
None •
• CANNOT CREATE THE SHC WITHIN BOUNDS OR ddd
Startup Message. There is unsufficient space to create the system master
catalog with a block address containable in 17 bits.
Operator Action:
Initialize the pack.
6-3
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
.CADOT DETERMINE MeA NUMBER 01 lMU-x, MCA RELEASED
Startup Message. The MeA configuration files for all lMUs/IMXs are read by
startup for all lMUs/IMXs. These files reflect the MeA numbers (internal board
mounted switch) which result in the identification of the MeA on the
maintenance console log and in other journalized logs (the character string
100> on the console reflects MeA number 00, 101> MeA number 01, etc.) These
MCA numbers *MUST* be unique if the MeAs are to be connected together via the
MDI interface, and *SHOULD* be unique to correctly identify which MeA detected
and logged an error if they are not connected together via the MDI interface.
Startup was unable to read the configuration file from the specified MCA and
thus the MCA will be released until its configuration can be verified. This is
an FYI message.
Operator Action: Correct the problem encountered (documented via a message
preceeding this one) so that the MeA config file can be read to verify the MCA
number field.
CADOT EXCHG SYSTEM 1/0 MASS STORE
Exception Processor Message. An X response was made to a previous mass store
system 1/0 error message. The X response is not allowed. This message is
followed immediately by the original illegal major status message.
Operator Action:
message.
Enter an allowable response to the repeat of the original
CANNOT FIND DCAF DATA FOR THIS FAULT
ALL WILL BE USED AS DUMP OPTION
Dump Message. A DeAF error has occurred.
default DeAF options.
Operator Action:
The ALL option will overwrite the
None.
6-4
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
.CANNOT IDENTIFY MPC DATA DEC[
MPC Subsystem Startup Message. The MPC subsystem data deck does not contain
expected device description information.
Operator Action: Check the data deck and reboot Startup.
recurs, a new data deck should be created.
If the message
sssss CANNOT JCHGCY OR JDELCY A CYCLIC JOB IN EXECUTION
System Scheduler Message. The operator made a request either to change cyclic
parameters or to delete a specific cyclic job, but the job was in execution.
The request is ignored.
Operator Action:
execution •
Resubmit the original request after the job has completed
• CANNOT HOVE - BPM
Exception Processing Message. The label that was read after the disk pack
exchange was not the one expected or could not be read at all.
BPM - A bad pack was mounted
Operator Action: Put the original pack on the primary device to continue
operation. The original error message follows this message. With the original
pack mounted, enter R to continue operation. A special interrupt is required
to read the label and return to normal operation •
• CANNOT MOVE - NUA
Exception Processing Message. No PERM or RMVBL device is available.
message is followed by the original error message.
This
NUA - No units available
Operator Action: Put the original pack on the primary device to continue
operation. Enter R to the second error message to retry the device command.
6-5
DH13-04
C
OUTPUT MESSAGES
C
OUTPUT MESSAGES
•• CARROT PROCEED OVERLAY I/O ERROR
Dump Message.
overlays.
The Dump program was unable to read one of its three program
Operator Action:
Reboot the system from cards or tape.
CAN'T ACCESS SIS RECOVERY/RESTART STATUS xx
Rollcall Message. During a restart, the permanent file used to communicate
restart data from POPM to ALC1 could not be allocated. (xx = error status
returned by FILSYS.)
Operator Action:
Contact the Honeywell Bull Response Center •
••• CAN'T ALLOCATE $S SPACE FOR RESTART •••
Peripheral Allocator Message. The system is being restarted, and the
Peripheral Allocator was denied the file space it requested to build to swap
file for a phase 1 recovery process that it attempts to start.
Operator Action: None.
CAN'T ASGNI m - NOT CONFIGURED
lOS message.
configured.
The input/output controller specified in the request is not
Operator Action:
Move or enter correct input/output controller designator •
• CAN'T 'SGNI m - INPUT INVALID
lOS Message.
The request format contained an error.
Operator Action:
Enter correct format.
6-6
DH13-04
C
C
OUTPUT MESSAGES
.xxx
OUTPUT MESSAGES
{PERM
}
{CATALOGABLE}
CAN'T CHARGE DEVICE STATUS FROM {FHS
}
{BPS
}
{RVBL
}
TO {NON FHS
{NOH FHS
}
}
{~CATALOGABLE}
Startup Message.
aborts.
The status of device xxx could not be changed.
Startup
Operator Action: Make Startup configuration change to correct the error and
reboot the system •
• CAN'T CHANGE TO SMCDUP WITHOUT INIT
Startup Message.
Startup aborts.
The system status was changed from non-SMCDUP to SMCDUP.
Operator Action: To effect the change to SMCDUP, perform a complete
initialize; otherwise, remove the $ INFO SMCDUP/xxx statement.
CAN'T FIND TAPE DRIVE: (drive)
Dump Message. The tape drive was not specified correctly, and should be
entered again.
Operator Action:
Enter (DDD/Tapel,Density)
6-7
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
88888
ClifT GET A TAPE DRIVE FOR aaaaa
NEED {ORE} {800} BPI DRIVE(S)
---- {TWO} {1600}
{6250}
{PREFER } DRIVE(S) FROM POOL: { name1,name2, ••• ,name8
}
{REQUIRE}
{(name1,name2) ••• (name7,name8)}
[TRY-TIME LEFT
= nnnnn
MINUTE(S)]
Where:
sssss
aaaaa
nnnnn
name1 ••• 8
-
SNUMB of Integrated Software.
Journal name.
Product of TRYCOUNT and SLEEPTlME values, in minutes.
Name of a tape device used in a $ 10M statement in the Startup
job stream.
Integrated Software Message.
A tape drive is not available for allocation for:
o The mounting of a tape volume for collection of data base images.
o The save/restore operation associated with a DDBA or RFWD command.
o The mounting of the first tape volume associated with a RBCK or RFWD
command.
The message is issued before SLEEPTIME is invoked, and is repeated TRYCOUNT
times at SLEEPTIME intervals if a "drive not available" status is returned by
the operating system in response to a tape allocation request. Only the first
line of the message is produced when the product of TRYCOUNT and SLEEPTIME
values is zero.
The second line of the message indicates whether one or two tape drives is
required, depending upon whether the FLIPFLOP option has been specified for the
journal.
NOTE: A separate allocation is attempted when a duplicate journal is being
maintained. The specified tape density (DENSITY option) is also
indicated in the message.
6-8
DH13-04
C
OUTPUT MESSAGES
C
OUTPUT MESSAGES
The third line of the message is produced only when any "device list" type
options (i.e., DEVLST, DEVLST REQ, DEVSET, and DEVSET REQ) have been specified
for the journal. DEVLST and DEVLST REQ are used when-the FLIPFLOP option is
not specified. DEVSET and DEVSET REQ options support the FLIPFLOP allocation,
which allocates tape drives in paIrs. DEVLST and DEVSET specify preferred tape
drives (PREFER appears in the message), and DEVLST REQ and DEVSET REQ indicates
required tape drives (REQUIRE appears in the message).
The values following "POOL:" in the third line of the message are the "pool" of
tape drives to be used for journaling as indicated for the device list
options. Up to eight tape drives can be specified for a device list option.
If either the DEVSET or DEVSET REQ option has been specified, the tape drives
specified will be coupled within parentheses.
The fourth line indicates the total time available within which a tape drive
allocation can be made. Otherwise, an allocation denial is returned to the
calling process.
Operator Action:
None.
Informational message only •
• sssss CAN'T GET A TRACE COLLECTION TAPE
Trace Analyzer Message.
to GEMORE a tape.
The Trace Analyzer trace collector program was unable
sssss - Job identifier (SNUMB) of the trace collector program
Operator Action:
available •
Rerun trace collector program when a tape drive becomes
• CAN'T HAVE CATDUP WITHOUT SMCDUP
Startup Message. The Startup program contains a $ INFO statement with the
CATDUP option, but does not contain a $ INFO statement with the SMCDUP option.
Startup aborts.
Operator Action:
Insert a $ INFO SMCDUP/xxx statement and reboot.
6-9
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
.CAN'T MARK DEFECTIVE SPACE UNAVAILABLE ON
i:ooo:dd
Startup Message. An error has oocurred while an entry contained in the
DEFECTIVE LLINK DIRECTORY was being converted to a space descriptor for the
startup program to use to mark the allocation units describing a defective
track unavailable in the available space table.
Operator Action: This message is activated when a $ BUGON statement is
included in the $INITIAL1ZE section of the system description deck. Such an
inclusion is made by the site administrator or at the request of the Technioal
Assistance Center (TAC). An ALL startup dump should be taken for analysis by
the party requesting inclusions of the bugon. The error may be recoverable by
MTARing the failing MSU and assigning alternate tracks •
• CAN'T MOVE CONSOLE EMULATOR
Startup Message. A $ CHAN statement was rejeoted. The console emulator is
logioally connected to channel 31 of 10X-O and cannot be moved.
Operator Action:
Delete the conflicting statement.
• CAN'T RECOVER PROTECTED FILES FOR PROCESS(ES):
• ssssO
[. ssss5
[ssss1
[ssss6
[ssss2
[ssss7
[ssss3
[ssssa
[ssss4]]]]
[ssss9]]]]]
GPOP Message. Protected file rollback cannot be provided to the SNOMBs listed,
because they were not in execution when the system went down.
ssss[0 ••• 9] - SNUMB of prooess requiring deferred recovery
Operator Action: Exeoute deferred recovery to rollbaok files and release the
proteotion struoture.
NOTE: Items within the braokes [ ] mayor may not appear.
6-10
DH13-04
C
OUTPUT MESSAGES
C
OUTPUT MESSAGES
*
CAN'T RECOVER PROTECTED FILES Slsssss W/ACTY nn (xx)
tile system error message «]
[ »
Peripheral Allocator Message.
conclusion.
A phase 1 cannot proceed to a successful
The second line of the message is present only for error codes PF and PT.
xx - Error code, as follows:
AS
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is ACTIVE, which
is invalid for the circumstances. The process (sssss) is SHARD.
This indicates a system error.
Response Center.
Contact the Honeywell Bull
BJ
Either (1) no J* file was present for the process, (2) an I/O
error occurred while the J* file was being read, (3) the SNUMB in
the J* record did not match a SNOMB in the .CRSNB table, (4) the
J* Peripheral Assignment Table (PAT) contains an erroneous System
Configuration Table (SCT) address, or (5) an I/O error occurred
while the restart file was being read. Restart is not permitted
in any of these instances.
C1
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is EOA. (EOA
indicates the end of an activity whereby the commitment unit for
the data base has been closed.) Because a SHARD restart error
occurred, SHARD was unavailable to release Integrity Management
structure. Restart is not permitted.
The process (sssss) is neither SHARD nor a Transaction Processing
snumb (TDS or DM-IV/TP).
C2
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is EOA. (EOA
indicates the end of an activity whereby the commitment unit for
the data base has been closed.) Because SHARD was not present for
restart, it is not permitted.
The process (sssss) is neither SHARD nor a Transaction Processing
snumb (TDS or DM-IV/TP).
6-11
DH13-04
C
C
OUTPUT MESSAGES
C3
OUTPUT MESSAGES
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is EOA. (EOA
i,ndicates the end of an activity whereby the commitment unit for
the data base has been closed.) Because a SHARD restart error
occurred, SHARD was unavailable to release Integrity Management
structure. Restart is not permitted.
The process (sssss) is a Transaction Processing snumb (TDS or
DM-IV/TP) •
C4
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is EOA. (EOA
indicates the end of an activity whereby the commitment unit for
the data base has been closed.) Because SHARD was not present for
restart, Integrity Management structure was not released. Restart
is not permitted.
The process (sssss) is a Transaction Processing snumb (TDS or
DM-IV/TP) •
CN
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is EOA. (EOA
indicates the end of an activity whereby the commitment unit for
the data base has been closed.) An error was returned by the IMOO
domain when it attempted to release Integrity Management
structure. Protected file recovery is not needed and the recovery
structure can be released. If the deferred recovery utility is
run, it will release any remaining structure if it exists.
Restart is not permitted.
Since the protected file deallocations mayor may not have been
done before the system interruption, busy spurious counts may
still exist.
The process (sssss) is neither SHARD nor a Transaction Processing
snumb (TDS or DM-IV/TP).
CS
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is EOA, which is
invalid for the circumstances. The process (sssss) is SHARD.
This indicates a system error.
Response Center.
6-12
Contact the Honeywell Bull
DH13-04
~
C
OUTPUT MESSAGES
C
OUTPUT MESSAGES
CT
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is EOA.
(EOA
indicates the end of an activity whereby the commitment unit for
the data base has been closed.) An error was returned by the IMOO
domain when it attempted to release Integrity Management
structure. Protected file recovery is not needed and the recovery
structure can be released. If the deferred recovery utility is
run, it will release any remaining structure if it exists.
Restart is not permitted.
Since the protected file deallocations mayor may not have been
done before the system interruption, busy spurious counts may
still exist.
The process (sssss) is a Transaction Processing snumb (TDS or
DM-IV/TP).
DN
An error was encountered while attempting to convert a device name
to an SCT address. The job is deleted.
ER
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is ERROR IN
DEFERRED RECOVERY. (ERROR IN DEFERRED RECOVERY indicates rollback
was unsuccessful during a previous deferred recovery operation.)
Attempt deferred recovery again.
ET
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is ERROR IN
TERMINATION. (ERROR IN TERMINATION indicates a commitment unit
remained open at the end of process termination and file rollback
failed.)
NJ
Either no restart record was present or an attempt to write to the
J* file failed. Neither system recovery nor restart is possible.
P2
Either an I/O error occurred during an attempt to read the
Peripheral Assignment Table (PAT) file or a segment with an
invalid size was read from the PAT file. The process was deleted.
PF
A cataloged file could not be reallocated. The identity of the
file (file code) and the reason for unsuccessful allocation
immediately follow the .CAN'T RECOVER message.
PT
An unsuccessful attempt was made to reallocate the Peripheral
Assignment Table (PAT) file.
6-13
The process (sssss) was deleted.
DH13-04
C
OUTPUT MESSAGES
C
OUTPUT MESSAGES
RD
An 1/0 error occurred while the control file was being read.
process was deleted.
SO
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is 0 (zero),
which is invalid for the circumstances. Recovery cannot complete
and the process is deleted.
This indicates a system error.
Response Center.
S1
The
Contact the Honeywell Bull
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is SETUP. (SETUP
indicates that the recovery structure was in the process of being
established, and there is no danger to data base integrity because
the files were not accessed. However, spurious busy counts may
exist.) Because a SHARD restart error occurred, SHARD was unable
to release Integrity Management structure. Restart is not
permitted.
The process (sssss) is a Transaction Processing snumb (TDS or
DM-IV/TP).
S2
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is SETUP. (SETUP
indicates that the recovery structure was in the process of being
established, and there is no danger to data base integrity because
the files were not accessed. However, spurious busy counts may
exist.) Because SHARD was not present for restart, Integrity
Management structure was not released. Restart is not permitted.
The process (sssss) is neither SHARD nor a Transaction Processing.
S3
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is SETUP. (SETUP
indicates that the recovery structure was in the process of being
established, and there is no danger to data base integrity because
the files were not accessed. However, spurious busy counts may
exist.) Because a SHARD restart error occurred, SHARD was unable
to release Integrity Management structure. Restart is not
permitted.
The process (sssss) is a Transaction Processing Executive snumb
(TDS DM-IV/TP).
6-14
DH13-04
C
C
OUTPUT MESSAGES
S4
OUTPUT MESSAGES
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) 1s SETUP. (SETUP
indicates that the recovery structure was in the process of being
established, and there is no danger to data base integrity because
the files were not accessed. However, spurious busy counts may
exist.) Because SHARD was not present for restart, Integrity
Management structure was not released. Restart 1s not permitted.
The process (sssss) is a Transaction Processing snumb (TDS
DM-IV/TP) •
S5
The status of the Integrity Management structure
in question (i.e., the recovery structure state)
(ACTIVE indicates that the process was executing
not have written to data base files.) Because a
error occurred, SHARD was unavailable to release
Management structure. Restart is not permitted.
for the process
is ACTIVE.
and mayor may
SHARDs restart
Integrity
The process (sssss) is a Transaction Processing snumb (TDS or
DM-IV/TP) •
s6
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is ACTIVE.
(ACTIVE indicates that the process was executing and mayor may
not have written to data base files.) Because SHARD was not
present for restart, Integrity Management structure was not
released. Restart is not permitted.
The process (sssss) is a Transaction Processing.
SE
The status of the Integrity Management structure for the process
in question is invalid (i.e., the recovery structure state value
exceeds the largest valid value).
This indicates a system error.
Response Center.
6-15
Contact the Honeywell Bull
DH13-04
C
OUTPUT MESSAGES
SN
C
OUTPUT MESSAGES
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is SETUP.
(SETUP
indicates that the recovery structure is in the process of being
established, and there is no danger to data base integrity because
the files were not accessed. However, spurious busy counts may
exist.) An error was returned by the IMOO domain when it
attempted to release Integrity Management structure for the data
base. Protected file recovery is not needed and the recovery
structure can be released. If the deferred recovery utility is
run, it will release any remaining structure if it exists.
Restart is not permitted.
The process (sssss) is neither SHARD nor a Transaction Processing.
SS
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is SETUP, which
is invalid for the circumstances. The process (sssss) is SHARD.
This indicates a system error.
Response Center.
ST
Contact the Honeywell Bull
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is SETUP. (SETUP
indicates that the recovery structure is in the process of being
established, and there is no danger to data base integrity because
the files were not accessed. However, spurious busy counts may
exist.) An error was returned by the IMOO domain when it
attempted to release Integrity Management structure for the data
base. Protected file recovery is not needed and the recovery
structure can be released. If the deferred recovery utility is
run, it will release any remaining structure if it exists.
Restart is not permitted.
The process (sssss) is a Transaction Processing snumb (TDS or
DM-IV/TP).
6-16
DH13-04
C
C
OUTPUT MESSAGES
UN
OUTPUT MESSAGES
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is unuseable.
This state is entered when a process before journal fills, but the
process before journal protected files are also protected by
archived before journal. The protected files must be recovered
via the RBCK utility. (Refer to GCOS 8 OS Integrity Control
manual).
Operation Action: To recover, correct the error, run a Deferred Recovery, and
either rerun the job or perform a deferred restart •
• CAN'T RESTART Slsssss W/ACTY aa (xx)
[ »file system error mesage «]
Peripheral Allocator Message.
conclusion.
A phase 2 restart cannot proceed to a successful
The second line of the message is present for error codes CK, PF, and PT.
xx - Error code, as follows:
AJ
Phase 1 recovery was requested for the process. However, system
software determined that the process either had not executed or
had previously terminated. Consequently, phase 1 recovery is
unneccessary.
AN
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is EOA. (EOA
indicates the end of an activity whereby the commitment unit for
the data base has been closed.)
A system interruption occurred while the process was terminating,
but before the process recovery structure could be released.
Phase 1 recovery released the structure since protected file
recovery was not needed.
Since the protected file deallocations mayor may not have been
done before the system interruption, busy spurious counts may
still exist.
6-17
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
A1
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is EOA. (EOA
indicates the end of an activity whereby the commitment unit for
the data base has been closed.) While attempting restart at
either the beginning of the process or at the beginning of the
activity, Integrity Management structure could not be released for
the data base because a SHARD restart error occurred. Restart is
not permitted.
Attempt deferred recovery for the process (sssss).
A2
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) is EOA. (EOA
indicates the end of an activity whereby the commitment unit for
the data base has been closed.) While attempting restart at
either the beginning of the process or at the beginning of the
activity, Integrity Management structure could not be released
because SHARD was not present for restart. Restart is not
permitted.
Attempt deferred recovery for the process (sssss).
BJ
No J* file was present for the process, an I/O error occurred
while reading the J* file, or the SNUMB in J* record did not match
SNUMB in the .CRSNB table.
BZ
Device requested for this process (to assign data files) was
released or allocated to another process.
CB
Checksum error occurred after the commitment control block was
read or the SNUMB or user identification in the control block is
different from that in the J* file.
CK
Commitment file cannot be allocated by FMS.
CN
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure state) was EOA. (EOA
indicates the end of an activity whereby the commitment unit for
the data base has been closed.)
A system interruption occurred while the process was terminating
before the process recovery structure could be released. Phase 1
recovery released the structure since protected file recovery was·
not needed.
6-18
DH13-04
C
OUTPUT MESSAGES
C
OUTPUT MESSAGES
Since the protected file deallocations mayor may not have been
done before the system interruption, busy spurious counts may
still exist.
The process is neither SHARD nor a Transaction Processing snumb
(TDS or DM-IV/TP).
Attempt deferred recovery for the process (sssss).
CP
Commitment is unreadable.
CT
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure status) was EOA. (EOA
indicates the end of an activity whereby the commitment unit for
the data base has been closed.)
A system interruption occurred while the process was terminating
before the process recovery structure could be released. Phase 1
recovery released the structure since protected file recovery was
not needed.
Since the protected file deallocations mayor may not have been
done before the system interruption, busy spurious counts may
still exist.
Attempt deferred recovery for the process (TP).
DJ
An error occurred while attempting input/output to/from the $J or
J* file.
DN
An error was encountered while attempting to convert a device name
to an SCT address. The job is deleted.
ER
The status of the Integrity Management structure for the process
in question (i.e., the recovery structure status) is ERROR IN
DEFERRED RECOVERY. (ERROR IN DEFERRED RECOVERY indicates that
rollback was unsuccessful during the previous deferred recovery
operation.)
Attempt deferred recovery again.
ET
~
The status of the Integrity Management structure for
in question (i.e., the recovery structure status) is
TERMINATION. (ERROR IN TERMINATION indicates that a
unit remained open at the end of process termination
rollback failed.)
the process
ERROR IN
commitment
and file
j
6-19
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
The process is neither SHARD nor a Transaction Processing.
Attempt deferred recovery for the process (sssss).
JD
An error occurred while attempting input/output to/from the J$
file (possibly as the result of an invalid Peripheral Assignment
Table (PAT) for the J$ file).
MS
Requested file space or mass storage is unavailable or an attempt
was made to reallocate a non structured or stranger disk pack. (A
stranger pack is a disk pack that is unknown to system software.
The pack mayor may not contain a label and/or permanent file
catalog structure.)
NR
The aborted program did not request process restart (i.e., the job
stream included the NJREST or NREST option).
NJ
No restart record was found.
NS
System software failed to locate the applicable System
Configuration Table (SCT) entry while attempting to set the
density for a tape during restart from a commitment point.
OP
Operator responded A (abort) to an MNT (mount tape) message.
P2
An input/output error occurred while the Peripheral Assignment
Table (PAT) file was being accessed; or a PAT sequent with an
invalid size was read from the PAT file. The process is deleted.
Deferred recovery must be performed for the process.
PF
Unsuccessful attempt was made to reallocate a permanent data file.
PT
Unsuccessful attempt was made to reallocate the Peripheral
Assignment Table (PAT) file for this SNUMB (i.e., process).
Deferred recovery is required.
RD
Attempt to read J* file was unsuccessful.
TP
Magnetic tape repositioning information was lost.
UD
Attempt was made to allocate a file to a card reader, card punch,
printer, or removable mass storage device.
WS
An error return was taken following a call to the Workstation
Management Domain (WMAN) during phase 1 recovery.
6-20
DH13-04
C
C
OUTPUT MESSAGES
OUTPU'l' MESSAGES
The job is terminated and either OPERATOR TERM REQUEST or OPERATOR KILL REQUEST
is printed on the user's execution report.
Operator Action: To recover, correct the error and either rerun the job or
perform a deferred restart •
• CAN'T RESTART SYSTEM
Dump Message. An error occurred that prevents a subsequent system restart.
This is an informational message.
Operator Action:
None •
• CAR'T BLSBI m - SINGLE 10M
lOS Message.
Release cannot be done because only one 10M is configured.
Operator Action:
None.
CAN'T BLSEI m - NOT CONFIGURED
lOS Message.
system.
The specified input/output controller is not configured in the
Operator Action:
Enter the correct input/output controller designation •
• CAN'T BLSEI m - INVALID INPUT
lOS Message.
The release request contained an error (e.g., incorrect format).
Operator Action:
i cee
Enter the correct format.
dd CAN'T ASGN/RLSE THIS DEVICE TYPE
GPOP Message. The operator attempted to assign or release a device type that
cannot be assigned or released via the console verbs ASGN or RLSE.
Operator Action: The device status is not affected by the failure of the
assign/release attempt. The NOI console verbs should be used to functionally
assign or release (enable or disable) a UNCP device type.
\ 6-21
DH13-04
C
OUTPUT MESSAGES
C
OUTPUT MESSAGES
*CAN'T SAVE MASK CARD BELOW SO CAN'T APPLY
Startup Message. The MASK statement indicated that it could not be processed;
therefore, Startup cannot make the correction indicated on that statement.
Operator Action: Either resubmit a new MASK statement or run Startup without
the correction indicated on the MASK statement.
*CAN'T SET TABS ON SCC
Startup Message.
The system cannot set the tabs on the system console.
Operator Action: Either fix the problem or reconfigure without the failing
device until it is fixed.
*CARD AT xxxxxx HAS CHECKSUM ERROR
Startup Message.
The control statement indicated has a checksum error.
Operator Action:
Correct the statement and restart.
*CARD AT xxxxxx SKIPPED DUE TO CHECKSUM ERROR
Startup Message.
checksum error.
The control statement indicated was skipped because of a
Operator Action:
restart.
Check the statement for errors; correct if necessary, and
6-22
DH13-04
C
OUTPUT MESSAGES
C
OUTPUT MESSAGES
• xxxxxx CARD BELOW CONTAINS ERROR NEAR COLUMN nn
Startup Message. The Startup configuration card indicated is either
incorrectly punched or contains invalid data at or near the card column nne
the card pertains to hardware required for successful startups, the system
aborts.
If
xxxxxx - Startup job stream section:
CONFIG
INITIALIZE
EDIT
FILES
PATCH
LOAD
Operator Action: Respond to the .BOOT SOURCE: CARDS, AUTO, REPL, FILE?
question. Startup must be restarted at least from the beginning of the section
which contained the card in error •
• CARD BELOW IS OUT OF ORDER
Startup Message.
the program.
The control statement indicated is in the wrong position in
Operator Action: Correct the statement sequence and retry.
System Startup manual for sequence requirements •
Refer to GCOS 8 OS
• CARD BELOW SPECIFIED REMOVABLE DEVICE
Startup Message.
Startup attempted to edit a file on a removable disk device.
Operator Action: Either assign the file to a PERM device, or reconfigure the
device as a PERM device and initialize the disk pack.
6-23
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
.CARD CHAR ILLEGAL, i coe dd: BACKSPACE, OPERATE WEll READY
Startup Message.
An
illegal character was sensed by the card reader.
Operator Action: Remove the last card from the output stacker, place it in the
input hopper, and press OPERATE/RESET. If the message is repeated, correct or
replace the incorrect card, backspace, and press OPERATE/RESET.
.CARD
{PUNCH }
{READER}
i-ccc RELEASED
GPOP Message. The specified device could not be assigned by Startup because
either the power is off or the device is in an offline condition.
Operator Action: Either run the system without the device or ready the
specified device and enter an ASGN request. The device may not be aSSigned
while the system is running, if assignment requires initializing the catalogs •
••• CATALOG COMPRESSION ERROR •••
{A)BORT, (C)OITIHUE
Save/Restore Message. An illegal type continuation catalog was found on the
save tape. The user is identified.
Operator Action: Check the save tape and/or the MASLIST/CLIST reports for
discrepancies. Enter A to abort or C to continue the restore. If the C option
is used, restore activity will continue with the next user identifier •
••• CATALOG RELOCATION ERROR •••
(A)BORT, (C)OITIHUE
Save/Restore Message.
An error occurred on catalog relocation.
Operator Action: Enter A to abort or C to continue. If the continue option is
selected, restore continues with the next user, and a message is output on the
printer identifying that the user was not restored.
6-24
DH13-04
C
C
OUTPUT MESSAGES
\
OUTPUT MESSAGES
••• CATALOG RESTORE COMPLETE FROM DEVICE SAVE ST1 •••
File Management Supervisor Message. If a restore is to be performed from
multiple device saves, the catalogs must be restored from the ST1 device saves
before other restores can be initiated.
Operator Action:
None •
••• CATALOG SPACE TABLES OVERFLOWED•••
(A)BOR'l', (C)ONTIRUE
SavelRestore Message. The disk packs are fragmented (more than 20 descriptors
to map the user catalog structure).
Operator Action: Enter A to abort or C to continue. If the continue option is
selected, restore continues with the next user, and a message is output on the
printer, identifying that the user was not restored.
C.DIR ABT BLK# xxxxxx ON yy
GPOP Message. An 1/0 failure occurred on the cleanpoint directory.
Bootloading terminates.
Operator Action:
Contact the Honeywell Bull Response Center.
CHI INVALID
GPOP Message. The operator entered an illegal channel (PUB) number (not
8-31). The channel is not configured or the channel has been released.
Operator Action: Reenter the input message i f it is incorrect. If the channel
was not configured, insert the correct $ 10M statement in the configuration
program and restart the program. When the channel is released by a console
message, enter an ASGN message.
6-25
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
CHARGE?
Startup Message. System asks the operator if the options listed on the
$ ANSWER statement(s) are to be ignored.
Operator Action: Enter YES to ignore options.
system perform the options •
Enter NO or press EOM to have
• CHARGE > 5 MIN, YES TO ACCEPT?
Startup Message. Permits reentry of the time if the operator attempted to
change time by more than five minutes.
Operator Action: Enter time change. If "NO" is entered in reply to the "ENTER
TIME" question, it will be repeated •
• CHANGE DATE?
Startup Message.
Issued when the "CHANGE?" question is answered "YES".
Operator Action:
Enter YES to change the date and time •
• CHAIGE SYSTEM COlT ROLLER CLOCK?
Startup Message. Asks if the system controller clock setting is to be
changed. A NO response will cause normal Startup console display to continue
and no change will be made in the system controller clock setting. A YES
response will cause the -DATE? and -TIME? messages to occur which permits the
operator to change the system controller clock setting •
• CHAIGE TIME?
Startup Message. Issued when the "CHANGE?" question is answered "YES" and
always follows the "CHANGE DATE?" message.
Operator Action:
Enter YES to change the time.
6-26
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
-CHANNEL ALREADY DEFINED
Startup Message.
Second channel on $ CHAN statement was previously defined.
Operator Action: Correct $ CHAN statement or remove I/O controller statement
for applicable channel and reboot.
-CHANNEL ALREADY DEFINED ON $ MPC-N CARD
Startup Message.
One channel can be connected to only one MPC.
Operator Action:
Correct the $ MPC statement and reboot.
CHARNEL NOT DEFINED AS MPC DEVICE ON $ IOM-n, $ lHO-n, OR $ XBAR
Startup Message. A channel named on a $ MPC statement was not previously
defined on a $ 10M, $ lMU, or $ XBAR statement.
Operator Action: Correct the $ MPC statement or add the $ 10M, $ lMU, or
$ XBAR statement.
-CHANNEL NOT DEFINED AS URMPC DEVICE ON $ IOM-n OR $ lMU-n
Startup Message. When special URMPC port assignments were being defined, a
channel specified that a URMPC device type was not defined.
Operator Action:
Correct the $ MPC statement and reboot.
-CBAIREL lUMBERS OUT OF ORDER
Startup Message.
The channel numbers specified are not consecutive.
Operator Action:
Correct $ MPC statement and reboot.
6-Z7
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
.CHAIlEL ccc OR IOI-n RELEISED, ROT CONFIGURED 01 SSF
Startup Message. Startup read a $ lOX statement that attempted to configure a
channel that is not listed in the System Support Facility (SSF) configuration
file.
Operator Action:
Correct error using one of the following alternatives:
o
Use System Maintainability Availability Software (SHAS) Interactive
Configuration (ICON) facility to configure the channel.
o
Delete the conflicting statement.
o Use the $ CHAN statement to move the devices to another channel.
{IMO}
.CHANNEL - nnn ON {10M} NOT DEFINED OR MPC-n
{lOX}
Startup Message.
The MPC-n statement is missing for the specified channel.
Operator Action:
Add the missing MPC statement and reboot •
• CHECK STEM COLLECTOR sssss-aa ON 1-ccc-dd
STEM (PERSUE-8) Message.
Operator Action:
Tape drive i-ccc-dd is in check status.
Ready the device or exchange for another •
••• CHECKSUM ERROR •••
(A)BORT, (C)ONTlNUE
Save/Restore Message.
activity.
Operator Action:
A checksum error occurred during an SMC llink read
Enter A to abort or C to continue restore.
6-28
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
.CHECKSUM ERROR, FILE filename, CADOT PROCEED
Startup Message. The header block on one of the programs, in a file described
by a $ SYSTEM statement, contains a checksum error.
Operator Action:
statement.
Reboot and re-edit the file indicated on the $ SYSTEM
'CHECKSUM ERROR, FILE PRINTIMAGE
'ANSWER YES TO IGNORE ERROR AlID CONTINUE
'ANSWER NO TO ABORT, & THEN EDIT PRIHTIMAGE
Startup Message. Startup detected that the presence of $ IMAGE statements, in
the $CONFIG section, caused a checksum error. If the TVIM program was running
while the system was operational, a difference in content causes the checksum
error.
Operator Action: Enter YES to use the existing images.
abort startup. Edit the print1mage on the next boot.
Enter NO (or CR) to
CHECKSUM ERROR IN MPC BOOT DECK
MPC Bootload Program Message. The MPC boot load program that was loaded
contains a checksum error. A mispunched or missing statement could cause the
problem.
Operator Action: Check The bootload program and reboot Startup.
recurs, a new bootload program should be created.
If the message
CHECKSUM ERROR IN SHC LLINK
CLASS on CIT?
Save/Restore Message.
operation.
A checksum error occurred on the SMC llink during save
Operator Action: Enter C to continue, in which case this class will be
bypassed and the save function will continue with the next class; or, enter I
to ignore, in which case the save function will continue as if the error never
occurred (which can, however, lead to further problems, depending on the
condition of the SHC llink); or enter T to terminate the save function
operation.
6-29
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
-CHECKSUM ERROR, MODULE name, CANNOT PROCEED
Startup Message.
checksum error.
The module control block or the file itself contains a
Operator Action:
statement.
Reboot and re-edit the file indicated on the $ SYSTEM
-CHECKSUM ERROR ON SSFILE, MUST EDIT SSFILE AGAIN
Startup Message. The $ SSFILE statement used for autoload was not valid when
read from mass storage.
Operator Action:
Reboot from $FILES.
-CHECKSUM ERRORS LISTED ON PRINTER, SAVE THEM
Startup Message. Checksum of Part A of Startup (main body of code) failed. A
list of the changed Startup locations will appear on the printer. Startup may
or may not continue to run normally.
Operator Action: Notify site techniques personnel who should initiate a System
Technical Action Request (STAR).
-i cee dd: CHG PACK Innnnn?
Startup Message. Startup wrote and rechecked the disk pack label information
requested. At this point the operator may approve or change the label.
nnnnn - Pack number now in the pack label
Operator Action: If the label is correct, enter NO or EOM to complete
initialization. If not, enter a new pack number to change the label.
CKSUM ERROR, BKSP 2 CARDS sssss-aa
Source/Object Library Editor Message. An illegal checksum was encountered
while reading *C assigned to an online card reader.
Operation Action:
None.
6-30
DH13-04
C
OUTPUT MESSAGES
C
OUTPUT MESSAGES
CKSUM ERROR CARD READER 1 cee SlUMS sssss
TO REREAD-BACKSPACE n CARDS AND TYPE B
TO CONTINUE WITH NO FURTHER CKSUMMING-TYPE C
Bulk Media Conversion Message.
card in the input data deck.
BMC encountered a checksum error on a binary
Operator Action: Reposition in the input hopper the last one or two cards read
and enter either B or C.
*CKSUM ERROR IN READING xxxxxxxx xxxxxxxx CANNOT PROCEED
Startup Message.
The system file
Operator Action:
Re-edit the file.
~xxxxxxx
xxxxxxxx cannot be read.
••• CLASS xx •••
Restore Message. This message follows the SMC error message n._-READ DISC
ERROR ••• n, where xx is the class indicated during a device restore of the
substructure. This is an informative message.
Operator Action:
None •
• CLEAR AND OVERWRITE EXISTING DECKFILE?
Startup Message. A $ DECKFIL statement was read in from the card reader, other
than at Autoload, specifying an overwrite option after the size (1600/0). An
existing deck file was found during the $INITIALIZE section processing (after
the controller for the AUTOLOAD device was booted) and decks are to be saved
(even if found on the existing deckfile). This message allows the operator to
clear the existing deckfile such that new firmware can be written in correct
order if there are ITR or MDR revisions. The ITRs and MIRs must be in the
correct order such that MOLTS can run successfully.
Operator Action: Enter YES to clear the deckfile. Enter NO or EOM if the deck
file is not to be cleared. To inhibit this message, remove the /0 from the
$ DECKFIL statement.
6-31
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
CLI PT. DISABLED DUE TO SET UP ERROR (S)
GPOP Message. Errors occurred, either while attempting to establish file space
for passing restart levels to FMS, or while attempting to clear cleanpoint
entries resulting from cessation of cleanpointing. The system has disabled
cleanpointing.
Operator Action: Correct the cause of cleanpoint warning messages. If
cleanpoint is desired, then schedule a system reboot after the errors have been
corrected.
•
{SD.INJ}
{SD.SBT}
{SD.JOT}
{SD .BDI}
{SD.JOS}
{SD.SCA}
{.CRSLQ}
CLK PT. INIT
&
WRITE EBTRY • MRCV5 ,1 ER nn
Rollcall Message. The specified segment or data encountered an error while
attempting to establish cleanpoint information.
nn - 26
27
28
29
30
31
32
33
34
35
Unknown SeT address or device name
Requested cleanpoint data not found
Cleanpoint recovery table full
Cannot obtain file space
Cleanpointing not in effect
Wrong SNOME accessing entry
DCW problem
Data checksum error
Recovery table I/O error
Device ST1 I/O error
6-32
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
CLI PT. RESTART TBL.SET UP .MRCV5,3 ER nn
GPOP Message. An error occurred, either while attempting to establish file
space for passing restart levels to FMS, or while attempting to clear
cleanpoint entries resulting from cessation of cleanpointing.
nn - 26
27
28
29
30
31
32
33
34
35
Unknown SCT address or device name
Requested cleanpoint data not found
Cleanpoint recovery table full
Cannot obtain file space
Cleanpointing not in effect
Wrong SNOMB accessing entry
DCW problem
Data checksum error
Recovery table I/O error
Device STI I/O error
Operator Action:
Correct the cause of cleanpoint warning message •
• CLOSING SCF Rlrrrrr/Flfffff-sss BLOCKS = bbbb
SCF/Dump Message. Issued based on data in the statistical collection file when
an SCF tape was dismounted by .MACTS during a reel switch that resulted from an
end-of-file condition, an I/O error, or an ACCNT message. Message is issued by
.MDUMP when .MDUMP closes tape accounting. The message is directed to TY2.
rrrrr
fffff
sss
bbbb
-
reel serial number
file serial number
reel sequence number
number of blocks written
Operator Action:
None.
ICMD REJECTED'
Remote Maintenance Interface Message. Transmitted to the remote console if an
attempt to enter an ESC,CNT-I or ESC, CNT-B from the remote is made without
IEnable Initialize true.
Operator Action:
None.
6-33
DH13-04
C
OUTPUT MESSAGES
C
OUTPUT MESSAGES
.COMMA NOT FOLLOWED BY AN ETC CARD NEAR: (Card Image)
Startup Message. A statement in the Startup program ended with a comma and was
not followed by an $ ETC statement. The message is output with the statement
image.
Operator Action: Check the statement that was printed and the previous
statement. Either add the missing $ ETC statement or repunch the faulty
statement without an ending comma. Then enter GO.
CONCATENATED file-name SMC-user1d BUSY
File and Record Control. In the process of concatenating the file file-name,
the PRMFL was found to be busy. The system retries the access every minute
until the access is successful. The busy message is printed every five
minutes.
Operator Action:
None •
• COIFIG CARD BELOW CORTAINS UNDEFINED PRIMARY CHANNEL
Startup Message. The primary channel (i.e., the first channel on the $ XBAR
statement) described by the $ XBAR statement was not previously defined on a
$ 10M statement. The contents of the erroneous statement are output following
the message.
Operator Action:
Correct the $ XBAR statement or define the primary channel •
• CORPIG CARD BELOW SPECIFIES DUPLICATION
Startup Message. The channel crossbar arrangement described involves a
secondary channel which was previously configured. The contents of the
statement are output following the message.
Operator Action:
Correct the $ XBAR statement.
6-34
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
*$CORFIG HOT FIRST CARD
Startup Message. An EOF statement or some other BCD statement appears before
the $ CONFIG statement.
Operator Action:
Correct the job stream and enter GO.
*COHFIG_MAP FILE NOT FOURD, YES TO COITIllUE?
Startup message. Startup cannot find the configuration map to verify that the
proper packs are mounted.
Operator Action: Enter YES which causes Startup to create a new configuration
map file. Enter NO or EOM to abort.
*CONFIG MAP WRITTEN TO DEVICE ddd
Startup Message. This message is sent every time that a new CONFIG MAP file is
written. Device ddd can be any GCOSFILE device.
Operator Action:
None.
CORFIGURED xxx PRIITER FOURD yyy PRIITER 01 ioodd
FII $CORFIG SECTION PRINTER DEFIIITIOR
Where:
xxx = MPC
yyy = URP
or
xxx
yyy
= URP
= MPC
i = Iyy input/output controller number
cc = Channel number
dd = Device number
Startup Message. A configured printer was found to be defined via the wrong
type statement for the MPC type ($ MPC-n or $ URP-n). Startup will correct the
internal tables; however, this can only be deteoted if the printer is online
and ready. If released the error would propogate to the operating system where
it could not be corrected thus the $ MPC-n or $ URP-n statement should be
corrected.
6-35
DH13-04
C
OUTPUT MESSAGES
C
OUTPUT MESSAGES
NOTE: This could inadvertenlty result if Startup aborts during $CONFIG section
processing when a default printer is found and used (assumed to be an
MPC) but th~ $ URP-n card has not yet been processed. Ignore the message
under these conditions.
Operator Action:
Correct the statement •
• CONTROL CPU NOT DEFINED ON $ MeT/, CIU
Startup Message. Startup is executing in a CPU that is not defined on a $ CIU
or $ MCT statement.
Operator Action: Correct the $ CIU or $ MCT statement or correct the SCU MASK
PORT SELECT SWITCH and reboot from switches to cause a defined CPU to start
executing •
• CONTROL CPU PORT TURNED OFF
Startup Message. The $ MCT statement specified the option OFF for the port for
the currently executing control CPU.
Operator Action: Correct the $ MCT statement or change the SCU MASK PORT
ASSIGNMENT SWITCH on the control SCU and reboot from switches to cause the new
CPU to start executing as the control CPU •
• CONTROL CPU WAS MARKED RELEASED IN PRIOR BOOT
ENTER YES TO CONTINUE WITH CURRENT CONTROL CPU
Startup Message. An auto boot was performed, but the DPS-8 SCU MASK PORT
ASSIGNMENT SWITCH was changed to cause the reboot to execute on a CPU which was
marked released on the prior boot.
Operator Action: Enter YES to cause startup to crontinue - the current control
CPU will not be marked release and NO to cause the output of the REBOOT USING
NEW CONTROL CPU message •. None if the answer is YES, otherwise change the seu
MASK PORT ASSIGNMENT SWITCH on the control SCU and reboot from switches to
cause the new CPU to start executing as the control CPU.
6-36
DH13-04
C
OUTPUT MESSAGES
C
OUTPUT MESSAGES
CONTROL PROCESSOR PORT IS INCORRECT
Startup Message. The wrong SCU port is specified on the MCT-O statement for
the control processor. This message is followed immediately by the n*CONFIG
CARD BELOW CONTAINS AN ERROR NEAR COLUMN nnn message.
Operator Action:
Correct the appropriate statement and bootload.
ICONSOLE ENABLEDI
Remote Maintenance Interface. Transmitted to the local or remote console (when
the IENABLE CONSOLE command is entered at the remote console) when exiting from
the Maintenance Mode.
Operator Action: None.
*CPU-x ACCESSED WRONG SCU-x
WRONG PORT POSSIBLY ENABLED
Startup Message. Prior to surveying each slave CPU, startup writes the
beginning byte address of each SCU into the beginning word of each SCU. Each
slave CPU will read the beginning address of each SCU from the beginning word
of each SCU (and one's complement the beginning byte address and write it
back). When the control CPU detects that the slave CPU has finished and has
parked itself , the control CPU reads back the first word in each SCU expecting
to find the one's complement of the starting byte address of the SCU. This was
not found. The slave CPU found that the word read from an SCU matched the
expected value but the slave CPU was accessing an SCU that is not even sWitched
on for the control CPU.
Operator Action: Correct the port assignment switches for the appropriate CPU
(the control CPU could be the incorrect one) and re-boot from switches.
6-37
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
.CPU-x PORT-y ACCESSED LOCATION LLLLLLOOO AT ADDRESS A!AAAAOOO,
PORT ASSIGRMENTS POSSIBLY WRONG
Startup Message. Prior to surveying each slave CPU, Startup writes the
beginning byte address of each seu into the beginning word of each seu. Each
slave CPU will read the beginning address of each seu from the beginning word
of each SCU (and one's complement the beginning byte address and write it
back). The slave CPU detected that the word read from the seu did not match
the expected value. Either the slave CPU is accessing secondary seu's in an
opposite order from the control CPU (if the low seu was incorrectly accessed
then the slave CPU would probably not even respond) or possibly accessing a SCU
that is not even switched on for the control CPU.
Operator Action: Correct the CPU port assignment switches or port enable
switches and re-boot from switches •
• CPU-x CANNOT ACCESS SCU-y
PORT POSSIBLY NOT ENABLED
Startup Message. The control CPU did the memory survey and it is known how
many SCU's the control CPU could access. The slave CPU did not have a port
enabled for the specified control CPU accessable SCU.
Operator Action: Turn on the port enable switches for the slave CPU so it can
access the specified seu or turn off the associated control CPU port enable
switches such that it does not access the specified SCU •
• CPU-w PORT-x CONFIGURED ON SCU PORT-y, FOUND ON SCU PORT-z,
PORr DEFINITION ON $ MeT/$ CIU POSSIBLY WRONG
Startup Message. Each CPU reads the SeU configuration register from each seu
and verifies that the SCU port through which the CPU is accessing the seu
matches the defined port on the $ MCT statement.
Operator Action: Correct the port definition on the $ MCT statement (that is
not caused by incorrect switch settings, the port cables are actually wrong).
6-38
DH13-04
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
.CPU-n CACHE CONTROL (BITS 54-62) WAS
WNW,
SHOULD BE
888
Startup Message. Cache may not be fully enabled and system performance may be
degraded. This is informative message only. Startup will not abort.
n = CPU number
= was value
sss = should be value
www
Operator Action:
Response Center •
Check the cache enable switches or call the Honeywell Bull
• CPU n DID NOT RESPOND
THE FOLLOWING MUST BE PERFORMED:
TERM OS
DETACH CPU
BOOT FROM MAINTENANCE CORSOLE
Startup Message.
A second CPU did not respond to the Startup connect.
Operator Action:
As directed •
• CPU-x PORT-y ENABLED FOR NON-ENABLED seu,
PORT ENABLE SWITCH POSSIBLY WRORG
Startup Message. Startup memory survey for DPS-8 terminated because of memory
error. This occurred before reaching the SCU selected by the CPU port switches
(if this is the control CPU, then the CPU port switch could be enabled but not
the SCU port switch). This indicates potential problems since the SCU is
assumed to be released but could still send a CONNECT to the CPU.
Operator Action: Either set the CPU port enable switch OFF, or the SCU port
enable switch ON, or correct the problem which caused the memory survey to
terminate early (CPU port size incorrect on prior SCU or MSU switched off line
or prior seu Non-Existant Address switches set wrong etc.) then reboot startup
from switches.
6-39
DH13-04
C
C
OUTPUT MESSAG!S
OUTPUT MESSAGES
.CPU-x PORT-y, ERROR ACCESSIRG SCU-z
SCU PORT POSSIBLY ROT ERABLED
Startup Message. The control CPU did the memory survey and is known how many
SCU's the control CPU could access. The slave CPU had a port enabled for the
specified SCU but encountered a fault while accessing the SCU. The SCU may
have the port enable switch turned OFF, the CPU may be getting errors accessing
the SCU (port logic failure), or the wrong SCU may be enabled for the slave
CPU.
Operator Action: Correct the appropriate switches, or have CSD fix the faulty
hardware, or switch off the SCU from the control CPU (to come up without the
memory defined, also advisable to remove the $ MCT statement for the SCU to
prevent later re-assigning of the memory with resultant memory errors from the
slave CPU), or select the correct SCU (could be the control CPU incorrectly set
up in switches) •
• CPU n HALTED (ARD AUTOMATICALLY RELEASED) UNDER (PI mmmmm sssss
Dispatcher/FALT/POQ3 Message. A CPU's process has stopped due to a malfunction
or due to the detection of a maintenance stop condition. The process in
execution will be moved to another processor, aborted, or left "hanging". The
processor is marked released.
n - number of the halted processor
mmmmm - KPX number of the process
sssss - SNUMB of the process
A second line is usually printed.
messages:
It will be one of the following major status
RELIEF OF THE FAULTING CPU COMPLETE
A second CPU completed the process that the released CPU was executing when
it failed.
RELIEF PROCESSING ROT POSSIBLE
The process could not be retried in a second CPU.
6-40
DH13-04
~
C
C
OUTPUT MESSAGES
OUTPUT MESSAGES
CPU WOULD ROT RESPOND TO CORRECT REQUEST.
FALT/SD.GTW automatically released a CPU that would not respond to a connect
within a one-minute period (for all hardware platforms except DPSE, which is
allowed to delay its response up to four minutes).
A concise, detailed explanation of the CPUs minor status is normally provided.
It may be one or more of the following messages:
NO PROGRAM IN EXECUTION
TSS SUBDISPATCH WAS IN PROGRESS
NO PROCESSOR AVAILABLE TO CONTINUE EXECUTION
SYSTEM PROCESS WAS RUNNING
.STATE BITS PRECLUDE ABORTING PROCESS
PROCESS WAS IN TYPE 2 CRICTICAL SECTION
SAFESTORE STACK OVERFLOWED ON THE FAULT
RELIEF OF THE FAULTING CPU COMPLETE
The following instruction may be added if the halted CPU is a DPS 8:
PLS COpy HALTED CPU'S REGISTERS IC,IR,ISR,ETC
This information cannot be gathered automatically on a DPS 8; however, it is
required by maintenance personnel when investigating the problem.
The following information may be added if the halted CPU is a DPS 8000:
SP TO SAVE THE CPU STATE AND RUN NFT TESTS
If the RAQ queue is full, prohibiting the DPS 8000 automatic information
retrieval process, the following message will be printed:
RAQ FULL - COULD NOT START THE SAVE OR NFTS (POQ3)
The following information will be printed if the processor release fails:
AUTO REQUEST RELEASE OF THE CPU.
PLEASE REQUEST RELEASE OF THE CPU.
An attempt to release the CPU using the RLSEP verb is in order. If the RLSEP
command fails, then a message indicating the nature of the failure will be
printed on the console.
6-41
DH13-04
QC
OUTPUT MESSAGES
C
OUTPUT MESSAGES
If the process was left hung, then the following warning message will be
printed:
••• PROCEED WITH CAUTION - NOTIFY TAC •••
Operator Action: Having a process left hung could produce negative
consequences. It is of upmost importance that a qualified expert evaluate the
failure. In some cases, the process may be aborted after resetting its
execution bit (PS.EXC) in the PST. Other cases may require that the system be
rebooted to clear the failure.
o
.CPU-x NO COllECTABILITY FOUID
EITHER THE CPU WAS NOT CONFIGURED IN THE SERVICE PROCESSOR COIFIG FILE
OR MAY HAVE BEEI RELEASED/DETACHED BY THE SERVICE PROCESSOR.
TYPE YES TO RELEASE AND CONTINUE; NO TO TERMINATE:
Startup Message. The $ CIU statement specified a CPU for which no
connectability was found from the DPS-88 CIU or DPS-8000 SCU.
Operator Action: To continue without the specified CPU, enter YES and startup
will mark the CPU as released, otherwise correct the DPS-88 ICON file or the
DPS-8000 service processor config file to assign the CPU and then reboot from
switches •
• CPU n ROT FOUID, CHECK • MCT CARD
Start up Message. There is a lapse in the CPU configuration. The $ MCT
statement must define CPU~O and all defined CPUs must be contiguous.
n - Processor (CPU) number
Operator Action: Check the $ MCT statements in the startup program for
inconsistencies •
• CPU-x PORr-y SCU-z PORr SIZE MISMlTCH
PORT SIZB SI'lTIIG POSSIBLY VBORG
Startup Message. The CPU port size switches do not reflect the SCU size as
defined on the $ MCT statement.
Operator Action: Correct the • MCT statement or correct the CPU port size
switches and re-boot Startup trom switches.
6-42
DH13-04
~
C
OUTPUT MESSAGES
C
OUTPUT MESSAGES
*CPU-n RELEASED, NOT CONFIGURED ON SSF
Startup Message. Startup detected a Central Processing Unit (CPU) that is
configured in the GCOS system but not in the System Support Facility (SSF).
Startup will not abort.
Operator Action: Use the System Maintainability Availability Software (SMAS)
Integrated Firmware and Diagnostics (IFAD) facility to configure the CPU or
delete the CPU from the $ CIU statement.
*.CRMTP RCfRY ERR-LOST-SIEVE LIMITS SET FROM
CONSOLE IN PRIOR BOOT
Rollcall Message. SIEVE LIMIT data could not be recovered. The SIEVE LIMITS
will be set to the system defaults or to those provided via $ INFO data.
Operator Action:
Reenter the SIEVE LIMITS that had been set via the console.
CROSS COpy QUEUE ENTRY ERROR FOR LINES xx=>yy
Time Sharing Message. One copy of TSS received a queue entry to switch
terminal line xx to UST with line id yy. TSS was unable to accomplish the
switch.
Operator Action:
None.
6-43
DH13-04
SKCTlOK 1
OUTPUT MESSAGES BEGIDIBG WITH THE LETTER D
DATA CAPTURE OPTIONS: option(s)
ENTER [(O)PTION], (U)SE • AHSWER, OR (K)ORE.
Dump Message. The system operator must choose between the default options
displayed by the DATA CAPTURE OPTIONS: message, and those options set in the
$CONFIG section on a $ANSWER DUMP card.
Operator Action:
o
(O)PTION or EOM will cause DUMP to display the following list of
additional options.
o
(U)SE causes DUMP to use the options specified on the $ ANSWER statement.
o
(N)ONE should be used if dump should not be taken.
·DATE'?
Startup Message.
Startup detected a value not within the limits indicated.
Operator Action:
Enter correct date •
• DATE mmddyy TIME hh .mmm
.CHAHGE SYSTEM CONTROLLER CLOCK'?
Startup Message. Inform the operator of the current setting of the System
Controller Clock date and time, and allows the operator to specify whether or
not to change it. The message is displayed when the response to "CHANGE?" was
"YES".
mm
dd
yy
hh
= month
= day of the month
= year
= hours (24 hour clock)
.mmm = millihours
Operator Action:
None.
7-1
DH13-04
D
OUTPUT MESSAGES
D
OUTPUT MESSAGES
• DBC DEVICES MUST BE SEQUENTIAL EVER/ODD PAIRS
Startup Message. A pair of DBC devices were not configured as an even/odd
(EVEN,EVEN+1) pair of devices.
Operator Action:
Correct the card and reboot •
•••dd1 AND dd2 ARE BOTH CAT DEVICES. USER xxxxxxxx •••
Save/Restore Message. User xxxxxxxx has original and duplicate catalogs on
devices dd1 and dd2 for which a device restore is attempted. Restore Skips to
the next user.
Operator Action:
None.
DDT APE: DEVICE NAME NOT FOUND
Operator Interface Message. The device name table does not contain the device
name entered with the DDT APE verb.
Operator Action:
Select an appropriately named device.
DDTAPE: DEVICE UNAVAILABLE
Operator Interface Message. The device which was requested with the DDTAPE
verb is not currently available.
Operator Action: Request a different device which is currently available or
wait until the requested device is available.
DDTAPE:
ILLEGAL FORMAT - SIB
SNUMB
DEV-NAME,FC
Operator Interface Message. The system recognized an improper format; the
format must be: SNUMB Device Name File Code.
Operator Action: Enter the SNUMB, device name, and file code correctly when
using the DDTAPE verb.
7-2
DH13-04
D
D
OUTPUT MESSAGES
OUTPUT MESSAGES
DDT APE: INVALID FILE CODE
Operator Interface Message. The system recognized an improper file code. This
is commonly caused by a file code entry which was left blank or made zero.
Operator Action:
Enter the correct file code with the DDT APE verb.
DDTAPE: SRUMS NOT FOUND
Operator Interface Message. The SNUMB which was entered with the DDT APE verb
is incorrect, or the job is not in execution.
Operator Action:
Enter correct SNUMB or establish job execution.
DDT APE: TABLE SIZE EXCEEDED
Operator Interface Message.
The table size of 30 entries was reached.
Operator Action: Wait until entries are free or use DDTAPE verb to remove
unneeded devices.
DDT APE:
WRONG DEVICE NAME
Operator Interface Message.
incorrect.
Operator Action:
The device name entered with the DDTAPE verb is
Enter correct device name with the DDTAPE verb.
DEAD Ie xxxxxx PGM I ppp sssss AT tt.ttt
IC+I aaaaaa bbbb PRC c WSR d WSI eee MOD ftf
ISR BASE gggggggggggg E1 hhhhhhhhhhhh 01 111111111111
Dump Message. Program number ppp (SNUMB sssss) called .MBRT1 from location
xxxxxx to cause a system dump. (Fast bootload is not active.) No fault
occurred. An informative message only.
aaaaaa
bbbb
c
d
eee
-
Instruction counter
Indicator register
Processor number
Working space register number
Working space number
7-3
DH13-04
D
D
OUTPUT MESSAGES
fff
gggggggggggg
hhhhhhhhhhhh
iiiiiiiiiiii
Operator Action:
OUTPUT MESSAGES
-
Module number
Base of instruction segment (words)
Even instruction
Odd instruction
None.
-DECK TO BE SAVED BAS ALL ZERO DATA
Startup Message. A binary deck input to the Startup $INITIALIZE section was
invalid for the reason specified. This situation is very improbable.
Operator Action:
Reassemble data deck and reboot.
-DECK TO BE SAVED HAS ZERO SIZE
Startup Message. A binary deck input to the Startup $INITIALIZE section was
invalid for the reason specified. This situation is very improbable.
Operator Action:
*DECKFILE
Reassemble data deck and reboot.
{CATALOG CBEc[SUM ERROR}
{FILE SIZE ERROR
}
{BLOC[ HUMBER ERROR
}
{NO. OF ENTRIES ERROR }
{ENTRY DATA ERROR
}
{EITENSION FILE ERROR }
Startup Message. An existing program file was found, but the catalog is bad
for the reason specified.
Operator Action: Verify that the disk pack containing the DECKFILE is mounted
on the proper spindle and is correctly defined in the $CONFIG section. If it
is, the existing deck file must be purged to eliminate the error.
7-4
DH13-04
D
OUTPUT MESSAGES
D
OUTPUT MESSAGES
{FULL
.DEF TRACK HIST TABLE
}
{I/O ERROR } dv i-cco-dd
{CKSUM ERROR}
TRACK tttttt SW1-ssssssssssss (I/O Error only)
Exception Processor Message. The update of the defective track history table
was unsuccessful, because of either an error condition or exhausted table.
dv - Device type
tttttt - Defective track address (octal) that would have been inserted
s ••• s - Status word 1
Operator Action:
«<
None.
Slsssss DEFERRED RECOVERY DIRECTIVES STARTING
Integrated Software Message.
execution.
»>
Printed when the deferred recovery process begins
sssss - Deferred recovery process SNOMB
Operator Action:
«<
None.
Slsssss DEFERRED RECOVERY DIRECTIVES COMPLETE
»>
Integrated Software Message. The deferred recovery utility (processing LIST,
RECOVER, and/or ANALYZE directives) terminated, and no apparent error exists.
sssss - Deferred recovery process SNOMB
Operator Action:
«<
Examine the deferred recovery reports for more information.
Slsssss ••• nnnnn DEFERRED RECOVERIES FAILED (see listing) •••
»>
Integrated System Message. Deferred recovery was not successful for one or
more processes. The listing indicates which deferred recoveries failed and the
reason for the failure.
sssss - Deferred recovery process SNUMB
Operator Action:
Examine the deferred recovery reports for error information.
7-5
DH13-04
D
OUTPUT MESSAGES
D
OUTPUT MESSAGES
The following 'DEFERED RECOVERY' console messages are suppressed when
-SUPPRESS MESSAGES {YES} option is specified for the RECOVER directive.
«<
Slsssss DEFERRED RECOVERY {xxxxx }
{ wsnue }
NO PROTECT FILE TO RECOVER »>
sssss - deferred recovery process SNUMB
xxxxx - batch process SNUMB for which deferred recovery is attempted
wsname - workstation name for which deferred recovery is attempted
Integrated Software Message.
One of two conditions exists:
1. The system aborted during a deferred recovery run after protected files
were recovered but before recovery structure was released. A subsequent
deferred recovery run will generate this message. The structure is
released at this time.
2. The system aborted or a process "disaster" occurred immediately after a
commitment unit was opened and before any before images were written to
the journal.
Operator Action:
«<
None.
Slsssss DEFERRED RECOVERY {xxxxx
}
{w~ue}
HOT ELIGIBLE - IT IS ACTIVE
»>
sssss - deferred recovery process SNUMB
xxx xx - batch process SRUMB for which deferred recovery is attempted
wsname - workstation name for which deferred recovery is attempted
Intregrated Software Message. File structure for active batch or workstation
processes is not a candidate for recovery.
Operator Action:
None.
7-6
DH13-04
D
OUTPUT MESSAGES
D
OUTPUT MESSAGES
«<
Slsssss DEFERRED RECOVERY {xxxxx }
{ wsname }
HOT RECOVERED - BAD PAT FILE »>
sssss - deferred recovery process SNUMB
xxxxx - batch process SNUME for which deferred recovery is attempted
wsname - workstation name for which deferred recovery is attempted
Integrated Software Message.
usable.
The PAT image file for the process was not
Operator Action: Check the summary report (SYSOUT report code
why recovery was not complete.
«<
01)
to determine
Slsssss DEFERRED RECOVERY {xxxxx }
{ wsname }
NOT RECOVERED - NO STRUCTURE »>
sssss
- deferred recovery process SNUMB
xxxxx - batch process SNUMB for which deferred recovery is attempted
wsname - workstation name for which deferred recovery is attempted
Integrated Software Message. No recovery structure exists or there is an
incomplete structure on SYS RECOVERY/JOURNAL for the batch process or
workstation.
Operator Action:
«<
None.
S#sssss DEFERRED RECOVERY
{xxxxx
}
{ wsname }
HOT SUCCESSFULLY RECOVERED
sssss
»>
- deferred recovery process SNUMB
xxxxx - batch process SNUMB for which deferred recovery is attempted
wsname - workstation name for which deferred recovery is attempted
Integrated Software Message. The file structure was not successfully recovered
to its most recent known state (i.e., commitment).
Operator Action: Refer to the summary report (SISOUT report code
determine why recovery was not complete.
7-7
01)
to
DH13-04
D
OUTPUT MESSAGES
D
OUTPUT MESSAGES
«< Slsssss DEFERRED RECOVERY %%Xxx PROBLEM IN DEFERRED RECOVERY»>
sssss
xxxxx
- deferred recovery process SNUMB
- batch process SNUMB for which deferred recovery is attempted
Integrated Software Message.
An undetermined error occurred.
Operator Action: Check the summary report (i.e., SYSOUT report code 01) to
determine what problems exists.
«< S#sssss DEFERRED RECOVERY {xxxxx }
{ wsname }
SKIPPED PER USER DIRECTIVE »>
sssss - deferred recovery process SNUMB
xxxxx - batch process SNUMB for which deferred recovery is attempted
wsname - workstation name for which deferred recovery is attempted
Integrated Software Message. The option -CLEANUP ONLY {YES} was specified for
the RECOVER directive. As a result, no deferred recovery is performed for the
batch process or workstation indicated.
Operator Action:
None.
«< S#sssss DEFERRED RECOVERY {xxxxx }
{ wsname }
RECOVERY HOT NEEDED »>
sssss - deferred recovery process SNUMB
xxxxx - batch process SNUMB for which deferred recovery is attempted
wsname - workstation name for which deferred recovery is attempted
Integrated Software Message. File structure for this batch process or
workstation reached a known state (i.e., commitment) before the failure
occurred.
Operator Action:
None.
7-8
DH13-04
D
D
OUTPUT MESSAGES
«<
OUTPUT MESSAGES
Slsssss DEFERRED RECOVERY {%%XXX }
{ vsname }
RECOVERY NOT REEDED - LOCKS?
sssss - deferred recovery process SNUMB
xxxxx - batch process SNUMB for which deferred recovery is attempted
wsname - workstation name for which deferred recovery is attempted
Integrated Software Message. The recovery structure is in a setup or
end-of-activity state. Because either (1) protected files were not updated or
(2) protected file updates were complete, no recovery action is required.
However, protected files allocated to the process may not have been
deallocated. Consequently, spurious abort locks or busy counts may exist.
Operator Action: Check the detailed file name list in report code 01 to see if
any files remain abort locked.
«<
DEFERRED RECOVERY {xxxxx }
{vsname}
SUCCESSFULLY RECOVERED »>
SI88888
sssss - deferred recovery process SNUMB
xxxxx - batch process SNUMB for which deferred recovery is attempted
wsname - workstation name for which deferred recovery is attempted
Integrated Software Message. The file structure was successfully recovered to
its most recent known state (i.e., commitment).
Operator Action:
«<
SI88888
None.
DEFERRED RECOVERY wsname WORKSTATION NOT RECOVERED
»>
sssss - deferred recovery process SNUMB
wsname - workstation name for which deferred recovery is attempted
Integrated Software Message. All processes associated with the workstation
indicated were not recovered.
Operator Action: Refer to the summary report (SYSOUT report code 01) to
determine why recovery was not completed.
7-9
DH13-04
D
D
OUTPUT MESSAGES
OUTPUT MESSAGES
.DENSITY IS dddd sssss ieee dd •••
lOS Message. Indicates density of the MTS500/600 or MTU0400/MTU0500 tape unit
on the specified inp channel.
dddd - Density (6250, 1600, 800, 556, or 200 bpi)
Operator Action:
None.
DEV BSY and RLSED
GPOP Message. System reply to an operator RLSE message. The device for which
release was requested is busy and cannot be released at that time. System
releases device after its use is finished.
Operator Action:
None.
DEV INVALID
Peripheral Allocator Message. The operator entered an illegal device number;
the device is not configured; or the device has been released.
Operator Action: Reenter the input message if it was incorrect. If the device
was not configured, insert a correct $ 10M statement in the configuration deck,
reboot and restart the program. When the device has been released by a console
message, enter an ASGN message.
ieee dd DEVICE ALREADY ASSIGNED
GPOP Message. The operator attempted to assign the specified device but the
operating system determined that this device is already assigned.
Operator Action: No further action is required.
normal operations on this device.
7-10
The operator may continue
DH13-04
D
D
OUTPUT MESSAGES
OUTPUT MESSAGES
DEVICE xxx CORTAINS NON-STRUCTURED REMOVABLE PACK - REQUEST IGNORED
Disk Space User Report Message. The removable device named by DSUR option xxx
contains a non-structured removable pack. Any SECTOR entries for this device
will be ignored.
Operator Action: DSUR cannot search for space on a non-structured removable
pack. Enter the correct device name if the non-structured device name was
entered in error •
•••DEVICE DIRECTORY CHECKSUM ERROR •••
{A)BORT, (C)ORTINUE
Save/Restore Message.
read.
A checksum error occurred on the device directory being
Operator Action: Enter A to abort or C to continue restore. If the continue
option is selected, restore continues with the next user, and a message is
printed identifying the user that was not restored.
DEVICE x MISMATCH ON i-ccc-dd
CONFIG = y, IPC = z
DEVICE RELEASED
Startup Message. The FIPS disk device specified in the startup configuration
section does not match the IPC configuration table. In the message forms
below, type is used to specify a FIPS disk device type (e.g., MSC1A).
x
a NUMBER
b TYPE
y
dd
type
c FORMAT
d STATUS
type
type
z
UNDEF
type
UNKNWN
UNFMI'D
NOTONL
Message form a appears when the device number in $CONFIG is not found in the
IPC CONFIG.
7-11
DH13-04
D
D
OUTPUT MESSAGES
OUTPUT MESSAGES
Message form b appears when $CONFIG device does not match IPC CONFIG device
(e.g., CONFIG=MSC1A, IPC=MSC1B). Startup aborts at the end of section
processing unless IPC=UNKNWN appears.
Message form c appears for unformatted FIPS device.
removable, it will be changed to a stranger device.
removable, the message
If the device is
If it is not marked
UNFORMATTED DEVICE MUST BE "RMVBL"
appears.
Startup aborts at the end of section processing.
Message form d appears if the device is not online (i.e., powered off).
Operator Action: If Startup aborts at the end of section processing, correct
the error and reboot the system •
••• DEVICE
i-ccc-dd
NOI-ALLOCATABLE BY 'PALC STATUS=ssssss, RELEASED
Peripheral Allocator Message: While attempting to allocate device i-ccc-dd the
Peripheral Allocator attempted an I/O to the device and received the exception
status "ssssss". It then released the device.
ssssss - Upper half of I/O status word 1
Operator Action:
device •
After exception condition has been corrected, assign the
• DEVICE ddd NOT DEFIlED
Startup Message.
The device indicated was not defined on the $ 10M statement.
Operator Action:
Correct the $ 10M statement and restart.
DEVICE xxx NOT FOUND
Disk Space User Report Message. The DSUR DEVICE name input (xxx) could not be
found in the System Configuration Name Table. Any SECTOR entries for this
device will be ignored.
Operator Action:
Enter a valid device name.
7-12
DH13-04
D
D
OUTPUT MESSAGES
OUTPUT MESSAGES
-DEVICE dd NOT SYSTEM STORAGE
Startup Message. The device indicated is not a system storage device. If the
device field (dd) is RES, there is no $ SAVE statement for the storage file for
Startup and Dump (i.e., DUMP file).
Operator Action:
Assign the device to system storage and retry.
-DIRECT/CLEAR WILL FORMAT ALL TRACKS GOOD, YES TO CORTINUE
Startup Message. A user's or manufacturer's pack is being initialized for the
first time, and a $ DIRECT CLEAR statement is also in the job stream for this
pack. This condition will result in the loss of all pack-resident information
about the user's or manufacturer's known bad areas.
Operator Action: Remove $ DIRECT CLEAR statement and reboot, unless the
situation described is desired. If situation is desired, enter YES.
-DIRECTORY FULL, DEVICE ddd
Startup Message. The maximum of 62 entries was made in the bad llink
directory. The directory statement listed on the console following this
message is ignored and the next statement processed. When the next End-Of-File
(EOF) is encountered, Startup aborts.
Operator Action: Advise the site techniques personnel of the situation.
Possible action may involve replacing the pack or releasing the device (if it
is not required) which may necessitate a Startup deck change. In addition, the
Honeywell Bull Response Center may need to repair the device.
-DISC ERROR i
OCO
dd eeeeee CANNOT PROCEED
Startup Message. One of the following statuses exists: Instruction Rejected,
Device Busy, Invalid Control Character, or an Illegal Status.
eeeeee - Error status
Operator Action: If the disk is not an online device, as described in the
Configuration section, correct the condition.
7-13
DH13-04
D
D
OUTPUT MESSAGES
OUTPUT MESSAGES
-DISC ERROR, i ccc dd eeeeee END MESSAGE WHER READY
Startup Message.
An
Attention status was detected.
eeeeee - Error status
Operator Action:
at the console.
-DISC
i-ccc-dd
The disk is not online.
Correct the condition and press EOM
RELEASED--CAN'T BUILD AST--JYYYYY
Peripheral Allocator Message. An error occurred when the Peripheral Allocator
attempted to build the AST for the specified (non-physically removable)
structured removable pack. The drive has been released.
yyyyyy - Reason code for the error. May be of the form STATUS xxxxxxxxxxxx
where xxxxxxxxxxxx is the status.
Operator Action:
-DISC
i-ccc-dd
Refer to your own Site Administrator for further questions.
RELEASED--CAN'T READ LABEL-STATUS=xxxxxxxxxxxx
Peripheral Allocator Message. An 1/0 error occurred when Peripheral Allocator
attempted to read the label of the specified (non-physically removable)
removable pack. The pack has been released.
xxxxxxxxxxxx. Operator Action:
-DISC
i-ccc-dd
rio
Status returned word
Refer to your own Site Administrator for further questions.
RELEASED-LABEL INFO DESTROYED.
Peripheral Allocator Message. The label of the (non-physically removable)
removable pack is not formatted properly. The drive has been released.
Operator Action:
Notify techniques.
1-14
DH13-04
D
OUTPUT MESSAGES
D
OUTPUT MESSAGES
DISC PACK ERROR i ccc dd eeeeee END MESSAGE WHEN READY
Startup Message.
A Device Attention status exists on a disk device.
eeeeee - Error status
Operator Action:
Correct the problem and press EOM.
The I/O will be repeated.
DISC PACK ERROR i ccc dd eeeeee ILLEGAL STATUS
CANNOT PROCEED
Startup Message.
Startup aborts.
An illegal status occurred on the specified disk device.
eeeeee - Error status
Operator Action: Correct the problem (perhaps requiring a call to the
Honeywell Bull Response Center) and reboot.
-DISC PACK SELECT ADDRESS ERROR
Startup Message.
A seek address error exists on a disk device.
Operator Action:
Retry.
-DISC SC, CLOSED OK
DUMP Message. The contents of the Statistical Collection File (SCF) buffers at
the time of the call to .MDUMP were written onto the SCF and an EOF was written
on the file. This message is applicable when disk accounting is defined.
Operator Action: YES to the SCF CONTINUATION? message on next boot to save the
data for automatic purge to tape.
-DISC SEEK ADDRESS ERROR, i cce dd CAIIOT PROCEED
Startup Message. The Seek address calculation routine was given a nonexistent
link or llink number, a nonconfigured device, or illegal arm positioning.
Operator Action: Check CONFIG and EDIT cards for accuracy. Physical
configuration of the system should be compared to that described on the cards.
7-15
DH13-04
D
D
OUTPUT MESSAGES
OUTPUT MESSAGES
•••DISK CACHE CAN'T GET BACKDOOR SPACE •••
Rapid Access Data System Message. The control program attempted to create a
temporary file for printing statistics using the SYSOUT backdoor feature and
was denied file space. The statistics are lost if the CLEAR parameter is
specified for the STATS option. If the CLEAR parameter is not specified, the
statistics are accumulated until the next reporting period.
Operator Action:
None •
•••DISK CACHE HAS BEEN SHUT DOWN AT mmddyy hh:mm:ss
Rapid Access Data System Message. The Rapid Access Data System (RADS) is shut
off and the RADS memory is released starting at the month, day, year, hour,
minute, and second indicated.
Operator Action:
None.
••• DISK CACHE HAS ·CACHE OFF" FOR ALL DISKS
Rapid Access Data System Message. The options specified on the I. option file
for Rapid Access Data System (RADS) prevent RADS from caching any data. RADS
will continue to run, accumulate statistics, and print its reports.
Operator Action: None, if RADS is being run just to accumulate statistics and
print reports. Otherwise, ABORT the control program, change the DEVICE
parameters on the I. option file to specify which disks to cache, and start the
control program again •
•••DISK CACHE OPERATIONAL AT mmddyy hh:mm:ss
Rapid Access Data System Message. The Rapid Access Data System (RADS) is
turned on and the RADS memory is assigned at the month, day, year, hour,
minute, and second indicated.
Operator Action:
None.
7-16
DH13-04
D
D
OUTPUT MESSAGES
OUTPUT MESSAGES
---DISK CACHE OPTION FILE NOT PRESENT - DEFAULTS WILL BE USED
Rapid Access Data System Message. An option file is not referenced by either a
$ DATA I- file or a $ PRMFL 1* file, or it is not under the default
OPNSUTIL/DISCACHE catalog/file string (no JCL reference needed).
Operator Action: Provide the default OPNSUTIL/DISCACHE file or the I* option
file and its JCL statement unless all the default values of the SDC parameters
are not acceptable.
--- DISK CACHE SET LOCK WRITE TRRU BECAUSE OF COMMON FILES ENVIROIMEIT
Rapid Access Data System Message. The "lock write thru" option was forced
because all RADS writes are "write thru" rather than "write into" on a common
file system.
Operator Action:
None.
DISK FILES FULL, OVERWRITE (Y OR 1)1
Dump Message. When attempting to dump to disk, all dump files (DUMP1-DUMP9)
contain data. The operator must determine whether or not to overwrite existing
data with the new dump.
Operator Action:
The following responses are available:
Enter NO (EOM or N) - The dump will not be written to a disk file, and the
dump question will be repeated to allow the operator
to select tape or printer output.
Enter YES(Y) - The disk file with the oldest date/time will be
overwritten by the dump.
NOTE: If the FASTBOOT option is specified for restart, the YES response to
the overwrite question is implicit. Any condition that prevents the
completion of the dump to disk turns off the FAST BOOT option (e.g., no
dump file defined, dump file too small, etc.)
7-17
DH13-04
D
D
OUTPUT MESSAGES
OUTPUT MESSAGES
DISK FILES NOT COIFIGURED
Dump Message. The system attempted to write a dump to a disk file (i.e., to
DUMP1-DUMP9). However, the file was not defined at system startup on a
$ FILDEF statement.
Operator Action: The message ENTER [(O)PTION, (U)SE $ANSWER, OR (N)ONE 1s
issued to the console. The operator may enter:
D - Dumps memory to the output device specified on the $ ANSWER statement in
the Startup job stream.
N - Discontinues the dump.
o-
Allows the operator to select the dump device by the SELECT DEVICE:.
Subsequently, mass storage files can be defined in the Startup job
stream for dump purposes and the system can be rebooted.
DISK PACK ERROR i ccc dd: TRACK ZERO BAD
Startup Message. Startup cannot format track 0 or it was found to be bad using
the "TEST" option.
Operator Action: This pack cannot be used in this condition.
Honeywell Bull Response Center.
Notify the
-DISK PACK ERROR; ccc-dd (status)
-FN TYPE "GO·, OR TYPE "STOp·
Startup Message. An unrecoverable error was detected while trying to read or
write a disk pack. Status is the 12-digits octal for the first status return
word (refer to GeOS 8 OS I/O Programming. manual for the specific meaning of
this status).
Operator Action: Correct the condition causing the status and enter GO. If
the condition is uncorrectable, enter STOP, replace the failing unit, and
reboot.
7-18
DH13-04
D
D
OUTPUT MESSAGES
.DLT
OUTPUT MESSAGES
88888 XXXXX
Peripheral Allocator Message.
the reason specified.
The Peripheral Allocator has deleted the job for
xxxxx - Reason:
STRING ERROR
EXCESS DATA
NO RU FILE
BAD PASSWORD
NO FILE CODE
PERMS DENIED
NO DEVICE
NO PACK II
FORMAT ERROR
MISSED LUD
SCC INVALID
MULTI-PRINTER
PRMFL ERROR
NO SUCH NAME
NO CIPT FILE
LIMITS ERROR
NO PUNCH
MULTI-READER
FILE SIZE
TAPE CATALOG
NO $ PRODUCT
NEED $IDENT
CORE DROUTH
00 FILE CODE
Operator Action:
• »LT
ILLEGAL FC
RMC JCL ERR
FC/LUD ERROR
NO ACTIVITY
NEED PPS ID
NO FILENAME
NO ENDJOB
NTAPE EXCESS
NEED USE RID
FG ERROR
BAD J* FORM
INVALID DISP
EXCESS n LUD
PACK DROUTH
None •
S8888 XXXXX
Scheduler Message.
specified.
The System Scheduler has deleted the job for the reason
xxxxx - Reason:
BAD J* FORM SYS SCHED
I/O ERROR
Operator Action.
None.
7-19
DH13-04
D
OUTPUT MESSAGES
D
OUTPUT MESSAGES
*DLT Slsssss-aa xxxxx
Scheduler Message.
specified.
The System Scheduler has deleted the job for the reason
OPERATOR DELETE
CLASS CATALOG EXHAUSTED
M-S-L I/O ERROR
$ MSG3 CARD -- BAD DATE
$ MSG3 CARD -- BAD TIME INTERVAL
TRANSPORT JOB HAS BEEN DELETED
Operator Action.
None.
*DLT 81sssss CANT READ J* FILE
Peripheral Allocator Message. There is a mismatch in the SNUMB as it appears
on the J* file with the SNOMB as it appears in the JCT in ALC1 or as it appears
in the SD.SNB segment.
Operator Action:
None.
*DLT Slsssss-aa IMPROPER CONTROL CARDS
Peripheral Allocator Message. The job control statements contain a fatal
error. Details concerning the error will appear on the job execution report.
Operator Action:
None.
The system will delete the job.
*DLT Slsssss tc I/O ERROR II .PALC
Peripheral Allocator Message. An I/O error occurred while the Peripheral
Allocator was doing an I/O on the file indicated.
fc - File code of the file on which the I/O error occurred.
Operator Action:
None.
7-20
D813-04
D
OUTPUT MESSAGES
*DLT
SlSS88S
D
OUTPft
~AGES
(X1)
Peripheral Allocator Message. A job was deleted as the result of an ABORT
sssss option request by the operator or a JABT sssss request from TSS.
Operator Action:
None.
*DMr i-ccc-dd REEL #nnDnn Slsssss-aa TO xxxxx B-M-C
Peripheral Allocator Message. The specified magnetic tape is to be dismounted
and to be used as the input tape to the $ CONYER activity which was spun off as
job xxxxx from job sssss.
Operator Action: Dismount the specified tape and retain it pending running job
xxxxx.
*DMr TAPE-SIsssss (i-ccc-dd) (fc)
Allocation/Termination Message.
program.
The specified file was released by the
Operator Action: Dismount and save the tape.
*DMr UNIT-Slsssss i-ccc-dd(fo)[, i-ccc-dd(fc)]
Peripheral Allocator Message.
tape unites).
Requests the operator to dismount the specified
fc - File code of the file on the specified unit
Multiple files may be included in one *DMT UNIT message.
included, the message occupies more than one line.
Operator Action:
If enough files are
Dismount the tape(s) from the specified unites).
7-21
DH13-04
D
D
OUTPUT MESSAGES
OUTPut MESSAGES
-DOES sssss-aa Mr i
000
dd (to) tile-name HAVE A VOL:mmmm YN
Standard COBOL-68 IIO System Message. An unlabeled or user-labeled file
reached the end of an input reel. The operator must determine whether to treat
this reel as the end of file or attempt a reel swap.
file-name - 12-character file identifier supplied by the file assignment
statement (will be suppressed if not present)
mmmm - Reel sequence number within file
Operator Aotion:
Enter Y if there is another input reel. Processing
continues.
Enter N if another input reel is not present. The current
reel will be treated as the end of the file.
-D,O,L,I DEVICE TYPE VROIG - FIX, HIT EOM
Startup Message. The named device on a D, 0, L, I, or A card is not the same
type as the device type specified on the $ DIRECT statement.
Operator Action:
Correct the card and press EOM.
DOR'T UNDERSTAND
PLEASE ERTER ORE OF THE FOLLOWING:
PRINT OR EOM
PRI
(EG PR1 PR2)
DISK
DRIVE-NAME/TAPEI,DENSITI
(EG 114/12345,1600)
Dump Message.
The operator has made a mistake in selecting a device.
Operator Action:
The device selection should be input again.
DRCPNC HAS BEEN REPLACED - PLEASE USE REDRC
GPOP Message.
The verb DRCPNC was replaced with the verb REDRC.
Operator Action:
Use the correct verb, REDRC.
7-22
DH13-04
D
D
OUTPUT MESSAGES
OUTPUT MESSAGES
8888S DSUR OPTIOIS = (D nx OR S NNNRNNN,MMM)
XX = DEVICE NAME
NNHNIII = STARTING SECTOR NUMBER II OCTAL
MMM = NUMBER OF CORSECUTIVE SECTORS II OCTAL
BB88B ENTER ONE OPTION -
Disk Space User Report Message. An input r* file for the DSUR program is not
present. The operator is asked to input the appropriate disk address via the
console. The ENTER ONE OPTION line may be separated from the first four lines
by other console traffic. This line of output leaves the keyboard unlocked for
operator entry.
Operator Action: Enter the device and sector information (one entry per line)
in the following format:
(D)EVICE XXX
followed by,
(S)ECTOR NNNNNNN,MMM
(EOM or Return key)
(S)ECTOR NNNNNNN,MMM
(EOM or Return key)
(EOM or Return key)
where:
xxx - The name of a disk device that contains a permanent disk or a
structured removable pack
NNNNNNN - An octal sector address (1-7 digits)
MMM - A one- to three-digit octal number of consecutive sector addresses
(two-digits maximum for MSU0501 devices)
At least one device parameter followed by one sector parameter must be
present. Up to 100 input sector parameters are accepted. Multiple sector
ranges are placed one range to a SECTOR entry following the appropriate
(D)EVICE entrY$ All sector ranges pertain to the last device encountered on a
(D)EVICE entry ..
When the last entry has been made, press the End-or-Message or Return key, or
enter DONE or EOM (without entering a device name or sector address).
7-23
DH13-04
D
D
OUTPUT MESSAGES
OUTPUT MESSAGES
-DUAL BOT Mr 1-ccc-dd
88888
AST / FIX+RDY AF?
Exception Processor Message. Multiple BOT (beginning-or-tape) marks exist on
the designated device media. The tape reel is not usable in this condition.
The tape will be unloaded automatically.
Operator Action: Enter A - Abort the job.
Enter F - Fix the tape reel by removing the second BOT mark
and remounting the reel. GeOS will reposition the
tape and retry the original command.
DUMPn I/O ERROR STATUS
88888
Dump Message. An error occurred while the dump was being written to mass
storage. The status or the error is defined by sssss.
Operator Action: The message .-*DUMP (O)PTION/(D)EFAULT/(N)ONE is issued to
the console. To continue the dump operation, the operator can enter the 0
option, causing the PRINT TAPE/I, DENSITY DISK OR NONE? message to be issued.
The operator can then choose another dump device. D causes the dump to be sent
to the device specified on the $ ANSWER statement. N causes no dump to be
taken.
DUMP TAPE FULL ENTER TAPE/NEXT REEL I
Dump Message. The current reel is full, and DUMP is requesting an additional
tape handler and reel.
Operator Action:
Enter (DDD/tapel').
7-24
DH13-04
D
D
OUTPUT MESSAGES
OUTPUT MESSAGES
---DUMP (O)PTION/(D)EFAULT/(N)ORE?
Dump Message. In response to the console entry of the DUMP verb, an
unrecoverable system error, or a manual fault executed from the processor.
operator can continue or discontinue the dump operation.
The
Operator Action:
Enter D - Dump memory to the output device specified on the $ ANSWER
statement in the startup job stream.
Enter N - Discontinue the dump.
Enter 0 - Allows the operator to select the dump device. The following
message is issued:
PRINT TAPEII,DENSITY DISK OR NONE?
where:
PRINT - Dump to printer (PR1) and causes the
"DUHP:ALL,HCM,SOFT,SLV,Wxxx-yyy,ppp,
REAL,NPURE,NON,OPTS(-)SD.xxx,.Mxxxx,
PH.xxx, PSH,SSF,HIS,TRC,COM,PTW,ONLyn
message to be printed at the console. If PR1 is not
available, the message n.SELECT PRINTER DEVICE" is
issued. The operator can:
o
Enter the logical device name of another online printer
or,
o
Press EOM, whereupon the "DUMP
(O)PTION/(D)EFAULT/(N)ONE?n message is again output.
TAPE/I,DENSITY - Dump to the tape identified by tape device name, reel
number, and density (if other than system default).
DISK - Dump to available disk dump file (DUMP1-DUMP9). If no
dump files are allocated this message will be repeated to
allow printer or tape selection.
NONE - Discontinue the dump_
7-25
DH13-04
D
D
OUTPUT MESSAGES
OUTPUT MESSAGES
DUMP WROTE xxxxxx LLIRICS OR DUMPn
Dump Message. A dump to the disk file is completed. The number of LLINKS
(xxxxxx) occupied on the dump file (DUMP1-DUMP9) is defined. An informative
message.
Operator Action:
-DUMP WHITTER TO
None.
DUMPn
Startup Message. The operator replied ftDISKft to the ftpICK ONE DUMPft message.
Following successful completion of the dump writeout, Startup informs the
operator that the dump was written to the DUMP file (DUMP 1 through DUMP9).
Operator Action:
None.
-DUPLICATE FILE CARD BELOW IGNORED
Startup Message. There is more than one of the following card types in the
deck: $ LIBRARY, $ ACCOUNT, $ SAVE, $ SYSTEM, and $ SYSOUT. The contents of
the duplicated card are output following the message.
Operator Action: Remove the duplicate card.
contained on the first card read.
7 -26
Startup will use the information
DB 13-04
SECTION 8
OUTPUT MESSAGES BEGINNING WITH THE LETTER E
-ECOL FOUND A SLOW CACHE ON PORT n
ECOL Message. The Cache timing test found a slow cache on the processor
configured on SCU-O Port n. (There is less than 13% improvement between cache
enabled and cache disabled.) This indicates that cache may be malfunctioning.
Operator Action: Contact supervisory personnel to determine if system
availability necessitates continuing to run with slow cache. If not, two
options are available. The operator can dynamically release the malfunctioning
processor (if multi-processing) and notify the field engineers of its
availability for repair. A second option involves disabling cache via the
console input message ECOL CSHOFn (n = 0-7, processor connected to SCU-O port).
ECOL REQUEST DENIED; CPU OFF LINE
ECOL Message. The operator action was denied. If the CPU specified in the
request was not a DPS 88, the following message is displayed:
ECOL REQUEST DENIED; INVALID FOR THIS CPU
Operator Action:
None.
ECOL REQUEST DENIED; CSH DISABLED
ECOL Message. In response to the operator input ECOL CSHOFn, and system
communication region cache status bit (in .CRCMM+3, bits 0 to 7) for the port
indicates that the cache memory on the port is already disabled (DPS 8/20 &
8/44 systems only).
Operator Action:
None.
8-1
. DH13-04
E
E
OUTPUT MESSAGES
OUTPUT MESSAGES
ECOL REQUEST DENIED; CSH ENABLED
ECOL Message. In response to the operator input EeOL CSHONn, and when system
communication region cache status bit (in .CRCMM+3, bits 0 to 7) for the port
indicates that the cache memory on the port is already enabled. (DPS 8/20 &
8/44 systems only).
Operator Action:
None.
ECOL REQUEST DENIED; IN EXECUTION
ECOL Message. In response to the operator input ECOL START, and with the ECOL
program is already in execution.
Operator Action:
None.
ECOL REQUEST DENIED; INVALID
ECOL Message. An ECOL verb and its options are entered or formatted improperly
at the system console. The action requested has been ignored.
Operator Action:
Reenter the message in the proper format.
EcaL REQUEST DENIED; NO PROCESSOR
ECOL Message.
The processor specified was not configured.
Operator Action:
Enter correct designation of configured processor.
ECOL REQUEST DENIED; PTL DISABLED
ECOL Message. In response to the operator input ECOL PTLOFn, and when system
communication region status bits (in .CRCMM, bits 24 to 30) for the port
indicate that PATROL is already disabled for the processor. (DPS 8/20 & 8/44
systems only.)
Operator Action:
None.
8-2
DH13-04
E
E
OUTPUT MESSAGES
OUTPUT MESSAGES
ECOL REQUEST DENIED; PTL ENABLED
ECOL Message. In response to the operator input ECOL PTLONn, and when system
communication region status bits (in .CRCMM, bits 24 to 30) for the port
indicate that PATROL is already enabled for the processor (DPS 8/20 & 8/44
systems only).
Operator Action:
None.
-EDIT?
Startup Message. Asks whether to process the statements between $EDIT and the
following ---EOF.
Operator Action: Enter YES, NO, EOM, or PARTIAL. A YES answer causes all
files to be edited automatically. A PARTIAL answer causes a separate question
to be asked for each statement or statement type in the $EDIT section to
determine if that statement should be processed. The following questions are
asked:
EDIT FILENAME?
PROCESS SSFILE CARD?
If more detailed information is required, refer to GCOS
manual.
~
OS System Startup
-EDIT CARD BELOW CONTAINS ERROR NEAR COLUMN nn
Startup Message. A statement format error exists. The contents of the
statement are output on the console following the message.
nn - Column number
Operator Action:
Replace the erroneous statement with a corrected statement.
-EDIT CARD BELOW SPECIFIES FILE IN UNKNOWN FORMAT
Startup Message.
The file being edited is in the wrong format.
Operator Action: Verify the format field on the $ FILDEF statement listed,
either SIS or RDM. If this field is in error, correct the statement and
re-edit. If that is not the case, a new tape is required or the edit tape is
in the wrong density.
8-3
DH13-04
E
OUTPUT MESSAGES
E
OUTPUT MESSAGES
-EDIT CARD BELOW SPECIFIED FILE WITH BAD CHECKSUM
Startup Message.
The data on the tape file is bad.
Operator Action:
Get a new edit tape or do not edit this file.
-EDIT CARD BELOW SPECIFIES TOO FEW LLINKS
Startup Message. While SYS or RDM copy function defined on a FILDEF statement
is being processed, the file being copied is found to be longer than the size
indicated. The contents of the statement are output following the message.
Operator Action: Check that the tape being copied is the proper one, and
correct the size field on the FILDEF statement.
EDIT CATALOG/FILENAME?
Startup Message. When EDIT is answered with PARTIAL, this question is asked
with every $ FILDEF statement.
Operator Action:
Answer YES if this FILDEF statement is to be processed.
EDITOR sssss-aa ENTER: language FOR: routine name AT:
Source Library Editor Message.
by the Source Library Editor.
Operator Action:
tt.tt~
A special trace of routines is being assembled
None.
-END
Startup Message.
The Startup dump is completed.
Operator Action:
None.
This message will be followed by another question.
8-4
DH13-04
E
E
OUTPUT MESSAGES
OUTPUT MESSAGES
END sssss-aa @ tt.ttt (abort reason)
Termination Message. The specified activity was aborted by the system for the
reason stated. Further explanation of the abort reason can be found in the
GCOS 8 OS Programmer Messages And Abort Codes manual.
sssss - Job
aa - Last activity of job
tt.ttt - Time of day
The job was terminated by peripheral allocation for one of the following
reasons:
o Fatal errors occurred during compilation.
o
A $ GOTO or $ IF JCL statement caused a skip to a label and the label
either does not exist or does not have an activity following it.
o
A $ GOTO or $ IF JCL statement caused a skip to ENDJOB and the latest
activity of the job aborted.
Operation Action:
None.
-END sasss-aa @ tt.ttt • (abort reason)ROLLBACK?
Termination Message. An abnormal termination condition exists that affects job
sssss, and the JROLL option has been specified in the JCL. The operator is
asked if a rollback to the nearest checkpoint is desired. Further information
of the "abort reason" can be found in the GCOS 8 OS Programmer Messages And
Abort Codes manual.
Operator Action:
Respond YES to affect the rollback if the abort reason code
indicates the error condition is operational in nature (i.e.,
hardware problems, operator error), as opposed to programming
errors.
Respond NO to continue termination activities. The message
is repeated without the "ROLLBACK?" to verify the termination
of the activity.
Any other response causes the message to be repeated every 30
seconds until a YES or NO entry is made.
8-5
DH13-04
E
E
OUTPUT MESSAGES
OUTPUT MESSAGES
-END sssss-aa tt.ttt ACTY DELETE
Peripheral Allocator Message. The job was terminated by peripheral allocation
because of fatal errors during compilation or because the last activity in the
job which went into execution aborted, but that activity has at least one other
activity following it in the JCL.
Operator Action:
None.
-END OF TAPE ENTER FILE NAME
Startup Message. During an edit, FIND was given as an option to a label check
message. The requested file does not exist on this tape. A list of all files
on the tape is output after this message.
Operator Action: Reply with one of the file names on the tape, or enter a new
name and mount a new tape.
ENTER GESEP OPTIONS, EOM WILL GIVE ALL
Summary Edit Program Message. This message provides for input of options
through the console. (Refer to GCOS 8 OS Accounting manual.)
Operator Action:
Enter one of the following:
A or EOM - Prints all records and summary.
E - Forces termination of Summary Edit Program.
o - Retypes options message and disregards previous option entries.
S - Prints only the summary report and type 9 and 12 records.
n, ••• ,n - Prints selected record types (1-7) and (14-18).
8-6
DH13-04
E
OUTPUT MESSAGES
E
OUTPUT MESSAGES
ENTER THE HUMBER OF THE rIP TO BE DUMPED
DATANET 355/6600 Dump Program (855D) Message. Requests the operator to enter
the number of the DATANET 355/6600 processor to be dumped.
Operator Action:
messages •
Enter 0-7.
System will reply with one of the following
• FNP In NOT CONFIGURED
.FNP In DUMPED SUCCESSFULLY
.FNP In NOT DUMPED - (reason)
.NOT ENOUGH MEMORY ASSIGNED TO 355 DUMP PROGRAM - INCREASE LIMITS AND
AGAIN
RUN
.ENTER TIME OR ENTER A CORRECTION FACTOR?
Startup Message.
answered "YES".
This message 1s issued when the "CHANGE TIME?" question is
Purpose: To allow the operator to change System Controller Clock time, which
1s independent of GCOS time.
Operator Action:
The response can be one of the following:
o
Enter time in normal manner.
o
Enter a correction factor in the same format used to answer the "TIME?"
question preceded by a plus (+) or minus (-) sign.
Example: +01:20
In this example, one hour and 20 minutes will be added to the value of
the system controller clock •
• ROJ sssss-aa tt.ttt
Termination Message. The job was terminated by normal termination of the last
activity of the job, or the job was terminated by peripheral allocation when a
$ C~TO or $ IF JCL statement caused a skip to ENDJOB and the latest activity of
the job underwent normal termination.
Operator Action:
None.
8-7
DH13-04
E
OUTPUT MESSAGES
E
OUTPUT MESSAGES
-EOJ PGM on tt.ttt
Termination Message. A job that was not input through System Input has
terminated. Does not have a control stack or J- file.
Operator Action:
None.
-EOT sssss-aa Mr 1 ccc dd
Standard COBOL-68 I/O System Message. The program attempted to perform a reel
swap on a multiple file reel. Since COBOL rules do not permit the multiple
file/multiple reel configuration, the program is aborted.
Operation Action:
None.
-sssss ERR IN BLDG AST FOR ppppp OR i-ccc-dd STATUS xxxxxxxxxxxx
Peripheral Allocator Message. An error occurred when the Peripheral Allocator
attempted to build an AST for the structured removable pack.
ppppp - Pack number
xxxxxxxxxxxx - Error status
Operator Action: None if the error is transient. But if the error cannot be
be recovered use the ABORT sssss reply to abort the job.
---ERR
---ERR WORK SPACE 1 PAGE TABLE IS TOO SMALL.
---ERR USE $ lIFO PT1SIZ/nnnn AND REBOOT.
---ERR
nnnn
= size
of page table for working space 1
POPM Message. The default size of the page table is not sufficient.
size is 2048 words.
Default
Operator Action: Boot using the $ AUTOLOAD file for input, and using the
Startup console editor to add the $ INFO PT1SIZ/nnnn.
8-8
DH13-04
E
OUTPUT MESSAGES
E
OUTPUT MESSAGES
ERROR
ERROR
ERROR
ERROR
ACCESSDING DCAF VECTOR TO SPT
ACCESSING DCAF V-BLDOCK
ACCESSING DCAF IN-HEM MESSAGE DATA
ACCESSING DCAF IN-HEM OPTION DATA
ALL WILL BE USED AS DUMP OPTION.
Dump Message. A DeAF error has occurred.
default DeAF option.
Operator Action:
The ALL option will overwrite the
None.
ERROR IN CREATING RESTART FILE
» file system error message «
Peripheral Allocator Message. During restart processing the Peripheral
Allocator attempted to create the restart file and received an error from the
file system other than non-unique name.
Operator Action:
«<
Abort the system.
Slsssss ••• ERROR IN DEFERRED RECOVERY - See output listing • •••
»>
Integrated Software Message. The listing indicates the error encountered.
Refer to the appropriate table for error explanations.
sssss - Deferred recovery process SNUMB
Operator Action:
Examine the deferred recovery reports for error information.
••• ERROR IN RELEASED DESCR LIST •••
(A)BOHr, (C)OlTlNUE
Restore Message. This message can occur when releasing existing catalog and
file space at the beginning of a Restoremast operation. The descriptor list
could not be sorted properly for the optimal mass storage allocator operation.
Operator Action: Enter A to abort the program or C to continue the restore.
Appropriate personnel should be notified if the situation persists as this can
result in lost mass storage space.
8-9
DH13-04
E
OUTPUT MESSAGES
E
OUTPUT MESSAGES
.ERROR 01 OLD ACerG FILE, nnnnnn GOOD RECORDS
ACTS Message. A bad status was returned when trying to write an end of record
to the accounting file.
nnnnnn - number of good records on the file
Operator Action:
None •
••••ERROR ON OLD Acer FILE-mmmmmm GOOD RECORDS
(yyy)
(optional)
GPOP Message. An accounting tape switch identifies a completed tape and
notifies the operator of any errors.
mmmmmm - Number of good records on the file
yyy - Type of trailer label attempted when error occurred (EOR or EOF)
Operator Action:
Save completed tape for acc.ounting function.
ERROR READING THE SIS ERROR CODE FILE
STAT = (status)
ALL WILL BE USED AS DUMP OPTION.
Dump Message. A DCAF error has occurred.
default DCAF options.
Operator Action:
The ALL option will overwrite the
None.
••• ERROR SPLITTING DESCRIPTORS FOR ABOVE FILE ••••
(A)BOHr, (C)OlTlRUE
FMS Message. Caused by the Replace Directive. While trying to replace
defective disk space more defective descriptors were to be replaced than there
were descriptors for the file.
Operator Action: Enter A to abort the restore, if desired, or C to continue.
The continue option skips to the next file to be replaced.
8-10
DH13-04
E
E
OUTPUT MESSAGES
OUTPUT MESSAGES
••• ERROR WHILE TRYING TO GEK>RE RECVYIRFO FILE •••
(R)ETRI, (C)OHTIRUE?
Restore Message.
unsuccessful.
An attempt to GEMORE the FMS recovery file RECVYINFO was
Operator Action: If possible, wait for a brief period, then respond R to retry
the GEMORE. Try several times. If unsuccessful, contact the appropriate site
personnel before responding C, which will continue processing after ignoring
the GEMORE.
EVEN IDENTIFICATION: message
(message describing what occurred)
DATA CAPTURE OPTIO!: (options that will be dumped)
Dump Message. If the reason for the system to abort was due to the special
DCAF zero opcode, the default set of options will be extracted from the
faulting module or program. These messages will vary, depending upon the
module in which the ZOP occurred.
Operator Action:
None •
• EXCBlIGING i ccc dd FOR x yyy zz, K>VE MEDIA
Exception Processor Message. The operator chose the X option or entered EXCHG,
and device i ccc dd is replacing device x yyy zz.
Operator Action: Move the medium (cards, tape, or disk pack) to the new
device, x yyy zz, and make it ready.
8-11
DH13-04
E
E
OUTPUT MESSAGES
OUTPUT MESSAGES
••• nnnnn EXECUTIVE VERSION
WWWWWW
OFr xxxxxx AT tt.tt P.T.zzzzzzzzzzzz
TOLTS Message. The designated subsystem has terminated normally, not as a
result of wrapup or abort valid for the COLTS, MOLTS, or POLTS subsystems.
MOLTS Termination follows F6 abort memory testing.
{ COLTS
nnnnn - { MOLTS
{ POLTS
wwwwww - TTL statement in mmddyy
xxxxxx - Current date in mmddyy
zzzzzzzzzzzz - Processor time used in milliseconds
Operator Action: Following MOLTS testing, assign all good memory back to GCOS,
using the ASGNC verb. Assign operational communications or peripheral
equipment back to GCOS via the ASGN verb, following successful COLTS or POLTS
testing.
• nnnnn EXECUTIVE VERSION xxxxxx OR Y11111 AT tt.tt
TOLTS Message. COLTS, MOLTS, or POLTS was loaded into memory to initiate
testing of communications equipment, memory associated with a slave F6 abort,
or peripheral equipment.
{ COLTS
nnnnn - { MOLTS
{ POLTS
xxxxxx - TTL statement in mmddyy
YYYYYY - Current date in mmddyy
tt.tt - Time in hours and hundredths of hours
Operator Action:
Monitor testing until completion •
• EXPECT $ DICEND
Startup Message.
statement.
A $ DKEND was not the first statement read after a $ OBJECT
Operator Action:
Correct job stream and continue by pressing EOM.
8-12
DH13-04
E
E
OUTPUT MESSAGES
OUTPUT MESSAGES
-EXPECT $ DKEND BUT READ
Startup Message.
The $ DKEND statement was not found in the object file.
Operator Action:
Correct the object file and restart.
-EXPECT EOF BUT READ xxxxxxxx
ANSWER YES TO CONTINUE TO FILE LOADER
Startup Message.
read.
A **.EOF statement was expected, but a binary statement was
Operator Action: Enter YES to cause Startup to skip the read operation and go
to the system fi.le loader. Enter NO to cause Startup to abort; then correct
the source file and reboot.
-EXPECT EOF BUT READ BINARY CARD
Startup Message.
Statements in the Startup job stream are out of order.
Operator Action:
Correct the job stream and retry.
-EXPECT
{$INITIALIZE}
{$EDIT
}
{$FILES
}
{$LOAD
}
{$PATCH
}
Startup Message. The statement following ***EOF of the last section was not
the expected section or another .**EOF.
Operator Action: Check the startup program sequence and make the necessary
corrections, then enter GO. Enter STOP if the booting process is to be halted.
8-13
DH13-04
E
OUTPUT MESSAGES
E
OUTPUT MESSAGES
*EXPECT INITIALIZE CONTROL DECK
Startup Message. An object program input to the $INITIALIZE section was not
identified as a control statement file (CON did not appear in columns 28-30 or
35-37 of the $ OBJECT statement).
Operator Action: Put the correct control statement file in front of the data
file (DAT in columns 28-30 or 35-37 of the $ OBJECT statement), or correct the
$ OBJECT statement and continue.
*EXPECT INITIALIZE DATA DECK
Startup Message. A data file (DAT in columns 28-30 or 35-37 of the $ OBJECT
statement) did not immediately follow a control statement file (CON in columns
28-30 or 35-37 of the $ OBJECT statement) input to the $INITIALIZE section of
Startup.
Operator Action:
Supply the data deck and continue.
*EXPECT MASK CARD OR BINARY TRANSFER CARD
Startup Message. A MASK or a binary transfer statement did not immediately
follow the Startup job stream.
Operator Action:
Supply the necessary statement(s) and continue.
*EXPECT OBJECT DECK OR ***EOF
Startup Message. The $LOAD section of the Startup job stream contains
something other than object programs.
Operator Action:
Correct job stream and reboot.
8-14
DH13-04
E
OUTPUT MESSAGES
E
OUTPUT MESSAGES
.EXPECT $ OBJECT OR •• -EOF BUT READ
Startup Message. A $ OBJECT statement or ---EOF was expected, but the
statement indicated was read.
Operator Action:
Correct the job stream and continue •
• EIPECTED COMMA AFTER ·xxxxxx·
Dump Message. Syntax error. The option "xxxxxx" was not followed by a comma
separating it from the next option.
Operator Action:
Reenter the options line correctly.
-icccdd EXPECTED PACK NAME yyy FOUND zzz
.YES TO ACCEPT CHANGE
Startup Message. The pack name in the device label (llink 0) is not the same
name that was there on the last bootload.
yyy - Device name on previous bootload
zzz - Device name found on pack
Operator Action: Respond YES to accept change.
Startup to abort.
Any other response causes
-xxx EXPECTED PACK NUMBER 11YYYY FOUND zzzzzz
.YES TO ACCEPT CHANGE
Startup Message. The pack number in the device label (llink 0) is not the same
number that was there on the last bootload.
xxx - Device name
yyyyyy - Device number on previous bootload
zzzzzz - Device number found on pack
Operator Action: Respond YES to accept change.
Startup to aborte
8-15
Any other response causes
DH13-04
SECTIOR 9
OUTPUT MESSAGES BEGIRRIRG WITH THE LETTER F
.FATAL
{CORrIG
}
{EDIT
}
{FILE
} SECTIOR ERROR, STARTUP ABOHrEn
{INITIALIZE}
{PATCH
}
{LOAD
}
Startup Message. A previously described error occurred, which makes
continuation of Startup impossible.
Operator Action:
Perform the actions specified on previous error messages •
• FATAL ERROR RETURR FROM CONTROL DEC(
Startup Message. This message should be preceded by a message from the control
statement file in the $INITIALIZE section of the Startup program.
Operator Action:
Correct Startup program and reboot •
• tttttt!!!!!! FAULT AT nnnnnnnn, CAINOT PROCEED
Startup Message.
A major system fault occurred.
ff ••• f - Fault identification:
SYSTEM
MEMORY
MME
FAULT TAG
TIMER
COMMAND
DERAIL
LOCKUP
CONNECT
PARITY
-
System fault
Memory fault
Master Mode Entry fault
Fault Tag fault
Timer Run Out fault
Command fault
Derail fault
Lockup fault
Connect fault
Parity fault
9-1
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
ILL OP CODE
OP NOT COMP
STARTUP
OVERFLOW
DIV CHECK
EXECUTE
SECURITY 1
DYNAMI CLINK
MISSING SEG
MISSING WS
MISSING PAGE
SECURITY 2
M1JLTIPLE
-
Illegal Procedure fault
Operation Not Complete fault
Startup fault
Overflow fault
Divide Check fault
Execute fault
NSA hardware detected fault
Dynamic linking fault
Missing Segment fault
Missing Work Space fault
Missing Page fault
NSA hardware detected fault
Fault outside Fault type table
nnnnnnnn - Instruction counter
Operator Action: Check the Startup job stream and physical configuration.
Another message should follow.
*ttftffffffff FAULT AT aaaaaa
Dump Message.
A fault occurred during the dump process.
ffffffffffff - Type of fault
aaaaaa - Location of fault
Operator Action:
Select another device or dump option.
*FAULT CHANNEL INTERRUPT i
000
Startup Message.
The input/output controller reported a fault condition.
Operator Action:
Check the hardware, then reboot.
* FAULT IN SIS
SHARED KPX=kkk DOMAIN ID=dddd
Integrated Software Message.
Integrated software.
Indicates an error may have occurred in the
kkk - KPX of process
dddd - domain id
Operator Action: None.
9-2
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
{ON }
{PA } FAULT, RETRY SUCCESSFUL, KPX#xxx, SNUMBssssss,PORT Y
{ IPR }
ECOL Message. RETRY SUCCESSFUL indicates recovery from a transient
processor/memory hardware error condition by the Instruction Retry feature in
the GCOS Fault Processor module.
Operator Action:
None •
•• -FCB m ffxx device i ccc dd sssss RU
Exception Processor Message.
mff xx RU -
A fault channel error occurred.
I for I/O fault
S for System Controller fault
Fault code from system fault word
Instruction code (refer to Appendix A)
Possible operator replies
I/O Faults
(Octal)
00
01
02
03
04
05
06
07
10
11
12
13
14
15
16
17
Fault with no code
Illegal channel number
Illegal service request
Parity error, scratch pad read
256K overflow (OVF)
LPW tally runout, connect channel
Not PCW on connect channel
Control port field all ones
Character position/size Descripancy
No System Control Unit (SCU) response
Parity between modules
Illegal tally control
Page Table Pointer (PTP) fault
Page Table Word (PTW) flag fault
Mode position switch software incorrect
No port selected
9-3
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
System Controller Faults
(Octal)
02
03
05
06
07
10
11
12
13
14
15
16
17
Nonexistent address
Fault as condition
Data parity, store to System Controller
Data parity, in store
Data parity, store to System Controller and in store unit
Not control port
Port not enabled
Illegal instruction
Store not ready
ZAC parity, active module to System Controller
Data parity, active module to System Controller
ZAC parity, System Controller to store unit
Data parity, System Controller to store unit
Operator Action: Enter R to retry, U returns the status to the user program,
and A to abort the program •
---FCB u fff ttt xx device i ccc dd sssss seek address (disk only) RU
Exception Processor Message. A fault channel error occurred.
issued only on DPS 88 systems.)
(This message is
u - Unit
fff - Fault status
ttt - Transaction
xx - Instruction code
RU - Possible operator replies
Channel Faults (u
fff
= 400
= 200
= 100
= 040
= 0)
Central parity error in channel
Status parity error in channel
DCW fault
Data fault
CIU Access Control Faults (u
= 1)
fff = 400 Hyperdata switch parity err'ol"
= 200 Hypertable parity error
= 100 Transfer error
= 040 Buffer parity error
9-4
DH13-04
F
OUTPUT MESSAGES
F
OUTPUT MESSAGES
Channel Service Processor Faults (u = 2)
fff =
=
=
=
=
=
040
020
010
004
002
001
DI channel address error
Buffer parity error
SPM parity error
Transaction faults
Data parity error
Control parity error
Control Word Processor Faults (u = 4)
fff = 002 ALU parity error
= 001 SPM data parity error
Read Register Faults (u = 6)
fff = 001 SPM data/address parity error
System Support Facility Faults (u = 7)
fff = 777 Control swap
Operator Action: Enter R to retry, U returns the status to the user program,
and A to abort the program.
*FCHuffrfrtttt xx device i ccc dd sssss seek address (disk only)
Exception Processor Message. A fault channel error occurred.
issued only on DPS 88 systems.)
u
fffff
tttt
xx
RU
-
R~
(This message is
Unit (u=3 - FIPS Channel fault; u=5 - lOX A fault)
Octal representations of bits 3-17 of the Fault Channel Status Word
Octal representation of bits 24-35 of the Fault Channel Status Word
Instruction code (refer to Appendix A)
Possible operator replies
Operator Action: Enter R to retry, U to return to the user program, A to abort
the program, or contact Field Engineering for an analysis.
)
,
9-5
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
***FD EQUATE LIST ERROR***
(A)BaRT, (C)ONTINUE
Save/Restore Message.
An FD equate list error occurred during restore.
Operator Action: Enter A to abort the job or C to continue. If the continue
option is selected, restore continues with the next user, and a message is
output on the printer, identifying the user that was not restored.
*FILE CARD BELOW CONTAINS ERROR NEAR COLUMN nn
Startup Message. The statement format is incorrect; too many file names or
errors in punctuation. The contents of the statement are output following the
message.
nn - Column number
Operator Action:
Correct the statement.
FILE xxxxxxxxxxxx EXISTS ON DEVICE dd AND WILL BE ACCESSED
INCORRECTLY
Startup Message. File xxxxxxxxxxxx was located on several devices, and Startup
is not sure which file is supposed to be accessed.
Operator Action:
None.
FILE xxxxxxxxxxxx IS NOT ON A GCOSFIL DEVICE AND CANNOT BE
ACCESSED IN .FILES
Startup Message. A file is being created on a device that was not defined on
the $ GCOSFIL statement. Startup will not be able to access the file.
Operator Action: If access to the file is required for completion of startup
activities, resubmit $CONFIG section with corrected $ GCOSFIL statement. If
file access is not required, no action is necessary.
9-6
DH13-04
F
OUTPUT MESSAGES
F
OUTPUT MESSAGES
.FILE IS xxxxxxxxxxxx SHOULD BE xxxxxxxxxxxx SCFR?
(S)TOP, (C)ONTINUE, (F)IND, (R)EWIND
Startup Message. The 12-character label on the total system tape which was
written by the system editor does not match the filename on the $ FILDEF
statement.
Operator Action:
S
C
F
R
-
Respond with one of the following:
Startup will
File will be
Tape will be
Tape will be
response •
stop and start over.
accepted and edited.
searched for the file specified.
rewound. Another tape can be mounted before giving this
• FILE filename UNDEFINED
Startup Message. Either a file described in tile $FILES
previously defined; or a file that is identified in the
$EDIT section resides on a device that was not included
statement. In the case of the $FILES section error, it
".FATAL FILE DEFINITION ERROR" message and Startup will
section was not
$CONFIG section or the
on the $ GCOSFIL
will be followed by a
abort.
Operator Action: Make the necessary corrections to the $ GCOSFIL statement or
to statements in the $EDIT or $FILE sections and reboot •
• FILES DESCRIBED BELOW ARE NOT ON SAME TYPE DEVICE
Startup Message. The multiple files described on a $ SYSOUT statement are not
on the same device type. The contents of the statement are output following
the message.
Operator Action: Delete the file(s) and/or redefine the file descriptions on
the $ FILDEF statements so that files are on the same device.
9~
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
-FILES FOR DISC ACCOUNTING MUST BE AT LEAST 2 LLINKS
Startup Message.
disk SCF.
The $ ACCOUNT statement does not specify enough space for the
Operator Action:
Correct the $ ACCOUNT statement and restart.
-FIRMWARE ID BLOCK REVISION WAS xxxxxx DOESN'T MATCH $ DKEID
BELOW
Startup Message.
The firmware revision levels are not in agreement.
Operator Action:
Get a new copy of the subject firmware.
FLT xxxxxxxxxxxx PGM I ppp BBBBB AT tt.tt
IC+I aaaaaa bbbb PRC c WSR d WSI eee--MOf) fff
ISR BASE gggggggggggg EI hhhhhhhhhhhb OI jjjjjjjjjjjj
Dump Message.
A fault occurred that caused a system abort.
xxxxxxxxxxxx - Type of fault as follows:
SYSTEM
MEMORY
MME
FAULT TAG
TIMER
COMMAND
DERAIL
LOCKUP
CONNECT
PARITY
ILL OP CODE
OP NOT COMP
STARTUP
OVERFLOW
DIV CHECK
EXECUTE
-
System fault
Memory fault
Master Mode Entry fault
Fault Tag fault
Timer Run Out fault
Command fault
Derail fault
Lockup fault
Connect fault
Parity fault
Illegal Procedure fault
Operation Not Complete fault
Startup fault
Overflow fault
Dlvi.de Check fault
Execute fault
9-8
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
SECURITY 1
M~mCU~
MISSING SEG
MISSING WS
MISSING PAGE
SECURITY 2
MULTIPLE
ppp
sssss
aaaaaa
bbbb
c
d
eee
fff
gggggggggggg
hhhhhhhhhhhh
iiiiiiiiiiii
Operator Action:
message.
-
-
NSA hardware detected fault
Dynamic linking fault
Missing Segment fault
Missing Work Space fault
Missing Page fault
NSA hardware detected fault
Fault outside fault type table
Program number of aborting program
SNUMB of aborting program
Instruction counter
Indicator register
Processor number
Working space register number
Working space number
Module number
Base of instruction segment (words)
Even instruction
Odd instruction
None.
Wait for the - ••DUMP (O)PTION / (D)EFAULT / (N)ONE
FMS - CAN'T CREATE CACHE SEGMENT - CODE=nnnnnn
FS35 Message. Denial from memory management while trying to create the Catalog
Cache segment.
nnnnnn -
The error code returned from the PMME CRSEG process. Error code
000004 indicates that there is insufficient real memory to create
the cache segment. Reduce the number of buffers and retry. Any
other status indicates a system problem.
Operator Action: None.
9-9
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
FMS- nnn - DEVICE MUST BE RESTORED
File Management Supervisor (FMS) Initialization Message. Device nnn was
initialized during system startup. This message appears once for each device
that is initialized.
Operator Action: When the system is operational, restore the device using the
DEVICE option on an FMS RESTOREMAST directive. Journalized files on the device
might also require updating via Integrated Software and/or a TDS RCVY function.
FMS- x nnn DEVICE NOT ON LINE
File Management Supervisor (FMS) Initialization Message. An error occurred
during a read attempt of the disk pack label for configuration crosschecking.
Crosschecking for device nnn cannot be accomplished.
x - Type of error, as follows:
R - Released
o - Offline
P - Power off
S - Seek error
Operator Action:
None.
FMS- •• DEVICE TABLE OVERFLOW
File Management Supervisor (FMS) Initialization Message. An internal table in
FMS initialization overflowed. The maximum number of devices that can be
initialized at one time is 32, unless a total initialization is performed.
Operator Action: Reboot. Either initialize all permanent devices or boot
several times, initializing < 32 devices at a time, allowing FLIP to complete
its Restore Lock scan on each boot.
9-10
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
FMS- DO MASTER RESTORE - SHCS INITED
File Management Supervisor (FMS) Initialization Message.
devices were initialized during system startup.
The SMC and SMCDUP
Operator Action: When the system is operational, perform a RESTOREMAST, using
the latest save file. When this message is received, the operator does not
respond to the nnn - DEVICE MUST BE RESTORED message.
{ COPYA }
FMS-DUP FILE ERROR { COPYB } FILE xxxxxxxxxxxx USER YY11YYYY"YY
File Management Supervisor (FMS) Initialization Message. An I/O error occurred
on a duplicated file (either Copy A or Copy B) with file name xxxxxxxxxxxx and
user name yyyyyyyyyyyy.
Operator Action:
None.
FMS- ERROR xxxxyy CATALOGING SYSTEM FILES
File Management Supervisor (FMS) Initialization Message. FMS error xxxx
occurred during processing of the $ PFILES entries. Refer to the GCOS 8
OS File Management Supervisor manual for error code and error message
definitions.
yy - Function that encountered the error, as follows:
04
05
07
13
20
21
31
-
Query GCOS 8 system master catalog
Create GCOS 8 system master catalog
Create GCOS 8 user master catalog
Error in $ PFILES entry
Attempting to locate a currently existing file
Creating a GCOS 8 file
Unable to unlock device directory lock during configuration
crosschecking
Operator Action:
None.
9-11
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
FMS- ERROR II COIFIGURATIOI MAP
File Management Supervisor (FMS) Initialization Message. The device(s) named
as SMC and/or SMCDUP in the FMS device directory do not agree with those in the
FMS configuration mapping information. This message is for information only
and is a result of changes in the $CONFIG and/or $INIT section of the system
description section of the Startup program. The devices specified in the
device directory will continue to be used as the SMC and/or SMCDUP device.
Operator Action:
None.
FMS- •• ERROR HlDIFYIIG FILE xxxxxxxxxxxx
File Management Supervisor (FMS) Initialization Message. During FMS
initialization, when all files defined during startup as "DTFILES" should be
modified to give USERID "SYS SOFTWARE" specific write permission. The
procedure failed.
Operator Action: Execute a privileged FILSYS activity to assign the
appropriate permissions.
FMS - FLIP •• SHC SIZE ROT UPDATED FOR xxxxxxxxxxxx/yyyyyyyyyyyy
File Management Supervisor. The System Master Catalog (SMC) size was not
updated for the specified userid/filename.
Operator Action:
Notify site techniques group of inaccurate SMC entry.
FMS - FLIP •• SHC SIZE UPDATED BUT DHC SIZE NOT UPDATED FOR
xxxxxxxxxxxxlyyyyyyyyyyyy
File Management Supervisor Message. The System Master Catalog (SMC) size was
updated but the Duplicate Master Catalog (DMC) size was not updated for the
specified userid/filename.
Operator Action:
Notify site techniques group of inaccurate DMC entry.
9-12
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
FMS- GECAL ERROR LOADING RESTORE PROGRAM
File Management Supervisor (FMS) Initialization Message. After a partial INIT,
FMS attempts to restore-lock the structure for any files that were on affected
devices. The restore overlay could not be loaded.
Operator Action: Reboot the system. Probably, the restore overlays and/or
GECALL processors will have to be re-edited.
FMS- GESAVE ERROR ON FILE SR
File Management Supervisor (FMS) Initialization Message. FMS initialization
was unable to GESAVE in order to call restore overlays after a partial INIT.
Operator Action:
None •
• FMS- INVALID INPUT
File Management Supervisor (FMS) Message. The operator entered an
unrecognizable message or an invalid parameter.
Operator Action:
Enter the correct message.
FMS - KEY MODULE INVALID - CATALOG CACHE
File Maintenance Supervisor (FMS) Message. Initialization of catalog cache
failed due to a bad KEY3 module. Delete the $ INFO CCACHE JCL statement until
the KEY3 module is replaced.
Operator Action:
None.
9-13
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
FMS- NO CAT. SPACE 01 DEV xxx
File Management Supervisor (FMS) Initialization Message. After initialization
of the SMC (ST1) or SMCDUP device, when FMS attempted to rebuild the affected
system master catalog from the remaining copy, an attempt to obtain space for
an extension of a SMC section was denied by the mass store allocator.
Operator Action: Reboot the system, initialize the device, and allow enough
space on the affected device either by moving part of the startup files or by
increasing the "$ INFO CATFNC" value.
FMS- PACK: { 111 ppppp} MAP: nnn mmmmm
{ UNDEFIlED }
File Management Supervisor (FMS) Initialization Message. The disk pack
currently mounted on the permanent device nnn does not agree with the system
configuration mapping information. The configuration map indicates that pack,
serial number mmmmm, should be in the device. However, disk pack, serial
number ppppp mounted in device named 111, as determined from the disk pack
label, is currently mounted. This message usually appears on a system reboot
following a disk pack swap. The configuration map is not changed. If the word
"UNDEFINED" appears, the FMS device is no longer configured in the system, or
the device name was removed from the $CONFIG section of the Startup program.
Operator Action: Change the $CONFIG section in the Startup program and reboot
the system. If the word "UNDEFINED" appears and if the device was previously
marked catalogable, do the total system saves followed by an INIT edit and the
total restores. Otherwise, FMS will not be able to do file creates or
restores. If the device was not marked catalogable, then FMS will not be able
to process files residing on the device.
FMS- •• RESTORE AROLIS! OVERFLOW
File Management Supervisor (FMS) Message. A failure occurred after a partial
INIT, when an attempt was made to set up a task block to restore the
initialized devices.
Operator Action:
retry.
Reboot the system, reinitialize all affected devices, and
9-14
DH13-04
~I
~
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
FMS- STARTING SUBSTRUCTURE RESTORE LOCKS
File Management Supervisor (FMS) Message. This informative message is issued
after a partial INIT, when FMS calls restore logic to set restore-locks for all
affected files.
Operator Action:
None.
*FMS STATUS- $FSYS NOT IN SYSTEM
File Management Supervisor (FMS) Message. The operator entered a request for
status of the FMS Executive (SNUMB - $FSYS), but $FSYS is not in the system.
Operator Action:
None.
FMS- SUBSTRUCTURE RESTORE LOCKS COMPLETE
File Management Supervisor (FMS) Message. This informative message is issued,
when processing of FMS structures is completed after a partial INIT.
Operator Action:
None.
*FMS SWAPPED - TRY AGAIN
File Management Supervisor (FMS) Message. The operator entered a FMS console
request message, but the FMS Executive (SNUMB - $FSYS) had been swapped out.
Operator Action:
FMS-
**
Reenter original FMS request; $FSYS has been swapped back in.
UNABLE TO GEMORE MORE MEMORY
File Management Supervisor (FMS) Message. Initialization was denied five
times, when an attempt was made to obtain additional memory to call restore for
initialized devices.
Operator Action: This is a system fault. While FMS initialization is in
progress no other processes must be active.
9-15
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
FMS-.. UNABLE TO GEMDRE p. FILE
FMS-.. UNABLE TO GEMORE SR FILE
File Management Supervisor (FMS) Message. FMS was denied temporary space for a
restore report (p.) or a GESAVE file after a partial INIT.
Operator Action: This is a system fault. Reboot the system and retry.
one or more devices were initialized, space should be obtainable.
Since
FMS- UNMATCHED DESCRIPTOR ON SYSTEM FILE - nnnnnnnnnnnn
File Management Supervisor (FMS) Initialization Message. The file space for
file nnnnnnnnnnnn changed across bootloads, and FMS was unable to use the new
space for the file. This message can result from changing a $ FILDEF statement
whose file-name can also appear on a $ PFILES statement on a device initialize.
Operator Action:
None.
FMS- WRITE ERROR USER xxxxxxxxxxxx
File Management Supervisor (FMS) Message. A write error occurred, when an
attempt was made to update the FMS substructure for a system USERID
(SYS PREFIX). This results during FMS initialization, when an attempt is made
to restore-lock files on the affected devices after a partial INIT. The
affected file definition could not be rewritten.
Operator Action: This error was caused, probably, by a hardware failure.
Reboot the system; if the error recurs, notify the Honeywell Bull Response
Center •
• i cco dd: FMT PACK I nnnnn?
Startup Message. This message always follows the .i ccc dd:CHG PACK Hnnnnn?
message during system startup. The operator is asked if PACK Hnnnnn should be
formatted.
Operator Action: Enter NO - Do not format the pack. EOM is equivalent.
Enter YES - Format the pack. Startup tests for bad tracks and
redefines defective llink directories and
alternate track tables.
9-16
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
.FMr v MC w SD xx DEi Y SC zzzz i-ccc-dd
Exception Processing Message for MSU3380. This message precedes the standard
exception processing message for all errors encountered on these mass storage
devices. This new message reflects the sense-byte information, represented in
hexidecimal, which is returned in the extended status from the I/O error.
v
w
xx
y
zzzz
i
ccc
dd
= Format code from byte 7 bits 0 - 3 of extended status
code from byte 7 bits 4 - 7 of extended status
Storage
Director
Physical ID from byte 21 bits 0 - 7 of
=
status
= Device Number from byte 4 bits 4 - 7 of extended status
= Symptom code from bytes 22 & 23 of extended status
= I/O controller number in decimal
= Channel number in decimal
= Device Number in decimal
-. Message
extended
The icccdd information is given for correlation with the subsequent standard
exception processing message.
On these devices a format code of E indicates a status of Storage Director Off
Line has occurred. When this occurs, the subsequent GEPR message will indicate
a major status of 12 and a substatus of 16.
Operator Action: It is recommended that the operator enter the K option
(request to deactivate a channel) to enable the operating system to route all
further I/O for these devices to another channel.
*FNP In APPEARS OPERATIONAL - ABORT FNP BEFORE
DUMPING (YES) OR TERMINATE DUMP REQUEST (NO)?
DATANET 355/6600 Dump Program (FDMP) Message. Operator attempted to dump a
DATANET 355/6600 processor that has been bootloaded and is operational.
Operator Action: Respond NO to void the dump command. Just before the Dump
program terminates, the following message is output to the operator.
*FNP In NOT DUMPED - AT OPERATOR'S REQUEST
Enter YES to cause an abort by the DATANET 355/6600 processor to be dumped.
9-17
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
If one second elapses after the abort command is sent to the DATANET 355/6600
processor and the Dump program does not receive acknowledgement of the command
from the processor, the following message is printed to tbe operator.
*FNP In NOT DUMPED - NO RESPONSE FROM ABORT REQUEST SENT TO FNP
When the abort command is acknowledged by the processor, the Dump program waits
for a completion of the processor abort wrapup procedures. If, after 30
seconds, the DATANET 355/6600 processor has not completed the abort process,
the following messag~ is printed to the operator.
*FNP In NOT DUMPED - ABORT OP ACKNOWLEDGED BUT NO ABORT OCCURRED
If abort occurs within 30 seconds, the dump process continues.
• FIP In BOOTLOAD COMPLETED
DATANET 355/6600 Bootload Program Message. This appears on the console when no
errors (fatal/non-fatal) are detected during the bootload process.
Operator Action:
* FIP
None.
In BOOTLOADED WITH DIRECT LOADER
DATANET 355/6600 Bootload Program Message.
Operator Action:
Bootload (of FDLD) is successful.
None •
• FIP In BOOTLOADED WITH IIITIALIZATIOI ERRORS - CHECK EXECUTIOI REPORt
GRTS II Bootload Program (FDBL) Message. Although the DATANET 355/6600
processor was bootloaded successfully, there were errors in initialization as a
result of inconsistencies, either in the configuration statements or in
hardware configuration.
Operator Action: Check the Execution report to determine what problems were
encountered during initialization.
9-18
DH13-04
F
OUTPUT MESSAGES
F
OUTPUT MESSAGES
• FNP In BOOTLOADED WITH m WARNING FLAGS
DATANET 355/6600 Bootload Program Message. This appears on the console when
the loading finishes with no fatal errors, but one or more non-fatal errors are
detected.
m - number of non-fatal errors detected
If a fatal error is detected during the boot10ad process, then
1. The error is printed on the load map
2. The following message appears on the host console:
.FNP In NOT BOOTLOADED - FATAL ERROR ENCOUNTERED DURING LOAD
The bootload program is terminated with a user 03 MME GEBORT
Operator Action:
None •
• rNP DUMP PROGRAM NOT LOWLOADED RUH AGAIN WITH $ LOWLOAD CARD
DATANET 355/6600 Dump Program (FDMP) Message. The $ LOWLOAD statement was
omitted from the job stream which is used to run the 855D dump program.
Operator Action:
Rerun with the $ LOWLOAD statement •
• rlP INITIALIZATION ERROR 10M-a, CBAHREL-occ
Rollcall Message. FNP configuration data is invalid to Rollcall.
marked released and should not be assigned or boot10aded.
Operator Action:
required.
• rIP
The FNP is
Verify the system configuration and reboot i f the FNP 1s
In INITIALIZED SUCCESSFULLY
GRTS II System Initialization Message.
initializes successfully.
Operator Action:
This appears on the console when FNP
None.
9-19
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
• FIP In IIITIALIZED WITH ERRORS
This appears on the console when initialization errors occurred during system
initialization •
•••• FATAL INITIALlZATIOI ERROR - xx ON Crt
where:
xx - fatal error code
yy - input/output controller channel
This occurs when DIA failed to initialize successfully •
••• FATAL INITIALIZATION ERROR - ELAPSED TIMER DISABLED
This appears on the console when when the elapsed timer is disabled.
When this occurs, the elapsed timer should be enabled on the DATANET
maintenance panel and the bootload retried.
Operator Action:
None.
FIP. IIPT. TERM. Sr!. ID xx TIP 11
DISC/DRUM ERRORS
ROIN Message. Disk errors occurred while remote input from the specified
station was being collected.
xx - Remote station identification
yy - Terminal type
03 - Remote computer
Operator Action:
None.
9-20
DH13-04
F
F
OUTPUT MESSAGES
FNP.
IIPT.
OUTPUT MESSAGES
~A.
TERM.
ID xx TIP yy
DUPLICATE SNUMBS
RGIN Message. A duplicate SNUMB was found and the input from the specified
station terminated.
xx - Remote station identification
yy - Terminal type
03 - Remote computer
Operator Action:
FIP.
IIPT.
None.
~A.
TERM.
ID xx TYP Y1
JOB SOURCE TOO LONG
RGIN Message. The job being collected from the specified station is larger
than the maximum size allowed.
xx - Remote station identification
yy - Terminal type
03 - Remote computer
Operator Action:
FIP.
INPT.
None.
TERM. ST A.
MISSING $ SNUMB
RGIN Message.
ID xx TYP 11
A $ SNUMB statement is missing from the specified station.
xx - Remote station identification
yy - Terminal type
03 - Remote computer
Operator Action:
None.
9-21
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
FNP. IMPT. TERM. BTA.
NO AVAIL. PGM. NUMBER
ID xx TIP yy
RGIN Message. Input from the specified station has been terminated because all
program numbers have been assigned.
xx - Remote station identification
yy - Terminal type
03 - Remote computer
Operator Action:
None.
FNP. IMPT. TERM. BTA.
NO MORE LINKS
ID xx TIP yy
RGIN Message. Input from the specified station has been terminated because all
available links have been used.
xx - Remote station identification
yy - Terminal type
03 - Remote computer
Operator Action:
None.
FNP IOM FAULT icccdd
••••••••••••••••••••••
•
FNP-n IS DOWN
•
• PLEASE INVESTIGATE •
•••••••••••••• ***«*~ftl
nc..lN Message. The DATANET 355/6600 processor, number n, is not in operation.
Operator Action:
Check for the cause of the processor failure.
9-22
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
Slsssss-aa FNPln NOT BOOTLOADED - (reason)
DATANET 355/6600 Bootload Program Message. The fourth or greater attempt to
bootload DATANET 355/6600 processor-n was unsuccessful for one of the following
reasons:
Reason - NO RESPONSE FROM FNP
The operator should check for the specified host system mailbox base
address on the DATANET FNP maintenance panel. If the address is
different from the one shown in message "SHOULD BOaTLOAD BE ATTEMPTED
AGAIN?", the host system should be bootloaded as soon as possible. The
location specified by the swithces has been reset to zero and
inconsistent operation of the host software may result from any incorrect
switch setting.
Reason - DIA FAULT ON 10M
A channel fault exists on the DIA channel. When this is encountered, the
bootload should be retried. If this error persists, notify the Honeywell
Bull Response Center.
Reason - UNABLE TO LOCATE DIA MAILBOX
The DIA mailbox is set to a value less than 500 (octal) or greater than
1000 (octal).
Reason - INVALID DNE! CALLING PARAMETERS
The host software detects an error in the bootload calling sequence.
Reason - DIET INTERFACE BUSY
The host software determines that the host interface adapter interface is
busy after several retries.
Reason - PROCESSOR FAULT IN FNP AT LOC mmmmm
mmmmm - location of processor fault
A processor fault has occurred during bootload verification.
9-23
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
Reason - DIA STATUS ERROR mmmmm
mmmmm - lower 21 bits of status returned by host interface adapter
A bad status has been returned on the host interface adapter by the
bootload command.
Reason - ILLEGAL STATUS FROM FNP
This indicates a status code has been returned to the host system
privileged slave program that is currently not recognized.
When this occurs, the bootload operation should be retried after pressing
the initialize button on the DATANET FNP maintenance panel. If this
persists, a dump should be taken of the FNP.
During the bootload process, fatal errors are detected by both FDBL and
FDLD and printed on the load map.
-FNP-n NOT RESPONDING
Rollcall Message.
marked released.
FNP In did not respond to a Rollcall connect.
Operator Action:
Bootload FNP In when the system is operational.
The FNP is
-FNP ON ieee RELEASED
GPOP Message. The specified front-end network processor (FNP-n) could not be
assigned by Startup because either the power is off or the device is in an
offline condition.
Operator Action: Either run the system without the processor or ready the
specified processor and enter an ASGN request. The processor cannot be
assigned while the system is running if assignment requires initializing the
catalogs.
9-24
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
Slsssss-aa FNPln NO RESPONSE SHOULD BOOTLOAD BE ATTEMPTED AGAIN?
DATANET 355/6600 Bootload Program Message.
processor-n was unsuccessful.
Bootload on DATANET 355/6600
Operator Action: Enter NO, the bootload is not attempted again and the program
terminates. If YES is entered, the bootload is attempted once again. If the
DATANET FNP still does not respond, the same question is output to the
operator. In no case, however, is the bootload tried more than three times.
After the third unsuccessful attempt to bootload the DATANET processor, the
program automatically prints the error message: Slsssss-aa FNPln NOT BOOTLOADED
- (reason).
-FORMAT i ccc dd?
Startup Message.
be formatted.
Requests the operator to check whether the disk pack should
Operator Action:
Enter YES if formatting is required.
-FORMAT/LABEL QUESTIONS?
Startup Message. This question is asked only once. It allows the operator to
have all the pack label verification and format questions typed. A YES
response to this message results in the following response from the system.
FORMAT i ccc dd?
Operator Action: Enter YES if formatting or label checking is required;
otherwise, enter NO or press EOM.
If the pack number is 00000, the following message is given regardless of the
response to the above message:
*icccdd:
ENTER PACK #nnnnn?
The operator responds by entering the desired pack number.
9-25
DH13-04
F
OUTPUT MESSAGES
F
OUTPUT MESSAGES
If the resonse to the *FORMAT/LABEL QUESTIONS? message was YES, the following
messages are issued:
*icccdd: CHG PACK Alnnnn?
*icccdd: FMT PACK Innnnn? (except MSS0500/501)
*icccdd: TEST PACK Innnnn? (MSS0500/501 only)
The operator responds to the *icccdd: CHG PACK Innnnn? message as follows:
NO - Pack number is not changed
nnnnn - New pack number
Operator Action:
respond to the *icccdd:
FMT PACK Innnnn? message as follows:
NO - No formatting will be done
YES - Startup attempts to format (write tracks headers on) all tracks,
except those in the defective space history table, as GOOD. Those
tracks in the history table as well as those which cannot be
formatted GOOD are formatted DEFECTIVE/NO ALTERNATE and entered
into the defective llink directory.
RTHDRS - Startup issues a "read' track header" command to all tracks on the
disk. Tracks with track indicator (TI) bits specifying
DEFECTIVE/NO ALTERNATE and tracks that cannot be successfully read
are entered into the defective llink directory. Tracks with TI
bits specifying DEFECTIVE/ALTERNATE ASSIGNED are entered into the
alternate track table.
Respond to the *icccdd: TEST PACK Innnnn? message as follows:
NO - No testing will be done
YES - Startup issues a "read track header" command to all tracks on
or
the disk. Tracks with track indicator (TI) bits specifying
RTHDRS
DEFECTI'VE/NO ALTERNATE and tracks that cannot be successfully read
are entered into the defective llink directory. Tracks with TI
bits specifying DEFECTIVE/ALTERNATE ASSIGNED are entered into the
alternate track table. MSS0500/501 disks do not have alternate
track tables; therefore, tracks marked DEFECTIVE/ALTERNATE
ASSIGNED are treated as if they were marked GOOD.
9-26
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
-FPT TAPE-Slsssss i-ooo-dd (i-oco-dd) fo filename
Termination Message.
Requests operator action at the specified tape unit.
Operator Action: Dismount the tape, remove the write-permit ring, and remount
it on the same handler •
• FYI CACHE FLT REG CIT
= xxxx
@ tt.ttt, PORT n
ECOL Message. The ECOL program detected an abnormally high error occurrence in
cache fault register bits 41-46. ECOL error threshold of a summation of bits
41-46 has reached a count of 200 within a 36-hour period.
Operator Action: Notify the Honeywell Bull Response Center that this situation
requires analysis, and that corrective action should be taken at the first
opportunity. (Also, refer to the output message:
-CACHE ERROR, FLT REG BITS 32-46
= XXXXX,
PORT n.)
.FYI ECOL - CACHE DISABLED, PROI-n PORT n
ECOL Message. Cache memory was disabled on the indicated processor port on
SCU-O. This message appears after initial startup of the ECOL program, if the
known state of the cache memory is off, a cache memory error is detected, or a
request to disable cache memory is encountered. In either case, cache memory
has been disabled to provide an error-free operational environment.
Operator Action:
None.
9-27
DH13-04
·F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
.FYI ECOL - CACHE ENABLED, PROI-n PORT n
ECOL Message. Cache memory was enabled on the indicated processor port on
SCU-O. This message normally occurs either when the ECOL program enables cache
memory initially, if certain fault types have locked the processor history
register and ECOL re-enables cache memory, or after a request to enable cache
memory.
Operator Action:
None •
• FYI ECOL - CACHE STATUS
ECOL Message. This message is issued in response to (1) the ECOL CSHSTS verb,
(2) a detected processor online reconfiguration, or (3) ECOL processing of a
cache memory parity error.
In response to the CSHSTS verb or to processor reconfiguration, a cache memory
status line is displayed for each currently assigned processor. In response to
an ECOL-detected cache parity error, status is displayed only for the cache
memory applicable to the error reported.
Operator Action: Determine cache control from the value found in site patch
location 105 in FALT module (default is ECOL control).
FYI ECOL COULD NOT LOG SYSTEM CONFIGURATION; ERROR nn
ECOL Message.
nn - 00,
01,
02,
03,
04,
Informative message.
Job will have to be resubmitted.
Program error
Unable to find $CONFIG
Bad 1/0 status on read
Invalid seek address calculation
Did not find ***EOF or slew data
Operator Action: None.
9-28
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
-FYI ECOL - ENCOUNTERED ERROR, SNAP TAKEN.
RETURN ACcrG FILE SNAPS TO DEVELOPER IN PHOENIX.
ECOL Message. An invalid record size was detected by ECOL and a snapshot was
taken. Part of the buffer is bypassed and processing continues.
Operator Action:
Submit System Technical Action Request (STAR) with snapshot.
-FYI ECOL - ERROR RATE ON 1-ccc-dd EXCEEDS THRESHOLD
ECOL Message. The calculated percentage is equal to or greater than the
current error threshold percentage (default value = 0.01%).
Operator Action: Alter threshold percentage by entering ECOL MPC ETxxx verb or
applying a site patch to location 112 (octal) of the FALT module.
---FYI ECOL EXECUTING; TTL DATE yymmdd, ASSEMBLY DATE mmddyy
ECOL Message. This message is issued each time the ECOL module starts its
initialization routine.
Operator Action:
None.
-FYI ECOL IS CREATING STATISTICS FILES
ECOL Message.
ECOL is creating its statistics gathering files.
Operator Action:
None.
-FYI ECOL IS NOT SERVICING CACHE
ECOL Message. The system contains one or more cache processors, and a patch to
the .MFALT module has set option 5 to specify cache service by GeOS hard-core
cache service routines only.
Operator Action:
None.
9-29
DH13-04
F
OUTPUT MESSAGES
F
OUTPUT MESSAGES
*FYI ECOL - STATUS ERROR ON i-ccc-dd ssssssssssss
ECOL Message.
An error was encountered on a statistics sampling I/O command.
i-Port number of I/O controller
ccc - Channel number
dd - Device
Operator Action:
None.
*FYI ECOL - SY EC FILE ERROR 4000001;
*FYI ECOL - COLLECTOR FILE NOT CREATED.
* RELEASE SY EC FILE & DO ECOL START.
EeOL Message. The numeric value in the first line represents an error code for
the condition described in the second line of the message. This message is
followed by a HU MME GEBORT. A collector file was not created due to an
invalid status return when an attempt was made to create a file with a MME
GEFSYE.
Operator Action:
console.
Release ECOL data files and enter ECOL start verb on the
*FYI ECOL - SY EC FILE ERROR 4000002;
*FYI EeOL - ERROR ON GEMORE OF EC REC·
ECOL Message. The error condition which caused this message is described in
the second line of the message. The numeric sequence in the message's first
line is the specific error code. This message is followed by a HU MME GEBORT.
Operator Action.
Seek next level of technical support.
*FYI ECOL - BY EC FILE ERROR 4000003;
*FYI ECOL - FILE CODE HOT IN leOL PAT
ECOL Message. The number sequence in the message's first line is the specific
error code for the condition described in the second line of the message. This
message is followed by a HU MME GEBORT.
Operator Action.
Seek next level of technical support.
9-30
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
-FYI EeOL - 8Y Ee FILE ERROR 400000_;
-FYI EeOL - FILE BLOCK SIZE NOT 64 WORDS
ECOL Message. File block size (which should be 64 words) is incorrect. The
numeric sequence in the first line of the message is the specific error code
for this condition. This message is followed by a HU MME GEBORT.
Operator Action:
Seek next level of technical support.
*FYI EeOL - SY Ee FILE ERROR 4000005;
-FYI EeOL - COLLECTOR FILE CONTROL BLOCK ERROR
- RELEASE SY EC FILE & DO ECOL START.
ECOL Message. Some error exists in the control block of the collector file.
The numeric sequence in the first line of the message is the unique error code
for this condition. The message is followed by a HU MME GEBORT.
Operator Action: Run appropriate report program version, then release the
SY EC file and enter ECOL START verb on console.
-FYI ECOL - SY EC FILE ERROR 4000006;
*FYI EeOL - CALLERS RECORD TYPE ILLEGAL.
ECOL Message. An illegal record type was encountered. The numeric sequence in
the message's first line is the specific error code for this condition. The
message is followed by a HU MME GEBORT.
Operator Action:
Seek next level of technical support.
-FYI EeOL - SY EC FILE ERROR 4000007;
-FYI ECOL - CALLED WITH ILLEGAL RECORD SIZE.
ECOL Message. An illegal record size was encountered. The numeric sequence in
the message's first line is the unique error code for this condition. The
message is followed by a HU MME GEBORT.
Operator Action:
Seek next level of technical support.
9-31
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
*FYI ECOL - SY EC FILE ERROR 40000010;
*FYI ECOL - COLLECTOR BUSY TRY LATER.
ECOL Message. The attempt to access the collector was unsuccessful due to its
busy status. The numeric sequence in the first line of this message is its
unique error code. The message is followed by a HU MME GEBORT.
Operator Action:
Seek next level of technical support.
*FYI ECOL - SY EC FILE ERROR 40000011;
*FYI ECOL - FILES WERE CREATED BY xxxxxx; YOUR SYSTEM ID IS yyyyyy.
* RELEASE SY EC FILE & DO ECOL START.
ECOL Message. In the first line of the message, the numeric sequence is the
specific error code for this condition. In the message text, xxxxxx represents
a variable which is the system ID found in the file by ECOL and yyyyyy
describes the current ID. This message is followed by a HU MME GEBORT.
Operator Action: Determine i f the files are correctly loaded; if not, either
load the files properly, or if system ID was changed, release SY EC file and
allow ECOL to recreate file by entering ECOL START verb on console.
*FYI ECOL - SY Ee FILE ERROR 40000012;
*FYI ECOL - YOUR SY EC FILE WAS CREATED PRIOR TO yymmdd.
CURRENT FILE FORMAT-INCOISISTENT; TTL DATE OF ECOL IS yymmdd.
RELEASE SY EC FILE & DO ECOL START.
ECOL Message. The numeric sequence in the message's first line is the unique
error code for this condition. The first occurrence of "yymmdd" is the file
format revision date while the second occurrence represents the current TTL
date of ECOL. This message is followed by a HU MME GEBORT
Operator Action: Ensure that proper files exist, release SY EC files and enter
ECOL START verb on console.
9-32
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
-FYI ECOL - SY EC FILE ERROR 400013;
-FYI ECOL - COULD NOT OBTAIN AT LEAST 800 LLINKS PERMFILE
SPACE, PLEASE RESTART ECOL WHEN ADEQUATE
SPACE IS AVAILABLE
ECOL Message. A minimum of 800 llinks of permanent file space was unobtainable
and ECOL aborted.
Operator Action:
Seek next level of technical support.
-FYI ECOL - SY EC FILE ERROR 400014;
-FYI ECOL - EC-FILE IS RESTORE LOCKED
COMPLETE RESTORE OR RELEASE COLLECTOR FILE
AND RESTART ECOL
ECOL Message.
A restore lock condition was encountered and ECOL aborted.
Operator Action: Complete the restore and ECOL START verb or call next level
of technical support if no restore of the SY EC SMC is in progress.
-FYI ECOL - SY EC FILE ERROR 400015;
ECOL SYMBOL REVISION DOES NOT AGREE WITH
THE REVISION OF THE COLLECTOR FILE
DO ECOL STOP & RELEASE THE SY EC SHC &
THEN DO ECOL START
ECOL Message: The symbol revision does not agree with the revision level
contained in the collector file, and the ECOL aborted.
Operator Action: Run the appropriate report program version, then release the
SY EC file and enter EeOL start verb.
-FYI ECS ECC CRT ON PRC' n = xxxx @ tt.ttt
ECOL Message. ECOL program detected ECS ECC errors on the indicated processor
(DPS 8/20 & 8/44 systems only).
xxxx - total number of ECS ECC errors.
Operator Action:
None.
9-33
D813-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
FYI nnnnn FAULT CHARNEL IGNORED
lOS Message. A non-fatal fault channel error was detected and ignored.
number nnnnn refers to either a system controller or an I/O fault.
The
FYI (mm/6.> HUNG BUSY ON ieee dd
lOS Message. The magnetic tape handler dd on i ccc did not return a ready
condition in a reasonable time. If a magnetic tape handler, the rewind may not
have completed properly. If a shared disk device, the alternate channel may
have locked us out.
Operator Action:
device.
Check the device.
If rewinding is complete, ready the
--FYI LB-xxx THRESHOLD
FMS Message. FMS, in this system, is waiting on a lock byte shut by another
system. This message is repeated every few minutes while the lock byte is
shut; if this condition persists, the system will hang.
Operator Action: If message persists and the system hangs resulting in a dump,
gather all information from all common files systems associated with this
system.
FYI HOS EDAC CNT = %XXx tt.ttt
ECOL Message.
ECOL program detected EDAC-corrected errors.
xxxx --Total number of EDAC errors
Operator Action:
None.
-FYI MPC CH NOT SAMPLED ON icccdd, RESERVED FOR T&D
ECOL Message. ECOL was unable to sample MPC statistics on the designated
channel because it was reserved for T&D.
Operator Action: If the deSignated channel is not supposed to be reserved for
T&D, investigate th~ reason. The "Reserved for T&D" bit could have been set by
GCOS as a result of errors on the PUB (channel). The T&D bit can be reset by
running T&D on any device on the PUB (channel).
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
-FYI MPC CH NOT SAMPLED ON iooodd, STATUS: xxxxxxxxxxxx
ECOL Message. MPC statistics were not sampled on the designated channel
beoause a status error oocurred on the I/O operation issued by ECOL to read MPC
statistics counters.
Operator Action: Contact the Honeywell Bull Response Center.
hardware malfunction exists.
A probable MPC
-FYI MPC CH NOT SAMPLED OR iocodd, TEMPORARILY STOPPED
ECOL Message. ECOL was unable to sample MPC statistics on the designated
channel because it was temporarily stopped (under control of the Exception
Processor).
Operator Aotion:
investigate.
If this message ocours on successive sampling attempts,
-FYI PARSa HAS DETERMINED CPU x CACHE OR ASSOCIATIVE MEMORY IS OFF OR
DISABLED. PLEASE INFORM wCSDw OF PROBLEM.
PARsa Messages. The PARSa Collector determines if the processor cache and/or
associative memory is off or disabled, or the oache is being continuously
flushed. This message is issued if this condition persists for more than 60
seconds. This test is based on two internal program timing loops. One loop
times each processor executing a series of instructions in cache. The other
times each processor executing a series of instructions which do not use caohe
except for instruction look-ahead. Both instruction loops are timed based on
the system clock which has a 1-microsecond resolution. This test is considered
TRUE when the oaohe timing is equal to or greater than the non-cache timing.
Operator Action:
Nofity CSD of this problem.
9-35
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
*FYI PARSa HAS DETERMINED CPU x IS NOT AVAILABLE FOR DISPATCH INFORM ·CSD" OF
PROBLEM.
PARS8 Message. The PARS8 Collector tries to determine if all available
processors have been coming back from a dispatch. This message is issued if
the collector determines a problem in this area. The test for this condition
is to check if .CRIDT and .CROVH have been changed during the last sample
interval. If the values remain unchanged for two sample intervals, the message
is issued.
Operator Action:
Nority CSD of this problem.
*FYI PARsa INTERFACE FILE [D1 or D2] IS FULL.
HISTORY UPDATE PROGRAM.
PROBLEM WITH [PARSE OR PARSO]
PARS8 Message. This occurs when either file fills completely with data. One
or both of the PARS8 history file update programs have been unsuccessful in
emptying in the interface file(s). Inspect the PARSE or PARSO execution report
to determine the cause of the problem. The operator must spawn either PARSE or
PARSO. This enables the default value of BUSY and the history file is
updated. This is the only time an operator should manually spawn PARSE or
PARSO.
Operator Action: Notify the person responsible for PARS8 SPAWN [PARSE or
PARSO] to correct this problem. Save execution reports for analysis.
* FYI Sf xxxxx PARSa MONITOR ABORTING --
PARS8 Message.
= NEEDS
& PRIVITY TO RUN
WRONG SNUMB -- USE Slxxxxx
MUST LOAD VIA $ PROGRAM
CANNOT OBTAIN MEMORY NEEDED
UNKNOWN SOFTWARE RELEASE
INTERNAL CALL LIMITS BAD
UNEXPECTED I/O ERROR ON CALL
NO PAT FOR •• FILE
BAD DEVICE CALL
9-36
D1
D6
D7
D9
DA
DB
DC
DD
DE
ABORT
ABORT
ABORT
ABORT
ABORT
ABORT
ABORT
ABORT
ABORT
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
NONRANDOM -- FILE
CHECKSUM ERROR IN -CANNOT FIND MONITOR IN -CALL OUT OF FILE SPAN
IMPROPER CALL
NEEDS $ LOWLOAD
Operator Action:
DF
DH
DK
DL
DM
DS
ABORT
ABORT
ABORT
ABORT
ABORT
ABORT
Report abort to person responsible for PARS8.
- FYI Slxxxxx PARsa KlIITOR VER yyyyy zzzzz.
PARsa Message. This is describing the software release and GECALL name of the
PARSa collector being selected by the PARS8 loader. It is enabled by the $ SET
35 JCL statement in the PARS8 spawn JCL.
xxxxx - SHUMB
yyyyy - Sotware Release (e.g., 2300, 2500 or 3000)
zzzzz - GECALL NAME (e.g., N230C, N250C, and N300C)
Operator Action:
None.
-FYI PARSS RECORD CRT vvvvv SYSTEM-ID MHVDD/YI
[PI BUSY wwwww [PI BYPASS xxxxx
INtD PAT yyyyy INVLD IOQ zzzzz.
HH:MM:SS
Where:
vvvvv -
The number of program loops since the start of the program. This
number should increment by approximately 20 for each 10-minute
interval, providing the "TIME=xx" option is set to default
(tlTIME=30" or "TIME").
wwwww -
The number of times another process was being accessed via .MMISC
and was found to be busy.
xxxxx -
The number of processes that were bypassed due to being busy.
total of 40 attempts are made before a process is bypassed.
A
NOTE: If a process is bypassed, this means access to a process via the
.MMISC module was denied and that data from the SSA, PAT, and
user program area could not be obtained. PARS8 marks this job as
swapped.
9-37
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
yyyyy -
A count of the SCT pointers within a user PAT segment that
contain addresses exceeding SD.CR uper limits.
zzzzz -
A count of the SCT pointers within the SD.IOQ segment that
contain addresses exceeding SD.CR upper limits. These fields
should always be zero.
PARS8 Message. This message is provided to try and detect why data gaps occur
in the collected data. The $ SET 35 option will produce this console message
every 10 minutes.
Operator Action If the message is not being printed, obtain a snap or dump of
the program PARS8. If the message is being printed, yet data gaps are noted on
the output report, try to determine what significant events might have caused
the data gap.
-FYI S#sssss [PI nnn EXTENDED MEMORY PROCESS IS WAITING FOR DDt CORTIGUOUS
MEMORY HH .nnn
Extend Memory (EXTM) Message. EXTM cannot get the necessary amount of memory
to build the 'big' page-table.
Operator Action:
Do not start new jobs; try to make memory available.
-FYI SCPR 06 STORED ZEROS FROM K>DE REG BITS 54-11 PORT n
ECOL Message. A failure occurred in the SCPR instruction in the indicated
processor connected to SCU-O port n.
Operator Action: Notify the Honeywell Bull Response Center that this situation
requires immediate analysis, and that corrective action should be taken at the
first opportunity.
9-38
DH13-04
F
F
OUTPUT MESSAGES
OUTPUT MESSAGES
FYI SHLIBBSn REQUIRES nnnn LLIHKS
Startup Message. This is an informative message intended to provide the user
with the size of the backing store associated with the SHRLIB that is being
edited.
n - WSR of the SHRLIB
nnnn - Decimal size of the backing store in llinks.
Operator Action:
• FYI
(mm/ 64)
None required •
THRESHOLD ON 1 ccc dd
Exception Processor Message.
the device.
Informs the operator of the local error rate on
Operator Action: When a device gives repeated threshold messages with high
error rates, it should be released.
FYI WS XXX - VA XXXXXXOOO NOT READ DUE TO RU
FILE FRAGMENTATION
FYI BS/RU READ ERROR
Dump Message.
DUMP could not read the backing store and/or run unit pages.
Operator Action:
None.
9-39
DH13-04
SECTION 10
OUTPUT MESSAGES BEGIRBIIG WITH THE LETTER G
GCOS 8 FILE SYSTEM FATAL ERROR 01 DEVICE xxx
xxx - Three-character BCD device name
Startup Message.
This message is followed by one of these entries:
Operator Action:
.NOT ENOUGH SPACE FOR MASTER CATALOG
Device does not have any
available llinks. Use a
different device •
• NOT ENOUGH SPACE FOR FILE REQUEST
Device does not have enough
contiguous llinks for this
file. Use a different
device •
• BAD BLOCK ZERO
Block zero has been
destroyed. Initialize the
device •
• BAD MASTER CATALOG
The Startup master catalog
has been destroyed.
Initialize the device or
remove this name from the
$ GCOSFIL statement •
• CHECKSUM ERROR ON AU TABLE
The available llink table
does not checksum.
Initialize the device •
• TOO MANY STARTUP FILES
More than 79 Startup files
are trying to be built on a
device. Additional Startup
files will have to be
edited on some other
device.
(Continued on next page)
10-1
DH13-04
G
G
OUTPUT MESSAGES
OUTPUT MESSAGES
Operator Action:
.CANNOT GET FILSYS SHC'S
There are not 38 contiguous
llinks available for the
System Master Catalog (SMC)
or duplicate •
• BAD IN-CORE AVAILABLE SPACE TABLE IMAGE
The in-memory available
space table image is bad.
Perform a secondary
initialization of the
device •
• IN-CORE AVAILABLE SPACE TABLE IMAGE OVERFLOW
The in-memory available
space table is too large.
Perform a secondary
initialization of the
device •
• ILLEGAL FILE NAME
The file name cannot be
found in the master
catalog •
• CANNOT CREATE THE SMC WITHIN BOUNDS
Cannot create the SMC
within system bounds.
Initialize the device •
• BAD BOOT SEQUENCE NUMBER BLOCK
A checksum error occurred
on the bootload sequence
number block.
Re-initialize with correct
sequence number •
• NPS PACK VS DEVICE ERROR
An NPS pack was configured
for a non-NPS system or a
non-NPS pack was configured
for an NPS system. Perform
an initialization of the
device.
10-2
DH13-04
G
OUTPUT MESSAGES
G
OUTPUT MESSAGES
*$ GCOSFIL CARD IS MISSING
Startup Message.
Startup program.
There is no $ GCOSFIL statement in the $CONFIG section of the
Operator Action: Put a $ GCOSFIL statement in the $CONFIG section of the
Startup program and reboot.
***GECALL NAME TABLE FULL
Startup Message.
Files on $ SYSTEM statement call for too many modules.
Operator Action: Check to see that the files described on $ SYSTEM statement
are correct. Reboot.
***GEIM CAN'T INIT: BAD SIZE PATCH AT 114
System Input Message. The site option patch applied to location 114 of GEIN is
invalid. The upper half of the word must be within the range 1 to 4095 and the
lower half of the word must be modulo 12 and within the same range. Note that
no job will be processed until the patch is corrected.
Operator Action: Notify the site techniques personnel or correct the patch and
reboot the system.
System Input Message. A GEIN request for permanent assignment (during duration
of job) of J* or *J space to job identifier (SNUMB) number nnnnn was denied by
mass store allocator. Cause of denial may vary and is not necessarily a system
fault, but if condition persists notify the Honeywell Bull Response Center.
Operator Action: Rerun the job with specified identifier.
followed by the message:
This message is
GEIN IN ABORT STATUS
10-3
DH13-04
G
G
OUTPUT MESSAGES
OUTPUT MESSAGES
GEII CR 1 cec, CKS ERR, BACKUP nn CARDS BA
System Input Message.
GEIN
CKS
nn
BA
-
A
checksum error occurred.
System Input
Checksum
Number of statements
Operator reply
Operator Action: To recover, enter B and backspace the number of statements
specified. To delete the job, enter A.
GEII CR 1 cec, RESTART w/ISIUMB AFTER sssss
System Input Message.
The job just read cannot be run.
GEIN - System Input
Operator Action:
deck.
Restart the card reader, beginning with the job next in the
GEII CR 1 cee, RESTART w/SIUMS = sssss
System Input Message.
An I/O error was encountered.
GEIN - System Input
Operator Action:
Restart the specified job or start another job.
GEIN CR 1 ccc, SlUMS MISSING, RESTART
System Input Message.
The job was loaded without a $ SNUMB statement.
GEIN - System Input
Operator Action:
reload.
Place a $ SIUMB statement in front of the job stream and
10-4
DH13-04
G
G
OUTPUT MESSAGES
OUTPUT MESSAGES
GElI GECALL CAI'T LOAD xxxx stATUS
= nnnnnn
System Input Message. The System Input program was unsuccessful in calling one
of the overlay routines.
xxxx - Module called (GENA, GENB, or GENC)
nnnnnn - Return error status (octal)
Operator Action:
Contact the designated site personnel.
-GEII II ABORT STATUS RERUN OF SIUMB sssss NECESSARY
System Input Message.
Operator Action:
The System Input program aborted.
Rerun job sssss.
GEII AT i ccc dd IMCV READ ERROR CA
System Input Message.
from an IMCV tape.
An unrecoverable error was detected while reading input
GEIN - System Input
Operator Action: Enter C to continue with next job on the tape.
discontinue reading the tape.
Enter A to
GEII AT i ccc dd, TYPE IN REELI OF IMCV
System Input Message.
tape.
System Input determined that a label exists on the IMCV
Operator Action: If no comparison is desired enter EOM. If the label is to be
checked, enter the reel number of the tape to be processed. If reel numbers do
not agree, the following message is an output at the console.
GEIN AT i ccc dd, REELIS DO NOT AGREE CA
Enter C to continue or A to abort.
10-5
DH13-04
G
G
OUTPUT MESSAGES
OUTPUT MESSAGES
GEII xxxxxx READ ERROR 01 SlUMS, RESTAR't
System Input Message. System Input read an error on the $ SNUMB statement of
the last job submitted.
xxxxxx - Input device being used to read job .
Operator Action:
Resubmit the last job.
GEII xxxxxx, SRUMB
S8888
System Input Message.
specified job.
on the console reflects MCA
number 00, 101> MCA number 01, etc.). These MCA numbers -MUST- be unique if
the MCAs are to be connected together via the MDI interface, and -SHOULD- be
unique to correctly identify which MCA detected and logged an error if they are
not connected together via the MDI interface. This is an FYI message to
indicate two specified MCAs share a common MCA number zz (not connected
together via MDI which would cause lMU/IMX internal hardware errors).
Operator Action: Have CSD change the internal MCA switchs to make all MCAs on
the system unique and change all the lMU/IMX configuration files for the
changed lMUs/IMXs.
NOTE: This is not the lMU/IMX number that needs to be changed, but the MCA
number.
-IHO-x, PORT-y SIZE DOES NOT MATCH CORPIG
Startup Message. The MCA configuration files for all lMUs/IMXs are read by
startup for all lMUs/IMXs. The specified port definition field is incorrect in
the lMU/IMX configuration file and does not match the size that the CPU can
access.
Operator Action: Correct the lMU/IMX configuration file port definition field
for the specified port and reboot startup from an INIT of the lMU/IMX.
$ INFO DPSE - NOT AVAILABLE OR ELS SYSTEM
Startup Message. Startup does not check fop system type, if a $ INFO DPSE
statement appears in the $CONFIG section and, if the system is an ELS, it will
abort with a missing page fault error and issue this message.
Operator Action:
Remove the $ INFO DPSE statement and reboot the system.
12-5
DH13-04
I
I
OUTPUT MESSAGES
OUTPUT MESSAGES
• $ INFO FIP DEFINED dd FIP t S, tt FNP' S WERE FOUND
Startup Message. If the number of FNPs found (ft) by the startup program
exceeds the number of FNPs defined (dd), startup will abort. The $ INFO FNP
statement tells Startup how much space to reserve for FNP mailboxes. If too
little space is reserved, the mailboxes will intrude into the communications
region, which is a fatal Startup error.
If the number of FNPs found is less than the number defined, startup will not
abort. However, the message is issued to inform the operator that hard core
space is being wasted on too large of an FNP mailbox area.
Operator Action: When rebooting the system, define the correct number of
configured FNP's on the $ INFO statement.
IN/PROCESS Slsssss LOST CODEn
GPOP Message. Restart processing of job sssss failed, and the job is then
deleted from the system. Processing of other jobs continues.
n - 1,
2,
3,
4,
5,
6,
7,
8,
9,
No such name
Released Device
Status failure
SSFIL SNUMB oJ. J* SNUMB
Program number invalid or not assigned
BLINK zero error
No BLINKS recovered
BLINK not assigned
BLINK recovered or BLINK NO. G.R.R MAX, allowed.
Operator Action:
To run job sssss, resubmit it.
sssss-aa INCORRECT COLLATION INPUT TAPE
GET REEL # rrrrr FOR Mr ieee dd
(File name, File Serl/Reel Seql)
Sort/Merge Message. The wrong reel was placed on the handler designated~ The
handler is placed in standby to facilitate reel changing. When the handler is
ready, Sort checks the label without further operator action.
Operator Action:
None.
12-6
DH13-04
I
I
OUTPUT MESSAGES
OUTPUT MESSAGES
*IIIT CARD NOT ALLOWED AFTER ABY STRUCTURING
Startup Message.
structuring.
The $ INIT statement cannot follow any statement that causes
Operator Action:
Place all $ INIT statements first in the $INITIALIZE section.
*INIT DEVICE ddd?
Startup Message. The $ INIT Startup statement for the named permanent mass
storage device was read and the operator is asked if an initialization or a
secondary initialization must be performed on the device.
Operator Action: Enter NO or EOM to cause the initialization of this device to
be skipped. A YES response causes the process to continue with the following
output message at the console:
*FORMAT/LABEL QUESTIONS?
This message is discussed in Section 9.
A third possible reply is SECONDARY. Enter SECONDARY to rebuild the available
space table (AST) on the device from the Device Allocation Unit Table (DAUT) on
the device and to rebuild an empty Temporary Descriptor Table (TDT). This
secondary initialization does not release any permanent file space, but does
release all temporary file space back to the system. Under normal
circumstances a secondary initialization is performed automatically whenever
needed. The system provides the opportunity for the SECONDARY response in case
any unusual circumstances require a secondary initialization. During a system
boot specifying the NIAST mode, a secondary initialization is automatically
performed for each permanent device whose last mode of operation was
non-NIAST. (For more information refer to the "Operator Controls During
Initialization" and the $ INFO statement for the NIAST parameter description in
the GeOS ~ OS System. Startup manual.)
12-7
DH13-04
I
I
OUTPUT MESSAGES
OUTPUT MESSAGES
lIlT RMVBL DEVICE ddd?
Startup Message. The $ INIT startup statement for the named removable mass
storage device was read and the operator is asked if an initialization or a
secondary initialization should be performed on this device.
Operator Action: Enter NO or EOM to cause the initialization of this device to
be skipped. A YES response causes the process to continue with the following
message to be printed at the console:
-FORMAT/LABEL QUESTIONS?
This message is discussed in' Section 9.
A third possible reply is SECONDARY. Enter SECONDARY to rebuild the available
space table (AST) on the device from the device allocation unit table (DAUT) on
the device. This secondary initialization does not release any permanent file
space. Under normal circumstances a secondary initialization is performed
automatically whenever needed. The system provides the opportunity for the
SECONDARY response in case any unusual circumstances require a secondary
initialization. For removable mass storage devices in the NIAST mode, a
secondary initialization is automatically performed whenever a structured disk
pack is already mounted during Startup or is later mounted during system
operation. (For more information refer to the "Operator Controls During
Initialization" and the $ INFO statement for the NIAST parameter description in
the GCOS ~ OS System Startup manual.)
-INIT SHARED DEVICE ddd?
Startup Message. The $ INIT Startup statement for the named permanent mass
storage device, that is shared by one or more other systems, was read and the
operator is asked if an initialization or a secondary initialization can be
performed.
NOTE: In a CFF environment, each permanent device is shared by all the
configured systems. An initialization or secondary initialization
affects all the systems in the configuration. Therefore, an
initialization or secondary initialization must be performed on the
device only when all other systems in the configuration are down.
12-8
DH13-04
I
I
OUTPUT MESSAGES
OUTPUT MESSAGES
Operator Action: Enter NO or End of Message to cause the initialization of
this device to be skipped. A YES response causes the process to continue with
the following message to be printed at the console:
.FORMAT/LABEL QUESTIONS?
This message is discussed in Section 9.
A third possible reply is SECONDARY. Enter SECONDARY to rebuild the available
space table (AST) on the device from the device allocation unit table (DAUT) on
the device. This secondary initialization does not release any permanent file
space. Under normal circumstances a secondary initialization is performed
automatically whenever needed. The system provides the opportunity for the
SECONDARY response in case any unusual circumstances require a secondary
initialization. During a system boot specifying the NIAST mode, a secondary
initialization is automatically performed for each permanent device whose last
mode of operation was non-NIAST. In accordance with the above note, make sure
all other systems in the CFF configuration are down whenever a forced secondary
initialization occurs. (Refer to "Operator Controls During Initialization" and
the $ INFO NIAST Startup statement description in the GCOS 8 OS System Startup
manual for additional information.)
---- - - -
*INITIALIZATION FOR NEXT POST-MORTEM ReYRY FAILS
Rollcall Message. A restart after the next system failure is prevented due to
an error return from RCV4,EP1.
Operator Action: Reboot the system as soon as practical.
recurs, notify the Honeywell Bull Response Center.
If the condition
*INITIALIZATION?
Startup Message. The operator is asked whether to process all statements in
the $INITIALIZE section of the Startup program.
Operator Action: Answer YES to initialize all devices on the $ INIT
statements. However, a YES response causes the following system response •
• YES TO INITIALIZE COULD DESTROY THE SHARED DATA BASE, ANSWER YES TO
CONTINUE
12-9
DH13-04
I
I
OUTPUT MESSAGES
OUTPUT MESSAGES
A YES answer to this subsequent system response causes an automatic YES answer
to the following system questions unless an $ ANSWER statement in the $CONFIG
section specified otherwise.
(The message versions in parentheses are used in the Common File Facility
environment) •
• INIT DEVICE ddd (INIT SHARED DEVICE ddd)
.INIT RMVBL DEVICE ddd
.MPC iccc BOOTLOAD?
(.SHARED DSKMPC ON iccc APPEARS OK, BOOTLOAD)
.PROCESS DIRECTORY CARD FOR DEVICE ddd?
Answer NO to either the original .INITIALIZE? question or to the subsequent
.YES ••• CONTINUE question for no initialization. Statements in the $INITIALIZE
section will not be processed. A NO response will also pre-answer the BOOTLOAD
question and the ~WC question, unless a $ ANSWER statement in the $CONFIG
section specified otherwise.
Answer TOTAL for automatic edit on all devices, without further operator
communication.
In a Common File Facility environment, this response is invalid and results in
another opportunity for the operator to respond to the .INITIALIZE? question.
Answer PARTIAL to receive separate console messages for each function.
-INITIALIZE CARD BELOW CONTAINS ERROR NEAR COLUMN nn
Startup Message. An error was encountered while processing the statement, in
the $INITIALIZE section, listed after the above message.
nn - Statement column of the beginning of the field in error.
Operator Action:
Correct statement and reboot.
12-10
DH13-04
I
I
OUTPUT MESSAGES
OUTPUT MESSAGES
INPUT ERROR, BE-INPUT
Dump Message.
An invalid or misspelled option name was entered.
Operator Action: Enter correct option name.
system to output the message:
A correct response causes the
MORE?
INPUT INVALID
GPOP Message.
misspelled) •
The console entry MSG ON or MSG OFF is not recognized (i.e., is
Operator Action:
Reenter message •
• INPUT NEW TAPEII,DENSITY
Dump Message. An end-of-tape was encountered before the system has completed
dumping to that tape.
Operator Action: To continue the dump, mount a new tape and then enter the
logical device name of the magnetic tape unit on which the tape was mounted,
the tape reel number, and the tape density: ddd/rrrrr,DENS •
••• INSUFFICIENT REAL MEMORY FOR DISK CACHE
••• ASKING FOR aaaaaK HAVE RECEIVED rrrrrK
••• DO YOU WANT TO RETRY OR ABORT R1
Software Disk Cache Buffer Message.
satisfy the CSIZE option.
Enough real memory is not available to
Where:
aaaaa
rrrrr
= is
= is
the amount of real memory requested
the amount of real memory that has been acquired to this point.
Operator Action: Enter an R to retry the request or A to abort the control
program to verify that the CSIZE option is not too long.
12-11
DH13-04
I
I
OUTPUT MESSAGES
OUTPUT MESSAGES
-INTERRUPT BUT NO STATUS
-IOI-n, CHAI-occ, DEV-dd
Startup Message. The Startup program read an lOX interrupt queue entry and
went into a loop waiting for status to be written to the mailbox. The lOX did
not write status to the mailbox in time to prevent the lockup fault from
occurring.
n - lOX number
ccc - Channel number
dd - Device number
Operator Action:
None.
'INVALID COMMANDI
Remote Maintenance Interface Message. This message is issued to the console
device upon which an IENABLE MAINTENANCE command verb was entered, if the
diagnostic processor interface is not operational. Remote Maintenance
Interface entries do not affect system operation.
Operator Action: If onsite diagnostic processor interface is available, the
Honeywell Bull Response Center can be notified of the failure.
-INVALID FIELD ON • DIRECT - EOM SKIPS THIS CARD
Startup Message.
An invalid field was used on the $ DIRECT statement.
Operator Action: Press EOM to ignore the statement.
replace the statement.
Otherwise, correct and
INVALID TP REQUEST
TPE Message. TPE was configured to reject the request entered by the system
console operator.
Operator Action:
None.
12-12
DH13-04
I
I
OUTPUT MESSAGES
OUTPUT MESSAGES
-INVALID TPAP-ID
TPE Message. The system console operator specified an unknown TPAP identifier
in a TERM or REST command.
Operator Action:
Specify a known TPAP identifier.
I/O ERROR SR= xx/xx/xx eM= %XXx
lOS Message. This message informs the operator of an I/O error on the
specified drive.
SR= xx/xx/xx - the MAJOR/SUB/10M status of the error
eM= xxxx - the command generating the error
Operator Action:
None.
10M INVALID
GPOP Message.
The operator entered an illegal input/output controller number.
Operator Action:
Enter the correct message.
12-13
DH13-04
I
I
OUTPUT MESSAGES
OUTPUT MESSAGES
{ B }
-IOM lIT ssxx pp i-ccc-dd sssss seek address (disk only) {R/U}
{ RS}
Exception Processor Message.
related error exists.
An input/output controller (10M) or memory
10M - Inputloutput controller central or channel error
I - Status was returned on an initiate/terminate interrupt
ss - Octal substatus code. The first s denotes channel error codes and the
second s denotes central error codes. Values are shown below:
Channel Error Codes
Central Error Codes
o No
o No
error
, 1 Unexpected Peripheral Control
error
1 LPW tally runout
Word (PCW)
2 Illegal instruction to channel
2 Two TDCWs
3
3
4
5
6
4
5
6
7
in pew
Incorrect DCW
Incomplete instruction sequence
Incorrect peripheral action
Parity error to channel from
peripheral (CPI or Peripheral
Subsystem Interface (PSI»
Parity error, I/O bus, data
to channel
Boundary error
Not used
IDCW in restricted mode
Character position/size
discrepancy
7 Parity error, I/O bus,
data from channel
xx - Instruction code (refer to Appendix A)
Operator Action:
B - Before giving this response the operator should:
Card punch - Manually cycle the transport three times, discard the last
two cards from the stacker, and press OPERATE/RESET. (Or,
press RUNOUT, backspace the last card into the input
hopper, and press START.)
Card reader - Reenter the last card in the card reader and press
OPERATE/RESET.
R(U) - Enter R to retry or, if the option is given, U to return to
the user program.
12-14
DH13-04
I
I
OUTPUT MESSAGES
OUTPUT MESSAGES
RS - Respond S if the Seek address is desired, then enter R to
retry (several times if necessary).
In all cases, if the condition persists, enter A to abort the program.
the condition recurs, call the Honeywell Bull Response Center.
If
-10M m IS ASSIGNED
lOS Message. The input/output controller numbered m was successfully assigned
to the system and is available for use.
Operator Action:
None.
-10M m IS RELEASED
lOS Message. The input/output controller numbered m was successfully released
from system availability.
Operator Action:
None.
-IOPMPS REJECTED
{device code}
{channel
}
Startup Message. GeOS 8 Startup issues a rollcall connect from the $ lOP
statement processing routine. IOPMPS responds to the rollcall connect with one
of the following statuses:
o verified good
o wrong device code
o channel released
GeOS 8 Startup issues the "wrong device code" or "channel rejected" messages in
response to those statuses and then rejects the $ lOP statement that contained
the erroneous device description.
Operator Action:
None.
12-15
DH13-04
I
I
OUTPUT MESSAGES
OUTPUT MESSAGES
• lOP -n FOURD HUIG AID AUTOMATICALLY RELEASED FROM GCOS
RELEASE AND ASIGI lOP FROM MSOS TO CLEAR
n - 0, 1, 2, 3
lOS Message. Should GCOS 8 detect an anomaly during 1/0 processing, an lOP may
be released automatically from GCOS 8. This is an attempt to avoid a system
interrupt. The preceeding message is displayed at the console.
Operator Action: Use the MSOS command LOOK to dump the lOP that was released.
The Honeywell Bull Response Center can then be notified to analyze the
information gathered.
If you release (RELE
system will continue
IOPMPS reboot of the
assigned back to the
laPin) and assign (ASSIGN laPin) the failed lOP, the
in a fully operational mode. The release will cause an
lOP, which clears the problem and allows the lOP to be
active system •
••••filename IS ALREADY DEFINED 01 xxx FOR nnnn LLINKS
MUST BE AT LEAST mmmm LLIHKS LONG
Startup Message. Either there is a file on system storage with the same file
name described on a $ FlLDEF statement; (the function indicated is ignored and
the next statement is read), or the existing file is too small.
xxx
nnnn
mmmm
filename
-
Device name
Number of existing llinks
Number of required llinks
The name of the file on the $ FILDEF which already exists
Operator Action: If the existing file on system storage is to be overridden,
change the $ FILDEF statement such that the size field is followed by O. If
the file is too small, move it to a different device defined on a previous
$ GCOSFIL statement or do an INlT on the device on which the file is defined.
••• sssss: nnnn IS LOWEST ADDRESS THAT CAl BE RELEASED
Memory Release Message. MEMREL program was spawned by RLSEC request. The
value nnnn is the lowest 512-word block number that can be released and the
input request was for a lower value. Blocks 0 through nnnn are in use for hard
core segments, and MEMREL will release blocks nnnn+1 through mmmm where mmmm is
the end of the range given in the request.
Operator Action:
None.
12-16
DH13-04
I
I
OUTPUT MESSAGES
88888
OUTPUT MESSAGES
{IS
}
{IS NOT} A CYCLIC JOB IN .HOLD CLASS,
{STANDARD}
CAN'T USE {CYCLIC } VERBS
System Scheduler Message. The operator input a status-type request message for
a job in the .HOLD class, but used the wrong message form. If the job is a
cyclic job, a cyclic message form must be used as follows:
JCHGCY
JDELCY
JLSTCY
sssss
sssss
sssss
If the job is a standard job, one of the following standard forms must be used.
JPURGE
JRERUN
JSCHED
ABORT
sssss
sssss
sssss
sssss
Operator Action:
{ S
}
{ SCHED }
Reply with the correct message.
• xxx IS NOT__ACTIVE, Slsssss IS IN HOLD
Peripheral Allocator Message. The named device is required for execution of
the job, but was released by the operator or by system rollcall at Startup.
xxx - Device name
Operator Action: To run the job, enter an ASGN i ccc dd then a RUN sssss
request. If the device cannot be assigned to this job, enter ABORT sssss.
12-17
DH13-04
1
I
OUTPUT MESSAGES
OUTPUT MESSAGES
.ITDE - SI sssss - aa i-ccc-dd «(c)-INCOMPATIBLE DEISIT! -BlCW
UFAS Message. This message is only produced as a result of a failure to verify
both the recording density of the input volume and (if present) the explicitly
stated $TAPE entry tape reel serial number.
ITDE - Input Tape Density Error
sssss - SNUMB
aa - Activity number
i-Input/output controller number
ccc - Channel
dd - Device number
fc - File code
Operator action:
Enter:
N - Dismount tape and mount new tape to continue processing.
A - Abort the activity. This resolution produces an Execution Report
message " ••• FATAL ERROR - MODULE LMF1.1 CODE = 14 IC = nnnnnn ***"
where nnnnnn is the zero relative address of the error encountered in
module LMF 1.1.
C Accept the current input volume a.nd continue processing. This
resolution produces an Execution Report message " ••• WARNING Slsssss-aa i-ccc-dd - TRUE DENSITY IS nnn BPI FOR FILE CODE fc ••• "
W - This option forces a five-minute wait; the activity is delayed for five
minutes in order to provide operations time to attempt to resolve the
".ITDE" problem. The ".ITDE" message is automatically redirected to the
console following the wait period.
ITL! sssss-aa FOR FILE ON DS i ccc dd
IS: first 10 words of label
SHOULD BE: first 10 words of label image in program CEA
LABEL
Standard COBOL-68 1/0 System Message. The actual content of an input mass
storage file trailer label does not match the program parameters for that
content. The two values are given in alignment. The complete label is printed
if it is less than ten words.
Operator Action:
Enter C to continue execution using the present file.
Enter E to force the end-of-file condition on the input file.
Enter A to terminate the activity.
12-18
DH13-04
I
I
OUTPUT MESSAGES
OUTPUT MESSAGES
*ITLR S8S88-&a Mr i ccc dd
LABEL IS: first 10 words of tape trailer label
SHOULD BE: first 10 words of label image in program eEA
Standard COBOL-68 I/O System Message. The actual content of an input tape
trailer label does not match the program parameters for that content. The two
values are given in alignment. The complete label is printed if it is less
than ten words.
Operator Action:
Enter C to continue execution using the present reel.
Enter E to force the end-of-file condition on the input file.
Enter A to terminate the activity.
ITUL - SI sssss - aa i-occ-dd (fc) - UNRECOGNIZABLE LABEL - NAW
Tape Label Processor. The rTUL console message is produced when a tape was
successfully read, but the label type expected is not present. For example, if
a labelled GFRC tape was specified by the program, and the literal "GE BTL" is
not found, the "*ITUL" message is given.
rTUL - Input Tape Unrecognizable Label
sssss - SNOMB
aa - activity number
i-Input/output controller number
ccc - channel
dd - device
fc - file code
Operator Actions:
Enter N to dismount tape and mount new tape to continue processing.
Enter A to abort the job.
Enter W to forces a five-minute wait. The activity is delayed for 5 minutes
in order to provide the operator with time to attempt to resolve
the "*ITUL" problem. The "*ITUL" message is automatically
redirected to the console after the wait period.
12-19
DH13-04
I
I
OUTPUT MESSAGES
OUTPUT MESSAGES
-IVR Mr i oee dd sssss-aa HAl
Standard COBOL-68 I/O System Message. The I/O system was unable to read the
scratch tape mounted on the tape handler and could not check the reel for an
internal label.
Operator Action:
Enter N to try a new reel. The input/output system will dismount the
present reel to facilitate mounting another reel.
Enter A to terminate the activity.
Type xxxxx (a 5-character identifier for reel number) to continue processing
using the present reel. The existing content is overwritten with a
label containing this identifier (do not enter the number sign (I)
character) •
-IVR sssss-aa Mr i cco dd NAI
File and Record Control Message. An invalid reel exists.
tape file opened as output cannot be read.
The label on the
NAI - Operator reply
Operator Action: Enter N to dismount tape, mount new tape and continue; enter
A to abort the program; or, if the I option is used, enter the reel number of
the tape being accepted, not the character I.
12-20
DH13-04
SECTION 13
OUTPUT MESSAGES BEGINNING WITH THE LETTER J
JOB DELETED ssss ERROR EXIT
GPOP Message.
This job could not be restarted.
Operator Action:
None •
• JOB ENDED, R. TABLE OVERFLOW
GPOP Message. Too many object programs/loader statements caused the R.
description table to overflow.
Operator Action:
None.
xx JOBS IN .HOLD
System Scheduler Message. Jobs are cataloged in the .HOLD class that will not
be started automatically at a specific DATE/TIME.
xx - Number of jobs affected
Operator Action:
Release jobs from .HOLD class when possible.
JOBS THAT SIS SCHID CANNOT RECOVER ARE
System Scheduler Message. Batch jobs completed the input phase, but were not
yet cataloged on the SSFILE at the time of the restart.
sssss
sssss
Operator Action: To run any affected jobs during the currently-bootloaded
system operation, resubmit the jobs.
13-1
DH13-04
J
J
OUTPUT MESSAGES
{ALL
JPURGE
OUTPUT MESSAGES
}
{ONL }
{sid }
{sssss} READY
{.NAME}
Inn
}
{ACT
}
{SAY
}
System Scheduler Message.
upon operator request.
The system is ready to execute the requested purge
ALL - Purge all jobs currently cataloged by the System Scheduler
ONL - Purge all online jobs currently cataloged by the System Scheduler
sid - Purge all jobs originating at remote station identifier that are
currently cataloged by the 'System Scheduler
sssss - Purge a particular job currently cataloged by the System Scheduler
.NAME - Purge all jobs currently cataloged in class .NAME
nn - Purge all jobs currently cataloged under class number nn
ACT - Purge all jobs currently catalogued in ACTIVE status
SAY - Purge all jobs currently catalogued in SAVED status
Operator Action:
CANeL.
Reply JPURGE RUN, JPURGE (option) RUN, or JPURGE (option)
JRNL-MSG: sssss HAS { nn% } MORE COLLECTION SPACE FOR aa ••• a @ tt.ttt
{NO }
Integrated Software Message. The warning-fence is reached. It is then
re-issued each time the available collection space is halved. The final
warning message is issued when one percent of the collection space remains.
Where:
sssss
aa ••• a
nn
tt.ttt
-
snumb of SHARD
the journal's name
the percentage of Journal collection space let
the time in hours and thousandths of an hour
Operator Action:
None.
13-2
DH13-04
J
J
OUTPUT MESSAGES
OUTPUT MESSAGES
JRHL-MSG: S88SS COULD HOT ALLOCATE SISTEM JOURNAL FILE @ tt.ttt
CATALOG = 00 ••• 0
FILENAME = bb ••• b
BECAUSE { OF BAD CAT IFILE STRING}
{ DEVICE xu IS NOT ORLlNE }
Integrated Software Message. A file cannot be opened for collection because
the device on which it is located is not available or because the file does not
exist.
sssss
cc ••• c
bb ••• b
xxx
tt.ttt
-
the
the
the
the
the
snumb of the job attempting the allocation
name of the level-1 catalog under which the file is located
filename of the file
name of the logical device that is unavailable
time in hours and thousandths of an hour
Operator Action: No response for the bad CAT/FILE string.
have to be assigned.
DEVICE xxx will
JRIL-MaG: sssss {OPENED } FILE FOR aa ••• a @ tt.ttt
{ CREATED}
CATALOG = co ••• o
FILENAME = bb ••• b
Integrated Software Message. The "created" message is issued each time a
collection file is automatically created by journal software. Such creation
occurs only when collection space is exhausted and only if the AUTO CREATE
option is in effect.
sssss
aa ••• a
bb ••• b
cc ••• c
tt.ttt
-
the
the
the
the
the
snumb of the process performing the file open/create
journal's name
filename of the file
name of the level-1 catalog under which the file is located
time in hours and thousandths of an hour
The "opened" message is issued each time a collection file is opened.
is opened when:
A file
1. a volume swap occurs, or
2. a journal itself is opened (i.e., a journal is put into use after a
period of inactivity during which the resources (buffers, etc.) required
for journaling are not obtained or held).
Operator Action:
None.
13-3
DH13-04
SECTION 14
OUTPUT MESSAGES BEGIRBIHG WITH THE LETTER K
There are no output messages beginning with the letter K in this release.
14-1
DH13-04
SECTION 15
OUTPUT MESSAGES BEGINNING WITH THE LETTER L
.ssssss-aa LABEL ERR .nn ••• nn
LOAD CORRECT DECK, TYPE RD
CC.eeCC
NO
Bulk Media Conversion and UTL2 Message. Label checking was requested on a
$ INPUT statement (BMC) or the $ FOPT statement (UTL2) and the label on the
first statement in the reader did not match.
nn ••• nn - Label specified on $ INPUT statement or $ FOPT statement
cc ••• oc - Label found on first statement of data files
Operator Action:
the label check.
Place the correct deck in the reader and enter RD to repeat
LABEL FMS SAVE TAPE # xxxxx bbbbb
Integrated Software Message. This is produced as the result of an execution of
a DDBA command. It is issued when the first FMS save tape is mounted.
Where:
xxxxx - Reel number of the tape volume
bbbbb - Label of the tape volume
Operator Action:
None; informational message only.
LABEL JOURRAL TAPE # %%XXx aaaaa
Integrated Software Message. This indicates the header label processing for a
new tape volume of a journal was performed successfully.
xxxxx - Tape number
aaaaa - Label of the tape volume
Operator Action:
None; informational message only.
15-1
DH13-04
L
OUTPUT MESSAGES
-LABEL Mr i
L
OUTPUT MESSAGES
dd sssss-aa (io) xxxxx
000
File and Record Control Message.
tape is unlabeled.
An output tape has retention or an output
xxxxx - Reel number
Operator Action:
None.
-LABEL sssss-aa Mr i
000
dd (fo) VOL:mmm nnnnn
Standard COBOL-68 I/O System Message. The I/O system has completed the opening
procedure for an output file that is unlabeled, has a user-defined label, or
has a nonzero retention period. It indicates that the reel may be labeled with
an external label, if necessary.
mmm - Reel sequence number within file
nnnnn - Reel serial number of file to be labeled
Operator Action:
Prepare an external label, if necessary.
-LBL i coo dd filename
UFAS Message.
The reel on the specified tape unit is to be labeled.
Operator Action:
~~~~~
None.
LBL Mr Dliooodd sssss-aa rrrr
File and Record Control Message.
Operator Action:
The H2000 output tape is unlabeled.
None.
15-2
DH13-04
L
L
OUTPUT MESSAGES
OUTPUT MESSAGES
LDT!PE: Mr-DEVICE nnn !SGB TO SNUMB xxxxx FC fo
Operator Interface Message. Displays all tape devices that are currently
assigned by the DDTAPE verb.
nnn - device name
xxxxx - SNUMB number
fc - file code
Following the list of assigned tape devices a message is issued that shows the
number of free table entries. The message appears as:
LDTAPE: zz MORE TAPES CAN BE DEDICATED
zz - the number of available entries.
Operator Action:
None.
LDTAP!: SCT POINTER NOT FOURD
Operator Interface Message.
Operator Action:
«<
The SCT pointer is not in the device name table.
None.
Slsssss nnn LIST
nnn RECOVER
Integrated Software Message.
directives processed.
nnn ANALYZE
»>
Presents a summary of the deferred recovery
sssss - Deferred recovery process SNUMB
nnn - Totals for LIST, RECOVER, and ANALYZE directives
Operator Action: None.
15-3
DH13-04
L
L
OUTPUT MESSAGES
OUTPUT MESSAGES
-LINK WORD SYNC BIT
-IOI-a,CBAI-b,DEV-o
=0
Startup Message. An I/O to the above device terminated without setting the
mailbox link word sync bit (bit 27). This causes Startup to abort with a
linkage fault.
a - lOX number
b - channel number
c - device number
Operator Action: Notify the site administrator to check theSMAS ICON to
determine if the device indicated is properly configured. If it is, contact
Honeywell Bull Response Center.
-LLINK # TOO BIG 01 D,O,L,Y - EOM SKIPS THE CARD
Startup Message.
An invalid area is specified on the $ DIRECT statement.
Operator Action:
Correct the $ DIRECT statement and press EOM.
-xxx LINK ZERO BAD, DIRECTORY CLEARED MOST RESTORE HISTORY TABLE
Startup Message. The device named had its tables destroyed and all device
headers must be read to rebuild the tables.
Operator Action:
None.
sssss-aa LOAD CARD READER i coo
Bulk Media Conversion, UTL2 and Source/Object Library Editor Message. The
operator is requested to load the job input specified in the previous build
message:
sssss HAS RDR 1 ccc.
Operator Action:
reader.
Load the card input for the specified job into the card
15-4
DH13-04
L
L
OUTPUT MESSAGES
OUTPUT MESSAGES
-LOADFIL NOT VALID, MOST REPLACE $LOAD NEXT TIME
Startup Message. An error occurred on the last boot in the $LOAD section, and
it could not be corrected during LOADFILE.
Operator Action:
Correct the $LOAD section and reboot.
-LOADFIL TOO SMALL
Startup Message.
Insufficient file space was allocated for the GCOS files.
Operator Action:
Allocate more file space and retry.
-LOC. 0
-LOC. 0
= nnnnnnnnnnnn
= RESTORED,
nnnnnnnnnnnn
YES TO CONTINUE
Startup Message. The absolute location 0 or 1 in memory was corrupted. Upon
detection of this error, Startup restores location 0 and 1 and gives the
operator the choice of continuing or aborting.
n - Octal contents of locations 0 and 1
Operator Action: Enter YES to continue.
will abort Startup.
Any other response, including EOM,
-LOC. 0 = nnnnnnnnnnnn nnnnnnnnnnnn AFTER INIT OF .Mmmmm
-LOC. 0 = RESTORED, YES TO CONTINUE
Startup Message. Absolute location 0 in memory was corrupted during
initialization of module .Mmmmm. Startup will restore location 0 and give the
operator the choice of continuing or aborting Startup.
n - Octal contents of location 0 and 1
mmmm - Module name
Operator Action: Enter YES to continue.
will abort Startup.
15-5
Any other response, including EOM,
DH13-04
L
L
OUTPUT MESSAGES
OUTPUT MESSAGES
-LOCATE SCRATCH FOR STEM COLLECTOR sssss-aa
ON i-eee-dd SEQ qq; ENTER I
STEM (PERSUE-8) Message. A tape mounted for STEM is to be continued. This
message requests the serial number of the next tape to be mounted on handler
i-ccc-dd such that trailer label can be constructed. The Locate message is
followed by a STEM Verify message.
Operator Action:
Enter the serial number of the next tape to be used.
-LOCATE SCRATCH sssss-aa SEQ' rrr FOR HT i cec dd AND ENTER I
or
-LOCATE SCRATCH sssss-aa SEQI rrr FOR HT i ccc dd (~ ccc dd) ENTER #
File and Record Control Message.
multi-reel file.
An end-of-reel label is required on a
rrr - Reel sequence number
Operator Action: Enter the next sequential reel number for i ccc dd, which
must not contain leading or embedded blanks or special characters.
-LOG STEM COLLECTOR sssss-aa 01 l-eec-dd;
REEL nnnnn SEQ qq DEldddd NEXT nnnnn
STEM (PERSUE-8) Message. STEM has filled a tape, written a trailer label, and
issued the dismount command.
Operator Action:
dismounted tape.
Prepare any site documentation (sticky label, etc.) for the
LOOK: ENTER (PXIX SSS, MID, H6nx) OFFSET HUM(OCTAL)
Operator Interface Message.
operator entered verb LOOK.
Operator Action:
Output on the system console in response to the
Enter one of the following values:
P - Dump a process
M - Dump a module
H6 - Dump an HCM segment
XXX - Process number to be dumped (three digit maximum)
- Module number to be dumped (identified via .ENTRY macro)
- Segment identification as defined in system linkage segment.
15-6
DH13-04
L
OUTPUT MESSAGES
L
OUTPUT MESSAGES
SSS - Index of the descriptor of the segment that is to be dumped.
OFFSET - Location within the segment/module where dumping is to begin.
NUM(OCTAL) - Number of locations to be dumped, beginning with the OFFSET
value.
NOTE: If dumping a module and the module is not in memory, the following
message is issued:
-NOT IN CORE/SYSTEM
-LOST SIEVE LIMITS IF SET FROM CONSOLE IN PRIOR BOOT
POPM Message. Sieve limits that were changed via entry of the LIMIT console
verb are normally carried across system bootloads. If the system
initialization and/or recovery error occur during the restart process, this
message may be issued.
Operator Action: Following successful system reboot, reenter the sieve limit
changes via the LIMIT console verb.
<
-LRT lIT ssxx ppp 1cccdd sssss (pppppppppppp dn) (operator response)?
Exception Processor Message. A Data Alert, with a substatus of ss, occurred on
the specified device ppp while trying to execute the instruction indicated by
the code xx.
I/T - Status was returned on an Initiate/Terminate interrupt.
ss - Octal substatus code (Refer to Appendix D). Substatus codes may be
combined. For example, -LRT T 30xx Mr ••• is a combination of both
lateral and longitudinal parity alerts.
xx - Instruction code (refer to Appendix A).
ppp - One of the following device types:
CP
CR
DP
DS
~ PR TY -
Card Punch
Card Reader
Disk Pack
Disk
Magnetic Tape
Printer (refer to the NOTE)
Console
15-7
DH13-04
L
OUTPUT MESSAGES
L
OUTPUT MESSAGES
NOTE: In the event of an interface error on the PRU1200/PRU1600 (i.e., major
status 12 and substatus 02) it is necessary to execute a stop/start
sequence at the printer even though the printer appears to be ready
(i.e., the ready lamp is lit). This interrupt procedure must be executed
prior to any further operator intervention such as a retry request.
i-Input/output controller number
ccc - Channel number
dd - Device number
sssss - SNUMB number
Operator Action: One or more of the following explicit responses may be
available. These are punctuated with a question mark (?) and the keyboard is
enabled to allow operator input.
R - Retry I/O.
U - Return status to the user program.
B - Card Punch - Manually cycle three cards and ready the device before
responding.
Card Reaqer - Remove the last card from the stacker, reposition it in
the input hopper and ready the device before responding.
P - Rewind and reposition the magnetic tape.
S - Type the disk seek address. The Data Alert message will be repeated.
M - Move all messages from the failing device to an alternate console.
V - Select an alternate track.
W - Deallocate defective space and abort the program.
The following implicit options are· not printed on the console by the Exception
Processor, but are available:
A - Abort the job.
X - Exchange the device for another device (may be combined with the R or B
option).
If the message is not punctuated by a question mark (7), the keyboard will not
be enabled. In this case, an interrupt from the device is required after
correcting the existing condition. The following options may be seen:
RDY - Ready the device.
BSP - Manually backspace and then ready the device.
U - Status is sent to the user program. Ready the device.
15-8
DH13-04
L
OUTPUT MESSAGES
<
L
OUTPUT MESSAGES
A variety of conditions may have caused the Data Alert message to be printed
depending on the device type. Before responding at the console, the operator
may attempt to manipulate punched cards, replace VFU's, move console names,
etc.
EXAMPLE:
*LRT T 2015 MT 0 12 10 5840Z HUP?
A Data Alert exists on a terminate interrupt from the magnetic tape device 10
on IOM-O, channel 12, while running SNOME 5840Z. While executing a write tape
binary (15) instruction the system encountered a longitudinal parity (20). The
operator can retry I/O (R) several times or to try to reposition the tape (P).
If not successful, enter a "un to allow the user a chance to recover. The next
step is to enter "X" and try the tape on a different handler. Finally, if all
else fails, enter "A" to abort the program.
***LST xx pp 1-ccc-dd sssss seek address (disk only) (operator response)?
Exception Processor Message. An instruction, coded xx, was issued to the
device pp, but no termination interrupt was received.
LST - Lost interrupt
xx - Instruction code (refer to Appendix A)
pp - Indicates one of the following device types:
CP
CH
DP
DS
MT
PR
TY
-
Card Punch
Card Reader
Disk Pack
Disk
Magnetic tape
Printer
Console
i-Input/output controller number
ccc - Channel number
dd - Device number
sssss - SNUMB number
Operator Action: One or more of the following explicit responses may be
available. These are punctuated with a question mark (?) and the keyboard is
enabled to allow the operator to respond.
R - Retry I/O.
U - Return status to the user.
S - Type the disk Seek address.
The Lost Interrupt message is repeated.
15-9
DH13-04
L
L
OUTPUT MESSAGES
OUTPUT MESSAGES
The implicit "A" option is not always printed on the console by the Exception
Processor, but it is always available for aborting the job.
A variety of conditions may have caused the Lost Interrupt to occur. Before
responding at the console, the operator may attempt to clear or reset the
device or its MPC, power on or ready devices, or correct other device
malfunctions.
EXAMPLE:
***LST 31 DP 0 08 26 6837Z RUS?
A wl'ite disk-continuous instruction was issued to the disk pack on IOM-O,
channel 08, device 26, while running SNUMB 6837Z. No termination interrupt was
received back from the device. After correcting any malfunction, if possible,
the device should be placed on-line and in a ready condition. The options
available are to (S) check the disk Seek address (the original message is
repeated), (R) retry the IIO, (U) let the user program try to recover, or (A)
abort the job.
LSTRE HAS BEEN REPLACED - PLEASE USE SISOUT
SYSOUT Message.
Operator Action:
The verb LSTRE was replaced with the verb SYSOUT.
Use the correct verb, SYSOUT.
LSTWT HAS BEEN REPLACED - PLEASE USE SYSOUT
SYSOUT Message. This message indicates that the verb LSTWT was replaced with
the verb SYSOUT.
Operator Action:
Use the correct verb, SYSOUT.
. 15-10
DH13-04
SECTION 16
OUTPUT MESSAGES BEGIIRIHG WITH THE LETTER M
*Mmm I/T ssxx pp i-ccc-dd
SBBBS
(p ••• p) (operator response)?
Exception Processor Message. A major status error occurred on device pp. The
problem may be coded in the major status itself (mm) or in the substatus (55).
• - Indicates an error on a user I/O
••• - Indicates an error on GCOS 8 system I/O
mm - Two-character major status code (octal):
Hardware Initiated
00
01
02
03
04
05
12
13
15
-
Channel Ready
Device Busy
Attention (with substatus code)
Data Alert
End of File
Instruction Reject/Command Reject
MPC Device Attention (see to Appendix B)
MPC Device Data Alert (see to Appendix B)
MPC Command Reject (see to Appendix B)
Software Initiated
02
07
11
14
14
16
17
17
-
PAT Refresh On PERM File (No substatus code)
PAT Contains Linkage Descriptor Error Or Seek Address Error
Lost Interrupt
Invalid Seek Address (substatus code 76 octal)
Inoperative Channel (substatus code 77 octal)
Missing Sync Bit
Fault Channel Interrupt (if no substatus code returned)
Logical EOF (if substatus code 55 (octal) returned)
For more information about software-initiated statuses, refer to
Section 5 of the GCOS 8 OS I/O Programming manual.
I/T
ss
xx
pp
-
Status was returned on an Initiate/Terminate interrupt.
Octal Substatus code (refer to Appendix D).
Instruction code (refer to Appendix A).
Indicates one of the following device types:
CP
CR
DP
DS
-
Card Punch
Card Reader
Disk Pack
Disk
MI' - Magnetic Tape
PR - Printer
TY - Console
16-1
DH13-04
M
M
OUTPUT MESSAGES
OUTPUT MESSAGES
i-Input/output controller number
ccc - Channel number
dd - Device number
sssss - SNUMB
p ••• p - Optional; one of the following:
If device (pp) is Magnetic Tape (MT) then p ••• p is equal to position
and density.
If device (pp) is Disk Pack (DP) or Disk (DS) the p ••• p is equal to
SA (seek address).
Operator Action: A variety of conditions may have caused the Major Status .
message to occur. In each case, the device must be reset and readied before
any operator response is input.
One or more of the following explicit responses may be available. These are
punctuated with a question mark (?) and the keyboard is enabled to allow the
operator to respond.
R - Clear and ready device and retry I/O.
U - Return status to the user program.
S - Type the disk seek address. The major status message will be repeated.
The implicit A (abort) option is not always printed on the console by the
Exception Processor, but it is always available for aborting the job as a last
resort. If recovery is not possible contact Honeywell Bull Response Center.
EXAMPLE 1:
.M02 I 0246 MT 0-08-01 MDUMP 001604454001 0 R?
The system has detected a major status 02 (Attention) while trying to process a
terminate Initiate (I) from the magnetic tape (MT) on IOM-O, channel 08, device
01. More specifically, the system detected a substatus code of 02 (No Such
Tape Unit) at seek address (SA=001604454001 0). The operator should clear the
device, readi it, and enter R to retry.
EXAMPLE 2:
.M01 I 2031 DP 1-44-16 6181T SA=2240 03054140 RA?
The system has detected a major status M01 (Device Busy) while trying to
process a Initiate interrupt (I) from a disk pack (DP). More speCifically, the
system detected a sUbstatus code of 20 (storage directory busy; alternate
channel in control) at seek address (SA) 2240 03054140. The operator should
clear the deVice, -ready it, andenterR t-o retry~viaon the alternate channel.
If the problem persists, enter A to abort the job.
16-2
DR13-01l
M
M
OUTPUT MESSAGES
OUTPUT MESSAGES
MASS STORE ERROR AT nnnnnn STATUS ssssss
An error status (ssssss) was returned during performance of function at
nnnnnn. The Dump program attempts to continue with the next operation.
Operator Action:
None •
••• MASS STORAGE ALLOCATOR DENIAL •••
(A)BORT, (C)ONTINUE
Save/Restore Message.
One of the following circumstances occurred.
o
When releasing an existing catalog and file space at the beginning of a
Restoremast operation, the mass store allocator found that some of the
space was already marked as being available because of a previously
aborted restore (aborted before some of the catalog or file space was
marked unavailable) or because one or more disk packs (but not all)
containing files (but not the catalog) were utilized by the installation
prior to the Restoremast.
o
No space was available on any catalog devices for the user's structure.
Restore is terminated.
o
A request was made to the Mass Storage Allocator to obtain space for an
overflow SMC llink, and the request was denied because no space was
available on the disk.
Operator Action:
Enter A to abort or C to continue restore.
MC:
[=>unit_id in error]
The MC: (Modify Configuration) output messages are listed in the following
order:
1. Error messages denoting errors in input message syxtax.
2. Error messages denoting errors during DEDICATE processing.
3. Error messages denoting errors during UNDEDICATE processing.
4. Error messages denoting errors during ASSIPN, ASSIGN CPU, ASSIGN MEM,
ASSIGN SCU, and ASSIGN lOP processing.
16-3
DH-13-04-
M
M
OUTPUT MESSAGES
OUTPUT MESSAGES
5. Error messages denoting errors during RELEASE, RELEASE CPU, RELEASE MEM,
RELEASE SCU, and RELEASE lOP processing.
6. Error messages denoting errors during HELP processing.
7. Error messages denoting errors of a general nature (i.e., not unique to
one of the categories above).
On the MC Level
MC: (input message>
The messages shown below, are all produced as errors prior to any
checking of the command.
System Replies possible:
MC: (input message repeated>
PLACEMENT OF HELP COMMAND NOT VALID
The command "HELP" is not at either the beginning or the end of the
request, therefore the message is ABORTED.
MC: (input message repeated>
THE REQUESTED OPTION IS NOT VALID
The option specified is not in the table of valid options.
OPTION
= -FORCE
used with input/output controller
-TEST used with CPU/EPU
MC:
MESSAGE DOES NOT CORT AIN A COMMAND
This probably will not happen very often but if it does, the message will
be displayed and aborted since there obviously is not anything to
process.
MC: (input message repeated>
HC IS HOT A VALID CLASS CODE FOR THIS COMMAND
The command is not a Modify Configuration command but is a List
Configuration command. Therefore, the construction of this message is
illegal and will be aborted.
16-4
DH13-04
M
M
OUTPUT MESSAGES
OUTPUT MESSAGES
MC: MESSAGE CONTAINS wNON BCD- CHARACTER
INPUT MESSAGE REJECTED
The message contains a nBACKSLASHn meaning that the character "In was
entered or an ASCII character which would not translate (also producing a
"\") was detected. This character is used by the scanning routines as
the terminator character for the message processing and cannot contain
any other "\" characters in the string. Therefore the message is
aborted.
On the MC Level
MC:
The message shown below is produced when something is found to be invalid
with the command.
System Replies Possible:
MC:
INVALID COMMAND
No match was found in the table of valid commands. The message is
aborted.
On the MC Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.6 Linearized : No XMP Toolkit : Adobe XMP Core 4.2.1-c041 52.342996, 2008/05/07-21:37:19 Create Date : 2018:03:09 09:47:49-08:00 Modify Date : 2018:03:09 10:22:51-08:00 Metadata Date : 2018:03:09 10:22:51-08:00 Producer : Adobe Acrobat 9.0 Paper Capture Plug-in Format : application/pdf Document ID : uuid:2d854326-51e2-2d46-8262-c7e65565a0cd Instance ID : uuid:6602ed58-7d05-c243-9a84-0c9506de84fd Page Layout : SinglePage Page Mode : UseNone Page Count : 1216EXIF Metadata provided by EXIF.tools