Water System User Manual

ManualsBrandsStorageTek ManualsWater SystemHost Software Component 6

Host Software Component

(VM Implementation)

System Programmer’s Guide

Release 6.0

312579601

Summary of content (718 pages)

PAGE 1
Host Software Component (VM Implementation) System Programmer’s Guide Release 6.
PAGE 2
Information contained in this publication is subject to change without notice. Comments concerning the contents of this publication should be directed to: Global Learning Solutions Storage Technology Corporation One StorageTek Drive Louisville, CO 80028-3526 USA sid@stortek.com Export Destination Control Statement These commodities, technology or software were exported from the United States in accordance with the Export Administration Regulations. Diversion contrary to U.S. law is prohibited.
PAGE 3
Document Effectivity EC Number Date 128976 June, 2004 Doc Kit Number --- Type Effectivity First Edition This document applies to the Host Software Component for VM (VM/HSC), Version 6.0. Document Effectivity iii 1st ed.
PAGE 4
iv VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 5
Contents What’s New With This Release? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 6
Matching VOLATTR and TAPEREQ Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Precedence of VOLATTR and TAPEREQ Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mount/Dismount Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mount Processing for Specific Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mount Processing for Scratch Volumes . . . . . . . . .
PAGE 7
Options Offered by PARMLIB Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control Statement Continuation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDS Definition (CDSDEF) Control Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EXECParm Control Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Journal Definition (JRNDEF) Control Statement . .
PAGE 8
Utility Environmental Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACS UTIL Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CMS Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCP Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 9
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Invoking the BACKup Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JCL Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 10
Journal Offload Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Utility Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 11
JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Invoking the Scratch Redistribution Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JCL Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 12
SCP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSC ABEND Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCP ABEND Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 13
Using the Performance Measurement and Predictive Maintenance System (PM2) . . . . . . . . Redistribute Scratch Volumes in the Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintain Quantities of Scratch Cartridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define CAP Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 14
How to Specify a CAPid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAPid Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ranges And Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control Statement Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 15
Reconfiguration utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . REPLace utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RESTore utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCRAtch utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 16
DUMP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FILE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HELP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modify Command (SCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 17
SLSSLHDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SLSSVLG1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SLSSBLOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SLSSLLG1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 18
LSM Robotics Error Codes: 0701 - 0718 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LSM Hardware Error Codes: 0801 - 0809 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LSM Logical Error Codes: 0901 - 0977 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drive Error Codes: 1001 - 1011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Undefined Response Code . . . . . . . .
PAGE 19
Figures Figure 1. HSC Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Figure 2. Virtual Machine Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Figure 3. Shared Library Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Figure 4. HSC/Automated Cartridge System Interaction . . . . . . . . .
PAGE 20
Figure 27. Subsystem Data Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 Figure 28. Using LSMs as Scratch Loaders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 Figure 29. Configuration 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622 Figure 30. Configuration 3 . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 21
Tables Table 1. HSC Command Execution at Base and Full Service Levels . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Table 2. Utility Execution at Base and Full Service Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Table 3. MODel/RECtech Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Table 4. HSC/LMU Validity Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 22
Table 27. SLLUIPCS Print Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 Table 28. Performance Parameters Controlled by PARMLIB Control Statements . . . . . . . . . . . . . . . . 415 Table 29. MEDia, RECtech, and MODel Cross-reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Table 30. Key to Record Format Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 23
Table 60. SLUVHDAT Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574 Table 61. SLUVIDAT Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577 Table 62. SLUVSDAT Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580 Table 63. SLUVVDAT Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 24
xxiv VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 25
What’s New With This Release? HSC 6.0 includes the following enhancements and modifications: Enhancement/Modification Support for the StreamLine (SL8500) library.
PAGE 26
Enhancement/Modification Publication(s)/ Primary Locations The HSC mount/dismount component has been changed to allow any host to mount or dismount a volume. Previously, only the mounting host could perform mount/dismount operations. System Programmer’s Guide Chapter 2 The Volume Report utility displays mounted volumes in a volume report. System Programmer’s Guide Chapter 4 The SLUVVDAT record format has been changed to include a new flag value for the VOLFLAG2 field.
PAGE 27
Preface Scope This guide provides information about the Storage Technology Corporation (StorageTek®) Host Software Component (HSC) and its use with the Automated Cartridge System. Reference information is provided for systems programmers to install, debug, and provide systems support to users of the HSC and the automated library Intended Audience This guide is intended primarily for systems programmers responsible for installing and maintaining HSC software at their library sites.
PAGE 28
• Chapter 4, “Utility Functions” describes control statement conventions for the utilities and presents an overview description, syntax, JCL requirements, JCL examples and a description of output for each utility. Example reports are shown for those utilities producing activity-type reports. • Chapter 5, “Problem Determination, Diagnostics, and Recovery” provides overall diagnostic capabilities supported by the Host Software Component including tracing, dumps, and logging failures.
PAGE 29
References to HSC Product Releases For purposes of convenience, the HSC Release 6.0.0 product is referred to as HSC 6.0 throughout all guides of the HSC documentation set. Related Publications The following documents are referenced in this guide. Additional information may be obtained on specific topics relating to the Automated Cartridge System from these publications.
PAGE 30
xxx VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 31
Chapter 1. System Description Automated Cartridge System Overview The StorageTek Automated Cartridge System (ACS), called the library, is an automated storage and retrieval facility for tape cartridges. The library incorporates the Host Software Component (HSC) to accomplish automated mounting and dismounting of resident cartridges for the library-attached cartridge transports. The library may be attached to a maximum of 16 CPUs (hosts) with an HSC installed on each attached host system.
PAGE 32
- TimberWolf (9740) 10-cell removable magazine or 14-cell permanent rack CAP - StreamLine (8500) includes 3, 13-cell removable magazines. An optional 39-cell CAP can be added. The complete inventory of each LSM and the storage location for each cartridge is contained in the library control data sets maintained by the HSC. • Library Management Unit (LMU)— controls the Library Storage Modules (LSMs) in the ACS. The LMU interprets the commands from the host and relays the instructions to an LSM for execution.
PAGE 33
Host Software Component Overview The HSC performs a variety of functions including: • assisting the tape management system in device allocation • processing mount and dismount requests • delivering library mount/dismount instructions to the LMU via a terminal control unit • providing exits at key points • providing for operator control of the library through a set of operator commands and utility programs • determining the LSM location of each library cartridge from the library control data set (CDS).
PAGE 34
HSC Subsystem Components The HSC is a secondary subsystem that executes in various environments including a standard class G virtual machine. The HSC contains the following components: • External Components — External components interface with other virtual machines, an operator, an administrator, and/or a system programmer.
PAGE 35
Tape Management Interface external component The tape management interface component receives and directs requests for configuration, status, mount, dismount, and other information, from users and programs.
PAGE 36
VM Environment The VM version of the HSC product is the implementation of the ACS Host Software Component (HSC) product on VM. The principal interfaces and components under VM are: • • • • • VM Operating System (CP and CMS) The System Control Program (SCP) The Host Software Component (HSC) The tape management system (TMS) Operators and utility users. VM Operating System (CP and CMS) VM HSC requires relatively few system services.
PAGE 37
System Control Program (SCP) The service virtual machine executes a proprietary System Control Program which provides a small subset of MVS services that include the following major components: • • • • • • • • • Storage management Device management File management Task management Job management Processor management Communication Inter-machine communication Task recovery/termination.
PAGE 38
Task Management Multi-tasking is provided by the SCP to support the MVS-type task requests such as POST, WAIT, ATTACH, etc. that the HSC expects. All modules are made resident at the time of initialization. Also included in this component is the processing of System Management Facility (SMF) records for output to a spool file. Job Management Most utilities are executed within the SCP environment as batch jobs punched by other virtual machines.
PAGE 39
Task Recovery/Termination Task recovery is concerned with resource recovery, possible retry operations, and the logging of software-detected errors. Terminations can be considered a special case of recovery where resources must still be recovered but no retry or logging is necessary. The SCP supports the most common ESTAE and ESTAI options and major SDWA fields. Recovery includes a disabled and enabled (scheduled task) mode.
PAGE 40
HSC and Automated Cartridge System Interaction After the HSC is started and the tape management system (TMS) service machine has begun a dialog, mount or dismount requests are processed from the TMS, and the library control data set is used to determine the location of the requested cartridge (library-controlled or nonlibrary). The library control data set is created on a DASD volume when you perform a data set initialization during installation.
PAGE 41
VM HOST A NONLIBRARY TAPE DRIVE LSM CD TMS SERVICE MACHINE TMS REQUESTOR (CMS) LMU LMU 3174/3274 TERMINAL CONTROL UNIT OPERATOR PRIMARY CONTROL DATA SET SECONDARY CONTROL DATA SET HSC STANDBY CONTROL DATA SET ACS SERVICE MACHINE OPERATOR (CMS) SCP ADMINISTRATOR RSCS ADMINISTRATOR (CMS) VM HOST B RSCS OPERATOR ADMINISTRATOR C27925 Figure 2. Virtual Machine Relationships Chapter 1. System Description 11 1st ed.
PAGE 42
VM/XA HOST ACS MVS/XA SERVICE GUEST MACHINE JOURNAL MVS HOST VM/SP HOST MVS/XA (JES2 OR JES3) ACS SERVICE MACHINE JOURNAL JOURNAL PRIMARY CONTROL DATASET JOURNAL SECONDARY CONTROL DATASET STANDBY CONTROL DATASET C29335 Figure 3. Shared Library Data Sets Automated cartridge mounts/dismounts are performed in response to calls to the tape management interface.
PAGE 43
Automated Mount Figure 4 on page 14 shows the LMU communicating with the LSM through LAN 0. In this illustration, LAN 1 is represented as the backup used in case of a LAN 0 failure. Note: The HSC can select either LAN for communications with the LSM(s). Whichever LAN is not picked becomes the backup. Within the LSM, the robot’s hands are positioned to the correct panel/row/column cartridge location.
PAGE 44
PRIMARY CONTROL DATA SET HOST 1 SECONDARY CONTROL DATA SET STANDBY CONTROL DATA SET JOURNALS HOST 3 HOST 2 HOST 16 3274 CONTROL UNIT (0) 3274 CONTROL (7) (STATIONS 1 - 16) (STATIONS 1 - 16) LMU 0 LMU 255 LAN 0 LOCAL LAN 1 AREA NETWORK LSM 0 LAN 0 LSM 15 CD ACS 0 LSM 0 CD CD LOCAL AREA NETWORK LAN 1 LSM 15 CD ACS 255 C27409 Figure 4. HSC/Automated Cartridge System Interaction 14 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 45
In a library configuration containing more than one LSM, if a cartridge exchange operation occurs to obtain the cartridge for mounting, the cartridge may be returned by one of these possible ways: • If the MNTD Float command is set to ON (the HSC initial value), the cartridge is returned to any new cell location in the LSM containing the tape transport from which it was dismounted.
PAGE 46
User Control of HSC Functions Various controls are in place in the HSC software to permit you to select how the HSC functions. Macros, Utilities, and PARMLIB control statements are normally used by the systems programmer to tune and customize the system. Commands are normally invoked by a systems operator in the performance of daily operations tasks. A description of the function of each of these available controls follows.
PAGE 47
Commands Operator commands are available for Systems Operators to use in daily library operation to perform various tasks. Commands perform such functions as: • assigning a preference to a specific cartridge access port (CAP) • displaying system status, such as control data set status, ACS, LSM, and volume status • entering, ejecting, mounting, and dismounting cartridges • setting of system parameters. Refer to the HSC Operator’s Guide for information about HSC operator commands and usage. Chapter 1.
PAGE 48
18 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 49
Chapter 2. Host Software Component Functions Overview of HSC Functions This chapter describes the basic function of the HSC. Functions for each of the HSC components fit within the architecture structure presented in Figure 1 on page 4. Not all of the components of the architecture structure have functions directly visible to you. Only those HSC functions that you can control or those that are operationally apparent are described in this chapter.
PAGE 50
• automatic cleaning of tape transports with cleaning cartridges under the control of the HSC and the library • restricting the write access to volumes in the library through the Virtual Thumbwheel feature • dual LMU support • control data set recovery. Facilities Available for User Control of HSC Functions There are facilities available for system programmers and operators to use to control various system functions. These include: • • • • macros utilities PARMLIB control statements operator commands.
PAGE 51
Initialization/Termination Functions Initialization/termination functions control initialization and termination of HSC components. This section describes the major initialization/termination functions. HSC Service Levels To provide you with a more flexible, dynamic, automated cartridge mounting execution environment, the HSC has a service level strategy. Operation at either of the two service levels impacts the HSC subsystem.
PAGE 52
Description of Full Service Level The full service level of operation for the HSC provides all of the functions available and necessary to invoke and sustain complete library operations. These functions include: • • • • • • • mount/dismount processing CAP processing cartridge and cell inventory management LMU access library resource recovery support for utilities which require services from the hardware support for the tape management interface.
PAGE 53
Table 1.
PAGE 54
Table 2. Utility Execution at Base and Full Service Levels Service Level Execution Utility Base Full AUDIt NO YES BACKup YES YES EJECt NO YES ENTEr NO YES LIBGen YES YES MOVe NO YES OFFLoad YES YES REPLaceall YES YES RESTore NO NO SCRAtch YES YES SCREdist NO YES SET YES YES UNSCratch YES YES UNSElect YES YES VOLRpt YES YES 24 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 55
Displaying/Setting Service Level An HSC operator command, SRVlev, sets a different service level. Refer to information presented on the Display command in Chapter 2, ‘‘Commands, Control Statements, and Utilities’’ in the HSC Operator’s Guide for information on how to display the current HSC service level.
PAGE 56
Media Type and Recording Technique Processing When a job requests specific media type and recording technique, the HSC uses information provided by TAPEREQ control statements to select a cartridge with the appropriate media type and influence the tape management system to allocate a transport with the requested recording technique. 26 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 57
MEDia and RECtech Parameters When a TMI request or MOUNT command is executed, the HSC searches the appropriate control statements to determine the media type and recording technique to assign to the data set. The MEDia and RECtech parameters are specified on the TAPEREQ and VOLATTR control statements.
PAGE 58
Model Parameter The MODel parameter is specified on the TAPEREQ and UNITATTR statements. MODel values are processed as if they were RECtech values. UNITATTR control statements do not use the RECtech parameter. Table 3 shows the relationship between MODel and RECtech parameters. Table 3.
PAGE 59
Matching VOLATTR and TAPEREQ Statements The type of request (specific or nonspecific) determines whether the HSC uses media type and recording technique information from the VOLATTR statement or the TAPEREQ statement. (See “Precedence of VOLATTR and TAPEREQ Statements” for additional information.) The statements are searched until matches are found for both the media type and recording technique.
PAGE 60
Precedence of VOLATTR and TAPEREQ Statements The precedence of VOLATTR and TAPEREQ statements depends on whether the request is for a specific or nonspecific volume. Specific Volume Requests For a specific volume request, VOLATTR information overrides TAPEREQ information provided that the VOLATTR statements supply both media type and recording technique.
PAGE 61
How To Resolve Scratch Shortages Whenever the HSC cannot satisfy a library mount request for a scratch cartridge, the following message is issued: ... SHORTAGE ACS AA; MMMMMMMM; RRRRRRRR; SSSSSSSS; ...
PAGE 62
If the recording technique specified in the request is 36-track, examine the TAPEREQ statements to determine if the requested media must be: • • • • Standard and 36track Long and 36track Standard and LONGItud Standard and no recording technique specified. Notes: If the default VOLATTR specifies MEDia(Standard) RECtech(18track), then scratch volumes defined as MEDia(Standard) and no recording technique specified cannot be mounted on a 36-track device.
PAGE 63
Mount/Dismount Functions Mount and dismount functions consist of the following processing: • • • • • • mounting specific volumes mounting scratch volumes dismounting library volumes handling abnormal mounts and dismounts virtual thumbwheel (VTW) automated tape transport cleaning. The mount/dismount component receives the request sent by the tape management interface component and makes the mount/dismount of cartridges occur. Each mount/dismount function is described in this section.
PAGE 64
Mount Processing for Scratch Volumes To process scratch mount requests, the HSC determines which volumes within an LSM are considered as scratch volumes. The HSC makes the determination from information contained in the library control data set. Note: A scratch tape is marked as nonscratch when it is mounted even if it is not written on. Normally, only requests for nonspecific VOLSERs and the appropriate label type (as defined in the LIBGEN) are considered as requests for scratch volumes.
PAGE 65
The MNTD PASSTHRU parameter works with SCRDISM by setting the maximum number of pass-thrus that can occur for a cartridge that is to be archived. Refer to the ‘‘MNTD (Mount/Dismount Options) Command and Control Statement’’ in the HSC Operator’s Guide for a description of all the options associated with this command. If the dismount occurs for a temporary volume, the volume is ejected through a CAP, and a message informs the operator to retrieve the cartridge.
PAGE 66
• The TMS is unsatisfied with the scratch cartridge provided. - The HSC dismounts the current volume, removes it from the scratch list, and mounts another scratch volume. Virtual Thumbwheel (VTW) Virtual thumbwheel is the HSC function that allows read-only access to a cartridge in an ACS. Normally cartridges are stored in the library with the physical cartridge thumbwheel enabled for writing.
PAGE 67
Tape Transport Cleaning The HSC allows you to automate the cleaning process or to manually clean library-attached tape transports. When a library transport needs to be cleaned, it informs the LMU, which broadcasts a ‘‘drive needs cleaning’’ message to all connected hosts. The LMU broadcast causes the HSC to issue a console message indicating that a transport needs cleaning. Until a cleaning cartridge is loaded, future mounts continue to initiate this message.
PAGE 68
Once auto-cleaning is activated, the CLean command can be issued to initiate cleaning of specified drives on specified hosts. An example of issuing the CLean command is: CLEAN 582 HSTA Notes: 1. The MNTD AUtocln command must be set to ON before attempting to use the CLean command. 2. The CLean command sets the transport to ‘‘needs cleaning’’ status. The cleaning process is not initiated until the next mount is issued against the transport.
PAGE 69
VOLATTR control statement MAXclean parameter(s). For example, if the helical cleaning cartridges have volsers between CLN500 and CLN599, the following VOLATTR statement can be used to set a different maximum cleaning usage limit for this range of helical cleaning cartridges: VOLATTR SERial(CLN500-CLN599) MAXclean(nn) 5. Contact your StorageTek Customer Services Engineer for appropriate MAXclean values for different cleaning media types.
PAGE 70
during tape transport cleaning. The default can be changed by using the MNTD EJctauto command. Managing Over-use Cleaning Cartridges If an operator is not available to empty a CAP, it may be desirable to retain over-use cleaning cartridges in the LSM for later removal. The MNTD EJctauto command allows you to control processing of over-use cleaning cartridges.
PAGE 71
Messages are written to the console if any over-use cleaning cartridges are found in the ACS, how many were found, and if an over-use cleaning cartridge has been kept in the ACS. These messages help the operator manage cleaning cartridges in the ACS. Managing Cleaning Cartridges Appropriate numbers of compatible cleaning cartridges must be available to clean the transports attached to an LSM.
PAGE 72
solution. This task can be used to initiate the clean process for all drives at a predetermined time. 42 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 73
Volume/Cell Control Functions Volume/cell control functions coordinate and control the location of tape cartridges in the library. Volume/cell control functions described in this section include: • Moving volumes within the library • Scratch subpool management • Scratch threshold task restart. Moving Volumes within the Library Often there is need to move a single volume, several volumes, or a range of volumes to other locations within a library.
PAGE 74
Scratch Subpool Management Management of scratch subpools within the library is an important function affecting library performance and your ability to have greater control over scratch volume activity. You can effectively manage your scratch subpools by several available means. These include: • Defining subpool information in a PARMLIB control statement — Scratch subpools can be defined using the Scratch Subpool (SCRPOol) PARMLIB control statement.
PAGE 75
Refer to Chapter 2, ‘‘Commands, Control Statements, and Utilities’’ in the HSC Operator’s Guide for detailed information about operator commands and to Chapter 4, ‘‘Utility Functions’’ for information about utilities. Scratch Threshold Task Restart The scratch threshold task is a function within the HSC that maintains a count of scratch volumes that are available within a library. Should this task fail, the HSC is unaware of the number of scratch volumes available.
PAGE 76
Cartridge Access Port (CAP) Processing Functions CAP processing functions control cartridge enter and eject functions. The HSC provides operator commands and utilities which permit you to: • enter cartridges into the library • eject cartridges from the library. The CAP is the focal point for the activities of entering or ejecting cartridges. At least one CAP is located on the access door of every LSM, and indicators are provided for the operator to identify what CAP operations are active.
PAGE 77
Ejecting Cartridges from the Library Cartridges are ejected from the library by using either the EJect command or the EJECt utility. Either a single cartridge, a range of cartridges, or a list of cartridges can be identified for removal from the library. The robot locates the appropriate storage cell, withdraws the cartridge from its cell, and moves it to an available cell in a CAP. The operator must remove cartridges from the library through the CAP.
PAGE 78
Releasing an Allocated CAP The RELease cap-id operator command allows you to release a CAP that is allocated to a failed host. A CAP can be left allocated to a system if the HSC terminated without recovery while the CAP is active. When you issue the command, appropriate messages inform you of conditions and actions to take. You are prompted by an initial message to confirm or terminate release of the specified CAP. This confirmation prevents the release of a CAP that is currently being used by the system.
PAGE 79
Near Continuous Operations A number of HSC facilities and techniques are provided that customers can employ to avoid outages and make changes less disruptive to their library hardware and HSC environment.
PAGE 80
primary copy. If a standby CDS copy is active, the new primary CDS copy is copied over the standby CDS copy, and the standby becomes the new secondary copy. • If a standby CDS copy is active, and a failure occurs in accessing the secondary CDS copy, the current primary CDS copy is copied over the standby CDS copy, and the standby becomes the new secondary copy.
PAGE 81
that are not directly affected. Then, these subsystems can be recycled (brought down and then restarted) to pick up the changed information. Cycling the affected HSCs can be done at a convenient time, with only one HSC down at a time. This permits an HSC server to remain up, servicing requests from clients. Note: In many instances, the SET utility can run while HSC subsystem(s) are active. However, some SET options require that the HSC(s) affected must be down, e.g., SET HOSTID.
PAGE 82
Changing Panels The following procedures describe methods to make changes to panels. These include changing panels types in an LSM and removing cartridges to facilitate hardware changes. • To change panel types in an LSM: 1. Use the SET utility to freeze the panel, preventing any additional cartridges from being moved to it. This prohibits new cartridge home cell locations from being allocated on the frozen panel. SET FREEZE(ON),FORLSMID(aa:ll),FORPANEL(pp) 2.
PAGE 83
• To remove cartridges from rows on panel(s) to facilitate hardware (e.g., cabling) changes: 1. Use the SET utility to freeze the panel, preventing any additional cartridges from being moved to it. This prohibits new cartridge home cell locations from being allocated on the frozen panel. SET FREEZE(ON),FORLSMID(aa:ll),FORPANEL(pp) 2. Use the MOVe utility or the MOVe or EJect commands to move all cartridges off the panel rows being changed.
PAGE 84
Using CDS Rename/Relocate/Expand The HSC can rename, relocate, and expand an existing CDS(s) without requiring tape activity to be suspended or the HSC to be taken down on all hosts. To use these features, users must be at HSC 5.0 or later, however, compatible down-level releases of the HSC may be initialized after the CDS has been modified as long as the CDSDEF control statements are consistent with the active CDS definitions.
PAGE 85
Note: TSO 3.2 may create a single extent data set even when no secondary quantity is specified. It is not necessary to initialize the CDS copy, that is, you do not have to execute SLICREAT or copy another CDS copy to the new data set. Assume that ACS.DBASECPY has been disabled and deleted (or uncataloged), and ACS.DBASENEW has been allocated and cataloged. The following command enables the renamed and relocated CDS: CDS ENABLE DSN(ACS.
PAGE 86
Warning: StorageTek recommends backing up all CDS copies prior to issuing the CDS EXpand command. Failures during the expand operation usually cause the CDS to be unusable. It is important to back up the CDS before invoking the CDS EXpand command to insure that the latest copy of the CDS is available in case of a failure during the expand operation. The number of formatted blocks in the CDS remains constant for all copies of the CDS regardless of the physical space allocated for CDS copies.
PAGE 87
Swapping Library Transports - New Model Types When you physically upgrade or change tape transports, a mismatch can occur between the model types stored in the CDS and the updated model types specified in the UNITDEF command. If this situation arises, you receive an error message: SLS1628I UNITDEF: Record 1 ...MODEL is incompatible with UNIT Follow this procedure to avoid the problem: 1. Terminate the HSC on all hosts by issuing the MVS STOP command. 2. Physically replace the tape transports. 3.
PAGE 88
Common Recovery Functions Common recovery functions consist of information gathering from the control data sets and journals, and processing to recover from a database or hardware failure. The most vital recovery function is control data set recovery which is described in this section. Control Data Set Recovery Control data sets contain valuable information required for the HSC software and the library to function.
PAGE 89
Control data sets can be accessed by different hosts and are kept synchronized. In event of a failure, the BACKup and RESTore utilities can be used to perform extensive error checking and synchronization of the data. A backup control data set and journals are used to reconstruct the control data sets. The integrity of the control data sets is extremely important. In multiple processor environments, data set integrity is much more difficult to maintain.
PAGE 90
Dynamic Enable/Disable of Control Data Sets Operator commands are supplied to give you control over which data sets the HSC is utilizing. This functionality is particularly useful in a multiple-processor environment. Before attempting to enable or disable any data set, you can use the Display CDS command to display the current status of the control data sets. The commands to enable or disable a control data set can be issued without halting HSC execution or disrupting any running HSC.
PAGE 91
3. Make SLS.DBASE2 the new secondary control data set by issuing the command: CDS ENABLE DSN=SLS.DBASE2 4. Issue the command: DISPLAY CDS to view the current control data set status and assignments. • HSC BACKup and HSC RESTore procedure: 1. Stop the host software on all hosts. 2. Backup the control data set with the HSC BACKup utility. 3. Restore the control data set with the HSC RESTore utility. This will clear the control data set information in the Database Heartbeat record. 4.
PAGE 92
Command Functions Command functions consist of real-time control of automated cartridge handling, dynamic selection of HSC processing options, and various query operations. Figure 6 illustrates the specific areas within a library where HSC commands enable you to control processing.
PAGE 93
Controlling LSM Operating Mode The operating mode for any LSM is controlled by using the MODify command to place the LSM online or offline. An LSM operating mode is a relationship between an LSM and all attached hosts. The two LSM operating modes are: • automatic – the LSM is online to all hosts. • manual – the LSM is offline to all hosts. When an LSM is online, the LSM is in the automatic mode, meaning that the robot is fully operational. When an LSM is offline, the LSM is in manual mode.
PAGE 94
Using the VIew command to Inspect an LSM Component When you issue the VIew command, you direct the vision system to focus on an item inside of the LSM for a specified length of time. Upon entering the command, the following events occur: • A VIew request is sent to the controlling LMU. • A WTOR is displayed on the console when the camera is in position; the message indicates which camera/robot hand is focused on the specified object.
PAGE 95
Utility Functions Utility functions provide control and recovery of library resources. In addition, reporting of library and volume activity can be invoked using various HSC utilities. Figure 7 illustrates the control concept provided by the various HSC utilities. Figure 6.
PAGE 96
LMU Server Functions LMU server functions control each of the Automated Cartridge Systems within a library. Many of the LMU server functions are completely transparent to users. This section contains information about LMU server tasks of which you should be aware. Dual LMU Functionality With dual LMU functionality, a switch happens when the LMU designated as the master fails, or is forcibly switched by issuance of an operator command.
PAGE 97
LMU Switchover Messages The HSC Messages and Codes Guide contains all the messages appropriate to the LMU switchover process. After an LMU Switch Occurs After a switch of LMUs occurs and the LSMs have finished quick initialization procedures, all cartridge motion requests are re-driven and completed. If a motion request cannot be completed, the cartridge in question is made errant. Note: ENter and EJect operations may need to be restarted after a switchover.
PAGE 98
Adding New Stations to an ACS The following is an example of JCL for the SET utility that can be used as a pattern for adding new stations to an ACS without requiring a reconfiguration. Note: Update LIBGEN control statements to make changes permanent. You do not have to execute the Reconfig utility to implement these changes. Refer to “Reconfiguration Utility” on page 225 for more information about reconfiguration.
PAGE 99
Reconstructing a LIBGEN The Database Decompile (LIBGEN) utility can be used to reconstruct a LIBGEN, reflecting the true configuration of your HSC subsystem if for some reason your LIBGEN has been lost. Refer to “Database Decompile (LIBGEN) Utility” on page 184 for details on how to use the Database Decompile utility. Chapter 2. Host Software Component Functions 69 1st ed.
PAGE 100
Dynamic LMU Connection LMU network connections can be defined dynamically to TCP/IP addresses using the LMUPATH and LMUPDEF control statements. Note: For information on implementing TCP/IP connections, refer to the LMUPATH and LMUPDEF control statements in Chapter 3, “HSC Control Statements and HSC Start Procedure” and to display information about the LMUPDEF data set, refer to Display LMUPDEF in the HSC Operator’s Guide.
PAGE 101
For example, if a user enters Display CDS and the following output appears HOSTID---LEVELFLAG---DESCRIPTION--HSTA 4.0.0 (F0) ACTIVE PRIMARY HSTB 4.0.0 (F0) ACTIVE PRIMARY HSTC 4.0.0 (F0) ACTIVE PRIMARY HSTD 4.0.0 (F0) ACTIVE PRIMARY SECONDARY SECONDARY SECONDARY SECONDARY STANDBY STANDBY STANDBY STANDBY then, HSTA is host index number 1, which when added to 50000 means that the HSC on HSTA uses port number 50001, the HSC on HSTB uses 50002, the HSC on HSTC uses 50003, and the HSC on HSTD uses 50004.
PAGE 102
Transitioning Between 3270 and TCP/IP A number of methods are available to move between 3270 station connections and TCP/IP LMU network attachment. StorageTek recommends cycling the HSC as the preferred process to transition between 3270 and TCP/IP. However, the following procedures offer alternative ways to accomplish the transition. Note: The host ACS client must be upgraded to VM 4.0 or higher and must be running IBM TCP/IP. 3270 to TCP/IP 1.
PAGE 103
Recovering TCP/IP Communications StorageTek suggests either performing a normal HSC shutdown or changing the HSC state to the base service level prior to recycling TCP/IP or taking TCP/IP down for any extended period of time. Note: Please refer to “Recovery Maintenance Requirements” on page 70 to see PTFs that must be applied before recovery processes discussed in this section can be implemented.
PAGE 104
Operator Intervention - Single LMU Configuration If the HSC network recovery times out, the ACS is automatically changed to an offline state and all outstanding LMU requests are purged. After troubleshooting the network connection, vary the ACS online. Vary ACS acs-id ONline Note: During network recovery, the ACS can be forced offline, however, all outstanding LMU requests are purged. StorageTek recommends that users allow the HSC network recovery process to remain active and not to force the ACS offline.
PAGE 105
Configuring VM for TCP/IP Support The following items must be updated to allow VM to support TCP/IP station protocol. • • • • System Definition File System Profile File HSC Startup Job File LMUPATH Definition Data Set. System Definition File (ACS SYSDEF) To define the IUCV connection with the LMU communications component, add the TCP/IP file statement to the ACS SYSDEF file. FILE LCOMM IUCV DSN .LMU.COMM where tcpip is the user ID of the TCP/IP service machine.
PAGE 106
Initializing the LMUPATH Definition Data Set The next three tasks apply to the LMUPATH definition data set. Minidisk Statement for the LMUPATH Data Set Add a minidisk statement to the directory entry for the STKACS userid. Refer to “Define the ACS Service Machine” in the HSC Installation Guide for an example. Minidisk Format Format the minidisk as an OS or CMS RESERVED minidisk using the SLIMDISK utility.
PAGE 107
LMUPATH Definition Data Set Add the LMUPATH statements to the LMUPDEF data set using the ACS UTIL VOLCOPY command. Note: ACS UTIL VOLCOPY creates skeleton JCL that you modify to match your configuration. /JOB SLSXUTIL SLUGENER /PARM RECCOPY /FILE SYSPRINT DEV PRNT CLASS A /FILE SYSUT2 DEV DSN /FILE SYSUT1 * LMUPATH ACS(aa) LMUADDR(nnn.nnn.nnn.nnn) LMUPATH ACS(aa) LMUADDR(nnn.nnn.nnn.nnn) • • • Chapter 2. Host Software Component Functions 77 1st ed.
PAGE 108
Communication Functions HSC communication functions ensure that passing of pertinent information between HSC components and hosts is accomplished successfully. Host-to-Host Communications Services The HSC permits you to select the hierarchy of methods used for host-to-host communications. The communications services are designed to provide you with fail-safe communications between HSC hosts in a data center complex.
PAGE 109
How Communications Services are Set or Changed Communications services are set or changed by the Communications Path (COMMPath) command and control statement. This command specifies host, communication method, LMU paths and VTAM path name for the associated host. The communication path definitions can be modified at any time during library operation without terminating the HSC. The COMMPath command and control statement sets up a table of definitions for the host that is executing the command.
PAGE 110
COMMPath can be specified by an operator as an operator command, or by a systems programmer as a PARMLIB control statement. Before COMMPath is issued, all methods of communications are set to CDS. Refer to ‘‘Communications Path (COMMPath) Command and Control Statement’’ in the HSC Operator’s Guide for information on the usage of the command. It is recommended that host-to-host communications be defined in PARMLIB at startup.
PAGE 111
Software Requirements The following software requirements apply: • LMU 3.0 (or higher) or 9315/9330 1.0 (or higher) µ-software is required for a multiple-level communications service. • ACF/VTAM 3.2 (or higher) must be available to use the VTAM method of communications. Tape Management Interface The tape management interface component provides you with the interface definitions that can be used to interface a tape management system with the HSC.
PAGE 112
Batch Application Program Interface (API) The Batch API allows you to retrieve 2.0- and 2.1-level CDS information in batch mode. The CDS specified as input to the request does not have to be active nor does it have to be referenced by the HSC address space (the request executes in the user address space). In addition, the HSC does not have to be active to submit the request. Refer to Appendix F, “Batch Application Program Interface (API)” on page 629 for more information. 82 VM/HSC 6.
PAGE 113
Chapter 3. HSC Control Statements and HSC Start Procedure Overview This chapter discusses two kinds of control statements, PARMLIB (below) and definition data set (refer to “Definition Data Set Control Statements” on page 103), and the HSC Start procedure (refer to “Starting HSC Execution” on page 163). For more information about HSC installation and initialization, refer to the HSC Installation Guide.
PAGE 114
Processing PARMLIB Control Statements PARMLIB control statements are processed at HSC initialization. “Sample ACS SLKJCL File” on page 161 contains /FILE statements defining data sets and members that contain PARMLIB control statement definitions. Note: In the ACS SLKJCL example, ‘‘MEMBER(xx)’’ is the MEMBER parameter described in “Defining PARMLIB Control Statements” on page 83. Multiple PARMLIB data sets can be allocated. At HSC startup, members can be specified at your discretion.
PAGE 115
(CDSDEF) Control Statement” on page 87 for control statement syntax, parameter information, and example statements. Communications Path Definition This control statement and operator command provides you a way to set the communications path utilized in a multi-host environment. A hierarchy for communications can be established. If a communications failure occurs, the hierarchy defined ensures continued operation of HSC software and the communications path.
PAGE 116
Option Control The general purpose OPTion control statement and operator command provides you methods to control the following: • viewing time when using the VIew command • issuance of a message if an attempt is made to enter duplicate volumes into a library • display of uppercase and lowercase characters output at the system console. • maximum number of cartridges that can be ejected for one eject operation.
PAGE 117
CDSDEF CDS Definition (CDSDEF) Control Statement The CDSDEF control statement is required and provides static information to the HSC. This information is used by the HSC at initialization and remains for the life of the HSC execution. The primary, secondary, and standby control data sets are dynamically allocated. The CDSDEF PARMLIB control statement defines which copies of the control data set are used while the HSC is running.
PAGE 118
CDSDEF Control Statement Name CDSDEF initiates the control statement. Parameters DSNx dataset.name is the name of an HSC control data set. At least one DSN parameter must be specified, as many as three can be specified. If two data sets are specified, then the volume inventory information on both copies is kept current, and these two data sets are referred to as the primary and the secondary CDS.
PAGE 119
CDSDEF Example The following is an example of using the CDSDEF control statement. CDSDEF DSN1(SLS.DBASE),VOL1(HSC101),UNIT1(501),+ DSN2(SLS.DBSEC),VOL2(HSC102),UNIT2(502),+ DSN3(SLS.DSTBY),VOL3(HSC103),UNIT3(503),+ DISABLE Note: Control statements can only be continued if PARMLIB begins with a /*...*/ comment statement (see “Control Statement Syntax Conventions” on page 439). Chapter 3. HSC Control Statements and HSC Start Procedure 89 1st ed.
PAGE 120
EXECParm EXECParm Control Statement The EXECParm control statement is an alternative method for specifying the GTF event ID (Eid(gtfeid)) and GTF format ID (Fid(gtffid)). The EXECParm control statement also provides a parameter that enables you to control display of the system command prefix when messages are written to the operator at the system console. This parameter controls the command prefix on WTO and WTOR messages.
PAGE 121
EXECParm Fid optionally, gtffid specifies a GTF format ID. /PARM Fid(user-specified-format-id) parameter is valid for use in the HSC startup SLKJCL file as an alternative method of specifying the GTF format ID. HOSTID optionally, host-id specifies the system ID associated with the request to process the EXECParm control statement. Note: If the hostid specified does not match the host executing the command, the command is ignored and no message is issued.
PAGE 122
JRNDEF Journal Definition (JRNDEF) Control Statement The JRNDEF control statement provides static information to the HSC. This information is used by the HSC at initialization and remains for the life of the HSC execution. Control information provided to the HSC by JRNDEF includes: • the name for HSC journal data sets Note: If your recovery technique involves using journals, both journal data sets are required. HSC will not initialize if only one journal data set is provided.
PAGE 123
JRNDEF UNITx optionally, unitname is used to specify the unit parameter in the SVC99 dynamic allocation parameter list. The UNIT parameter must be specified in VM. FULL optionally, this parameter provides the following options: Abend the HSC internally abends if both journals fill to capacity before a CDS backup is executed. This parameter is the default. Continue library operations in the complex continue to occur without the benefit of journaling on any host.
PAGE 124
LKEYDEF LKEYDEF Command and Control Statement The LKEYDEF command/control statement retrieves LKEYINFO control statements containing HSC license key information, and loads them into an address space where they are available for retrieval by the HSC license key validation service. Refer to the VM/HSC Installation Guide for more information about StorageTek license keys. Warning: The LKEYDEF control statement must be present in the HSC START procedure prior to initialization.
PAGE 125
LKEYDEF UNIT Optionally, specifies the unit where the definition data set resides. unitname Indicates the unit name. If the definition data set is not cataloged or this parameter is omitted, a unit name of SYSDA is the default. HOSTID Optionally, limits the execution of this command or control statement to the specified hosts. host-id Specifies the name of one or more hosts from which to execute this command or control statement.
PAGE 126
LKEYINFO License Key Information (LKEYINFO) Control Statement The LKEYINFO control statement is used to input license key information for the HSC. It is placed in a data set or Partitioned Data Set member identified by an LKEYDEF control statement in the HSC START procedure, and must be present for HSC to initialize. Note: Refer to the VM/HSC Installation Guide for more information about configuring your HSC license key.
PAGE 127
LKEYINFO KEY Specifies the license key string as received from StorageTek. license-key-string Indicates the license key string. Examples In the following example, the LKEYINFO control statement is used to input HSC license key information as received from StorageTek. LKEYINFO PROD(VER0600) CUST(‘CUSTOMER NAME’) SITE(12345) EXPRD(2004365) KEY(DKEEXEDERTB3466) Chapter 3. HSC Control Statements and HSC Start Procedure 97 1st ed.
PAGE 128
RECDEF Reconfiguration CDS Definition (RECDEF) Control Statement The RECDEF control statement, in combination with the CDSDEF control statement (refer to “CDS Definition (CDSDEF) Control Statement” on page 87), defines which CDS copies are to be used when running the Reconfiguration utility. CDSDEF specifies the old input copies of the CDS; RECDEF the new copies. Note: RECDEF parameters replace the DBPRMNEW and DBSHDNEW DD statements used in previous releases.
PAGE 129
RECDEF Example The following is an example of using the RECDEF control statement. RECDEF DSN1(SLS.DBASE),VOL1(HSC101),UNIT1(501),+ DSN2(SLS.DBSEC),VOL2(HSC102),UNIT2(502) Note: Control statements can only be continued if PARMLIB begins with a /*...*/ comment statement (see “Control Statement Syntax Conventions” on page 439). Chapter 3. HSC Control Statements and HSC Start Procedure 99 1st ed.
PAGE 130
SCRPOol Scratch Subpool Control Statement The scratch subpool control statement provides you with control of the scratch volume activity in a library. Refer to “Scratch Subpool Management” on page 44 for more information relating to this control statement. Warning: If scratch pools are defined by this method and the TMS attempts to define scratch pools with scratch pool indices, the TMS requests will return an invalid return code.
PAGE 131
SCRPOol RANGE range specifies the volume serial numbers which the subpool represents. Range start and end values are separated by a single dash (-). Multiple ranges may be specified separating each range by commas. Notes: 1. The range of volume serial numbers must be unique for each subpool; that is, a volume serial number cannot be used in more than one subpool range. 2.
PAGE 132
SCRPOol Example The following is an example of using the Scratch Subpool control statement. SCRPO SCRPO SCRPO SCRPO NAME(SITE1),RANGE(100000-200000,300000-400000),LABEL(SL) NAME(SITE2),RANGE(500000-540072),LABEL(NL),HOSTID(HSC1) NAME(SITE3),RANGE(540081-610094),LABEL(NSL) NAME(SITE4),RANGE(AP1000-AP1999),LABEL(SL),HOSTID(HSC1,HSC6) Other Methods of Controlling Scratch Subpools There are other ways to control scratch volumes and scratch subpools in the library.
PAGE 133
Definition Data Set Control Statements Definition data sets contain the control statements used to define tape data set storage policies to the HSC. A definition data set must be sequential (it may be a partitioned data set [PDS] member) with any valid record format (RECFM). The syntax rules for the HSC PARMLIB data set designated by SLSSYSxx apply to the statements contained in a definition data set, except that comment statements with an asterisk in column one are not allowed.
PAGE 134
Options Offered by Definition Data Set Control Statements The following definition data set control statements are included in this chapter: OPTion TITLE This control statement allows you to specify a string that identifies a definition data set. Refer to “OPTion TITLE Control Statement” on page 113 for control statement syntax, parameter information, and example statements. LMU Path The LMUPATH control statement defines network LMU attachments.
PAGE 135
(UNITDEF) Command and Control Statement” on page 140 for control statement syntax, parameter information, and example statements. Volume Attribute The VOLATTR control statement specifies tape volume attributes. Refer to “Volume Attribute (VOLATTR) Control Statement” on page 143 for control statement syntax, parameter information, and example statements.
PAGE 136
Defining Unit Attributes (UNITATTR) UNITATTR statements describe the recording technique attributes of library and nonlibrary transports. Transports are described by: • unit address • transport model number. To allow the HSC to operate correctly, the user must specify UNITATTR statements for all nonlibrary transport models that appear to the operating system as 3490E-type and 3590-type devices. For library devices, the model type is determined by the LMU.
PAGE 137
The VOLDEF command causes the HSC to open the definition data set containing the VOLATTR statements. See “Volume Attribute Definition (VOLDEF) Command and Control Statement” on page 154 and “Volume Attribute (VOLATTR) Control Statement” on page 143 for descriptions of syntax and parameters. Identifying the Definition Data Sets (OPTION TITLE) The OPTion TITLE control statement places an identifying string in a definition data set to describe the contents of the data set.
PAGE 138
LMUPATH LMUPATH Control Statement The LMUPATH control statement allows users to define network LMU attachments. LMUPATH statements are read from the definition data set specified by the LMUPDEF command. The LMUPATH statement must be placed in the definition data set; it cannot be issued as an operator command. Note: Users can find additional important TCP/IP-related information by referring to “Dynamic LMU Connection” on page 70.
PAGE 139
LMUPATH LMUADDR identifies an LMU by IP address or host name for each ACS. To designate a single LMU environment, specify one IP address or host name. To specify a dual LMU environment, users can enter an additional IP address and/or host name. Note: A maximum of two addresses can be specified. Users can intermix host name and IP addresses in one LMUPATH control statement. Each parameter entered must represent a different IP address. lmu_hostname defines a host name for the TCP/IP connection.
PAGE 140
LMUPDEF LMUPDEF Command and Control Statement The LMUPDEF command and control statement is used to specify the definition data set that contains network LMU attachment (LMUPATH) statements. The data set must be a sequential or a partitioned data set (PDS) with any valid record format (RECFM). Also, the data set must contain one or more LMUPATH statements. The LMUPDEF statement can be specified in PARMLIB, or it can be issued as an operator command to dynamically load or reload LMUPATH parameters.
PAGE 141
LMUPDEF Syntax LMUPDEF DATASET(dataset.name) DSN(dataset.name) , HOSTID( host-id VOLume(volser) UNIT(unitname) ) Control Statement Name LMUPDEF Initiates the LMUPDEF command and control statement. Parameters DATASET or DSN specifies the name of the data set containing the LMUPATH statements to be processed and, optionally, an OPTion TITLE statement. Note: The definition data set may contain VOLATTR, UNITATTR, TAPEREQ, LMUPATH, and OPTion TITLE statements.
PAGE 142
LMUPDEF UNIT specifies the unit where the definition data set is located. unitname specifies the unit name. If the definition data set is not cataloged and this parameter is omitted, a unit name of SYSALLDA is the default. HOSTID (This parameter is valid only for use in PARMLIB, so that multiple systems can share a PARMLIB member containing TAPEREQ, VOLATTR, UNITATTR, or LMUPATH statements for different releases of HSC. If entered from the console, message SLS0018I is issued.
PAGE 143
OPTion TITLE OPTion TITLE Control Statement The OPTion TITLE statement is used to specify an identifying string for a definition data set. The identifying string can be any information that helps the user describe the contents of the definition data set. The OPTion TITLE statement must be placed in the definition data set; it cannot be issued as an operator command.
PAGE 144
OPTion TITLE Example The following example illustrates the use of the OPTion TITLE control statement. Specify an Identifying String For a Definition Data Set OPTION TITLE(‘SAMPLE IDENTIFYING STRING’) 114 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 145
SCRPDEF Scratch Subpool Definition (SCRPDEF) Command and Control Statement The SCRPDEF command and control statement is used to specify the definition data set that contains scratch subpool (SCRPOol) parameter statements. (Refer to “Scratch Subpool Control Statement” on page 100 for details on syntax and parameters.) The data set must be a sequential or a partitioned data set (PDS) with any valid record format (RECFM). Also, the definition data set must contain one or more SCRPOol statements.
PAGE 146
SCRPDEF 4. For additional information about syntax, refer to “Control Statement Syntax Conventions” on page 439. Syntax SCRPDEF DATASET(dataset.name) DSN(dataset.name) , HOSTID( host-id VOLume(volser) UNIT(unitname) ) Control Statement Name SCRPDEF initiates the SCRPDEF command and control statement. Parameters DATASET or DSN specifies the name of the data set containing the SCRPOol statements to be processed and, optionally, an OPTion TITLE statement.
PAGE 147
SCRPDEF UNIT specifies the unit where the definition data set is located. unitname specifies the unit name. If the definition data set is not cataloged and this parameter is omitted, a unit name of SYSALLDA is the default. HOSTID (This parameter is valid only for use in PARMLIB, so that multiple systems can share a PARMLIB member containing SCRPOol, TAPEREQ, VOLATTR, or UNITATTR statements for different releases of HSC. If entered from the console, message SLS0018I is issued.
PAGE 148
TAPEREQ Tape Request (TAPEREQ) Control Statement The TAPEREQ control statement is used to specify tape request attributes. TAPEREQ statements are read from the definition data set specified by the TREQDEF command. (Refer to “Tape Request Definition (TREQDEF) Command and Control Statement” on page 133 for details on syntax and parameters.) The TAPEREQ statement must be placed in the definition data set; it cannot be issued as an operator command.
PAGE 149
TAPEREQ After searching the TAPEREQ statements, the HSC • selects the appropriate devices • mounts cartridges that are the right media type. The TAPEREQ parameters are divided into selection criteria (i.e., input) parameters, and media and recording technique or model (i.e., output or result) parameters. The selection criteria are used to locate the first TAPEREQ statement that matches the request under consideration.
PAGE 150
TAPEREQ With the modified definition data set in effect, the HSC searches the remaining TAPEREQ statements to determine the media type and recording technique (or model) to assign to a request. To disable all TAPEREQ definitions, load a definition data set that contains only one TAPEREQ statement with no parameters. Refer to Table 5 on page 126 and Table 6 on page 128 to see a list of TAPEREQ media and recording technique (or model) default values. 120 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 151
TAPEREQ Syntax TAPEREQ * JOBname( * jobname ) STEPname( * PROGram( program-name stepname ) ** ) PGMname(program-name) DATASET( dataset-name ) DSN(dataset-name) DDName(DD-name) GE RETPD( EQ NE ,retention-period ) GT LT LE EXPDT( GE EQ ,expiration-date ) NE GT LT LE * VOLType( Specific Nonspec ) Chapter 3. HSC Control Statements and HSC Start Procedure 121 1st ed.
PAGE 152
TAPEREQ Syntax (continued) , MEDia( STK2 LONGItud 18track 36track 36Atrack 36Btrack 36Ctrack HELical DD3 STK1R STK1R34 STK1R35 STK1RA STK1RA34 STK1RA35 STK1RB STK1RB34 STK1RB35 STK1RAB STK1RAB4 STK1RAB5 STK1RC STK1RC34 STK1RC35 STK2P STK2P34 STK2P35 STK2PA STK2PA34 STK2PA35 STK2PB STK2P STK2PB34 LONGItud ) RECtech( Standard CST MEDIA1 STD 1 3480 ECART E ECCST ETAPE Long MEDIA2 3490E ZCART Z HELical DD3 DD3A DD3B DD3C STK1 STK1R R ) STK2PB35 , MODel( model1 SUBPool(subpool-name) 122 VM/HSC 6.
PAGE 153
TAPEREQ Control Statement Name TAPEREQ initiates the TAPEREQ control statement. If any of the following apply: • there is no TAPEREQ statement specified in the definition data set to match a request, or • no matching TAPEREQ statement specifies MEDia or RECtech, or • no definition data set loaded, then MEDia and RECtech are set to undefined, which matches all requests. Any available device is eligible for allocation. Table 5 on page 126 shows default values used if the media type is omitted.
PAGE 154
TAPEREQ PROGram or PGMname optionally, specifies the program name. If PROGram is not specified, the default value is *. The program name used is the job step program name. program-name specifies the program name.The TAPEREQ statement is used only when the specified program-name matches the program name in the request. DATASET or DSN optionally, specifies the data set name. If DATASET (or DSN) is not specified, the default value is **. The rules of SMS and RACF generics are followed for this parameter.
PAGE 155
TAPEREQ retention-period specifies the retention period in days for the data set. Specify the number of days as a 1- to 4-digit decimal number. EXPDT optionally, specifies the expiration date and the relationship that must exist. EQ equal to NE not equal to GT greater than GE greater than or equal to LT less than LE less than or equal to. expiration-date specifies the expiration date of the data set in yyddd or yyyy/ddd format.
PAGE 156
TAPEREQ This parameter is ignored for an existing data set if the media characteristics are determined by the volume. If this parameter is not specified, a default is chosen based on the value of the RECtech parameter. Table 5 shows default values used if MEDia is omitted. Table 5.
PAGE 157
TAPEREQ • • • • • • E ECCST ETAPE Long MEDIA2 3490E. ZCART indicates a 3490E, extended capacity cartridge that provides greater storage capacity than an ECART. It can be used only on a 9490EE drive. ZCART can be abbreviated as Z. DD3 indicates any DD3A, DD3B, or DD3C (HELical) cartridge. DD3A, DD3B, DD3C indicates a helical cartridge. The media indicator in the external label is encoded with the cartridge type (A, B, or C). Note: DD3A, DD3B, or DD3C can be abbreviated to A, B, or C, respectively.
PAGE 158
TAPEREQ RECtech optionally, specifies the method used to record data tracks on the tape surface for the desired data set. You can enter a list of recording techniques, but they must be separated by commas. Notes: 1. A list specifies a generic pool from which a selection is made. There is no implied priority. 2. The SL8500 library supports only the T9x40 (9840/T9840B/T9840C and T9940A/T9940B) media types and recording techniques. RECtech and MODel are mutually exclusive.
PAGE 159
TAPEREQ 36Atrack indicates a 4490 transport. 36Btrack indicates a 9490 transport. 36Ctrack indicates a 9490EE transport. HELical indicates a device using helical recording. DD3 indicates a device using helical recording. STK1R indicates any 9840 or T9840B transport. STK1R34 indicates a 3490E-image 9840 or T9840B transport. STK1R35 indicates a 3590-image 9840 or T9840B transport. STK1RA indicates a 3490E or 3590-image 9840 transport. STK1RA34 indicates a 3490E-image 9840 transport.
PAGE 160
TAPEREQ STK1RC indicates a 3490E or 3590-image T9840C transport. STK1RC34 indicates a 3490-image T9840C transport. STK1RC35 indicates a 3590-image T9840C transport. STK2P indicates any T9940A transport. STK2P34 indicates a 3490E-image T9940A transport. STK2P35 indicates a 3590-image T9940A transport. STK2PA indicates a T9940A transport. STK2PA34 indicates a 3490E-image T9940A transport. STK2PA35 indicates a 3590-image T9940A transport. STK2PB indicates a T9940B transport.
PAGE 161
TAPEREQ 4490 indicates a 4490 (36-track Silverton) transport. 9490 indicates a 9490 (36-track Timberline) transport. 9490EE indicates a 9490EE (36-track Timberline EE) transport. SD3 indicates an SD-3 (RedWood) transport. 9840 indicates a 3490E-image 9840 transport. 984035 indicates a 3590-image 9840 transport. T9840B indicates a 3490E-image T9840B transport. T9840B35 indicates a 3590-image T9840B transport. T9840C indicates a 3490E-image T9840C transport. T9840C35 indicates a 3590-image T9840C transport.
PAGE 162
TAPEREQ Example The following example illustrates how to use TAPEREQ statements to specify tape request attributes. Set Tape Request Attributes TAPEREQ TAPEREQ TAPEREQ TAPEREQ DSN(BACKUP.**) MEDIA(ECART) RECTECH(36TRACK) DSN(PAYROLL.**) MED(DD3A) RECTECH(DD3) MED(STANDARD) RECTECH(36TRACK) MED(STK1R) RECTECH(STK1) Note: In the example above, the last TAPEREQ statement specifies a user-defined default for all data sets that do not match one of the first three statements. 132 VM/HSC 6.
PAGE 163
TREQDEF Tape Request Definition (TREQDEF) Command and Control Statement The TREQDEF command and control statement is used to specify the definition data set that contains tape request (TAPEREQ) parameter statements. (Refer to “Tape Request (TAPEREQ) Control Statement” on page 118 for details on syntax and parameters.) The data set must be a sequential or a partitioned data set (PDS) with any valid record format (RECFM). Also, the definition data set must contain one or more TAPEREQ statements.
PAGE 164
TREQDEF Syntax TREQDEF DATASET(dataset.name) DSN(dataset.name) , HOSTID( host-id VOLume(volser) UNIT(unitname) ) Control Statement Name TREQDEF initiates the TREQDEF command and control statement Parameters DATASET or DSN specifies the name of the data set containing the TAPEREQ statements to be processed and, optionally, an OPTion TITLE statement. (Refer to “Tape Request (TAPEREQ) Control Statement” on page 118 and “OPTion TITLE Control Statement” on page 113 for details on syntax and parameters).
PAGE 165
TREQDEF UNIT specifies the unit where the definition data set is located. unitname specifies the unit name. If the definition data set is not cataloged and this parameter is omitted, a unit name of SYSALLDA is the default. HOSTID (This parameter is valid only for use in PARMLIB, so that multiple systems can share a PARMLIB member containing TAPEREQ, VOLATTR, or UNITATTR statements for different releases of HSC. If entered from the console, message SLS0018I is issued.
PAGE 166
UNITATTR Unit Attribute (UNITATTR) Control Statement The UNITATTR statement specifies unit attributes and allows the user to define the model number of transports. A series of UNITATTR statements can be specified and are contained in the definition data set named in the UNITDEF statement. The first statement that matches the requested attributes is used. (Refer to “Unit Attribute Definition (UNITDEF) Command and Control Statement” on page 140 for details on syntax and parameters.
PAGE 167
UNITATTR Syntax UNITATTR UNITATTR ADDRess( ADDRess( unit-address unit-address unit-address-range unit-address-range , , unit-address-list unit-address-list ) ) MODel( MODel( 4480 4480 4490 4490 9490 9490 9490EE 9490EE SD3 SD3 9840 9840 984035 984035 T9840B T9840B T9840B35 T9840B35 T9840C T9940A T9840C35 T9940A35 T9940A T9940B T9940A35 IGNORE T9940B T9940B35 ) ) IGNORE NETHOST(host-id) NETHOST(host-id) Control Statement Name UNITATTR initiates the UNITATTR control statement.
PAGE 168
UNITATTR MODel optionally, specifies the model number of a tape transport. Notes: 1. If the model specified does not match that reported by the LMU, an error results which causes all UNITATTRs to be rejected. 2. The SL8500 library supports only the T9x40 (9840/T9840B/T9840C and T9940A/T9940B) model types. 4480 indicates a 4480 (18-track) tape transport. 4490 indicates a 4490 (36-track Silverton) tape transport. 9490 indicates a 9490 (36-track Timberline) tape transport.
PAGE 169
UNITATTR T9940B35 indicates a 3590-image T9940B transport. IGNORE indicates a nonexistent physical transport. Note: IGNORE cannot be specified for a device that actually exists inside the library. HSC validates that UNITATTR models, if specified, match those reported by the LMU. If they do not, all UNITATTRs are rejected. NETHOST optionally, indicates a parameter used by LibraryStation. If this parameter is specified, the HSC ignores the entire UNITATTR statement.
PAGE 170
UNITDEF Unit Attribute Definition (UNITDEF) Command and Control Statement The UNITDEF command and control statement allows the user to specify the data set that contains the unit attribute (UNITATTR) statements. The UNITDEF statement can be specified in PARMLIB, or it can be issued as an operator command to dynamically load or reload unit attribute parameters. (Refer to ‘‘PARMLIB Control Statements’’ in the HSC Installation Guide for an explanation of PARMLIB.
PAGE 171
UNITDEF Syntax UNITDEF DATASET(dataset.name) DSN(dataset.name) , HOSTID( host-id VOLume(volser) UNIT(unitname) ) Control Statement Name UNITDEF initiates the UNITDEF control statement. Parameters DATASET or DSN specifies the name of the data set containing the UNITATTR statements to be processed and, optionally, an OPTion TITLE statement. (Refer to “Unit Attribute (UNITATTR) Control Statement” on page 136 and “OPTion TITLE Control Statement” on page 113 for details on syntax and parameters.
PAGE 172
UNITDEF HOSTID (This parameter is valid only for use in PARMLIB, so that multiple systems can share a PARMLIB member containing TAPEREQ, VOLATTR, or UNITATTR statements for different releases of HSC. If entered from the console, message SLS0018I is issued.) Optionally, limits the execution of this control statement to the specified hosts. If one of the specified hostids matches the host executing this control statement, the control statement is executed for that host. Otherwise, it is ignored.
PAGE 173
VOLATTR Volume Attribute (VOLATTR) Control Statement The VOLATTR control statement is used to specify tape volume attributes. VOLATTR statements are read from the definition data set specified by the VOLDEF command. (Refer to “Volume Attribute Definition (VOLDEF) Command and Control Statement” on page 154 for details on syntax and parameters.) The VOLATTR statement must be placed in the definition data set; it cannot be issued as an operator command. Notes: 1.
PAGE 174
VOLATTR If you enter any VOLATTR statement that globally defaults to all volumes (i.e., VOLATTR SER(*) REC(18)), you must precede this statement with VOLATTRs specifying the cleaning cartridges for each type of transport defined in the ACS. Cleaning cartridges for longitudinal drives should be defined as MED(S); for helical drives, MED(DD3D); for 9840 drives, MED(STK1U).
PAGE 175
VOLATTR Syntax VOLATTR SERial( volser vol-range , vol-list ) MEDia( Standard CST ) MEDIA1 STD 1 3480 ECART E ECCST ETAPE Long MEDIA2 3490E ZCART Z DD3A DD3B DD3C DD3D STK1R STK1U R U STK2 STK2P STK2W This syntax diagram is continued on the next page. Chapter 3. HSC Control Statements and HSC Start Procedure 145 1st ed.
PAGE 176
VOLATTR Syntax (continued) RECtech( LONGItud 18track ) MAXclean(use-limit) 36track 36Atrack 36Btrack 36Ctrack HELical DD3 STK1R STK1R34 STK1R35 STK1RA STK1RA34 STK1RA35 STK1RB STK1RB34 STK1RB35 STK1RAB STK1RAB4 STK1RAB5 STK1RC STK1RC34 STK1RC35 STK2P STK2P34 STK2P35 STK2PA STK2PA34 STK2PA35 STK2PB STK2PB34 STK2PB35 Control Statement Name VOLATTR initiates the VOLATTR control statement. This statement applies to all cartridges including all types of cleaning cartridges.
PAGE 177
VOLATTR Parameters SERial specifies one or more volume serial numbers (VOLSERs) to which this definition applies. volser or vol-range or vol-list identifies a single VOLSER, a VOLSER range, or a list of VOLSERs and/or VOLSER ranges in any combination. This parameter may include the following wildcard characters: % or ? any single non-blank character. * any character string (length 0 to 6). The wildcard characters shown above may not be used in a range. Notes: 1.
PAGE 178
VOLATTR If this parameter is not specified, a default is chosen based on the value of the RECtech parameter. Table 7 shows default values used if MEDia is omitted. Table 7.
PAGE 179
VOLATTR • MEDIA2 • 3490E ZCART indicates a 3490E, extended capacity cartridge that provides greater storage capacity than an ECART. It can be used only on a 9490EE drive. ZCART can be abbreviated as Z. DD3A, DD3B, DD3C, DD3D indicates a helical cartridge. The media indicator in the external label is encoded with the cartridge type (A, B, C, or D). Note: DD3A, DD3B, DD3C, or DD3D can be abbreviated to A, B, C, or D, respectively.
PAGE 180
VOLATTR STK2P, STK2W indicates a T9940 cartridge. The media indicator in the external label is encoded with the cartridge type (P or W). Note: STK2P or STK2W can be abbreviated to P or W, respectively. Types of T9940 cartridges, along with their associated media capacities are: • STK2P — 60GB (T9940A) or 200GB (T9940B) • STK2W — cleaning cartridge. RECtech optionally, specifies the method used to record data tracks on the tape surface for the VOLSER designated in the SERial parameter.
PAGE 181
VOLATTR 36Btrack indicates a 9490 (Timberline) transport. 36Ctrack indicates a 9490EE transport. HELical indicates a device using helical recording. DD3 indicates a device using helical recording. STK1R indicates any 9840 or T9840B transport. STK1R34 indicates a 3490E-image 9840 or T9840B transport. STK1R35 indicates a 3590-image 9840 or T9840B transport. STK1RA indicates a 3490E or 3590-image 9840 transport. STK1RA34 indicates a 3490E-image 9840 transport. STK1RA35 indicates a 3590-image 9840 transport.
PAGE 182
VOLATTR STK1RC34 indicates a 3490-image T9840C transport. STK1RC35 indicates a 3590-image T9840C transport. STK2P indicates any T9940A transport. STK2P34 indicates a 3490E-image T9940A transport. STK2P35 indicates a 3590-image T9940A transport. STK2PA indicates a T9940A transport. STK2PA34 indicates a 3490E-image T9940A transport. STK2PA35 indicates a 3590-image T9940A transport. STK2PB indicates a T9940B transport. STK2PB34 indicates a 3490E-image T9940B transport.
PAGE 183
VOLATTR Notes: 1. If MAXclean is not specified in the VOLATTR statement, the value or default of the MAXclean parameter in the MNTD operator command is used for all cleaning cartridge counts. 2. If MAXclean is specified, the MEDia setting must be Standard, DD3D, STK1U, or STK2W. Example The following example illustrates how to use VOLATTR statements to specify volume attributes for particular VOLSERs.
PAGE 184
VOLDEF Volume Attribute Definition (VOLDEF) Command and Control Statement The VOLDEF command and control statement is used to specify the definition data set that contains volume attribute (VOLATTR) statements. (Refer to “Volume Attribute (VOLATTR) Control Statement” on page 143 for details on syntax and parameters.) The data set must be a sequential or a partitioned data set (PDS) with any valid record format (RECFM). Also, the data set must contain one or more VOLATTR statements.
PAGE 185
VOLDEF Syntax VOLDEF DATASET(dataset.name) DSN(dataset.name) , HOSTID( host-id VOLume(volser) UNIT(unitname) ) Control Statement Name VOLDEF initiates the VOLDEF command and control statement. Parameters DATASET or DSN specifies the name of the data set containing the VOLATTR statements to be processed and, optionally, an OPTion TITLE statement. (Refer to “Volume Attribute (VOLATTR) Control Statement” on page 143 and “OPTion TITLE Control Statement” on page 113 for details on syntax and parameters).
PAGE 186
VOLDEF UNIT specifies the unit where the definition data set is located. unitname specifies the unit name. If the definition data set is not cataloged and this parameter is omitted, a unit name of SYSALLDA is the default. HOSTID (This parameter is valid only for use in PARMLIB, so that multiple systems can share a PARMLIB member containing TAPEREQ, VOLATTR, or UNITATTR statements for different releases of HSC. If entered from the console, message SLS0018I is issued.
PAGE 187
Creating an SLKJCL File for Starting the HSC An SLKJCL file must be created on the ACS191-disk. The ACS INIT command submits the SLKJCL file. This loads the nucleus of the HSC into main storage, instructs the SCP to allocate data sets, and invokes the library host software initialization routine. Note: Refer to “EXECParm Control Statement” on page 90 for an alternative method of specifying GTF Eid and Fid parameters. Also, see ‘‘HSC Initialization Parameters’’ and ‘‘HSCPARM’’ in the HSC Installation Guide.
PAGE 188
SSYS specifies that HSC initialization search for the subsystem name specified. If SSYS is specified, the name must match the LIBSUBSYS parameter value in the system profile (SYSPROF). If the name is not found or is not a valid name, the subsystem terminates. subsystem must be a 1- to 4-character name or problems can occur when initializing the HSC. This parameter permits you to symbolically specify the subsystem if the job name in the startup SLKJCL file does not match the subsystem name.
PAGE 189
This parameter should only be used in extreme situations and may not correct all error conditions. Contact StorageTek Software Support before using this parameter. Eid xxxx is 1 to 4 hex characters specifying the GTF event ID used for the duration of this subsystem. ‘‘E’’ is the abbreviation for this parameter. The default Eid value is E086. Fid xx is 1 to 2 hex characters specifying the GTF format ID used for the duration of this subsystem. ‘‘F’’ is the abbreviation for this parameter.
PAGE 190
HSC Startup Job (ACS SLKJCL) Perform the steps in the following procedure to create the job file to be used to start the library subsystem. It is later invoked in an AUTOJOB statement in the ACS SYSPROF file. 1. Log on to MAINTSTK. 2. Issue the command: ACS UTIL HSCINIT (NOSEND 3. When XEDIT displays the file, modify it as desired. a. If the PARMLIB data set is shared with other hosts, specify the data set information and delete the remaining lines. or b.
PAGE 191
Example The following listing is an example job for the ACS INIT command.
PAGE 192
Notes: 1. The job name in the startup SLKJCL file must match the subsystem name specified with the LIBSUBSYS parameter in the SYSPROF or it must be specified with the SSYS parameter in the /PARM statement. Refer to “SSYS” on page 158 for more information. 2. Control data sets are defined using the CDSDEF control statement. The CDSDEF statement must be present in your PARMLIB definitions. Control and journal data sets may no longer be defined in JCL.
PAGE 193
Starting HSC Execution Initialize the HSC. Refer to “Starting the HSC” on page 165 for information about how to start execution of the HSC. Note: The subsystem name specified with the LIBSUBSYS parameter in the SYSPROF must match the jobname in the startup SLKJCL file or it must be specified with the SSYS parameter in the /PARM statement. Refer to “SSYS” on page 158 for more information.
PAGE 194
In these cases, the affected ACS(s) is forced offline. The HSC continues to support the unaffected ACS(s). While the unaffected ACS(s) remains online, the mismatched configuration can be corrected. If the hardware configuration is incorrect, the affected ACS(s) can then be brought online. Otherwise, the configuration can be changed through the LIBGEN/SLICREAT/Reconfiguration process at your convenience. Multiple Hosts Startup Considerations In a multiple-host configuration, start one host at a time.
PAGE 195
Starting the HSC The HSC software can be initialized in three ways: • Start the ACS service machine via the CP AUTOLOG command. • Issue the ACS INIT command from the service machine virtual console. • Submit the HSC startup SLKJCL to the ACS service machine, if the SCP is already executing but without the HSC.
PAGE 196
Initializing the HSC to the Full Service Level Normally, HSC software is initialized to the full service level when it is started. The syntax for the commands used to initialize the HSC to the full service level is shown below. Syntax for Initializing HSC to Full Service Level AUTOLOG svmname pswd - or ACS INIT - or ACS SUBMIT strtjclfn strtjclft strtjclfm libclass AUTOLOG svmname pswd - or - ACS INIT - or - ACS SUBMIT strtjclfn strtjclft strtjclfm libclass. 166 VM/HSC 6.
PAGE 197
Initializing the HSC to the Base Service Level HSC software can be started to the base service level by adding the BASE parameter on the /PARM statement of the startup SLKJCL, this includes specifying it on the ACS INIT or ACS SUBMIT commands. When using the CP AUTOLOG command, the BASE parameter must be specified on an existing /PARM statement in the startup SLKJCL. The BASE parameter can be used with other parameters on the /PARM statement.
PAGE 198
168 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 199
Chapter 4. Utility Functions Overview of Library Utilities The HSC contains utility functions that provide you with ways to manage library resources. Primary utility functions include: • • • • library CDS maintenance control of library cartridges control of scratch volumes preparation of reports covering library activity. Table 9.
PAGE 200
• The ACS UTIL exec can be used to generate a template for all required SLKJCL and control statements for any utilities requested, and is recommended for beginners. Selecting a Utility There are many utilities described within this chapter. If you know what function you want to perform, find that function in Table 10. The applicable utility for each specific function is contained in the table. Table 10.
PAGE 201
Table 10.
PAGE 202
Typical Use of Utilities A typical use of utility functions might be, for example, to enter some cartridges into the library through the CAP using the Enter Cartridges utility, add scratch volumes to the CDS by invoking the Scratch Update utility, and run the Volume Report utility to determine the physical location of volumes in an LSM.
PAGE 203
The Volume Report utility executes in the SCP batch job environment in CMS, or in stand-alone mode in the POST/SAE environment. Stand-alone mode allows the administrator to locate backup tapes when the ACS service machine cannot be started due to the loss of a critical DASD data set. Control Statement Syntax Conventions The control statement for each utility program consists of a command (indicating the utility function) followed by parameters, as applicable, in 80-character card-image records.
PAGE 204
ACS UTIL Exec The most convenient way for a beginner to run the utilities is to use the ACS UTIL exec. When provided with the names of the utilities to be executed, the ACS UTIL exec builds a file containing the control statements required to execute these utilities in the appropriate SCP or CMS environment. The file is then displayed for editing by the user who must then fill in, or change the supplied template parameters.
PAGE 205
SET Change library configuration information SLICREAT Library control data set creation SLIMDisk Allocate an OS-format data set on a minidisk SLIVInt Initialize a volume in OS format SLSBINIT Create HSC startup job SLUACtv Activity distribution report SLUETRac Format trace records SLUPErf Reblock performance log data TRAce Format execution trace data UNSCratch Change volumes to non-scratch status UNSElect Unselect a volume that was left selected by HSC VOLRpt Volume location report C
PAGE 206
5. Enter the XEDIT command FILE. The file ACSCMS EXEC A is then executed to run the utility, and the ACSCMS exec remains on the caller’s A-disk. SCP Environment For utilities that run in the SCP environment, job statements for the requested utilities are constructed from parameters in the system profile (ACS SYSPROF). Parameter statement templates are presented for the caller to edit. Only noncomment statements are processed further.
PAGE 207
JCL and Control Statements Although the ACS exec can generate a template job file, the utility control statements (and possibly the SCP JCL) must be modified by the user. To do this the user should have some understanding of the format and function of these statements. SCP Batch Job Control Language (JCL) The function of the SCP Job Control Language is to provide enough information to the SCP to execute the requested utility within the SCP batch job environment.
PAGE 208
/PARM Statement The /PARM statement supplies parameters for the program (pgmname). These parameters and their format are program dependent. There may be only one /PARM statement per job. If supplied, it must immediately follow the /JOB statement. /PARM parms parms the parameters to be passed. Note: Mixed case parameters will not be forced to uppercase. /COMM Statement A /COMM statement is a comment statement. It may be used only before or after /FILE statements.
PAGE 209
Submitting Jobs Jobs may be submitted to the ACS service machine in several ways. 1. One method is to use ACS EXEC. This method does not require that the sender knows the protocol or the name/node of the ACS service machine. It is the recommended technique. EXEC ACS SUBMIT fname ftype fmode class fname the CMS filename of the job file. ftype the CMS filetype of the job file. If omitted, it defaults to ‘SLKJCL’. fmode the CMS filemode of the job file. If omitted, it defaults to ‘‘*’’.
PAGE 210
Utility Control Statements Control Statements vs. JCL In contrast to the SCP Job Control Language, the utility control statements are processed only by the executed utility, not by the SCP. They supply all the specific parameters required to execute a utility program (that is, function, cartridge VOLSER, location, etc.). Briefly then, a control statement consists of a command (indicating the utility function) followed by zero or more parameters in 80 column card-image records.
PAGE 211
Utility Administrator (SLUADMIN) The SLUADMIN program operates as a batch job and controls initialization processing for most utility functions. The utility administrator (SLUADMIN) can accept multiple control statements which are handled as serial requests for multiple utilities. If all requirements needed to execute the utility function are met, control is passed to the appropriate program which handles the actual processing.
PAGE 212
How to Invoke Utility Programs For convenience, most utility programs are packaged to appear as a single, user-invoked program. The Performance Log Reblocker utility is an exception. All other utility functions are invoked as a normal batch job using the SLUADMIN program and user-specified control statements needed to invoke the required utility function.
PAGE 213
Reports Created by Utilities Several utilities produce reports when executed. The reports are in addition to the utility function. Utilities that produce reports include: • • • • • Activities Report AUDit BACKup MOVe Volume Report. A description of each utility and resulting report is contained in this chapter. Report Headings Utilities provide reports at the end of execution.
PAGE 214
DATE=2YR Specifies that all dates displayed in report detail lines are in the ‘‘mm/dd/yy’’ format. A yy value of 71 or greater indicates a 20th century (19xx) date. A yy value of 70 or less indicates a 21st century (20xx) date. To avoid confusion, you are encouraged to use the DATE=4YR parameter setting described below. DATE=4YR Specifies that all dates displayed in report detail lines are in the ‘‘yyyymmdd’’ format. This is the default.
PAGE 215
Stand-Alone Utilities Most of the utility functions require the Host Software Component (HSC) to be up and functional. Some utilities run stand-alone, in the sense that they perform no dialogues with other HSC components, but they do require the VM Operating System to be available and some require the SCP to be running. These stand-alone utilities are: • Activities Report • BACKup • Database Decompile • Directory Rebuild • Journal Offload • RESTore, which requires the HSC to be quiesced • Volume Report.
PAGE 216
Activities Report Activities Report Utility The Activities Report utility provides you with information to analyze library resource loading by volume groups (for example, scratch compared to nonscratch, mounted, dismounted, entered, and ejected). This report provides the information necessary for analyzing and possibly redistributing library resources. You specify the time period to be reported against. The utility executes in the CMS environment using the SLUACTV exec.
PAGE 217
Activities Report PARM parameters to the SLUADMIN program that drive the utility. MIXED specifies that output is to be mixed case. The default is uppercase. NOHD specifies that page headers are not to be printed. The default is to print page headers. SLSCNTL vaddr DSN dsname specifies the name of the library’s primary control data set (dsname). The default is obtained from the ACS SYSPROF file. The caller must have the volume it is on accessible as the given device address (vaddr).
PAGE 218
Activities Report Syntax ACTIvities Optional Parameters Optional Parameters: BEGIN( TODAY begin-date TODAY 23:59:59 END( end-date end-time , 00:00:00 begin-time Utility Name ACTIvities specifies that an activities report is to be produced. Parameters BEGIN optionally specifies the beginning of the period for the activities analysis. begin-date begin-date specifies the starting date of the analysis, expressed in mm/dd/yy or yyyymmdd format.
PAGE 219
Activities Report Examples: In each of the following examples, activity reporting begins on October 27, 1997 at midnight. BEGIN(10/27/97,00:00:00 BEGIN(19971027,00:00:00) BEGIN(TODAY,00:00:00) BEGIN(,00:00:00) END optionally specifies the end of the period for the activities analysis. end-date end-date specifies the ending date of the analysis, expressed in mm/dd/yy or yyyymmdd format. If begin-date is specified, end-date must be in the same format.
PAGE 220
Activities Report Invoking the Activities Report Utility To invoke the Activities Report utility in VM, enter: EXEC ACS UTIL ACTIVities Execution of the statement results in the following ACSCMS EXEC file: ACSCMS EXEC &TRACE ALL * EXEC SLUACTV To execute the ACTIvities utility: 1. Remove the comment indicator (*) on the left, and specify the name of the control file to be used to specify the actual utility parameters. 2.
PAGE 221
Activities Report Cartridge Movement Statistics - Move Section of the Report In the first section of the report, the Move section, the HSC provides two summary lines: • The first summary line lists from 1 to 16 SMF system IDs found in the SMF records input to the utility. • The second summary line lists the SMF record type being reported, the total number of SMF records, and the date (mm/dd/yy or yyyymmdd) and time (hh:mm:ss) of the earliest and latest SMF record found matching the duration criteria.
PAGE 222
Activities Report All ‘‘-same LSM’’ subcategories report moves which have the source and destination of the move in the same LSM. All ‘‘-diff LSM’’ subcategories report moves which have the source and destination of the move in different LSMs. % of all is the percent of move operations represented by the category or subcategory found in SMF input matching the duration criteria.
PAGE 223
Activities Report Earliest is the date (mm/dd/yy or yyyymmdd) and time (hh:mm:ss) of the earliest SMF record found matching the category being reported for the duration requested. Latest is the date (mm/dd/yy or yyyymmdd) and time (hh:mm:ss) of the last SMF record found matching the category being reported for the duration requested. Usage Notes 1. Only cartridge moves involving a CAP or a transport are reported. Cell to cell moves such as those used by the Scratch Redistribution utility are not reported.
PAGE 224
Activities Report 7. As the HSC attempts to float dismounts to a nearby LSM, there should be less pass-thru activity on dismounts than on mounts. However, to float cartridges, free cells must be available. Ejects also may incur more pass-thru activity than enters because the HSC attempts to place entered cartridges into the same LSM as the entry CAP. Ejected cartridges may take numerous pass-thru operations to move from their home cell to the preferred CAP. 8.
PAGE 225
Activities Report Overall ACS Statistics - ACS Section of the Report For the ACS section of the Activities report, ACS statistics are reported under the following report headings: ACS ID is the ACS number of the ACS being reported, the number of SMF records, and the earliest and latest SMF record date (mm/dd/yy or yyyymmdd) and time (hh:mm:ss) found matching the Activities Report verbs duration specification. LSM the LSM numbers are listed across the page.
PAGE 226
Activities Report Usage Notes 1. Merging multi-host HSC SMF records impacts the LSM ARM USE statistic as described above. However, not merging multi-host HSC SMF records affects the number of pass-thrus reported, as this is only the number of pass-thru operations occurring during the hosts LMU interval. 2. LSM ARM USE should never be reported higher than 100 percent.
PAGE 227
Activities Report SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility TIME hh:mm:ss PAGE 0001 Control Card Image Listing DATE yyyy-mm-dd ACTIVITIES BEGIN(20040301) SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility TIME hh:mm:ss PAGE 0002 Activities Begin 2004-03-01 DATE yyyy-mm-dd SYSTEM IDS: HSC1 HSCH HSCF HSCE HSC6 HSC2 SMF RECORD TYPE: 245 TOTAL RECORDS: 1,580 TOTAL ALL MOUNTS: SCRATCH 346 % OF ALL 22.4 SEC. 19.7 SEC.
PAGE 228
Audit Audit Utility The Audit utility provides the user the ability to perform a physical inventory of library volumes and to optionally update the library control data set to reflect all observed changes in cell storage for the specified component(s).
PAGE 229
Audit You can specify whether or not the library control data set is updated as a result of audit, or if only the discrepancy listing is produced by the parameters chosen. • If the APPly(YES) is specified, the library control data set is updated to reflect all observed contents in cell storage. A discrepancy listing is also produced. Duplicate VOLSERs and cartridges with unreadable or illegal external labels are ejected from the LSM.
PAGE 230
Audit • If the media value is unreadable by the LMU (recorded in the CDS), the HSC issues a warning message. • If the media value is unreadable by the LMU (not recorded in the CDS), the HSC issues a warning message. In both of these cases (APPLY(NO) or APPLY(YES)), the audit continues.
PAGE 231
Audit After the Audit ejects volumes from the current panel, a write-to-operator with reply (WTOR) is issued allowing the operator to keep or release the CAP. If the operator responds with a ‘‘K’’, the CAP remains allocated for the duration of the Audit. If the operator responds ‘‘R’’, the CAP is released so that it may be allocated to another operation. If another volume is to be ejected, the Audit again acquires the CAP and the keep/release dialog is repeated.
PAGE 232
Audit Syntax AUDIt ALL ACS(acs-id) Optional Parameters APPLy( YES NO ) Optional Parameters: LSM(lsm-list) PANel(panel-list) ROW(row-list) COLumn(column-list) CAP(cap-id) EMPTYCel DIAGScan( ONLY ) ALSO INTRANs Utility Name AUDIt specifies that an audit operation is to be performed. Parameters ALL specifies that the total library is to be audited.
PAGE 233
Audit LSM optionally specifies that only certain LSMs within the specified ACS are to be audited. (lsm-list) An lsm-list can be a single LSMid or a list of LSMids. An LSMid (lsm-id) is made up of the ACSid (hexadecimal 00-FF) and the LSM number (hexadecimal 00-17) separated by a colon (:). An LSM range is not allowed. If a list is specified, the elements must be separated by blanks or commas, and the entire list enclosed in parentheses.
PAGE 234
Audit ROW optionally specifies that only certain rows within the specified LSM panel are to be audited. (row-list) row-list may be a single row or a list of rows. Ranges are not allowed. If a list is specified, the elements must be separated by blanks or commas, and the entire list enclosed in parentheses. If this parameter is specified, the LSM and PANel parameters may contain only one element. A row-list element is a one or two digit decimal number.
PAGE 235
Audit • For 4410 and 9310 LSMs, valid column entries are 0 though 23, left to right, for outside wall panel columns. Inner wall panels are numbered 0 through 19, right to left. • For 9360 (WolfCreek) LSMs, columns 0 through 5 can be specified. • For 9740 LSMs, valid column entries are 0 through 3 for panels 0, 2, and 3 (if the optional cells are present); 0 through 2 for panel 1. • For SL8500 libraries, valid column entries are 0 through 1 for each panel type.
PAGE 236
Audit Note: If a CAP is not specified, a CAP in the identified ACS is selected based on the CAPPref operator command (refer to the ‘‘CAP Preference (CAPPref) Command and Control Statement’’ in the HSC Operator’s Guide). Multi-ACS audits cannot specify the CAP parameter. A CAP is chosen for each ACS based upon CAP preference values. EMPTYCel optionally specifies that only empty cells are to be audited. This parameter can be used in combination with all other AUDIt parameters except DIAGScan(ONLY).
PAGE 237
Audit INTRANs optionally specifies that in-transit cartridges in an LSM are to be processed. All in-transit cartridges, except those identified in the note below, are read and ejected as part of an AUDIt utility operation. Notes: 1. INTRANs is mutually exclusive with the APPLY(NO) parameter. It can be used in combination with all other AUDIt parameters. 2. Only the first two cells (columns 0 and 1) in a 9310 playground are accessible to an in-transit audit.
PAGE 238
Audit 3. Specify values for the desired parameters. 4. Delete the parameters that are not desired. 5. Enter the command ‘‘FILE.’’ The job file is then submitted to the ACS service machine for execution. JCL Examples The following example shows JCL for auditing an entire library (all ACSs). JCL for Audit of Entire Library (all ACSs) /JOB /PARM /FILE /FILE AUDIT jobname MIXED SLSPRINT SLSIN ALL SLUADMIN DEV PRNT CLASS A * The following example shows JCL for a selective audit of a single ACS and two LSMs.
PAGE 239
Audit JCL for Selective Audit of Empty Cells //JOBAUDT job (account),programmer //S1 EXEC PGM=SLUADMIN,PARM=MIXED //SLSPRINT DD SYSOUT=A //SLSIN DD * AUDIT ACS(00) LSM(01) EMPTYCELL /* // JCL for Selective Audit of Diagnostic Cells Only /JOBAUDT job (account),programmer //S1 EXEC PGM=SLUADMIN,PARM=MIXED //SLSPRINT DD SYSOUT=A //SLSIN DD * AUDIT ACS(00) LSM(02) DIAGSCAN(ONLY) /* // JCL for Selective Audit that Includes Diagnostic Cells /JOBAUDT job (account),programmer //S1 EXEC PGM=SLUADMIN,PARM=MIXED
PAGE 240
Audit SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility TIME hh:mm:ss Control Card Image Listing PAGE 0001 DATE yyyy-mm-dd AUDIT ACS(00) LSM(11) SLUADMIN (n.n.
PAGE 241
Backup Backup Utility The BACKup utility allows you to back up the library control data set. The control data set is the single most important resource required in the operation of the HSC. Various controls and services are available to keep the control data set intact and to enable you to recover the data set from a total failure. Features such as shadowing, journaling, backup, and restore, are all intended to provide for the integrity of the control data set.
PAGE 242
Backup How the BACKup Utility Functions The BACKup utility performs extensive error checking on CDS records, as well as comparison checking between primary and secondary copies of the CDS. Note: In order to run a back up correctly, all data sets currently defined to the HSC should be specified. This ensures that proper CDS selection and reservation occurs.
PAGE 243
Backup Backup Procedure Backup of the control data set may be performed using conventions for specifying the secondary control data set and with copy data sets to enable block analysis, if desired. The following procedure describes steps for performing backups (see “JCL Examples” on page 247 for each step). 1. If OPTion(Analyze) is specified, allocate the SLSCOPY1 and SLSCOPY2 data sets. This step is not necessary if you specify OPTion(Copy).
PAGE 244
Backup • Avoid running the SET utility. • Avoid running the Scratch Update and Scratch Redistribution functions during this time. • Take all HSCs down prior to the link being restored. Special considerations after the link is restored include: • Avoid restoring CDS copies from backups taken while the link is down. If a restore of the CDS(s) is necessary only on one side of the link, make sure that only the CDS(s) on that side is restored.
PAGE 245
Backup For regularly scheduled backups of HSC control data sets, do not specify the CDS keyword when each CDS copy is not being backed up individually in the same time frame. The reason for not specifying the CDS keyword is that a CDS switch(es) may have taken place. (Primary) specifies that the primary control data set is to be copied to the SLSBKUP data set. (Secondary) specifies that the secondary control data set is to be copied to the SLSBKUP data set.
PAGE 246
Backup summary report and to the SLSBKUP data set. Refer to Figure 11 on page 222 to see a sample discrepancy report. An errant and in-transit destination report, followed by a block processing report, also is produced in this case. Figure 11 shows these reports. Note: The VOLSERs and cell locations that are discrepant are sorted into an incremental stack to reduce the amount of robotic movement.
PAGE 247
Backup JCL Requirements The following definitions apply to the BACKup utility JCL: SLSPRINT the message output data set. SLSCNTL the primary control data set. This statement must be provided. SLSCNTL2 the secondary control data set. If a secondary CDS exists, it should be specified so that if a switch occurs and the secondary data set is now active, the CDSs can be reordered to maintain database integrity. SLSBKUP the created backup data set. SLSSTBY the standby data set.
PAGE 248
Backup Invoking the BACKup Utility The easiest way to run utilities is to execute the ACS UTIL exec by entering the following command: EXEC ACS UTIL BACKUP Execution of the statement results in the ACSUTIL SLKJCL file: ACSUTIL SLKJCL File /JOB jobname SLUADMIN /PARM MIXED /FILE SLSPRINT DEV PRNT CLASS A /FILE SLSCNTL DEV DSN /FILE SLSCNTL2 DEV DSN /FILE SLSBKUP DEV DSN /FILE SLSCOPY1 DEV DSN /FILE SLSCOPY2 DEV DSN /FILE SLSJRN01 DEV DSN /FILE SLSJRN02 DEV
PAGE 249
Backup JCL Examples Various examples showing JCL for running the BACKup utility are presented. Select an appropriate example matching the control statement conventions that you have used for specifying data sets. JCL for Running Backup The first example shows JCL for backup with the primary, secondary, and standby control data sets, copy data sets (SLSCOPY1 and SLSCOPY2), and journals.
PAGE 250
Backup This example specifies BACKup with the SLSCNTL statement to identify the primary control data set. Backup is processed without a secondary control data set and journals. JCL for Backup of the Primary CDS without Secondary and Journals /JOB jobname /PARM MIXED /FILE SLSBKUP /FILE SLSCNTL /FILE SLSPRINT /FILE SLSIN BACKUP SLUADMIN DEV vaddr DSN backup.set.name DEV vaddr DSN primary.set.
PAGE 251
Backup • a condition code from backup processing: 0 no errors and no SLUADMIN control cards generated 4 warning MESSAGES – Backup successful 8 a system failure occurred. Restart or rerun backup. Chapter 4. Utility Functions 221 1st ed.
PAGE 252
Backup SLUADMIN (n.n.n) TIME hh:mm:ss STORAGETEK AUTOMATED CARTRIDGE SYSTEM UTILITY CONTROL CARD IMAGE LISTING PAGE 0001 DATE yyyy-mm-dd STORAGETEK AUTOMATED CARTRIDGE SYSTEM UTILITY BACKUP UTILITY PAGE 0002 DATE yyyy-mm-dd BACKUP OPTION(ANALYZE) SLUADMIN (n.n.n) TIME hh:mm:ss SLS1315I SLS1212I SLS1216I SLS1215I SPRC.@793665.V6L.
PAGE 253
Backup SLUADMIN (n.n.
PAGE 254
Backup How to Restart Backup After executing the BACKup utility, if a system failure or any other circumstance occurs that causes a return code of eight (RC=8), the BACKup utility can be restarted as long as criteria described in “Parameters” on page 214 for OPTion(Restart) is true. Related Utilities The RESTore utility complements the BACKup utility. If a restore is required, it should be performed immediately after a CDS failure.
PAGE 255
Database Decompile Database Decompile (LIBGEN) Utility The Database Decompile utility provides a way to generate LIBGEN macro statements from an existing library control data set. Prerequisites The utility runs under the control of the SLUADMIN program and does not require the HSC to be running.
PAGE 256
Database Decompile Syntax LIBGEN Utility Name LIBGEN specifies that database processing is to be performed and invokes the SLUDBMAP module. SLUDBMAP creates a complete HSC LIBGEN from an existing control data set. Parameters None. JCL Requirements The following definitions apply to the LIBGEN utility JCL: SLSPRINT output messages from the utility program. SLSCNTL the primary control data set. This statement is required. Note: SLSCNTL should be the copy of the CDS currently selected as the primary CDS.
PAGE 257
Database Decompile Invoking the Database Decompile Utility The easiest way to run utilities is to execute the ACS UTIL exec by entering the following command: EXEC ACS UTIL LIBGEN Execution of the statement results in the ACSUTIL SLKJCL file: ACSUTIL SLKJCL File /JOB jobname /PARM MIXED /FILE SLSPRINT /FILE SLSCNTL /FILE SLSLIBGN /FILE SLSIN * LIBGEN SLUADMIN DEV PRNT CLASS A DEV <500> DSN DEV PNCH CLASS A * To execute the utility: 1.
PAGE 258
Database Decompile Output Description Outputs resulting from the execution of the Database Decompile utility include: • a valid LIBGEN file matching the existing control data set. The output file has the following characteristics: - All station and drive addresses are 4-character addresses. - In cases where multiple parameters point to the same label statement, the utility duplicates the statement with a unique label and points each parameter to a different, although identical statement.
PAGE 259
Database Decompile *********************************************************************** * THIS IS A LIBGEN OF A SINGLE ACS WITH 24 POWDERHORN LSMS ATTACHED * * TO 16 HOSTS.
PAGE 260
Database Decompile * LSM0002 * P000002 SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM0000,LSM0001,LSM0003,LSM0004), DRIVE=(10), DRVELST=(P00002), TYPE=9310, DOOR=ECAP X X X X X SLIDLIST HOSTDRV=(D0000002,D0000002,D0000002,D0000002, D0000002,D0000002,D0000002,D0000002,D0000002, D0000002,D0000002,D0000002,D0000002,D0000002, D0000002,D0000002) X X X * D0000002 SLIDRIVS ADDRESS=(0A08,0A09,0A0A,0A0B) * *---------------* LSM0003 SLILSM PASTHRU=((8,S),(6,S),(4,M),(2,M)), ADJACNT=(LSM0001,LSM0002,LSM
PAGE 261
Database Decompile * LSM0006 * P000006 SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM0004,LSM0005,LSM0007,LSM0008), DRIVE=(10), DRVELST=(P000006), TYPE=9310, DOOR=ECAP X X X X X SLIDLIST HOSTDRV=(D0000006,D0000006,D0000006,D0000006, D0000006,D0000006,D0000006,D0000006,D0000006, D0000006,D0000006,D0000006,D0000006,D0000006, D0000006,D0000006) X X X * D0000006 SLIDRIVS ADDRESS=(0A18,0A19,0A1A,0A1B) * *---------------* LSM0007 SLILSM PASTHRU=((8,S),(6,S),(4,M),(2,M)), ADJACNT=(LSM0005,LSM0006,LS
PAGE 262
Database Decompile * LSM000A * P00000A SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM0008,LSM0009,LSM000B,LSM000C), DRIVE=(10), DRVELST=(P00000A), TYPE=9310, DOOR=ECAP X X X X X SLIDLIST HOSTDRV=(D000000A,D000000A,D000000A,D000000A, D000000A,D000000A,D000000A,D000000A,D000000A, D000000A,D000000A,D000000A,D000000A,D000000A, D000000A,D000000A) X X X * D000000A SLIDRIVS ADDRESS=(0A28,0A29,0A2A,0A2B) * *---------------* LSM000B SLILSM PASTHRU=((8,S),(6,S),(4,M),(2,M)), ADJACNT=(LSM0009,LSM000A,LS
PAGE 263
Database Decompile * LSM000E * P00000E SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM000C,LSM000D,LSM000F,LSM0010), DRIVE=(10), DRVELST=(P00000E), TYPE=9310, DOOR=ECAP X X X X X SLIDLIST HOSTDRV=(D000000E,D000000E,D000000E,D000000E, D000000E,D000000E,D000000E,D000000E,D000000E, D000000E,D000000E,D000000E,D000000E,D000000E, D000000E,D000000E) X X X * D000000E SLIDRIVS ADDRESS=(0A38,0A39,0A3A,0A3B) * *----------------* LSM000F SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM000D,LSM000E,L
PAGE 264
Database Decompile * LSM0012 * P000012 SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM0010,LSM0011,LSM0013,LSM0014), DRIVE=(10), DRVELST=(P000012), TYPE=9310, DOOR=ECAP X X X X X SLIDLIST HOSTDRV=(D0000012,D0000012,D0000012,D0000012, D0000012,D0000012,D0000012,D0000012,D0000012, D0000012,D0000012,D0000012,D0000012,D0000012, D0000012,D0000012) X X X * D0000012 SLIDRIVS ADDRESS=(0A48,0A49,0A4A,0A4B) * *---------------* LSM0013 SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM0011,LSM0012,LS
PAGE 265
Database Decompile * LSM0016 * P000016 SLILSM PASTHRU=((8,S),(6,S),(4,M)), ADJACNT=(LSM0014,LSM0015,LSM0016), DRIVE=(10), DRVELST=(P000016), TYPE=9310, DOOR=ECAP X X X X X SLIDLIST HOSTDRV=(D0000016,D0000016,D0000016,D0000016, D0000016,D0000016,D0000016,D0000016,D0000016, D0000016,D0000016,D0000016,D0000016,D0000016, D0000016,D0000016) X X X * D0000016 SLIDRIVS ADDRESS=(0A58,0A59,0A5A,0A5B) * *---------------* LSM0017 SLILSM PASTHRU=((2,S),(4,S)), ADJACNT=(LSM0015,LSM0016), DRIVE=(10), DRVELST=(P0000
PAGE 266
Directory Rebuild Directory Rebuild Utility The Directory Rebuild utility provides a means to rebuild the database directory for all defined CDS copies. Prerequisites The stand-alone Directory Rebuild utility: • runs under the control of the SLUADMIN utilities program • may be run while the CDS-related HSCs are STOPped • must be run using all CDS copies as input.
PAGE 267
Directory Rebuild SLSCNTL, SLSCNTL2, SLSSTBY SLSCNTL is the primary CDS, SLSCNTL2 is the secondary CDS, and SLSSTBY is the standby CDS from which the directory is rebuilt. This statement is required for each CDS that has been defined. SLSIN input to the utility in the form of control cards.
PAGE 268
Directory Rebuild JCL Example The following example shows JCL for Directory Rebuild execution. JCL for Directory Rebuild /JOB jobname /PARM MIXED /FILE SLSCNTL /FILE SLSPRINT /FILE SLSIN * DIRBLD SLUADMIN DEV 501 DSN SLS.
PAGE 269
Eject Cartridge Eject Cartridge Utility The EJECt Cartridge utility permits you to remove one or more cartridges from an ACS in a batch mode. For the automated ejection of cartridges, the EJECt Cartridge utility takes advantage of the Cartridge Access Port (CAP) in an LSM. The control statement allows you to designate a single CAP, a specific CAP, or a list of specific CAPs. Specifying one or more CAPs limits cartridge ejection to those CAPs.
PAGE 270
Eject Cartridge Eject Method 2 (continued): MEDia( Standard ) RECtech( 18track CST 36Atrack MEDIA1 36Btrack STD 36Ctrack 1 DD3 3480 STK1R ECART STK1R34 E STK1R35 ECCST STK1RA STK1RA34 STK1RA35 ETAPE Long MEDIA2 3490E ZCART Z DD3A DD3B DD3C STK1 STK1R R STK2 STK2P STK1RB STK1RB34 STK1RB35 STK1RAB STK1RAB4 STK1RAB5 STK1RC STK1RC34 STK1RC35 STK2P STK2P34 STK2P35 STK2PA STK2PA34 STK2PA35 STK2PB STK2PB34 STK2PB35 Utility Name EJECt specifies that ejection processing is to be performed.
PAGE 271
Eject Cartridge Parameters VOLser specifies that a VOLSER(s) is to be ejected. (vol-list) vol-list specifies the list of volumes to be ejected. A vol-list can be a single VOLSER, a range of VOLSERs or a list of VOLSERs and/or VOLSER ranges in any combination. If a list is specified, the elements must be delimited by commas or blanks, and the entire list enclosed in parentheses. A range of VOLSERs consists of a starting VOLSER and an ending VOLSER separated by a dash.
PAGE 272
Eject Cartridge • • • • • CST MEDIA1 STD 1 3480 ECART indicates a 3490E, extended capacity cartridge. It can be used only on a 36-track drive (4490, 9490, or 9490EE). Synonyms include: • • • • • • E ECCST ETAPE Long MEDIA2 3490E ZCART indicates a 3490E, extended capacity cartridge that provides greater storage capacity than an ECART. It can be used only on a 9490EE drive. ZCART can be abbreviated as Z. DD3A, DD3B, DD3C indicates a helical cartridge.
PAGE 273
Eject Cartridge STK2 indicates any T9940 cartridge. This parameter is the default for all T9940A and T9940B data cartridge types. STK2P indicates a T9940 data cartridge. The media indicator in the external label is encoded with the cartridge type (P). Note: STK2P can be abbreviated to P. RECtech optionally, specifies scratch cartridges of the desired recording technique are to be ejected. RECtech indicates the method used to record data tracks on the tape surface. 1.
PAGE 274
Eject Cartridge STK1R34 indicates a 3490E-image 9840 transport. STK1R35 indicates a 3590-image 9840 transport. STK1RA indicates a 3490E or 3590-image 9840 transport. STK1RA34 indicates a 3490E-image 9840 transport. STK1RA35 indicates a 3590-image 9840 transport. STK1RB indicates a 3490E or 3590-image T9840B transport. STK1RB34 indicates a 3490E-image T9840B transport. STK1RB35 indicates a 3590-image T9840B transport. STK1RAB indicates a 3490E or 3590-image T9840A or T9840B transport.
PAGE 275
Eject Cartridge STK2PA indicates a T9940A transport. STK2PA34 indicates a 3490E-image T9940A transport. STK2PA35 indicates a 3590-image T9940A transport. STK2PB indicates a T9940B transport. STK2PB34 indicates a 3490E-image T9940B transport. STK2PB35 indicates a 3590-image T9940B transport. CAP specifies which Cartridge Access Port(s) is being used for the operation. This utility ejects scratch volumes to the specified CAP(s) only.
PAGE 276
Eject Cartridge • For 9360 LSMs, the 20-cell WolfCreek CAP • For 9740 LSMs, fixed rack 14-cell or 10-cell removable magazine CAP • For SL8500 libraries, the CAP consists of 3, 13-cell removable magazines. 01 • For 4410 and 9310 LSMs, left-hand 40-cell enhanced CAP • For 9360 LSMs, the 30-cell WolfCreek optional CAP • For SL8500 libraries, this is an optional CAP consisting of 3, 13-cell removable magazines. 02 priority CAP (PCAP) for a 4410 or 9310 LSM enhanced CAP or for a 9360 LSM CAP.
PAGE 277
Eject Cartridge 4. Delete the parameters that are not desired. 5. Enter the command ‘‘FILE.’’ The job file is then submitted to the ACS service machine for execution. JCL Examples The following example shows JCL for ejecting a single volume from the library. JCL for Ejecting a Single Volume /JOB /PARM /FILE /FILE EJECT jobname SLUADMIN MIXED SLSPRINT DEV PRNT CLASS A SLSIN * VOLSER(A1B1C1) The following example shows JCL for ejecting one standard scratch cartridge.
PAGE 278
Eject Cartridge Output Description Output resulting from the execution of the EJECt Cartridge utility includes: • a listing of input commands, with appropriate messages, when syntax errors occur • messages associated with error conditions resulting from an unsuccessful attempt to execute ejection processing • a message indicating successful ejection processing (see Figure 13). SLUADMIN (n.n.
PAGE 279
Enter Cartridges Enter Cartridges Utility The Enter Cartridges utility permits you to batch enter cartridges into the library through the CAP. CAP Operating Instructions Operating instructions for the CAP are provided in the HSC Operator’s Guide. Note: When there are no more cartridges to be entered, open the CAP once again to ensure that no cartridges are present in the CAP cells, and then close the CAP to complete processing.
PAGE 280
Enter Cartridges 00 • For 4410 and 9310 LSMs, standard 21-cell CAP or the right-hand 40-cell enhanced CAP • For 9360 LSMs, the 20-cell WolfCreek CAP • For 9740 LSMs, fixed rack 14-cell or 10-cell removable magazine CAP • For SL8500 libraries, the CAP consists of 3, 13-cell removable magazines. 01 • For 4410 and 9310 LSMs, left-hand 40-cell enhanced CAP • For 9360 LSMs, the 30-cell WolfCreek optional CAP • For SL8500 libraries, this is an optional CAP consisting of 3, 13-cell removable magazines.
PAGE 281
Enter Cartridges To execute the utility: 1. Delete the lines in the template that are not required, or leave the comment indicator (*) in column one. 2. Remove the comment indicator from the desired lines. 3. Specify values for the desired parameters. 4. the parameters that are not desired. 5. Enter the command ‘‘FILE.’’ The job file is then submitted to the ACS service machine for execution. JCL Example The following example shows JCL for entering a cartridge(s) into a CAP.
PAGE 282
Enter Cartridges SLUADMIN (n.n.n) TIME hh:mm:ss StorageTek Automated Cartridge System Utility Control Card Image Listing PAGE 0001 DATE yyyy-mm-dd ENTER CAP(01) SLUADMIN (n.n.
PAGE 283
Journal Offload Journal Offload Utility The Journal Offload utility allows you to offload one or both of the journals on a given host without backing up the control data set. It is extremely important that you archive the offloaded journals, in the event that these journals are required for a restore operation. The HSC can be operational while the Journal Offload utility is executing. Syntax OFFLoad Utility Name OFFLoad specifies that a journal offload is to be performed. Parameters None.
PAGE 284
Journal Offload SLSOFF02 the created offload data set for the second journal (SLSJRN02). Note: The offload data sets created by SLSOFF01 and SLSOFF02 must be allocated on DASD. You can then copy the offloaded DASD data sets to tape if you desire. SLSIN input to the utility in the form of control statement card images.
PAGE 285
Journal Offload JCL Example The following example shows JCL for the offload of both journals. JCL for Offload of Journals /JOB jobname /PARM MIXED /FILE SLSCNTL /FILE SLSOFF01 /FILE SLSOFF02 /FILE SLSJRN01 /FILE SLSJRN02 /FILE SLSPRINT /FILE SYSPRINT /FILE SLSIN OFFLOAD SLUADMIN DEV DEV DEV DEV DEV DEV DEV * vaddr DSN vaddr DSN vaddr DSN vaddr DSN vaddr DSN PRNT CLASS PRNT CLASS control.set.name offload.file1 offload.file2 journal.file1 journal.
PAGE 286
Journal Offload SLUADMIN (n.n.n) TIME hh:mm:ss StorageTek Automated Cartridge System Utility Control Card Image Listing PAGE 0001 DATE yyyy-mm-dd OFFLOAD) SLUADMIN (n.n.
PAGE 287
Move Move Utility The MOVe utility permits you to request the HSC to move a single volume, a list of volumes, or a range of volumes to other locations within an ACS. MOVe Considerations You should be aware of the following considerations before attempting to use the MOVe utility: • Movement of volumes to all LSMs is done on a first-come first-served basis.
PAGE 288
Move Syntax MOVe Parameters Parameters: Flsm(lsm-id) Panel(panel-list) Row(row-list) Column(column-list) Volume(vol-list) TLsm(lsm-list) TPanel(panel) Utility Name MOVe specifies a move request. Parameters Flsm The ‘‘From’’ LSMid in the format ‘‘AA:LL’’ that the cartridges are to be moved from. If you designate the Flsm parameter, you may not designate the Volume parameter. (lsm-id) LSM identifier name. LSMs are specified as AA:LL, where AA is the ACSid and LL is the LSMid.
PAGE 289
Move (row-list) A one or two digit row number or list of row numbers. The maximum list allowed is four rows. However, this parameter cannot contain a list if a list was specified for the Column parameter. Ranges are not valid. Column list of Columns to be moved from. This parameter has a corequisite of the Row parameter and is optional. If this parameter is not specified, all columns will be moved for the rows specified. (column-list) A one or two digit column number or list of column numbers.
PAGE 290
Move JCL Requirements The following definitions apply to MOVe utility JCL: SLSPRINT output messages from the utility program. SLSIN input to the utility in the form of control cards.
PAGE 291
Move JCL Examples The following example shows JCL for moving a single volume from a panel to another panel within the same LSM. The example JCL moves a volume from LSM 00:01, Panel 08, Row 05, Column 02 to the same LSM (00:01) to Panel 09.
PAGE 292
Move SLUADMIN (n.n.n) TIME hh:mm:ss StorageTek Automated Cartridge System Utility Control Card Image Listing PAGE 0001 DATE yyyy-mm-dd MOVE FLSM(00:04) PANEL(00) TLSM(00:11) SLUADMIN (n.n.
PAGE 293
Performance Log Reblocker Performance Log Reblocker Utility The Performance Log Reblocker utility is used by sites sharing an ACS between MVS and VM hosts. The utility is used to reformat the VM performance log data to a common format similar to that of the MVS/SMF data. This data is then used as input for the Activities Report utility. The Performance Log Reblocker utility is required to reconstruct the original-image SMF data; different versions are provided to execute in the CMS and MVS environments.
PAGE 294
Performance Log Reblocker fmode the CMS filemode of the output file. The default is A2. (APPend specifies that the records from the reader file are appended to the specified CMS file if it exists.
PAGE 295
Performance Log Reblocker SET PERFLOG ON (CLASS class TO JOB AT mvsnode where: ON enables performance log recording class specifies the virtual spool file class to be used while transferring the spool file JOB specifies to transmit the virtual spool file as a job to the MVS system mvsnode specifies the node of the MVS system 3. The SMF parameters must be specified by the SCP SET PERFLOG command, which is normally included within the SYSPROF file.
PAGE 296
Reconfiguration Reconfiguration Utility The Reconfiguration utility is used as part of a four-stage process to create a new copy of the control data set when library hardware configurations change, such as the addition of drives or LSMs, but when information regarding the location of cartridges in the library must be retained from the original control data set. Note: This utility requires a 2.1-level CDS.
PAGE 297
Reconfiguration Since the LIBGEN macros define the various physical aspects of a library, most changes or modifications affecting the physical configuration of the library require that corresponding LIBGEN macro(s) be updated. Any update to the LIBGEN (except changes made via the SET utility) requires that a new library control data set be created.
PAGE 298
Reconfiguration • The old and new control data sets must be on volumes that are configured properly for real reserve/release to all hosts running HSC. (Refer to the IBM documentation for your environment.) • If it is necessary to copy the control data set to another minidisk, use the BACKup and RESTore utilities to ensure proper reset of database flags. How the Reconfiguration Utility Functions During a reconfiguration, volume information is copied from the old CDS to the new CDS.
PAGE 299
Reconfiguration (including all commands used when automated mounts or dismounts are necessary) need to be issued after the LSMs are brought online. Note: ALL new control data sets (primary, secondary, and standby) must conform to the library hardware. I/O Considerations Reconfiguration is I/O intensive. For this reason, it is highly recommended that you reduce the number of scratch volumes as much as possible to shorten reconfiguration time. Refer to “Minimizing I/O Time” on page 270 for more information.
PAGE 300
Reconfiguration Minimizing I/O Time Any or all of the following approaches will reduce reconfiguration time: • Using a solid state disk (SSD) device (such as StorageTek’s 4080) • Having no scratch tapes in the old CDS, rather than many scratch tapes Note: Reconfiguration to real DASD with many scratch volumes has been known to take hours of wall clock time. • Minimize I/O to the CDS copies by defining only the new primary CDS copy to RECONFIG.
PAGE 301
Reconfiguration 2. Identify any proposed changes to the host system’s Configuration Plan. It may be necessary to update the RIOGEN (i.e., DMKRIO, HCPRIO) to reflect changes to the hardware addresses. 3. Code the necessary modifications in the LIBGEN macros. Note: Changing or deleting an ACSid or LSMid in the LIBGEN is not supported by the HSC, except for the last LSMid defined for any ACS or the last ACS defined in the LIBGEN. 4.
PAGE 302
Reconfiguration 13. Perform the following tasks to prepare for reconfiguration: a. Issue the following commands: ACCESS 191 A ACCESS 254 B ACCESS 255 C The 191-disk is MAINTSTK 191, the 254-disk is the RUN-disk, and the 255-disk is STKACS 191. b. Make a backup copy of the ACS SYSPROF by issuing: COPY ACS SYSPROF B ACSOLD SYSPROF A (REPLACE c. Copy ACS SYSPROF from the RUN-disk (B) to the A-disk.
PAGE 303
Reconfiguration Note: Virtual device addresses may need to be changed in ACS SYSPROF when adding new data set names. e. Copy the updated SYSPROF to the RUN-disk. COPY ACS SYSPROF A ACS SYSPROF B (REPLACE f. Allocate the new data sets using SLIMDISK. Note: Review all the DASD considerations before allocating data sets. Refer to ‘‘Calculating DASD Space’’ in the HSC Installation Guide. g. Issue the following command to create a job to initialize the new library data sets: EXEC ACS UTIL SLICREAT (NOSEND h.
PAGE 304
Reconfiguration statements and deleting the DSNs created in step 13d on page 260. Do not alter DBPRMNEW or DBSHDNEW. Note: Virtual device addresses may need to be changed in ACS SYSPROF when adding new data set names. o. Issue the following command to create a job to reconfigure the new library data sets: EXEC ACS UTIL RECONFIG (NOSEND /JOB jobname SLSBINIT /PARM E(E086) F(23) MEMBER(XX) RECONFIG /FILE SLSSYSXX * /* DEFINE CONTROL DATA SETS */ CDSDEF DSN1=, VOL1=, UNIT1= DSN2=
PAGE 305
Reconfiguration 16. XEDIT ACS SYSPROF B to remove the comments from the AUTOJOB statements. Note: Make sure that the AUTOJOB file name matches the new startup job file created earlier. Modify the SLSCNTL, SLSCNTL2, and SLSSTBY data set names to match the new names. 17. Save ACS SYSPROF on the RUN-disk (B). 18. Issue the following command to restart the ACS service machine: AUTOLOG STKACS 19. Change any startup files (SYSPROF, STARTUP JCL, and/or PROCs) for other hosts to reflect the new configuration.
PAGE 306
Restore Restore Utility The RESTore utility provides a way to re-create the library control data set from a previous backup copy of the data set. You also have the option to apply all journals (maximum of 99 files per run) since the last backup, if journaling is enabled. Caution: It is critical that you restore all data sets referenced by the HSC (primary, secondary, standby). Failing to restore all data sets can cause CDS mismatches.
PAGE 307
Restore The RESTore utility does not reset the journals. It is recommended that a backup be performed following the completion of the restore to reset the journals and reflect the newly restored control data set. Special Considerations for Control Data Sets Processing Independently Special precautions should be taken for running BACKup and RESTore when local/remote-linked libraries run control data sets independent of each other.
PAGE 308
Restore Note: If OPTion(Analyze) was specified for backup, this parameter should be specified for the restore. (Only) specifies that all statements are sent to the SLSAUDIT data set. The CDS and Journal /FILE statements need not be present. The control data sets are not restored. (Short) specifies that Audit statements only are sent to the SLSAUDIT data set. The control data sets are restored.
PAGE 309
Restore Invoking the Restore Utility The easiest way to run utilities is to execute the ACS UTIL exec by entering the following command: EXEC ACS UTIL RESTore Execution of the statement results in the ACSUTIL SLKJCL file: ACSUTIL SLKJCL File /JOB jobname SLUADMIN /PARM MIXED /FILE SLSPRINT DEV PRNT CLASS A /FILE SLSAUDIT DEV PNCH CLASS A /FILE SLSCNTL DEV DSN /FILE SLSCNTL2 DEV DSN /FILE SLSSTBY DEV DSN /FILE SLSBKUP DEV DSN /FILE SLSJRN0
PAGE 310
Restore JCL for RESTore (with Journals Applied) /JOB jobname SLUADMIN /PARM MIXED /FILE SLSBKUP DEV vaddr DSN /FILE SLSCNTL DEV vaddr DSN /FILE SLSCNTL2 DEV vaddr DSN /FILE SLSSTBY DEV vaddr DSN /FILE SLSJRN#1 DEV vaddr DSN /FILE SLSJRN#2 DEV vaddr DSN /FILE SLSAUDIT DEV PNCH CLASS /FILE SLSPRINT DEV PRNT CLASS /FILE SLSIN * RESTORE APPLY(YES backup.set.name primary.set.name secondary.set.name standby.set.name journal1.set.name journal2.set.
PAGE 311
Restore JCL for RESTore (Journals and Output to SLSAUDIT) /JOB jobname SLUADMIN /PARM MIXED /FILE SLSCNTL DEV vaddr DSN primary.set.name /FILE SLSCNTL2 DEV vaddr DSN secondary.set.name /FILE SLSBKUP DEV vaddr DSN backup.set.name /FILE SLSPRINT DEV PRNT CLASS * /FILE SLSIN * RESTORE APPLY(YES) GENERATE(YES) Output Description Output resulting from the execution of the RESTore utility includes: • a restored library control data set. A shadow or secondary data set is also output if specified in the JCL.
PAGE 312
Restore SLUADMIN (n.n.n) TIME hh:mm:ss StorageTek Automated Cartridge System Utility Control Card Image Listing PAGE 0001 DATE yyyy-mm-dd RESTORE GENERATE(YES) SLUADMIN (n.n.
PAGE 313
Restore How to Handle BACKup/RESTore Discrepancies Under abnormal circumstances (CDS mismatch, link down, and so on), the backup operation must be performed periodically. During this operation, discrepancy blocks are generated within the SLSBKUP data set. Then, during the restore process, the discrepant records are formatted into control card statements and output to the SLSAUDIT data set.
PAGE 314
Scratch Redistribution Scratch Redistribution Utility The Scratch Redistribution utility provides you with a way to balance the number of scratch volumes across the ACS. It permits the redistribution of scratch volumes either: • among LSMs implied by the specification of an ACS, or • among the LSMs explicitly identified through an optional parameter. This utility allows the user to select one media type and recording technique.
PAGE 315
Scratch Redistribution Syntax SCREdist ACS(acs-id) , LSM( BALtol(tolerance-value) SUBpool(subpool-name) lsm-list MEDia( ) LONGItud ) RECtech( LONGItud Standard CST 18track 36track MEDIA1 36Atrack STD 1 36Btrack 36Ctrack 3480 HELical ECART E DD3 STK1R ECCST STK1R34 ETAPE Long STK1R35 STK1RA MEDIA2 STK1RA34 3490E STK1RA35 ZCART Z HELical STK1RB STK1RB34 STK1RB35 DD3 DD3A STK1RAB STK1RAB4 DD3B DD3C STK1 STK1RAB5 STK1RC STK1RC34 STK1R STK1RC35 R STK2 STK2P34 STK2P STK2P
PAGE 316
Scratch Redistribution Parameters ACS specifies one ACS in the library in which the scratch volumes are to be redistributed. (acs-id) identifies the ACS. The one or two digit hexadecimal ACS identifier. LSM optionally, specifies that only certain LSMs within an ACS are to contain scratch cartridges (if not specified, scratch volumes are redistributed across all LSMs in the ACS). (lsm-list) lsm-list can be a single LSMid or a list of LSMids. An LSM range is not allowed.
PAGE 317
Scratch Redistribution The expected number can be determined as follows: totcellslsm expnumlsm = totscracs * totcellsacs where: expnumlsm expected number of scratches for each LSM. totscracs total number of scratches in the ACS. totcellslsm total number of cells in the LSM. totcellsacs total number of cells in the ACS. In the previous example, the 4410 should have a range 470-530 scratches and the 9360 a range of 70-130.
PAGE 318
Scratch Redistribution LONGItud indicates any Standard, ECART, or ZCART cartridge. Standard indicates a standard length, 3480 cartridge. It can be read on any longitudinal drives (4480, 4490, 9490, or 9490EE). Data can be written in 36-track mode on 4490, 9490, or 9490EE transports but cannot be read on an 18-track (4480) drive. Synonyms for this type of cartridge include: • • • • • CST MEDIA1 STD 1 3480 ECART indicates a 3490E, extended capacity cartridge.
PAGE 319
Scratch Redistribution Data capacity differences between DD3A, DD3B, and DD3C cartridges are related to the length of the tape in the cartridge, not to the recording density of the data. STK1 indicates any T9840 cartridge. STK1R indicates a T9840 20GB data cartridge. The media indicator in the external label is encoded with the cartridge type (R). STK1R can be abbreviated to R. STK2 indicates any T9940 cartridge. This parameter is the default for all T9940A and T9940B data cartridge types.
PAGE 320
Scratch Redistribution HELical indicates a device using helical recording. DD3 indicates a device using helical recording. STK1R indicates any 9840 or T9840B transport. STK1R34 indicates any 3490E-image 9840 or T9840B transport. STK1R35 indicates any 3590-image 9840 or T9840B transport. STK1RA indicates a 3490E or 3590-image 9840 transport. STK1RA34 indicates a 3490E-image 9840 transport. STK1RA35 indicates a 3590-image 9840 transport. STK1RB indicates a 3490E or 3590-image T9840B transport.
PAGE 321
Scratch Redistribution STK2P indicates any T9940A transport. STK2P34 indicates a 3490E-image T9940A transport. STK2P35 indicates a 3590-image T9940A transport. STK2PA indicates a T9940A transport. STK2PA34 indicates a 3490E-image T9940A transport. STK2PA35 indicates a 3590-image T9940A transport. STK2PB indicates a T9940B transport. STK2PB34 indicates a 3490E-image T9940B transport. STK2PB35 indicates a 3590-image T9940B transport.
PAGE 322
Scratch Redistribution JCL Requirements The following definitions apply to Scratch Redistribution utility JCL: SLSPRINT output messages from the utility. SLSIN input to the utility in the form of control statement card images.
PAGE 323
Scratch Redistribution JCL to Perform Scratch Redistribution /JOB jobname SLUADMIN /PARM MIXED /FILE SLSPRINT DEV PRNT CLASS A /FILE SLSIN * SCREDIST ACS(01) The following example shows JCL for redistributing 36-track scratch volumes within all LSMs in ACS 00.
PAGE 324
Scratch Redistribution Output Description Output occurring from execution of the Scratch Redistribution utility includes: • updated library control data set reflecting the redistribution of scratch volumes • messages detailing actions or attempts to provide an even distribution of scratch volumes across LSMs in an ACS (see Figure 18). SLUADMIN (n.n.
PAGE 325
Scratch Update Scratch Update Utilities Scratch Update utilities provide three basic functions: • SCRAtch utility — allows you to scratch a volume, a list of volumes, or a range of volumes • UNSCratch utility — allows you to unscratch a volume, a list of volumes, or a range of volumes. The entire scratch list in the library control data set can be deleted by using the UNSCratch utility.
PAGE 326
Scratch Update Parameters VOLser specifies the list of volume serial numbers to be added, deleted, or replaced in the scratch list(s). (vol-list) vol-list specifies the volume serial numbers; this can be a single volume, a list of volume serial numbers, ranges of volume serial numbers, or combinations of lists with ranges delimited by commas. The entire list must be enclosed in parentheses.
PAGE 327
Scratch Update To execute the utility: 1. Delete the lines in the template that are not required, or leave the comment indicator (*) in column one. 2. Remove the comment indicator from the desired lines. 3. Specify values for the desired parameters. 4. Delete the parameters that are not desired. 5. Enter the command ‘‘FILE.’’ The job file is then submitted to the ACS service machine for execution.
PAGE 328
Scratch Update SLUADMIN (n.n.n) TIME hh:mm:ss StorageTek Automated Cartridge System Utility Control Card Image Listing PAGE 0001 DATE yyyy-mm-dd SCRATCH VOL(102412,102414) SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility TIME hh:mm:ss Scratch Update SLS0167I Volume 102412 successfully added to library as scratch SLS0164I Volume 102414 already defined in library as scratch SLS0155I Condition code for utility function is 4 Figure 19.
PAGE 329
Set SET Utility The SET utility allows you to change certain library configuration information without performing reconfiguration on the library. The utility performs operations directly on the control data set, without requiring the HSC to be active. In many cases, the SET function may run with an active HSC. In most such cases, changes made are not effective until the HSC has been brought down and then reactivated.
PAGE 330
Set Table 14.
PAGE 331
Set When the HSC is started on any host, it initially serializes on the CDS using the StorageTek-defined QNAME. This prevents the HSC from being started while the customer-defined QNAME is potentially in the process of being changed. If this is successful (no SET utility in progress), the customer-defined QNAME is read from the CDS and is used for future serialization requests. The SET utility does not perform changes that require the structure of the database to be changed.
PAGE 332
Set Table 15.
PAGE 333
Set Syntax SET Options Options: ACSDRV(esoteric) ,FORACS(acs-id) ,FORHOST(host-id) CLNPRFX(prefix) COMPRFX(cmdhex) DELDISP( SCRTCH ) NOSCRTCH EJCTPAS( ) newpswd FREEZE( ON ,OLDPASS(oldpswd) ),FORLSMID(lsm-id) ,FORPANEL(panel) OFf HOSTID (newhost),FORHOST(oldhost) HSCLEVEL(OFF),FORHOST(host-id) MAJNAME(qname) NEWHOST(newhost) ,LIKEHOST(model-host) NNLBDRV( ) esoteric SCRLABL( SL ,FORHOST(host-id) ) AL NL NSL Note: This syntax is continued on the next page. Chapter 4.
PAGE 334
Set Syntax (continued) SET Options Options: SLIDRIVS( ) ,FORLSMID(lsm-id),FORPANEL(panel) addr0 ,...addr19 ,FORHOST(host-id) SLISTATN( ),FORACS(acs-id) stat1,...,stat16 ,FORHOST(host-id) SMF(libtype) TCHNIQE( NONE JOURNAL SHADOW ) BOTH STANDBY ALL Utility Name SET specifies that the SET function is to be invoked. Parameters SET ACS Esoteric ACSDRV specifies that the esoteric for the specified ACS is to be changed. The change does not take effect until the relevant HSC(s) are recycled.
PAGE 335
Set FORACS specifies that the operation is being restricted to a specific ACS. (acs-id) specifies the ACSid whose esoteric is being changed. FORHOST specifies that the operation is being restricted to a specific host. Only the specified hosts’ esoteric is set. If omitted, the esoterics for all hosts are changed. (host-id) specifies the 1- to 8-character host ID for the host to which the operation is restricted. SET Cleaning Prefix CLNPRFX specifies that the cleaning prefix is to be set.
PAGE 336
Set Note: Do not assign any characters which could conflict with those in use by CP line edit for any command-authorized virtual machines. Table 16. Mapping of Command Prefix Codes to Characters Hex Character 40 null blank 4A ¢ cent 4B .
PAGE 337
Set Table 16. Mapping of Command Prefix Codes to Characters Hex Character Description Note: Ensure that the prefix character used does not conflict with any of the following: • another subsystem’s command prefix character (such as “*” for SCP) • any of the CP line editing symbols in effect (such as “#,” “@,” “¢,” or “““). Issue the CP QUERY TERM command to determine the line editing symbols in effect. SET Delete Disposition DELDISP specifies that the delete disposition parameter is to be set.
PAGE 338
Set (oldpswd) specifies the 1-to 8-character old eject password. Note that oldpswd is not displayed on SLSPRINT. SET Freeze Panel FREEZE specifies to disallow (freeze) or allow (unfreeze) additional cartridges to be stored on| a panel. Notes: Frozen or unfrozen panels are recognized immediately by all active HSCs. It| is not necessary to stop and reinitialize active HSCs to detect changes made by SET FREEZE. ON specifies to freeze a panel, which prevents additional cartridges from being moved to it.
PAGE 339
Set SET Host ID HOSTID specifies that the old host ID is being changed to a new name. (newhost) specifies a 1- to 4-character host ID which also serves and the SMF system ID. This host ID must also be specified by the LIBSUBSYS parameter in the ACS SYSPROF file. newhost cannot already be defined in the CDS. FORHOST specifies the old host ID. (oldhost) specifies a 1-to 8-character host ID. This host must not be marked active in the CDS. An HSC can be down but still marked active.
PAGE 340
Set • Restart the HSC on the host. • Enter the RECover host-id FORCE operator command. SET ENQ/DEQ/RESERVE QNAME MAJNAME specifies that the ENQ/DEQ/RESERVE QNAME is to be set This parameter requires that the HSC on all systems be shut down before changing the QNAME. (qname) specifies a 1- to 8-character QNAME. The QNAME is blank padded on the right. The name should conform to the requirements for a QNAME.
PAGE 341
Set Note: The NNLBDRV parameter has no effect in the operation of the VM/HSC. The utility may still be used to set this parameter for MVS systems sharing this CDS. (esoteric) specifies a 1-to 8-character esoteric. If the value is omitted, this means that there are no nonlibrary drives installed. FORHOST specifies that the operation is being restricted to a specific host. Only the specified hosts’ nonlibrary drive esoteric is to be set. If omitted, the nonlibrary esoterics for all hosts are to be changed.
PAGE 342
Set (addr0,...addr19) specifies the device numbers for the panel. The numbers are from the top of the panel down. If a device number is omitted, this means that the host cannot access a drive in that particular position in the panel, or the drive does not exist. Notes: 1. Blanks as well as commas may be used to separate the drive specifications. 2. The total number of drives specified (including comma placeholders) must be 4, 10, 16 (for an SL8500), or 20.
PAGE 343
Set An example showing how to define a 9740 10-drive panel containing five 9840 drives i SET SLIDRIVS(,,,,,BD4,BD3,BD2,BD1,BD0),FORLSMID(lsmid), FORPANEL(panel) FORLSMID specifies that the operation is being restricted to a specific LSM. (lsm-id) specifies the LSMid containing the drive panel whose addresses are being changed. An LSMid is made up of the ACSid (hexadecimal 00-FF) and the LSM number (hexadecimal 00-17) separated by a colon (:).
PAGE 344
Set Table 17. HSC State/SET SLIDRIVS Operation HSC State Effect on SET SLIDRIVS Active If unit addresses are changed or deleted for an existing drive location, either • the affected LSM must be offline until the HSC has been recycled on all hosts, or • the affected ACS must be offline to all affected hosts that access an HSC that has not been recycled. SET SLIDRIVS Procedure The following procedure shows one method for changing unit addresses with the HSC active. • For one host: 1.
PAGE 345
Set ACS and Host ID) not specified here will be deleted and no longer available for use. 2. To remove station addresses for an ACS or host, do not specify station addresses following the SLISTATN parameter. For example SET SLISTATN(),FORACS(#1),FORHOST(HSCA) FORACS specifies the ACS for which station addresses are being changed. (acs-id) specifies the ACSid whose stations are being changed (00 - FF). FORHOST specifies that the operation is being restricted to a specific host.
PAGE 346
Set The journals contain a record of all transactions that update the control data set. There are two journals per host. It is recommended that they are placed on separate HDAs from the primary control data set DASD volume. SHADOW specifies that there is to be two distinct copies of the control data set (primary and secondary) for recovery purposes. It is recommended that these data sets reside on separate HDAs and separate strings. A journal is not recorded.
PAGE 347
Set SLSCNTL the primary control data set. A primary control data set is required. SLSCNTL2 the secondary control data set. This statement is used only if you have configured and initiated a secondary control data set for your installation. A secondary control data set is optional, but highly recommended. SLSSTBY the standby control data set. This statement is used only if you have configured and initiated a standby control data set for your installation.
PAGE 348
Set JCL Examples The following example shows basic JCL that is required for executing the SET utility. Statements that represent individual utility functions are included in the JCL, as you deem necessary, to comprise the HSC configuration that you want to invoke. JCL for Set Utility /JOB jobname SLUADMIN /PARM MIXED /FILE SLSCNTL DEV vaddr DSN control.set.name /FILE SLSCNTL2 DEV vaddr DSN secondary.set.name /FILE SLSSTBY DEV vaddr DSN standby.set.
PAGE 349
Set JCL for Multiple SET Statements /JOB /PARM /FILE /FILE /FILE /FILE SET SET SET SET jobname SLUADMIN MIXED SLSCNTL DEV vaddr DSN control.set.name SLSCNTL2 DEV vaddr DSN secondary.set.name SLSPRINT DEV PRNT CLASS A SLSIN * HOSTID(HSC2) FORHOST(HSCB) SLISTATN(0CD,0DD) FORACS(00) FORHOST(HSC2) NNLBDRV(CTAPE) FORHOST(CPUA) NNLBDRV(CTAPE) FORHOST(CPUB) Note: The last two lines of the JCL example above (SET NNLBDRV...) are not used by VM, but they are valid for setting an MVS host from a VM host.
PAGE 350
Unselect Unselect Utility The UNSElect utility allows you to ‘‘unselect’’ a volume that the HSC leaves in a selected state. Usually, this is an error. The ‘‘unselect’’ operation is performed without cycling the HSC. Note: Use this utility only if you are certain that the HSC has incorrectly left the volume selected. Incorrect use of this utility can result in HSC abends and errant volumes. Issue a Display Volume DEtail command to determine which host has the volume in question.
PAGE 351
Unselect Utility Name UNSElect specifies that the UNSElect function is to be performed. Parameters VOLser indicates that a VOLSER is being specified for unselection. (volser) volser specifies the VOLSER to be unselected. FORCE optionally indicates that the volume is to be unselected even if communication with the host that has the volume selected is not possible. JCL Requirements The following definitions apply to UNSElect utility JCL: SLSPRINT output messages from the utility program.
PAGE 352
Unselect 4. Delete the parameters that are not desired. 5. Enter the command ‘‘FILE.’’ The job file is then submitted to the ACS service machine for execution. JCL Example The following example shows JCL for unselecting volume BWX119.
PAGE 353
Unselect SLUADMIN (n.n.n) TIME hh:mm:ss StorageTek Automated Cartridge System Utility Control Card Image Listing PAGE 0001 DATE yyyy-mm-dd UNSELECT VOL(BWX119) SLS0376I Volume BWX119 is now unselected; owning host was HSC1 SLS0155I Condition code for utility function is 0 Figure 20. Unselect Utility Sample Output Chapter 4. Utility Functions 323 1st ed.
PAGE 354
Volume Report Volume Report Utility The function of the Volume Report utility is to produce a listing of the physical location for volumes residing in an LSM. This utility is used primarily for informational purposes and provides history and usage statistics on specific library volumes. The Volume Report utility program functions as a stand-alone process in batch mode and does not require that the HSC be operational in order to execute.
PAGE 355
Volume Report The volume location information in this report is accurate only up to the time that the volume information is read from the database. For recovery purposes, a listing from a Volume Report run, while the HSC is down on all hosts, must be used to assist locating the required volumes. Note: Volume movement occurs as a result of: • mount activity, dismount activity, enter activity, or eject activity • invoking the Scratch Redistribution utility • invoking the MOVe command or utility.
PAGE 356
Volume Report If the VAR is not synchronized with the VOLATTR statements, one of the following actions will resolve the mismatch. • • • • • change the VOLATTR statement(s) add an external media label to cartridges that are not Standard mount the cartridges enter the cartridges through the CAP run an audit. Note: If an external label is not provided for all ECARTs, the volume report may continue to show mismatches.
PAGE 357
Volume Report Syntax Note: This utility can be run either under CMS or SCP. If the utility is running under SCP, architectural limitations restrict the parameters that can be specified to ACS, LSM, VOLser, and VOLume. Parameters relating to sorting and data filtering are not available. If the utility is running under CMS, however, it is fully functional.
PAGE 358
Volume Report Utility Name VOLRpt specifies that a volume report is to be produced. Parameters ACS optionally specifies that a report is to be produced for only a particular ACS. (acs-id) The one or two digit hexadecimal ACS identifier. LSM optionally specifies that a report is to be produced for only certain LSMs within an ACS. (lsm-list) lsm-list indicates the LSMs. An lsm-list can be a single LSMid or a list of LSMids.
PAGE 359
Volume Report SORT optionally specifies a specified sort sequence. The following options are available: VOL indicates that the report is to be sorted by volume serial number (VOL is the default) LOC indicates that the report is to be sorted by location. USE indicates that the report is to be sorted by selection count. INS indicates that the report is to be sorted by date and time the volume was inserted into the control data set.
PAGE 360
Volume Report INCLude optionally specifies the criteria for including volume information in the report. If this keyword is specified, all volumes that match at least one of the specified criteria are tentatively selected for the report. Information about volumes may be removed from the list of volumes selected for the report if other options, such as EXCLUDE, VOL, ACS, or LSM are specified. Notes: 1. INCLude parameters are applied before EXCLude parameters in volume selection. 2.
PAGE 361
Volume Report MEDEQUAL specifies that volumes for which the media types of the VOLATTR and the VAR are equal match the criteria. NONMEDEQ specifies that volumes for which the media types of the VOLATTR and the VAR are not equal match the criteria. NOEXTernal NOEXTernal specifies that volumes without an external label match the criteria. For example, INCLUDE(SEL,ERR) tentatively chooses only selected and errant volumes for the report.
PAGE 362
Volume Report VOLIST optionally specifies that the utility produce a volume report. This parameter is used in combination with VOLDATA so that both a flat file and a volume report can be created. Normally, you would not specify VOLIST without also designating VOLDATA. If VOLIST, VOLDATA, and CDSDATA (see below) are specified, a volume report is created and a single flat file is produced that contains volume and non-volume information. Note: VOLIST is not available if Volume Report is running under SCP.
PAGE 363
Volume Report The totals are listed on a separate listing, on a new page from the Volume Report Listing, the Control Card Listing, and the Volume Report Totals Listing. An example displaying subpool information is shown in Figure 22 on page 344. If subpools overlap (i.e., a volume belongs to more than one subpool) then the sum of the subpool totals may be greater than the total number of scratch volumes or the number of volumes in the library.
PAGE 364
Volume Report Table 18. SLSVA Effect on Volume Report HSC State: SLSVA Specified: SLSVA Not Specified: Active Use VOLATTRs pointed to by SLSVA. * Use VOLATTRs used by the HSC. * Inactive Use VOLATTRs pointed to by SLSVA.* The HSC generates an error message saying that SLSVA is missing and incorrect data may be reported. In addition, no prefix characters appear before the ‘‘Media’’ field on the report to identify media type discrepancies.
PAGE 365
Volume Report Note: The ‘‘|’’ symbol indicates that the user must choose either PRINTER or DISK. where: C SYSOUT class for the printed report. PRINTER report is sent to the virtual printer of the userid executing the utility. DISK report is sent to disk. fn, ft, fm file name, file type, and file mode used if the report is sent to disk. SLSIN For SCP: /FILE SLSIN * For CMS: SLSIN keywords where: keywords Volume Report utility keywords.
PAGE 366
Volume Report SLSVA (CMS only) SLSVA fn ft fm where: fn, ft, fm file name, file type, and file mode containing the VOLATTR statements. PARM Parameters to pass to the SLUADMIN program. For SCP: /PARM parameters For CMS: PARM parameters where: parameters any parameters acceptable to the SLUADMIN program. JOB (SCP only) Specifies the start of the Volume Report utility to SCP. /JOB jobname programname where: jobname identifier for the job. programname name of the program to be executed. 336 VM/HSC 6.
PAGE 367
Volume Report Invoking the Volume Report Utility Depending upon the environment in which it is being run, the Volume Report utility can be invoked in one of two ways: • SLUVOLR EXEC (CMS) • ACSUTIL SLKJCL file (SCP). SLUVOLR EXEC (CMS) The user can invoke the utility under CMS by running the SLUVOLR EXEC. SLUVOLR fn ft fm where: fn, ft, fm the parameter file description. If omitted, fn defaults to ‘‘SLUVOLR,’’ ft defaults to ‘‘PARMS,’’ and fm defaults to ‘‘*.
PAGE 368
Volume Report To execute the utility: 1. Delete the lines in the template that are not required, or leave the comment indicator (*) in column one. 2. Remove the comment indicator from the desired lines. 3. Specify values for the desired parameters. 4. Delete the parameters that are not desired. 5. Enter the command ‘‘FILE.’’ The job file is then submitted to the ACS service machine for execution. JCL Example The following example shows JCL to produce a Volume Report for several LSMs.
PAGE 369
Volume Report JCL to Produce a Volume Report for an MVS PDS The following example shows JCL to produce a Volume Report for ACS 01. /JOB SLSXUTIL SLUADMIN /PARM MIXED /FILE SLSCNTL DEV 501 DSN CDS.PRIM /FILE SLSPRINT DEV PRNT CLASS A /FILE SLSVA DEV 520 DSN SOS600.SPSB.PARMLIB(VOLATTR) VOL HSC20B /FILE SLSIN * * VOLRPT ACS(01) Output Description A report in the specified sort order provides details about the library volumes in the ACSs/LSMs for which the report is produced.
PAGE 370
Volume Report Media Type Prefix Characters If discrepancies exist between the media type reported by the LMU (in the VAR) and the VOLATTR information, the media type is prefixed by one of the following characters: * displayed if the VAR media type and VOLATTR information do not match. In this case, the user should correct the erroneous VOLATTRs.
PAGE 371
Volume Report Subpool ID Field Scratch subpools for volumes are listed if: • SUMMary(SUBpool) is specified and • scratch subpool definitions have been provided by SCRPOol control statements. If the VOLSER is not within any scratch subpool range, ** DEFAULT ** appears in this field. Times Selected Field The Times Selected count is the number of times the volume has been selected for use by a host.
PAGE 372
Volume Report Volume Report Flat Files Specifying the VOLDATA parameter produces a volume flat file. The layout of the volume records is defined by the SMP/E-distributed SLUVVDAT macro. Refer to Appendix C, “Record Formats” on page 497 to see the SLUVVDAT record format. When VOLDATA is specified under CMS, only the volume information that passed all of the selection criteria is written to the specified output data set, one volume per record. The CDSDATA parameter creates a non-volume CDS flat file.
PAGE 373
Volume Report SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility TIME hh:mm:ss PAGE 0001 Control Card Image Listing DATE yyyy-mm-dd VOLRPT SUMMARY(TOTAL) VOLUME(CLN400-CLN418) SLUADMIN (n.n.
PAGE 374
Volume Report SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility TIME hh:mm:ss PAGE 0001 Control Card Image Listing DATE yyyy-mm-dd VOLRPT SUMMARY(SUB) VOLUME(EE0000-EE9999) SLUADMIN (n.n.
PAGE 375
Volume Report SLUADMIN (n.n.
PAGE 376
346 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 377
Chapter 5. Problem Determination, Diagnostics, and Recovery Overview The following indicators and facilities may be used in the determination of the source of a perceived problem. • • • • • • • Messages ABEND codes Software trace facilities Diagnostic capabilities Recovery capabilities Dump processing Major SCP data relationships. Messages HSC Messages Messages with the prefixes: ‘‘SLSxxxxs’’ are emitted by the HSC, and are documented in the HSC Messages and Codes Guide.
PAGE 378
Software Trace Facilities There is a hierarchy of facilities that may be used to trace the activity of the ACS service machine. They range from standard VM services, to SCP and HSC services. Utilities are also provided. The SCP and the HSC have separate trace facilities. Both have internal and external trace functions. The use of the HSC ‘‘TRACE’’ command (external trace) involves an interaction with the SCP ‘‘TRACE’’ command.
PAGE 379
VM (CP) Debug Commands The following CP commands are useful in diagnosing problems in the system. See appropriate VM documentation for details on syntax and use.
PAGE 380
Master Trace Table Header A data area, called the Master Trace Table Header (MTTH) is a 32-byte header which describes the actual trace table. The address of the MTTH is in the 4-byte area at absolute address x’54’ (label TRCTAB in structure NUCON). The MTTH actually resides in the CVT at offset x’238’ (label CVTMTTH).
PAGE 381
DSP Trace Entry event-type = ‘D’ event-code TTEWORD1 TTEWORD2 TTEWORD3 = dispatch priority = R15 = R12 = R13 Return from SVC Trace Entry event-type event-code TTEWORD1 TTEWORD2 TTEWORD3 = ‘W’ = dispatch priority = R15 = R0 = R1 SIO Trace Entry event-type event-code TTEWORD1 TTEWORD2 TTEWORD3 = ‘S’ = device address = IOB address = CAW = Reserved I/O Trace Entry event-type event-code TTEWORD1 TTEWORD2 TTEWORD3 = ‘I’ = device address = IOB address = CSW (bytes 0-3) = CSW (bytes 4-7) SVC Trace Entry e
PAGE 382
RST Trace Entry event-type event-code TTEWORD1 TTEWORD2 TTEWORD3 = ‘R’ = (unused) = (unused) = (unused) = (unused) EXT Trace Entry = ‘E’ = external interrupt code: = ‘CP EXT’ (generic external interrupt) = CLKC (TOD clock comparator) = CPUT (CPU Timer) = LDEV interrupt (logical device) = IUCV interrupt event-type event-code x’0040’ x’1004’ x’1005’ x’2402’ x’4000’ external interrupt (subtype EXT): TTEWORD1: TTEWORD2 TTEWORD3 unused unused unused external interrupt (subtype CLKC): TTEWORD1: TTEWORD2: TT
PAGE 383
Table 19.
PAGE 384
The IPARML fields are defined by VM.
PAGE 385
IPARML for IUCV SEND to *BLOCKIO *----------------------------------------------------------* x’00’ | Path ID |flags 1|IPRCODE| IPMSGID = message id | *------+------+-------+-------+--------+-----+------+------+ x’08’ | IPTRGCLS = target class | IPRMMSG1 = block number | | (1-write) (2=read) | | *------+------+-------+-------+------+------+------+-------+ x’10’ | IPRMMSG2 = bufffer address | xx | xx | xx | xx | *------+------+-------+-------+------+------+------+-------+ x’18’ | xx | xx | xx | xx | xx | xx
PAGE 386
IPARML for IUCV RECEIVE *----------------------------------------------------------* x’00’ | Path ID |flags 1|IPRCODE| IPMSGID = message id | *------+------+-------+-------+--------+-----+------+------+ x’08’ | IPTRGCLS = target class | IPBFADR1 = buffer address | *------+------+-------+-------+------+------+------+-------+ x’10’ | IPBFLN1F = bufffer length | xx | xx | xx | xx | *------+------+-------+-------+------+------+------+-------+ x’18’ | xx | xx | xx | xx | xx | xx | xx | xx | *------+------+------
PAGE 387
IPARML for IUCV REPLY *----------------------------------------------------------* x’00’ | Path ID |flags 1|IPRCODE| IPMSGID= message id | *------+------+-------+-------+--------+-----+------+------+ x’08’ | IPTRGCLS = target class | xx | xx | xx | xx | *------+------+-------+-------+------+------+------+-------+ x’10’ | xx | xx | xx | xx | xx | xx | xx | xx | *------+------+-------+-------+------+------+------+-------+ x’18’ | xx | xx | xx | xx |IPBFADR2= reply buffer addr | *------+------+-------+-------+
PAGE 388
IPARML for IUCV SEVER *----------------------------------------------------------* x’00’ | Path ID | xx |IPRCODE| xx | xx | xx | xx | *------+------+-------+-------+--------+-----+-----+--- ---+ x’08’ | IPVMID= userid connected to | *------+------+-------+-------+------+------+------+-------+ x’10’ | xx | xx | xx | xx | xx | xx | xx | xx | *------+------+-------+-------+------+------+------+-------+ x’18’ | xx | xx | xx | xx | xx | xx | xx | xx | *------+------+-------+-------+------+------+------+-------+
PAGE 389
IPRCODE The following is a list of IPRCODE values and meanings from DMKSP MACLIB member IUCVBLOK for VM/SP, VM/SP HPO and VM/ESA 370. For VM/XA and VM/ESA, the codes are defined in CPLIB MACLIB member IPARML. The codes are also documented in the IBM VM/SP System Programmer’s Guide and System Facilities for Programming documents.
PAGE 390
28 no control buffer exists 48 function not supported for CSS IUCV Interrupt Buffer As an IUCV-type external interrupt occurs, CP places data in the IUCV external interrupt buffer. The data describes the type of IUCV event, and data specific to each event subtype. For a full description, see the appropriate VM documentation. The external interrupt is traced in the internal trace table, and the first 8 bytes of the IPARML are saved in the TTE. The following is a list of possible IUCV interrupt codes.
PAGE 391
IPARML for Pending Connection Interrupt *----------------------------------------------------------* x’00’ | IPPATHID | Flag 1| 01 | IPMSGLIM | xx | xx | *------+------+-------+-------+--------+-----+-----+--- ---+ x’08’ | IPVMID= userid wishing to establish the connection | *------+------+-------+-------+------+------+------+-------+ x’10’ | IPUSER | *------+------+-------+-------+------+------+------+-------+ x’18’ | IPUSER | *------+------+-------+-------+------+------+------+-------+ x’20’ | xx | xx | x
PAGE 392
IPARML for Connection Complete Interrupt *----------------------------------------------------------* x’00’ | IPPATHID | Flag 1| 02 | IPMSGLIM | xx | xx | *------+------+-------+-------+------+-------+-----+--- ---+ x’08’ | xx + xx + xx + xx + xx + xx + xx + xx | *------+------+-------+-------+------+------+------+-------+ x’10’ | IPUSER | *------+------+-------+-------+------+------+------+-------+ x’18’ | IPUSER | *------+------+-------+-------+------+------+------+-------+ x’20’ | xx | xx | xx | xx | xx
PAGE 393
IPARML for Path Severed/REsumed/Quiesced Interrupt *----------------------------------------------------------* x’00’ | IPPATHID | xx | IPTYPE| xx | xx | xx | xx | *------+------+-------+-------+------+------+--- --+--- ---+ x’08’ | xx | xx | xx | xx | xx | xx | xx | xx | *------+------+-------+-------+------+------+------+-------+ x’10’ | IPUSER | *------+------+-------+-------+------+------+------+-------+ x’18’ | IPUSER | *------+------+-------+-------+------+------+------+-------+ x’20’ | xx | xx | xx |
PAGE 394
IPARML for Incoming Message Interrupt *----------------------------------------------------------* x’00’ | IPPATHID | Flag 1| 08/09 | IPMSGID= message id | *------+------+-------+-------+------+------+--- --+--- ---+ x’08’ | IPTRBCLS= target class | xx | xx | xx | xx | *------+------+-------+-------+------+------+------+-------+ x’10’ | IPBFLN1F= message length | xx | xx | xx | xx | *------+------+-------+-------+------+------+------+-------+ x’18’ | xx | xx | xx | xx | xx | xx | xx | xx | *------+------+--
PAGE 395
IPARML for Message Complete Interrupt *----------------------------------------------------------* x’00’ | IPPATHID | Flag 1| 06/07 | IPMSGID= message id | *------+------+-------+-------+------+------+--- --+--- ---+ x’08’ | IPAUDIT | | xx | xx | xx | xx | xx | *------+------+-------+-------+------+------+------+-------+ x’10’ | xx | xx | xx | xx | xx | xx | xx | xx | *------+------+-------+-------+------+------+------+-------+ x’18’ | xx | xx | xx | xx | xx | xx | xx | xx | *------+------+-------+-------+-
PAGE 396
Diagnostic Capabilities This section describes the overall diagnostic capabilities supported by all components of the HSC. Diagnostic capabilities include: • SCP Trace Facility. This facility provides a history of the processing before a failure. • Supervisor Call (SVC), Dump (SDUMP), and Abnormal End (ABEND) Dumps. Record information on dumps is made available at the time of failure by using these dumps. They appear as VMDUMPS. • Error Recording Data Sets (ERDS).
PAGE 397
SCP External Trace Facility The SCP can trace interrupt, IUCV, I/O, dispatch, and GTRACE events as they occur and send the trace records to a designated virtual machine for later analysis. The target may be any virtual machine in an RSCS network. The system TRACE task (SLKTKT) is responsible for writing the trace records to a VM punch spool file. The records are written in a special format, where a logical record may span multiple physical records. The system TRACE task is not traced.
PAGE 398
SCP Trace Formatter Utility SLUETRAC EXEC spoolid events ( IN= OUT= infile outfile ALL DSP EXT I/O IUC MCK PGM RST SIO SVC USR infile: ACS infn TRACE inft A infm outfile: ACSTRACE outfn LISTING outft A1 outfm * EXEC optionally specified to invoke the EXEC. SLUETRAC initiates the SLUETRAC EXEC. 368 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 399
spoolid indicates the VM spool id of the reader spool file containing the trace data. If neither spoolid nor IN= is specified, the first non-held reader spool file of type PUN is processed. Note: IN= overrides specification of a reader spool file.
PAGE 400
Supervisor Call (SVC) Functions The SCP partially supports the following SVC functions. They are included here for use when reading trace output. Documentation of the actual subfunctions supported is for StorageTek internal purposes only. 370 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 401
Table 20.
PAGE 402
SCP GTRACE Emulation The SCP emulates the following MVS GTRACE features: 1. The MVS GTRACE macro is supported, without alteration. 2. A Monitor Call (MC) program interrupt occurs when the GTRACE function is invoked. The SCP program check handler recognizes and handles the Monitor Call as a GTRACE event. 3. Up to 256 bytes of user data may be traced. 4. With most interrupts, the SCP dispatcher does not return to the interrupted task immediately, but dispatches the next task in the priority queue.
PAGE 403
The valid EID ranges are: 0 <= user EID <= x’3FF’ x’400’ <= system EID <= x’FFF’ The actual EID used by the SCP is x’400’, for all FIDs. The actual EID used by the HSC is passed to the HSC initialization routine (SLSBINIT), and is recorded in the ACS SYSPROF file. The default EID is x’E086’, corresponding to user event x’086’. Chapter 5. Problem Determination, Diagnostics, and Recovery 373 1st ed.
PAGE 404
HSC Internal Trace Table The HSC itself has an internal trace table. It is pointed to by the contents of the 4-byte field at offset x’40’ from the start of the LVT (LVTTBLK). It is a wrap-around table, recording the last 256 events that occurred in the HSC subsystem. There are more than 90 different types of events. Trace entries are 108 bytes long. The data traced will be truncated in order to fit into the table entry. Programs issue an SLSTRACE macro at important trace points.
PAGE 405
00B613F0. 00B61400. 00B61410. 00B61420. 00B61430. 00B61440. 00B61450. 00B61460. 00B61470. 00B61480. 00B61490. 00B614A0. 00B614B0. 00B614C0. 00B614D0. 00B614E0. 00B614F0. 00B61500. 00B61510. 00B61520. 00B61530. 00B61540. 00B61550. 00B61560. 00B61570. 00B61580. 00B61590. 00B615A0. 00B615B0. 00B615C0. 00B615D0. 00B615E0. 00B615F0. 00B61600. 00B61610. 00B61620. 00B61630. 00B61640. 00B61650. 00B61660. 00B61670. 00B61680. 00B61690. 00B616A0. C2E3D9C3 00006C10 F1300000 00000000 | BTRC..%.1.......
PAGE 406
HSC TRACE Command The HSC TRace command enables or disables tracing of events in selected HSC components. It uses GTRACE to perform the actual tracing. The SCP TRACE command must have the “USR” event enabled for any trace output to result. For a detailed description of how to use the HSC TRACE command, refer to the HSC Operator’s Guide. Format of HSC GTRACE USR Records Table 23.
PAGE 407
Diagnostic Commands VM (CP) Commands The CP commands listed in “VM (CP) Debug Commands” on page 349 are very useful in diagnosing a problem. For maximum effectiveness, they should be used in conjunction with the SCP’s diagnostic subsystem commands. SCP Debug Mode The SCP may operate in a special ‘‘debug’’ mode, initiated by some of the commands of the SCP diagnostic subsystem. The debug mode is special in the following ways: • When entering debug mode, the SCP issues the CP command SET RUN OFF.
PAGE 408
If the name is known, it will be located in storage. It will be brought into storage if it was not there before. If epname is not specified, the current traces are displayed. offset the optional offset from the address of epname at which to set a breakpoint using CP PER. The default is 0. .length the optional length of the breakpoint. The default is 1. Note: length must be preceded by a period with no space between offset and the period.
PAGE 409
SCP Diagnostic Subsystem Commands These commands are provided for use when diagnosing a problem with a ‘‘live’’ system. Any other use may result in indeterminate conditions. Note: It is recommended that StorageTek support personnel be contacted before using diagnostic subsystem commands. These commands are only valid when entered from the ACS service machine’s virtual console.
PAGE 410
=NODEBUG This diagnostic command terminates the special ‘‘debug’’ mode. ‘CP SET RUN ON’ is also executed. = the command character for the DIAG subsystem. The default is ‘‘=’’, but may be set to any character by the SUBSYS command that started the subsystem. =DDICT This diagnostic command displays data dictionary information describing an SCP or HSC data area fieldname. The information returned is the assembler definition of the field with the DSECT name and the offset from the DSECT.
PAGE 411
=HPER This diagnostic command sets one or more break-points for a list of named modules and offsets. The CP QUERY PER command is then issued to display the current program traps in effect. Note: In the VM/XA environment, CP PER and QUERY PER are synonyms for the CP TRACE and QUERY TRACE commands. ‘CP SET RUN OFF’ is executed, and the SCP debug environment is entered. The diagnostic command ‘=NODEBUG’ terminates the debug environment. = the command character for the DIAG subsystem.
PAGE 412
Results in CP QUERY PER output. The following output is for VM/SP, VM/SP HPO, and VM/ESA 370. 1 INSTRUCT RANGE addr TERMINAL NORUN CMD * FUNC=SLSBINIT OFFSET=000000 2 INSTRUCT RANGE addraddr TERMINAL NORUN CMD * FUNC=SLKODE OFFSET=000054 The following output is for VM/XA and VM/ESA.
PAGE 413
Examples: Issuing the command: =WHERE SLSBINIT 23FDF0 Results in the messages: SLKOWH671I Module SLSBINIT at address 23FD50 compiled 09/20/88 14.20 SLKOWH674I Address 23FDF0 = EP : SLSBINIT +0000A0 SLKOWH674I Address 23FDF0 = CSECT: SLSBINIT +0000A0 HSC Diagnostic Commands The following HSC diagnostic commands are provided: • LIst command • Display command. The HSC LIst command is provided for diagnostic support for the HSC. Use this command under the direction of StorageTek support personnel.
PAGE 414
address specifies a hexadecimal address of memory. size specifies the amount of memory (in decimal) to display. The default size is 16. DISPLAY Command The HSC Display command offers several options that are useful for diagnostic purposes. For more information on the Display command and its uses for diagnostics, refer to the HSC Operator’s Guide. 384 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 415
CDS Recovery Capabilities Capabilities to recover the CDS from certain hardware and software failures are inherent in the HSC.
PAGE 416
When access to a failing data set is restored, you must run the BACKup and RESTore utilities to restore the integrity of the failed data set. An alternative method is to use the CDs command, specifying the Enable parameter to append the data set again to the end of the Active CDS List. 386 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 417
Figure 24 illustrates the built-in recovery scheme for the control data sets.
PAGE 418
All HSCs in operation must be stopped to perform the restore operation. If the three control data sets fail, the journal(s) can be used to restore a valid control data set. Refer to “Backup Utility” on page 211 for detailed information about running the BACKup utility. Refer to “Restore Utility” on page 276 for detailed information about running the RESTore utility. Control Data Set Error Diagnostics Numerous messages are provided to permit you to diagnose problems pertaining to the control data sets.
PAGE 419
Switching to a Backup Copy of the Control Data Set If you have initialized your HSC subsystem with the additional backup copies of the control data set, you can dynamically switch operation to any one of the copies without affecting the HSC and library operation. With an operator command, you can enable or disable specific copies of the control data set.
PAGE 420
Recommended Recovery Actions Once you are aware that a switch of the control data set has occurred, it is recommended that the following actions be taken: 1. Run the BACKup utility. 2. Retain a backup copy of each control data set for diagnostic purposes. 3. Run the RESTore utility. 4. If DASD hardware errors are found, reallocate valid control data sets to a good storage device. If you are unsuccessful in recovering from mismatch errors, contact StorageTek Software Support.
PAGE 421
Dump Processing The following dump processing topics are discussed below: • • • • • • • Type of dumps supported How to request a dump What to do when a dump occurs Dump analysis using SLUIPCS Major SCP data relationships Diagnostic techniques Common dump analysis tasks. Type of Dumps Supported In order to use IPCS for dump analysis, dumps must be produced via the CP ‘VMDUMP’ command (or diagnose code x’94’). The dump ‘‘format’’ for this product is ‘SLK’.
PAGE 422
What to do When a Dump Occurs When a VM HSC dump occurs, it is sent as a CLASS V spool file to the virtual machine defined by the current DUMPOPTS setting. Dump files are large and can have a negative impact on system spool space; they should be processed as soon as possible after they occur. The following steps should be taken when a dump occurs: 1. Move the CONSLOG and dump spool files to the dump processing machine’s virtual reader. 2. Note the reason for the dump. 3.
PAGE 423
Load Dump and CONSLOG Onto Disk Load the dump spool file onto MAINTSTK’s IPCS disk. Ensure that MAINT’s 193 disk is ACCESSed. MAINTSTK normally has a LINK to this disk in its directory entry. To access the disk, issue the following command from MAINTSTK’s virtual console: ACCESS 193 B Issue the following command to load the first dump spool file onto disk: SLUIPCS LOAD A message is issued providing the name of the disk file created. This disk file has a name of the form PRBnnnnn DUMP.
PAGE 424
Below is an example of the VMFPLC2 commands normally used to copy the problem materials onto a tape mounted at virtual address 181: VMFPLC2 DUMP PRBnnnnn * * VMFPLC2 DUMP SMS2000 VMFSVLOG * VMFPLC2 WTM 2 Dump Analysis Using SLUIPCS Normally, dump analysis is performed by a StorageTek Software Support Representative. However, the facilities described in this section are available to all users.
PAGE 425
To terminate the SCAN environment, use the END subcommand. To format and print data areas and control blocks, issue the SLUIPCS PRINT command. The user is prompted for StorageTek-defined print options. SLUIPCS SCAN Subcommands These StorageTek-supplied SCAN subcommands ‘‘know’’ about SCP and HSC data structures and module locations. VIEW The VIEW subcommand displays a data structure, and saves its last resolved dump address.
PAGE 426
Table 25.
PAGE 427
Table 26.
PAGE 428
FIND FIND is identical to the VIEW command, except that only the address of the found structure is displayed. It is useful when following pointer chains to a structure. It is especially useful when analyzing a dump over a slow communications line. EX (EXECUTE CMS COMMAND) This subcommand executes any CMS command in subset mode. EX token token ..... TRB (SAVE AREA TRACEBACK) The TRB subcommand displays register save areas.
PAGE 429
STAT (STATUS) The STAT subcommand displays status of the system at the time of the problem that caused the dump: • • • • • general and control registers the PSW TOD clock TOD clock comparator dump id STAT TASK (FIND TASK) This subcommand displays a list of addresses of all tasks with a given name. The data displayed is the TBLOK address for each task that matches. TASK taskname WA (WHERE ADDRESS) The WA subcommand finds the program module that contains the given address.
PAGE 430
SLUIPCS PRINT Options The options listed in the following table are supported for SLK-type dumps. Table 27.
PAGE 431
Command, Message, Trace Processing NUCON X’10’: VECTPTR CVT CCVT COMANC MSGEL CCVWTOQ CMDPLIST CCVCMDQ TRCTAB MTT MTTCURR INTERNAL TRACE TABLE MTTFIRST MTTLAST CURRENT TTE X’A60’: INTERRUPT DATA SAVE AREA C29330 Figure 25. Command, Message and Trace Processing Chapter 5. Problem Determination, Diagnostics, and Recovery 401 1st ed.
PAGE 432
SCP Task/Job Data Relationships Refer to Figure 26 on page 403 for a description of these relationships. Subsystem Data Relationships Refer to Figure 27 on page 404 for a description of these relationships. Diagnostic Techniques The user must be logged on the ACS virtual console. 1. Loops: a. Disabled loops: 1. Press PA1. Enter: SET RUN OFF 2. Press PA1. Enter: VMDUMP 0.END FORMAT SLK * comments The PSW will be within the loop. b. Enabled loops: These will be detected by the dispatcher.
PAGE 433
NUCON JBLOK PSAAOLD JBLTASK TBLOK PSATOLD RQBLOK TKRBLIST C29331 Figure 26. SCP Task/Job Data Relationship Chapter 5. Problem Determination, Diagnostics, and Recovery 403 1st ed.
PAGE 434
NUCON CVT VECTPTR JESCT CVTJESCT JESSSCT SSCT SSCTSCTA SSVT SSCTSSVT SSCT SSCTSCTA SSVT SSCTSSVT SSCTSUSE LVT C29332 Figure 27. Subsystem Data Relationships 404 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 435
2. Enter: D PSW 3. PSW is BC mode if Bit 12 is 0 (high bit in the fourth nibble). If PSW is BC mode, then enter: VMDUMP 0.END FORMAT CMS * comments else enter: VMDUMP 0.END FORMAT SLK 0 comments b. Enabled Waits: These are difficult at best. Whatever failed to happen has already been obscured. Take a ‘‘FORMAT SLK’’ dump via PA1, or cancel the job that is hung up with ‘‘DUMP’’.
PAGE 436
(or) VIEW NUCON • If ABEND was the result of an ‘ABEND’ SVC: - NUCICODE = x’000D’ - NUCIGR1 = ABEND code (system and user) - NUCIGRF = optional ABEND reason code • If ABEND was the result of a ‘CALLRTM’: - NUCICODE = (not) x’000D’ - RTM1FLG1 = has bit x’40’ set - RTM1SR1 = ABEND code (system and user) - RTM1SR15 = optional ABEND reason code Identify the Failing Routine Look in the ‘PRBxxxxx REPORT’ file (or) STAT WA xx (xx = address in ‘INSTAD’) (or) VIEW NUCON WA xx (xx = address in ‘NUCIOPSW’) Find the Fa
PAGE 437
Save Area Trace Back Find an R13 value (for example, RQGPR13, NUCIGRD, etc.) TRB address Find the LVT VIEW LVT (or) Find LVT (or) Register 11 usually contains the LVT address for HSC modules (for example, SLS* or SLU*).
PAGE 438
Examine an SDWA Find the failing TBLOK (see instructions above) VIEW RTM2WA TKRTM2WA Display xx (xx = address in RT2RSDWA) Find IUCV Path Descriptors VIEW CVT VIEW IRT IRTANC repeat VIEW IRT IRTLNK until end-of-queue Find IUCV Interrupt Blocks Find an IRT VIEW XINT IRTINQ repeat VIEW XINT XINTLNK until end-of-queue Find IUCV Request Blocks Find an IRT VIEW IUB IRTOUTQ repeat VIEW IUB IUBQ until end-of-queue Gather Diagnostic Materials During problem resolution, Software Support may request that you provide
PAGE 439
- details of problem circumstances • STKACS abend - VMDUMP (process with SLUIPCS), CONSLOG, VMFSVLOG (refer to ‘‘Dump Processing’’ on page 5-35) • problems relating to HSC utilities - utility SLKJCL utility output (SLSPRINT) dump data if applicable STKACS CONSLOG • problems relating to CP - VM operator console log STKACS CONSLOG EREP or PM2 reports for failing period trace data may be required (virtual and real) system configuration information dump data may be required • problems relating to PROP messa
PAGE 440
Tape Format Software Support prefers that diagnostic data be sent in machine-readable format on tape in the following format: • VMFPLC2 format • for VM dump processing, refer to “Dump Processing” on page 391 • if possible, DO NOT use SPTAPE format. Tape Return When requested, Software Support will return any tapes which the sending party has labeled with a return address. 410 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 441
Chapter 6. Performance Considerations Overview After installing your Automated Cartridge System you will notice an improvement in your site system performance, especially for jobs and programs where tape cartridge handling is involved. Without any tuning, the ACS should significantly decrease mount/dismount times, shorten batch elapse times, open production windows, and reduce operator intervention. By making minor performance adjustments, you may achieve even more efficiency from your library.
PAGE 442
How Systems Programmers Control Library Performance Systems programmers command extensive control of overall library performance. This control of performance is inherent with how a systems programmer: • • • • initially configures the library (during the LIBGEN process) uses available utilities and commands monitors and analyzes performance participates in the development of standard methods and procedures for the data center.
PAGE 443
This utility provides the library administrator with the information necessary to balance mount/dismount activity across ACSs and LSMs within a library. The information is based on statistics contained in SMF records that are tallied for each cartridge movement.
PAGE 444
Redistribute Scratch Volumes in the Library The Scratch Redistribution utility allows you to redistribute scratch volumes across the LSMs within a particular ACS. You can choose to have the scratch volumes go to only specified LSMs or all LSMs within an ACS. Redistribution is performed to an evenness defined by the balance tolerance level which is specified via the Scratch Redistribution utility.
PAGE 445
If ejects and/or enters of large numbers of cartridges are frequent, you may want to set higher CAP preferences for enhanced CAPs. Refer to the HSC Operator’s Guide for information about the CAPPref command. Use SMF Records to Collect Performance Data Library performance data can be accumulated from SMF records. The SMF operand of the SLILIBRY macro for LIBGEN or the SMF parameter of the HSC SET utility determines the SMF record type written by the HSC.
PAGE 446
Table 28.
PAGE 447
Define High Dispatching Priority for the HSC The VM dispatch priority and SHARE settings of the ACS service machine may be altered to improve overall HSC performance for a VM host system. Set High-Performance Host-to-Host Communications In a multi-host ACS configuration, host-to-host communications allows hosts to notify each other of a CDS switch. Host-to-host communications can be accommodated through three performance levels of communications, ranked as follows: • ACF/VTAM • the LMU(s) • the CDS.
PAGE 448
Functioning of Host-to-Host Communications The method hierarchy that is established is, from highest to lowest, VTAM, LMU, CDS. Initially, all methods are set to CDS. Appropriate entries can be placed in the PARMLIB statement to set the communications method at HSC initialization. If an error in communications occurs during communications with the current communication method, a method switch is performed.
PAGE 449
Define Secondary and Standby Control Data Sets Various controls and services are in place in the HSC subsystem to ensure that the primary control data set maintains its integrity. Included among the controls are the capability to: • designate secondary and standby control data sets as backup • run BACKup and RESTore utilities • designate journal data sets for use in recovery of control data set errors.
PAGE 450
Excessive Use of VIew Command Affects Performance Each time the VIew command is invoked, the automatic functioning occurring within an LSM is interrupted. During the interruption, the robot hands and associated cameras are stopped from performing HSC directed library functions to focus on some specified area within the LSM for some specified time interval.
PAGE 451
• With the use of SMF logging, accurate records can be accumulated for system analysis or to monitor system status. Chapter 6. Performance Considerations 421 1st ed.
PAGE 452
Loading Cartridges Into the Library There are different methods that can be used to load an LSM with cartridges at installation time. There are advantages and disadvantages involved for each method. The following brief discussions may help you determine which loading method is best for your installation.
PAGE 453
Unavoidable Pass-Thrus The HSC attempts to minimize the number of pass-thrus required; however, depending upon available tape transports and locations of cartridges, pass-thrus often cannot be avoided. By running Activities Reports on a regular basis and examining the results, you can see that mounts for different LSMs take longer than mounts for the same LSM. Unnecessary Pass-Thrus Scratch mounts, dismounts, enters, and ejects that require pass-thrus are unnecessary and should be avoided.
PAGE 454
Ensure adequate free cells Setting MNTD Float to ON can be defeated if there are no free cells in the dismounting LSM. Dismounted cartridges are passed to other LSMs to find a new home cell. Use the Display Lsm command to determine the number of free cells in each LSM. Use MOVe or EJect to create free cells if they are needed. Eject through the CAP closest to the cartridge If you eject a cartridge through the CAP of the LSM where it resides, no pass-thrus are required.
PAGE 455
Prefetch Enters Nonlibrary cartridges that are mounted on library transports are delayed while the operator fetches and enters them. This is a common occurrence for HSC sites with all transports attached to the library. If you or your scheduling system can predict which nonlibrary cartridges will be mounted in the library before a mount message appears, your operator can improve performance by entering those cartridges in advance.
PAGE 456
DETACHed from a virtual machine. This enables the volume to be available (that is, unselected) earlier than would otherwise be possible. ACSPROP EXEC can also be used with VMOPERATOR to trap MOUNT messages for VMTAPE. LOGTABLE SAMPLE contains sample VMOPERATOR LOGTABLE statements to assist you. Consult VMOPERATOR documentation for information about tailoring the samples to your needs. Syntax ACSPROP EXEC Parameters There are no external parameters required.
PAGE 457
Scheduling Nonproductive Activities During Low-Demand Times There are several library utilities, which, though very essential, severely impact the library’s ability to mount and dismount cartridges. The following utilities should not be run when high-priority production jobs are pending: • • • • • • AUDIt EJECt Enter Cartridges MOVe Scratch Redistribution Scratch Update. These utilities should be scheduled during quiet periods so they do not contend with mounts and dismounts.
PAGE 458
Use LSMs as Scratch Loaders in a Mixed ACS In an environment where massive cartridge input is required or a lot of cartridge movement occurs, 9360 (WolfCreek) or 9310 (PowderHorn) LSMs can be used to simulate scratch loaders intermixed with 4410 LSMs to improve library performance. 1. Specify the following operator command: MNTD SCRDISM(ARCHIVE) 2. Run scratch redistribution frequently. 3. Eject cartridges when necessary from the archive device (4410 or 9310).
PAGE 459
Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference Syntax Flow Diagrams Syntax is illustrated using flow diagrams. These can include the following elements: • syntax – the diagram itself. • items – individual elements inside the diagram. Items can be keywords, variables, delimiters, operators, fragment references, and separators. • groups – a collection of items or other groups. The following sections describe syntax flow diagram features and include some generic examples.
PAGE 460
Flow Lines Syntax diagrams consist of horizontal and vertical lines and the text of a command, control statement, macro, or utility. COMMAND/MACRO/UTILITY or Item1 Item2 Item3 Diagrams are read left to right and top to bottom. Arrows indicate flow and direction.
PAGE 461
Single Optional Choice If the first item is on the line below the base line, a single choice of items in the stack is optional. Item1 Item2 Item3 Defaults Default values and parameters appear above the syntax diagram line. In the following example, if a value is not specified with the command, Default Value is used by the HSC. Default Value Value2 Value3 Some keyword parameters provide a choice of values in a stack.
PAGE 462
Syntax Continuation (Fragments) Fragment references direct you to parts (fragments) of the syntax that contain more detail than can be shown in the main syntax diagram. COMMAND/UTILITY NAME Fragment Reference Fragment: Item1( variable1 variable2 , variable3 variable4 ) Item2( variable5 , variable7 ) variable6 variable8 432 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 463
Library Identification Each ACS, LSM, and CAP is assigned a unique identification number during LIBGEN. Use this number in HSC commands and utilities when identifying a specific ACSid, LSMid, or CAPid. • ACSid (acs-id) is a hexadecimal value from 00 through FF that identifies the LMU. An acs-id is the result of defining the SLIALIST macro during a LIBGEN. See ‘‘LIBGEN Macros’’ in the HSC Configuration Guide for information about the SLIALIST macro.
PAGE 464
How to Specify a CAPid A CAPid specifies a particular CAP in the library. Each CAP is identified by the LSMid of the LSM that the CAP is attached to and a CAP number to distinguish it from other CAPs in that LSM. CAP configurations differ based on the LSM type. The following configurations are possible: LSM (Model 4410) and PowderHorn LSM (Model 9310) This LSM is configured with either the standard 21-cell CAP or an enhanced CAP.
PAGE 465
• The AA:LL:CC format can be specified for any CAP hardware in any command that accepts a CAPid. This is the preferred format. Valid CAP numbers are: 00 indicates one of the following: - a 21-cell standard CAP the right-hand 40-cell CAP of an enhanced CAP the 20-cell CAP of a WolfCreek CAP a 14-cell or 10-cell removable magazine 9740 TimberWolf CAP the 3, 13-cell removable magazines for an SL8500 CAP.
PAGE 466
Ranges And Lists HSC commands and utilities often allow the user to specify ranges and lists of elements. 1. An inclusive range is indicated by a pair of elements of the same length and data type, joined by a dash. The first element must be strictly less than the second element. • A hexadecimal range consists of a pair of hexadecimal numbers (for example, 0A2-0AD, or 000-0FC). • A decimal range consists of a pair of decimal numbers (for example, 1-9, or 010-094). Leading zeros are not required.
PAGE 467
- You cannot increment two portions of a range element. If 111AAA is the first element, you cannot specify 112AAB for the second element. - The alphabetic portion of the VOLSER range is defined as being from character A to Z. To increment multi-character sequences, each character increments to Z. For instance, ACZ is part of the AAA-AMM range. Examples are: A00A0-A99A0 increments VOLSERs A00A0 through A09A0, then A10A0 through A99A0.
PAGE 468
2. A list consists of one or more elements. If more than one element is specified, the elements must be separated by a comma or a blank, and the entire list enclosed in parentheses. • For some HSC operator commands, an element may consist of a single item or a range. Refer to the individual command explanations for valid list entries. • In general, HSC utilities do not allow ranges to be specified in a list. The exception to this is a VOLSER list (vol-list) which does allow ranges to be specified.
PAGE 469
Control Statement Syntax Conventions The control statement for each utility program consists of a command (indicating the utility function) followed by parameters, as applicable, in 80-character card-image records. The standard syntax conventions for control statements are as follows: • The only valid control statement information area is from column 2 to column 72. Columns 73-80 are ignored. • Parameters are separated by one or more blanks or a comma.
PAGE 470
The following examples illustrate continuations used correctly: SCRPOOL NAME=STD36,RANGE+ (AAA000AAA999,ZZZ000ZZZ999) SCRPOOL NAME=STD36,RANGE(AAA000AAA999,ZZZ000ZZZ999) The following example illustrates a continuation used incorrectly: SCRPOOL NAME=STD36,RANGE(AAA000AAA999,ZZZ+ 000ZZZ999) - Users must enter a nonblank character in column 72 (e.g., an X). - PARMLIB control statements can be continued using the preceding continuation rules only if they are new format control statements.
PAGE 471
MEDia, RECtech, and MODel Parameters Table 29 describes the HSC commands and control statements that accept MEDia, MODel, and RECtech parameters. Table 29. MEDia, RECtech, and MODel Cross-reference Related Parameters Name Type Display Drive Command DETail Yes Yes Yes Displays the transports that are capable of the specified MEDia, RECtech, or MODel. When DETail is supplied, the MEDia and MODel are displayed for all transports.
PAGE 472
Table 29. MEDia, RECtech, and MODel Cross-reference (Continued) Name Type Related Parameters MEDia RECtech MODel Description Mount Command SUBpool, SCRTCH, PRIVAT Yes No No Mounts scratches that match the MEDia. If a SUBpool is supplied, a cartridge that matches MEDia within the subpool is mounted.
PAGE 473
Table 29. MEDia, RECtech, and MODel Cross-reference (Continued) Name Type Related Parameters MEDia RECtech MODel Description VOLATTR Control Statement N/A Yes Yes No The MEDia of a given volume must be defined here and the desired RECtech to be used on this volume may also be expressed. Lists are used to define a pool of volumes from which to select. If VOLATTR is improperly defined, scratch counts may be incorrect or volume-to-transport incompatibilities may exist.
PAGE 474
LIBGEN Macros The LIBGEN macros are shown below in alphabetical order. Refer to ‘‘Syntax Flow Diagrams’’ in the HSC Installation Guide for complete explanations of macro syntax and parameters, and the order in which they must be specified. 444 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 475
SLIACS macro acs0 SLIACS Additional Parameters Additional Parameters: ACSDRV=(esoteric0, ...,esoteric15) ,LSM=(lsm0,lsm1, ...,lsm23) ,STATION=(station0, ...,station15) SLIALIST macro acslist SLIALIST acs0, acs1,.....acs255 SLIDLIST macro drvelst0 SLIDLIST HOSTDRV= (drives0,...,drives15) SLIDRIVS macros drives0 SLIDRIVS ADDRESS=(addr0,addr1...) SLIENDGN macro SLIENDGN Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 445 1st ed.
PAGE 476
SLILIBRY macro SLILIBRY HOSTID=(host-id0,host-id1,...,host-id15) ,ACSLIST=acslist Optional Parameters Optional Parameters: CLN ,CLNPRFX= prefix 255 ,SMF= libtype ,NNLBDRV=(esoteric0,...,esoteric15) NOSCRTCH ,DELDISP= STKALSQN ,MAJNAME= qname SCRTCH . ,COMPRFX= commandchar SL ,SCRLABL= AL NL NSL ,EJCTPAS=password 446 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 477
SLILSM macro lsm0 SLILSM 4410 TYPE= 9310 9360 , - 9740 100 075 050 8500 DRIVE=(drvpanel0,...,drvpanel3) ,DRVELST=(drvelst0,...,drvelst3) ,PASTHRU=((ptppane10, S ),..., (ptppane18, M STD ,DOOR= S )) ,ADJACNT=(lsm1,...,lsm4) M ,WINDOW=(wndpanel0,...,wndpanel3) ECAP WC1 WC2 8500-1 8500-2 SLIRCVRY macro SLIRCVRY LABEL BOTH TCHIQE= NONE SHADOW JOURNAL STANDBY ALL SLISTATN macro station0 SLISTATN ADDRESS=(addr0,...addr15) Appendix A.
PAGE 478
HSC Control Statements Refer to Chapter 3, “HSC Control Statements and HSC Start Procedure” on page 83 for more information on control statement syntax and parameters. Control Data Set Definition (CDSDEF) control statement CDSDEF DSN1(dataset.name) ,VOL1(volser),UNIT1(unitname) ,DSN2(dataset.name) ,VOL2(volser),UNIT2(unitname) ,DSN2(dataset.
PAGE 479
LKEYDEF command and control statement LKEYDEF DATASET(dataset.name) DSN(dataset.name) UNIT(unitname) VOLume(volser) HOSTID(host-id) LKEYINFO control statement LKEYINFO PRODuct(product_identifier) SITEno(nnnnnnn) EXPRdate(yyyyddd) CUSTomer('customer_name') KEY(license_key_string) LMUPATH control statement LMUPATH ACS(aa) LMUADDR( , ) lmu_hostname nnn.nnn.nnn.nnn LMU Path Definition (LMUPDEF) command and control statement LMUPDEF DATASET(dataset.name) DSN(dataset.
PAGE 480
OPTion control statement OPTion TITLE(identifying-string) TRACE TRACEF Reconfiguration Definition (RECDEF) control statement RECDEF DSN1(dataset.name) ,VOL1(volser),UNIT1(unitname) ,DSN2(dataset.name) ,VOL2(volser),UNIT2(unitname) Scratch Subpool (SCRPOol) control statement , SCRPOol NAME(subpool-name) ,RANGE( range-start-range-end ) ,LABEL( SL NL AL NSL ALL ,HOSTID( host-id , host-list 450 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 481
Scratch Subpool Definition (SCRPDEF) command and control statement SCRPDEF DATASET(dataset.name) DSN(dataset.
PAGE 482
Tape Request (TAPEREQ) control statement (continued) , MEDia( STK2 LONGItud 18track 36track 36Atrack 36Btrack 36Ctrack HELical DD3 STK1R STK1R34 STK1R35 STK1RA STK1RA34 STK1RA35 STK1RB STK1RB34 STK1RB35 STK1RAB STK1RAB4 STK1RAB5 STK1RC STK1RC34 STK1RC35 STK2P STK2P34 STK2P35 STK2PA STK2PA34 STK2PA35 STK2PB STK2P STK2PB34 LONGItud ) RECtech( Standard CST MEDIA1 STD 1 3480 ECART E ECCST ETAPE Long MEDIA2 3490E ZCART Z HELical DD3 DD3A DD3B DD3C STK1 STK1R R ) STK2PB35 , MODel( model1 SUBPool(subpoo
PAGE 483
Tape Request Definition (TREQDEF) command/control statement TREQDEF DATASET(dataset.name) DSN(dataset.name) , host-id HOSTID( VOLume(volser) UNIT(unitname) ) Unit Attribute (UNITATTR) control statement UNITATTR ADDRess( unit-address unit-address-range , unit-address-list ) MODel( 4480 ) 4490 9490 9490EE SD3 9840 984035 T9840B T9840B35 T9840C T9840C35 T9940A T9940A35 T9940B T9940B35 IGNORE NETHOST(host-id) Appendix A.
PAGE 484
Unit Attribute Definition (UNITDEF) command/control statement UNITDEF DATASET(dataset.name) DSN(dataset.name) , HOSTID( host-id VOLume(volser) UNIT(unitname) ) Volume Attribute (VOLATTR) control statement VOLATTR SERial( volser vol-range , vol-list ) MEDia( Standard CST MEDIA1 STD 1 3480 ECART E ECCST ETAPE Long MEDIA2 3490E ZCART Z DD3A DD3B DD3C DD3D STK1R STK1U R U STK2 STK2P STK2W 454 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 485
Volume Attribute (VOLATTR) control statement (continued) RECtech( LONGItud 18track ) MAXclean(use-limit) 36track 36Atrack 36Btrack 36Ctrack HELical DD3 STK1R STK1R34 STK1R35 STK1RA STK1RA34 STK1RA35 STK1RB STK1RB34 STK1RB35 STK1RAB STK1RAB4 STK1RAB5 STK1RC STK1RC34 STK1RC35 STK2P STK2P34 STK2P35 STK2PA STK2PA34 STK2PA35 STK2PB STK2PB34 STK2PB35 Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 455 1st ed.
PAGE 486
Volume Attribute Definition (VOLDEF) command/control statement VOLDEF DATASET(dataset.name) DSN(dataset.name) , HOSTID( host-id ) 456 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 487
Utilities Refer to Chapter 4, “Utility Functions” on page 169 for more information on utility syntax and parameters.
PAGE 488
BACKup utility BACKup CDS( ) Copy Primary Secondary STandby OPTion( Analyze Restart Database Decompile (LIBGEN) utility LIBGEN Directory Rebuild (DIRBLD) utility DIRBLD EJECt utility EJECt Eject Method 1 Eject Method 2 Eject Method 1: CAP( , cap-list , VOLser( vol-list ) Eject Method 2: SCRTCH SUBpool(subpool-name) 458 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 489
EJECt utility (continued) Eject Method 2 (continued): MEDia( Standard ) RECtech( 18track CST 36Atrack MEDIA1 36Btrack STD 36Ctrack 1 DD3 3480 STK1R ECART STK1R34 E STK1R35 ECCST STK1RA STK1RA34 STK1RA35 ETAPE Long MEDIA2 3490E ZCART Z DD3A DD3B DD3C STK1 STK1R R STK2 STK2P ) STK1RB STK1RB34 STK1RB35 STK1RAB STK1RAB4 STK1RAB5 STK1RC STK1RC34 STK1RC35 STK2P STK2P34 STK2P35 STK2PA STK2PA34 STK2PA35 STK2PB STK2PB34 STK2PB35 Enter Cartridges utility ENTEr CAP(cap-id) SCRatch Appendix
PAGE 490
Journal OFFLoad utility OFFLoad MOVe utility Parameters MOVe Parameters: Flsm(lsm-id) Panel(panel-list) Row(row-list) Column(column-list) Volume(vol-list) TLsm(lsm-list) TPanel(panel) Reconfiguration utility START S reconfig-procname REPLace utility REPLaceall , VOLser( vol-list 460 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 491
RESTore utility RESTore YES APPly( NO NO ) GENerate( YES Only ) Short SCRAtch utility SCRAtch VOLser( , vol-list ) Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 461 1st ed.
PAGE 492
Scratch Redistribution (SCREdist) utility SCREdist ACS(acs-id) , LSM( BALtol(tolerance-value) SUBpool(subpool-name) lsm-list MEDia( ) LONGItud ) RECtech( LONGItud Standard CST 18track 36track MEDIA1 36Atrack STD 1 36Btrack 36Ctrack 3480 HELical ECART E DD3 STK1R ECCST STK1R34 ETAPE Long STK1R35 STK1RA MEDIA2 STK1RA34 3490E STK1RA35 ZCART Z HELical STK1RB STK1RB34 STK1RB35 DD3 DD3A STK1RAB STK1RAB4 DD3B DD3C STK1 STK1RAB5 STK1RC STK1RC34 STK1R STK1RC35 R STK2 STK2P34 S
PAGE 493
SET utility SET Options Options: ACSDRV(esoteric) ,FORACS(acs-id) ,FORHOST(host-id) CLNPRFX(prefix) COMPRFX(cmdhex) DELDISP( SCRTCH ) NOSCRTCH EJCTPAS( ) newpswd FREEZE( ON ,OLDPASS(oldpswd) ),FORLSMID(lsm-id) ,FORPANEL(panel) OFf HOSTID (newhost),FORHOST(oldhost) HSCLEVEL(OFF),FORHOST(host-id) MAJNAME(qname) NEWHOST(newhost) ,LIKEHOST(model-host) NNLBDRV( ) esoteric SCRLABL( SL ,FORHOST(host-id) ) AL NL NSL Appendix A.
PAGE 494
SET utility (continued) SET Options Options: SLIDRIVS( ) ,FORLSMID(lsm-id),FORPANEL(panel) addr0 ,...addr19 ,FORHOST(host-id) SLISTATN( ),FORACS(acs-id) stat1,...,stat16 ,FORHOST(host-id) SMF(libtype) TCHNIQE( NONE JOURNAL SHADOW ) BOTH STANDBY ALL UNSCratch utility , UNSCratch VOLser( vol-list Unselect utility UNSElect VOLser(volser) ,FORCE 464 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 495
Volume Report (VOLRpt) utility VOLRpt ACS(acs-id) VOLser ( , SORT( LSM( lsm-list volser vol-range ) ) volser ASCend ) LOC SEL DEScend USE NOSORT , vol-list VOLume ( VOL INS ) vol-range , vol-list , INCLude( * SCR NONSCR ERR ) EXCLude( , SCR NONSCR ERR ) NONERR SEL NONERR SEL NONSEL READable NONSEL READable UNREADable MEDEQUAL UNREADable MEDEQUAL NONMEDEQ NOEXTernal NONMEDEQ NOEXTernal VOLIST VOLDATA CDSDATA SUMMary( TOTal SUBpool TOTal,SUBpool ) Appendix A.
PAGE 496
Operator Commands Refer to ‘‘Operator commands’’ in the HSC Operator’s Guide for complete explanations of command syntax and parameters. CAP Preference (CAPPref) command and control statement CAPPref prefvlue lsm-id cap-id host-id cap-range , ( cap-list AUTO MANual ) CDs Enable/Disable command CDs Enable DSn(dsn) NEWVol(volser),NEWUnit(unitname) NEWLoc Disable DSn(dsn) Primary SEcndry STandby EXpand CLean command CLean dev-id dev-range host-id , ( dev-list ) 466 VM/HSC 6.
PAGE 497
Communications Path (COMMPath) command and control statement COMMPath METHod( HOSTid(host-id) CDS ) LMU LMU,acs-id LMUpath( acs-id acs-range VTAM ) VTAMpath(name) , acs-list LMUpath( acs-id ) acs-range VTAMpath(name) , acs-list VTAMpath(name) DELete LMUpath( acs-id acs-range ) VTAMpath (name) , acs-list VTAMpath (name) DISMount command DISMount , volser devaddr host-id Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 467 1st ed.
PAGE 498
Display command Display Acs Display Acs acs-id acs-range , ( acs-list Display ALl Display ALl Display ALLOC Display ALLOC Display Cap (all CAPs) Display Cap acs-id lsm-id cap-id Display CDS Display CDS 468 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 499
Display Cmd Display CMd COmmand command-name Display COMMPath Display COMMPath * HOSTid( ALL host-id ) , host-list Display DRives Display DRives Library ACS(acs-id) ACtive Idle LSM(lsm-id) ALl DETail Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 469 1st ed.
PAGE 500
Display Drives (continued) MEDia( LONGItud ) RECtech( Standard CST MEDIA1 STD 1 3480 ECART E ECCST ETAPE Long MEDIA2 3490E ZCART Z HELical DD3 DD3A DD3B DD3C DD3D STK1 STK1R R STK1U U STK2 STK2P STK2W MODel( LONGItud 18track 36track 36Atrack 36Btrack 36Ctrack HELical DD3 STK1R STK1R34 STK1R35 STK1RA STK1RA34 STK1RA35 STK1RB STK1RB34 STK1RB35 STK1RAB STK1RAB4 STK1RAB5 STK1RC STK1RC34 STK1RC35 STK2P STK2P34 STK2P35 STK2PA STK2PA34 STK2PA35 STK2PB STK2PB34 STK2PB35 IGNORE 4480 4490 9490 9490EE SD3 9840
PAGE 501
Display Exceptions Display EXceptns X Display LKEYDEF Display LKEYDEF Display LMUPDEF Display LMUPDEF Display LSM Display Lsm lsm-id lsm-range ( , lsm-list ) Display Message Display Message Msg msgnum Display MNTD Display MNTD Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 471 1st ed.
PAGE 502
Display MONitor Display MONitor ,PGMI ,L( cc name Display OPTion Display OPTion Display Requests Display Requests 472 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 503
Display SCRatch Display SCRatch acs-id SUBpool(subpool-name) DETail lsm-id MEDia( LONGItud ) RECtech( LONGItud Standard 18track CST MEDIA1 36track 36Atrack STD 36Btrack 1 3480 36Ctrack HELical ECART DD3 E ECCST STK1R STK1R34 ETAPE STK1R35 Long MEDIA2 STK1RA STK1RA34 3490E STK1RA35 ZCART Z STK1RB HELical STK1RB35 STK1RAB STK1RAB4 STK1RAB5 DD3 DD3A DD3B DD3C STK1 STK1R R STK2 STK2P ) STK1RB34 STK1RC STK1RC34 STK1RC35 STK2P STK2P34 STK2P35 STK2PA STK2PA34 STK2PA35 STK2PB STK2
PAGE 504
Display SCRPDEF Display SCRPDEF Display SRVlev Display SRVlev Display Status Display Status 474 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 505
Display THReshld Display THReshld acs-id SUBpool(subpool-name) lsm-id DETail MEDia( LONGItud ) RECtech( STD LONGItud 18track 36track 36Atrack 36Btrack 1 3480 36Ctrack HELical Standard CST MEDIA1 ECART E ECCST ETAPE Long MEDIA2 3490E ZCART Z HELical DD3 DD3A DD3B DD3C STK1 STK1R R STK2 STK2P ) DD3 STK1R STK1R34 STK1R35 STK1RA STK1RA34 STK1RA35 STK1RB STK1RB34 STK1RB35 STK1RAB STK1RAB4 STK1RAB5 STK1RC STK1RC34 STK1RC35 STK2P STK2P34 STK2P35 STK2PA STK2PA34 STK2PA35 STK2PB STK2PB34 STK2PB35 Di
PAGE 506
Display UNITDEF Display UNITDEF Display VOLDEF Display VOLDEF Display Volume Display Volser Volume volser vol-range , ( vol-list DETail ) DRAin CAP command ENter DRAin cap-id EJect , ( cap-list ) EJect command EJect Option 1 Option 2 00 Option 1: volser vol-range acs-id lsm-id , ( vol-list ) cap-id , ( cap-list 476 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 507
Eject Command (continued) Option 2: SCRTCH acs-id lsm-id SUBpool(subpool-name) VOLCNT(count ) cap-id , ( MEDia( cap-list LONGItud ) ) RECtech( LONGItud Standard CST 18track 36track MEDIA1 36Atrack STD 1 36Btrack 36Ctrack 3480 HELical ECART DD3 E ECCST STK1R STK1R34 ETAPE STK1R35 Long STK1RA MEDIA2 STK1RA34 3490E ZCART Z STK1RA35 STK1RB STK1RB34 HELical STK1RB35 DD3 DD3A STK1RAB STK1RAB4 DD3B DD3C STK1 STK1R R STK2 STK2P ) STK1RAB5 STK1RC STK1RC34 STK1RC35 STK2P STK2P34 STK
PAGE 508
ENter command 00 ENter acs-id SCRatch cap-id lsm-id Journal command Journal Full( ABEND Continue ) MODify command MODify F CAP cap-id lsm-id ONline OFFline lsm-id lsm-range , ( lsm-list ) LSM MONITOR command MONITOR MN PGMI ,L( ) cc name 478 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 509
Mount command Mount volser devaddr , host-id SCRTCH PRIVAT Readonly devaddr host-id SUBpool(subpool-name) MEDia( LONGItud Standard ) CST MEDIA1 STD 1 3480 ECART E ECCST ETAPE Long MEDIA2 3490E ZCART Z HELical DD3 DD3A DD3B DD3C STK1 STK1R R STK2 STK2P Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 479 1st ed.
PAGE 510
Mount/Dismount Options (MNTD) command and control statement , MNTD AUtocln( OFf ) HOSTID(host-id) ON Dismount( Auto ) EJctauto( Manual ON ) ACS(acs-id) MSg OFf Float( OFf ON MAXclean(count) MMount( ) ACS(acsid) Delete ) Reply MOuntmsg( Roll Noroll ) PASSTHRU(count) Scratch( SCRDISM( Manual Auto ) CURRENT ) ARCHIVE Unload( Noscr Scratch ) VOLWatch( OFf ON ) 480 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 511
MOVe command MOVe Flsm(lsm-id) Panel(pp) Row(row-list) Column(cc) Row(rr) Column(column-list) Volume( TLsm( volser vol-range , vol-list lsm-id , ) ) TPanel(pp) lsm-list Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 481 1st ed.
PAGE 512
OPTion command and control statement , OPTion Dialog( Both Log ) HOSTID(host-id) Console Off SHow SUppress DISCmsg( ) ACS(acs-id) EJLimit(count) ENTdup( Manual Auto LOGging( Standard Extended ) Output( Upper Mixed ) Repath( Yes No Reply SWAP( MVSmsg HSCmsg Viewtime(count) Warnmsg(minutes) RECover Host command RECover host-id FORCE RELease CAP command RELease cap-id 482 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 513
SENter command SENter cap-id SRVlev (Service Level) command SRVlev BASE FULL Stop Monitoring (STOPMN) command STOPMN PM PGMI ,L( ) cc name SWitch command SWitch Acs acs-id (1) Note: (1) ACS acs-id is optional in a single-ACS environment; it is required in a multiple-ACS environment. Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 483 1st ed.
PAGE 514
TRace command TRace comp-name , comp-list OFF comp-name , comp-list TRACELKP command TRACELKP table-name , table-list OFF table-name Vary Station command Vary ACS acs-id ONline OFFline acs-range , ( STation acs-list FORCE ) dev-id dev-range , ( dev-list ) 484 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 515
VIew command VIew CAPID(00:00:00) Row(00) Column(00) CAPID(cap-id) Lsm(lsm-id) Row(rr) Column(cc) CAp Lsm(00:00) Panel(00) Row(00) Column(00) Lsm(lsm-id) Panel(pp) Row(rr) Column(cc) CEll DRive Address(xxx) Host(host-id) Lsm(00:00) Column(00) Lsm(lsm-id) Column(cc) PLaygrnd Lsm(00:00) Column(0) PTp Lsm(lsm-id) Xlsm(ll) Column(c) Time(ttt) Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 485 1st ed.
PAGE 516
Warn command Warn SCRatch acs-id lsm-id THReshld(threshold-value) SUBpool(subpool-name) , MEDia( LONGItud ) RECtech( LONGItud Standard CST 18track 36Atrack MEDIA1 36Btrack STD 1 36Ctrack HELical 3480 ECCST DD3 STK1R STK1R34 STK1R35 ETAPE STK1RA Long MEDIA2 STK1RA34 STK1RA35 3490E STK1RB ZCART Z STK1RB34 STK1RB35 DD3 STK1RAB DD3A DD3B STK1RAB4 ECART E DD3C STK1RAB5 STK1RC STK1 STK1R STK1RC34 STK1RC35 R STK2 STK2P STK2P STK2P34 STK2P35 STK2PA STK2PA34 STK2PA35 STK2PB STK2PB
PAGE 517
HSC Diagnostic Commands LIst command LIst data-structure 16 address size TRace command TRace comp-name , comp-list OFF comp-name , comp-list Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 487 1st ed.
PAGE 518
SCP Operator Commands * (comment) Statement * comments AUTHorize Command , AUTHorize userid user-list ( CMDS MSGS route-codes NETVM NONE CANCEL command CANCEL taskid DUMP CP Command CP cmdparm DEFine Command DEFine CHAN chnum chtype CU chcu cutype DEV cuu devtype id DUMP Command DUMP comment 488 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 519
FILE Command FILE ddname BLOCKIO DISK CLEAR DEV vaddr DSN dsn vaddr DSN dsn CARD PNCH IUCV PRNT userid CLass class * HELP Command HELP HELP scp-command diag-command msgnum topic Modify Command (SCP) taskname hsc-command Query Command Query Active Conslog Dump Files jobname Label cuu Operator Perflog Reply System Trace Units Vstor Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 489 1st ed.
PAGE 520
Reply Command nn Reply text 'text' SET Command SET CONSlog ON OFF destination CLOSE DUMPOpts REset maxcount (userid (userid MSGtype MSGNOH MSG PERFlog ON OFF CLOSE SMF subsystem dest. interval , SUBTYPE( TRACE ON OFF CLOSE events SELect SET 490 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601 dest.
PAGE 521
destination: ( Class class userid TO AT node FOR events: , ALL DSP EXT IO I/O IUC MCK NONE PGM RST SIO SVC USR Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 491 1st ed.
PAGE 522
SLK Command SLK scp-command STArt Command STArt progname 50 taskid prio JOBRDR 50 progname ( parms JOBRDR (CLass class taskid prio AUTHRDR AUTHRDR taskid STOP Command STOP taskid STOPSCP Command (REIPL STOPSCP (LOGOFF SUBSYS Command SUBSYS sysname initpgm (parms 492 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 523
GCS Component Server Commands SLKGCS Command SLKGCS START DISPLAY STOP CANCEL Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 493 1st ed.
PAGE 524
CMS Operator Commands ACS EXEC ACS EXEC command INIT ( NOJOBs BREAK breakstr PARM=parmstr SUBMIT jobfname SLKJCL ftype (PARM=parmstr * fmode U class UTILity utility util-list ( NOSEND CMS HELP MENU HELP ACS scp-command =diag-command .hsc-command topic msgnum MSG 494 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 525
Appendix B. CP Commands and DIAGNOSE Codes Overview This appendix lists all of the CP commands and programming services codes that may be issued by the VM HSC. The VM HSC uses only privilege class G DIAGNOSE codes, and with the exception of MSGNOH, uses only privilege class G commands. Refer to ‘‘Define the ACS Service Machine’’ in the HSC Installation Guide for more information about MSGNOH.
PAGE 526
IUCV Communication vehicle for API and communication with Host to Host component. 496 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 527
Appendix C. Record Formats Overview This appendix provides the record formats for the HSC SMF, LOGREC, Volume Report, and Batch API records. These records are mapped by SMP/E-distributed macros. Each record format contains the following information: • • • • • • decimal representation hexadecimal representation type length label information description.
PAGE 528
Table 30 provides a key to the SMF record format tables. Table 30.
PAGE 529
SMF Records SMF Mapping Macros Table 31. Mapping Macros for SMF Records Macro Description SLSDVAR Volume Attribute Record Data Length (within other SMF records) SLSSFHDR SMF Record Header Information SLSSBLOS SMF LSM Operations Statistics SLSSCAPJ SMF CAP Eject Record SLSSCAPN SMF CAP Enter Record SLSSVSTA SMF Vary Station Record SLSSMLSM SMF Modify LSM Record SLSSLSB SMF LMU ATHS Statistics Buffer SLSSMF07 SMF Move Detail Record SLSSMF08 SMF View Detail Record Appendix C.
PAGE 530
SMF Record Formats SLSDVAR Table 32. SLSDVAR Record Format Dec Hex Type Length Label Description SLSDVAR - Distributed Volume Attribute Record Length FUNCTION: Pass the HSC Volume Attribute Record Length(VARL) for other Distributed HSC Macros to use as needed. 0 (0) HEXSTRING 40 (28) LENGTH 40 Cross Reference Name Len Offset Value SLSDVAR 000040 00 VARL - 28 500 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 531
SLSSFHDR Table 33. SLSSFHDR Record Format Dec Hex Type Length Label Description SLSSFHDR - SMF RECORD HEADER MAP FUNCTION: MAPS THE STANDARD SMF RECORD HEADER AS DEFINED IN THE IBM SMF MANUAL (GC28-1153). IBM PROVIDES NO MAPPING MACRO. MAPS THE ACHS EXTENSIONS TO THE HEADER.
PAGE 532
Table 33. SLSSFHDR Record Format (Continued) Dec Hex Type Length Label Description 18 (12) CHARACTER 4 OSHDSSID SUBSYSTEM ID 22 (16) SIGNED-HWORD 2 OSHDRSTY RECORD SUBTYPE. If adding new record subtype(s), change field OSHDMAXS and add an entry in the HSSUBS table of SLUPERF. Then reassemble modules SLSOOSMF, SLSOWSMF, and SLUPERF.
PAGE 533
Table 33. SLSSFHDR Record Format (Continued) Dec Hex Type Length Label Description 27 (1B) CONST OSHDVT27 (VTCS) VTV SCRATCH Event 28 (1C) CONST OSHDVT28 (VTCS) REPLICATE VTV->CLUSTERED VTSS Rqst 28 (1C) CONST OSHDMAXS MAXIMUM RECORD SUBTYPE VALUE 24 (18) LENGTH OSHDL LENGTH OF FIXED PORTION OF OSHDR 24 (18) OFFSET SLSSTYPE DEFINE EACH SMF SUBTYPE Appendix C. Record Formats 503 1st ed.
PAGE 534
Cross Reference Name Len Offset Value OSHDBLOS - 01 OSHDDATE 000004 0A OSHDDESC 000002 02 OSHDEJCT - 05 OSHDENTR - 06 OSHDFLAG 000001 04 OSHDL - 18 OSHDLRST - 04 OSHDMAXS - 1C OSHDMLSM - 03 OSHDRCTY 000001 05 OSHDRC07 - 07 OSHDRECL 000002 00 OSHDRSTY 000002 16 OSHDSID 000004 0E OSHDSSID 000004 12 OSHDSTV - 40 OSHDTIME 000004 06 OSHDVIEW - 08 OSHDVSTA - 02 OSHDVT09 - 09 OSHDVT10 - 0A OSHDVT11 - 0B OSHDVT12 - 0C OSHDVT13 - 0D OSHDVT
PAGE 535
Name Len Offset Value OSHDVT20 - 14 OSHDVT21 - 15 OSHDVT22 - 16 OSHDVT23 - 17 OSHDVT24 - 18 OSHDVT25 - 19 OSHDVT26 - 1A OSHDVT27 - 1B OSHDVT28 - 1C SLSSTYPE - 18 Appendix C. Record Formats 505 1st ed.
PAGE 536
SLSSBLOS Table 34. SLSSBLOS Record Format Dec Hex Type Length Label Description SLSSBLOS - LSM OPERATIONS STATISTICS FUNCTION: CONTAINS PERFORMANCE STATISTICS FOR THE LSM. THE SAME STRUCTURE IS USED TO CREATE THE SMF PERFORMANCE RECORD, HOWEVER THE CONTROL BLOCK HEADER IS ELIMINATED, AND ONLY THE FIXED AND MULTIPLE SECTIONS GENERATED. THE FIXED SECTION OF THE RECORD IS OSHDL OFF THE BEGINNING OF THE SMF RECORD.
PAGE 537
Table 34.
PAGE 538
SLSSCAPJ Table 35. SLSSCAPJ Record Format Dec Hex Type Len Label Description SLSSCAPJ - CAP EJECT SMF RECORD FUNCTION: USED TO HOLD INFORMATION PASSED TO THE ALS SMF WRITER SERVICE ROUTINE FOR THE CARTRIDGE EJECT EVENT.
PAGE 539
SLSSCAPN Table 36. SLSSCAPN Record Format Dec Hex Type Length Label Description SLSSCAPN - CAP ENTER SMF RECORD FUNCTION: USED TO HOLD INFORMATION PASSED TO THE ALS SMF WRITER SERVICE ROUTINE FOR THE CARTRIDGE ENTER EVENT. SYMBOLICS: &DSECT - DSECT OR CONTINUATION OF DATA AREA.
PAGE 540
SLSSVSTA Table 37. SLSSVSTA Record Format Dec Hex Type Length Label Description SLSSVSTA - VARY STATION SMF RECORD SUBTYPE MAP FUNCTION: CONTAINS A RECORD OF SUCCESSFUL SUBSYSTEM VARY COMMANDS. SYMBOLICS: &DSECT - DSECT OR CONTINUATION OF DATA AREA. YES - PRODUCE A DSECT LISTING NO - NO DSECT 0 (0) AREA 2 SLSSVSTA VARY STATION SMF RECORD SUBTYPE 0 (0) SIGNED-FWORD 4 SVSTFLAG FLAGS 0 (0) A-ADDR 1 SVSTFLG0 TYPE OF STATISTIC FLAGS 1... .... X’80’ SVSTVON VARY ON .1.. ....
PAGE 541
Cross Reference Name Len Offset Value SLSSVSTA 000002 00 SVSTACID 000001 04 SVSTACS - 10 SVSTATID 000002 04 SVSTFLAG 000004 00 SVSTFLG0 000001 00 SVSTFOR - 20 SVSTL - 08 SVSTSTBY - 08 SVSTUNID 000002 06 SVSTVACS - 04 SVSTVOF - 40 SVSTVON - 80 Appendix C. Record Formats 511 1st ed.
PAGE 542
SLSSMLSM Table 38. SLSSMLSM Record Format Dec Hex Type Length Label Description SLSSMLSM - MODIFY LSM SMF RECORD SUBTYPE MAP FUNCTION: CONTAINS A RECORD OF SUCCESSFUL SUBSYSTEM MODIFY COMMANDS. SYMBOLICS: &DSECT - DSECT OR CONTINUATION OF DATA AREA. YES - PRODUCE A DSECT LISTING NO - NO DSECT 0 (0) AREA 2 SLSSMLSM MODIFY LSM SMF RECORD SUBTYPE 0 (0) SIGNED-FWORD 4 SMLSFLAG FLAGS 0 (0) A-ADDR 1 SMLSFLG0 TYPE OF STATISTIC FLAGS 1... .... X’80’ SMLSVON MODIFY ON .1.. ....
PAGE 543
SLSSLSB Table 39. SLSSLSB Record Format Dec Hex Type Length Label Description SLSSLSB - LMU STATISTICS BUFFER DATA BLOCK FUNCTION: THE CALLER OF THE SLSLRSTA FUNCTION SUPPLIES THE ADDRESS OF A DATA BUFFER TO BE FILLED IN WITH THE RESPONSE DATA FROM AN LMU READ STATISTICS REQUEST. THE DATA AREA CONTAINS 16 ENTRIES, ONE FOR EACH LSM CONFIGURED TO THE LMU. INFORMATION SUPPLIED ABOUT EACH LSM INCLUDES: 1) LSM ARM UTILIZATION PERCENTAGE. 2) LSM NUMBER MASTER PASSTHRU PORT ONE IS CONNECTED TO.
PAGE 544
Table 39.
PAGE 545
SLSSMF07 Table 40. SLSSMF07 Record Format Dec Hex Type Length Label Description DSECT: SLSSMF07 - HSC RECORD TYPE 7 MAPPING MACRO FUNCTION: MAPS THE SUBTYPE 7 SMF RECORD PRODUCED BY THE HSC. THIS IS PRODUCED FOR EACH SUCCESSFUL MOVE INITIATED BY THE HSC. THESE RECORDS WERE ORIGINALLY DESIGNED TO PROVIDE OUR FIELD AND MARKETING STAFFS WITH STATISTICAL CARTRIDGE MOVEMENT, LMU TIMING, AND ROBOTICS TIMING INFORMATION. THESE RECORDS REPORT MOVEMENT SOURCE, DESTINATION, LMU TIMES, AND ROBOTICS TIMES.
PAGE 546
Table 40. SLSSMF07 Record Format (Continued) Dec 2 Hex (2) Type Length Label Description .... .1.1 X’05’ SMF07OPR HSC OPERATOR COMMAND INITIATED .... .11. X’06’ SMF07TMI VM TMI INTERFACE SMF07FLG FLAG BYTE 1... .... X’80’ SMF07DSV SMF07DRS CONTAINS A DRIVE DEVICE NUM .1.. .... X’40’ SMF07DTV SMF07DRT CONTAINS A DRIVE DEVICE NUM ..1. .... X’20’ SMF07CNV SMF07CON CONTAINS VALID DATA ...1 .... X’10’ SMF07LMD LMU DATA IS AVAILABLE .... 1...
PAGE 547
Table 40. SLSSMF07 Record Format (Continued) Dec Hex Type Length Label Description 27 (1B) CHARACTER 8 SMF07US1 THIS SHOULD ALWAYS ONLY CONTAIN DISPLAYABLE EBCDIC (INC BLANKS). JOBNAME IF REQ FROM JOB PROCESSING, HSC UTILITY, OR HSC PROGRAMATIC INTERFACE, OR HSC INITIATED. ‘CONSOLE’ IF INITIATED BY THE OPERATOR VIRTUAL MACHINE NAME THE IUCV RECEIVED FROM (VM TMS INTERFACE) 35 (23) CHARACTER 8 SMF07US2 THIS SHOULD ALWAYS ONLY CONTAIN DISPLAYABLE EBCDIC (INC BLANKS).
PAGE 548
Table 40.
PAGE 549
Table 40. SLSSMF07 Record Format (Continued) Dec 88 Hex (58) Type Length LENGTH Label SMF07SL Description LENGTH OF NON-LMU PORTION OF SUBRECORD THIS MAPS THE DATA RETURNED BY THE LMU. IT IS ONLY AVAILABLE IF SMF07LMD IS ON. NOTE THAT THE LMU TIMES ARE ONLY VALID TO A TENTH OF A SECOND. THE HSC CONVERTS THE TIMES TO HUNDREDTHS TO BE CONSISTENT WITH OTHER TIMES. 88 (58) HEXSTRING 4 SMF07LTO INTERVAL IN HUNDREDTHS OF A SECOND THE LMU HAD THE REQUEST.
PAGE 550
Cross Reference Name Len Offset Value SLSSMF07 000001 00 SMF07CNV - 20 SMF07CON 000004 2B SMF07CPO 000004 17 SMF07DEI 000001 3D SMF07DNS - 10 SMF07DRO 000004 60 SMF07DRQ 000004 64 SMF07DRS 000002 43 SMF07DRT 000002 45 SMF07DSS - 20 SMF07DSV - 80 SMF07DTV - 40 SMF07DWT 000004 5C SMF07EDT 000004 53 SMF07EJT - 01 SMF07ETM 000004 4F SMF07FLG 000001 02 SMF07HSC - 01 SMF07JOB - 02 SMF07L - 78 SMF07LBL 000001 2F SMF07LDT 000004 0F SMF07LMD -
PAGE 551
Name Len Offset Value SMF07MVU - ‘CVAL’ SMF07MVV - ‘CVAL’ SMF07NRD 000004 13 SMF07NTR - 02 SMF07OPR - 05 SMF07ORO 000004 68 SMF07ORQ 000004 6C SMF07PRF - 08 SMF07PRG - 04 SMF07PRO 000004 70 SMF07PRQ 000004 74 SMF07RQS 000001 01 SMF07SAC 000001 38 SMF07SCE - ‘CVAL’ SMF07SCO 000001 3C SMF07SCP - ‘CVAL’ SMF07SDR - ‘CVAL’ SMF07SDT 000004 4B SMF07SFI - ‘CVAL’ SMF07SFN - ‘CVAL’ SMF07SF1 000001 36 SMF07SL - 58 SMF07SLS 000001 39 SMF07SPN 0000
PAGE 552
Name Len Offset Value SMF07TDR - ‘CVAL’ SMF07TDT 000004 07 SMF07TDW - ‘CVAL’ SMF07TLS 000001 3F SMF07TMI - 06 SMF07TNM 000001 57 SMF07TPN 000001 40 SMF07TRO 000001 41 SMF07TTM 000004 03 SMF07TYP 000001 00 SMF07UNK - 00 SMF07US1 000008 1B SMF07US2 000008 23 SMF07UTL - 03 SMF07VMT - ‘CVAL’ SMF07VMU - ‘CVAL’ SMF07VMV - ‘CVAL’ SMF07VOL 000006 30 522 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 553
SLSSMF08 Table 41. SLSSMF08 Record Format Dec Hex Type Length Label Description SLSSMF08 - HSC RECORD TYPE 8 MAPPING MACRO FUNCTION: MAPS THE SUBTYPE 8 SMF RECORD PRODUCED BY THE HSC. THIS IS PRODUCED FOR EACH SUCCESSFUL VIEW COMMAND INITIATED BY THE HSC. SPECIAL CONSIDERATIONS: This data represents a record that is written out to the SMF data set.
PAGE 554
Cross Reference Name Len Offset Value SLSSMF08 000001 00 SMF08ACS 000001 00 SMF08CAP - 02 SMF08CEL - 01 SMF08CID 000001 02 SMF08COL 000001 07 SMF08CUA 000002 12 SMF08DRV - 03 SMF08HST 000008 0A SMF08L - 14 SMF08LSM 000001 01 SMF08LSM2 000001 05 SMF08MAG 000001 03 SMF08PNL 000001 05 SMF08PTP - 04 SMF08ROW 000001 06 SMF08RTM 000001 08 SMF08SLT 000001 06 SMF08TYP 000001 04 SMF08VTM 000001 09 SMF08XPT 000001 06 524 VM/HSC 6.
PAGE 555
LOGREC Records LOGREC Mapping Macros Table 42.
PAGE 556
LOGREC Record Formats SLSSLHDR Table 43. SLSSLHDR Record Format Dec Hex Type Length Label Description SLSSLHDR - LOGREC RECORD HEADER MAP FUNCTION: MAPS THE STANDARD LOGREC RECORD HEADER AS DEFINED IN THE EREP MANUAL (GC28-1378). IBM PROVIDES NO MAPPING MACRO. MAPS THE ACHS EXTENSIONS TO THE HEADER.
PAGE 557
Table 43. SLSSLHDR Record Format (Continued) Dec Hex Type 32 (20) OFFSET 32 (20) HEXSTRING 32 (20) CONST 432 (1B0) HEXSTRING 435 (1B3) 436 Length Label Description OLHDERID ERROR ID OLHDRSDW SDWA SLSSTYPE HSC software error subtype LOGREC data overlays SDWA area.
PAGE 558
Table 43. SLSSLHDR Record Format (Continued) Dec 652 Hex (28C) Type Length LENGTH 528 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 559
Cross Reference Name Len Offset Value LTYPAREA - 282 LTYP4001 - 4001 LTYP5000 - 5000 LTYP6501 - 6501 LTYP6502 - 6502 LTYP6503 - 6503 LTYP6504 - 6504 LTYP6505 - 6505 LTYP6506 - 6506 LTYP7000 - 7000 LTYP7001 - 7001 LTYP8500 - 8500 LTYP8501 - 8501 LTYP9201 - 9201 OLHDCDCT 000001 06 OLHDCPID 000008 10 OLHDDATE 000004 08 OLHDERF - 20 OLHDERID - 20 OLHDETIM 000004 288 OLHDJBID 000008 18 OLHDKEY1 000001 00 OLHDKEY2 000001 01 OLHDL - 28C OLH
PAGE 560
Name Len Offset Value OLHDRVRA 000006 1B4 OLHDSMS 000001 02 OLHDSOFT - 40 OLHDSTC 000004 284 OLHDSW2 000001 03 OLHDTFLG - 08 OLHDTIME 000004 0C OLHDVS2 - 80 SLSSTYPE - 20 530 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 561
SLSSVLG1 Table 44. SLSSVLG1 Record Format Dec Hex Type Length Label Description SLSSVLG1 - VOL/CELL LOGREC RECORD FORMAT 1 FUNCTION: MAPS LOGREC RECORD CREATED WHEN A VOLUME IS FORCE UNSELECTED SYMBOLICS: &DSECT - DSECT OR CONTINUATION OF DATA AREA. YES - PRODUCE A DSECT LISTING NO - NO DSECT 0 (0) AREA 16385 (4001) CONST 2 SLSSVLG1 VOL/CELL FORCE UNSELECT RECORD VLG1SUBT SUBTYPE X’4001’.
PAGE 562
Cross Reference Name Len Offset Value SLSSVLG1 000002 00 VLG1HDR 000004 00 VLG1HOST 000008 0C VLG1JOBN 000008 14 VLG1KEY 000001 09 VLG1L - 36 VLG1LEN 000004 04 VLG1OWNR 000008 22 VLG1SP 000001 08 VLG1SUBT - 4001 VLG1VOLS 000006 1C 532 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 563
SLSSBLOG Table 45. SLSSBLOG Record Format Dec Hex Type Length Label Description SLSSBLOG - INIT/TERM LOGREC RECORD FUNCTION: THIS MAPS THE LOGREC RECORD CREATED BY SLSBINIT WHENEVER THE SUBSYSTEM IS INITIALIZED OR TERMINATED, NORMALLY OR ABNORMALLY SYMBOLICS: &DSECT - DSECT OR CONTINUATION OF DATA AREA.
PAGE 564
Cross Reference Name Len Offset Value BLOGABND - 20 BLOGCNCL - 10 BLOGFLAG 000004 00 BLOGFLG0 000001 00 BLOGID - 5000 BLOGL - 08 BLOGRECO - 08 BLOGSHTD - 40 BLOGSTRT - 80 SLSSBLOG 000002 00 534 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 565
SLSSLLG1 Table 46.
PAGE 566
Table 46.
PAGE 567
Table 46. SLSSLLG1 Record Format (Continued) Dec Hex Type Length .1.. .... X’40’ Label Description LLG1STTC STATION IS A NETWORK IP ADDRESS 24 LLG1SHNM STATION NETWORK HOST NAME FOR TCP/IP HOSTNAME ADDRESS: 102 (66) CHARACTER FOR TCP/IP NETWORK ADDRESS: 126 (7E) HEXSTRING 4 LLG1STCP STATION NETWORK IP ADDRESS 130 (82) HEXSTRING 22 -RESERVED- RESERVED FOR FUTURE USE 152 (98) LENGTH LLG1L Appendix C. Record Formats 537 1st ed.
PAGE 568
Cross Reference Name Len Offset Value LLG1ACKE - 24 LLG1ACS 000001 0C LLG1BBLK - 64 LLG1DBKE - 1C LLG1ECD 000001 0F LLG1ERSP - 18 LLG1ERTP - 34 LLG1HDFL 000001 5D LLG1HDR 000004 00 LLG1ILGL - 33 LLG1INVB - 28 LLG1INVR - 10 LLG1ITYP - 84 LLG1KEY 000001 09 LLG1L - 98 LLG1LEN 000004 04 LLG1LMLV 000002 63 LLG1NCJI - 09 LLG1NEOB - 03 LLG1NEOT - 05 LLG1NHNL - 07 LLG1NING - 06 LLG1NLRQ - 0C LLG1NNUM - 0B LLG1NSHP - 08 LLG1NSOB - 02 LL
PAGE 569
Name Len Offset Value LLG1NWSN - 32 LLG1RCDE 000001 10 LLG1RNTN - 14 LLG1RQST 000044 11 LLG1RSPN 000032 3D LLG1SHNM 000024 66 LLG1SNOB - 0C LLG1SP 000001 08 LLG1STCP 000004 7E LLG1STHN - 80 LLG1STN 000002 0D LLG1STTC - 40 LLG1STYP 000001 65 LLG1SUBT - 6501 LLG1SWAT - 0D LLG1UNKB - 20 SLSSLLG1 000002 00 Appendix C. Record Formats 539 1st ed.
PAGE 570
SLSSLLG2 Table 47. SLSSLLG2 Record Format Dec Hex Type Length Label Description SLSSLLG2 - LMU DRIVER LOGREC RECORD FORMAT TWO FUNCTION: MAPS LOGREC RECORD CREATED WHEN AN INVALID BLOCK IS RECEIVED FROM THE LMU SYMBOLICS: &DSECT - DSECT OR CONTINUATION OF DATA AREA.
PAGE 571
Table 47.
PAGE 572
SLSSLLG3 Table 48. SLSSLLG3 Record Format Dec Hex Type Length Label Description SLSSLLG3 - LMU DRIVER LOGREC RECORD FORMAT THREE FUNCTION: DEFINES FORMAT OF DOOR OPEN LOGREC RECORD SYMBOLICS: &DSECT - DSECT OR CONTINUATION OF DATA AREA.
PAGE 573
SLSSLLG4 Table 49. SLSSLLG4 Record Format Dec Hex Type Length Label Description SLSSLLG4 - LMU DRIVER LOGREC RECORD FORMAT FOUR FUNCTION: DEFINES FORMAT OF LMU DEGRADED RECORD SYMBOLICS: &DSECT - DSECT OR CONTINUATION OF DATA AREA.
PAGE 574
Cross Reference Name Len Offset Value LLG4COND 000001 0E LLG4DEVC 000002 0C LLG4FSC 000004 10 LLG4HDR 000004 00 LLG4KEY 000001 09 LLG4L - 14 LLG4LEN 000004 04 LLG4SP 000001 08 LLG4SUBT - 6504 SLSSLLG4 000002 00 544 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 575
SLSSLLG5 Table 50. SLSSLLG5 Record Format Dec Hex Type Length Label Description SLSSLLG5 - DUAL LMU STATUS CHANGE LOGREC RECORD FUNCTION: DEFINES FORMAT OF DUAL LMU STATUS CHANGE LOGREC RECORD SYMBOLICS: &DSECT - DSECT OR CONTINUATION OF DATA AREA.
PAGE 576
Table 50. SLSSLLG5 Record Format (Continued) Dec Hex Type Length Label Description 1... .... X’80’ LLG5STHN STATION IS A NETWORK HOSTNAME .1.. .... X’40’ LLG5STTC STATION IS A NETWORK IP ADDRESS 24 LLG5SHNM STATION NETWORK HOSTNAME FOR TCP/IP HOSTNAME ADDRESS: 20 (14) CHARACTER FOR TCP/IP NETWORK ADDRESS: 44 (2C) HEXSTRING 4 LLG5STCP STATION NETWORK IP ADDRESS 48 (30) HEXSTRING 24 -RESERVED- RESERVED FOR FUTURE USE 72 (48) LENGTH 546 VM/HSC 6.
PAGE 577
Cross Reference Name Len Offset Value LLG5ACS 000001 0C LLG5HDR 000004 00 LLG5KEY 000001 09 LLG5L - 48 LLG5LEN 000004 04 LLG5NMST 000001 11 LLG5NSLV 000001 12 LLG5OMST 000001 0F LLG5OSLV 000001 10 LLG5SHNM 000024 14 LLG5SP 000001 08 LLG5STCP 000004 2C LLG5STHN - 80 LLG5STN 000002 0D LLG5STTC - 40 LLG5STYP 000001 13 LLG5SUBT - 6505 SLSSLLG5 000002 00 Appendix C. Record Formats 547 1st ed.
PAGE 578
SLSSLLG6 Table 51. SLSSLLG6 Record Format Dec Hex Type Length Label Description SLSSLLG6 - Robotic Motion & Softfail Counts LOGREC Record FUNCTION: DEFINES FORMAT OF Robotic Motion & Softfail Counts Record SYMBOLICS: &DSECT - DSECT OR CONTINUATION OF DATA AREA.
PAGE 579
Table 51. SLSSLLG6 Record Format (Continued) Dec Hex Type Length Label Description .... 1... X’08’ LLG6L12AV LSM 12 Configured if flag is on. .... .1.. X’04’ LLG6L13AV LSM 13 Configured if flag is on. .... ..1. X’02’ LLG6L14AV LSM 14 Configured if flag is on. .... ...1 X’01’ LLG6L15AV LSM 15 Configured if flag is on.
PAGE 580
Table 51.
PAGE 581
Cross Reference Name Len Offset Value LLG6ACS 000001 0C LLG6FLG1 000001 0E LLG6FLG2 000001 0F LLG6HDR 000004 00 LLG6KEY 000001 09 LLG6L - 90 LLG6LEN 000004 04 LLG6L0AV - 80 LLG6L0RM 000004 10 LLG6L0SF 000004 14 LLG6L1AV - 40 LLG6L1RM 000004 18 LLG6L1SF 000004 1C LLG6L10AV - 20 LLG6L10RM 000004 60 LLG6L10SF 000004 64 LLG6L11AV - 10 LLG6L11RM 000004 68 LLG6L11SF 000004 6C LLG6L12AV - 08 LLG6L12RM 000004 70 LLG6L12SF 000004 74 LLG6L13AV - 0
PAGE 582
Name Len Offset Value LLG6L2AV - 20 LLG6L2RM 000004 20 LLG6L2SF 000004 24 LLG6L3AV - 10 LLG6L3RM 000004 28 LLG6L3SF 000004 2C LLG6L4AV - 08 LLG6L4RM 000004 30 LLG6L4SF 000004 34 LLG6L5AV - 04 LLG6L5RM 000004 38 LLG6L5SF 000004 3C LLG6L6AV - 02 LLG6L6RM 000004 40 LLG6L6SF 000004 44 LLG6L7AV - 01 LLG6L7RM 000004 48 LLG6L7SF 000004 4C LLG6L8AV - 80 LLG6L8RM 000004 50 LLG6L8SF 000004 54 LLG6L9AV - 40 LLG6L9RM 000004 58 LLG6L9SF 000004 5C
PAGE 583
SLSSDJLR Table 52. SLSSDJLR Record Format Dec Hex Type Length Label Description SLSSDJLR - DATABASE JOURNALING LOGREC MAP FUNCTION: TO MAP THE VARIABLE LENGTH AREA OF THE JOURNALLING ERDS LOG RECORD WHICH BEGINS AT LABEL OLHDRCRD OF OLHDR LOGREC MAPPING MACRO. SPECIFYING OLHDR TYPE=7000 WILL GENERATE THIS MAP VIA AN INNER MACRO CALL WITHIN OLHDR. SYMBOLICS: &DSECT - DSECT OR CONTINUATION OF DATA AREA.
PAGE 584
Table 52. SLSSDJLR Record Format (Continued) Dec Hex Type Length Label Description 120 (78) CHARACTER 4 DJLRUN42 ALTERNATE JOURNAL’S UNIT NAME 124 (7C) CHARACTER 4 DJLRUN41 INITIAL JOURNAL’S UNIT NAME 128 (80) AREA 8 -RESERVED- FORCE THE LENGTH OF DJLR TO A 128 (80) LENGTH DJLRL DOUBLE-WORD MULTIPLE FOR GETMAIN.
PAGE 585
SLSSPSWI Table 53. SLSSPSWI Record Format Dec Hex Type Length Label Description SLSSPSWI - PRIMARY/SHADOW SWITCH LOGREC RECORD FUNCTION: THIS MAPS THE LOGREC RECORD CREATED BY SLSDRDSR WHENEVER THE SUBSYSTEM SWITCHES THE DATABASE FROM PRIMARY TO SHADOWING MODE SYMBOLICS: &DSECT - DSECT OR CONTINUATION OF DATA AREA.
PAGE 586
Cross Reference Name Len Offset Value PSWITERR 000004 04 PSWITFLG 000004 00 PSWITID - 7001 PSWITL - 84 PSWPRDCB 000004 08 PSWPRFLG 000001 00 PSWPRQNM 000044 16 PSWPRUCB 000004 0C PSWPRVOL 000006 10 PSWSCDCB 000004 44 PSWSCFLG 000001 01 PSWSCQNM 000044 52 PSWSCUCB 000004 48 PSWSCVOL 000006 4C SLSSPSWI 000002 00 556 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 587
SLSSRL00 Table 54. SLSSRL00 Record Format Dec Hex Type Length Label Description SLSSRL00 - RECOVERY ERDS RECORD 00 FUNCTION: THIS MAPS THE LOGREC RECORD CREATED BY SLSRAURE. IT CONTAINS THE LSM ID OF AN LSM REQUIRING AUDIT SYMBOLICS: &DSECT - DSECT OR CONTINUATION OF DATA AREA.
PAGE 588
SLSSRL01 Table 55. SLSSRL01 Record Format Dec Hex Type Length Label Description SLSSRL01 - RECOVERY ERDS RECORD 01 FUNCTION: THIS MAPS THE LOGREC RECORD CREATED BY SLSRHRVC. IT CONTAINS THE HOST ID OF A HOST BEING RECOVERED. SYMBOLICS: &DSECT - DSECT OR CONTINUATION OF DATA AREA.
PAGE 589
SLSSHLG1 Table 56. SLSSHLG1 Record Format Dec Hex Type Length Label Description SLSSHLG1 - Host Communications LOGREC format 1 FUNCTION: Defines the LOGREC record formatted for method switches.
PAGE 590
Table 56. SLSSHLG1 Record Format (Continued) Dec Hex Type Length Label Description ..1. .... X’20’ HLG1IWRT Initiated by WRITE function error ...1 ....
PAGE 591
Cross Reference Name Len Offset Value HLG1FLG1 000001 38 HLG1FLG2 000001 39 HLG1HDR 000004 00 HLG1ICMD - 80 HLG1ID - ‘CVAL’ HLG1IICN - 10 HLG1INTH 000008 20 HLG1IOTH - 40 HLG1IWRT - 20 HLG1KEY 000001 09 HLG1L - 80 HLG1LCLH 000008 10 HLG1LEN 000004 04 HLG1NLP 000004 28 HLG1NMTH 000004 28 HLG1PLP 000004 28 HLG1PMTH 000004 28 HLG1RC 000004 0C HLG1SLSI 000001 3C HLG1SP 000001 08 HLG1SUBT - 9201 HLG1SWTH 000008 18 Appendix C.
PAGE 592
Volume Report and Batch API Records Volume Report and Batch API Mapping Macros These SMP/E-distributed macros map both Volume Report and Batch API records. Refer to “Batch API Records” on page 593 to see SLUVDDAT and SLUVPDAT, which are used only by the Batch API. Table 57.
PAGE 593
Volume Report and Batch API Record Formats SLUVADAT Table 58. SLUVADAT Record Format Dec Hex Type Length Label Description SLUVADAT - FLAT FILE ACS/LSM INFORMATION DSECT FUNCTION: DESCRIBES THE ACS/LSM INFORMATION WHICH MAY BE GENERATED TO THE FLAT FILE BY THE VOLUME REPORT UTILITY 0 (0) STRUCTURE SLUVADAT 0 (0) CHARACTER 1 -RESERVED- RECORD TYPE (C’A’) 1 (1) HEXSTRING 1 ACSNUMBR ACS NUMBER 2 (2) BITSTRING 1 ACSSTAT STATUS FLAG ACSDUALL 1... .... - DUAL LMU 1... ....
PAGE 594
Table 58. SLUVADAT Record Format (Continued) Dec 2 Hex (2) Type Length Label Description .1.. .... X’40’ LSMOFFPN .1.. .... - OFFLINE PENDING .... 1... X’08’ LSMPTPRO .... 1... - PTPS REORDERED 1111 1111 X’FF’ LSMNONEX 1111 1111 - NON-EXISTENT LSM LSMVCAMF FLAG BYTE 1... .... X’80’ LSMAUDIP 1... .... - AUDIT IN PROCESS .1.. .... X’40’ LSMVCAMR .1.. ....
PAGE 595
Table 58.
PAGE 596
Table 58. SLUVADAT Record Format (Continued) Dec Hex Type Length Label Description ...1 ..1. X’12’ LSMCISDR ...1 ..1. - CIMARRON INSIDE DOOR ...1 ..11 X’13’ LSMCWIDN ...1 ..11 - CIMARRON 20-DRIVE PANEL ...1 .1.. X’14’ LSMCWIDD ...1 .1.. CIMARRON 20-DRIVE PANEL ADJACENT TO DOOR ..1. .... X’20’ LSMWPNL0 ..1. .... - WOLF PANEL 0 ..1. ...1 X’21’ LSMW2PSL ..1. ...1 - WC PANEL 2 WITH PTP (SLAVE) ..1. ..1. X’22’ LSMWP0PT ..1. ..1. - WOLF PANEL 0 W/PTP ..1. ..11 X’23’ LSMW1NOD ..1. ..
PAGE 597
Table 58. SLUVADAT Record Format (Continued) Dec Hex Type Length Label Description 1... .... X’80’ LSMELDRV 1... .... - ELIB DRIVE 1... ...1 X’81’ LSMELCAP 1... ...1 - ELIB CAP 1... ..1. X’82’ LSMELCEL 1... ..1. - ELIB STORAGE 1... ..11 X’83’ LSMELCE3 1... ..11 - ELIB STORAGE 1... .1.. X’84’ LSMELCE4 1... .1..
PAGE 598
Name Len Offset Value LSMCDRVP - 06 LSMCDR10 - 07 LSMCIM - 01 LSMCINPN - 10 LSMCIN19 - 11 LSMCISDR - 12 LSMCLCUP - 08 LSMCLNNM 000002 26 LSMCNOCL - 09 LSMCPTMP - 04 LSMCSTMP - 05 LSMCWIDD - 14 LSMCWIDN - 13 LSMDPNUM 000001 1E LSMELCAP - 81 LSMELCEL - 82 LSMELCE3 - 83 LSMELCE4 - 84 LSMELDRV - 80 LSMELIB - 07 LSMENTLN - B8 LSMFRECL 000002 24 LSMHCLVL 000006 30 LSMHSTID 000008 03 LSMHWTYP 000001 0E LSMIDPNO 000001 17 LSMLCLSL 000
PAGE 599
Name Len Offset Value LSMNADLS 000001 1F LSMNCIPN 000001 1D LSMNCLSL 000002 28 LSMNCOPN 000001 1B LSMNDPPN 000001 15 LSMNONEX - FF LSMNPGCS 000001 12 LSMNRIPN 000001 1C LSMNROPN 000001 1A LSMNUMBR 000001 00 LSMNXPRT 000001 16 LSMODPNO 000001 18 LSMOFFPN - 40 LSMPANLS 000006 3E LSMPCCNT 000002 01 LSMPFLG 000001 03 LSMPFRZ - 80 LSMPFRZL - 03 LSMPNLEL - 06 LSMPNLTY 000001 00 LSMPNTOT 000001 0F LSMPOWDR - 04 LSMPTPNO 000001 11 LSMPTPRO -
PAGE 600
Name Len Offset Value LSMTWLF - 06 LSMVCAMF 000001 02 LSMVCAMR - 40 LSMWOLF - 03 LSMWPNL0 - 20 LSMWPNL2 - 25 LSMWPNL3 - 27 LSMWP0PT - 22 LSMWP1DR - 24 LSMWP2PT - 26 LSMWP3DR - 28 LSMWP41C - 29 LSMWP42C - 30 LSMW3NOC - 31 LSMW1NOD - 23 LSMW2PSL - 21 LSMW3DNC - 32 LSMW3WIN - 33 LSMW4CCN - 36 LSMW4CNC - 35 570 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 601
SLUVCDAT Table 59.
PAGE 602
Table 59. SLUVCDAT Record Format (Continued) Dec Hex Type Length Label Description .... ...1 X’01’ CFGSCRAL .... ...1 - AL (ANSI) .... ..1. X’02’ CFGSCRNL .... ..1. - NL (NONLABELLED) .... ..11 X’03’ CFGSCRNS .... ..11 - NSL (NON-STANDARD) .... .1.. X’04’ CFGSCRBL .... .1.. - BLP (BYPASS LBL PROC) .... .1.1 X’05’ CFGSCRNA .... .1.1 - LBL TYPE NOT AVAIL. 26 (1A) LENGTH CFGLNGTH LENGTH OF RECORD 256 (100) CONST CFGMXLSM MAXIMUM NUMBER OF ACSS 572 VM/HSC 6.
PAGE 603
Cross Reference Name Len Offset Value CFGCCPFX 000003 01 CFGCHKEP - 20 CFGCMDPF 000001 15 CFGDDISP 000001 16 CFGDDNSC - 40 CFGDDSCR - 80 CFGDISVF - 40 CFGENGLS - 80 CFGFLAG1 000001 17 CFGFRNCH - 10 CFGGERMN - 20 CFGITALN - 40 CFGLANG 000001 18 CFGLIBFX - 80 CFGLNGTH - 1A CFGMXLSM - 100 CFGNMACS 000002 0C CFGSCRAL - 01 CFGSCRBL - 04 CFGSCRLB 000001 19 CFGSCRNA - 05 CFGSCRNL - 02 CFGSCRNS - 03 CFGSCRSL - 00 CFGSMFTY 000001 14 CFGTOT
PAGE 604
SLUVHDAT Note: Field HSTLIBEN contains only the first 16 ACS esoterics. Table 60.
PAGE 605
Table 60. SLUVHDAT Record Format (Continued) Dec Hex Type Length Label Description .1.. .... X’40’ HSTR200 .1.. .... - HSC 2.0.0 ...1 .... X’10’ HSTR201 ...1 .... - HSC 2.0.1 .... 1... X’08’ HSTR210 .... 1... - HSC 2.1.0 .... .1.. X’04’ HSTR400 .... .1.. - HSC 4.0.0 .... ..1. X’02’ HSTR410 .... ..1. - HSC 4.1.
PAGE 606
Cross Reference Name Len Offset Value HSTDEAD - 10 HSTDELAY - 20 HSTFLAG1 000001 09 HSTFLAG2 000001 0A HSTFLAG3 000001 0B HSTFXLEN - 03 HSTHNAME 000008 00 HSTHOSLN - 94 HSTHOSTS - 03 HSTHSTAC - 20 HSTINDEX 000001 08 HSTLIBEN 000008 14 HSTNHOST 000002 01 HSTNONEN 000008 0C HSTPRIAC - 80 HSTRCVRH - 40 HSTRCVRR - 80 HSTR110 - 20 HSTR120 - 80 HSTR200 - 40 HSTR201 - 10 HSTR210 - 08 HSTR400 - 04 HSTR410 - 02 HSTSBYAC - 10 HSTSHDAC - 4
PAGE 607
SLUVIDAT Table 61. SLUVIDAT Record Format Dec Hex Type Length Label Description SLUVIDAT - FLAT FILE CDS INFORMATION DSECT FUNCTION: DESCRIBES THE CDS INFORMATION WHICH MAY BE GENERATED TO THE FLAT FILE BY THE VOLUME REPORT UTILITY. 0 (0) STRUCTURE SLUVIDAT 0 (0) CHARACTER 1 -RESERVED- RECORD TYPE (C’I’) 1 (1) BITSTRING 1 CDSRCVRY CDS RECOVERY OPTIONS 1... .... X’80’ CDSSECND 1... .... - SECONDARY .1.. .... X’40’ CDSSTDBY .1.. .... - STANDBY ..1. .... X’20’ CDSJOURN ..1. ....
PAGE 608
Table 61. SLUVIDAT Record Format (Continued) Dec Hex Type Length Label Description 0 (0) CHARACTER 44 CDSDSN CDS DATASET NAME 44 (2C) CHARACTER 6 CDSVOL CDS VOLSER 50 (32) HEXSTRING 2 -RESERVED- *** RESERVED *** 52 (34) CHARACTER 8 CDSUNIT CDS UNIT NAME 60 (3C) HEXSTRING 2 CDSSWCNT CDS SWITCH COUNT 62 (3E) HEXSTRING 2 -RESERVED- *** RESERVED *** 64 (40) HEXSTRING 4 -RESERVED-(4) *** RESERVED *** 80 (50) LENGTH CDSINFOL LENGTH OF CDS ENTRY 578 VM/HSC 6.
PAGE 609
Cross Reference Name Len Offset Value CDSALL - E0 CDSBDATE 000008 30 CDSBOTH - A0 CDSBTIME 000008 28 CDSCDATE 000008 18 CDSCTIME 000008 20 CDSDSN 000044 00 CDSENQNM 000008 08 CDSINFOL - 50 CDSJOURN - 20 CDSLEVEL 000008 10 CDSLNGTH - 138 CDSNAMES 000240 48 CDSNONE - 00 CDSRCVRY 000001 01 CDSRDATE 000008 40 CDSRSVD1 000004 04 CDSRTIME 000008 38 CDSSECND - 80 CDSSTDBY - 40 CDSSWCNT 000002 3C CDSUNIT 000008 34 CDSVOL 000006 2C Appendix C.
PAGE 610
SLUVSDAT Table 62. SLUVSDAT Record Format Dec Hex Type Length Label Description SLUVSDAT - FLAT FILE ACS STATION ADDRESS DSECT FUNCTION: MAP THE STATION ADDRESS INFORMATION BY HOST WITHIN ACS WHICH MAY BE WRITTEN TO THE FLAT FILE BY THE VOLUME REPORT UTILITY.
PAGE 611
Cross Reference Name Len Offset Value STNACS 000001 01 STNADDRS 000003 01 STNADENL - 03 STNCUA 000002 01 STNENTLN - 31 STNFLAG 000001 00 STNFXLEN - 02 STNHINDX 000001 00 STNONLIN - 80 STNSTNS - 02 Appendix C. Record Formats 581 1st ed.
PAGE 612
SLUVVDAT To determine the HSC release that produced a volume report flat file, use the CDSDATA parameter to create flat file records with non-volume information. Interrogate the CDSLEVEL field in the SLUVIDAT (CDS Information) record. A CDS at level 02.00.00 is reported by an HSC VOLRpt at release level 2.0.1 and earlier. CDS level 02.01.00 is reported by an HSC 5.0, 5.1, or 6.0 VOLRpt. The CDSDATA records are appended to the VOLDATA records.
PAGE 613
Table 63. SLUVVDAT Record Format (Continued) Dec Hex Type Length Label Description ‘R’ (D9) CHAR CONST VOLMEDTR (X’D9’) STK1R MEDIA ‘U’ (E4) CHAR CONST VOLMEDTU (X’E4’) STK1U CLEANING CARTRIDGE “U” ‘W’ (E7) CHAR CONST VOLMEDTW (X’E7’) STK2W CLEANING CARTRIDGE “W” ‘Z’ (E9) CHAR CONST VOLMEDTZ (X’E9’) ZCART MEDIA 2 (2) BITSTRING VOLFLAG1 VOLUME FLAG BYTE 1 1... .... X’80’ VOLSCR 1... .... - VOLUME IS SCRATCH .1.. .... X’40’ VOLSEL .1.. .... - VOLUME IS SELECTED ..1. ....
PAGE 614
Table 63. SLUVVDAT Record Format (Continued) Dec Hex Type Length Label Description 26 (1A) CHARACTER 2 VOLHMCEL DECIMAL NUMBER OF THE COLUMN WITHIN VOLHMROW WHERE THE VOLUME RESIDES.
PAGE 615
Table 63.
PAGE 616
Table 63. SLUVVDAT Record Format (Continued) Dec 121 122 Hex (79) (7A) Type Length Label Description ..1. .... X’20’ VOLERSSC ..1. .... - SOURCE LOC. SCANNED ...1 .... X’10’ VOLERDSC ...1 .... - DEST. LOC. SCANNED .... 1... X’08’ VOLERLSC .... 1... - LOST IN LSM SCANNED .... .1.. X’04’ VOLERHSC .... .1.. - HOME LSM SCANNED .... ..1.X’02’ VOLERMNT .... ..1.- VOLUME IS MOUNTED VOLITTAG IN-TRANSIT TAG TYPE .... .... X’00’ VOLITOTH .... .... - OTHER (OR NOT IN TRAN) .... ...
PAGE 617
Table 63.
PAGE 618
Table 63. SLUVVDAT Record Format (Continued) Dec Hex Type Length Label Description 5 (5) HEXSTRING 1 -RESERVED- RESERVED 3 (3) HEXSTRING 1 VOLSDIDX DRIVE INDEX NUMBER 4 (4) HEXSTRING 1 -RESERVED- RESERVED 5 (5) BITSTRING 1 VOLSDFLG DRIVE FORMAT FLAG VOLSDFIX DRIVE IS DRIVE INDEX FORMAT -RESERVED- RESERVED 1111 1111 X’FF’ 6 (6) HEXSTRING 2 FOR “OTHER” TYPES, THIS RECORD IS TREATED AS IF THE VOLUME WERE ERRANT. 588 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 619
Cross Reference Name Len Offset Value VOLDEST 000006 84 VOLDTINS 000008 44 VOLDTMNT 000008 64 VOLDTSEL 000008 54 VOLD4YR - 80 VOLERACT - 80 VOLERDSC - 10 VOLERHSC - 04 VOLERLIL - 40 VOLERLSC - 08 VOLERMNT - 02 VOLERSSC - 20 VOLEXLBL - 20 VOLEXRD - 10 VOLFLAG1 000001 02 VOLFLAG2 000001 78 VOLFLAG3 000001 74 VOLHMACS 000002 0E VOLHMCEL 000002 1A VOLHMLOC 000014 0E VOLHMLSM 000002 11 VOLHMPNL 000002 14 VOLHMROW 000002 17 VOLIELEN - 9C V
PAGE 620
Name Len Offset Value VOLITRTN 000001 7A VOLITTAG 000001 79 VOLITUSE - 80 VOLITVOL - 08 VOLLILSM 000002 8A VOLLNGTH - 78 VOLMEDC 000008 94 VOLMEDIA 000001 01 VOLMEDST - ‘CVAL’ VOLMEDTA - ‘CVAL’ VOLMEDTB - ‘CVAL’ VOLMEDTC - ‘CVAL’ VOLMEDTD - ‘CVAL’ VOLMEDTE - ‘CVAL’ VOLMEDTJ - ‘CVAL’ VOLMEDTP - ‘CVAL’ VOLMEDTR - ‘CVAL’ VOLMEDTU - ‘CVAL’ VOLMEDTW - ‘CVAL’ VOLMEDTZ - ‘CVAL’ VOLMEDT1 - ‘CVAL’ VOLMNDSM - 20 VOLMXCLN 000002 2C VOLNILIB - 01
PAGE 621
Name Len Offset Value VOLRRCNL - 34 VOLRRDEJ - 14 VOLRRERR - 2C VOLRRMCT - 44 VOLRRMNT - 10 VOLRRSCA - 20 VOLRRSCD - 24 VOLRRSLV - 3C VOLRRSRE - 40 VOLRRSUA - 38 VOLRRVDL - 28 VOLSACSN 000001 01 VOLSCAP - ‘CVAL’ VOLSCELL - ‘CVAL’ VOLSCLOC 000002 03 VOLSCOLN 000001 05 VOLSCR - 80 VOLSDFIX - FF VOLSDFLG 000001 05 VOLSDIDS 000001 03 VOLSDNUM 000001 04 VOLSDPNL 000001 03 VOLSDRIV - ‘CVAL’ VOLSEL - 40 VOLSELCT 000004 04 VOLSER 000006
PAGE 622
Name Len Offset Value VOLSPNLN 000001 03 VOLSPNON - ‘CVAL’ VOLSPNSL - ‘CVAL’ VOLSPSL - ‘CVAL’ VOLSRCE 000006 7E VOLSROWN 000001 04 VOLSTYPE 000001 00 VOLTDINS 000004 38 VOLTDMNT 000004 40 VOLTDSEL 000004 3C VOLTMINS 000008 4C VOLTMMNT 000008 6C VOLTMSEL 000008 5C 592 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 623
Batch API Records Batch API Mapping Macros These SMP/E-distributed macros map only Batch API records. Refer to “Volume Report and Batch API Records” on page 562 to see the records that map both Volume Report and Batch API. Table 64. Mapping macros for Batch API Records Macro Description SLUVDDAT Batch API Drive Information DSECT SLUVPDAT Batch API CAP Information DSECT Appendix C. Record Formats 593 1st ed.
PAGE 624
Batch API Record Formats SLUVDDAT This record is produced only by the Batch API QCDS request. Refer to Appendix E, “Batch Application Program Interface (API)” on page 713 for more information. Table 65. SLUVDDAT Record Format Dec Hex Type Length Label Description SLUVDDAT - QCDS DRIVE INFORMATION DSECT FUNCTION: MAPS THE DRIVE DATA PRODUCED BY THE QCDS READ REQUEST FOR THE CDS DRV RECORD AREA.
PAGE 625
Table 65.
PAGE 626
Name Len Offset Value UVDFLAG2 000001 02 UVDFLAG3 000001 03 UVDIDACS 000001 06 UVDIDLSM 000001 07 UVDIDNUM 000001 09 UVDIDPNL 000001 08 UVDLEN - 34 UVDLUNIT 000002 12 UVDNOLMU - FFFF UVDNSCR - 40 UVDNUNIT 000002 10 UVDOPRQ - 40 UVDRACF - 10 UVDREDW - ‘CVAL’ UVDRT 000001 00 UVDSCR - 80 UVDSILV - ‘CVAL’ UVDTIMB - ‘CVAL’ UVDTMS7 - 08 UVDTYPE 000002 04 UVDUNITN 000002 14 UVDV5310 - 20 UVD3490E - ‘CVAL’ UVD3590 - ‘CVAL’ UVD4480 - ‘CVAL’
PAGE 627
Name Len Offset Value UVD994B5 - ‘CVAL’ Appendix C. Record Formats 597 1st ed.
PAGE 628
SLUVPDAT This record is produced only by the Batch API QCDS request. Refer to Appendix E, “Batch Application Program Interface (API)” on page 713 for more information. Table 66. SLUVPDAT Record Format Dec Hex Type Length Label Description SLUVPDAT - QCDS CAP INFORMATION DSECT FUNCTION: MAPS THE CAP DATA PRODUCED BY THE QCDS READ REQUEST FOR THE CDS CAP RECORD AREA. 0 (0) STRUCTURE 0 (0) CHARACTER 1 UVPRT RECORD TYPE 1 (1) BITSTRING 1 UVPFLAG1 CAP STATUS: 1... ....
PAGE 629
Table 66. SLUVPDAT Record Format (Continued) Dec Hex Type Length Label Description 32 (20) SIGNED-HWORD 2 UVPLPRIO LENGTH OF CAP PRIORITY ELEMENTS 34 (22) HEXSTRING 1 UVPPRITY(16) CAP PRIORITY ELEMENTS, BY HOST INDEX 50 (32) HEXSTRING 1 UVPPANEL PANEL NUMBER OF CAP 51 (33) BITSTRING 1 UVPTYPE TYPE OF CAP: 1... .... X’80’ UVPPCAP PRIORITY CAP .... ...1 X’01’ UVPCIM CIMARRON .... ..1. X’02’ UVPCLIP CLIPPER .... ..11 X’03’ UVPTWSTD STANDARD WOLF CLIPPER .... .1..
PAGE 630
Cross Reference Name Len Offset Value UVPCIM - 01 UVPCLIP - 02 UVPFLAG1 000001 01 UVPFLAG2 000001 02 UVPF1ACT - 80 UVPF1AUT - 20 UVPF1LNK - 10 UVPF1ONL - 08 UVPF1REC - 40 UVPF2CLN - 10 UVPF2DRA - 40 UVPF2EJT - 20 UVPF2ENT - 80 UVPF2IDL - 08 UVPHOST 000008 0E UVPHOSTI 000001 16 UVPID 000003 03 UVPJOBN 000008 06 UVPLEN - 34 UVPLPRIO 000002 20 UVPNCELL 000002 18 UVPNCOLS 000001 1B UVPNMAGC 000001 1D UVPNMAGS 000001 1C UVPNPRIO 000002
PAGE 631
Name Len Offset Value UVPTWSTD - 03 UVPTYPE 000001 33 UVP9740 - 05 Appendix C. Record Formats 601 1st ed.
PAGE 632
602 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 633
Appendix D. Logging ACS Robotics Motion Overview StorageTek provides a way to monitor the reliability of ACS robotics motion. This appendix describes what information is logged and how that information is logged. Information Being Logged StorageTek logs robotic motion statistics in three categories: • robotic Motion Start Counts • temporary Motion Error Counts • permanent Motion Errors. Each category is described in the following paragraphs.
PAGE 634
Permanent Motion Errors Each time a permanent motion failure occurs, complete information concerning the failure is logged. A permanent error is counted against any motion which causes a Mount, DISMount, Swap, MOVe, Catalog, or VIew command to fail in such a way that user intervention is required to correct the situation. 604 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 635
How Information is Logged The HSC periodically retrieves the statistics for robotics motions begun and temporary errors from the LMU. This information is logged to SYS1.LOGREC as software errors as shown in the Table 67. This record is a valid ‘‘Initiated and Temporary Error Motion Software Error Record’’ only under the following circumstances: • if the Record Type Field (bytes 642-643) has value X’6506’ and • the StorageTek identifier (X’FEEDFACE’ at bytes 644-647) is present.
PAGE 636
Table 67.
PAGE 637
Table 67.
PAGE 638
These records, regardless of whether the hard fail indicator is turned on, are LLG1 records. Table 68.
PAGE 639
Table 68.
PAGE 640
operations that do result in an error, only those that requested robotic motions are logged as hard fails with the appropriate indicator set in the record. Errors that do not represent failed robotic motions are software errors. These should be analyzed and reported to StorageTek. Single-Host Environment In a single-host environment, there is only one SYS1.LOGREC data set and only one copy of the HSC. In such an environment, everything is straightforward and easy to manage.
PAGE 641
LMU Response Codes The following tables contain a list of permanent error LMU response codes with associated • • • • descriptions indications of whether a console message is generated indications of whether a LOGREC record is cut indications of whether this response code is included as an R+ hard fail or if it is excluded. Symbols used in the tables are as follows: Code Description M Console message posted L Record logged to SYS1.LOGREC L+ Record sometimes logged to SYS1.
PAGE 642
Invalid Parameter Error Codes: 0101 - 0127 Table 69.
PAGE 643
Configuration Error Codes: 0201 - 0203 Table 70. LMU Response Codes 0201 thru 0203 LMU Resp Response Description Con Msg LOG rec Mnt B Dmt C Swp D Mov E Cat J/K Vw X 0201 LSM is not in static configuration M L H H H H H H 0202 Drive does not exist M L H H H H H H 0203 CAP does not exist M L H H H H H H CAP Procedural Error Codes: 0301 - 0310 Table 71.
PAGE 644
General Procedural Error Codes: 0401 - 0427 Table 72.
PAGE 645
Table 72. LMU Response Codes 0401 thru 0427 (Continued) LMU Resp Response Description Con Msg LOG rec Mnt B Dmt C Swp D Mov E Cat J/K Vw X 0426 Drive not rewound M L+ r - - H H H 0427 Cartridge not mounted M L H - - H H H LMU LAN Interface Error Codes: 0501 - 0512 Table 73.
PAGE 646
LMU Logical Error Codes: 0601 - 0620 Table 74.
PAGE 647
LSM Robotics Error Codes: 0701 - 0718 Table 75.
PAGE 648
LSM Hardware Error Codes: 0801 - 0809 Table 76.
PAGE 649
Table 77.
PAGE 650
Table 77. LMU Response Codes 0901 thru 0977 (Continued) LMU Resp Response Description Con Msg LOG rec Mnt B Dmt C Swp D Mov E Cat J/K Vw X 0976 Can’t rewind M L H - - H H H 0977 Can’t unload M L - - - H H H 0978 Drive cannot honor write protected M L H H H H H H 0979 Drive currently reserved M L H H H H H H Drive Error Codes: 1001 - 1011 Table 78.
PAGE 651
Appendix E. Remote-linked Libraries Overview This appendix contains illustrations of configurations for remote-linked libraries. In addition, programming and operational considerations for each of the configurations are presented. Appendix E. Remote-linked Libraries 621 1st ed.
PAGE 652
Configuration 1 This configuration consists of one ACS remote-linked to one CPU. The primary, secondary, and standby control data sets all run on the one CPU. MANUAL TRANSPORTS OPERATING SYSTEM ACS 0 HSC PRIMARY CONTROL DATA SET CH EXT SECONDARY CONTROL DATA SET CH EXT STANDBY CONTROL DATA SET LEGEND: CH EXT = CHANNEL EXTENDER = OPTIONAL Figure 29. Configuration 1 622 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 653
Configuration 2 This configuration consists of one ACS remote-linked to one CPU. The primary, secondary, and standby control data sets all run on the one CPU. Multiple Clients on a Local Area Network TCP/IP Path for Robotic Control Corporate Ethernet MVS/CSC Operating System Data Path ESCD Data Path ESCD HSC/SMC SL8500 Library Primary Control Data Set Legend: ESCD Secondary Control Data Set Standby Control Data Set = ESCON Director = Optional = Data Path = Ethernet (TCP/IP) C51183 Appendix E.
PAGE 654
Configuration 3 This configuration consists of one ACS local to one CPU that is remote-linked to another CPU with one ACS local to it. The primary and secondary control data sets run on separate SSDs each attached to separate CPUs. The standby control data set can be attached to either SSD.
PAGE 655
Configuration 4 This configuration consists of one ACS local to one CPU that is remote-linked to another CPU with one ACS local to it. The primary and secondary control data sets run on separate SSDs each attached to separate CPUs. ACS 0 ACS 1 CH EXT LMU OPERATING SYSTEM CH EXT CH EXT LMU CH EXT OPERATING SYSTEM HSC HSC SSD SSD PRIMARY CONTROL DATA SET SECONDARY CONTROL DATA SET LEGEND: CH EXT = CHANNEL EXTENDER = OPTIONAL C29326 Figure 31. Configuration 4 Appendix E.
PAGE 656
Configuration 5 This configuration consists of one ACS local to one CPU that is remote-linked to another CPU with one ACS local to it. In addition, a third ACS is remote-linked to both CPUs. The primary and secondary control data sets run on separate SSDs each attached to separate CPUs.
PAGE 657
Programming and Operational Considerations The following are programming and operational considerations that should be observed if you have libraries resembling any of the illustrated configurations. The HSC permits operation of these library configurations provided that some programming and operational precautions are observed. These precautions are based on various functional restrictions described in following paragraphs.
PAGE 658
The original primary control data set continues to operate for ACS0 only. As the library operates, any updates occurring to either control data set after the link was severed causes the data sets to be unsynchronized. It is a difficult task to resynchronize the data for both data sets. Possible solutions to resynchronize the data sets include: • Execute the AUDIt utility and reconcile the differences between the primary control data set and the secondary data set.
PAGE 659
Appendix F. Batch Application Program Interface (API) Overview The Batch API allows you to retrieve CDS information in batch mode. The CDS specified as input to the request does not have to be active nor does it have to be currently referenced by the HSC address space (the request can execute entirely in the user address space). In addition, the Batch API executes in the user’s virtual machine, and the HSC does not have to be active to submit the request.
PAGE 660
The SLSUREQM macro maps the SLSUREQ reply header, parameter list, and return code values. Refer to “SLSUREQM Macro” on page 645 to see the record layout. Reply header length is defined in SLSUREQM, and library element record lengths are defined in the SLUVxDAT macros. Return codes for each request (see “Return Codes” on page 634) are stored in register 15. VM Requirement The program issuing the SLSUREQ macro must include the SLSMAC MACLIB in the GLOBAL MACLIB definition. GLOBAL MACLIB SLSMAC...
PAGE 661
• Register (15): stores QCDS request return codes. Syntax The syntax for the QCDS request is: label SLSUREQ QCDS ,BUFLEN=buflen ,MF= ,REQUEST=request ,TOKEN=token ,TYPE=type ,DDNAME=ddname ,BUFFER=buffer ,UCALADR=rtnaddr L (E,parmaddr) Parameters label label indicates a user-defined assembler label. REQUEST request indicates to access a library element record area. OPEN specifies to open a library element area and move to the first record of the area.
PAGE 662
HST specifies the host information record area MVC specifies the Multi-Volume Cartridge record area STA specifies the station record area VOL specifies the volume record area VTV specifies the Virtual Tape Volume record area This parameter is required. BUFFER buffer indicates an RX-type fullword location or a register (2) - (12) containing the response area address for this READ request. This parameter is required for the READ request but is ignored for OPEN and CLOSE requests.
PAGE 663
Notes: 1. A CDS must be preallocated to ddname in the JCL or in a SVC 99 dynamic allocation request before issuing QCDS requests. 2. The input CDS does not need to be active or referenced by the HSC address space. 3. QCDS allows for multiple input CDSs, as long as each uses a unique ddname and specifies a different token for each open CDS. For example, an application can open two input CDSs and process them in an alternating, or interleaved, fashion. This parameter is optional.
PAGE 664
Return Codes Invalid SLSUREQ requests and QCDS access requests provide return codes in register 15. Table 80 shows the list of return codes. Table 81. Batch API Return Codes Return Field Name: Decimal Value and Description: Invalid SLSUREQ Requests: SLURRQPL 1000 - SLSUREQ request failed: Invalid SLSUREQ parameter list. SLURRQRT 1001 - SLSUREQ request failed: Invalid SLSUREQ request type. SLURQCRT 1002 - SLSUREQ request failed: Invalid QCDS access request type.
PAGE 665
Table 81. Batch API Return Codes (Continued) Return Field Name: Decimal Value and Description: SLURRDBA 24 - Read failed: Attempt to read beyond the end of the record area. SLURRDIB 28 - Read failed: Invalid response area buffer address. SLURRDIL 32 - Read failed: Response area buffer length too short to contain both the reply header and at least one library element record. CLOSE Return Codes: SLURCLOK 0 - Record area was closed successfully.
PAGE 666
QCDSVTV TITLE 'QCDS Read current primary CDS VTV record area' * * * Function: Use QCDS to automatically allocate and Open the * current primary CDS. Issue SLSUREQ QCDS requests to * read all the VTV records. * * Attributes: * 1. Problem state, user key. * 2. Non-APF authorized. * 3. AMODE 24, RMODE 24 (for below-the-line QSAM), reentrant. * * Notes: * The caller must have read access for the current primary * CDS.
PAGE 667
MVC LA OPEN WKFLATDD(KFLATDDL),KFLATDD Initialize the working R4,WKFLATDD storage version of the DCB from the ((R4),(OUTPUT)) copy in the constants area.
PAGE 668
* Inner loop - process each VTV record in the response area: * VOLPROC DS 0H Over all VTV records in reply: * ... process VTV record here ...
PAGE 669
* Constants: * QCDSMODL SLSUREQ MF=L SLSUREQ plist model QCDSMLEN EQU *-QCDSMODL Length of SLSUREQ plist model QCDSBLEN DC F'655360' QCDS READ response area buffer length KFLATDD DCB DDNAME=VDRECDAT,DSORG=PS,MACRF=(PM), + LRECL=VDRECLEN, + BLKSIZE=VDRECLEN*100,RECFM=FB KFLATDDL EQU *-KFLATDD * * Module work area map: * WKAREA DSECT Module work area WKSAVE DS 18F MVS register save area WKUCAL DS A SLSUCAL routine address WKTOK DS F QCDS request token WKRDRC DS F QCDS READ return code WKBUFP DS A QCDS READ re
PAGE 670
Sample 2 - Reading the ACS and DRV Record Areas Together This sample QCDS request reads two different CDS record areas (ACS and DRV), alternating between the two. The job step JCL must include a DDNAME statement for the input CDS DDname (MVS1CDS in this example). 640 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 671
QACSDRV TITLE ‘QCDS READ ACS AND DRIVE RECORD AREAS TOGETHER’ * * QACSDRV QCDS READ ACS AND DRIVE RECORD AREAS TOGETHER. * * FUNCTION: USE SEPARATE RESPONSE AREAS TO READ THE ACS AND DRV * RECORD AREAS IN AN ALTERNATING FASHION. * EACH RESPONSE AREA IS A 1KB BUFFER. * * ATTRIBUTES: * 1. PROBLEM STATE, USER KEY. * 2. NONAPF AUTHORIZED. * 3. AMODE 31, RMODE ANY, REENTRANT. * * NOTES: * THE CALLER MUST HAVE READ ACCESS FOR THE INPUT CDS.
PAGE 672
* * OPEN ACS AND DRIVE RECORD AREAS AND MAP THE RESPONSE AREAS: * OPEN DS 0H OPEN ACS AND DRIVE RECORD AREAS: SLSUREQ QCDS, OPEN ACS RECORD AREA REQUEST=OPEN, TYPE=ACS, TOKEN=WKTOK, DDNAME=QCDSDD, UCALADR=WKUCAL, MF=(E,WKQCDS) SLSUREQ QCDS, OPEN DRIVE RECORD AREA REQUEST=OPEN, TYPE=DRV, TOKEN=WKTOK, UCALADR=WKUCAL, MF=(E,WKQCDS) USING SLUR,R9 MAP QCDS READ RESPONSE AREA * * MAIN PROCESSING LOOP INTERLEAVED PROCESSING OF ACS AND * DRIVE RECORDS: * PROCESS DS 0H MAIN PROCESSING LOOP: LA R9,WKACSBUF POINTER
PAGE 673
* * CONDITIONALLY BRANCH TO CLOSE LABEL WHEN AN APPROPRIATE * LOOP TERMINATION CONDITION HAS BEEN SATISFIED (NOT SHOWN).
PAGE 674
* * MAPPING MACROS: * EQUATES SLSREGS SLSUREQM , MAPPING MACRO REGISTER SLSUREQ SLUVADAT , ACS Figure 34. Sample 2 - Reading ACS and DRV Together (4 of 4) Output Description Each successful OPEN request returns the name of the input CDS in the SLSUREQ parameter list (SLSUREQM field SLSUQDSN). Each successful READ request returns one or more library element records in the user-designated response area. Use the SLUR DSECT in the SLSUREQM macro to map the response area reply header.
PAGE 675
SLSUREQM Macro The SLSUREQM mapping macro must be specified in any assembly that uses the SLSUREQ macro. Syntax label SLSUREQM PRO= NO YES Parameters PRO={NO|YES} Specifies whether the prologue should be generated (YES) or not (NO). The default is NO. Appendix F. Batch Application Program Interface (API) 645 1st ed.
PAGE 676
Batch API Mapping (SLSUREQM) Macro Table 83. SLSUREQM Record Format Dec Hex Type Length Label Description MACRO: SLSUREQM - BATCH API USER INTERFACE MAPPING MACRO FUNCTION: THIS MACRO MAPS THE SLSUCAL PARAMETER LIST, REPLY HEADER, AND RETURN CODES.
PAGE 677
Table 83.
PAGE 678
Table 83. SLSUREQM Record Format (Continued) Dec Hex Type 12 (C) SIGNED-FWORD 0 (00) 4 Length 4 Label Description SLURQCDO OFFSET TO QCDS LIBRARY ELEMENT RECORD SECTION FROM START OF REPLY HEADER. QCDS OPEN RETURN CODES: CONST SLUROPOK RECORD AREA WAS OPENED SUCCESSFULLY. (04) CONST SLUROPAO OPEN FAILED - ATTEMPT TO OPEN A RECORD AREA THAT IS ALREADY OPEN. 8 (08) CONST SLUROPIT OPEN FAILED - INVALID TOKEN VALUE. 12 (0C) CONST SLUROPRA OPEN FAILED - INVALID RECORD AREA TYPE.
PAGE 679
Table 83. SLSUREQM Record Format (Continued) Dec Hex Type Length Label Description 4 (04) CONST SLURRDEA READ SUCCEEDED - ONE OR MORE RECORDS WERE TRANSFERRED TO THE RESPONSE AREA AND NO ADDITIONAL RECORDS CAN BE READ FROM THE ASSOCIATED RECORD AREA. 8 (08) CONST SLURRDIT READ FAILED - INVALID TOKEN VALUE. 12 (0C) CONST SLURRDRA READ FAILED - INVALID RECORD AREA TYPE. 16 (10) CONST SLURRDIO READ FAILED - I/O ERROR WHILE ACCESSING THE ASSOCIATED CDS.
PAGE 680
Table 83. SLSUREQM Record Format (Continued) Dec Hex Type Length Label Description 16 (10) CONST SLURCLIO CLOSE FAILED - I/O ERROR WHILE ACCESSING THE ASSOCIATED CDS. 16 (10) LENGTH SLURRHLN LENGTH OF REPLY HEADER. 16 (10) AREA SLURFRS START OF VARIABLE-LENGTH FORMATTED RECORD SEGMENT. 650 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 681
Cross Reference Name Len Offset Value SLSUACSA - 00 SLSUARAN - 0A SLSUCAPA - 01 SLSUCDSA - 02 SLSUCFGA - 03 SLSUDRVA - 04 SLSUHDR 000004 00 SLSUHSTA - 05 SLSUID - ‘CVAL’ SLSULN - 148 SLSUMVCA - 08 SLSUQCDA 000001 07 SLSUQCDB 000004 0C SLSUQCDC - 02 SLSUQCDD 000004 14 SLSUQCDK 000004 08 SLSUQCDL 000004 10 SLSUQCDO - 00 SLSUQCDR - 01 SLSUQCDS - 01 SLSUQCDT 000001 06 SLSUQDSN 000044 18 SLSURT 000001 05 SLSUSTAA - 06 SLSUVER 000001 04
PAGE 682
Name Len Offset Value SLURCLOK - 00 SLURCLRA - 0C SLURFRS 000004 10 SLURHDR 000004 00 SLURHSCV 000002 04 SLURID - ‘CVAL’ SLUROPAO - 04 SLUROPDA - 1C SLUROPDD - 14 SLUROPDM - 20 SLUROPIO - 10 SLUROPIT - 08 SLUROPNA - 18 SLUROPOK - 00 SLUROPRA - 0C SLURQCDN 000004 08 SLURQCDO 000004 0C SLURQCRT - 3EA SLURRDBA - 18 SLURRDEA - 04 SLURRDIB - 1C SLURRDIL - 20 SLURRDIO - 10 SLURRDIT - 08 SLURRDNO - 14 SLURRDOK - 00 SLURRDRA - 0C SL
PAGE 683
Appendix F. Batch Application Program Interface (API) 653 1st ed.
PAGE 684
654 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 685
Glossary Terms are defined as they are used in the text. If you cannot find a term here, check the index. intervention. This is the normal operating mode of an LSM that has been modified online. A B AC— Alternating current. basic direct access method (BDAM)— An access method used to directly retrieve or update particular blocks of a data set on a direct access device. access method— A technique for moving data between processor storage and I/O devices. ACS— See Automated Cartridge System.
PAGE 686
CAPid— A CAPid uniquely defines the location of a CAP by the LSM on which it resides. A CAPid is of the form AA:LL:CC where AA is the ACSid (00-FF hexadecimal), LL is the LSM number (00-17 hexadecimal), and CC is the CAP number. Some commands and utilities permit an abbreviated CAPid format of AA:LL. cartridge— The plastic housing around the tape. It is approximately 4 inches (100 mm) by 5 inches (125 mm) by 1 inch (25 mm). The tape is threaded automatically when loaded in a transport.
PAGE 687
control data set recovery area— A portion of the CDS reserved for maintaining integrity for updates that affect multiple CDS blocks. control data set subfile— A portion of the CDS consisting of Data Blocks and Pointer Blocks containing related information. Control Unit (CU)— (1) A microprocessor-based unit situated logically between a host channel (or channels) and from two to sixteen transports.
PAGE 688
device group— A subset of the eligible devices. Device groups are defined by esoteric unit names but also may be created implicitly if common devices exist in different device groups. device number— A four-digit hexadecimal number that uniquely identifies a device attached to a processor. device separation— See drive exclusion. DFP— Data Facility Product. A program that isolates applications from storage devices, storage management, and storage device hierarchy management.
PAGE 689
ECCST— (1) A value that can be specified on the MEDia parameter and that includes only enhanced capacity cartridge system tapes. (2) An alias of ECART. (3) See Enhanced Capacity Cartridge System Tape. EPO— Emergency Power Off. EDL— See eligible device list. error recovery procedures (ERP)— Procedures designed to help isolate and, where possible, to recover from errors in equipment. EDTGEN— Eligible Device Table Generation.
PAGE 690
frozen panel— A panel to which cartridges cannot be moved. This restriction includes allocating new cartridge locations on a panel as a result of: • a MOVe command, utility, or PGMI request • cartridge entry into the ACS • float, scratch dismount, or scratch redistribution processing. G 9 GB— Gigabyte, billion (10 ) bytes. GDG— Generation Data Group. An MVS data set naming convention. Sequence numbers are appended to the basic data set name to track the generations created for that data set.
PAGE 691
programs at IPL execution. Devices running µ-software reload the functional µ-software usually from a floppy diskette at IPL execution. keyword parameter— In command and utility syntax, operands that include keywords and their related values (See positional parameter). initial value— A value assumed until explicitly changed. It must then be explicitly specified in another command to restore the initial value. An initial value for the HSC is the value in effect when the product is installed.
PAGE 692
LMUPDEF— An HSC command used to load the definition data set that contains LMUPATH control statements. M load point— The beginning of the recording area on magnetic tape. magnetic recording— A technique of storing data by selectively magnetizing portions of a magnetizable material. loader— See Cartridge Scratch Loader. Local Area Network (LAN)— A computer network in which devices within the network can access each other for data transmission purposes.
PAGE 693
media capacity— The amount of data that can be contained on storage media and expressed in bytes of data. media mismatch— A condition that occurs when the media value defined in a VOLATTR control statement does not match the media value recorded in the CDS VAR record. micro-software— See µ-software under Symbols. MIM— Multi-Image Manager. Third-party software by Computer Associates International, Inc.
PAGE 694
primary CDS— The active control data set. It contains the inventory of all cartridges in the library, the library configuration, information about library hardware and resource ownership across multiple processors, and serves as a vehicle of communication between HSCs running on multiple processors. RECtech— The parameter used to specify recording technique. priority CAP (PCAP)— A one-cell CAP that is part of an enhanced CAP.
PAGE 695
problem impacts operations. Customers can set maintenance threshold levels. be used to clean tape transports. See also over-limit cleaning cartridge. servo— A device that uses feedback from a sensing element to control mechanical motion. SSD— Solid state disk. Shared Tape Allocation Manager (STAM)— Third-party software by Computer Associates International, Inc. Silverton— See 4490 Cartridge Subsystem. SL8500 library— See StreamLine (SL8500 library).
PAGE 696
specified type of 9840 cartridge or recording technique. STK1R can be abbreviated as R. STK1U— Value that can be specified on the MEDia parameter and includes only the specified type of 9840 cleaning cartridge. STK1U can be abbreviated as U. STK2— A generic value that can be specified on the MEDia parameter and includes all types of 9940 cartridges and recording techniques.
PAGE 697
See also Cartridge Access Port, standard CAP, enhanced CAP, priority CAP, WolfCreek CAP, or WolfCreek optional CAP. TP— Tape-to-Print. transaction— A short series of actions with the control data set. These actions are usually related to a specific function (e.g., Mount, ENter). transport— An electromechanical device capable of threading tape from a cartridge, moving the tape across a read/write head, and writing data onto or reading data from the tape.
PAGE 698
available in 500, 750, and 1000 cartridge capacities (model numbers 9360-050, 9360-075, and 9360-100, respectively). WolfCreek LSMs can be connected by pass-thru ports to 4410, 9310, or other WolfCreek LSMs. WolfCreek CAP— The standard WolfCreek CAP contains a 20-cell magazine-style CAP and a priority CAP (PCAP). 18track— A generic value that can be specified on the RECtech parameter and includes all 18-track transports.
PAGE 699
4490 Cartridge Subsystem— Cartridge tape transports that provide read/write capability for 36-track recording format and extended capacity tape. 4490 transports can also read data recorded in 18-track format. The StorageTek 4490 Cartridge Subsystem is equivalent to a 3490E device. 8500 library— See StreamLine (SL8500) library. 9310 LSM— See PowderHorn LSM. 9360 LSM— See WolfCreek LSM.
PAGE 700
670 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 701
Index DIAGScan 206 EMPTYCel 206 INTRANs 207 Numerics 4480 Cartridge Subsystem, defined 668 4490 Cartridge Subsystem, defined 669 9490 Cartridge Subsystem, defined 669 9490EE Cartridge Subsystem, defined 669 9840 Cartridge Subsystem, defined 669 A abend codes HSC 347 SCP 347 abnormal mounts/dismounts 35 access method, defined 655 ACS See Automated Cartridge System ACS UTIL exec, description 174 ACSCMS exec, description 175 ACSid, defined 655 ACSPROP exec overview 425 parameters 426 syntax 426 usage require
PAGE 702
backup, CDS 170 Base service level, description 21 Batch Application Program Interface (API) overview 82, 629 QCDS request addresses and registers 630 function 629 invoking 629 output description 644 programming considerations 633 return codes 634 sample requests 635 syntax 631 SLSUREQM mapping macro 645 SLUVADAT, Flat File ACS/LSM Information DSECT 563 SLUVCDAT, Flat File Static Configuration Data DSECT 571 SLUVHDAT, Flat File Host Information DSECT 574 SLUVIDAT, Flat File CDS Information DSECT 577 SLUVS
PAGE 703
control data set definition control statement 448 control statement continuation conventions 86, 107, 439 control statements CDS Definition (CDSDEF) 87 continuation 86, 107, 439 EXECParm 90 Journal Definition (JRNDEF) 92 License Key Definition (LKEYDEF) 94 License Key Information (LKEYINFO) 96 LKEYINFO 96 LMU Path (LMUPATH) 108 LMU Path Definition (LMUPDEF) 110 OPTion TITLE 113 Reconfiguration CDS Definition (RECDEF) 98 Scratch Subpool 100 Scratch Subpool Definition (SCRPDEF) 115 specifying a CAPid 434 synt
PAGE 704
JCL example 238 JCL requirements 236 output description 238 parameters 236 prerequisites 236 syntax 236, 458 disconnected mode, defined 658 dismount abnormal 35 processing 33, 34 DISMount command 467 Dismount parameter 480 Display command 384, 468 DOMed, defined 658 DRAin CAP command 476 drive loaded, defined 658 drive panel, defined 658 DRIVEid, defined 658 dual LMU defined 658 environment 15 functionality 66 dump defined 658 dumps analysis using SLUIPCS 394 common analysis tasks display queued WTO message
PAGE 705
Scratch Subpool control statement 102 SCRPDEF command and control statement 117 selective audit 1 ACS, 2 LSMs w/CAPid, JCL for 208 with panel/discrepancy list, JCL for 208 TAPEREQ control statement 132 TREQDEF control statement 135 Unit Attribute Definition (UNITDEF) control statement 142 UNITATTR control statement 139 VOLDEF control statement 112, 156 Volume Attribute (VOLATTR) control statement 153 Volume Attribute Definition (VOLDEF) control statement 156 EXECParm control statement example 91 overview 9
PAGE 706
setting 417 Unselect utility 322 Volume Report utility 338 I Job control Language (JCL) Move utility 261 Improved Cartridge Recording Capability (ICRC), defined 660 Journal command 478 Index, defined 660 INISH deck, defined 660 Initial Microprogram Load (IML), defined 660 Initial Program Load (IPL), defined 660 initial value, defined 661 input stack, defined 661 installation functions 20 Installation Verification Programs (IVP), defined 661 internal trace table 374 inventory cartridges in the library
PAGE 707
MONITOR 478 MOVe 481 OPTion 482 RECover 482 RELease 482 SENter 483 SRVlev 483 STOPMN 483 SWitch 483 TRace 484 Vary 484 VIew 485 Warn 486 Library Control Unit (LCU), defined 661 Library Management Unit (LMU) defined 661 dynamic network connections to TCP/IP 70 LMU LAN interface error codes (0501-0512) 615 operator control of dual 66 response codes 611 server functions 66 standby, defined 665 Library Storage Module (LSM) automatic update from 4410 to 9310 50 defined 661 hardware error codes (0801-0809) 618 lo
PAGE 708
SLSSCAPJ, SMF CAP Eject Record 508 SLSSCAPN, SMF CAP Enter Record 509 SLSSDJLR, LOGREC Database/Journaling 553 SLSSFHDR, SMF Record Header 501 SLSSHLG1, LOGREC Host Communications Format 559 SLSSLHDR, LOGREC Header Layout 526 SLSSLLG1, LOGREC LMU Driver Format 535 SLSSLLG2, LOGREC LMU Driver Format 540 SLSSLLG3, LOGREC Host Communications Format 542 SLSSLLG4, LOGREC LMU Driver Format 543 SLSSLLG5, LOGREC Dual LMU Status Change 545 SLSSLLG6, LOGREC Robotic Motion & Soft Fail Counts Record 548 SLSSLSB, SMF LM
PAGE 709
command-name 468 COMMPath 468 comp-list 484 comp-name 484 dataset.
PAGE 710
Journal Definition (JRNDEF) 92 License Key Definition (LKEYDEF) 94 License Key Information (LKEYINFO) 96 options 84 overview 83 processing 84 Reconfiguration CDS Definition (RECDEF) control statement 98 Scratch Subpool 100 pass-thru reduction 422 scheduled 423 unavoidable 423 unnecessary 423 Pass-thru port (PTP), defined 663 performance considerations ACSPROP exec 425 Activities Report utility 412 Audit utility 427 CAP preferences 414 communication parameters 418 library activity 411 limiting view time 419
PAGE 711
SLUVHDAT, Flat File Host Information DSECT 574 SLUVIDAT, Flat File CDS Information DSECT 577 SLUVPDAT, Batch API CAP Information DSECT 598 SLUVSDAT, Flat File ACS Station Address DSECT 580 SLUVVDAT, Flat File Volume Data DSECT 582 S recovery functions 54 SCP abend codes 347 external trace facility 367 internal trace table 349 messages 347 SET TRACE command 349 Trace Facility 366 recovery functions 58 SCP trace formatter utility 368 RECover Host command 482 REcovery functions, common 54 recreating (re
PAGE 712
device numbers for drives 302 function 300 invoking 317 JCL requirements 316 new host parameters LIKEHOST 310 NEWHOST 310 output description 319 overview 299 parameters 304 LIKEHOST 310 NEWHOST 310 Set Cleaning Prefix 305 Set Delete Disposition 307 Set Device Numbers for Drives 311 procedure 314 running with HSC active 313 Set Eject Password 307 SET ENQ/DEQ/RESERVE Qname 310 Set Freeze Panel 308 Set Host ID 309 Set HSC Command Prefix 305 Set HSC Level 309 Set LMU Station Address Numbers 314 Set Nonlibrary D
PAGE 713
Performance log reblocker 263 Reconfiguration CDS Definition (RECDEF) control statement SRVlev command syntax 483 98 stand-alone utilities 185 Reconfiguration CDS Definition (RECDEF)control statement standard (4410) LSM, defined 665 450 RECover Host command 482 RELease CAP command 482 REPLace utility 295 Restore utility 277 SCRAtch 295 Scratch Conversion utility 462 Scratch Redistribution utility 285, 462 Scratch Subpool control statement 100, 450 SCRAtch utility 461 SENter command 483 Set utility 30
PAGE 714
T9840C Cartridge Subsystem, defined 669 parameters 296 syntax 295 T9940A Cartridge Subsystem, defined 669 T9940B Cartridge Subsystem, defined 669 Tape Management Interface (TMI), description 81 TAPEREQ control statement disabling 119 example 132 overview 118 parameters 123 PROGram/PGMname 124 syntax 121 usage 118 TCP/IP connections to the LMU 70 TimberWolf (9740) LSM, defined 666 TimberWolf CAP, defined 666 TRace command 484 trace facilities, software CCWTRACE 348 CP trace table 348 IPARML (IUCV Parameter
PAGE 715
CP and CMS 6 operators and utility users 9 overview 6 SCP 7 tape management system (TMS) 9 Z ZCART, defined 668 Zeroscr parameter 466 VOLDEF command and control statement examples 112, 156 VOLSER defined 667 ranges and lists 436 volume defined 667 specifying 143 Volume Attribute (VOLATTR) control statement disabling 144 examples 153 overview 143 parameters 147 syntax 145 usage 143 Volume Attribute Definition (VOLDEF) control statement examples 156 overview 154 parameters 155 syntax 155 volume report recor
PAGE 716
686 VM/HSC 6.0 System Programmer’s Guide 1st ed.
PAGE 717
PAGE 718
Printed in U.S.A.