System80_8 20_OG_7004_5208 00_ System80 8 20 OG 7004 5208 00
System80_8-20_OG_7004_5208-00_ System80_8-20_OG_7004_5208-00_
User Manual: System80_8-20_OG_7004_5208-00_
Open the PDF directly: View PDF 
.
Page Count: 292
| Download | |
| Open PDF In Browser | View PDF |
(
Sysferp'8()/
odels~:8~20
OS/3···'
Operatiori~':·
Guide . .
..
(
\
November 1991
Printed in U S America
Priced Item
7004 5208-000
(
c
System 80
Models 8..20
OSj3
Operations
Guide
Copyright © 1991 Unisys Corporation
All rights reserved.
Unisys is a registered trademark of Unisys Corporation.
OS/3 Release 14
November 1991
Printed in U S America
Priced Item
7004 5208-000
'I
~,
NO. WARRANTIES DF AN( NATURE ARE EXTENDED BY THIS DDCUMENT. Any product and related material
disclosed herein pre only fu(1!ished pursuant and s\Jbject to.the terms arid conditions of a duly executed Program
,Product UcenseCirAgreement to purchase or lease equipment.. The only warranties made by Unisys, if any, with
respect to the products described in this dccumeilt aresi!t:forth in such License or Agreement. Unisys cannot
accept financial or other responsibility that may be the result of your use of the information in this document or
software material, including direct, indirect, special, or consequential damages.
.
You should be very careful to ensure that the use of this information and/or software material compliegwith the
laws, rules, and regulations of the jurisdist;ion~ with respect to whtch it is. used.
. .'
.:
Theiriformation cQntained herein is subject to change without notice. Revisions may be issued to advise of such
changes and/or addmons.
.
Corresp.ondeilCe regarding this publication should be forwarded to Unisys'Corporation either by using the User
Reply form at the oack of this manual or by addressing remarks directly to Unisys Corporation, SPG East Coast
Systems Documentation Development, Tredyffrin Plant, 2476 Swedesford Road, P.o.. Box 203, Paoli, PA, 1930.1·
o.~03, U.!i.A. .: , . '
'"
" ,'.: '
,.
",
'('.\
•
UNISYS
Product Information
Announcement
..
o New Release
Revision
0
Update
0
New Mail Code
Title
System 80 Models 8·20 05/3 Operations Guide
This announces the release of a revision to this guide. It was previously released as the System 80 Models 3-6 and 8-20 OS/3
Operations Guide, UP-8859.
This guide provides all information required to operate System'BO models 8;' lO, 15, imq20rtmningunder the OS/3 operating
system. The guide is intended for use bysystemoperatdr~ and administrators. ,
Changes for OS/3 Release 14 include:
~.
\
".
An enhanced console screen that provides a menu bar; pull-down windows, and express command entries via the keyboard
function key.
",
.,'
Y.
'~/,~.'
An automatic boot procedure that automaticallY,loaqs your supervisor ..each time;anaatd-l,PLLo'ccurs.
~
,.
,
'.,
"
.
"', ; ".
,.,~1
\: ':
.J' ~
. :.,o::~
.~;
,. ,",',
-
)
'-.
-'
'.'
f'>"
Addition of the NOWRITE and WRITE parameters for the SET 10 commimq (used to write':ProteCt your I/O devices).
Additional job status informational messages (JS/SY command).
Security and resource management generation requirements affecting the LIMITS command.
A SET LX command that lets delegated console/Workstation users view messages sent to logged off users.
Procedures for downline loading a Telcon file to front-end processor or a remote concentrator DCPs.
Two ICAM unsolicited messages that bring a switched line type up as either a manual dial line or an unattended line.
Revised information for optimizing the disk cache facility.
41
Expanded ONUERL procedures for running the program manually on an as-needed basis or automatically on a fixed, 7-day
cycle.
The deletion of all information related to System 80 Models 3 through 6.
To order additional copies of this document:
..
..
..
United States customers should call Unisys Direct at 1-800448-1424.
All other customers should contact their Unisys Subsidiary Librarian.
Unisys personnel should use the Electronic Literature Ordering (ELO) system.
Announcement only:
Announcement and attachments:
SAB, SAE, and MBOO
ECC3 and MB01
System: System 80
Release: 14
Date: November 1991
Part Number: 7004 5208-000
'1'
(
(
\
PAGE STATUS SUMMARY
ISSUE: 7004 5208-000
Part/Section
Page
Nl.iI1ber
Update
level
Cover
000
Title Page/Disclaimer
000
PSS
iii
About This Document v thru x
Part/Section
Page
Nl.iI1ber
Update
Level
Part/Section
Page
Nl.iI1ber
Update
level
000
000
Contents
xi thru xix 000
1
1 thru 23
000
2
1 thru 18
000
3
1
000
4
1
thru 87
000
5
1
thru 11
000
6
1
thru 14
000
7
1
thru 38
000
8
1 thru 13
000
9
1 thru 40
000
10
1
thru 4
000
Appendix A
1
thru 4
000
Index
1 thru 10
000
User Reply Form
000
Back Cover
000
Unisys uses an ll-digit document numbering system. The SuffIX of the document number (1234 5678-xyz) indicates the document level. The first digit of the suffix (xl
designates a revision level; the second digit (y) designates an update level. For example, the first release of a document has a suffix of.ooo. A suffix of -130 designates the
third update to revision 1. The third digit (zl is used to indicate an errata for a partcular level and is not reflected in the page status summary.
7004 5208-000
iii
(
About This Document
Purpose
This guide is one of a series designed to instruct and guide the operator in the
procedures required to operate the System 80 under the control of Operating SystemJ3
(OS/3). It indicates how to initiate and control basic system operations. This guide also
provides general reference material that may be used after you have become proficient
with all basic operating procedures.
Scope
This guide describes the daily operational tasks normally performed by the system
operator. These tasks include system start-up and initialization, job processing,
control of interactive services, control of the integrated communications access method
(ICAM), and use of I/O media system services.
Audience
The intended audience for this guide is the novice operator with a basic knowledge of
data processing operations and the more sophisticated operator who has some
experience with the Unisys operating systemJ3 (OS/3).
Prerequisites
The reader should have experience or training in the concept of data processing.
How to Use This Guide
Read the entire guide to familiarize yourself with the concepts, procedures, and
instructions that it presents; then use it for reference as needed.
(
7004 5208-000
v
About This Document
III
The delta symbol/:::" indicates a space:
SHUTDQl,JNllDDP
III
Lowercase letters represent variable information that is either displayed or
keyed in. For example, the following command format implies that the command
DELETE must be followed by the name ofthejob to be deleted.
DELETElljobname
III
Underlined letters in a command indicate that they are the only letters required
to be keyed in to initiate processing of the command and its associated symbiont.
For example, only the letters DE need be keyed in to initiate processing of the
DELETE command and subsequent running ofthe delete symbiont. Its format is
presented as:
DELETElljobname
III
(
Braces { } illustrate alternate choices. For example, the format of the change
command
CHANGEAjObname'~PRE
1
!!IGH
MOR
LQI,J
indicates that PRE (P), HIGH (H), NOR (N) or Low (L) may be keyed in after the
job name.
III
Brackets [ ] denote optional entries.
For example, this portion of the FILE command format
FILE~(did)
([dld], label) ~
(RDR, label)
indicates that the FILE command can be keyed in by itself, or with a parameter
as specified in the format.
III
Default parameters are shaded. For example, the ENTER command format
ENTERA' f i l ename I I QUEUE=RDR [HOLD=
{i~
specifies that the filename and QUEUE=RDR parameters must be included
(parameters 1 and 2). If you omit parameter 3, HOLD=Y is used.
Note:
viii
Not all optional parameters have a default specification.
7004 5208-000
About This Document
•
An ellipsis C.. ) indicates the omission of a variable number of entries.
modifier-1, ••• ,modifier-n
•
A colon (:) and parenthesis symbols 0 are indicates for several job initialization
commands. These symbols are part of the applicable command syntax and must
be entered to define the indicated parameter.
Related Product Information
Other current OS/3 publications that are helpful when operating the models 8-20
system include:
Note:
(
Throughout this guide, when we refer you to another manual, use the current
version that applies to the software level in use at your site.
Consolidated Data Management Programming Guide, UP-9978
Describes what data management is and how it handles the transfer of data between
peripheral devices and programs. It also describes OS/3 data file formats.
Dump Analysis Programming Guide, UP-9980
Discusses the process of analyzing OS/3 dumps. Explains the purpose of various types
of dumps, when and how to use them, their formats, and their interpretation.
Installation Verification Procedures (IVP) Operating Guide, 7004 5232
Describes the procedures used to verify that OS/3 software products are properly
installed and ready to use.
Interactive Services Operating Guide, UP-9972
Describes the use of interactive services terminals and their capabilities. Includes logon and log-off procedures, ICAM sign-on procedures, and use of interactive commands
and utilities.
Integrated Communications Access Method (lCAM) Utilities Programming
Guide, 7004 4565
Describes how to use the ICAM utility routines.
7004 5208-000
ix
About This Document
Interactive Services Commands and Facilities Programming and Operations
Quick-Reference Guide, UP-9973
Provides quick-reference information on interactive services commands,
log-on and log-off procedures, and ICAM sign-on procedures.
Job Control Programming Guide, 1004 4623
Describes the OS/3 job control procedures and options.
Models 8-20 Installation Guide, 7004 5505
Describes procedures for installation and maintenance of OS/3 software in a model
8-20 environment.
Models 8-20 Integrated Communications Access Method (lCAM) Operations
Guide, 1004 4551
Describes how to prepare the ICAM syrnboint to support communications on model
8-20 systems.
Spooling and Job Accounting Operating Guide, 10044581
Describes the spooling capabilities and controls provided for the system administrator,
programmers, and operators.
Supervisor Technical Overview, UP-8831
Describes concepts of the OS/3 supervisor.
System Messages Reference Manual, 1004 5190
Describes the OS/3 system messages and operator actions.
(
x
7004 5208-000
Contents
About This Document
Section 1.
System Definition
1.1. System Configuration •.....••..•.•..•........•••.
1.2. Central Hardware . . . • . . . • . . . . . . . . . . . . . . . . . . . . . . .
1-1
1-3
1.2.1. Control Storage •••••••••••••••••••••••••••.
1.2.2. Main Storage ••••••.•••••••.•••••••.•••••..
1.2.3. System Instructions .•••••.••..•••••••.•••••..
1.2.4. System Registers ••••.••••••••••••.••••••••.
1.2.5. System Control Processor (SCP) •••••••••••.••••••
1.2.6. Input/Output Microprocessor (IOMP) or Input/Output
Processor (lOP)
••••.••.•••••.••••••••••••••••
Diskette Controller .•••••••••••.••.•••..••••••
Workstation Controller •••••.•••.•••••••••••••••
Paper Peripheral Controller •.••••••••••.•••••••••
Integrated Tape Controller
••••.••.•••••••.••••••
Single-Line Communications Adapter (SLCA) ••...•••••••
1.2.7. Channel Controller (Model 8 Only) ••.••••.••••••••••
Byte MUX Channel ••.•.•••••••••••••••••••••.
Integrated Selector Channel ••••.••.••••••.•.•••••
1.2.8. Selector Channel (Models 10/15/20 Only) ••••..•••.•••
1-4
1-4
1-4
1-4
1-5
1.3. Input/Output Subsystems
•.....••......•......... •
1.4. OS/3 Operating System
.•••. . •. •••. . . . . ••. . . . . . . .
1.4.1. Supervisor •••••••••••••.•.•••..••..•••••
1.4.2. Job Control •••••••.••••••..•••••.••..••••
1.4.3. Data Management •.•..••••••••.••••••.•••••
1.4.4. Integrated Communications Access Method ••••.••••••
1.4.5. Utility Programs .••••••.••.•...••.•...•.•••
1.4.6. Information Management System •..•••••.•..•..••
1.4.7. Language Processors
••.••••.•...•••..•.••••
1.4.8. Diagnostic Programs .•••.••.•••.•••••..•••••
1.4.9. Data Base Management System
••••••••••.••.•••
1.4.10. Application Programs ••.•••••••••••••.•••.••
1.4.11. Interactive Services •••••.•.•••.•••••••••••.
(
1.5. Console and Control Panel
.••...•..•....•.•..•....
1. 5.1. System Console •••••••..••••.•••••••.•••••
1.5.2. System Control Panel .•••••••.•••••••••••••••
1.5.3. System Console Screen .•••••••..•••••••••••.
7004 5208-000
1-5
1-6
1-6
1-6
1-6
1-7
1-7
1-7
1-7
1-8
1-8
1-9
1-10
1-11
1-11
1-11
1-12
1-12
1-13
1-13
1-13
1-13
1-13
1-14
1-14
1-16
1-18
xi
Contents
Section 2.
System Power-On and Initialization Procedures
2.1.
2.2.
2.3.
2.4.
Generallnformation ....••..•..•..•..•.•...•...••• 2-1
System Power On and Initialization - Cold Start •••........• 2-3
Automating the Supervisor Load Process •...••...•.•••.
2-14
System Reinitialization ••••..•.•••....•.•...•.....
2-15
2.4.1. Initial Microprogram Load Procedure •••••••••••••••
2.4.2. Initial Program Load Procedure •••••••••••.•••..••
2.5. IPL Information
Section 3.
.•.•••..•..•.•••.••...•.......•.
2-15
2-16
2-17
System Power-Off Procedure
3.1. System Power Off
3-1
(
Section 4.
Job Processing Procedures
4.1. Keyin Procedure
..•••.•..••••.•.....•....•....•.
4.1.1. Console Keyin Procedure .• • • • • • • • • • • • • • • • . . • • ••
4.1.2. Alternate Console Keyin Procedure •••••••••••••••.••
4.2. Command Characteristics ••...•••..••.......•..•.•.
4.3. Message Characteristics .•..•...•...•.••...••......
4.3.1. Output Messages •••••••••••.•.••••••••.••...
4.3.2. Solicited Input Messages
••.• • • . • • • • • • . • • • . . • • ••
4.3.3. Unsolicited Input Messages •••.•.•••••••••••••.••
4.4. Job Processing During the Daily Memory Refresh Routine
4.5. Job Processing Commands
•..•......••...•..•.....
4.5.1. Job Initialization •••••••••••••.••••.•..•.••••
Filing Job Control Streams (FILE) •••.••••.•••••••••
Running Job Control Streams (RUN/RV)
••••.•••••••••
Running Saved Job Control Streams (SI/SC) ••.••...••.•
4.5.2. Job Scheduling •••••••••••••.•.•••••••.••••
Deferring Jobs Scheduled for Execution (HOLD)
• • • • • • • .•
Scheduling Deferred Jobs (BEGIN)
• • • • • • • • • • • • • • • ••
Deleting Jobs or Symbionts from Scheduling Priority Queues
(DELETE) ••••••••••••••.•.••••••••••••.•
Displaying Jobs in Scheduling Priority Queues (DISPLAY)
Changing a Job Scheduling Priority (CHANGE) •••.•••••••
4.5.3. Job Execution ••••••.•••••••••••••••••.••••
Suspending a Job in Progress (PAUSE) ••.•••••.•••.••
Reactivating a Suspended Job (GO) •••••••.••••..•••
Changing a Job Switching Priority (SWITCH) ••.••••.••••
4.5.4. Job Termination ••••••••••••.••••••••••.••••
Canceling a Job in Progress (CANCEl) ••••••••••.••••
Soft Cancel of a User's Job (CJ) .••••••••.••••.••••
Stopping Execution of a Dump (END) .•••••••.••.••••
Terminating a Job (STOP) ••.••••••.••.•..•.•••..
xii
4-1
4-1
4-2
4-4
4-6
4-6
4-7
4-7
4-9
4-10
4-11
4-12
4-14
4-19
4-22
4-23
4-25
4-28
4-31
4-35
4-36
4-36
4-37
4-38
4-39
4-39
4-41
442
4-43
7004 5208-000
(
Contents
4.6. Selected Occasion Operator Commands .....•.........
4.6.1. Displaying Portions of Main Storage (DISPLAY) ••.••••••
4.6.2. Displaying System Information (MIX) •••••••••.•••••
4.6.3. Reconstructing Console Display (REBUILD) •••..••••••
4.6.4. Setting Simulated Day Clock (SET CLOCK) •••••.•••.•
4.6.5. Setting Date Field (SET DATE) •••..•••••••••••.•.
4.6.6. Setting Error Log (SET ELOG) •••••••••••..••••••
4.6.7. Discarding System Messages (FLUSH) ..•••••..•.•••
4.6.8. Setting Physical Unit Blocks (SET 10) •.••••••••••.••
4.6.9. Reading a Mounted Volume Serial Number (AVR) ••••••••
4.6.10. Displaying Job Status (DISPLAY JS/SY) ••••••••••••.
4.6.11. Dumping the Contents of Main Storage (SYSDUMP)
4.6.12. Setting the $Y$DUMP File to Unlocked Condition (SET SY)
4.6.13. Setting Main Storage Condition (SET MEM) ••••••••• •
4.6.14. Setting the Unattended Console Feature (SET UN CON)
4.6.15. Terminating System Activity (SHUTDOWN) ••.•.•••••.
4.6.16. Initiating Transient Work Area Feature (TW) • • • • • • • • • •
4.6.17. Specifying Resource Management(LlMITS) •.•••••••.
4.6.18. Verifying and Correcting the vroc (VV) •••••••••••••
(
vroc
Verifying the
during AVR (SET VV)
•••••••••••••
Error Reporting to Unisys Support Center
'" • • • • • • • • •
4.6.19. Setting Memory Consolidation Conditions (SET MC)
4.6.20. Setting Job Immovability Conditions (SET 1M) ....•••••
4.6.21. Displaying Buffer Pool Information (DI BI) •••••.••••••
4.6.22. Enabling;Disabling the Console/Workstation Alarm Beeper
(SET AL) ••••••••••••••••••••..•••••••••••.
4.6.23. Enabling;Disabling the Console Video Clock (SET VCl
4.6.24. Changing Symbiont Execution Priorities (SET PSl •.•.•••
4.6.25. Setting Console Message Viewing Privileges (SET CV)
4.6.26. Viewing Messages Sent to Logged Off Users (SET LX)
Section 5.
445
446
4-52
4-52
4-53
4-54
4-57
4-57
4-61
4-61
4-67
4-68
4-68
4-69
4-70
4-71
4-71
4-75
4-82
4-82
4-83
4-83
4-84
4-85
4-86
4-86
4-87
4-87
Interactive Services
5.1. Interactive Services Commands ...................•.
5.1.1. Sending Messages to Users (TELl) •••••••••••••••••
5.1. 2. Asking Questions of Users (ASK) ••••••••••••••••.•
5.1.3. Displaying System Status (STATUS) ••.• • • • • • • • . • • • •
5.1.4. Displaying Log File (RECALL) ••••••.•••••.••.•.•••
5.1.5. Modifying Bulletin and/or Log Values (SET IS) •..••.•••.•
5.1.6. Starting Interactive Services (IS) • • • • • • • • • • • • • • • • • •
5.1. 7. Terminating User Tasks or Sessions (REMOVE) ••••.•••••
5.2. Interactive Services Messages .....................
5.2.1. Restricting New User Sessions (CLOSE Message) •••••••
5.2.2. Releasing New User Session Restrictions (OPEN Message) .•
5.2.3. Controlling Interactive Services for Terminals
(REMOTE Message)
.•.••••••••••.•••••.•••••••
5.2.4. Terminating Interactive Services (SHUTDOWN Message)
7004 5208-000
444
5-1
5-2
5-2
5-3
5-7
5-8
5-8
5-9
5-10
5-10
5-10
5-10
5-11
xiii
Contents
Section 6.
Integrated Communications Access Method (lCAM) Procedures
6.1. ICAM Operator Commands ............•...........•
6.1.1. Loading the ICAM Symbiont (Cn/Mn) .••••••••••••••••
6.1.2. Changing the ICAM Name (SET IC) •.•••••••••••.••••
6.2. Initializing and Terminating the Global User Service Task (GUST) .
6.2.1. Running the Global User Service Task Job •••••••..••••
6.2.2. ML$$GI Program Operator Messages ••••••••••••••••
6.2.3. Terminating the Global User Service Task
• • • • • • • • • • • ••
6.3. ICAM Operator Messages ....•••...................
6.3.1. Standard Unsolicited Messages ••••••••••••••••••.
6.3.2. Public Data Network (PDN) Unsolicited Messages •••••••••
How to Enter Packet-Switched PDN Unsolicited Messages
How to Enter Circuit-Switched PDN Unsolicited Messages ••••
6.3.3. Remote Batch Processing (RBP) Unsolicited Messages •••••
6.4. Downline loading a Telcon File ......................
6.4.1. Loading Telcon File to Front-End Processor (DCP) •••••.••
6.4.2. Loading Telcon File to Remote Concentrator (DCP) •••••••
Section 7.
(
System Utility Services
7.1. System Utility Commands and Messages (SUfTU)
. . . . . . . . ..
7.2. Card Functions ............................•....
7.2.1. Reproducing Cards Punched in Hollerith Code (CC) ••••••.•
7.2.2. Reproducing Cards Containing Binary Data (CCB) •••••.•••
7.2.3. Reproducing and Resequencing Source Programs (CCS) •••••
7.2.4. Writing Cards to Tape in Unblocked Format (Cn ••••••••••
7.2.5. Writing Cards to Tape in Blocked Format (CTR) •••••••.••
7.2.6. Listing Cards (CP) •••••••••••••••••••••••••••
7.2.7. Listing Cards Containing Compressed Mode (CH) ••••..••
7.2.8. Punching Cards from the System Console (JCP) •••••.••.
7.3. Tape Functions .•..................•...........
7.3.1. Tape Addressing •••••.••••••••••••••.••.•••
7.3.2. Tape Error Processing ••••••••••••••••••••••••
7.3.3. Tape Operating Instructions •••••••.•••••••••••••
Copying a Tape to Another Tape (TTI ••••••••••••••••
Printing a Tape in Character or Hexadecimal Format (TH) ••••
Printing a Tape in Character or Hexadecimal Deblocked Format
(THR)
• • • • • • • • • . • • • • • • • • • • • • • • • • • • • . • ••
Printing a Tape Containing Only Standard Characters (TP) ••••
Printing a Tape in Character and Deblocked Format (TPR)
Locating a Specific Record (TRS) ••••••••••••••••.•
Punching Cards from a Tape (TC) ••••••••••••••••••
Prepping a Tape (INTI ••••••••••••••.••••••••••
Forward Space to a Specific File (FSF) ••.•••••••••••.
Backspace to a Specific File (BSF) •.•••••••••••••••
Forward Space to a Specific Record (FSR)
• • • . • • • • • • ••
xiv
6-1
6-1
6-2
6-3
6-3
6-3
6-5
6-6
6-6
6-9
6-9
6-10
6-12
6-13
6-13
6-14
7-3
7-6
7-7
7-7
7-7
7-8
7-9
7-10
7-10
7-10
7-10
7-11
7-11
7-12
7-13
7-15
7-16
7-16
7-16
7-17
7-19
7-20
7-21
7-22
7-22
7004 5208-000
(
Contents
Backspace to a Specific Record (BSR) ••••••••••••••
Write Tape Marks (WTM)
•••••. •.•••••. . •••••••
Rewind Tape (REWl •••••••••••••••.••.•••••.•
Rewind and Unload Tape (RUN) •••••.•••••••..••••
Erase Tape Record Gap (ERG) •••...•••••••••••••
7.4. Disk and Format label Diskette Functions ........•..••.
7.4.1. Operating Considerations •••••.••••••••.•••••••
7.4.2. Disk and Format Label Diskette Operating Instructions
7.4.3. Printing a Disk or Format Label Diskette in Unblocked
Format (DD) •••••••••••••••.••••••••••••••••
7.4.4. Printing a Disk or Format Label Diskette in Deblocked
Format (DDR) ••••••••••••••••••••••••.••.•••
7.4.5. Printing the Disk or Format Label Diskette Volume Table of
Contents (VTP) ••••••••••••••••••••••••••••••
Disk and Format Label Diskette VTP Listing Summary
7.4.6. Printing a Short Format VTOC for a Disk or Format Label
Diskette (SVT)
•••.••••••••••••.••••.••..••••
SVT Listing Summary for Disk and Format Label Diskette
7.4.7. Displaying the Available Disk and Format Label Diskette
Extents (AVXJ •••••••••••••••••••••••••••••••
AVX Listing Summary ••.•••••• • • • • • • • • • • • • • • •
7.5. Data Set label Diskette Functions .....•.•...•.••....
7.5.1. Data Set Label Diskette Operating Instructions •••••••••
7.5.2. Printing the Data Set Label Diskette in Unblocked Format •••
Single-Sided Diskette in Unblocked Format (DD) •••••••••
Double-Sided Diskette in Unblocked Format (DD)
.•••••• •
7.5.3. Printing the Data Set Label Diskette in Deblocked Format •• ,
Single-Sided Diskette in Deblocked Format (DDR) ••••••••
Double-Sided Diskette in Deblocked Format (DDR)
.••••••
7.5.4. Printing the Data Set Label Diskette Volume Table of
Contents (VTOC) •••••••••••••••••••••••••••••
Single-Sided Diskette VTOC (DO) •.••••••••••.•••••
Double-Sided Diskette VTOC (DD)
•.••. •••••••. ••••
Section 8.
7·25
7·27
7·28
7·29
7-32
7·32
7·33
7·34
7·34
7·34
7·35
7·35
7·35
7·36
7·36
7·37
7·37
7·37
7·38
Disk Cache Facility (DCF)
8.1. Initializing Disk Cache (CM) •.•••.....•••....•......
8.1.1. Specifying Cache Buffer Size (CM SIZ) •••••••••••••••
8.1.2. Specifying Cache Buffer Segment Size (CM SEG)
••.•••••
8.2. Resegmenting the Existing Cache Buffer (CM RESEG) ••.....
8.3. Selective Caching •.••...•...••....•..••.•..•..•
8.3.1. Removing Drives from DCF (CM REM) •••••••••••••.•
8.3.2. Removing Files from DCF •••••..••••.••••..•••••
8.4. Activating Drives to DCF (CM ACT) •..•..••.••...••....
8.5. Removing DCF from the System (CM SHUT) ...•.......•..
7004 5208-000
7·22
7·23
7·23
7·23
7·24
7·24
7-24
7·24
8-2
8-2
8-3
8-4
8-4
8-4
8-5
8-5
8-5
xv
Contents
8.6. Displaying DCF Statistics (CM STA, STARES)
..••.•..•.....
8.6.1. Displaying and Turning Off Timer Statistics
(CM STATIME, STARESTIME, TIMER) •.••••••••••.••••••
8.6.2. Displaying Statistics on a Specified Drive
(CM STADISK, STARESDISK) ••••••••••••••••••••••••
8.6.3. Interpreting DCF Statistics •••••••••••••••••••••••
8-5
8-6
8-6
8-7
8.7. DCF Supportive Information ...•.••••.•..••••.••..... 8-8
8.7.1. Cache Modules ••••.•••••••••••••••••••••••• 8-8
8.7.2. Main Storage Layout with Disk Cache •••••••••••••••• 8-8
8.7.3. Cached I/O Commands ••••••••••••.•••••••••• 8-10
8.7.4. I/Os Not Cached
••••.•••••••••••••••••••••• 8-10
8.7.5. Monitoring DCF Effectiveness •••••••••••.•••••••• 8-11
8-11
8.8. Fine-Tuning DCF •..•.••.•••.•...•....•.•....•..
8.8.1. Specifying Segment Size
•••••••••.••.••.•••••• 8-11
8.8.2. Optimizing Disk Cache Performance •••.•••••.••••.• 8-13
Section 9.
(
ONUERL Program
9-1
9-2
9-4
9.2. ONUERL Program Options .....••....•...•..•....•.. 9-5
9.3. SDF$DSP System Program ...••.•.......••.•.....•. 9-9
9.4. ONUERL Console Messages ...•.••.•.••..••.••.....
9-10
9.5. ONUERL Reports •••....••.•.•••...•.•.•.••...••
9-12
9.6. Error Log Analysis (ONELAN Program) •..•.•..•.••...•.
9-28
9.6.1. Standard Mode Procedure •••••••••••••••••••••. 9-28
9.6.2. Tutorial Mode Procedure .•••••••••••••••••••••• 9-31
ONELAN Messages ••••••••••••••••••••••••.• 9-33
9.7. Sending Error Data to Unisys Support Center
•..•..•.•...
9-40
9.1. Executing ONUERL
••... • . • • . . • . . . • . . • . . . . • . . • . •.
9.1.1. Manual Program Execution .••••••••••••.••••.••••
9.1.2. Automatic Program Execution •••••••••••••••..•••.
Section 10.
Error Data Handling
10.1.1. How to Contact the Support Center
••..•.••••.••••
10.1.2. What to Do before Calling the Support Center
••••.••••
10.1.3. When You Call •••••••••••••••.••.••••.••••
10.2. The User Communication Form •..•.•..•.•.•.•...•..
10-1
10-1
10-1
10-2
10-3
10.3. Sending Error Log Data .....•..•.•.•..•.•....••..
104
10.1. Contacting the Unisys Support Center
Appendix A.
.•......•.......
Supervisor Modification Procedure
Index
User Reply Form
xvi
7004 5208-000
(
Figures
(
1-1.
1-2.
1-3.
1-4.
1-5.
1-6.
1-7.
Minimum System 80 Configuration
•••••••••• • • • • . • . • • • . • • • • • • • • • • • •
Maximum System 80 Configuration •••••••••••••••••••••••••••••••.•
OS/3 Components •••••••••.••••••.•••.••••.•••••••••.•••••••
Model 8 Console Keyboard ••.••••••••••••..•••••.•••••.••••••••
Model 8 System Control Panel ••••••••••••••••••••.••••••••••••••
Sample Console Screen ••.••••.••.••••••••.••.••••.••.••.•••.•
Example of a Pul~Down Menu Window
.•••••.•.• • • . • • • • • • • • • • . • . • • • •
1-1
1-2
1-9
1-15
1-16
1-18
1-19
4-1. Typical Messages •••••• • • • • • • . • • • • • • • . . • • • . • • • • • • • • • . • • • • • • •
4-2. vroc Verification/Correction Procedure ••••..•..•••••••••••••.••••••
4-9
4-80
8-1. DCF Statistics Displayed at the System Console
•••••••••••••.•••••••.•••
8-2. Effect of Segment Size on Run Time •••••••••••.••.•••••••••••••••.
8-7
8-13
9-1. Sample ONUERL Program Execution .•••••.••.•••..•••••••••••••••••
9-2. Sample Error Log Report Format ••.••••••••••.••.•••..••.•••••••.
9-3. Sample ONELAN Dialog, Standard Mode •.••..•••••...•••••••.••••.•.
9-4. Sample ONELAN Dialog, Tutorial Mode ••••••••.••••••.••••••••...•••
9-5. Device Error Log Analysis for 3561 Workstation
.••. . • • • • • . • • • • • . • • . • • • •
9-6. Device Error Log Analysis for 8420 Diskette •••.••••••.•.•••••••••.••••
9-7. Disk Subsystem Error Log Analysis •••••••••••••••••.••••••••••••••
9-15
9-30
9-32
9-35
9-36
9-37
9-8
(
7004 5208-000
xvii
(
Tables
1-1. Console Control Selections •••••••••••••••.•••••.•.•••.•••••••••
1-2. Console Screen Function Key Assignments
••••••••••. ••••••••••••••••
1-15
1-20
6-1. Standard ICAM Unsolicited Messages ••••••••••••••••••••••••••••••••
6-7
7-1.
7-2.
7-3.
7-4.
7-5.
7-6.
7-7.
System Utility Functions •.•••••.••••••••••.•••.•••••••••••••••••
Assembler Format ••••.•••••••••••••••••••.•••••••.•••.••••••
COBOL Format •.••••.•••..•.••..•••••.•••.••.••••••••••••••
RPG Format .••••••...•..••••••••.••••••••.••••••.•••.•••..
Summary of Disk;Diskette VTP Information
•••••••••••• • • • • • • • . • • • • • • .
Summary of SVT Information for Disk and Format Label Diskette
•.••••••.••• • •
Summary of AVX Information for Disk and Format Label Diskette
•••••••••.•••.
7-2
7-7
7-7
7-8
7-30
7-33
7-34
9-1. ONUERL Program Options •••••••.••••••••.••••.••••••.•••••••••
9-2. ONUERL Console Messages •••••••••••.•••••••..•••••••••••.•••
9-3. CHARACTERISTICS Field Displayed in ONUERL Report •••••••.••••••.••.•••
9-4. FLAGS Field Displayed in ONUERL Report •••••••••••. • • • • • • • • • • • • . • • •
9-5. MSE Display of ONUERL Report ••.•••.•.••••••••.••.••••••••.••••
9-6. CPU Retry Stack Log-Out Display of ONUERL Report •••••.•••••••••••.•.••
9-7. Exigent Machine Check Displays •••.•••••••••••..••••••••••.•••.•.
9-5
9-10
9-25
9-25
9-26
9-27
9-27
A-1. How to Modify List of Resident Shared Code Modules
7004 5208-000
A-2
xix
(
(
Section 1
System Definition
System 80 models 8-20 are interactive data processing systems which operate on
Operating System/3 (OS/3), the multiprogramming software system. The versatility of
System 80 models 8-20 permit you an almost unlimited variety of system
configurations from which you can tailor one to your particular needs. The system is
configured from the basic processor complex to maximum expansion with one
expansion cabinet.
1.1. System Configuration
Diagrams showing minimum and maximum configurations of the System 80 models
8-20 are presented in Figures 1-1 and 1-2, respectively.
SYSTEM 80 MODELS 8-20 PROCESSOR COMPLEX
•
•
•
•
•
•
INPUT/OUTPUT MICROPROCESSOR
MAIN STORAGE
MODEL 8 - 1MB
MODEL 10 - 2MB
MODELS 15 & 20 - 4MB
gJ
~
I
~':."':.,,-....:::..":.::":..":.:.--~
INTEGRATED
DISK
CONTROL
UNIT
(IDCU)
I
18417/19/70
DISK
SUBSYSTEM
OR
28416/18
DISK
SUBSYSTEMS
REQUIRES
NONINTEGRATED
OR
CONTROL
-I
I
28430/33
DISK
SUBSYSTEMS
OR
28494
DISK
SUBSYSTEMS
GJ
DISKETTE
CONTROLLER
UNIT
•
•
32 GENERAL REGISTERS
64 RELOCATION REGISTERS
4 FLOATING POINT REGISTERS
175 INSTRUCTIONS
STORAGE PROTECTION
ERROR CORRECTION
h'~=-ff
f
J;JIJ
f~f
-----
PAPER
PERIPHERAL
CONTROLLER
~":."':.~....~':,.--:~--
BYTE
ADAPTER
WORKSTATION
CONTROLLER
(PPC)
I
CONSOLE
I
I
8420
OR
8422
DISKETTE
SUBSYSTEM
0776/0789
LINE
PRINTER
I
0770/0776
LINE PRINTER
OR
9246-14B
LINE PRINTER
I
3569 OR 3561
WORKSTATION
Figure 1·1. Minimum System 80 Configuration
7004 5208-000
1-1
......
N
i
3
c
~
:J
8!
o
:J
MAtH STORAGE EXPANSION
SYSTEM 80 MODELS 8·20 PROCESSOR COMPLEX
ALLOWABlE
10 K WORDS CONTROl STORAGe
2 INPUT1000PUT MICROPROCESSORS
32 GENERAL REGISTERS
64 RElOCA noN REGlSTERS
~
INTEGRATED
DISK
CONTROl
UNIT
t1OCU!
I
I
-.....-
REOUlAfS
NONINTEGRATED
DISK
D~
124MAX.I·
"'94
SUBSYSTEMS
on
~
10
15
20
w
OISKEITE
CONTROllER
-r
I
8430/8433/
•
175 INSTRUCTIONS
ERROR COMfC1lQN
STORAGe PROTECTION
ADAPTf:R
T~
8470,8418.
OR 8418
SUBSYSTEMS
SINGLE-lINE
COMMUNICATIONS
MOOEl
4 FLOATING POWT REGISTERS
I
COMMUNICA T10NS DeVICeS fOR
liNES 1 THRU 28 CAN INClUDE:
CONSOlE
•
llNISCOPe 200 Display
T"""'"
•
UTS 400 Universal TenriNII
•
UTS<4000tJriveruI
TfIffJIiNISysttm
Syllom
SVT 1120/1123/1124
PC
UNIX Sytl.."
MAPPER·5
OCP
HoSl-to-Hoa1 PON
~
l;lJ
~
PAPER
P£RtPHfRAl
BYTE
CONTROU£R
ADAPTER
WORKSTATION
CONTROllER
(I'PC)
I
I
I
84'0
OR
8422
OISKEnE
0776/0783 AOO:0608 CARD
0710/0776
PAMER
PUNC1l
_TER
OIl
ANO
0716
0719
SUBSYSnMS
(4 MAX.)
CARD
CARD
READER
READER
00
0198 PNNTER
(4 MAX.)
1
I
0
D
OCP
WTEGRATED
UNlSERVO 10
RE"",",S
TAPE
TAPE
NONINTEGRATED
SELECTOR
CONTlIOllER
AnACHMENT
CONTROl
CHANNEL
SYSTEM 80
WORKSTATIONS
(MOORS 1 AND 2
AND SVT 11221
1120 MAX.)
079110797/0798
CHARACTER
PR1NTER
. 3389
MAGf,Enc
STRIPE READeR
OR
0426
..".
PAMER
OISKEnE
9248·148
lINE
PfI1NTER
• Up toBof the 24 dish C¥'Ibe 8418 or 8-418
-....J
o
~
1.2.3,4,6.8
2.4.8
4,8,12
4.8.12,16
lNT
RP1_A
789/198
REMOTE
PRINTER
01
EXPANSfONS {MBI
Figure 1-2. Maximum System 80 Configuration
f'.)
~o
o
/"'
OCPI,
OCP40
System Definition
1.2. Central Hardware
The basic System 80 models 8-20 hardware consists ofthe processor complex, the
console, disk and diskette subsystems, and a printer subsystem. It also includes the
standard processor features and input/output controls shown in Figure 1-1. The
central hardware for a maximum system can consist of the processor complex, an I/O
expansion cabinet, and the additional integrated processor features and I/O controls
shown in Figure 1-2.
The central processor complex contains all processors, I/O channels, and integrated
peripheral system controls. The following central processor components are provided:
•
High-performance control storage
•
Expandable main storage
•
l75 basic instructions, including instructions for floating-point, decimal, and
system control
•
32 registers for program and system use, plus 4 floating-point registers and 64
relocation registers
•
System control processor
•
For model 8 systems, an input/output microprocessor (maximum of 2) supporting:
Diskette controller
Workstation controller
Paper peripheral controller
Integrated tape controller
Single-line communications adapter (SLCA)
•
For model 8 systems, a channel controller (maximum of 2) supporting:
One byte MUX channel (for console, printer, and card reader support)
Up to five integrated selector channels (for disk, printer, tape, and
distributed communications processor (DCP) support)
•
For model 10115/20 systems, a selector channel (maximum of 6) for disk, printer,
tape, and DCP support
•
For modell Oil 5/20 systems, an input/output processor (lOP) (maximum of 2)
that provides support equivalent to the IOMP on the model 8
7004 5208-000
1-3
System Definition
1.2.1. Control Storage
Control storage contains the macroinstructions that control operations of the central
processor. The CPU executes and controls instructions and processes I/O interrupts,
interval timer activities, and general interrupts.
1.2.2. Main Storage
The main storage unit stores data and commands. The minimum main storage values
are shown in Figure 1-1. The main storage can be expanded (by adding another main
storage unit). The increments vary by processor as shown in Figure 1-2.
Main storage provides error correction for single bit errors and error detection for
double bit errors. It also provides a protection scheme for data and programs using
keys. Main storage is accessed directly by the central processor (for programs), the
system control processor, the input/output microprocessor, and the channel controller.
1.2.3. System Instructions
The system instructions control the operation of the central processor. A repertoire of
175 basic instructions, 31 of which are privileged, is provided with the system. The
privileged instructions are used for system control and input/output operations.
N onprivileged instructions are used for general control, data manipulation, decimal
operations, list processing, and floating-point operation.
1.2.4. System Registers
The system registers are provided for accumulating, addressing, and controlling
operations and data within the system. The 32 general purpose registers may be used
as accummulators in general arithmetic and logical operations. They are also used as
base address and index registers in arithmetic and logical operations and in address
generation. The 16 control registers are used to specify whether or not an operation
can be performed in the system, or they may be used to provide special information
required by a system facility. The four floating-point registers are available for
floating-point operations when the floating-point instruction feature is included in the
system. Main storage space is fully used by the system through dynamic storage
relocation and the 48 relocation registers. Automatic relocation of all programs in
main storage allows maximum loading of programs.
1-4
7004 5208-000
c
System Definition
1.2.5. System Control Processor (SCP)
The system control processor (SCP) functions independently of the central processor
to control the console, control panels, system initialization, maintenance, and
diagnostic functions, system recovery, and remote maintenance.
1.2.6. Input/Output Microprocessor (lOMP) or Input/Output Processor (lOP)
The IOMP (for model 8) or lOP (for model 10115/20) initiates, directs, and monitors
the transfer of data between main storage and some of the peripheral VO devices. The
IOMPIIOP accepts instructions from the central processor (through user and system
software), from the workstation, and from operator controls on the devices. After an
VO instruction is initiated, the data is transferred independently of other processor
functions; i.e., the VO and the processor operate concurrently.
The IOMPIIOP is used to support low-speed peripheral subsystems, such as those
attached to a diskette controller, workstation controller, paper peripheral controller,
or integrated magnetic tape controller. Up to eight controllers and a UNISERVO® 10
tape subsystem (low profile) can be attached to an IOMPIIOP through the shared
direct memory access interface (SDMA). Data transfer rate with SDMA is 200K
bytes/second.
Each IOMPIIOP can also support a single-line communications adapter (SLCA) with
up to 14 communications lines. The multiple line communications multiplexer
(MLCM) is the interface between the SLCA and the IOMPIIOP. MLCM microcode and
IOMPIIOP hardware control buffer pool management, data chaining, and command
chaining. The MLCM transfers data at the rate of 128K bytes/second.
The IOMP or lOP supports:
(
•
Diskette controller
•
Workstation controller
•
Paper peripheral controller
•
Integrated tape controller
•
Single-line communications adapter
The following subsections describe these hardware components.
UNISERVO is a registered trademark of Unisys Corporation.
7004 5208-000
1·5
System Definition
Diskette Controller
The 8420 or 8422 diskette subsystem is attached to the system through the diskette
controller. The controller is capable of controlling up to four diskette drives - either
two autoload drives and two manual drives or four manual drives. Your system must
include at least one. The autoload type provides an automatic loading capacity of up to
20 standard diskettes. The controller uses microprocessors and interfaces the
IOMPIIOP through shared direct memory access.
Workstation Controller
A workstation controller attaches up to eight workstations to the system. Additional
workstation controllers can be attached to expand the number of workstations in the
system to a maximum of120.
The workstation controller accommodates three types of workstations on the System
80 models 8-20 - the model 1 , the model 2, and the SVT 1122. All types may be located
up to 5000 cable feet (1500 meters) from the processor cabinet. The controller uses
dedicated buffers to allow data transfers at a rate ofl9,200 bits/second. The model 2
workstation can directly connect to an 0791, 0797, 0798, or 0425 printer.
Paper Peripheral Controller
The paper peripheral controller attaches various peripheral printers and card
processors to the system through the IOMPIIOP. The controller can support one or two
printers and two card processors for a maximum offour devices operating
concurrently. The controller accommodates the following types of devices: 0776, 0789,
0798 printers, 0608 card punch, and an 0719 card reader. The total print capacity of
the paper peripheral controller is 1500 lines per minute. The System 80 models 8-20
support up to 12 paper peripheral controllers.
(
Integrated Tape Controller
The integrated tape controller connects up to four streaming tape subsystems or eight
UNISERVO 22 tape drives to the system. The total number of drives the integrated
controller can support is eight and only one controller is allowed per system.
1-6
7004 5208-000
System Definition
Single-Line Communications Adapter (SLCA)
The SLCA provides the system with communications capabilities. Models 8-20 can
support up to 14 SLCAs. You can have 14 low- or medium-speed half-duplex, 7 highspeed full-duplex, or 12 high-speed half-duplex SLCAs. Since your system can include
two laMPs or lOPs, each supporting 14 SLCAs, the total number of communications
lines your system can have is 28. Each line can accept devices operating at speeds of
up to 56 kilobitslsecond.
SLCAs connect remotely located workstations, terminals, and all other
communications devices to the system. They perform special character recognition,
integrity checks, data transfer control between main storage and devices, and other
required control functions.
1.2.7. Channel Controller (ModelS Only)
In model 8 systems, the channel controller initiates, directs, and monitors the transfer
of data between main storage and those devices not connected via the laMP. The
system can include two channel controllers. The first channel controller supports the
byte MUX channel and three integrated selector channels. A second channel controller
can support up to two integrated selector channels.
Byte MUX Channel
The byte MUX channel connects the console to the system. The console includes two
diskette drives for system initialization and maintenance. Via the byte adapter, the
byte MUX channel also connects the 0770/0776 line printer and the 0716 card reader.
The system can support only one byt~ MUX channel. In tum, the byte MUX channel
can connect up to eight devices at a maximum data rate of 70 KB/second.
Integrated Selector Channel
An integrated selector channel controls high-speed 110 devices, such as disks,
magnetic tapes, high-speed buffered printers, and distributed communications
processors. It operates in burst mode with the subsystem for data transfers. There is a
maximum of five integrated selector channels per model 8 system.
The 8416, 8417, 8418, 8419, and 8470 disk subsystems are connected to the integrated
selector channel via an integrated disk control unit (lDCU). Each selector channel can
support no more than three IDCU s (a maximum of six IDCUs per system) and 24
disks.
7004 5208-000
1-7
System Definition
The 8430, 8433, and 8494 disk subsystems are connected to the integrated selector
channel via nonintegrated (freestanding) disk control units. The system supports a
maximum of 16 subsystems.
The integrated selector channel also connects, via nonintegrated controllers,
UNISERVO 10,12,14,16,20,22,24,26, and 28 tape units; 3200 series tape units;
0770 and 0776 printers; 9246-14B and 9246-25B printers; and DCP 15, 30, 40, and 50
units. The system supports a maximum of eight subsystems in any combination.
1.2.8. Selector Channel (Models 10/15/20 Only)
In model 1 0/15/20 systems, selector channels initiate, direct, and monitor the transfer
of data between main storage and high-speed printer, disk, tape, and the DCP. A
minimum system requires one selector channel; a maximum of six selector channels
may be configured.
(
Each model 10/15/20 selector channel can be connected to I/O devices as defined for
the model 8 integrated selector channel.
1.3. Input/Output Subsystems
The I/O peripheral subsystems available for use with System 80 include the console,
disk and diskette subsystems, workstations, magnetic tape subsystems, printer
subsystems, card reader/punch subsystems, and remote communications subsystems.
(
(
1-8
7004 5208-000
System Definition
1.4. OS/3 Operating System
OS/3 is composed of a group of 11 major programs - supervisor, job control, data
management, integrated communications access method (leAM), utility programs,
information management system (IMS), language processors, data base management
system (DMS), application programs, diagnostic programs, and interactive services.
(Figure 1-3).
OS/3
SYSTEM
(
r-
SUPERVISOR
f--
JOB CONTROL
-
DATA
MANAGEMENT
-
'-
INTEGRATED
COMMUN ICATIONS
ACCESS METHOD
(lCAM)
UTILITY
PROGRAMS
-
INFORMATION
MANAGEMENT
SYSTEM
(lMS)
-
DATA BASE
MANAGEMENT
SYSTEM
(OMS)
-
LANGUAGE
PROCESSORS
"-
APPLICATION
PROGRAMS
-
DIAGNOSTIC
PROGRAMS
'-
INTERACTIVE
SERVICES
Figure 1·3. OSj3 Components
(
7004 5208-000
1·9
System Definition
1.4.1. Supervisor
The supervisor is a resident program of the operating system; it interfaces with the
user programs to provide the necessary control for the best use of the system
hardware and software. It controls the physical I/O operations, system resource
allocation on a dynamic basis, task switching to achieve multitasking, hardware
interrupt servicing, communications with the system operator, and interface to user
programs with the system hardware. To accomplish this, the supervisor is composed
of these program elements:
1-10
•
Interrupt control
•
Priority control
•
Transient control
•
Physical I/O controls
•
Resource allocation
•
Task control
•
Interrupt timer and day clock services
•
Program management
•
Console workstation management
•
File services
•
Program error handling
•
Cooperative/symbiont operations
•
Physical inputJoutput control system (PlOeS)
•
Debugging aids
(
70045208-000
System Definition
1.4.2. Job Control
Job control is a nonresident program of the operating system responsible for
controlling the orderly initiation and termination of jobs within a multiprogrammed
environment. The job control services are performed prior to execution of the initial
job step of a job, during the transition between job steps, and at the conclusion of a
job. Some of the services of job control are:
•
Volume label and file label storage
•
Job control stream file maintenance
•
Job scheduling by priority
•
Main storage allocation and reallocation
•
Peripheral device assignment
•
Program restart
The functions of job control are implemented interactively or in batch mode by the
programmer through the job control language. These sequenced control statements
form the control stream that defines facility requirements of ajob and directs the
execution of the job. The job control statements, through the job control stream,
function as an interface between the programmer and OS/3.
1.4.3. Data Management
Data management provides a consolidated data interface between the hardwareoriented I/O facility (card, tape, printer, and MlRAM disk files) and the user program.
The data management facilities consist oflogical input/output control stream (laCS)
modules, transient routines, declarative macroinstructions, and imperative
macroinstructions.
1.4.4. Integrated Communications Access Method
The integrated communications access method (I CAM) may be used to control local
workstations directly connected to the processor and other lCAM-supported terminals
connected to the processor by means of communications lines. lCAM is loaded as a
symbiont and acts as an extension to the System 80 supervisor.
7004 5208-000
1-11
System Definition
Application programs communicate with ICAM by means of the following interfaces
using imperative and declarative macroinstructions:
•
CPl - communications physical interface
•
DDl - direct data interface
•
STDMCP - standard GETIPUT interface
1.4.5. Utility Programs
The OS/3 utility programs make available to the system the means for sorting data
into a specified order, merging data to facilitate processing, maintaining files on
magnetic disk storage, linking output modules oflanguage processors into executable
programs, and copying input cards, magnetic tapes, disk or diskette files to any other
card, magnetic tape, disk or diskette, or printer device.
The major utility programs include:
•
Data utilities
•
Linkage editor
•
System librarian
•
Sort/merge
•
Disk, diskette, and tape prep routines
•
System utility
(
1.4.6. Information Management System
(
The information management system (lMS) is a transaction-oriented application
package that facilitates access to information stored in data files. IMS provides a
terminal-oriented data retrieval and update capability for managerial and clerical
personnel and, thereby, relieves them of needing to learn complex methods employed
by programming personnel.
\
\
1-12
70045208-000
System Definition
1.4.1. Language Processors
Eight language processors are available with OS/3: basic assembly language (BAL),
COBOL, FORTRAN IV, FORTRAN 77, Pascal, report program generator II (RPG II),
BASIC, and ESCORT. Language processor input can be on punched cards, disk or
diskette files, or magnetic tape; output can be recorded on disk or diskette files or on
magnetic tape. All processor output is in a common system output format.
1.4.8. Diagnostic Programs
The diagnostic programs provided with OS/3 are hardware verification and
maintenance routines that can be executed concurrently with user programs. These
programs are intended to be run as confidence tests by the system operator and as
diagnostic and maintenance tests by the customer engineer.
1.4.9. Data Base Management System
The data base management system (DMS) is a collection of system programs that
support integrated data bases. These programs provide for the description,
initialization, creation, accessing, maintenance, backup, and recovery of data base.
The languages used in the description and manipulation ofDMS data bases are
derived from the CODASYL data base specifications. A data base may be accessed by
batch application programs and communications application programs.
1.4.10. Application Programs
Application programs are those specialized programs that are available to a user but
not provided as part of the standard software package. These programs are directed
towards handling problems distinctive to a particular user and include program
evaluation and review techniques/critical path method analysis (PERT/CPM) and
linear programming (LP).
1.4.11. Interactive Services
Interactive services provides an extensive interactive command set that is available to
a user as part of the standard software package. These commands enable you to
control the interactive system environment, including all jobs within the system, all
workstation users (local locations), and all terminal users (local and remote locations).
7004 5208-000
1-13
System Definition
Interactive services also perform a variety of functions including program creation
and file/data manipulation. The interactive facilities used to perform these functions
are:
•
Screen format services
•
Interactive data utilities
•
General editor
•
Interactive job stream preparation
•
Menu services
•
Interactive dump/restore facility
•
ESCORT
•
BASIC
(
1.5. Console and Control Panel
As the system operator, most ofthe functions and procedures you perform are
accomplished at the system console and system control panel. Following is a brief
general description of these items. Note that two different system console versions
are used; one for the model 8 and another for models 10, 15, and 20. Refer to the
Processor and Central Peripherals Operating Guide (UP-9608) for detailed
information on switch and indicator functions for both system console versions.
1.5.1. System Console
The console consists of a display monitor and a keyboard. The model 8 United States
national keyboard is shown in Figure 1-4. Seven additional national keyboard styles
are available.
The keyboard is used to communicate with the system via input commands and to
select display frames. When you press the ESC key, a command input mode is
initiated. You can enter commands by pressing an appropriate key while pressing and
holding the ESC key. On the model 8 system, the LOCKIUNLOCK switch must be set
to the UNLOCK position to allow command inputs. Table 1-1 summarizes console
operations that can be performed with the ESC key. Refer to the Processor and
Central Peripherals Operating Guide (UP-9608) for more detailed information.
1-14
7004 5208-000
(
System Definition
PoWER
o
Figure 1·4. ModelS Console Keyboard
Table 1·1. Console Control Selections
Key Input
Function
ESC and R
Switches processor from stop state to operational state so that software instructions
can be executed.
ESC and S
Switches processor from operational state to stop state.
ESC and C
Puts console in system control mode and displays the configuration control frame. This
frame is used to control auto IPL, autorecovery, and remote console modes. It also
displays processor configuration data and the state of system control panel and console
indicators.
ESC and M
Puts console in system control mode and displays the manual frame. This frame is used
to perform manuallPL and IMPL functions, and to debug programs and operations.
ESC and A
Puts console in system control mode and displays the alter/display frame. This frame
allows you to display and alter various registers, main storage locations, and the PSW.
ESC and P
Puts console in maintenance console mode and displays the service frame. This frame
provides numerous error logging and maintenance-related functions.
ESC and T
Puts console in remote maintenance mode and displays the teleprocessing frame.
CNSL
Puts console in operator console mode and displays the console frame. This frame is
used to exchange information between the operator and the operating system.
7004 5208-000
1-15
System Definition
1.5.2. System Control Panel
The system control panel contains controls and indicators used for operator
maintenance during system operation. On the model 8, this panel is located on the
door of the console table. On models 10, 15, and 20, it is physically attached to the
keyboard.
Figure 1-5 shows the model 8 system control panel. The model 10115/20 system control
panel is of a different design but provides similar functionality. Brief descriptions of
the panel indicators and switches follow (refer to the Processor and Central
Peripherals Operating Guide (UP-9608) for more detailed information on this panel).
PWR
TH
c:::J
c:::J
RUN
WAIT
c:::J
c:::J
SEQl
SEQ2
SEQ3
P-SEQ
c:::J
c:::J
c:::J
c:::J
STOP
C-STOP
TEST
CD
POWER
c:::J
c:::J
c:::J
c:::J
c:::J
CHECK
RESET
IMPL
IPL
~ ~ ~
A19169
Figure 1-5. Model 8 System Control Panel
Indicator Lights
•
PWR
Indicates a fault in the dc power supply to the system. This light stays lit until
the fault is corrected. When this light goes on, the system alarm buzzer also
sounds.
•
TH
Indicates that the speed of the cooling fan in the system has dropped below a
safe level. This light stays lit until the fan is fixed. When this light goes on, the
system alarm buzzer also sounds.
1-16
7004 5208-000
System Definition
•
SEQ1, SEQ2, SEQ3
Indicates that power has been applied to your system or that the initial
microprogram load (IMPL) has begun. Once IMPL and initial program load (IPL)
complete, these lights go off. Anytime an error occurs within the system control
panel itself during IMPL, IPL, or system operation, these lights go on.
•
P-SEQ
Indicates that you are performing the power-on procedure. This light goes on as
soon as you turn on the POWER switch behind the control panel door. It turns off
when the P-OK signal is displayed on your console.
•
RUN
Indicates that your system is running jobs.
•
WAlT
Indicates that your system is in a WAIT state.
•
STOP
Indicates that your system is in a STOP state.
•
C-STOP
Indicates that your system is in a CHECK STOP state. This light stays lit until
you perform system reset. When this light goes on, the system alarm buzzer also
sounds.
•
TEST
Indicates that you are operating the system under other than normal conditions,
such as processor STEP mode. This light stays lit until the abnormal condition is
cleared.
•
CD
Indicates a remote console is connected. Your system receives the carry detect
(CD) signal from the modem and turns this light on.
•
POWER
Indicates that your system is receiving power.
7004 5208-000
1-17
System Definition
Switches
•
CHECK RESET
Stops the system alarm buzzer.
•
IMPL
Starts the service processor (SVP) and console initial microprogram load (IMPL)
procedure. Note that additional IMPL functions must be performed using the
manual frame display.
•
IPL
Specifies manual (MNL) or automatic (AUTO) initial program load.
(
1.5.3. System Console Screen
The console screen (Figure 1-6) is the normal operating screen from which you
monitor and control system activities.
OS/3 Console
14.n.n
SUP20/C1
Friday, April 19, 1991
14:20
Spl=nn%
~j1:~EXfitjmmi~Z:MQIUitQr,i*NOji'ii,j ~3i~se!ti!lp ,'jj"'F4;';jQQ$'.:iii~5';Mtximi'ilR~~oil1$pl
(Monitor Display Area)
RV LISTRES
JC01 JOB LISTRES EXECUTING JOB STEP LIBS0000 #001 14:19:29
CA LISTRES,N
JC03 JOB LISTRES TERMINATED ABNORMALLY, ERR 049 14:19:38
PR(2E0)
MI DS,2E0
DVC UP AVL SHR REA - - - - - - USERS - . - - - 2E0 Y Y
N
MI SQ
NO SYMBIONTS QUEUED
PR(2E0)
01 SPL
0101 HOLD
FILES=0002 PAGES=00009
CARDS=00000
29?DI02 SPOOL FILE DETAILS?
***Y,N,Q,H,I,S,SQ,SH,SI***
BE SPL
BE01
BE SPL,PR,JO=LISTRES
14:19
14:19
14: 19
14: 19
14:20
14:20
14:20
14:20
14:20
14:20
14:20
LISTRES
LI STRES
MIX
MIX
MIX
>i(O'o._n!iliiiitnPi!lti'iiili~nliij~iiii
CONSOLE
Figure 1-6. Sample Console Screen
1-18
7004 5208-000
System Definition
The console screen is displayed at the completion of a successful system initialization
sequence. The screen is divided from top to bottom into the following areas:
•
Console header line (line 1, top of screen)
•
Menu bar (line 2)
•
Monitor display area (lines 3.... n)
•
Message display area (end of monitor area to line 23)
•
Command input line (line 24)
•
Status line (line 25)
The header line identifies the display as the console screen. It also identifies the
system software level, supervisor name, ICAM network name (when ICAM is loaded),
the day of the week, the current date and time, and the percentage of spooling being
used. The time display is updated once every minute.
The menu bar lists the function keys (F1 through F6) that you use to select and
display the pull-down menus associated with common command execution and system
activity monitor control. Pressing one of the function keys shown in the menu bar
causes the menu associated with that function key to appear directly below it on the
screen (if applicable). This display area is called a pull-down menu window. (See the
example shown in Figure 1-7.)
OS/3 Console 14.n.n
F1:Exit F2:Monitor=YES
RV LISTRES
JC01 JOB LISTRES EX
CA LISTRES,N
JC03 JOB LISTRES TE
PR(2E0)
MI DS,2E0
DVC UP AVL SHR REA
2E0 Y Y
N
MI SQ
NO SYMBIONTS QUEUED
PR(2E0)
01 SPL
0101 HOLD
FILES=0002
29?D102 SPOOL FILE DETAILS?
BE SPL
BE01
BE SPL,PR,JO=LISTRES
14: 19:38
14: 19
LISTRES
14: 19
14:20
14:20
14:20
14:20
14:20
14:20
14:20
LISTRES
MIX
MIX
MIX
PAGES=00009
CARDS=00000
***Y,N,Q,H,i,S,SQ,SH,SI***
>iC!:1Qnndi:!itn~:ti:lilC,tnej~'i.i
Figure 1-7. Example of a Pull-Down Menu Window
70045208-000
1-19
System Definition
The pull-down menus list the function keys associated with each operation or
command that can be issued from that menu. To initiate an operation or to issue a
command, press the appropriate function key displayed in the menu. The pull-down
menu usually disappears after you complete your selection. There are a few choices
that display a second pull-down menu. In all cases, the F1 key exits the current menu.
The F1 function key also toggles the menu bar display off and on whenever pull-down
menus are not being displayed.
User-defined function key operations are not recognized by the system when they
conflict with the menu bar definitions. When such conditions exist, you should exit the
menu bar. The system will then acknowledge all your function key definitions with
the exception ofthe F1 key, which remains the same. The functions you can perform
from the menu bar and their associated pull-down menus are listed in Table 1-2. The
function key values shown in the first column of Table 1-2 represent the default value
assigned to each key.
(
Table 1-2. Console Screen Function Key Assignments
Function Keys
Menu Bar / Pull'Down Menu
Description
iRi1:~Ex~it
Exi ts the current pull-down menu being di splayed. Also
turns (toggles) the menu bar display on and off when
pull-down menus are not being displayed.
iRa~MQnl:itQr$EYE$
Turns the monitor display area on (YES) and off (NO)
~~~$~tuP.
Displays the Setup pull-down menu
F1:Exit
Exits the Setup pull-down menu
F2:Job Status Monitor =YES
Turns (toggles) the Jobs monitor on (YES) and off (NO)
F3:GUST, IMS, TIP
=YES
Includes (YES) or excludes (NO) the TIP, IMS, and GUST jobs
in the Jobs monitor
F4:Use Highlights
=YES
Turns (toggles) display highlighting on (YES) and off (NO)
FS:Maximum Lines
= 7
Defines the number of jobs (lines and header) displayed in
the display area of the screen. The default value is 7 but
can be increased or decreased by preSSing the FS function
key to pull down a second menu. From the second menu, press
the function key (F2-F22) that corresponds the new value
you want specified. That actual number of lines displayed
may be dynamically reduced if additional screen lines are
required for other uses
F6:Job l s Columns
=AUTO Automatically divides the display area into the appropiate
number of columns based on the number of jobs. The display
can be manually divided into 1- to 3-columns by specifying
the values 1, 2 ,or 3
continued
1-20
7004 5208-000
(
System Definition
Table 1·2. Console Screen Function Key Assignments (cont.)
Function Keys
Menu Bar / Pull-Down Menu
Description
F7:Spool - OUt Monitor =YES
Turns (toggles) the output writer (spooling) monitor on
(YES) and off (NO)
F8:Maximum Lines
= 5
Defines the number of spooLing jobs (lines and header)
displayed in the monitor display area of the screen.
The default value is 5 but can be increased or decreased
by pressing the F8 function key to pull down a second
menu. Select the Function key (F2 - F22) in the second
menu that correspond to the new value and press that key
F9:Display EXEC Msgs
=YES
Displays (YES) or inhibits (NO) the display of EXEC (JC01)
and terminated normally (JC02) messages in the display
area of the screen
F10:Display USING Msgs = NO
Displays (YES) or inhibits (NO) the display of USING
messages in the display area of the screen
F11:Display LOGON Msgs = NO
Displays (YES) or inhibits (NO) the display of LOGON
messages in the display area of the screen
F12:Device is PC(U20)
=YES
Ignore. Not used on model 8-20 systems
F13:SAM Sunmary
=YES
Toggles the display of the SAM sunmary line on (YES) and
off (NO). When YES, sunmary line displayed if SAM active
F14:SAM I/O Info
=YES
Toggles display of SAM I/O class data display information
on (YES) and off (NO). When YES, information is displayed
if SAM active and I/O class monitoring and display enabled
Displays the Jobs command pull-down menu
F1:Exit
Exits the Jobs command pull-down menu
F2:CJ Cancel Normal-No Dump Selects the CJ command to soft cancel job; dump not taken.
Also displays second pull-down menu in which you indicate
the jobs to be canceled
(
F3:CJ Cancel Normal-
Dump Selects the CJ command to soft cancel job; dump taken.
Also displays second pull·down menu in which you indicate
the jobs to be canceled
F4:CA Cancel Hard
-No Dump Selects the CA command to hard cancel job; dump not taken.
Also displays second pull-down menu in which you indicate
the jobs to be canceled
F5:CA Cancel Hard
-
Dump Selects the CA command to hard cancel job; dump taken.
Also displays second pull-down menu in which you indicate
the jobs to be canceled
continued
7004 5208-000
1-21
System Definition
Table 1-2. Console Screen Function Key Assignments (cont)
Function Keys
Menu Bar / Pull-Down Menu
Description
F6:PA Pause
Selects the PAUSE command to suspend processing of a job.
Also displays second pull-down menu in which you indicate
the jobs to be paused
F7:GO Un-Pause
Selects the GO command to reactivate a suspended job.
Also displays second pull-down menu in which you indicate
the jobs to be reactivated
Displays the MIX command pull-down menu
F1:Exit
Exits the MIX command pull-down menu
F2:DA
Issues a MIX DA command to display specific job/symbiont
information
F3:DS
Issues a MIX OS command to display peripheral device
information
F4:EL
Issues a MIX EL command to display error log information
F5:FR
Issues a MIX FR command to display information about unused
areas (free regions) of main memory
F6:MM
Issues a MIX MM command to display information about every
main memory area
F7:SC
Issues a MIX SC command to display information about shared
code modules currently residing in main memory
F8:SI
Issues a MIX SI command to display information pertaining
to system operations
F9:SQ
Issues a MIX SQ command to display information pertaining
to outstandIng symbiont requests
F10:VI
Issues a MIX VI command to display the volume serial number
for each disk and tape volume currently mounted
Displays the Display command pull-down menu
1-22
F1:Exit
Exits the Displ pull-down menu
F2:Spool ing
Issues a 01 SPL command to display the status of completed
spool fi les
F3: Job Status
Issues a 01 JS command to display the status of jobs
in the system for processing
F4:Job Queue
Issues a 01 JBQ command to display the contents of all job
scheduling queues
F5:Active Spool
Issues a 01 SPL command to display the status of active
spool files
7004 5208-000
(
(
System Definition
The monitoring display area of the console screen starts at display line 3 and occupies
a variable amount of screen space based on the number of monitors turned on and the
number of items being tracked. The monitoring area is displayed whenever F2=YES.
The information displayed is limited to the specific monitors turned on. In the
following example, the monitoring display area uses eight lines to display status
information for SAM, jobs GUSTCI and GBILOP, and the output writer.
OS/3 Console 14.n.n
F1:Exit " F2:Monitor=YES
" gii"
. !iii
SUP20/C1
Friday, April 19, 1991
F4:Jobs F5:MIX
F6:Di
" !,'-'
'''j.
14:20 Spl=nn%
:'
I
,
I
i
RV LISTRES
JC01 JOB LISTRES
CA LISTRES,N
JC03 JOB LISTRES
,:
iii
.:
. . . . . , ...
i:ii :Hi
"" . " t," [.;,
EXECUTING JOB STEP LIBS0000 #001
14:19:29
TERMINATED ABNORMALLY, ERR 049
14:19:38
14:19
14:19 LISTRES
14:19
14:19 LISTRES
The message display area occupies the space from the bottom of the monitoring
display area to the command input line. Messages are scrolled up from the bottom of
the display. Messages contain a I3-character prefix that includes:
•
The sequential message number
•
The originating program name
•
Special characters, such as:
? for messages requiring an operator response
* for ACTION "GO" required message
You enter commands from the command input line near the bottom of the screen.
Pressing the XMIT key enters your input.
7004 5208-000
1-23
(
Section 2
System Power-On and Initialization
Procedures
Use the procedures in this section to:
(
•
Power on and initialize your system from a cold startup.
•
Automate supervisor loading.
•
Reinitialize your system after the occurrence of an unrecoverable error or when
you want to load a different supervisor.
2.1. General Information
Main power to the equipment comprising your system is controlled from circuit
breakers in the main power distribution panel for your site. The circuit breakers at
the rear of the central equipment complex cabinets and the peripheral cabinets are
usually left in the ON position when the equipment is powered off. Operating power
to these cabinets is controlled by the ON/OFF switches on the operator panels of the
equipment. There may be times, however, when site requirements or emergency
situations make it necessary to remove main power by use of the cabinet circuit
breakers. Therefore, if the power-on procedure (2.2) in this section fails to apply
power to your equipment, check to make certain that the cabinet circuit breakers and
the circuit breakers in the main power distribution panel are set ON.
(
Each time operating power is removed from and reapplied to the system, it is
necessary to perform the IMPL (initial microprogram load) and the IPL (initial
program load) procedures. The IMPL procedure loads your system's control storage
with the microcode from the diskette mounted in the diskette drive behind the
processor cabinet door. This drive is reserved for the microcode diskette; the diskette
should be mounted at all times. Once loaded, the microcode stays in control storage
until you turn the system off or you choose to re-IMPL. The IMPL process is
automatically performed whenever you power on your system.
The IPL procedure loads the resident portion of your operating system software. It
can be initiated automatically or interactively by setting the IPL switch on the system
control panel to the AUTO or MNL position. In the AUTO position, IPL automatically
follows IMPL without operator intervention. In the MNL position, the system waits
for you to manually initiate IPL after IMPL completes.
7004 5208-000
2-1
System Power-On and Initialization Procedures
Supervisor loading usually requires operator intervention. That is, you ten the system
what supervisor you want loaded. Then you define the characteristic and the load
specifications for your supervisor by answering a series of menu driven questions. The
system loads the supervisor after you input your specifications. Once your system is
up an running, you have the option of automating the supervisor load process (2.3).
You do this through interactive services. You simply log on to interactive services, call
the CFIG program, and complete the information requested by the ABP (automatic
boot procedure) menu. The CFIG program creates a file called $Y$CONFIG which
defines the load criteria and specifications for your supervisor. From this point on, the
system automatically loads your supervisor any time an automatic IPL is performed.
The automated supervisor load process is set up so that you can interrupt it and load
an alternate supervisor or opt for the default supervisor displayed in the menu
portion of the IPL screen. However, once you interrupt the automatic procedure you
must manually complete the loading process.
(
There are two day-to-day operations where system initialization is required. They are:
1.
When a nonrecoverable error occurs while the system is running (such as a
CHECK STOP, when the C-STOP indicator lights)
2.
When you want to use a different supervisor (possibly on another load device).
In both of these situations, you must initialize the system (2.4). It is not automatic.
When you perform both the IMPL and IPL procedures, you're completely
reinitializing the system. This isn't always required. In fact, more often than not, the
only procedure you need is the IPL procedure. For instance, when you need an
alternate supervisor, all you're changing is the resident portion of OS/3. Since you're
not changing the microcode, it isn't necessary to IMPL.
Similarly, many nonrecoverable errors only require you to re-IPL. You rarely have to
IMPL once the system is powered on. When a nonrecoverable error does occur, the
system displays an error message on the manual frame, or lights an indicator on the
processor cabinet. Refer to the error message in the OS /3 System Messages Reference
Manual, 70045190. This manual explains what you should do. If it tells you to reboot
the system, it still might only require the IPL procedure. However, it's a good rule of
thumb to perform both the IMPL and IPL procedures in this case. The IMPL
procedure is easy and fast and ensures that the system is properly loaded.
If an error occurs during either the IMPL or IPL procedure, always start again with
the IMPL procedure.
2-2
7004 5208-000
(
System Power-On and Initialization Procedures
2.2. System Power On and Initialization .. Cold Start
Before proceeding, decide whether you want to perform an automatic or manual IPL.
And, decide if you want to automate supervisor loading.
To perform an automatic IPL, set the IPL switch on the system control panel to the
AUTO position. At the end of IMPL, the system automatically initiates the IPL
process. The load device is the one defined in the configuration frame.
To perform a manual IPL, set the IPL switch to the MNL position. At the end of
IMPL, the system displays the configuration frame allowing you to define an
alternate load device.
To automate supervisor loading, initialize your system as described in the procedure
that follows. After you have the system up and running, create the $Y$CONFIG file
as described section 2.3. The creation of the $Y$CONFIG file automatically loads you
supervisor whenever an auto-IPL is performed.
Proceed as follows to power on your system:
Note:
The power circuit breakers located at the rear of the GEG and peripheral
cabinets are usually left in the ON position. This allows operating power for
the equipment to be controlled from the power on / off switch on the operator
panel of each unit of equipment. Perform steps 1 through 3 if setting the
cabinet circuit breakers off is a site procedure for powering down the
equipment.
1.
Set the MAIN POWER circuit breaker at the rear of the processor cabinet to the
ON position.
2.
Set the MAIN POWER circuit breaker at the rear of the VO cabinet to the ON
position.
3.
Set the circuit breaker at the rear of the VO expansion cabinet (when configured)
to the ON position.
Caution
When performing step 4, it is recommended that the data files stored on your disk
subsystems are protected before powering on the system. Otherwise, a portion of the
recorded data may be accidently erased.
4.
7004 5208-000
Power on peripheral devices (except diskette subsystems and workstations)
according to the power-on procedures described in their respective operating
guides. (Diskette subsystems power-on with CEC cabinets; the workstations are
powered on as required by their users.)
2-3
System Power-On and Initialization Procedures
5.
Make certain that the POWER ON/OFF switch on the console monitor is in the
ON (depressed) position.
6.
Set the system LOCKIUNLOCK switch to the UNLOCK position (Model 8 only)
7.
Make certain that the IPL switch is set for the type of IPL you plan to perform:
8.
•
AUTO (automatic) position to IPL from load device defined in the
configuration frame.
•
MNL (manual) position to IPL from an alternate load device.
Set the system POWER ON/OFF switch to the ON position.
Observe the following:
•
The SEQ1, SEQ2, SEQ3, and P-SEQ lights on the system control panel tum
on as the system steps through the power sequencing process.
•
The P-SEQ light turns off and the PWR light turns on when power
sequencing is complete.
•
The console displays the following messages indicating that the IMPL
procedure is in progress:
c
HEALTH CHECK RUNNING
BPU IMPL W08START
BPU IMPL W09 START
DMUX IOML START
•
The SEQ1, SEQ2, and SEQ3lights turn off when the IMPL procedure
completes.
•
If the IPL switch is set to position MNL, the STOP and POWER lights on
the system control panel light and then the configuration frame appears on
the console monitor. Go to step 9 to manually initiate the IPL process.
•
If the IPL switch is set to position AUTO, the system automatically initiates
the IPL procedure. The system turns on the RUN. WAIT. and POWER lights
on the system control panel and then displays the OS/3 initial program load
screen console monitor.) Go to step 10.
Note:
24
If the system encounters an error during the automatic IPL procedure. it
displays the configuration display frame. The cause of the error is
displayed as a message in the upper-right corner of the frame. Go to step
9 to manually initate the IPL procedure.
7004 5208-000
(
System Power-On and Initialization Procedures
9.
Proceed as follows to manually initiate IPL:
a.
Press the E8C key, then the M key to display the manual frame.
b.
Key in the character L and then press the XMIT key reset the system.
c.
Key in the character N (normal program load option) followed by the 3-digit
address of the load device where your supervisor resides. (If you are loading
from an autoload diskette, substitute the G option for N to prevent ejection
of the diskette.)
Example: Your supervisor resides on a disk drive with the address of1S0.
Complete the manual frame as follows:
(
ENTER.N11~
>L<
PROG LOAD(0-BFF)
N NORMAL
C CLEAR
G NORMAL (NO RESET)
T IMPL
o ALL
1 BPU
2 DMUX
CONTROL
U RUN
Q STOP
RESET
L SYSTEM
B BPU
COMPUTE CTRL
d.
Press the XMIT key. The 08/3 Initial Program Load (IPL) screen replaces
the manual screen on the console monitor. Continue with step 10.
10. Observe the 08/3 initial program load screen.
INITIAL
PROGRAM
LOAD
-
R14
ENTER SELECTIONS OR USE THE CURRENT VALUES DISPLAYED:
SY$STD : SUPERVISOR OR STAND/ALONE PROGRAM
S
: LOAD OPTION - S=STANDARD, Q=QUICK, L=S/A LOAD, D=DEBUG
did
: LOAD DEVICE ADDRESS
>SY$STD,S,did
> l(!!to._nlifilllin~ltmil~lrm.~)
7004 5208-000
2-5
System Power-On and Initialization Procedures
a.
If you automated supervisor loading, the following message is displayed on
the status line of the IPL screen:
IPL20 AUTO IPL IN XX SECONDS; DEPRESS MESSAGE WAIT TO HALT
To let the autoload process take place, take no action. The system
automatically loads the supervisor defined in the $Y$CONFIG file when the
countdown period reaches 0 (zero). System initialization is complete and the
system is ready to process user jobs after the supervisor load completes. Go
step 15.
To stop the autoload process, press the message wait key before the
countdown period (XX) shown in the message reaches 0 (times out). You can
now perform a manual supervisor load as described in step 11.
h.
If you did not automate supervisor loading or elected to perform a manual
IPL, the status line of the IPL screen is blank. The system takes no action.
You must manually load your supervisor. Go to step 11.
11. To manually load your supervisor, you must enter its name, the load option, and
the address of the load device where the supervisor resides. You have the option
of accepting the default values displayed above the command input line on the
screen or entering your own values. A description of the screen values follows:
supervisor-name,load-option,load-device-address
where:
supervisor-name
Specifies the name of the supervisor you want to load. When you create
a supervisor, you usually assign it a name. If you elected not to name
your supervisor, the system assigns it the default name SY$STD.
load-option
S
Specifies the STANDARD, default load option. This option is use
primarily for the initial IPL after receiving a new release or after
applying an SMC or SMP. When specified, it updates the table of
symbiont sizes that is maintained on disk. The update process is
time-consuming and is only necessary when a symbiont size has
changed.
D
Specifies the supervisor DEBUG load option. (For details, see the
Supervisor Technical Overview, UP-8831.)
L
Specifies the special supervisor load for stand-alone programs.
2-6
7004 5208-000
(
System Power-On and Initialization Procedures
Q
Specifies the QUICK load option. This option performs IPL
significantly faster than the others and should be used in most
cases.
Note:
Do not use the Q option if an SMC has been applied or if a new
supervisor or [CAM has been generated.
load-device-address
This is the device address (did) where the supervisor resides. If you
manually initiated the IPL procedure, the device address you entered on
the manual frame is displayed.
IfIPL was initiated automatically, the address of the volume named as
SYSRES on the configuration frame is displayed.
12. Enter the supervisor load values as follows:
a.
If you accept all the default values shown, press the XMIT key; no other
entry is required. Go to step 13.
h.
If you don't accept the default values, enter the values you want.(The cursor
is automatically positioned at the command input line for you to enter your
values in the format shown.)
For example, if the name of your supervisor is SUP140, it's located on device
180, and you want to use the quick load option, you complete the IPL screen
as follows:
INITIAL
PROGRAM
LOAD
-
R14
ENTER SELECTIONS OR USE THE CURRENT VALUES DISPLAYED:
SY$STD : SUPERVISOR OR STAND/ALONE PROGRAM
S
: LOAD OPTION - S=STANDARD, Q=QUICK, L=S/A LOAD, D=DEBUG
180
: LOAD DEVICE ADDRESS
>SY$STD,S,180
r sI!JP:14~!~i~1;l
c.
70045208-000
Press XMIT to enter your load values. Go to step 13.
2-7
System Power-On and Initialization Procedures
13. Observe the supervisor initialization screen.
*** OS/3 VERSION xx.xX.xx supname SUPERVISOR INITIALIZATION
DATE: sysgen date format TIME:
HH:MM:SS
RUN USS DVC ADDR: XXX (SYSRES)
FILE RECOVERY
JOB QUEUE (N,Y,H
) DEFAULT=N
ERROR LOG (N,Y
) DEFAULT=Y
SPOOL FILES (N,A,C,L,H ) DEFAULT=N
D) MODIFY SUPERVISOR? (N,Y) DEFAULT=N
E) SPOOLING DVC ADDR: XXX T0<
PROG LOAD(0-BFF)
N NORMAL
C CLEAR
G NORMAL (NO RESET)
T IMPL
o ALL
1 BPU
2 DMUX
CONTROL
U RUN
Q STOP
RESET
L SYSTEM
B BPU
(
COMPUTE CTRL
4.
Go to 2.4.2 to perform the initial program load (lPL).
2.4.2. Initial Program Load Procedure
System IPL consists of two phases: the initiation and supervisor loading. The
procedure for re-IPL is the same as that described in section 2.2, steps 9 through 15.
Keep in mind two thoughts:
•
Because the disk control units for the models 8-20 need loadable microcode, you
must IPL from the same control unit that contains the SYSRES devices.
•
Make sure no user jobs are active. The system must be idle before you initiate the
IPL procedure.
Go to section 2.2, step 9 to re-IPLyour system.
2-16
70045208-000
(
System Power-On and Initialization Procedures
2.5. IPllnformation
If the IPL process is not successful, IPL error message may be displayed on the
console monitor, or the STOP or CHECK STOP indicators on the control panel light.
Look up the IPL error message in the System Messages Reference Manual, 7004 5190
for its meaning and the corrective action to be taken.
If the STOP or CHECK STOP indicators on the control panel light, your system has
stopped and the load procedure has halted. In this case, you must display the manual
frame to determine why the machine stopped. Do this by pressing the ESC key,
releasing it, then pressing M for the manual frame.
The console screen clears at this point, then displays the following manual frame. On
the second line from the bottom of the screen, the status message (BPU STATUS=S)
appears. Directly under this line, the manual frame displays INS and the number of
the instruction that caused your machine to stop and the program status word (PSW)
identification. Check the instruction number in the System Messages Reference
Manual, 70045190, for an explanation of why your machine stopped and the
corrective action you should take.
The following sample frame display shows the BPU STATUS as stopped (S) and
shows that instruction 41 DOC8C94820 caused the IPL procedure to halt and the
system to stop.
ENTER.
PROG LOAD(0-BFF)
N NORMAL
C CLEAR
G NORMAL (NO RESET)
T IMPL
o ALL
1 BPU
2 DMUX
ROPER RECOVERY(0-BFF)
CONTROL
U RUN
Q STOP
RESET
L SYSTEM
B BPU
COMPUTE
P NORMAL
S STEP
ADR STOP(0-FFFFFFFF)
M NORMAL
I STOP IA
A STOP ANY
CHECK CTRL
H NORMAL
K STOP
V STORE STATUS
BPU STATUS=S
HPR=99080801
00000000
I NS=41D0C8C94820
PSW=00000000 3003A2D8
RLR=00000000
70045208-000
2-17
System Power-On and Initialization Procedures
If you configured your supervisor with the transient work area feature, your system
should display the message TRANSIENT WORK AREA IS INITIALIZED as soon as
the IPL procedure completes. If it doesn't, initiate the transient work area feature
yourself at this time. To do so, issue the TW command (see 4.6.16).
Disk and tape devices can be identified as unavailable to the operating system and
user applications at system generation (SYSGEN) time. This allows creation of
supervisors that, by default, prevent access to specific devices. However, when
loading a supervisor from a device generated as "down", the IPL software will
automatically set that device to the "up" state. (Loadable controllers supporting
devices that are generated down are also loaded during IPL.)
If a device generated as down is selected as a RUN, SPOOL, or DUMP device from
the system initialization screen, a warning message is displayed indicating that the
device is generated as down. You have the option of changing your device selection or
retransmitting the screen unaltered to indicate that you want the IPL software to set
the device up and proceed with system initialization. The IPL software does the same
thing for devices generated as read-only at SYSGEN time.
During the IPL operation, the system automatically sets all devices or subsystems,
except workstations, not online (not turned on) to not available. The devices or
subsystems are not available for system use until you identify them as available via
the SET 10 command for a disk drive, until you mount a disk pack and initialize the
drive. You can review the availability status for devices by using the MIX command.
Jobs requiring more than the available devices are terminated with an R277 message.
(
(
(
2-18
7004 5208-000
Section 3
System Power. . Off Procedure
3.1. System Power Off
The power-off procedure terminates system operations in an orderly manner and then
removes operating power supplied to your system. The procedure does not include
specific instructions for removing operating power to those peripheral subsystems
that power on and off separately from your system. Instructions for powering off
peripheral devices are contained in their respective operating guides.
Proceed as follows to power off your system:
1.
Enter the SHUTDOWN command to terminate all system activity in an orderly
manner.
Caution
When performing step 2, make certain that the data files stored on your disk subsystems
are protected before powering off the system. Otherwise, a portion of the recorded data
may be erased.
2.
Power off all peripheral devices (those that power on and off separately from
your system) as described in their respective operating guides.
3.
Set the system POWER ON/OFF switch to the OFF position to remove dc
operating power from the console, integrated disks, and diskettes subsystems.
(The console screen clears and the POWER light on the console keyboard and all
lights on the control panel go off.)
4.
Be sure to leave the POWER ON/OFF switch on the console display in the ON
(depressed) position.
Note:
5.
7004 5208-000
Step 5 need not be performed unless you want to completely remove all power
from the system due to an emergency or if the step is performed as a normal
site requirement.
Set the circuit breakers at the rear of the processor, the I/O cabinet, and the I/O
expansion cabinet to the OFF position.
3-1
(
(
Section 4
Job Processing Procedures
(
After you successfully initialize your system, the system is ready to process user jobs.
To begin processing, place the input media (cards, diskette, or disk) containing the job
control stream (JCS) to be processed (or the input data required by a prefiled job to be
processed) on the input device. Then proceed to the console workstation or console to
initiate running the job, using the system commands described in this section. When
card input is used, press the RUN switch on the card reader after you enter the
command and the I/O stop state message is displayed.
Notes:
1.
To demonstrate that all installed products in the system are operational, refer to
the Installation Verification Procedures Operating Guide (70045232).
2.
See the About This Document section for the conventions used to illustrate the
commands and messages appearing in this guide.
'
4.1. Keyin Procedure
4.1.1. Console Keyin Procedure
Before keying in any message or cO'Jl:\mand on the console for transmittal to the
system, you must press the MSG WAlT key on the console. Pressing this key:
(
•
Notifies the system that you want to send a message or command to it
•
Automatically opens a line on the console screen for display of the input
command or message
•
Gives the start of entry ~) signal
•
Sets the cursor (I ) to the position where typing is to start
70045208-000
4-1
Job Processing Procedures
After keying in the message or command, press the XMIT key on the console
keyboard. This initiates transmittal of the message or command to the system. The
accepted command (or unsolicited message used instead of a command, as we describe
in 4.3.3) is either acted upon immediately or placed on a queue for future processing;
it is never ignored or lost. Commands are placed on queue when insufficient main
storage exists or a required device is not available.
Queued commands are activated as soon as all requirements for execution are met.
Therefore, commands keyed in twice are eventually executed twice. If a message or
command is unacceptable, the system responds with a negative acknowledgment
(NAK) error message indicating why. This error message appears in the last 12
character positions of the line of the unacceptable message or command and, if
necessary, overwrites any message or command text that may be present in the last 12
character positions.
A pair of blinking marker symbols (II and II) bracket each error message. The message
or command must then be retyped in accordance with the information furnished by
the error message, so that the job involved with the unacceptable message or
command may be executed. The error messages that may be displayed are described
in the System Messages Reference Manual, 70045190.
(
If console logging is configured in your system, the console log messages are recorded
in a spool file for later printing.
(
4.1.2. Alternate Console Keyin Procedure
You can designate that a local workstation serve as the alternate console by system
generation or the SET command. The local workstation takes the place of the
hardware console and becomes the command entry and system control device.
Before keying in any message or command on the alternate console for transmittal to
the system, you must press MSG WAIT on the keyboard. Pressing this key:
4-2
•
Notifies the system that you want to send a message or command to it
•
Automatically opens a line on the console screen for display of the input
command message
•
Positions the cursor at the beginning of the input line to allow you to type in your
command
7004 5208-000
(
Job Processing Procedures
After keying in the command or message, press the XMIT key to enter it into the
system. The system will exit the system line and repeat your input at the bottom of
the screen. Input received is handled the same way as input from the regular console
(see 4.1.1).
The spacebar is set as destructive so you need not clear the input line manually each
time you use it. Just type in the new text on top of the previous command. The last
command entered remains on the system command line so that you may edit and
reenter it without having to rekey the entire command.
Although the device is physically a workstation, when it is functioning as the
alternate console it cannot run programs or functions that allocate the entire screen
(such as the editor or screen format services).
(
If the alternate console becomes unusable, the system will automatically reactivate
the original console. Normally when the alternate console is active, input from the
original console is rejected with a negative acknowledgement (NAK) error message.
If you specify a workstation at system generation to be the alternate console, the
hardware console is still used to IPL the system. The system switches control to the
alternate console when the system is successfully initialized. The hardware console
screen is cleared and has the header line:
OS/3 INACTIVE CONSOLE' ALTERNATE CONSOLE IS DEVICE ddd
You can switch the alternate console to another device or back to the hardware console
by using the command:
SET 10,
d'd)
O~G ,CON
[ ALT
where:
did
Is the device address.
ORG
Is the original hardware console.
ALT
Is the system generated.
CON
Is a console change.
70045208-000
4-3
Job Processing Procedures
4.2. Command Characteristics
When a command is being typed in, there must be at least one space between the
command and the first parameter, and commas between all parameters. The general
format for these commands is:
~cOmmand~(did)
([didl,LabeL)
(RDR, LabeL)
~~[command.parameters]
where:
Is the start-of-entry (SOE) symbol that must precede all lines. This symbol is
automatically generated by OS/3 when the MSG WAIT key is pressed.
(
command
Is two to eight alphabetic characters that identify the system command to be
processed. At least two characters must be supplied.
(did)
Is a three-digit device identification number that identifies the channel,
sub channel, and selected device number to be used when carrying out the
command. A did should be included when a particular peripheral device is to
be specified or when no default option is provided.
If a did is not entered, the first appropriate device is used.
([did],LabeL)
When a diskette is used to serve the function of a card reader or card punch,
it must be formatted in data set label mode; a file identifier (label) is
required to identify the specific file to be accessed on the diskette. The
device address also must be included, unless the diskette is configured as the
SYSRDR. The label, which may be a maximum of eight alphanumeric
characters, is separated from the device address by a comma. The data set
label diskette record size must be 128 bytes or less, and the records must be
unblocked and unspanned.
(RDR, labeL)
Specifies that the device address to be used is the input spool file with the
specified label. The label may be a maximum of eight alphanumeric
characters and is separated from the RDR entry by a comma.
7004 5208-000
(
Job Processing Procedures
Examples
RUN(010,DATANAM1) JOBNAM1
Specifies that the diskette with a device address of 01 0 contains a
file labeled DATANAMl to be accessed by the command.
RUN(,DATANAM1) JOBNAM1
Specifies that the diskette configured as SYSRDR contains a file
labeled DATANAMl to be accessed by the command.
RUN(RDR,DATANAM1) JOBNAM1
Specifies that the input spool file contains a subfile labeled
DATANAMl to be accessed by the command.
command-parameters
Are optional positional parameters used to tailor the effect of the command
being issued. Each specified parameter must appear in its own position.
Commas are used to separate positions. For example, the following portion
of the RUN command format indicates that two positional parameters are
associated with the command; the comma separates the first from the
second.
RUN
~(d([dldl,label)
i~)
~ b. ~j(new-name)
obname [( new -name) lli
(RDR,label)
[m
~
PRE
HIGH
NOR
If only the second parameter is to be specified, the command must be
keyed in as follows:
RUN ,HIGH
As shown, the comma must be included to indicate the omission of
the first parameter; otherwise, HIGH is considered the name of the
job to be run.
Also, if a parameter takes more than one form (as is the case with
the first parameter in the RUN command), the punctuation marks
(in this case, parentheses) must be keyed in whenever shown in the
format. For example, if a new-name is specified, the command
could be keyed in either of the following ways:
(
RUN MYJOB(JOBA),PRE
RUN (TEMPNAME)
In either case, the parentheses must be included.
7004 5208-000
4-5
Job Processing Procedures
4.3. Message Characteristics
4.3.1. Output Messages
Output messages are displayed on the console workstation or console to provide you
with information, to direct you to take some action, or to ask you a question that
requires a response. The messages that can be output to the console workstation or
console by the components of 08/3 are described in the System Messages Reference
Manual, 70045190, together with their associated operator responses, when
appropriate. The format of an output message is:
[i
nn[?)
obnamez)
d message-text synnnn
*
cOllll1and
where:
nn
(
Is a unique message number from 11 to 99 (numbers 1 through 10 are
reserved for other system uses). This number serves as the message
identification. Numbers 11 to 42 are used for questions.
?
Identifies an output message that must be responded to before the job that
issued the message can continue. Output messages requiring replies are not
rolled off the console workstation or console screen until they are answered.
Identifies an output message that requires no reply or operator action; it
gives information only. Input messages, solicited and unsolicited, must
include a space between the message-id and message text.
*
Identifies an output message that requires you take some action. The job
that generated the message has placed itself in a yield state. A GO command
is required from the operator to reactivate the job (see 4.5.3).
message-text
Comprises the actual message content and is a maximum of 60 characters.
The message text includes the message prefix which you use to find the
message in the 08/3 manual documenting it - either the System Messages
Reference Manual, 70045190 or the 08/3 manual describing the system
program that displays the message.
7004 5208-000
(
Job Processing Procedures
jobnamez
Is the name of the user job sending the message. This name is the 8character name taken from the job preamble.
synnnn
Is the name of the symbiont sending the message. This name is the 2character symbiont identification followed by a four-digit binary job number
inserted at task initiation. It is a six-character name altogether.
conmand
Is the interactive command followed by the interactive command ID.
4.3.2. Solicited Input Messages
Solicited messages are those messages you input in direct response to an output
message that requires a reply (question mark immediately follows message-id). The
format for all solicited input messages is:
nnrunessage-text
where:
nn
Is the unique message number of the message you are responding to.
Note:
In some cases, an apparent system halt is caused by the operator's failure to
answer output messages that require a response. Before deciding that the
system is in a halt condition, you should ensure that all output messages have
been answered.
4.3.3. Unsolicited Input Messages
Unsolicited messages are those messages you input that are not in direct response to
an output message that requires a reply. You may enter unsolicited messages from
the console or from the workstation that initiated the job or symbiont. The format for
all unsolicited input messages is:
006synnnn
006symbname,
006symid
runessage text
006symid(did)
UNS6jobname,
UNS6symid,S
UNS6synnnn
UNs6symbname,S
UNS6symid(did),S
70045208-000
4-7
Job Processing Procedures
where:
00
Specifies that the unsolicited message is for a symbiont.
UNS
Specifies that the unsolicited message is for a user job.
symbname
Is the eight-character name of the symbiont receiving the message. For
example, SL$$OWOO is the symbiont name of the output writer.
symid
Is the two-character symbiont identification used to invoke the symbiont
receiving the message. For example, PR is the symbiont identification of the
output writer.
(
symid(did)
Is the two-character symbiont identification currently used to invoke the
symbiont receiving the message, along with the address of the device used or
controlled by a specific copy of the symbiont in main storage. For example,
PR(160) is the symbiont identification of the output writer using the printer
that is at device address 160. The symbiont having this device allocation
receives the unsolicited message. If the specified device is not assigned to
the symbiont, the unsolicited message is not acknowledged. The did must be
enclosed in parentheses.
jobname
Is the name of the user job receiving the unsolicited message.
s
Indicates a symbiont identification.
synnnn
Is the name of the symbiont sending the message. This six-character name is
the two-character symbiont identification followed by a four-digit binary job
number inserted at task initiation.
(
message-text
Is the actual text of the message.
Note:
When you key in an unsolicited message to a symbiont, the system task control
blocks (TCB) are searched to locate an active symbiont identified by the name
specified in the message. When no address is specified, the unsolicited
message is transferred to the buffer of the first symbiont active; only the first
will get the message. Figure 4-1, line 11 is an example of an unsolicited key in
to a symbiont.
7004 5208-000
Job Processing Procedures
Following in 4.4 and 4.5 are descriptions of the operator procedures for entering
commands, unsolicited messages, and solicited messages according to the function
required. Specific command and message formats are included, specifying the
appropriate parameters and their order for that particular function.
Figure 4-1 shows typical messages, how OS/3 displays them, and how you respond to
them. Note that the messages are not meant to be real; they simply show how you use
the message characteristics described in this section.
THIS IS A COMMENT FROM PROGRAM ?
12?THIS IS A QUESTION FROM PROGRAM 1
12THIS IS THE ANSWER TO PROGRAM 1
ACTIVE USER ISLAND CODE FOR PROGRAM 12
14*MOUNT DEV=440 VSN=DSP614 LU=050 DEV=441 VSN=DSP633 LU=051
15*MOUNT DEV=442 VSN=DSP554 LU=052 GO?
GO PROGRAM4
DISPLAY 100
16?DI0032 THIS IS A QUESTION FROM THE 'DISPLAY' SYMBIONT
16THIS IS THE RESPONSE TO DI0032'S QUESTION
00 PR ST
CANCEL PR,S
CANCEL PROGRAM12,D
JC03 JOB PROGRAM 12 TERMINATED ABNORMALLY. ERR CODE 049
(
PROGRAM?
PROGRAM 1
PROGRAM 12
PROGRAM4
PROGRAM4
PROGRAM12
Figure 4-1. Typical Messages
4.4. Job Processing During the Daily Memory Refresh
Routine
Model 10, 15, and 20 systems automatically run a memory refresh routine every day
at midnight. When initiated, this routine accesses four megabytes of main storage and
causes a hardware correction mechanism to correct any single-bit errors that are
encountered. This operation increases overall system performance since it reduces the
possibility that uncorrectable multibit errors will occur. Multibit errors require system
recovery operations and may cause halts.
The memory refresh routine automatically starts at midnight and runs for
approximately three minutes. During this time, you may notice a slight decrease in job
processing performance.
70045208-000
4-9
Job Processing Procedures
Note:
Refer to 4.3.1. for output message format definition.
When memory refresh is initiated, the following message is displayed at the system
console:
nn MEMORY REFRESH INITIATED
synnnn
When memory refresh is completed, the following message is displayed at the system
console:
nn MEMORY REFRESH OF xxxxxxx-yyyyyyy COMPLETE
synnnn
where:
xxxxxxx
Is the starting main storage address.
(
yyyyyyy
Is the ending main storage address.
4.5. Job Processing Commands
Job processing commands enable the operator to:
•
Read job control streams into the system and assign scheduling priorities to them
(job initialization)
•
Control jobs awaiting execution within the scheduling priority queues (schedule
jobs)
•
Control jobs being executed (execute jobs)
•
Stop jobs under execution (terminate jobs)
In the job processing commands that follow, scheduling priorities are defined as
preemptive, high, normal, or low to specify in what order jobs begin execution. Jobs to
be run are placed in one of the four scheduling priority queues:
1.
PRE (preemptive) Queue
Contains jobs to be executed first (i.e., before any jobs assigned HIGH, NOR, or
LOW scheduling priority), even if the resources for any HIGH, NOR, or LOW
priority jobs are available and the resources for any PRE jobs are not. PRE jobs
are always executed first unless they're placed on hold via the HOLD command
(see 4.5.2). If rollin/rollout is configured, a PRE job initiated for execution when
4-10
7004 5208-000
(
(
Job Processing Procedures
sufficient main storage is not available may cause HIGH, NOR, or LOW jobs
being processed to be rolled out to make main storage space available for the
PRE job. Rolled out jobs are rolled in and continue processing when main storage
is again available. When rollin/rollout is configured, a maximum of 14 jobs can be
in the preemptive queue.
2.
HIGH Queue
Contains jobs to be executed before any jobs assigned a NOR or LOW scheduling
priority. HIGH scheduling priority jobs are not executed unless the PRE queue is
either empty or placed on hold. HIGH priority jobs are always executed before
NOR or LOW priority jobs (unless they're placed on hold), even if the resources
for the HIGH job are not available and the resources for the NOR or LOW jobs
are. A maximum of 35 jobs can be in the high priority queue.
3.
NOR (normal) Queue
Contains jobs to be executed before any jobs assigned a LOW scheduling priority.
NOR scheduling priority jobs are executed only when there are no jobs left in the
PRE or HIGH queues or when the queues are placed on hold. NOR scheduling
priority is the default for a job control stream and for some of the job scheduling
commands (4.5.2). NOR scheduling priority jobs are always executed before the
LOW priority jobs (unless they're placed on hold) even if the resources for the
NOR job are not available and the resources for the LOW job are. A maximum of
70 jobs can be in the normal priority queue.
4.
LOW Queue
Contains jobs to be executed only when there are no jobs left in the PRE, HIGH,
or NOR queues or when the queues are placed on hold. A maximum of 70 jobs can
be in the low priority queue.
4.5.1. Job Initialization
(
Job control streams are read into the system by using one of the job initialization
commands (FILE, RUNIRV, and SlISC). These commands enable you to file the job
for future use or to process the job immediately.
When a job is filed for future use, it is placed in the job control stream library
($Y$JCS) file or in an alternate library file, as specified in the operator command.
7004 5208-000
4-11
Job Processing Procedures
A job may be initiated for processing from one of three places:
1.
Input device (card reader, data set label diskette, or spool file)
2.
$Y$JCS or an alternate library where the job is filed
3.
$Y$SAVE file where it has been saved in its expanded run state via a statement
included in the job control stream (II OPTION SAVE or II OPTION NOSCHED
statement)
When a job is initiated, it is placed in a scheduling priority queue to await execution.
This scheduling priority queue can be specified by the programmer submitting the job
in the job control stream itself. You can override this specification by entering another
scheduling priority in the job initialization command. The default is to use the normal
priority queue.
(
Filing Job Control Streams (FILE)
The FILE command files jobs and JPROCs, read from an input device, into the
permanent JCS library file ($Y$JCS) or an alternate library file. (The alternate file
may be a MIRAM or a SAT file, but keep in mind that the RUN processor cannot
access data in a MIRAM file.) The input can be from a card reader, a diskette drive
(data set label diskette only), or the input spool file.
Note:
The FILE command cannot be issued from an enter stream.
Ifno device and label are identified, the first available card reader, as defined when
the system was generated, is expected to contain the job control streams and/or
JPROCs to be filed. If the job control stream is on a diskette, the label is required; if it
is in the input spool file, RDR and label are required (see 4.2).
Jobs filed from the card reader must terminate with a II FIN job control statement.
When jobs are filed from diskette or the spool file, the II FIN job control statement is
not necessary. Jobs input from diskette to the spool file must be single volume and
formatted in data set label mode.
Format
FILE~(did)
~!J.
([dldl,label)
(RDR,label)
:alt-filename
:alt-filename,[RES)
RUN
vsn
,.It.fllen.... ~;~~.w'lte ....swO,d
4-12
7004 5208-000
(
Job Processing Procedures
Positional Parameter 1
Identifies an alternate library file where job control streams and/or JPROCs are to be
filed. Omit this parameter when no alternate file is required; the job is filed into
$Y$JCS. You can use a disk or a format label diskette for the alternate library file.
:alt-filename
Specifies the name of the alternate library file, residing on SYSRES, to
receive the job and/or JPROC. If the alternate file name is cataloged, the vsn
of that file in the catalog is used. There must not be a write password for the
alternate file in the catalog.
:alt-filename,[RES)
RUN
vsn
Specifies the name of the alternate library file to receive the job and/or
JPROC and identifies a volume serial number (RES, RUN, or vsn) for the
file. You specify RES to identify SYSRES as the volume to contain the file or
RUN to identify the system RUN pack as the volume to contain the file; or
you may specify the volume serial number (vsn) of a disk pack or format
label diskette to be used. If a file with the same file name is in the catalog,
the volume serial number you include in the command makes the distinction
between the files and overrides the catalog vsn. There must not be a write
password for the alternate file in the catalog. The colon and enclosing
parentheses are optional and included only for consistency with the format
of the RUNIRV command.
c
,.'t.. ,'en.... [[;:.:!l.w"te.p.'..,'d
Specifies the name of the alternate library file to receive the job and/or
JPROC and includes the write password, identified in the catalog, required
to write to that file. You specify RES to identify SYSRES as the volume to
contain the file or RUN to identify the system RUN pack as the volume to
contain the file; or you may specify the volume serial number (vsn) of a disk
pack or format label diskette to be used. If you omit a volume serial number
(RES, RUN, or vsn), your file is written to the volume associated with that
file name in the catalog. You must specify RES, RUN, or a vsn if you want
the file written to a different volume; the volume serial number you specify
overrides the catalog vsn. The colon and enclosing parentheses are optional
and included only for consistency with the format ofthe RUNIRV command.
(
7004 5208-000
4-13
Job Processing Procedures
Note:
If you specify a disk or diskette vsn for the alternate library file in the
command when the volume isn't already mounted, the system displays a
mount message suggesting an available device. The volume can be
mounted on the available device or any other suitable device. In rare
instances when the system cannot determine whether the volume is a disk
or diskette, the message may suggest an available disk drive for a
diskette volume. Ignore this inconsistency and mount the diskette volume
on any suitable device.
Example
Operator keyin:
FI :(ALTJCS,RUN)
Function requested:
The job control stream, residing on a card reader, is to be written to the alternate job
control library file called ALTJCS on the system RUN pack.
Running Job Control Streams (RUNjRV)
Function
The RUNIRV commands read a job control stream from either an input device, or the
$Y$JCS or alternate job control library file. The input device can be a card reader, a
diskette drive (data set label diskettes only), or the input spool file.
The commands cause the job control stream to be written to the job run library
($Y$RUN) file and expanded to its run state (JPROCs are expanded), then scheduled
for execution. $Y$RUN is a temporary file; the job is deleted when it is run.
When an II OPTION SAVE job control statement is included in the job control stream,
the job is scheduled to be run from $Y$RUN and a copy ofthe expanded job is saved
in the $Y$SAVE file. When an II OPTION NOSCHED job control statement is
included in the job control stream, a copy of the expanded job is saved in $Y$SAVE;
however, the job is not scheduled to be run.
The expanded job to be saved in $Y$SAVE or an alternate save file can be run by
using the SIISC commands. (SIISC commands are described next in this subsection.)
4-14
7004 5208-000
(
Job Processing Procedures
The RV command initiates the reading of a prefiled job control stream that does not
contain a II CR statement indicating that there is input (cards, diskette, or spool file)
to be read and inserted into the stream. The RUN command initiates the reading of a
job control stream that requires an input device (i.e;, card reader, diskette, or spool
file). This means if the job is initiated from an input device or if the job contains a
II CR statement to read input, you must use RUN. When the RUN command is issued,
it is accepted only if an input device is available, whether or not one is needed by the
job control stream being read. The RV command allows a job control stream to be
initiated that does not require an input device. You must include ajob name when you
enter an RV command.
Remember that, when a system card reader is placed online, the RUN command to
read a job control stream from cards in the hopper is initiated when the RUN switch
on the card reader is pressed, or when the RUN command is keyed in at the console
workstation or console. The RUN command can be initiated from either location, but
not from both. If a duplicate RUN command is initiated for the same job, the
supervisor queues the second command until the input device is available. Presuming
that nothing is in the hopper when the second RUN command is executed, a hopper
empty message results.
Format
RUN [(did)
([didl,label)
(RDR,label)
j
~A~jObname[(new-name)
]lij
(new-name)
RVAjobnamej[(new-name)]
:alt'filename
:alt'filename,!RES]
RUN
vsn
"[t.f;[.o....
(
[I;~~.'.ad.P"S'O,d)
~{!l!H]][t;me + O][.,.y·, ..,[·, •••.• 'ey·o--.,[·o,
Command Codes
Initiates the running of a job control stream that requires an input device.
You must specify ajob name when the job control stream is prefiled. Ifthe
job is prefiled and you don't specify an input device, the first available card
reader is assigned to the job, whether or not it is required. If you omit an
input device and job name, the first available card reader is expected to
contain the job to be run.
7004 5208-000
4-15
Job Processing Procedures
You must specify a label when the job control stream is on a diskette. If it is
in the input spool file, you must specify RDR and a label (see 4.2). For
diskette and spool file input, the last II FIN job control statement is not
needed because it is used only to terminate card reader operation. However,
the II FIN statements that separate groups of card images read with II CR
statements are still necessary. Jobs input from diskette to the spool file
must be single volume and formatted in data set label mode.
RV
Initiates the running of a prefiled job control stream that does not require
an input device; that is, it does not contain a II CR (read card reader,
diskette, or spool file) statement. You must specify a job name.
Parameter!
jobname[(new-name)]
Identifies the name of the job to be read from $Y$JCS or an alternate job
control library file and stored in a scheduling priority queue to await
execution. The job name consists of one to eight alphanumeric characters.
The job name is required with RV.
You include new-name to assign a new one- to eight-character alphanumeric
name to a job already stored in $Y$JCS or an alternate job control library
file. The job identified by thejobname parameter is read from $Y$JCS or an
alternate file, and stored in a scheduling priority queue under the name
identified by the new-name parameter to await execution. The new name
cannot contain blanks.
(new-name)
U sed with the RUN command to assign a new one- to eight-character
alphanumeric name to a job input from the card reader. The job is read and
stored in a scheduling priority queue under the new name to await
execution. The new name cannot contain blanks.
If parameter 1 is omitted from the RUN command, the job is read and stored in a
queue under the job name on the II JOB statement in the job control stream.
Parameter 2
U sed when the job control stream resides in an alternate job control library file on
disk or format label diskette, rather than in $Y$JCS. When the job resides in an
alternate library file, this parameter identifies the library file to be read. If omitted,
the job is read from $Y$JCS.
:aL t- filename
Specifies the name ofthe alternate library file, residing on SYSRES, that
contains the job. If the alternate file name is cataloged, the vsn of that file
in the catalog is used. There must not be a read password for the alternate
file in the catalog.
4-16
7004 5208-000
Job Processing Procedures
:alt-filename,[RES)
RUN
vsn
Specifies the name of the alternate library file that contains the command
which makes the distinction between the files and overrides the catalog vsn.
There must not be a read password for the alternate file in the catalog.
"L t - H L"""".
~;:;~ • ,e,d-.""""d
Specifies the name of the alternate library file that contains the job stream
and includes the read password, identified in the catalog, required to read
from that file. You specifY RES to identifY SYSRES as the volume that
contains the file or RUN to identifY the system RUN pack as the volume
that contains the file; or you may specify the volume serial number (vsn) of a
disk pack or format label diskette to be read. If you omit a volume serial
number (RES, RUN, or vsn), your file is read from the volume associated
with that file name in the catalog. You must specifY RES, RUN, or a vsn if
you want the file read from a different volume; the volume serial number
you specifY overrides the catalog vsn.
(
Parameter 3
Used to specify scheduling priority and/or time (hour and day).
J:RE
.!!.IGH
.!fOR
(
Places the job in the preemptive scheduling priority queue to await
execution .
Places the job in the high scheduling priority queue to await execution.
Places the job in the normal scheduling priority queue to await execution.
L()\.J
Places the job in the low scheduling priority queue to await execution.
time
Is a four-digit number specifYing a time of day in military format indicating
when execution of the job is to begin.
n
Is an integer from 1 to 9 specifYing the number of days after today to start
execution of the job.
Parameter 3 can be specified with priority only, time only, or priority and time. If
parameter 3 is omitted, the scheduling priority specified in the job control stream is
used. If not specified in the job stream, the normal priority is used.
7004 5208-000
4-17
Job Processing Procedures
Parameters 4 through n
key-1=val-1, ••• ,key-n=val-n
Are the keywords and their values, which may be used by the job being run.
The keywords and values must be supplied by the user requesting the job.
Notes:
1.
The total length of all the parameters specified in this command, from the first
character ofparameter 1 to the last character of the last keyword value specified,
is limited to 60 characters.
2.
If you specify a disk or diskette vsn for the alternate library file in the command
when the volume isn't mounted, the system displays a mount message suggesting
an available device. The volume can be mounted on the available device or any
other suitable device. In rare instances when the system cannot determine whether
the volume is a disk or diskette, the message may suggest an available disk drive
for a diskette volume. Ignore this inconsistency and mount the diskette volume on
any suitable device.
(
Examples
1.
Operator keyin:
RU MYJOB:(ALTJCS,RUN)
Function requested:
The job named MYJOB, filed in the alternate job control library file ALTJCS on
the system RUN pack, is run under the priority specified in the job control
stream. The first available card reader is expected to contain some input for
MYJOB, which contains a II CR statement.
2.
Operator keyin:
RV MYJOBA(NETPAY)
(
Function requested:
The job named MYJOBA, filed in $Y$JCS, is run under the new name NETPAY
according to the priority specified in the job control stream.
3.
Operator keyin:
RV JOBABC:(CPYLIB,PUBDSK)
Function requested:
The job named JOBABC, filed in the alternate library file CPYLIB on volume
serial number PUBDSK, is placed in the scheduling queue specified in the job
control stream.
4-18
7004 5208-000
Job Processing Procedures
4.
Operator keyin:
RV MYJOB,2230
Function requested:
Execution of the job, MYJOB, will begin as soon as resources are available after
2230 hours (10:30 p.m.).
5.
Operator keyin:
RV MYJOB,P2230+1
Function requested:
The job, MYJOB, win be placed in the preemptive scheduling priority queue at
10:30 p.m. tomorrow.
Example:
JC06 USING DEV=104 VSN=PUBDSK
JC01 JOB JOBABC EXECUTING JOB STEP LIBS0000 #001 11:52:19
JC02 JOB JOBABC TERMINATED NORMALLY
11:52:38
Explanation:
The system messages provide device information and the job step currently executing.
However, the console does not display job slots, so you do not see your job occupying a
job slot on the screen.
Running Saved Job Control Streams (SI/SC)
(
The SI/SC commands initiate the running of a job control stream from the $Y$SAVE
MIRAM library file or from an alternate library file, then schedule the job for
execution. In either case, the control streams have been saved in their expanded run
state. A control stream is expanded in the $Y$RUN file when the RUNJRV command
is issued for the job. When an II OPTION SAVE or II OPTION NOSCHED job control
statement is included in the job control stream, a copy of the expanded control stream
is stored in the $Y$SAVE or alternate file for subsequent runs using SI or SC.
The SC command is used only to initiate the reading of a job control stream that does
not require an input device to replace embedded data. The SI command initiates the
reading of ajob control stream that requires an input device (Le., card reader, data set
7004 5208-000
4-19
Job Processing Procedures
label diskette, or spool file) to replace embedded data. When the SI command is
issued, it is accepted only if an input device is available. The se command allows a job
control stream to be initiated that does not require an input device.
(
Format
l
S1~(did
~lajObname[(new-name)]
([didJ,label)
(RDR,label)
sc
:alt-filename
:alt'filename,[RES)
RUN
vsn
,.'t'fi,en""~;;~~""d'P"'WO'd
(
\
Command Codes
S1
Initiates the running of a job control stream that requires an input device. If
no device and label are identified, the first available card reader, as defined
when the system was generated, is expected to contain the replacement data
required by the job. If the data is on a diskette, the label is required; if it is
in the input spool file, RDR and label are required. (See 4.2.) For diskette
and spool file input, the last II FIN job control statement is not necessary.
sc
Initiates the running of a job control stream that does not require an input
device to replace embedded data.
Parameter 1
jobname[(new-name)]
Identifies the name of the job to be read from $Y$SAVE or an alternate
library file and stored in a scheduling priority queue to await execution. The
name consists of one to eight alphanumeric characters.
You include new-name to assign a new one- to eight-character alphanumeric
name to a job stored in $Y$SAVE or an alternate file. The job identified by
the job name parameter is read from $Y$SAVE or an alternate file and
stored in a scheduling priority queue under the name identified by the newname parameter to await execution. The new name cannot contain blanks.
4-20
7004 5208-000
(
Job Processing Procedures
Parameter 2
U sed when the job control stream resides in an alternate job control library file on
disk or format label diskette, rather than in $Y$SAVE. When the job resides in an
alternate library file, this parameter identifies the library file to be read. If omitted,
the job is read from $Y$SAVE.
:alt-filename
Specifies the name of the alternate library file, residing on SYSRES, that
contains the job. If the alternate file name is cataloged, the vsn of that file
in the catalog is used. There must not be a read password for the alternate
file in the catalog.
aLtofiLename,[RES)
RUN
vsn
Specifies the name of the alternate library file that contains the job or
JPROC and identifies a volume serial number (RES, RUN, or vsn) for the
file. You specify RES to identify SYSRES as the volume that contains the
file or RUN to identify the system RUN pack as the volume that contains
the file; or you may specify the volume serial number (vsn) of a disk pack or
format label diskette to be read. If a file with the same file name is in the
catalog, the volume serial number you include in the command makes the
distinction between the files and overrides the catalog vsn. There must not
be a read password for the alternate file in the catalog.
'lto"lenome'[[;;;l]"eadOP",",'d
Specifies the name of the alternate library file that contains the job stream
and includes the read password, identified in the catalog, required to read
from that file. You specify RES to identify SYSRES as the volume that
contains the file or RUN to identify the system RUN pack as the volume
that contains the file; or you may specify the volume serial number (vsn) of a
disk pack or format label diskette to be read. If you omit a volume serial
number (RES, RUN, or vsn), your file is read from the volume associated
with that file name in the catalog. You must specify RES, RUN, or a vsn if
you want the file read from a different volume; the volume serial number
you specify overrides the catalog vsn.
(
Parameter 3
Used to specify scheduling priority and/or time (hour and day) .
.!:RE
Places the job in the preemptive scheduling priority queue to await
execution.
!J.IGH
Places the job in the high scheduling priority queue to await execution.
7004 5208-000
4-21
Job Processing Procedures
NOR
Places the job in the normal scheduling priority queue to await execution.
hOW
Places the job in the low scheduling priority queue to await execution.
time
Is a four-digit number specifying a time of day in military format indicating
when execution of the job is to begin.
n
Is an integer from 1 to 9 specifying the number of days after today to start
execution of the job.
Parameter 3 can be specified with priority only, time only, or priority and time. If
parameter 3 is omitted, the scheduling priority assigned to the job via the job control
stream is in effect.
(
Example
Operator keyin:
SI MYJOB(AVGYTD),H2230+1
Function requested:
The job called MYJOB, expanded and filed in $Y$SAVE, is run under the new name
AVGYTD. The job is to be placed in the high scheduling priority queue to await
execution. Replacement embedded data for AVGYTD is expected to be found on the
first available card reader after 10:30 p.m. tomorrow.
4.5.2. Job Scheduling
Ajob is placed in a scheduling priority queue to await the availability of system
resources (e.g., main storage, disk drive, printer) to execute that job. While waiting for
these resources, you can exercise control over any specific job in a queue, all jobs in a
specific queue, and all jobs in all queues, by using job scheduling commands. You may
also control, in a similar manner, jobs initiated by a specific workstation user. These
commands allow you to:
4-22
•
Defer jobs from being executed
•
Permit jobs to be executed
•
Delete jobs from a queue
•
Display contents of a queue
•
Change a job scheduling priority
7004 5208-000
(
Job Processing Procedures
Deferring Jobs Scheduled for Execution (HOLD)
The HOLD command permits you to defer the scheduling of jobs according to the
command parameters specified. You can defer scheduling for aU jobs in an queues or
in a specific queue; for a specific job within a queue; for a specific workstation user's
jobs in all queues or a specific queue; or for a specific host's jobs in an queues or a
specific queue. Scheduling remains deferred until the jobs are reactivated via the
BEGIN command.
Format
JBQ[~iHr [!~;~li [i:~
HOLDA
(
jobname
jj
I,ur .....'·'d]I,HOS'·h"'·'d]
Positional Parameter 1
JBQ
Specifies the command applies to the jobs in a job scheduling priority queue,
as further defined by PRE, HIGH, NOR, LOW or ALL, where:
ERE
HIGH
-
NOR
hOW
Defers the jobs in the preemptive scheduling priority queue.
Defers the jobs in the high scheduling priority queue.
Defers the jobs in the normal scheduling priority queue.
Defers the jobs in the low scheduling priority queue.
Defers the jobs in all scheduling priority queues.
jobname
Defers a particular job from being scheduled for execution. No further
parameters are permitted.
Keyword Parameters
OLD
Defers only jobs already in the scheduling priority queue defined in
parameter 1. Jobs subsequently entered in this queue are not deferred.
NEW
Defers only jobs subsequently placed in the scheduling priority queue
defined in parameter 1. All existing jobs are still available for execution.
7004 5208-000
4-23
Job Processing Procedures
Once a new job is placed in queue, it becomes an old job for any subsequent
commands to defer or permit execution. Therefore, the NEW parameter is used
with the HOLD command to defer new jobs entering a queue, while the old jobs
already residing in the queue remain unchanged and are still able to be
scheduled for execution. Likewise, the OLD parameter is used with the HOLD
command to defer old jobs already residing in the queue while the new jobs
entering the queue are still able to be scheduled for execution. Once a new job
enters a queue that is under the influence of a HOLD NEW command, a
subsequent command to permit the old jobs in that queue to be scheduled for
execution will also release the new job from its deferred status.
Note:
DDP
When issued from a workstation, the HOLD console command will hold
all OLD jobs on the job queue that were initiated by the same
workstation, but will not hold NEW jobs entering the job queue. There is
no mechanism at a workstation to hold NEW jobs.
(
Defers only distributed data processing jobs initiated from a remote host.
LOCAL
-
Defers only locally entered jobs.
RBP
Defers only jobs entered remotely (i.e., from a remote batch terminal).
WKSTN
-
Note:
Defers only jobs either initiated from a workstation or using the II OPTION
ORI= or II OPTION MAS= job control statement.
All of the preceding keyword parameters may be interchanged.
UID=user-id
Defers all old jobs associated with a particular workstation user-id in the
scheduling priority queue defined in parameter 1. Jobs subsequently entered
with this user-id are not deferred. The user-id is a one- to six-character
alphanumeric identification that does not start with $Y$.
(
HOST=host-id
-
Defers all old jobs associated with a particular host in the scheduling
priority queue defined in parameter 1. Jobs subsequently entered with this
host-id are not deferred. The host-id is one to four alphanumeric characters.
Notes:
4-24
1.
The UID and HOST parameters may be interchanged. No other keyword
parameters are permitted.
2.
If a command is entered from the system console (local or remote), the HOST
parameter should not be used; that site's host-id is used automatically.
7004 5208-000
Job Processing Procedures
3.
The special user-id OPERATOR indicates that the command applies to consoleinitiated jobs.
4.
Any command from the system console aocal or remote) pertains only to jobs with
a matching host-id regardless ofuser-id.
5.
DDP users submitting the HOLD command via a parameterized enter stream may
use HOST=$HOST to specify that the host-id of the command's submitter be used.
Examples
1.
Operator keyin:
HO JBQ,A,NE,WKSTN
Function requested:
All jobs subsequently initiated from workstations and placed in all scheduling
priority queues are to be deferred.
2.
Operator keyin:
HO JBQ,H,UID=WKSTA1
Function requested:
All jobs in the high scheduling priority queue associated with the workstation
user WKSTAl are to be deferred.
3.
Operator keyin:
HO JBQ,N,HOST=B
Function requested:
All jobs in the normal priority queue and associated with host B are to be
deferred. New jobs entered into this queue are not to be deferred.
(
Scheduling Deferred Jobs (BEGIN)
The BEGIN command reinstitutes the scheduling for execution of currently deferred
jobs, according to the command parameters specified. You can reinstitute scheduling
for all jobs in all queues or in a specific queue; for a specific job within a queue; for a
specific workstation user's jobs in all queues or a specific queue; or for a specific host's
jobs in all queues or a specific queue. Jobs remain deferred by a HOLD command
until you enter a BEGIN command to permit their rescheduling for execution.
7004 5208-000
4-25
Job Processing Procedures
Format
BEGINd
JBQ[~.=.~.~.~. H~ ~ti~~~ [i,:,~
,WKSl~
, ,,,,,,., "
:'~Iii.t:
[,UID=user·id][,HOST=host·id]
jobname
Positional Parameter 1
JBQ
Specifies that the command applies to the jobs in a job scheduling priority
queue, as further defined by PRE, HIGH, NOR, LOW or ALL, where:
ERE
HIGH
-
!l,OR
hOW
Permits the jobs in the preemptive scheduling priority queue to be
scheduled for execution.
(
Permits the jobs in the high scheduling priority queue to be scheduled
for execution.
Permits the jobs in the normal scheduling priority queue to be
scheduled for execution.
Permits the jobs in the low scheduling priority queue to be scheduled for
execution.
Permits the jobs in all scheduling priority queues to be scheduled for
execution.
jobname
Permits the particular job to be scheduled for execution. No further
parameters are permitted.
Keyword Parameters
QLD
Permits only jobs already in the scheduling priority queue defined in
parameter 1 to be scheduled for execution.
!l,EW
Permits newly entered jobs to be placed in the scheduling priority queue
defined in parameter 1 to be scheduled for execution.
If omitted, both old and new jobs are permitted to be scheduled for execution.
(See the HOLD command earlier in this subsection.)
4-26
7004 5208-000
(
Job Processing Procedures
DDP
Permits only distributed data processing jobs to be scheduled for execution.
LOCAL
-
Permits only locally entered jobs to be scheduled for execution.
RBP
Permits only jobs entered remotely (i.e., from a remote batch terminal) to be
scheduled for execution.
IrJI(STN
-
Note:
Permits only jobs either initiated from a workstation or using the II OPTION
ORI= or II OPTION MAS= job control statement to be scheduled for
execution.
All of the preceding keyword parameters may be interchanged.
UID=user-id
Permits all jobs associated with a particular workstation user-id to be
scheduled in the priority queue defined in parameter 1. The user-id is a oneto six-character alphanumeric identification that does not start with $Y$.
HOST=host-id
Permits all jobs associated with a particular host to be scheduled in the
priority queue defined in parameter 1. The host-id is one to four
alphanumeric characters.
Notes:
1.
The UID and HOST parameters may be interchanged, but no other parameters are
permitted.
2.
If a command is entered from the system console aocal or remote), the HOST
parameter should not be used; that site's host-id is used automatically.
3.
The special user-id OPERATOR indicates that the command applies to consoleinitiated jobs.
4.
Any command from the system console aocal or remote) pertains only to jobs with
a matching host-id regardless ofuser-id.
(
7004 5208-000
4--27
Job Processing Procedures
Examples
1.
Operator keyin:
BE MYJOB
Function requested:
The currently deferred job named MYJOB is permitted to be scheduled for
execution.
2.
Operator keyin:
BE JBQ,UID=WKSTA2
Function requested:
All currently deferred jobs in all scheduling priority queues associated with the
workstation user WKSTA2 are permitted to be scheduled for execution.
3.
(
Operator keyin:
BE JBQ,H,HOST=ABC
Function requested:
All currently deferred jobs in the high priority queue associated with the host
ABC may be scheduled for execution.
The BE command produces the same screen display as the RNIRV command (see
4.5.1).
Deleting Jobs or Symbionts from Scheduling Priority Queues (DELETE)
The DELETE command permits you to delete jobs or symbionts according to the
command parameters specified.
You can delete all jobs in all queues or in a specific queue; a specific job within a
queue; a specific workstation user's jobs in all queues or a specific queue; or a specific
host's jobs in all queues or a specific queue. Only those jobs residing in a scheduling
priority queue, and thus waiting to begin execution, can be deleted.
You can delete all queued symbionts or specific symbionts by queue slot ID number.
These ID numbers are provided in the MI SQ command display.
Note:
428
The DELETE command cannot be issued from an enter stream.
7004 5208-000
(
Job Processing Procedures
Format
DELETEA
JBQ',.~ )j[~DP ~
.t!IGH
. liOR
_,PR.•.•E.
LOW
:Att
LOCAL
RBP
WKSTN
) [,LOG]
[,UID=user·id][,HOST=host·id]
SQ,{id[id, .•• ,id]}
ALL
jobriame
Positional Parameter 1
JBQ,
Specifies the command applies to the jobs in a job scheduling priority queue,
as further defined by PRE, HIGH, NOR, LOW, or ALL, where:
(
ERE
HIGH
-
liOR
hOW
':iAUD
Deletes the jobs in the preemptive scheduling priority queue.
Deletes the jobs in the high scheduling priority queue.
Deletes the jobs in the normal scheduling priority queue.
Deletes the jobs in the low scheduling priority queue.
Deletes the jobs in all scheduling priority queues. When UID=user-id is
specified in the command, ALL is the default condition.
SQ,
Specifies the command applies to symbionts in the outstanding symbiont
queue, as further defined by id or ALL, where:
id
(
ALL
Is the queue slot ID number for the symbiont to be deleted. You obtain
this ID number by executing the MI SQ command.
Deletes all symbionts from the outstanding symbiont queue. The MI SQ
command lists all symbionts in the queue.
jobname
Specifies that a particular job is to be deleted from being scheduled for
execution.
7004 5208-000
4-29
Job Processing Procedures
Keyword Parameters
DDP
LOCAL
-
Deletes only distributed data processing jobs.
Deletes only locally entered jobs.
RBP
Deletes only jobs entered remotely (i.e., from a remote batch terminal).
WKSTN
-
Deletes only jobs either initiated from a workstation or using the II OPTION
ORI= or II OPTION MAS= job control statement.
Note:
All of the preceding keyword parameters may be interchanged.
UID=user-id
Deletes all old jobs associated with a particular workstation user-id in the
scheduling priority queue defined in parameter 1. Jobs subsequently entered
with this user-id are not deleted. The user-id is a one- to six-character
alphanumeric identification that does not start with $Y$.
c
HOST=host-id
-
Deletes all old jobs associated with a particular host in the scheduling
priority queue defined in parameter 1. Jobs subsequently entered with this
host-id are not deleted. The host-id is one to four alphanumeric characters.
Notes:
1.
The UID and HOST parameters may be interchanged, but no further parameters
are permitted.
2.
If a command is entered from the system console (local or remote), the HOST
parameter should not be used; that site's host-id is used automatically.
3.
The special user-id OPERATOR indicates that the command applies to consoleinitiated jobs.
4.
Any command from the system console (local or remote) pertains only to jobs with
a matching host-id regardless of user-id.
LOG
Specifies that the job log is printed for all jobs deleted. If omitted, the log is
not printed.
4-30
7004 5208-000
(
(
Job Processing Procedures
Examples
1.
Operator keyin:
DE JBQ,H,HOST=CDE
Function requested:
All jobs residing in the high scheduling priority queue and originating from host
CDE are to be deleted.
2.
Operator keyin:
DE JBQ,A,UID=WKSTA1,LOG
Function requested:
All jobs in all scheduling priority queues associated with the workstation user
WKSTAl are deleted and their logs are printed. A system message tells you the
number of jobs deleted.
Displaying Jobs in Scheduling Priority Queues (DISPLAy)
The DISPLAY command permits you to display the contents of any or all job
scheduling queues on the console workstation or console screen as specified by
command parameters. You can display all jobs in all queues or in a specific queue; a
specific job within a queue; a specific workstation user's jobs in all queues or a specific
queue; or a specific host's jobs in all queues or a specific queue. All requested jobs
within the specified queue are displayed. Jobs in a deferred status (HOLD command)
are displayed with parentheses around the job name. When all queues are requested,
PRE is displayed first, followed by HIGH, then NOR, then LOW. Ifno jobs are found
in the queue you request, a system output message is displayed stating that condition.
A system output message is displayed prior to the list of jobs. The message specifies:
..
Whether the request was for LOCAL, RBP, DDP, WKSTN, or for all jobs
(QUEUED)
..
The user-id and host-id
..
The priority of the queue display to follow
..
Whether a hold local (HL), hold RBP (HR), hold workstation (HW), or hold DDP
(HD) sta~us is in effect for that queue
7004 52m3·000
4-31
Job Processing Procedures
Jobs are displayed in three different formats, depending on the parameters you
specify on the DISPLAY command. In all cases, jobs in hold status are displayed in
parentheses.
•
Two jobs per line
If the DDP parameter is specified, the host-id is included in the following format:
jobname: host-id/user-id
•
jobname: host-id/user-id
Three jobs per line
This format is the most common and is used when you specify the HOST
parameter or the WKSTN parameter, or the command is from the system console
(local or remote) with no other parameters. The format is:
jobname: user-id
jobname: user-id
•
(
jobname: user-id
Five jobs per line
If there can be no user-id (LOCAL or RBP) or if there is only one user-id to be
selected (UID= or DI JBQ from workstation), the jobs are displayed in the
following format:
jobname
Note:
jobname
jobname
jobname
jobname
The DISPLAY command cannot be issued from an enter stream.
Format
DISPLAY'JBQ'!~H) [I!:~~
[,UID=user-id][,HOST=host-id]
(
Positional Parameter 1
JBQ
Specifies the command applies to the jobs in a job scheduling priority queue,
as further defined by PRE, HIGH, NOR, LOW, or ALL, where:
.ERE
Displays the jobs in the preemptive scheduling priority queue.
HIGH
-
4-32
Displays the jobs in the high scheduling priority queue.
7004 5208-000
Job Processing Procedures
N.OR
Displays the jobs in the normal scheduling priority queue.
hOW
:)~illili
Displays the jobs in the low scheduling priority queue.
Displays the jobs in all scheduling priority queues.
Keyword Parameters
DDP
Displays only distributed data processing jobs.
LOCAL
-
(
Displays only locally entered jobs.
RBP
Displays only jobs entered remotely (i.e., from a remote batch terminal).
WKSTN
-
Displays only jobs either initiated from a workstation or using the
II OPTION ORI= or II OPTION MAS= job control statement.
Note:
All of the preceding keyword parameters may be interchanged.
UID=user- id
Displays all old jobs associated with a particular workstation user-id in the
scheduling priority queue defined in parameter 1. Jobs subsequently entered
with this user-id are not displayed. The user-id is a one- to six-character
alphanumeric identification that does not start with $Y$.
HOST=host- id
Displays all jobs associated with a particular host and residing in the
scheduling priority queue defined in parameter 1. The host-id is one to four
alphanumeric characters.
(
Notes:
1.
The UID and HOST parameters may be interchanged, but no further parameters
are permitted.
2.
If a command is entered from the system console aocal or remote), the HOST
parameter should not be used; that site's host-id is used automatically.
3.
The special user-id OPERATOR indicates that the command applies to consoleinitiated jobs.
4.
Any command from the system console aocal or remote) pertains only to jobs with
a matching host-id regardless of user-id.
7004 5208-000
~33
Job Processing Procedures
Examples
1.
Operator keyin:
DI JBQ
Function requested:
Display all jobs in all scheduling queues.
Screen display:
JC23 NO
JC23 NO
*******
QUEUED
QUEUED
QUEUED
JOBS WITH PREEMPTIME PRIORITY
JOBS WITH HIGH
PRIORITY
PRIORITY
JOBS WITH NORMAL
(JOBABC)
Explanation:
The job JOBABC is the only job presently in the system. It is in the normal
priority queue and the parentheses indicate that the job is being held.
2.
Operator keyin:
DI JBQ,N,LO,RBP
Function requested:
Display all locally and remotely entered jobs in the normal scheduling priority
queue.
3.
Operator keyin:
(
DI JBQ,UID=WKSTA2
Function requested:
Display all jobs in all scheduling priority queues that are associated with the
workstation user WKSTA2.
4-34
7004 5208-000
Job Processing Procedures
Changing a Job Scheduling Priority (CHANGE)
The CHANGE command changes the scheduling priority ofa specific job. If you place
a deferred job into a new (changed) scheduling priority queue, the job retains its
deferred status. Likewise, if you place a job into a queue that is under the influence of
a HOLD NEW command, it too will become deferred. The job is put on the end of the
new queue; it is the last examined for scheduling for execution in that queue.
Format
CHANGEAjObname'~PRE
l
!i IGH
NOR
LOW
Positional Parameter 1
(
jobname
\
Specifies the particular job to have its scheduling priority changed.
Positional Parameter 2
ERE
HIGH
-
NOR
hOW
Moves the specified job into the PRE scheduling priority queue.
Moves the specified job into the HIGH scheduling priority queue.
Moves the specified job into the NOR scheduling priority queue.
Moves the specified job into the LOW scheduling priority queue.
Example
Operator keyin:
(
\.
CH JOBABC,H
Function requested:
Moves JOBABC from a previously assigned (via the job control stream, command
entry for running the job, or NOR by default) scheduling priority queue into the
HIGH scheduling priority queue. The following message appears on your screen:
CH OF JOB JOBABC
7004 5208-000
4-35
Job Processing Procedures
4.5.3. Job Execution
When a job is being executed, you can control the processing of that job through job
execution commands. These commands allow you to:
•
Suspend a job under execution
•
Restart a job that has been suspended
•
Raise or lower the switching priority level of a job being executed
Suspending a Job in Progress (PAUSE)
The PAUSE command suspends processing of a job. You may enter the command at
any time, at a workstation or at the system console, and job processing suspends
immediately or at the completion of a specified job step. If the job is between job
steps, PAUSE (without ajob-step-number parameter) takes effect at the beginning of
the next job step. The PAUSE command permits you to mount a new volume on a
tape, disk, or diskette drive, replace paper on the printer, or place more cards in the
card reader. The suspended job is reactivated by the GO command. Furthermore, a
suspended job cannot be cancelled until it is reactivated with the GO command.
Note:
(
Ajob paused by the console operator cannot be reactivated with a GO
command from the workstation user. It can only be reactivated by the console
operator.
Format
PAUSE~jobname[,job-step-number]
Positional Parameter 1
jobname
Specifies the name of the job whose processing is suspended.
(
Positional Parameter 2
job-step-number
Specifies the number of a job step that must complete before processing is
suspended. This is an optional entry.
Examples
1.
Operator keyin:
PA JOBA
Function requested:
Suspends JOBA processing immediately.
4-36
7004 5208-000
Job Processing Procedures
2.
Operator keyin:
PA JOBA,02
Function requested:
Suspends JOBA following completion of the second job step.
Reactivating a Suspended Job (GO)
The GO command reactivates ajob suspended by the PAUSE command or by job
control operations. Job control suspends processing of ajob when it issues instructions
to mount a new volume on a tape, disk, or diskette drive. The GO command also is
required as a response to a message from the system preceded by an asterisk (*).
(
Jobs started at a workstation and paused at the system console can be restarted only
with a GO command at the system console. A GO command at a workstation on a job
that was paused at the system console results in an NAK (negative acknowledgment)
error message.
Format
GOAjobname[,nn]
Positional Parameter
jobname
Specifies the job to be reactivated after execution was temporarily
suspended.
nn
(
Is the number of the message requiring the GO command. This specification
allows multitask jobs to suspend and start tasks other than the primary
ones.
Example
Operator keyin:
GO JOBA
Function requested:
Reactivate job processing for the suspended job named JOBA
7004 5208-000
4-37
Job Processing Procedures
Changing a Job Switching Priority (SWITCH)
The SWITCH command changes the switching priority level for ajob under execution.
The switching priority level is changed for either the currently executing job step or
for the current job step and all subsequent job steps. If the priority level is changed
for the current job step only, any subsequent job step executes under the priority
established for it (via II EXEC job control statement or default to the lowest level
established at SYSGEN) unless changed by another SWITCH command. A job
assigned a higher switching priority level has priority over lower switching priority
level jobs for control of the central processor. If a job is changed to a higher switching
priority level than another job currently being executed, the lower switching level job
will often be processed slower than the higher switching level job.
The number of switching priority levels a job can be raised or lowered is governed by
the number of switching priority levels established at system generation time
(maximum 60 levels). Switching priority levels are from 1 to n, where 1 is the highest
priority level and n is the lowest.
(
When you change any job's switching priority, all tasks ofthatjob retain the same
switching priority relative to each other; therefore, if a job's task exceeds the upper or
lower switching priority limit, all the job's tasks move only by the number of priority
levels that the highest or lowest priority task can be moved within the switching
priority limits.
Format
~ITCHAjObname,{+number-of-prioritY-leVelS}[,ALL]
-number-of-priority-levels
Positional Parameter 1
jobname
Specifies the name of the job whose task switching priority is changed_
Positional Parameter 2
(
+number-of-priority-levels
Specifies the number of switching priority levels a job is raised.
-number-of-priority-levels
Specifies the number of switching priority levels a job is lowered.
Positional Parameter 3
ALL
Indicates that the priority to which the job is switched is in effect for all
subsequent job steps. If omitted, the priority is only for the current job step.
\.
4-38
7004 5208-000
Job Processing Procedures
Example
Operator keyin:
SW PAYJOB,-5
Function requested:
Lowers the switching priority level of the currently executing PAYJOB job step
by five queues. The switching priority remains changed for the duration of the
job step.
4.5.4. Job Termination
(
,
Job termination commands permit you to terminate the processing of a job or
symbiont, as defined by the command parameters.
Canceling a Job in Progress (CANCEL)
The CANCEL command immediately halts all processing of a job or symbiont. The
CANCEL command may be issued at any time during processing of a job and results
in the immediate termination of the job step being executed at the time the CANCEL
command is given, plus any subsequent job steps scheduled for the job. The job run
library file for the job also is deleted.
Format
~NCEL~ljobn~e
[{Oil
symblont,S1
N
synnnn,S
sy(did),S
sy
(
Positional Parameter 1
jobname
Specifies the name of the job whose processing is immediately terminated
and whose job run library file is deleted.
synnnn
Is the name ofthe symbiont sending the message. This six-character name is
the two-character symbiont identification followed by a four-digit binary job
number inserted at task initiation.
symbiont
Specifies the eight-character symbiont name.
7004 5208-000
4-39
Job Processing Procedures
sy
did
Specifies the two-character ID used to call the symbiont to be terminated.
Is the device address.
Positional Parameter 2
D
Specifies that a dump is to be taken when the job terminates, regardless of
the dump option specified in its job control stream.
N
Specifies that no dump is taken when the job terminates, regardless of the
dump option specified in its job control stream.
S
Specifies that the name specified in positional parameter 1 is the name of a
symbiont.
(
If omitted, the job control dump options remain in effect. Positional parameter 2
must be specified when a symbiont is cancelled.
Examples
1.
Operator keyin:
CA JOBA,D
Function requested:
Terminates JOBA immediately, deletes the JOBA run library file, and provides a
JOBAdump.
2.
Operator keyin:
CA SU,S,N
(
Function requested:
Terminates the system utility symbiont immediately without a dump.
(
\
440
7004 5208-000
Job Processing Procedures
Soft Cancel of a User's Job (CJ)
The CJ command delays the standard cancel procedure until the job is executing
under "normal" job conditions. This allows the operator to cancel a job without
compromising a MIRAM file. Normal job execution requires:
•
Execution under the job's key
•
No wait flags set
•
Not executing in external code
If this command does not terminate ajob, the CANCEL command can be used. When
CJ is issued, an unknown period of time may pass before the job actually cancels (for
instance, the job may have been paused or yielded when the command was executed).
A dump requested at the time of the command may not reflect the status of the
command at that time; instead, it will reflect the job status when the cancel becomes
effective.
Format
CJA(jObn~e
[{D~
symblont,S1
synnnn,S
N
sy(did),S
sy
Positional Parameter 1
jobname
Specifies the name of the job that will be terminated the next time it is
executing under normal job conditions.
symbiont
Specifies the eight-character symbiont name.
(
synnnn
Is the name of the symbiont sending the message. This six-character name is
the two-character symbiont identification followed by a four-digit binary job
number inserted at task initiation.
sy
Specifies the two-character ID used to call the symbiont to be terminated.
did
Is the device address.
s
70045208-000
Identifies the parameter entry as the name of a symbiont.
441
Job Processing Procedures
Positional Parameter 2
D
Specifies that a dump is to be taken at the time when the job is effectively
canceled, regardless of the dump option specified in its job control stream.
N
Specifies that no dump is taken when the job terminates, regardless of the
dump option specified in its job control stream.
Examples
1.
Operator keyin:
CJ JOBA,D
Function requested:
(
Terminates JOBA as soon as JOBA is executing under normal conditions, deletes
the JOBA run library file, and provides a JOBA dump.
2.
Operator keyin:
CJ JOBA,N
Function requested:
Terminates JOBA as soon as JOBA is executing under normal conditions, deletes
the JOBA run library file, and does not provide a JOBA dump.
Stopping Execution of a Dump (END)
The END command terminates execution of a cancel or end-of-job dump for a
particular job.
Format
l
(
ENDADUMP'jjObn~e
symbl0nt,S
sy,S
sy(did),S
Positional Parameter 1
DUMP
Specifies that the execution of a dump is to stop.
Positional Parameter 2
jobname
Specifies the name of the job whose cancel or end-of-job dump you want
stopped.
4-42
7004 5208-000
Job Processing Procedures
symbiont
Specifies the eight-character symbiont name.
sy
Specifies the two-character ID used to call the symbiont to be terminated.
did
Is the device address.
Positional Parameter 3
s
Specifies that the name specified in positional parameter 1 is the name of a
symbiont.
Example
Operator keyin:
EN DUMP,JOBA
Function requested:
Terminates the execution of the dump being taken for JOBA
Terminating a Job (STOP)
The STOP command terminates a specific job at the end of the current or specified job
step. This command provides for orderly termination of the job.
Format
~OP~jobname[,job'step'number]
Positional Parameter 1
(
jobname
Specifies the job whose processing is terminated in an orderly sequence.
Positional Parameter 2
job-step-number
Specifies the number of a job step that must complete before processing is
suspended. This is an optional entry.
7004 5208-000
4-43
Job Processing Procedures
Examples
1.
Operator keyin:
ST JOSC
Function requested:
Terminates JOBC at the end of the currently executing job step.
2.
Operator keyin:
ST JOSC,02
Function requested:
Terminates JOBC at the end of job step 02.
4.6. Selected Occasion Operator Commands
During the course of processing a job, you may be required to enter system-oriented
commands to obtain information or make changes not involved with the execution of a
particular job. These commands enable you to:
4-44
•
Display an area of main storage
•
Display information on active jobs and symbionts, current system IJO device
status, and outstanding requests and commands
•
Clear the console workstation of all but outstanding output messages
•
Change the system time or date
•
Control software-detected hardware error logging
•
Set an IJO device down or up as required for normal maintenance or device
malfunction
•
Read the volume serial number of a mounted disk or tape volume
•
Display the status of jobs in the system
•
Dump contents of main storage
•
Set the $Y$DUMP file to an unlocked condition
•
Set one or more blocks of main storage up or down
•
Terminate system activity
70045208-000
(
Job Processing Procedures
•
Specify resource management
•
Verify the volume table of contents (VTOC)
•
Set viewing privileges
The commands enabling you to perform these functions are described in the following
subsections. Commands required to control interactive services, data communications,
and system utility functions are described in Sections 5, 6, and 7.
4.6.1. Displaying Portions of Main Storage (DISPLAY)
The DISPLAY command displays selected areas of main storage at the console
workstation or console. You usually enter the command when your system
administrator needs a job address displayed for program debugging purposes.
QlSPLAYAaddr[,jobname]
Positional Parameter 1
addr
Is a hexadecimal number used for a specific (absolute) main storage address
or a job-relative main storage address. Ajob-relative address is identified by
the job name; otherwise, an absolute address is displayed.
Positional Parameter 2
jobname
Identifies the job name of the job in main storage whose relative address is
displayed.
When no parameter 2 is entered, the address entered in positional
parameter 1 is an absolute address.
(
After you enter DISPLAY to load the display symbiont (DI), the following output
message appears on the console workstation or console:
addr[JOBNAME] contents-of-selected-addr Y,N,NXT?
where:
addr
Is the address of the main storage location being displayed, in hexadecimal.
JOBNAME
Identifies the address being displayed as a job-relative address and
identifies the job region by the job's name. If JOBNAME is not displayed,
the address being displayed is an absolute address.
contents-of-selected-addr
Is the hexadecimal representation of the contents of the selected main
storage address.
70045208-000
4-45
Job Processing Procedures
y
Is a message response to display the next sequential main storage location.
N
Is a message response to terminate the display symbiont.
NXT
Is a reminder that you can display another nonconsecutive main storage
location without recalling the display symbiont by responding to this output
message with the solicited input message:
addr[,jobname]
where:
addr
Is the address of the main storage location to be displayed, in
hexadecimal.
(
jobname
Identifies the job name of the job whose relative address is to be
displayed.
When there are no more addresses to display, terminate the display symbiont by
responding to the last display message with an N for none.
4.6.2. Displaying System Information (MIX)
The MIX command displays tables of different aspects of system information.
Format
p
.!llXlI DA [{jObn~e
symbIont-nameD
(
P
c/ca/caaD
VI [{did
SQ
SI
DS[,did]
SC
FR
MM
EN
EL
HF (models 10/15/20 only)
446
7004 5208-000
Job Processing Procedures
Positional Parameter 1
DA
Displays the following information on the console workstation or console
screen for the job or symbiont you specify (positional parameter 2) or for all
active jobs and symbionts when you omit positional parameter 2:
(
II
Job name or symbiont name
II
Job slot number; 0 for symbiont
•
Priority
•
Allocated device numbers
•
Allocated device types
•
Volume serial number or user identification
VI
Displays the following information for the devices you specify in positional
parameter 2 that have a mounted volume, or for all devices having a
mounted volume, if you omit positional parameter 2:
•
Device address of each device
•
Volume serial number
•
Mode setting of tape devices (U26 and U28 only)
SQ
Displays a list of outstanding symbiont requests, including unprocessed
queued operator commands. (These are console commands that could not be
processed immediately.) The displayed list includes a queue slot ID number
that can be used to delete items from the outstanding symbiont queue (see
DELETE command).
SI
Displays system information, including supervisor name, release-id, date,
time, RES device address, RUN device address, system reader (RDR) device
address, spool (SPL) device addres/O, and total available main storage in
decimal.
70045208-000
447
Job Processing Procedures
os
SC
FR
MM
Displays the following information on the console workstation or console
screen for the device you specify in positional parameter 2, or for all devices
in the system if you omit positional parameter 2 (use MI DS to determine if
a diskette drive is available when the device requires maintenance; when the
drive is in use, an I/O error occurs if its door is opened):
•
Device address of each device
•
Whether the device is up or not (Y or N)
•
Whether the device is available or not (Y or N)
•
Whether the device is sharable or not (Y or N)
•
Job numbers of all the jobs to which the device is allocated
(
Displays the name, address, and decimal size of each shared code module
currently residing in main storage.
Displays the address and decimal size of all regions currently unused in
main storage.
Displays the type, name, address, and decimal size of every main storage
region. The following types are displayed:
•
FREE
Free region
•
JOB
Job region
•
JOB SCHD Job scheduler
•
SYMBIONT Symbiont (RUN processor, ICAM, etc.)
•
RESERVED Region reserved for a job just scheduled
•
BUF POOL
Dynamic buffer pool. These storage pools are internally
subdivided to provide dynamically allocated main storage for
system software.
Note:
See Section 8 regarding disk cache storage allocations.
(
7004 5208-000
Job Processing Procedures
41
SHR CODE
Shared code. When shared code occupies its own main storage
region, you display it by using either the SC or the :MM
parameters. When shared code is part of a dynamic buffer
pool, you display it by using the SC parameter only.
41
DISABLED
Not available. The region is either temporarily or permanently
disabled. A region is temporarily disabled when it is in the
process of being changed from one type to another (e.g., from
SYM to FREE). This temporary condition exists for no more
than a few seconds. A region is permanently disabled when a
system error, such as a parity error, prevents the termination
and clearing out of a region.
41
DOWN
Down. The region is set down as the result of either an
operator command or too many recoverable main storage
errors occurring in that region.
(
EN
Terminates the MIX function currently in progress.
EL
Displays error log information, including error logging functions that are in
effect, percentage of error records used, and number of records remaining.
HF
Displays the enabled or not enabled status of various model 10115/20
hardware features (this parameter is not supported on other models). The
displayed response indicates the model number (10,15, or 20) and whether
the following features are enabled (Y) or not enabled (N): bypass cache
(BYF), floating point processor (FPP), instruction cache (ICM), and operand
cache sets 1 through 4 (OC1 - OC4).
Positional Parameter 2
jobname
Used with the DA parameter to identify ajob name for which information is
desired. If you omit this parameter, information for all active jobs and
symbionts is displayed.
(
symbiont-name
Used with the DA parameter to identify a symbiont name for which
information is desired. If omitted, information for all active jobs and
symbionts is displayed.
7004 5208-000
4-49
Job Processing Procedures
did
Used with the VI and DS parameters to obtain status information for a
device or group of devices. One, two, or three characters may be used. Key in
three characters to specify the exact device address of the device to be
displayed. If you key in two characters, the group of devices whose device
addresses start with those two characters is displayed. If you key in one
character, information is displayed about all devices whose addresses begin
with that character. If you omit this parameter, the status of all the devices
in the system is displayed.
caa
Used with the VI parameter to indicate a device or group of devices. C
specifies the channel; a, the address. One, two, or three characters may be
used, as with did.
Examplel
(
Operator keyin:
MI DA
Function requested:
Display information pertaining to all active jobs and symbionts.
Screen display:
JOB NAME
RC$$IS00
JOB NO
PRI
o
o
DEV
312
TYPE
3560 WRKSTN
VSN/UID
LKT
The symbiont RC$$ISOO is recognized as a symbiont by a job slot number of o. Its
priority is 0, and it is allocated to device number 312, which is a 3560
workstation. LKT is the user-id.
Example 2
Operator keyin:
MI SI
Function requested:
Display system information.
4-50
7004 5208-000
(
Job Processing Procedures
Screen display:
SUP204
14. OS/3 91/11/01
ROR=332 RES=103
13:34:04 USABLE MEMORY=
RUN=103 SPL=103
971,520
Supervisor SUP204 is running under release 14.0. The date and time is followed
by the available main storage, which is 971 ,520 bytes. The reader device address
is 332, the RES device address is 103, the RUN device address is 103, and the
spool device address is 103.
Example 3
(
Operator keyin:
MI os
Function requested:
Display information pertaining to all devices in the system.
Screen display:
OVC
xxx
xxx
xxx
xxx
xxx
(
UP
YIN
YIN
YIN
YIN
YIN
AVL
YIN
YIN
YIN
YIN
YIN
SHR
YIN
YIN
YIN
YIN
YIN
USERS
0, .•• ,n
0, .•• ,n
0, ••• ,n
0, ... ,n
0, ... ,n
The DVe column contains the device addresses of all the devices in the system.
The next three columns tell you whether the device is up, available, and sharable.
Also provided are the number of users of each device and the job slot numbers of
all the jobs to which the device is allocated.
70045208-000
4-51
Job Processing Procedures
4.6.3. Reconstructing Console Display (REBUILD)
The REBUILD command clears all information from the console workstation, then
restores the job number header lines and rewrites all outstanding question and action
request output messages on the console workstation screen. All displays other than
unanswered questions and action requests are lost.
Format
REBUILD
Positional Parameters
No positional parameters are required for the REBUILD command.
Note:
The REBUILD command does not restore thejob number header lines on the
console screen.
(
4.6.4. Setting Simulated Day Clock (SET CLOCK)
The SET CLOCK command resets the time of day in the system-simulated day clock;
it updates the hardware clock. The date and time are changed automatically at
midnight of each day.
Format
(
~T6CLOCK,hh:mm:ss
Positional Parameter 1
CLOCK
-
Sets the simulated day clock and hardware clock to the time specified in
positional parameter 2.
'
Positional Parameter 2
(
hh:mm:ss
Specifies the time to set the simulated day clock and hardware clock as
follows:
hh
mm
Specifies hours (00 through 99).
Specifies minutes (00 through 59).
ss
Specifies seconds (00 through 59).
4-52
7004 5208-000
Job Processing Procedures
4.6.5. Setting Date Field (SET DATE)
The SET DATE command resets the calendar date in the system information block
date field, updates the hardware clock, and resets the job date for every job currently
in main storage (except those jobs containing a II SET DATE job control statement).
The date and time are changed automatically at midnight of each day.
Format
.§g,Tt.DATE,yy/mm/dd[ ,yyddd]
Positional Parameter 1
DATE
Changes the calendar date in the system information block date field, the
hardware clock, and in the preambles for current jobs to the date specified in
positional parameter 2.
Positional Parameter 2
yy/mm/dd
Specifies the date to be used for the calendar date in the system information
block date field, the hardware clock, and job preambles, as follows:
yy
Specifies year (00 through 99).
mm
Specifies month (01 through 12).
dd
Specifies day (01 through 31).
Positional Parameter 8
yyddd
Specifies the ordinal date, where yy is the year (00 through 99) and ddd is
the day of year (001 through 366). This date is maintained in a separate part
of the system information block and is used by data-management routines
that check the label fields.
(
If omitted, this field in the system information block is set to the ordinal date
corresponding to the yy/mmldd date specified in positional parameter 2.
70045208-000
4-53
Job Processing Procedures
4.6.6. Setting Error Log (SET ELOG)
The SET ELOG command should not be used without first consulting your customer
engineer. Communications, I/O device, machine check, and I/O termination record
error logging can be turned on or off when you enter specified combinations of the
command and parameters. The IPL procedure automatically turns on error logging
and all error logging functions. Any changes to this all-on condition that you enter are
lost when the system is reloaded.
Format
.§gTAELOG, {ON } , ALL
.QE.F
fQMM
.M£HK
10
lE,RM
g,OG
MTK
(
,M,§,E
did
factor,{RSTK}
MSE
Positional Parameter 1
ELOG
-
Specifies that the PIOCS error logging processor is to be set to some
condition.
Positional Parameter 2
ON
Turns on the function oflogging errors. When parameter 3 is included, error
logging is turned on for that parameter specification only.
OFF
Turns off the logging of errors for the function specified by parameter 3.
factor
Specifies a one- to three-character decimal value that is used to redefine
main storage error (MSE) or retry stack error (RSTK) limits. The error is
suppressed when its established limit is exceeded. The factor value entered
is multiplied by 32 to redefine the millisecond time factor (F) in the error
limit formula:
F*S:E
4-54
7004 5208-000
(
Job Processing Procedures
where:
F
Is the millisecond time factor to be redefined.
S
Is the size or number ofMSE or RSTK errors.
E
Is the elapsed time (in milliseconds) since the last interrupt of the same
type.
When F times S is greater than E, the reported type of suppressible machine
error is disabled and a message to that effect is displayed on the console
workstation or console screen.
(
Positional Parameter 3
Is valid only when ON is specified in parameter 2. ALL specifies that all
loggable errors (i.e., communications, machine check, I/O device, and I/O
termination record error logging) are to be logged for all devices in the
system.
COMM
-
MCHK
-
Turns on or off communications error logging as directed by parameter 2.
Turns on or off machine check error logging as directed by parameter 2.
10
Turns on or off all I/O device error logging as directed by parameter 2.
TERM
-
Turns on or off all I/O termination record error logging as directed by
parameter 2.
CLOG
(
-
Turns on or off channel logout error logging as directed by parameter 2.
RSTK
-
Is valid for all parameter 2 specifications and has the following functions:
ON
Turns on retry stack error logging.
OFF
Turns off retry stack error logging.
7004 5208-000
4-55
Job Processing Procedures
factor
Specifies that the factor specified in parameter 2 is to be used in the
algorithm for establishing retry stack error limits.
MSE
Is valid for all parameter 2 specifications and has the following functions:
ON
Turns on main storage error logging.
OFF
Turns off main storage error logging.
factor
Specifies that the factor specified in parameter 2 is to be used in the
algorithm for establishing main storage error limits.
did
Represents a device address as one, two, or three hexadecimal characters
specifying a channel, subchannel, and device, respectively. A did can be used
with any parameter 2 specification.
•
If did is specified as one character, all devices on that channel are
directed by the parameter 2 specified.
•
If did is specified as two characters, all devices on that channel and
subchannel are directed by the parameter 2 specified.
•
If did is specified as three characters, a specific device on that channel
and subchannel is directed by the parameter 2 specified.
If omitted, the error logging condition for each parameter 3 remains unchanged,
(i.e., turned on or off as previously set). Thus, if you omit parameter 3 and enter
the command SET ELOG,ON, the error logging function is turned on, but only
for those parameter 3 specifications previously turned on.
Operator Considerations
(
When the ELOG file ($Y$ELOG) is almost full, the system displays the message:
LOG FILE IS NEARLY FULL
At this time you should run the system-supplied ONUERL program (Appendix A).
The ELOG file can become completely full only if the ONUERL program was not run
when the nearly full message was displayed. If the ELOG file fills up, ELOG asks you
whether you want to turn off error logging or wrap around to the beginning of the log
file.
4-56
7004 5208-000
Job Processing Procedures
When the message
LOG FILE IS FULL W(RAP) OR O(FF)
appears, respond using the solicited message format:
where:
o
Turns off the PIOCS error logging processor.
Informs the PIOCS error logging processor to wrap around the log file and
continue logging.
(
If ONUERL has already been run, respond with the letter W. If ONUERL has not
been run, enter 0 to turn off logging, then initiate ONUERL.
Note:
It is recommended that you run ONUERL when the message LOG FILE IS
NEARLY FULL is displayed. Allowing the ELOG file to wrap around causes
loss of potentially valuable data.
4.6.7. Discarding System Messages (FLUSH)
The FLUSH command allows you to discard system messages queued for delivery at
your workstation. You can discard all queued messages or only those with a specified
message prefix.
Format
FLUSH{*ALL
}
mss-prefix
(
Parameters
*ALL
Discards all queued messages.
mss-prefix
Discards only messages with this prefix.
4.6.8. Setting Physical Unit Blocks (SET 10)
The SET 10 command allows you to set specific bits in the physical unit blocks (PUB),
which define operational characteristics and assignments of I/O devices. There is one
physical unit block, comprising a three- or four-character did (device address), for
each physical device in your system. You must set all devices or subsystems DOWN
before attempting operation on the device, such as forms loading or changing ribbon;
or in case of malfunction, before turning the device off. This is required if the
70045208-000
4-57
Job Processing Procedures
processor is to continue operation with other peripheral devices while the subject
device undergoes isolated operations. Before performing a procedure or turning power
off for the device, key in SET IO,did,DOWN. After the offline procedure completes or
after turning on power independently of the processor, key in SET IO,did,UP.
Note:
The system automatically sets all devices or subsystems not online during IPL
time to not available (NA). After IPL, any attention interrupt from a device
causes that device to be set available (AV).
Format
SETllIO,did, AV
CON
DOWN
EON
EOF
(
£E.A, type· code
l1QME
NA
HQ,SHARE
HQ.WRITE
RDR
gARE
llPE, type-code
UP
WRITE
Positional Parameter 1
(
10
Specifies the change is made in the device address specified by positional
parameter 2.
Positional Parameter 2
did
Specifies a one- to four-character numeric field identifying the device
address to be changed (device addresses are usually attached at a visible
location on the device cabinet) as follows:
4-58
ALT
Alternate console specified in SYSGEN
caa
Alternate console specified by channel (c) and address (aa)
ORG
Original (hardware) console
100
SYSRES integrated disk
DDD
Indirect printer
nnn
Specific hardware device (channel/controller/device address)
70045208-000
(
Job Processing Procedures
nn.
All devices on the channeVcontroller addresses specified
n.
All devices on the channel address specified
Note:
Positional parameter 2 DDD can be associated only with positional
parameter 3 UP or DOWN.
Positional Parameter 3
AV
Specifies the device identified by positional parameter 2 is recognized by the
system and available for assignment to user jobs.
CON
(
DOWN
-
Designates the specified device as the current console.
Specifies the device identified in positional parameter 2 is not to be
considered available for assignment to user jobs, although the device is
recognized by the system.
The DOWN[,n] format is applicable only if the device identified in positional
parameter 2 is an indirect printer. The n is a single-digit number indicating
the indirect printer PUB on which the SET 10 command is to be performed.
If n is omitted, the first indirect PUB is assumed.
EON
EOF
Turns on error logging for the specified device.
Turns off error logging for the specified device .
.E.5.A, type· code
Modifies the feature bytes of the device specified in positional parameter 2,
where type-code is a one- to four-character field specifying the device, its
options, and features desired. See the Job Control Programming Reference
Manual (UP-9984) for the definition of type and feature codes.
HOME
NA
Synchronizes the operating system with the physical paper position of an
0768, 9200, or 9300 printer during a home operation.
Specifies the device identified by positional parameter 2 is not recognized by
the system; it is not available for assignment to user jobs.
NOSHARE
-
Forbids allocation of the device specified in positional parameter 2 to more
than one program simultaneously.
NOWrite
-
7004 5208-000
Specifies the device identified by positional parameter 2 (did) is write
protected by the system.
4-59
Job Processing Procedures
EQR
Assigns the new did specified in positional parameter 2 as the system card
reader.
SHARE
-
Permits the device specified in positional parameter 2 to be shared by more
than one program simultaneously.
llPE,type-code
Modifies the type bytes of the device specified in positional parameter 2,
where type-code is a one- to four-character field specifying the device, its
options, and features desired. See the Job Control Programming Reference
Manual (UP-9984) for the definition oftype and feature codes.
UP
Specifies the device identified in positional parameter 2 is considered
available for assignment to user jobs. The device remains recognized by the
system.
(
The UP[,n] format is applicable only if the device identified in positional
parameter 2 is an indirect printer. The n is a single-digit number indicating
the indirect printer PUB on which the SET 10 command is to be performed.
If n is omitted, the first indirect PUB is assumed.
WRITE
-
Specifies the device identified by positional parameter 2 (did) is removed
from its write protected state.
(
Notes:
1.
For more information on the indirect printer, see the Installation Guide,
70045505.
2.
Positional parameter 4 is required in order to set a device to available, not
available, down, or up when your system is configured with stability monitoring.
Positional Parameter 4
o
Indicates that the device status change specified in positional parameter 3
(AV, DOWN, NA, or UP) is required for operational reasons (for example, to
set a device down to change forms or ribbons).
H
Indicates that the device status change specified in positional parameter 3
(AV, DOWN, NA, or UP) is required for hardware reasons (for example, to
set a device to not available because the hardware is malfunctioning).
4-60
7004 5208-000
(
Job Processing Procedures
Example
Operator keyin:
SET 10,321,DOWN
Function requested:
Set the device identified by device number 321 down. Device 321 is a diskette. No
screen display results after this command is issued. To determine if the device is
now unavailable to user jobs, issue aMI DS command (see 4.6.2).
4.6.9. Reading a Mounted Volume Serial Number (AVR)
(
The AVR command initiates reading the volume serial number of a premounted
prepped disk pack, diskette, or magnetic tape volume and storing it in the device
physical unit block.
Format
AVR~did[,did]r,did]
Positional Parameters 1 through 3
did
Specifies the device addresses for the volumes to be recognized.
4.6.10. Displaying Job Status (DISPLAY JS/SY)
(
The DISPLAY JS command displays the status of jobs in the system at the console
workstation or console. You can display the status of a specific job or all jobs in main
storage, a specific job in a scheduling priority queue, a job being processed by the RUN
or OCL processor, or all tasks attached to symbionts. The display includes the job
name along with the CPU time used when the job is under execution, the reason why
the job is not executing (such as waiting for 10, waiting for mount message, under a
pause), or the scheduling priority queue in which the job resides. It also includes the
status of all subtasks attached to the job.
Format
QlSPLAY~{JS,[jObname][,ALL]
}
SY[,symbiont-name] [,ALL]
Positional Parameter 1
JS
Displays job status at the console workstation or console.
SY
Displays at the console the status of all tasks attached to symbionts.
70045208-000
4-61
Job Processing Procedures
Positional Parameter 2
jobname
Displays the status of the job name specified. If omitted, the status of all
jobs in main storage is displayed except for those on the job queues.
symbiont-name
Displays the tasks attached to the symbiont named. This name is the name
displayed by the MIX. DA command. If omitted, the tasks attached to all
symbionts are displayed.
ALL
Displays the status of all tasks attached to a job or symbiont, instead of just
the primary task.
Example
(
Operator keyin:
01 JS,MYJOB
Function requested:
Produce a display of status information about a job named MYJOB.
Typical informational messages:
The following messages illustrate the information produced by the DISPLAY JS
command when it is entered at various stages of jobs processing. The job name
MYJOB is used for the purpose of example in the messages shown.
For the message:
MYJOB IN STEP 01(LNKEOT00)-PRI=10 CPU-TIME=00:01:43.874
MYJOB is active in its first step, performing linkage editing. The CPU TIME
portion ofthe display indicates the linkage editor had control of the processor for
1 minute, 43 seconds, and 874 milliseconds. If the job is proceeding, you can
reenter DIMS for MYJOB and see an increase in the CPU TIME.
For the message:
MYJOB IN STEP 01(MYJOB0)-WTLOCK=JOBFILE
MYJOB is waiting to access the file JOBFILE. Another job accessing JOBFILE
has defined a file share environment that is incompatible with the file share
requirements specified by MYJOB. MYJOB must wait until its share
requirements are compatible with the file share environment.
462
7004 5208-000
(
Job Processing Procedures
For the message:
MYJOB IN STEP 01(MYJOB0)-WAITING FOR TRANSIENT AREA
MYJOB requested a system function that requires a transient area. All transient
areas are currently in use. MYJOB waits until a transient area is available for
use.
For the message:
MYJOB IN STEP 01(MYJOB0)-JOB BEING MOVED
(xxxx)
MYJOB is being acted upon by memory management and may be moved to a
different address to allow better use of main memory. The values in parentheses
are internal memory management values that are useful for software debugging.
(
For the message:
MYJOB IN STEP 01(MYJOB0)-WAITING UNTIL 12:00:00.000
MYJOB execution is suspended and will not restart until the time of day reaches
that displayed in the message (12 noon in this example).
For the message:
MYJOB IN STEP 01(MYJOB0)-WAITING DUE TO PAUSE
MYJOB is paused by a PAUSE console command. MYJOB pauses until it is
activated by a GO console command.
For the message:
MYJOB IN STEP 01(MYJOB0)-WAITING FOR IORB
MYJOB requires use of an input/output request block (lORB). All lORBs
generated in the system are currently in use. MYJOB waits until an lORB is
available for use.
(
For the message:
MYJOB IN STEP 01(MYJOB0)-WAITING FOR OPCOM SYSTEM MESSAGE
MYJOB issued a message to the system console or terminal. MYJOB waits until
the supervisor processes the message.
For the message:
MYJOB IN STEP 01(MYJOB0)-WAITING DUE TO TASK PAUSE
A subtask ofMYJOB issued a TPAUSE macro against the primary task of
MYJOB. MYJOB pauses until a subtask issues a TGO macro against the primary
task ofMYJOB.
7004 5208-000
463
Job Processing Procedures
For the message:
MYJOB IN STEP 01(MYJOB0)-YAITING DUE TO TASK YIELD
The primary task ofMYJOB issued a TYIELD macro to suspend execution. The
primary task ofMYJOB remains suspended until a subtask ofMYJOB issues an
AWAIm macro against the primary task to activate it.
For the message:
MYJOB IN STEP 01(MYJOB0)-YAITING FOR SHARED CODE LOAD
MYJOB requested a supervisor function be performed that requires a shared
code module. The required shared code module is not currently in main memory.
MYJOB waits until the required shared code module is loaded into main memory.
For the message:
MYJOB IN STEP 01(MYJOB0)-YAITING FOR DYNAMIC BUFFER
MYJOB requested a function that requires a dynamically allocated memory
buffer for its processing. MYJOB waits until the supervisor has successfully
allocated a storage buffer to MYJOB for its use.
For the message:
MYJOB IN STEP 01(MYJOB0)-CANCEL IN PROGRESS
MYJOB is in the process of being canceled from the system.
For the message:
MYJOB IN STEP 01(MYJOB0)-YAITING FOR OPERATOR REPLY
MYJOB issued a message to the system console or terminal that requires a reply.
MYJOB waits until there is a reply from the console or terminal operator.
(
For the message:
MYJOB IN STEP 01(MYJOB0)-YIELDED TO ICAM
MYJOB issued a CYIELD macro and is waiting for activity from ICAM.
For the message:
MYJOB IN STEP 01(MYJOB0)-YAITING FOR MOUNT MSG
Job control or data management issued a message requesting that a volume be
mounted on a specific tape or disk device for use by MYJOB. MYJOB waits until
the volume is mounted and a console GO command is entered.
4-64
70045208-000
Job Processing Procedures
For the message:
MYJOB IN STEP 01(MYJOB0)-WAITING FOR SUB-TASK
The primary task ofMYJOB suspended processing and waits until one or more of
its subtasks completes processing before it begins executing.
For the message:
MYJOB IN STEP 01(LNKEDT)-ACTIVE AT PRIORITY 10
MYJOB is active in its first step, performing linkage editing. It is executing at
priority level 10. SYSGEN option JOB ACCOUNTING is not configured in the
supervisor currently loaded.
For the message:
/
\
MYJOB IN STEP 01(MYJOB0)-WAITING FOR 999xxxxx
MYJOB is waiting for a supervisor function to be performed on its behalf. All
supervisor functions are displayed with the message that lists both the threedigit function number (999) and a five-character abbreviation (xxxxx) that
describes it.
For the message:
MYJOB IN STEP 01(MYJOB0)-WAITING FOR LOCK (xxxxxxxx)
MYJOB is waiting because a system resource that it requires is currently locked
by another job. The job waits until the system lock is released. The current
system locks are as follows:
VTOC
PUBS
JOB QTBL
VOL TBL
S.R.Q.
$Y$SHARE
(
N. T.R.
SCOPE
System VTOC lock
Physical unit block (PUB) allocation lock
Job queue table lock
Volume use table lock
Symbiont request queue lock
$Y$SHARE file lock
System NTR lock
Scope table lock
For the message:
MYJOB IN STEP 01(LNKEDT00)-PRI=10 CPU-TIME=00:01:43.874
MYJOB is active in its first step, performing linkage editing. The CPU TIME
portion of the display indicates the linkage editor had control of the CPU for 1
minute, 43 seconds, and 874 milliseconds. If the job is proceeding, you can reenter
DI JS for MYJOB and see an increase in the CPU TIME displayed.
7004 5208-000
4-65
Job Processing Procedures
For the message:
MYJOB IN STEP 02(LIBS0000)-WAITING FOR I/O #00005736
MYJOB is in its second step, executing the librarian. Currently, the 5736th I/O
operation of this step is being performed. If you reenter DI JS, you may see the
I/O number increase. IfMYJOB remains at #00005736, it might be stuck,
requiring your intervention.
For the message:
MYJOB IN STEP 03 -IN STEP PROCESSOR
MYJOB is between job steps. Step 03 just completed or is about to start.
For the message:
(
MYJOB NOT YET SCHEDULED-INSUFFICIENT MAIN STORAGE
MYJOB is not executing; it is placed on ajob queue but is not scheduled for
execution because not enough main memory is available.
For the message:
MYJOB IS ROLLED OUT
MYJOB was removed from main memory to allow another job, which was
scheduled with preemptive priority, to be loaded into main memory. MYJOB
remains in the rollout status until there is enough main memory for its
requirements.
For the message:
MYJOB JUST SCHEDULED-NOW BEING INITIATED
All system resources that MYJOB requires are available and assigned to it.
MYJOB was scheduled and is currently being loaded into main memory to begin
execution.
For the message:
MYJOB WAITING FOR QUEUED SYMBIONT xx
All the system resources needed by the symbiont in question for processing
MYJOB are currently not available. The symbiont is placed on the symbiont
request queue until the required system resources are available. Values for xx
are:
RV
RU
SC
SI
SV
4-66
RV
RU
SC
SI
SV
version
version
version
version
version
of
of
of
of
of
the
the
the
the
the
run processor
run processor
save processor
save processor
save processor
7004 5208-000
(
Job Processing Procedures
4.6.11. Dumping the Contents of Main Storage (SYSDUMP)
The SYSDUMP command is used to dump the entire contents of main storage to the
$Y$DUMP file on SYSRES. Use this command whenever a system dump is required
without supervisor reloading (no manual IPL is required). After the contents of main
storage are dumped, the job SYSDMPnn (where nn is a unique number assigned by
the system) is automatically initiated to print the $Y$DUMP file. The $Y$DUMP file
locks until the SYSDMPnn job completes, to prevent other system functions (caused,
for example, by an II OPTION SYSDUMP statement or by system errors) from also
using the file (see the Dump Analysis Programming Guide (UP-9980).)
(
If you don't want a printout ofthe dump, enter NONE when the SYSDMPnn job asks
what type of dump should be printed. If you delete the SYSDMPnn job from the job
queue or cancel it before it sends you the SDOI DUMP OPTION message, you must
enter the SET SY command to unlock the $Y$DUMP file.
You can't use the console workstation or console keyboard until the main storage
contents are completely written (only a few seconds). After the keyboard unlocks, you
can resume system activity without impairing the integrity of your dump.
Format
SYSDUMP
Notes
1.
If a nonrecoverable error occurs and you want a dump of everything in main
storage at that time, press the ESC key, then the M key to display the manual
frame. Then key in L for system reset and press the XMIT key. Next, key in U for
run and press the XMIT key.
If you get an HPR of 999F, it means the $Y$DUMP file contains data from a
previous main storage write operation that hasn't been processed by SYSDUMP or
SYSDUMPO. You can overwrite the contents of the file by keying in U for run on
the manual frame and pressing X1r1IT, or you can follow the next procedure.
(
2.
7004 5208-000
If there's information in the $Y$DUMP file that you want to preserve and a
nonrecoverable error occurs, perform the IPL procedure in Section 2. This
reinitializes the system without affecting the $Y$DUMP file. To print the contents
of $Y$DUMP, run the SYSDUMP or SYSDUMPO job stream when the IPL
procedure is completed.
4-67
Job Processing Procedures
4.6.12. Setting the $Y$DUMP File to Unlocked Condition (SET SY)
The SET SY command unlocks the $Y$DUMP file after an SY command (4.6.10) or
system error has locked it. You use the SET SY command to unlock $Y$DUMP if you
previously entered the SYSDUMP command and deleted the SYSDMPnn job from the
job queue or canceled it before it displayed the SD01 output message.
Format
~TASY ,.b.Q.FF
Positional Parameter 1
SY
Specifies the $Y$DUMP file condition is set.
(
Positional Parameter 2
.b.Q.FF
Specifies the $Y$DUMP file is unlocked.
Note:
No dump is provided in stand-alone IPL.
4.6.13. Setting Main Storage Condition (SET MEM)
The SET MEM command sets one or more blocks of main storage up or down. The
length of one block is determined by the replacement element size (RES), that is, the
size of the replacement element that contains the main storage block determined
unusable. Normally, main storage is in an up (usable) condition. The system
automatically determines when a main storage block becomes unusable. The system
sets the block down and displays a listing on the console workstation or console screen
of all main storage blocks currently set to down. The down block is unavailable for use
by new jobs or symbionts until it is set to up via the SET MEM command. However,
any jobs or symbionts currently running in the down block continue to run until
completed.
The map of usable storage is kept in the error log. If you add main storage to your
system or take a system-resident pack from a smaller system to a larger system and
the error log is not initialized, the additional main storage will not be usable. To make
the main storage usable, initialize the error log when you perform an IPL or use the
SET MEM command to set the additional main storage up.
You enter the SET MEM command at the request of your system administrator to set
a main storage block up or down as required. Normally, SET MEM is used to set a
block to up after your Unisys customer engineer corrects the condition that made it
unusable.
4-68
7004 5208-000
(
Job Processing Procedures
Format
Positional Parameter 1
!:!E.M
Specifies main storage is to be set up or down.
Positional Parameter 2
QQ.WN
Sets one or more blocks of main storage down.
UP
Sets one or more blocks of main storage up.
Positional Parameter 3
address
Specifies the beginning address, in hexadecimal, of a block to be set up or
down. This address must be on a RES boundary (a multiple of the
replacement element size).
Positional Parameter 4
no-of-blocks
Specifies the number of contiguous blocks, in decimal, set up or down
beginning with the address specified in positional parameter 3. If omitted,
one block is assumed.
4.6.14. Setting the Unattended Console Feature (SET UNCON)
(
The unattended console feature is a SYSGEN option that allows messages requiring
operator intervention to be answered by the operating system if you do not respond in
15 minutes. These messages are informational only and pertain to device I/O errors.
The unattended console feature decreases the need for operator intervention by
requiring operator responses only in extreme cases. The SET UNCON command
allows you to remove the previous SYSGEN option, reactivate it once it has been
removed, and change the unattended console auto-answer time of 15 minutes.
Format
SETllUNCON[~;F )
tlme
7004 5208-000
469
Job Processing Procedures
Positional Parameter 1
UN CON
-
Specifies that the unattended console feature enabled during SYSGEN is to
be disabled, reactivated, or changed.
Positional Parameter 2
OFF
Specifies that the previously enabled (during SYSGEN) unattended console
feature is to be removed.
ON
time
Specifies that the unattended console feature enabled at SYSGEN and .
removed by a previous SET UNCON command is to be reactivated.
Specifies the time in minutes for the unattended auto-answer. If this
parameter is not specified, the time is 15 minutes.
(
4.6.15. Terminating System Activity (SHUTDOWN)
The SHUTDOWN command terminates system activity or distributed data processing
(DDP) in an orderly manner.
Format
SHUTDOWNA{SYSTEM}
DDP
Positional Parameter 1
SYSTEM
Specifies that system activity will be terminated. The spooler and job
scheduler will not start any new files or jobs. Interactive services will not
start any new functions and will terminate when its current activity ceases.
This command cannot be abbreviated; the entire word SYSTEM is required
to protect the user against accidental keyin and shutdown.
DDP
4-70
Specifies that only distributed data processing will be terminated when its
activity ceases. During DDP shutdown processing, all DDP activity is logged
into the interactive services log file. The activity information remains in the
log file and will be printed only when interactive services is shut down by
using the IS SHUTDOWN message (see 5.2.4).
7004 5208-000
(
Job Processing Procedures
4.6.16. Initiating Transient Work Area Feature (TW)
The TW command initiates the transient work area feature. This feature can improve
system performance. The most recently used transients are stored in the transient
work area of main storage. Therefore, an I/O delay can be avoided by satisfying the
transient load request directly from the work area rather than from SYSRES.
Format
TWll[ SZ=nnn]
Positional Parameter 1
SZ=nnn
Specifies the number (nnn) ofl,024-byte blocks for the work area, where
nnn must be in the range of 32 to 250. Any value outside of this range causes
your system to terminate the transient work area and display the message
INVALID PARAMETER. If omitted, 65K is allocated for the work area by
default.
You can initiate the transient work area whenever sufficient free main storage is
available to satisfy the work area space requirements. However, you should initiate
TW immediately after the IPL procedure to avoid possible fragmentation of main
storage.
Once the transient work area is activated, the message TRANSIENT WORK AREA IS
INITIALIZED appears. If you receive this message during the IPL procedure, it
indicates that the work area in your supervisor generation has already been allocated
to the specified size during system initialization.
To change the work area size, you must terminate the transient work area and then
key in the TW command with a new value. To terminate the transient work area, key
in:
00ATWAEOJ
The message TRANSIENT WORK AREA TERMINATED then appears.
4.6.17. Specifying Resource Management (LIMITS)
The LIMITS command lets you control the percentage of your system's main storage
space used for symbionts, interactive processing, and batch processing. This enables
you to maximize system turnaround time and workstation response. Resource
management lets you control these activities:
•
Number of batch jobs run from both the console and workstations
•
Number of batch jobs run from the workstations only
70045208-000
4-71
Job Processing Procedures
•
Number oflogged-on workstations (including workstations logged on to both
interactive services and OS/3 interactive)
•
Number of ENTER processing tasks
•
Number of RUN symbionts
You can issue the LIMITS command at any time during the session. However, all
parameters of this command (except MAXLOGONS and UPTERMINAL) require that
resource management be generated at SYSGEN. Otherwise, the parameters are
considered invalid. MAXLOGONS and UPTERMINAL parameters are valid only
when security is generated.
If your system is primarily a batch or interactive system, you can specify resource
management parameters during system generation (SYSGEN). See the Installation
Guide, 7004 5505, for a description of the resource management SYSGEN
parameters.
(
If your system operations change throughout the day or week from batch to
interactive, or you use a mixture of both, then use the LIMITS command to change
your resource management controls as your processing needs change. When you reuse
the LIMITS command, any parameters not specified remain unchanged.
Before using the LIMITS JOBMEM command to reduce the percentage of main
storage available for batch jobs, be sure there is sufficient main storage for the jobs in
the current running system. The MAXJOBS limit can be temporarily lowered to
insure that no new jobs are initiated. After some jobs have terminated normally and
the percentage of main storage in use falls below the new target level, then you can
issue the LIMITS JOBMEM command and reset the MAXJOBS limit. This precaution
helps avoid jobs from aborting due to insufficient memory.
Format
llMITSlI
~YMBMEM= {~~~~0~ [ I NTMEM={~~~~0~ [JOBMEM={~~~~0~ [,MAXJOBS=1-nl
(
[,MAX~OBS=0-n][,MAX~JOBS=0-n][,MAXINTUSERS=0-2SS][,MAXENTERS=0-2SS]
[,MAXRUNSYMBS=1-10] [MAXLOGONS=
H-99~ [UPTERMINAL={;!~~~
Parameters
SYMBMEM={S-100}
.!!b.MT
Specifies the percentage of available main storage your system uses for
symbiont use. Either specify a percentage value between 5 and 100, or
specify NLMT. NLMT specifies that resource management does not control
that area of main storage allocated to symbionts. The value you specify can
be greater than or less than the SYSGEN value.
4-72
7004 5208-000
Job Processing Procedures
illMEM={S'100}
.tib.MT
Specifies the percentage of available main storage your system uses for
interactive use. Either specify a percentage value between 5 and 100, or
specify NLMT. NLMT specifies that resource management does not control
that area of main storage allocated for interactive use. The value you specify
can be greater than or less than the SYSGEN value .
.dQ[MEM={0'100}
.tib.MT
Specifies the percentage of available main storage your system uses for
batch use. Either specify a percentage value between 0 and 100, or specify
NLMT. NLMT specifies that resource management does not control that
area of main storage allocated for batch use. The value you specify can be
greater than or less than the SYSGEN value.
MAX~=1'n
Specifies the number of jobs that can be executed concurrently. The value
you choose cannot exceed the value you have specified for the SYSGEN
JOBSLOTS parameter. The maximum number of jobs is 48.
MAX.\:lfu1.0BS=0·n
Specifies the maximum number of jobs that can be executed concurrently
from workstations only. The value you choose cannot exceed the value you
have specified for the SYSGEN MAXJOBS parameter, or the last LIMITS
command MAXJOBS parameter.
MAX.§!§.JOBS=0·n
Specifies the maximum number of jobs that can be initiated concurrently
from any single workstation. The value you choose cannot exceed the value
you have specified for the SYSGEN MAXWSJOBS parameter or the last
LIMITS command MAXWSJOBS parameter.
MAXINTUSERS=0·2SS
Specifies the maximum number of interactive users that can be logged on at
one time. This parameter changes the value of the ISINTLMT parameter
defined at SYSGEN or set with a previous LIMITS command.
MAXENTERS=0·2SS
Specifies the maximum number of batch tasks initiated with the ENTER
command that can execute concurrently in the system. This parameter
changes the value of the ISBATCHLMT parameter defined at SYSGEN or
set with a previous LIMITS command.
MAX~SYMBS=1'10
Specifies the maximum number of RUN symbionts that can be concurrently
executed. This parameter changes the value of the MAXRUNSYMBS
parameter defined at SYSGEN or set with a previous LIMITS command.
7004 5208-000
4-73
Job Processing Procedures
MAX.bQfiONS={1-99}
Ii
Specifies the maximum number of invalid logon attempts before a terminal
is deactivated. The default value is 5.
YETERMINAL={tttt}
*ALL
Specifies the terminal (tttt) to be reactivated. *ALL reactivates all terminals,
whether they have been deactivated or not.
Examples
1.
Let's say your system is used primarily for interactive jobs in the morning, for
both batch and interactive jobs in the afternoon, and then only batch jobs in the
evening.
Upon user requests for a better balance between system turnaround time and
workstation response time during each of these shifts, the operator issues the
LIMITS command.
First, before the morning shift, he issues:
LIMITS JOBMEM=20,INTMEM=80,MAXRUNSYMBS=1
This example shows a small value for the JOBMEM parameter, the
parameter that specifies the percentage of main storage to be used for
batch jobs. It shows a high value for INTMEM, the parameter that
specifies the percentage of main storage to be used for interactive jobs.
And it shows a low value for the number of RUN symbionts that can
execute concurrently.
Next, before the afternoon shift, the operator issues:
LIMITS JOBMEM=70,INTMEM=70,MAXRUNSYMBS=2
This example shows a balance of the percentage of main storage to be
used for batch and interactive use. (Both JOBMEM and INTMEM are
specified as 70). This time, the operator increases the number of RUN
symbionts that can execute concurrently.
Finally, before the evening shift, the operator issues:
LIMITS JOBMEM=80,INTMEN=10,MAXRUNSYMBS=3
This example shows a much higher percentage of main storage to be
used for batch use (JOBMEM is specified as 80; but, INTMEM is
specified as only 10.) The operator increases the number of RUN
symbionts that can execute concurrently to 3.
2.
The following example reactivates workstation C12 and changes the invalid logon
limit to 3:
LI
4-74
UP=C12,LOG=3
7004 5208-000
(
Job Processing Procedures
4.6.18. Verifying and Correcting the VTOC (W)
The preventive maintenance procedures, VTOC verification and VTOC correction, are
called using the VV system command. The VTOC verification routine determines
whether volume table of contents (VTOC) corruption has occurred on an OS/3 disk. It
performs a thorough analysis of a VTOC, looking for any inconsistencies between the
labels in the VTOC. When it detects an inconsistency, it displays a message providing
details on the error.
Use this routine under the following circumstances to detect VTOC problems as soon
as possible:
•
Initially, to verify that all volumes pass verification.
•
After a system stop, to verify that all volumes in use at the time of the stop pass
verification.
•
When one of the error codes described under "Symptoms of Compromised VTOC"
is experienced.
The VTOC correction routine can correct volume label errors (yv08) only. See the
VV08 message description in the System Messages Reference Manual, 7004 5190, for a
list of the specific error codes that are correctable.
It is not necessary to prevent other jobs from accessing the device specified when
using the VTOC correction routine; however, you should use this facility only during
periods of minimal activity in the system.
Before using the VTOC correction routine, you should make an alternate copy of the
VTOC being corrected. (See Note 5, Figure 4-2.)
Format
(
Positional Parameter 1
did
Specifies a one- to four- character numeric field identifying the device
address of the device whose VTOC is to be verified. If you omit this
parameter, the system prompts you for the device address.
The VV command automatically locks the specified VTOC to prevent it from
being accessed while it is being read or updated.
7004 5208-000
4-75
Job Processing Procedures
Positional Parameter 2
END
Terminates the routine when it completes the verification. If you omit this
optional parameter:
•
The system prompts you for another device address when the VTOC
successfully passes verification.
•
The routine terminates if verification fails.
FIX
Calls the VTOC correction routine and performs the following steps:
1.
Complete VTOC verification
2.
VTOC correction
3.
Reverification
(
If the error encountered is not correctable, the system informs you that the
error cannot be automatically corrected (VV22).
If you omit the FIX. parameter, only verification is performed.
Note:
It is recommended that you specify the FIX parameter after you detect an
error. It is also suggested that you correct an alternate VTOe
(VVdid,FIX,ALT) as a first trial correction before correcting your VTOe
file.
ECnn
Causes a dump to be taken when the error code nn is encountered.
For example,
W 190,EC18
(
causes a dump to be taken when VVOS EC1S is encountered. (See the System
Messages Reference Manual, 70045190.)
The symbiont produces an error code 33A, calls SYSDUMP to print the
dump, and continues processing. (Select the MINI SYSDUMP option.)
Use this debug facility to provide U nisys with additional documentation for
an unexplained error condition.
COpy
Copies the VTOC to a file named ALT$VTOC. You must create this file
before using the COPY parameter.
4-76
7004 520s.:o00
Job Processing Procedures
PACK
Indicates that the VTOC is to be packed (i.e., reorganized). Format 1 labels
are searched on all ALLOCATE, SCRATCH, EXTEND, OPEN, and CLOSE
file management operations. The pack process consists of moving the
Format 1 labels to the front of the VTOC to reduce search times when
performing these common operations.
First a verify is performed to guarantee that the VTOC passes verification.
Then the VTOC is copied to the alternate VTOC file and the VTOC is
reorganized. Should a problem occur during the pack process, the VTOC is
restored to its original contents. Do not cancel VV while a pack function is in
progress.
The alternate VTOC file (ALT$VTOC must be allocated prior to performing
the pack.
You should use PACK only when the device in question is not being used by
any other jobs (i.e., VV can get exclusive use of the device). If you pack the
VTOC on a system disk (i.e., RES, RUN, or SPOOL), you must guarantee
that the system is completely idle and, immediately upon completion of the
pack, you must re-IPL the system because there may be internal tables that
contain invalid (i.e., old) format label addresses. You can pack multiple
system disks in succession without a re-IPL after each one, but you must
pack the RES device last and then re-IPL immediately.
Positional Parameter 3
ALT
Performs the specified routine on the alternate VTOC (ALT$VTOC). The
VTOC must be copied to the alternate file, using the COPY parameter,
before the ALT parameter is used.
This parameter is optional. If omitted, the specified routine is performed on
the original VTOC.
When you specify ALT, all VTOC verify messages (information and error)
include the label ALT$VTOC at the end of the message.
Note:
It is suggested that you correct an alternate VTOC (VV did,FIX,ALT) as a
first trial before correcting your VTOC file.
The volume table of contents (VTOC) is a file that resides on every disk and serves as
a directory for all files on that disk. The address of the VTOC is contained in the
VOLl label, which resides in a fixed location on each disk. Each physical record (i.e.,
sector) in the VTOC file is one of six types offormat labels.
70045208-000
4-77
Job Processing Procedures
The following summarizes the various format label types, presented according to their
logical progression.
•
FORMAT 4 (F4) - Contains device-dependent information about the volume and
a pointer to the FO chain. There is only one F4 label.
•
FORMAT 5 (F5) - Contains information regarding available space on the disk.
There can be multiple F5 labels.
•
FORMAT 0 (FO) - An unreserved label type available for label usage by the
system as necessary. There can be multiple FO labels that are logically linked
together by pointers.
•
FORMAT 1 (F1) - Contains information regarding the physical space allocated to
a specific file (i.e., physical extents).
•
FORMAT 2 (F2) - Contains supplementary F1 information that specifies how the
physical space allocated to the file is subdivided (i.e., logical extents).
•
FORMAT 3 (F3) - Contains additional Fl logical extent information.
(
Cause of Compromised VTOC
The VTOC is updated when a new file is added or deleted, or when an existing file
requires that two or more labels in the VTOe be updated. If the update does not
complete due to a system stop (HPR) or unrecoverable VO error, the VTOC may be
left in a compromised state, which can lead to files being destroyed.
Symptoms of Compromised VTOC
•
Error codes 30, 31, or 32
,p
•
Caused by an unrecoverable VO error during a VTOC update.
•
Error code 3A
A definite indication of a compromised VTOC. Disk space management (DSM)
reports this error when it detects a label inconsistency.
•
Error codes 35 or 36 or DM41
Generally occurs when there are no available (FO) labels or no available space. In
this case, these errors are generally not a symptom of a compromised VTOC.
However, if they occur when there should be labels or space available, then it
could be a sign of a compromised VTOC.
.
4-78
7004 5208-000
Job Processing Procedures
•
Invalid data
Ifinvalid data (e.g., data from a different file) is being returned to a program,
this could be sign of a compromised VTOC.
Error Conditions during Verification
Several conditions prevent the verification routine from performing. When any of
these is encountered, it is identified by a VV07 message followed by a VV02 message
prompting you to enter a device address. Correct the condition specified by the VV07
message and reenter the device address.
Volume and file type errors are identified by VVOS and VV09 messages, respectively.
It is possible to get several VVOS or VV09 messages or a combination of both.
During verification, the routine attempts to identify all volume and file type error
conditions. However, certain error conditions may be too serious for the routine to
continue. Correct the conditions listed, then perform the VTOC verification routine
again to identify any remaining VV08 and VV09 errors.
.
Refer to the System Messages Reference Manual, 7004 5190 for an explanation of
VTOC verification messages and their error codes.
Corrective Action
The flow chart in Figure 4-2 shows the procedure to follow whenever a disk fails the
VTOC verification routine.
(
7004 5208-000
4-79
Job Processing Procedures
FOLLOW
CORRECTIVE
PROCEDURE
FOR
W07 ERROR
N
Y
N
Y
Y
NOTE 1
DISK IS OK
NOTE 2
IDENTIFY
OTHER IiF ANY!
AFFECTED FILES
Y
(
NOTE 7
CONTACT
SUPPPORT
CENTER
CREATE
TEMPORARY
BACKUP
N
NOTE 3
NOTE 8
(
GO TO START
N
NOTE 4
Y
>----.....
SCRATCH OR
RENAME
VVS$ DUMMY FILE
SCRATCH AND
RESTORE BACKUP
COPIES OF ALL
AFFECTED
FILES
~
NOTE 10
GO TO START
DISK IS OK
A19144
Figure 4-2. VTOC Verification/Correction Procedure (Part 1 of 2)
4-80
7004 5208-000
Job Processing Procedures
NOTES:
1. Some W07 errors are user errors, such as wrong device address or device not on-line.
2. If you get a WOg message with error code 09 or 11, other files besides the ones identified in the message may
be affected.
For example, when a cylinder is assigned to two different files, a W09 message is displayed for the second file.
The verification routine cannot determine which file is corrupted. You must use the SU VTP listing to determine
whether there are other files whose disk space allocations (physical or logical) overlap the allocations of the file
named. If so, these files might have been affected also.
3. If you do not have a previously created backup copy of the affected files, create a temporary backup by copying
the files onto another disk. Remember, however, that the integrity of this copy may be affected by the incorrect
labels.
4. Restore all potentially corrupted files (identified by WOg messages or as in note 2 above) from a previously
created backup copy using a copy program such as DATA utility or DUMP/RESTORE in file mode.
5. Using the COPY parameter, make an alternate VTOC for a trial correction.
6. Make two passes through the correction routine: the first, a trial correction on the alternate VTOC and the
second, the correction of your VTOC file. If the trial correction is unsuccessful, your VTOC file is not affected.
7. Dump each file on the disk (except those identified by W09 messages or identified as in note 2) to another
medium using the DUMP/RESTORE utility in file mode. Then prep the VTOC of the bad Disk and restore all of the
files just dumped.
8. Should this situation ever occur, verify the disk using the ECnn parameter. Send the resulting dump and a copy
of the old VTOC (on tape or diskette) to the Unisys Support center.
9. If the correction was performed against the alternate VTOC, correct your VTOC file.
(
10. Space that was not accounted for in the previous step is assigned to a temporary file (W$$DUMMY), giving you
the opportunity to access that data. If you want to keep the data, rename the file. If not, you can scratch the
file and return the space to the free space list.
Figure 4-2. VTOC Verification/Correction Procedure (Part 2 of 2)
7004 5208-000
4-81
Job Processing Procedures
Verifying the VTOC during AVR (SET VV)
The verify routine can be invoked explicitly via the system command VV or implicitly
whenever an automatic volume recognition (AVR) is performed. AVR is performed
under the following circumstances:
•
DuringIPL
•
Whenever a disk is set online
•
Explicitly, via the AVR command
Automatic VTOC verification AVR time can be requested in two ways:
1.
Via the VVAVR SYSGEN parameter. See the Installation Guide, 7004 5055, for
details on the VVAVR parameter.
2.
Via the SET VV command.
(
Format
SET W,{ON }
OFF
Positional Parameter 1
ON
Performs automatic VTOC verification at AVR time.
OFF
Does not perform automatic VTOC verification at AVR time. This overrides
the VVAVR SYSGEN specification, described in the Installation Guide, 7004
5505.
(
Error Reporting to Unisys Support Center
If a volume that previously' passed verification suddenly fails verification when there
were no system stops or unrecoverable I/O errors to cause the VTOC to be
compromised, report this occurrence to the Unisys support center. An analyst at the
support center will record your information, assign you a User Communication Form
(UCF) authorization number, and submit a UCF in your behalf.
When mailing support documentation to the support center, include the release level
of your software and the UCF number assigned by the analyst Also enclose as much
information as possible about the jobs that accessed the volume that was
compromised, including:
•
4-82
A formatted VTOC print (SU VTP) and a disk print of the VTOC (SU DD) taken
both before and after the program is run
7004 5208-000
Job Processing Procedures
•
The JCL for the jobs in question
•
A console log and an error log
•
Any additional information useful in duplicating the problem (for example,
operational information, copies of programs, or copies of disks)
Procedures for reporting error conditions to a Unisys support center are provided in
the System Technical Support Overview, 7002 3916.
4.6.19. Setting Memory Consolidation Conditions (SET MC)
(
The SET MC command enables or disables the memory consolidation (MEMCON)
feature. MEMCON is enabled to allow movable jobs to be consolidated at the highest
possible addresses, thus creating the largest possible free regions. All movable job
task control blocks (TBCs) must be inactive prior to moving a job. In a system that is
not fully utilizing its memory resources, memory consolidation may not be desirable.
In this case, MEMCON should be disabled.
Ongoing MEMCON s at the time of the keyin are not affected by the command.
Format
SET MC,{ON }
OFF
Positional Parameter 1
MC
Specifies that the MEMCON condition is to be altered.
Positional Parameter 2
ON
Enables memory consolidation.
(
OFF
Disables memory consolidation.
4.6.20. Setting Job Immovability Conditions (SET 1M)
The SET 1M command enables or disables the job immovability (lMVJOB) feature.
Some jobs present a problem to MEMCON because they become immovable. Normally
IMVJOB is enabled to move those jobs to the high addressed portion of memory. This
reduces the possibility that a particular job will become a roadblock to an ongoing
memory consolidation. To perform this move, several jobs may have to be idled
simultaneously, thus temporarily preventing any processing by those jobs involved. If
this condition is not desirable to the operator, IMVJOB can be disabled by this
command.
70045208-000
483
Job Processing Procedures
An ongoing move at the time of the keyin is not affected by the command.
ROLLOUT must have been configured for the current supervisor in order for
IMVJOB to be enabled by this command.
Format
SET IM,{ON }
OFF
Positional Parameter 1
1M
Specifies that the IMVJOB condition is to be altered.
Positional Parameter 2
ON
c
Enables job immovability moves.
OFF
Disables job immovability moves.
4.6.21. Displaying Buffer Pool Information (DI BI)
The DI BI command displays system buffer pool information at the system console.
Format
01 BI
Example
The following is a sample system console display of buffer pool information for the
DI BI command.
33 BR0022
BREAKPOINT TAKEN FOR CONSOLE LOG 88/09/08
01 BI
EXPANSION REGION SIZE (ByTES) ••..•••••••••••••••
4,096
RESERVE REGION SIZE (ByTES) •••.•••••••••••••••••
500
DISK CACHE BUFFER SIZE (ByTES) .•.•••••••.••••••• 2,050,048
TRANSIENT CACHE BUFFER SIZE (ByTES) ••.••••••••••
o
TOTAL JOB/SYMBIONT BUFFER SIZE (ByTES) ••••••••••
59,272
TOTAL ALLOCATED BUFFERS (ByTES) ••••••...•••••••.
2,109,320
CURRENT NUMBER OF BUFFERS ALLOCATED .••••.••••.•.
43
LARGEST NUMBER OF BUFFERS ALLOCATED •••••.•••••••
49
LARGEST NO. OF JOB/SYMB. BUFFERS USED (BYTES) •.•
77,812
DISPLAY END
(
010024
010024
010024
010024
010024
010024
010024
010024
010024
010024
7004 5208-000
Job Processing Procedures
where:
EXPANSION REGION SIZE (BYTES)
Specified in a SYSGENIIPL parameter.
RESERVE REGION SIZE (BYTES)
Specified in a SYSGEN parameter.
DISK CACHE BUFFER SIZE (BYTES)
Specified in a SYSGENIIPL parameter/console command.
TRANSIENT CACHE BUFFER SIZE (BYTES)
Specified in a SYSGEN parameter/console command.
TOTAL JOB/SYMBIONT BUFFER SIZE (BYTES)
Is the total size of buffers currently allocated to jobs or symbionts.
TOTAL ALLOCATED BUFFERS (BYTES)
(
Is the total size of disk cache, transient cache, and job/symbiont buffers.
CURRENT NUMBER OF BUFFERS ALLOCATED
Is the number of buffer regions currently allocated in memory.
LARGEST NUMBER OF BUFFERS ALLOCATED
Is the largest number of buffer regions allocated in memory since the last
IPL.
LARGEST NO. OF JOB/SYMB. BUFFERS USED (BYTES)
Is the largest number of buffer allocated to jobs or symbionts since the last
IPL.
4.6.22. EnablingjDisabling the ConsolejWorkstation Alarm Beeper (SET AL)
This command turns alarm beeper feature on or off at the console or workstation.
Format
(
SET
ALARM'(~~E)
OFF
Parameters
ONE
Turns the alarm beeper feature on. Only a single warning beep is sounded.
ON
Turns the alarm beeper feature on. Continuous warning beeps are sounded.
OFF
Turns the alarm beeper feature off.
7004 5208-000
4-85
Job Processing Procedures
4.6.23. EnablingjDisabling the Console Video Clock (SET VC)
This command turns on or off the console time-of-day clock. This clock is located at
the upper right corner of the console and is normally incremented every 10 seconds.
Format
SE T .l!£, {ON }
OFF
Parameters
ON
Turns on the console time-of-day clock.
OFF
Turns off the console time-of-day clock. The clock display goes blank and it
is no longer incremented.
4.6.24. Changing Symbiont Execution Priorities (SET PS)
This command assigns an execution priority to a specific symbiont. The priority
remains in effect until it is either changed by another SET PS command or the system
is rebooted.
(
Format
SET~PS,symbiont·name,n
Parameters
symbiont name
Two- or three-character name identifYing the affected symbiont.
n
A value from 0 to 59 indicating the execution priority of the symbiont
identified by parameter 1. This value cannot exceed the value specified by
the PRIORITY parameter specified in SUPGEN.
4-86
7004 5208-000
(
Job Processing Procedures
4.6.25. Setting Console Message Viewing Privileges (SET CV)
This command allows privileged users to view the console messages sent to the
operator in addition to their own messages.
Format
SETACV,{ON }
OFF
Parameters
ON
Turns viewing privileges on.
OFF
Turns viewing privileges off.
(
4.6.26. Viewing Messages Sent to Logged Off Users (SET LX)
This command lets console and delegated console users view the screen messages sent
to users who have logged off. The messages are displayed only at the console or
terminal issuing the command. The messages sent to the logged off users are placed
in the console log regardless of whether the SET LX command is issued.
Format
SETALX,{ON }
OFF
Parameters
ON
Turns on message viewing function. CU ser issuing this command views
messages directed to logged off users.)
(
OFF
Turns off message viewing function. CU ser issuing this command no longer
receives messages directed to logged off users.)
7004 5208-000
4-87
(
Section 5
Interactive Services
You use interactive services with an extended set of commands and messages to
control the interactive system environment. (For a description of all interactive
services commands, see the Interactive Services Operating Guide (UP-9972.) These
commands and messages enable you to exercise control over the interactive OS/3
operating system, all jobs within the system, all workstation users (local locations),
and all terminal users (local and remote locations).
5.1. Interactive Services Commands
The interactive services components are loaded automatically whenever required for
the system operator and workstation users. Provided ICAM and the global user
service task (GUST) are ready, a workstation user's interactive entry or your
command loads interactive services for terminal users. Interactive services commands
are used to:
•
Send messages to a workstation
•
Ask questions of workstation and terminal users
•
Display the volumes in use and the status of active workstations, terminals, jobs,
and functions
•
Display status of system resources in use and available
•
Display the log file
•
Modify bulletinllog logon default setting and override values
•
Load interactive services
•
Terminate workstation and terminal user tasks or sessions
(
7004 5208-000
5-1
Interactive Services
5.1.1. Sending Messages to Users (TEll)
The TELL command sends a message not requiring a response to a specific
workstation or terminal user or to all users.
Format
TELLA{ALL _ },Itext l
user-ld
Positional Parameter 1
ALL
Displays the message on all active user screens.
user-id
Specifies the one- to six-character alphanumeric identification ofthe user to
receive the message display.
(
Positional Parameter 2
text
Specifies the text of the message to be sent. The text may be a maximum of
88 characters long. Text must be preceded and followed by apostrophes.
5.1.2. Asking Questions of Users (ASK)
(
The ASK command sends a message that requires a response to a specific workstation
or terminal user. The command displays your question to the specified user, accepts
the reply, and returns the reply to the console workstation screen.
Format
ASKAuser·id,'text '
Positional Parameter 1
(
user-id
Specifies the one- to six-character alphanumeric identification of the local or
remote user to receive the message display.
Positional Parameter 2
text
Specifies the text of the message to be sent. The text may be a maximum of
88 characters long. Text must be preceded and followed by apostrophes.
5-2
70045208-000
Interactive Services
5.1.3. Displaying System Status (STATUS)
The STATUS command displays the volumes currently in use and the status of active
workstations, terminals, jobs, and functions. It also displays the status of system
resources in use and their availability and limitations.
Format
STATUSlI .4.0BS
fUNCTIONS
RESOURCES
IERMINALS
IERMINALS[,uid]
YOLUMES
LIMITS
Positional Parameter 1
JOBS
-
Displays a listing of the jobs and symbionts currently active in the system.
The list includes the job or symbiont name and the amount of storage and
CPU time used by each, information on what program each job is executing
and its job step number, the job slot number for the job, and the master userid for the job or symbiont. A summary line displays the amount offree main
storage in the system and the largest contiguous region.
FUNCTIONS
-
Displays a listing of an active commands and tasks initiated by users.
RESOURCES
-
Displays a listing of the amount of storage being used by all users; the
number of interactive, batch, and batch with interactive commands
(ENTER) tasks; the number of active jobs and configured job slots; and the
amount of total system storage.
TERMINALS
-
Displays a listing of all currently active (logged on) workstations and
terminals and the associated user-id.
IERMINALS,[uid]
Displays a listing of an currently active (logged-on) terminals and associated
user-ids that match the user-id you specify. The uid parameter must be
between one and six alphanumeric characters.
VOLUMES
-
Displays a listing of the tape, disk, and diskette volumes currently mounted
on the system.
LIMITS
-
7004 5208-000
Displays the system resource management limits values and their current
status.
5-3
Interactive Services
Example!
Operator keyin:
STA V
Function requested:
Display a listing of the tape, disk, and diskette volumes currently mounted
on the system.
Screen display:
D-REL110 D-REL14x D-OS3WRK D-REL120 D-REL13X
IS90 STATUS COMMAND TERMINATED NORMALLY
Disk volumes RELllO, RELI4X, OS3WRK, REL120, and REL13X are
currently mounted on the system.
Example 2
Operator keyin:
STA T
Function requested:
Display a listing of all the currently active workstations and terminals and their
associated user-ids. In a secure system, display all terminals with at least one
invalid log-on attempt and number of log-on attempts remaining for them.
Screen display:
(
TRM USERID
313 PUBS I
TRM USERID
314 PUBS
TRM USERID
TRM USERID
Workstations 313 and 314 are currently logged on under user-ids PUBSI and
PUBS, respectively.
7004 5208-000
Interactive Services
Additional screen display if security is active:
TRM
LOGON TRIES LEFT
C12
3
(MAXLOGONS)
5
IS90 STATUS COMMAND TERMINATED NORMALLY
ExampleS
Operator keyin:
STA J
Function requested:
Display a listing of the jobs and symbionts currently active in the system.
Screen display:
JOB NAME SIZE
CPU TIME STEP EXEC
RC$$IS00 006912
7.3
00 RC$$IS
SL$$VT00 001536
.0
00 SL$$VT
SFGEN03 029696
2.9
01 SF$GEN
IiilDATA02 036864
4.8
01 DATA00
UNUSED MEMORY 0781312
IS90 STATUS COMMAND TERMINATED NORMALLY
JOB NO
00000
00000
00003
00002
MASTER
PUBS
PUBSI
PUBS
The jobs and symbionts currently active are listed in the first column. The SIZE
column indicates the amount of storage each job is using. The CPU time is given
next, followed by the job step number and the name of the program each job is
executing. The JOB NO column is the job slot number of each job; MASTER
provides the master user-id for the job or symbiont. The amount of unused
memory is also shown.
(
7004 5208-000
5-5
Interactive Services
Example 4
Operator keyin:
STA L
Function requested:
Display a listing of the current values and available limits for the resource
management controls. These controls were set by the last LIMITS command or by
resource management parameters specified during system generation.
Screen display:
WSJOBS
JOBS
02/10
01/07
SYMBMEM
05/10% (030K/060K)
SWSJOBS
01
INTUSER
12/15
INTMEM
55/80% (330K/480K)
ENTERS
10/30
(
RUNSYMBS
01/01
JOBMEM
08/10% (048K/060K)
The values on this screen show that this user system will perform as follows:
JOBS 02/10
Can execute 10 jobs concurrently, but is now executing only 2.
WSJOBS 01/07
Can execute seven jobs concurrently from workstations only, but is now
executing only one.
SWSJOBS 01
Can execute only one job from a single workstation at a time.
INTUSER 12/15
Can support up to 15 interactive users logged on at anyone time, but only 12
users are logged on at this moment.
ENTERS 10/30
Can support 30 batch sessions executing concurrently, but is now supporting
only 10.
RUNSYMBS 01;01
Can support one run symbiont executing at a time and is now supporting it.
SYMBMEM 05/1WI. (030K/060K)
Can use up to 10 percent (or 60K) of available main storage for symbiont
use, but is now using only 5 percent (or 30K) for symbiont use.
5-6
7004 5208-000
(
Interactive Services
INTMEM 55/80% (330K/480K)
Can use up to 80 percent (or 480K) of available main storage for interactive
use, but is now using 55 percent (or 330K) for interactive use.
JOBMEM 08/10% (048K/060K)
Can use up to 10 percent (or 60K) of available main storage for batch use,
but is now using only 8 percent (or 48K) for batch use.
Note:
If you specified NLMT for the SYMBMEM, INTMEM, or JOBMEM
parameters, then the STATUS command listing would display NL as your
upper limit for those three values.
5.1.4. Displaying Log File (RECALL)
The RECALL command lets you display all or part of your log file at your workstation
screen or at the system console. RECALL only uses the lines that are available on the
screen for the recall.
Format
RECALL~{LAST~nn
}[,prefixl
hh:mm:ss-hh:mm:ss
Parameters
LAST~nn
Indicates the number of messages (nn) in the log file that you wish to see.
hh:mm:ss-hh:mm:ss
Indicates that you wish to see the contents of the log file for a particular
time period. All time must be specified in military time. The minutes (mm)
and seconds (ss) are optional. You must, however, separate the beginning
time from the ending time with a dash (-). To display all messages from a
specific time until the end of the log file, specify only a beginning time. To
display all messages from the beginning of the log file until a specific time,
specify only an ending time. When keying in an ending time only, you must
prefix it with a dash.
(
prefix
Indicates that you only wish to view those messages that begin with this
prefix. The prefix can be from one to eight characters.
70045208-000
5-7
Interactive Services
5.1.5. Modifying Bulletin and/or Log Values (SET IS)
The SET IS console command allows you to modify the bulletinllog logon default
setting and override values during normal system processing.
Format
SETAIS,!BULLDEF),{YES}
BULLOVR NO
WLOGDEF
WLOGOVR
Parameters
BULLDEF and WLOGDEF
Specify whether YES or NO appears as the default on the logon screen.
These specifications are also valid for a user who logs on batch or does a
smart logon (from system mode).
(
BULLOVR and WLOGOVR
Specify whether the interactive services user logging on can change the
values that appear as defaults. These specifications also apply to batch and
smart logons. If NO is specified and the user attempts to change the value,
the following message appears:
IS136 USER NOT ALLOWED TO CHANGE BULLETIN AND/OR LOG VALUES
The user will remain logged on providing there are no other logon errors.
5.1.6. Starting Interactive Services (IS)
Normally, the interactive services facility is started automatically for the system
operator and all workstation users, whenever needed. However, there are occasions
when you must manually load interactive services via the IS command.
•
•
Enter the IS command with the REMOTE START parameter to manually start
interactive services when IeAM and GUST are ready and interactive services are
needed for terminals; but no workstation entry has automatically loaded them.
Enter the IS REMOTE unsolicited message (see 5.2.3) to start interactive
services when IeAM and GUST are ready and the interactive services facility is
active (already loaded) before being needed for terminals.
If, however, IeAM and GUST are not ready, terminal users cannot initiate interactive
sessions. (See Section 6 for the operator procedures on loading !CAM and running the
global user service task.)
You also use the IS command to manually start interactive services after a completed
shutdown (termination). When you terminate interactive services via the
SHUTDOWN message (5.2.4), the interactive services facility is placed in a closed
condition and is unable to start automatically when needed. After a completed
shutdown, you enter the IS command to remove the closed condition and restart
interactive services.
7004 5208-000
(
Interactive Services
Format
ISA[REMOTEASTART]
Positional Parameter
REMOTE START
Loads interactive services for terminals when no workstation entry has
automatically loaded them.
5.1.7. Terminating User Tasks or Sessions (REMOVE)
The REMOVE command terminates a single command for a specific task, a specific
workstation or terminal user session, or all user sessions. Following the termination, a
cancellation message is displayed on the terminated user's screen.
Format
REMOVEA[task-~d)
user-ld
ALL
where:
task-id
Specifies the particular task under which a command is to terminate. Taskids can be determined by using the STATUS FUNCTION command.
user-id
Specifies the particular user whose session is to terminate. User-ids can be
determined by using the STATUS TERMINAL command. All interactive
functions for the user-id specified are terminated and the user is logged off.
If the user is running an interactive session as a batch job (via ENTER), the
user is logged off; however, the session is not affected. A message is
displayed on the console workstation or console screen to indicate when the
user cannot be logged off.
(
ALL
Specifies all user sessions and batch runs are to terminate for each user-id
that can be controlled by this user. All interactive functions are terminated
and the users are logged off. Users running interactive sessions as batch jobs
(via ENTER) are logged off. A message indicating which users cannot be
logged off is displayed on the console workstation or console screen.
7004 5208-000
5-9
Interactive Services
5.2. Interactive Services Messages
You use unsolicited messages provided by interactive services for additional control
over the interactive environment. These messages are used to:
•
Restrict and release new workstation and terminal user sessions
•
Control interactive services for terminals
•
Terminate interactive services
5.2.1. Restricting New User Sessions (CLOSE Message)
The CLOSE unsolicited message restricts any new workstation or terminal user
sessions from starting. Currently active sessions are not affected.
(
Format
00~IS~CLOSE
5.2.2. Releasing New User Session Restrictions (OPEN Message)
The OPEN unsolicited message removes a previously entered CLOSE or reverses an
incomplete SHUTDOWN to permit new workstation and terminal user sessions to
start.
(
Format
00~IS~OPEN
5.2.3. Controlling Interactive Services for Terminals (REMOTE Message)
The REMOTE unsolicited message provides additional control over interactive
services for terminals. You must load lCAM and run the global user service task
(GUST) before you start interactive services for terminals. (See Section 10 for a
description of the ICAM and GUST operator procedures.)
Format
00~IS~REMOTE~[START )
SHUTDOWN
CANCEL
5-10
70045208-000
(
Interactive Services
Parameters
START
Starts interactive services for terminals after ICAM and GUST are ready.
You use this parameter when interactive services are already active in the
system (via a prior IS command or an automatic start by a workstation user).
If you enter the REMOTE START message with ICAM and GUST not ready,
an error message is displayed on the console workstation or console screen.
SHUTDOWN
Tenninates the interactive services facility for tenninals as soon as the last
tenninal session completes. (Workstation users are not affected.)
CANCEL
Immediately terminates the interactive services facility for terminals.
Tenninal users are not logged off.
(
You use interactive services with an extended set of commands and messages to
control the interactive system environment. (For a description of all interactive
services commands, see the Interactive Services Operating Guide, UP-9972. These
commands and messages enable you to exercise control over the interactive OS/3
operating system, all jobs within the system, and all terminal users.
5.2.4. Terminating Interactive Services (SHUTDOWN Message)
The SHUTDOWN unsolicited message terminates interactive services after all
sessions have completed. If no sessions are active when you enter the command, it
takes effect immediately. Otherwise, interactive services do not terminate until all
active sessions complete. An OPEN message can be used to stop a shutdown in
progress (incomplete). After the interactive services facility is completely shut down,
you can restart it only via the IS command (5.1.6); it is not automatically loaded for
workstation users via an interactive services command entry.
Format
0011ISllSHUTDOWN~
70045208-000
5-11
(
(
Section 6
Integrated Communications Access Method
(ICAM) Procedures
The integrated communications access method (!CAM) is an extension of the
supervisor (a symbiont) that handles data communications tasks. Each symbiont can
contain multiple network definitions or communications control areas (CCAs); each
CCA can handle one or more communications lines.
At system generation time, the !CAM symbionts are tailored to each user's
requirements. One or more !CAM symbionts can be configured during SYSGEN, each
symbiont satisfying specific communications network requirements; or a single !CAM
symbiont can be configured to satisfy all communications network requirements.
You must load the appropriate ICAM symbiont before the programs requiring it can
execute or before interactive services can start for terminals. In addition, when
interactive services or global networks are required, you must initiate the running of
the global user service task (GUST) after loading ICAM.
The ICAM symbiont remains in main storage until GUST is shut down. Then !CAM
shuts itself down unless you loaded ICAM with a KEEP operand. In this case, ICAM
must be terminated with a CANCEL command.
The following subsections describe how to load ICAM, change the ICAM name
established during SYSGEN, run and terminate the global user service task, and use
messages to control the active communications environment.
(
6.1. ICAM Operator Commands
6.1.1. Loading the ICAM Symbiont (CnjMn)
Key in the following CnlMn command from the console to load the !CAM symbiont.
(lOAM symbiont names are established during the COMMCT phase of system
generation.) Always load !CAM in an idle state to avoid main storage fragmentation.
Format
7004 5208-000
6-1
Integrated Communications Access Method (ICAM) Procedures
where:
{~~}
Is the lOAM synboint name as specified in the MOPNAME parameter
defined during the OOMMOT phase of system generation (n can be a value
of1 to 9).
KEEP
Keeps the ICAM symbiont loaded until you cancel it or lOAM suffers an
unrecoverable error.
lOAM loading is complete when the following output message is displayed on the
console workstation or console screen:
ICAM xx.x READY
(
where:
xx.x specifies the lOAM release level; for example, 14.0
Note:
Users can also load ICAMfrom ajob control stream with the / / CCjob
control statement. This statement allows users to load ICAM as part of your
information management system (lMS) or transaction information
processing (TIP) execution job, or as part of a job that executes the global user
service task (including the job executed as part of the automatic boot
procedure).
6.1.2. Changing the ICAM Name (SET IC)
Key in the following SET IC command to change the name of the lOAM symbiont that
is currently loaded. Use this procedure when the remote batch output has output
ready and the required lOAM symboint is not loaded.
Format
(
~ETAIC'[~~)
where:
IC
Specifies that you want to change the SPOOLIOAM SYSGEN parameter.
Specifies the ICAM symbiont name (01-09 or M1-M9) as defined at system
generation. Specifying O? indicates that you want to be queried (requested)
to supply the symboint name the next time output is ready and the required
lOAM symboint is not loaded.
6-2
7004 5208-000
Integrated Communications Access Method (tCAM) Procedures
6.2.
Initializing and Terminating the Global User Service
Task (GUST)
You can initialize GUST after ICAM is loaded and before starting interactive services
or executing user programs requiring global networks. Initialize GUST by running the
job that executes the GUST program ML$$GI. (Ask your system administrator for the
name of the job you must run to execute the ML$$GI program.) When you no longer
require global network processing, enter an unsolicited message to shut GUST down.
6.2.1. Running the Global User Service Task Job
Enter the following RUN command from the system console to initiate ML$$GI.
(
Format
RUNAjobname
where:
jobname
Names the prefiled job stream that executes the GUST ML$$GI program.
6.2.2. ML$$GI Program Operator Messages
When ML$$GI executes, it displays messages at the console workstation or console
requesting you to provide information needed to initialize the global network.
Respond to each message as indicated. (Only those messages pertaining to GUST
initialization are presented here. See the System Messages Reference Manual,
70045190 for all GUST messages.)
For the message:
MC#420 ENTER NETREQ: CCA, PASS, RESTART, LINEREQ
GUST request you to enter the cca-name, password, restart, and line information
associated with the global network to be initialized. When multinode global networks
are used, ML$$GI automatically requests all virtual lines. Use the following format
when keying your response:
Format
cca.nameA~,paSSWOrd][,restart][,line.request2J
where:
cca-name
Names the global network to be initialized. This name must be the same as
the label of the CCA macroinstruction that begins the network definition for
the global network.
7004 5208-000
6-3
Integrated Communications Access Method (lCAM) Procedures
password
Is a
one~
to eight-character password.
restart
Determines the type of restart GUST requests for the network. Key in Y for
warm starts (messages are recovered from existing disk files). Key in N for
normal reinitiatization. That is, new disk files are created if required.
line·request
Specifies the lines for which line requests are issued. Response may be one
of the following:
ALL,Y
Specifies that line requests are issued for all lines in the network. Any
errors are treated as non-fatal and the network is brought up.
line·', ••• ,line-n
Specifies the lines for which line requests are issued. Lines specified
must be identical to those specified in label fields ofrelated LINE
macroinstructions.
*
(
Displays the MC#421 message asking you to enter line request
information. (See message MC#421 which follows.)
For the message:
MC#421 ENTER LNEREQS: LINE-', LINE-2, ••• * OR BLANK
Enter the lines for which line requests are issued. This message is displayed only
when you respond to the MC#420 message with an asterisk for the line request.
where:
line-1, line·2, ••• line-n
Names the lines to be activated by means of line requests. GUST issues a
LNEREQ statement for each line-name you specifY. The line-name must be
identical to that specified in the label field of the related LINE
macroinstruction.
blank
Signals the GUST program to issue no specified line requests at this time.
(VLINES and RWS lines are automatically requested during GUST
processing.)
For the message:
MC#430 GUST ACTIVE FOR CCA nnnn
No response is required. This message informs you that the network you requested is
loaded and ready for processing; nnnn is the name of the global network loaded.
Message MC#25 or MC#20 will appear shortly after the MC#430 message.
6-4
7004 5208-000
(
Integrated Communications Access Method (lCAM) Procedures
For the message:
MC#25 nnnn ch/cu dddd CHANNEL INITIALIZED
When this message appears after the MC#430 message, it indicates that ICAM
successfully communicated with the DCP. No response is required. Specified in the
message are the name ofthe global network (nnnn), the DCP's channel/control unit
addresses (ch/cu), and the label on the DCPCHNL macroinstruction (dddd).
Message
MC#20 nnnn ch/cu dddd CHANNEL DOWN ERROR ee
(
When this message appears after the MC#430 message, it indicates that ICAM could
not establish communications with the DCP. In addition to the global network name
(nnnn), DCP channel/control unit addresses (ch/cu), and DCPCHNL macroinstruction
label, the message includes a 2-byte decimal error code (ee). Look up this code in the
Systems Message Reference Manual, 7004 5190, for its explanation and recommended
action to be taken.
6.2.3. Terminating the Global User Service Task
Key in the following unsolicited message to terminate the GUST job and end global
network processing.
Format
00~{;~}~Gu~s,network-name
where:
00
Specifies this message is destined for the supervisor.
{;~}
Identifies the currently loaded !CAM symbiont name (C1-C9 or M1-M9).
GU
Specifies this message is for GUST.
s
Specifies a shutdown is required.
network-name
Is the one- to four-character name of the active global network. This name
must be the same as the label of the CCA macroinstruction in the global
network definition.
7004 5208-000
6-5
Integrated Communications Access Method (lCAM) Procedures
If the shutdown request is accepted, the following message is displayed when the
global user service task job is canceled:
MC#401 GUST SHUTDOWN COMPLETE
Note:
To resume communications processing with global networks or to start
interactive services for terminals, you must repeat the procedures for loading
ICAM and initializing GUST. Never use the CANCEL command to cancel the
GUST job. If you do, the CANCEL command and the requested GUST
shutdown command are rejected and the following message is displayed:
MC#402
CANCE~
REJECTED, ISSUE SHUTDOWN COMMAND
6.3. ICAM Operator Messages
Occasionally, the you must communicate with ICAM to change the communications
environment or to advise ICAM of some external event. You use unsolicited messages
to do this. The descriptions of the ICAM console messages are divided into three
types:
•
Standard messages - those not related to public data networks or remote batch
processing
•
PDN unsolicited messages - those related to public data networks
•
RBP unsolicited messages - those having to do with remote batch processing
(
6.3.1. Standard Unsolicited Messages
Standard unsolicited messages to ICAM have the following format:
00A{~}ACCAf,{~},nnnn
where:
(
{~~}
Specifies the name of the required ICAM symbiont (Cl-C9 or Ml-M9).
CC
Is a two- to four-character command code.
f
Is a one-character facility type (L=line, P=port, T=terminal).
xxxx
Is a one- to four-character name of a line or terminal as defined in the label
field of a LINE or TERM macroinstruction.
6-6
7004 5208-000
Integrated Communications Access Method (ICAM) Procedures
ccpp
Specifies the input/output microprocessor (lOMP) channel number (cc) and
the single line communications adapter id (Pp) on the specified channel.
Select your parameters from the following list:
Number of IOMPs
Channel No. (cc)
SLCA No. (pp)
1 IOMP
2 IOMPs
13
13 or 15
01 to 14
01 to 14
nnnn
Is the one- to four-character name of the network as specified in the label
field of the CCA macroinstruction.
Table 6-1 lists the standard unsolicited messages ICAM provides for you. A typical
ICAM response to an unsolicited message is:
NET1 TERM TRM1 MARKED UP
This response tells you that terminal TRMl on network NETl is now available.
Table 6·1. Standard ICAM Unsolicited Messages
Message
Description
00A{Mcnn}AUPAL,xxxx,nnnn Marks line specified as available (up). Activates a communications
line. Equivalent to a line request issued by a program. lCAM can
poll, send output, and prepare to receive input. No traffic can
flow over a nonactivated communications line.
Marks line specified as unavailable (down). Stops all activity on
a communications line. lCAM does not poll, send, or receive
traffic. A switched line is disconnected. lCAM does not answer
calls or dial out.
(
00A{Mcnn}AUPAT,xxxx,nnnn Marks terminal (UNlSCOPE or DCP) or remote workstation specified
as available (UP). Enables ICAM to send output to a terminal
previously marked down.
00A{Mcnn}ADOAT,xxxx,nnnn Marks terminal (UNlSCOPE or DCP) or remote workstation specified
as unavailable (down). Stops lCAM from sending output to the
terminal specified and aborts any current session at the terminal.
If the last terminal in a poll group (UNISCOPE or remote workstation) is marked down, the entire poll group is placed on slow
poll (the group is polled about once every minute). If input
is entered at one of these terminals, a response is delayed until
the next time the terminal is polled and the terminal marked up.
When a remote workstation is marked down, its session as well as
its partner's session is aborted. (Partners are defined by the
primary/secondary specifications on adjacent TERM macroinstructions.)
continued
7004 5208-000
6-7
Integrated Communications Access Method (lCAM) Procedures
Table 6-1. Standard ICAM Unsolicited Messages (cont.)
Message
00A{~~}AUPAP,ccpp,nnnn
Description
Marks port specified as available (UP). Useful when an ICAM
symbiont contains more than one network and communications lines
are shared between them. To reassign a line:
· Down the port where the line is connected (specify the network
currently using the line).
· Using this command (UP port), reactive the port. (Specify the
network to receive the line).
·
Issue an UP command to active the communications line. (Specify
the network now using the line.)
00A{~~}ADOAP,ccpp,nnnn
Marks port specified as unavailable (down). See the preceding
message description.
00A{~~}ACNAl,xxxx,nnnn
Notifies ICAM that dialing is completed on switched line
specified. This is a response to a dialing message from ICAM to
dial a manually dialed line. ICAM does not pass traffic on the
switched line until it receives a response.
00A{~~}ACNAl,AlL,nnnn
Notifies ICAM that dialing is completed on all switched lines.
This is a response to one or more ICAM messages to manually dial
switched lines.
00A{~~}ASTAl'llll,CCCC
Displays status of a communications line (tlll) in a CCA (cccc).
00A{~~}ASTAl,*All,CCCC
Displays status of all communications lines in a CCA (cccc).
00A{~~}ASTAT,tttt,cccc
Displays status of a terminal/workstation (tttt) within a CCA
(cccc).
00A{~~}ASTAU,UUUU,cccc
Displays status of a lOCAP (uuuu) within a CCA (cccc).
00A{Cn}AUUAL,Llll,cca. Brings a switched line type up as an unattended line.
Mn
name
(
(
00A{Cn}AUMAl,llll,cca. Brings a switched line type up as a manual dial line.
Mn
name
(
6-8
7004 5208-000
Integrated Communications Access Method (lCAM) Procedures
6.3.2. Public Data Network (PDN) Unsolicited Messages
There are two kinds of public data networks: packet-switched and circuit-switched.
The fonnats for entering unsolicited messages to ICAM vary with the type of public
data network involved. The following paragraphs describe these fonnats. (See the
ICAM Operations Guide, 70044557, for infonnation about public data networks.)
Note:
In addition to the commands described in the following paragraphs, ICAM
lines connected to public data networks use the standard ICAM UP and
DOWN commands to activate and deactivate lines, terminals, or ports.
How to Enter Packet-Switched PDN Unsolicited Messages
Packet-switched public data network unsolicited messages have the following fonnat:
006{~~}6eeee6nnnn,llll[,dddd]
where:
00
Specifies this message is destined for the supervisor.
Cn
or Mn
Specifies the name of the !CAM symbiont to which this type-in is destined
(C1-C9 or M1-M9).
eccc
Specifies one of the following four-character command codes: STAT, CONN,
DISC, or TEST.
where:
STAT
Causes the status of the level 2 link, the virtual circuits, or the
subscribers to be displayed on the operator console. The llIl parameter
specifies the type of status requested.
(
CONN
Reestablishes a connection to the level 2 link after it is disconnected.
DISC
Drops (disconnects) a connection to the level 2 link.
TEST
Initiates (for DDX only) the level 2 self-testing procedures.
nnnn
Specifies the one- to four-character network name as specified in the label
field of the GGA macroinstruction.
7004 5208-000
6-9
Integrated Communications Access Method (lCAM) Procedures
llll
Specifies (for CONN, DISC, and TEST) the one- to four-character label of
the VLINE macroinstruction defining the link. For the STAT command code,
this parameter indicates the type of status to be displayed:
•
Enter link name 1111 as instructed for the other command codes for the
status of the link.
•
Enter VCT to display the status of the virtual circuit.
•
Enter SUBS to display the status of the subscriber.
dddd
Is the one- to four-character label of the PDN macroinstruction that
identifies the packet-switched public data network affected by this keyin. This parameter is optional and, if omitted, defaults to the label of
the first PDN macroinstruction in the network definition.
(
How to Enter Circuit-Switched PDN Unsolicited Messages
The following formats are available for entering circuit-switched public data network
unsolicited commands to ICAM.
In general, when the PDN keyword is omitted, the default is the label on the first
PDN macroinstruction in the ICAM network definition. When the LDTE keyword is
omitted, the default is the label on the first LDTE macroinstruction in the ICAM
network definition.
Formatl
00~{cn}~STAT~nnnllLDTE=ldte.namel[IPDN=pdn.nameJ
Mn
RDTE=rdte·name
TERM=term·name
cPs={CC }
ALL
(
Displays the status of the specified LDTE, RDTE, terminal (TERM), or call progress
signal (CPS), where:
{~~}
Specifies the name of the ICAM symbiont for which this command is
destined (C1-C9 or M1-M9).
nnnn
Specifies the one- to four-character network name as specified in the label
field of the CCA macroinstruction.
ldte-name
Is the label on an LDTE macroinstruction in the ICAM network definition.
6-10
7004 5208-000
Integrated Communications Access Method (lCAM) Procedures
rdte-name
Is the label on an RDTE macroinstruction in the !CAM network definition.
term-name
Is the label on a TERM macroinstruction in the !CAM network definition.
CC
Specifies a valid call progress signal number.
pdn-name
Is the label on a PDN macroinstruction in the lCAM network definition.
Format 2
00a{Cn}aNETSannn,!LOTE=ldte-narnej[,PON=pdn-namel
Mn
ROTE=rdte-name
CPS={CC }
ALL
(
Displays the network statistics for the specified LDTE, RDTE, or call progress signal
(CPS).
FormatS
00a{~~}aCONNannn,ROTE=rdte-name[,LOTE=ldte-name][,PON=pdn-name]
Establishes a connection to the specified RDTE.
Format 4
00a{~~}aOISCannn,ROTE=rdte-narne[,LOTE=ldte-namel[,PON=pdn-narne]
Disconnects from the specified RDTE.
Format 5
00a{Cn}aCHNGannn, ROTE=rdte.name!,AOOR=addreSSj [LOTE=ldt e-name] [,PON=pdn-name]
Mn
oscO=t
OSCI=t
TIME=t
(
For the specified RDTE, changes:
a.
Network address (ADDR=address) (maximum 16 digits)
b.
For terminal connections
Time before disconnect following output (DSCO) (range 0-32767)
Time before disconnect following input (DSCI) (range 0-32767)
c.
70045208-000
For host to host connections, the activity timer (TIME) (range 0-32767)
6-11
Integrated Communications Access Method (lCAM) Procedures
FormatS
00A{Cn}ACHNGAnnn,CPS=CC!,NIR=njtLDTE=ldte-name][,PDN=pdnoname]
Mn
TIR=n
NSR=n
TSR=n
TBD=n
For the specified call progress signal (OPS), changes:
a.
lOAM retry parameters where
NIR = number ofIOAM retries (range 0-32767)
TIR
b.
= time between lOAM retries (range 0-32767)
SLOA retry parameters where
(
NSR = number of SLOA retries (range 0-63)
TSR = time between SLOA retries (range 0-255)
c.
Time before disconnect (TBD) (range 0-254)
For further descriptions of these parameters and their usage, refer to the ICAM
Operations Guide, 70044557.
6.3.3. Remote Batch Processing (RBP) Unsolicited Messages
You communicate with the remote batch processing lOAM symbiont by means of
console commands in the form of unsolicited messages. These commands enable you
to specify the functions you want performed. The format of a remote batch processing
unsolicited message is:
00A{~~yCC[ID]
(
where:
{~~}
Specifies the two-character remote batch processing lOAM symbiont
identifier (01-09) or (M1-M9).
CC
o
6-12
Specifies two-character command code.
Is an optional dump operand associated with the SH command.
7004 5208-000
Integrated Communications Access Method (ICAM) Procedures
The following command codes are accepted by remote batch processing. They are
explained in detail in the ICAM Utilities Programming Guide, 70044565.
•
SH
Specifies shutdown. It removes the ICAM symbiont from the system when
remote batch processing is the only active !CAM interface or idles remote batch
processing when other !CAM interfaces are active in the same ICAM symbiont. If
you specify the n option on the SH command, your system produces a dump
during termination of the ICAM symbiont.
•
RB
Reactivates remote batch processing after it has been idled by an SH command.
(
•
RD
Starts the reading of batch jobs or data files from the central processor card
reader under control of remote batch processing.
6.4. Downline Loading a Telcon File
The two procedures that follow let you downline load a Telcon file to a DCP front-end
processor or a ncp remote concentrator. Additional detailed information concerning
this subject is presented in the Integrated Communications Access Method (lCAM)
Utilities Programming Guide, 7004 4565.
6.4.1. Loading Telcon File to Front-End Processor (DCP)
Perform the following sequence to d~wnline load a Telcon file to a ncp front-end
processor:
1.
Load the !CAM symbiont.
2.
Run GUST.
3.
Initialize the line over which the ncp load sequence is to occur. (GUST
automatically does this unless the line was previously marked down, in which
case you must enter an unsolicited command to reinitialize the line.)
4.
At the ncp front-end processor, initiate a Telcon load sequence. Refer to the
DCP / OS Operations Reference Manual, 7831 5702, for information on initiating
downline loading from a ncp.
Note:
70045208-000
To avoid reinitializing the line, it is recommended that you start the downline
load procedure at the DCP before GUST is executed.
6-13
Integrated Communications Access Method (ICAM) Procedures
6.4.2. Loading Telcon File to Remote Concentrator (DCP)
Perform the following sequence to downline load a Telcon file to a DCP remote
concentrator:
1.
Load the ICAM symbiont.
2.
Run GUST.
3.
Initialize the line over which the DCP load sequence is to occur. (GUST
automatically does this unless the line was previously marked down, in which
case you must enter an unsolicited command to reinitialize the line.)
4.
Start the TELRCLD job stream by entering:
(
RV TELRCLD
The following message is displayed:
ENTER NETWORK NAME, PASSWORD, LOCAP NAME
Respond to this message with the network (CCA) name, the password (if any),
and the word LOAD (the LOCAP name).
5.
At the DCP remote concentrator, initiate a Telcon load sequence. Refer to the
DCP / OS Operations Reference Manual, 7831 5702, for information on initiating
a downline load from a DCP.
6.
The TELRCLD job now displays the following messages to indicate the status of
the load operation:
RCLD Established a Session
Remote Load of DCPID 156 Started Load ELT PRCnnn
Remote Load of DCPID 156 Complete Load ELT PRCnnn
7.
(
The TELRCLD job remains in memory after the load is completed. If desired,
you can use it to load another remote concentrator. To terminate the TELRCLD
job, enter:
UNS TELRCLD TERM
6-14
7004 5208-000
Section 7
System Utility Services
The system utility symbiont (SL$$SU) is a multipurpose utility that allows you to
perform many card, tape, disk, and diskette functions at the console workstation or
console. To initiate a function, you include its function code as a parameter with the
SU!rU command or enter it as a solicited message. The functions you can perform
and their function codes are listed in Table 7-1. The SU!rU command and the
functions for card, tape, disk, and diskete are described in 7.1 through 7.5.
7004 5208-000
7-1
System Utility Services
Table 7·1. System Utility Functions
Function Code
Function Performed
Card Functions
CC
CCB
CCS
CT
CTR
CP
CH
JCP
Reproducing cards punched in Hollerith code
Reproducing cards punched in binary and Hollerith code
Reproducing and resequencing source programs
Writing card to tape in unblocked format
Writing card to tape in blocked format
Listing cards
Listing cards containing compressed mode
Punching cards from the system console
Tape Functions
TT
TH
THR
TP
TPR
TRS
TC
INT
FSF
BSF
FSR
BSR
WTM
REW
RUN
ERG
copying a tape to another tape
Printing a tape in character and hexadecimal format
Printing a tape in character, hexadecimal, deblocked format
Printing a tape containing only standard characters
Printing a tape in character and deblocked format
Locating a specific record on tape
Punching cards from tape
Prepping a tape
Forward space to a specific file
Backward space to a specific file
Forward space to a specific record
Backward space to a specific record
Writing tape marks
Rewinding a tape
Rewinding a tape with interlock
Erasing a portion of a tape
Disk and Format Label Diskette Functions
DD
DDR
VTP
SVT
AVX
Printing a disk in unblocked format
Printing a disk in deblocked format
Printing the volume talb of contents of disk
Printing short format VTOC file
Displaying available disk extents on console screen
(
Data Set Label Diskette Functions
DO
DDR
VTP
Printing a diskette in unblocked format
Printing a diskette in deblocked format
Printing the data set labels of a diskette
NOTE: If XXX is entered in place of the function code, all function codes are displayed.
7·2
70045208-000
System Utility Services
7.1. System Utility Commands and Messages (SUjTU)
The SUII'U command loads the system utility symbiont. SU and TU can be used
interchangeably for all functions. However, we recommend that you use TU for tape
operations because it increases the buffer size for tapes from 8,189 to 32,767 bytes.
You can include the required function as a parameter with the SUII'U command.
A spooling parameter also can be entered with the command, if spooling is configured
in your system. (For the description of all spooling commands, see the Spooling and
Job Accounting Operating Guide, 70044581.)
When you enter the command alone to load the symbiont, you enter the function as a
solicited message. After the symbiont is loaded, you control it by responding with
solicited messages. You use unsolicited messages only to terminate the symbiont or
current symbiont functions on certain occasions.
Note:
The SU /TU command cannot be issued from an enter stream.
Format
Positional Parameter 1
function-code
Specifies the appropriate two- or three-character function code. (Function
codes are listed in Table 7-1.) If omitted, the symbiont displays a message
requesting that you enter a function code. All possible function codes that
are recognized by either symbiont can be displayed on the console or console
workstation by entering XXX in place of the function code. Following this
display, the symbiont requests that you enter the required function code.
(
Positional Parameter 2
Spools the system utility output.
N
Specifies that the system utility output is not spooled.
R
Retains system utility output in the HOLD condition in the spool file after it
is printed or punched. The retained output is unavailable for additional
processing until released via the BEGIN SPL command.
70045208-000
7-3
System Utility Services
H
Places system utility output in the HOLD condition in the spool file before it
is printed or punched. The output must be released via the BEGIN SPL
command to permit processing.
This parameter is entered only if spooling is configured in your system. When Y is
specified or taken as the default condition, the output writer automatically prints any
spooled output at the end of every SU function.
Operator Considerations
•
When the symbiont is loaded, the following message is displayed:
nn6SYSTEM UTILITY SYMBIONT LOADED
SUNNNN
where:
nn
(
Is the two-digit message number
SUNNNN
Is the name of the symbiont sending the message. This name is the twocharacter symbiont identification plus a four-digit binary job number
inserted at task initiation.
•
If the command entry includes a function code, the symbiont completes the
requested function, then displays an ENTER REQUIRED FUNCTION message
to allow you to either terminate the symbiont or request another function.
(
If you omit the function code, the symbiont displays the ENTER REQUIRED
FUNCTION message to allow you to enter a function.
The ENTER REQUIRED FUNCTION message is displayed as follows:
a.
With spooling:
nn?ENTER REQUIRED FUNCTION AND SPOOL OPTION [,Y,N,R,H]iDEFAULT=Y
b.
SUNNNN
Without spooling:
nn?ENTER REQUIRED FUNCTION
SUNNNN
Initiate the required function with the keyin:
a.
74
With spooling:
7004 5208-000
(
System Utility Services
b.
Without spooling:
nn~funct;on-code
Each time the symbiont completes a requested function, it transmits the ENTER
REQUIRED FUNCTION message to allow you to either terminate the symbiont
or request another function.
•
If your system supports spooling and the spool option is incorrectly entered (i.e., a
character other than Y, N, R, or H is entered), the following message is displayed:
nn?IS{PRINTED}OUTPUT TO BE SPOOLED FROM SU Y,N,R,H
PUNCHED
SUNNNN
Enter the required spooling option with the keyin:
(
To terminate the symbiont, you reply to the ENTER REQUIRED FUNCTION
with the end-of-job keyin:
nn~EOJ
The symbiont terminates and displays the message:
nn~SYSTEM
•
UTILITY SYMBIONT ENDED
SUNNNN
You can also end the symbiont by pressing the MSG WAIT key on the console
workstation or console and keying in the applicable unsolicited message:
00~SU~EOJ
00~TU~EOJ
This permits you to terminate the symbiont before it completes a function.
(
•
To terminate only the current function of the symbiont, key in the applicable
unsolicited message:
00~SU~END
00~TUIlEND
Note:
7004 5208-000
When message replies are keyed in incorrectly or the reply cannot be honored,
the symbiont requests the information to be keyed in again. If no
determination can be made on why the keyed input is not accepted, use the
previous unsolicited message to terminate the current function or to terminate
the symbiont.
7-5
System Utility Services
7.2. Card Functions
All the card functions you can perform are described in this subsection. All input card
files must be terminated by a card with the words END OF DATA punched in
columns 1 through 11.
Proceed as follows to perform the card functions.
1.
As described in 7.1:
a.
Enter the SU symbiont command.
b.
Enter the appropriate function code either as a command parameter or as a
solicited message response to the ENTER REQUIRED FUNCTION
message.
c.
Enter the spooling option; otherwise, default is Y (applicable only if spooling
is configured).
(
2.
If a card file is being read, place it in the card reader designated the system
reader (SYSRDR). Ifthis card reader is unavailable, the first available card
reader is assigned to the symbiont, causing the following message to be displayed
on the console workstation or console:
nnAUSE READER did
SUNNNN
where:
(
did
Is the device address of the card reader assigned to read the input file.
If no card readers are available, the function aborts and the following
message is displayed on the console workstation or console:
nnANO READER AVAILABLE
SUNNNN
Likewise, if the required output device is not available, the function
aborts and the following message is displayed on the console
workstation or console:
nnANO!PUNCH jAVAILABLE
TAPE
PRINTER
SUNNNN
If the required devices are available, the operation continues for each function code as
described in 7.2.1 through 7.2.8.
7-6
70045208-000
(
System Utility Services
7.2.1. Reproducing Cards Punched in Hollerith Code (CC)
You use the CC function code to reproduce cards in 80 x 80 format containing the
Hollerith code. All job control cards, even the 1*, can be reproduced by using this
function. You must submit an END OF DATA card with your input deck indicating
the end of file to the symbiont.
7.2.2. Reproducing Cards Containing Binary Data (CCB)
You use the CCB function to reproduce cards containing binary data in addition to the
Hollerith code. Again, you must submit an END OF DATA card as the last card in
your input deck. When punching column binary, the output must not be spooled.
7.2.3. Reproducing and Resequencing Source Programs (eCS)
You use the CCS function code to reproduce and resequence an assembler (BAL),
COBOL, or RPG II source language program. For a BAL program, the program name
can be up to three characters in length; COBOL can be up to eight characters in
length; and RPG II can be up to six characters in length. If you supply a name having
fewer characters than the number permitted, the name is left-justified and spacefilled. You must submit an END OF DATA card as the last card of your source
program. Tables 7-2 through 7-4 show the formats of the source programs being
reproduced and resequenced.
Table 7-2. Assembler Format
Column
Description
1-72
Source statement
73-75
3'character program name
76-80
5-character sequence number; first number is 00010. Succeeding
numbers are incremented by 10.
Table 7-3. COBOL Format
Column
Description
1-3
Page sequence number; starts at 001 and is incremented by every 20
lines (cards)
4-6
Line sequence number; starts at 010 and is incremented by 10 for
every line up to 200
7-72
Source statement
73-80
8-character program name
70045208-000
7-7
System Utility Services
Table 7-4. RPG Format
Column
Description
1-2
Page number sequence; starts at 01
3-5
Line number sequence; starts at 010 and is incremented by 10 for
every line up to 200
6-74
Source statement
75-80
6-character program name
7.2.4. Writing Cards to Tape in Unblocked Format (CT)
You use the CT function code to write cards to an unblocked tape in 80 x 80 fonnat.
You must submit an END OF DATA card in your input deck indicating the end offile
whereby two tape marks are then written on your tape.
(
Procedure
Copies a deck of cards onto an unlabeled output tape in 80 x 80 fonnat. No leading
tape marks are written, but two tape marks are written when the END OF DATA
card is read. Each data block is 80 bytes long. You specify the tape unit device
address, and the density and mode in which the tape is written at execution time. The
tape is not rewound at either the beginning or the end of this function.
(
For the message:
nn?CUUMMB OUTPUT TAPE B=BLK CNT
SUNNNN
You respond with the tape unit device address, mode setting, and block count
characteristics of the output tape (as described in 7.3.1).
If the output tape reaches EOV before all the card input is processed, SU writes two
tapemarks, rewinds, and unloads the tape.
For the message:
nn?MOUNT NEXT OUTPUT TAPE. REPLY R OR END
SUNNNN
Key in the following if the CT function is to be terminated:
nnilEND
7-8
70045208-000
(
System Utility Services
Otherwise, dismount the unloaded tape, mount the next output tape; then
Key in:
nnM
For the message:
nn?DOES USER WISH TO PREP THIS TAPE? REPLY YES OR NO
SUNNNN
Key in:
nn6N
nn6Y
(
If no tape prep is required. The CT function resumes, using the new output
tape.
To prep the tape. The SU INT tape function is activated (see "Prepping a
Tape (INT)" in 7.3.3). The CT function resumes when INT function is
completed.
7.2.5. Writing Cards to Tape in Blocked Format (CTR)
You use the CTR function code to write cards to a tape in blocked format. The
blocking factor is in the range of 1 to 100 for SU and 1 to 400 for TU.
Procedure
Same as the CT function, except that tape blocks written are 80 x {long, where f is
the blocking factor. Ifthe last block is not full, the length of the last block is 80 x r,
where r is the number of records in the last block.
For the message:
nn?BLK FACTOR
SUNNNN
You respond with blocking factor 1 to 100 (SU) or 1 to 400 (TU).
For the message:
nn?CUUMM OUTPUT TAPE B=BLK CNT
SUNNNN
You respond with the tape unit device address, and the mode setting of the output
tape (see 7.3.1).
7004 5208-000
7-9
System Utility Services
For the message:
nn?OUTPUT EXCEEDS ALLOCATED BUFFER
SUNNNN
You must reenter the function and blocking factor because the factor supplied was
greater than the maximum allowed and the function was terminated.
Multivolume output tape is described in "Tape Addressing" in 7.3.3.
7.2.6. Listing Cards (CP)
You use the CP function code to list cards in 80 x 80 format on the printer. You must
submit an END OF DATA card as the last card in your input. Only printable punch
configurations are printed; however, any standard punch configuration is accepted.
The function is useful when listing your job control cards.
(
7.2.7. Listing Cards Containing Compressed Mode (CH)
You use the CH function code to list cards containing the compress mode
(hexadecimal characters) and the standard characters. Again, you must have an END
OF DATA card as the last card in your input deck.
7.2.8. Punching Cards from the System Console (JCP)
The JCP function punches job control or data cards entered through the console
workstation or console. Up to 60 columns may be entered in reply to the scale
message. If 60 or more columns are needed, position the cursor under the 0 of 60 in
the scale message and transmit. Another message requesting 20 more characters will
appear. If a card having a blank in column 1 or column 61 is required, key in a right
parenthesis instead of a blank in that column. The symbiont replaces a right
parenthesis in column 1 or 61 with a blank. The right parenthesis is needed because
all messages received by SU are returned left-justified. To terminate the JCP
function, key in lEND and transmit immediately.
7.3. Tape Functions
Use the SU command if your tape block size does not exceed 8189 bytes; TU supports
tape blocks up to 32,767 bytes.
7·10
7004 5208-000
(
System Utility Services
1.3.1. Tape Addressing
The tapes to be used for a TU function must be identified using the tape unit !D.
Communication by you is initiated by the following message:
cuunmb
where:
cuu
Is device ID (channel and unit).
nm
Is mode setting of the tape. Ifmm is blank, 00, or not entered (e.g., response
is 102), the SYSGEN mode settings are assumed. Commonly used mode
settings are:
CO for 1600 bpi (PE)
C8 for 800 bpi (NRZ)
DO for 6250 bpi (GCR)
E9 for slow-speed operation (50 ips)
F9 for fast-speed operations (100 ips)
Refer to the System 80 as /3 Job Control Programming Guide, 7004 4623,
for information on mode settings.
b
Is block count characteristics of the tape. Ifblank or omitted, the tape is
assumed not to have a block count. Ifb is entered, the tape is assumed to
have a block count.
Notes:
(
1.
The block count specification is 'not needed for tape functions used to position a
tape (e.g., FSF).
2.
The record number (REC) printed by the system utility for the TRS function is
relative to the beginning of scan. For other tape functions, it is relative to where
printing begins. The REC number does not correspond to the 3-byte block number
on block numbered tapes.
3.
The block number (TBLKJ printed for the TRS function is a display of the 3-byte
block number prefixed to block-numbered tapes.
1.3.2. Tape Error Processing
If an error is encountered on an input tape, control is turned over to a tape error
correction routine, where communication is established with you to determine
whether the error should be ignored or bypassed or the function terminated.
7004 5208-000
7-11
System Utility Services
If an error is ignored, the record is processed as is and the tape is forward spaced to
the next block. If an error is bypassed, no information from the bad block is processed
and the tape is forward spaced to the next block.
The messages:
nn~TAPE ERROR ON INPUT TAPE
nn?B-BYPASS, I-IGNORE, OR E-END FUNCTION
SUNNNN
SUNNNN
indicates a tape error has occurred and one of the following options may be replied:
nn~BYPASS
(This reply is not applicable during a TRL function.)
nn~IGNORE
nn~END
The message:
nn~WARNING:
TAPE BLK FILLS AVAILABLE BUFFER OR MAY BE TRUNCATED
SUNNNN
(
warns that a tape input or output record completely fills the allocated buffer. SU
reads/writes a maximum of8189 bytes and TU reads/writes a maximum of 32,767
bytes; any tape block exceeding this is truncated.
1.3.3. Tape Operating Instructions
To perform a tape function, proceed as follows:
1.
2.
As described in 7.2:
a.
Enter the TU symbiont command (or enter SU if the tape block size does not
exceed 8189 bytes).
b.
Enter the appropriate function code either as a command parameter or as a
solicited message response to the ENTER REQUIRED FUNCTION
message.
c.
Enter the spooling option; otherwise, default is Y (applicable if spooling is
configured).
Place the input tape volume on an available tape unit, and identifY the tape unit
to the TU (or SU) symbiont by keying in its unit address as described in 7.4.1.
If the required devices are available, the operation continues for each function code,
as described in this subsection.
7-12
7004 5208-000
(
System Utility Services
Copying a Tape to Another Tape (TT)
You use the TT function code to copy from one tape to another tape of the same or
different device type. You can copy either labeled or unlabeled tapes in blocked or
unblocked format. If you are copying standard label tapes, the file marks are used as
controlling devices. The first file mark on the tape includes the header record; the
second file mark includes all of your data; and the third file mark includes the trailer
record. Therefore, three file marks make up one complete file.
Procedure
For the messages:
nn?CUUMMB'INPUT TAPE B=BLK CNT
(
SUNNNN
Respond with the tape unit device address, and the mode setting and block count
characteristics of the input tape (7.3.1).
nn?CUUMMB'OUTPUT TAPE B=BLK CNT
SUNNNN
Respond with the tape unit device address, and the mode setting and block count
characteristics of the output tape.
nn?#FILES 1·99
SUNNNN
Respond with the number of files or file marks to be copied. The number must be
from 1 through 99. See the previous description ofTT for the number offiles on a
standard labeled tape.
If a high density tape is copied to a lower density, or if you copy a longer tape to a
shorter tape, all of the input tape data may not fit on the output tape. SUIl'U provides
the option of mounting another output tape to continue. When the output tape reaches
EOV before all the tape input is processed, SUIl'U:
(
•
Writes two tape marks
•
Writes EOV labels, when appropriate, to correspond to a previously copied HDR1
HDR2 label set
•
Rewinds and unloads the tape
For the message:
nn?MOUNT NEXT OUTPUT TAPE. REPLY R OR END
SUNNNN
Key in:
nnAEND
If the TT function is to be terminated.
7004 5208-000
7·13
System Utility Services
Otherwise, dismount the unloaded tape, mount the next output tape; then
Key in:
nnM
If the input tape and the newly mounted output tape are prepped, the TT function
resumes. If the input tape is prepped but the new output tape is not, SUII'U queries
the operator.
For the messages:
nn~SUPPLY
VOLUME SERIAL NUMBER FOR NEW OUTPUT TAPE
nn?XXXXXX
SUNNNN
SUNNNN
Key in:
(
nn~vsn
where:
vsn
Is the six-character volume serial number for the new output tape. If the vsn
is less than six characters, it is left-justified by SUII'U. The TT function
resumes, using the new output tape.
For the message:
USER LABEL RESTRICTIONS APPLY.
This message cautions you that SUII'U does not generate user trailer or header labels
for multivolume output in addition to those actually encountered on the input tape.
For the message:
nn?END OF VOLUME? Y OR N
SUNNNN
This message is issued after all files specified are copied. Key in Y to write a second
tape mark after the file; otherwise N if it is not to be written. After processing this
response, the function is completed.
An example of tape copy with block count is as follows:
System message:
nn?CUUMMB - INPUT TAPE
SUNNNN
Operator response:
nn~10M~B
7-14
7004 5208-000
System Utility Services
System message:
nn?CUUMMB - OUTPUT TAPE
SUNNNN
Operator response:
nnt.101t.l!B
System message:
nn?#FILES 1-99
SUNNNN
Operator response:
nnt.3
System message:
/
<
nn?END OF VOLUME? YIN
SUNNNN
Operator response:
nnt.Y
Printing a Tape in Character or Hexadecimal Format (TH)
You use the TH function code to print a tape containing either standard or
compressed mode (hexadecimal) characters. The tape error correction routine is
enabled to allow you to bypass or ignore tape errors with this function. Tape
positioning does not occur at either the beginning or the end of this function. The
block number printed is relative to the location where printing begins.
Procedure
An option allows you to print the entire field or only a specified number of blocks:
nn?CUUMMB - INPUT TAPE B=BLK CNT
SUNNNN
Respond by entering the tape unit device address and the mode setting and block
count characteristics of the input tape (see 7.3.1). If you enter a block count, data is
considered to begin in position 3, relative to position 0, for a length of block size minus
3 bytes.
nn?#BLKS OR END
SUNNNN
Respond END to print the entire tape, or respond with the number of blocks to be
printed. If the end-of-file code (that is, two tape marks side by side) is detected before
the specified number of blocks is printed, the function terminates.
7004 5208-000
7-15
System Utility Services
Printing a Tape in Character or Hexadecimal Deblocked format (THR)
You use the THR function code to print records from a tape individually rather than
in a contiguous string. Prints logical tape records in character and vertical
hexadecimal formats. The tape error correction routine is enabled to allow you to
correct, bypass, or ignore tape errors for this function.
Procedure
An option allows you to print the entire file or only a specified number of blocks.
nn?CUUMMB - INPUT TAPE B=BLK eNT
SUNNNN
Enter the tape unit device address, and the mode setting and block count
characteristic of the input tape (see 7.3.1). If you specify block count, data is
considered to begin in position 3, relative to position 0, for a length of block size minus
3 bytes.
(
If you specify B (for block count), the following message is displayed:
nn?#BLKS OR END
SUNNNN
If the entire tape is to be printed, enter END. To print a specified number of blocks,
enter a decimal number indicating the number of blocks to be printed. If the end of
file (two tapemarks side by side) is detected before the specified number of blocks are
read, the function is terminated.
nn?LOGICAL REC LNTH
SUNNNN
(
Respond with the logical record length.
Printing a Tape Containing Only Standard Characters (TP)
You use the TP function code to print a tape in blocked format containing only
standard characters. This function is identical to the TH function, except that your
output is only in character format rather than character and hexadecimal format.
Printing a Tape in Character and Deblocked format (TPR)
You use the TPR function code to print records from a tape individually in character
format only. This function is identical to the THR function, except that your output is
in character format rather than character and hexadecimal format.
7-16
7004 5208-000
(
System Utility Services
locating a Specific Record (TRS)
You use the TRS function code to search for one or more specific logical records in
your file. The following information is needed for the symbiont to locate the record:
•
Logical record length
•
Length scan argument (length of the data field)
•
Starting data position in your record
•
Whether the data is in character or hexadecimal format
•
Actual data needed
(
Procedure
You identify the scan field with the length and location within the logical record. The
logical record length is also required for deblocking purposes. When you enter the
scan argument in either hexadecimal or character format, it is compared to the scan
field of each logical tape record and printed on the printer for future reference. When
an equal is located, the block having the record is printed in character and
hexadecimal format.
After each find, you are given the option of continuing the scan for more finds or
terminating the function. Tape positioning does not occur at either the beginning or
the end of this function. The tape error correction route is enabled, so you can ignore
or bypass tape errors (see 7.3.2). The function is terminated either at the end-of-file
(two tape marks side by side) or when a find is made and you terminate the function.
The scale is printed to improve readability. You also enter the scan argument for use
in the search.
For the messages:
(
nnAINVALID HEX CHAR
SUNNNN
An error message is printed when the scan argument is entered in hexadecimal and
an invalid hexadecimal character was detected. You reenter the sequence to obtain the
scan argument.
nnANO MATCH FND
SUNNNN
This message is printed when an end-of-file mark (two tape marks back to back) is
encountered before any finds were made. The function is terminated.
nnACONTINUE SCAN? YIN
7004 5208-000
SUNNNN
7-17
System Utility Services
This message is printed each time a find is made. You enter Y to continue the scan or
N to terminate the scan.
The displayed find record is preceded by a header that includes:
REC
Specifies the sequential number of the record, which is relative to the
beginning of the search.
DATA
Specifies the logical record length.
TBlK
Specifies the block number, which is maintained by the system in a 3-byte
prefix to each tape block.
An example of a tape with block count that is to be searched for a tape record
containing a key field of "4637275467" in the first 10 bytes of the record is as follows:
(
System message:
nn?CUUMMB - INPUT TAPE
SUNNNN
Operator response:
nn1l10000B
System message:
nn?lOGICAl REC lENGTH
SUNNNN
Operator response:
nn1l125
System message:
nn?lENGTH ARGUMENT (1-3010/)
SUNNNN
Operator response:
nn1l10
System message:
nn?STARTING DATA POSITION IN REC
SUNNNN
Operator response:
nnil1
7-18
7004 5208-000
(
System Utility Services
System message:
nndENTER IN HEX-H, CHAR-C
SUNNNN
Operator response:
nndC
System messages:
nndENTER 10 BYTES, 1 CHAR PER BYTE
nn?1 ••• S.•• 10 •••
SUNNNN
SUNNNN
Operator response:
nnd463727S467
(
System message:
nn?CONTINUE SCAN? YIN
SUNNNN
Operator response:
nndN
Punching Cards from a Tape (Te)
You use the TC function code to punch cards from either a blocked or unblocked tape.
The data portion of the tape is transferred 80 bytes at a time to the card. If the data
portion of the block is not a multiple of 80, the remaining data is left-justified and
space-filled. When a tape mark is detected, a card containing all asterisks (*) is
punched. When two tape marks are detected back to back, the function ends.
Procedure
When a tape mark is encountered, a card with all * is punched. The function is
terminated when two tape marks back to back are encountered. Tape error processing
is described in 7.3.2.
For the message:
nn?CUUMMB . INPUT TAPE B=BLK CNT
SUNNNN
Respond with the tape unit device address, and the mode setting and block
characteristics ofthe input tape (as described in 7.3.1).
7004 5208-000
7-19
System Utility Services
Prepping a Tape (INT)
You use the INT function code to prep a tape by writing a standard label on a
specified tape. When you enter the volume serial number and file label, the tape is
positioned to the load point prior to the prep and the VaLl, HDR1, and HDR2labels
are written, along with two tape marks. When the prep is completed, the tape is
positioned following the first tape mark. No AVR is performed; the volume serial
number is not entered in the tape unit physical unit block (pub). It is, therefore,
possible to prep multiple tapes with the same vsn.
Procedure
For the messages:
nn?CUUMMB - OUTPUT TAPE B=BLK CNT
SUNNNN
Respond with the tape unit device address and the mode setting and block count
characteristic of the output tape (refer to 7.3.1).
nnAENTER NEW FILE LABEL
nn?XXXXXXXXXXXXXXXXX
SUNNNN
SUNNNN
Enter up to six digits for VaLl record. If you enter fewer than six digits, the new
volume serial number is left-justified and space is filled on the right.
nnAENTER OWNER 1.0. OR SCRATCH
nn?XXXXXXXXXXXXXXXXX
SUNNNN
SUNNNN
Enter up to 17 characters for a new owner identifier.
Example
System message:
nn?CUUMMB • OUTPUT TAPE
SUNNNN
Operator response:
(
nnA10100B
7-20
7004 5208-000
System Utility Services
System messages:
nnAENTER NEW VOL#
nn?XXXXXX
SUNNNN
SUNNNN
Operator response:
nnA001036
System messages:
nnAENTER NEW FILE LABEL
nn?XXXXXXXXXXXXXXXXX
SUNNNN
SUNNNN
Operator response:
nnATAPE1
(
\
System messages:
nnAENTER OWNER 1.0. OR SCRATCH
nn?XXXXXXXXXXXXXXXXX
SUNNNN
SUNNNN
Operator response:
nnAMr. Smith
Forward Space to a Specific File (FSF)
You use the FSF function code to advance the tape to the next tape mark.
Procedure
Advances the specified tape to the next tape mark.
For the message:
nn?CUUMM • OUTPUT TAPE
(
SUNNNN
Enter the tape unit device address and the mode setting ofthe tape to be spaced
forward Crefer to 7.3.1).
7004 5208-000
7-21
System Utility Services
Backspace to a Specific File (BSF)
You use the BSF function code to backspace the tape until a tape mark is
encountered.
Procedure
For the message:
nn?CUUMM • OUTPUT TAPE
SUNNNN
Enter the tape unit device address and the mode setting of the tape to be backspaced
(refer to 7.3.1).
forward Space to a Specific Record (FSR)
(
You use the FSR function code to forward space a specific number of blocks on your
tape.
Procedure
For the message:
nn?CUUMM . OUTPUT TAPE
SUNNNN
Enter the tape unit device address and the mode setting of the tape to be forward
spaced (refer to 7.3.1).
nn?#BLKS
SUNNNN
Enter the number of blocks to be advanced (maximum number is 9999).
Backspace to a Specific Record (BSR)
You use the BSR function code to backspace a specific number of blocks on your tape.
Procedure
For the message:
nn?CUUMM . OUTPUT TAPE
SUNNNN
Enter the tape unit device address and the mode setting ofthe tape to be backspaced
(refer to 7.3.1).
nn?#BLKS
SUNNNN
Enter the number of blocks to be backspaced (maximum number is 9999).
7·22
7004 5208-000
(
System Utility Services
Write Tape Marks (WTM)
You use the WTM function code to write tapemarks on your file.
Procedure
For the message:
nn?CUUMM . OUTPUT TAPE
SUNNNN
Enter the tape unit device address and the mode setting of the output tape (refer to
7.3.1).
Rewind Tape (REW)
(
You use the REW function code to rewind your tape to load point.
Procedure
For the message:
nn?CUUMM . OUTPUT TAPE
SUNNNN
Enter the tape unit device address and the mode setting of the tape to be rewound
(refer to 7.3.1).
Rewind and Unload Tape (RUN)
You use the RUN function to rewind either UNISERVO 16 or UNISERVO 20 tapes to
load point with interlock.
Procedure
(
For the message:
nn?CUUMM . OUTPUT TAPE
SUNNNN
Enter the tape unit device address and the mode setting of the tape to be rewound
(refer to 7.3.1).
7004 5208-000
7-23
System Utility Services
Erase Tape Record Gap (ERG)
You use the ERG function code to erase a portion of your tape. This function is useful
to erase known defective areas on your tape. Erases the specific tape for
approximately 3.5 inches.
Procedure
For the message:
nn?CUUMM - OUTPUT TAPE
SUNNNN
Enter the tape unit device address and the mode setting of the tape to be erased (refer
to 7.3.1).
7.4. Disk and Format Label Diskette Functions
The disk and format label diskette functions that can be performed are described in
the following subsections.
1.4.1. Operating Considerations
Consider the following when operating with the system utility on disks or format
label diskettes:
•
An end-of-file record is a disk record on which data length is in binary zeros (not
applicable on IDA disks).
•
The system utility should be run only when no other job will be starting up or
performing multiple steps that will allocate the same volumes. This could cause
the system utility to terminate abnormally.
1.4.2. Disk and Format Label Diskette Operating Instructions
(
Proceed as follows to perform a disk or format label diskette function:
7-24
1.
Place the subject disk/diskette volume on an available unit.
2.
As described in 7.1:
a.
Enter the SU symbiont command.
b.
Enter the function code as a command parameter or as a solicited message
response to the ENTER REQUIRED FUNCTION message.
c.
Enter the spooling option; otherwise, default is Y (applicable if spooling is
configured).
7004 5208-000
System Utility Services
7.4.3. Printing a Disk or Format Label Diskette in Unblocked Format (DD)
You use the DD function code to print your disk pack or format label diskette in
character and hexadecimal format. The DD function does not deblock your logical
records.
Procedure
For the messages:
nn?ENTER DVC ADDRESS
SUNNNN
Enter the disk or diskette unit device address of the disk pack or format label diskette
to be displayed.
nn?CCCHH • BEGIN OR FILE-ID
(
SUNNNN
Enter in decimal the beginning cylinder (CCC) and head (HH) to be displayed, or the
file identifier (up to 44 characters) as used on the II LBL job control statement when
the file was created. If you enter less than 44 characters, the file ID is padded with
blanks on the right. Printing begins at the start of the file when a file is entered.
Note:
System utility permits embedded blanks in file names. However, you must not
place apostrophes or quotes around file names as delimiters, or they will be
taken by system utility as part of the file names.
nn?CCCHH . END
SUNNNN
Enter the last cylinder (CCC) and head (HH) in decimal to be displayed.
nn?NO OF TRACKS TO PRINT UP TO 9
(
SUNNNN
If you entered the file ID, now enter the number of tracks to be printed. Note that
printing begins with the low cylinder and head numbers of the first extent. If the file
is not laced, printing continues for the requested number of tracks or until end of file
(EOF) is encountered, whichever comes first. If the file is laced, printing continues for
the requested number of tracks. Printing is not confined to the end extent specified in
the format label. For DD, a format label diskette is considered to have 74 cylinders,
with 2 heads (0 and 1) in each cylinder. (Laced files are discussed in the System
Service Programs (SSP) Operating Guide (UP-8841) in the section describing diskette
prep.)
Examplel
The data on cylinder 3, head 4 through cylinder 6, head 6 on device 300 is to be
printed.
For the message:
nn?ENTER DVC ADDRESS
7004 5208-000
SUNNNN
7-25
System Utility Services
Key in:
nn6300
For the message:
nn?CCCHH - BEGIN OR FILE-ID
SUNNNN
Key in:
nn600304
For the message:
nn?CCCHH END
SUNNNN
Key in:
nn600606
(
Example 2
The first three tracks from a file called SEQUENTIAL DISC on device 440 are to be
printed.
For the message:
nn?ENTER DVC ADDRESS
SUNNNN
Key in:
nnM40
For the message:
nn?CCCHH - BEGIN OR FILE-ID
SUNNNN
Key in:
nn6SEQUENTIAL DISC
(
For the message:
nn?NO OF TRACKS TO PRINT UP TO 9
SUNNNN
Key in:
nn63
7-26
7004 5208-000
System Utility Services
7.4.4. Printing a Disk or Format Label Diskette in Deblocked Format (DDR)
You use the DDR function code to print your disk pack or format label diskette in both
character and hexadecimal formats. This function is similar to the DD function,
except that the printing is reformatted according to the logical record length that is
entered.
Procedure
For the message:
nn?ENTER DVC ADDRESS
SUNNNN
Enter the disk/diskette unit device address.
For the message:
(
nn?CCCHH-BEGIN OR FILE-ID
SUNNNN
Enter in decimal the first cylinder (CCC) and head (HH) to be printed or the file
identifier (up to 44 characters) as on the II LBL job control statement when the file
was created. If you enter less than 44 characters, the file-id is padded with blanks on
the right. Printing begins at the start of the file when a file-id is entered.
If cylinder and head are entered, SU displays these messages:
nn?CCCHH-END
SUNNNN
Enter in decimal the last cylinder (CCC) and head (HH) to be displayed.
nn?ENTER LOGICAL RECORD LENGTH
SUNNNN
Enter in decimal the logical record size to determine the print format.
nn?ENTER BLOCKSIZE
(
SUNNNN
Enter in decimal the logical block size. However, if the block size is not an exact
multiple of the record size, the following message will be displayed:
BLOCKSIZE NOT MULTIPLE OF RECORD SIZE
Reenter the record sizelblock size sequence.
If a file-id is entered, SU displays these messages:
nn?NUMBER OF TRACKS TO BE PRINTED UP TO 9
SUNNNN
Enter the number of tracks to be printed. Note that printing begins with the low
cylinder and head numbers of the first extent and continues for the requested number
oftracks, or until end offile (EOF) is encountered, whichever comes first. Printing is
not confined to the extents specified in the format label.
nn?ENTER LOGICAL RECORD LENGTH
SUNNNN
Enter in decimal the logical record size to determine the print format. The block size
will be taken from the VaLl label.
7004 5208-000
7-27
System Utility Services
(
7.4.5. Printing the Disk or Format Label Diskette Volume Table of
Contents (VTP)
You use the VTP function code to get a copy of your VTOC. You can print:
•
A full VTOC listing, giving you all the device information plus extents and other
information for all your allocated files
•
Device information only, giving you the available space left on your volume and
other information regarding your volume
•
File information only, giving you the extent and other information regarding the
file
VTP edits and prints the volume table of contents (VTOC) information for the
requested volume. It will not process other than OS/3-created VTOCs. Use the DD
function to print a VTOC from a disk or diskette not created by OS/3.
(
Procedure
Three list options are available, as follows:
•
VSN, DI - Device Information Only
Lists the available free extents and other information on the requested volume.
•
VSN, FILE-ID - File Information
Lists device information plus the extent and other information on the requested
file.
•
VSN, ALL - Full VTOC Listing
Lists device information plus the extent and other information for all files
allocated on the requested file.
For the message:
nn?ENTER DVC/VSN, 01, ALL, FILE-ID, END OR EOJ
SUNNNN
Key in one of the following, where vsn is the volume serial number of the disk pack or
format label diskette whose VTOC is to be printed.
For full VTOC listing:
nnllvsn,ALL
For a listing of only the device information:
nnllvsn,DI
7-28
7004 5208-000
(
System Utility Services
For a listing of up to 44 characters as used on the II LBL card when the file was
created:
nn~vsn,FILE-ID
To terminate the VTP function:
nnAEND
To terminate SU:
nn~EOJ
Notes:
1.
The device address of the disk pack or format label diskette may replace the vsn in
the preceding messages.
2.
When a VTP function terminates, SU produces the following message:
(
nn?ENTER DVC/VSN, DI, ALL, FILE-ID, END OR EOJ
SUNNNN
You may specify another volume for VTP display, END to end VTP functions, or
EOJ to terminate the SUD
3.
System utility permits embedded blanks in file names. However, you must not
place apostrophes or quotes around file names as delimiters, or they will be taken
by system utility as part of the file names.
Disk and Format label Diskette VTP listing Summary
The information listed by VTP is either taken directly from the disk or diskette labels
or calculated from data contained in the labels. A summary of the VTOC information
listed by the VTP function is provided in Table 7-5. (Refer to the Consolidated Data
Management Macroinstructions Programming Guide, 7004 4607, for details.)
(
7004 5208-000
7-29
System Utility Services
Table 7·5. Summary of Disk/Diskette VTP Information
Field Heading
Field Label
VOLUME INFORMATION
VOLUME SERIAL NUMBER
VTOC ADDRESS (CCC HHRR)
VOLUME SECURITY
OWNER NAME/ADDR CODE
DL$VSN
DL$VTC
DL$VSB
DL$ONR
DEVICE INFORMATION
ADDRESS LAST FORMAT 1
ADDRESS HIGHEST ALT TRACK
NO CYL/TRK THIS DISK
TOLERANCE
NO UNUSED VTOC RECORDS
NO OF ALT TRACKS
NO BYTES PER TRACK
NO VTOC LABELS PER TRACK
DL$LF4
DL$HA4
DL$DS4
DL$T04
DL$AF4
DL$AT4
DL$TL4
DL$LT4
(
AVAILABLE EXTENT DATA
START ADDRESS
END ADDRESS
EXTENT SIZE
DL$XT5
DL$XC5 (calculated)
(calculated)
FILE INFORMATION
FILE NAME
FILE SERIAL NUMBER
VOLUME SEQ NO
CREATION DATE
EXPIRATION DATE
EXTENT COUNT
OPTION CODES
PCA COUNT
TRACKS/CYLINDERS
LOW HEAD
FILE TYPE
LAST ACCESS DATE
LAST ACCESS TIME
LAST UPDATE DATE
LAST UPDATE TIME
UPDATE JOBNAME
UPDATE ACCESS CODE
PRIOR UPDATE DATE
PRIOR UPDATE TIME
PRIOR UPDATE JOBNAME
PRIOR UPDATE ACCESS CODE
DL$ID1
DL$FS1
DL$VS1
DL$CD1
DL$ED1
DL$XC1
DL$OC1
DL$PC1
DL$TPC2
DL$FLH2
DL$FT1
DL$ACDTE
DL$ACTME (milliseconds)
DL$UPDTE
DL$UPTME (milliseconds)
DL$UPID
DL$UPACC
DL$PUPD
DL$PUPT (milliseconds)
DL$PUPID
DL$PUPAC
(
continued
7-30
7004 5208-000
System Utility Services
Table 7-5. Summary of Disk/Diskette VTP Information (cont.)
Field Heading
Field Label
FILE PARTITION (PCA) INFORMATION
PCA NUMBER
BLOCK SIZE
RECORD SIZE*
RECORD FORMAT*
BLOCK FACTOR*
BLOCKS PER TRACK
NO. OF RECS IN LAST BLOCK
KEY LENGTH OR LACE FACTOR
END OF DATA BLOCK NO.
TOTAL # RECORDS
(
(1 through 7)
DL$BL1
DL$RL1
DL$RF1
(calculated: records per block for fixed· length blocked
record format.)
DL$SLA2
DL$SPC2
DL$SLF2
DL$SEP2
(calculated: totaL number of records for sequential
FIXBLK and FIXUNB fiLes, and for VARUNB fiLes.)
LOGICAL EXTENT INFORMATION
PCA NO
START CCC' HH
END ADDR CCC HH
(0 through 7)
DL$SXAR2 (calcuLated from reLative track address)
DL$SXAR2 (caLcuLated from number of tracks in extent)
ALLOCATION SUMMARY
EXT SIZE CCC HH
CUM/PCA CCC HH
CUM/FIL CCC HH
DL$SXAR2 (calculated: END ADDR minus START)
(caLculated: cumulative CCC HH for this PCA)
(calcuLated: cumulative CCC HH for this fiLe)
EXTENT UTILIZATION SUMMARY
OCCUPIED;PCA CCC HH BLOCK
AVAILABLE/PCA CCC HH BLOCK
RECORD CAPAC REMAINING
END OF DATA CCC HH RRR
(caLcuLated: aLlocated space used for this PCA)
(caLculated: unused space for this PCA)
(caLculated: approximate number of LogicaL records that
fit in availabLe space; not caLcuLated for variable·
length blocked record format)
DL$SEP2 (calcuLated)
PHYSICAL EXTENT INFORMATION
(
EXTENT TYPE
EXTENT SEQ NO.
EXTENT START CCC HH
EXTENT END CCC HH
CUM CCC HH
AUTO EXTENT INCREMENT
DL$XT1
DL$SX1
DL$XL1
DL$XU1
(caLcuLated)
DL$SA1
SAT FILE INFORMATION
DIRECTORY PCA
DIRECTORY PCA
TEXT PCA LACE
TEXT PCA LACE
LACE FACTOR
LACE ADJUST
FACTOR
ADJ
DL$DIRL2
DL$DIRF2
DL$TXTL2
DL$TXTF2
*Not applicable to MIRAM files on peA basis.
continued
7004 5208-000
7·31
System Utility Services
Table 1·5. Summary of Disk/Diskette VTP Information (cont.)
Field Label
Field Heading
(M)IRAM FILE INFORMATION
KEY LOCATION
KEY LENGTH
DUPLICATES ALLOWED
CHANGES ALLOWED
DATA RECORD COUNT
RECORD SIZE
INDEX BUFF SIZE
CL$XILOC
CL$XILOC+2
CL$XILOC+3,X'80'
CL$XILOC+3,X'40'
CL$COUTR
CL$DREC
CL$CSIZ
7.4.6. Printing a Short Format VTOC for a Disk or Format Label Diskette
(SVT)
(
You use the SVT function to obtain an abbreviated VTOC listing, consisting of a
single print line for each physical extent for each file.
Procedure
For the message:
nn?ENTER DVC OR VSN OR END
SUNNNN
Enter the volume serial number (up to six characters) of the disk unit or diskette
device address of the disk pack or diskette whose VTOC is to be printed; either entry
prints the abbreviated VTOC. Enter END to terminate the SVT function.
If SVT is attempted on a data set label diskette, the following message is displayed.
SVT VALID ON FORMAT LABEL VOLUMES ONLY
(
SVT Listing Summary for Disk and Format label Diskette
The various information listed by SVT is either taken directly from the disk or
diskette labels or calculated from data contained in the labels. A summary of the
short format VTOC information listed by the SVT function is provided in Table 7-6.
(Refer to the Consolidated Data Management Macroinstructions Programming Guide,
70044607, for details.)
7-32
7004 5208-000
System Utility Services
Table 7·6. Summary of SVT Information for Disk and Format Label Diskette
(
Field Heading
Field Label
VSN
SECUR
OWNER
FILE-NAME
FILE TYPE
FILE SER_ NO
SEQ NO
CREATION DATE
EXPIRATN DATE
OPT COD
PCA CT
START CCC HH
END CCC HH
CUM CCC HH
AIN
DL$VSN
DL$VSB
DL$ONR
DL$ID1
DL$FT1
DL$FS1
DL$VS1
DL$CD1
DL$ED1
DL$OC1
DL$PC1
DL$XL1
DL$XU1
(calculated: cumulative)
DL$SA1
7.4.7. Displaying the Available Disk and Format Label Diskette Extents
(AVX)
You use the AVX function to display a list of available disk or diskette extents on the
console workstation or console screen. The display is similar to the listing printed by
the VTP function with the DI option; however, output is displayed at the console
workstation console and printed at the console output printer rather than at the
customary line printer.
Procedure
For the message:
nn?ENTER DEVICE ADDRESS
(
SUNNNN
Enter the did of the disk or diskette drive containing the disk or diskette whose
available extents are to be displayed.
If AVX is attempted on a data set label diskette, the following message is displayed:
AVX VALID ON FORMAT LABEL VOLUMES ONLY
7004 5208-000
7-33
System Utility Services
AVX listing Summary
The various information listed by AVX is either taken directly from the disk or
diskette labels or calculated from data contained in the labels. A summary of the
available disk or diskette extent information listed by the AVX function is provided in
Table 7-7. (Refer to the Consolidated Data Management Programming Guide,
70044607, for details.)
Table 7·7. Summary of AVX Information for Disk and Format label Diskette
Field Heading
Field Label
VSN
SEeUR
VToe ADRS
OWNR
START eee HH
END eee HH
SIZE CCC HH
DL$VSN
DL$VSB
DL$VTe
DL$ONR
DL$XTS
DL$XeS (calculated)
(calculated)
(
7.S. Data Set Label Diskette Functions
The data set label diskette functions that can be performed are described in the
following subsections.
7.5.1. Data Set Label Diskette Operating Instructions
Proceed as follows to request a data set label diskette function:
1.
Place the subject data set label diskette volume on an available diskette unit.
2.
As described in 7.1:
(
a.
Enter the SU symbiont command.
b.
Enter the DD or DDR function code either as a command parameter or as a
solicited message response to the ENTER REQUIRED FUNCTION
message.
c.
Enter the spooling option; otherwise, default is Y (applicable if spooling is
configured).
(
7-34
70045208-000
System Utility Services
7.5.2. Printing the Data Set label Diskette in Unblocked Format
You use the DD function to print a single-sided or double-sided data set label diskette
in unblocked format.
Single-Sided Diskette in Unblocked Format (DO)
The DD function code prints your data set label diskette in character and hexadecimal
format. The DD function does not deblock your logical records.
Procedure
For the messages:
nn?ENTER DVC ADDRESS
SUNNNN
Enter the diskette unit device address of the data set label diskette to be displayed.
nn?TTRR-BEGIN
SUNNNN
Enter in decimal the beginning track (Tr) and sector (RR) to be displayed.
nn?TTRR-END
SUNNNN
Enter the last track (Tr) and sector (RR) in decimal to be displayed.
Double-Sided Diskette in Unblocked Format (DO)
The DD function code prints your data set label diskette in character and hexadecimal
format. The DD function does not deblock your logical records. Your diskette is
considered to have 74 cylinders with 2 heads (0 and 1) in each cylinder.
Procedure
(
For the messages:
nn?ENTER DVC ADDRESS
SUNNNN
Enter the diskette unit device address of the data set label diskette to be displayed.
nn?CCCHH . BEGIN
SUNNNN
Enter in decimal the beginning cylinder (CCC) and head (HH) to be displayed.
nn?CCCHH - END
SUNNNN
Enter the last cylinder (CCC) and head (HH) in decimal to be displayed.
7004 5208-000
7-35
System Utility Services
Example
The data on cylinder 3, head 4 through cylinder 6, head 6 on device 300 is to be
printed.
For the message:
nn?ENTER DVC ADDRESS
SUNNNN
Key in:
nnA300
For the message:
nn?CCCHH . BEGIN
SUNNNN
Key in:
(
nnA00300
For the message:
nn?CCCHH END
SUNNNN
Key in:
nnA00601
(
7.5.3. Printing the Data Set label Diskette in Deblocked Format
You use the DDR function to print a single-sided or double-sided data set label
diskette in deblocked format.
Single-Sided Diskette in Deblocked Format (DDR)
The DDR function code prints your data set label diskette in character and
hexadecimal format. The DDR function deblocks your logical records.
Procedure
For the messages:
nn?ENTER DVC ADDRESS
SUNNNN
Enter the diskette unit device address of the data set label to be displayed.
nn?TTRR-BEGIN
SUNNNN
Enter in decimal the first record (RR) and track (TT) to be printed.
7-36
7004 5208-000
(
System Utility Services
nn?ENTER LOGICAL RECORD LENGTH
SUNNNN
Enter in decimal the logical record size to determine the print format.
Double-Sided Diskette in Deblocked Format (DDR)
The DDR function code prints your data set label diskette in character and
hexadecimal format. The DDR function deblocks your logical records. Your diskette is
considered to have 74 cylinders with 2 heads (0 and 1) in each cylinder.
Procedure
For the messages:
nn?ENTER DVC ADDRESS
SUNNNN
Enter the diskette unit device address of the data set label diskette to be displayed.
nn?CCCHH-SEGIN
SUNNNN
Enter in decimal the first cylinder (CCC) and head (HH) to be printed. Double-sided
diskettes have 72 cylinders and 2 heads, 00 and 01.
nn?CCCHH-END
SUNNNN
Enter in decimal the last cylinder (CCC) and head (HH) to be printed.
nn?ENTER LOGICAL RECORD LENGTH
SUNNNN
Enter in decimal the logical record size to determine the print format.
7.5.4. Printing the Data Set Label Diskette Volume Table of Contents
(VTOC)
(
You use the DD function to print the diskette volume table of contents (that is, the
data set labels).
Single-Sided Diskette VTOC (DO)
The DD function code prints your single-sided data set label diskette VTOC.
Procedure
For the message:
nn?ENTER DVC ADDRESS
SUNNNN
Enter the diskette unit device address of the data set label diskette whose VTOC is to
be printed.
7004 5208-000
7-37
System Utility Services
For the message:
nn?TTRR-SEGIN
SUNNNN
Key in:
nn~0008
For the message:
nn?TTRR-END
SUNNNN
Key in:
nn~0026
Double-Sided Diskette VTOC (DO)
(
The DD function code prints your double-sided data set label diskette VTOC.
Procedure
For the message:
nn?ENTER DVC ADDRESS
SUNNNN
Enter the diskette unit device address ofthe data set label diskette whose VTOC is to
be printed.
For the message:
nn?CCCHH-BEGIN
SUNNNN
Key in:
nn~00000
(
For the message:
nn?CCCHH-END
SUNNNN
Key in:
nn~00001
7·38
7004 5208-000
Section 8
Disk Cache Facility (DCF)
The OS/3 disk cache facility (DCF) increases system performance by reducing the
number of physical lIOs to disk devices. lIOs are slow relative to processor speed. The
number of physical lIOs is reduced by buffering disk data in main storage (the cache
buffer) so that the data is retrieved from memory rather than disk.
When a read is done of a particular area on a disk, the disk cache facility (DCF) reads
into a reserved cache storage area all or a portion of the track being read (depending
on the segment size when DCF was initialized). Consequently, in subsequent reads of
that same disk area, a physical lIO is unnecessary, since that data is already present
in storage.
The advantage ofDCF is that a reduction in the number of physical lIOs required
results in:
(
•
Reduced queuing delays (as lIO requests must wait to be issued in turn)
•
Reduced disk seek time (as the disk accessor moves to the proper cylinder)
•
Reduced latency (as the disk rotates so that the disk read/write heads reach the
proper record)
•
Reduced data transfer time (from disk to storage)
•
Reduced process time overall
Main storage disk cache is supported via software. The software is included in the
system microcode file ($Y$MIC) and is called via the system definition file ($Y$SDF)
to maintain consistency between all System 80 models. Refer to the Installation
Guide, 7004 5505, for information on the system microcode and system definition
files.
You can selectively activate or remove individual disk drives to DCF (8.3 and 8.4) or
turn it off completely (8.5). Also, you can bypass the caching of specific files using the
CACHE parameter of the DD job control statement and the CACHE IOGEN
parameter. (See the Consolidated Data Management Programming Guide, UP-9978,
and the Installation Guide, 7004 5505.) Information to help you optimize DCF
performance is given in section 8.7.
7004 5208-000
8-1
Disk Cache Facility (DCF)
To use DCF, your system must be configured with the disk cache feature. Following
are descriptions ofDCF features. Refer to the System Messages Reference Manual,
70045190, for an explanation of messages and error codes.
8.1. Initializing Disk Cache (CM)
DCF is normally initialized during IPL. However, if it was not initialized during IPL
or was shut down, you can initialize it manually by entering the CACHE MEMORY
command at the system console. When DCF is initialized, all devices are activated or
removed from DCF according to their CACHE IOGEN parameter specifications.
Refer to the Installation Guide, 7004 5505, for details on this parameter.
Format
CM
(
8.1.1. Specifying Cache Buffer Size (CM SIZ)
When cache is initialized at IPL time, the size of the cache buffer is determined by
one of the following methods:
•
If the last four digits of the cache manager microcode name in $Y$SDF file are
not zero, they specifY the cache size. For example, CA130256 indicates a cache
size of 256KB.
•
Ifthe last four digits of the cache manager microcode name in $Y$SDF file are
zero (CA130000), a CMOl message prompt asks for a buffer size.
The CM SIZ command lets you override the cache buffer size when you initialize DCF.
Format
CM SIZ=n
(
where:
n
Specifies the number ofl,024-byte blocks allocated to the cache buffer.
Valid specifications are 160 to 8,192. Note that larger cache buffers
generally result in increased performance.
See 8.7 for more information on cache buffer and segment size.
8-2
7004 5208-000
Disk Cache Facility (DCF)
8.1.2. Specifying Cache Buffer Segment Size (CM SEG)
The cache buffer is divided into fixed size segments. The amount of data that DCF
reads from a disk is equal to the cache buffer segment size. You can specify the cache
buffer segment size by entering the CM SEG command.
Format
CM SEG=n
where:
n
Specifies the segment size in 1,024-byte blocks. Valid specifications are 2 to
24. This command overrides the cache segment size previously defined
through the CACHESEGSIZE SUPGEN parameter, as described in the
Installation Guide, 7004 5505.
(
If you don't specify the CM SEG command, the size specified in the CACHESEGSIZE
SUPGEN parameter is used. If you don't specify either parameter, the default values
used are as follows:
Default Cache Buffer Segment Size
Cache Buffer Size
(in 1,024·byte blocks)
160 - 255K
256 - 511K
512 - 8,192K
3
6
12
Note that using a smaller segment size causes a greater number of segments in your
cache buffer. Generally, sequential processing performs better with large segments,
and random processing performs better with a larger number of small segments. You
can experiment to find the combination that is best suited to your environment. Use
the statistics that DCF provides (see 8.6) to help tune these specifications.
(
The SIZ and SEG options can be separated by a comma and specified together on the
CMcommand.
Format
CM SEG=15, SIZ=1000
70045208-000
8-3
Disk Cache Facility (DCF)
8.2. Resegmenting the Existing Cache Buffer (CM RESEG)
With the unsolicited CM RESEG command, you can resegment the cache buffer that
you allocated during DCF initialization with a different segment size. You can use
this command without shutting down or reinitializing DCF. However, if you want to
change the buffer size, then you must reinitialize DCF. The RESEG command resets
the cache statistics to zero.
Format
00 CM RESEG=n
where:
n
Specifies segment size in 1,024-byte blocks. Valid specifications are 2 to 24.
Note:
Resegmenting the cache buffer resets all cache statistics but does not affect
the activated or removed status of the disks on the system.
(
8.3. Selective Caching
Normally, all drives and files are cached. The performance of cache memory may be
optimized by using cache memory only with the most frequently accessed drives and
files. Use selective caching to remove the less frequently used drives and files.
8.3.1. Removing Drives from DCF (eM REM)
You can remove a disk drive from DCF via the CACHE IOGEN parameter (also see
the Installation Guide, 70045505, or via the unsolicited CM REMOVE command.
Note that when a disk drive is shared by two processors, the drive must be removed
from DCF in any processor that writes to it.
Format
00 CM
(
~OVE
dve#[,dve, ••• ,dve#]
where:
dve#
Specifies the device address (drive number) of the drive to be removed from
the DCF. You can specify more than one address.
84
7004 5208-000
Disk Cache Facility (DCF)
8.3.2. Removing Files from DCF
You can bypass the caching of specific files using the CACHE parameter of the DD
job control statement and the CACHE IOGEN parameter. For more information, see
the Consolidated Data Management Programming Guide, UP-9978, and the
Installation Guide, 70045505.
8.4. Activating Drives to DCF (CM ACT)
You can activate a drive to DCF via the CACHE IOGEN parameter (see the
Installation Guide, 7004 5505) or via the unsolicited CM ACTIVATE command.
Format
00 eM
(
~IVATE
dvc#[,dvc#, ••• ,dvc#l
where:
dvc#
Specifies the device address (drive number) of the drive to be activated to
DCF. You can specify more than one address.
8.5. Removing DCF from the System (CM SHUT)
Remove DCF from the system at any time using the unsolicited CM SHUTDOWN
command:
Format
00 eM .§.!:illlDOWN
8.S. Displaying DCF Statistics (CM STA, STARES)
You can monitor DCF operations by displaying DCF statistics. You can display DCF
statistics on demand or at periodic, timed intervals. You can also display DCF
statistics for a specific drive.
To display DCF statistics immediately, use the unsolicited cache commands CM STA
and CM STARES.
Formats
00 eM STA
Displays statistics on the system console.
00 eM STARES
Displays statistics on the system console and resets all of the counters
including disk device statistics maintained by DCF. It can be used to monitor
DCF operations during a specific period of time.
7004 5208-000
8-5
Disk Cache Facility (DCF)
8.S.1. Displaying and Turning Off Timer Statistics (CM STATIME,
STARESTIME, TIMER)
Formats
00 eM STATIME=n
Displays statistics on the system console repeatedly.
where:
n
Specifies the time interval between displays. Valid values are 1 to 999
minutes.
00 eM STARESTIME=n
Repeatedly displays statistics and resets all counters maintained by DCF.
This command can be used to monitor DCF operations for a specified time
interval.
where:
n
Specifies the time interval between displays. Valid values are 1 to 999
minutes.
00 eM TIMER=OFF
Turns off the timer you set using the STATIME or STARESTIME command.
8.S.2. Displaying Statistics on a Specified Drive (CM STADISK,
STARESDISK)
Formats
00 eM STADISK=did
Displays statistics for the specified disk on the system console.
where:
did
Specifies the device address of the disk.
00 eM STARESDISK=did
Displays statistics and resets the counters for the specified disk.
where:
did
Is the device address of the disk.
Note:
8-6
If you generate an attention interrupt, A VR a disk, or mount another disk, the
counters for that disk's device statistics are reset.
7004 5208-000
Disk Cache Facility (DCF)
8.S.3. Interpreting DCF Statistics
Figure 8-1 shows samples of the statistics displayed at the system console.
00 CM STA
CM16 READ HIT RATE
CM17 SEARCH READ HIT RATE
CM18 UNREFERENCED I/O RATE
CM19 CACHE BUFFER SIZE
CM20 SEGMENT SIZE (x 1024)
CM21 TOTAL NUMBER DISK I/O
CM22 NUMBER READ HITS
CM23 NUMBER WRITES
CM24 NUMBER SEARCH EQUALS
CM25 NUMBER SEARCH HIIEQ
CM26 NUMBER READ ERRORS
CM27 NUMBER READS NOT CACHED
CM28 NUMBER SEARCH HITS
CM29 NUMBER WRITE THROUGHS
CM30 NUMBER UNREFERENCED I/OS
CM31 NUMBER (CACHE=NO) lIDS
CM32 READS OVER HALF SEGMENT
CM33 NUMBER READS
(
73.0%
99.5%
0.3%
1024k
12
46170
30320
1846
248
1121
1
8945
1116
1407
140
20
50
41508
CM0005
CM0005
CM0005
CM0005
CM0005
CM0005
CM0005
CM0005
CM0005
CM0005
CM0005
CM0005
CM0005
CM0005
CM0005
CM0005
CM0005
CM0005
Figure 8-1. DCF Statistics Displayed at the System Console
•
Hit rates
A hit occurs when a read or search/read operation does not have to access the disk
because the data is in the cache buffer. Hit rates are the most significant
indication of cache performance. The search hit rate is the number of search hits
divided by the number of search HIlEQs. (Search equal commands are not
cached.)
•
Read errors
Read errors are I/O errors encountered by DCF. When a read error occurs, the I/O
is reissued directly into the program's I/O buffer, rather than into the cache
buffer. The reissued I/O may be successful.
(
•
Write-throughs
A write-through occurs when the data being written resides in the cache buffer.
The buffer is updated and the data is written to the disk.
•
Unreferenced I/Os
Unreferenced I/Os are a count of the number of segments that were reused
without ever having been referenced by read or search/read commands. Segments
are reused when space is required for an I/O. The first segments reused are those
that were never referenced through a read, search/read, or write (LRU).
70045208-000
8-7
Disk Cache Facility (DCF)
•
Unreferenced I/O rate
The unreferenced I/O rate is the number of unreferenced I/Os divided by the
number of reads.
•
Reads over half segment
This count is the number of reads that are greater than half the segment size
and, therefore, are not cached. This count is not included in the hit rate
calculations.
•
Reads not cached
DCF automatically bypasses read or search/read commands that are multitrack
or without data transfer. This count is included in the hit rate calculations.
(
•
(CACHE=NO) I/Os
This count records the number of read or search/reads that bypass DCF because
of the selective noncaching by file option (see 8.3.2). This count is not included in
the hit rate calculations.
Note:
If a read is larger than half of the segment size, it is counted as a read over
half segment even when CACHE=NO has been specified.
8.7. DCF Supportive Information
The following information provides you with background and illustrative information
to help you use the disk cache facility optimally.
8.7.1. Cache Modules
There are two modules that support disk cache, the cache symbiont (SL@@CM) and
the cache manager (CAxxOOOO). The cache symbiont is responsible for loading the
cache manager, initializing the cache buffer, and processing unsolicited cache
commands. Once the manager is loaded and initialized, the symbiont becomes inactive
until an unsolicited cache command is entered. The manager is responsible for
managing the cache buffer and handling I/O requests to the disk.
8.7.2. Main Storage Layout with Disk Cache
When disk cache is initialized at IPL, the cache buffer is established at the high end
of main storage. The cache buffer contains the cache manager, a search/read buffer,
and cache segments. The search/read buffer is used by search/read high or equal
commands, which will be explained later.
Note:
8-8
8470, 8494, and M9720 disks have equivalent logical track sizes.
7004 5208-000
(
Disk Cache Facility (DCF)
The size of the search/read buffer is that of an 8470 or 8417 disk track depending on
whether or not an 8470 (or equivalent) disk is configured. The manager is located in
the beginning of the cache buffer and is followed by the search/read buffer. If the
cache buffer size is greater than 511K, DCF automatically allocates two search/read
buffers. Also, if the segment size configured is greater than or equal to the largest
track size for a disk on the system, DCF does not build separate search/read buffers.
DCF uses any available cache segments for search/read operations.
The rest of the cache buffer is divided into fixed size segments. These segments are
used by disk cache to read blocks of data. Each segment is associated with a disk track
and device address. It may take several segments to contain a track of data,
depending on the segment size. If the segment size is larger than a track, then part of
the segment will be unused.
(
Segments are not reserved for specific disks on the system, but are available for use
by any disk, based on a least recently used (LRU) algorithm. Section 8.7.6 explains
how the segment size is determined.
Use the following formula to calculate the number of segments in the cache buffer.
#Segments = (cache buffer size * 1024) - (cache manager + search/read buffer(s»
(segment size * 256)
The following example applies this formula. The cache manager is approximately 8K
If:
cache buffer size
segment size
search buffer
=
=
=
700K
48 sectors
24576 bytes (8470)
Then:
#Segments
(
=«700 * 1024) - (8000 + (2 * 24576))) / (48 * 256)
=(716800 - 57152) / 12288
=659648/12288
=53
In this example there are 53 segments in the cache buffer. Each segment can hold 48
sectors (12K bytes) of disk data.
When disk cache is initialized manually (via the CM command) the cache buffer
cannot be placed in high main storage because that area is reserved for the job region.
The cache buffer is obtained from an available buffer in middle main storage.
7004 5208-000
8-9
Disk Cache Facility (DCF)
8.7.3. Cached I/O Commands
The cached va commands are read, write, and search/read high/equal commands.
Search/read high/equal commands are primarily issued by data management, while
searching through the index of a MIRAM file, as a fast method to locate the index
record(s) that point(s) to the user data record. The search is based on a key argument
that is supplied by the initiator of the search.
Search/read equal commands are not cached due to the infrequency of use. If data on
the disk is accessed infrequently and is read into the cache, it displaces other data and
increases disk cache overhead. Search/read equal commands are used mainly in VTaC
searches by disk space management and in $Y$SHR searches by data management
during open and close processing.
8.7.4. I/Os Not Cached
Disk cache does not cache all read and search/read high/equal commands. It is
important to know which VOs are not cached because they may cause the cache
statistics to reflect lower hit rates.
The following vas are not cached:
•
Search/read or read multitrack,
•
Read with no data transfer
•
Read larger than half ofthe segment size
('
A MIRAM file with IRAM characteristics or an IRAM file has an index that is more
than one track. Data management issues multitrack searches and reads to this index.
A read with no data transfer is commonly used by data management when issuing a
write command with a read verification option.
A read larger than half of the segment size is not cached, so that a program issuing
large reads bypasses the caching of data, reduces disk cache overhead, and avoids the
displacement of other disk data. If the disk data is accessed infrequently, then a large
VO buffer or the use of the selective caching options (see 8.3) is recommended. If the
data is accessed frequently, it is recommended that the va buffer be less than or
equal to the cache segment size, so that the data is cached.
8-10
7004 5208-000
(
Disk Cache Facility (DCF)
8.7.5. Monitoring DCF Effectiveness
Generally, the larger the cache buffer, the greater the performance. However, there is
an exception. When the production mix is random, there is a significantly large
amount of cache overhead with a very low hit rate. In this situation, it is better to run
without DCF.
The most effective way to determine the optimal cache buffer and segment sizes is to
use the cache statistics to monitor DCF operations, while experimenting with
different cache and segment sizes. See Section 8.6 for information on DCF statistics
commands.
8.8. Fine..Tuning DCF
(
8.8.1. Specifying Segment Size
Disk cache segment size is specified by the following methods:
•
System generation (SYSGEN)
•
Unsolicited cache command (CM RESEG)
•
Manual cache loading (CM SIZ and CM SEG)
•
Default value
For information on specifYing segment size at system generation, see the Installation
Guide, 7004 5505. See 8.1 for information on the CM#RESEG, SIZ, and SEG
commands and default values.
(
The default segment sizes may not be optimal for every user. You may not have
enough main storage to run with a large cache buffer to get large segments.
SpecifYing segment size allows you to run with large segments even with a small
cache buffer and, conversely, small segments with a large cache buffer.
7004 5208-000
8-11
Disk Cache Facility (DCF)
If a segment size is not specified, the default values specified in the following table
are used:
Cache
Buffer Size
Number of 25S·Byte Sectors
160 - 255K
12 (3K)
256 - 511K
24 (6K)
512 -1,024K
48 (12K)
Note that 8417 and 8419 disks have 60 and 50 sectors per track respectively. The
maximum default segment size is 48 sectors. Thus, with a 48-sector segment, an 8419
track would use one segment of 48 sectors and a second segment with 2 sectors (46
sectors of the second segment are unused). An 8417 track would use two segments of
48 and 12 sectors (36 sectors of the second segment are unused).
(
It is recommended that system with predominantly 8419 and/or 8417 disks run with a
segment size that minimizes unused segment space (Le., full track segment size).
The following lists the System 80 disks and the corresponding number of segments
per track:
8430/8433
33 sectors (256-byte sectors)
8416/8418
40 sectors
8419
50 sectors
8417
60 sectors
8470/84941M9720
96 sectors
(
Note:
8-12
8430/33 disks are variable-sectored disks. When you choose a segment size,
consider the fact that smaller sector sizes increase track overhead.
70045208-000
Disk Cache Facility (DCP)
8.8.2. Optimizing Disk Cache Performance
Generally, sequential processing performs better with a small number oflarger
segments, and random processing performs better with a larger number of small
segments. By experimenting with different sizes, you can find the combination best
suited to your production environment. Figure 8-1 shows the effect of segment size on
run time.
You may need to remove a disk from disk cache for performance reasons. If data
accessed infrequently is read into the cache buffer, then other disk data is displaced,
a lower hit rate is obtained, and disk cache overhead is increased. For information on
the remove and activate commands, see 8.3.1 and 8.4, respectively.
15
SEQUENTIAL MIX
1l: 15.19
-
DEFAULT SIZE
- - - 24 SECTOR SEGMENT
en
LU
9.52
10
·~.8.38
>::>
:z
~
~
LU
~
I-
9
~
3.43·=..,------------. 3.46
~
c::
~
-·3.19
8
a
100
200
300 400
SOD
600
700
BOO 900 1000
CACHE BUFFER SIZE IKJ
6
(
1
RANDOM MIX
6 17
.
DEFAULT SIZE
- - - 24 SECTOR SEGMENT
en
LU
>::>
::z
~
4.45
• __
LU
~
I-
5
~
~40
~4.36
~.20
§J
-.
§J
• .. - __ ... ________
@]
c::
5.~~
- -_ _ _ _ _
~.~6
4
o
100
200
300 400 500
600 700
800 900 1000
CACHE BUFFER SIZE IKJ
A19130
Figure 8·2. Effect of Segment Size on Run Time
7004 5208-000
8-13
(
(
Section 9
ONUERL Program
ONUERL is a utility program that edits the contents Of the system error log file
($Y$ELOG) and prints a formatted report containing both detailed and summary
information. ONUERL also maintains a summary of the error data in the system
summary file ($Y$ESUM), which is available for transmission to a Unisys support
center when it is written to the system journal.
(
You have several options when running ONUERL. You can:
•
Choose to hold the output in a spool file for later printing
•
Select where processing will start in the ELOG file
•
Suspend error logging
•
Spool error summary data to a diskette
•
Obtain a printout that documents what ONUERL does
•
Request graphic and tabular displays of accumulated error data (ONELAN
program, described later in this appendix)
Note:
(
It is recommended that you run ONUERL on a planned schedule to help
diagnose system problems. You must run the ONUERL program whenever the
message "Error log is nearly full" is displayed. The run time for ONUERL
varies according to the amount and type of data being processed.
9.1. Executing ONUERl
You have the option of executing the ONUERL program in two ways:
•
Manually. on an as-needed basis, with the ability to change the default (preset)
program options each time you run the program
•
Automatically, on a fixed, 7-day cycle, with the ability to change the preset
options only for the initial running of the program
7004 5208-000
9-1
ONUERL Program
9.1.1. Manual Program Execution
Enter the following command to run the ONUERL program.
RV ONUERL,["OPT=Y]
•
Omit the OPT=Ykeyword if you want to run the program by using the preset
program options currently in effect. (See 9.2.)
•
Include the OPT=Y keyword if you want to modify or view the program options
before running ONUERL.
ONUERL displays the following message after loading:
nn OS/3 ONUERL-ERROR LOG EDITOR VERSION xx/xx.
If you omitted the OPT=Ykeyword from your RV command, ONUERL:
•
Executes using the preset program options in effect (See 9.2.)
•
Prepares its output per the preset program options in effect
•
Displays the following message upon normal termination of the program:
JCnn JOB ONUERL TERMINATED NORMALLY
hh:mm:ss
If you included the OPT=Ykeyword in your RV command, ONUERL displays the
following message:
nn MODIFY PROGRAM OPTIONS (Y,N,?)
?
The message requests you to indicate whether you want to make changes to the
program options (y), run the program by using the preset option values as currently
defined (N), or display the preset option values for your review (?)
Respond to this message by entering the message identification number (nn) followed
by the appropriate character displayed in the message. The program reacts to your
response as follows:
? Response
The program displays the current preset value for each option. Then it redisplays
the modify program option message to let you run the program by using the
preset options shown or to let you redefine the options.
Example:
on!;!?
nn
9-2
PRESET OPTIONS :
OPEN=CURRENT, SUMMARY=THRESHOLD, ELOG=YES,
ELOG=YES, DUMP=NO, ESUMFIL=U, DMPSUM=NO
MODIFY PROGRAM OPTIONS (Y,N,?) ?
DOC=NO,
THRESHOLDS=NO,
7004 5208-000
(
ONUERL Program
N Response
ONUERL executes using the preset program options in effect (shown). The
output is prepared as directed by the preset program options and the
"Terminated Normally" message is displayed at the successful completion of
the program.
Y Response
The program displays a message instructing you to key in the numbers
corresponding to the options you want to change.
Example:
nn
nn!i!Y
nn -
(
MODIFY PROGRAM OPTIONS (Y,N,?)
?
ENTER OPTIONS, SEPARATED BY COMMAS (1,2,3,4,5,6,7,8,?)
Each number displayed in the message corresponds to a specific program
option. To display the correlation between numbers and options, enter the
message number followed by a question mark (?). After displaying the
numbers and options, the program automatically redisplays the "Enter
options" message to let you select the options you want to change.
Example:
1=OPEN, 2=SUMMARY, 3=ELOG, 4=DOC, 5=THRESHOLD,
6=DUMP, 7=ESUMFIL, 8=DMPSUM
nn - ENTER OPTIONS, SEPARATED BY COMMAS (1,2,3,4,5,6,7,8,?)
Select the options you want to change by entering their respective numbers
(1 through 8). The program displays (one at a time) each option you selected,
along with the choices for modifying that option.
Example:
on
(
nn -
!~~a~$'ij;!)'~~e
1: OPEN= (C,P,B,?)
Specify your choice by entering the appropriate character displayed.
Example:
nn -
rlnific
nn
1: OPEN= (C,P,B,?)
2: SUMMARY= (T,Y,R,N,D,?)
If you want the program to display a brief definition of each choice before
making your selection, key in the ? Otherwise, refer to Table A-1 for an indepth description of the options and their functions, and then enter your
selection.
7004 5208-000
9-3
ONUERl Program
Example:
nn
2: SUMMARY= (T,Y,R,N,D,?)
Mi!!~
.
nn?
nn
00
T=SPooL SUMMARY IF THRESHOLD eXCEEDeD
Y=SPOOL SUMMARY TO SYSTEM JOURNAL
R=REPEAT LAST SUMMARY SPOOLING
N=NO SUMMARY SPOOLING THIS RUN
D=INHIBIT SUMMARY SPOOLING PERMANENTLY
2: SUMMARY= (T,Y,R,N,D,?)
11
3: ELOG= (Y,N,?)
ONUERL executes after you complete your last option modification.
Figure 9-1 shows a step-by-step example of the messages and response
related to ONUERL execution.
(
9.1.2. Automatic Program Execution
Enter the following command to schedule the ONUERL program for automatic
execution cycle:
RV ONUERLAS,Ntime+x[,OPT=Y]
where:
ONUERLAS
The program JCS uses to initiate the automatic execution cycle. Subsequent
jobs are identified as ONUERLxx, where xx is the last two digits of the job
number.
N
Specifies a normal scheduling priority.
time
Specifies the time of day (military format) to run the program.
(
+X
Specifies a value (0-6) indicating the number of days between the day that
this RV command is entered and the day that the program is executed. For
example, you enter the RV command on a Monday but you want the program
to run every Friday. There is a 4-day delay between the day the command is
entered and the day the program is scheduled to execute. Therefore, the
value of x is specified as 4.
OPY=Y
Specifies that you want to view and/or change the program options under
which ONUERL executes. With the OPT=Y keyword omitted, ONUERL
runs using the preset default options currently in effect. (See Table 9-1.)
94
7004 5208-000
ONUERl Program
Be aware that when you execute ONUERL on an automatic schedule, the
option changes you make apply only to the initial execution of the program.
All subsequent executions ofthe program are run with the preset default.
If the OPT=Y keyword is omitted from the RV command you enter, ONUERL is
scheduled for execution using the preset program options in effect.
If the OPT=Ykeyword is included in your RV command, the program displays the
following message asking you to indicate whether you want to make changes to the
program options 00, run the program by using the preset option values as currently
defined (N), or display the preset option values for your review (?):
nn MODIFY PROGRAM OPTIONS (Y,N,?) ?
(
From this point on, the process of reviewing the preset options and making changes is
the same as that described for manually running the ONUERL program. (See 9.1.1.)
9.2. ONUERL Program Options
The ONUERL program options are listed with their associated message display
numbers and functional descriptions in Table 9-1. The shaded entries in the table
identify the preset (default) value for each option. When executed, ONUERL uses the
preset option values unless you elected to make changes to these values (by including
the OPT=Yparameter in the RV command). Modified option values (except for
SUMMARY=D) remain in effect only for the current execution of the program.
Therefore, you must define the changes each time you run the program.
Table 9-1. ONUERl Program Options
OPEN= [ :
(
c
1
Current. ONUERL opens the error log file $Y$ELOG at the record following the
final record of the last ONUERL run. ONUERL processes to the most recent record.
P
Prior. $Y$ELOG is opened at the same record where it was opened the last time
ONUERL was run. The data displayed the last time is displayed again, along with
any new data. ONUERL processes up to the most recent record.
B
Begin. $Y$ELOG is opened at the beginning of the file and displays the oldest
record to the most recent record in the file.
continued
7004 5208-000
9-5
ONUERL Program
Table 9-1. ONUERL Program Options (cont.)
2
SUMMARY=
I;~ 1
11
N
R
D
Y
Yes. Summary data gathered during execution of ONUERL is written to the system
journal file for tramnsmission later.
Threshold. Summary data gathered during the execution of ONUERL is examined for
over-threshold occurrence. When total error count exceeds 5 percent of the total
I/O count for any device, the program displays a message indicating that summary
data is being written to the system journal file; the operator can later transfer
this information to the support center.
(
If over-threshold condition did not occur, summary data gathered is merged into
the summary data file $Y$ESUM for future transmission.
N
No. ONUERL operates in local mode and does not spool error summary data to the
system journal file even if over-threshold conditions are detected. However,
summary data is still saved in the summary data file ($Y$ESUM) for future
transmission. Note that summary data present in $Y$ESUM before ONUERL is run is
destroyed unless SUMMARY=REPEAT.
R
Repeat. Indicates that summary data previously saved in $Y$ESUM is to be
written to the system journal. In this case, only $Y$ESUM is opened, not the
error log file ($Y$ELOG). If there are no records in the $Y$ESUM file, an error
message is displayed and the program is terminated.
D
Disable. This option permanently disables the writing of error summary data
to the system journal file. It is intended for those sites where transmission of
summary data is not allowed.
If writing of summary data is disabled, selection of the YES or THRESHOLD option
prompts a console message to determine if you want writing to the system journal
restored.
If writing was disabled, selection of the REPEAT option prompts a console
message indicating that the request cannot be honored.
3
ELOG= { ~ }
y
Yes. ONUERL has no effect on error logging.
N
No. Error logging is suspended during ONUERL execution.
continued
9-6
7004 5208-000
(
ONUERl Program
Table 9-1. ONUERl Program Options (cont.)
4
DOC= { ~ }
Y
Yes. Operating instructions are printed at the local printer, and the program
terminates.
No. Operating instructions are not printed.
5
Y
Yes. Modify recoverable error thresholds.
No. Run with present recoverable error thresholds.
D
Display. Display current recoverable error thresholds. This option will broadcast
the following message: - DO YOU WISH TO ALTER THRESHOLDS (Y,N)
6
Y
Yes. Causes a hexadecimal dump of the entire contents of $Y$ELOG. (This is a
debug option.)
No. Do not dump $Y$ELOG.
7
Initialize $Y$ESUM file
Update $Y$ESUM file.
8
Y
Yes. Causes a hexadecimal dump of the entire contents of $Y$ESUM. (This is a
debug option.)
No. Do not dump $Y$ESUM.
7004 5208-000
9-7
ONUERl Program
The step-by-step sample session shown in Figure 9-1 illustrates the progam messages
and operator responses that are used when making changes to the ONUERL program
options.
RV ONUERL"OPT=Y
R03 RUN PROCESSOR SUCCESSFULLY PROCESSED ONUERL
JC01 JOB ONUERL EXECUTING JOB STEP ONUERL00 #001 13:28:30
OS/3 ONUERL-ERROR LOG EDITOR VERSION xx/xx.
11 . MODIFY PROGRAM OPTIONS (Y,N,?)
11 ?
- PRESET OPTIONS :
OPEN=CURRENT, SUMMARY=THRESHOLD, ELOG=YES, DOC=NO,
THRESHOLD=NO, DUMP=NO, ESUMFIL=U, DMPSUM=NO
14 - MODIFY PROGRAM OPTIONS (Y,N,?)
?
14 Y
15 • ENTER OPTIONS, SEPARATED BY COMMAS (1,2,3,4,5,6,7,8,?)
15 ?
- 1=OPEN, 2=SUMMARY, 3=ELOG, 4=DOC, 5=THRESHOLDS,
6=DUMP, 7=ESUMFIL, 8=DMPSUM
17 - ENTER OPTIONS, SEPARATED BY COMMAS (1,2,3,4,5,6,7,8,?)
17 1,2,3,4,5,6,7,8
18 - 1: OPEN= (C,P,B,?)
18?
- C=CURRENT.(ERRORS LOGGED SINCE LAST EDIT).
P=PRIOR.(REPEAT LAST EDIT).
B=BEGIN.(ENTIRE CONTENTS OF ERROR LOG).
22 - 1: OPEN= (C,P,B,?)
22C
23 . 2: SUMMARY= (T,Y,R,N,D,?)
23?
- T=SPOOL SUMMARY IF THRESHOLD EXCEEDED.
Y=SPooL SUMMARY TO SYSTEM JOURNAL
R=REPEAT LAST SUMMARY SPOOLING
N=NO SUMMARY SPOOLING SUMMARY THIS RUN
D=INHIBIT SUMMARY SPOOLING SUMMARY PERMANENTLY.
29 - 2: SUMMARY= (T,Y,R,N,D,?)
29T
30 - 3: ELOG=(Y,N,?)
30?
- Y=HAS NO EFFECT ON ERROR LOGGING.
N=SUSPEND ERROR LOGGING DURING EDIT.
33 - 3: ELOG=(N,Y,?)
33Y
34
4: DOC= (N,Y,?)
34?
. N=INHIBIT PRINTING OF OPERATING INSTRUCTIONS
Y=PRINT OPERATING INSTRUCTIONS AND TERMINATE
37
4: DOC= (N,Y,?)
37N
38
5: THRESHOLDS= (N,D,Y,?)
38?
. N=RUN WITH CURRENT THRESHOLDS
D=DISPLAY CURRENT THRESHOLDS
Y=MODIFY RECOVERABLE ERROR THRESHOLDS
13:28
13:28
13:28
13:28
13:28
13:28
13:28
13:28
13:28
13:28
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:29
13:30
13:30
13:30
13:30
13:30
13:30
13:30
13:30
13:30
13:30
13:30
RV7939
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
Figure 9-1. Sample ONUERl Program Execution (Part 1 of 2)
9-8
(
70045208-000
(
ONUERl Program
(
42 - 5: THRESHOLDS= (N,D,Y,?)
42N
43 - 6: DUMP= (N,Y,?)
43?
- N=INHIBIT DUMP.
Y=HEX. DUMP OF ENTIRE $Y$ELOG.
NOTE: THIS OPTION WILL NOT BE ACCEPTED IF SUMMARY ON.
47 - 6: DUMP= (N,Y,?)
48N
49 . 7: ESUMFIL= (U,I,?)
49?
- U=UPDATE ESUM
I=INITIALIZE ESUM.
52 - 7: ESUMFIL= (U,I,?)
52U
53 - 8: DMPSUM= (N,Y,?)
53?
- N=INHIBlT DUMP
Y=HEX. DUMP OF $Y$ESUM FILE.
56 - 8: DMPSUM= (N,Y,?)
56N
- LAST RUN ON
yy/mm/dd AT
hh:mm:ss
SORT MI00 END OF SORT
175 IN,
0 DELETED
SORT AI86 RECORD COUNT
- THRESHOLD EXCEEDED
- LOGICAL UNIT= 12 VOL= SJ0001
- CONTACT CUSTOMER SUPPORT CENTER FOR TRANSMISSION
JC02 JOB ONUERL TERMINATED NORMALLY
13:34:06
13:30
13:30
13:30
13:30
13:30
13:30
13:30
13:30
13:31
13:31
13:31
13:31
13:31
13:31
13:31
13:31
13:31
13:31
13:31
13:31
13:31
13:32
13:32
13:32
13:33
13:33
13:33
13:34
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
ONUERL
Figure 9-1. Sample ONUERL Program Execution (Part 2 of 2)
9.3. SDF$DSP System Program
When you run ONUERL, the content of the system definition file spools to the system
journal diskette after all summary data is spooled. It also spools simultaneously to the
local printer.
7004 5208-000
9-9
ONUERl Program
9.4. ONUERl Console Messages
Table 9-2 lists the console messages that may be displayed during execution of the
ONUERL program. An explanation and operator action, where required, also are
provided.
Table 9-2. ONUERL Console Messages
MessagejExplanation/Operator Action
ERROR READING PARAM, R0=e·code. TERMINATE? (Y,N)
An error was detected in reading a II PARAM statement from the job control stream, where e-code specifies
the error encountered. Respond Y to terminate program. Respond N to ignore.
INVALID ENTRY nnnnn. IGNORE? (Y,N)
AII PARAM statement has the wrong format, where nnnnn is a display of the PARAM statement. Respond Y to
ignore statement and continue. Respond N to terminate program.
$Y$ELOG IS EMPTY
$Y$ELOG contains no new error data since the last time ONUERL was run. ONUERL is terminated.
ERROR ACCESSING $Y$ELOG. R0=e·code
An error was detected in attempting to access $Y$ELOG, where e-code is the error encountered. The
program makes on attempt at recovering. If unsuccessful, ONUERL terminates.
(
INVALID DATA IN $Y$ELOG. JOB TERMINATED
The data in $Y$ELOG is meaningless. ONUERL terminates.
FIRST RECORD NOT HISTORICAL RECORD. JOB CANCELED
The beginning of $Y$ELOG cannot be found. ONUERL terminates.
COTABL FULL. JOB CANCELED
The capacity of the internal device list was exceeded. ONUERL terminates.
(
MEDIA TABLE FULL
The capacity of the media error table was exceeded. Further media errors are not saved.
NO SUMMARY DATA AVAILABLE. JOB CANCELED
In running ONUERL in the SUMMARY, REPEAT mode, no summary data is found in $Y$ESUM. ONUERL
terminates.
$Y$ESUM nnnn error. CD$FNMC: sense·data
An error was detected in accessing $Y$ESUM, where nnnn is OPEN, CLOSE, INPUT, or OUTPUT. Sense-<1ata
is the contents of the four sense bytes returned by the system. ONUERL terminates.
continued
9-10
7004 5208-000
ONUERL Program
Table 9-2. ONUERL Console Messages (cont.)
MessagejExplanation/Operator Action
$Y$ESUM ERROR: EOF. FILE CAPACITY EXCEEDED
An attempt to create a new record failed for lack of space. ONUERL terminates. $Y$ESUM must be erased
and reallocated. Then ONUERL can be re-executed. File $Y$ESUM is reinitialized with the latest device list.
NEW SUMRCD CREATED FOR DEVICE nnn
This channeVdevice number was assigned to a new or different device type. A new record must be created
and stored in $Y$ESUM.
INVALID DATE/TIME: xxx. JOB CANCELED.
Atest of system date and time shows invalid values that are displayed. Error records cannot be summarized
reliably. ONUERL is canceled. Rerun ONUERL when date and time have been properly entered.
$Y$ESUM NOT INITIALIZED.
This message appears if $Y$ESUM file was not initialized. It is followed by:
ENTER CUSTOMER-ID. ( _________ ,?)
This message is displayed during $Y$ESUM file initialization. Enter your 9-character customer ID. The
following message then appears:
CUSTOMER-ID IS your-customer-id. CONFIRM (Y,N)
This message echoes the customer ID you entered and requests your confirmation.
If ? is entered as a response to the customer ID request, the following message appears:
DEPRESS EOT IF 10. NOT AVAILABLE.
SUMMARY PERMANENTLY DISABLED. RESTORE? (Y,N)
Option SUMMARY=YES or THRESHOLD was selected, but SUMMARY was previously disabled. Respond Y to
restore SUMMARY capabilities. Respond N to ignore this request.
(
CANNOT HONOR SUMMARY REQUEST. JOB CANCELED.
Option SUMMARY=REPEAT was selected, but SUMMARY was previously disabled. No SUMMARY data is
available for transmission.
SUMMARY NOT TRANSMITTED. SEND? (Y,N)
Over-threshold occurred in the last execution of ONUERL, and SUMMARY data was not transmitted.
Transmission must be made before the program can proceed with collection of new data. Respond Y to
permit transmission. Respond N to terminate program.
INVALID DISKETTE (R,C?)
The diskette in FDDI is not a system journal diskette. Respond Rto retry after loading the correct diskette.
Respond C? to cancel program.
continued
7004 5208-000
9-11
ONUERL Program
Table 9-2. ONUERL Console Messages (cont.)
Message/EXplanation/Operator Action
THRESHOLDS EXCEEDED
Error thresholds were exceeded for the processing period.
LOGICAL UNIT= xx VOL=xxxxxxxxxxx
Identifies the logical unit and volume being referenced.
OVER-WRITE, NEXT LU, END JOB? (O,N,E,?)
Request for operator permission to write to the LU and volume previously displayed. The choices available
are:
1. Overwrite the volume on the current logical unit.
2. Skip this logical unit and proceed to the next available logical unit.
3. Terminate the program without writing any data.
(
OVER-WRITE, ANOTHER DISKETTE, END JOB? (O,D,E,?)
Request to operator when LUOO (FOO) is being accessed and the volume inserted is not SJOOOl. The choices
available are:
1. Overwrite the volume on logical unit 00.
2. Allow operator to insert another diskette.
3. Terminate the program without writing any data.
INSERT 1.44MB FORMATTED DISKETTE IN FDD1 AND 60
Message displayed when logical unit 00 (FOOl is used as system journal. Insert diskette into FDO and then
enter '50 job name'
LOGICAL UNITS/MEDIA FOR SYSTEM JOURNAL NOT USABLE. PROGRAM TERMINATING
The permitted logical units were not usable.
9.5. ONUERL Reports
The reports obtained as a result of running the ONUERL program provide a
comprehensive listing of all errors contained in the $Y$ELOG file, as defined by the
program parameters. The main body of the reports consists of a single line for each
error log entry. The entries are sorted chronologically by channel device number. The
reports also include a summary of sense bits in error for the device, and a summary of
total error count versus total count of valid IIOs by device address.
Note:
9-12
ONUERL reports do rwt include your customer-id unless you add it to the
control stream. To do so, use the general editor (EDT). (The ONUERLjob
control stream resides in the $Y$JCS file located on SYSRES.) When you've
read the file into the workspace, look for the / / PARAM LOG-ID=1.og id data'
statement, where 'log id data' is 29 characters reserved for your installation
name followed by your 9-character customer-id. This information must be
enclosed in single quotes. When you've saved the file, your customer-id is
permanently added to the control stream.
70045208-000
(
ONUERL Program
The description of each summary report heading follows:
device name
N ames the device in error.
CHDV
The channel, subchannel, and device number representing the did for the
device.
date and time
The date and time the error was written to the error log.
VSN
The volume serial number of the media in use at the time of error, if present
in the error log.
J-NME
(
J-ADD
The name of the job (if present in the error log) encountering the error.
The starting address in main storage for the job running at time of error
report.
J-SIZE
Main storage assigned to user job.
CEIQ/CAIQ
Identifies the queue reporting the error: channel attention interrupt queue
(CAIQ) or channel error interrupt queue (CEIQ).
CCW
Identifies the channel command word.
I/O
The number of valid 1I0s prior to the error.
RTRY
The number oftimes the 110 was attempted before reporting the error.
(
STST
The device and subchannel status of the device in error.
DSX
The device status extension byte.
DSSC
The device state sequence code.
DSW
The directive status word.
7004 5208-000
9-13
'ONUERl Program
SS0-SS23
The sense bytes transmitted by the device to the channel at the time of the
error. Up to 24 sense bytes are printed.
OPR
REC
Operator response to error message displayed on console workstation/screen,
if any. Possible response is U (unrecovered), I (ignore), C (cancel), or R
(retry).
Indicates whether the I/O recovered (Y) or not (N).
SENSE BYTE X'80 ' -X'01'
Summary counts of sense bits set for the device_ These counts are taken
from the error log file and will vary depending upon the OPEN option that
was selected.
DEVICE #
The device address (channel, subchannel, and device number) of the device
in error.
DEVICE (did) number of ERROR/S OCCURRED FOR number of VALID I/O'S_
By device address, a summary of total errors versus total I/Os. These counts
are taken from the error log file and will vary depending upon the OPEN
program option that was selected.
VSN/ERROR TABLE FOR DVC (did)
By device address and VSN, a summary of all errors taken from the error
log file. The count will vary depending upon the OPEN program option that
was selected.
Note:
The total of all VSN errors and the device error count will typically be equal
only if all device errors are associated with a VSN.
Samples of the reports produced by the ONUERL program are shown in Figure 9-2.
The samples provided may differ slightly from the actual reports produced for your
system. Supervisor characteristics and ELOG flags displayed in the system
description lines of the ONUERL report are defined in Tables 9-3 and 9-4. MSE
display and CPU retry stack log-out display of the ONUERL report are defined in
Tables 9-5 and 9-6. Exigent machine check displays are defined in Table 9-7.
9-14
7004 5201'W00
(
/~"
-...,J
o
~
U1
I\.)
~
o
o
OS/3 ONUERL·ERROR LOG EDITOR VERSION xx/xx,
*****device name*********************
*
DVC TYPE CODE:
*
CHAN./DVC ADDR.: 00 00
*
*
FEATURES:
*
*
24x80 SCREEN
*
*
*,
*
LGERMSK: xxxx, LGEMSK: xxxx
*************************************
CUST. Ig ; •••••••••• - ••••• - ••••••
*****device name*********************
*
*
DVC TYPE CODE:
*
*
CHAN./DVC ADDR.: 00 00
*
*
FEATURES:
*
*
24x80 SCREEN
*
*
LGERMSK: xxxx, LGEMSK: xxxx
*************************************
SERIAL# .. _. yy/mm/dd hh.mm PAGE XX
*****device name*********************
DVC TYPE CODE:
*
*
*
CHAN./DVC ADDR.: 00 00
*
*
FEATURES:
*
*
24x80 SCREEN
*
LGERMSK: xxxx, LGEMSK: xxxx
*
*
*************************************
OS/3 ONUERL·ERROR LOG EDITOR VERSION 48/29
CUST. 10.: XXXXXXXXX
yy/mm/dd hh.mm PAGE XX
CUSTOMER ID.: C42722 • OS/3 VER.
15,
REV. 00, DATE yY/mm/dd, TIME 07.27.30, FLAGS 0080, CHARACTERISTICS 33BE0080
, SYSRES: 401, PRINTER: 330, READER: 332,
MAIN STORAGE
SIZE; 00100000, USER MEMORY SIZE:000C2400
, - ' $Y$ELOG: 401-, -... _.,.
BIT MAP ADDRESS: 01F478, BITMAP WORD COUNT:
1. BITMAP DATA: (IN BITS. EACH BIT=64K. O=ON LINE, 1=OFF LINE)
00000000 00000000 11111111 1111111
~.
OS/3 ONUERL·ERROR LOG EDITOR VERSION 48/29
CUST .'-10. : 'XXXXXXXXX
yy/mm/dd
hh.mm PAGE XX
* EMCIC *
yy/mm/dd 20.40.28 JOB:
A~PR: 000000.
SIZE: 000000.
MCIC: 0800005D 20000000.
PSW: E0010000 00000000.
TOO: 9786DAC6 33CE8000.
SPV RGS:OO: 00000000, 01: 0000D7CO, 02: 000261B8, 03: 60026102, 04: 00003002, 05: 00008860, 06:046FAD42, 07: 0000E240,
08: 00001720, 09: 0000E240, 10: 400034FA, 11: 000000400, 12: 0000DE94, 13: 400261BA, 14: 000034F4, 15: 0000320A,
MMU LOG #0 0: 00000000 00000000, 1: 00000000 00000000,
2: 00000000 00000000,
3: 00000000 00000000, '4: 00000000 00000000,' 5: 00000000 00000000,
ED MCIC: 08000050 30000000. ED ERO: 00000390.' EO ER1: 110201FO.
INST. + CACHE LOGOUT: 0: 00000000 00000000, 1: 00000000 00000000,
OPERAND CACHE LOGOUT: 0: 00000000 00000000, 1: 00000000 00000000,
FLOATING POINT LOGOUT:O: 00000000 00000000, 1: 00000000 00000000,
o
2
C
ITI
::::0
r
."
""'l
~
.......
U1
Figure 9-2. Sample Error log Report Format (Part 1 of 10)
o
O'Q
""'l
Q)
3
o
If'
......
m
:2
c:
I'TI
AI
r
OS/3 ONUERL-ERROR LOG EDITOR VERSION 48/29
BPU LOGOUT: 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000
LOW MEMORY (X'310'-'313'): 00000000
MACHINE CHECK INTERRUPT CODES:
SUBCLASS: EXTERNAL DAMAGE
AREA CODE: I/O EXTERNAL DAMAGE: CHC AND lOP ABNORMALITY
VALIDITY:
8
OS/3 ONUERL-ERROR LOG EDITOR VERSION 48/29
yy/nm/dd
CUST. 10.: XXXXXXXXX
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
97860AC6
yy/nm/dd
CUST. 10.: XXXXXXXXX
hh.nm PAGE XX
xxxxxxxxxxxxxxxxxxxxxxxx
J - NME: _______
_
I/O RTRY STST DSX DSSC DSW SSO-1
J-SIZE:
J-ADD:
hh.nm PAGE XX
2-3 4-5 6-7 8-9 10-11 OPR REC
xxxxxxxxxxxxxxxxxxxxxxx xxxxx xx xxxxx xxxx xx xx xxxxx xxxx xxxx xxxx xxxx xxxx x
OS/3 ONUERL-ERROR LOG EDITOR VERSION 48/29
U-14 TAPE DR., CHDV: 180
CCW/ICW
yy/nm/dd hh.nm.ss
VSN:TAPE1
C308A80C60002900 0108A80C20022900
XPCT BLK:
CMD: WRITE
yy/nm/dd
CUST. 10.: XXXXXXXXX
J-NME:DUMPTAPE
0001: RCVD BLK:
o
~
(]'I
N
~
Figure 9·2. Sample Error log Report Format (Part 2 of 10)
o
o
~
x
hh.nm PAGE XX
I/O RTRY STST DSX DSSC DSW SSO-1 2-3 4-5 6-7 8-9 10-11 OPR REC
J-ADD:
J-SIZE:
2 2 OEOO 800 35 00 0840 0084 0000 0000 0000 0000
Y
VRC SPEEC CHK
0001
'-I
,,~
~,
iiJ
3
00000000
00000000
00000000
33CE8000
device name. CHDV: xxxx, ADDR: xxxxxx. SZE: xxxxxx
ICW/CCW
yy/nm/dd hh.nm.ss
VSN:
"o'""
II'Q
/~,
-...J
0
0
.p.
U1
'"0
~
0
0
SENSE BYTE
0
X'80'
X'40'
xxx
xxx
xxx
xxx
2
xxx
xxx
3
xxx
xxx
xxx
4
xxx
5
xxx
xxx
6
xxx
xxx
7
xxx
xxx
8
xxx
xxx
9
xxx
xxx
xxx
A
xxx
B
xxx
xxx
xxx ERROR/S OCCURRED FOR
X'20'
X'10'
X'08'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxxxxxx VALID I/O's
X'04'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
X'02'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
X'01'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
DEVICE # xxx
VSN/ERROR TABLE FOR DVC 1B1.
VSN:TAPE2
24 ERRORS FOR 7475 I/O'S
VSN:SCRT
33 ERRORS FOR 12612 I/O'S
VSN:TEST01
6 ERRORS FOR 6283 I/O'S
5 I/O'S
VSN:OlMTAP
1 ERRORS FOR
VSN:R512Q1
25 I/O'S
22 ERRORS FOR
OS/3 ONUERl-ERROR lOG EDITOR VERSION 48/29
CUST. 10.: XXXXXXXXX
yy/rrm/dd
hh.rrm PAGE XX
8470 DISC DR., CHDV: 290, ADDR: 000000, SZE: 000000
8-11 12-15
16-19
20-23 OPR REC
RTRY STST DSSC 0·3 4-7
CCW
I/O
J-NME:________
J-ADD:
J-SIZE:
yy/rrm/dd hh.rrm.ss
VSN:REl08S
1 1 0200 35 00000000 00000038 00000000 00000000 00000000 00000000
00000000000000000 1300516860000008
CMD: RECAll B.
ClY: 768,
HD:N/A.
Y
o
c:
:2
m
:::0
r-
"'0
Figure 9-2. Sample Error log Report Format (Part 3 of 10)
~
......
-...J
o'"'
O'Q
'"'I»
3
I~m
\f'
......
00
SENSE BYTE
X'80'
X'40'
xxx
0
xxx
xxx
xxx
2
xxx
xxx
xxx
3
xxx
xxx
4
xxx
xxx
5
xxx
6
xxx
xxx
xxx
7
xxx
8
xxx
xxx
xxx
9
xxx
xxx
A
xxx
B
xxx
xxx
xxx ERROR/S OCCURRED FOR
X'04'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
X'20'
X'10'
X'08'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxxxxxx VALID I/O's
VSN/ERROR TABLE FOR DVC xxx.
x ERRORS FOR
VSN:REL08S :
xxxx I/O'S
cn
80
768
20
OS/3 ONUERL'ERROR LOG EDITOR VERSION 48/29
HEAD
N/A
N/A
N/A
X'02'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
"""'"
0
"'"
S\)
3
ERR
04
01
03
YY/I1111/dd
I/O RTRY STST DSX DSSC DSW SSO-1
J-ADD:
J-SIZE:
1 OEOO 0000 35 00 0811
"-J
§
U1
N
~o
Figure 9·2. Sample Error log Report Format (Part 4 of 10)
o
/"'.
r
IrQ
CUST. ID.: XXXXXXXXX
8418 DISC DR., CHDV: 2A1
CCW
CMD: SEEK-READ
CYL: 711, HD:N/A.
yy/l1111/dd hh.lIII1.ss
VSN:SCRT
J'NME:PREP18
00000000000000000 17005B0060000008
CYL: 711,
HD:N/A_
CMD: SEEK-READ
::0
DEVICE # xxx
X'01'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
~~
hh.1III1 PAGE XX
2-3 4·5 6-7 8-9 10-11 OPR REC
DTA FLD ECC
0220 OC06 8000 0000 0000
DTA FLD ECC
Y
,,~
.....
o
~
(J1
N
~
o
SENSE BYTE
0
1
2
X'80'
X'40'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
3
xxx
xxx
4
xxx
xxx
5
xxx
xxx
6
xxx
xxx
7
xxx
xxx
8
xxx
xxx
9
xxx
xxx
A
xxx
xxx
B
x ERROR/S OCCURRED FOR
X'08'
X'20'
X'10'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxxxxxx VALID I/O's
VSN/ERROR TABLE FOR DVC xxx.
x ERRORS FOR
VSN:REL08S :
xxxx I/O'S CYL
80
768
20
OS/3 ONUERL-ERROR LOG EDITOR VERSION 48/29
CUST.
X'04'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
HEAD
N/A
N/A
N/A
ID .:
X'02'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
X'01'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
DEVICE # xxx
ERR
04
01
03
XXXXXXXXX
YY/JIII1/dd
hh.JIII1 PAGE XX
8420/22 DSKTE, CHDV: C20, ADDR: 000000, SZE: 000000
I/O RTRY STST DSX DSSC DSW SSO-1 2-3 4-5 6-7 8-9 10-11 OPR REC
ICW
YY/JIII1/dd hh.JIII1.ss
VSN:
J-NME: _______ _
J-SIZE:
J-ADD:
N
0000 0000 35 03 0000 0000 0000 0000 0000 0000
1
5600886A2000008000000070 000000000000000000000000
CMD: READ VOL. 10
I/O TERMINATION UNKNOWN
o
2
c::
I'll
::0
I
"0
Figure 9·2. Sample Error log Report Format (Part 5 of 10)
""'I
o
(JQ
""'I
\f'
I-'
lO
I»
3
ONUERl Program
SENSE BYTE
0
1
2
3
4
5
6
7
8
X'80'
X'40'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
9
xxx
xxx
A
xxx
xxx
B
xxx
xxx
x ERROR/S OCCURRED FOR
X'20'
X' 10'
X'08'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxxxxxx VALID I/O's
VSN/ERROR TABLE FOR DVC xxx.
VSN:ID16JO
x ERRORS FOR
VSN:JHPDD1
x ERRORS FOR
VSN:JHPDD2
DEVICE
DEVICE
DEVICE
DEVICE
DEVICE
DEVICE
DEVICE
DEVICE
DEVICE
DEVICE
DEVICE
xxx:
xxx:
xxx:
xxx:
xxx:
xxx:
xxx:
xxx:
xxx:
xxx:
xxx:
x ERRORS FOR
xxxx
xxxx
xxxx
xxxx
xxxx
xxxx
xxxx
xxxx
xxxx
xxxx
xxxx
ERRORS
ERRORS
ERRORS
ERRORS
ERRORS
ERRORS
ERRORS
ERRORS
ERRORS
ERRORS
ERRORS
OCCURRED
OCCURRED
OCCURRED
OCCURRED
OCCURRED
OCCURRED
OCCURRED
OCCURRED
OCCURRED
OCCURRED
OCCURRED
x I/O'S TRK
01
xxxx I/O'S TRK
36
36
x I/O'S TRK
36
FOR
FOR
FOR
FOR
FOR
FOR
FOR
FOR
FOR
FOR
FOR
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
VALID
VALID
VALID
VALID
VALID
VALID
VALID
VALID
VALID
VALID
VALID
SCTR
01
SCTR
06
07
SCTR
08
X'04'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
X'02'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
X'01'
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
DEVICE # xxx
(
ERR
05
ERR
05
05
ERR
05
I/O'S
I/O'S
I/O'S
I/O'S
I/O'S
I/O'S
I/O'S
I/O'S
I/O'S
I/O'S
I/O'S
(
Figure 9-2. Sample Error Log Report Format (Part 6 of 10)
9-20
7004 5208-000
,~
o
"""
~
U1
I'\.)
~
o
o
OS/3 ONUERL·ERROR LOG EDITOR VERSION 48/29
CUST. 10.: XXXXXXXXX
YY/IlIIl/dd
hh.1lIIl PAGE XX
YY/IlIIl/dd
hh.1lIIl PAGE XX
hh.llIIl.ss
OS/3 VER. 14/00 CUST. 10.: XXXXXXXXX YY/IlIIl/dd
FLAGS 0080, CHAR. 73B30080, MAIN STOR. 00600000
SYSRES: 2AO, PRNTR: 005, READER:
C20, $Y$ELOG: 2AO
BIT MAP DATA (IN BITS. ONE BIT=64K.
O=ON LINE, 1=OFF LINE)
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
OS/3 ONUERL·ERROR LOG EDITOR VERSION 48/29
CUST. 10.: XXXXXXXXX
VER. 48/29 . SENSE SUMMARY DATA AT: hh.1lIIl
CUSTOMER ID.:XXXXXXXXX
DVC LIST:C12,C14,C18, . . . . . . • .
OVER· THRESHOLD DVC/S:XXX,XXX,XXX ••.••.•
SUMMARY SPAN: YY/IlIIl/dd. TO YY/IlIIl/dd.
~
I'\.)
......
U·RCD ADDR
DEVICE
THRESH. VALUE
TOT. I/O COUNT
RECOV. COUNT
UNRECOV. COUNT
OPR RTRY
BUF LOAD CHECK
390
0770
.050
15
4
5
3
9
TAPE ADDR
DEVICE
THRESH. VALUE
TOT I/O COUNT
NOISE
SKEW CHCK
END CHK
RD/WR VRC CHK.
MTE/LRC CHK.
ENV/EDD CHK.
480
481
503
U26/28 BH2 BT32
.050
.050 .050
58582 68231 81323
114
42
6
29
174
3
101
0
2
c::::
m
::tI
r
"0
211
6
46
"'
<:)
(JQ
"'
£I)
Figure 9-2. Sample Error log Report Format (Part 7 of 10)
3
ONUERL Program
DISK ADDR
DEVICE
THRESH. VALUE
TOT I/O COUNT
1A1
8494
.050
6267
DISK ADDR
DEVICE
THRESH. VALUE
TOT I/O COUNT
RECOV. COUNT
UNRECOV. COUNT
OPR RTRY
DVC CHCK
10 FLO DATA CHK
STOP STATE
186
8419
.050
142
12
DSKT ADDR
DEVICE
THRESH. VALUE
TOT I/O COUNT
RECOV. COUNT
UNRECOV. COUNT
DVC NOT ROY
NO DTA SEP
C21
8420/22
.050
19
7
4
5
6
1A2
1A3
8494 8494
.050
.050
8746 12089
(
68
2
74
5
2
(
Figure 9-2. Sample Error log Report Format (Part 8 of 10)
9-22
7004 5208-000
/'
BETWEEN yy/mm/dd AND yy/mm/dd, OVER-THRESHOLD DEVICES:
-...J
o
~
U1
N
o
~
o
o
* EMCIC *
DATE: yy/mm/dd TIME: hh.mm.ss MCIC:
ED MCIC: 00000000 00000000 PSW:
ED RO: 00000000 ED R1: 00000000
DATE: yy/mm/dd TIME: hh.mm.ss MCIC:
ED MCIC: 00000000 00000000 PSW:
ED RO: 00000000 ED R1: 00000000
ERROR ACTIVITY BY VSN.
DVC VSN
TIC
TOC
20200000 OOOBA9DO
E0040000 9006825C
20200000 000BBD60
E0040000 9006825C
TIC/TOC
67921 0_000353
2AO REl08X
24
4; 28, 2;
CYl,ER#: 155,
2; 536,
1; 466,
1; 776, 1;
1;
465,
162, 10; 132,
2; 140,
REL082
22
68105 0.000323
CYL,ER#: 462,
3; 466,
4; 464,
2; 163, 1,•
1; 140,
2; 781, 1,.
162,
1; 543,
2; 542,
28,
2; 155, 3',
2A1
DATAPK
CYL,ER#: 54,
2;
89
69,
39856 0_002233
12; 81,
7; 145, 12;
OS/3 ONUERL-ERROR LOG EDITOR VERSION 48/29
CUST. 10.: XXXXXXXXX
9',
70, 18; 71, 11; 00,
8', 74,
55,
53, 1,•
SCRT
49
51091 0.000959
CYl,ER#: 11,
4; 424,
8; 453, 11; 711,
12;
764, 14;
<.p
N
W
8
3095 0.002585
290 REL08S
CYl,ER#: 80,
4; 768, 1; 20, 3',
5
6 0.833333
C20 1D16JO
TK,SCTR,ER#: 01, 01, 5',
JHPDD2
5
674 0.007418
yy/mm/dd
hh.mm PAGE XX
9',
o
2:
c:
m
::u
r
."
'"'l
o
(JQ
'"'l
I»
Figure 9·2. Sample Error log Report Format (Part 9 of 10)
3
0
:2
~
c:
rn
.t>-
TK,SCTR,ER#:
JHPDD1
TK,SCTR,ER#:
36, 08,
10
36, 06,
5-,
7277 0.001374
5; 36, 07,
5',
::::a
r
.,"'0
0
(I'Q
C21
OS3PCB
TK,SCTR,ER#:
2
16, 01,
I~
10 0.2
2',
- END OF DATA
NOTES: + SIGNS IN TOTAL I/O COUNT INDICATE THAT THE I/O COUNTER HAS WRAPPED.
NUMBER SHOWN IS MINIMUM AND MAY BE GREATER BY 32768 BYTE INCREMENTS
** IN OTHER COUNTS INDICATE THAT ERROR THRESHOLD HAS BEEN EXCEEDED.
ONLY COUNTERS WITH NON-ZERO VALUES ARE DISPLAYED.
I/O COUNT INCLUDES THE ON ON WHICH ERROR HAS INCURRED.
OS/3 ONUERL-ERROR LOG EDITOR VERSION 48/29
yy/nm/dd
CUST. ID.: XXXXXXXXX
SYSTEM DEFINITION FILE
DEVICE ADDRESS
TYPE/FEATURE
MICROCODE NAME
C10
WSC
WSC2-400
DEVICE ADDRESS
TYPE/FEATURE
MICROCODE NAME
C13
3560
WS1DJOOO
Note:
.......
Each device in the device table is printed here in this report .
tTl
BASE OS/3 RELEASE
§
N
~
o
o
-- 14.0.0
Figure 9-2. Sample Error log Report Format (Part 10 of 10)
/~
"~~
hh.nm PAGE XX
ONUERL Program
Table 9-3. CHARACTERISTICS Field Displayed in ONUERl Report
Byte No.
Bit No.
0
0
1
2
3
4
5
6
7
1
0
1
2
3
4
(
5
6
7
2
0
1
2
3
4
5
6
7
3
0
1
2
3
4
5
6
7
Definition
Minimum supervisor
Software performance monitor
Online diagnostics
Timer
N/A
Suppress JC58 message display
Suppress R06 message display
Memory consolidation
Error logging
User files locked
Job accounting
Spool ing
Rollout/roll in
Input spooling
Shared code
Tape block numbers
Console log
Retain console log
File lock = share
File lock = granule
Interactive OS/3
Maximum CPU time configuration
Maximum wall time configuration
Workstation support
RC symbiont available
CDI supported
DTFs supported
Ignore DM SFTs
Dynamic buffer management
Resident loader
Setime support
Workstation RU can use card RDR
Table 9·4. FLAGS Field Displayed in ONUERl Report
(
Byte No.
Bit No.
0
N/A
1
0
1
2
3
4
5
6
7
7004 5208-000
Definition
N/A
Error log effective
Error log active
Logging machine check HPR
ELOG not recovered at IPL
Exigent machine check to be logged
Retry stack machine check to be
logged
Main storage machine check to be
logged
Resident ELOG in control
9-25
ONUERL Program
Table 9·5. MSE Display of ONUERL Report
Definition
Item
ADR
Address range in hexadecimal
CNTRL bits
0:
ENC (ENable Count)
When 1, permits the incrementation of the near-valie count field in
this MSE log entry.
1:
EN! (ENable Incrementation)
When 1, permits the incrementation of the total near-valid count field
in control register 13.
2:
SR (Source Report)
When 1, indicates the near-valid count field in this MSE log entry has
been incremented.
3:
MS (Multiple Syndrome)
When 1, indicates that one or more syndrome changes have been detected
while logging into this MSE log entry.
4-6:
Reserved
7:
CO (Carry Out)
When 1, indicates the near-valid count in this MSE log entry has
wrapped around (FFFF 16 to 0000 16 ), Multiple occurrences of wraparound
will be merged.
SYND
(SYNDrome)
Contains the most recent syndrome recorded, if any, in this MSE log entry.
This identifies the byte and bit position (X-coordinate) at which the singlebit failure (corrected) occurred.
COUNT
Contains a count of the occurrences of logging into the particular MSE log
entry.
(
(
9-26
7004 5208-000
ONUERl Program
Table 9-6. CPU Retry Stack Log-Out Display of ONUERL Report
Definition
Item
(
error CLASS
00:
01:
02:
03:
04:
05:
06:
07:
08:
09:
0A:
OB-FF:
RETRY COUNT
Indicates the number of retries that occurred in the process of recovering
from the failure described. Exceeding 255 retries results in an exigent
machine check.
HyPerViSoR
State
indicator
(currently
active
slot)
WD2 and WD3
01:
02:
03:
04:
05:
06:
07:
Not used
Internal CPU
COS
Main storage
M·bus
D-bus
MSP detected unconnectable ECC error
MSP detected error (non-ECC related)
I/O structure fauLt
Channel check
Machine check hardware mask (MC bit) set
Reserved
DBUS extension
OMA
MLCM
SOMA
QUER
Maintenance panel
S-2
The format of words 2 and 3 depends upon the error class:
Error Class 01, 02
Word 3, bits 16-31 indicate the failing microinstruction or COS
address
Error Class 03, 06, 07
Word 3, bits 0-7 indicate the absolute main storage address.
Error Class 04
Words 2 and 3 contain the error report from failing unit.
(
Table 9-1. Exigent Machine Check Displays
Item
Mcrc
PSW
TOO
SPV RGS
ED MCIC
ED ERO, ER1
7004 5208-000
Definition
Machine check interrupt code
Program status word
Time of day
Supervisor registers
External damage MCIC
External damage registers 0,
9-27
ONUERl Program
9.6. Error Log Analysis (ONELAN Program)
The ONE LAN program provides error log analysis and functions as part of the
ONUERL program. You use ONE LAN to display accumulated error data in the form
of graphs and tables. Analyzing errors in this way provides you with:
•
Equipment deviation
•
Equipment trends and performance
•
Significant error counts
•
Serious equipment error problems
You can obtain this information for individual devices (device error count) or for all
devices of a particular type (subsystem error count). The error counts are based on
monthly totals. Each graph displays up to 5 months of accumulated errors.
Note:
(
Before running ONELAN for the first time, ONUERL must be run to
properly initialize the $Y$ESUM file used by ONELAN. It is also
recommended that ONUERL be run at least twice between executions of
ONELAN so that ONELAN produces a more meaningful output.
Enter the following command to execute the ONELAN program:
RVllONELAN
After ONELAN begins to execute, it displays the following message:
ONE LAN . ERROR LOG ANALYSIS VER. 01/06
. DO YOU NEED HELP RUNNING THIS PROGRAM? (Y,N)
Your answer to this message determines whether you use standard or tutorial mode to
communicate your requests to the ONELAN program. You cannot change modes after
making a selection unless you reload the entire program.
(
Enter N for standard mode, Y for tutorial.
9.6.1. Standard Mode Procedure
When standard mode is selected, the program displays the following message:
nn
ENTER REQUEST (LST,DOC,ALL,DVC,SUB,END,?)
The message lists the keywords that identify the options for running ONELAN. It
requests you to enter the keywords related to the functions you want performed.
9-28
7004 5208-000
ONUERl Program
Enter a '?' if you want the program to display definitions for the keywords. The
program redisplays the 'ENTER REQUEST' message after listing the definitions.
nn
AVAILABLE REQUESTS:
LST: DISPLAY LIST OF AVAILABLE GRAPHS.
DOC: PRINT OPERATING INSTRUCTIONS.
ALL: PRINT ALL GRAPHS.
END: TERMINATE PROGRAM.
DVC: PRINT DEVICE GRAPH.
SUB: PRINT SUB-SYSTEM GRAPH.
ENTER REQUESTS (LST,DOC,ALL,DVC,SUB,END,?)
Enter the keywords in any order (freeform) but make certain that they are preceded
by the message-id number and separated by commas.
nn DVC,SUB
(
Entering the DVO (device graph) keyword displays the following message requesting
you to identify the device by channel (0), sub channel (S), and unit (U) address:
- ENTER DEVICE ADDRESS (CSU(,CSU) ... ,?)
Enter the addresses. Multiple addresses must be separated by commas. To display a
sample address, enter a question mark (?).
Entering the SUB (subsystem graph) keyword displays the following message
requesting you to enter the channel (0) and subchannel (S) address for the subsystem:
- ENTER SUB-SYSTEM ADDRESS (CS(,CS) ••• ,?)
Enter the addresses. Multiple addresses must be separated by commas. To display a
sample address, enter a question mark.
After validating the device and subsystem addresses, ONELAN directs the
appropriate graphs to the system printer.
(
When more than one keyword is entered on a line, the program honors them one at a
time until there are no outstanding keywords. If the END keyword is omitted, the
program redisplays the 'ENTER REQUEST' soliciting you to enter additional
keywords. If any keywords are specified after "END", they are not processed.
To terminate ONE LAN , enter the END request when the "ENTER REQUEST"
message is redisplayed.
7004 5208-000
9-29
ONUERl Program
A sample ONE LAN dialog in standard mode is shown in Figure 9-3.
RV ONE LAN
R03 RUN PROCESSOR SUCCESSFULLY PROCESSED ONELAN
JC01 JOB ONELAN EXECUTING JOB STEP ONUERL00 #001 09:20:17
ONELAN-ERROR LOG ANALYSIS VER. xx/xx
34 - DO YOU NEED HELP RUNNING THIS PROGRAM ?(Y,N)
34 N
- LAST RUN ON yy/mm/dd AT hh:mm:ss
36 - ENTER REQUEST (LST,DOC,ALL,DVC,SUB,END,?)
36 ?
- AVAILABLE REQUESTS:
LST: DISPLAY LIST OF AVAILABLE GRAPHS.
DOC: PRINT OPERATING INSTRUCTIONS.
ALL: PRINT ALL GRAPHS.
END: TERMINATE PROGRAM.
DVC: PRINT DEVICE GRAPH.
SUB: PRINT SUB-SYSTEM GRAPH.
11? - ENTER REQUEST (LST,DOC,ALL,DVC,SUB,END,?)
11 LST,ALL,SUB
GRAPHS AVAILABLE: 311,312,313,314,330,332,370,100,101,103
104,105,320,321
14 - ENTER SUBSYSTEM ADDRESS (CS(,CS) ••• ,?)
14 ?
EXAMPLE: 10,37
16 - ENTER SUBSYSTEM ADDRESS (CS(,CS) .•• ,?)
16 31,32,33,10,37
17 - ENTER REQUEST (LST,DOC,ALL,DVC,SUB,END,?)
17 DVC,END
18 - ENTER DEVICE ADDRESS (CSU(,CSU) ••• ,?)
18 ?
EXAMPLE: 100,101,370
20 - ENTER DEVICE ADDRESS (CSU(,CSU) ••• ,?)
20 103,104,321,END
JC02 ONELAN TERMINATED NORMALLY
09:24:34
9:20
9:20
9:20
9:20
9:20
9:20
9:20
9:20
9:21
9:21
9:21
9:21
9:21
9:21
9:21
9:21
9:21
9:21
9:21
9:22
9:22
9:22
9:22
9:22
9:22
9:23
9:23
9:23
9:23
9:23
9:24
9:24
RV7962
ON ELAN
ONELAN
ONELAN
ONE LAN
ON ELAN
ONELAN
ONELAN
ONELAN
ONELAN
ONE LAN
ONELAN
ONELAN
ONELAN
(
\
ONE LAN
ONELAN
ONELAN
ONELAN
ONELAN
ONELAN
ONELAN
ONE LAN
ONELAN
ONE LAN
Figure 9·3. Sample ONElAN Dialog, Standard Mode
(
9-30
7004 5208-000
ONUERl Program
9.6.2. Tutorial Mode Procedure
When tutorial mode is selected, ONE LAN displays a series of prompts asking you to
define the operations you want it to perform. The prompts are displayed one at a time
with each prompt requiring a response before the next one can be displayed. A
response ofN to any prompt causes the program to display the next prompt in the
sequence. A response ofY causes the appropriate graph/display to occur before
ONELAN displays the next prompt.
The order in which ONE LAN displays the prompts is as follows:
DO YOU NEED OPERATING INSTRUCTIONS? (Y OR N)
Enter a Y response if you want ONELAN to print the operating instructions on
your system printer. Enter N to terminate this request and display the next
prompt.
DO YOU WANT A LIST OF AVAILABLE GRAPHS? (Y OR N)
Enter a Y response if you want ONELAN to display, at the console, a list of all
device address for which there is a graph. Enter N to terminate this request and
display the next prompt.
DO YOU WANT ALL DEVICES GRAPHED? (Y OR N)
Enter a Y response if you want ONELAN to print individual graphs for all
devices on your system printer. Enter N to terminate this request and display the
next prompt.
DO YOU WANT SUBSYSTEM GRAPH(S) ? (Y OR N)
Enter a Y response if you want ONELAN to print graphs for one or more
subsystems.
ONELAN now displays the following message requesting you to specify the
required channel and subchannel address for each subsystem.
ENTER SUBSYSTEM ADDRESS (CS(,CS) .•• ,?)
Enter the channel and sub channel addresses of the devices you want graphed.
Multiple addresses must be separated by commas.
If you want to see a sample address, enter a question mark (?). ONELAN
displays the sample address and then redisplays the sub-system address request.
?
EXAMPLE: 10,37
ENTER SUBSYSTEM ADDRESS (CS(,CS) ••• ,?)
7004 5208-000
9-31
ONUERl Program
After you respond with the addresses, ONELAN asks you if you want device
graphs.
DO YOU WANT DEVICE(S) GRAPH(S) ? (Y OR N)
Enter a Y response if you want ONELAN to print individual graphs for specific
devices.
ONELAN now displays the following message requesting you to specify the
required channel, sub channel, and unit address for each device.
ENTER DEVICE ADDRESS (CSU(,CSU) .•. ,?)
Enter the channel, subchannel, and unit address of the device you want graphed.
Multiple addresses must be separated by commas.
If you want to see an address example, enter a question mark (?). ONELAN
displays the sample address and then redisplays the device address request.
(
?
EXAMPLE: 100,101,370
ENTER DEVICE ADDRESS (CSU(,CSU) .•• ,?)
After you enter the addresses (or if you answered N to the device graph request),
ONELAN displays the fonowing request:
TERMINATE PROGRAM ? (Y OR N)
Enter a N response of you want to print more graphs. (ONELAN redisplays the
"Enter subsystem request.)
Enter a Y response to terminate ONE LAN.
A sample ONELAN dialog in tutorial mode is shown in Figure 9-4.
RV ON ELAN
R03 RUN PROCESSOR SUCCESSFULLY PROCESSED ONE LAN
JC02 JOB ONELAN EXECUTING JOB STEP ONUERL00 #001 09:20:17
ONELAN'ERROR LOG ANALYSIS VER. 01/06
11? . DO YOU NEED HELP RUNNING THIS PROGRAM ?(Y,N)
11
Y
13? . DO YOU NEED OPERATING INSTRUCTIONS ?(Y OR N)
13 N
14? . DO YOU WANT A LIST OF AVAILABLE GRAPHS ?(Y OR N)
14 Y
15
• GRAPHS AVAILABLE: 330,370,100
16? . DO YOU WANT ALL DEVICES GRAPHED ?(Y OR N)
16 Y
17? . DO YOU WANT SUBSYSTEM GRAPH(S) ?(Y OR N)
17 Y
18? . ENTER SUBSYSTEM ADDRESS (CS(,CS) ••• ,?)
18 ?
19 EXAMPLE: 10,37
9:20
9:20
9:20
9:20
9:20
9:20
9:21
9:21
9:21
9:21
9:21
9:21
9:22
9:22
9:22
9:22
9:22
RV7962
ONELAN
ONELAN
ONELAN
ONE LAN
ONELAN
ONELAN
ON ELAN
ONELAN
ONELAN
ON ELAN
Figure 9·4. Sample ONELAN Dialog, Tutorial Mode (Part 1 of 2)
9-32
7004 5208-000
(
ONUERl Program
20?
20
21?
21
24?
24
25
26?
26
277
27
28?
28
29?
29
30?
30
31?
31
32
· ENTER SUBSYSTEM ADDRESS (CS(,CS) ••• ,?)
37,33,10
· DO YOU WANT DEVICE(S) GRAPH(S) ?(Y OR N)
Y
· ENTER DEVICE ADDRESS (CSU(,CSU) ... ,?)
?
· EXAMPLE: 100,101,370
· ENTER DEVICE ADDRESS (CSU(,CSU) ••• ,?)
100
· TERMINATE PROGRAM ?(Y OR N)
N
· DO YOU WANT SUBSYSTEM GRAPH(S) ?(Y OR N)
N
· DO YOU WANT DEVICE(S) GRAPH(S) ?(Y OR N)
Y
- ENTER DEVICE ADDRESS (CSU(,CSU) ••• ,?)
370
- TERMINATE PROGRAM ?(Y OR N)
Y
TERMINATED NORMALLY
JC02 JOB ONE LAN
09:24:47
9:22
9:22
9:23
9:23
9:23
9:23
9:23
9:23
9:23
9:23
9:24
9:24
9:24
9:24
9:24
9:24
9:24
9:24
9:24
9:24
ONELAN
ONE LAN
ONE LAN
ONELAN
ONE LAN
ONELAN
ONELAN
ONELAN
ONELAN
ONELAN
ONE LAN
Figure 9-4. Sample ONELAN Dialog, Tutorial Mode (Part 2 of 2)
ON ElAN Messages
The following console workstation or console messages may be displayed during
execution of the ONELAN program:
INVALID ENTRY
The request entered is invalid, probably due to incorrect spelling. The
'ENTER REQUEST' message will be redisplayed. Reenter the request.
TOO MANY ENTRIES. REQUEST TRUNCATED.
The request buffer cannot a.ccommodate the number of requests entered.
The leftover requests must be reentered when the accepted requests have
been honored.
(
NO RECORD AVAILABLE FOR DVC xxx.
A request was made for a graph for the specified device, but there is no
summary data for that device. The request is ignored.
$Y$ESUM nnnn error. CD$FNMC: sense data
An error was detected during accessing of$Y$ESUM, where nnnn is OPEN,
CLOSE, INPUT, or OUTPUT. Sense data is returned by the system.
ONELAN terminates.
7004 5208-000
9-33
ONUERl Program
Figures 9-5 and 9-6 show sample device error log analysis graphs for a 3561
workstation (address 312) and a 8420 diskette (address 321), respectively. The graph
on the left is the device error count for the months of November and December. The
graph on the right shows the ratio ofthe total incident count (device error count) to
the total output count (TICfrOC ratio). The exact error counts and ratios are given in
the table at the bottom of each display.
Note:
As a new month's counts become available, the graphs will expand to the right
until 5 months are shown. Thereafter, the leftmost month is truncated
automatically.
The following dialog was used to obtain the displays shown in Figures 9-5 and 9-6:
ENTER REQUEST (LST,DOC,ALL,DVC,SUB,END,?)
DVC,END
ENTER DEVICE ADDRESS (CSU(,CSU) ••• ,?)
(
312,321
A sample subsystem error log analysis for disk is provided in Figure 9-7. The device
error count and TICfrOC ratio graphs show the device addresses for all diskettes
present on the system and charts their errors for the months of November and
December, with each month appearing on a separate page. The exact totals and
TIClrOC ratios are given in the table at the bottom of each display. The third part of
the subsystem error log analysis charts the total subsystem errors by month. The
fourth part of the subsystem error log analysis summarizes the disk error totals by
function for each month.
The following dialog was used to obtain the subsystem error log analysis graphs for
disk:
ONELAN . ENTER REQUEST (LST,DOC,ALL,DVC,SUB,END,?)
SUB
ONELAN - ENTER SUBSYSTEM ADDRESS (CS,(,CS) .•• ,?)
10
When the ENTER REQUEST message reappears, you may request additional
displays or END.
9-34
70045208-000
(
ONUERl Program
ONELAN-ERROR LOG ANALYSIS. VER_ xx/xx.
SYSTEM-80 - 3561 WK-STA
DEVICE ERROR COUNT
250
yy/mm/dd hh.mm PAGE n
ADDRESS: 0312
DEVICE TIC/TOC RATIO
1.0 .
X
200
(
\
ERROR
COUNT
.1 · X
150 .
I X
1X
1X
X
100 . X
X
X
1X
1X
50 . X
1X
I X
1X
1X
.01
TIC/TOC
RATIO
.001
.0001
o. x
X
--1·_·-1··
NOV DEC
.00001
MONTH
TIC
TOC
TlC/TOC:
(
\
NOV
140
506
0.27668
I X
I X
I X
I X
· X
I X
1X
I X
1X
· X
I X
1X
1X
I X
- X
1X
1X
I X
I X
X
· X
'-1-"-1"
NOV DEC
DEC
0
3
0.
Figure 9-5. Device Error Log Analysis for 3561 Workstation
7004 5208-000
9-35
ONUERL Program
ONELAN-ERROR LOG ANALYSIS_ VER. xx/xx.
SYSTEM-80 - 8420
DEVICE ERROR COUNT
250 -
YY/Il1Il/dd hh_1l1Il PAGE n
ADDRESS: 0312
DEVICE TIC/TOC RATIO
1.0
200 -
150 I
I
COUNT
I
I
100 I
I
I
I
50 I
I
I
I
0 -
ERROR
.1
.01 I
I
RATIO
I
I
.001 I
I
I
I
.0001 I
I
I
I
.00001 -
TIC/TOC
X
X
X
X
X
X
X
X
X
X
X
X
X
X
x
X
--1----1--
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
--1----1--
NOV DEC
NOV DEC
MONTH
TIC
TOC
TIC/TOC:
NOV
150
15049
0.009967
'DEC
43
4357
0.009869
(
Figure 9·6. Device Error Log Analysis for 8420 Diskette
9-36
7004 5208-000
ONUERL Program
ONELAN-ERROR LOG ANALYSIS. VER. xx/xx.
yy/mn/dd hh.mn PAGE n
SYSTEM 80 - DISK SUB-SYSTEM.
MONTH: DEC
DEVICE TIC/TOC RATIO
DEVICE ERROR COUNT
250 1.0 I
I
I
200 -
.1
I
I
150 -
.01
ERROR
TIC/TOC
(
COUNT
x
RATIO
x
I
100 -
x
.001 -
x
x
x
50 -
.0001 -
x
x
x x
x x
I
o-
X
--I --- 1---1- -- I -- - I - --I - --1- --I105 106 107 100 101 102 103 104
(
DVC 10.
105
TIC
0
TOC
0
TIC/TOC: 0.
106
107
0
0
0.
100
0
0
0.
10
86236
0_000116
x
x
x
x
x
x
x
x
x
x
x
x
.00001 x x
x
- -1---1-- -1-- - I - --I ---I -·-1-- - 1105 106 107 100 101 102 103 104
101
26
5339
0_00487
102
103
0
0
0.
0
0
0.
0.
Figure 9·7. Disk Subsystem Error log Analysis (Part 1 of 3)
7004 5208-000
9-37
ONUERl Program
ONELAN-ERROR LOG ANALYSIS. VER. xx/xx.
yy/nm/dd hh.nm PAGE n
SYSTEM 80 - DISK SUB-SYSTEM.
DEVICE TIC/TOC RATIO
DEVICE ERROR COUNT
MONTH: NOV
250 X
1.0
X
X
X
X
X
I
X
X
I
X
X
200 -
X
I
150 -
.1 -
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
.01
X
ERROR
TIC/TOC
X
X
COUNT
X
X
RATIO
X
X
X
X
X
X
X
X
X
X
X
I
X
X
100 -
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
I
X
X
X
X
X
X
50 -
X
X
X
X
X
X
I
o-
.001 -
.0001 -
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
x
x
X
- -1--- I - --1--- 1---1 - - -I -- - 1- -- 1105 106 107 100 101 102 103 104
DVC 10.
105
TIC
0
TOC
0
TIC/TOC: 0.
106
107
0
0
0.
0
0
0.
_00001 X
X
X
X
--1---1---1---1---1---1---1---1105 106 107 100 101 102 103 104
100
105
413005
0.000254
101
3
2
0.
102
0
0
0.
103
366
103354
0.003541
Figure 9·7. Disk Subsystem Error Log Analysis {Part 2 of 3}
9-38
(
7004 5208-000
(
ONUERL Program
ONELAN-ERROR LOG ANALYSIS. VER. xx/xx.
yy/mm/dd hh.mm PAGE n
SYSTEM-80
DISK SUB-SYSTEM.
* •••• - .• _....•..• _-- •• _-*
** SUB'SYSTEM TOTALS **
* •••• _-_. __ ••••• _•••••• _*
SUB-SYSTEM ERROR COUNT
SUB-SYSTEM TIC/TOC RATIO
1250 .
1.0 -
1000 .
.1
ERROR
TIC/TOC
RATIO
(
I
750 -
.01 -
COUNT
500
.001
250 I
I
I
I
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
I X
I X X
I X X
.0001 . X X
X
X
I X X
X
I X X X
I X X X X X
I X X X X X
_00001 - X X X X X
'-1 --·1'-- 1'--1- -- I
NOV DEC JAN FEB MAR
X
X
o. x x x x x
. -I' --1"-1- -- I ---I
NOV DEC JAN FEB MAR
(
MONTH
TIC
TOC
TIC/TOC:
NOV
XX
XXX
.XXXX
DEC
XX
XXX
.XXXX
JAN
FEB
xx
xxx
xx
xxx
.XXXX
.XXXX
MAR
XX
xxx
.xxxx
Figure 9·7. Disk Subsystem Error Log Analysis (Part 3 of 3)
7004 5208-000
9-39
ONUERL Program
9.7. Sending Error Data to Unisys Support Center
ONUERL does not automatically transmit error summary data to a Unisys support
center. Instead, if error threshold has been exceeded or you've chosen the
SUMMARY=YES option, ONUERL writes the error summary data to the system
journal file. You can later transfer this information to the support center.
You must establish initial contact with the support center. Instructions for
transferring data to the support center as provided in Section 10.
(
(
(
9-40
7004 5208-000
Section 10
Error Data Handling
10.1. Contacting the Unisys Support Center
Contact the support center whenever you need software or hardware assistance from
Unisys. The support center expects to receive calls from the system administrator or
another authorized person.
It is important to call as soon as possible after you encounter a problem so that you
can save needed information by using appropriate dump procedures.
10.1.1. How to Contact the Support Center
In the continental United States, you call the following toll-free number to contact the
support center:
1-800-328-0440
International customers should contact their Unisys subsidiary.
10.1.2. What to Do before Calling the Support Center
Before calling, consult all available documentation, such as:
(
•
Programming or operating guides and reference manuals
•
System messages manual
•
Software release announcements (SRAs)
These manuals may answer your questions, or provide you with a solution to your
problem.
7004 5208-000
10-1
Handling Error Data
When you do call, be prepared to provide the following types of infonnation:
•
Your name and telephone number
•
The name of your company
•
Your software release level
•
Your SMP level and SMCs beyond your SMP level
•
SYSGEN, ICAM, and IMS generation infonnation
•
Console log data
•
Error messages
(
If you have already called the center about a software problem, give the contact
number, the date, or the name ofthe representative who handled your previous call,
as well as the results of the corrective actions previously recommended.
If your hardware problem is a checkstop or hardware-related HPR, you may be
requested to make a remote maintenance connection. Have the dataset, modem, or
acoustic coupler powered up and ready for immediate use.
(
10.1.3. When You Call
When you call the support center in the continental United States, you are prompted
for a call routing code and other preliminary routing infonnation. If you use a pushbutton telephone, enter the requested codes by pushing the appropriate buttons on the
telephone. (Calls from rotary phones are automatically intercepted by a receptionist.)
When prompted, enter the codes that identifY the model of your System 80 and
whether you need hardware or software support.
After this preliminary infonnation is entered, a receptionist will verifY your service
entitlement and then direct your call to the appropriate support center specialist.
10-2
70045208-000
(
Handling Error Data
10.2. The User Communication Form
The User Communication Form (UCF) is the Unisys form used to record the
information needed to correct a problem. UCFs are created electronically by support
center representatives.
When you call the support center with a problem that has not already been reported,
the support representative creates a UCF by using the information you provide on the
telephone. The completed UCF is routed to the OS/3 development center for analysis
and resolution.
When the UCF is created, it is assigned an authorization number. Refer to this
number whenever you call to ask about that problem or to check on the current status
ofyourUCF.
During the UCF process, you may be asked to send additional documentation
describing the suspected problem. Label any documentation you send to Unisys with:
(
•
UCF authorization number
•
Unisys customer number (assigned by Unisys)
•
Company name
•
Host system (processor)
•
Operating system
•
O.S.level
•
Materials description identifying the kind of documentation you are sending
(tape label, device type, etc.)
•
Detailed description of the documentation you are sending and any new
information that was not apparent when you reported the problem
This additional documentation should be sent to:
Unisys Corporation
OS/3 Systems Development
2476 Swedesford Road
Paoli, PA USA 19301-0203
Attention: UCF Coordinator
7004 5208-000
10-3
Handling Error Data
10.3. Sending Error Log Data
Use the following procedure to send error data to the Unisys support center.
1.
Power on modem, if not already powered on.
2.
Press the ESC and C keys to display the configuration frame.
3.
Press the E and then the XMIT keys to display the configuration select frame.
4.
Key in SCP and then press the XMIT key to enter the first part of the user ID.
5.
Key in J3280404 and press XMITkey to enter second part of the user ID.
6.
Key in UO and press XMIT key to establish modem as remote facility.
7.
Key in Zl and press XMIT key to set baud rate at 1200 bps. (ZO for 300 bps.)
8.
Press the N and then XMIT keys to turn the remote console on.
9.
Key in M1 and press Enter key to place console in master-master mode.
(
10. Press the US and TLK switches on modem (MC indicator lights).
11. Can support center personnel (1·800·328·0440).
12. Enter 1 to complete the can at the prompt.
13. Enter your 3-digit prompt (system) code 050.
14. Enter 1 for hardware or 2 for software at the prompt.
15. Support center personnel win guide you through the remote session.
(
16. Support center personnel win terminate the session.
17. After session is terminated, return the console to system mode and turn off the
modem as follows:
10-4
•
Press the ESC and C keys to display the configuration frame.
•
Press E and then the XMIT key to display the configuration select frame.
•
Enter MO and then press the XMIT key to return to system mode.
•
Press 0 and then press the XMIT key to turn the moden off.
7004 5208-000
Appendix A
Supervisor Modification Procedure
For special processing requirements, your system administrator may tell you to
modifY the selections made for the supervisor during SYSGEN. Tables A-I and A-2
list the procedures you use to modifY the supervisor. Respond with Y to the MODIFY
SUPERVISOR:: IPL statement, then proceed with the appropriate operator action
described in Table A-l.
Note:
70045208-000
For a description of system output messages and how to respond to them (via
solicited input messages), see Section 4.
A-I
Supervisor Modification Procedure
Table A-l. How to Modify list of Resident Shared Code Modules
IPl Output Message
IS THE SHARED CODE DIRECTORY INDEX
TO BE BUILT? (Y,N)
Operator Response
Y
Specifies an index is to be built for the shared
code library. The system will do a binary search
on the index rather than a serial directory search.
This allows faster loading of shared code modules
into main storage and faster processing between
two or more shared code modules. The directory
itself uses approximately 4000 bytes of main
storage.
N
No shared code directory index is to be built.
ANY RESIDENT SHARED MODULES TO ADD
OR DELETE? (Y,N)
(
N
Terminates output messages for modifying shared
code module list. Specifies no modification is
required to SYSGEN list of shared code modules
to be made resident. Proceed with operator action
described in Table Pr2.
y
Specifies SYSGEN list of shared code modules
requires modification. Output message requesting
a function is displayed.
FUNCTION? (ADD,DEL,LIST,END,HELP)
END
Terminates output messages for modifying shared
code module list. Specifies no further supervisor
modification is required. The SYSGEN list of
shared code modules is updated by the changes
previously specified with the ADD and DEL
functions. Modules in updated list are loaded and
made resident until next IPL. Proceed with
operator action descried in Table A-2.
HELP
Displays brief description of the ADD, DEL, LIST,
and END functions, followed by an output
message requesting another function.
LIST
Displays a list of the individual shared code
modules currently specified to be made resident,
followed by an output message requesting another
function.
continued
A-2
7004 5208-000
(
Supervisor Modification Procedure
Table A-i. How to Modify List of Resident Shared Code Modules (cont.)
IPl Output Message
Operator Response
ADD}
{DEL
Specifies an individual module or group of
modules is to be added to or deleted from the
current list of shared code modules. Displays the
following list of shared code module groups,
followed by an output message requesting a group
or module name.
POSSIBLE SYSTEM GROUPS ARE:
SF
- SCREEN FORMAT SERVICES
ISB - BASIC INTERACTIVE SERVICES
ISF - FULL INTERACTIVE SERVICES
EDT - EDITOR
DP - DIALOG PROCESSOR
RPG
RPG EDITOR
DDPR - REMOTE DISTRIBUTED DATA
PROCESSING
DDPL - LOCAL DISTRIBUTED DATA
PROCESSING
ESC - ESCORT
ESCF - ESCORT FULL
BAS - BASIC
WHICH GROUP TO {ADD? }
DELETE?
group-name} [,Ll
{module-name
Specifies the group of shared code modules or
the individual shared code module to be added or
deleted. Provides option to display (L) individual
module names as they are added or deleted from
the current list After processing the addition or
deletion, an output message requests another
function.
Note: Run the job stream SCLIST to get a list of
all system shared code modules filed in $Y$CLOD.
7004 5208-000
A-3
Supervisor Modification Procedure
Table A-2. How to Modify Buffer Sizes Used by Dynamic Buffer Management
IPL Output Message
Operator Response
ANY CHANGES TO DYNAMIC BUFFER
MANAGEMENT PARAMETERS? (Y,N)
N
Terminates output messages for modifying buffer
sizes. Specifies no changes are required to the
expansion region and resident buffer sizes
specified at SYSGEN. Proceed with the interactive
IPL procedure in Section 2.
Y
ENTER NEW EXPANSION REGION SIZE?
(CURRENTLY decimal-byte-size)
Specifies SYSGEN=specified expansion region and
resident buffer sizes require modification. Output
message requesting new expansion region size is
displayed.
new-size
Specifies new size", in decimal bytes, of
expansion region and terminates output messages
for modifying buffer sizes. Expansion region size
is changed until next IPL. Proceed with the
interactive IPL procedure in Section 2.
o
ENTER NEW RESIDENT BUFFER SIZE?
(CURRENTLY dec;mal-byte-size)
Specifies no expansion regions are to be allocated
until the next IPL. Dynamic buffer management
must use resident buffer pool. Output message
requesting new resident buffer size is displayed.
new-size
Specifies new size", in decimal bytes, of resident
buffer pool and terminates output messages for
modifying buffer sizes. Resident buffer size is
changed until next IPL. Proceed with the interactive
IPL procedure in Section 2.
"The new decimal size can be specified with or without a comma, or as a multiple of K. For example:
200000
200,000
200 k
A4
is 200,000 decimal bytes
is 200,000 decimal bytes
is 200 x 1024 = 204,800 decimal bytes
7004 5208-000
Index
(
A
c
Alarm beeper, console, 4-85
Application programs, 4-13
ASK command, 5-2
Assembler format, source program, (table)
7-7
Automatic volume recognition (AVR)
command, 4-61
verifying VTOC, 4-82
Automating supervisor loading, 2-14
AVR command, 4-61
AVX function code, 7-33
Cache, disk (See Disk cache facility.)
Caching, selective, 8-4
CANCEL command, 4-39
Canceling
job in progress, 4-39
without compromising MIRAM file,
4-41
Card functions
listing, (table) 7-7
listing cards, 7-10
performing, 7-6
punching cards from system console,
7-10
reproducing and resequencing source
programs, 7-7
reproducing cards containing binary
data, 7-7
reproducing cards punched in Hollerith
code, 7-7
writing cards to tape in blocked format,
7-9
Card processors, paper peripheral
controller, 1-6
Cards
punching from system console, 7-10
punching from tape, 7-19
CC function code, 7-7
CCB function code, 7-7
CCS function code, 7-7
Central processor, 1-3
CH function code, 7-10
CHANGE command, 4-35
B
Backward space
to a file, 7-22
to record, 7-22
Batch processing
LIMITS command, 4-71
remote, unsolicited messages, 6-12
BEGIN command, 4-25
Binary data cards, 7-7
Blocked format, tape, 7-9
BSF function code, 7-22
BSR function code, 7-22
Buffer pool, displaying information, 4-84
Buffer sizes
cache, 8-2
(See also Disk cache facility.)
Bulletin default setting, 5-8
Byte MUX channel, 1-7
70045208-000
Index-!
Index
Channel controller, model 8, 1-7
Character format, tape, 7-15,7-16
Circuit-switched PDN unsolicited
messages, 6-10
CJ command, 4-41
Clock
setting, 4-52
enabling/disabling display of, 4-86
CLOSE message, 5-10
CM command, 8-2
CnlMn command, 6-1
COBOL format, source program,
(table) 7-7
Commands
ASK, 5-2
AVR,4-61
BEGIN,4-25
CANCEL, 4-39
cached 110, 8-10
CHANGE, 4-33
Characteristics, 4-4
CJ, 4-41
CM, 8-2
CnlMn, 6-1
DELETE, 4-28
DI BI, 4-84
DISPLAY, 4-31,4-45
DISPLAY JS/SY, 4-61
END, 4-42
FLUSH, 4-57
FILE, 4-12
general format, 4-5
GO, 4-37
HOLD,4-23
ICAM, 6-1
interactive services, 5-1
IS, 5-8
job execution, 4-36
job initialization, 4-11
job processing, 4-10
job termination, 4-39
job scheduling, 4-22
LIMITS, 4-71
MIX, 4-46
PAUSE, 4-36
REBUILD, 4-52
RECALL, 5-7
RUNIRV, 4-14
SET AL, 4-85
Index-2
selected occasion operator, 4-44
SET CLOCK, 4-52
SETCV, 4-87
SET DATE, 4-53
SET ELOG, 4-54
SET IC, 6-2
SET 1M, 4-83
SET 10, 4-57
SET IS, 5-7
SETLX, 4-87
SETMC, 4-83
SET MEM, 4-68
SET PS, 4-86
SETSY, 4-68
SET UNCON, 4-69
SETVC, 4-86
SETVV, 4-82
SHUTDOWN, 4-70
SIISC, 4-19
STATUS, 5-3
STOP, 4-43
SU, 7-3
SWITCH, 4-38
SYSDUMP, 4-67
system-oriented, 4-45
system utility, 7-3
TELL, 5-2
TU, 7-3
TW,4-75
VV, 4-75
Communications (See Integrated
Communications Access Method.)
Communications adapter, single-line, 1-7
Compressed mode, listing cards, 7-10
Configuration, 1-1, (figures) 1-2, 1-3
Console
alarm beeper, 4-85
clock, 4-51,4-86
control selections, (table) 1-15
DCF statistics, (figure) 8-9
keyboard, (figure) 1-15
keyin procedures, 4-1
messages,ONUERL, 9-10
punching cards, 7-10
reconstructing display, 4-52
screen, 1-18
Console screen
description, 1-18
function key assignments, (table) 1-21
pull-down menus, 1-19
7004 520&000
(
(
Index
Console workstation
alarm beeper, 4-85
alternate console keyin procedure, 4-2
keyin procedure, 4-2
reconstructing display, 4-52
Control panel, 1-14,1-16
Control storage, 1-4
CP function code, 7-10
CPU retry stack log-out display ONUERL
report, (table) 9-27
CT function code, 7-8
CTR function code, 7-9
D
/
Data base management system (DMS),
4-13
Data management, 1-11
Data set label diskette functions
listing, (table) 7-2
operating instructions, 7-34
printing in deblocked format, 7-36
printing in unblocked format, 7-35
printingVTOC, 7-37
Data field, setting, 4-53
Day clock, setting, 4-52
DCF (See Disk cache facility.)
DD function code, 7-25,7-35,7-37
DDR function code, 7-27,7-37,7-38
Deblocked format
data set label diskette, 7-37
disk, 7-27
format label diskette, 7-27
tape, 7-15,7-16
DI BI command, 4-84
Diagnostic programs, 1-13
Disk cache facility (DCF)
activating drives, 8-5
cache modules, 8-8
cached I/O commands, 8-10
description, 8-1
displaying and turning off timer
statistics, 8-6
displaying statistics, 8-5
displaying statistics on a specific drive,
8-6
effect of segment size on run time, 8-13
7004 520&000
fine-tuning, 8-11
initializing, 8-2
interpreting statistics, 8-7
I/O not cached, 8-10
main storage layout, 8-8
monitoring effectiveness, 8-11
optimizing performance, 8-13
removing drives, 8-4
removing files, 8-5
removing from the system, 8-5
resegmenting existing cache buffer, 8-4
selective caching, 8-4
specifYing cache buffer size, 8-2
statistics displayed on system console,
(figure) 8-7
Disk drives
activating to DCF, 8-5
displaying DCF statistics, 8-6
removing from DCF, 8-4
Disk functions
displaying available extents, 7-33
listing, (table) 7-2
operating considerations, 7-24
operating instructions, 7-24
printing in deblocked format, 7-27
printing in unblocked format, 7-25
printing short format VTOC, 7-32
printingVTOC, 7-28
SVT information summary, (table) 7-32
Disk subsystems, error log analysis,
(figure) 9-37
Diskette controller, 1-6
Diskette functions
data set label (See Data set label
diskette functions.)
format label (See Format label diskette
functions.)
listing, (table) 7-2
Diskette subsystems
error log analysis, (figure) 9-34
integrated 8420/8422, 1-6
DISPLAY command, 4-31,4-45,4-61
Display frames, selecting, 1-10, (table) 1-1
DISPLAY JS/SY command, 4-61
Drives (See Disk drives.)
Dumps
main storage, 4-67
stopping execution, 4-42
Index·3
Index
E
ELOG file (See ONUERL program.)
END command, 4-42
ERG function code, 7-24
Error data
handling procedure, 10-1
sending to Unisys support center, 10-4
user communication form, 10-3
Error log
analysis, ONELAN program, 9-28
analysis for disk, (figure) 9-37
analysis for 3561 workstation, (figure)
9-35
analysis for 8420 diskette, (figure) 9-36
file, retaining, 2-10
report format, 9-12
setting, 4-54
(See also ONELAN program.)
Error log editor program (See ONUERL
program.)
Error processing, tape, 7-11
Error recovery option, 2-10
Exigent machine check displays, (table)
9-27
Extents, displaying disk and format label
diskette, 7-33
F
FILE command, 4-12
Files
backward space to a specific file, 7-22
error recovery, 2-10
forward space to a specific file, 7-21
removing from DCF, 8-5
FLUSH message, 4-57
Format label diskette functions
displaying available extents, 7-33
listing, (table) 7-2
operating considerations, 7-24
operating instructions, 7-24
printing in deblocked format, 7-27
printing in unblocked format, 7-25
printing short format VTOC, 7-32
printingVTOC, 7-28
SVT information summary, (table) 7-33
Index-4
Forward space
to a file, 7-21
to a record, 7-22
FSF function code, 7-21
FSR function code, 7-22
Function key assignments, (table) 1-20
Functions, system utility
card, 7-6
data set label diskette, 7-36
disk and format label diskette, 7-24
listing, 7-2
tape, 7-10
G
General registers, 1-4
Global user service task (GUST)
initializing, 6-3
running, 6-3
terminating, 6-5
GUST (See Global user service task.)
H
(
Hardware, central, 1-3
Hexadecimal format, tape, 7-15
HIGH queue, 4-10
Hit rates, DCF, 8-7
HOLD command, 4-23
Hollerith code, 7-7
ICAM (See Integrated communications
access method.)
ICP function code, 7-10
IMPL (See Initial microprogram load)
IMVJOB feature, 4-83
Index registers, 1-4
Indicator lights, model 8, 1-16
Information management system (IMS),
1-12
Initial microprogram load, 2-1,2-13
Initial program load, 2-1,2-16
7004 5208-000
Index
Initialization procedures
IMPL, 2-1,2-15
IPL, 2-4,2-16
Input messages
solicited, 4-7
unsolicited, 4-7
input/output processor (lOP), 1-6
Input/output subsystems, 1-8
Instructions system (See System
instructions.)
INT function code, 7-20
Integrated communications access method
(ICAM)
changing the symbiont name, 6-2
Cn/Mn command, 6-1
description, 1-11,6-1
GUST,6-3
loading the symbiont, 6-1
ML$$GI program operator messages,
6-3
operator commands, 6-1
operator messages, 6-6
public data network unsolicited
messages, 6-9
remote batch processing unsolicited
messages, 6-12
SET IC command, 6-2
standard unsolicited messages, 6-6
Integrated selector channel, 1-7
Integrated tape controller, 1-6
Interactive IPL, 2-16
Interactive processing, LIMITS command,
4-71
Interactive services
ASK command, 5-2
asking questions, 5-2
CLOSE message, 5-10
commands, 5-1
controlling for terminals, 5-10
description, 1-13
displaying log file, 5-7
displaying system status, 5-3
IS command, 5-8
messages, 5-10
modifying bulletinllog values, 5-8
OPEN message, 5-10
RECALL command, 5-7
releasing new user session restrictions,
5-10
7004 5208-000
REMOTE message, 5-10
REMOVE command, 5-9
restricting new user sessions, 5-10
sending messages, 5-2
SET IS command, 5-8
SHUTDOWN message, 5-11
starting, 5-8
STATUS command, 5-3
TELL command, 5-2
terminating, 5-11
terminating user tasks or sessions, 5-9
IIO devices
SET I/O command, 4-57
IOMP (See Input/output microprocessor.)
IOP (See Input/output processor.)
IIOs, unreferenced DCF, 8-7
IPL (See Initial program load.)
IS command, 5-8
J
Job control, 1-11,4-15
Job control streams
filing, 4-12
job initialization, 4-11
running, 4-14
running saved, 4-19
Job immovability (IMVJOB) feature, 4-83
Job processing commands
BEGIN,4-25
CANCEL, 4-39
CHANGE, 4-35
DELETE, 4-28
DISPLAY, 4-31
END, 4-42
FILE, 4-12
GO,4-37
HOLD, 4-23
job execution, 4-36
job initialization, 4-11
job scheduling, 4-22
job termination, 4-39
PAUSE,4-36
RUNIRV, 4-14
scheduling priority queues, 4-10
selected occasion operator commands
(See Operator commands.)
SIISC, 4-19
Index-5
Index
soft cancel, 4-41
STOP, 4-43
SWITCH, 4-38
Job queue file, 4-11
Jobs
canceling, 4-39, 4-41
changing priority, 4-35
changing switching priority, 4-38
deferring scheduled, 4-23
deleting, 4-28
displaying, 4-31
displaying status of, 4-61
executing, 4-37
keyin procedure, 4-1
initializing, 4-11
processing, 4-1
processing commands (See Job
processing commands.)
processing during daily memory refresh
routine, 4-9
reactivating suspend, 4-37
scheduling, 4-22
scheduling deferred, 4-27
scheduling priority queues, 4-10
soft canceling, 4-41
stopping dumps, 4-42
suspending, 4-36
terminating, 4-39, 4-43
K
Keyboard, console, 1-15
Keyin procedure
alternate, all models, 4-2
console, 4-1
M
Machine check, exigent, 9-27
Main storage
displaying portions of, 4-45
dumping contents of, 4-67
layout with disk cache, 8-8
resource management, 4-67
MEMCON feature, 4-83
Memory consolidation (MEMCON) feature,
4-83
Memory refresh routine, 4-9
Messages
console ONUERL, (table) 9-10
ICAM operator, 6-6
interactive services, 5-10
ML$$GI program operator, 6-3
ONELAN program, 9-28
output, 4-6
public data network, 6-9
remote batch processing, 2-12
sending to users, 5-2
solicited input, 4-7
system, discarding, 4-57
system utility, 7-3
terminating GUST, 6-5
unsolicited input, 4-7
MIX command, 4-46
ML$$GI program, 6-3
Modules, cache, 8-8
MSE display ofONUERL report, (table)
9-26
N
Language processors, 1-13
LIMITS command, 4-71
Log file
displaying, 5-7
error (See Error log file.)
Log values, modifying, 5-8
LOW queue, 4-10
Index-6
(
(
NOR (normal) queue, 4-10
L
(
o
ONELAN program
description, 9-28
disk subsystem error log analysis,
(figure) 9-37
diskette error log analysis, (figure) 9-36
7004 5208-000
Index
(
sample dialog, standard mode, (figure)
9-20
sample dialog, tutorial mode, (figure)
9-32
workstation error log analysis, (figure)
9-35
ONUERL program
console messages, (table) 9-10
CPU retry stack log-out display, (table)
9-27
description, 9-1
error log report format, (figure) 9-15
executing, 9-1
exigent machine check displays, (table)
9-27
MSE display, (table) 9-26
ONELAN program (See ONELAN
program)
options, 9-5
reports, 9-12
responding to, (figure) 9-8
SDF$DSP system program, 9-9
supervisor characteristics displayed,
(table) 9-25
supervisor ELOG flags displayed,
(table) 9-25
OPEN message, 5-10
Operator commands, selected occasion
AVR,4-61
description, 4-44
DI BI, 4-84
DISPLAY, 4-45
DISPLAY JS/SY, 4-61
FLUSH,4-57
LIMITS, 4-71
MIX, 4-46
REBUILD, 4-51
SET AL, 4-85
SET CLOCK, 4-52
SETCV, 4-87
SET DATE, 4-53
SET ELOG, 4-54
SET 1M, 4-83
SET 10, 4-57
SET LX, 4-87
SET MEM, 4-64
SETMC, 4-83
SETSY, 4-68
SET UNCON, 4-69
7004 5208-000
SETVC, 4-86
SETVV, 4-82
SHUTDOWN, 4-70
SYSDUMP, 4-67
TW,4-71
VV, 4-75
OS/3 operating system
application programs, 1-13
components, (figure) 1-9
data base management system, 1-13
diagnostic programs, 1-13
ICAM, 1-11
information management system, 1-12
interactive services, 1-13
job control, 1-11
language processors, 1-13
supervisor, 1-10
utility programs, 1-12
Output message, 4-7
p
Packet-switched PDN unsolicited messages,
6-9
Paper peripheral controller, 1-6
PAUSE command, 4-36
Physical unit blocks, setting, 4-57
PRE (preemptive) queue, 4-10
Prepping a tape, 7-20
Printers, paper peripheral controller, 1-6
Priority, job
queues (See Scheduling priority
queues.)
switching, 4-38
Processor complex, 1-3
Public data network (PDN), unsolicited
messages, 6-9
Pull-down menus, 1-19
Punching cards
from system console, 7-10
from tape, 7-19
Q
Questions
ASK command, 5-2
Index-7
Index
R
Read command, disk cache, 8-10
Read errors, DCF, 8-7
Reads, DCF, 8-7,8-8
REBUILD command, 4-52
RECALL command, 5-7
Records
backward space to specific, 7-22
forward space to specific, 7-22
locating, 7-16
tape gap, 7-24
Refresh memory routine, 4-9
Registers, system, 1-4
Remote batch processing, unsolicited
messages, 6-12
REMOTE message, 5-10
REMOVE command, 5-9
Reports, ONUERL program
CPU retry stack log-out display, (table)
9-27
error log report format, (figure) 9-14
exigent machine check displays, (table)
9-27
MSE display, (table) 9-26
supervisor characteristics, (table) 9-25
supervisor ELOG flags, (table) 9-25
Resident shared code modules, modifying,
(table) A-I
Resource management, 4-68
REW function code, 7-23
Rewind tape, 7-23
RPGformat, source programs, (table) 7-8
RUN function code, 7-22
RUNIRV command, 4-14
s
SC command, 4-19
Scheduling priority queues
changing, 4-35
deferring scheduled jobs, 4-23
deleting jobs, 4-28
description, 4-10
displaying jobs, 4-31
scheduling deferred jobs, 4-25
SDF$DSP system program, 9-9
Search commands, disk cache, 8-10
Index-B
Segments
cache buffer, 8-2
size, 8-11,8-13
Selective caching, 8-4
Selector channel, 1-8
Sessions, interactive services
releasing restrictions, 5-10
restricting new, 5-10
terminating, 5-9
SET AL command, 4-85
SET CLOCK command, 4-52
SET DATE command, 4-53
SET ELOG command, 4-54
SET Ie command, 6-2
SET 1M command, 4-83
SET 10 command, 4-57
SET IS command, 5-7
SET LX command, 4-87
SET MC command, 4-83
SET MEM command, 4-68
SET PS command, 4-86
SET SY command, 4-68
SET UNCON command, 4-69
SET VC command, 4-86
SET VV command, 4-82
Shared code modules, resident modifying,
(
A-2
SHUTDOWN command, 4-70
SHUTDOWN message, 5-11
SI command, 4-19
Simulated day clock, setting, 4-52
Single-line communications adapter
(SLCA), 1-7
SLCA (See Single-line communications
adapter.)
Soft cancel command (CJ), 4-41
Solicited input messages, 4-7
Source programs, reproducing and
resequencing, 7-7
Spool files, recovering, 2-10
Spooling
multivolume, 2-12
single volume, 2-12
Statistics, DCF
displaying, 8-5
displaying on a specific drive, 8-6
interpreting, 8-7
timer, 8-6
7004 5208-000
(
Index
Status
job, displaying, 4-61
system, displaying, 5-3
STATUS command, 5-3
STOP command, 4-43
SU command, 7-3
Supervisor
automated load procedure, 2-14
characteristics displayed on ONUERL
report, (table) 9-25
description, 1-10
ELOG flags displayed in ONUERL
report, (table) 9-25
initializing, 2-6
modification procedures, A-1
modifYing resident shared code modules,
(table) A-2
Suspended job, reactivating, 4-37
Suspending a job in progress (PAUSE),
4-36
SVT function code, 7-32
SWITCH command, 4-38
Switches, model 8, 1-18
Switching priority, changing, 4-38
Symbionts, LIMITS command, 4-71
SYSDUMP command, 4-67
System activity, terminating, 4-70
System configuration
maximum, (figure) 1-2
minimum, (figure) 1-1
System console (See Console.)
System control processor, 1-5
System definition file, 9-9
System information, displaying, 4-45
System instructions, 1-4
System messages, discarding, 4-57
System-oriented commands (See Operator
commands, selected occasion.)
System registers, 1-4
System status, displaying, 5-3
System utility services
card functions, 7-6
commands and messages, 7-3
data label diskette functions, 7-34
disk and format label diskette functions,
7-24
functions, (table) 7-2
tape functions, 7-11
7004 52Q8..()00
System 80
central hardware, 1-3
channel controller, 1-7
console, 1-14
console keyboard, (figure) 1-15
control panel, 1-16, (figure) 1-16
control storage, 1-4
disk cache performance, 8-13
IMPL, 2-5, 2-16
initialization procedures, 2-5,2-16
input/output microprocessor, 1-5
input/output processor, 1-5
input/output subsystems, 1-8
IPL, 2-5,2-16
keyin procedures, 4-1
main storage, 1-4
maximum system configuration, (figure)
1-1
memory refresh routine, 4-9
minimum system configuration, (figure)
1-1
power off procedure, 3-1
power on procedure, 2-3
switches, 1-16
system configuration, 1-1
system control processor, 1-5
system definition, 1-1
system instructions, 1-4
system registers, 1-4
tum-off procedure, 3-1
tum-on procedure, 2-2
T
Tape
marks, 7-23
record gap, 7-24
writing cards in blocked format, 7-9
writing cards in unblocked format, 7-8
Tape controller, 1-7
Tape functions
backward space to a specific file, 7-22
backward space to a specific record,
7-22
copying a tape to another tape, 7-13
erasing tape record gap, 7-24
error processing, 7-11
Index-9
Index
forward space to a specific file, 7-21
forward space to a specific record, 7-22
listing, (table) 7-2
locating a specific record, 7-17
performing, 7-12
prepping a tape, 7-20
printing a tape containing only standard
characters, 7-16
printing a tape in character and
deblocked format, 7-16
printing a tape in character or
hexadecimal format, 7-15
rewind and unload tape, 7-23
rewind tape, 7-23
tape addressing, 7-11
writing tape marks, 7-23
Tasks, terminating, 5-9
TC function code, 7-19
TELL command, 5-2
Terminals, controlling interactive services,
5-10
Terminating
end-of-job dump, 4-43
jobs, 4-39,4-41,4-43
tasks, 5-9
TH function code, 7-15
THR function code, 7-16
Timer statistics, DCF, 8-6
TP function code, 7-16
TPR function code, 7-16
Transient work area feature, 4-71
TRS function code, 7-17
TT function code, 7-13
TU command, 7-3
Tum-off procedure, 3-1,
Tum-on procedures, 2-2
TW command, 4-71
u
Unload tape, 7-23
Unreferenced IIOs, DCF, 8-8
Unsolicited messages
ICAM standard, 6-6
input, 4-7
public data network, 6-9
remote batch processing, 6-12
User Communication Form (UCF),
submitting, 4-82,10-1
Utility programs, 1-11
Utility services (See System utility
services.)
v
(
Volume serial number, reading, 4-61
Volume table of contents maC)
printing data set label diskette, 7-37
printing disk or format label diskette,
7-28
printing short format disk or format
label diskette, 7-32
verifying during AVR, 4-82
verifying and correcting, 4-75
VTP function code, 7-28
VV command, 4-75
w
Workstation controller, 1-6
Workstations
alternate console, 4-2
console (See Console workstation.)
error log analysis, 9-33
Write command, disk cache, 8-10
Write-throughs, DCF, 8-7
WTM function code, 7-23
Unattended console feature, setting, 4-69
Unblocked format
data set label diskette, 7-35
disk, 7-25
format label diskette, 7-24
tape, 7-8
Index-IO
7004 5208-000
(
r---------------------------------------------i
User Reply Form
,
Help Us To Help You
,
Document Title
Document Number
Date
We are interested in your comments and suggestions regarding Ihis document. We will use them to improve the quality
of this product information. Please check Ihe type 01 suggestion.
o Addition
0
Deletion
o Revision
o General Comment
Recommended Change IPlease idenfify each aJlecled item, such as page, paragraph, figure. or tabteJ
,,I
,,
,
,
,
,
,I
,
I
,,I
,,,
,
I
(
,
Name
Telephone Number
Title
Company
,I,
,
I
:
Address (Street. City. State. ZIP)
~---------------------------------------------~
:
,
Help Us To Help You
I
,
Document Title
,
Document Number
User Reply Form
:
,
,,
Date,
,
I
,
,
We are interested in your comments and suggestions regarding this document. We will use them to improve the Quality
of this product information. Please check the type of suggestion.
I
,
,,)
,,
0
Recommended Change (Please identify each aJlected item, sucli as page, paragraph. figure, or table.)
,,
,
,
Addition
0
Deletion
0
Revision
General Comment
,
,
I
I
I
I
I
,
,
I
I
,
I
I
I
0
I
I
I
I
I
I
I
I
I
I
I
Name
Telephone Number
Title
Company
Address IStreet, City, State. ZIP'
I
I
I
I
,
----------------------------------------------~
r---------------------------------------------iI
I
:
NO POST AGE
NECESSARY
IF MAILED IN THE
UNITED STATES
I
:
I
:
BUSINESS REPLY MAIL
I
I
FIRST CLASS MAIL
I
POST AGE WILL BE PAID BY ADDRESSEE
:
Unisys Corporation
SPG East Coast
Systems Documentation Development
Tredyffrin Plant
2476 Swedesford Road
PO BOX 203
PAOLI, PA 19301-9898
I
I
I
I
I
:
I
I
I
I
I
:
PERMIT NO. 72
:
I
I
:
1
PAOLI. PA
I
I
I
I
I
:
'I
I
I
:
I
I
I
I
I
1'11111.1111111.11 .. 1111111.1 III III. I.1111 111 111 1.11
:
I
I
r----------..;·------------lrrfl---------;~~;---l
:
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
IF MAILED IN THE
UNITED STATES
I
BUSINESS REPLY MAIL
FIRST CLASS MAil
PERMIT NO. 72
PAOLI. PA
POSTAGE WILL BE PAID BY ADDRESSEE
Unisys Corporation
SPG East Coast
Systems· Documentation Development
Tredyffrin Plant
2476 Swedesford Road
PO BOX 203
PAOLI, PA 19301-9898
1".11 J.1111111.11111111111.1111111.1.11111111111.11
I _____________________________________________
L
I
~
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.3 Linearized : No XMP Toolkit : Adobe XMP Core 4.2.1-c043 52.372728, 2009/01/18-15:56:37 Format : application/pdf Creator : HyperGEAR TIFF/PDF Convert Library Create Date : 2005:02:11 15:09:51Z Creator Tool : HyperGEAR,inc. Modify Date : 2009:10:01 22:25:50-07:00 Metadata Date : 2009:10:01 22:25:50-07:00 Producer : Adobe Acrobat 9.13 Paper Capture Plug-in Document ID : uuid:618500a1-c5b5-495e-a846-1cc97afefbfd Instance ID : uuid:9480ef80-d07e-4017-90b0-d6323b585889 Page Count : 292 Author : HyperGEAR TIFF/PDF Convert LibraryEXIF Metadata provided by EXIF.tools