UNISYS System 80
Models 8-20
OS/3
Installation
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 5505-000
NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product and related material
disclosed herein are only furnished pursuant and subject to the terms and conditions of a duly executed Program
Product License or Agreement to purchase or lease equipment. The only warranties made by Unisys, if any, with
respect to the products described in this document are set 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 complies with the
laws, rules, and regulations of the jurisdictions with respect to which it is used.
The information contained herein is subject to change without notice. Revisions may be issued to advise of such
changes and/or additions.
Correspondence regarding this publication should be forwarded to Unisys Corporation either by using the User
Reply Form at the back 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,
19301-0203, U.SA
umsys Product Information
Announcement
o New Release • Revision o Update o New Mail Code
Title
System 80 Models 8-20 OS/3 Installation Guide
This announces the release of a revision to this document, which was previously released as UP-8839.
This guide contains the information and procedures necessary to install, generate, and maintain OS/3 software on the
System 80 models 8 through 20.
This revision documents a number of enhancements to the OS/3 software applicable to Release 14. These include:
Deletion of documentation on the System 80 Models 3-6
Change to the CONALARM SUPGEN parameter to permit a single audible alarm
Setting of the SPOOLCYL SUPGEN parameter to 25 for the basic starter supervisors
Change to the PRINTER l/OGEN parameter to increase the maximum number of allowable virtual printers to 999
Change to the SYSLOG SUPGEN parameter to add three new options
Change to the SPOOLMAXLINE SUPGEN parameter to permit an unlimited number of records to be entered
into the spool file
New SUPGEN parameter, SPOOLMAXREC, to allow the spooling of records up to 224 bytes
The new RELOAD parameter on the SG$PRB job control stream.
An enhancement to the DCOP job control stream that allows copies between different disk devices
with similar operating characteristics.
This revision also includes a number of minor technical and editorial corrections.
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: System: System 80
MBOO, SAB, and SAE MB01 and ECC3 Release: 14
Date: November 1991
Part Number: 7004 5505-000
Part/Section
Page Update
Number Level
Cover
Title Page/Disclaimer
PSS
iii
About This Guide v thru xii
Contents
xi l i thru xix
1 thru 11
1 thru 35
1 thru 52
1 thru 71
1 thru 38
Appendix
1 thru 4
Index
1 thru 10
User Reply Form
Back Cover
PAGE STATUS SUMMARY
ISSUE: 7004 5505-000
Part/Section
Page
Number
Update
Level
Part/Section
Page
Number
Update
Level
Unisys uses an 11-digit document numbering system. The suffix of the document number (1234 5678-xyz) indicates the document level. The first digit of the suffix (x)
designates a revision level; the second digit (y) designates an update level. For example, the first release of a document has a suffix of -000. A suffix of -130 designates the
third update to revision 1. The third digit (z) is used to indicate an errata for a particular level and is not reflected in the page status summary.
7004 5505-000
About This Guide
Purpose
This guide specifically describes the system installation procedures for the Unisys
System 80 models 8 through 20. It is assumed that the system hardware is installed
and that your system is ready for software installation.
Audience
The intended audience of this guide is the site administrator who is to install the
current release of OS/3 software.
Prerequisites
Before beginning the installation task, read the documentation that accompanies your
software release to familiarize yourself with the most current information pertaining
to installation, restrictions s and guidelines. You should also familiarize yourself with
the other documents referred to in this guide. They are listed under the heading
"Related Product Information" in this section.
How to Use This Guide
This installation guide tells you how to install and generate OS/3 software on the
System 80 models 8 through 20. You should follow the procedures that configure a
system that matches the system configuration at your site. This document also has a
number of reference sections that provide detailed information required to complete
specific system installation steps.
To verify that you performed the installation procedures correctly, see the Installation
Verification Procedures (TVP) Operating Guide, 7004 5232.
7004 5505-000
About This Guide
Organization
This manual presents system installation information as follows:
Section 1. Introduction
Defines system installation and discusses all the installation facilities that Unisys
provides to simplify the process.
Section 2. Software Installation
Describes software installation considerations and gives specific procedures for
installing the software that Unisys delivers to you.
Section 3. System Generation
Describes system generation considerations and gives specific procedures for tailoring
the operating system to meet your particular needs.
Section 4. Using an Alternate Method to the SYSGEN Dialog
Provides information on how to prepare system generation parameters by using
alternate methods. Includes statement conventions, keyword parameters, and
reference tables.
Section 5. System Maintenance
Describes system maintenance considerations and gives specific procedures on how to
install system maintenance packages.
Appendix. Performance Tuning
Provides SUPGEN parameters and additional information that can be used to obtain
optimum system performance for most system applications.
Results
After reading this guide and following the procedures in it, the site administrator will
have successfully installed the current release of OS/3 system control software.
7004 5505-000
About This Guide
Notation Conwentions
The conventions used to define the configuration parameter values in this guide are:
• Parameter definition is by keyword association. Keyword parameters consist of a
word or a code immediately followed by an equal sign, which is followed by a
specification. Keyword parameters can be written in any order except where
restrictions are noted. Keyword parameters can be written in columns 1 through
71. More than one keyword parameter can be included on the same statement,
but they must be separated by at least one blank character. Keywords and their
specifications must be contained on the same statement.
Example
PRIORITY^
PRIORITY=5 J0BSL0TS=3 TRANS=3
PRIORITY^ TRANS=3 J0BSL0TS=3
Special rules for coding ICAM network definition keywords and macro
instructions are described in 4.1.3.
• Capital letters, commas, equal signs, and parentheses must be coded exactly as
shown. The exceptions are acronyms, which are part of the generic terms
representing information to be supplied by the programmer.
Example
SUPHOD=supvrnam
COMM=4
CACH=Cnn, network-name, I ine- number)
• Lowercase letters and words are generic terms representing information that
must be supplied by the user. Such lowercase terms can contain hyphens and
acronyms (for readability).
Example
channel
supervisor -name
vsn
• Information contained within braces represents alternate choices. Code only one
of the choices.
Example
max '
NIN
HO
MORM
7004 5505-000 vii
About This Guide
Information contained within brackets represents optional entries that
(depending upon program requirements) are included or omitted. Braces within
brackets signify that one of the specified entries must be chosen if that parameter
is to be included.
Example
[SUPMOD-supvrnam]
SUPVRNAM= [supervisor -name]
|SY$STD J
An optional parameter that has a list of alternate entries can have a default
specification that is supplied by the operating system when the parameter is not
specified by the user. The default can be specified by the user, but it is considered
inefficient. Default specifications shown in the format are printed on a shaded
background.
Example
SUPWHAM- (supervisor -name]
|SY$STD J
Keyword parameters can contain sublists called subparameters. Subparameters
can be positional or nonpositional, as indicated in the text. Subparameters must
be separated by commas.
- Positional subparameters must be coded in the order shown, and commas
must be retained for any that are omitted, with the exception of trailing
commas.
Example
SPOOLHODE=ACCT UO, account number value
- Nonpositional subparameters can be coded in any order, on a single
statement, separated by commas. If all subparameters do not fit on one
parameter statement, that statement can exceed one line, provided you
repeat the keyword parameter and its equal sign for each additional line
that you need. Remember that this rule does not apply to parameters that fit
on one line; in those instances, every keyword parameter and its
specifications must be on one line.
Example
RESHARE=BAS,DDLP,DDPR,DP„EDT,ESC,ESCF,ISB f ISF,RPG,SF
viii 7004 5505-000
About This Guide
If all but one subparameters in this example fit on one statement, code the
keyword parameter as follows:
RESHARE=8AS f DDLP,DDPR # DP,EDT f ESC,ESCF f ISB,ISF
RESHARE=SF
• The label entry must begin in column 1.
Example
1 1® 16 72
SUPGEN
END
• Use the Assembler Coding Form 5 UD1 -1 548, to code the SYSGEN keyword
parameters. The LABEL, OPERATION, and OPERAND field limits are shown.
• Keyword parameters must not appear on the following label statements:
SURGED
I/OGEM
COMMCT
MTRGE^f
COBGEN
END
7004 5505-000
About This Guide
Related Product Information
The following Unisys documents may be helpful In understanding and Implementing
the information presented in this guide.
Note: Use the version that applies to the software level in use at your site.
System Messages Reference Manual (7004 5190)
Describes system messages, message response, and remedial actions, when applicable.
Job Control Programming Guide (7004 4623)
Describes the OS/3 job control language used to manage system resources, prepare
programs for execution, and start program execution.
Consolidated Data Management Programming Guide (UP-9978)
Describes the organization, type, and format of the data files under OS/3. Also
describes the manner in which data management handles the movement of data
between programs and peripherals.
Models 8-20 Operations Guide (7004 5208)
Provides the information needed to operate System 80 models 8-20 within the OS/3
environment.
Integrated Communications Access Method (ICAM) Operations Guide
(7004 4557)
Describes how to define an ICAM network on models 8-20, submit it to the systems
generation procedure, and load and operate the resulting ICAM symbiont. Sample
network definitions are included.
Integrated Communications Access Method (ICAM) Utilities Programming
Guide (7004 4565)
Describes the utilities provided by ICAM. Where applicable, these descriptions
include necessary ICAM network definition examples.
1974 American Standard COBOL Programming Reference Manual (7004 4490)
Describes 1974 ANS COBOL for the applications programmer.
1985 American Standard COBOL Programming Reference Manual (7002 3940)
Describes 1985 ANS COBOL for the applications programmer.
7004 5505-000
About This Guide
System Activity Monitor Programming Guide (UP-9983)
Describes the use of the system activity monitor for evaluating system performance.
Spooling and Job Accounting Operating Guide (7004 458D
Describes spooling concepts and functions.
System Service Programs (SSP) Operating Guide (UP-8841)
Describes the use of system service utility programs that support the operation of the
OS/3 operating system.
Data Utilities Operating Guide (7004 4516}
Describes how to use the data utilities for reproducing and maintaining data files on
various media.
Installation Verification Procedures (WP) Operating Guide (7004 5232)
Describes the procedures and information needed to verify that OS/3 software
products are properly installed and ready for use.
Information Management System (IMS) System Support Functions
Programming Guide (UP-11907)
Describes how to configure and generate IMS.
NTR Utility Programming Guide CUP-9502)
Describes the NTR utility ,which permits a System 80 system to operate as a remote
job entry/batch terminal to a Series 1100 system via ICAM.
Interactive Services Operating Guide (UP-9972)
Describes the procedures for communicating with the operating system interactively
through local workstations or remote terminals.
General Editor (EDT) Operating Guide (7004 4599)
Describes the commands and procedures needed to use the general editor.
Supervisor Technical Overview (UP-8831)
Provides an overview of the OS/3 supervisor and its functions.
7004 5505-000
About This Guide
System 80 Models 8/10/15/20 Processor Complex Controllers Programming
Reference Manual Volume 1: Controllers of the Selector Channel and Byte
Multiplexer (UP-9607)
Provides hardware design, operations, and programming information to assist in
programming peripheral subsystems integrated with System 80 models 8, 10, 15,
and 20.
System 80 Models 8/10/15/20 Processor Complex Controllers Programming
Reference Manual Volume 2: Controllers and Communications Channels of
the I/O Processor (UP-9732)
Provides hardware design, operations, and programming information to assist in
programming peripheral devices and communications attachments integrated with
System 80 models 8, 10, 15, and 20.
System 80 Models 8/10/15/20 Processor and Central Peripherals Operating
Guide (UP-9608)
Provides operating information for models 8, 10, 15, and 20 processor and peripheral
equipment required for minimum system configurations.
System 80 Models 8/10/15/20 Processor Programming Reference Manual
(UP-9692)
Describes the operating characteristics of the models 8, 10, 15, and 20. Also provides
the commands, formats, and other data needed to operate the system.
y» 7004 550>000
Contents
About This Guide
Section 1. Introduction
1.1. What is System Installation? 1-1
1.2. What Does Software Installation Involve? 1-2
1.3. What Does System Generation Involve? 1-2
1.4. What Does System Maintenance involve? 1-3
1.5. Delivery of OS/3 Software 1-3
1.5.1. Software Delivered on Diskettes 14
1.5.2. Software Delivered on Dump/Restore Tape 1-5
1.6. How to Install OS/3 Software 1-5
1.6.1. Stand-Aione installation Facilities 1-5
1.6.2. Optional Software Installation Facilities 1-6
1.6.3. Tape Software Installation Facilities Using an
Existing SYSRES 1-6
1.6.4. System Maintenance Installation Facilities 1-6
1.7. How t© Perform System Generation 1-6
1.7.1. SYSGEN Dialog 1-7
1.7.2. SYSGEN Parameter Processor 1-9
1.7.3. SYSGEN Job Control Streams 1-9
1.8. System Installation Review 1-10
Section 2. Software Installation
2.1. Considerations 2-1
2.1.1. Initial Users 2-1
2.1.2. Existing Users 2-2
Installing New Optional OS/3 Software 2-2
Installing a New Release of OS/3 2-3
2.1.3. SYSRES Build Guidelines 24
2.2. Installation Procedures ../...... 2-6
2.2.1. Installing Standard Release OS/3 Software from Diskettes or
Tapes Using Stand-Alone Routines 2-6
Stand-alone Routines Considerations 2-11
Restarting SU@RST 2-11
2.2.2. Installing Optional Program Product Software from Diskettes 2-12
2.2.3. Installing Standard Release OS/3 Software from Tapes Using
Online Dump/Restore Routines 2-13
Using PRPMIC 2-15
Sample Disk Prep 2-16
7004 5505-000 xiii
Contents
2.3. Post-Software Installation Procedures 2-17
2.3.1. Updating the System Definition File (SDR 2-17
Determining What to Update by Reviewing
$Y$MIC and $Y$$DF 2-21
Adding a Device to $Y$SDF 2-23
Deleting a Device from $Y$SDF 2-26
Updating Existing Device information in $Y$SDF 2-26
Confirming $Y$SDF 2-28
Dumping $Y$SDF 2-28
Restoring $Y$SDF 2-29
Terminating SDU 2-29
Performing IMPL and IPL Procedures 2-30
2.3.2. Copying and Restoring $Y$SDF 2-32
2.3.3. Creating an IMPL System Microcode Diskette 2-33
2.3.4. Creating an IDCU Microcode Diskette 2-34
2.3.5. Restoring Modules Saved from a Previous Release 2-34
2.3.6. Verifying System Installation 2-35
2.3.7. Performing System Generation 2-35
Section 3- System Generation
3.1. Considerations.................................................. 3-1
3.1.1. Supervisor Elements 34
Supplied Starter Supervisors 3-5
User-Generated Supervisors 3-5
Supervisor Maintenance Considerations 3-8
3.1.2. Nine-Thousand-Remote (NTR) Element 3&
3.1.3. COBOL Element 3-9
3.1.4. Communications (ICAM) Elements 3-9
3.1.5. Resource Management 3-10
Resource Management Batch System Configuration 3-11
Resource Management Interactive System Configuration .................... 3-12
Resource Management Mixed System Configuration 3-13
3.2. Procedures 3-14
3.2.1. Using SYSGEN Dialog to Prepare Parameter Sets 3-14
3.2.2. Processing the SYSGEN Parameter Sets 3-19
Automatic Execution of the Parameter Processor 3-20
Manual Execution of the Parameter Processor 3-26
3.2.3. Running the SYSGEN Job Control Streams 3-29
Supervisor SYSGEN Job Control Stream ........................................... 3-29
ICAM Job Control Stream 3-29
NTR Job Control Stream 3-31
COBOL Job Control Stream 3-31
3.3. Post-SYSGEN Procedures ......................................................................... 3-32
3.3.1. Updating the System Definition File 3-32
3.3.2. Configuring Automatic Supervisor Loading 3-32
3.3.3. Generating an IMS Online Load Module 3-32
3.3.4. Defining Alternate Printer Characteristics 3-32
3.3.5. Changing the Interactive Services Logo 3-38
xiv 7004 5505-000
Contents
3.3.6. Changing the System Bulletin 3-38
3.3.7. Verifying System installation 3-39
3.3.8. Making and Restoring a Backup Copy of Your
Current SYSRES 3-39
Using a Fixed Disk for Your Backup SYSRES (DCOP) 340
Using a Removable Disk for Your Backup SYSRES (SETREL/COPYREL) 342
Using Diskettes for Your Backup SYSRES 347
Using Tape for Your Backup SYSRES 3-51
Restoring SYSRES from Tape Using SU@RST 3-52
Section 4. Using an Alternate Method to the SYSGEN Dialog
4.1. Creating Parameter Sets 4-1
4.1.1. SUPGEN 4-2
4.1.2. I/OGEN 4-2
4.1.3. COMMCT 4-3
4.1.4. NTRGEN 45
4.1.5. COBGEN. 4-5
4.2. SYSGEN Keyword Parameters 4-5
4.3. Additional SYSGEN Parameter Information 4-62
4.3.1. Spool-File Bit Map Calculation Table 462
4.3.2. Shared Load Module Groups 4-63
4.3.3. Logical Unit Numbers (l/OGEN DVCNO Parameter for
All Devices) 4-64
4.3.4. Nine-Track Recording Mode Settings (l/OGEN
MODE Parameter) 4-66
4.3.5. Seven-Track Recording Mode Settings (i/OGEN MODE
Parameter) 4-66
4.3.6. Line Speed Values 4-68
4.3.7. Space Compression Characters 4-69
4.3.8. Device Function Codes 4-70
4.3.9. I/O Guidelines - Co-Channel Support 4-70
Section 5. System IVlaiotenariee
5.1. System Maintenance Packages 5-1
5.2. Installation of SMPs 5-2
5.2.1. Initiating the SMC Program 5-3
5.2.2. installing an SMP 5-7
5.2.3. Performing Additional Regenerations 5-11
5.2.4. Erasing SMP Files 5-12
5.3. Installation of Individual SMCs 5-12
5.4. Running the SMC Installation Program 5-13
5.4.1. Building Your SMC from the Console 5-16
5.4.2. Building Your SMC from a Workstation 5-19
5.4.3. Installing the SMC 5-23
5.5. Sample SMC Printouts 5-28
7004 5505-000 xv
Contents
Appendix. Perf ormance Tuning
A.l. SUPGEN Priority Values A-l
A.2. SUPGEN Memory Management Values A-2
A3. SUPGEN Data Management Values A-2
A.4. SUPGEN Spooling Values A-2
A.5. SUPGEN Resident Shared Load Module Values A-2
A.6. I/OGEN Considerations ...................................................'........................... A-3
A.7. Determining Disk Cache Size A-3
Index
User Reply Form
xvi 7004 5505-000
Figures
1-1. System Installation Process 1-11
2-1. Software Installation from Diskettes for an Initial User 2-2
2-2. Software Installation from Tapes for an Initial User 2-2
2-3. Installation of New Optional OS/3 Software 2-3
24. Installation of a New OS/3 Release 2-5
2-5. System DateAime Display 2-11
2-6. Updating $Y$SDF 2-20
2-7. SDU Operation Request Screen 2-22
2-8. SDU Display Operation Screen 2-22
2-9. Sample $Y$SDF Printer Output 2-23
2-10. SDU Add Screen for Non-IMPL Devices 2-24
2-11. SDU Add Screen for IMPL Devices 2-24
2-12. SDU Delete Operation Menu 2-26
2-13. SDU Update Operation Menu 2-27
2-14. SDU Dump Operation Menu 2-28
2-15. SDU Restore Operation Menu 2-29
2-16. SDU Termination Screen 2-29
2-17. System Operations Menu 2-30
2-18. System Date/Time Display 2-30
5-1. Processing Options Menu Screen 5-6
5-2. Supervisor Regeneration Screen 5-8
5-3. ICAM Regeneration Screen 5-9
54. Installation of Individual SMCs 5-12
5-5. SMC Instruction Screen 5-19
5-6. First SMC Entry Screen 5-20
5-7. Second SMC Entry Screen 5-20
5-8. Editing Commands HELP Screen 5-21
5-9. SMC Special Processing Screen 5-26
5-10. Sample SMC - Required Fields for SMC Console Dialog 5-29
5-11. Sample SMC - Required Fields for Interactive SMC Entry from Workstation 5-30
7004 55054)00 xvii
Tables
3-1. Control Element Generations for Optional Software 3-2
3-2. SY#BAS (Model 8) 3-6
3-3. SY$BAS (Models 10 through 20) 3-7
34. Resource Management Elements for a Batch-Oriented System 3-11
3-5. Resource Management Elements for an Interactive System 3-12
3-6. COPYREL Copy Order 346
4-1. SUPGEN Keyword Parameters 4-6
4-2. I/OGEN Keyword Parameters 4-34
4-3. COMMCT Keyword Parameters 449
44. NTRGEN Keyword Parameters 4-55
4-5. COBGEN Keyword Parameters 4-59
4-6. Spool-File Bit Map Calculations 463
4-7. Shared Load Module Groups 463
46. Logical Unit Numbers 4-64
4-9. Nine-Track Recording Mode Settings 466
4-10. Seven-Track Recording Mode Settings 4-67
4-11. Line Speed Values 4-68
4-12. Space Compression Characters 4-69
4-13. Device Function Codes 4-71
7004 55054300 xix
Section 1
Introduction
1.1. What Is System Installation?
System installation is the process of installing the Unisys System 80 hardware,
integrating the Operating System/3 (OS/3) software into it, and tailoring this software
to fit your specific needs. The process of tailoring operating system software is called
system generation.
SYSTEM
INSTALLATION
SYSTEM 80
HARDWARE
INSTALLATION
OS/3
SOFTWARE
INSTALLATION
OS/3
SYSTEM
GENERATION
This guide discusses the system installation tasks that concern you after the hardware
is installed - those of installing and generating the OS/3 software. It also describes the
installation of system maintenance packages (SMPs), which contain OS/3 software
changes that maintain the software's effectiveness.
7004 5505-000
14
Introduction
1.2. What Does Software Installation inwolwe?
Software installation involves the transfer of all OS/3 software from the delivered
release media to the disk that serves as the system resident volume, or SYSRES. This
includes both the standard OS/3 software that all users need to operate their system
and the separately priced program products and programming aids (optional software)
you order to complement the standard OS/3 system software.
The SYSRES contains all the OS/3 system software, and it must be online whenever
you operate the OS/3 system.
Use software installation procedures in this guide to install:
• Initial releases of OS/3 software
• Any new software that you receive between major releases
• Updated software as Unisys releases major improvements to OS/3
Once the software is installed on the SYSRES, you are ready for system generation.
Install all delivered release software before you generate the system.
1.3- What Does System Generation Inwolwe?
System generation, or SYSGEN, is the process whereby you define the system's
hardware configuration to OS/3 and generate, or create, the control elements that you
need to satisfy your particular processing requirements. Using SYSGEN facilities, you
can configure:
• Customized supervisors and their associated input/output (I/O) device
configurations
• Nine-thousand-remote (NTR) system utilities
• Processing options for the ANSI 74 or '85 COBOL compiler
• Communications networks (ICAM)
You don't need to perform system generation to begin normal system operations
immediately. The OS/3 system contains its own ready-to-use starter supervisor, called
SY#BAS for model 8 and SY$BAS for models 10 through 20. This starter supervisor
lets you load the operating system and generate a customized supervisor and its
associated I/O device configuration. See 3.1.1 for instances when system generation is
required.
1-2 7004 5505-000
introduction
As you gain experience with the system and your site operations, you can add features
to satisfy special processing requirements that the starter supervisor does not include,
or you can delete features that you can do without. In either case, you can perform
system generation to customize the system to meet your particular processing
requirements.
1.4. What Does System Maintenance Inwolwe?
System maintenance involves the installation of system maintenance packages
(SMPs) to your SYSRES. SMPs contain a collection of software changes that maintain
your system's operation and effectiveness. System maintenance changes (SMCs) are
the individual changes within the package.
Installation routines are used to install SMPs. They are easy to run and protect the
system's integrity during SMP application. For example, the routines automatically
regenerate the supervisor if it must be regenerated to operate properly. The routines
also copy all original modules affected by the SMP. If the SMP adversely affects
system operation, you can restore the system to its original operating configuration.
1.5. Delivery of OS/3 Software
OS/3 software is available on diskette and tape. This software must be copied to disk
before it can be loaded.
Choose the media type that is compatible with your system configuration, subject to
the following guidelines on OS/3 software delivery:
• Initial users receive standard software on tape or diskette.
• Optional software ordered between major releases is shipped on diskette only.
• System maintenance packages (SMPs) are always delivered on diskette
accompanied by an SMP document.
OS/3 standard software ordered on tape or diskette is delivered in dump/restore file or
volume format, depending on the disk and system type. Dump/restore dumps or
restores only to like device types; therefore it is necessary to order the tape or diskette
media that correspond to your disk configuration. File mode media can be used by
stand-alone restore and dump/restore to install a new OS/3 release. File and volume
mode installations are discussed later in this section.
Note: For model 8 customers only, software is available on an M9720 disk only as
an optional program product (S809720-DSK).
7004 5505-000 1-3
Introduction
Media Type
Format
Data set label
8417
File mode
diskette
8478
File mode
8494
File mode
H9720
File mode
Tape
8430
Volume mode
8433
Volume mode
8419
Volume mode
8417
File mode
8470
File mode
8494
File mode
M9728
File mode
1.5.1. Software Deliwered on Diskettes
Unisys delivers two sets of release diskettes: one set contains standard OS/3 software,
and the other contains the optional OS/3 software that meets your specific processing
needs.
The standard release diskettes contain four types of software:
1 . Initial microprogram load (IMPL) code
2. Integrated disk control unit (IDCU) microcode
3. Initial program load (IPL) code plus stand-alone products
4. System control software on sequential diskettes
Standard OS/3 Release Software
r
— >
C)
n
IMPL
()
CODE
IDCU
()
MICROCODE
IPL CODE &
STAMD-ALOME
<)
PRODUCTS
n
SYSTEH
CONTROL
()
SOFTWARE
n
1-4
7004 5505-000
Introduction
Unisys delivers optional software on separate release diskettes, one set for each
component. These components can include program products, such as language
compilers, or programming aids, such as conversion products.
1.5.2. Software Deliwered on Dump/Restore Tape
OS/3 release software is also available on dump/restore tapes in a format compatible
with your disks. Tape releases contain only the standard OS/3 software; optional
software is delivered on separate release diskettes upon request.
No existing SYSRES disk is required if the tape is loaded to a nonremovable disk
using stand-alone restore.
1.6. How to Install OS/3 Software
Unisys provides facilities that simplify OS/3 software installation. Each set of release
media includes all the software needed to install the release software on your system.
The following subsections describe these software facilities.
1.6.1. Stand-Alone Installation Facilities
To install an initial or updated OS/3 release from diskettes or tapes, Unisys includes
two installation routines as part of the standard OS/3 release: a stand-alone disk prep
and a stand-alone disk restore. These routines transfer the system control software
from the release diskettes or tapes to your SYSRES, which is on a nonremovable
(fixed) disk. Perform this transfer before installing optional software or performing
SYSGEN.
You must run SU@PRP before you run SU@RST. The stand-alone prep routine,
SU@PRP, prepares (or preps) your nonremovable disk to serve as your SYSRES. The
stand-alone restore program, SU@RST, copies the system control software from the
release diskettes or tapes to your SYSRES.
Stand-Atone Routines
Stand- A l one Media
SYSRES Disk
Diskette
84 1 7/8470/8494/H9720
Tape
8417/8470/8494/M972®
These stand-alone routines also let you rebuild or restore your SYSRES if necessary.
See Section 3 for more information on making and restoring a backup SYSRES copy.
7004 5505-000
1-5
Introduction
1.6.2. Optional Software Installation Facilities
To install optional software components from diskettes, Unisys provides a job control
stream, SG@CPYPD 3 as part of the system control software. It automatically initiates
the routines that move separate program products and programming aids from
release diskettes to the SYSRES. Run SG@CPYPD after you install your system
control software. Then install each separate component before you perform SYSGEN.
1.6.3. Tape Software Installation Facilities Using an Existing SYSRES
To install an OS/3 release using an existing SYSRES from a dump/restore tape (file or
volume mode), use the job control stream SG$DMPTD. This control stream copies the
standard release software from the dump/restore tape to an output disk that you
specify at run time. The output disk must be the same disk type used to produce the
tape.
This job control stream can transfer an 8433 dump/restore tape onto a removable 8433
SYSRES volume. However, if you order your release on a removable disk formatted
tape (such as the 8419 disk) and you have a fixed 8417 disk as your SYSRES, you
must first run SG$DMPTD to transfer the software to an 8419 disk. Then you must
run SETREL/COPYREL to copy the software to your permanent 8417 SYSRES
volume.
1.6.4. System Maintenance Installation Facilities
To install system maintenance packages and system maintenance changes, Unisys
provides two installation programs, SMP and SMC, as part of the system control
software. The installation programs check the software components of your system
and then install the changes that apply to you. If your system requires regeneration as
a result of an SMP or SMC, the installation programs perform the regeneration for
you.
1.7. How to Perform System Generation
SYSGEN is the process that defines the system's hardware configuration to OS/3.
SYSGEN generates the control elements you need to satisfy particular processing
requirements. Unisys provides various facilities that define these requirements to
your system. These are the SYSGEN dialog, parameter processor, and job control
streams.
1-6 7004 5505-000
Introduction
1.7.1. SYSGEN Dialog
The SYSGEN dialog is an easy-to-use facility that helps you prepare and process the
SYSGEN parameters, or requirements. At your workstation, the SYSGEN dialog:
• Displays questions, menu choices, explanations, and help screens concerning the
various SYSGEN options
• Accepts your answers and choices
m Stores your parameters until you are ready to process them
• Executes the SYSGEN component that processes your parameters (the SYSGEN
parameter processor)
The workstation screen displays groups of options to choose from and provides
explanations and questions. If you need more information about a particular
parameter to make a valid choice, you can request help. The dialog provides detailed
explanations of that parameter. After it displays a help screen, the dialog resumes
where it left off.
An experienced SYSGEN user can build parameter sets quickly and easily, receiving
help only when needed. Users less familiar with SYSGEN can use the help screens to
learn about SYSGEN as the dialog guides them in building valid parameter sets. The
following screens show typical examples of the SYSGEN dialog.
PROGRAM=DIALOG FOR SYSTEM GENERATION
THE DIALOG FOR SYSTEM GENERATION IS A COMPUTER
ASSISTED METHOD FOR PREPARING SYSGEN PARAMETER SETS.
FOR A DESCRIPTION OF THE DIALOG PROCESS, ENTER "HELP"
IN THE SPACE PROVIDED.
THE DIALOG METHOD USES THE COMPUTER TO ASSIST YOU IN
PREPARING PARAMETER SETS BY PROVIDING EXPLANATIONS AND
PROMPTING FOR DATA ENTRY. AS PARAMETERS ARE NEEDED,
THE DIALOG PROCEEDS UNTIL A COMPLETE PARAMETER SET HAS
BEEN GENERATED. ALL THE PARAMETERS ARE VERIFIED BY THE
USER BEFORE THEY ARE OUTPUT FOR USE BY THE SYSGEN
PARAMETER PROCESSOR. PARAMETERS ARE SPECIFIED EITHER BY
SELECTING OPTIONS FROM A MENU OR BY ENTERING DATA DIRECTLY
FROM A WORKSTATION.
7004 5505-000
1-7
Introduction
Select the phases of SYSGEN you want to perform by entering the appropriate
number. See Section 3 for detailed descriptions of these SYSGEN phases.
SELECT THE SYSGEN PHASE TO BE PREPARED :
1. SUPERVISOR GENERATION (SUPGEN and IOGEN)
2. COBOL COMPILER OPTIOMS SPECS (COBGEN)
3. HTR UTILITY GENERATION (NTRGEN)
4. NO FURTHER PHASE REQUIREMENTS
5. DISPLAY PHASE DESCRIPTIONS
(EMTER PHASE NUMBER OR 'ALL') -----
ENTER CHOICE BY NUMBER
The SYSGEN dialog displays only those screens that pertain to the SYSGEN phases
you select. These screens display the parameter choices for each selected section,
explain your options in specifying parameters, and give the parameter default values.
You can specify values for most parameters, or you can accept the OS/3 default values
that create a workable system and are usually sufficient. At the end of each section of
related SYSGEN parameters, the dialog lists the selections you chose. You can:
• Accept the list as it is
• Correct or change a selection
• Completely erase and ignore a parameter set that you mistakenly specified
The SYSGEN dialog lets you double-check choices and display only those parameters
that apply to you. After you respond to the choice at the end of each parameter section,
you move on to the next set of parameter statements.
You can also save a record of the dialog sessions in case you want to change your
SYSGEN parameters. The dialog saves this record in a dialog audit file and provides a
printed summary listing. You can use this summary listing as a map to the audit file.
After you respond to all the phases of SYSGEN, a system message displayed at the
workstation informs you that the dialog session is complete. The SYSGEN dialog then
asks you to execute the parameter processor. If you are satisfied with your parameter
choices and are ready to process them, direct the SYSGEN dialog to execute the
parameter processor.
1-8 7004 5505-000
introduction
1.7.2. SYSGEN Parameter Processor
The SYSGEN parameter processor (SG$PARAM) is the SYSGEN component that
accepts and processes your parameter choices. It informs the system of the choices
made during the SYSGEN dialog session. The SYSGEN parameter processor:
• Checks and validates each of the SYSGEN parameters to ensure that you
specified them correctly (These checks are in addition to those of the SYSGEN
dialog.)
• Substitutes the OS/3 default values for those parameters that you specify
incorrectly or omit
• Informs you of incorrect and defaulted parameters
• Lists the OS/3 job streams that actually generate your system
The parameter processor gives you information on a printed summary listing. This
listing includes all the SYSGEN parameters (specified and defaulted), error
diagnostics, and instructions to proceed with SYSGEN.
1.7.3. SYSGEN Job Control Streams
Unisys provides job control streams to execute the SYSGEN dialog and parameter
processor and to generate the system for you. In addition, the job control stream lets
you define alternate printer characteristics if your printer has features different from
the OS/3 default printer characteristics. These job streams eliminate the need for you
to know the OS/3 job control language before generating your system.
The parameter processor lists the job control streams that you must run to build the
system elements you want. It bases this list on the parameter choices that you defined
through the SYSGEN dialog session.
The following SYSGEN job control streams are available:
• SG$BLD - Initiates the SYSGEN dialog, accepts parameter choices and
selections, and stores these sets until the parameter processor needs them. When
you are ready to process the parameter choices at the end of your dialog session,
SG$BLD automatically executes the parameter processor.
• IC$BLD - Initiates the ICAM portion of the SYSGEN dialog, accepts parameter
choices and selections, and stores these sets until the parameter processor needs
them. When you are ready to process them at the end of the ICAM portion of the
dialog session, IC$BLD automatically executes the parameter processor.
• SG$PARAM - Manually executes the parameter processor, verifies and processes
your SYSGEN parameter definitions, and lists the additional job streams you
should run, as well as parameter specifications, defaults, and error diagnostics.
7004 5505-000 1-9
Introduction
•
SG$SUPMK - Initiates the routines that generate the new or remodeled
supervisor configurations and stores them in the system load library file
($Y$LOD) on the designated SYSRES.
SG$COMMK - Initiates the routine that creates and transfers the integrated
communications access method (ICAM) load module to the designated SYSRES.
SG$NTRMK - Creates a nine-thousand-remote (NTR) system utility load module
and stores it in the $Y$LOD library on the designated SYSRES.
• SG$COBMK - Configures options for the ANSI 74 or '85 COBOL compiler.
• SG$PRB - Equates nonstandard printer character sets and vertical format
characteristics to your operating system. If none of the printers in your system
uses a 63-STD, 48-BUS, or 48-SCI print cartridge, you must run this job control
stream before you can perform any software installation or system generation
procedure that gives a printed listing.
1-8. System Installation Review
This review can help you better understand the relationships between the various
system installation facilities and procedures. Use the flowchart in Figure 1-1, and the
following list, to review the system installation process.
1 . Install any new release software that you receive from Unisys. Use the routines
and facilities you need to install system control software and optional software.
2. Perform post-software installation routines to complete the installation process.
See 2.3.
3. Generate your system by specifying SYSGEN parameters. Use the SYSGEN
dialog to define the elements of your system to fit your special processing needs.
Those thoroughly familiar with the SYSGEN process can expedite the process by
using the OS/3 editor to manually code or modify these parameter sets. See
Section 4.
4. Run the SYSGEN parameter processor to validate the selected parameters and
list the SYSGEN job control streams you must run to generate the system you've
defined. Make sure that each job terminates before initiating the next one.
5. Run each of the job control streams in the order that the parameter processor
lists them. When all the job control streams are run, system generation is
completed.
Before using your system, you should perform the applicable post-system generation
procedures to complete the system installation process. See details in 3.3.
140 7004 5505-000
Introduction
—
RUN
SGSDMPTD
^0
RUN
SU@RST
AND
SU@PRP
(IF NECESSARYI
RUN
SG@CPYPD
FOR EACH
PRODUCT
SOFTWARE
INSTALLATION
RUN THE
SYSGEN DIALOG
TO PREPARE
YOUR SYSGEN
PARAMETER
Recommended to back up release software or copy it to another type of disk.
Figure 1-1. System installation Process
7004 5505-000
Ml
Section 2
2.1. Considerations
This section describes the procedures you use to install standard and optional
software from the release media to your SYSRES.
Basically, three factors determine which software installation procedures you must
perform:
1. The type of user you are - initial or existing
2. The type of release software you have to install - standard or optional
3. The type of media you install your software from - diskette or tape
Regardless of the type of software you install, you should perform certain post-
software installation procedures to complete the installation process. (See 2.3.)
If your printer does not have the OS/3 default printer characteristics, you must define
its characteristics to the system before you can perform any software installation
procedure that gives a printed listing. (See 3.3.4 for a detailed description of the OS/3
default printer characteristics and the procedure for defining alternate printer
characteristics.)
2.1.1. Initial Users
Initial users must install both the standard release OS/3 software and any optional
software products they ordered.
When you receive the release software on diskettes or tapes, you first build the
SYSRES volume by installing the standard release OS/3 software. Then you can
install the optional software. Figure 2-1 shows the process to install release software
from diskettes. Figure 2-2 shows the process to install release software from tapes.
7004 5505-000 24
Software Installation
_d^ZZZZZZZZ
r~~
.1 • t
OS/3
rS\
SYSTEM
CONTROL
SOFTWARE
STAND-
ALONE
INSTALLATION
ROUTINES
OPTiONAL-
SOFTWARE
INSTALLATION
PROGRAM
OPTIONAL
OS/3
®
SOFTWARE
n
Figure 2-1. Software Installation from Diskettes for an Initial User
STAND-
ALONE
INSTALLATION
ROUTINES
OPTIONAL-
SOFTWARE
INSTALLATION
PROGRAM
OPTIONAL
OS/3
SOFTWARE
n
Figure 2-2. Software Installation from Tapes for an Initial User
Noter The stand-alone restore routine accepts only file mode format and supports
only nonremovable disk types.
2.1.2. Existing Users
For existing users, OS/3 software is released as:
• An entire new release of OS/3 software delivered on diskette or tape
• Optional OS/3 software delivered on diskettes
Installing New Optional OS/3 Software
To install optional OS/3 program product software after a system is already installed
and generated, the release level of the optional software must be the same as the
release level of the existing system software, Otherwise, the optional software cannot
operate properly. If you receive optional software at a different release level, it must
be part of a new OS/3 release. You must then update the operating system before you
install the optional software.
To install new optional software, perform the optional-software installation procedure
once for each separate program product or programming aid that you want to install.
2-2
7004 5505-000
Software installation
Figure 2-3 shows the installation of new optional OS/3 software.
OPTIONAL
OS/3
COMPONENT
n
OPTIONAL-
SOFTWARE
INSTALLATION
PROGRAM
SG@CPYPD
OPTIONAL SOFTWARE MUST BE AT SAME RELEASE LEVEL AS SYSTEM SOFTWARE
Figure 2-3. Installation of New Optional OS/3 Software
Snstalling a Mew Release of OS/3
Existing users who receive an entire new release of OS/3 must install this release to
update the system. The new release contains updated standard OS/3 release software
and updates to any optional software that you have. You should make a backup copy
of the existing SYSRES volume before installing the new release software. The
procedures to install a new release are similar to installing the initial release, with the
following exceptions:
• First, terminate all jobs before you install the new software. Do not process any
other jobs until the new release software is installed.
• Second, make copies on the SYSRES of your own software that you want to use
with the new release. Prepare these copies on disk or on diskettes, using the
following general procedures:
Copy all program modules from the system libraries (including source
modules that contain SYSGEN parameter sets that are still valid with the
new release). Use the system librarians, LIBS and MLIB. (See the System
Service Programs Operating Guide, UP-8841, for the details to perform this
operation.)
- Make copies of all program library files residing on the SYSRES (not system
library files), using the procedures described in Section 3. Specifically, use
the SG@DUFIL job stream, described In detail in that section, to make
backup copies on diskettes. Use LIBS or MLIB to make the copies on disk.
Use data utilities to make copies of any data files on your SYSRES. (See the
Data Utilities Operating Guide, 7004 4516.)
After you install the new release, copy the program modules and library files back to
the updated SYSRES. Use the same system facility that you used to prepare the
copies of this software. During subsequent SYSGEN operations, you can use these
SYSGEN parameter sets as input to the parameter processor.
7004 5505-000
2-3
Software Installation
This procedure lets you generate the system without defining all system parameters
as required for initial users.
Figure 2-4 shows the installation of a new release of OS/3.
Note: This installation procedure represents one method of installing a new release
of OS/ 3 for an existing user. There are other methods available. They are
discussed in 2.2.
2.1.3. SYSRES Build Guidelines
The following guidelines assist you in tailoring your SYSRES. They are especially
useful when you are using the disks with the smaller capacities (8419 or 8430). These
guidelines provide information on file maintenance and the allocation of specific files
on disks other than the SYSRES.
• Librarian format files are expanded if there is module replacement or updating
due to SMC applications, system generations, ICAM generations, or extraneous
processing. The unused space in these files is recovered only either by packing the
file or by copying it to another disk and copying it back after initializing the file.
You can track the status of your file size and expansion by using the VTOC
command at defined intervals. The amount of expansion depends on the number
of generations or SMCs and is site specific.
• The MAPPER® data files do not have to reside on SYSRES. They can be placed
on a volume with the VSN of MAPPER.
• The $Y$DUMP file does not have to reside on SYSRES. This can be specified with
the DUMPVSN system generation parameter or on the date/time screen at IPL
time. A system job stream, SG$SADMP, that will scratch a full $Y$DUMP file
and reallocate a minimum $Y$DUMP file on SYSRES is also available. A
minimum $Y$DUMP file always resides on your SYSRES.
• The spool file can be allocated with the SPOOLVSN system generation parameter
or on the time/date screen at IPL time.
• Run files can be allocated on a non-SYSRES disk with the RUNVSN system
generation parameter or on the date/time screen at IPL time.
• You can move additional selected modules/products from system files on your
SYSRES to files on a non-SYSRES disk. However, this should be done only with
the assistance of your Unisys Customer Support Center.
MAPPER is a registered trademark and service mark of Unisys Corporation.
2-4 7004 5505-000
Software Installation
> a. Save all desired user software
b. Install new OS/3 release software
on your SYSRES
} c. Copy user software back
to SYSRES
Figure 2-4. Installation of a New OS/3 Release
7004 5505-000
2-5
Software Installation
2.2. Installation Procedures
You can build the SYSRES on any disk device the system supports, except for 8416 or
8418-1 (low-density) disks.
The following procedures let you install:
• Standard release OS/3 software from diskettes or tapes using stand-alone
routines (2.2.1)
• Optional program product software from diskettes (2.2.2)
• Standard release OS/3 software from tapes using online dump/restore routines
(2.2.3)
2.2.1. Installing Standard Release OS/3 Software from Diskettes or Tapes
Using Stand-Alone Routines
The following procedure lets you install standard release OS/3 software on a system
that does not have an operable SYSRES. The stand-alone media contains the
SU@PRP and SU@RST routines necessary for this procedure.
The following procedure preps the disk you are going to use as your SYSRES and then
installs the system control software (SCS). The SCS is installed by the restore routine
which transfers the SCS from the release media to the SYSRES disk.
If you are unfamiliar with these routines, you should review the considerations listed
at the end of the procedure.
To install OS/3 software using the stand-alone routines:
1. Load the initial microprogram load (IMPL) code diskette containing the system
microcode supplied with the release diskettes into diskette drive FDDO. This
diskette stays loaded in this drive permanently.
2. Perform the system tum-on procedure as described in the Operations Guide,
7004 5208, with the IPL switch set to manual.
3. When the configuration frame appears, enter the device address (did) of your disk
candidate SYSRES disk. This establishes the disk as the default value for the
SYSRES.
4. Load the IPL diskette in an available diskette drive.
5. Press ESC and then the M key to display the manual frame.
6. Enter C (or G if you have an autoloader diskette) and the device address (did) of
the diskette drive containing the IPL diskette. Press XMIT.
2-6 7004 5505-000
Installation Procedures
When the OS/3 initial program load (IPL) screen is displayed, key in:
SUaPRP f L#did
where:
L
Specifies the option for loading stand-alone programs.
did
Is the device address of the diskette drive containing the IPL diskette.
Press XMIT. The system loads the stand-alone disk prep routine Into main
storage and requests information from you. For most applications of SU@PRP,
the following responses are valid. In some cases, you can choose options different
from the ones shown.
Note: When you use the autoloader to load S U@PRP or S U@RST, a channel
reset is done by IPL. This ejects the diskette and an I/O error occurs.
Remount the diskette and reply R.
a. When SU@PRP requests ENTER OUTPUT DISK DEVICE TYPE (nnnn),
key In the disk type and press XMIT.
b. When SU@PRP asks WHAT DRIVE IS YOUR DISK ON?, key in the device
address (did) of your SYSRES disk device and press XMIT.
c. If SU@PRP asks DOWNLINE MICROCODE TO DISK?, key in Y and press
XMIT. (This question does not appear for 8494 or M9720 disks.)
d. If SU@PRP asks WHAT DRIVE IS MICROCODE DSKT ON?, key in the
device address (did) of the diskette drive containing the IDCU microcode
diskette for the disk you are prepping and press XMIT. (This question does
not appear for 8494 or M9720 disks.)
e. When SU@PRP asks WHAT DISK VOL SERIAL NUMBER DO YOU
WANT? (xxxxxx), key in the six-character volume serial number you want
written into the VOL1 label on the disk.
f. If SU@PRP asks DO YOU WANT TO WRITE HOME ADDRESSES? (Y/N),
key in Y for yes and press XMIT. (This question appears only during prep of
8470 disks.)
g. If SU@PRP asks DO YOU WANT SURFACE ANALYSIS? (Y/N), key in Y for
yes and press XMIT. (This question does not appear for 8470 disks.)
h. When SU@PRP asks DO YOU WANT FAST OR COMPLETE ANALYSIS?
(F/C), key In C and press XMIT.
7004 5505-000 2-7
installation Procedures
i. When you are prepping an 8470 disk, SU@PRP asks IS THE TCT NEW OR
FROM DISK? (N/D). Key in one of the following:
N and press the XMIT key if the disk is factory fresh or if you suspect that
the disk requires formatting. The disk will be formatted and basic surface
analysis performed. Any defects found during the surface analysis are placed
into a new track condition table (TCT).
D and press the XMIT key if the disk was previously prepped using OS/3
disk prep or SU@PRP. The TCT is not rebuilt. However, any defects found
during surface analysis are added to the TCT.
j When you are prepping an 8494 or M9720 disk, SU@PRP asks IS THE SCT
NEW OR FROM DISK (N/D). Key in one of the following:
N and press the XMIT key if the disk is factory fresh or if you suspect that
the disk requires formatting. The disk will be formatted and basic surface
analysis performed. Any defects listed in the factory defect table, or found
during the surface analysis, are placed into a new sector condition table
(SCT).
D and press the XMIT key if the disk was previously prepped using OS/3
disk prep or SU@PRP. The SCT is not rebuilt. However, any defects found
during surface analysis are added to the SCT.
k. When you are prepping an 8417 disk, SU@PRP asks IS THE TCT NEW,
FROM DISK, OR FROM DISKETTE? (N/D/K). Key in one of the following:
N and press the XMIT key if the disk is factory fresh or if you suspect that
the disk requires formatting. The disk will be formatted and basic surface
analysis performed. Any defects found during the surface analysis are placed
into a new track condition table (TCT).
DorK and press the XMIT key if the disk was previously prepped using
OS/3 disk prep or SU@PRP to read the TCT from disk or diskette. The TCT
is not rebuilt. However, any defects found during surface analysis are added
to the TCT.
1. When SU@PRP requests that you ENTER INSERT (cccchh/END/NONE) or
ENTER INSERT (cccchhrr/END/NONE) for 8494 and M9720 disks, key in
NONE and press XMIT.
Note: If you know of defective tracks I records on the SYSRES disk, enter
the hexadecimal address of those tracks / records so the routine
formats them as defective.
After you provide SU@PRP with the information requested, it preps the disk and
informs you when it terminates.
9. When SU@PRP terminates normally, press XMIT to re-IPL the system.
2-8 7004 5505-000
installation Procedures
10. When the OS/3 IPL screen is displayed, key in:
SUaRST,L,did
where:
L
Specifies the option for loading stand-alone programs.
did
Is the device address of the diskette drive containing the IPL diskette.
Note; Device address (did) values are site dependent and are configured
when your hardware is installed.
11. Press XMIT. The system loads the stand-alone disk restore program (SU@RST).
The program then requests information from you. Respond to these requests as
follows:
a. When SU@RST requests ENTER OUTPUT DISK DEVICE TYPE (nnnn),
key in the disk type and press XMIT.
b. When SU@RST asks WHAT DRIVE IS YOUR OUTPUT DISK ON? (did),
key in the device address (did) of the disk to be the SYSRES and press
XMIT.
c. If SU@RST asks DOWNLOAD MICROCODE TO DISK?, key in N for no and
press XMIT. (This question does not appear for 8494 or M9720 disks.)
d. When SU@RST asks IS INPUT MEDIUM TAPE OR DISKETTE?
(TAPE/DSKT), key in TAPE or DSKT and press XMIT.
If you enter TAPE, the message ENTER INPUT TAPE DEVICE TYPE
(NNNN) is displayed. Key in Uxx or BT32.
e. When SU@RST asks WHAT DRIVE IS YOUR INPUT TAPE/DISKETTE
ON?
1 . Replace the IPL diskette with your first system control software release
diskette or mount the first system control software tape on an available
drive.
If you are using an autoload diskette unit, the program loads the
diskettes automatically. Remember that the volumes must be in the
order requested by SU@RST for the program to copy them.
2. Key in the device address (did) of the drive containing your system
control software release diskette or tape.
7004 5505-000 2-9
Installation Procedures
3. Press XMIT.
Note: If the input device is aUll tape (streamer) or U22 on a DMUX
channel (C or E), SU@RST asks DOWNLINE LOAD
MICROCODE TO DEVICE? Key in Y and press XMIT.
When SUmiST asks WHAT DRIVE IS MICROCODE DSKT
0N? f key in the device address (did) of the diskette drive
containing the ITCU microcode for the streamer tape and press
XMIT.
f. When SU@RST asks ARE YOU INITIALIZING YOUR SYSTEM? ( Y/N ),
key in Y and press XMIT.
After you have provided SU@RST with the response information, it copies
the entire contents of the system control software release to the SYSRES.
The routine informs you of completion as it successfully copies your diskettes
or tapes and displays a message telling you where to mount the next volume.
g. When SU@RST displays the MOUNT message, mount the requested tape or
diskette, key in R for ready, then press XMIT.
h. After SU@RST copies all your release diskettes or tapes to the SYSRES, a
message informs you that the program terminated normally. (If SU@RST
does not terminate normally, use the SU@RST restart capability.) You now
have a functional SYSRES and you are ready to load the system with a
starter supervisor.
12. Press XMIT to re-IPL the system. At the IPL screen, key in:
SY#BAS f S s did
or
SY$BAS,S,did
where:
SY#BAS
Specifies the starter supervisor for model 8.
SY$BAS
Specifies the starter supervisor for models 10 through 20.
s
Specifies the option for loading a supervisor.
did
Specifies the device address of the SYSRES disk.
13. Press XMIT. The System Date/Time screen is displayed (Figure 2-5).
2-10 7004 5505-000
Installation Procedures
A)
DATE; YY/MM/DD
TINEs HH:HMs
B)
RUM LIBS DVC ADDRs
XXX (SYSRES)
C)
FILE RECOVERY
JOB QUEUE
<H,Y,H DEFAULTS)
ERROR LOG
CN,Y DEFAULTS)
SPOOL FILES
(N,A,C s L f H DEFAULT=N)
D)
MODIFY SUPERVISOR*
DEFAULTS
E)
SPOOLING DVC ADDR;
XXX C SYSRES)
F)
DUMP FILE DVC ADDR
; XXX C SYSRES)
ss
TRANSMIT TO ENTER DEFAULTS. OTHERWISE ENTER THE LETTERS OF THE
PARAMETERCS) TO BE CHANGED.
Figure 2-5. System Date/Time Display
14. Press XMIT to accept the defaults supplied by the system.
When the system displays header messages indicating OS/3 version number,
supervisor name, date, and time, It is ready for you to perform your next installation
task - either Installing software or performing system generation.
Note: If the documentation that accompanied your standard release software
instructs you to update loadable microcode, go to the post-installation task of
updating the system definition file in 2.3.1. If you do not install optional
software or generate your own supervisor, the system is now ready for use.
Stand-alone Routines Considerations
When using the stand-alone routines to Install SCS, you should be aware of the
following:
• Initializing your disk destroys any files that are on your disk.
• The stand-alone SU@PRP routine does not destroy the factory defect table.
• If you experience I/O errors loading from diskette or tape during the stand-alone
routine, use the restart capability of the SU@RST program.
Restarting SU@RST
Use the following procedure, when necessary, to initiate the restart capability of
SU@RST. Note that all data successfully copied to SYSRES when the error occurred
remains intact on SYSRES.
It Is preferable that you use a different diskette drive or tape unit, if possible, for the
restart operation in case the error was caused by a peripheral unit hardware problem.
1. Press ESO and then the M key to display the manual frame.
7004 5505-000
2-11
Installation Procedures
2. Enter C (or G, If the autoloader is used) and the device address (did) of the
diskette drive containing the IPL diskette.
3. Press XMIT to redisplay the IPL screen.
4. Reinitiate the restore routine by starting at step 10 in the procedure in 2.2.1.
5. When SU@RST asks AEE YOU RESTARTING (Y/N)?, key in Y for yes and press
XMIT.
6. When SU@RST asks AT WHAT VOLUME? (nnn), key in the three-character
volume number where you encountered the error. This number is on the external
label of the media. For example, if you encountered the error on diskette SYS009,
key in 009. Press XMIT.
7. When SU@RST requests ARE YOU INITIALIZING YOUR SYSTEM (Y/N)?, key
in Y for yes and press XMIT.
After you provide SU@RST with this information and the necessary diskette or
tape Input, It resumes copying the entire contents of your remaining release
media to the SYSRES. The routine Informs you that it begins to restore a file
either midway through the file or from the beginning of the file, depending on
where you experienced the I/O error. These messages are informational messages
and there is no need for you to respond to them. SU@RST also informs you as It
successfully copies each diskette or tape and displays a message when you should
mount the next volume. Remember - your diskettes and tapes must be in the
order requested by SU@RST for the program to copy them.
8. When SU@RST displays the MOUNT message, mount the requested diskette or
tape. Key in the two-character message number, R for ready, and press XMIT.
After SU@RST copies all the release media to the SYSRES, a message Informs
you that the program terminated normally.
2.2.2. Installing Optional Program Product Software from Diskettes
The following paragraphs describe the procedure for Installing optional, separately
delivered program products and programming aids. These products can only be
Installed after your SGS is Installed and the system is initialized with a valid
supervisor.
If the optional components that you are Installing require operating system support,
be sure to generate control elements that support these products before you attempt to
use them. Table 3-1 lists all the optional components that OS/3 offers and shows
which control elements you need to support them.
Perform this procedure for each optional software component you want to install. That
is, if you are installing several optional components, you must run SG@CPYPD once
for each component.
242 7004 5505-000
Installation Procedures
It takes approximately 2 to 10 minutes to install an optional program product or
programming aid, depending upon the size of the product.
1. Key in:
RV SG3CPYPD
2. Press XMIT.
3. When SG^CPYPD displays the message MOUNT VSN=A GO?, mount the first
component diskette.
4. Key in GO SG^CPYPD and press XMIT. SG@CPYPD then initiates the
SGSMVPD routine, which moves the separate component software from its
release diskette to the SYSRES. If the component resides on more than one
release diskette, SG@MVPD asks you to mount the next volume.
5. When SG^MVPD displays a MOUNT message:
a. Mount the requested diskette.
b. Key in the two-character message number and R for ready in the following
format:
nn R
where:
nn
Is the message number.
c. Press XMIT.
When SG@MVPD successfully copies your optional software onto the SYSRES, it
displays a message to inform you that the routine terminated normally.
2.2.3. Installing Standard Release OS/3 Software from Tapes Using
Online Dump/Restore Routines
Unisys delivers (upon request) updated standard release OS/3 software on
dump/restore tapes. Existing users can install this updated software using the online
dump/restore routines if they have an active SYSRES and an additional free disk. The
free disk then becomes the new SYSRES. Following installation of the updated
software, perform post-installation and SYSGEN procedures as described in 2.3.
The job stream SG$DMPTD is used to transfer the software from the dump/restore
tape to the new SYSRES disk. It is important to note that the dump/restore tapes are
created to be used with a specific disk type.
7004 5505-000 243
Installation Procedures
To Install OS/3 release software from dump/restore tape, perform the following
procedure:
1. Perform an initial program load (IPL) from the existing SYSRES to load either
the starter supervisor or a supervisor that you previously generated. Make sure
the free (output) disk is online before you perform the IPL.
2. Prep your output disk, using the online DSKPRP routine. For a full description of
disk prep functions, see the System Service Programs Operating Guide,
UP-8841. (A sample disk prep job control stream that preps an 8417 disk so that
release software can be installed on It is presented following this procedure. With
a few minor changes, you can also use this control stream to prep any disk.)
3. Mount the release tape. If you have two release tapes, you can mount the second
tape on a second tape drive. If you only have one tape drive, you must wait until
the first tape Is read and rewound before you can mount the second tape.
4. Initiate the SG$DMPTD Installation job control stream by keying in:
RV SG$DMPTD
5. SG$DMPTD now generates a series of prompts to allow you to complete the
installation procedure:
a. When IS THE INPUT TAPE MULTI-VOLUME (N,Y)? is displayed, answer
N if you received the software on one tape or Y If you received the software
on more than one tape. Press XMIT.
b. If you responded Y, this message appears: TO SPEED PROCESSING USE
ALTERNATE TAPE DRIVES TO DECREASE SETUP TIME. After a
moment, ARE MULTIPLE TAPE DRIVES AVAILABLE (N,Y)? Is displayed.
Respond with N If you must use a single tape drive or Y If a second tape
drive is available. Press XMIT.
c. When ENTER THE NUMBER OF INPUT TAPE VOLUMES Is displayed,
key In the number of volumes you have (the maximum is six) and press
XMIT.
d. When ENTER VSN OF INPUT TAPE Is displayed, key In the VSN
identified on the tape label. If you received your release on two tapes, key in
the VSN of the first tape. Press XMIT.
e. If you specified multlvolume input in step a, the ENTER VSN OF INPUT
TAPE 2 message appears. Key in the VSN Identified on the second tape and
press XMIT.
f. When the IS INPUT TAPE IN FILE FORMAT? (Y,N) message appears, key
In Y and press XMIT. (Release tapes are always in file format.)
g. When the ENTER VSN OF OUTPUT DISK message appears, key in the
RELxxx value that was specified when you prepped the output disk (step 2).
Press XMIT.
2-14 7004 5505-000
Installation Procedures
Notes:
1. You can ignore any error messages for the $IMPL S $lPL t and $VTOC file that may
be displayed when SG$DMPTD starts.
2. If any errors occur affecting $IPL, then you must run the PRPMICjob stream
before re-IPLing. This is necessary to properly place the IPL load modules on
SYSRES.
SG$DMPTD now copies release software from tape volumes to the output disk. If
applicable, it provides messages when additional tapes must be loaded. A termination
message is displayed when SG$DMPTD is completed.
Using PRPMiC
PRPMIC is a canned job stream that places IPL load modules into the $IPL file on a
specified disk.
This job should be run if either of the following occur:
• An error occurs in restoring the $IPL file using dump/restore (SG$DMPTD).
• A new IPL is transmitted via an SMC.
To ran PRPMIC, key in:
RV PRPMIC „V=vsn
,INRES=
ffl
where:
V=vsn
Identifies the volume serial number of the output disk.
INRES= I or Y
Indicates the location from which the IPL load modules should be retrieved.
Specify N if an error occurs while restoring $1PL using dump/restore. This
indicates that the output disk contains the latest version of the IPL load
modules. The load modules on SYSRES should not be retrieved. N is the
default value.
Specify Y if an SMC containing a new IPL was applied to SYSRES. This
indicates that SYSRES contains the latest version of the IPL load
modules. The load modules on SYSRES should be retrieved.
7004 5505-000 245
Installation Procedures
Sample Disk Prep
The following is a sample execution of disk prep:
1.
//
JOB PREP
2.
//
DVC 28 // LFD PRNTR
3.
//
DVC 50,188
4.
//
VOL Newvol(NOV)
5.
//
LFD D1SKIN
6.
//
DVC RES
7.
//
LBL $Y$SDF
8.
//
LFD $Y$SDF
9.
//
EXEC DSKPRP
18.
/$
11.
SERNR=RELxxx,TRCON=D,fPLDK=Y,
12.
PREPT=C,ILOPT=Y
13.
VOL1
14.
INSERT NONE
15.
/*
16.
/&
Explanation:
Line 3: The number 100 specifies the device address of the 8417 integrated disk. If
you are prepping any disk other than this one, you must replace 100 with the
appropriate device address.
Lines 6-8: This DVC-LFD sequence identifies the system definition file, $Y$SDF, used
for building the IMPL records on the disk you're prepping.
Line 11: SERNR=RELxxx specifies the volume serial number of your output disk,
where xxx is the release level. Refer to the documentation accompanying your
software release if you are uncertain of the level of your release. TRCON=D specifies
that you're updating the track condition table of a disk that has been prepped before.
If your output disk has never been prepped, specify TRCON=N to create a new track
condition table.
Line 14: The entry NONE in the INSERT statement indicates there are no known
bad tracks on your output disk. If there are known defective tracks on your output
disk, use INSERT control statements to specify the hexadecimal addresses of these
tracks.
246 7004 5505-000
Post-Software Installation Procedures
2.3. Post-Software Installation Procedures
After you install all your OS/3 release software, perform all the applicable post-
software installation procedures in the order listed.
.' ;, ; ' 'U' . J". '■!! ' ■( . ... i <r* ]* V, !' "' ' ' I ■
If you installed updated OS/3 software or an SMP, you might need to update the
system definition file, $Y$SDF, which contains the names of the microcode associated
with all the devices in the system. Microcode names in $Y$SDF must match the
names of the actual microcode in the system microcode file, $Y$MIC. If the names and
the actual microcode do not match, you must update $Y$SDF to reflect the actual
microcode that the system contains.
When Unisys delivers the system, $Y$SDF contains the microcode names for
microcode in $Y$M1C for:
- ( ■esiya 1 pr^eessivig afA.it, (>y»od'~) f* only)
• A disk cache program
• One other local workstation
However, if your system includes any of the following devices, you must update
$Y$SDF after you install an updated OS/3 release or SMP. This update is necessary
because, even though the installation processes add the microcode for those devices to
$Y$MIC, they don't automatically place the names of that microcode in $Y$SDF.
Therefore, the microcode names in $Y$SDF do not match the actual microcode in
$Y$MIC.
The devices for which you must update $Y$SDF are:
• An integrated disk control unit (1DGU)
• An input/output processor
• Any workstations other than the console/workstation plus one more
• Any 0739 remote printer
• Any streaming tape
7004 5505-000
247
Post-Software Installation Procedures
The documentation that accompanies an OS/3 release or SMP informs you of any
changes in the microcode in $Y$MIC.
If your system includes an input/output processor, you must update $Y$SDF to
include not only CPU 1MPL code, but also IOMP and DBUS microcode. If your system
includes an integrated disk control unit (IDCU), you must update $Y$SDF to include
not only CPU IMPL code, but also IDCU DBUS microcode. (CPU, IOMP, IDCU, and
DBUS are types of IMPL code.)
To update $Y$SDF, Unisys supplies the system definition utility (SDU). SDU can run
$Y$SDF at a workstation/terminal. If you are a user without a workstation, a similar
product, XSDU, can run from your system console. XSDU communicates with you
through console statements.
XSDU is a console version of SDU, but with limited capabilities in working with
$Y$SDF. You can use this version only in systems that do not have a
workstation/terminal
After a system is configured with a workstation/terminal and you use SDU, do not
attempt to use XSDU. Once SDU invokes full functionality and sets up keys for search
fields, XSDU cannot satisfy the search request for these entries.
This subsection describes how to use both products but is primarily oriented to the
SDU user. Specific references to XSDU are limited to critical differences. If you are
running XSDU, you can assume most workstation references also apply to the console.
The differences between SDU screens and XSDU console statements are self-
explanatory at execution and therefore are not detailed here.
SDU provides three functions that let you:
• Add a new device to $Y$SDF
• Delete an existing device from $Y$SDF
• Update information for an existing device in $Y$SDF
SDU also has print and display capabilities that let you print the contents of $Y$SDF
on your system printer or display its contents on your workstation. By checking the
contents of $Y$SDF both before and after you perform one of the update functions,
you can be sure that you properly updated $Y$SDF.
You can also display the contents of $Y$MIC at your workstation. $Y$MIC contains
the information that SDU asks from you concerning the microcode in your system.
248 7004 5505-000
Post-Software Installation Procedures
Whenever you update $Y$SDF to include IMPL code, you must also place the
microcode in the correct position on the SYSRES disk so that you can later perform
initial microprogram load code procedures. To place the microcode in the IMPL area
on your SYSRES, SDU automatically schedules a prefiled job control stream called
PRPMIC. Then SDU terminates itself.
If you are updating $Y$SDF to include any type of IMPL code, both SDU and
PRPMIC must terminate before you can proceed with system installation. (SDU can
only be run from a workstation.)
The actual updating of $Y$SDF is made up of several steps that are shown in
Figure 2-6. The first step you must perform is to display the contents of $Y$MIC to
review the microcode applicable to your system. This review provides you with
information that SDU specifically asks as input when updating $Y$SDF.
Next, you must review the contents of $Y$SDF and compare it to the contents of
$Y$MIC to determine which entries in $Y$SDF you must update (add, delete, or
modify). After determining what to update, select the appropriate SDU update
procedure and proceed to update the contents of $Y$SDF. When completed, review the
contents of $Y$SDF to confirm that the file was updated correctly.
Once you make certain that the microcode names in $Y$SDF now match the actual
microcode in $Y$MIC, you can terminate SDU. If you added IMPL code to $Y$SDF,
SDU automatically runs PRPMIC to place the microcode in the correct position on the
SYSRES disk. At this point, you must perform initial microprogram load (IMPL) and
initial program load (IPL) procedures. Then the system is ready for use.
The 8416, 8417, 8418, 8419, and 8470 disks and the 3561 and 3612 (1122)
workstations use loadable control units and require entries in $Y$SDF and loadable
code in $Y$MIC. These devices can be loaded in two ways:
1. Disk control units loaded during IPL
If a disk is prepped as an IMPLTPL device, the control unit loads itself from the
disk prior to completing the IPL process.
2. Disk and workstation control units loaded during system initialization
If the control unit is not used in the IMPL/IPL load path, it is downline loaded
from the processor during system initialization.
7004 5505-000 2-19
Post-Software Installation Procedures
r
DETERMINE
WHAT REQUIRES H
UPDATING
DISPLAY CONTENTS
OF $Y$MIC
DISPLAY/PRINT CONTENTS
OF $Y$SDF
INITIATE
SDU (OR XSDU)
COMPARE $Y$MIC WITH $Y$SDF TO
DETERMINE UPDATE REQUIREMENTS
SELECT UPDATE OPERATIONS
TO BE PERFORMED
ADD DEVICE
TO $Y$SDF
DELETE DEVICE
FROM $Y$SDF
UPDATE INFORMATION
IN $Y$SDF
DISPLAY/PRINT CONTENTS OF
$Y$SDF TO CONFIRM UPDATE
TERMINATE
SDU (OR XSDU)
SDU RUNS PRPMIC IF YOU UPDATED
$Y$SDF TO INCLUDE IMPL CODE
PERFORM IMPL AND
I PL PROCEDURES
Figure 2-6. Updating $Y$SDF
2-20
7004 550S000
Post-Software Installation Procedures
The procedures for updating $Y$SDF are presented in the following order:
1. Determining what to update by reviewing the contents of $Y$M1C and $Y$SDF
2. Adding a device to $Y$SDF
3. Deleting a device from $Y$SDF
4. Updating existing device information in $Y$SDF
5. Confirming that $Y$SDF is updated correctly
6. Performing IMPL and IPL procedures
Notes:
1. With the exception of those messages included here, the System Messages
Reference Manual, 7004 5190, describes all messages concerning this procedure in
the section on unprefixed messages.
2. To perform this procedure, we assume that the system is operating under the
control of either the starter supervisor or one that you generated yourself.
Determining What to Update by Reviewing $Y$MIC and $Y$SDF
1 . At your workstation in system mode, key in:
FSTAT f $YSHIC # RES
and then press XMIT. The contents of $Y$MIC are displayed.
2. Record the following information:
9 Microcode name
• Microcode device
• Microcode type (Refer to the documentation accompanying your release
software for the microcode type.)
SDU will request this information from you later.
3. Key in SDU (or XSDU if you are a user with no workstation), and press XMIT.
The operation request screen (Figure 2-7) is displayed.
7004 5505-000 2-21
Post-Software Installation Procedures
SYSTEM DEFINITION UTILITY
ENTER THE OPERATION TO BE PERFORMED:
( )
1. ADD A DEVICE TO THE $Y$SDF FILE.
6. PRINT THE $Y$SDF FILE.
2. DELETE A DEVICE FROM THE $Y$SDF
7. DUMP THE $Y$SDF FILE.
FILE.
3. UPDATE A DEVICE IN THE $Y$SDF
8. RESTORE THE $Y$SDF
FILE.
FILE.
4. DISPLAY SELECTED $Y$SDF ENTRIES.
9. TERMINATE SDU.
5. DISPLAY ALL $Y$SDF ENTRIES.
FUNCTION F1 WILL TERMINATE OPERATION
AND RETURN TO
J THIS SCREEN.
Figure 2-7. SDU Operation Request Screen
This screen offers you three choices for checking the contents of $Y$SDF against
$Y$MIC.
• Selection number 4, DISPLAY SELECTED $Y$SDF ENTRIES, lets you
select specific $Y$SDF entries for display. A screen listing all entries is
provided and you key in an X next to the entries you want to display. A
sample SDU Display Operation screen is shown in Figure 2-8.
SDU DISPLAY OPERATION
DEVICE ADDRESS
HHH
TYPE/FEATURE/SELECTION
ANNNN-NN
MICROCODE NAME
XXXXXXNN
SERIAL NUMBER
XXXXXXXX
UNIQUE ID
XXXXXXXXXXXXXXX
FCO LEVEL
kuuun-UM
NOTES
XXXXXXXXXXXXXXX
PCA PART NUMBER
NNNNNNN-NNN
PROM KIT NUMBER/FCO LEVEL
NNNNNNN-NN NNNN-NNN
PRESS TRANSMIT TO CONTINUE.
Figure 2-8. SDU Display Operation Screen
where:
A=alphabetic ? N=numeric, X=alphanumeric, H=hexadecimal
2-22
7004 5505-000
Post-Software Installation Procedures
• Selection number 5, DISPLAY ALL $Y$SDF ENTRIES, lets you display
every entry in the $Y$SDF file. Refer to Figure 2-8 for the display screen
format.
• Selection number 6, PRINT THE $Y$SDF FILE, lets you print the entire
contents of $Y$SDF on the system printer as shown in Figure 2-9.
DEVICE TYPE
MICROCODE SERIAL
UNIQUE FCO
ADDRESS FEATURE
&IAME MUHBER
ID LEVEL
NOTES
XXXX ANNNN-NN
XXXXXXMN XXXXXXXX
XXXXXXXXXXXXXXX ANNNN-NNN
XXXX
PCA
PROM KIT
PROM KIT
NUMBER
MUMBER
FCO
miH,m<^-mn
NMUNNNN-NN
nnnn-nnn
Figure 2-9. Sample $Y$SDF Printer Output
4. Determine the $Y$SDF display choice that you want, key in the applicable
selection number (4, 5, or 6), and press XMIT. After display or print operation is
completed, the dialog returns to the SDU operation request screen.
5. Compare the contents of $Y$SDF (obtained in step 4) with the contents of
$Y$MIC (obtained in step 2). From this comparison, determine which entries
must be added, deleted, or updated in $Y$SDF.
If no update is necessary, terminate SDU by keying in 9 and pressing XMIT. If
$Y$SDF requires updating, proceed to the appropriate following subsection.
Adding a Dewlce to $Y$SDF
Note! Do not perform the following procedure unless you completed the previous
procedure on reviewing the contents of$Y$MIC and $Y$SDF or are
continuing from one of the other $Y$SDF update procedures.
1. Key in 1 on the SDU operation request screen, then press XMIT.
2. Respond to the following message that SDU displays:
IS DEVICE TO BE ADDED FOR AM IMPL DEVICE?(Y,M)
7004 5505-000
2-23
Post-Software Installation Procedures
If your response is N, the following add screen (Figure 2-10) is displayed:
SDU ADD OPERATION
ENTER NEW INFORMATION
(A=ALPHABETIC N=NUMERIC X=ALPHANUMERIC H=HEXADECIMAL Z=OPTIONAL NUMERIC)
DEVICE ADDRESS (HHH) .
TYPE/FEATURE (TNNNN-NN, FNNNM-NN, _____
WSC-ZZ, STCU -ZZ, IDCU-NN BPU-ZZ, SVP-ZZ, OR I0MP-ZZ)
MICROCODE NAME (XXXXXXNN) ______
SERIAL NUMBER (XXXXXXXX) ______
UNIQUE ID (XXXXXXXXXXXXXXX)
FCO LEVEL (ANNNN-NNN) _______
NOTES (XXXXXXXXXXXXXXX) _____________
PCA PART NUMBER (NNNNNNN-NNN)
PROM KIT NUMBER/FCO LEVEL (NNNNNNN-NN NNNN-NNN)
Figure 2-10. SDU Add Screen for Non-MPL De¥ices
If your response is Y 3 the following IMPL add screen (Figure 2-11) is displayed:
SDU ADD OPERATION
ENTER NEW INFORMATION
(A=ALPHABETIC N-NUMERIC X-ALPHANUMERIC Z^=OPTIONAL NUMERIC)
DEVICE ADDRESS IMPL
TYPE/FEATURE (CPU-NN, DBU8-ZZ, IOMP-ZZ,
CACH-ZZ, IDC-ZZ, IDCU-NN, OR CAC8-ZZ)
MICROCODE NAME (XXXXXXNN)
SERIAL NUMBER (XXXXXXXX) ,
UNIQUE ID (XXXXXXXXXXXXXXX) _____
FCO LEVEL (ANNNN-NNN) ______
NOTES (XXXXXXXXXXXXXXX) ______
PCA PART NUMBER (NMNNNNN-NNN)
PROM KIT NUMBER/FCO LEVEL (NNNNNNN-NN NNNN-NNN)
Figure 2-11. SDU Add Screen for IMPL Devices
Enter the appropriate device identifiers in the formats shown on the add screen.
The device address, type/feature, and microcode name are the only required
entries; all other entries are optional If you are specifying a type/feature value of
WSC-ZZ, STCU-ZZ, IDCU-NN, or RPI-ZZ, the last digit of the device address
must be 0. If you are specifying a type/feature value of BPU-ZZ, SVP-ZZ, or
IOMP-ZZ, the device address must be 001.
2-24
7004 5505-000
Post-Software Installation Procedures
Notes:
1. If you keyed in an address of a device that already exists in $Y$SDF, the
following message appears and SDU returns to the SDU operation request
screen:
ENTRY ALREADY EXISTS IN $Y$SDF, USE UPDATE OPERATION
2. If you keyed in the address for a device not configured in your system, SDU
displays the message:
DEVICE NOT CONFIGURED, DO YOU WISH TO CONTINUE? (Y # N)
If you keyed in the address for a device that is configured hut is nonloadable,
SDU displays the message:
DEVICE NOT LOADABLE, DO YOU WISH TO CONTINUE? (Y f N)
To continue the procedure, key in Y, then press XMIT. If you don't want to
continue the dialog, key inN, then press XMIT. The SDU operation request
screen is redisplayed.
3. If you keyed in a microcode name that is not contained in $Y$MIC, SDU
displays the following message:
MICROCODE NAME NOT FOUND IN $Y$MIC, ADD AS SHOWN? (Y/N)
Key in Yto add the entry to $Y$SDF. Otherwise, key in N to change the
microcode name. Press XMIT to continue with the SDU operation request
screen.
4. After you complete the insertions on the add screen, press XMIT. The SDU
operation request screen is redisplayed,
5. If you. want to add another device to $Y$SDF, repeat steps 1 through 4 of this
procedure. If you want to perform one of the other SDU functions listed on the
operation request screen, refer to the appropriate procedure.
7004 5505-000 2-25
Post-Software Installation Procedures
Deleting a Bemce from $Y$SDF
Note: Do not perform the following procedure unless you completed the procedures
to review the contents of$Y$MIC and $Y$SDF or are continuing from one of
the other $Y$SDF update procedures.
1.
2.
Key in 2 on the SDU operation request screen, then press XMIT. SDU displays a
listing of all the entries in $Y$SDF. Enter an X next to each entry you wish to
delete. If all the entries do not fit on one screen, press XMIT to display additional
screens until all the entries are shown.
Each entry you select for deletion appears in the following SDU delete operation
screen (Figure 2-12):
SDU
DELETE
OPERATION
DEVICE ADDRESS
HHH
TYPE/FEATURE
mum - mm :
MICROCODE NAME
XXXXXXNN
SERIAL NUMBER
xxxxxxxx
UNIQUE ID
xxxxxxxxxxxxxxx
FCO LEVEL
mum-nun
NOTES
xxxxxxxxxxxxxxx
PCA PART NUMBER
NNNN^NN-NNN
PROM KIT NUMBER/FCO
LEVEL
NNNNNNN-NN NNNN-NNN
IS THIS THE ENTRY YOU
WISH TO DELETE
3. Respond with Y to delete the entry or N to leave it alone.
4. After all the entries you selected for deletion are displayed, the dialog returns to
the SDU operation request screen. You can now perform additional SDU
functions or terminate the SDU utility.
Updating Existing Dewice Information in $Y$SDF
Note: Do not perform this procedure unless you completed the procedures to review the
contents of$Y$MIC and $Y$SDF or are continuing from one of the other
$Y$SDF update procedures,
1. Key in 3 on the SDU operation request screen, then press XMIT. SDU displays a
listing of the entries in $Y$SDF, Enter an X next to each entry you wish to
update. If all the entries do not fit on the first screen, press XMIT to display
additional screens until all the entries are shown.
2-26
7004 5505-000
Post-Software Installation Procedures
2. Each entry you select to update appears in an update screen (Figure 2-13):
SDU UPDATE OPERATION
ENTER NEW INFORMATION (ANALPHABETIC NUMERIC X-ALPHANUMERIC H=HEXADECIMAL)
DEVICE ADDRESS
TYPE/FEATURE
MICROCODE NAME (XXXXXXNN)
SERIAL NUMBER (XXXXXXXX)
UNIQUE ID (XXXXXXXXXXXXXXX)
FCO LEVEL (ZNNNN-NNN)
NOTES (XXXXXXXXXXXXXXX)
PCA PART NUMBER (NNNNNNN-NNN)
PROM KIT NUMBER/FCO NUMBER (NNNNNNN-NN NNNN-NNN}
Figure 2-13. SDU Update Operation Menu
You can update any information except the device address and type/feature
fields.
You specify a cache buffer size to be auto-allocated during disk cache
initialization by updating the microcode name for the cache entry. To do so,
select cache entry CAC8 (type/feature) on the update menu.
Change the microcode name from CAxxOOOO to CAxxnnnn, where xx is the cache
version number (for example, 11 or 12), and nnnn is the cache buffer size in 1024-
byte blocks. The allowable values for nnnn are identical to those that can be
specified at IPL time.
For example, if CA13000 is the microcode name for the cache entry and a 512K
cache buffer size is required, update the microcode name to CA130512.
Note: The specified cache buffer size is used regardless of which supervisor is
used.
If you updated the microcode name, the $Y$MIC file is searched for the new
microcode name. If it is not found, the following message appears:
MICROCODE NAME NOT FOUND IN SY$MIC f UPDATE AS SHOWN (Y/N)
Respond with Y to update the entry. Respond with N to change the microcode
name. Press XMIT to continue with the update function.
After all the entries selected for update are displayed, the dialog returns to the
SDU operation request screen. You can now perform additional SDU functions or
terminate the SDU utility.
7004 5505-000
2-27
Post-Software Installation Procedures
Confirming $Y$SDF
Notez Perform this procedure after you have completed the $Y$SDF add, delete, or
update procedures.
1. Key in 5 or 6 on the SDU operation request screen, then press XMIT. SDU
displays or prints (based upon your entry) the entire contents of $Y$SDF.
2. Check the current entries in $Y$SDF to make sure that you performed the
update properly.
3. If $Y$SDF is not properly updated, repeat the appropriate update procedure.
4. If $Y$SDF is properly updated, key in 9 and press XMIT to display the SDU
termination screen (Figure 2-16).
Dumping $Y$SDF
1. Key in 7 on the SDU operation request screen, then press XMIT. The following
dump screen (Figure 2-14) appears:
SDU DUMP OPERATION
SDU WILL TERMINATE AMD SCHEDULE JOB SDFSAVE -TO DUMP THE $Y$SDF FILE.
ENTER DEVICE TYPE AMD VSN OF THE OUTPUT DEVICE.
DEVICE TYPE _
1. DISKETTE
2. TAPE
3. DISK
VSN
Figyre 2-14. SDU Dump Operation Menu
2. Key in the type and volume serial number of the output device that is to receive
the $Y$SDF dump.
3. Press XMIT. SDU schedules SDFSAVE and automatically continues with the
termination screen (Figure 2-16).
Note: For a description of SDFSAVE, see 2.3.2.
2-28
7004 5505-000
Post-Software Installation Procedures
Restoring $Y$SDF
1. Key in SDU then press XMIT. The SDU operation request screen appears at the
console/workstation.
2. Key in 8 on the SDU operation request screen and press XMIT. The following
restore screen (Figure 2-15) appears:
SDU
RESTORE
OPERATION
SDU
WILL TERMINATE
AND
SCHEDULE JOB
SDFSAVE TO
RESTORE
THE
SYSSDF
FILE.
ENTER DEVICE
TYPE
AND
VSN OF
THE INPUT DEVICE.
DEVICE TYPE _
1. DISKETTE
VSN
2.
TAPE
3.
DISK
Figure 2-15. SDU Restore Operation Menu
3. Key in the type and volume serial number of the input device that $Y$SDF is to
be restored on. Press XMIT.
4. SDU schedules SDFSAVE and the dialog automatically continues with the
termination screen (Figure 2-16).
Note: For a description of SDFSAVE, see 2.3.2.
Terminating SDU
Note: If you initiated a dump or restore operation, proceed to step 2.
1. Key in 9 on the SDU operation request screen. Then press XMIT.
2. If the IDCU microcode was updated for the SYSRES, the following termination
screen (Figure 2-16) appears:
SYSTEM DEFINITION UTILITY
SDU WILL SCHEDULE JOBS PRPMIC AND IMPLDSKT.
PRESS TRANSMIT TO TERMINATE SDU.
Figure 2-16. SDU Termination Screen
7004 5505-000
2-29
Post-Software Installation Procedures
3. Press XMIT and SDU terminates.
Note: IfPRPMIC terminates with errors, reinitiate the job yourself by keying in
the following and then pressing XMIT:
RV PRPMlC,,V=vsn1
where:
vsn1
Is the volume serial number of your SYSRES disk.
4. After the message SDU TERMINATED NORMALLY appears, continue with the
following IMPL and IPL procedures.
Performing IMPL and IPL Procedures
After you finish updating $Y$SDF 5 you must perform initial microprogram load
(IMPL) code and initial program load (IPL) code procedures to continue with system
installation. Perform the following steps:
1. Press the IMPL switch down (toward the AUTO position) and release it. When
the SEQ1, SEQ2, and SEQ3 lights go off, the IMPL procedure is complete.
2. Press ESC, then press the M key. The following screen (Figure 2-17) appears:
ENTER.
PROG 1CADC8-BFF)
CONTROL
N NORMAL
U RUN
C CLEAR
Q STOP
G NORMAL (NO RESET)
R OPER RECOVERY(0-BFF)
RESET
L SYSTEM
B BPU
ADR STOP(0-FFFFFFFF)
COMPUTE CTRL
M NORMAL
P NORMAL
I STOP I A
S STEP
A STOP ANY
CHECK CTRL
T TRACE
H NORMAL
K STOP
W SENSE SW(0000-1111)
-8008-
V STORE STATUS
Figure 2-17. System Operations Menu
2-30
7004 5505-000
Post-Software Installation Procedures
3. Press the L key (SYSTEM) and then press XMIT to reset the system. The screen
continues to be displayed.
4. Press the N key (NORMAL) and enter the device address (did) of the IPL disk.
5. Press XMIT. (The IPL screen is displayed.)
6. Key in:
SY#BAS,S,did
or
SY$BAS f S f did
where:
SY#BAS
Specifies the starter supervisor for model 8.
SY$BAS
Specifies the starter supervisor for models 10 through 20.
Specifies the option for loading a supervisor.
did
Specifies the device address of your SYSRES disk.
7. Press XMIT.
8. The following date/time screen (Figure 2-18) appears:
A)
DATE: YY/MM/DD TIME HH:MM:SS
B)
RUN LIBS DVC ADDR: XXX (SYSRES)
C)
FILE RECOVERY
JOB QUEUE (N,Y,H DEFAULT=N)
ERROR LOG (N, Y DEFAULT=Y)
SPOOL FILES (N,A,C f L,H DEFAULTS)
D)
MODIFY SUPERVISOR: DEFAULT=N
E)
SPOOLING DVC ADDR: XXX (SYSRES)
F)
DUMP FILE DVC ADDR? (DEFAULT=XXXXXX) __
TRANSMIT TO ENTER DEFAULTS. OTHERWISE ENTER THE LETTERS OF THE PARAMETER(S)
TO BE CHANGED.
Figure 2-18. System Date/Time Display
9. Press XMIT to accept the defaults supplied by the system.
7004 5505-000
2-31
Post-Software Installation Procedures
After a short wait 3 the system displays header messages indicating OS/3 version
number, supervisor name, date, and time. The system is now ready for you to
perform your next installation task - either installing optional software or
performing system generation.
Note: If you are not installing optional software or generating your own
supervisor, your system is now ready for use.
2.3.2. Copying and Restoring $Y$SDP
If you are installing a new release, you can make a copy of your old $Y$SDF file and
later restore It to your new SYSRES with the job stream SDFSAVE. This job stream
lets you copy $Y$SDF from your old SYSRES to any of the following types of media:
• Single-sided, single-density diskette
• Tape
• Another disk volume (other than your SYSRES)
If you use diskette or tape, SDFSAVE preps the media and allocates a file to contain
the copied version of $Y$SDF. If you use another disk volume, you must prep this
volume and allocate a file for $Y$SDF yourself.
After you install your new release, run SDFSAVE again to restore $Y$SDF from the
diskette, tape, or disk media to your SYSRES volume. You do not have to completely
re-create $Y$SDF each time you install a new release.
To run SDFSAVE, mount the media you are copying to or restoring from and enter the
following command at your system console:
RV SDFSAVE
These messages appear on the console screen, along with the responses you must
enter when running SDFSAVE:
• ENTER THE APPROPRIATE FUNCTION (DUMP OR RESTORE)
Enter DUMP If you want to make a copy of $Y$SDF or RESTORE if you want to
restore $Y$SDF to your SYSRES,
• THEN ENTER THE DEVICE TYPE (DISK, DISKETTE, or TAPE)
Enter the type of media you are copying to or restoring from.
• THEN ENTER THE VOLUME NAME FOR THE GIVEN DEVICE TYPE
Enter the volume serial number of the media you are copying to or restoring
from.
2-32 7004 5505-000
Post-Software Installation Procedures
WHEN DUMPING TO TAPE OR DISKETTE THE VOLUME NAME WILL BE USED FOR THE PREP
This is the last message displayed. Respond to it by pressing XMIT. SDFSAVE
then performs the copy or restore function you specified.
2=3.3. Creating an IMPL System Microcode Diskette
Model 8
On the model 8 the FDDODSKT job stream creates two identical diskettes that you
can mount in the FDD 0# diskette drive to perform an initial microprogram load to the
system. You can use these diskettes as backups to the system IMPL diskette that is
sent with the system or plateau level You must run this job each time you update the
$Y$SDF file as a result of adding new BPU, SVP, or IOMP microcode to your system.
You can then insert one of the diskettes you created in the FDD 0# diskette drive and
re-IMPL your system. (See the Operations Guide, 7004 5208, for the IMPL procedure.)
To create the IMPL diskettes, you must have two single-sided, single-density
diskettes. Mount one of the diskettes and enter the following command:
RV FDD0DSKT[ , , VSN1-xxxxxx # VSH2=xxxxxx]
where:
XXXXXX
Specifies the VSN of each diskette. If the diskettes are not prepped, the
program supplies default VSNs.
The job creates one IMPL diskette and then displays a mount message requesting
another diskette. Remove the first diskette from the drive and mount the second
single-sided, single-density diskette. The job then creates a second IMPL diskette.
Notez You must ensure that the diskettes you use do not have any bad tracks. If the
program encounters bad tracks on a diskette, it terminates abnormally and
you must use another diskette.
Models 10 through 20
On the models 10 through 20 the FDDCOPY job stream creates a microcode diskette
that you can mount in the FDD 0# drive and perform an initial microprogram load to
the system. You should run this job to create a backup IMPL diskette when one of
your IMPL diskettes sent with the system or plateau becomes defective. The IMPL
microcode modules (BPU, SVP, IOP, and USEL) are not needed in the $Y$SDF and
$Y$MIC files because the FDDCOPY job does not access these files, but does a direct
copy from the FDD 0# drive to the DMUX drive diskette.
7004 5505-000 2-33
Post-Software Installation Procedures
To create an 1MPL diskette, mount a double-sided diskette and enter the following
command:
RV FDDCOPY
After you respond to the diskette mount message, the job preps the diskette and then
copies the FDD 0# diskette to the DMUX diskette. The FDD controller has limited
functions when compared to the DMUX diskettes. This results in slower access time.
The FDDCOPY job runs in approximately 15 minutes. When the job is finished, you
can mount the diskette in the FDD 0# drive and re-lMPL the system.
2.3.4. Creating an IDCU Microcode Diskette
The IMPLDSKT job stream creates a backup IDCU microcode diskette. Run this job
when a new IDCU microcode is added to your system.
To create an IDCU diskette, mount a diskette and enter the following command:
RV IMPLDSKT„CU=n
where:
Is the control unit address of the IDCU disk. The control unit address must
end with zero. For example, the device address of 292 has a control unit
address of 290 (CU=290).
2.3.5. Restoring Modules Sawed from a Pre¥ious Release
If you saved any of your own software on another set of diskettes or on disk before you
installed the new release software, copy it back to your updated SYSRES. Use the
same system facility that you used originally to prepare the copies of your software.
• Use the system librarians, LIBS and MLIB, to restore your program modules to
system libraries (including source modules that contain SYSGEN parameter sets
still valid with the updated release). See the System Service Programs Operating
Guide, UP-8841, for the details to perform this operation.
• Restore your program library files and data files onto SYSRES using the
SG@RUFIL job stream described in 3.3.8 for restoring a backup copy of your
SYSRES.
2~34 7004 5505-000
Post-Software Installation Procedures
2.3.6. Verifying System Installation
To verify that you installed your software correctly and completely, use the
installation verification procedures (TVPs). Verify software using the Installation
Verification Procedures Operating Guide, 7004 5232.
Note: Those TVPs that require specific SYSGEN options will not run until after you
generate those options. In these instances, perform the TVPs for those products
after system generation.
23.7. Performing System Generation
Before you can use your system effectively, you must make sure that it contains the
necessary system control elements to satisfy your processing needs. To generate those
elements, use the OS/3 SYSGEN procedures. Section 3 describes the system
generation process in detail
7004 5505-000 2-35
Section 3
3.1. Considerations
The OS/3 operating system must contain the necessary system control elements to
operate effectively and satisfy your processing requirements. These elements must
reflect the system's hardware configuration. To create these elements and to define
the system's hardware configuration to OS/3 3 Unisys provides system generation, or
SYSGEN.
SYSGEN lets you generate four types of elements. They are:
1 . Supervisor elements
2. Nine-thousand-remote (NTR) elements
3. ANSI 74 or '85 COBOL elements
4. Communications (ICAM) elements
Whichever element you generate, the procedure for performing SYSGEN is the same.
Basically, it consists of the following three steps:
1 . Preparing the SYSGEN parameter sets
2. Processing the SYSGEN parameter sets
3. Running the SYSGEN job control streams
Perform SYSGEN once for each control element that you want to create or once to
build any combination of the supervisor, NTR, and ANSI 74 or '85 COBOL elements
that you want. However, to build an ICAM element, you must perform the three steps
of the SYSGEN procedure independently of any other control elements.
SYSGEN is designed this way for two reasons.
First, initial users can build all their control elements (excluding ICAM) in one
SYSGEN operation.
Second, it allows existing users to add control elements, if necessary, whenever they
add new components to their systems. Table 3-1 lists all the optional products that
OS/3 offers; it indicates which control elements you must generate (or regenerate, if
need be) to use these optional products. Each of the four SYSGEN control elements is
defined as required (R), not required (NR), or optional (O).
7004 5505-000 3-1
System Generation
For example, if you just Installed the extended system software for the purposes of
using spooling and job accounting, regenerate the supervisor to support the spooling
and job accounting products. However, you are not required to generate any other
control elements to use these optional products.
If specific SYSGEN requirements exist for any optional software, such requirements
are documented in the appropriate manuals in the OS/3 library.
The first step in performing SYSGEN is preparing the SYSGEN parameter sets, if you
are Installing a new OS/3 release, you can bypass this step. Remember to save copies
of the SYSGEN parameter sets before you install the new software and designate
these saved modules as Input to the parameter processor. See 3.2.2 for more
information on supplying parameter sets to the parameter processor.
After you complete any SYSGEN operation and before you use the system, you must
perform the appropriate post-system generation procedures, described in 3.3.
Also, if your printer does not have the OS/3 default printer characteristics, you must
define its characteristics to the system before you can perform any system generation
procedure. See 3.3.4 for a detailed description of the OS/3 default printer
characteristics and the procedure for defining alternate printer characteristics.
Table 3-1. Control Element Generations for Optional Software
OS/3 Control Elements
ANSI "74
OS/3 Optional Products
Supervisor
COBOL
NTR
I CAM
Extended System Software (ESS)
R
NR
NR
NR
Data Utility
NR
NR
NR
MR
Sort/Merge
MR
NR
NR
NR
S0RT3
NR
NR
NR
MR
Spooling and Job Accounting
R
NR
NR
NR
Screen Format Generator (SFG)
MR
NR
NR
NR
Dialog Specification Language Translator (DSLT)
NR
MR
NR
MR
IMS - Multithread*
R
NR
NR
R
DMS
NR
NR
NR
NR
RPG Group
NR
NR
MR
NR
RPGII
NR
NR
MR
NR
RPGEDIT
NR
NR
NR
NR
RPG Auto Report
NR
NR
MR
NR
COBOL -' 74
NR
NR
NR
COBOL- "85
NR
NR
NR
If you installed IMS, you must perform an IMSGEN as a post-SYSGEN procedure.
See the IMS System Support Functions Programming Guide, UP- 11987.
continued
3-2
7004 5505-000
System Generation
Table 3-1. Control Element Generations for Optional Software (cont.)
OS/3 Control Elements
ANSI '74
OS/3 Optional Products
Supervisor
COBOL
NTR
I CAM
COBOL Editor
NR
NR
NR
NR
FORTRAN IV™
NR
NR
NR
NR
FORTRAN 77
NR
NR
NR
NR
Pascal
NR
NR
NR
NR
BASIC
NR
NR
NR
NR
ESCORT™
NR
NR
NR
NR
MAPPER 80
NR
NR
NR
NR
S889728-DSK
R
NR
NR
NR
Editor
NR
NR
NR
NR
Menu Generator
NR
NR
NR
NR
Assembler
NR
NR
NR
NR
Sort/Merge
NR
NR
NR
NR
S0RT3
NR
NR
NR
NR
ICAM-TSF
R
NR
NR
R
NTR
R
NR
NR
R
DCA Termination Systems
R
NR
NR
R
IBM R 3270 RDH
R
MR
NR
R
IBM 3270 Emulator
R
NR
NR
R
RTP (HASP) Facility
R
NR
NR
R
ESCORT is a trademark of Unisys Corporation,
FORTRAN IV is a registered trademark of SuperSoft Associations.
IBM is a registered trademark of International Business Machines Corporation.
continued
7004 5505-000
3-3
System Generation
Table 3-1. Control Element Generations for Optional Software (cont)
OS/3
Control Elements
ANSI «74
OS/3 Optional Products
Supervisor
COBOL
NTR
I CAM
DATEX-L PDN Support
R
NR
MR
R
DATEX-P
R
NR
NR
R
TRANSPAC
R
NR
NR
R
DATAPAC
R
NR
NR
R
DDX-P
R
NR
NR
R
NORDIC- PDN
R
NR
NR
R
IBERPAC
R
NR
NR
R
PSS PDN
R
NR
NR
R
DDP Transfer Facility
R
NR
NR
R
DDP File Access
R
NR
NR
R
DDP IMS Transaction Processor
R
NR
NR
R
Conversion Aids
NR
NR
NR
R
UTS488 L/D Terminal Package
R
NR
NR
R
UTS488 COBOL
R
NR
NR
R
UTS408 Edit Processor
R
NR
NR
R
System Activity Monitor
R
NR
MR
R
On-line Diagnostics
NR
NR
NR
R
Legend:
NR = not required
R = required
= optional
3.1.1. Supervisor Elements
All systems must contain at least one supervisor element. Supervisor elements
identify supervisor services and processing options that you want employed in your
system. They also describe your system's hardware configuration to the operating
system.
M
7004 5505-000
System Generation
Supplied Starter Supervisors
OS/3 supplies a starter supervisor, SY#BAS for model 8, and SY$BAS for models 10
through 20, as part of the system control software. This starter supervisor satisfies
most System 80 user processing needs. It eliminates the need to perform a SYSGEN
operation unless there is a specific reason to do so.
Use the starter supervisor as your operating supervisor and bypass SYSGEN until you
are more familiar with OS/3 and have learned which SUPGEN features would
improve your system's performance. Then, you can perform SYSGEN to create a
supervisor tailored to your specific needs. Remember, even if you do not perform
SYSGEN, do the post-generation procedures that apply to you.
Tables 3-2 and 3-3 list for all models:
• The starter supervisor features
• Specific capabilities of the starter supervisors
• The input/output (I/O) device configurations that the starter supervisors support
. Notes
1. When you are booting starter supervisors SY#BAS and SY$BAS, the IPL process
(when necessary) dynamically reconfigures the SYSRES disk to the proper device
type regardless of the PUB specification, provided that a PUB is generated for that
address.
2. During the IPL sequence, the SYSRES device is dynamically reconfigured to the
proper TYPE /SUBTYPE regardless of the TYPE=xxxx specification in the
SYSGEN process. The reconfiguration will only occur on disk addresses of the
supervisor being loaded.
User-Generated Supervisors
If you are going to access any devices not included in the I/O configuration supported
by SY#BAS, SY$BAS, or your present supervisor, you must generate a supervisor to
support them. Do this by reconfiguring the I/OGEN to include all devices desired.
Also, if your system includes the integrated communications access method (ICAM)
terminal support facility or a nine-thousand remote (NTR) system utility, you must
generate your own supervisor to support them.
If you use the starter supervisor, do not specify devices for RUN LIBS DEV ADDR or
SPOOLING DEV ADDR on the system installation time/date screen if your disks are
physically co-channeled 2 and 3 on model 8 or 1 and 2 on models 10 through 20.
7004 5505-000 3-5
System Generation
Table 3-2. SY#BAS (Model 8)
SUPERVISOR
FEATURES
24 job slots
Spooling*
5 switching priorities
System Activity Monitor
1CAM support of Local workstations
Console logging
Job accounting*
Job queue recovery at I PL time
SPECIFIC CAPABILITIES
Transient areas - 5
Error logging buffers - 6
Resident modules - SMSLOCK, SM$STXIT,
Dynamically allocated load
SMSTASK, SMSASCKE,
buffers - 7 blocks
SH$ATCH # SMSGTPUT
Dynamically allocated
Spool file size* - 25 cylinders
load table entries - 7 per job
Spool file bit map* - 64 words
Spool buffer* - 8 blocks
Spool output writer buffer* - 8 blocks
Resident shared code modules -
DM$CFM, D3SM111, DM$W111, PRSIOE
Shared data management
modules - 88, 24-byte slots
System security administrator
name - SYSADM
Expansion region - 4096 bytes
1/0 DEVICES
1 - SOMA printer (C38)
4 - 8433 disks (380, 381, 288, 281)
7 - 8778 printers (004, 085, 1B0, 1E0,
12 - 8417 disks (3B8-3B5, 2B0-2B5)
1F0, 2E0 } 2F8)
4 - 8419 disks (3B6, 3B7, 2B6, 2B7)
1 - 8719 reader (C32)
4 - 8428/22 diskettes (C28-C23)
1 - 0716 reader (806)
1 - 3568 workstation (C12)
16 - 8494J8418 disks <3A0~3A7, 2A0-2A7)
1 - 3561 workstation <C18)
16 - 8478 disks (398-397, 298-297)
* Your system disables spooling and job accounting at IPL time if your system does
not include them.
Note: All printers are generated with LCB=0WNLC1.
3-6
7004 5505-000
System Generation
Table 3-3. SY$BAS (Models 10 through 20)
SUPERVISOR
FEATURES
24 job slots
Spooling*
5 switching priorities
System Activity Monitor
ICAM support of local workstations
Console logging
Job accounting*
Job queue recovery at I PL time
SPECIFIC CAPABILITIES
Transient areas - 5
Error logging buffers - 6
Resident modules - SM$L0CIC, SM$STXIT,
Dynamically allocated load
SM$TASK, SMSASCKE,
buffers - 7 blocks
SMSATCH, SM$GTPUT
Dynamically allocated
Spool file size* - 25 cylinders
load table entries - 7 per job
Spool file bit map* - 64 words
Spool buffer* - 8 blocks
Spool output writer buffer* - 8 blocks
Resident shared code modules -
DMSCFM, D3SM111, DMSW111, PR$I0£
Shared data management
modules - 88, 24-byte slots
System security administrator
name - SYSADM
Expansion region - 4096 bytes
I/O DEVICES
1 - SOMA printer (C30)
4 - 8433 disks (280, 281, 180, 181)
3 - 8778 printers (398, 2E8 f 1E8)
12 - 8417 disks (1B0-1B5, 2B0-2B5)
1 - 8776 printer (3B8)
4 - 8419 disks <1B6, 1B7, 2B6, 2B7)
1 • 8719 reader (C32)
4 - 8420/22 diskettes (C28-C23)
1 - 8716 reader (3A0)
1 - 3560 workstation (C12)
16 - 8494 disks (1A0-1A7, 2A0-2A7)
1 - 3561 workstation (C18)
16 - 8478 disks (198-197, 298-297)
1 - 1122 workstation (C14)
* Disabled at IPL time if your system does not include this feature.
Note: All printers are generated with LCB=0WNLC1.
7004 5505-000
3-7
System Generation
You can generate any number of supervisor modules for the system, but only four in
one SYSGEN operation. No matter how many you generate, you must make sure that
you give each one a different name. When you actually begin processing, only one
supervisor can be active at one time.
If you don't specify a name for a supervisor module you are generating the SYSGEN
parameter processor assigns it the default name SY$STD. You should use this default
value for the supervisor you expect to use most frequently, by putting it in the
configuration file ($Y$CONFIG). Then you will boot your most common supervisor
every time you perform an auto-IPL. See 3.3.2 for additional information.
The Supervisor Technical Overview, UP-8831, fully describes the SYSGEN supervisor
options. Review them thoroughly before generating any supervisor modules.
Superwisor Maintenance Considerations
When you want to delete a supervisor to conserve SYSRES space, use the delete
(DEL) and pack (PAC) functions of the system librarian (LIBS). See the System
Service Programs Operating Guide, UP-8841.
When you delete an unwanted supervisor and its associated I/O configuration module,
you must also delete the two modules from both the system load code library
($Y$LOD) and the system source code library ($Y$SRC).
When you delete an unwanted supervisor from $Y$SRC, you must prefix the name of
the unwanted supervisor with S$. When you delete the I/O configuration module for
an unwanted supervisor from $Y$SRC, you must prefix the name of the unwanted I/O
module with 1$. For example, if the name of your unwanted supervisor is MYSUP1,
specify to the librarian that you want to delete both the supervisor module named
S$MYSUP1 and the I/O module named I$MYSUP1 from $Y$SRC.
3.1.2. Nine-Thousand-Remote (NTR) Element
An NTR element defines a nine-thousand-remote system utility and is required only if
the system contains the optional NTR component. This component gives you the
capability to use a Unisys System 80 Data Processing System as a remote device to a
Unisys 1100 Data Processing System.
An NTR element includes two types of parameters: NTR parameters and LOCAL
parameters. NTR parameters define the general characteristics of the NTR element
that you are generating. In one SYSGEN, you can prepare only one set of these
parameters because they apply to the entire NTR system.
3-8 7004 5505-000
System Generation
LOCAL parameters define the specific remote device handlers used with the NTR
element you are generating. In one SYSGEN, you can include up to 14 sets of LOCAL
keywords. Each one is unique but related to the set of NTR parameters that you
defined.
For more information about the capabilities and operation of NTR, see the NTR
Utility Programming Guide, UP-9502, before attempting to generate an NTR element.
3.1.3. COBOL Element
A COBOL element defines processing options for the 1974 American Standard or 1985
American Standard COBOL compiler. You are required to generate one only if two
conditions exist:
1. Your system contains a COBOL compiler.
2. You want to specify processing options different from the compiler's default
values.
By default, the compiler supplies various processing options that create a usable
compiler; therefore, you have no need to generate a COBOL element unless you need
to specify option values other than the default values.
For complete details about the applicable COBOL compiler, see the 1974 American
Standard COBOL Programming Reference Manual, 7004 4490, or the 1985 American
Standard COBOL Programming Reference Manual, 7002 3940.
3.1 A Communications (ICAM) Elements
ICAM elements define the communications services that you want in the system. They
are required only if the system uses the ICAM terminal support facility or the
information management system (IMS), both of which are optional OS/3 components.
They are also required when you want to configure a communications network with
workstations acting as your terminals.
You can generate as many as 18 different ICAM symbionts for use in the system; but
you must create each one in a different SYSGEN operation, and only one ICAM
symbiont can be active in the system at a given time.
OS/3 divides the ICAM parameters into two types: network definition parameters and
message control program (MCP) parameters.
Network definition parameters define the modules that ICAM needs to operate, and
they create a communications control area (CCA). You supply these parameters to the
parameter processor in the form of ICAM macroinstructions. The ICAM Operations
Guide, 7004 4557, describes the ICAM network definition requirements and
macroinstructions. Refer to that guide before attempting to configure an ICAM
element.
7004 5505-000 3-9
System Generation
Message control program parameters specify the name of the ICAM element, the disk
volume where you want the system to store it, and the characteristics of each
communications line In the system.
When you generate a communications element, be sure that the SYSGEN parameter
processor provides correct default substitutions for the specific ICAM element that
you want to generate.
3.1.5. Resource Management
OS/3 provides an optional facility, resource management, which enables the
configuration of resource management capabilities. Factors that can be controlled are:
• The maximum percentage of main storage available for:
Symbionts
- Interactive jobs
- Batch jobs
Note: The sum of the percentages can be greater than 100%, in which case the
overlapping portion would be available on a first-come, first-served basis.
m The maximum number of:
- Total jobs
- Jobs initiated from all workstations
- Jobs initiated from any single workstation
- Logged-on interactive users
Batch tasks initiated with the ENTER command
- Concurrently executing run symbionts
The following subsections provide examples of how the resource management
capability might be used. Note that the RESMGT keyword parameter is defined in
Table 4-1.
3-10 7004 5505-000
System Generation
Resource Management Batch System Configuration
Table 3-4 presents an example of how the resource management feature might be set
up in a heavily batch-oriented system.
Table 3-4. Resource Management Elements for a Batch-Oriented System
Element
Maximum
User storage avai table for
batch jobs
80%
User storage available for
interactive jobs
10%
Total number of batch jobs
20
Workstation batch jobs scheduled
from workstations
10
Number of batch jobs that can be
scheduled from any single workstation
1
Number of concurrently executing
run symbionts
3
For the configuration defined in Table 3-4, a supervisor would be generated with the
following parameters:
Phase
Parameter
SUPGEN
SUPVRMAM = SYSSTD
JOBSLOTS = 25
RESMGT = YES
JOBMEM = 80
INTMEH = 10
MAXJOBS = 20
MAXWSJOBS = 10
HAXSWSJOBS - 1
RUNSYMBS = 3
END
7004 5505-000
3-11
System Generation
Resource Management Interactive System Configuration
Resource management In a heavily interactive environment can be set up as shown in
Table 3-5.
Table 3-5. Resource Management Elements for an Interactive System
Element
Maximum
User storage available for;
• Interactive jobs
i Batch jobs
80%
20%
Total number of workstations logged on
30
Total number of batch tasks that can
be initiated from a workstation with
an ENTER command
20
Total number of batch jobs
5
Batch jobs scheduled from a workstation
2
Batch jobs that can be scheduled from
any single workstation
1
Number of concurrently executing
run symbionts
3
For the configuration defined in Table 3-5, a supervisor would be generated with the
following parameters:
Phase
Parameter
SUPGEN
SUPVRNAM = SY$STD
JOBSLOTS = 25
TIMER - MAX
RESMGT = YES
*
JOBMEM = 20
IMTMEM - 80
ISINTLMT = 30
ISBATCHLMT = 20
MAXJOBS = 5
MAXWSJOBS = 2
MAXSWSJOBS = 1
RUNSYMBS = 3
END
3-12
7004 5505-000
System Generation
Resource liarnagemeiif ilkecf System Coofiigyration
If the system is used for both batch and interactive processing, up to 70 percent of
variable storage can be allocated for both (batch and interactive) types of jobs. The
STATUS command and the console operation log are useful tools for determining
what percentages of variable storage to allocate for each job category.
If 70 percent of the variable storage is available for both batch and interactive jobs, a
supervisor would be generated with the following parameters:
Phase Parameter
SUPGEH SUPVRNAM = SYSSTD
JOBSLOTS = 25
TIMER = MAX
*
RESMGT = YES
JOBMEH = 70
1MTMEM = 70
1SINTLMT - 2®
ISBATCHLMT = 20
HAXJOBS = 12
HAXWSJOBS = 5
HAXSWSJOBS = 1
RUNSYMBS
Em
7004 5505-000 3-13
System Generation
3.2. Procedures
The following procedures let you:
• Prepare SYSGEN parameter sets for all users who did not prepare or save
SYSGEN parameter sets for all the elements that their systems require
• Process SYSGEN parameter sets
• Run the SYSGEN job control streams on processed SYSGEN parameter sets
You must perform all three procedures to create a system control element.
3.2.1. Using SYSGEN Dialog to Prepare Parameter Sets
The following paragraphs describe the procedure for preparing the SYSGEN
parameter sets using the SYSGEN dialog. Unisys supplies the SYSGEN dialog that
lets you easily prepare your parameter sets. You can also prepare the SYSGEN
parameter sets without the aid of the SYSGEN dialog (see Section 4), but the
SYSGEN dialog minimizes the risk of preparing invalid parameter sets. Only the most
experienced SYSGEN users should use alternate methods. If you prepare your sets
using an alternate method, you must process them using the procedure for manually
executing the parameter processor in 3.2.2.
Note: To perform this procedure, you need to install the system, control software and
perform an initial program load procedure to load either the starter
supervisor (SY#BAS or SY$BAS) or one that you've generated yourself.
Prepare the SYSGEN parameter sets by using the SYSGEN dialog as follows:
1. Determine which system control elements you need in the system according to
the information in 3.1. Table 3-1 lists all the optional components that OS/3 offers
and shows which control elements you need to support them.
2. At your console/workstation, enter the workstation mode by simultaneously
pressing the FUNCTION key and the workstation mode key (WS MODE) to
display the OS/3 LOGON request screen:
000000
SSSS
/
333
00000000
ssssss
//
33333
00 00
ss
///
33 33
00 00
ss
///
33
00 00
ss
///
33
00 00
ss
///
333
00 00
ss
///
33
00 00
ss ss
///
33 33
00000000
ssssss
//
3333333
000000
SSSS
/
3333
INTERACTIVE
OPERATING SYSTEM
DEPRESS TRANSMIT FOR LOGON
3-14
7004 5505-000
System Generation
3. Press XMIT to display this LOGON menu:
OS/3 INTERACTIVE SERVICES
LOGON IDENTIFICATIONS USER- ID
> <
ACCOUNT NUMBER
> <
PASSWORD
> <
OPT IONS : EXECUTION PROFILE
> <
BULLETIN
>YES <
LOG
>YES <
5.
Fill in the applicable fields. If you are an initial user, fill in the USER-ID field
(your user-id cannot exceed six characters) and press XMIT. If you are an existing
user operating under a supervisor that includes interactive security, fill in the
menu screen as the Interactive Services Operating Guide, UP-9972, describes.
Either action causes the system to display a message informing you that it
accepted your user-id and the system bulletin is also displayed.
Enter system mode by simultaneously pressing the FUNCTION key and the
system mode key (SYS MODE).
Note: If you are performing this procedure at a remote communications terminal,
be sure the terminal contains the field-protect feature; otherwise, you will
encounter errors.
Allocate the file that will hold the audit file version of this dialog session by
keying in:
AL MI f FILsfilenaine,VSN=volume ( SI=2
where:
MI
Specifies that the audit file is a MIRAM file.
FIL=filename
Is the file label that you assign to the audit file.
VSN=volume
Specifies the volume serial number of your disk that will contain the
audit file. If you are using the SYSRES for the audit file, this value is
always RELxxx, where xxx is the release level of your software. For
example: REL140.
si=2
Is the size, In cylinders, of the audit file.
7. Press XMIT.
7004 5505-000
3-15
System Generation
8. If you are preparing parameter sets for the supervisor, NTR, or COBOL
elements, execute the SYSGEN dialog by keying in:
RV SGSBLD
If you are preparing parameter sets for the 1CAM element, execute the ICAM
portion of the SYSGEN dialog by keying in:
RV ICSBLD
9. Press XMIT. This response causes the dialog to display a short paragraph
explaining RUN libraries.
10. When the message DO YOU WANT TO SAVE RUN LIBRARY? (Y OR N)
appears, key in N for no.
1 1 . Press XMIT. When you see the message ARE YOU CREATING A NEW AUDIT
FILE (Y/N)?, key in Y for yes.
12. Press XMIT. When you see the message ENTER VSN OF DISC CONTAINING
NEW AUDIT FILE, key in the volume serial number.
13. Press XMIT. When you see the message ENTER FILE LABEL OF NEW AUDIT
FILE, key in the file label of the file that you allocated in step 6 to hold the audit
file version of your dialog session.
14. Press XMIT. When you see the message ARE YOU AUDITING AN OLD AUDIT
FILE? (Y/N), key in N for no.
15. Press XMIT. The dialog then displays the message DIALOG PROCESSOR
READY to inform you that it is ready to help you prepare the SYSGEN
parameters. Then, it asks what type of system you are using.
16. When you see the message WHAT TYPE OF SYSTEM ARE YOU
GENERATING?, key in 2 for model 8 or 3 for models 10 through 20.
17. Press XMIT. The dialog displays the message HOW MANY IOMPS DOES YOUR
MODEL HAVE? Key in 2 or 3. If you need HELP, key in 4.
18. Press XMIT. The dialog displays a short definition of the SYSGEN dialog.
19. When you see the paragraph titled either PROGRAM=DIALOG FOR SYSTEM
GENERATION or PROGRAM=DIALOG FOR ICAM GENERATION, key in
HELP and press XMIT. The dialog then displays a description of the dialog
method for preparing SYSGEN parameters.
3-16 7004 5505-000
System Generation
20. After you've read the description of the dialog method, press XMIT. The dialog
then displays the master menu screen shown here. Through the master menu
screen, you can select SYSGEN phases that correspond directly to control
elements that you need to generate.
SELECT THE SYSGEN PHASE TO
BE PREPARED:
1.
SUPERVISOR GENERATION
CSUPGEN and
I0GEN)
2.
COBOL COMPILER OPTIONS
SPECS (COBGEN)
3.
NTR UTILITY GENERATION
CNTRGEN)
4.
NO FURTHER PHASE REQUIREMENTS
5.
DISPLAY PHASE DESCRIPTIONS
CENTER PHASE NUMBER OR
'ALL')
EN*
FER CHOICE BY NUMBER
....
If you are building the ICAM control element, the dialog bypasses the master
menu screen and goes directly to the COMMCT phase. This is where you prepare
all necessary parameters for generating an ICAM element. When you have
completed the parameter specifications, the SYSGEN dialog displays the
message DIALOG SESSION TERMINATED NORMALLY. Press XMIT. The
dialog then displays a message asking if you want to execute the parameter
processor. At this point, proceed to step 24.
21. Each time you see the master menu screen, choose one of the selections to
prepare parameter sets for all the control elements you must generate:
• To perform the SUPGEN and IOGEN phases, key in 1 and press XMIT.
These phases let you prepare all the necessary parameters to generate a
supervisor control element and define your hardware configuration to OS/3.
When you key in 1, the SYSGEN dialog displays screens requesting which
services and facilities you want in the supervisor. Next, it displays menu
screens that let you define your hardware configuration to OS/3. When
specifying these devices, you do not have to define all devices In the same
category at the same time. For example, you can define the disk device
containing the SYSRES volume first, followed by your printers,
workstations, and other disk devices. You should define each I/O device In
the order of most frequent use to reduce I/O access time during later
processing.
When it requires no other information from you, the dialog redisplays its
master menu screen.
7004 5505-000
3-17
System Generation
• To select the COBGEN phase, key in 2 and press XMIT. This phase lets you
generate an ANSI 74 or '85 COBOL element. The dialog displays only those
screens that pertain to the COBOL element and then redisplays the master
menu screen.
• To select the NTRGEN phase, key in 3 and press XMIT. This phase lets you
prepare the necessary parameters for generating an NTR element in the
system. The dialog displays only those messages concerning NTRGEN, then
redisplays its master menu screen.
• To complete the dialog session after all control element parameter sets are
prepared, key in 4 and press XMIT.
• To read descriptions of each of the SYSGEN phases, key in 5 and press
XMIT. After it displays these phase descriptions, the dialog redisplays its
master menu screen.
22. After you respond to the master menu screen, the SYSGEN dialog guides you
step by step through the SYSGEN parameter sets for the phases you select. As
you proceed through the dialog, press XMIT to go on to subsequent screens.
You may need to refer to Tables 4-1 through 4-5 for specific SYSGEN parameter
information. These tables give you guidelines and formulas for specifying
particular SYSGEN parameters.
To omit a parameter from your sets while using the dialog, you must replace the
enter field for that parameter with either underlines or spaces. For parameters
that have only numeric values, you must use spaces since the underline character
is not a numeric character and is rejected by the system. On ICAM terminals, use
a destructive space bar by putting (SP/DS) in the last field on the control page.
If you need more information about a parameter, request help by keying in the
choice that gives a HELP screen or by keying in HELP in the space provided. If a
parameter does not concern you, simply press the TAB FORWARD key to ignore
it and the system automatically provides a sufficient default value for you. As
you proceed through the dialog, press XMIT to go on to subsequent screens. Then,
when you reach the bottom of the screen, press XMIT. (When specifying your
hardware configuration to OS/3, be sure to specify a device category parameter
and a type parameter for each device, whether you want to accept the default
values for that device or not. Otherwise, OS/3 generates the supervisor without
an I/O configuration for that device.)
Each time you complete the parameter specifications for a single phase, the
dialog redisplays its master menu screen until you respond to it with choice 3.
23. When you key in 4 to inform the dialog that you've completed your session, the
SYSGEN dialog displays the message DIALOG SESSION TERMINATED
NORMALLY. Press XMIT. The dialog then displays a message asking whether
you want it to execute the parameter processor.
3-18 7004 5505-000
System Generation
24. When the message DO YOU WANT TO EXECUTE THE PARAMETER
PROCESSOR AGAINST DIALOG OUTPUT? (Y OR N) appears, key in Y and
press XMIT if you want to proceed with the SYSGEN process. However, if you
want to review your parameter sets, or if (because of time limits) you do not want
to execute the parameter processor, key in N and press XMIT. Either response
displays a message (step 25) asking you where you want your dialog output
stored.
25. When the message ENTER A 1-8 CHARACTER NAME FOR THIS OUTPUT
MODULE appears, press XMIT if you want to accept the default module name.
The dialog stores the supervisor, NTR, and COBOL parameter sets as a module
named SG$INPUT or the ICAM parameter set as a module named IC$INPUT on
$Y$SRC. If another dialog parameter set already exists with the module name
SG$INPUT or IC$INPUT and you want to keep that set, key in an alternate one-
to eight-character name for your new module and press XMIT.
Note; After responding to step 25, your next action depends on your response to
step 24. If you keyed in Yin step 24, go to "Automatic Execution of the
Parameter Processor" in 3.2.2. If you keyed in N in step 24, the dialog
stores your sets under the module name that you specified in step 25 and
then terminates. In this case, proceed to "Manual Execution of the
Parameter Processor" in 3.2.2.
3.2.2. Processing the SYSGEN Parameter Sets
This subsection presents the procedures for processing the SYSGEN sets either by
automatically or manually executing the parameter processor (SG$PARAM). Which
method you use depends, primarily, on how you prepared your sets.
You can automatically execute the parameter processor at the end of the dialog
session. At that time, the parameter processor is run against the dialog session
output.
You must manually execute the parameter processor for any of the following reasons:
• You want to review all your parameter sets at the end of the dialog session.
• You did not want to automatically execute the parameter processor.
• The parameter sets are in any of the following forms:
- As source modules saved from a previous release
- As parameter output from a previous dialog session corrected by the general
editor
- As parameters prepared using any method other than the SYSGEN dialog
7004 5505-000 3-19
System Generation
Note: Never rerun SG$PARAM until you run all the jobs listed by SG$PARAM;
otherwise, the variables generated by the first execution ofSG$PARAM are
lost. You can only run the jobs listed for the current (second) execution of
SG$PARAM,
Automatic Execution of the Parameter Processor
The system executes the parameter processor automatically when you answer Y to the
dialog's question DO YOU WANT TO EXECUTE THE PARAMETER PROCESSOR
AGAINST DIALOG OUTPUT? (Y OR N).
After you decide where to store the dialog output by responding to the message
ENTER A 1-8 CHARACTER NAME FOR THIS OUTPUT MODULE, the dialog:
Stores the sets
Automatically executes the parameter processor
Supplies it with the parameter sets that you just created
Prints a summary listing of the entire dialog session
Terminates normally
The parameter processor then processes and verifies the SYSGEN parameter values.
It provides a complete listing of all your parameter values, defaults, errors in your
sets, and the execution sequence of the job control streams that you must execute if it
finds no errors.
If the processor terminates normally and finds no errors in your sets, carefully check
the SG$PARAM listing to be sure that all its default substitutions are correct for your
situation and the type of system you are generating. Then, go to the procedure for
running the SYSGEN job control streams in 3.2.3.
If the processor finds errors in your sets, it displays a message on your screen
informing you of the number of errors in your sets. When this message appears, you
must correct or change your parameter sets, using the parameter processor output
listing as a guide to identifying the errors. To correct or change parameters, use the
audit capability of the SYSGEN dialog that we describe here. The audit capability lets
you easily correct parameters that you prepared using the dialog. These parameters
now reside in the audit file that you allocated to contain them.
You can also use the general editor to correct or change parameters. The general
editor is a general-purpose editor that lets you edit, change, or correct the contents of
any module in the system. To use the editor, see the General Editor Operating Guide,
7004 4599. When using the editor, specify the name of the source module containing
your dialog output as the module that you want to edit. After you correct your
parameter sets, go to step 1 of the procedure for manually executing the parameter
processor.
3-20 7004 5505-000
System Generation
To use the audit file capability of the SYSGEN dialog, perform the following steps:
1. Allocate the file that will hold the new audit file version of this dialog session by
keying in:
AL MI,FIL=filename f VSN=volume,SI=2
where:
MI
Specifies that the audit file is a MIRAM file.
FIL=filename
Specifies the file label that you assign to the audit file.
VSN=volume
Specifies the volume serial number of your disk containing the audit
file.
SI=2
Is the size, in cylinders, of the audit file.
2. Reexecute the SYSGEN dialog starting at step 8 of 3.2.1, which gives the
procedure for preparing your parameter sets.
3. When you see the message ARE YOU CREATING A NEW AUDIT FILE? (Y/N),
key in Y and press XMIT.
4. When you see the message ENTER VSN OF DISC CONTAINING NEW AUDIT
FILE, key in the volume serial number of the SYSRES disk and press XMIT.
5. When you see the message ENTER FILE LABEL OF NEW AUDIT FILE, key in
a file name different from the file name containing the audit version of the dialog
session during which you prepared your parameter sets. That is, provide a name
for your new audit file different from the name you gave your old audit file. Press
XMIT.
6. When you see the message ARE YOU AUDITING AN OLD AUDIT FILE? (Y/N),
key in Y and press XMIT.
7. When you see the message ENTER VSN OF DISC CONTAINING OLD AUDIT
FILE, key in the volume serial number of the SYSRES disk and press XMIT.
8. When you see the message ENTER FILE LABEL OF OLD AUDIT FILE, key in
the file label name of the file containing the audit version of the dialog session
you prepared your parameter sets in. Press XMIT.
i(m SSO>00(1 3-21
System Generation
9. The dialog displays a message that it is ready to help you audit your old audit
file. Then it asks which paragraphs you want to change. Use the summary listing
that the dialog provides at the end of the dialog session as a guide to the
paragraphs you want to change. The paragraphs are numbered sequentially to
act as a map to your audit file.
Notes:
1. If you need to make changes to the paragraph containing the SYSGEN dialog
master menu screen, you must re-create the dialog entirely. In that case, go
back to the procedure for preparing the SYSGEN parameter sets (3.2.1).
2. At the end of the upcoming dialog audit session, the dialog either
automatically executes the SYSGEN parameter processor or terminates. The
action that takes place depends on the response, contained in the new audit
file, to the dialog question DO YOU WANT TO EXECUTE THE
PARAMETER PROCESSOR? If you do not change the paragraph containing
that response, the dialog uses the same response that both your old and new
audit files contain; if you change that response in the upcoming audit session,
the dialog uses the response that your new audit file will contain after this
session. Therefore, according to what you want the dialog to do at the end of
this session, decide if you want to change the paragraph containing that
response. If you do, specify it in step 10.
10. When you see the following screen, key In the paragraph numbers of the
paragraphs that you want to change or correct:
DP108 OS/3 DIALOG PROCESSOR VERSION
READY
ENTER PARAGRAPH NUMBERS TO BE EDITED.
PARAGRAPH NUMBERS MUST BE IN ASCENDING ORDER
WITH ONLY ONE NUMBER IN EACH AREA.
11. Press XMIT. The dialog displays each of the paragraphs that you Indicate you
want to change, one at a time.
12. Correct all the paragraphs you want to change according to the following
instructions:
a. When the dialog displays a paragraph, the top of the screen shows what your
old audit file contains for that paragraph. The middle of the screen is blank
and the bottom of the screen displays your auditing options at the beginning
of a paragraph. For example, in step 10, you tell the dialog that you want to
change paragraph 8 of your old audit file. In this example, paragraph 8
contains part of the SUPGEN parameters. The dialog would show you a
screen resembling this one:
S-22
7004 5505000
System Generation
8. SUPERVISOR SIZING PARAMETERS
1.
PRIORITY
2.
JOBSLOTS
3.
TRANS
4.
SHAREDMGT
5.
SYMBPRI
TASK PRIORITY LEVELS
DUMBER OF JOBSLOTS
NUMBER OF TRANSIENT AREAS
SHARED DATA MNGMENT TABLE SLOTS
SYMBIONT PRIORITY LEVEL
FOR HELP ENTER PARAMETER NUMBER OR 'ALL'
AT THE BEGINNING OF PARAGRAPH, YOU CAN:
ENDSESSIOM (F4) f EDIT <F7) S OR PROCEED (XMIT)
Choose one of the following auditing options by pressing the FUNCTION key
and simultaneously pressing the workstation function key that corresponds
to it:
• ENDSESSION (F4) - This option lets you normally terminate an
auditing session before you've made all your changes to the old audit
file. If you choose ENDSESSION, the dialog displays a message telling
you that it terminated normally;, but your new audit file is incomplete
and must not be used. When you subsequently want to complete the
auditing session, you must perform this procedure again starting at step
1 and specify the same name for the old audit file that you did in this
session.
• EDIT (F7) - This option lets you make changes and corrections to the
paragraph that you are working on. In most cases, you choose EDIT at
this point because you told the dialog that you wanted to change this
paragraph in step 10. If you choose EDIT, go to step b.
• PKOCEED (XMIT) - This option lets you go on to the next paragraph
you indicated in step 10, without making any changes to the current
paragraph. You choose PROCEED at this point only if, after rereading
the paragraph, you realize you don't want to change it, but you indicated
that you did in step 10. If you choose PROCEED, go back to the
beginning of this step (step a).
7004 5505-000
3-23
System Generation
b. When you choose EDIT, the top of the screen again shows your old audit file,
the middle of the screen is reserved for your changes, and the bottom of the
screen shows your auditing options at a choice point in a paragraph. Using
our same example, the dialog shows a screen resembling this one:
8. SUPERVISOR SIZING PARAMETERS
1.
PRIORITY
TASK PRIORITY LEVELS
2.
JOBSLOTS
NUMBER OF JOBSLOTS
3
3.
TRAMS
NUMBER OF TRANSIENT AREAS
4
4.
SHAREDMGT
SHARED DATA MNGMENT TABLE SLOTS
5
5.
SYMBPRI
SYMBIONT PRIORITY LEVEL
6
FOR
HELP, ENTER
PARAMETER NUMBER OR ! ALL'
AT CHOICE POINT IN PARAGRAPH, YOU CAN:
CANCEL CF2)„ REEDIT (F3)> ENDSESSION (F4),
INSERT (F5) f DELETE <F6>, EDIT <F7), OR PROCEED CXMIT)
Choose only one of the following auditing options by pressing the FUNCTION
key and simultaneously pressing the workstation function key that corresponds
to it:
• CANCEL (F2) - This option is invalid at this point.
• REEDIT (F3) - This option is invalid at this point.
• ENDSESSION (F4) - See explanation under step a.
• INSERT (F5) - This option lets you insert a choice that you neglected to
specify in the paragraph during your original dialog session. If you choose
INSERT, the dialog displays the paragraph and positions the cursor at the
first data field. To skip to the next data field without inserting a value at the
current field, press the TAB FORWARD key. After you finish all the data
fields, go to step c.
3-24
7004 5505-000
System Generation
• DELETE (F6) - This option lets you delete a choice that you specified in the
paragraph during the original dialog session. If you choose DELETE, the
dialog displays the paragraph, deletes the first data field, then positions the
cursor at the next data field. To delete that value, press F6 again; to skip to
the next data field without deleting the current value, press the TAB
FORWARD key. After you finish all the data fields, go to step c.
• EDIT (F7) - This position lets you edit, or change, a value that you specified
in the paragraph during the original dialog session. If you choose EDIT, the
dialog displays the old audit file screen for that paragraph and positions the
cursor at the first data field. Press the TAB FORWARD key to position the
cursor at the data field that you want to change, key in the correct value over
the incorrect value, and press XMIT. After you edit the data fields, go to
step c.
c. After you perform the auditing option at the choice point in the paragraph, the
top of the screen shows your old audit file, the middle of the screen shows your
new audit file, and the bottom of the screen shows your auditing options at the
end of the paragraph. Using our same example, assume you chose to edit
paragraph 8 to change the number of job slots from 3 to 7. The dialog shows you a
screen resembling this one:
8. SUPERVISOR SIZING PARAMETERS
1. PRIORITY TASK PRIORITY LEVELS
2. J08SLOTS NUMBER OF JOBSLOTS
3
3. TRAMS NUMBER OF TRANSIENT AREAS
4
4. SHAREDMGT SHARED DATA MNGMENT TABLE SLOTS
5
5. SYMBPRI SYMBIONT PRIORITY LEVEL
6
FOR HELP, ENTER PARAMETER NUMBER OR «ALL«
8. SUPERVISOR SIZING PARAMETERS
1. PRIORITY TASK PRIORITY LEVELS
2. JOBSLOTS NUMBER OF JOBSLOTS
7
3. TRANS NUMBER OF TRANSIENT AREAS
4
4. SHAREDMGT SHARED DATA MNGMENT TABLE SLOTS
5
5. SYMBPRI SYMBIONT PRIORITY LEVEL
6
FOR HELP, ENTER PARAMETER NUMBER OR 'ALL'
AT END OF PARAGRAPH, YOU CAN;
CANCEL (2), REEDIT (F3) f ENDSESSION <F4>, OR PROCEED (XMIT)
7004 5505-000
3-25
System Generation
At this point, choose one of the following auditing options:
• CANCEL (F2) - This option lets you cancel the changes you made to the
paragraph in step b. Choose this function if you made many changes that you
now want to cancel. If you choose CANCEL, go back to step a.
• REEDIT (F3) - This option lets you reedit the paragraph that you audited in
step b. Choose this option if you made only a few changes that you now want
to reedit. If you choose REEDIT, go back to step b.
• ENDSESSION (F4) - See explanation under step a.
• PROCEED (XMIT) - This option either lets you proceed to the next
paragraph you indicated in step 10, or it automatically takes you back into
the SYSGEN dialog if you make extensive changes to your old audit file. If
you do not make extensive changes, it lets you terminate this auditing
session when you have no other paragraphs to change. After you make all
your changes and, if necessary, go through the SYSGEN dialog, you receive a
message that the dialog session terminated normally. At this point, the
dialog then automatically executes the parameter processor or terminates.
The action that takes place depends on the response, contained in the new
audit file, to the dialog question DO YOU WANT TO EXECUTE THE
PARAMETER PROCESSOR? If it contains a Y for yes, go back to the
beginning of this section for automatic execution of the parameter processor.
If it contains an N for no, go to "Manual Execution of the Parameter
Processor."
Manual Execution of the Parameter Processor
The following paragraphs describe the procedure for manually executing the
parameter processor. You must process your SYSGEN parameter sets in this way if
your sets are in any of the following forms:
• As source modules saved from a previous dialog session
• As source modules saved from a previous release
• As parameters saved from a previous dialog session and corrected by the general
editor
• As parameters prepared using any method other than the SYSGEN dialog
3-26 7004 5505-000
System Generation
To manually execute the parameter processor, proceed as follows:
Note; If your parameter sets are on keypunched cards, load the cards in your card
reader. If you are processing supervisor, NTR, or COBOL parameter sets, key
in RU SG$PARAM on the console I workstation. If you are processing an
ICAM parameter set, key in:
RU SG$PARAM„ICAM=Y
Proceed with step 2 of this procedure.
1. At your console/workstation In console mode, key in:
*F=Jf i I enamel
j$Y$SRC J
[ # V-vsn]
RV SG$PARAM„S=source-module[ s SCHASM=Y][,lCAM==Y]
[ , RESVSN=vsn 3 [ , PR I UJ-H 1 [ , SWEDEN=Y ] L
where:
S=source -module
Identifies the name of the source module where you stored your
parameter sets.
SCHASM=Y
Automatically schedules SG$SUPMK and SG$COMMKIf no parameter
errors occur.
ICAM=Y
Is required if you are processing an ICAM parameter set.
F=fil<
Identifies the name of the file that contains that source module.
v=vsn
Identifies the volume serial number of the volume that contains that
file.
RESVSN=vsn
Allows users to SYSGEN properly when they change the volume serial
number of their release disk.
PRIMT=N
Inhibits printer output.
SWEDEN=Y
Specifies nonstandard character translation for Sweden and Finland.
7004 5505-000 3-27
System Generation
Notes;
1. If you do not supply a value for the S parameter, the parameter processor
requests this information from you.
2. If you execute SG$PARAMfrom a workstation and do not specify the S
parameter, the parameter processor asks whether you want to run
interactively through the SYSGEN dialog. Respond Y if you have not
prepared SYSGEN parameter sets.
3. If you do not specify a volume serial number, the default is your SYSRES
volume.
2. The parameter processor now processes and verifies your SYSGEN parameter
set. It provides a complete listing of all parameter values, defaults, errors, and
the execution sequence of the job control streams that must be executed. When
parameter processing is completed, one of the following situations occurs:
a. No errors were found and the SCHASM=Y parameter was selected:
The applicable job control stream (SG$SUPMK or SG$COMMK) is
automatically scheduled. When this job terminates, perform the post-
SYSGEN procedures in 3.3 that apply to you.
b. No errors were found and the SCHASM=Y parameter was not selected:
You can check the SG$PARAM listing to be sure that all default
substitutions are correct for your situation. You can then manually execute
the required SYSGEN job control stream (with desired options) as defined in
3.2.3.
c. Parameter set errors were found:
You must correct or change your parameter sets, using the parameter
processor output listing as a guide to the errors. Unless your sets are on
keypunched cards, use the general editor according to the instructions in the
General Editor Operating Guide, 7004 4599, to correct your parameters.
When using the editor, specify the source module name that contains your
parameter sets and the name of the file containing this source module. If
your sets are on keypunched cards, simply replace the cards that contain
misstated or incorrect parameters. When you correct all errors in your
parameter sets, rerun the parameter processor, starting at step 1 of this
procedure.
3-28 7004 5505-000
System Generation
3.2.3. Running the SYSGEN Job Control Streams
SYSGEN job control streams must be run to generate your system after your
parameter sets are prepared and processed. As previously described, use of the
SCHASM=Y option when you run the parameter processor causes the SG$SUPMK
and SG$COMMK job control streams to be automatically scheduled and run.
However, you must manually run the required SYSGEN job control stream for either
of the following conditions:
• The SCHASM=Y option was not specified when the parameter processor was run.
• A COBOL compiler is being generated with the SG$COBMK job control stream.
For these cases, use the applicable run command to initiate each job that the
parameter processor lists. When the last job terminates, perform the post-SYSGEN
procedures in 3.3 that apply to you. The SYSGEN process will then be completed.
Supervisor SYSGEN Job Control Stream
To manually run the supervisor SYSGEN control stream, use the following command:
RV SGSSUPMC
,[,TPUK=vsn]
} PRIMT= fDKl
where:
TPWK-vsn
Provides temporary work files for the assembler on an alternate disk device.
The value vsn identifies the volume serial number of the alternate device.
PRINT=DK
Specifies that you want spooled output directed to a format label diskette.
PRINT=N
Inhibits printer output.
The system generates the supervisors that you configured and stores them on your
SYSRES volume. When it has successfully done so, it displays a message informing
you that the job stream terminated normally.
ICAM Job Control Stream
Caution
Before running SG$COMMK, determine if ICAM is active. If active, ensure that the
ICAM being generated (e.g. C1-C9, M1-M9) differs from the active ICAM.
Unpredictable results can occur if the active ICAM is regenerated or relinked.
7004 5505-000 3-29
System Generation
To manually run the ICAM SYSGEN control stream, use the following command:
# PRIMT
= n
RV SG$COMMK[ , [ # GENLST=Y] [ ,TPUK=vsn]
[,RELINK=Y][,CYL=cyl][,SECALL=cyl]]
where:
GENLST=Y
Specifies that you want a complete listing of the ICAM macroinstruction
generations.
TPWK-vsn
Provides temporary work files for the assembler on an alternate disk device.
The value vsn identifies the volume serial number of the alternate device.
PRINT=DK
Specifies that you want spooled output directed to a format label diskette.
PRINT=N
Inhibits printer output.
RELINK=Y
Specifies that the ICAM just processed by SG$PAEAM needs only relinking
rather than a complete generation. If RELINK=Y is not specified, a
complete generation is done and the object modules for all assembly job steps
are saved in SG$OBJ. With RELINK=Y, the assembly job steps issue the
error message SOURCE INPUT MODULE CANNOT BE LOCATED
ASSEMBLER ABORTED and the previously saved object modules are
included in the link.
CYL^cyl
Specifies the initial allocation of cylinders on the spool pack for the scratch
files.
SECALL-cyl
Specifies the secondary allocation value for each extent of the scratch files on
the spool pack.
Note: CYL and SECALL are most effective when specified with the TPWK
parameter if the error DM45 EXTENT TABLE EXHAUSTED is received
while running SG$COMMKon a very large ICAM.
The system generates the ICAM element that you configured and stores it on the
SYSRES, unless you specified an alternate output volume during COMMCT. When
completed, the job stream displays a message that it terminated normally.
3-30 7004 5505-000
System Generation
NTR Job Control Stream
To manually run the NTR SYSGEN control stream, use the following run command:
RV SG$NTRMKE ff PRINT=DK]
where:
PRINT^DK
Specifies that you want spooled output directed to a format label diskette.
The system generates the NTR element you configured and stores it on the SYSRES,
unless you specified an alternate output volume during NTRGEN. When complete,
SG$NTRMK tells you that it terminated normally.
COBOL Job Control Stream
To manually run the COBOL SYSGEN job control stream, use the following run
command:
RV SGSCOBMK
f ,PRINT=
n
where:
PRINT=DK
Specifies that you want spooled output directed to a format label diskette.
PRINT=N
Inhibits printer output.
The system generates the ANSI '74 or '85 COBOL element that you configured and
stores it on the SYSRES. When completed, the job stream tells you that it terminated
normally.
7004 5505-000 3-31
System Generation
After you generate the system, perform the following post-system generation
procedures that apply to you.
You must update the system definition file ($Y$SDF) if you install software that
changes the microcode for any of the following devices that exist on the system:
• Any workstation other than the console/workstation plus one more local
workstation
• Remote printer
• Any single-line communications adapter
You must update $Y$SDF before you continue with any post-generation procedures.
See 2.3.1.
3*3.2* Configuring Automatic Supervisor Loading
The CFIG command is used to create and update the configuration file ($Y$CONFIG).
The contents of this file are used during the IPL sequence to control the automatic
boot procedure (ABP). Refer to the Models 8-20 Operations GuideJOOA 5208, for more
information on using ABP and the CFIG command.
333. Generating an IMS Online Load Module
If you install the OS/3 information management system (IMS), generate an IMS
online load module before the IMS system is operational. See the IMS System Support
Functions Programming Guide, UP-11907.
3.3.4. Defining Alternate Printer Characteristics
The I/OGEN parameters supply a number of default characteristics for the system
printers. For example:
• One of these three print cartridges: 48-BUS, 48-SCI, or 63-STD.
• An 11-inch vertical form and six printed lines per inch. (These characteristics are
indicated in the VFB=STAND1 parameter.)
3-32 7004 5505-000
System Generation
Alternate printer characteristics must be defined If you configure either a physical
printer or an indirect printer (for a printerless system) and you don't want to use these
default characteristics.
Note" If you configure a printerless system, specify the ADDR=NO II OGEN
parameter described in the table in 4.2.
You should define alternate characteristics at this time for all your physical or
indirect printers that have alternate printer characteristics, rather than each
time you want to use those printers.
You use the SG$PRB job control stream to define the alternate characteristics.
The format of this job control stream Is:
RV SG$PRB„MOD=module-name[,DVC=caa][ ( PRINT=N]
, RELOAD*^'
where:
MOD=module-name
Specifies the $Y$SRC source module that contains the alternate printer
characteristics.
DVC=caa
Specifies the address (channel and device) of the printer.
PRINT=N
Inhibits printer output. (If you don't inhibit printer output, ensure that the
printer is online before running SG$PRB.)
RELOADS or N
Specifies when the LCB is loaded. When Y (the default) is specified, you
must re-IPL the system to load the LCB. When N is specified, the LCB is
loaded without a re-IPL.
Physical Printers
To define alternate printer characteristics for a physical printer:
1 . Perform an Initial program load (IPL) to load your choice of operating supervisor
into main storage. See the Operations Guide, 7004 5208.
2. Use the general editor to prepare your alternate printer characteristics as a
source module in the system source code library, $Y$SRC, on your SYSRES. To
use the general editor, see the General Editor Operating Guide, 7004 4599. Follow
the instructions and formats In the Job Control Programming Guide, 7004 4623,
and proceed as follows:
7004 5505-000 3-33
System Generation
a. Key in a // DVC job control statement for each printer that has defined
alternate printer requirements. You. can submit one // DVC for both a LCB
and a VFB.
If you are defining two sets of printer characteristics for one printer, prepare
a // DVC statement for each set. Each // DVC statement and its associated
// LCB and // VFB statement must be prepared separately. That is, you must
include one // DVC and one // LCB and / or one // VFB in each source module
that you prepare as input to SG$PKB.
On each // DVC statement:
(1) Identify the physical printer type by specifying the appropriate logical
unit number from Table 4-8.
(2) Specify the physical printer's address (PUB) to ensure that your system
accesses the physical printer (and not a virtual printer) at SG$PRB
scheduling time. (If you do not specify the printer's address, a spooling
supervisor does not change the contents of the default LCB/VFB.)
b. Key in a // LCB job control statement for each alternate print cartridge that
you are defining. Specify a user LCB (OWNLC1 through OWNLC9) in the
label field to specify that your printer uses a print band other than 48-BUS,
48-SCI, or 63-STD.
If you only want to specify character mismatch reporting for one of these
three print bands, specify the name of your print band in the label field.
c. Key in a // VFB job control statement for each set of alternate VFB you are
defining. On each // VFB statement, proceed as follows:
(1) Specify the user VFB name (OWNVF1 through OWNVF9) in the label
field.
(2) Specify FORMNAME=STANDl as the form name parameter.
(3) Define the remainder of your vertical format characteristics.
3. Key in the appropriate SG$PRB job stream.
4. Press XMIT. The system generates the load code and vertical format
characteristics that you defined and tells you when it terminates normally.
3-34 7004 5505-000
System Generation
Examples
The following examples show how to change VFB and LCB characteristics.
Example 1. Changing VFB Characteristics
EDT
1.888 // DVC 28,330
2.080 //OWNVF1 VFB FORMNAME=STAND1 f DEN=8,LM=88,OVF=88
3.808 WRITE MO=VFBCHG,FIL=$Y$SRC,VSN=REL140
4.008 3HALT
RV SG$PRB„MOD=VFBCHG
In Example 1, the general editor (EDT) is used to create a source module that alters
the VFB printer characteristics. The // DVC statement shows the logical unit number
(20) and the hardware address (330) of the printer. The //VFB statement must contain
OWNVF1 in the label field and STANDI as the form name. A standard 11 -inch form
and a density (DEN) of 8 lines per inch is selected, giving the form a length (LEN) of
88 lines. The overflow (OVF) Is set at line 80. Printing will stop at line 80 and continue
at the top of the next form, leaving a 1-inch margin at the bottom of each form.
The ©WRITE command names the source module and writes it in $Y$SRC on the
SYSRES volume (VSN=REL140). EDT terminates with the ©HALT command. After
creating the source module, SG$PRB Is run using the module name specified in the
©WRITE statement (VFBCHG). SG$PRB displays a message when it terminates.
Example 2. Changing LCB Characteristics
EDT
1.808 // DVC 28 , 330
2.808 //48-BUS LCB MISM=REPORT
3.888 aWRITE MO=LCBCHG,FIl=$Y$SRC,VSN=REl148
4.080 3HALT
RV SG$PRB„MOD=LCBCHG
In Example 2, EDT is used to create a source module that alters LCB printer
characteristics. The // DVC statement shows the logical unit number (20) and the
hardware address (330) of the printer. The LCB statement contains the cartridge
name in the label field (48-BUS) and specifies that character mismatch errors are
reported.
The ©WRITE command names the source module and writes it in $Y$SRC on the
SYSRES volume. EDT terminates with the ©HALT command. After the source
module is created, SG$PRB is run using the module name specified in the ©WRITE
statement (LCBCHG). SG$PRB displays a message when it terminates.
7004 5505-000
3-35
System Generation
Indirect Printers
To define alternate printer characteristics for an indirect printer:
1 . Perform an initial program load (IPL) to load your choice of operating supervisor
into main storage. See the Operations Guide, 7004 5208.
2. Enter the following command to set the spool file temporarily to the HOLD state.
By holding all spooled output, you prevent it from being sent to the indirect
printer while it is set UP.
HOLD SPL.ALL
3. Enter the following command to set the physical unit block (PUB) for the indirect
printer temporarily to the UP state (normally, the PUB is set to the down state).
SE IO,did # UP,n
where:
did
Is the device address.
Is a one-digit number indicating the indirect printer PUB being
used. If omitted, the first virtual PUB is assumed.
4. Use the general editor (EDT) to prepare your alternate printer characteristics as
a source module in the system source code library, $Y$SRC 5 on your SYSRES. For
each indirect printer with alternate characteristics, proceed as follows:
a. Key in a // DVC job control statement for the indirect printer with the
following format:
// DVC 28 , REAL
You can submit one // DVC for both a LCB and a VFB.
b. Key in a // LCB job control statement for each alternate print cartridge that
you are defining. Specify a user LCB (OWNLC1 through OWNLC9) in the
label field if you are using a print band other than 48-BUS, 48-SCI, or
63-STD.
3-36 7004 5505-000
System Generation
c. Key in a // VFB job control statement for each set of alternate WB
characteristics that you. are defining. On each // VFB statement, proceed as
follows:
• Specify the user VFB (OWNVF1 through OWNVF9) in the label field.
• Specify FORMNAME=STANDl as the form name parameter.
• Define the remainder of your vertical format characteristics.
5. Key in the appropriate SG$PRB job stream.
6. Press XMIT. The system generates the load code and vertical format
characteristics that you defined and tells you when it terminates normally.
7. Enter the following command to set the indirect printer down (reversing the
procedure described in step 2).
SE IO,did,DO,n
where:
did
Specifies the device address.
n
Is a one-digit number indicating the indirect printer PUB being
used. If omitted, the first virtual PUB is assumed.
8. Enter the following command to begin spooling.
BEGIM SPL # ALL
Example
This example changes the VFB characteristics for an indirect printer.
EDT
1.088 // DVC 20 , REAL
2.000 //OWMVF1 VFB FORMMAME=STAND1 S DEN==8,LEN=88,OVF=80
3.000 aWRITE HO=FBCHG,FIL=$Y$SRC # VSM=REL140
4.000 SHALT
RV SG$PRB s ,MOD=VFBCHG
In this example, EDT creates a source module to alter VFB printer characteristics.
The // DVC statement specifies that we are changing VFB characteristics for an
indirect printer.
7004 5505-000
3-37
System Generation
3.3.5. Changing the Interactive Services Logo
When you sign on to Interactive services, the OS/3 default logo is displayed. If you
want to change this logo, refer to the instructions in the Interactive Services Operating
Guide, UP-9972.
3.3.6. Changing the System Bulletin
Every time you log on, your system displays the system bulletin.
Initially, the system displays the default bulletin, which Unisys provides to describe
how you enter commands. The default bulletin looks like this:
IS27 TODAYS BULLETIN IS:
****************** WELCOME TO OS/3
THIS BULLETIM MAY BE CHANGED BY REPLACING OR MODIFYING
THE SOURCE MODULE "BULLETIN" IN FILE $Y$SRC
If you want the system bulletin to display other Information, you can overwrite the
system default bulletin. You can use either the general editor or the system librarian.
In both methods, you overwrite the contents of the BULLETIN module in $Y$SRC,
which can contain only one system bulletin at a time.
Note: If you want to save the default bulletin before making any changes, use the
interactive services COPY command. See the Interactive Services Operating
Guide, UP-9972.
When you create new text for the system bulletin, follow these rules:
• Do not write more than 60 characters In each line of the bulletin.
• Do not create a bulletin more than 20 lines long.
• Do not use the dollar sign ($) as the first character of a line.
• Be sure all the characters in the bulletin text are printable characters.
The following example shows how to change the bulletin by using the general editor:
LOGON
JOHNM
EDT
1.088
3READ MODULE=BULLET!N,FILENAME=$Y$SRC
5.000
8PRINT 1:4
1.880
****************** WELCOME TO OS/3 ******************
2.880
* THIS BULLETIN MAY BE CHANGED BY REPLACING OR MODIFYING
3.000
* THE SOURCE MODULE "BULLETIN" IN FILE $Y$SRC
4.888
3DELETE 1:3
1,808
SYSTEM AVAILABLE FROM 0908 TO 1980 TODAY
2.880
aWRI TE MODULE - BULLET I N , F I LEMAME=$Y$SRC
2.000
3HALT
LOGOFF
3-38 7004 5505-000
System Generation
The following example shows how to change the bulletin by using the librarian:
// JOB BULLADD
// DVC 20 // LFD PRNTR
// EXEC LIBS
/$
FIL D1=$Y$SRC
ELE.D D1,S,BULLETIN
SYSTEM AVAILABLE FROM 8908 TO 1988 TODAY
EOD
/*
/&
II FIN
Note: In the ELE statement, the D option causes the contents of the module (the
bulletin text) to he printed.
3.3.7. Verifying System Installation
To verify that you successfully performed your entire system installation without
destroying any software during SYSGEN, perform the installation verification
procedures that apply to your system. The Installation Verification Procedures (TVP)
Operating Guide, 7004 5232, describes these procedures in detail.
3.3.8. Making and Restoring a Backup Copy of Your Current SYSRES
After you successfully complete and verify system installation, make and save a
backup copy of your current, customized SYSRES for your convenience and protection
in the event the SYSRES device becomes inoperable. Remember that the software
release media you received does not include the customized changes that you made
during SYSGEN.
Making backups should be an ongoing process. Anytime you make changes to the
release software, or if you are using SYSRES to store your own software, you should
ensure that you have an up-to-date copy of the tailored SYSRES.
Before you build your backup copy, give some thought to which type of media would
best serve as your backup. You have a choice of:
• A fixed disk volume (841 7, 8470, 8480, 8494, or M9720)
• A removable disk volume (8419, 8430, or 8433)
• A set of diskettes
• Tape
7004 5505-000 3-39
System Generation
If your system includes a removable disk device, build the backup SYSRES on it. This
allows you maximum protection at minimum cost because you can run your system
using the removable backup disk as the SYSRES, if necessary. Although this method
takes a little longer, the use of the SETREL/COPYREL job streams allows a more
thorough cleanup and secure backup. In addition, you don't tie up a disk drive for
backup purposes. Remember that you minimize your system's performance and
security by using a fixed disk device as your SYSRES device. You should use your
removable backup copy as a temporary SYSRES only and restore your system to a
fixed disk device as soon as possible.
If your system does not include a removable disk device, you have the choice of
building a backup copy on a set of diskettes, tape, or a fixed disk device. When making
this choice, keep in mind the trade-off between space and convenience.
• Using diskettes or tapes as backup devices conserves online disk space but
requires that you use multiple diskettes or tapes in a specified file sequence and
requires more time to perform the backup and restore operation. It also requires
that you perform the restore operation before you can resume normal system
operation.
• Using a fixed disk as a backup device Is a fast and convenient way to build a
backup copy, and a fixed disk can conveniently serve as your new SYSRES, if
necessary. However, using a fixed disk as a backup SYSRES uses valuable online
disk storage space.
No matter which device you choose as your backup device, make certain that you keep
your backup SYSRES current. Failure to do so may require you to completely reinstall
and regenerate your entire system from the OS/3 release media that you originally
received from Unisys.
Note: If error messages are generated when you build your backup copy, do not
assume the copy is good. Refer to the System Messages Reference Manual,
7004 5190, for a description of all messages generated during the backup
procedure and, if indicated, repeat the procedure.
Using a Fixed Disk for Your Backup SYSRES {DCOP)
You can use the following fixed disks as your backup SYSRES:
• 8417 disk
• 8470 disk
• 8480 disk
• 8494 disk
• M9720 disk
340 7004 5505-000
System Generation
You build your backup SYSRES on these disk drives by using the system-supplied
DCOP job control stream. This method is very efficient as it copies all the files on
your SYSRES to the new disk through the single run command.
To build your backup SYSRES with DCOP:
1. Perform an initial program load (IPL) from your existing SYSRES to load either
the starter supervisor or one that you've generated into main storage.
2. Key in:
RV DCOP, f T=disk- type
,N= ("numberl ,V= [YES]
[,F=Y][,An=caa]
where:
T=disk type
Specifies the two-digit type number of the disk subsystem that you are
using.
Jxee
Disk
17
8417
20
M9720
70
8470
80
8480
94
8494
Specifies the number of copies that you are making. In this case, you
can make only one copy.
V=YES
Specifies that you want verification of your backup copy.
f=y
Specifies the FILE mode copy of dump/restore which allows SYSRES to
be copied to another disk type with similar characteristics. This permits
copies between 8470 s 8494, and M9720 disks.
An=caa
Specifies the channel and address of the output disks. The n value
should be the same as the N value that specifies the number of copies. If
the default value (1) is used, then Al should be specified. The channel
and address are specified by the caa value.
After you supply this information, DCOP displays a message inquiring if you are
ready for the routine to copy your SYSRES.
7004 5505-000 Ml
System Generation
When the message MOUNT DEV=did VSN=DISC GO? appears, check that did is
the device address of the disk you are copying your SYSRES to, key in GO DCOP,
and press XMIT.
DCOP then copies the entire contents of your SYSRES, including the VSN, to the
backup disk. If you don't want two disks with the same VSN, use the CGV job
stream to change one as explained In the System Service Programs Operating
Guide, UP-8841. When it completes the copy operation, DCOP displays a message
to inform you that It terminated normally.
Noie^ Unisys preps all 8417 disks before you receive them and supplies track
condition tables (TCTs) for those disks. These TCTs identify which tracks
on the disks are defective. If the TCTfor the disk on which you built the
SYSRES copy indicates that the disk contains defective tracks in any one
of its first six cylinders, perform an extra operation when DCOP
terminates. Place the initial microprogram load (IMPL) and initial
program load (IPL) codes to the correct position on the disk. Execute this
operation to perform IMPL and IPL operations from the SYSRES copy.
To place the IMPL and IPL codes in their correct positions, use the job
stream PRPMIC. (See 2.2.3.)
Using a Removable Disk for Your Backup SYSRES fSETREL/COPYREL)
You use the system-supplied SETREL and COPYREL job control streams to create a
backup SYSRES on a removable disk. These job streams must be used together. You
use SETREL to prep a second disk and then allocate SYSRES files to that disk. You
then use COPYREL to copy SYSRES files to the new disk volume (see Table 3-6). As
indicated in the Table 3-6 note, COPYREL does not transfer certain SYSRES files; you
must use LIBS, MLIB, data utilities, or DMPRST to transfer these files.
Although this method involves multiple steps to make a complete copy of your
SYSRES, you can use this procedure to create a backup copy on a disk type different
than your existing SYSRES.
To build the backup SYSRES on a removable disk:
1 . Mount your backup disk.
2. Perform an Initial program load (IPL) from the SYSRES to load either the starter
supervisor or one that you've generated into main storage.
3. Prep the backup disk by keying In at the console/workstation In console mode:
RV SETREL, # V=vsn,T-disk-type,P=prep-type[,CR=NO][,R=n]
342 7004 5505-000
System Generation
where:
V-vsn
Specifies the volume serial number of the backup disk. This vsn must be
different from the vsn of your SYSRES.
T=disk-type
Specifies the two-digit type number of your backup SYSRES disk. The
disk type numbers may be:
Tyjee
Disk
18
8418-2 (model 8 only)
19
8419
30
8430
33
8433
P=prep type
Specifies the type of prep you want SETREL to perform. The prep type
codes are:
Code Meaning.
F Full prep (surface analysis) requires insert information from
cards/keyins. A full prep of the disk must be done if you plan
to use the disk as your SYSRES.
P Fast prep (fast surface analysis) does not require insert
information.
N No prep performed, assign files only, does not require insert
information. This option causes SETREL to use the existing
VTOC. If the existing VTOC is not from a previous SETREL
execution, it is unlikely that the VTOC will be positioned in
the best location. In this case, system files are allocated on a
contiguous basis by absolute cylinder addresses. Allocation
errors occur if other files cross these absolute cylinder
allocations.
Notes;
1. IfP=F is entered from a console, the system expects inserts from a
card reader. Do not enter CR=NO.
2. IfP=F is entered from a workstation, insert information through a
workstation screen. No card reader is required,
7004 5505-000 343
System Generation
CR=MO
Specifies that you, are entering information concerning known bad
tracks on the backup disk volume from the console/workstation. You
must specify this parameter if your system does not have a card reader.
R=n
Specifies the number of times a defective track is retested before it is
declared unusable and an alternate track is substituted. The value n is
a hexadecimal number from 00 to FF. The default value is OA.
After you enter this parameter, press XMIT.
If you specified P=N in step 3, this message appears: ALLOCATION ERRORS
POSSIBLE USING P=N IF EXISTING VTOC IS NOT THE RESULT OF A
PREVIOUS SETREL PREP -CONTINUE (N,Y). If you respond N s the backup
process terminates. If you respond Y, SETREL preps the backup disk and
assigns the system files that will reside on that disk after you execute COPYREL.
If unrecoverable errors occur during the prepping of a volume, a message
indicates this at your console or terminal, and the job terminates immediately. If
other errors occur, a warning message is sent and the job continues processing.
If you specified P=F in step 3, SETREL requests information from you concerning
known bad tracks on the backup disk volume. Enter the hexadecimal address of
any defective tracks on that disk and press XMIT.
Note: If you are entering this information on cards, had tracks must he
identified by an INSERT statement (one track per statement) and the set
must be terminated with all FIN statement. If you are prepping a disk
with no known bad tracks, you must place an INSERT statement with
the word NONE starting in column 10, followed by a 1 1 FIN statement,
to satisfy the request made by SETREL.
Prepare backup copies of all the system files on your current SYSRES by keying
in at the console/workstation in console mode:
RV COPYREL,, V=vsn,T=disk-type[,S=first-file-code]
[ f E=last-f lie-code] [,CAT=Y][,SEC=Y][ f CONFIG=Y]
where:
v=vsn
Specifies the volume serial number of the backup disk volume. (This vsn
must be different from the vsn of your SYSRES.)
344 7004 5505-000
System Generation
T=disk-type
Specifies the two-digit type number of your backup SYSRES disk. The
disk type numbers may be:
Jiee
Disk
18
8413-2 (model 8 only)
19
8419
30
8430
33
8433
S=f irst-f ile-code
Specifies the code Identifying the first file that you want COPYREL to
copy. Table 3-6 shows the order that COPYREL copies the system files
and shows the codes for each system file. If you omit the S keyword,
COPYREL begins copying at $Y$SRC.
E=last-f ile-code
Specifies the code for the last file that you want COPYREL to copy. (See
Table 3-6.) If you omit the E keyword but specify the S keywords
COPYREL ends copying at $Y$SEC. If you omit both the S and E
keywords, COPYREL begins with $Y$SRC and ends with $Y$TRANA.
CAT=Y
Specifies $Y$CAT (catalog file) Is copied using SGTRAN.
SEC=Y
Specifies $Y$SEC (security file) is allocated and copied using MLIB.
CQNFIG=Y
Specifies $Y$CONFIG (configuration file) is allocated and copied by
using data utilities.
When you specify the S and E keywords, COPYREL overrides the CAT, SEC and
CONFIG parameters and generates an error to the console. The S and E keyword
parameters control the number of files that COPYREL copies. They can also
indicate to COPYREL where to restart a copy function if you ever encounter an
error while performing COPYREL. You can use these keywords to specify that
you want to copy a single library by specifying the same file for each parameter.
7004 5505-000 345
System Generation
Table 3-6. COPYREL Copy Order
Copy
Copy
Order
Code
File Name
Order
Code
File Name
1
S
$Y$SRC
13
SMCFilE
SMCFILE
2
SYSOBJ
14
SMACLOG
$Y$SMCLOG
3
L
$Y$10D
15
FMT
$Y$FMT
4
M
$Y$MAC
16
SAVE
$Y$SAVE
5
J
$Y$JCS
17
DIALOG
$Y$D1AL0G
6
G
SG$JCS
18
SDF
$Y$SDF
7
SGMAC
SG$MAC
19
HELP
$Y$HELP
8
SGOBJ
SG$OBJ
28
T
SYSTRAN
9
SGLOD
SG$LOD
21
A
$Y$TRANA
10
SCLOD
$Y$CLOD
22
CAT
$Y$CAT*
11
MIC
$Y$MIC
23
SEC
$Y$SEC*
12
IVP
IVPLIB
24
CONFIG
$Y$CONFIG*
* These files are copied when requested by parameters in RUN statements.
Note: COPYREL does not copy certain SYSRES files because they are
initialized at IPL time. The files that are not copied are:
$Y$SYSTEMTABLES, $Y$DUMP, $Y$SHR, $Y$ELOG, $Y$ESUM S
$Y$FDY, and SG$XXX.
6. Press XMIT. COPYREL then copies your system files onto the backup disk
volume and tells you when it terminated normally.
Note: Place the initial microprogram load (IMPL) code and initial program
load (IPL) code to the correct positions on the disk using thejobstream
PRPMIC. (See 2.2.3.)
7. Use the system librarians, LIBS and MLIB, to prepare copies of your own
program library files - LIBS for SAT program library files and MLIB for MIRAM
program library files. See the System Service Programs Operating Guide,
UP-8841.
346
7004 5505-000
System Generation
8. If you store any data files on SYSRES, use data utilities to make copies of it. See
the Data Utilities Operating Guide, 7004 4516.
This entire procedure can be used again to create another copy of your SYSRES in the
event your existing SYSRES is destroyed. If you need to restore only selected files, use
the appropriate procedure. For example, use SETREL/COPYREL to restore your
backup system files. Then, use whatever system facility you used to make backup
copies of your own software (user program libraries and data files) to restore that
software on SYSRES.
Using Diskettes for Your Backup SYSRES
If you decide to build your backup SYSRES on a set of diskettes, your backup copy
should consist of two parts: system files, Including the volume table of contents
(VTOC) for your entire SYSRES, and user files.
To build backup copies of each type of software, Unisys supplies the following two
control streams.
SG3DSFIL
Dumps all your system files to sequential data set label diskettes.
Here is a list of the files saved by SG@DSFIL:
$VTOC SGSOBJ $Y$SEC
SIHPL
$Y$HAC
IVPLIB
$IPL
SGSMAC
SYSHELP
SYSTRAN
$Y$SRC
SHCFILE
$Y$TRANA
$Y$HIC
$Y$CAT
$Y$LOD
$Y$FMT
$Y$SHR
SGSLOD
$Y$SAVE
$Y$EL0G
$Y$SCLOD
$Y$SMCL0G
$Y$ESUH
$Y$JCS
$Y$DIAL0G
$Y$SJF
SG$JCS
$Y$SDF
$Y$SYSTEMTABLES
$Y$0BJ
7004 5505-000
M7
System Generation
SGiDUFIL
Lets you, group the names of up to 20 of your own files and store them under
a single name in the system library, SG$JCS. It also initiates the routine
SG@DMFIL, which actually dumps all files that you've grouped together to
sequential data set label diskettes. Thus, in a single dump operation,
SG@DMFIL can copy up to 20 of your user files. You can also use
SG@DUFIL to save your own software from your existing release before
installing a new release.
Both job control streams feature a restart capability. If you get an error while running
either control stream after a job successfully dumped some of your files, reexecute the
job, using the restart feature to resume where the system left off. The job streams
continue dumping your files, beginning with the file where the error occurred. The
restart feature is shown in the procedure that executes these job streams.
When you build backup files, take the following precautions to ensure that you can
restore the SYSRES if needed:
• Sequentially label the diskettes as you copy them to the SYSRES files so you can
easily restore them. Keep the diskettes in the correct order.
• Get and keep the listings of the SG@DSFIL and SG^DUFIL job streams. They
tell you the exact file sequence on your diskettes.
• Prep diskettes with a record size of 128 or 256. Do not prep diskettes with a VSN
ofSCRTCH.
To build a backup copy of your SYSRES on diskettes, proceed as follows:
Note: If you don't store your own files on SYSRES, or if you don't want to save any
of your own files that you've stored on SYSRES, disregard steps 1 through 8 of
this procedure and go directly to step 9.
1 . Build a backup copy of your own files by keying in:
RV SG3DUFII
2. Press XMIT.
3. When the message ENTER VSN OF INPUT DISC appears, key in the six-
character volume serial number of your SYSRES volume and press XMIT.
4. When the system asks DO YOU WANT TO CREATE A LIST OF FILENAMES
(Y OR N)?, press XMIT if you want to group your user file names under a single
name to expedite dumping them. If you have already done so, key in N and press
XMIT. If you key in N, proceed to step 8; otherwise, go on to step 5.
5. When the message WHAT DO YOU WANT TO NAME THE LIST OF
FILENAMES? appears, key in a one- to eight-character file name and press
M8 7004 5505-000
System Generation
6. Follow the directions that your system displays for keying in up to 20 file names
(each 1 to 44 characters in length) using the FNAME1, FNAME2,...FNAMEn=
format. Press XMIT after each file name that you specify in that group. After you
specify all the file names that you want in one group, key in END and press
XMIT. Your system then stores that list of file names until you are ready to dump
them to diskettes. It then asks if you are ready to dump them.
Note: If you need to make backup copies of more than 20 files, you must rerun
SG®DUFIL, starting at step 1 of this procedure. SG@DUFIL cannot
group more than 20 files at one time.
7. When the message DO YOU WANT TO DUMP THE LIST JUST CREATED (Y
OR N)? appears, press XMIT if you are ready to dump the files in the list that you
just created. If for some reason, such as time limits, you do not want to dump the
files, key in N and press XMIT. If you press XMIT, SG^DUFIL initiates the
SG@DMFIL routine, which actually dumps your user files to a set of sequential
data set label diskettes. If you key in Y, proceed to step 9. If you key in N, you
must rerun this procedure from step 1, but respond to step 4 with N.
8. When the message WHAT IS THE NAME OF THE LIST OF FILE NAMES TO
BE DUMPED? (1 TO 8 CHARACTERS) appears, key in the name of the list of
files that you want to dump and press XMIT. SG@DUFIL then initiates
SG@DMFIL. Now proceed to step 9.
9. When SGODMFIL asks DO YOU WANT RESTART CAPABILITY? (Y/N), key in
N and press XMIT. If you are executing SG@DUFIL to resume dumping the files
after you encounter an error, place the last successfully copied diskette into the
diskette reader, key in Y and press XMIT. Either response causes SG@DMFIL to
dump your user files to a set of sequential data set label diskettes and tells you
when it terminates normally. Go to step 10 to build a backup copy of your system
files.
Note: If you executed SG@DUFIL only to build copies of your own software before
installing a new release, do not perform the remaining steps in this procedure.
1 0. Build a backup copy of your system files by keying in:
RV SG3DSFIL
11. Press XMIT.
12. When the message ENTER VSN OF INPUT DISC appears, key in the six-
character volume serial number of your SYSRES and press XMIT.
13. When SG@DSFIL asks DO YOU WANT TO USE RESTART FEATURE? (Y/N),
key in N and press XMIT. If you are executing SG^DSFIL to resume dumping
your files after you encounter an error, place the last successfully copied diskette
into the diskette reader, key in Y and press XMIT. Either response causes
SG@DSFIL to dump your system files to a set of sequential data set label
diskettes and tells you when it terminates.
7004 5505-000 349
System Generation
To restore the SYSRES, use two parts: system files and user files. To restore the
operating system, you must restore the system files first and user files last.
To restore the SYSRES from diskette, use the following two control streams:
SU3RST
If you received your release on diskettes and if your resident volume
becomes inoperative, use SU@RST to restore the system files from
sequential data set label diskettes to the SYSRES.
SG3RUFiL
Lets you restore your own user files from sequential diskettes to the
SYSRES or to restore your own software that you saved from a previous
release onto the new SYSRES.
To restore your backup system files from diskettes:
1. Follow the IPL and installation procedures defined in Section 2 except that when
SU@RST requests ARE YOU INITIALIZING YOUR SYSTEM, respond N. This
allows files on the output disk to be preserved.
2. When SU@RST terminates normally, reinitialize your system by performing an
initial program load (IPL) to load your desired operating supervisor into main
storage. (See the Operations Guide, 7004 5208.) After you load the supervisor,
proceed to step 4.
3. If you attempt to restore either an incomplete or out-of-date version of your
SYSRES, SU@RST displays an error message indicating that a format label is
mismatched or missing from your VTOC or that your disk does not contain a
VTOC. If you receive these messages, then:
a. Rerun SU@RST, starting at step 1 of this procedure, but respond Y to the
message ARE YOU INITIALIZING YOUR SYSTEM?
b. When SU@RST terminates normally, add the new files that you want on
your SYSRES but never dumped to your backup copy.
c. Using SG@DSFIL make a current and complete copy of your system files and
continue with step 4.
4. To restore your backup user files from diskettes, key in:
RV SG3RUFIL
5. Press XMIT.
6. When the message ENTER VSN OF OUTPUT DISC appears, key in the six-
character volume serial number of your SYSRES disk and press XMIT.
3-50 7004 5505-000
System Generation
7. When your system prompts, WHAT IS THE NAME OR LIST OF FILENAMES
TO BE RESTORED (1-8 CHARACTERS)?, key in the group name that you
assigned to the group of up to 20 files of which you made backup copies using
SG@DUFIL.
Note: If you ran SG@DUFIL more than once to build your backup copy, you
must also run SG@RUFIL once for each set of 20 files of which you made
backup copies.
After you supply this information, SG@RUFIL restores the user files in the group
that you specified and tells you which diskette to mount next.
8. If your system displays a MOUNT message:
a. Mount the requested diskette.
b. Key in R for ready.
c. Press XMIT.
After SG@RUFIL restores all your own backup files, a message tells you that the
routine terminated normally.
Using Tape for Your Backup SYSRES
To save your backup SYSRES on tape, use the job stream SG$DMPDT to dump your
disk to tape.
In order for this tape to be used by the stand-alone restore routine (SU@RST) ? be sure
to:
• Specify dump/restore file mode when creating these tapes.
• Prep your backup tapes without block numbering before running SG$DMPDT if
your system is generated with tape block numbering (TAPEBLKNO=YES). Refer
to the System Service Programs (SSP) Operating Guide, UP-8841, for additional
information on tape prep.
To build your backup SYSRES on tape:
1. Key in:
RV SG$DMPDT
2. Press XMIT.
7004 5505-000 3-51
System Generation
3. SG$DMPDT asks DO YOU WANT THE DMPRST OUTPUT TAPE IN FILE
FORMAT (N,Y). Enter Y and press XMIT.
4. When the message ENTER VSN OF OUTPUT TAPE appears, key in the six-
character volume serial number of your output tape and press XMIT.
When SG$DMPDT terminates normally, the tape backup is complete.
Restoring SYSRES from Tape Using SU@RST
If your backup tape is a current and complete copy of your SYSRES, you can use the
procedures in 2.2.1, which describe the stand-alone SU@PRP and SU@RST routines,
to restore your SYSRES from that tape.
You can use the SU@RST routine to restore your files between disk types with
different capacities. When you restore a disk to another disk with a smaller capacity
(for example, from an M9720 disk to an 8494 disk), the following message is displayed:
RESTORING TO DISK WITH SMAI^LER CAPACITY - CONTINUE ? (Y/N).
Reply Y to continue. If you also reply Y to the ARE YOU INITIALIZING YOUR
SYSTEM prompt, the available space in the VTOC is automatically adjusted.
If your backup tape does not contain your current user files and customized system
files, you may not be able to restore them. You can try one of the following approaches
In an effort to save these files. The success of these actions, however, depends upon
the nature of the problem with your existing SYSRES.
• Before running the stand-alone prep and restore routines, use the online
dump/restore routines to save your user files from SYSRES. After restoring
SYSRES, use these same online routines to return the user files to your new
SYSRES.
• Run the stand-alone restore (SU@RST) routine starting at step 10 in the
procedure in 2.2.1. (Don't prep the disk using SU@PRP.) When the ARE YOU
INITIALIZING YOUR SYSTEM message Is displayed, respond with N. This may
allow files on the output disk that are unaffected by the new load tape to be
preserved.
3-52 7004 5505-000
Section 4
Using an Alternate Method to
the SYSGEN Dialog
4.1. Creating Parameter Sets
The SYSGEN dialog lets you create supervisor, NTR, COBOL, and ICAM parameter
sets with relative ease; the system automatically stores your sets in source modules
(SG$INPUT and IC$INPUT) on the system source library file ($Y$SRC). (SG$INPUT
contains the supervisor, NTR, and COBOL sets; IC$INPUT contains the ICAM sets.)
Once you become thoroughly familiar with the SYSGEN process, you can expedite the
process by creating and modifying the parameter sets by using the general editor
rather than the SYSGEN dialog. The general editor is more efficient in that it lets you
work with only those parameters that you need to add, delete, or modify, thereby
saving you time.
Create your parameter sets on disk or diskette as 80-column card image source
modules. Give them any name you want and store them in any file. (If your sets are on
keypunched cards, submit the cards to the parameter processor when you run
SG$PARAM.) To create your parameter sets, you need to know the choices for each
SYSGEN phase, their coding formats, value ranges, and their defaults. Use the tables
in 4.2 to assist you in selecting the appropriate SYSGEN keyword parameters. Also
use the guidelines and formulas provided in the SYSGEN parameter reference tables
in 4.3 to help you specify particular SYSGEN parameters.
When you generate parameter set source modules without the aid of the SYSGEN
dialog, it is your responsibility to ensure that all parameters are valid and to manually
execute the parameter processor as defined in Section 3.
If you omit the label parameter for a particular SYSGEN phase, the system does not
execute that phase. OS/3 does not provide default parameters that identify the
SYSGEN phases. Also, you cannot specify parameters on the same statement of the
label fields. For example, don't specify any parameters on the statement containing
the SUPGEN label in the label field.
7004 5505-000 4-1
An Alternate SYSGEN Method
4.1.1. SUPGEN
The statements containing the supervisor configuration parameters immediately
follow the statement with SUPGEN coded in the label field. Use this statement to
signify the start of the supervisor section. Use the statement with END coded in the
label field to delimit It. Each SUPGEN phase consists of one SUPGEN section
immediately followed by its associated Input/output (I/O) device configuration.
You can specify all the SUPGEN keyword parameters In any order, but specifying the
SUPMOD parameter tells the parameter processor to ignore all other keywords for
the SUPGEN section. Therefore, if you specify SUPMOD, It must be the first one
specified in this section. Specifying the SUPGEN keywords and SUPMOD actually
wastes time. The SUPGEN keyword parameters are listed In Table 4-1.
4.1.2. i/OGEN
This phase must immediately follow a SUPGEN phase in order to form a complete
supervisor definition. If you have specified the generation of multiple supervisors In
SUPGEN, you must also prepare Individual I/OGEN configurations for each of those
supervisors. Each I/OGEN section must immediately follow Its associated SUPGEN
section.
Submit the I/OGEN configuration specifications in the form of label parameters and
keyword parameters immediately following the statement containing the 1/OGEN
parameter coded in the label field. The 1/OGEN parameter signifies the start of the
I/OGEN section, and an END statement coded in the label field delimits it. The label
parameters Identify a device category - PRINTER, READER, PUNCH, DISC,
DISKETTE, TAPE, and WORKSTATION. The keyword parameters define the
particular specifications for that category, such as ADDR or TYPE. The I/OGEN
keyword parameters are listed in Table 4-2.
When you specify the hardware configuration to OS/3, include a device category and a
type parameter for each device in the system, even if you want to accept the default
values for them. Otherwise, OS/3 generates the supervisor without an I/O
configuration for those devices.
Define each I/O device in the order of most frequent use to reduce I/O access time
during later processing. You do not need to define all devices for the same category
consecutively (even if they are of the same type). For example, you can define the disk
device containing the SYSRES volume first, followed by printers, readers, tapes, other
disk devices, punches, and workstations.
4-2 7004 5505-000
Ail Alternate SYSGEN Method
The I/OMOD keyword parameter tells the parameter processor to ignore all other
keywords for the I/OGEN section. If an existing I/O configuration meets your present
requirements., you can specify it by using the I/OMOD keyword parameter to name the
supervisor in which you defined that I/O configuration. If you specify I/OMOD, it must
be the first parameter that you specify.
4.1.3. COHIUCI
The keyword parameters used to define communications generation are divided into
two categories: network definitions and message control program (MCP) definitions.
The network definition portion creates a communications control area (CCA). The
MCP portion includes the processing modules needed by ICAM and defines the
physical characteristics of each single line communications adapter (SLCA) in the
system. The COMMCT keyword parameters are listed in Table 4-3.
This guide does not describe the ICAM network definition parameters, only their use
in generating the ICAM symbiont. See the ICAM" Operations Guide, 7004 4557, before
attempting to configure an ICAM network definition.
The network definition parameters immediately follow the statement with COMMCT
coded in the label field. Each network definition starts with a CCA macroinstruction
and ends with an ENDCCA macroinstruction.
The coding of network definition macroinstructions and operands follows these OS/3
assembler coding rules:
• Follow each operand with a comma, except the last operand.
• Continue a macroinstruction on additional statements, using standard
continuation conventions; that is, specify a trailing comma after the last operand
on a line and a non-null character in column 72. Start the next operand in column
16.
• Start and end an operand, its specification, and its trailing comma (if required) on
the same statement.
When you use an existing network definition, specify the four-character name of a
previously saved network definition in the system source library file ($Y$SRC) of the
SYSRES. Specify this source module with the CCAMOD parameter in place of
network definition macroinstructions. Each CCAMOD parameter must be followed by
an ENDCCA parameter.
7004 5505-000 4-3
An Alternate SYSGEN Method
The MCP portion of COMMCT must begin with MCP coded as a nonlabel parameter.
This parameter functions as a delimiter that signifies the end of the network
definition and the beginning of the MCP parameters. The statement with END coded
in the label field then delimits both the MCP parameters and the entire COMMCT
section.
The MCP parameters differ in format from the network definition macroinstructions
because they follow the SYSGEN coding rules. Blank characters delimit them. You
can submit the MCP parameters in separate statements without indicating
continuation (X in column 72).
The MCP keyword parameter, CACH, describes each SLCA that the 1CAM symbiont
accesses or supports. It has three formats that identify SLCAs used by
communications lines, dialers, and virtual channels.
• Format 1 lets system generation access the 1CAM network definition and
determine the SLCA requirements automatically. If you use this format to define
an automatically dialed (for output) switched line, do not also specify a format 3
CACH statement for the dialer SLCA,
• Format 2 lets you explicitly define the requirements for an SLCA that carries
data. When you use it to define an automatically dialed switched line SLCA S you
must also include a format 3 CACH statement to define the dialer SLCA.
Communications physical interface (CPI) users and universal data link control
(UDLC) users must use this format.
• Format 3 defines dialer SLCAs. Use this format when you have used format 2 to
define an SLCA for an automatically dialed switched line.
Logical network users (including global network users) can specify either format 1 or
format 2 for SLCAs used by communications lines. Communications physical interface
(CPI) network users and UDLC SLCA users must use format 2. Format 3 is used with
format 2 and describes a dialer SLCA, Use it only when the autodial capability is
included for a communications line.
44 7004 5505-000
An Alternate SYSGEN Method
4.1.4. NTRGEN
The first statement in the NTR generation set must be a statement with NTRGEN
coded in the label field to signify the beginning of the NTR section. Don't code
anything else on this statement. Following this statement are statements containing
the NTR and LOCAL keywords. A statement with NTR coded in the label field
precedes each set of NTR statements, and a statement with LOCAL coded in the label
field precedes each set of LOCAL keywords. The last statement in the NTR generation
set must be one with END coded in the label field to delimit the NTR section.
NTRGEN can accept and process various input NTR and LOCAL keyword set
configurations. You can follow or precede NTR keyword data with up to 14 sets of
LOCAL keyword data, or you can process the NTR or LOCAL keyword data alone.
This capability lets you preprocess LOCAL keyword data sets and then link them with
the NTR module when you process the NTR keyword data. Only when NTRGEN
processes NTR keyword data does it produce the job streams needed to produce an
NTR system utility module, whether or not LOCAL keyword data sets are present.
When you omit the NTR section, you can preassemble LOCAL keywords for future use
by running the job stream SG$NTRMK. The NTRGEN keyword parameters are listed
in Table 4-4.
When you specify a previously generated NTR network name, the first keyword
specified in this section must be NTRMOD. The parameter processor ignores all other
parameters except NTRVOL, NTRNAME, and TASK and writes a diagnostic message
in its output listing.
4.1.5. COBGEN
A statement with COBGEN coded in the label field must immediately precede the
COBGEN parameter specifications. This statement signifies the beginning of the
COBGEN section, and a statement with END coded in the label field delimits it. The
COBGEN keyword parameters are listed in Table 4-5.
4.2. SYSGEN Keyword Parameters
Tables 4-1 through 4-5 list all the SYSGEN keyword parameters you can specify when
preparing your parameter sets. Each parameter is shown in its correct coding format,
with parameter value ranges, default values, and descriptions of parameter functions.
Note: See 4.3 for the SYSGEN parameter reference tables (Tables 4-6 through 4-13)
to help you code parameters.
7004 5505-000 4-5
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters
Phase
Parameter in Coded Format
Description
SUPGEN
[ SUPMOD=supvrnam ]
SUPVRMAM=
^supervisor
$Y$STD
Requests a previously generated supervisor
stored in $Y$SRC. SUPMOD must be the first
keyword specified in this section; all other
SUPGEN parameters are ignored except
SUPVRMAM.
Names generated supervisor or renames
previously generated supervisor when used
with SUPMOD; 1-6 characters.
SUPERVISOR SIZING PARAMETERS
DLOADBUFR-
"[ 1- 32767 j
DLOADTABLE=
1-255
ERRLOGBUF=
{7-2488J
EXECPRI=
n
Maximum number of 256-byte blocks of main
storage dynamically allocated (expanded)
for a job. Recommended for use with ANSI 1 74
COBOL compilers. If you want COBOL CALL
statements to dynamically expand your job
regions, specify the maximum value, 32767,
unless you must limit the expansion by
specifying a smaller value.
Number of entries per job in the job DLOAD
table. Recommended for use with COBOL
compiler. Choose a value equal to the
maximum number of COBOL CALL statements in
any one COBOL job. For example, if JOBA
contains 4 CALL statements and JOBB contains
10, specify DLOADTABLE=10.
Number ©f resident 80-byte buffers for error
logging. For additional buffers, use the for-
mula N x80 where U is the number of addi-
tional buffers. The minimum and default
value is 6.
The job step processor defaults to a user-
specified priority rather than the lowest
execution priority. If the priority is not
specified on the EXEC statement, this is the
value used. This value cannot exceed the
PRIORITY keyword value. The default value <d)
is one less than the PRIORITY keyword value
(or default), with 1 as the minimum value.
continued
4-6
7004 5505-000
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont)
Phase
Parameter in Coded Format
Description
SUPGEM (cont)
EXPBFCTS2=
expreg!oh= mm \
J0-999999 J
Specifies the maximum number of dynamic
buffer control blocks CDBCB) that can be
dynamically allocated at any one time should
the resident control block become full.
Smaller allocations than the value specified
will be made if a free region exists at a
low address that can accommodate a minimum
number of DBCBs.
When possible, the system consolidates DBCBs
in the dynamic regions into the resident
control block as memory becomes available
there.
The DI BI command is a useful tool when
attempting to determine the optimal value.
Size in bytes of system dynamic buffer pools
within main storage from which the system
dynamically allocates buffers to a job. To
avoid continuous dynamic allocation of buffer
pools altogether, specify EXPREGION=0.
This specification forces dynamic buffer
management to restrict its allocation of
buffer pools to one pool. The size of this
pool is determined by the value specified on
the RESBUFSIZE option. All buffer requests
are then satisfied by acquiring memory from
within this pool. If this pool becomes
totally allocated, critical buffer requests
are satisfied from the resident buffer pool,
while others are placed in an awai ting-
memory state. Although this configuration
can reduce fragmentation between buffer
polls, it is less dynamic in its use of
memory and can therefore be more wasteful .
If too much buffer space is set aside, the
memory within the large buffer pool is never
utilized by the user. If not enough is set
aside, tasks spend an inordinate amount of
time waiting for memory. This configuration
must be very precise.
You can change values each time you perform
an IPL to load this supervisor. See the
Operations Guide, 7802 5208.
continued
7004 5505-000
4-7
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
JOBSLOTS-Jli 1
I 2 " 48 !
PRIOR
ITY= M-601
RESBFCTSZ=
180-9999
Specifies the number of concurrent jobs that
can run in the system.
■ One job slot is always reserved for
interactive services (IS); and
• If transaction platform software (TPS) or
TIP/38 is implemented, two job slots
are reserved.
■ If the information management system
(IMS) is implemented, two job slots
are reserved.
Once set during SYSGEN, this parameter
cannot be changed without generating a new
supervisor.
Establishes the number of task priority
levels in a mult! jobbing environment.
The maximum number of dynamic buffer control
blocks (DBCB) for which resident memory is
set aside. A DBCB is created for each buffer
created in the resident and dynamic buffer
pools. A DBCB contains 36 bytes ©f informa-
tion pertaining to its associated buffer.
To handle priority situations^ a few of the
DBCB slots available in the resident control
block are reserved for buffers requested at
times when no memory is available for
additional DBCBs. For one of these slots to
be utilized, a critical routine must request
the buffer at a time when a DBCB cannot
be allocated from memory. This number
depends upon the size of the region, but
will not exceed 18 slots.
The specified value should be the average
number of buffers in use at any one time
plus 18 to cover the reserved DBCB slots.
This ensures the most efficient use of
memory.
continued
4-8
7004 5505-000
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont.)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
[RESBUFSIZE=lH-999999]
This value cannot be altered during IPL. If
more buffers are requested than can be
satisfied by this value, free memory is
allocated as control blocks, based on the
size specified in the EXPBFCTSZ option.
Additional control blocks are only allocated
during peak buffer conditions. Under normal
conditions, when all the DBCBs fit into the
resident memory, no additional memory regions
are allocated.
The Dl BI command is a useful tool when
attempting to determine the optimal value.
Resident buffer pool size, in bytes, within
the supervisor, from which the system
dynamically allocates buffers. This value
reserves buffer regions within supervisor
memory for use by critical routines that
require memory at a time when user memory
unavailable. This requirement occurs
infrequently, and only small amounts of
>ry are required at any one time.
is
The default size of 800 bytes should always
be used unless no expansion buffers are
desired (EXPREGION=0), in which case a
buffer size large enough to accommodate all
buffer needs must be specified.
Note: If a value larger than 800 is specified
the option is flagged by SYSGEN and
the default value (800) is used.
If you specify EXPREGION=0, the size
specified on the RESBUFSIZE option becomes
the size of a single buffer pool. This is
the only buffer pool created during this
boot period. This buffer must then be large
enough to accommodate the maximum amount of
dynamic buffer memory requested at peak
periods of buffer usage, or the tasks, on
whose behalf the memory has been requested,
are placed in a waiting- for -memory state.
continued
7004 5505-O00
4-9
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
SHAREDMGT=
m i
1-2000J
[SYHBIOMT=symbiont,8-59]
The resident buffer pool size defaults to
808 bytes if this configuration is specified.
If you ever need to change the value that
you specify now, you can do so each time you
perform an IPL to load this supervisor. See
the Operations Guide, 7004 5208.
Total number of 40 -byte slots reserved in
resident table that controls shared data
management modules. Each shared module, at a
given time, requires one table entry or
slot. For most multi jobbing applications,
default values are sufficient. For unusually
heavy multijobbing systems, specify higher
values; if less than three job slots, specify
lower values.
Assigns a specific execution priority to a
specific symbiont. Enter this option for
each symbiont to be assigned its own
priority. Those not assigned a specific
priority are executed at the priority
specified on the SYMBPRI parameter.
Name Symbiont
BEG
Begin
BRK
Breakpoint
CHA
Change job queue
CS
Create symbiont
DEL
Delete
DT
Device trace
FIL
File
HOL
Hold
IED
I CAM trace display
IU
Input
10
I/O trace
MM
Mini monitor
MOM
Monitor
PD
Output writer (data set label diskette)
PR
Output writer (printer)
PU
Output writer (punch)
PT
Patch transient
RP
Output writer (aux printer)
RUN
Run processor
RV
Run processor (without card reader)
SCH
Schedule (without card reader)
SI
Schedule (with card reader)
SPM
System performance monitor
su
System utility
TU
System utility (also)
VV
VTOC verify
continued
4-10
7004 5505-000
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
SYMBPRI = f8-59'
I=jC
TRANS=
N
If you specify a symbiont name more than
once, the first occurrence is accepted. All
subsequent specifications are ignored, and
an error message is issued.
Priority Level for running system symbionts
(including job scheduler, but excluding
ICAM). When a PRIORITY value of 8 or less is
specified, the default (d) is three less,
with a minimum value of 8. Otherwise, the
default value is 5.
The SYMBIONT parameter can be used to
assign specific priorities to individual
symbionts.
Number of 1200-byte transient areas in main
storage. As the number of transient areas
increases, more jobs using them can run con-
currently. The number of transient areas
generated cannot exceed 15.
SUPERVISOR FEATURE PARAMETERS
ALTJCS=f Rename,
[,S]
Identifies the file that is to be the system
default for the alternate $Y$JCS library via
a file name (Iblnaroe) and the disk identifier
in which the file resides. The disk
identifier is not required if the file is
cataloged.
The S option suppresses operator message R06
when a job is not found in the alternate
library and continues the search in $Y$JCS.
continued
7004 5505-000
4-11
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont)
Ph£
Parameter in Coded Format
Description
SUPGEN (cont)
CACHESEGS
!ZE= Jn ]
|yes}
CONALARM=
1
[ONI
DAYCHANGE
■P
Specifies the number of 1824 -byte blocks in a
cache segment. A YES response indicates that
a message appears requesting the cache
segment size during cache initialization.
Otherwise, allowable values for n are 2
through 24.
If this keyword is not specified, the
following values are used by CACHE
initialization:
CACHESEGS I ZE
Cache Buffer Size Default
64/168-255
3
256-511
6
512-1824
12
1825-8192
12
Changing the segment size can affect perfor-
mance. See the Operations Guide, 7004 5288,
for guidelines on selecting appropriate
it sizes.
Specifies whether to sound an audible
alarm uhen an action or reply message is
delivered to the system console.
If CONALARM=YES is specified, a continuous
beep sounds. If CONALARM^OME is specified,
a single beep sounds.
Specifies whether the supervisor
automatically changes the date and time at
midnight of each day. This feature requires
approximately 20 bytes.
continued
4-12
7004 5505-000
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont.)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
DMGTMODE= [MIXED!
DMRECV=
m
YES
INDEX
Specifies the type of data management
supported.
CD I
The system uses only consolidated data
management (common data interfaces). The
only exception is that SAT files can be
accessed using basic data management
(define the file CDTF) interfaces).
Mote-. Some disk file types (for example,
SAM, DAM, ISAM) cannot be accessed in
this mode. Specify MIXED to permit
access to these file types.
MIXED
The system operates in a mixed data manage-
ment mode. You can execute in either basic
data management (DFT) interfaces or
consolidated data management (CDI)
interfaces.
Specifies whether IRAM/MIRAM files are
created with the recover option. This can be
overridden for individual files with the RECV
parameter of the DD job control statement.
Note; Temporary job work files (physical file
names prefixed with SSCR and SJOB) are
created without the recovery option.
MO
Recovery is not used for any files.
YES
Recovery is used for all data files
(i.e., not MIRAM library files).
INDEX
Recovery is used for indexed data files
only (i.e., not nonindexed or MIRAM library
files).
continued
7004 5505-000
4-13
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (corrt)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
DUMPVSN= JSYSRES
' vsn
FILELOCK= [SHARE j
See the Job Control Programing Guide,
7004 4623, for details on the format of the
DO statement* See the Consolidated Data
Management Programming Guide, UP-9978, for
details on the recovery option CRECV DD
parameter).
Supports $Y$DUMP file on a non-SYSRES device.
During IPL, the time/date screen provides an
option to specify the channel /address of the
disk device that contains $Y$DUMP. During
system initialization, $Y$DUHP is allocated
on the non-SYSRES disk when required.
If an alternate dump file is requested,
SYSRES contains a minimum SY$DUMP file for
dumps taken during system initialization.
Specifies nhich files are lockable.
If a file is lockable, the data management
file share facility guarantees that the
program's share requirements are honored.
These requirements are usually specified by
the ACCESS parameter in your program or by
the ACCESS parameter of the DD job control
statement.
If a file is not lockable, the file share
facility is not invoked and there is no
protection against invalid use of the file.
YES
Only files whose LBL names are prefixed
with $Y$ or SLQKnn are lockable (where nn
can be from 01 to 99). You should specify
this only if you have an explicit need to
have nonlockable files.
SHARE
All files are lockable.
This parameter only applies to basic data
management def ine-the-f ile (DTF) interfaces.
In consolidated data management, all files
are lockable and are independent of this
specification.
continued
4-14
7004 5505-000
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont.)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
IGNJCERR= Jlffli
[E,R86][ f E58]
1GN0RESFT= [YES]
IMVJOB=
Pf
JCREADWKS= [life
W
Allows certain job control error conditions
to be ignored.
R06
Suppresses the R06 message when a job
can not be found in the alternate library.
Prevents $Y$JCS from being searched.
E58
Prevents a JC58 message when a job cannot
be scheduled because the required work-
station is busy with another job-
Specifies whether the system ignores // SFT
statements.
YES
All // SFT statements are ignored and the
data management modules these statements
identify are loaded as the job needs them
during execution. Allows you to use dynamic
shared code without having to delete //SFT
statements from existing control streams.
This feature is recommended to provide
improved ease of use.
NO
All // SFT statements are processed and the
data management modules that these state-
ments identify are loaded before the job
is scheduled*
Allows relocation (shuffle) of immovable
jobs to more efficient memory utilization
locations. Rollout is required.
Specifies whether workstation- initiated job
control commands <RU, FI, and SI) can be
read from the card reader.
Note: Make sure that the cards you want to
read are actually in the card reader
at the time you issue the command.
continued
7004 5505-000
415
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont)
Phase
Parameter in Coded Format
Description
SUPGEM (cont)
r i
-
JOBQUEREC= \m 1
Job queue recovery at I PL.
YES
[holdJ
J
YES
System recovers all jobs scheduled and
queued when shut down.
HOLD
System recovers and holds all queued jobs
until ready to run.
Must be set to NO if specifying any of
the following parameters: SYMBMEM, INTMEM,
JOBMEM, MAX JOBS, MAXWSJOBS, MAXSWSJOBS, or
MAXRUNSYHBS.
MAXTIME=
[1 1
Default time (minutes) for the maximum time
'
1-9991
parameter on a job statement. To execute, you
-
must also specify (no default) spooling and
job accounting.
MAXTYPE- [He]
Specifies if the max-time parameter on a JOB
|cpu ■
statement defines the elapsed wall -clock time
[wALLJ
or the job CPU time.
MEMCON=
[YESl
Allows execution with or without job consoli-
NO j
dation when free memory is available.
MIRAMCHAR= JlO 1
JYESj
Indicates if newly created M1RAM files are
created as HIRAM CHARACTERISTIC.
MO
Designates HIRAM CHARACTERISTIC based
on file characteristics (default). If the
file contains any of the characteristics,
it is created as MI RAM CHARACTERISTIC.
See Consolidated Data Management Program-
ming Guide, UP-9978, for details on
required characteristics.
YES
The files are always created as MI RAM
CHARACTERISTIC. You can use TRACK ALLO-
CATION and MILOAD for all MIRAM files
since these facilities are only used on
MIRAM CHARACTERISTIC files. On the model
8, it is possible to use BDM I RAM (an RPG
program compiled on a Series 90 system,
or a BAL program). An attempt to open a
MIRAM CHARACTERISTIC file using IRAM
results in a DM61 TYPE=19 error.
continued
4-16
7004 5505-000
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (coot)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
RECOVERDS=
py
RESHARE= [mod-name- 1
[group -name -sym- 1
",mod-name-2
, group- name- sym- 2
Lmod-name-n 1
j,group-naroe-sym-n]
ROLLOUT- ffllll
Specifies the option of either recovering
disk space to retry a job or terminating a
job Mhen the job step processor displays a
warning message that it cannot allocate
sufficient disk space for the job.
List of shared load module names or shared
load module group names that you want
resident in main storage. This option helps
avoid fragmenting main storage space when
modules are used frequently. If you want to
specify individual module names, execute the
SCLIST job stream by keying in RV SCLIST. The
job lists all module names eligible for RE-
SHARE. If you want to specify shared load
module group names* see Table 4-7 for a list
of eligible group names.
To decide which modules to make resident for
your applications, see the Supervisor
Technical Overview, UP-8831. If you need to
change the RESHARE specification, you can do
so each time you perform an IPL to load this
supervisor. See the Operations Guide,
7004 5208.
YES
Specifies the capability of the supervisor
to recognize jobs with preemptive priority.
The supervisor can roll lower priority jobs
out of main storage for higher priority
jobs and later roll the lower priority jobs
back into main storage.
NO
The supervisor automatically equates the
preemptive priority jobs to high priority
jobs and no roll in or rollout is performed.
Note: IMVJOB requires ROLLOUT=YES.
continued
7004 5505-000
417
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont.)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
RUNVSN=
SYSRES
SYSSPL
vsn
SAM=
m
SCDINDEX=
NO
t SCRATCHDVC=vsn , dvcno ]
SYSTEMDATE= [fw
MDY
DMY
TAPEAVR= fYESl
Run device volume serial number.
SYSRES
System resident volume as RUN device.
SYSSPL
First spooling volume as RUN device
(spooling must be configured).
Serial number of the volume serving as RUN
device.
Specifies whether the system activity
monitor dynamically links itself with the
supervisor when you load the monitor. See
System Activity Monitor Programming Guide,
UP-9983, for details.
Note: SAM collects device statistics for both
I/O and DSK classes according to the
device s s position in I/OGEN. It does
not collect statistics for any more
than 72 devices. Therefore, be sure
that the real devices that you intend
to have SAM monitor are the first 72
listed in the I/OGEN.
Allows faster loading of shared code modules
into main storage and faster processing
between two or more shared code modules.
Commonly used shared code modules include the
general editor, interactive services, data
management, and ESCORT. Requires about 4080
bytes of main storage.
Defines the location of the default work and
temporary files for RES and RUN,
System date format at I PL. YMD defines
yy/mm/dd, MDY defines mm/dd/yy, and DMY
defines (M/rnn/yy.
Specifies whether tape automatic volume
recognition is supported during system
initialization.
continued
4-18
7004 5505-000
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont.)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
TAPEBLKNO= Jll j
|YES}
TRNWKAREA=
YES
32-250
[UNATCONSOLE=l-30]
VVAVR=
w
Specifies whether the supervisor supports
tapes written with block numbers.
Specifies whether the system generates a
32K- to 250K- transient work area to keep
the roost recently used transient modules in
main storage. If specified, transients can
be loaded into main storage directly from
the work area instead of from the SYSRES
volume. This reduces the number of I/O
delays that occur and thus improves perfor-
mance. Specifying YES initializes the
transient work area to 250K at initial
program loading (IPL). This feature is for
systems other than DTF-only systems.
To change the TRNWKAREA specification, you
can issue the TU command after you perform an
initial program load (IPL). See the Opera-
tions Guide, 7004 5208.
The unattended console feature specifies
whether hardware error messages that require
an RU (retry/unrecoverable error) or RC
(retry/cancel) response are automatically
answered by the operating system. Values
1-38 specify time (in minutes) that elapses
before the error message is answered automa-
tically with either a C (cancel ), or U (unre-
coverable error) response. The default
value suppresses this feature.
Indicates whether automatic volume table of
contents (VTOC) verification is performed
at automatic volume recognition (AVR) time.
See the Operations Guide, 7004 5208, for
details on the VTOC verification routine.
continued
7004 5505-000
4-19
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont.)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
SUPERVISOR HARDWARE PARAMETERS
CHAN=
(1
CHAN1=
COMM=
1-14
YES
COMM
" {f u}
[DCPCHNL=n]
Specifies the input/output processor (IMP
or 10P) channel number.
Specifies the second input/output processor
channel number.
You must specify if the system supports
communications capability (I CAM). Specifies
ICAM network interfaces with conrounica-
tions terminals; value specifies the
number of cosmnunication lines (SLCAs)
in the system .
YES
ICAM network interfaces with directly
connected local workstations only. Do
not specify YES if you have both local
workstations and communi cat ions
terminals.
NO
Communi cat ions not supported.
Must specify if system supports communi ca-
tions capability (ICAM) and two iOMP
channels. Definitions are the same as the
COMM parameter.
Channels to which DCPs are connected. If
specified, the channels can only be used by
ICAM and cannot be specified in I/OGEN.
Up to four channels can be specified. Entries
must be separated by commas.
Valid entries are:
1-3, 6, or 7 for model 8
1 through 6 for models 18 through 28
continued
4-20
7004 5505-000
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (conL)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
FLOATPT= FYESl
IORB=
J5 x
[5-150
iorbi= |5;:k;otmii
Specifies whether your supervisor supports
floating point software.
Specifies the number of input/output resource
blocks (IORBs) to be generated for the
channel. Default value is equal to 5 times
the number of communication lines specified
in the CQMM parameter.
Number of IORBs to be generated for the
second channel. Default value is equal to 5
times the number of lines specified in the
C0MM1 parameter.
INTERACTIVE SERVICES AND SECURITY PARAMETERS
DDPSC=
YES
REM
Specifies whether host- ids are checked as
part of a user's identity nhen the user
enters a command into the system from a
)te host (if DDP is in the system).
NO
Specifies that commands entered into
this system from remote hosts via DDP
are not restricted. This is the default.
YES
Specifies that commands entered into
this system from remote hosts via DDP
are restricted. Host- ids are not included
as part of the identity of the user en-
tering a command into the system.
REM
Specifies that commands entered into
this system from remote hosts via DDP
are restricted. Host- ids are included as
a part of the identity of the user enter-
ing a command into the system.
Note: If DDPSC=YES or DDPSC=REM is specified,
user profiles must be created for users
entering commands from remote hosts.
continued
7004 5505-000
4-21
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (corrt.)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
[ISADMID=administrator-id]
ISBATCHLMT
ISINTLMT=
j'l'-ZSs}
{'l-ZSs}
[ISINTPRNl-68]
ISLOGONSC-
YES
1- to 6-character id identifying the system
security administrator (only user who can
add or delete other user names from security
file). The first character of the administra-
tor-id is an alphabetic character; the
remaining five must be alphanumeric. If id
is not specified, the system defaults to no
id and n© security administrator exists. When
using the security maintenance utility, you
must specify an administrator id; otherwise,
you encounter errors. If you identify a
system security administrator, ISLOGONSC-YES
must also be specified*
Maximum number of batch sessions that can
execute concurrently in the system. Batch
sessions use only card, card image, tape, or
disk input.
Maximum number of interactive users the sys-
tem recognizes at any one time. Interactive
sessions use input only from a workstation or
an interactive communications terminal.
Priority level of interactive commands
entered from workstations or interactive
terminals.
Logon security. The system checks the secur-
ity file when a user logs on. If ISLOGONSC-
YES, identification roust be a valid name in
the file. If ISLOGONSC=NO, any user can log
onto the system with any identification.
Commands are restricted according to the
restrictions in the user profile.
If you specify YES, the ISADMID parameter
must also be specified.
If PASSWORD or DDPSC are specified as YES,
this keyword roust also be YES.
continued
4-22
7004 5505-000
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont.)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
ISWKSBULs
Jllljll]
[NO ,NO J
ISWKSLOG=
YES,YESl
[NO ,N0 J
ISWORKn= [RUN]
vsn
PASSWORD= fm 1
Jyes}
Interactive services (IS) logon BULLETIN
default value and override option. The first
entry specifies whether YES or NO appears as
the default for the BULLETIN on the logon
screen. The second entry specifies whether
the interactive services user can change
the value that appears as the default.
Interactive services (IS) LOG default value
and override option. The first entry
specifies whether YES or NO appears as the
default for LOG on the logon screen. The
second entry specifies whether the
interactive services user can change the
value that appears as the default.
An interactive services (IS) work volume
specification that controls where EDT #
ESCORT # and BASIC work files are allocated,
n is a number from 1 to 4 that specifies the
number of different work packs among which
work files can be distributed. The system
obtains work space equally from only the
specified volumes. If all parameters are
omitted, then work space is allocated on the
execution time RUN volume.
Notes If a system failure occurs when EDT,
ESCORT, or BASIC work files are open,
a re-IPL merely scratches the files on
the RES and RUN volumes. Use the SCR
job control statement to scratch work
files on volumes other than RES or RUN,
Specifies whether all users are required to
enter a password in order to log on.
continued
7004 5505-000
4-23
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
SUPERVISOR SPOOLING PARAMETERS
SPOOL ING=
m i
INPUT
OUTPUT
•
REMOTE
_DDP
Indicates spooling type. See Spooling and Job
Accounting Operating Guide, 7084 4581.
NO
No spoo ling capab i I i ty .
INPUT
Both input readers and output writers are
used for spooling.
OUTPUT
Only output writers are used for spooling.
REMOTE
Remote batch processors, input readers,
and output writers are used for spooling
mode. If SPOOLING=REMOTE, also specify
SPOOL I CAM.
DDP
Distributed data processing, remote batch
processors , input readers, and output
writers are used for spool ing* If
SPOOL iNG=DDP, also specify SPOOL I CAM.
Main storage requirements for spooling:
■ 4808 bytes for spooler
« 720 bytes for system control table
■ Directory requi rement :
72 bytes for OUTPUT
128 bytes for INPUT
168 bytes for REMOTE
32 bytes for each virtual device in
I/OGEN
4 bytes times number specified by
SPOOLMAP for spool -file bit map
Any spooling option requires resident
SMSTASK module
continued
4-24
7004 5505-000
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont.)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
cqnprint= [no 1
{yes}
CONSOLOG=
MAX
MIN
NORM
ddpspool^ rie 1
tl-128|
JOBACCT=
H
Note: If spooling is not configured, all
other keyword parameters associated
with it are ignored. Also, no virtual
devices or direct printers are in
I/OGEN.
Console log (C records) printed when file
breakpointed.
Indicates whether console log C records and
workstation log W records are collected.
Also specifies the size of the main storage
buffer area for storing. The system collects
a record of all communication between the
system and the console (log) and between the
system and the workstation (log) in this
buffer. It then copies it into the spool file
when it fills the buffer area. MIN specifies
304-byte buffer; NORM specifies 568-byte
buffer; MAX specifies 1872-byte buffer. If it
is omitted or if NO is specified, the console
and workstation log are not recorded in the
spool file.
Specifies the number of concurrently running
tasks that can return spool out of distribut-
ed data processing (DDP) jobs. Each task
that can return DDP spoolout needs a task
control block and at least 8K of dynamic
buffer space.
In most cases, the default value of 18 tasks
is sufficient. If, however,, your system
takes too much time to return the DDP
spoolout, raise the value. If the default
value of 18 tasks degrades your system's
overall performance, lower the value.
Resident job accounting routines maintain a
record of CPU time used by these job and job
step facilities: number of I/O requests per
device, number of supervisor requests, main
storage use, and transient function use,
Specify only if spooling is configured. Adds
approximately 350 bytes to the resident
supervisor in addition to 100 bytes in each
job prologue.
continued
7004 5505-000
4-25
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
RETAINLOG=
YES
SPOOLBUFR=
a
4
8
16
32
SPOOLBURST=
m
SPOOLCOMP=
SPOOLCYL=
ALL
1-1808
Console log (C records) retained in spool
file after printing.
Size of spooler work buffer allocated to
each job preamble in terms of number of
256-byte blocks of main storage. Specify
only parameters shown in format.
Output spooling functions in burst mode.
Operating in burst mode requires the output
processing criterion to be configured to the
control output writer's mode of processing
for available output subfiles* Enables output
files to write before the termination of an
associated job s depending on the criterion
selected. Operating in nonburst mode implies
that the output subfile processing by the
output writers is not done until the job is
terminated.
Specifies if your supervisor compresses the
output image in a spool file. If this para-
meter is omitted, the output image of the
spool file is compressed if three or more
consecutive blanks are present. Do not
specify SPOOLCOMP=NQ when most of the files
created contain a large amount of blanks or
use block sizes greater than 128.
Number of cylinders initially allocated for
the spool file on the primary spooling
volute. The default is recommended. If this
selection exceeds the default value of dev-
ices in i/OGEN the default number of spool
cylinders is insufficient. ALL allocates all
available cylinders on the primary spooling
volume. This option should be used only for
a dedicated spooling volume.
continued
4-26
7004 5505-000
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont.)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
SPOOLCYLn=
ALL
SPOOL PARS I = flo 1
JYES}
SPOOLHDR= fYES'
m
Specifies the number of cylinders initially
allocated for the spool file on the nth
sequent i a I spoo I i ng vo I ume ,
Spool file allocation (SPOOLCYL and
SPOOLCYLn) is done only at spooling
initialization when:
■ Mo spool exists on the spool volume
■ The sequence of the spool volume is
different from that of the previous boot.
To increase or decrease the amount of spool
space on an existing spool volume,, the file
must first be scratched. Do this by booting
in the supervisor* using a different spool
volume. After the system is initial ized f a
user- initiated job stream is executed to
scratch the spool file (SYSPOQL) on the
required volume. Upon rebooting of the
supervisor , which uses the spool volume that
was just scratched, spool space is allocated
as designated by the SPOOLCYL OR SPOOLCYLn
parameter.
PARS I (Iranian language) translation execut-
ed for all spool files containing *FARSI or
3FARSI as first six characters of // LBL job
control statement. To accommodate this cap-
ability s the output writer is loaded with an
additional 488 16-byte increments of main
storage and the input reader is loaded with
an additional 300 16-byte increments.
Spooled output files are printed without
headers- If omitted, a 3-page header
precedes the printing of each spooled file.
continued
7004 5505-000
4-27
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
SPOOLICAM=
SPOOLMAP= fm
\ 1-32767
SPOOLMAXLIME=
1-255
SPOOLMAXREC-
m
SPOQLH0DE=
ACCTNO, account -
number
CARTNAME, cartridge-
name
DEVICE, device-type-
code
FILE, filename
FORM, form-name
JOB, jobname
Name of ICAM symbiont load module (C1-C9 and
H1-M9) called by spooler to service e remote
batch and distributed data processing spool-
ing. If SPOOLICAM=C?, the console operator is
asked at load time for the value I CAN name
to load. If you specify SPOOL I CAM, you must
specify SPQOLING=REMOTE or SPOOLING=DDP and a
value for COMH during SUPGEN. You must also
configure an ICAH element through the COMMT
phase. If omitted, jobs creating output for
remote batch or distributed data processing
encounter errors at the end of a job and
require ICAM to be manually loaded to process
the output.
Mumber of full words (4 bytes) of main
storage reserved for resident spool -file bit
map. Refer to 4.3.1. and Table 4-6 for
information about how this value is used
and hoy it can be optimized.
Specifies the maximum number of I/O records
(in thousands) to be processed before the
system halts the job and sends a warning
message to the operator. If % is specified,
no limit is put on the number of records that
can be entered into the spool file.
Allows, spooling of records up to 224 bytes.
Overrides the IOGEM PRIMTPOS parameter and
permits the use of printers that accept a
print line greater than the PRIMTPOS maximum
of 16® characters.
Output file processing criterion and its
value for the spooler when operating in burst
mode. Output files are processed according to
the criterion and its value specified; pro-
cess stops when the criterion is satisfied.
If operating in burst mode, and no criterion
is specified, output is governed under the
job priority basis.
If you are uncertain which criterion to im-
plement, you can change the specification
from the console later. See the procedures
in the Operations Guide, 7004 5208.
continued
4-28
7004 5505-000
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont.)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
Subpararoeters:
ACCTNO, account -number
One to four alphanumeric characters
indicating that the account number is the
criterion used to determine file process-
ing. Subfiles created by jobs whose
account number is the same as the criter-
ion specified on the JOB control state-
ment are processed without operator
intervention.
CARTMAME, cartridge- name
One to eight alphanumeric characters
indicating that the cartridge name is the
criterion to determine file processing.
All subfiles whose cartridge name is the
same as the criterion specified on the
LCB job control statement are processed
without operator intervention.
DE V I CE , dev i ce - type - code
Indicates to output writer that the de-
vice type number such as 8776 or 8789 is
the criterion to determine file process-
ing. All subfiles available for proces-
sing Mhose device type is the same as the
criterion configured are processed with-
out operator intervention.
F!LE # filename
One to eight alphanumeric characters
indicating that the file name is the cri-
terion used to determine file processing.
All subfiles available for processing
whose file name is the sane as the cri-
terion configured are processed without
operator intervention.
FORM, form -name
One to eight alphanumeric characters in-
dicating that the form name is the cri-
terion used to determine file processing.
All subfiles whose form name is the same
as the criterion configured (on VFB or
SPL job control statements) are process-
ed without operator intervention.
continued
7004 5505-000
4-29
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont.)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
SPOOLNOINPUT=
m
SPOOLOWBUFR=
rii
4
8
16
[32
SPOOLPRT=
ALL*
ACT
LOG
i
_N0 .
J
JOB,jobname
One to eight alphanumeric characters
indicating that job name is the criterion
used to determine file processing. AH
subfiles whose job name is the same as
the criterion specified on the job
control statement are processed without
operator intervention.
Specifies whether your supervisor suppresses
input spooling. Use when you specify
SPOOL 1NG-REM0TE or SPOOLING=DDP and you want
to suppress the INPUT SPOOLING capability
throughout your SPOOLING system. You cannot
run the input reader when you specify YES.
Number of 256-byte blocks of main storage
allocated to the spool buffers for the print
and punch output writer. Specifying larger
values for this keyword parameter increases
system performance by reducing the number of
disk accesses to the spool file. Specify only
the parameters shown in the format.
Specifies log printing criteria for a termi-
nated job. Includes log types for printing
(L and A) and whether to print log records.
Must specify JOBACCT=YES to have A records.
ALL
Specifies that both job log and account-
ing records are printed when a job ends.
ACT
Specifies that job accounting records are
printed when a job terminates.
LOG
Specifies that only log records are
printed when the job terminates.
NO
Specifies that job log and accounting
records are not printed.
continued
4-30
7004 5505-000
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont.)
Phase
Parameter in Coded Format
Description
SPO0LRECV=
CLOSED
LOG
SPOOLTEST= pi]
NO
W
SPOOLTPBUFR=
[31
2
4
8
16
.
32
.
SPOOLUPDATE= J
ps]
•
NO j
L
J
SPOOLVSN=
Level of recovery for spool file when it is
necessary to reinitialize the supervisor.
NONE
Spool file not recovered (cold start).
CLOSED
Only completed spooled subfiles recovered
(warm start).
LOG
Only log files recovered (warm start).
Specifies whether your supervisor suppresses
console messages requesting an operator
decision to print a test line for form
change. If omitted, a test line message is
displayed at the console.
Specifies the size of the buffer used to
generate the tape block in 256-byte
increments.
Tape processing efficiency increases in
speed and tape utilization when larger block
sizes are used.
Spool subdirectory entry update. If SPOOLUP-
DATE=NOj the entry is updated only when a
file is closed. If cancelled, all program
output generated prior to the cancellation is
lost. If a parameter is omitted, an entry is
updated whenever a logical track is crossed.
Volume serial number of the primary disk that
the supervisor uses as a pool file,
continued
7004 5505-000
4-31
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont)
Phase
Parameter In Coded Format
Description
SUPGEN (cont)
SPOOLVSNn=
SYSRES
vsn
SYSLOG=
YES
ACT[,10GH,WS]
Mul 1 1" volume spooling is supported. You can
allocate up to eight disk volumes for spool-
ing. SPOOL VSNn identifies the nth sequential
volume of a spool file, where n is a decimal
number from 2 to 8. You can Identify each
spool volume through multiple calls of the
keyword. For example, SP00LVSN2=vsn, SPOOL -
VSN3, etc., or denote only the last sequen-
tial volume. If you identify only the Last
volume, all other volumes default to *, let-
ting you specify device addresses of disk
units containing spooling volumes at IPL.
Accumulation of job and workstation log
records (A, L, and W/R) in spool file for
future transfer to user disk or tape file.
If not configured at SYSGEN, the operator
can request from the console later. See the
Spooling and Job Accounting Operating Guide,
7084 4581.
Note that when the first accumulated log
entry is made or when MERGE=NO is selected
on the //OPTION job control statement, the
entire log is saved.
Subparameters ACT, LOG, and WS may be
specified in any order.
You must specify JOBACCT-YES to have A
records.
RESOURCE MANAGEMENT PARAMETERS
RESMGT=
[NO 1
YES
Enables the configuration of resource
management* capabilities.
NO
The system ignores the next seven
parameters (INTMEM through SYMBMEM).
YES
The next seven parameters (INTMEM through
SYMBMEM) come up, and the system
implements the defaults for each unless
other values are specified.
This is a separately priced product that you must purchase to configure in your system.
continued
4-32
7004 5505-000
SUPGEN Keyword Parameters
Table 4-1. SUPGEN Keyword Parameters (cont.)
Phase
Parameter in Coded Format
Description
SUPGEN (cont)
INTMEM= riLMT
.MT 1
•100 J
JOBMEM=
MAXJOBS=
0-180
m
END
MAXRUNSYMBS^
MAXSWSJOBS=
{e-10}
MAXWSJOBS
W
SYMBMEM=
§LMI
5-100
Specifies the percentage of available main
storage allocated for interactive services
use. NLMT indicates no limit to amount of
main storage available for interactive
services use. Valid only if RESMGT=YES.
Specifies the percentage of available main
storage allocated for jobs use. NLMT
indicates no limit to amount of main storage
available for jobs use. Valid only if
RESMGT=YES.
Specifies the maximum number of jobs that
can be run concurrently in the system. The
maximum value is 48. Valid only if
RESMGT=YES.
Default value is as shown unless a different
value is specified for number of job slots
(JOBSLOTS=). If value is different, default
value for this parameter is the number of
job slots previously specified.
Specifies the maximum number of run
symbionts that can execute concurrently in
the system. Valid only if RESMGT-YES.
Specifies the maximum number of jobs
initiated from a single workstation that can
run concurrently in the system, where n is
the value assigned to MAXWSJOBS. Valid only
if RESMGT=YES.
Specifies the maximum number of jobs
initiated from workstations that can run
concurrently in the system. Valid only if
RESMGT=YES. The default value of 2 is equal
to one half the number that was assigned to
MAXJOBS. Valid only if RESMGT=YES.
Specifies the percentage of available main
storage allocated for symbiont use. NLMT
indicates no limit to the amount of main
storage available for symbiont use. Valid
only if RESMGT=YES.
7004 5505-000
4-33
I/OGEN Keyword Parameters
Table 4-2. 1/OGEN Keyword Parameters
Phase
I/OGEN
PRINTER
Parameter in Coded Format
[I/OMOD=supvrnam]
TYPE=
SOMA "
0770
«
07701
0776
07761
[CHAM=n]
Description
Supervisor name for which I/O configuration
was previously created and saved on $Y$SRC
on SYSRES. Hay request established I/O
configuration by specifying I/OMOD keyword
parameter as the only parameter immediately
following the statement with I/OGEM parameter
in label field. Mo other I/OGEN parameters
are then required! if specified, it is
ignored and diagnostic message displayed.
Identifies printer or group of printer types
defined.
SOMA
Specifies any of these types of printers;
0776, 0789, and 0798 printers.
0770
Used to identify the 0770 (type 0770-84/05)
printer.
07701
Used to identify the 8770 II (type 0770-
06/07) and 9246- 25B printers.
0776
Used to identify the 0776 printer.
07761
Used to identify the 9246- 14B printer.
Hexadecimal number identifying the physical
I/O channels with access to a printer or a
group of printers described. The default
specification is device dependent and deter-
mined as a function of the TYPE keyword.
Allowable values are as follows (the default
value for each device type is shaded):
!S,E for SOMA
S-3,6,7 for 0770,0776 model 8
1 for 07701,07761 model 8
1-3-6 for %77% s 0776, 07701, 07761
models 10-20
continued
4-34
7004 5505-000
I/OGEN Keyword Parameters
Table 4-2. i/OGEN Keyword Parameters (cont)
Phase
I/OGEN (cont)
PRINTER
Parameter in Coded Format
[ADDR=nn]
[DVCNO=lun]
CLASS™
CHARSET=
810*
48
63
94
108
EXT.
Description
2-digit hexadecimal number identifying the
hardware address and number of printer types.
If more than one address is specified, it
must be separated by commas or hyphenated to
indicate consecutive addresses.
The device dependent defaults for nn are:
38
for SDMA
84
for 0770 (model
8)
98
for 8770 (model
10-20)
90
for 87781
B0
for 87761
05
for 8776 (model
8)
B8
for §776 (model
10-28)
Changes the standard logical unit numbers
(lun) for specific printers. See Table 4-8
for logical unit numbers. If you specify
this parameter in a roultiprinter environment,
the output is to this printer first. If you
don't specify this parameter, output is sent
to any available printer.
Classifies a printer so that special logical
unit numbers can be used to direct output
for printers of the same subtype. See Table
4-8 for logical unit numbers.
For 0776 printers, the CLASS parameter
should specify high, medium, or low speed if
a unique logical unit number is required.
Number of printable characters in a printer
subsystem font set. Standard or extended
apply to all types of printers. Only the
0778 and 0776 printers can have 48, 63, 94,
or 188 printable characters.
continued
7004 5505-000
4-35
i/OGEN Keyword Parameters
Table 4-2. i/OGEN Keyword Parameters (cont.)
Phase
I/OGEN (cont)
PRINTER
Parameter in Coded Format
PRINTPOS=
(for SOMA,
8778)
136 (for 07781,
8776,87761)
160 (for 0778)
LCB=
VFB^
(for SOMA)
48-SCI
63-STD
OWNLC1-2
OWNLC3-9 (for SDMA)
OWNVF1
[OWNVF2-9 (for SDMA)
ATTNRE^ frlSl
REMOTE= m 1
[ADDR=NO]
Description
Number- of print positions pertaining to the
printer subsystem described. Though 132 is
the default for the 8778, 168 is also an
allowable entry for that printer.
Printer load code buffer used as default
buffer for the printer defined. 0WNLC1
through OWNLC9 reference load code buffers
other than 48-BUS, 48-SCI, 63-STD, or
those that report a character mismatch. See
3.3.4 for the procedure that defines
alternate printer characteristics.
Printer vertical format buffer as default
buffer for the printer subsystem defined.
0WNVF1 through OWNVF9 reference user -genera-
ted vertical format buffers. See 3.3.4 for
the procedure to generate your own vertical
format buffers.
Specifies whether your system supports
automatic retry of recoverable errors when
attention interrupts are received on a
printer that has an unanswered PIOCS error
message. If omitted, the retry feature is
active and the operator can initiate recovery
at the printer by placing it in online mode.
Specifies that your system includes SDMA
printers that are in remote locations from
your System 80 host.
Defines an indirect printer for your system.
If you configure a printer I ess system, you
must define at least one indirect printer and
also configure spooling. Print files genera-
ted on a printer I ess system are spooled for
subsequent printing on another system that
has a physical printer. You may specify an
indirect printer for each physical printer
type that exists on the system that prints
the spooled data.
continued
4-36
7004 5505-000
1/OGEN Keyword Parameters
Table 4-2. 1/OGEN Keyword Parameters (cont.)
Phase
i/OGEN (cont)
PRINTER
[READER]
Parameter in Coded Format
VIRTUAL^
mxmrnbe
slots
1-258
TYPE=
8716
[CHAN^n]
ADDR-
32 (for 8719)
06 (for 0716 model 8)
A8 (for 8716 models
10-20)
[DVCNO=lun]
r
i
FEED=
m.
51
•
66
98
96
Description
Number of virtual printers if spooling is
configured. To calculate the optimum number,
multiply the number of jobs that can run
concurrently by the average number of printer
files used for each job. Each virtual printer
uses 32 bytes of main storage.
Type of reader or group of readers defined.
Hexadecimal number identifying the physical
I/O channels with access to a reader or a
group of readers defined. The default speci-
fication is device dependent and determined
as a function of the TYPE keyword.
Valid entries for n are (defaults are
shaded) :
1,E (for 0719)
0-3,6,7 (for 8716 model 8)
1-1-6 (for 8716 models 10-28)
2-digit hexadecimal number that identifies
the hardware address and number of a reader
or group of readers defined. If more than one
address is specified, it must be separated by
commas or hyphenated to indicate consecutive
addresses.
Changes the logical unit numbers (lun) for
specific readers. See Table 4-8 for logical
unit numbers.
Card size read by reader if a short card
feature is installed.
continued
7004 5505-000
437
1/OGEN Keyword Parameters
Table 4-2. 1/OGEN Keyword Parameters (cont)
Phase
I/OGEN (cont)
READER
Parameter in Coded Format
ATTNREs
{11}
ALTSTACK=
SJ ]
DUALTRAN= Jll 1
|yes|
READER
[PUNCH]
HODE=
(for 0719,0716)
ASCII (for 8716
COMPCD (for 0716)
E0F= {S s }
VALIDITY=
m
VIRTUAL^
1 x number
of job
slots
1-99
[TYPE=8688]
CHAN=
ft
Description
Specifies whether your system supports
automatic retry of recoverable errors when
attention interrupts are received on a reader
that has an unanswered physical IOCS error
message. If omitted, the retry feature is
active and the operator can initiate recovery
retry by placing the reader in online mode.
Specifies whether your card reader has the
al ternate - stacker -fill capabi I i ty .
Specifies whether your card reader has the
dual translate capability.
Specifies the mode of card interpretation of
the reader.
Specifies whether your card reader can sense
an end-of-file condition even if the /* or
// FIN card is missing from the job control
streams. This applies only to a 1-job
environment on the 0716 card reader.
Specifies whether your card reader has the
validity check capability. This feature is
available only for the 8719 card reader.
Number of virtual readers if spooling is
configured. To calculate the optimum number,
multiply the number of jobs that can run
concurrently by the average number of reader
files used for each job. Each virtual reader
uses 32 bytes of main storage.
Type of punch defined.
Hexadecimal number identifying the physical
I/O channels with access to a punch or punch-
es defined.
continued
4-38
7004 5505-000
I/OGEN Keyword Parameters
Table 4-2. I/OGEN Keyword Parameters (cont.)
Phase
I/OGEN (cont)
[PUNCH]
PUNCH
DISC
Parameter in Coded Format
[ADDR=33]
[DVCNO=lun]
ATTNRE
" {is}
READ= fm 1
VIRTUAL^
llxliidfflei
of job
$ lots
1-99
TYPE=
(for Model 8)
8416
8417
8419
8438
8433 (for Models
18-28)
8470
8494
9728
Description
Identifies hardware address of the punch.
Changes the logical unit number (lun) for
the punch. See Table 4-8 for logical unit
numbers.
Specifies whether your system supports
automatic retry of recoverable errors when
attention interrupts are received on a punch
that has an unanswered physical IOCS error
message. If omitted* the retry feature is
active and the operator can initiate recovery
retry by placing the punch in online mode.
Specifies whether the punch has card reader
capabi I i ties.
Number of virtual punches if spooling is
configured. To calculate the optimum number,
multiply the number of jobs that can run
concurrently by the average number of
punch files uses for each job. Each virtual
punch uses 32 bytes.
Type of disk or group of disks defined.
Notes:
1. All 8416 disks are configured as 8418
low-density disks, and some messages
say 8418 instead of 8416. The logical
unit numbers for the 8418 low-density
disks should be used.
2. The 8488 device should be configured as
four 8478 disks.
3. If your system has both fixed and
removable disks,, the fixed disks must be
specified first.
continued
7004 55054300
439
I/OGEN Keyword Parameters
Table 4-2. i/OGEN Keyword Parameters (cont)
Phase
I/OGEN (cont)
DISC
Parameter in Coded Format
[CHAN=n]
[ADDR=nn]
[DVCNO=lun]
CACHE= [NO
■1
NOMI
Description
Physical I/O channels with access to disk.
The default specification is device
dependent and is determined as a function
of the TYPE word.
Allowable values for n are (shading indicates
defaults):
1, 2, I, 6, 7 for model 8
1 through 6 for models 10-28
2-digit hexadecimal number that identifies
the hardware address and number of disks
defined. If more than one address is
specified, it must be separated by commas or
hyphenated to indicate consecutive addresses.
The default addresses are:
88, 81 (for 8438/33)
90 (for 8478/8494/M9728)
A0, A1 (for 8416/18)
B8 (for 8417/19)
Changes the logical unit numbers (lun) for
specific disks* See Table 4-8 for logical
unit numbers.
Indicates if a disk device is activated to
the disk cache facility (DCF). See the Opera-
tions Guide, 7084 5208 for details on the
DCF.
You can override this specification (except
CACHE= NO) on a file basis through the CACHE
parameter on the // DD statement. See the Job
Control Programming Guide, 7884 4623 # and
Consolidated Data Management Programming
Guide, UP-9978, for CACHE DD parameter
details.
NO
The disk device is not activated to the
DCF. Specify NO if the device is shared by
two processors.
continued
440
7004 5505-000
1/06EN Keyword Parameters
Table 4-2. i/OGEN Keyword Parameters (cont.)
Phase
Parameter in Coded Format
Description
I/OGEN (cont)
DISC
YES
The disk device is activated to the DCF
for all files.
NOMI
The disk device is activated to the DCF
for all files except MIRAM data files.
[C0CHAN=n]
Specifies that the disk defined can be
accessed by multiple channels to provide for
simultaneous operation. Valid only for the
8438, 8433, 8478, 8494, and M9728 disk
devices. See 4.3.9 for additional
information.
Allowable values for n ares
1,2,3,6,7 for model 8
1 through 6 for models 18-28
[COADDR=nn]
Specifies that the disk unit can have
multiple addresses to provide simultaneous
operation. Each address specified must be a
2-digit hexadecimal number. Multiple
addresses must be separated by a comma or
hyphenated to indicate consecutive addresses.
Valid only for selector channel devices.
The default addresses are?
88, 81 (for 8438/33)
90 (for 8470/8494/M9728)
A0, A1 (for 8416/18)
B8 (for 8417/19)
READ0NLY=rI6 1
JYES} ^
Indicates if the disk is write-protected by
the system. Write-protection prevents any
write operations to the specified disk.
NO
The disk is not write-protected by the
system.
YES
The disk is write-protected by the system.
continued
7004 5505-000
441
S/OGEN Keyword Parameters
Table 4-2. 1/OGEN Keyword Parameters (cont)
Phase
1/OGEN (cont)
DISC
DISKETTE
Parameter in Coded Format
DOWN=
w
SELACC= Jll
[2-64 (for 8438/33 )j
TYPE= JS4281
J8422J
CHAN
[ADDR={28 r 21}]
Description
Indicates if the device is to be generated
in the UP or DOWN state. The DOWN state
prevents any access to the device by the
system.
NO
The device is generated in the UP state
and is accessible by the system.
YES
The device is generated in the DOWN state.
AH accesses are prevented.
Specifies the maximum number of physical
blocks on a disk that can be written in one
disk access when using the system access CCB
mode (BCW command). You can specify from 2 to
64„ depending ©n the multiblock I/O require-
ments of your applications. For each number
of blocks specified for writing, approxi-
mately three times as many reads are
provided. This parameter may be used to
optimize I/O for IRAM file applications or
SPOOLBUFR specifications greater than 2.
Note: For the 8430/33 disks, the default
value for the SELACC parameter is
changed to 33 because of higher full
track I/O use. If you are using a
smaller size f it is recommended that
you increase it to at least 33.
Type of diskette or group of diskettes
Hexadecimal number identifying the physical
I/O channel with access to a diskette.
2-digit hexadecimal number identifying the
hardware address and the number of diskette
devices defined. If more than one address is
specified, it must be separated by commas
or hyphenated to indicate consecutive
addresses .
continued
442
7004 5505-000
i/OGEN Keyword Parameters
Table 4-2. I/OGEN Keyword Parameters (cont.)
Phase
I/OGEN (cont)
DISKETTE
[TAPE]
Parameter in Coded Format
[DVCNO=lun]
AUT0L0AD= (11 '
YES
[ADDR=nn]
[CHAN^n]
TYPE=
111
11
12
14
16
28
22
24
26
28
32
L
J
[DVCNO=lun]
Description
Changes the Logical unit numbers (lun) for
specific diskettes. See Table 4-8 for
logical unit numbers.
Operating system can automatically load up to
28 diskettes.
Type of tape or group of tapes defined.
Values represent UN I SERVO 18/11/12/14/16/20/
22/24/26/28 devices and BT3288 tapes.
2-digit hexadecimal number identifying the
hardware address and number of tapes defined.
If more than one address is specified, it
must be separated by commas or hyphenated to
indicate consecutive addresses. The device
type dependent default values arei
(for 10/11/22/24)
A0,A1 (for 12/14/16/20/26/28/32)
Hexadecimal number identifying the physical
1/0 channel with access to tape. The
allowable values are as follows. Shading
indicates the device dependent default.
C # E (for 18/11/22/24)
:l-3,6,7 (for 12/14/16/28/26/28/32; model 8)
1,2-6 (for 12/14/16/28/26/28/32;
models 10-20)
Changes the logical unit numbers (lun) for
specific tapes. See Table 4-8 for logical
unit numbers.
continued
7004 5505-000
443
I/OGEN Keyword Parameters
Table 4-2. 1/OGEN Keyword Parameters (cont)
Phase
I/OGEN (cont)
[TAPE]
Parameter in Coded Format
[MODE=nn]
TRANSLATE=
DENSITY=
YES
NRZI
PHASE
GCR
[C0CHAN=n]
Description
Indicates the recording" mode of the tape unit
defined and whether it is a 7- track, 9- track,
or streaming tape device. See Tables 4-9 and
4-18 for the 9- and 7- track recording mode
settings that are supported. The device type
dependent default values are:
11 (for 18/12/14/16/28/22/24/26/28/32)
D3 (for 26/28/32)
W (for 11)
Indicates that the extended binary coded
decimal interchange code to binary coded
decimal (EBCDIC to BCD) translate feature
is described.
Indicates the recording modes of the tape
unit described. See Table 4-9 for the modes
that each tape device supports.
DUAL
Indicates that multiple recording modes
are allowed. The allowable combinations
are device dependent:
Deyjce Modes
10/12/14/ PHASE, NRZI
16/22/24
26/28/32 PHASE, GCR
NRZI
Identifies the non- return- to -zero (NRZI)
mode.
PHASE
Identifies the phase-encoded mode. (This
is the default value for U11/20.)
GCR
Identifies the group-coded recording mode.
Specifies that the tape unit defined
can be accessed by multiple channels to
provide for simultaneous operation. Valid
for 12, 14, 16, 20, 24. 26, 28, and 32.
Allowable entries are:
1,2,3,6,7 for model 8
1 through 6 for models 18-20
continued
444
7004 5505-000
I/OGEN Keyword Parameters
Table 4-2. I/OGEN Keyword Parameters (cont)
Phase
I/OGEN (cont)
[TAPE]
[WORKSTATION]
Parameter in Coded Format
[COADDR=nn]
DOWM=
YES
TYPE=
r 356«f
3561
1122
3612
CHAM=
fl
[ADDR=nn]
Description
Specifies that the tape unit can have
multiple addresses to provide for simul-
taneous operation. Each address specified
must be a 2-digit hexadecimal number.
Multiple addresses must be separated by a
comma or hyphenated to indicate consecutive
addresses. Valid only for selector channel
devices. The device type dependent defaults
are:
(for 18/11/22/24)
A8,A1 (for 12/14/16/28/26/28/32)
Indicates if the device is to be generated
in the UP or DOWN state. The DOWN state
prevents any access to the device by the
system.
NO
The device is generated in the UP state
and is accessible by the system.
YES
The device is generated in the DOWN state.
All accesses are prevented.
You must specify workstations if the system
supports interactivity from local
workstations.
Type of local workstation or group of local
workstations defined.
Hexadecimal number identifying the physical
I/O channel with access to a workstation. The
default specification is device dependent and
determined as a function of the TYPE keyword.
2-digit hexadecimal number identifying the
address and number of workstations defined.
The device type dependent defaults are:
12,13 (for 3560)
51,52 (for 3561, 1122, and 3612)
If more than one address is specified, it
must be separated by commas or hyphenated to
indicate consecutive addresses. You can spec-
ify from one to eight workstations for each
controller. Valid addresses must end with
digits 1-8.
continued
7004 5505-000
445
1/OGEN Keyword Parameters
Table 4-2. i/OGEN Keyword Parameters (cont.)
Phase
1/OGEN (cont)
[WORKSTATION]
Parameter in Coded Format
[DVCNQ=lun]
DESPACE-
YES
SCRENMEM=
(for 3561,1122
and 3612)
1 (for 3568)
jYES 1
}nn (ADDR)J
ALTCON= [YES
nn (ADDR)!
KATAKANA=
K
Description
Changes the logical unit numbers (lun) for
specific workstations. See Table 4-8 for
logical unit numbers.
Specifies whether the space key protects or
destroys the character the cursor is
positioned on.
YES
Character is replaced with a blank when
the space key is pressed.
NO
Character is not changed when the space
key is pressed.
Specifies whether the device has a single or
dual screen capability.
Specify 1 for UTS 20D.
Specify 2 for SVT 1122 and UTS 40D.
ALTCON defines a specific local workstation
as an alternate console. You can generate
only one alternate console per supervisor.
YES
The first address specified for a
workstation or a group of workstations
is designated as the alternate console.
The workstation specified by nn is the
alternate console. This address must fall
within the range of addresses specified
on the workstation parameter.
Workstation recognizes input in Japanese
Katakana language.
continued
446
7004 5505-000
I/OGEN Keyword Parameters
Table 4-2. i/OGEN Keyword Parameters (cont)
Phase
I/OGEN (cont)
[AUXPRINTER]
REMWORK
STATION
Parameter in Coded Format
TYPE-
0797
0791
0789
8425
8774
VFB=
OWNVF
'}
LOOP=
[AUX={1-8>]
AMOUNT= 1-999
Description
You can specify only one auxiliary printer
for each local workstation you define. You
must repeat the AUXPRINTER parameters for
each auxiliary printer you want configured.
If you define a range of local workstations,
the auxiliary printers you specify are
defined for each workstation in that range.
Identifies the type of auxiliary printer or
group of auxiliary printers defined.
Printer vertical format buffer is default
buffer for printer subsystem defined. 0WNVF1
references user -generated vertical format
buffers. See 3.3.4 for the procedure to
generate your own vertical format buffers.
Specifies whether a 3 -channel or 4 -channel
forms control loop is used to control
vertical form spacing.
Specifies single digit device identification
number (channel number) of the auxiliary
printer defined, Each printer is identified
by a 2-digit device identification number,
for example, 1 and 2, 3 and 4, and so on.
The actual channel number of the printer is
usually the odd number of the pair. There-
fore, you specify device identification
numbers of 1, 3, 5, and 7 to identify the
printer.
Number of communi cat ions terminals that
support interactivity. Value is the maximum
number of interactive sessions the system
recognizes from remote terminals or remote
workstations at one time. If communications
network supports interactivity, you must
specify how many terminals function as
workstations. The value must at least equal
the number of terminals recognized as
workstations, plus 2.
continued
7004 5505-000
447
1/OGEN Keyword Parameters
Table 4-2. 1/OGEN Keyword Parameters (cont.)
Phase
Parameter in Coded Format
Description
I/OGEN (cont)
REMWORK
STATION
SCRENMEM= (1
PI
[REMPRINTER
[KATACON]
END
KATAKANA= IfS 1
|yes|
AMOUNT= 1-99]
Specifies single or dual screen support for
UTS 28, UTS 38, UTS 40, U288, U480, SVT 1120
1123, 1124 workstations.
1
Indicates single screen support.
Indicates dual screen support. This
allows full screen system messages on
screen 1 when the workstation is not
allocated to a job. Screen 2 is used for
auxiliary output only. Applicable for
UTS 28, UTS 30, UTS 48, SVT 1120, 1123,
1124, and U488.
Workstation recognizes input in Japanese
Katakana language.
Specifies total number of auxiliary printers
connected to remote terminals or remote
workstations.
Console workstation recognizes input in
Japanese Katakana language in console mode.
AA8
7004 5505-000
COMMCT Keyword Parameters
Table 4-3. COMMCT Keyword Parameters
Phase
Parameter in Coded Format
Description
COMMCT
-
[network definition
Network definition macroinstructions. See the
macro instruct ion]
1CAM derations Guide, 7004 4557. Each net-
CCAMOD=name
work definition roust begin with a CCA macro-
instruction and end with an ENDCCA macro -
instruction. A physical I/O only CCA must be
the Last CCA in a multiple CCA generation.
CCAMOD-name
4-character name of a previously saved
network definition in $S$SRC on SYSRES,
used in place of the network definition
macroinstructions. Each CCAMOD parameter
must be followed by ENDCCA parameter.
MCP
Delimiter signifies the end of a network
definition and the start of MCP parameters.
MCPNAME= [W
Indexed name of ICAM symbiont, where n is a
|cn
decimal number between 1 and 9. A maximum of
[Mnj
18 ICAM symbionts are maintained on SYSRES.
No duplicate names are allowed.
[MCPVOL=vsn]
MCPVOL places the ICAM symbiont in the
$Y$LOD file on a disk other than the system
resident volume (SYSRES). Specify the volume
serial number of the disk where the ICAM
symbiont is to reside. If you do not specify
this parameter , the symbiont is stored on
your SYSRES volume.
CACH=
Identifies each single line communications
adapter (SICA) accessed or supported by the
Note:
ICAM symbiont. Since ICAM supports local
The CACH statement has four
workstations that do not require CACH
formats. See 4.1.3 for details
information, the CACH parameter is not
on using COMMCT parameter
required if COMM=YES at SUPGEN. Also
formats.
identifies the channel to which a DCP is
connected.
continued
7004 5505-000
449
COMMCT Keyword Parameters
Table 4-3. COMMCT Keyword Parameters (cont.)
Phase
COMMCT (cont)
Parameter in Coded Format
Format 1:
CACH=<nn, network -name,
line-number,)CHAN=nn
Format 2s
CACH=(nn # line-speed)
{half}
, f AUTODIAL] ,nn,EON,p
JAUTODIAL]
[manual j
[,SWITCHED][ f SYNC]
,CHAN=
2
13
15j
■ £3}
[,LDTE-ldte-name]
Description
Format 1 Positional Subparameters:
2-digit decimal number identifying an SLCA
default is 2. You can specify up to 14
SLCAs for each input/output processor
(1 to 14). The default is 13.
network -name
A 4-character name in the label of CCA
macro.
line -number
2-digit decimal number identifying the line
that uses this SLCA by order in the network
definition. The line number of the first
line in the network definition is 01 , the
second must be 02, etc.
CHAM
For model 8 with one input/output
processor, the only value permitted is
CHAN=13, the default. For models 8-20
with two input/output processors, CHAN=13
and CHAN=15 are permitted. The default is
CHAN=13.
Format 2 Positional Subparameters;
2-digit decimal number identifying an
SLCA address. You can specify up to 14
SLCAs for each input/output processor
(1 to 14).
line -speed
Decimal number identifying the maximum
baud rate. (See Table 4-11 for line speed
values.)
continued
4-50
7004 5505-000
COMMCI Keyword Parameters
Table 4-3. COMMCI Keyword Parameters (cont.)
Phase
COMMCT Ccont)
Parameter in Coded Format
Description
FULL
Specifies 2 -way simultaneous transmission
(full -duplex operation). If omitted, the
2-nay alternate transmission (half-duplex
operation) is assumed by default.
Notes:
3.
If an I CAM remote device handler uses
2- way- alternate protocol (half-duplex),
the line must be defined as 2-way-
alternate also. All I CAM remote device
handlers utilize 2-way-alternate
protocol except NTR, UDLC, ABM f and
level 2 X.25 public data networks.
If 2 -way simultaneous protocol is used,
the same protocol must be specified in
the I CAM generation (LINE and CACH)*
2-way simultaneous modems and lines can
be used with 2-way alternate protocol,
if required.
AUTODIAL
Specifies that automatic dialing is
performed in the subchannel. Also
indicates that the data transfer sub-
channel being defined as a dial adapter
subchannel associated with it t© which
dialing operations are directed. If
omitted, manual dialing is assumed by
default.
2-digit decimal number identifying the
SLCA address where the dialer is located.
You must specify a CACH parameter using
format 3 with this 2-digit number as the
first subparameter.
EON
Specifies that automatic dialing requires
an end- of -number code. Not used with the
Bell System 881 ACU. EON is required with
the European V25 automatic calling
equipment.
continued
7004 5505-000
4-51
COMMCT Keyword Parameters
Table 4-3. COMMCT Keyword Parameters (cont)
Phase
COMMCT (cont)
Parameter in Coded Format
Description
Single digit decimal number (8, 1, or 2)
that identifies which of the three ports
on the SLCA is used by the automatic
calling unit.
Note:
If no value is specified, 1 is the
default.
SWITCHED
Specifies a switched communications line.
If omitted,, only dedicated line services.
Note: SLCA switched line does not
support autodial ing.
SYNC
Synchronous operations. If omitted,
asynchronous operations is assumed.
I LA
Specifies that the Unisys intelligent
line adapter is used for bit -on* en ted
procedures .
CHAN
Specifies the 2-digit channel number.
For models with one input/output processor ,
the only value permitted is CHAN-13, the
default. For models with two input/output
processors* CHAN=13 and CHAN=15 are
permitted. The default is CHAN=15.
Note: For 2 -way simultaneous lines, specify
the even -numbered SLCA; the odd-
numbered SLCA is automatically
assigned. If you specify combinations
of these lines, be sure that
automatic assignments don't duplicate
SLCAs.
continued
4-52
7004 5505-000
COMMCT Keyword Parameters
Table 4-3. COMMCT Keyword Parameters (cont.)
Phase
COMMCT (cont)
Parameter in Coded Format
Format 3:
CACH=(nn f DIALER[,EON])
,CHAN-
" 2
13
15
L
J
Description
LDTE = Idte-name
Specifies the LDTE (local data terminating
equipment) to which this SLCA belongs.
The Idte name must match the LDTE
specified in the CCA. If this operand is
specified, both SWITCHED and X21 roust be
specified. The LDTE keyword parameter on
the CACH macro instruct ion is only supported
for use with UTS 28X terminals. The number
of CACH macro instruct ions using the LDTE
keyword must match the number of lines
specified by the LDTE macroinstruction.
Format 3 Positional Subparameters:
2-digit decimal number identifying an
SLCA address. You can specify up to 14
SLCAs for each input/output processor
(1 to 14).
DIALER
Specifies that an autodial adapter
resides in the specified SLCA address.
EON
Specifies that automatic dialing requires
an end-of -number code. Required if DIALER
subparameter is specified. Not used with
the Bell System 801 ACU. EON is required
with the European V25 automatic calling
equipment.
CHAM
Specifies the 2-digit channel number.
For models with one input/output processor,
the only value permitted is CHAN=13, the
default. For models with two input/output
processors, CHAN=13 and CHAN=15 are
permitted. The default is CHAN=13.
continued
7004 5505-000
4-53
COMMCT Keyword Parameters
Table 4-3. COMMCT Keyword Parameters (cont)
Phase
Parameter in Coded Format
Description
COMMCT (cont)
Format 4:
CACH=(nn„DCPCHNL)[ f CHAN=n]
[BPOOLEXP=NO]
[FASTLOAD=NO]
END
Format 4 Positional Subparameters:
Note: You roust use this format for
identifying a channel -connected DCP.
nn
2-digit decimal number identifying a
selector subchannel address. This
number must match the value of the ID
keyword on the DCPCHNL macro, if specified.
DCPCHNL
Specifies a DCP channel connection.
CHAN=n
Specifies a 1 -digit channel address. For
model 8 f valid entries are 1-3, 6 or 7.
For models 10-20, values 1-6 are allowed.
This entry must match the value of the
CNID keyword on the DCPCHNL
macroinstraetion* if specified.
Specifies that the dynamic buffer pool
services expansion routine (BPSX) is not
included in the ICAM generation. If you omit
this parameter j the BPSX routine is
automatically included in the generation.
BPSX is not included for a CPI-only ICAM.
If you do not specify this parameter your
ICAM symbiont supports the improved overlay
loading facility. Specifying FASTLOAD=NO
forces ICAM to perform a directory search
each time it loads an overlay instead of
only the first time it loads that overlay.
4-54
7004 5505-000
NTRGEN Keyword Parameters
Table 4-4. NTRGEN Keyword Parameters
Phase
NTRGEN
NTR
Parameter in Coded Format
NTRMOD=old-NTR-name
'ffl
NTRNAME-ntrname
[NTRVOL=vsn]
BLOCKING ine-buffer-size
Description
Identifies a previously generated NTR network
by name and module type to be linked with
LOCAL keyword sets processed in the current
run. If used, NTRMOD must be the first key-
word specified in the section; all other
parameters except NTRVOL, NTRNAME, and TASK
are ignored and a diagnostic message is
displayed.
Positional Subparameters:
old-NTR-name
Name of previously-generated NTR module;
does not include LOCAL keyword parameter
sets.
Source module.
Object module.
If omitted, assumed NTR module is the ob-
ject module residing in $Y$OBJ on SYSRES.
Name of NTR network generated.
Volume serial number for the SYSRES volume
where the NTR module resides in $Y$LOD.
Defaults to a fixed disk.
Line-buffer size in bytes for transmission
from an 1100 system to an OS/3 system (SOH
through BCC) as specified by the 1108 system.
For 1108 systems, versions 33 and earlier,
the line buffer size equals either 240 bytes
or 246 bytes when through half-word CTMC;
for later versions, the value is configurable
and should not exceed 9999 bytes.
continued
7004 5505-000
4-55
NTRGEN Keyword Parameters
Table 4-4. NTRGEN Keyword Parameters (cont.)
Phase
NTRGEN
NTR (cont)
Parameter in Coded Format
EBLOCKOUT=t ine-buf fer-size]
LINESP=
LINE=Line-name
NET=network-name
SiTE-id
TASK=taskns
"{if
Description
Line-buffer size in bytes for transmission
from an OS/3 system to an 1100 system (SOH
through BCC) as specified by the 1180 system.
For the 1188 system, version 33 and earlier*
the line buffer size equals 121 bytes; for
later versions, the value is configurable and
should not exceed 9999 bytes. If omitted, the
value specified for BLOCK IN size is assumed.
Line speed.
Same line name appearing as the label in the
LINE macroinstruction under CCA definition in
the I CAM generation.
Same network name appearing as the label for
the CCA definition in the I CAM generation.
(Must be the same as the CCA label name.)
Full , 6-character site identification (id)
number configured for the 1180 system. The
OS/3 processor uses the id for sign -on
(translated to truncate ASCII with odd
parity). The operator can override this para-
meter by using the SIGN-ON keyin during exe-
cution of an NTR utility. See the I CAM
Utilities Programming Guide, 7804 4565.
1- to 6-character name and module type
(source or object) of previously generated
NTR remote device handler. You can specify
up to a total of 14 TASK keywords including
LOCAL keyword sets. Only object modules are
permitted for user -own -code tasks.
Positional Subparatneters:
taskname
Taskname is not given in this run but it
is defined by a previous LOCAL keyword
TASKNAME object module name, or user-
own -code task.
continued
4-56
7004 5505-000
NTRGEN Keyword Parameters
Table 4-4. NTRGEN Keyword Parameters (cont)
Phase
NTRGEN
NTR (cont)
Parameter in Coded Format
Description
[PRTSPnn=hh]
[NPRTSPnn^hh]
LOCAL
[TASKNAME=taskname]
[BLKSIZE^image-buffer-size]
COMPRESS=
[DEVICE=n]
FUNCD=
function -code]
LOCAL task was placed in $Y$SRC on the
SYSRES by a previous SGSPARAM job; it must
be assembled by a SG$NTRMK job stream. If
it is omitted, the assumed module is the
object module in $Y$OBJ on the SYSRES.
For printer-type device only, specifies the
hexadecimal byte for space compression when
TRANS=NO. This value corresponds to the 2-
digit decimal function code (nn), in Table
4-12 (space compression table).
For nonpr inter -type devices only, specifies
the hexadecimal byte for space compression
or decompression when TRANS=NO» This value
corresponds to the 2-digit decimal function
code (nn) in Table 4-12.
1- to 6- character name that identifies an
NTR remote device handler generated by LOCAL
kevijord?..
Maximum image buffer size for the unit record
device; should be a multiple of 12 for a card
punch.
Suppresses space compression option for a
reader/input device (TYPE) sending data to an
OS 1108 system . If omitted, space compression
is performed on all data sent to an OS 1180
system by a reader/ input device defined in
the TYPE keyword. Space compression char-
acters are defaulted to X'40 1 (EBCDIC space)
when TRANS=YES, or taken from the NTR space
compression table when TRANS=NO, See
Table 4-12.
Local device numbers for an NTR remote device
handler generated by LOCAL keywords. This
parameter must agree with the OS 1188 system
device number.
2-digit decimal function code establishing
translation requirements for each image sent
to the OS 1108 system. Used with TYPE and
continued
7004 55054)00
457
NTRGEN Keyword Parameters
Table 4-4. NTRGEN Keyword Parameters (cont)
Phase
Parameter in Coded Format
Description
NTRGEN
LOCAL (cont)
[LFD=filename]
TRANS=
"YES/
NO
TYPE^
VFBLEN-
VFBDEN=
VFHOME=
{"}
[VFBFORM=formname]
END
TRANS keyword parameters. Function codes and
respective meanings are listed in Table 4-13
(device function code table).
File name as it appears on the // job
control statement.
Suppresses the NTR translation feature for
the device type defined by the TYPE keyword.
The space compression character is determined
by function code. See Table 4-13. If omitted,
images are sent to or received from the 1180
series system and translated* respectively,
to or from EBCDIC, according to the function
code (FUNCD keyword) parameter.
Device type of an NTR remote device handler
generated by LOCAL keywords.
Note: System-supplied NTR locals use the unit
record system access technique. To
access a diskette instead of a card
reader or a punch, write your oyn NTR
local that uses standard data manage-
ment according to the ICAM Utilities
Programming Guide, 7004 4565.
Number of lines (1 to 192) on printer form.
Number of print lines per inch <6 or 8),
Location (line 1 to 192) of home paper
position; the first line of printer output is
placed on each form (page). Must not exceed
the value in the VFBLEN keyword.
1- to 8-character alphanumeric name associa-
ted with a form. A console message instructs
the operator to load this form on a printer.
If omitted, no name is associated with the
form.
4-58
7004 5505-000
COBGEN Keyword Parameters
Phase
COBGEN
Table 4-5. COBGEN Keyword Parameters
Parameter in Coded Format
AXNON=
AXREF=
{yes}
CALLST= Jil 1
CMCSST= JH 1
COMP=
CPYTXT
DIAG=
DIAGWN
= I N0 1
[YISj
l m -l
{Is}
FIPS=
Y
2
3
4
[5J
MSCOD=
m] '
■
YES[
RENJ
IN=module name/ [filename]
{$Y$SRC j
Description
Specifies whether your compiler includes
nonreferenced entries in its alphanumerical ly
ordered cross-reference listing.
Alphanumerical ly ordered cross-reference
listing.
Subprograms named by the literal option of a
CALL statement linked with the main program.
COBOL communi cat ions control module bound
with a COBOL object program.
Specifies default computational type.
Copied COBOL library text included in source
listing.
Diagnostic listing prepared.
Warning diagnostics included in diagnostic
listing.
Specifies FIPS PUB 21-1 flagging options. See
the 1974 American Standard COBOL Programming
Reference Manual, 7804 4498.
IMS compatible code for COBOL programs exe-
cuted under the control of the IMS action
program. COBOL language elements restricted
by IMS are flagged and deleted.
IMSCOD=YES indicates generation of a shared
code action program. IMSCOD=REN indicates
generation of a reentrant action program.
Specifies a 1- to 8-character name of a
source module in the library and a 1- to 8-
character LFD name identifying the file where
the module resides.
continued
7004 5505-000
4-59
COBGEN Keyword Parameters
Table 4-5. COBGEN Keyword Parameters (cont)
Phase
COBGEN (cont)
Parameter in Coded Format
LIN= fn
ame
£§§i
LIST= [NO 1
1 YES J
ps}
LNKCON
LOFNON=
LSTREF=
LSTWTH=
HAP=
MXNON=
MXREF-
OBJ
II 1
YESj
m
[120-160]
}
}
YES
ml
YESj
[name 1
|$y$run}
{yes}
pagovf= wo 1
|yes|
OBJLST
OBJMOD=
Description
Specifies a 1- to 8-character LFD name
identifying the file where the COPY library
resides. Name is used if the library name is
omitted from the COPY statement. Do not
specify when using JPROCS.
Source program listing.
Linker control statements included in object
module.
Suppresses nonreferenced entries in the
cross-reference listing if CPYTXT-NO and the
entry is within COPY test.
Source listing with definition references.
Specifies listing page width in number of
characters printed per Line.
Object program iocator/MAP listing.
Specifies whether your compiler includes
nonreferenced entries in the MAP listing
with cross-references.
Map listing with cross-references.
Specifies a 1- to 8-character LFD name of the
file where the generated object module is
stored.
Specifies object program listing.
Specifies whether your compiler produces an
object module.
Automatic printer page eject in object
program.
continued
4-60
7004 5505-000
COBGEN Keyword Parameters
Table 4-5. COBGEN Keyword Parameters (cont)
Phase
Parameter in Coded Format
Description
COBGEN (cont)
PROVER= Jf6 1
JYESJ
S98= Jll 1
JYESJ
S!GNFX=
YES
SPRLST= m 1
SPROUT^
SUBCK=
END
SYNCHK
}.
m
TIPCOD= [»
[RE!
TRNADR=
TRUNC=
{tEs}
{yes}
Produces a listing of procedure names and
verbs with associated source line numbers
and object program relative addresses.
Generates object code that runs on 9888
series hardware. This parameter should not
be specified.
Specifies whether the compiler generates
code to check for valid sign in zoned
decimal field.
Suppresses all listings unconditionally.
Parameter overrides all other listing
specifications.
Suppresses compiler output (except source
listing, diagnostic listing, and related
options) when severity code 1, 2, or 3
errors are encountered.
Specifies whether the compiler generates
code to check for subscript or index out -of-
range conditions.
Syntax check compile only.
diagnostic listings only.
Source and
TIP compatible code for COBOL programs
executed under the control of IMS action
program. COBOL language elements protected
by TIP are flagged and deleted.
YES
Indicates generation of shared code action
programs.
REM
Indicates generation of reentrant action
program.
Specifies whether your compiler generates a
transfer address in the object module. If
TRMADR=NO f the program cannot be executed
unless it is called.
Bases data truncation and detection of SIZE
ERROR on the binary and packed decimal items
on an actual storage size allocated to those
items. If omitted, data truncation and
detection is based on specified decimal
digits in a PICTURE character string.
7004 5505-000
4-61
SYSGEN Parameter Reference Tables
4.3. Additional System Parameter Information
This subsection contains reference tables and additional information relative to
various SYSGEN parameters. Use the following SYSGEN parameter reference tables
to prepare SYSGEN parameter sets:
Table Title
4-6 Spool-File Bit Map Calculations (SUPGEN SPOOLMAP parameter)
4-7 Shared Load Module Groups (SUPGEN RESHAEE parameter)
4-8 Logical Unit Numbers (I/OGEN DVGNO parameter for all devices)
4-9 Nine-Track Recording Mode Settings
4-10 Seven-Track Recording Mode Settings
4-1 1 Line Speed Values (COMMCT CACH parameter, Format 2)
4-12 Space Compression Characters (NTRGEN PRTSPnn=hh, NPRTnn=hh,
and TRANS parameters)
4-1 3 Device Function Codes (NTRGEN FUNCD parameter)
4.3.1. Spool-File Bit Hap Calculation Table
The spool-file is divided into logical tracks, and the allocation of these tracks is
controlled by the spool-file bit map. Each bit in a bit map word represents a logical
track, and the size of the bit map (in words) is specified via the SPOOLMAP SUPGEN
parameter. The logical track size is a minimum of 64 (256-byte) sectors, but can be
larger depending on the size of the spool-file and the size of the bit map.
For optimal spool-file space utilization, the bit map should be large enough to permit
the smallest allowable (64 sectors) logical track size. Table 4-6 can be used to
calculate the number of bit map words required to guarantee a 64-sector logical track
size. Multiply the number of cylinders in the spool file by the factor for the disk type
being used; round up to the next higher integer if the result is fractional. The third
column shows the number of bit map words required to guarantee a 64-sector logical
track size for a 50-cylinder spool-file (the default value of the SPOOLCYL keyword
parameter).
4-62 7004 5505-000
SYSGEN Parameter Reference Tables
Table 4-6. Spool-File Bit Map Calculations
Disk Type
Multiplication
Factor
Bit Map Words Needed for
58-Cylinder Spool File
8416
.14
7
8417
.41
21
8418
.14
7
8419
.17
9
8438/8433
.31
16
8478
1.58
75
8494
.94
47
M9728
.94
47
4.3.2. Shared Load Module Groups
Table 4-7 lists the shared load module groups eligible for the SUPGEN RESHARE
parameter. To include a group as resident in main storage, use the group name
symbol in the RESHARE specification. To decide which groups to make resident for
your applications, see the Supervisor Technical Overview, UP-8831.
Table 4-7. Shared Load Module Groups
Group Name Symbol
Group Name
BAS
BASIC
DDPL
Local Distributed Data Processing
DDPR
Remote Distributed Data Processing
DP
Dialog Processor
EDT
Editor
ESC
ESCORT
ESCf
ESCORT FULL
I SB
Basic Interactive Services
ISF
Full Interactive Services (for heavy interactive
who experience main storage fragmentation).
users
RPG
RPG Editor
SF
Screen format Services
7004 5505-000
4-63
SYSGEN Parameter Reference Tables
4.3.3. Logical Unit Numbers (l/OGEN DVCNO Parameter for All Devices)
The DVCNO=lun keyword parameter changes the standard logical unit numbers for
the specific devices within each device category. You can modify or replace the logical
unit numbers for the device or group of devices by specifying the logical unit numbers
in decimal If you specify two or more logical unit numbers, separate them with a
hyphen. We recommend that you do not alter logical unit numbers outside a device
category or alter the logical unit numbers assigned to any device. Table 4-8 lists the
logical unit numbers for the devices supported by the models 8 through 20.
Table 4-8. Logical Unit Numbers
Logical Unit
Number
Device Type and Features
1-13
Spare
14, 15
0791 Correspondence quality printer (CQP-1)
16, 17
8798 printer, no features specified
18, 19
0789 printer
28, 21
Any printer, no features specified
22, 23
9246 printer, no features specified
24, 25
8776 printer subsystem, no optional features specified
28, 29
%77% printer, no optional features specified
38, 31
Any card reader subsystem, no features specified
32, 33
0719 card reader subsystem, no features specified
34, 35
8716 card reader
38, 39
Spare
40, 41
Any card punch subsystem, no features specified
42-45
Spare
46, 47
0688 card punch
48
Any remote printer, no features specified
49
Spare
50-59
Any disk
68-63
8419 disk subsystem
64-66
8416/8418 disk subsystem (low density)
67-69
8418 disk subsystem (high density)
78-74
8430 disk subsystem
75-79
8433 disk subsystem
80-85
8494 disk subsystem
continued
4-64
7004 5505-000
SYSGEN Parameter Reference Tables
Table 4-8. Logical Unit Numbers (cont)
Logical Unit
Number*
Device Type and Features
90-99
108-182
103-105
186-109
110-112
113-115
116-118
119-121
125-127
128, 129
138-133
136, 137
138, 139
140, 141
142, 143
144, 145
146, 147
148, 149
150, 151
152, 153
154-156
168-167
168, 169
170-174
175-179
188-185
186-188
198-199
200-215
216-219
220-223
224-227
228-231
232-254
255, 256
Any tape, no features specified
Any tape, 9- track phase-encoded
Any tape, 9-track NRZI
Any tape, 7- track NRZI
U26, U28, BT3208 tape
U18, U14 tape
U12, U16 tape
U20 tape
U22, U24 tape
Streaming tape
Any diskette
8428/8422 diskette
Any diskette, 128-byte
Any diskette, 256-byte
Any diskette, 512-byte
Any diskette, 1024 -byte
Any tape, 9-track GCR
Double -density diskette
Any diskette, autoloaded
Any diskette, double-sided
Spare
Spare
Any fixed- head disk
8417 disk subsystem
8478 disk subsystem
M9728 disk subsystem
Spare
Spare
Any workstation
Any workstation with 24 x 80 screen
Any printer, class = 1
Any printer, class = 2
Any printer, class = 3
Spare
Any workstation with printer attached
7004 5505-000
4-65
SYSGEN Parameter Reference Tables
4.3.4. Nine-Track Recording Mode Settings (l/OGEN MODE Parameter)
Three recording methods are supported for the nine-track tape devices, such as the
UNISERVO® tapes, available for your system: phase encoding (PE), non-retum-to-
zero (NRZI), and group coded (GCR). Making certain that your System 80 interprets
and processes your tapes correctly depends on the mode of processing you specify
when defining your tape devices during I/OGEN.
Table 4-9 lists the nine-track recording mode settings you must use when specifying
the I/OGEN MODE parameter.
Table 4-9. Nine-Track Recording Mode Settings
""' ' ""
Recording Method
Tape Density
(bpi)
Magnetic Tape Subsystem
MODE=nn Value
(hex.)
Phase encoding
(PE)
1688
UNISERVO 10/12/14/16/20/22/
24/26/28 and BT3208
UNISERVO 11
F9 (fast speed)
C3
E9
(slow speed)
Non - return- to - zero
(NRZI)
800
UNISERVO 10/12/14/16/22/24
C8
Group coded (GCR)
6258
UNISERVO 26 s 28 s and BT3208
D3
4.3.5. Sewen-Track Recording Mode Settings (l/OGEN MODE Parameter)
Seven-track tape support is provided as a compatibility feature for those of you who
have existing data files that were previously recorded on seven-track tapes. Making
certain that your System 80 interprets and processes these tapes correctly is
dependent on the specific tape features installed in your system and the method or
mode of processing you specify when defining your tape devices during I/OGEN.
The following processing modes are supported for systems containing UNISERVO 10
tape devices with seven-track features F31 33-00, F31 33-01, and C31 34-00 installed.
• Normal Processing
Provides read and write capability of seven-track tape recorded in NRZI format
at densities of 200, 556, and 800 bytes per inch (bpi) in either odd or even parity
(feature F31 33-00). Your system must include the nine-track NRZI feature
(F31 35-00) as a prerequisite for this mode of processing. Use the appropriate
recording mode setting in Table 4-10 for defining the I/OGEN MODE parameter
when processing seven-track tapes compatible with this mode of operation.
UNISERVO is a registered trademark of Unisys Corporation.
4-66
7004 5505=000
SYSGEN Parameter Reference Tables
• Data Conversion Processing
Permits reading and writing of disassembled eight-bit data on seven-track tape.
The nine-track NRZI feature (F31 35-00) and the seven-track feature (F31 33-00)
are prerequisites for this mode of processing. This same capability is available
with the addition of data translation processing of IBM seven-track compatible
tapes if your system is equipped with the seven-track NRZI native mode feature
(F31 33-01) in place of the F31 33-00 feature. Use the appropriate recording mode
setting in Table 4-10 for defining the I/OGEN MODE parameter when processing
seven-track tapes compatible with this mode of operation.
• Data Translation Processing
Permits the translation (reading and writing) of six-bit BCD data on tape to
EBCDIC data for processing In the system (feature C31 34-00). Your system must
contain the
nine-track NRZI feature (F31 35-00) with either the seven-track NRZI normal
mode feature (F31 33-00) or native mode feature (F31 33-01) as prerequisites for
this mode of processing. Use the appropriate recording mode setting in Table 4-10
for defining the I/OGEN MODE parameter when processing seven-track tapes
compatible with this mode of operation.
Specific information concerning tape formats, coding conventions, translation and
conversion formats, can be found in the documentation that came with your peripheral
devices.
Table 4-10. Sewen-Track Recording Mode Settings
Mode of Operation
Tap* Parity
I/OGEN MODE=nn Values (hex.)
288 bpi
Tape
556 bpi Tape
888 bpi Tape
Normal Processing
Even
Odd
23
33
63
73
A3
B3
Data Conversion Processing
Odd only
13
53
93
Data Translation Processing
Even
2B
6B
AB
Data Translation Processing
Odd
3B
7B
BB
7004 5505-000
4-67
SYSGEN Parameter Reference Tables
4.3.6. Line Speed Values
Table 4-11 lists the decimal numbers specifying the maximum baud rate obtainable in
the single-line communications adapter (SLGA) subchannel. Use this table for
specifying the line speed value in COMMCT.
Table 4-11. Line Speed Values
User- Specif ied
SLCA Hardware-
Value In CACH
Required Value
Asynchronous
Line Speeds
58
50.8
75
75.0
118
118.8
134
134.5
150
158.8
388
308.8
688
688.8
900
980.8
1288
1288.0
1880
1888.8
2488
2480.8
3688
3688.8
4808
4888.0
7208
7280.0
9688
9688.8
Synchronous
Line Speeds
Any decimal
Any decimal
value less
value less
i',~i:-i,! ";MW'.5
than 2088.8
2088
2888.0
2480
2488.8
4888
4808.8
7288
7288.8
9608
9608.0
48888
48808.8
56888
56880.0
64888
64888.8
4-68
7004 5505-000
SYSGEN Parameter Reference Tables
4,3.7, Space Compression Characters
Table 4-12 lists the two-digit decimal function codes that correspond to the
hexadecimal bytes used for space compression when the keyword parameter
TRANS=NO is specified for both printer and nonprinter devices. Use this table for the
PRTSPnn=hh, NPRTSPnn=hh, and TRANS keyword parameters in NTRGEN.
For example:
PRTSP03=20 indicates that hexadecimal 20 is the space character for printers
with function code 03 when the LOCAL keyword parameter TRANS=NO is
specified.
Or, NPRTSP05=05 indicates that hexadecimal 05 (field data space) is the space
character for all nonprinter type devices with function code 05 when the LOCAL
keyword parameter TRANS=NO is specified.
Table 4-12. Space Compression Characters
nn
hh (Hexadecimal)
Printer
Nonprinter
(Decimal)
(PRTSP)
(NPRTSP)
08
05
FF
81
28
85
02
§5
05
83
20
28
84
FF
28
05
FF
85
86
FF
20
07-14
FF
FF
7004 5505-000
469
SYSGEN Parameter Reference Tables
4.3.8. Device Function Codes
Table 4-13 lists the function codes and their respective meanings for input and output
devices for the FUNCD keyword parameter. This parameter specifies a two-digit
decimal function code that establishes the translation requirements for each image
sent to your Unisys OS 1100 system. Use this parameter with the TYPE and TRANS
keyword parameters.
4.3.9. I/O Guidelines - Co-Channel Support
For co-channeling, a primary path and a secondary I/O path are defined (via the
CHAN/COCHAN and ADDR/COADDR I/OGEN parameters). These paths provide
simultaneous operation. In addition, if the primary path is not operational, the I/O Is
retried on the secondary path. If both paths are not operational, the error message
NON OPERATIONAL CONTROL UNIT Is issued. Frequent occurrences of a
nonoperatlonal path are logged in the error log.
If you use co-channeling, establish your I/O configuration so that J/O activities are
spread over several channels. This improves system performance because the selector
channel can't handle more than one data transfer at a time. If a channel is specified
for a primary path (CHAN 1/OGEN parameter) for a device, then that same channel
should be used as a secondary path (COCHAN I/OGEN parameter) for a co-channeled
device.
The following are sample I/OGEN specifications that depict this recommendation:
CASE1:
TYPE=8419
TYPE=8433
CHAN=1
CHAN=2
COCHAN=l
ADDR=B0-B1
ADDR=80-81
COADDR=80~81
CASE 2:
TYPE=8470
TYPE=8433
CHAN=1
COCHAN=2
CHAN=2
COCHAN=l
ADDR=90~91
COADDR=90^91
ADDR=80^81
COADDR=80-81
If you are generating a system with more than one control unit on the same selector
channel and at least one is an IDCU (that Is, an 8417/18/19/70 disk), then the
following device address combinations must be avoided:
8x with Cy
9x with Dy
At with Ey
Bx with Fy
For example, if you have one 8470 and two 8494 control units and If the 8470 is
configured at address 190, you must avoid configuring anything at address 1D0.
However, the two 8494 control units could be configured at 1A0 and 1E0.
4-70
7004 5505-000
SYSGEN Parameter Reference Tables
Table 4-13. Dewice Function Codes
Function
Code 1
TRANS=YES
TRANS=N0 2
Card Readers and Input Devices
81
82
03
84
85
86
Read
Send
Send
Hex. fieldata 3
EBCDIC
Hex. fieldata 3
EBCDIC
EBCDIC
EBCDIC
Fieldata
Fieldata
ASCII
ASCII
Fieldata
ASCII
Fieldata
Fieldata
ASCII
ASCII
Fieldata
ASCII
Card Punches and Nonprinter Output Devices
01
82
83
94
85
06
Receive
Punch
Receive
Fieldata
Fieldata
ASCII
ASCII
Fieldata
ASCII
Hex. fieldata 3
EBCDIC
Hex. fieldata 3
EBCDIC
EBCDIC
EBCDIC
Fieldata
Fieldata
ASCII
ASCII
Fieldata
ASCII
Printers
%%
81
02
83
Receive
Print
Receive
Fieldata
ASCII
Fieldata
ASCII
EBCDIC
EBCDIC
EBCDIC
EBCDIC
Fieldata
ASCII
Fieldata
ASCII
NOTES:
1 The function code is controlled by OS 1100 for all data
sent to NTR.
2 For TRANS=NO, NTR passes the data untranslated. Fieldata/
ASCII is the standard OS 1108 correspondence for the device
type and function code.
3 Hex. fieldata is the hexadecimal equivalent of fieldata
(Hollerith punch card codes).
7004 5505-000
4-71
Section 5
System Maintenance
Unisys periodically distributes software updates on diskettes. These updates are
designed to maintain or enhance your system's operating effectiveness. Two types of
updates are normally distributed:
• System maintenance packages (SMPs). Each SMP consists of one or more
individual system maintenance changes (SMCs).
• Individual SMCs (not part of an SMP).
5.1. System Maintenance Packages
SMPs contain system maintenance changes (SMCs) that you install on the SYSRES
volume to support OS/3 software operations and effectiveness. SMPs are delivered on
one or more diskettes, as required. They are accompanied by an SMP document that
you must read before installing the SMP.
The SMP document gives information about the specific SMP you are installing and
the processing options you should specify during installation. Although the options
you select may vary with each SMP, follow these general guidelines whenever you
install an SMP:
• Install all SMPs as soon as possible upon receipt.
• Install SMPs in the order they are delivered. For example, install SMP 14A
before you install SMP 14B, SMP 14C, etc.
• Do not install SMPs while running other jobs because SMPs affect your operating
system and unpredictable results could occur.
• Before you execute the installation program, be sure you have a current and
complete copy of your SYSRES volume. See 3.3.8.
7004 5505-000 54
System Maintenance
You can direct the installation program to keep a copy of any affected modules in
SYSRES files before you install an SMP or SMC. These copies are saved in areas
called backout files on either your SYSRES volume or another disk you specify. Specify
this option as a precautionary measure in case an SMP or SMC produces adverse
effects on the system and you must back it out. By keeping the backout copy, you can
restore the system to the way it was before you Installed the SMP.
Each SMP requires approximately 100 cylinders for application. Refer to the SMP
document for the exact amount of space required. Before applying the SMP, you
should erase certain existing files. These files Include SMCBSAT, SMCBMIR,
SMCBTRAN, and the SMCF1LE. Please note that once these files are erased, SMCs
from the previous SMP cannot be backed out. Option 6 of the initial SMC screen
automatically erases these files for you.
If sufficient space is not achieved by erasing the above files, you might need to run
SETREL/COPYREL to transfer SYSRES to another disk. Another alternative to
erasing files or executing SETREL/COPYREL Is to place your backout files on an
alternate disk.
To install an SMP (or individual SMCs that you require but have not yet received as
part of an SMP), run the installation program from the system console or from a
workstation. This program offers additional processing options that let you regenerate
supervisors or 1CAM symbionts If any of these elements are affected during the
Installation.
5.2. Installation of MPs
You can Install SMPs either from a workstation or from the system console. Since you
can perform all the installation tasks from either of these devices, choose whichever
device you prefer. Help screens, however, are displayed only to the workstation user.
The following paragraphs describe the procedure for initiating the Installation
program and installing the SMP.
These procedures show the processing screens you see when you enter the SMC run
command at a workstation and explains the choices offered by those screens and how
you respond to them. You can also use these procedures to run the program from the
system console, but you respond to console messages rather than to screens. (Console
messages are noted Immediately after the workstation screen displays.) When you run
the program from the system console, you must answer the messages the program
displays as follows:
• Press MSG WAIT to position the cursor at the beginning of the next line.
5-2 7004 5505-000
System Maintenance
Key in the option you want to perform and press XMIT. Your keyin must be in
the format:
where:
Is the two-character number of the console message you are responding
to.
Is the number of the option you want to perform.
The time it takes to install an SMP depends on several factors, including the number
of SMCs in the SMP, the number of optional components the system contains, whether
you have already installed some of the SMCs in the SMP, the amount of cache
memory assigned, and whether the SMP is run with backout.
5.2.1. Initiating the SIC Program
To run the SMC program:
1. Perform an initial program load (IPL) to load either the starter supervisor
(SY#BAS or SY$BAS) or one you've generated. Load the starter supervisor unless
the system has a special configuration that requires another supervisor. For the
IPL procedure, see the Operations Guide, 7004 5208. For the SMP supervisor
generation requirements, see the SMP document that accompanies the SMP.
Note: If your supervisor contains the ALTJCS feature, you may want to include
the P S option available in Release 14. This option suppresses the R06
CONTINUE TO $Y$JCS? Y/N message and continues on to $Y$JCS
every time the SMC program initiates a job.
2. Mount the first SMP diskette. (If the SMP is on more than one diskette and you
are using a diskette autoloader, be sure all the SMP diskettes are now in the
loader.)
3. At your workstation or system console, key in:
RV SMC,,IMPUT=CDKD,vsn)
,B=
N
_<A,xxxxxx)
[ # FMT=F]
• m= ft}
[ S NEW=Y]
Note: Shading indicates the default value.
7004 5505-000
5-3
System Maintenance
where:
iNPUT=(DKD,vsn)
Indicates that the input for this job is the SMP diskette. DKD specifies a
data set label diskette and vsn specifies its volume serial number found
on the diskette cover.
_(A,xxxxxx)
Y or N
Specifies whether you want to use the backout feature on your
SYSRES.
(A,xxxxx)
Specifies backout and the vsn for an alternate disk.
If you use backout feature, the following guidelines apply:
• The disk used for the backout files, whether SYSRES or alternate,
should be prepped using a standard disk prep. Specifying your own
VTOC area can lead to backout initialization errors.
• The use of the backout feature increases the time required to install an
SMP and requires additional disk space on the SYSRES to hold the
saved modules.
• The SMC program always creates the following files on the SYSRES
volume.
SMCF1LE - A SAT library containing all SMCs that are part of an
installation.
$Y$SMCLOG - A MIRAM file containing information relating to all
the SMCs and program products applied to the system.
• If you use the backout feature, three additional files (SMCBSAT,
SMCBMIR, and SMCBTRAN) are created on the SYSRES volume or on
an alternate disk. These files must be kept consistent. Do not delete or
change any of them.
54
7004 5505-000
System Maintenance
Note: After your backout files are placed on the alternate disk, you
must always specify that your backout files are on this alternate
disk. If you wish to back out SMCs from an alternate disk, you
must specify the B=(A^cxxxxx) parameter.
When you use this feature, continue to place your backout files
on the disk you initially specified. If you change the disk
specified in the run stream, you receive the following error, and
the SMC program terminates immediately:
SMPU68 SMC BACKOUT FILES NOT ON DISK REQUESTED.
If you are forced to place your backout files on a different disk,
you must first reinitialize the backout files with this key in:
RV SMC„B=INIT
However, please note that B=INIT initializes backout files, and
all SMCs backed out in previous runs are nondeletable.
To regain space on the SYSRES, you can create backout copies
of these files on another disk, on tape, or on diskette and then
erase the files from the SYSRES (except for $Y$SMCLOG,
which is a system file and therefore cannot be erased).
Remember, however, that if you want to preserve backout
capability, you must restore these files to your SYSRES before
running the SMC installation program again.
As each SMC in an SMP is applied, the modules changed by the SMC
are stored in the appropriate backout files and the entry in
$Y$SMCLOG is marked BACKED UP. Each module is stored in the
backout file only once. Thus, each module in the backout file is stored as
it was prior to the application of any of the SMCs in the SMP.
When the SMC program is run to back out an SMC, any other SMCs
that affect the same modules are reapplied during the run.
If you apply additional SMCs after installing an SMP, the new SMCs
are added to the SMCFILE that was created by the original SMP run.
Also, any additional modules affected by the new SMCs are added to the
backout files. The end result is the same as if the new SMCs were
included in the SMP.
7004 5505-000 5-5
System Maintenance
FMT=F
PRT=
Specifies that a foil listing of SMCs is printed by the SMCLIST
program. Specify this option if you want more information about each
SMC than is provided by a condensed listing. For example, the full
listing shows whether an SMC is required or optional. If this option is
not specified, a condensed listing is printed.
Specifies whether the output is directed to the printer (PRT=Y) or to the
spool file (PRT=N).
NEW=Y
Specifies that new versions of the SMC program load and/or JCL
modules are to be copied to the SYSRES before SMC processing begins.
A diskette labelled CORETT accompanies the SMP/SMC diskettes
when this parameter is required.
4. Press XMIT. The SMC installation program displays messages telling you that
the librarian facilities are copying the contents of the SMP diskette to the
SYSRES to prepare for installation of the SMP. If the SMP is on more than one
diskette, you receive messages instructing you to mount the next diskette. In
response to those messages, mount the requested diskette and key in the
two-character message number and R for ready in the format nn R, where nn Is
the message number. Then, press XMIT. When the librarian completes the
operation for the SMCFILE, the librarian terminates and the SMC query
program (Figure 5-1) begins.
SMC APPLICATION SCREEN 1 - PROCESSING OPTIONS MENU
1. APPLY SMC IN NORMAL MODE (ACCEPT ALL DEFAULTS).
2. CHANGE NORMAL DEFAULTS.
3. PERFORM SPECIAL SMC PROCESSING.
4. PERFORM SUPERVISOR REGENERATIONS.
5. PERFORM I CAM REGENERATIONS.
6. ERASE 'SMCFILE' AND ALL BACKUP AND M$CO FILES.
7. HELP - OBTAIN ADDITIONAL INFORMATION.
8. ACCEPT SELECTED OPTIONS AND APPLY SMC.
ENTER SELECTION NUMBER: 1 ;PRESS TRANSMIT.
PRESS FUNCTION-F2 TO CANCEL JOB.
Figure 5-1. Processing Options Meny Screen
5-6
7004 5505-000
System Maintenance
Notes:
1. If you run the program from the system console, these options appear as a
series of messages that are scrolled up from the bottom of the screen. All
the options appear, with the exception of option 7 because the program
provides help screens only to workstation users.
2. To cancel the job, press FUNCTION and F2 simultaneously. Do not
cancel the job with the CANCEL command.
3. Options 1 and 2 on the processing options menu are mutually exclusive to
options 4 and 5. Therefore, selecting option J or 2 after 4 or 5 in the same
run of the SMPjob cancels option 4 or 5. Selecting 4 or 5 after lor 2
cancels option 1 or 2. However, options 4 and 5 are cumulative, so you
can enter both of these two options (4 or 5) in the same run without
canceling the other.
Determine from the options listed on this screen which function you want to
perform:
If you want to install an SMP (options 1 and 2), go to 5.2.2.
- If you want to perform additional supervisor regenerations only (option 4) or
additional ICAM regenerations only (option 5), go to 5.2.3.
- If you want to erase files created by the program after installation (option 6),
go to 5.2.4.
5.2.2. installing an SMP
Perform the following procedure after completion of the procedure in 5,2.1 if you want
to install an SMP. You can install an SMP in normal mode and thus accept the default
processing options provided, or you can suppress the defaults and install an SMP with
options you select yourself.
• To install an SMP in normal mode, go to step 1.
• To install an SMP and change the defaults, go to step 2.
1. Key in 1 and press XMIT, The SMC program accomplishes the following tasks:
Installs all the SMCs that apply to the system
Regenerates the supervisor you loaded to install the SMP if the SMP affects
its operation. If the basic supervisor was not loaded, the SMC program
regenerates it also.
- Prints an audit report of the status of all the SMCs installed in the system
7004 5505-000 5-7
System Maintenance
When the program completes these tasks, go to step 3.
2. Key in 2 and press XM1T to install an SMP without the normal defaults.
The installation program then displays the first of two additional processing
screens, the supervisor regeneration screen (Figure 5-2).
SMC APPLICATION SCREEN 3 - SUPERVISOR REGENERATION
REGENERATION OF UP TO THREE SUPERVISORS MAY BE PERFORMED ONLY OR
AT THE END OF THE SMP/SMC INSTALLATION.
DO YOU WISH TO REGENERATE A SUPERVISOR: AM. YES/NO
IF YOU WISH TO DO REGENERATIONS ENTER THE NAMES OF THE SUPERVISOR
PARAMETER SOURCE MODULES AND PRESS TRANSMIT.
XXXXXXXX XXXXXXXX XXXXXXXX
NOTE: TO REGENERATE A SUPERVISOR THE MODULE (PREFIXED WITH S7 FOR MODEL 7E
AND S8 FOR ALL OTHERS) CONTAINING SUPERVISOR PARAMETERS MUST BE
AVAILABLE IN $Y$SRC. IF YOU DO NOT WANT THE IPL'D OR BASIC SUPERVISORS
LISTED ABOVE REGEN'D, OVERWRITE THEM WITH SUPERVISORS OF YOUR CHOICE.
PRESS FUNCTION-F1 TO CANCEL SCREEN AND RETURN TO THE MASTER MENU.
PRESS FUNCTIONS TO CANCEL JOB.
PRESS FUNCTI0N-F13 FOR HELP INFORMATION.
J v - -, ' \ ■!>■,'- ,, m. ., .-
Note: The following messages are displayed to the console user:
SMPQ30 ENTER UP TO 3 SUPERVISOR NAMES, N: NO SUPVR REGEN,
# SMPQ78 C: CANCEL JOB, OR M: RETURN TO MENU. DEFAULT? ipl'd supervisor
a. Enter the source module names of the supervisors that you want to
regenerate and press XMIT. Remember that a supervisor cannot be
regenerated by the program unless the supervisor source module, prefixed
with S8, resides in $Y$SRC on the SYSRES and does not contain any errors.
There can only be one supervisor per module in $Y$SRC.
5.8
7004 5505-000
System Maintenance
If you're a workstation user, notice the options that appear at the bottom of
this screen as well as on each of the additional processing screens displayed
by the program, Select one of these options simply by simultaneously
pressing FUNCTION and the workstation function key that corresponds to
the option you want to perform:
FUNCTION - Fl Cancels the current screen and redisplays the
processing options menu.
FUNCTION - F2 Cancels the job.
FUNCTION - F13 Displays a help screen providing additional
information about the choices on the current screen.
Note: If you use the system console, you can return to the processing
options menu by entering M and pressing XMIT or cancel the job by
entering C and pressing XMIT. Help screens are not available to the
console user.
b. After you specify the supervisor elements you want to regenerate and press
XMIT 3 the following screen is displayed (Figure 5-3).
SMC APPLICATION SCREEN 4
I CAM REGENERATION
UP TO THREE ICAM REGENERATIONS CAN BE PERFORMED DULY OR AT THE
END OF THE SMP/SMC INSTALLATION.
DO YOU WISH TO REGENERATE AN ICAM:
YES/NO
IF YOU WISH TO DO REGENERATIONS ENTER THE NAMES OF THE ICAM PARAMETER
SOURCE MODULES AND PRESS TRANSMIT.
XXXXXXXX XXXXXXXX XXXXXXXX
NOTE: TO REGENERATE AN ICAM, THE MODULE CONTAINING THE ICAM PARAHETERS
MUST BE AVAILABLE IN $Y$SRC.
PRESS FUNCTION-F1 TO CANCEL SCREEN AND RETURN TO THE MASTER MENU.
PRESS FUNCTION-F2 TO CANCEL JOB.
PRESS FUNCTIQN-F13 FOR HELP INFORMATION.
Figure 5-3. ICAM Regeneration Screen
Note: The following messages are displayed to the console user:
SMPQ38 ENTER UP TO 3 ICAM NAMES. N: NO ICAM REGEN #
# SMPQ70 C: CANCEL JOB, OR M: RETURN TO MENU. DEFAULT :M
7004 5505-000
5-9
System Maintenance
You can regenerate up to three ICAM elements by entering the ICAM source
module names and pressing XMIT. As with supervisor regeneration, an
ICAM element cannot be regenerated by the SMC program unless the ICAM
source module resides in $Y$SRC on the SYSRES. If a prefix is entered, all
ICAM modules in $Y$SRC with that prefix are regenerated.
c. After you specify the ICAM elements you want to regenerate and press
XMIT, the processing options menu shown in Figure 5-1 is redisplayed. Key
in 8 (or 7 if you're running the program from the system console) and press
XMIT. The program then:
- Installs all the SMCs that apply to the system
- Performs any regenerations that you specified
Prints an audit report of the status of all the SMCs installed
3. After installing an SMP, the program displays a message to tell you that:
• The SMC job is issuing a command to execute SMCLIST.
• The SMC job terminated normally.
The SMC job leaves job slot 1 and SMCLIST takes its place. SMCLIST then
provides a condensed printout of the contents of $Y$SMCLOG ? which is a record
of all the SMCs that were installed in the system. If you specify the FMT=F
option on the SMC execution command, a full listing is printed. This listing
provides such additional information as whether an SMC is required or optional.
When SMCLIST successfully prints this list, a message informs you that
SMCLIST has terminated normally. The SMP installation process is now
complete.
It is recommended that you keep the SMCLIST printout with your other system
records so that you have a record of all the SMCs installed in the system. If you
wish to print that list, refer to the System Service Programs Operating Guide,
UP-8841, for instructions on executing SMCLIST as a separate function from the
SMC process.
Note: After you install an SMP, check the SMP document to see if the SMP
requires that you update the system definition file, $Y$SDF. If so, see
2.3.1 for the procedure for updating loadable microcode. Also, check the
audit trail printout for special notes about the SMP you just installed.
4. When the SMP installation is complete, perform an initial program load (IPL) to
continue with your normal processing. Be sure to specify the S option to update
the system tables.
Note: If the system has any supervisors or any ICAM elements affected by the SMP
(other than elements automatically regenerated as defaults) and you did not
tell the program to regenerate them, be sure to regenerate them yourself before
you load and use them. See Section 3 for the system generation procedure.
5-10 7004 5505-000
System Maintenance
5.2,3. Performing Additional Regenerations
Perform the following procedure after completion of 5.2.1 if you want to perform
additional supervisor or 1CAM regenerations. Proceed as follows:
• If you want to perform additional supervisor regenerations only, go to step 1.
• If you want to perform additional 1CAM regenerations only, go to step 2.
1. Key in 4 and press XMIT to display the supervisor regeneration screen
(Figure 5-2) or console messages. Enter the supervisor elements you want to
regenerate and press XMIT. The SMC program then redisplays the processing
options menu. If you want to perform additional tasks, repeat step 5 of 5.2.1.
Otherwise, key in 8 (or 7 if you're running the program from the system console),
press XMIT, and go to step 3 of this procedure.
2. Key in 5 and press XMIT to display the ICAM regeneration screen (Figure 5-3) or
console messages. Enter the ICAM elements you want to regenerate and press
XMIT. The SMC program redisplays the processing options menu. If you want to
perform additional tasks, repeat step 5 of 5.2.1. Otherwise, key in 8 (or 7 if you're
running the program from the system console), press XMIT, and go to step 3 of
this procedure.
3. The program performs the additional tasks that you specified, informs you when
it has successfully done so, and displays messages to tell you that:
- The SMC job is issuing a command to execute SMCLIST.
The SMC job terminated normally.
The SMC job leaves job slot 1 and SMCLIST takes its place. SMCLIST then
provides a condensed printout of the contents of $Y$SMCLOG, which is a record
of all the SMCs installed in the system. If you specify the FMT=F option on the
SMC execution command, a full listing is printed. This listing provides such
additional information as whether an SMC is required or optional. When
SMCLIST successfully prints this list, you receive a message informing you that
SMCLIST terminated normally. The process of performing additional
regenerations is now completed.
7004 5505-000 541
System Maintenance
5.2.4. Erasing SWP Files
After installing an SMP, you can erase the SMCFILE, a file containing all the SMCs
that are part of an SMP, and all backout files. Specify option 6 on the processing
options menu and press XMIT. The SMC program erases each of these files, updates
the $Y$SMCLOG to indicate that backout files no longer exist, and displays a message
to tell you that the SMC job terminated normally. Do not erase these files, however,
unless you are certain all SMCs in the SMP are successfully installed. If you used an
alternate disk for your backout files, you must specify B=(A,xxxxxx), where xxxxxx is
the vsn of your backout disk.
Note: Erase these files only if you no longer want to retain backout capability for
SMCs contained in the SMCFILE. Use the SMC program to erase SMC files,
as this automatically updates the $Y$SMCLOG to reflect this action.
5.3. Installation of Indiwiduai SMCs
If you receive an individual SMC prior to a regular SMP release, install it with the
same procedure used to install an SMP.
If you receive the SMC over the phone or through the mail, you must build the SMC in
the standard OS/3 change format yourself. The SMC installation program lets you
enter the changes from workstations or from the system console. If you elect to use a
workstation, the SMC program interactively displays fill-in-the-blank screens that
help you build the SMC in the correct change format.
If you use the console, the SMC program initiates the SMC console dialog to help you
build the change in the correct format.
Figure 5-4 illustrates the installation of an individual SMC.
Figure 5-4. Installation of Indivldyal SMCs
5-12
7004 5505-000
System Maintenance
5.4. tunning the SMC Installation Program
The following paragraphs describe the procedure for installing Individual SMCs that
are not part of an SMP.
Shown in the procedure are a series of interactive processing screens. These screens
are applicable only to workstation users. They explain the installation choices offered
by the SMC program and how you respond to them. You can also use this same
procedure to run the SMC program from the system console. When using the system
console, you respond to console messages rather than to screens. These messages are
noted immediately after the corresponding workstation screen. When running the
SMC program from the system console, you must answer the messages the program
displays as follows:
• Press MSG WAIT to position the cursor at the beginning of the next line.
• Key in the option you want to perform and press XMIT. Your keyin must be in
the format:
where:
is the two-character number of the console message you are
responding to.
<"!
Is the number of the SMC installation option you want to perform.
Perform the following steps to Install the individual SMC:
1. Perform an initial program load to load either the starter supervisor (SY#BAS or
SY$BAS) or one you've generated. Load the starter supervisor unless your system
has a special configuration that requires another supervisor.
Note: If your supervisor contains the ALTJCS feature, you may want to include
the ,S option available in Release 14. This option suppresses the R06
CONTINUE TO $Y$JCS? YIN message and continues on to $Y$JCS
every time the SMC program initiates a job.
2. If you received the SMC on diskette, mount that diskette and proceed to step 3. If
you received the change over the telephone or through the mail, proceed directly
to step 3. If you received the change on keypunched cards, read the note that
follows before inserting the card deck into your card reader and proceeding to
step 3.
7004 5505-000 543
System Maintenance
Note: If you are installing more than one SMC on cards, you can combine the
SMC decks and key in the SMC run command once to install all the
SMCs in the combined deck. Remove the / / FIN cards from the end of
each SMC deck except for the last deck and insert a I* card immediately
before the last 1 1 FIN card. If your system uses spooling, continue to read
this note. If your system does not use spooling, insert the combined card
deck into your card reader and proceed to step 3.
If your system uses spooling, you must create a spool file containing the
data in the card decks before you run the SMC program. To create the
spool file, place the following card at the beginning of the deck:
// DATA FILE I D=SMCREADER„ IGNORE
Insert the entire deck into the card reader and then enter the command
IN from your system console / workstation in console mode. The system
displays the message SPOOLFILE SMCREADER WAS CREATED after
it successfully creates the spool file. Proceed to step 3.
3. At the workstation or system console, key in:
RV SMC
"
*
,1NPUT=
"c
(DKD.vsn)
(DKF # vsn)
,B=
fl 1
N
.(AfXXxxxx),
•
[,FMT=F]
■ m= | "
CR
J
(D:,RES)
(D,vsn)
(CR s vsn)
.US
[,NEW=Y]
where:
Describes the medium you are using to enter the SMC into the system.
If you run the SMC program only to perform supervisor or IGAM
regenerations or to realign system files, omit this parameter.
Note that the INPUT parameter does not describe the device where
you're running the SMC program. There is a difference. You can run the
SMC program from your workstation or system console, but input the
SMC through any of the media described in the following list.
IMPUT=C
Specifies that you build the SMC in the correct change format using the
SMC console dialog at the system console. Choose this method if you
received the SMC over the telephone or through the mail and there are
no workstations in the system.
544
7004 5505-000
System Maintenance
INPUT=(DiCD,vsn)
Specifies the volume serial number of a data set label diskette.
INPUT=(DKF f vsn)
Specifies the volume serial number of a format label diskette.
INPUT=CR
Specifies the card reader. Select this if you received the SMC on cards or
if you keypunched the cards yourself.
Note: If you keypunch the SMC yourself, be sure you start the
1 1 OPTION SMC card in column 30 on card 2 y and include
only one space after the slashes and the word option. Otherwise,
you get errors.
Specifies that the SMCs to install reside in the SMCF1LE on SYSRES.
lMPUT=(D f vsn)
Specifies that the SMCs to install reside in the SMCFILE on the disk
with the specified volume serial number.
INPUT~(CR,vsn)
Specifies the volume serial number of a diskette to be used as card
reader input.
input =ws
Specifies that a workstation is used to enter the SMC. Specify this
choice if Unisys supplies the SMC information to you over the telephone
or through the mail.
B=
N
(A,xxxxxx}j
Specify this optional parameter only if you do not want the SMC job to
create permanent backout files on your SYSRES. The A specifies
backout for an alternate disk and xxxxxx specifies the vsn of this disk.
FMT=F
Specifies that a full listing of SMCs is printed by the SMCLIST
program. Specify this option if you want more information about each
SMC than is provided by a condensed listing. For example, the full
listing shows whether an SMC is required or optional. If this option is
not : : 4»<.x: ; i^yl ■■ eo;v^n,--,;d 'lis^uj; v; y->. ■."'.'■■;)
7004 5505-000 5-15
System Maintenance
PRT = pj
Specifies whether the output is directed to the printer (PRT=Y) or to a
spool file (PRT=N)
NEW-Y
Specifies that new versions of the SMC program load and/or the JCL
modules are to be copied before SMC processing begins. A diskette
labelled CORETT accompanies the SMP/SMC diskettes when this
parameter is required.
Notes:
1. Shading indicates the default value.
2. If you specify INPUT=C, you elected to use the SMC console dialog to build
your SMC; press XMIT and proceed to 5.4. 1.
3. If you specify INPUT=WS, you elected to use the workstation interactive SMC
entry process to build your SMC; press XMIT and proceed to 5.4.2.
4. If you do not need to build the SMC, press XMIT and proceed to 5.4.3.
5.4.1. Building Your SMC from the Console
Because you specified INPUT=C on the SMC execution command, the SMC job
initiates the SMC console dialog to build the change in the standard OS/3 change
format. A sample SMC in 5.5 shows, in the correct change format, the parts of the
change that Unisys provides and the information you must supply in response to
the SMC console dialog queries. If you received the SMC over the telephone, your
Unisys representative must supply all the information you need to answer the
dialog queries. Respond to the dialog queries in the following manner.
Note: If at any time in the current dialog session, you respond incorrectly to a
dialog query, key in CANCEL, press XMIT, and respond Y to the
subsequent message PROCESS ANOTHER SMC (Y OR N)? The SMC
dialog ignores all previous responses, both correct and incorrect, and
redisplays the dialog starting at step 1 so that you may enter correct
responses.
1 . When the message ENTER SMC NUMBER (XXXXXXX) appears, key in the
seven-character SMC number and press XMIT.
2. When the message ENTER COMPONENT NUMBER (XXXX) appears, key
in the four-character component number and press XMIT.
546 7004 5505-000
System Maintenance
3. When the message ENTER APPLIES TO RELEASE LEVEL
appears, key in the release level that the SMC applies to and press XMIT.
You must key in the release level as a six-digit number. For example,
Release 14.0 would be 140000.
4. When the message ENTER PRODUCT TYPE NUMBERS (XXXX-XX)
appears, key in a six-character, hyphenated product type number and press
XMIT:
5. When the message ENTER SYSTEM CODE (S=MOD 4-6, 8=MOD 8 thru 20,
7= MOD 7E, C=COMMON) appears, key in 8 and press XMIT.
6. When the message ENTER REGEN FLAGS (XXXXXXXX) appears, check
the REGEN specification in the job control provided. Key in Y for yes or N for
no for each of the eight fields in the specification in exactly the way that it is
shown. The REGEN flags identify the types of regenerations required as a
result of installing this SMC. Each field contains a value, either Y or N, that
tells whether regeneration is required for each type of module the system
could include. The eight fields in the value correspond to supervisors, ICAM
generations, NTR networks, ICAM links, ANSI '74 COBOL compiler
modules, IMS modules, and DMS modules (the eighth field identifies any
other modules affected by this SMC and is explained in line 13 of the job
control we provide). For example, installation of the sample SMC in 5.5
requires no regenerations because all eight REGEN flags show N for no.
7. When the message REQUIRED SMCs? (XXXXXXX,...MAX=5) appears, key
in up to five seven-character SMC numbers of prerequired SMCs and press
XMIT. If there are no required SMCs, simply press XMIT.
8. When the message ENTER CHARACTER TO REPRESENT LEADING
SPACE appears, key in any character on the keyboard that is not included in
the actual SMC. You must key in this character in steps 9 and 10, which
follow, as a substitute for leading spaces in any change lines requiring them.
If you don't specify a character, you must use the left bracket ([).
Note: The first time the messages in steps 9 and 10 appear, 32 occupies the
field XX because line 32 of an SMC is the first line of the actual
change and the first line you must key in. Each successive time these
messages appear, the number in the field XX increases by one until
you key in LAST to tell the SMC program you have no more change
lines to key in.
9. When the message ENTER LINE XXX COLS 1 TO 60 appears, either
continue entering the SMC at the console or use the card reader as the input
device for the remainder of the SMC.
a. To use the card reader, enter the letters CR in response to the ENTER
message and press XMIT. The card deck should contain the SMC
preceded by a // JOB card and followed by a /*. Then, continue with step
11 of this procedure.
7004 5505-000 547
System Maintenance
b. If you continue using the console, respond to the ENTER message by
keying in the first 60 columns of each line of the job control for the SMC 3
then pressing XMIT. You must provide the following (including
slashes):
• DVC-LFD sequences of any files that the SMC affects
• Execute statement for whatever system program that the SMC
executes. The SMC could execute one of the following system
programs to change the corresponding program module:
LIBS - to correct the SAT module
TRNPAT - to correct the system transient file
- MLIB - to correct the system MIRAM module
- MSGGEN - to correct the system message file
• /$
• Any parameters associated with the system program you are
executing
If you have no more change lines, key in LAST, press XMIT, and
proceed with step 11.
10. When the message ENTER LINE XXX COLS 61 TO 80 appears, key in the
last 20 columns of the information requested in step 9 and press XMIT. If
your entire change line fits on the first 60 columns, press XMIT and go back
to step 9.
1 1 . When the message ACCEPT THIS SMC (Y OR N)? appears:
• Check your responses to all the previous queries.
• Key in Y and press XMIT if they are all correct and proceed with step
12; key in N and press XMIT if any are incorrect. This response causes
the entire SMC to be disregarded and displays the message: PROCESS
ANOTHER SMC (Y or N)?
12. When the message PROCESS ANOTHER SMC (Y OR N)? appears, key in Y
if you need to define another SMC, press XMIT, and repeat the procedure
(5.4.1.). If you have no other SMCs to define, key in N and proceed to 5.4.3.
548 7004 5505-000
System Maintenance
5.4.2. Building Your SMC from a Workstation
Because you selected INPUT=WS on the SMC execution command, the SMC job
initiates the Interactive SMC Entry process for building the change (in the
standard OS/3 change format) from a workstation. The interactive process
displays a series of interactive screens explaining the build procedure and
showing both the required and optional data entry fields you are to complete. (If
you received the SMC over the telephone, a Unisys representative must supply
all information you need to use this process and complete the data entry fields.) A
blinking field on the screen indicates that you failed to enter data into a required
field or that the data you entered is invalid. The program does not allow you to
transmit an invalid or incomplete screen. To correct the entry screen, simply tab
back to the blinking field, reenter the data, then position the cursor at the bottom
of the screen, and press XMIT. If the data you entered is valid and complete, the
SMC program accepts the data and displays the next interactive screen. A sample
SMC showing both the information provided by Unisys and the information
supplied via the blank fields of the INTERACTIVE SMC ENTRY screens is
provided at the end of this section.
Note: If at any time during this process you want to terminate the. SMC job,
press FUNCTION and Fl simultaneously.
Perform the interactive SMC entry process in the following manner:
1. Figure 5-5 shows the first screen displayed. This screen explains the
Interactive SMC Entry process and lists the instructions for using the
workstation. After reading this screen, press XMIT to continue with the SMC
entry procedure.
INTERACTIVE SMC ENTRY INSTRUCTION SCREEN [01]
THE FOLLOWING SCREENS WILL REQUEST INFORMATION REQUIRED TO BUILD AN
SHC IN OS/3 FORMAT. JUST ENTER THE REQUESTED INFORMATION BY FILLING
IN THE BLANKS. YOU MAY TAB OVER FIELDS TO ACCEPT ANY DEFAULT VALUES.
A DATA FIELD WILL BLINK TO INDICATE THAT INVALID INFORMATION HAS BEEN
ENTERED OR THAT A FIELD WHICH REQUIRES INFORMATION TO BE ENTERED WAS
LEFT BLANK. JUST TAB TO THE BLINKING FIELD AND OVERWRITE IT WITH THE
CORRECT INFORMATION.
WHEN YOU HAVE COMPLETED A SCREEN, PRESS XMIT TO CONTINUE WITH
THE NEXT SCREEN. AFTER COMPLETING THE TWO FORMAT SCREENS YOU WILL BE
REQUESTED TO ENTER THE PATCH CARDS.
YOU MAY ELECT TO START OVER AT ANY TIME BY PRESSING FUNCTION KEY 1 [Fl].
PRESS [XMIT] TO CONTINUE OR, [Fl] TO TERMINATE. <_>
Figure 5-5. SMC instruction Screen
7004 5505-000 549
System Maintenance
2. Figure 5-6 shows the first SMC data entry screen. Complete (fill in) the
blank fields shown on this screen.
INTERACTIVE SMC ENTRY S..C KEEN [03]
// JOB ,jm%, 14080 X
// DVC 28 // LFD PRMTR // OPTION SMC
// NOP 'CORRECTION IS FOR '
// NOP 'IT WAS SUBMITTED ON AND IS '
// NOP 'IT APPLIES TO RELEASE THRU '
// NOP 'IT IS TESTED AND IS FIELD VERIFIED '
// NOP 'THE SUR ORIGINATED IN '
// NOP "CORRECTION HAS BEEN APPLIED TO RELEASE _._._ '
// NOP 'IT IS INCLUDED IN '
// NOP 'COMPONENT SOURCE IS CORRECTED IN RELEASE '
// NOP 'CONTINGENCY: SYSTEM=» REGEN=
// NOP '
// NOP 'FIXES SURSs '
// NOP 'REQUIRED COR: XXXX,XXXX,XXXX,XXXX,XXXX «
// NOP 'REPLACES COR: XXXX,XXXX,XXXX,XXXX,XXXX >
PRESS [XMIT] TO CONTINUE OR, [F1] TO START OVER. <_>
Figure 5-6. First SMC Entry Screen
3. Press XMIT to enter your data and to display the second SMC entry screen
shown in Figure 5-7. Fill in the required fields on this screen.
I h
TERACTIVE SMC ENTRY SCREEN [84]
// NOP '
IS REQUIRED BY CORS: XXXX,XXXX,XXXX,XXXX f XXXX •
// NOP
IS REPLACED BY CORS: XXXX S XXXX # XXXX,XXXX,XXXX «
// NOP
CORRECTION REQUIRES WITH VSN MODULE= '
// NOP
// NOP
(FILEID= ) '
CORRECTION DESCRIPTION: «
// NOP
// NOP
// NOP
// NOP
// NOP
// NOP
ECN=NONE »
// NOP
MODULES CORRECTED: '
// MOP
// NOP
// NOP
•CORRECTION CARD COUNT: _____ •
PRESS [XMIT] TO CONTINUE, OR [Fl] TO START OVER.
<->
Figure 5-7, Second SMC Entry Screen
5-20
7004 5505-000
System Maintenance
Press XMIT. If you made any errors on either of the entry screens, the
incorrect fields begin blinking. Should this occur, check the line to verify that
you entered it correctly, correct any errors, and press XMIT.
At this point, the workstation screen is cleared and a series of prompts for
the remainder of the change are displayed. Multiple spaces are not required
when entering an SMC.
When the line number prompt appears, key in the first line of the actual
SMC and press XMIT. Continue to enter all the lines of the actual SMC,
pressing XMIT after each one. You must enter the complete SMC as shown.
If any lines are omitted, you receive an error message.
If you have no more change lines, either press FUNCTION and the F2 key
simultaneously, or enter the word LAST and press XMIT. Proceed with
step 5.
When the message ACCEPT SMC (Y,N) OR CMD (C,D,F,I,P,S,U OR HELP)
appears, check your previous entries, then:
• If all entries are correct, key in Y and press XMIT. Proceed to 5.4.3.
• If the SMC is not in acceptable format, you may be able to correct it
with the SMC editor, a facility we provide to make SMCs easier to
prepare. Enter the command HELP and press XMIT to display the
editing commands HELP screen (Figure 5-8). Proceed with step 6.
EDITING COMMANDS HELP SCREEN [01]
= THE COMMAND REQUEST EXPECTS THAT YOU WILL ENTER THE LETTER OF THE COMMAND
= AND THEN PRESS THE RED [XMIT] KEY.
= SOME OF THE COMMANDS REQUIRE A LINE NUMBER (INDICATED BY THE '#' SYMBOL
= FOLLOWING THE COMMAND EXPLANATION BELOW), WHICH SHOULD BE SUPPLIED WITH
= THE COMMAND LETTER.
= YOU WILL BE PROMPTED FOR A LINE NUMBER IF ONE IS NOT SUPPLIED.
SYNTAX
COMMAND
C#
COPY
D#
DELETE
F
FIND
I
INSERT
SYNTAX
N
p#
S#
U#
y
COMMAND
NO
PRINT
SWAP
UPDATE
YES
FOR A MORE DETAILED EXPLANATION OF ANY COMMAND, JUST ENTER ITS LETTER HERE <X>
AND PRESS THE [XMIT] KEY, OTHERWISE PRESS [F1], [F2], OR THE [XMIT] KEY.
Figure 5-8. Editing Commands HELP Screen
7004 5505-000
5-21
System Maintenance
To perform one of the functions listed on this screen, enter the first letter of
that function and press XMIT. The following functions should be particularly
helpful to you in editing an SMC:
• C(opy) Duplicates a card image from one line to another. The
command must include two pieces of information - the line
number of the source image and the line number of the
destination line. If you request this command but do not
supply the line numbers of the source image or the destination
line, you are prompted to supply them. Any invalid line
numbers cause the INVALID ENTRY message and the
command terminates and returns control to the SMC editor.
To enter the source line number with the command, key it in
immediately following the command letter, for example, C043.
• F(ind) Scans the SMC card images for a search string and displays all
cards that contain the string. The search string can be up to 20
characters long. A prompt requests that you supply this string.
• I(nsert) Creates a new card image between two other lines in the SMC.
You must supply the line number where the source image is
inserted. The card image you are creating are inserted into the
SMC at this location and any existing lines are moved down. If
you request this command, you must supply the line number of
the source image and the text of the line or you are prompted
for it. An invalid line number causes the INVALID ENTRY
message, and the command terminates and returns control to
the SMC editor. To enter the source line number with the
command, just key it in immediately following the command
letter, for example, 1043.
• P(rint) Displays the SMC on the workstation screen. You can supply a
line number with this command in the format Pxxx (where xxx
is the three-digit starting line number of the lines to be
displayed). If no line number is supplied, the entire SMC is
displayed. The SMC is scrolled up from the bottom of the
screen until either the last line is displayed or you decide to
halt the display by pressing FUNCTION and F
simultaneously. To continue the display, press FUNCTION
and F19 simultaneously. If, at any time, you want to end the
display, press FUNCTION and F18 simultaneously.
• S(wap) Exchanges one card image with another. You must supply the
line number of the image (the line to swap from) and the line
number of the destination line (the line to swap with). The
command prompts you for this information if you do not
supply it. Any invalid line numbers causes the INVALID
ENTRY message, and the command terminate, returning
control to the SMC editor. To enter the source line number
with this command, just key it in immediately following the
command letter, for example, S043.
5-22
7004 5505-000
System Maintenance
• U(pdate) Displays the requested line and allows it to be changed. You
must supply a line number with this command in the format
Uxxx (where xxx is the three-digit line number you want to
update). If you do not supply a line number with the command,
a prompting message is displayed.
After you perform one of the editing functions, press XMIT to redisplay the
ACCEPT message: ACCEPT SMC (Y,N) OR CMD (C,D,F,I,P,S,U OR HELP)
• If all entries are correct, key in Y and press XMIT. Proceed to 5.4.3.
• If the SMC is not in acceptable format, enter the command HELP and
press XMIT to redisplay the editing commands HELP screen
(Figure 5-8). Repeat step 6 of this procedure.
• If the SMC cannot be corrected by repeating step f, enter N and press
XMIT. This response restarts the interactive SMC entry process. Return
to step 1 of this procedure and reenter your SMC information.
5.4.3. Installing the SMC
The SMC program displays the following menu screen asking what type of
processing you want.
SMC APPLICATION SCREEN 1 - PROCESSING OPTIONS MENU
1. APPLY SMC IN NORMAL MODE (ACCEPT ALL DEFAULTS).
2. CHANGE NORMAL DEFAULTS.
3. PERFORM SPECIAL SMC PROCESSING.
4. PERFORM SUPERVISOR REGENERATIONS.
5. PERFORM I CAM REGENERATIONS.
6. ERASE 'SMCFILE' AND ALL BACKUP AND M$CO FILES.
7. HELP - OBTAIN ADDITIONAL INFORMATION.
8. ACCEPT SELECTED OPTIOMS AND APPLY SMC.
ENTER SELECTION NUMBER: 1 ;PRESS TRANSMIT.
PRESS FUNCTI0N-F2 TO CANCEL JOB.
Note: If you run the SMC program from the system console, these options
appear as a series of messages that are scrolled up from the bottom of the
screen. All the options appear, with the exception of option 7 because the
SMC program provides help screens only to workstation users.
7004 5505-000
5-23
System Maintenance
The options on this screen are described in 5.2. Determine from the options listed
on this screen which function you want to perform.
Note: Options 1 and 2 on the Processing Options Menu are mutually exclusive
to options 4 and 5. Therefore, selecting option 1 or 2 after 4 or 5 in the
same run of the SMPjob cancels option 4 or 5. Selecting 4 or 5 after 1 or
2 cancels option 1 or 2. However, options 4 and 5 are cumulative, so you
can enter both of these two options (4 or 5) in the same run without
canceling the other.
• If you want to install an SMC, proceed to step 1.
• If you. want to perform additional supervisor regenerations or additional
ICAM regenerations, proceed to step 2.
• If you want to erase files created during SMC installation, proceed to step 3.
• If you want to perform one of the special processing operations, proceed to
step 4.
1 . You can install an SMC in normal mode and accept the default processing
options, or you can suppress the defaults and install an SMC with options
you select. Refer to 5.2 if you do not understand the options offered by the
SMC program.
• To install an SMC in normal mode, key in 1 and press XMIT. The SMC
program:
- Installs the SMC to the system
- Regenerates the supervisor you loaded to install the SMC and the
basic supervisor (if the two are not the same) when the SMC affects
- Prints an audit report of the status of all the SMCs installed to the
system
When the SMC program completes these tasks, go to step 5.
• To install an SMC without the normal defaults, key in 2 and press
XMIT.
The installation program then displays two additional processing
screens (or equivalent console messages): the supervisor regeneration
screen and the ICAM regeneration screen. These screens are shown in
5.2.1. The processing options they offer are also explained in that
paragraph. If you need help answering these screens, refer to 5.2.1 or
simply simultaneously press FUNCTION and F13 to display a help
screen.
5-24 7004 5505-000
System Maintenance
Note: The SMC program does not provide help screens to console
users.
Fill In the first processing screen (or respond to the console messages)
and press XMIT to display the second screen. Repeat the process for the
second screen, and so forth. After you. answer all the screens, the SMC
processing options menu is redisplayed. Key in 8 (or 7 if you're running
the program from the system console) and press XMIT. The SMC
program then:
- Installs the SMC
- Performs the regenerations that you specified
- Prints an audit report of the status of all the SMCs Installed to the
system
When the SMC program completes these tasks, go to step 5.
2. To perform additional regenerations, proceed as follows:
• To perform supervisor regenerations, key in 4 and press XMIT to
display the supervisor regeneration screen (or equivalent console
messages). Enter the supervisor elements you want to regenerate and
press XMIT. The SMC program then redisplays the processing options
menu. Key in 8 (or 7 if you're running the program from the system
console), press XMIT, and go to step 5.
• To perform 1CAM regenerations, key In 5 and press XMIT to display the
ICAM regeneration screen (or equivalent console messages). Enter the
ICAM elements you want to regenerate and press XMIT. The SMC
program redisplays the processing options menu. Key in 8 (or 7 If you're
running the program from the system console), press XMIT, and go to
step 5.
3. After you install an SMC, you can direct the SMC program to erase the
SMCFILE and all backout files. Key in 6 and press XMIT. The program
erases each of these files and updates the $Y$SMCLOG to indicate that
backout files no longer exist for any SMCs. The program then displays a
message that the SMC job terminated normally.
4. To perform one of the special processing options, key In 3 and press XMIT.
The SMC program then displays this screen (Figure 5-9).
7004 5505-000 5-25
System Maintenance
SMC APPLICATION SCREEN 2 - SPECIAL PROCESSING
...
(1) EXCEPTION (2) SELECTED (3) EXCLUDE (4) BACKOUT
ENTER THE NUMBER OF THE TYPE OF PROCESSING TO BE
PERFORMED. 1
ENTER THE NUMBERS OF THE SMCs TO BE PROCESSED".
XXXXXXX XXXXXXX XXXXXXX XXXXXXX
XXXXXXX XXXXXXX
XXXXXXX XXXXXXX XXXXXXX XXXXXXX
XXXXXXX XXXXXXX
XXXXXXX XXXXXXX XXXXXXX XXXXXXX
XXXXXXX XXXXXXX
PRESS FUNCTION-F1 TO CANCEL SCREEN AND RETURN TO
THE MASTER MENU.
PRESS FUNCT10N-F2 TO CANCEL JOB.
PRESS FUNCTION-F13 FOR HELP INFORMATION.
Figure 5-9. SMC Special Processing Screen
Note: The following messages are displayed to the console user:
• Primary request:
SMPQ20 SPECIAL PROCESSING OPTIONS ARE:
SMPQ21 (1) EXCEPTION (2) SELECTED (3) EXCLUDE (4) BACKOUT
SMPQ22 ENTER NUMBER OF THE TYPE OF PROCESSING TO BE DOME
SMPQ70 C: CANCEL JOB, OR M; RETURN TO MENU. DEFAULT :1
• Secondary request (displayed after you respond to the primary
request by selecting one of the special processing options):
SMPQ23 <n> ENTER UP TO 6 SMC NUMBERS, E: END OF INPUT,
SMPQ78 C: CANCEL JOB, OR M: RETURN TO MENU. DEFAULT:!
Messages SMPQ23 and SMPQ70 are repeated up to three times (as
indicated by n), provided that six valid SMC numbers are entered
for the current query, E is entered for query SMPQ70 if no more
entries are desired.
Select one of the four operations offered on this screen. The response and
criteria for each selection follow:
5-26
7004 5505-000
System Maintenance
• To install exception SMCs, key in 1. The SMC job then displays the
following message: ENTER UP TO 6 SMC NUMBERS, E:END OF
INPUT,C:CANCEL JOB, or M:RETURN TO MENU? Respond to this
message by keying in the numbers of the exception SMCs to be installed
and press XMIT. If you key in less than six, the SMC job redisplays the
SMC processing options menu. If you have more than six, the message
is redisplayed up to three times for you to enter more. When you have
no more exception SMC numbers to enter, respond M so the SMC job
returns you to the SMC processing options menu. On the SMC
processing options menu, key in 8 (or 7 if you're running the program
from the system console), press XMIT, and proceed to step 5. (Exception
SMCs apply only to certain types of users. Do not apply them unless
directed to do so by the Unisys representative.)
• To select a subset of the SMCs in the SMCFILE, key in 2 and enter the
numbers of the SMCs to be processed on the lines provided. Then, press
XMIT to redisplay the SMC processing options menu. Key in 8 (or 7 if
you're running the program from the system console), press XMIT, and
proceed to step 5.
• To exclude the installation of certain SMCs in the SMCFILE, key in 3
and enter the numbers of the SMCs to be excluded. Then, press XMIT to
redisplay the SMC processing options menu. Key in 8 (or 7 if you're
running the program from the system console), press XMIT, and
proceed to step 5.
• To back out bad SMCs, key in 4 and enter the numbers of the SMCs to
be backed out. Then, press XMIT to redisplay the processing options
menu. Key in 8 (or 7 if you're running the program from the system
console), press XMIT, and proceed to step 5.
5. After you install an SMC or perform additional tasks, the SMC program displays
messages to tell you:
• Whether the SMC was installed successfully
• That the SMC job is issuing a command to execute SMCLIST
• That the SMC job terminated normally
The SMC job leaves job slot 1 and SMCLIST takes its place. SMCLIST then
provides a condensed printout of the contents of $Y$SMCLOG, which is a record
of all the SMGs installed in the system. If you specify the FMT=F option on the
SMC execution command, a full listing is printed. This listing provides such
additional information as whether an SMC was required or optional. When
SMCLIST successfully prints this list, a message informs you that SMCLIST
terminated normally. The SMC installation process is now complete.
7004 5505-000 5-27
System Maintenance
5,5. Sample SMC Printouts
Figures 5-10 and 5-11 show sample printouts of SMCs in the correct change format.
The SMC sample shown in Figure 5-10 results from input entered Yia the console
using the SMC console dialog. The SMC sample shown in Figure 5-11 results from
input entered via a workstation using the Interactive SMC Entry screens. The shaded
areas in both samples identify those fields that you were asked to fill in (provide input
for) either by queries from the console dialog or by the blank fields in the interactive
screens.
5-28 7004 5505-000
System Maintenance
// JOB €120357, ,7000, 14000
// DVC 20 // LFD PRNTR
N0P i ********************
// OPTION SMC
//
// NOP "CORRECTION IS FOR HIS -DUMP FACILITY SYSDUMP- JOBDUMP
// NOP 'IT WAS SUBMITTED ON 872988 AND IS REQUIRED §81088
// NOP 'IT APPLIES TO RELEASE llBll THRU 129999
// NOP "IT IS TESTED AND IS NOT FIELD VERIFIED Sl'-l
// MOP "THE SUR ORIGINATED IN TEST
// NOP « CORRECT I ON HAS BEEN APPLIED TO RELEASE 12.8-S2.4
// NOP 'IT IS INCLUDED IN
// NOP 'COMPONENT SOURCE IS CORRECTED IN RELEASE 13.8.8
// NOP 'CONTINGENCY: SYSTEM=1, REGEN=NNNNNNNN
// NOP « •
// NOP 'FIXES PLES: 14805382, 14005579
// NOP "REQUIRES COR: H
// NOP "REPLACES COR: XXXX, XXXX, XXXX, XXXX, XXXX
// NOP "IS REQUIRED BY CORS: XXXX, XXXX, XXXX, XXXX, XXXX
// NOP «IS REPLACED BY CORS: XXXX , XXXX , XXXX , XXXX , XXXX
// NOP •CORRECTION REQUIRES WITH VSN MODULES=N
// NOP l (FILEID= )
// NOP "CORRECTION DESCRIPTION:
// NOP "SYSDUMPO OPTION RESTORE RESULTS
IN ERROR CODE DH56 WHEN TAPE
IS USED
ECN=C1 11335
MODULES CORRECTED:
SYSDMP80
CORRECTION CARD COUNT: 848
// NOP
// NOP
// NOP
// NOP
// NOP
// NOP
// NOP i ***********************
// DVC 20 // LFD PfflTR
// EXEC LIBS
/%
FIL D1=$Y$4QD '
POG C$SYSTEM,D1
COS Dl,L,SYSDMP,,8/0'
-860E,84,9W4BB88
»8612,84,47E0C1C8
-8616,04,D719801E801E
-861C # 04,9101BB88
^8628,M „47Eicl9C
- 8624 , 84 , %7M%immm7m
EOD
EOG €$SYSTEM,D1
/*
/&
// FIN
Figure 5-10. Sample SMC - Required Fields for SMC Console Dialog
7004 5505-000
5-29
System Maintenance
// JOB ISiHl, ,7000, 14000
// DVC 28 // LFD PRNTR
// MOP
// NOP
// NOP
// NOP
// NOP
// NOP
// NOP
// NOP
// NOP
// NOP
// NOP
// NOP
// NOP
// OPTION SMC
CORRECTION IS FOR HI! -DUMP FACILITY SYSDUMP- JOBDUMP
IT WAS SUBMITTED ON 872988 AND IS REQUIRED 881888
IT APPLIES TO RELEASE Hill THRU 111119
IT IS TESTED AND IS MOT FIELD VERIFIED
THE SUR ORIGINATED IN TEST
CORRECTION HAS BEEN APPLIED TO RELEASE 12.8.S2.4
IT IS INCLUDED IN
COMPONENT SOURCE IS CORRECTED IN RELEASE 13.8.0
CONTINGENCY: SYSTEM=#, REGEN=
FIXES PLES: 14005382, 14005579
REQUIRES COR: 0175
// NOP REPLACES COR: XXXX, XXXX, XXXX, XXXX, XXXX
// NOP IS REQUIRED BY CORS: XXXX, XXXX, XXXX, XXXX, XXXX
IS REPLACED BY CORS: XXXX , XXXX , XXXX , XXXX , XXXX
CORRECTION REQUIRES WITH VSN MODULES=N
(FILEID= )
CORRECT I OM DESCRIPTION:
'IN ERROR CODE DM56 WHEN TAPE
'IS USED
ECN=C1 11335
MODULES CORRECTED:
IfsiPii
CORRECTION CARD COUNT: 11
// NOP
// NOP
// NOP
// MOP
// MOP
// NOP
// NOP
// NOP
// MOP
// NOP
// NOP
// MOP ************************
// DVC W 11 LFD FWTR
// EXEC UBS
/$
FIL D1=*Y*L0P
EGG C$SYSTEH,D1
COS Dl,L,SYSDMP„8/a
-860E,d4,9M4BB88
-8612,04,47E0C1C8
-8616,44,D7198eiE80lE
-861C,04,9ttlBB88
-862a,04,47E0Ct9C
- 8624 , 84 , mmwmmmjm
EOp
EOG C$SYSTEM,D1
/*
/&
// FIN
The actual SMC change lines
Figure 5-11. Sample SMC - Required Fields for interacts SMC Entry from Workstation
5-30
7004 5505-000
Appendix
Performance Tuning
Your system should be tuned to allow operating system software to have necessary
control and resources to process online, interactive, and batch jobs at maximum
efficiency. Tuning is accomplished by adjusting functional priority levels, memory
management operations., and other critical SUPGEN parameters to optimal values.
This appendix defines recommended SUPGEN parameter settings that should provide
close to optimal performance in most operating environments. These settings were
verified using the system activity monitor (SAM) under varied user applications and
environments.
In addition to the settings defined below, the supervisor must be generated with the
SAM=Y parameter.
A.l. SUPGEN Priority Values
SUPGEN priority parameters can be set to the following values:
N&te; Hn 'foot prioniy is and lowest p; ioriiy is 60
SYMBIONT=PD,0
SYMBIONT=PR,0
SYMBIONT=PU,0
SYMBIONT=RP,0
SYMBIONT=SU,7
SYMB10NT=TU,7
SYMBPRI=5
1SINTPRI=6 (must have a priority lower than SYMBPRI)
''...&: "'- H<
PRIORITY=20
User job priority is defined by the EXECPRI parameter if a priority level is not
defined by a job control statement or the SWITCH command. Note that all user jobs
should run at priority levels lower than 6 (i.e., 7 through 60). The following user job
priority guidelines should be followed:
• High CPU usage jobs should be run at priorities 16 through 20.
• Low CPU usage jobs should be run at priorities 10 through 14.
7004 5505-000 A-l
Performance Tuning
The highest allowable priority for a high CPU usage job is 9.
The highest allowable priority for a low CPU usage job is 7.
The normal priority for most user jobs should be 15.
Priorities 1, 2, 3, and 4 are reserved for TPS, TIP/30 3 IMS, and GUST jobs.
Priority 8 is reserved for DBMS jobs.
A.2. SUPGEN Memory Management ¥alues
SUPGEN memory management parameters can be set to the following values:
EXPREGION=12288
RESBUFSIZE=500
IMVJOB=YES
MEMCON=YES
ROLLQUT=YES
TRNWKAREA=64
A.3. SUPGEN Data Management ¥alues
The SUPGEN DMRECV parameters should normally be set for indexed data files only
(DMRECV=INDEX). See the Consolidated Data Management Programming Guide,
UP-9978, for details in the recovery option.
A.4. SUPGEN Spooling Values
SUPGEN spooling parameters can be set to the following values:
SPOQLBUFR=4
SPOOLVSN=vsn of a disk other than SYSRES (should be least
used disk in system)
A.5. SUPGEN Resident Shared Load Module Values
Specify the following resident shared load modules with the SUPGEN RESHARE
parameter:
RESHARE=DM$CFM,DM$W1 1 1 ,D3$M1 1 1 3 PR$IOE
In addition, if the OS/3 general editor and screen format services are used heavily,
add:
RESHARE=EDT,ISF,SF
A-2 7004 5505-000
Performance Tuning
If the ESCORT compiler Is used, add:
RESHARE=ESC
You can use the MI SC and Ml MM commands to determine additional modules that
should be specified (see the Operations Guide, 7004 5208, for information on these
commands). Enter these commands every 10 to 15 minutes while your system Is
running at peak work loads, with heavy online applications , or with heavy batch
processing. At the completion of the processing period, breakpoint the console log and
then examine the printout to determine modules that are continually being loaded
into dynamic memory. Include these modules in the SUPGEN RESHAKE parameter
statement.
A.6. 1/OGEN Considerations
Define I/O devices in the following order:
1. All disk units
2. All tape units
3. All laser printers
4. All line printers
5. Local terminals and printers
6. Remote terminals and printers
Within each of the six categories, define units in the order of their usage. For instance,
define the most commonly used disk (typically SYSRES) first and the least commonly
used disk last within the first category.
A.7. Determining Disk Cache Size
The optimum size of disk cache can only be determined after the preceding SUPGEN
tuning is performed. The amount of main memory used for disk cache depends on the
available free memory In the system. Use a disk cache size that allows a minimum of
160K bytes of available free memory after all interactive and batch jobs are loaded
and running. To determine the amount of free memory available, use the MI MM
command (see the Operations Guide, 7004 5208, for information on this command).
7004 55054)00 A~3
Performance Tuning
The optimum disk cache size is that which provides the highest search and read hit
rates while the system is running with heavy disk activity. The optimum size can be
determined as follows:
1 . Specify a disk cache size. This can be done following system IPL or with the
CM SIZ command (see the Operations Guide, 7004 5208, for more information on
this command).
2. Initiate system activity with heavy disk activity.
3. While the system is running, enter the OOACMASTA command (see the
Operations Guide, 7004 5208) to determine the current read and search hit rates.
Record the current cache size and the two hit rates.
4. Repeat steps 1 through 3 using a wide range of cache sizes. The optimum cache
size is the one where the highest hit rates were found.
A4 7004 5505-000
Index
B
ACCTNO subparameter, SUPGEN, 4-29
ADDR keyword parameter, I/OGEN
DISC, 4-40
DISKETTE, 4-42
PUNCH, 4-39
PRINTER, 4-35,4-36
READER, 4-37
TAPE, 4-43
WORKSTATION, 4-45
ALTCON keyword parameter, I/QGEN,
4-46
Alternate line printer characteristics, 3-32
to 3-37
Alternate method to SYSGEN dialog,
Section 4
ALTJCS keyword parameter, SUPGEN,
4-11
ALTSTACK keyword parameter, I/QGEN,
4-38
AMOUNT keyword parameter, I/OGEN
REMPRINTER, 4-48
REMWORKSTATION, 4-47
ATTNRE keyword parameter, I/OGEN
PRINTER, 4-36
PUNCH, 4-39
READER, 4-38
Audit file capability, SYSGEN dialog
procedure, 3-21
AUTOLOAD keyword parameter, I/OGEN,
4-43
Automatic execution of parameter
processor, 3-20 to 3-26
Automatic supervisor loading, 3-32
AUX keyword parameter, I/OGEN, 4-47
AXNON keyword parameter, COBGEN,
4-59
AXREF keyword parameter, COBGEN,
4-59
Backout files, system maintenance
packages, 5-5
Backup of SYSRES
disk-DCOP, 3-40 to 3-42
disk - SETREL/COPYREL, 3-42 to 3-47
diskette, 3-47 to 3-51
making and restoring, 3-39 to 3-52
restoring SYSRES from tape, 3-51, 3-52
SU@RST, 3-52
tape, 3-51,3-52
Bit map calculation table, spool-file, 4-63
BLKSIZE keyword parameter, NTRGEN
LOCAL, 4-57
BLOCKIN keyword parameter, NTRGEN
NTR, 4-55
BLOCKOUT keyword parameter,
NTRGEN NTR, 4-56
BPOOLEXP keyword parameter,
COMMCT, 4-54
Build guidelines, SYSRES, 2-4
Bulletin, system, 3-38, 3-39
CACH keyword parameter, COMMCT,
4-49
CACH parameter, identifies SLCA, 4-4
CACHE keyword parameter, I/OGEN, 4-40
CACHESEGSIZE keyword parameter,
SUPGEN, 442
CALLST keyword parameter, COBGEN,
4-59
CANCEL auditing option, 3-27
CARTNAME subparameter, SUPGEN,
4-29
7004 5505-000
lndex-1
Index
CCA macroinstraction, start network
definition, 4-3
GCAMOD, COMMCT parameter, 4-49
CCAMOD parameter, specifying source
module, 4-3
CHAN keyword parameter, I/OGEN
DISC, 4-40
DISKETTE, 4-42
PRINTER, 4-34
PUNCH, 4-38
READER, 4-37
TAPE, 4-43
WORKSTATION, 4-45
CHAN keyword parameter, SUPGEN, 4-20
CHAN1 keyword parameter, SUPGEN,
4-20
Changing system bulletin, 3-38, 3-39
Character mismatch, 3-34
CHARSET keyword parameter, I/OGEN,
4-35
CLASS keyword parameter, I/OGEN, 4-35
CMCSST keyword parameter, COBGEN,
4-59
COADDR keyword parameter, I/OGEN
DISC, 4-41
TAPE, 4-45
COBGEN phase
COBOL element, 3-9
formats, 4-5, 4-59
preparing SYSGEN parameter sets,
3-14
specifying without SYSGEN dialog, 4-5
COBOL compiler, configured using
SYSGEN, 1-2
COCHAN keyword parameter, I/OGEN
DISC, 4-41
TAPE, 4-44
COMM keyword parameter, SUPGEN,
4-20
COMMCT phase
format, 4-49
preparing SYSGEN parameter sets,
3-14
specifying without SYSGEN dialog, 4-3
COMM1 keyword parameter, SUPGEN,
4-20
Communications control area (CCA), 3-9
Communications (ICAM) elements, 3-9
COMP keyword parameter, COBGEN, 4-59
COMPRESS keyword parameter, NTRGEN
LOCAL, 4-57
CONALARM keyword parameter,
SUPGEN, 4-12
CONPRINT keyword parameter, SUPGEN,
4-25
Console alarm, 4-12
Console mode, manual execution of
parameter processor, 3-27
CONSOLOG keyword parameter,
SUPGEN, 4-25
Control element generations for optional
software, Table 3-1 3-2
UOP-YEEL
backup SYSRES, 3-42
copy order, Table 3-6 3-46
CPU microcode, 2-18
CPYTXT keyword parameter, COBGEN,
4-59
DAYCHANGE keyword parameter,
SUPGEN, 442
DBUS microcode, 248
DCOP job stream, backup SYSRES, 3-40 to
3-42
DCPCHNL keyword parameter, SUPGEN,
4-20
DDP spooling, 4-24
DDPSC keyword parameter, SUPGEN,
4^21
DDPSPOOL keyword parameter,
SUPGEN, 4-25
Default bulletin, changing system bulletin,
3-38, 3-39
Defining alternate printer characteristics,
3-32 to 3-37
DELETE auditing option, 3-25
DENSITY keyword parameter, I/OGEN,
4-44
DESPACE keyword parameter, I/OGEN,
4-46
Device function codes, 4-70,
Table 4-13 4-71
DEVICE keyword parameter, NTRGEN
LOCAL, 4-57
DEVICE subparameter, SUPGEN, 4-29
lndex-2
7004 5505-000
Index
DIAG keyword parameter, COBGEN, 4-59
DIAGWN keyword parameter, COBGEN,
4-5S
DLOADBUFR keyword parameter,
SUPGEN, 4-6
DLOADTABLE keyword parameter,
SUPGEN, 4-6
DOWN keyword parameter, I/QGEN
DISC, 4-42
TAPE, 4-45
DMGTMODE keyword parameter,
SUPGEN, 4-13
DMRECV keyword parameter, SUPGEN,
4-13
DUALTRAN keyword parameter, I/OGEN,
4-38
Dump-restore, tape, 1-5
DUMPVSN keyword parameter, SUPGEN,
4-14
DVCNO keyword parameter, I/OGEN
DISC, 4-40
DISKETTE, 4-43
PRINTER, 4-35
PUNCH, 4-39
READER, 4-37
TAPE, 4-43
WORKSTATION, 4-46
DVCNO keyword parameter, logical unit
number change, 4-64, Table 4-8 4-64
EDIT auditing option, 3-23, 3-25
ENDCCA macroinstmction, network
definition, 4-3
ENDSESSION auditing option, 3-23
EOF keyword parameter, I/OGEN, 4-38
ERRLOGBUF keyword parameter,
SUPGEN, 4-6
EXECPRI keyword parameter, SUPGEN,
4-6
EXPBFCTSZ keyword parameter,
SUPGEN, 4-7
EXPREGION keyword parameter,
SUPGEN, 4-7
FASTLOAD keyword parameter,
COMMCT, 4-54
FEED keyword parameter, I/OGEN, 4-37
FILE subparameter, SUPGEN, 4-29
FILELOCK keyword parameter, SUPGEN,
4-14
FIPS keyword parameter, COBGEN, 4-59
FLOATPT keyword parameter, SUPGEN,
4-21
FORM subparameter, SUPGEN, 4-29
FUNCD keyword parameter, NTRGEN
LOCAL, 4-57
General editor
alternate printer characteristics, 3-33
changing system bulletin, 3-38
modify parameter sets, 3-20
SYSGEN parameter sets, 3-28
Generating control elements, 1-2, 3-1
Generating IMS online load module, 3-32
H
HELP screen
preparing SYSGEN parameter sets,
3-18
SYSGEN dialog, 1-7
i
ICAM element
COMMCT phase, 3-17
stored on SYSRES volume, 3-30
IC$BLD, 1-9
IC$INPUT, 3-19,4-1
IDCU microcode diskette, creating, 2-34
IGNJCERR keyword parameter, SUPGEN,
4-15
IGNORESFT keyword parameter,
SUPGEN, 4-15
IMPLDSKT, 2-34
7004 5505-000
Index-3
Index
IMSCOD keyword parameter, COBGEN,
4-59
IMVJOB keyword parameter, SUPGEN,
4-15
IN keyword parameter, COBGEN, 4-60
Initial microprogram load (IMPL)
code diskette, 1-4, 2-6, 2-30
creating IMPL diskette, 2-33
inserting via PRPMIC, 2-15
Initial program load (IPL)
diskette, 2-6
inserting via PRPMIC, 2-15
procedure, 2-6, 2-30
INSERT
auditing option, 3-24
statement, 3-44
Installation procedures. See software
installation.
Installation programs
SMC 5-3, 5-13
SMP 5-2, 5-7
Installing a new release of OS/3
description, 2-3
illustration, Fig. 2-4 2-5
Installing optional OS/3 components, 2-2,
Installing optional release software from
diskette, 2-12,2-13
Installing release software from
dump/restore tape, 2-13
Installing standard release software from
diskettes, 2-6 to 2-12
INTMEM keyword parameter, SUPGEN,
4-33
IOMP microcode, 2-33
I/OGEN phase
format, 4-34 to 4-48
generating supervisor control element,
3-17
nine-track recording mode settings,
4-66, Table 4-9 4-66
seven-track recording mode settings,
4-66, Table 4-10 4-67
specifying without SYSGEN dialog, 4-2
I/OMOD keyword parameter, I/OGEN,
4-34
IORB keyword parameter, SUPGEN, 4-21
IORB1 keyword parameter, SUPGEN, 4-21
ISADMID keyword parameter, SUPGEN,
4-22
ISBATCHLMT keyword parameter,
SUPGEN, 4-22
ISINTLMT keyword parameter, SUPGEN,
4-22
ISINTPRI keyword parameter, SUPGEN,
4-22
ISLOGONSC keyword parameter,
SUPGEN, 4-22
ISWKSBUL keyword parameter, SUPGEN,
4-23
ISWKSLOG keyword parameter, SUPGEN,
4-23
ISWORK keyword parameter, SUPGEN,
4-23
ITCU microcode, 2-9
JCREADWKS keyword parameter,
SUPGEN, 4-15
Job control streams, SYSGEN, 1-9
JOB subparameter, SUPGEN, 4-30
JOBACCT keyword parameter, SUPGEN,
4-25
JOBMEM keyword parameter, SUPGEN,
4-33
JOBQUEREC keyword parameter,
SUPGEN, 4-16
JOBSLOTS keyword parameter, SUPGEN,
4-8
K
KATACON keyword parameter, I/OGEN,
4-48
KATAKANA keyword parameter, I/OGEN
REMWORKSTATION, 4-48
WORKSTATION, 4-46
LCB (load code buffers), 3-33
LCB keyword parameter, I/OGEN, 4-36
LFD keyword parameter, NTRGEN
LOCAL, 4-58
Librarians, system, 2-4
LIN keyword parameter, COBGEN, 4-60
Index4
7004 5505-000
Index
LINE keyword parameter, NTRGEN NTR,
4-56
Line speed values, 4-68, Table 4-11 4-68
LINESP keyword parameter, NTRGEN
NTR, 4-56
LIST keyword parameter, COBGEN, 4-60
LNKCON keyword parameter, COBGEN,
4-60
LOCAL parameters
keywords, 4-57
NTR element, 3-8
NTRGEN parameter, 4-5
Logging on to workstation, 3-14
Logical unit numbers, 4-64, Table 4-8 4-64
LOGON request screen, OS/3, 3-14
LOOP keyword parameter, I/OGEN, 4-47
LSTREF keyword parameter, COBGEN,
4-60
LSTWTH keyword parameter, COBGEN,
4-60
Message control program (MCP)
communications elements, 3-9
defining COMMCT section, 4-3
MIRAMCHAR keyword parameter,
SUPGEN, 4-16
Microcode, adding microcode names to
DBUS, 2-18
IOMP, 2-33
rrcu, 2-9
$Y$SDF, 3-32
MODE keyword parameter, I/OGEN
READER, 4-38
TAPE, 4-44
MXNON keyword parameter, COBGEN,
4-60
MXREF keyword parameter, COBGEN,
4-60
N
1
Making and restoring backup copy of
current SYSRES, 3-39 to 3-52
Manual execution of parameter processor,
3-26 to 3-28
MAP keyword parameter, COBGEN, 4-60
MAXJOBS keyword parameter, SUPGEN,
4-33
MAXRUNSYMBS keyword parameter,
SUPGEN, 4-33
MAXSWSJOBS keyword parameter,
SUPGEN, 4-33
MAXTIME keyword parameter, SUPGEN,
4-16
MAXTYPE keyword parameter, SUPGEN,
4-16
MAXWSJOBS keyword parameter,
SUPGEN, 4-33
MCP keyword parameter, COMMCT, 4-49
MCPNAME keyword parameter,
COMMCT, 4-49
MCPVOL keyword parameter, COMMCT,
4-49
MEMCON keyword parameter, SUPGEN,
4-16
NET keyword parameter, NTRGEN NTR,
4-56
Network definition parameters
communications elements, 3-9
defining COMMCT section, 4-3
Nine thousand remote (NTR) element
description, 3-8, 3-9
format, 4-55
job control stream, 3-31
NTRGEN phase, 4-5
stored on SYSRES, 4-5
NPRTSP keyword parameter, NTRGEN
NTR, 4-57
NTRGEN phase
■A>] rs;;ri. } -i S5
preparing SYSGEN parameter sets,
3-16
specifying without SYSGEN dialog, 4-5
NTRMOD keyword, NTRGEN phase, 4-5
NTRMOD keyword parameter, NTRGEN
NTR, 4-55
NTRNAME keyword parameter, NTRGEN
NTR, 4-55
NTRVOL keyword parameter, NTRGEN
NTR, 4-55
7004 5505-000
lndex-5
Index
OBJ keyword parameter, COBGEN, 4-60
OBJLST keyword parameter, COBGEN,
4-60
OBJMOD keyword parameter, COBGEN,
4-60
Optional software installation procedure,
2-12, 2-13
OS/3 optional software, 1-6, 2-12, 2-13
PAGOW keyword parameter, COBGEN,
4-60
Parameter processor
automatic execution, 3-20 to 3-26
manual execution, 3-26 to 3-28
output listing, 3-20, 3-28
saved modules, 3-2
SYSGEN, 1-9
Parameter sets, SYSGEN, running job
control streams, 3-29
PASSWORD keyword parameter,
SUPGEN, 4-23
Password, user, 4-23
Performance tuning, A-l
Performing system generation, system
control elements, 2-35
Post-software installation procedures, 2-17
to 2-35
Post-SYSGEN procedures, 3-32 to 3-52
Printer characteristics, 2-1, 3-2, 3-32
Printer formats, vertical, 3-32
PRINTPOS keyword parameter, I/OGEN,
4-36
PRIORITY keyword parameter, SUPGEN,
4-8
PROCEED auditing option, 3-23, 3-26
Processing SYSGEN parameter sets, 3-19
to 3-28
PROVER keyword parameter, COBGEN,
4-61
PRPMIC, 2-15
PRTSP keyword parameter, NTRGEN
NTR, 4-57
READ keyword parameter, I/OGEN, 4-39
READONLY keyword parameter, I/OGEN,
4-41
RECOVERDS keyword parameter,
SUPGEN, 4-17
REEDIT auditing option, 3-26
Recording mode settings
nine-track, 4-66, Table 4-9 4-66
seven-track, 4-66, Table 4-10 4-67
Remote device handler, LOCAL parameters
3-8, 3-9
REMOTE keyword parameter, 1/OGEN,
4-36
RESBFCTSZ keyword parameter,
SUPGEN, 4-8
RESBUFSIZE keyword parameter,
SUPGEN, 4-9
RESHARE keyword parameter, SUPGEN,
4-17
RESMGT keyword parameter, SUPGEN,
4-32
Resource management, 3-10, 4-32
Restart ability, SU@RST, 2-11, 2-12
Restoring backup system files from
diskettes, 3-47 to 3-51
Restoring modules saved from a previous
release, 2-34
Restoring SYSRES from diskettes, 3-47 to
3-51
Retaining existing software, 2-3
RETAINLOG keyword parameter,
SUPGEN, 4-26
ROLLOUT keyword parameter, SUPGEN,
4-17
RUNVSN keyword parameter, SUPGEN,
4-18
S parameter, source module name, 3-28
SAM keyword parameter, SUPGEN, 4-18
SCDINDEX keyword parameter, SUPGEN,
4-18
SCRATCHDVC keyword parameter,
SUPGEN, 4-18
lndex-6
7004 5505-000
Index
SCRENMEM keyword parameter, I/OGEN
REMWORKSTATION, 4-48
WORKSTATION, 4-46
SDU (system definition utility)
adding a device, 2-23 to 2-25
deleting a device, 2-26
description, 2-18
updating device info, 2-26, 2-27
SELACC keyword parameter, I/OGEN,
4-42
SETREL, propping removable disk to serve
as backup SYSRES, 3-42
SG$BLD job control stream, 1-9
SG$COBMKjob control stream, 140
SG$COMMKjob control stream, 1-10
SG@DMFIL routine, dump user files to
diskettes, 3-48
SG$DMPDTjob control stream, 3-51
SG$DMPTD job control stream, 2-13, 2-14
SGSDSFIL, building backup SYSRES,
3-49
SG@DUFIL job stream
building backup SYSRES, 3-48
installing new OS/3 release, 2-3
SG$INPUT module, storing parameter sets,
3-19
SG@MVPD, mount message, 2-13
SG$NTRMK job control stream
NTR system utility module, 1-10
NTRGEN phase, 4-5
running, 3-31
SG$PARAM job control stream, 1-9
SG$PRB job control stream, 1-10, 3-33
SG@RUFIL job stream
restoring modules saved from a previous
release, 2-34
restoring SYSRES, 3-50
SG$SUPMKjob control stream, 1-10
SHAREDMGT keyword parameter,
SUPGEN, 4-10
Shared load module groups, 4-63, Table 4-7
4-63
SIGNFX keyword parameter, COBGEN,
4-61
Single line communications adapter
(SLCA), COMMCT procedure, 4-3
SITE keyword parameter, NTRGEN NTR,
4-56
SMC (See System maintenance change.)
SMCLIST, 5-5
SMP (See System maintenance package.)
Software installation
considerations, 2-1
defined, 1-1
delivered, 1-3
existing users, 2-2, 2-3
facilities, 1-5, 1-6
initial users, 2-1
optional, 1-6
post-installation procedures, 2-17 to
2-35
stand-alone routines, 1-5
Space compression characters, 4-69,
Table 4-12 4-69
SPOOLBUFR keyword parameter,
SUPGEN, 4-26
SPOOLBURST keyword parameter,
SUPGEN, 4-26
SPOOLCOMP keyword parameter,
SUPGEN, 4-26
SPOOLCYL keyword parameter, SUPGEN,
4-26
SPOOLFARSI keyword parameter,
SUPGEN, 4-27
Spool-file bit map calculation table 4-62,
Table 4-6 4-63
SPOOLHDR keyword parameter,
SUPGEN, 4-27
SPOOL1CAM keyword parameter,
SUPGEN, 4-28
SPOOLING keyword parameter, SUPGEN,
4-24
SPOOLMAP keyword parameter,
SUPGEN, 4-28
SPOOLMAXLINE keyword parameter,
SUPGEN, 4-28
SPOOLMAXREC keyword parameter,
SUPGEN, 4-28
SPOOLMODE keyword parameter,
SUPGEN, 4-28
SPOOLNOINPUT keyword parameter,
J'.H.JPGEN, 4 to
SPOOLOWBUFR keyword parameter,
SUPGEN, 4-30
SPOOLPRT keyword parameter, SUPGEN,
4-30
SPOOLRECV keyword parameter,
SUPGEN, 4-31
7004 5505-000
lndex-7
Index
SPOOLTEST keyword parameter,
SUPGEN, 4-31
SPOOLTPBUFR keyword parameter,
SUPGEN, 4-31
SPOOLUPDATE keyword parameter,
SUPGEN, 4=31
SPOOLVSN keyword parameter, SUPGEN,
4-31
SPOOLVSNn keyword parameter,
SUPGEN, 4-32
SPRLST keyword parameter, COBGEN,
4-61
SPROUT keyword parameter, COBGEN,
4-61
Stand-alone installation, diskette, 1-6
Stand-alone prep routine
preparing disk, 1-5
SU@PRP 2-7, 2-8
Stand-alone restore routine
copying standard control software, 1-5
SU@RST, 2-7 to 2-12
Statement conventions, vii to ix
SUBCK keyword parameter, COBGEN,
4-61
Supervisor
customized, 1-2
elements, 3-4 to 3-8
minimum, SY#BAS, 3-6
minimum, SY$BAS, 3-7
starter, 3-5
stored on SYSRES volume, 3-29
SUPGEN phase
creating parameter sets, 4-2
keyword parameters, 4-6 to 4-33
SUPMOD keyword parameter, SUPGEN,
4-2, 4-6
SUPVRNAM keyword parameter,
SUPGEN, 4-6
SU@PRP prep routine, 2-7, 2-8
SU@RST restore routine, 2-9 to 2-12
SY#BAS
description, 1-2
preparing SYSGEN parameter sets,
3-14
starter supervisors, 3-5
supervisor features, 3-6
SY$BAS
description, 1-2
preparing SYSGEN parameter sets,
3-14
starter supervisors, 3-5
supervisor features, 3-7
SYMBIONT keyword parameter, SUPGEN,
4-10
SYMBMEM keyword parameter, SUPGEN,
4-33
SYMBPRI keyword parameter, SUPGEN,
4-11
SYNCHK keyword parameter, COBGEN,
4-61
SYSGEN See system generation.
SYSGEN dialog
alternate methods, 4-1
auditing options, 3-21
description, 1-7, 1-8
help screen, 1-7
job control stream, 1-9
parameter processor, 1-9
preparing parameter sets, 3-14
system installation, 1-10
SYSGEN dialog capability, using procedure
for audit, 3-21
SYSGEN job control streams
defined, 1-9,1-10
running procedure, 3-29 to 3-31
system installation, 1-10
SYSGEN parameter processor
defined, 1-9
functions, 1-9
system installation, 1-10
values, 3-20
SYSGEN parameters, changing, 3-20
SYSLOG keyword parameter, SUPGEN,
4-32
SYSRES
building backup, 3-39
description, 1-2
System activity monitor, 4-18
System bulletin, changing, 3-38, 3-39
SYSTEMDATE keyword parameter,
SUPGEN, 4-18
lndex^8
7004 5505-000
Index
System definition file ($Y$SDF)
adding a device, 2-23 to 2-25
confirming, 2-28
copying and restoring, 2-32
deleting a device, 2-26
dumping, 2-28
restoring, 2-29
reviewing, 2-21
updating, 2-17
System definition utility (SDU)
add screen from 1MPL devices, Fig. 2-11
2-24
add screen from non-lMPL devices,
Fig. 2-10 2-24
display entry screen, Fig. 2-8 2-22
operation request screen, Fig. 2-7 2-22
terminating, 2-29
termination screen, Fig. 2-16 2-29
System generation
defined, 1-2
dialog, 1-7,3-14
job control streams, 1-9, 3-29
keyword parameters, 4-6
parameter processor, 1-9
parameter sets, 3-1, 3-14
parameter values, 3-20
performing, 1-6,2-35
purpose, 1-2
reference tables, 4-62
running job control streams, 3-29 to
3-31
system installation, 1-10
types of elements, 3-1
System installation
defined, 1-1
flowchart, Fig. 1-1 1-11
review, 1-10
verifying, 2-35
System librarians
changing system bulletin, 3-38, 3-39
LIBS and MLIB, 2-3
System microcode file ($Y$MIC), 2-18, 2-21
System maintenance (SMC, SMP), 1-3,
Section 5
System maintenance change (SMC)
backing out, 5-2
definition, 1-3, 5-1
entry screens, 5-9
installation program, 5-3, 5-12
System maintenance package (SMP)
definition, 1-3
installation program, 5-2, 5-7
System resident volume
defined, 1-2
initial users, 2-1
I/OGEN procedure, 4-2
TAPEAVR keyword parameter, SUPGEN,
4-18
TAPEBLKNO keyword parameter,
SUPGEN, 4-19
Tape mode settings
nine-track, 4-66
seven-track, 4-66
TASK keyword parameter, NTRGEN NTR,
4-56
TASKNAME keyword parameter,
NTRGEN LOCAL, 4-57
TIPCOD keyword parameter, COBGEN,
4-61
TRANS keyword parameter, NTRGEN
LOCAL, 4-58
TRANS keyword parameter, SUPGEN,
4-11
Transient work areas, 4-11
TRANSLATE keyword parameter, I/OGEN,
4-44
TRNADR keyword parameter, COBGEN,
4-61
TRNWKAREA keyword parameter,
SUPGEN, 4-19
TRUNC keyword parameter, COBGEN,
4-61
TYPE and TRANS keyword parameters
device function codes, 4-70
Table 4-13 4-71
TYPE keyword parameter, I/OGEN
AUXPRINTER, 4-47
DISC, 4-39
DISKETTE, 4-42
PRINTER, 4-34
PUNCH, 4-38
READER, 4-37
TAPE, 4-43
WORKSTATION, 4-45
TYPE keyword parameter, NTRGEN
LOCAL, 4-58
7004 5505-OOQ
lndex-9
Index
u
UNATCONS0LE keyword parameter,
SUPGEN, 4-19
Updates to optional software, 2-2
Updating system definition file, 2-17
Using another disk for the backup SYSRES,
3-40 to 3-47
Using diskettes for the backup SYSRES,
3-47 to 3-51
VIRTUAL keyword parameter, I/OGEN
PRINTER, 4-37
PUNCH, 4-39
READER, 4-38
Volume table of contents (VTOC)
automatic verification (VVAVR), 4-19
restoring SYSRES, 3-52
WAVR keyword parameter, SUPGEN,
4-19
w
VALIDITY keyword parameter, I/OGEN,
4-38
Verifying system installation procedure,
2-35
VFB keyword parameter, 1/OGEN
AUXPRINTER, 4-47
PRINTER, 4-36
VFBDEN keyword parameter, NTRGEN
LOCAL, 4-58
VFBFORM keyword parameter, NTRGEN
LOCAL, 4-58
VFBLEN keyword parameter, NTRGEN
LOCAL, 4-58
VFHOME keyword parameter, NTRGEN
LOCAL, 4-58
Workstation mode, preparing SYSGEN
parameter sets, 3-14
Symbols
$Y$SMCLOG, 5-4
$Y$MIC, 2-18, 2-21
$Y$SDF
adding a device, 2-23 to 2-25
confirming, 2-28
copying and restoring, 2-32
deleting a device, 2-26
dumping, 2-28
restoring, 2-29
reviewing, 2-21
updating, 2-17
$Y$TRANA, 3-45
lndex-10
7004 5505-000
