StorageTek Host Software Component 6.0 System Programmer's Manual

page of 718

/ 718
Contents
Table of Contents
Bookmarks

Table of Contents

Quick Links

Download this manual

Host Software Component

(VM Implementation)

System Programmer's Guide

Release 6.0

312579601

Table of Contents

Need help?

Do you have a question about the Host Software Component 6.0 and is the answer not in the manual?

Questions and answers

Summary of Contents for StorageTek Host Software Component 6.0

Page 1 Host Software Component (VM Implementation) System Programmer’s Guide Release 6.0 312579601...
Page 2 The information in this document, including any associated software program, may not be reproduced, disclosed or distributed in any manner without the written consent of Storage Technology Corporation. Should this publication be found, please return it to StorageTek, One StorageTek Drive, Louisville, CO 80028-5214, USA. Postage is guaranteed.
Page 3 Document Effectivity EC Number Date Doc Kit Number Type Effectivity 128976 June, 2004 First Edition This document applies to the Host Software Component for VM (VM/HSC), Version 6.0. Document Effectivity iii 1st ed., 6/30/04 - 312579601...
Page 4 iv VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 5: Table Of Contents
StorageTek HSC Publications - VM environment ....... . .
Page 6 Matching VOLATTR and TAPEREQ Statements ....... . Precedence of VOLATTR and TAPEREQ Statements ......Mount/Dismount Functions .
Page 7 Options Offered by PARMLIB Control Statements ....... . Control Statement Continuation Conventions ........CDS Definition (CDSDEF) Control Statement .
Page 8 Utility Environmental Requirements ..........ACS UTIL Exec .
Page 9 Parameters ..............JCL Requirements .
Page 10 Journal Offload Utility ............Syntax .
Page 11 JCL Requirements ............Invoking the Scratch Redistribution Utility .
Page 12 SCP Messages ............Abend Codes .
Page 13 Using the Performance Measurement and Predictive Maintenance System (PM2) ..Redistribute Scratch Volumes in the Library ......... . Maintain Quantities of Scratch Cartridges .
Page 14 How to Specify a CAPid ........... . CAPid Formats .
Page 15 Reconfiguration utility ............REPLace utility .
Page 16 DUMP Command ............FILE Command .
Page 17 SLSSLHDR ............. . SLSSVLG1 .
Page 18 LSM Robotics Error Codes: 0701 - 0718 ........LSM Hardware Error Codes: 0801 - 0809 .
Page 19 Figures Figure 1. HSC Architecture ............Figure 2.
Page 20 Figure 27. Subsystem Data Relationships ..........Figure 28.
Page 21 Tables Table 1. HSC Command Execution at Base and Full Service Levels ......Table 2. Utility Execution at Base and Full Service Levels .
Page 22 Table 27. SLLUIPCS Print Options ........... . Table 28.
Page 23 Table 60. SLUVHDAT Record Format ..........Table 61.
Page 24 xxiv VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 25: What's New With This Release
What’s New With This Release? HSC 6.0 includes the following enhancements and modifications: Publication(s)/ Enhancement/Modification Primary Locations Support for the StreamLine (SL8500) library. Installation Guide Chapter 2, Calculating DASD Space Chapter 6, SLILSM, SLIDRIVS macros Chapter 7, Storage Cell Capacity for StreamLine SL8500 Libraries Appendix B, Library Configurations...
Page 26 Publication(s)/ Enhancement/Modification Primary Locations The HSC mount/dismount component has been changed to allow any host to System Programmer’s Guide mount or dismount a volume. Previously, only the mounting host could perform Chapter 2 mount/dismount operations. 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...
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...
Page 28: How To Use This Guide
Chapters 1 and 2 provide general overview information that is useful to anyone associated with the Automated Cartridge System and the HSC software. It is recommended by StorageTek that these two chapters be read and understood. Most of the information in this guide is of primary interest to the system programmer and computer system administrator.
Page 29: References To Hsc Product Releases
See the Requesting Help from Software Support guide for information about contacting StorageTek for technical support and for requesting changes to software products. See “Gather Diagnostic Materials” on page 408 for information about diagnostic materials that Software Support might request.
Page 30 xxx VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 31: Chapter 1. System Description
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.
Page 32 - TimberWolf (9740) 10-cell removable magazine or 14-cell permanent rack - 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. •...
Page 33: Host Software Component Overview
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 •...
Page 34: Hsc Subsystem Components
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. The external components consist of an installation component, the initialization/termination component, a command component, the utility component, and a tape management interface component.
Page 35: Figure 1. Hsc Architecture
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. USER’S HSC ADDRESS SPACE ADDRESS SPACE HSC STARTUP INITIALIZATION COMMAND /TERMINATION (S SLS) APPLICATIONS OPERATOR UTILITIES COMMANDS...
Page 36: Vm Environment
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) •...
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 •...
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.
Page 39: Virtual Machine Configuration
Host Software Component (HSC) The HSC runs as an application program in the SCP environment. The HSC source code is compiled by StorageTek. The HSC accepts requests from the tape management interface (TMI) (see “Tape Management System (TMS)” below) and drives the library hardware.
Page 40: Hsc And Automated Cartridge System Interaction
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).
Page 41: Figure 2. Virtual Machine Relationships
VM HOST A NONLIBRARY TAPE DRIVE REQUESTOR SERVICE (CMS) MACHINE 3174/3274 TERMINAL CONTROL UNIT OPERATOR PRIMARY STANDBY SECONDARY CONTROL CONTROL CONTROL DATA SET DATA SET DATA SET SERVICE OPERATOR MACHINE (CMS) ADMINISTRATOR RSCS ADMINISTRATOR (CMS) VM HOST B RSCS OPERATOR ADMINISTRATOR C27925 Figure 2.
Page 42: Figure 3. Shared Library Data Sets
VM/XA HOST VM/SP HOST MVS HOST MVS/XA (JES2 OR JES3) MVS/XA SERVICE SERVICE GUEST MACHINE MACHINE JOURNAL JOURNAL JOURNAL JOURNAL PRIMARY SECONDARY CONTROL CONTROL DATASET 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
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.
Page 44: Figure 4. Hsc/Automated Cartridge System Interaction
PRIMARY STANDBY SECONDARY CONTROL CONTROL CONTROL JOURNALS DATA SET DATA SET DATA SET HOST 1 HOST 2 HOST 3 HOST 16 3274 3274 CONTROL UNIT (0) CONTROL (7) (STATIONS 1 - 16) (STATIONS 1 - 16) LMU 0 LMU 255 LOCAL LOCAL LAN 0...
Page 45: Dual Lmu Environment
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
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.
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 •...
Page 48 18 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 49: Chapter 2. Host Software Component Functions
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.
Page 50: Facilities Available For User Control Of Hsc Functions
• 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.
Page 51: Initialization/Termination Functions
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 •...
Page 53: Table 1. Hsc Command Execution At Base And Full Service Levels
Table 1. HSC Command Execution at Base and Full Service Levels Service Level Execution Command Base Full CAPPref CLean COMMPath DISMount Display DRAin EJect ENter Journal LIst MNTD MODify (F) MONITOR (MN) Mount MOVe OPTion RECover RELease SENter SRVlev STOPMN (PM) SWitch TRace TRACELKP...
Page 54: Table 2. Utility Execution At Base And Full Service Levels
Table 2. Utility Execution at Base and Full Service Levels Service Level Execution Utility Base Full AUDIt BACKup EJECt ENTEr LIBGen MOVe OFFLoad REPLaceall RESTore SCRAtch SCREdist UNSCratch UNSElect VOLRpt 24 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
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
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.
Page 57: Media And Rectech Parameters
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
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.
Page 59: Matching Volattr And Tapereq Statements
EDL, they are used to satisfy the request, unless doing so would cause the job to fail. StorageTek recommends placing all control statements in a most specific to least specific order. Very general VOLATTR or TAPEREQ statements should be placed last to act as a global or site defaults.
Page 60: Precedence Of Volattr And Tapereq Statements
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. For example, if the TAPEREQ statement specifies MEDia(ECART) RECtech(36track) and the VOLATTR statement specifies MEDia(Standard) but does not specify RECtech, the result is MEDia(Standard) from the VOLATTR statement and RECtech(36track) from...
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; ... This indicates that one of the following has occurred: •...
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/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.
Page 64: Mount Processing For Scratch Volumes
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 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: Abnormal Mounts/Dismounts
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.
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.
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.
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.
Page 69 VOLATTR SERial(CLN500-CLN599) MAXclean(nn) 5. Contact your StorageTek Customer Services Engineer for appropriate MAXclean values for different cleaning media types. Limits on the Use of Cleaning Cartridges Cleaning cartridges should only be used a limited number of times.
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., 6/30/04 - 312579601...
Page 73: Volume/Cell Control Functions
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: •...
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.
Page 76: Cartridge Access Port (Cap) Processing Functions
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.
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.
Page 79: Near Continuous Operations
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. This section discusses the following topics: • using multiple CDS copies •...
Page 80: Automatic Recognition Of Configuration Changes
CDS copy is copied over the standby CDS copy, and the standby becomes the new secondary copy. To utilize full automatic CDS recovery capabilities of the HSC, StorageTek recommends that all three CDS copies (primary, secondary, and standby) should be used. CDS copies must be created (by the SLICREAT program), defined to the HSC (by the CDSDEF control statement in PARMLIB), and active (by the CDs Enable/Disable command).
Page 81: Defining A New Configuration To Avoid Future Reconfigurations
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.
Page 82: Changing Panels
LIBGEN, SLICREAT, reconfiguration process to change other panel types. Notes: 1. StorageTek CSEs will change the library hardware at the same time the panel type is being changed. 2. The HSC must be recycled before the LSM and ACS containing the changed panel configuration can be brought online to the HSC.
Page 83 MOVe Flsm(aa:ll) Panel(pp) TLsm(aa:ll) Because the panel has been frozen, cartridges cannot be moved to it, and the rows will remain empty. The StorageTek CSEs will make the hardware changes required. 3. After the hardware changes are complete, unfreeze the panel, if it is still frozen.
Page 84: Using Cds Rename/Relocate/Expand
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.
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.
Page 87: Swapping Library Transports - New Model Types
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.
Page 88: Common Recovery Functions
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.
Page 89: Control Data Set Recovery Techniques
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.
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.
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.
Page 92: Command Functions
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. CARTRIDGE CONTROL ALLOC (MVS only) DISMount Display...
Page 93: Controlling Lsm Operating Mode
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: •...
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: •...
Page 95: Utility Functions
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. Utility Functions Overview Refer to Chapter 4, “Utility Functions”...
Page 96: Lmu Server Functions
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: Table 4. Hsc/Lmu Validity Matrix
New HSC features are available. Dual LMU must be configured . Switchover can be automated. * Configuration of dual LMU is done by a StorageTek Customer Services Engineer (CSE). Chapter 2. Host Software Component Functions 67 1st ed., 6/30/04 - 312579601...
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.
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.
Page 100: Dynamic Lmu Connection
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”...
Page 101: Multiple Tcp/Ip Stack Implications
For example, if a user enters Display CDS and the following output appears HOSTID---LEVELFLAG---DESCRIPTION--- HSTA 4.0.0 (F0) ACTIVE PRIMARY SECONDARY STANDBY HSTB 4.0.0 (F0) ACTIVE PRIMARY SECONDARY STANDBY HSTC 4.0.0 (F0) ACTIVE PRIMARY SECONDARY STANDBY HSTD 4.0.0 (F0) ACTIVE PRIMARY SECONDARY 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
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.
Page 103: Recovering Tcp/Ip Communications
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 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
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.
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 <vaddr>...
Page 108: Communication Functions
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: Figure 8. Hsc Communication Methods Between Multiple Hosts
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.
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.
Page 111: Tape Management Interface
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)
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).
Page 113: Chapter 3. Hsc Control Statements And Hsc Start Procedure
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
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”...
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.
Page 116: Control Statement Continuation Conventions
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 •...
Page 117: Cds Definition (Cdsdef) Control Statement
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.
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.
Page 120: Execparm Control Statement
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.
Page 121 EXECParm 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.
Page 122: Journal Definition (Jrndef) Control Statement
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: •...
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.
Page 124: Lkeydef Command And Control Statement
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.
Page 126: License Key Information (Lkeyinfo) Control Statement
Indicates the product identifier. For HSC 6.0, the product identifier is VER0600. CUSTomer Specifies the customer name as received from StorageTek. A maximum of 20 characters can be entered for the customer name. customer-name Indicates the customer name. SITEno Specifies the site number as received from StorageTek.
Page 127 LKEYINFO 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’) -...
Page 128: Reconfiguration Cds Definition (Recdef) Control Statement
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;...
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., 6/30/04 - 312579601...
Page 130: Scratch Subpool Control Statement
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 statement has been specified, the HSC reads only the last RANGE setting it encounters and loads only that range. All other ranges are ignored. StorageTek recommends that you specify multiple ranges, separated by commas, on one SCRPOol control statement if possible. LABEL type specifies the label type associated with the applicable subpool.
Page 132 SCRPOol Example The following is an example of using the Scratch Subpool control statement. SCRPO NAME(SITE1),RANGE(100000-200000,300000-400000),LABEL(SL) SCRPO NAME(SITE2),RANGE(500000-540072),LABEL(NL),HOSTID(HSC1) SCRPO NAME(SITE3),RANGE(540081-610094),LABEL(NSL) SCRPO 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. The following are additional methods that may be used: •...
Page 133: Definition Data Set Control Statements
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
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.
Page 135: Defining Lmu Network Connections
(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)
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.
Page 137: Identifying The Definition Data Sets (Option Title)
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 Control Statement
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.
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.
Page 140: Lmupdef Command And Control Statement
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.
Page 141 LMUPDEF Syntax LMUPDEF DATASET(dataset.name) DSN(dataset.name) VOLume(volser) UNIT(unitname) HOSTID( host-id 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.
Page 143: Option Title Control Statement
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;...
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., 6/30/04 - 312579601...
Page 145: Scratch Subpool Definition (Scrpdef) Command And Control Statement
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).
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) VOLume(volser) UNIT(unitname) HOSTID( host-id 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.
Page 148: Tape Request (Tapereq) Control Statement
These statements cause the HSC to attempt to select a Standard scratch cartridge from a subpool that contains only helical cartridges. To avoid such scenarios, StorageTek recommends that all applicable parameters be coded on each TAPEREQ and that parameters such as SUBPool not be specified on generic TAPEREQ statements.
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.
Page 151 TAPEREQ Syntax TAPEREQ JOBname( jobname STEPname( stepname program-name dataset-name PROGram( DATASET( PGMname(program-name) DSN(dataset-name) DDName(DD-name) RETPD( ,retention-period EXPDT( ,expiration-date VOLType( Specific Nonspec Chapter 3. HSC Control Statements and HSC Start Procedure 121 1st ed., 6/30/04 - 312579601...
Page 152 TAPEREQ Syntax (continued) MEDia( LONGItud RECtech( LONGItud 18track Standard 36track 36Atrack MEDIA1 36Btrack 36Ctrack HELical 3480 STK1R ECART STK1R34 STK1R35 ECCST STK1RA ETAPE STK1RA34 STK1RA35 Long STK1RB MEDIA2 STK1RB34 3490E STK1RB35 ZCART STK1RAB STK1RAB4 STK1RAB5 HELical STK1RC STK1RC34 DD3A STK1RC35 DD3B STK2P DD3C...
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 •...
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.
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. equal to not equal to greater than greater than or equal to less than...
Page 156: Table 5. Tapereq Media Default Values
STK2PA34, STK2PA35, STK2PB, STK2PB34, STK2PB35 To avoid problems, StorageTek recommends that all TAPEREQ statements specify MEDia and RECtech consistently. Make sure to include either one or both parameters on each statement. If both media type and recording technique are omitted, all available devices are eligible for allocation.
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. indicates any DD3A, DD3B, or DD3C (HELical) cartridge.
Page 158: Table 6. Tapereq Rectech Default Values
MEDia parameter on the first matching TAPEREQ. Table 6 shows default values used if RECtech is omitted. To avoid problems, StorageTek recommends that all TAPEREQ statements specify MEDia and RECtech consistently. Make sure to include either one or both parameters on each statement.
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. 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.
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.
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. 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.
Page 162 TAPEREQ Example The following example illustrates how to use TAPEREQ statements to specify tape request attributes. Set Tape Request Attributes TAPEREQ DSN(BACKUP.**) MEDIA(ECART) RECTECH(36TRACK) TAPEREQ DSN(PAYROLL.**) MED(DD3A) RECTECH(DD3) TAPEREQ MED(STANDARD) RECTECH(36TRACK) TAPEREQ 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.
Page 163: Tape Request Definition (Treqdef) Command And Control Statement
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).
Page 164 TREQDEF Syntax TREQDEF DATASET(dataset.name) DSN(dataset.name) VOLume(volser) UNIT(unitname) HOSTID( host-id 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”...
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.
Page 166: Unit Attribute (Unitattr) Control Statement
3590-type devices. For library devices, the model type is determined by the LMU. For newly defined drives, if the LSM has not been online, the model has not been reported by the LMU. Because of this, StorageTek recommends that UNITATTRs be defined for both library and nonlibrary devices.
Page 167 UNITATTR Syntax UNITATTR ADDRess( unit-address UNITATTR ADDRess( unit-address unit-address-range MODel( 4480 unit-address-range MODel( 4480 4490 4490 9490 unit-address-list 9490 9490EE unit-address-list 9490EE 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)
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.
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.
Page 170: Unit Attribute Definition (Unitdef) Command And Control Statement
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.
Page 171 UNITDEF Syntax UNITDEF DATASET(dataset.name) DSN(dataset.name) VOLume(volser) UNIT(unitname) HOSTID( host-id 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”...
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.
Page 173: Volume Attribute (Volattr) Control Statement
VAR reflects volume information from the LMU and can be compared to the VOLATTRs. StorageTek recommends that the volume attribute statements in effect be the same on all processors; if not, results are unpredictable. Chapter 3. HSC Control Statements and HSC Start Procedure 143...
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);...
Page 175 VOLATTR Syntax VOLATTR SERial( volser vol-range MEDia( Standard vol-list MEDIA1 3480 ECART ECCST ETAPE Long MEDIA2 3490E ZCART DD3A DD3B DD3C DD3D STK1R STK1U STK2 STK2P STK2W This syntax diagram is continued on the next page. Chapter 3. HSC Control Statements and HSC Start Procedure 145 1st ed., 6/30/04 - 312579601...
Page 176 VOLATTR Syntax (continued) RECtech( LONGItud MAXclean(use-limit) 18track 36track 36Atrack 36Btrack 36Ctrack HELical 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.
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.
Page 178: Table 7. Volattr Media Default Values
STK2PA34, STK2PA35, STK2PB, STK2PB34, STK2PB35 If both media type and recording technique are omitted, all media types and recording techniques are assumed to be eligible StorageTek recommends that MEDia always be specified on all VOLATTR statements. Valid media types are: Standard indicates a standard length, 3480 cartridge.
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).
Page 180: Table 8. Volattr Rectech Default Values
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: •...
Page 181 VOLATTR 36Btrack indicates a 9490 (Timberline) transport. 36Ctrack indicates a 9490EE transport. HELical indicates a device using helical recording. 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.
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.
Page 183 VOLATTR SER(CLN300CLN599) MED(S) REC(LONGI) VOLATTR SER(*) REC(18) Notes: 1. Ask your StorageTek CSE about recommended MAXCLEAN values for specific types of cleaning cartridges. 2. In the example above, the last VOLATTR statement specifies a user-defined default for all volumes that do not match any of the previous statements.
Page 184: Volume Attribute Definition (Voldef) Command And Control Statement
Notes: 1. StorageTek recommends that volume attributes be the same on all processors. This can be assured by defining the same volume attribute definition data set to all hosts. 2. When the VOLDEF command is issued, if the definition data set contains errors, an HSC message provides the parameter in error, a description of the problem, and the line number where the error occurred.If the definition data set contains errors, none...
Page 185 VOLDEF Syntax VOLDEF DATASET(dataset.name) DSN(dataset.name) VOLume(volser) UNIT(unitname) HOSTID( host-id 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”...
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.
Page 187: Creating An Slkjcl File For Starting The Hsc
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”...
Page 188 HSC that is at a different release level than the HSC that was previously running on a host. When an initializing HSC detects a release level difference, it performs an automatic internal cold start. Contact StorageTek Software Support before using this parameter (see the guide Requesting Help from Software Support for more information). RESET specifies that all subsystem status flags in the Subsystem Communications Vector Table (SSCVT) for the HSC are unconditionally reset.
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. xxxx is 1 to 4 hex characters specifying the GTF event ID used for the duration of this subsystem.
Page 190: Hsc Startup Job (Acs Slkjcl)
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.
Page 191 Example The following listing is an example job for the ACS INIT command. Sample ACS SLKJCL File /JOB jobname SLSBINIT /PARM E(E086) F(17) MEMBER(xx) /FILE SLSSYSXX DEV <vaddr> DSN <dsname><(member)> /COMM If using a library with multiple hosts /COMM modify the /FILE SLSSYSXX statement above /COMM and delete the lines following it /COMM Else delete the /FILE SLSSYSXX statement above...
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.
Page 193: Starting Hsc Execution
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.
Page 194: Multiple Hosts Startup Considerations
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.
Page 195: Starting The Hsc
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
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 -...
Page 197: Initializing The Hsc To The Base Service Level
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.
Page 198 168 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 199: Chapter 4. Utility Functions
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 •...
Page 200: Selecting A Utility
• 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.
Page 201 Table 10. HSC Utilities and Functions (Continued) Function Utility to Use Restore or recreate the library CDS RESTore Set or change library configuration information, including: - ACS esoteric - CDS level - cleaning prefix - delete disposition - device numbers for drives - eject password - host identification - HSC command prefix...
Page 202: Typical Use Of Utilities
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: Control Statement Syntax Conventions
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...
Page 204: Acs Util Exec
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.
Page 205: Cms Environment
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...
Page 206: Scp Environment
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).
Page 207: Jcl And Control Statements
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.
Page 209: Submitting Jobs
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.
Page 210: Utility Control Statements
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)
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
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
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: Example
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.
Page 215: Stand-Alone Utilities
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.
Page 216: Activities Report Utility
CMS environment. Note: In the CMS environment, this utility can report only on SMF data created by the library when running in the StorageTek SCP environment. The Performance Log Reblocker (SLUPERF) utility must be run prior to executing the Activities Report utility. Parameters are passed to the utility in a control file (SLUACTV PARMS).
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.
Page 218: Syntax
Activities Report Syntax ACTIvities Optional Parameters Optional Parameters: TODAY 00:00:00 BEGIN( begin-date begin-time TODAY 23:59:59 END( end-date end-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) 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.
Page 220: Invoking The Activities Report Utility
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 <ctlfname|SLUACTV> <ctlftype|PARMS> <ctlfmode|*> To execute the ACTIvities utility: 1.
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.
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.
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.
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.
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.
Page 227: Figure 9. Activities Report Utility Sample Output
Activities Report SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0001 TIME hh:mm:ss Control Card Image Listing DATE yyyy-mm-dd ACTIVITIES BEGIN(20040301) SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0002 TIME hh:mm:ss Activities Begin 2004-03-01 DATE yyyy-mm-dd SYSTEM IDS: HSC1 HSCH HSCF HSCE HSC6 HSC2...
Page 228: Audit Utility
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). Identification of the library components to be audited may include: •...
Page 229: Media Type Mismatch Conditions
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.
Page 230: Actions Permitted During An Audit
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: Concurrent Audits
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.
Page 232: Syntax
Audit Syntax AUDIt ACS(acs-id) Optional Parameters APPLy Optional Parameters: LSM(lsm-list) PANel(panel-list) ROW(row-list) COLumn(column-list) CAP(cap-id) DIAGScan( EMPTYCel ONLY INTRANs ALSO Utility Name AUDIt specifies that an audit operation is to be performed. Parameters specifies that the total library is to be audited. APPly (YES) specifies that the Audit operation ejects cartridges with duplicate VOLSERs,...
Page 233 Audit 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 (:).
Page 234 Audit 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.
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. •...
Page 236 The main benefit provided by auditing only empty cells is reducing the time required to run an audit. Note: StorageTek does not recommend running an empty cell audit on an SL8500 library because the time to run the audit will not be substantially reduced.
Page 237: Jcl Requirements
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.
Page 238: Jcl Examples
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 jobname...
Page 239: Output Description
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)
Page 240: Figure 10. Audit Utility Sample Output
Audit SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0001 TIME hh:mm:ss Control Card Image Listing DATE yyyy-mm-dd AUDIT ACS(00) LSM(11) SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0002 TIME hh:mm:ss Audit Utility DATE yyyy-mm-dd -SLS0231I Audit phase 1 (Registration) completed...
Page 241: Backup Utility
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.
Page 242: How The Backup Utility Functions
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.
Page 243: Backup Procedure
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”...
Page 244: Syntax
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.
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.
Page 247: Jcl Requirements
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.
Page 248: Invoking The Backup Utility
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...
Page 249: Jcl Examples
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: Output Description
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 SLUADMIN /PARM MIXED...
Page 251 Backup • a condition code from backup processing: no errors and no SLUADMIN control cards generated warning MESSAGES – Backup successful a system failure occurred. Restart or rerun backup. Chapter 4. Utility Functions 221 1st ed., 6/30/04 - 312579601...
Page 252: Figure 11. Backup Utility Sample Output
Backup SLUADMIN (n.n.n) STORAGETEK AUTOMATED CARTRIDGE SYSTEM UTILITY PAGE 0001 TIME hh:mm:ss CONTROL CARD IMAGE LISTING DATE yyyy-mm-dd BACKUP OPTION(ANALYZE) SLUADMIN (n.n.n) STORAGETEK AUTOMATED CARTRIDGE SYSTEM UTILITY PAGE 0002 TIME hh:mm:ss BACKUP UTILITY DATE yyyy-mm-dd SLS1315I SPRC.@793665.V6L.DBASEPRM WAS SELECTED AS THE PRIMARY CONTROL DATA SET...
Page 253 Backup SLUADMIN (n.n.n) STORAGETEK AUTOMATED CARTRIDGE SYSTEM UTILITY PAGE 0004 TIME hh:mm:ss BACKUP UTILITY DATE yyyy-mm-dd SLS1210I PROCESSING HAS STARTED FOR THE DITA BLOCK SLS1211I PROCESSING COMPLETE FOR THE DITA BLOCK SLS1210I PROCESSING HAS STARTED FOR THE DITR BLOCK SLS1211I PROCESSING COMPLETE FOR THE DITR BLOCK...
Page 254: How To Restart Backup
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.
Page 255: Database Decompile (Libgen) Utility
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: Syntax
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.
Page 257: Invoking The Database Decompile Utility
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 SLUADMIN...
Page 258: Output Description
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: Figure 12. Database Decompile Utility Sample Output
Database Decompile *********************************************************************** THIS IS A LIBGEN OF A SINGLE ACS WITH 24 POWDERHORN LSMS ATTACHED TO 16 HOSTS. EACH LSM HAS A SINGLE DRIVE PANEL WITH 4 DRIVES *********************************************************************** LIBGEN SLIRCVRY TCHNIQE=SHADOW SLILIBRY SMF=245, ACSLIST=ACSLIST, HOSTID=(EC17,MVSI,ECC4,ECCX,MVSE,MVSF,MVSS, EC21,ECCL,ECCY,MVSC,MVSJ,ECC6,ECCI, SLK1,SLK2), NNLBDRV=(,,,,,,,,,,,,,,,), DELDISP=SCRTCH, MAJNAME=ENQTHIS, CLNPRFX=CLN,...
Page 260 Database Decompile LSM0002 SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM0000,LSM0001,LSM0003,LSM0004), DRIVE=(10), DRVELST=(P00002), TYPE=9310, DOOR=ECAP P000002 SLIDLIST HOSTDRV=(D0000002,D0000002,D0000002,D0000002, D0000002,D0000002,D0000002,D0000002,D0000002, D0000002,D0000002,D0000002,D0000002,D0000002, D0000002,D0000002) D0000002 SLIDRIVS ADDRESS=(0A08,0A09,0A0A,0A0B) *---------------- LSM0003 SLILSM PASTHRU=((8,S),(6,S),(4,M),(2,M)), ADJACNT=(LSM0001,LSM0002,LSM0004,LSM0005), DRIVE=(10), DRVELST=(P000003), TYPE=9310, DOOR=ECAP P000003 SLIDLIST HOSTDRV=(D0000003,D0000003,D0000003,D0000003, D0000003,D0000003,D0000003,D0000003,D0000003, D0000003,D0000003,D0000003,D0000003,D0000003, D0000003,D0000003) D0000003 SLIDRIVS ADDRESS=(0A0C,0A0D,0A0E,0A0F) *---------------- LSM00004 SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM0002,LSM0003,LSM0005,LSM0006), DRIVE=(10), DRVELST=(P000004),...
Page 261 Database Decompile LSM0006 SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM0004,LSM0005,LSM0007,LSM0008), DRIVE=(10), DRVELST=(P000006), TYPE=9310, DOOR=ECAP P000006 SLIDLIST HOSTDRV=(D0000006,D0000006,D0000006,D0000006, D0000006,D0000006,D0000006,D0000006,D0000006, D0000006,D0000006,D0000006,D0000006,D0000006, D0000006,D0000006) D0000006 SLIDRIVS ADDRESS=(0A18,0A19,0A1A,0A1B) *---------------- LSM0007 SLILSM PASTHRU=((8,S),(6,S),(4,M),(2,M)), ADJACNT=(LSM0005,LSM0006,LSM0008,LSM0009), DRIVE=(10), DRVELST=(P000007), TYPE=9310, DOOR=ECAP P000007 SLIDLIST HOSTDRV=(D0000007,D0000007,D0000007,D0000007, D0000007,D0000007,D0000007,D0000007,D0000007, D0000007,D0000007,D0000007,D0000007,D0000007, D0000007,D0000007) D0000007 SLIDRIVS ADDRESS=(0A1C,0A1D,0A1E,0A1F) *---------------- LSM0008 SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM0006,LSM0007,LSM0009,LSM000A), DRIVE=(10), DRVELST=(P000008),...
Page 262 Database Decompile LSM000A SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM0008,LSM0009,LSM000B,LSM000C), DRIVE=(10), DRVELST=(P00000A), TYPE=9310, DOOR=ECAP P00000A SLIDLIST HOSTDRV=(D000000A,D000000A,D000000A,D000000A, D000000A,D000000A,D000000A,D000000A,D000000A, D000000A,D000000A,D000000A,D000000A,D000000A, D000000A,D000000A) D000000A SLIDRIVS ADDRESS=(0A28,0A29,0A2A,0A2B) *---------------- LSM000B SLILSM PASTHRU=((8,S),(6,S),(4,M),(2,M)), ADJACNT=(LSM0009,LSM000A,LSM000C,LSM000D), DRIVE=(10), DRVELST=(P00000B), TYPE=9310, DOOR=ECAP P00000B SLIDLIST HOSTDRV=(D000000B,D000000B,D000000B,D000000B, D000000B,D000000B,D000000B,D000000B,D000000B, D000000B,D000000B,D000000B,D000000B,D000000B, D000000B,D000000B) D000000B SLIDRIVS ADDRESS=(0A2C,0A2D,0A2E,0A2F) *---------------- LSM000C SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM000A,LSM000B,LSM000D,LSM000E), DRIVE=(10), DRVELST=(P00000C),...
Page 263 Database Decompile LSM000E SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM000C,LSM000D,LSM000F,LSM0010), DRIVE=(10), DRVELST=(P00000E), TYPE=9310, DOOR=ECAP P00000E SLIDLIST HOSTDRV=(D000000E,D000000E,D000000E,D000000E, D000000E,D000000E,D000000E,D000000E,D000000E, D000000E,D000000E,D000000E,D000000E,D000000E, D000000E,D000000E) D000000E SLIDRIVS ADDRESS=(0A38,0A39,0A3A,0A3B) *----------------* LSM000F SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM000D,LSM000E,LSM0010,LSM0011), DRIVE=(10), DRVELST=(P00000F), TYPE=9310, DOOR=ECAP P00000F SLIDLIST HOSTDRV=(D000000F,D000000F,D000000F,D000000E, D000000F,D000000F,D000000F,D000000F,D000000F, D000000F,D000000F,D000000F,D000000F,D000000F, D000000F,D000000F) D000000F SLIDRIVS ADDRESS=(0A3C,0A3D,0A3E,0A3F) *---------------- LSM0010 SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM000E,LSM000F,LSM0011,LSM0012), DRIVE=(10), DRVELST=(P000010),...
Page 264 Database Decompile LSM0012 SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM0010,LSM0011,LSM0013,LSM0014), DRIVE=(10), DRVELST=(P000012), TYPE=9310, DOOR=ECAP P000012 SLIDLIST HOSTDRV=(D0000012,D0000012,D0000012,D0000012, D0000012,D0000012,D0000012,D0000012,D0000012, D0000012,D0000012,D0000012,D0000012,D0000012, D0000012,D0000012) D0000012 SLIDRIVS ADDRESS=(0A48,0A49,0A4A,0A4B) *---------------- LSM0013 SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM0011,LSM0012,LSM0014,LSM0015), DRIVE=(10), DRVELST=(P000013), TYPE=9310, DOOR=ECAP P000013 SLIDLIST HOSTDRV=(D0000013,D0000013,D0000013,D0000013, D0000013,D0000013,D0000013,D0000013,D0000013, D0000013,D0000013,D0000013,D0000013,D0000013, D0000013,D0000013) D0000013 SLIDRIVS ADDRESS=(0A4C,0A4D,0A4E,0A4F) *---------------- LSM0014 SLILSM PASTHRU=((2,S),(4,S),(6,M),(8,M)), ADJACNT=(LSM0012,LSM0013,LSM0015,LSM0016), DRIVE=(10), DRVELST=(P000014),...
Page 265 Database Decompile LSM0016 SLILSM PASTHRU=((8,S),(6,S),(4,M)), ADJACNT=(LSM0014,LSM0015,LSM0016), DRIVE=(10), DRVELST=(P000016), TYPE=9310, DOOR=ECAP P000016 SLIDLIST HOSTDRV=(D0000016,D0000016,D0000016,D0000016, D0000016,D0000016,D0000016,D0000016,D0000016, D0000016,D0000016,D0000016,D0000016,D0000016, D0000016,D0000016) D0000016 SLIDRIVS ADDRESS=(0A58,0A59,0A5A,0A5B) *---------------- LSM0017 SLILSM PASTHRU=((2,S),(4,S)), ADJACNT=(LSM0015,LSM0016), DRIVE=(10), DRVELST=(P000017), TYPE=9310, DOOR=ECAP P000017 SLIDLIST HOSTDRV=(D0000017,D0000017,D0000017,D0000017, D0000017,D0000017,D0000017,D0000017,D0000017, D0000017,D0000017,D0000017,D0000017,D0000017, D0000017,D0000017) D0000017 SLIDRIVS ADDRESS=(0A5C,0A5D,0A5E,0A5F) *---------------- SLIENDGN , Figure 12.
Page 266: Directory Rebuild Utility
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 •...
Page 267: Invoking The Database Decompile Utility
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. Invoking the Database Decompile Utility The easiest way to run utilities is to execute the ACS UTIL exec by entering the following command:...
Page 268: Jcl Example
Directory Rebuild JCL Example The following example shows JCL for Directory Rebuild execution. JCL for Directory Rebuild /JOB jobname SLUADMIN /PARM MIXED /FILE SLSCNTL DEV 501 DSN SLS.DBASE /FILE SLSPRINT DEV PRNT CLASS A /FILE SLSIN * DIRBLD Output Description Output resulting from the execution of the Directory Rebuild utility includes: •...
Page 269: Eject Cartridge Utility
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.
Page 270: Utility Name
Eject Cartridge Eject Method 2 (continued): MEDia( Standard RECtech( 18track 36Atrack MEDIA1 36Btrack 36Ctrack STK1R 3480 STK1R34 ECART STK1R35 STK1RA ECCST STK1RA34 ETAPE STK1RA35 Long STK1RB MEDIA2 STK1RB34 3490E STK1RB35 ZCART STK1RAB STK1RAB4 DD3A STK1RAB5 STK1RC DD3B STK1RC34 DD3C STK1RC35 STK1 STK2P STK1R...
Page 271: Parameters
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.
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 •...
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.
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.
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. 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: Jcl Requirements
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. • For 4410 and 9310 LSMs, left-hand 40-cell enhanced CAP •...
Page 277: Jcl Examples
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 jobname...
Page 278: Output Description
• 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.n) StorageTek Automated Cartridge System Utility PAGE 0001 TIME hh:mm:ss Control Card Image Listing...
Page 279: Enter Cartridges Utility
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: Jcl Requirements
Enter Cartridges • 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. •...
Page 281: Jcl Example
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.
Page 282: Figure 14. Enter Cartridge Utility Sample Output
Enter Cartridges SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0001 TIME hh:mm:ss Control Card Image Listing DATE yyyy-mm-dd ENTER CAP(01) SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0002 TIME hh:mm:ss Enter Cartridges Utility DATE yyyy-mm-dd SLS0211I Volume C83040 successfully entered into library...
Page 283: Journal Offload Utility
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.
Page 284: Invoking The Journal Offload Utility
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: Jcl Example
Journal Offload JCL Example The following example shows JCL for the offload of both journals. JCL for Offload of Journals /JOB jobname SLUADMIN /PARM MIXED /FILE SLSCNTL DEV vaddr DSN control.set.name /FILE SLSOFF01 DEV vaddr DSN offload.file1 /FILE SLSOFF02 DEV vaddr DSN offload.file2 /FILE SLSJRN01 DEV vaddr...
Page 286: Figure 15. Journal Offload Utility Sample Output
Journal Offload SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0001 TIME hh:mm:ss Control Card Image Listing DATE yyyy-mm-dd OFFLOAD) SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0002 TIME hh:mm:ss Journal Offload Utility DATE yyyy-mm-dd SLS0282I Journal at DDname SLSJRN01 successfully offloaded to data set defined by SLSOFF01 DD statement...
Page 287: Move Utility
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: •...
Page 288: Syntax
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.
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.
Page 290: Jcl Requirements
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. Invoking the Move Utility The easiest way to run utilities is to execute the ACS UTIL exec by entering the following command: EXEC ACS UTIL MOVe Execution of the statement results in the ACSUTIL SLKJCL file:...
Page 291: Jcl Examples
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: Figure 16. Move Utility Sample Output
Move SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0001 TIME hh:mm:ss Control Card Image Listing DATE yyyy-mm-dd MOVE FLSM(00:04) PANEL(00) TLSM(00:11) SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0002 TIME hh:mm:ss Move Volume Utility DATE yyyy-mm-dd SLS1950I Volume X00609 moved from location 00:04:00:00:00 to location 00:11:00:00:14...
Page 293: Performance Log Reblocker Utility
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.
Page 294: Invoking The Performance Log Reblocker Utility In Cms
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. Invoking the Performance Log Reblocker Utility in CMS The easiest way to run this utility in CMS is to execute the following EXEC by entering: EXEC ACS UTIL SLUPERF Execution of the statement produces the ACSCMS EXEC file:...
Page 295: Jcl Requirements
Performance Log Reblocker SET PERFLOG ON (CLASS class TO JOB AT mvsnode where: enables performance log recording class specifies the virtual spool file class to be used while transferring the spool file specifies to transmit the virtual spool file as a job to the MVS system mvsnode specifies the node of the MVS system 3.
Page 296: Reconfiguration Utility
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.
Page 297: Considerations Before Running Reconfiguration
The following DASD considerations apply to running the Reconfiguration function in a VM-only environment: • If you are using full-volume minidisks for the HSC control data set, StorageTek recommends using OS-format minidisks to allow allocation of multiple data sets on the same real volume for reconfiguration purposes.
Page 298: How The Reconfiguration Utility Functions
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.
Page 299: Table 13. I/O Requirements
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.
Page 300: Running A Successful 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.
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.
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.
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.
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...
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.
Page 306: Restore Utility
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).
Page 307: Special Considerations For Control Data Sets Processing Independently
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: Jcl Requirements
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.
Page 309: Invoking The Restore Utility
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...
Page 310 Restore JCL for RESTore (with Journals Applied) /JOB jobname SLUADMIN /PARM MIXED /FILE SLSBKUP DEV vaddr DSN backup.set.name /FILE SLSCNTL DEV vaddr DSN primary.set.name /FILE SLSCNTL2 DEV vaddr DSN secondary.set.name /FILE SLSSTBY DEV vaddr DSN standby.set.name /FILE SLSJRN#1 DEV vaddr DSN journal1.set.name /FILE SLSJRN#2 DEV vaddr DSN journal2.set.name...
Page 311: Output Description
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:...
Page 312: Figure 17. Restore Utility Sample Output
Restore SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0001 TIME hh:mm:ss Control Card Image Listing DATE yyyy-mm-dd RESTORE GENERATE(YES) SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0002 TIME hh:mm:ss Restore Utility DATE yyyy-mm-dd SLS1212I JCL has been verified for the RESTORE utility...
Page 313: How To Handle Backup/Restore Discrepancies
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 Utility
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 •...
Page 315: Syntax
Scratch Redistribution Syntax SCREdist ACS(acs-id) SUBpool(subpool-name) LSM( lsm-list MEDia( LONGItud RECtech( LONGItud BALtol(tolerance-value) Standard 18track 36track MEDIA1 36Atrack 36Btrack 36Ctrack 3480 HELical ECART STK1R ECCST STK1R34 ETAPE STK1R35 Long STK1RA MEDIA2 STK1RA34 3490E STK1RA35 ZCART STK1RB STK1RB34 HELical STK1RB35 STK1RAB DD3A STK1RAB4 DD3B...
Page 316: Parameters
Scratch Redistribution Parameters 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. 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).
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.
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.
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).
Page 320 Scratch Redistribution HELical indicates a device using helical recording. 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.
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.
Page 322: Jcl Requirements
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. Invoking the Scratch Redistribution Utility The easiest way to run utilities is to execute the ACS UTIL exec by entering the following command: EXEC ACS UTIL SCREDIST Execution of the statement results in the ACSUTIL SLKJCL file:...
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. JCL to Perform Scratch Redistribution /JOB jobname SLUADMIN /PARM MIXED...
Page 324: Output Description
• 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.n) StorageTek Automated Cartridge System Utility PAGE 0001 TIME hh:mm:ss Control Card Image Listing...
Page 325: Scratch Update Utilities
When using the Replace utility, additions to the scratch list(s) are made after an initial clearing of the scratch list(s). StorageTek customers are responsible for creating HSC scratch utility statements to synchronize TMS and HSC scratch population definitions.
Page 326: Parameters
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.
Page 327: Jcl Example
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.
Page 328: Figure 19. Scratch Update Utilities Sample Output
Scratch Update SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0001 TIME hh:mm:ss Control Card Image Listing DATE yyyy-mm-dd SCRATCH VOL(102412,102414) SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0002 TIME hh:mm:ss Scratch Update DATE yyyy-mm-dd SLS0167I Volume 102412 successfully added to library as scratch...
Page 329: Set Utility
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: How The Set Utility Functions
LIBGEN and stored in the CDS. The RESERVE QNAME is used by the HSC and utilities running on each host to ensure that access to the CDS is serialized. The SET utility and HSC use an additional StorageTek-defined RESERVE QNAME to maintain serialization while the customer-defined RESERVE QNAME is being changed.
Page 331: Considerations Before Running The Set Utility
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.
Page 332: Table 15. Set Utility Options
Table 15. SET Utility Options SET Option SET Utility Function and Location of Description ACSDRV “SET ACS Esoteric” on page 304 CLNPRFX “SET Cleaning Prefix” on page 305 COMPRFX “SET HSC Command Prefix” on page 305 DELDISP “SET Delete Disposition” on page 307 EJCTPAS “SET Eject Password”...
Page 333: Syntax
Syntax Options Options: ACSDRV(esoteric) ,FORACS(acs-id) ,FORHOST(host-id) CLNPRFX(prefix) COMPRFX(cmdhex) DELDISP( SCRTCH NOSCRTCH EJCTPAS( newpswd ,OLDPASS(oldpswd) FREEZE( ON ,FORLSMID(lsm-id) ,FORPANEL(panel) HOSTID (newhost),FORHOST(oldhost) HSCLEVEL(OFF),FORHOST(host-id) MAJNAME(qname) NEWHOST(newhost) ,LIKEHOST(model-host) NNLBDRV( esoteric ,FORHOST(host-id) SCRLABL( Note: This syntax is continued on the next page. Chapter 4. Utility Functions 303 1st ed., 6/30/04 - 312579601...
Page 334: Utility Name
Syntax (continued) 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 Utility Name 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 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.
Page 336: Table 16. Mapping Of Command Prefix Codes To Characters
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 Character Description null blank ¢ cent period < less than left parenthesis plus vertical bar...
Page 337 Table 16. Mapping of Command Prefix Codes to Characters 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 “#,” “@,”...
Page 338 (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.
Page 339 1- to 8-character host ID of the host to which the operation is restricted. Note: StorageTek recommends the following alternatives to executing SET HSCLEVEL because they reset the HSC indicators and recover resources owned by the failing host: Chapter 4.
Page 340 • 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.
Page 341 Refer to “Running SET SLIDRIVS With the HSC Active” on page 313 for more information. Caution: StorageTek recommends you bring the HSC down on all hosts before specifying this parameter, and recycle the HSC after every SET SLIDRIVS operation. Table 17 on page 313 describes some instances where the HSC can remain active, however, unpredictable results can occur if the HSC is not terminated.
Page 342 (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.
Page 343: Table 17. Hsc State/Set Slidrivs Operation
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.
Page 344 1. Modify the affected LSM offline (MODify lsm-id OFFline). The LSM will be offline to all hosts. 2. Use SET SLIDRIVS to update the CDS drive records while the StorageTek CSE(s) is making the hardware changes. 3. Recycle the HSC on one host.
Page 345 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.
Page 346: Jcl Requirements
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.
Page 347: Invoking The Set Utility
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.
Page 348: Jcl Examples
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...
Page 349: Output Description
JCL for Multiple SET Statements /JOB jobname SLUADMIN /PARM MIXED /FILE SLSCNTL DEV vaddr DSN control.set.name /FILE SLSCNTL2 DEV vaddr DSN secondary.set.name /FILE SLSPRINT DEV PRNT CLASS A /FILE SLSIN SET HOSTID(HSC2) FORHOST(HSCB) SET SLISTATN(0CD,0DD) FORACS(00) FORHOST(HSC2) SET NNLBDRV(CTAPE) FORHOST(CPUA) SET 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 Utility
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.
Page 351: Utility Name
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.
Page 352: Jcl Example
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. JCL to Unselect a Volume /JOB jobname SLUADMIN...
Page 353: Figure 20. Unselect Utility Sample Output
Unselect SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0001 TIME hh:mm:ss Control Card Image Listing 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.
Page 354: Volume Report Utility
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: Media Type And Recording Technique Considerations
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.
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 •...
Page 357: Syntax
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: Utility Name
Volume Report Utility Name VOLRpt specifies that a volume report is to be produced. Parameters optionally specifies that a report is to be produced for only a particular ACS. (acs-id) The one or two digit hexadecimal ACS identifier. optionally specifies that a report is to be produced for only certain LSMs within an ACS.
Page 359 Volume Report SORT optionally specifies a specified sort sequence. The following options are available: indicates that the report is to be sorted by volume serial number (VOL is the default) indicates that the report is to be sorted by location. indicates that the report is to be sorted by selection count.
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.
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.
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.
Page 363: Jcl/Parameter File Requirements
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: Jcl/Parameter File Syntax
Volume Report Table 18. SLSVA Effect on Volume Report HSC State: SLSVA Specified: SLSVA Not Specified: Active Use VOLATTRs pointed to Use VOLATTRs used by the HSC. by SLSVA. Inactive Use VOLATTRs pointed to The HSC generates an error message saying that SLSVA by SLSVA.
Page 365 Volume Report Note: The ‘‘|’’ symbol indicates that the user must choose either PRINTER or DISK. where: 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.
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.
Page 367: Invoking The Volume Report Utility
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.
Page 368: Jcl Example
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.
Page 369: Output Description
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...
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.
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.
Page 373: Figure 21. Volume Report Summary(Total) Sample Output
Volume Report SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0001 TIME hh:mm:ss Control Card Image Listing DATE yyyy-mm-dd VOLRPT SUMMARY(TOTAL) VOLUME(CLN400-CLN418) SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0002 TIME hh:mm:ss Volume Report Utility DATE yyyy-mm-dd Volume Cell Loc...
Page 374 Volume Report SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0001 TIME hh:mm:ss Control Card Image Listing DATE yyyy-mm-dd VOLRPT SUMMARY(SUB) VOLUME(EE0000-EE9999) SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0002 TIME hh:mm:ss Volume Report Utility DATE yyyy-mm-dd Volume Cell Loc...
Page 375: Figure 22. Volume Report Utility Summary(Subpool) Sample Output
Volume Report SLUADMIN (n.n.n) StorageTek Automated Cartridge System Utility PAGE 0003 TIME hh:mm:ss Subpool Totals, All Ranges ATE yyyy-mm-dd SUBPOOL ID LABEL TYPE RANGE LIMITS SUB1 N/A - N/A SCRATCH SCRATCH Media Rectech 00:00 _______ _______ ACS Total 00:10 ZCART...
Page 376 346 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 377: Chapter 5. Problem Determination, Diagnostics, And Recovery
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 •...
Page 378: Software Trace Facilities
VM/ESA 370. There are several options that control the operation of CCWTRACE. It is recommended that you contact StorageTek Software Support to insure that the proper CCWTRACE options are specified to capture the necessary data for the particular problem at hand.
Page 379: Vm (Cp) Debug Commands
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. ADSTOP Single address stop (VM/SP, VM/SP HPO, and VM/ESA 370) BEGIN Start execution CPTRACE Enable and disable event tracing (VM/XA and VM/ESA) CPTRAP Enable and disable event tracing (VM/SP, VM/SP HPO, VM/ESA 370)
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’...
Page 381 DSP Trace Entry event-type = ‘D’ event-code = dispatch priority TTEWORD1 = R15 TTEWORD2 = R12 TTEWORD3 = R13 Return from SVC Trace Entry event-type = ‘W’ event-code = dispatch priority TTEWORD1 = R15 TTEWORD2 = R0 TTEWORD3 = R1 SIO Trace Entry event-type = ‘S’...
Page 382 RST Trace Entry event-type = ‘R’ event-code = (unused) TTEWORD1 = (unused) TTEWORD2 = (unused) TTEWORD3 = (unused) EXT Trace Entry event-type = ‘E’ event-code = external interrupt code: x’0040’ = ‘CP EXT’ (generic external interrupt) x’1004’ = CLKC (TOD clock comparator) x’1005’...
Page 383: Iparml (Iucv Parameter List)
Table 19. IUCV Functions Code Query X’03’ DESCRIBE X’04’ * SEND X’05’ * RECEIVE X’06’ * REPLY X’07’ TEST COMPLETION X’08’ * REJECT X’09’ PURGE X’0A’ * ACCEPT X’0B’ * CONNECT X’0C’ * DECLARE BUFFER X’0D’ * QUIESCE X’0E’ RESUME X’0F’...
Page 384 The IPARML fields are defined by VM. Examples of some common operations are: IUCV CONNECT to *BLOCKIO IUCV SEND to *BLOCKIO IUCV RECEIVE IUCV REPLY IUCV SEVER IPARML for IUCV CONNECT to *BLOCKIO *----------------------------------------------------------* x’00’ | Path ID |flags 1|IPRCODE| IPMSGLIM *------+------+-------+-------+--------+-----+------+------+ x’08’...
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 | *------+------+-------+-------+------+------+------+-------+ x’18’...
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 *------+------+-------+-------+------+------+------+-------+ x’18’ | *------+------+-------+-------+------+------+------+-------+ x’20’ | IPBFLN2F = reply length *----------------------------------------------------------+ Inputs: IPPATHID...
Page 387 IPARML for IUCV REPLY *----------------------------------------------------------* x’00’ | Path ID |flags 1|IPRCODE| IPMSGID= message id *------+------+-------+-------+--------+-----+------+------+ x’08’ | IPTRGCLS = target class *------+------+-------+-------+------+------+------+-------+ x’10’ | *------+------+-------+-------+------+------+------+-------+ x’18’ | |IPBFADR2= reply buffer addr | *------+------+-------+-------+------+------+------+-------+ x’20’ | IPBFLN2F = reply length *----------------------------------------------------------+ Inputs: IPPATHID = IUCV path id...
Page 388 IPARML for IUCV SEVER *----------------------------------------------------------* x’00’ | Path ID |IPRCODE| *------+------+-------+-------+--------+-----+-----+--- ---+ x’08’ | IPVMID= userid connected to *------+------+-------+-------+------+------+------+-------+ x’10’ | *------+------+-------+-------+------+------+------+-------+ x’18’ | *------+------+-------+-------+------+------+------+-------+ x’20’ | *----------------------------------------------------------+ Inputs: IPPATHID = IUCV path id IPVMID = name of virtual machine connected to Outputs: IPRCODE = IUCV return code...
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: Iucv Interrupt Buffer
no control buffer exists 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.
Page 391 IPARML for Pending Connection Interrupt *----------------------------------------------------------* x’00’ | IPPATHID | Flag 1| IPMSGLIM | xx *------+------+-------+-------+--------+-----+-----+--- ---+ x’08’ | IPVMID= userid wishing to establish the connection *------+------+-------+-------+------+------+------+-------+ x’10’ | IPUSER *------+------+-------+-------+------+------+------+-------+ x’18’ | IPUSER *------+------+-------+-------+------+------+------+-------+ x’20’ | *----------------------------------------------------------+ where: IPPATHID = IUCV pathid Flag 1 = IPFLAGS1...
Page 392 IPARML for Connection Complete Interrupt *----------------------------------------------------------* x’00’ | IPPATHID | Flag 1| IPMSGLIM | xx *------+------+-------+-------+------+-------+-----+--- ---+ x’08’ | *------+------+-------+-------+------+------+------+-------+ x’10’ | IPUSER *------+------+-------+-------+------+------+------+-------+ x’18’ | IPUSER *------+------+-------+-------+------+------+------+-------+ x’20’ | *----------------------------------------------------------+ where: IPPATHID = IUCV pathid Flag 1 = IPFLAGS1 = privilege flags IPMSGLIM = max.
Page 393 IPARML for Path Severed/REsumed/Quiesced Interrupt *----------------------------------------------------------* x’00’ | IPPATHID | IPTYPE| *------+------+-------+-------+------+------+--- --+--- ---+ x’08’ | *------+------+-------+-------+------+------+------+-------+ x’10’ | IPUSER *------+------+-------+-------+------+------+------+-------+ x’18’ | IPUSER *------+------+-------+-------+------+------+------+-------+ x’20’ | *----------------------------------------------------------+ Inputs: IPPATHID = IUCV path id IPTYPE = 03=severed, 04=quiesced, 05=resumed IPUSER = 16 bytes of application-dependent data.
Page 394 IPARML for Incoming Message Interrupt *----------------------------------------------------------* x’00’ | IPPATHID | Flag 1| 08/09 | IPMSGID= message id *------+------+-------+-------+------+------+--- --+--- ---+ x’08’ | IPTRBCLS= target class *------+------+-------+-------+------+------+------+-------+ x’10’ | IPBFLN1F= message length *------+------+-------+-------+------+------+------+-------+ x’18’ | *------+------+-------+-------+------+------+------+-------+ x’20’ | IPBFLN2F= reply length *----------------------------------------------------------+ where: IPPATHID...
Page 395 IPARML for Message Complete Interrupt *----------------------------------------------------------* x’00’ | IPPATHID | Flag 1| 06/07 | IPMSGID= message id *------+------+-------+-------+------+------+--- --+--- ---+ x’08’ | IPAUDIT *------+------+-------+-------+------+------+------+-------+ x’10’ | *------+------+-------+-------+------+------+------+-------+ x’18’ | *------+------+-------+-------+------+------+------+-------+ x’20’ | IPBFLN2F= residual length *----------------------------------------------------------+ where: IPPATHID = IUCV pathid Flag 1 = IPFLAGS1 = privilege flags...
Page 396: Diagnostic Capabilities
These diagnostic tools can be helpful to you in diagnosing software problems and helpful when discussing any problems with StorageTek Support Services. SCP Trace Facility The SCP Trace Facility provides a low level history of the recent past. The SCP emulates many of the functions of the MVS GTF.
Page 397: Scp External Trace Facility
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.
Page 398: Scp Trace Formatter Utility
SCP Trace Formatter Utility SLUETRAC events EXEC spoolid OUT= infile outfile infile: infn TRACE inft infm outfile: ACSTRACE outfn LISTING outft outfm EXEC optionally specified to invoke the EXEC. SLUETRAC initiates the SLUETRAC EXEC. 368 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
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. events indicates which events are to be traced: - all of the following events (this is the default)
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., 6/30/04 - 312579601...
Page 401: Table 20. Svc Functions
Table 20. SVC Functions Refer to Table Decimal Function Note EXCP WAIT POST EXIT LIST GETMAIN LINK LOAD DELETE GET/FREEMAIN R TIME SYNCH ABEND ERROR EXCP PURGE I/O OPEN CLOSE DEVTYPE OBTAIN IOHALT QEDIT/MGCR WTO/WTOR EXTRACT IDENTIFY ATTACH CIRB CHAP TTIMER STIMER SDUMP...
Page 402: Scp Gtrace Emulation
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.
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.
Page 404: Hsc Internal Trace Table
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.
Page 405: Figure 23. Hsc Internal Trace Table Example
00B613F0. C2E3D9C3 00006C10 F1300000 00000000 | BTRC..%.1..| 00B61400. 6550D3D9 E2D740BC 00DA0000 009DB6B8 | .&LRSP ..| 00B61410. 00000000 4DF1F8F6 F0F1F1F5 F7F2D2F1 | ..(186011572K1 | 00B61420. F1F1F8F1 F1F0F0F3 40404040 4040F340 | 11811003 00B61430. 40404040 40F34040 40404040 F3404040 | 00B61440. 404040F3 40404040 4040F340 40404040 |...
Page 406: Hsc Trace Command
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.
Page 407: Diagnostic Commands
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’’...
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.
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.
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.
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. NAME INITIAL (ACTIVE)
Page 413: Hsc Diagnostic Commands
• 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. LIst Command The LIst command is used to display an HSC data structure.
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.
Page 415: Cds Recovery Capabilities
CDS Recovery Capabilities Capabilities to recover the CDS from certain hardware and software failures are inherent in the HSC. CDS recovery capabilities include: • dynamic recovery of the control data set • control data set error diagnostics • initializing/running on one copy of the control data set •...
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.
Page 417: Figure 24. Control Data Set Recovery Scheme
Figure 24 illustrates the built-in recovery scheme for the control data sets. AT FAILURE OF INITIAL AT FAILURE OF THE PRIMARY CONTROL CONTROL SECONDARY CONTROL DATA SET, HSC DATA SET DATA SET, THE HSC OPERATES OPERATES ON CONFIGURATION ON THE STANDBY DATA SET SECONDARY DATA SET PROVIDED THAT STANDBY STANDBY DATA SET...
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.
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 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. Information Required for StorageTek Diagnosis To aid diagnosis, collect the following information: •...
Page 421: Dump Processing
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 •...
Page 422: What To Do When A Dump Occurs
3. Load the CONSLOG and dump onto MAINTSTK’s IPCS disk. 4. Call StorageTek Software Support. 5. Move requested material to tape and ship to StorageTek. Move Dump and CONSLOG to Dump Processing Machine’s Virtual Reader If no DUMPOPTS command had been issued, then the dump will be found in STKACS’s virtual reader.
Page 423 QUERY CPLEVEL Move Problem Materials to Tape StorageTek Software Support may require that the problem materials be copied to tape and shipped to them for detailed analysis. Copy the materials to tape using the VMFPLC2 CMS command. Details on using VMFPLC2 can be found in the IBM Service Guide for VM/SP and VM/SP HPO, Release 6, or the IBM Installation and Service manual for VM/XA SP, VM/ESA, and VM/ESA 370.
Page 424: Dump Analysis Using Sluipcs
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. The SLUIPCS CMS command supplied by StorageTek utilizes the dump processing facilities native to the VM release on which it executes.
Page 425 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. View-Able Scp Data Structures
Table 25. VIEW-able SCP Data Structures Data Structures ATTPARM *CCVT CHANCELL CMDPLIST CPIB CSWORD CUCELL *CVT DECB DEVBLOK ERREC EXDAT EXTDESC FREANC GRFA IEZCOM IHADCB IOBLOK JBLOK JFCB MCBLOK MSGEL *MTT NEWTQE *NUCON ORIGID PSWORD QSGET RQBLOK RTM1PARM RTM1WA RTM2WA SFCB SMFHDR *STORMAN...
Page 427: Table 26. View-Able Hsc Data Structures
Table 26. VIEW-able HSC Data Structures IHAASCB IHAPSA IKJTCB ILLT ITCA JCVT JPIAL JPIB JPMESG LASP LCCD LCCW LCVT LDBK LEPL LHRQ LIQE LITC LLG1 LLG2 LLG3 LLG4 LLSB LMDT LPVL LPVS LRPL LRSE LRSP LSLM LSSE LSTB LSWT LTAB LTCB LTEB LURB...
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.
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.
Page 430: Major Scp Data Relationships
SLUIPCS PRINT Options The options listed in the following table are supported for SLK-type dumps. Table 27. SLLUIPCS Print Options Option Function COMM Print console and WTO buffers Print formatted ENQ/DEQ blocks Print formatted I/O supervisor blocks MAIN Print registers, PSW, and ALL of dumped storage SLKM Print SCP-managed storage SLKP...
Page 431: Figure 25. Command, Message And Trace Processing
Command, Message, Trace Processing NUCON X’10’: VECTPTR CCVT COMANC MSGEL CCVWTOQ CMDPLIST CCVCMDQ TRCTAB MTTCURR INTERNAL TRACE TABLE MTTFIRST MTTLAST CURRENT X’A60’: INTERRUPT DATA SAVE AREA C29330 Figure 25. Command, Message and Trace Processing Chapter 5. Problem Determination, Diagnostics, and Recovery 401 1st ed., 6/30/04 - 312579601...
Page 432: Diagnostic Techniques
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.
Page 433: Figure 26. Scp Task/Job Data Relationship
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., 6/30/04 - 312579601...
Page 434: Figure 27. Subsystem Data Relationships
NUCON VECTPTR JESCT CVTJESCT JESSSCT SSCT SSCTSCTA SSVT SSCTSSVT SSCT SSCTSCTA SSVT SSCTSSVT SSCTSUSE C29332 Figure 27. Subsystem Data Relationships 404 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 435: Common Dump Analysis Tasks
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.
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’...
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*). Find the LCT, LST, HST First, find the LVT (see instructions above) VIEW LCT LVTLCT VIEW LST LVTLST...
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...
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 •...
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.
Page 441: Chapter 6. Performance Considerations
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.
Page 442: How Systems Programmers Control Library Performance
The data in the report can be easily analyzed to produce performance criteria for your installation. • using the StorageTek Performance Measurement and Predictive Maintenance System (PM2) to collect performance information. • using Expert Library Manager (ExLM) to monitor performance and to balance workload.
Page 443: Using The Performance Measurement And Predictive Maintenance System (Pm2)
Using the Performance Measurement and Predictive Maintenance System (PM2) The Performance Measurement and Predictive Maintenance System generates performance and error reports on various StorageTek equipment, including the library. There are two categories of reports that provide information about library operation: •...
Page 444: Redistribute Scratch Volumes In The Library
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: Use Smf Records To Collect Performance Data
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.
Page 446 Table 28. Performance Parameters Controlled by PARMLIB Control Statements Performance Parameter Control Statement Operator Command Journal Definition JRNDEF Journal (specify FULL=Abend or FULL=Continue) Journals JRNDEF Journal (specify FULL=Abend or FULL=Continue) Mount Processing MNTD MNTD General Purpose Options OPTion OPTion Scratch Subpool SCRPool Warn (specify SUBpool option)
Page 447: Define High Dispatching Priority For The Hsc
• the CDS. The high-performance telecommunications method is through VTAM. This method is recommended by StorageTek. Host-to-host communications through the control data set should be used only as a backup facility. You should implement the highest level of host-to-host communications available.
Page 448: Functioning Of Host-To-Host Communications
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
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 •...
Page 450: Excessive Use Of View Command Affects Performance
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., 6/30/04 - 312579601...
Page 452: Loading Cartridges Into The Library
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
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.
Page 454: Reduce Operator Intervention
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.
Page 455: Acsprop Exec
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: Syntax
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.
Page 457: Use Performance Log Reblocker To Format Data
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 •...
Page 458: Use Lsms As Scratch Loaders In A Mixed Acs
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.
Page 459: Appendix A. Macros, Control Statements, Utilities, And Commands Syntax Reference
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.
Page 460: Flow Lines
Flow Lines Syntax diagrams consist of horizontal and vertical lines and the text of a command, control statement, macro, or utility. COMMAND/MACRO/UTILITY Item1 Item2 Item3 Diagrams are read left to right and top to bottom. Arrows indicate flow and direction. •...
Page 461: Single Optional Choice
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.
Page 462: Syntax Continuation (Fragments)
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 variable3 variable2 variable4 variable5 variable7 Item2( variable6 variable8 432 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 463: Library Identification
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.
Page 464: How To Specify A Capid
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.
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
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.
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.
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.
Page 469: Control Statement Syntax Conventions
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.
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
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 Name Type MEDia RECtech MODel Description Parameters Display Drive Command DETail Displays the transports that are capable of the specified MEDia, RECtech, or...
Page 472 Table 29. MEDia, RECtech, and MODel Cross-reference (Continued) Related Name Type MEDia RECtech MODel Description Parameters Mount Command SUBpool, Mounts scratches that match SCRTCH, the MEDia. If a SUBpool is PRIVAT supplied, a cartridge that matches MEDia within the subpool is mounted. TAPEREQ Control Various Job...
Page 473 Table 29. MEDia, RECtech, and MODel Cross-reference (Continued) Related Name Type MEDia RECtech MODel Description Parameters VOLATTR Control The MEDia of a given Statement volume must be defined here and the desired RECtech to be used on this volume may also be expressed.
Page 474: Libgen Macros
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., 6/30/04 - 312579601...
Page 475: Sliacs Macro
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., 6/30/04 - 312579601...
Page 476: Slilibry Macro
SLILIBRY macro SLILIBRY HOSTID=(host-id0,host-id1,...,host-id15) ,ACSLIST=acslist Optional Parameters Optional Parameters: ,CLNPRFX= prefix ,SMF= libtype ,NNLBDRV=(esoteric0,...,esoteric15) NOSCRTCH ,DELDISP= SCRTCH STKALSQN ,MAJNAME= qname ,COMPRFX= commandchar ,SCRLABL= ,EJCTPAS=password 446 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 477: Slilsm Macro
SLILSM macro lsm0 SLILSM 4410 TYPE= 9310 9360 9740 8500 DRIVE=(drvpanel0,...,drvpanel3) ,DRVELST=(drvelst0,...,drvelst3) ,PASTHRU=((ptppane10, ),..., (ptppane18, )) ,ADJACNT=(lsm1,...,lsm4) ,WINDOW=(wndpanel0,...,wndpanel3) ,DOOR= ECAP 8500-1 8500-2 SLIRCVRY macro SLIRCVRY LABEL BOTH TCHIQE= NONE SHADOW JOURNAL STANDBY SLISTATN macro station0 SLISTATN ADDRESS=(addr0,...addr15) Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 447 1st ed., 6/30/04 - 312579601...
Page 478: Hsc Control Statements
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.name )
Page 479: Lkeydef Command And Control Statement
LKEYDEF command and control statement LKEYDEF DATASET(dataset.name) DSN(dataset.name) VOLume(volser) UNIT(unitname) HOSTID(host-id) LKEYINFO control statement LKEYINFO PRODuct(product_identifier) CUSTomer('customer_name') SITEno(nnnnnnn) EXPRdate(yyyyddd) 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.name) VOLume(volser) UNIT(unitname) HOSTID( host-id Appendix A.
Page 480: Option Control Statement
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( ,HOSTID( host-id...
Page 481: Scratch Subpool Definition (Scrpdef) Command And Control Statement
Scratch Subpool Definition (SCRPDEF) command and control statement SCRPDEF DATASET(dataset.name) DSN(dataset.name) VOLume(volser) UNIT(unitname) HOSTID( host-id Tape Request (TAPEREQ) control statement TAPEREQ JOBname( jobname STEPname( stepname program-name dataset-name PROGram( DATASET( PGMname(program-name) DSN(dataset-name) DDName(DD-name) RETPD( ,retention-period EXPDT( ,expiration-date VOLType( Specific Nonspec Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 451 1st ed., 6/30/04 - 312579601...
Page 482: Tape Request (Tapereq) Control Statement (Continued)
Tape Request (TAPEREQ) control statement (continued) MEDia( LONGItud RECtech( LONGItud 18track Standard 36track 36Atrack MEDIA1 36Btrack 36Ctrack HELical 3480 STK1R ECART STK1R34 STK1R35 ECCST STK1RA ETAPE STK1RA34 STK1RA35 Long STK1RB MEDIA2 STK1RB34 3490E STK1RB35 ZCART STK1RAB STK1RAB4 STK1RAB5 HELical STK1RC STK1RC34 DD3A STK1RC35...
Page 483: Tape Request Definition (Treqdef) Command/Control Statement
Tape Request Definition (TREQDEF) command/control statement TREQDEF DATASET( dataset.name ) DSN( dataset.name ) VOLume( volser ) UNIT( unitname ) HOSTID( host-id Unit Attribute (UNITATTR) control statement UNITATTR ADDRess( unit-address unit-address-range MODel( 4480 4490 9490 unit-address-list 9490EE 9840 984035 T9840B T9840B35 T9840C T9840C35 T9940A...
Page 484: Unit Attribute Definition (Unitdef) Command/Control Statement
Unit Attribute Definition (UNITDEF) command/control statement UNITDEF DATASET( dataset.name ) DSN( dataset.name ) VOLume( volser ) UNIT( unitname ) HOSTID( host-id Volume Attribute (VOLATTR) control statement VOLATTR SERial( volser vol-range MEDia( Standard vol-list MEDIA1 3480 ECART ECCST ETAPE Long MEDIA2 3490E ZCART DD3A...
Page 485: Volume Attribute (Volattr) Control Statement (Continued)
Volume Attribute (VOLATTR) control statement (continued) RECtech( LONGItud MAXclean(use-limit) 18track 36track 36Atrack 36Btrack 36Ctrack HELical 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., 6/30/04 - 312579601...
Page 486: Volume Attribute Definition (Voldef) Command/Control Statement
Volume Attribute Definition (VOLDEF) command/control statement VOLDEF DATASET(dataset.name) DSN(dataset.name) VOLume(volser) UNIT(unitname) HOSTID( host-id 456 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 487: Utilities
Utilities Refer to Chapter 4, “Utility Functions” on page 169 for more information on utility syntax and parameters. ACTIvities Report utility ACTIvities Optional Parameters Optional Parameters: TODAY 00:00:00 BEGIN( begin-date begin-time TODAY 23:59:59 END( end-date end-time AUDIt utility AUDIt ACS(acs-id) Optional Parameters APPLy Optional Parameters:...
Page 488: Backup Utility
BACKup utility BACKup CDS( Copy Primary OPTion( Analyze Secondary Restart STandby Database Decompile (LIBGEN) utility LIBGEN Directory Rebuild (DIRBLD) utility DIRBLD EJECt utility EJECt Eject Method 1 Eject Method 2 CAP( cap-list Eject Method 1: VOLser( vol-list Eject Method 2: SCRTCH SUBpool(subpool-name) VOLCNT(count)
Page 489: Eject Utility (Continued)
EJECt utility (continued) Eject Method 2 (continued): MEDia( Standard RECtech( 18track 36Atrack 36Btrack MEDIA1 36Ctrack STK1R 3480 STK1R34 ECART STK1R35 STK1RA ECCST STK1RA34 ETAPE STK1RA35 Long STK1RB MEDIA2 STK1RB34 3490E STK1RB35 ZCART STK1RAB STK1RAB4 DD3A STK1RAB5 STK1RC DD3B STK1RC34 DD3C STK1RC35 STK1 STK2P...
Page 490: Journal Offload Utility
Journal OFFLoad utility OFFLoad MOVe utility MOVe Parameters Parameters: Flsm( lsm-id ) Panel( panel-list ) Row( row-list ) Column( column-list ) Volume( vol-list ) TLsm( lsm-list ) TPanel( panel ) Reconfiguration utility START reconfig-procname REPLace utility REPLaceall VOLser( vol-list 460 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 491: Restore Utility
RESTore utility RESTore APPly( GENerate( Only Short SCRAtch utility SCRAtch VOLser( vol-list Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 461 1st ed., 6/30/04 - 312579601...
Page 492: Scratch Redistribution (Scredist) Utility
Scratch Redistribution (SCREdist) utility SCREdist ACS(acs-id) SUBpool(subpool-name) LSM( lsm-list MEDia( LONGItud RECtech( LONGItud BALtol(tolerance-value) Standard 18track 36track MEDIA1 36Atrack 36Btrack 36Ctrack 3480 HELical ECART STK1R ECCST STK1R34 ETAPE STK1R35 Long STK1RA MEDIA2 STK1RA34 3490E STK1RA35 ZCART STK1RB STK1RB34 HELical STK1RB35 STK1RAB DD3A STK1RAB4...
Page 493: Set Utility
SET utility Options Options: ACSDRV(esoteric) ,FORACS(acs-id) ,FORHOST(host-id) CLNPRFX(prefix) COMPRFX(cmdhex) DELDISP( SCRTCH NOSCRTCH EJCTPAS( newpswd ,OLDPASS(oldpswd) FREEZE( ON ,FORLSMID(lsm-id) ,FORPANEL(panel) HOSTID (newhost),FORHOST(oldhost) HSCLEVEL(OFF),FORHOST(host-id) MAJNAME(qname) NEWHOST(newhost) ,LIKEHOST(model-host) NNLBDRV( esoteric ,FORHOST(host-id) SCRLABL( Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 463 1st ed., 6/30/04 - 312579601...
Page 494: Unscratch Utility
SET utility (continued) 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 UNSCratch utility UNSCratch VOLser( vol-list Unselect utility UNSElect VOLser( volser ) ,FORCE 464 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 495: Volume Report (Volrpt) Utility
Volume Report (VOLRpt) utility VOLRpt ASCend ACS( acs-id ) SORT( LSM( lsm-list DEScend VOLser ( volser vol-range NOSORT vol-list VOLume ( volser vol-range vol-list EXCLude( INCLude( NONSCR NONSCR NONERR NONERR NONSEL NONSEL READable READable UNREADable UNREADable MEDEQUAL MEDEQUAL NONMEDEQ NONMEDEQ NOEXTernal NOEXTernal VOLIST...
Page 496: Operator Commands
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 AUTO cap-range MANual cap-list CDs Enable/Disable command CDs Enable DSn(dsn) NEWVol(volser),NEWUnit(unitname) NEWLoc...
Page 497: Communications Path (Commpath) Command And Control Statement
Communications Path (COMMPath) command and control statement COMMPath HOSTid(host-id) METHod( LMUpath( acs-id VTAMpath(name) LMU,acs-id acs-range VTAM 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 devaddr volser host-id Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 467 1st ed., 6/30/04 - 312579601...
Page 498: Display Command
Display command Display Acs Display acs-id acs-range acs-list Display ALl Display Display ALLOC Display ALLOC Display Cap (all CAPs) Display acs-id lsm-id cap-id Display CDS Display 468 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 499 Display Cmd Display command-name COmmand Display COMMPath Display COMMPath HOSTid( host-id host-list Display DRives Library ACtive Display DRives ACS(acs-id) Idle LSM(lsm-id) DETail Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 469 1st ed., 6/30/04 - 312579601...
Page 500 Display Drives (continued) MEDia( LONGItud RECtech( LONGItud 18track Standard 36track 36Atrack MEDIA1 36Btrack 36Ctrack HELical 3480 STK1R ECART STK1R34 STK1R35 ECCST STK1RA STK1RA34 ETAPE STK1RA35 Long STK1RB MEDIA2 STK1RB34 3490E STK1RB35 STK1RAB ZCART STK1RAB4 STK1RAB5 HELical STK1RC STK1RC34 STK1RC35 DD3A STK2P DD3B STK2P34...
Page 501 Display Exceptions Display EXceptns Display LKEYDEF Display LKEYDEF Display LMUPDEF Display LMUPDEF Display LSM Display lsm-id lsm-range lsm-list Display Message Display Message msgnum Display MNTD Display MNTD Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 471 1st ed., 6/30/04 - 312579601...
Page 502 Display MONitor Display MONitor ,PGMI name Display OPTion Display OPTion Display Requests Display Requests 472 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 503 Display SCRatch Display SCRatch acs-id SUBpool(subpool-name) DETail lsm-id MEDia( LONGItud RECtech( LONGItud Standard 18track 36track MEDIA1 36Atrack 36Btrack 36Ctrack 3480 HELical ECART STK1R ECCST STK1R34 ETAPE STK1R35 Long STK1RA MEDIA2 STK1RA34 3490E STK1RA35 ZCART STK1RB STK1RB34 HELical STK1RB35 STK1RAB DD3A STK1RAB4 DD3B STK1RAB5...
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., 6/30/04 - 312579601...
Page 505 Display THReshld Display THReshld acs-id SUBpool(subpool-name) lsm-id DETail MEDia( LONGItud RECtech( LONGItud Standard 18track 36track 36Atrack MEDIA1 36Btrack 36Ctrack HELical 3480 ECART STK1R STK1R34 ECCST STK1R35 ETAPE STK1RA Long STK1RA34 MEDIA2 STK1RA35 3490E STK1RB ZCART STK1RB34 STK1RB35 HELical STK1RAB STK1RAB4 DD3A STK1RAB5 DD3B...
Page 506: Drain Cap Command
Display UNITDEF Display UNITDEF Display VOLDEF Display VOLDEF Display Volume Display Volser volser vol-range Volume DETail vol-list DRAin CAP command ENter DRAin cap-id EJect cap-list EJect command EJect Option 1 Option 2 Option 1: volser vol-range acs-id lsm-id cap-id vol-list cap-list 476 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 507 Eject Command (continued) Option 2: SCRTCH acs-id SUBpool(subpool-name) VOLCNT(count lsm-id cap-id cap-list RECtech( MEDia( LONGItud LONGItud Standard 18track 36track MEDIA1 36Atrack 36Btrack 36Ctrack 3480 HELical ECART STK1R ECCST STK1R34 ETAPE STK1R35 Long STK1RA MEDIA2 STK1RA34 3490E STK1RA35 ZCART STK1RB STK1RB34 HELical STK1RB35 STK1RAB...
Page 508: Enter Command
ENter command ENter acs-id SCRatch cap-id lsm-id Journal command Journal Full( ABEND Continue MODify command MODify cap-id ONline lsm-id OFFline lsm-id ONline lsm-range OFFline FORCE lsm-list MONITOR command MONITOR PGMI name 478 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 509: Mount Command
Mount command Mount volser devaddr host-id Readonly SCRTCH devaddr PRIVAT host-id SUBpool(subpool-name) LONGItud MEDia( Standard MEDIA1 3480 ECART ECCST ETAPE Long MEDIA2 3490E ZCART HELical DD3A DD3B DD3C STK1 STK1R STK2 STK2P Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 479 1st ed., 6/30/04 - 312579601...
Page 510: Mount/Dismount Options (Mntd) Command And Control Statement
Mount/Dismount Options (MNTD) command and control statement MNTD AUtocln( HOSTID( host-id ) Dismount( Auto Manual EJctauto( ACS( acs-id ) Float( ACS( acsid ) MAXclean( count ) MMount( Delete Reply MOuntmsg( Roll Noroll PASSTHRU( count ) Scratch( Manual Auto SCRDISM( CURRENT ARCHIVE Unload( Noscr...
Page 511: Move Command
MOVe command MOVe Flsm(lsm-id) Panel(pp) Row(row-list) Column(cc) Row(rr) Column(column-list) Volume( volser vol-range vol-list TLsm( lsm-id TPanel(pp) lsm-list Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 481 1st ed., 6/30/04 - 312579601...
Page 512: Option Command And Control Statement
OPTion command and control statement OPTion Dialog( Both HOSTID(host-id) Console SHow DISCmsg( SUppress ACS(acs-id) EJLimit(count) ENTdup( Manual Auto LOGging( Standard Extended Output( Upper Mixed Repath( 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...
Page 513: Senter Command
SENter command SENter cap-id SRVlev (Service Level) command SRVlev BASE FULL Stop Monitoring (STOPMN) command STOPMN PGMI name SWitch command SWitch Acs acs-id Note: (1) ACS acs-id is optional in a single-ACS environment; it is required in a multiple-ACS environment. Appendix A.
Page 514: Trace Command
TRace command TRace comp-name comp-list comp-name comp-list TRACELKP command TRACELKP table-name table-list table-name Vary Station command Vary acs-id ONline acs-range OFFline FORCE acs-list STation dev-id dev-range dev-list 484 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 515: View Command
VIew command CAPID(00:00:00) Row(00) Column(00) VIew CAPID(cap-id) Row(rr) Column(cc) Lsm(lsm-id) Lsm(00:00) Panel(00) Row(00) Column(00) CEll Lsm(lsm-id) Panel(pp) Row(rr) Column(cc) DRive Address(xxx) Host(host-id) Lsm(00:00) Column(00) PLaygrnd Lsm(lsm-id) Column(cc) Lsm(00:00) Column(0) Lsm(lsm-id) Xlsm(ll) Column(c) Time(ttt) Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 485 1st ed., 6/30/04 - 312579601...
Page 516: Warn Command
Warn command Warn SCRatch acs-id THReshld(threshold-value) lsm-id SUBpool(subpool-name) MEDia( LONGItud RECtech( LONGItud Standard 18track 36Atrack MEDIA1 36Btrack 36Ctrack HELical 3480 ECART STK1R STK1R34 STK1R35 ECCST ETAPE STK1RA Long STK1RA34 MEDIA2 STK1RA35 3490E STK1RB ZCART STK1RB34 STK1RB35 STK1RAB DD3A STK1RAB4 DD3B STK1RAB5 DD3C STK1RC...
Page 517: Hsc Diagnostic Commands
HSC Diagnostic Commands LIst command LIst data-structure address size TRace command TRace comp-name comp-list comp-name comp-list Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 487 1st ed., 6/30/04 - 312579601...
Page 518: Scp Operator Commands
SCP Operator Commands * (comment) Statement comments AUTHorize Command AUTHorize userid CMDS user-list MSGS route-codes NETVM NONE CANCEL command CANCEL taskid DUMP CP Command cmdparm DEFine Command DEFine CHAN chnum chtype chcu cutype devtype DUMP Command DUMP comment 488 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 519: File Command
FILE Command FILE ddname BLOCKIO vaddr DSN DISK CLEAR vaddr DSN dsn CARD PNCH PRNT CLass class IUCV userid 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 Operator Perflog...
Page 520: Reply Command
Reply Command Reply text 'text' SET Command CONSlog destination CLOSE DUMPOpts REset maxcount (userid (userid MSGtype MSGNOH PERFlog dest. CLOSE subsystem interval SUBTYPE( subtype-list TRACE events dest. CLOSE SELect 490 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 521 destination: Class class userid AT node events: NONE Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 491 1st ed., 6/30/04 - 312579601...
Page 522: Slk Command
SLK Command scp-command STArt Command progname STArt progname taskid prio parms JOBRDR 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., 6/30/04 - 312579601...
Page 523: Gcs Component Server Commands
GCS Component Server Commands SLKGCS Command SLKGCS START DISPLAY STOP CANCEL Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 493 1st ed., 6/30/04 - 312579601...
Page 524: Cms Operator Commands
CMS Operator Commands ACS EXEC EXEC command INIT NOJOBs BREAK breakstr PARM=parmstr SUBMIT jobfname SLKJCL (PARM=parmstr ftype fmode class UTILity utility util-list NOSEND JOBName jobname NOEDIT CMS HELP MENU HELP scp-command =diag-command .hsc-command topic msgnum 494 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 525: Appendix B. Cp Commands And Diagnose Codes
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’’...
Page 526: Iucv
IUCV Communication vehicle for API and communication with Host to Host component. 496 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 527: Appendix C. Record Formats
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 •...
Page 528: Mapping Macros For Smf Records
Table 30 provides a key to the SMF record format tables. Table 30. Key to Record Format Tables Type Length values CONSTANT CHAR CONST BITMAP LENGTH offset AREA length STRUCTURE blank offset CHARACTER length (length of one element) HEXSTRING BITSTRING SIGNED-FWORD SIGNED-HWORD SHORT-FLOAT...
Page 529: Smf Records
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...
Page 530: Smf Record Formats
SMF Record Formats SLSDVAR Table 32. SLSDVAR Record Format 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. HEXSTRING SLSDVAR Volume Attribute Record (28) LENGTH VARL...
Page 531: Slssfhdr
SLSSFHDR Table 33. SLSSFHDR Record Format 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. SYMBOLICS: &TYPE - USED TO SELECT A VALID SMF RECORD TYPE 1 - BLOS STATISTICS...
Page 532 Table 33. SLSSFHDR Record Format (Continued) Type Length Label Description (12) CHARACTER OSHDSSID SUBSYSTEM ID (16) SIGNED-HWORD 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) Type Length Label Description (1B) CONST OSHDVT27 (VTCS) VTV SCRATCH Event (1C) CONST OSHDVT28 (VTCS) REPLICATE VTV->CLUSTERED VTSS Rqst (1C) CONST OSHDMAXS MAXIMUM RECORD SUBTYPE VALUE (18) LENGTH OSHDL LENGTH OF FIXED PORTION OF OSHDR (18) OFFSET SLSSTYPE...
Page 534 Cross Reference Offset Name Value OSHDBLOS OSHDDATE 000004 OSHDDESC 000002 OSHDEJCT OSHDENTR OSHDFLAG 000001 OSHDL OSHDLRST OSHDMAXS OSHDMLSM OSHDRCTY 000001 OSHDRC07 OSHDRECL 000002 OSHDRSTY 000002 OSHDSID 000004 OSHDSSID 000004 OSHDSTV OSHDTIME 000004 OSHDVIEW OSHDVSTA OSHDVT09 OSHDVT10 OSHDVT11 OSHDVT12 OSHDVT13 OSHDVT14 OSHDVT15 OSHDVT16 OSHDVT17...
Page 535 Offset Name Value OSHDVT20 OSHDVT21 OSHDVT22 OSHDVT23 OSHDVT24 OSHDVT25 OSHDVT26 OSHDVT27 OSHDVT28 SLSSTYPE Appendix C. Record Formats 505 1st ed., 6/30/04 - 312579601...
Page 536: Slssblos
SLSSBLOS Table 34. SLSSBLOS Record Format 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.
Page 537 Table 34. SLSSBLOS Record Format (Continued) Type Length Label Description (10) SIGNED-FWORD BLOSDTIM DIFFERENT LSM ELAPSED TIME (14) SIGNED-FWORD BLOSPTRU PASSTHRU COUNT (16) LENGTH BLOSVL LENGTH OF DATA SECTION (14) LENGTH BLOSVL1 LENGTH OF COUNTER SECTION (18) LENGTH BLOSL BLOS LENGTH Cross Reference Offset Name...
Page 538: Slsscapj
SLSSCAPJ Table 35. SLSSCAPJ Record Format Type 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. SYMBOLICS: &DSECT - DSECT OR CONTINUATION OF DATA AREA YES - PRODUCE A DSECT LISTING NO - NO DSECT AREA...
Page 539: Slsscapn
SLSSCAPN Table 36. SLSSCAPN Record Format 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. YES - PRODUCE A DSECT LISTING NO - NO DSECT AREA...
Page 540: Slssvsta
SLSSVSTA Table 37. SLSSVSTA Record Format 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 AREA SLSSVSTA...
Page 541 Cross Reference Offset Name Value SLSSVSTA 000002 SVSTACID 000001 SVSTACS SVSTATID 000002 SVSTFLAG 000004 SVSTFLG0 000001 SVSTFOR SVSTL SVSTSTBY SVSTUNID 000002 SVSTVACS SVSTVOF SVSTVON Appendix C. Record Formats 511 1st ed., 6/30/04 - 312579601...
Page 542: Slssmlsm
SLSSMLSM Table 38. SLSSMLSM Record Format 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 AREA SLSSMLSM...
Page 543: Slsslsb
SLSSLSB Table 39. SLSSLSB Record Format 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.
Page 544 Table 39. SLSSLSB Record Format (Continued) Type Length Label Description LSBECON1 AND LSBECON2 HAVE THE FOLLOWING MAPPING: BYTE 0 - RESERVED BYTE 1 - ACSID BYTE 2 - SLAVE LSMID BYTE 3 - RESERVED BYTE 4 - RESERVED BYTE 5 - RESERVED SIGNED-FWORD -RESERVED-(2) *** RESERVED...
Page 545: Slssmf07
SLSSMF07 Table 40. SLSSMF07 Record Format 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.
Page 546 Table 40. SLSSMF07 Record Format (Continued) Type Length Label Description ..1.1 X’05’ SMF07OPR HSC OPERATOR COMMAND INITIATED ..11. X’06’ SMF07TMI VM TMI INTERFACE BITSTRING SMF07FLG FLAG BYTE 1..X’80’ SMF07DSV SMF07DRS CONTAINS A DRIVE DEVICE NUM .1..X’40’ SMF07DTV SMF07DRT CONTAINS A DRIVE DEVICE NUM...
Page 547 Table 40. SLSSMF07 Record Format (Continued) Type Length Label Description (1B) CHARACTER 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)
Page 548 Table 40. SLSSMF07 Record Format (Continued) Type Length Label Description (F1) CHAR CONST SMF07SCE CELL ‘1’ ‘2’ (F2) CHAR CONST SMF07SCP (F3) CHAR CONST SMF07SDR DRIVE ‘3’ (38) HEXSTRING SMF07SAC SOURCE ACS (39) HEXSTRING SMF07SLS SOURCE LSM (3A) HEXSTRING SMF07SPN SOURCE PANEL (3B) HEXSTRING...
Page 549 Table 40. SLSSMF07 Record Format (Continued) Type Length Label Description (58) LENGTH SMF07SL 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.
Page 550 Cross Reference Offset Name Value SLSSMF07 000001 SMF07CNV SMF07CON 000004 SMF07CPO 000004 SMF07DEI 000001 SMF07DNS SMF07DRO 000004 SMF07DRQ 000004 SMF07DRS 000002 SMF07DRT 000002 SMF07DSS SMF07DSV SMF07DTV SMF07DWT 000004 SMF07EDT 000004 SMF07EJT SMF07ETM 000004 SMF07FLG 000001 SMF07HSC SMF07JOB SMF07L SMF07LBL 000001 SMF07LDT 000004 SMF07LMD...
Page 551 Offset Name Value SMF07MVU ‘CVAL’ SMF07MVV ‘CVAL’ SMF07NRD 000004 SMF07NTR SMF07OPR SMF07ORO 000004 SMF07ORQ 000004 SMF07PRF SMF07PRG SMF07PRO 000004 SMF07PRQ 000004 SMF07RQS 000001 SMF07SAC 000001 SMF07SCE ‘CVAL’ SMF07SCO 000001 SMF07SCP ‘CVAL’ SMF07SDR ‘CVAL’ SMF07SDT 000004 SMF07SFI ‘CVAL’ SMF07SFN ‘CVAL’ SMF07SF1 000001 SMF07SL SMF07SLS...
Page 552 Offset Name Value SMF07TDR ‘CVAL’ SMF07TDT 000004 SMF07TDW ‘CVAL’ SMF07TLS 000001 SMF07TMI SMF07TNM 000001 SMF07TPN 000001 SMF07TRO 000001 SMF07TTM 000004 SMF07TYP 000001 SMF07UNK SMF07US1 000008 SMF07US2 000008 SMF07UTL SMF07VMT ‘CVAL’ SMF07VMU ‘CVAL’ SMF07VMV ‘CVAL’ SMF07VOL 000006 522 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 553: Slssmf08
SLSSMF08 Table 41. SLSSMF08 Record Format 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 Offset Name Value SLSSMF08 000001 SMF08ACS 000001 SMF08CAP SMF08CEL SMF08CID 000001 SMF08COL 000001 SMF08CUA 000002 SMF08DRV SMF08HST 000008 SMF08L SMF08LSM 000001 SMF08LSM2 000001 SMF08MAG 000001 SMF08PNL 000001 SMF08PTP SMF08ROW 000001 SMF08RTM 000001 SMF08SLT 000001 SMF08TYP 000001 SMF08VTM 000001 SMF08XPT 000001 524 VM/HSC 6.0 System Programmer’s Guide...
Page 555: Logrec Records
LOGREC Records LOGREC Mapping Macros Table 42. Mapping Macros for LOGREC Records Macro Description SLSSLHDR LOGREC Header Layout SLSSVLG1 LOGREC Volume/Cell Force Unselect Record SLSSBLOG LOGREC Initialization/Termination Record SLSSLLG1 LOGREC LMU Driver Format 1 SLSSLLG2 LOGREC LMU Driver Format 2 SLSSLLG3 LOGREC LMU Driver Format 3 SLSSLLG4...
Page 556: Logrec Record Formats
LOGREC Record Formats SLSSLHDR Table 43. SLSSLHDR Record Format 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) Type Length Label Description (20) OFFSET OLHDERID ERROR ID (20) HEXSTRING OLHDRSDW SDWA (20) CONST SLSSTYPE HSC software error subtype LOGREC data overlays SDWA area. (1B0) HEXSTRING OLHDRARA SDWARA (1B3) HEXSTRING OLHDRRAL SDWAURAL (LENGTH OF VRA) (1B4) HEXSTRING OLHDRVRA...
Page 558 Table 43. SLSSLHDR Record Format (Continued) Type Length Label Description (28C) LENGTH OLHDL LENGTH OF FIXED PORTION OF OLHD 528 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 559 Cross Reference Offset Name Value LTYPAREA 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 OLHDCPID 000008 OLHDDATE 000004 OLHDERF OLHDERID OLHDETIM 000004 OLHDJBID...
Page 560 Offset Name Value OLHDRVRA 000006 OLHDSMS 000001 OLHDSOFT OLHDSTC 000004 OLHDSW2 000001 OLHDTFLG OLHDTIME 000004 OLHDVS2 SLSSTYPE 530 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 561: Slssvlg1
SLSSVLG1 Table 44. SLSSVLG1 Record Format 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 AREA SLSSVLG1...
Page 562 Cross Reference Offset Name Value SLSSVLG1 000002 VLG1HDR 000004 VLG1HOST 000008 VLG1JOBN 000008 VLG1KEY 000001 VLG1L VLG1LEN 000004 VLG1OWNR 000008 VLG1SP 000001 VLG1SUBT 4001 VLG1VOLS 000006 532 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 563: Slssblog
SLSSBLOG Table 45. SLSSBLOG Record Format 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. YES - PRODUCE A DSECT LISTING NO - NO DSECT AREA...
Page 564 Cross Reference Offset Name Value BLOGABND BLOGCNCL BLOGFLAG 000004 BLOGFLG0 000001 BLOGID 5000 BLOGL BLOGRECO BLOGSHTD BLOGSTRT SLSSBLOG 000002 534 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 565: Slssllg1
SLSSLLG1 Table 46. SLSSLLG1 Record Format Type Length Label Description SLSSLLG1 - LMU DRIVER LOGREC RECORD FORMAT ONE FUNCTION: MAPS LOGREC RECORD CREATED WHEN AN INVALID RESPONSE IS RECEIVED FROM THE LMU AREA SLSSLLG1 LMU DRIVER LOGREC FORMAT 25857 (6501) CONST LLG1SUBT SUBTYPE X’6501’...
Page 566 Table 46. SLSSLLG1 Record Format (Continued) Type Length Label Description (01) CONST LLG1NUNR UNRECOGNIZABLE TRANSMISSION (02) CONST LLG1NSOB NO START OF BLOCK CHARACTER (03) CONST LLG1NEOB NO END OF BLOCK CHARACTER (04) CONST LLG1NSOT NO START OF TRANSACTION CHARACTER (05) CONST LLG1NEOT NO END OF TRANSACTION...
Page 567 Table 46. SLSSLLG1 Record Format (Continued) Type Length Label Description .1..X’40’ LLG1STTC STATION IS A NETWORK IP ADDRESS FOR TCP/IP HOSTNAME ADDRESS: (66) CHARACTER LLG1SHNM STATION NETWORK HOST NAME FOR TCP/IP NETWORK ADDRESS: (7E) HEXSTRING LLG1STCP STATION NETWORK IP ADDRESS (82) HEXSTRING -RESERVED-...
Page 568 Cross Reference Offset Name Value LLG1ACKE LLG1ACS 000001 LLG1BBLK LLG1DBKE LLG1ECD 000001 LLG1ERSP LLG1ERTP LLG1HDFL 000001 LLG1HDR 000004 LLG1ILGL LLG1INVB LLG1INVR LLG1ITYP LLG1KEY 000001 LLG1L LLG1LEN 000004 LLG1LMLV 000002 LLG1NCJI LLG1NEOB LLG1NEOT LLG1NHNL LLG1NING LLG1NLRQ LLG1NNUM LLG1NSHP LLG1NSOB LLG1NSOT LLG1NTCT LLG1NTNM LLG1NUNR LLG1NWHI...
Page 569 Offset Name Value LLG1NWSN LLG1RCDE 000001 LLG1RNTN LLG1RQST 000044 LLG1RSPN 000032 LLG1SHNM 000024 LLG1SNOB LLG1SP 000001 LLG1STCP 000004 LLG1STHN LLG1STN 000002 LLG1STTC LLG1STYP 000001 LLG1SUBT 6501 LLG1SWAT LLG1UNKB SLSSLLG1 000002 Appendix C. Record Formats 539 1st ed., 6/30/04 - 312579601...
Page 570: Slssllg2
SLSSLLG2 Table 47. SLSSLLG2 Record Format 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. YES - PRODUCE A DSECT LISTING NO - NO DSECT AREA...
Page 571 Table 47. SLSSLLG2 Record Format (Continued) Type Length Label Description FOR TCP/IP NETWORK ADDRESS: (AA) HEXSTRING LLG2STCP STATION NETWORK IP ADDRESS (AE) HEXSTRING -RESERVED- RESERVED FOR FUTURE USE (C8) LENGTH LLG2L Cross Reference Offset Name Value LLG2ACS 000001 LLG2BLNN LLG2DBKE LLG2ECD 000001 LLG2HDR...
Page 572: Slssllg3
SLSSLLG3 Table 48. SLSSLLG3 Record Format 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. YES - PRODUCE A DSECT LISTING NO - NO DSECT AREA SLSSLLG3...
Page 573: Slssllg4
SLSSLLG4 Table 49. SLSSLLG4 Record Format 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. YES - PRODUCE A DSECT LISTING NO - NO DSECT AREA SLSSLLG4...
Page 574 Cross Reference Offset Name Value LLG4COND 000001 LLG4DEVC 000002 LLG4FSC 000004 LLG4HDR 000004 LLG4KEY 000001 LLG4L LLG4LEN 000004 LLG4SP 000001 LLG4SUBT 6504 SLSSLLG4 000002 544 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 575: Slssllg5
SLSSLLG5 Table 50. SLSSLLG5 Record Format 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. YES - PRODUCE A DSECT LISTING NO - NO DSECT AREA SLSSLLG5...
Page 576 Table 50. SLSSLLG5 Record Format (Continued) Type Length Label Description 1..X’80’ LLG5STHN STATION IS A NETWORK HOSTNAME .1..X’40’ LLG5STTC STATION IS A NETWORK IP ADDRESS FOR TCP/IP HOSTNAME ADDRESS: (14) CHARACTER LLG5SHNM STATION NETWORK HOSTNAME FOR TCP/IP NETWORK ADDRESS: (2C) HEXSTRING LLG5STCP...
Page 577 Cross Reference Offset Name Value LLG5ACS 000001 LLG5HDR 000004 LLG5KEY 000001 LLG5L LLG5LEN 000004 LLG5NMST 000001 LLG5NSLV 000001 LLG5OMST 000001 LLG5OSLV 000001 LLG5SHNM 000024 LLG5SP 000001 LLG5STCP 000004 LLG5STHN LLG5STN 000002 LLG5STTC LLG5STYP 000001 LLG5SUBT 6505 SLSSLLG5 000002 Appendix C. Record Formats 547 1st ed., 6/30/04 - 312579601...
Page 578: Slssllg6
SLSSLLG6 Table 51. SLSSLLG6 Record Format 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. YES - PRODUCE A DSECT LISTING NO - NO DSECT AREA SLSSLLG6...
Page 579 Table 51. SLSSLLG6 Record Format (Continued) 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..
Page 580 Table 51. SLSSLLG6 Record Format (Continued) Type Length Label Description (78) SIGNED-FWORD LLG6L13RM LSM 13 Robotic Motions Started (7C) SIGNED-FWORD LLG6L13SF LSM 13 Softfails Recovered (80) SIGNED-FWORD LLG6L14RM LSM 14 Robotic Motions Started (84) SIGNED-FWORD LLG6L14SF LSM 14 Softfails Recovered (88) SIGNED-FWORD LLG6L15RM...
Page 581 Cross Reference Offset Name Value LLG6ACS 000001 LLG6FLG1 000001 LLG6FLG2 000001 LLG6HDR 000004 LLG6KEY 000001 LLG6L LLG6LEN 000004 LLG6L0AV LLG6L0RM 000004 LLG6L0SF 000004 LLG6L1AV LLG6L1RM 000004 LLG6L1SF 000004 LLG6L10AV LLG6L10RM 000004 LLG6L10SF 000004 LLG6L11AV LLG6L11RM 000004 LLG6L11SF 000004 LLG6L12AV LLG6L12RM 000004 LLG6L12SF 000004...
Page 582 Offset Name Value LLG6L2AV LLG6L2RM 000004 LLG6L2SF 000004 LLG6L3AV LLG6L3RM 000004 LLG6L3SF 000004 LLG6L4AV LLG6L4RM 000004 LLG6L4SF 000004 LLG6L5AV LLG6L5RM 000004 LLG6L5SF 000004 LLG6L6AV LLG6L6RM 000004 LLG6L6SF 000004 LLG6L7AV LLG6L7RM 000004 LLG6L7SF 000004 LLG6L8AV LLG6L8RM 000004 LLG6L8SF 000004 LLG6L9AV LLG6L9RM 000004 LLG6L9SF 000004...
Page 583: Slssdjlr
SLSSDJLR Table 52. SLSSDJLR Record Format 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.
Page 584 Table 52. SLSSDJLR Record Format (Continued) Type Length Label Description (78) CHARACTER DJLRUN42 ALTERNATE JOURNAL’S UNIT NAME (7C) CHARACTER DJLRUN41 INITIAL JOURNAL’S UNIT NAME (80) AREA -RESERVED- FORCE THE LENGTH OF DJLR TO (80) LENGTH DJLRL DOUBLE-WORD MULTIPLE FOR GETMAIN. Cross Reference Offset Name...
Page 585: Slsspswi
SLSSPSWI Table 53. SLSSPSWI Record Format 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. YES - PRODUCE A DSECT LISTING NO - NO DSECT AREA...
Page 586 Cross Reference Offset Name Value PSWITERR 000004 PSWITFLG 000004 PSWITID 7001 PSWITL PSWPRDCB 000004 PSWPRFLG 000001 PSWPRQNM 000044 PSWPRUCB 000004 PSWPRVOL 000006 PSWSCDCB 000004 PSWSCFLG 000001 PSWSCQNM 000044 PSWSCUCB 000004 PSWSCVOL 000006 SLSSPSWI 000002 556 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 587: Slssrl00
SLSSRL00 Table 54. SLSSRL00 Record Format 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. YES - PRODUCE A DSECT LISTING NO - NO DSECT AREA...
Page 588: Slssrl01
SLSSRL01 Table 55. SLSSRL01 Record Format 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. YES - PRODUCE A DSECT LISTING NO - NO DSECT AREA...
Page 589: Slsshlg1
SLSSHLG1 Table 56. SLSSHLG1 Record Format Type Length Label Description SLSSHLG1 - Host Communications LOGREC format 1 FUNCTION: Defines the LOGREC record formatted for method switches. STRUCTURE SLSSHLG1 Communications LOGREC format 1 (9201) CONST HLG1SUBT Subtype X’9201’ 37377 Standard SLS Control Block Header A-ADDR HLG1HDR Identifier...
Page 590 Table 56. SLSSHLG1 Record Format (Continued) Type Length Label Description ..1..X’20’ HLG1IWRT Initiated by WRITE function error ...1 ..X’10’ HLG1IICN Initiated by internal condition (meaning internal to HSC processing, for example, operator switched method for local host so method is switched for all other possible hosts) (39)
Page 591 Cross Reference Offset Name Value HLG1FLG1 000001 HLG1FLG2 000001 HLG1HDR 000004 HLG1ICMD HLG1ID ‘CVAL’ HLG1IICN HLG1INTH 000008 HLG1IOTH HLG1IWRT HLG1KEY 000001 HLG1L HLG1LCLH 000008 HLG1LEN 000004 HLG1NLP 000004 HLG1NMTH 000004 HLG1PLP 000004 HLG1PMTH 000004 HLG1RC 000004 HLG1SLSI 000001 HLG1SP 000001 HLG1SUBT 9201 HLG1SWTH...
Page 592: Volume Report And Batch Api Records
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
Volume Report and Batch API Record Formats SLUVADAT Table 58. SLUVADAT Record Format 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 STRUCTURE SLUVADAT CHARACTER...
Page 594 Table 58. SLUVADAT Record Format (Continued) 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 BITSTRING LSMVCAMF FLAG BYTE 1...
Page 595 Table 58. SLUVADAT Record Format (Continued) Type Length Label Description (1D) HEXSTRING LSMNCIPN NUMBER OF COLUMES PER INSIDE PANEL (1E) HEXSTRING LSMDPNUM NUMBER OF DRIVE PANELS (1F) HEXSTRING LSMNADLS NUMBER OF ADJACENT LSMS (20) HEXSTRING LSMADLSM ADJACENT LSM NUMBERS (1 BYTE/LSM) (24) SIGNED-HWORD...
Page 596 Table 58. SLUVADAT Record Format (Continued) 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.
Page 597 Table 58. SLUVADAT Record Format (Continued) 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...
Page 598 Offset Name Value LSMCDRVP LSMCDR10 LSMCIM LSMCINPN LSMCIN19 LSMCISDR LSMCLCUP LSMCLNNM 000002 LSMCNOCL LSMCPTMP LSMCSTMP LSMCWIDD LSMCWIDN LSMDPNUM 000001 LSMELCAP LSMELCEL LSMELCE3 LSMELCE4 LSMELDRV LSMELIB LSMENTLN LSMFRECL 000002 LSMHCLVL 000006 LSMHSTID 000008 LSMHWTYP 000001 LSMIDPNO 000001 LSMLCLSL 000006 LSMLCLVL 000006 LSMLCUPN 000001 LSMLIPNO...
Page 599 Offset Name Value LSMNADLS 000001 LSMNCIPN 000001 LSMNCLSL 000002 LSMNCOPN 000001 LSMNDPPN 000001 LSMNONEX LSMNPGCS 000001 LSMNRIPN 000001 LSMNROPN 000001 LSMNUMBR 000001 LSMNXPRT 000001 LSMODPNO 000001 LSMOFFPN LSMPANLS 000006 LSMPCCNT 000002 LSMPFLG 000001 LSMPFRZ LSMPFRZL LSMPNLEL LSMPNLTY 000001 LSMPNTOT 000001 LSMPOWDR LSMPTPNO 000001...
Page 600 Offset Name Value LSMTWLF LSMVCAMF 000001 LSMVCAMR LSMWOLF LSMWPNL0 LSMWPNL2 LSMWPNL3 LSMWP0PT LSMWP1DR LSMWP2PT LSMWP3DR LSMWP41C LSMWP42C LSMW3NOC LSMW1NOD LSMW2PSL LSMW3DNC LSMW3WIN LSMW4CCN LSMW4CNC 570 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 601: Sluvcdat
SLUVCDAT Table 59. SLUVCDAT Record Format Type Length Label Description SLUVCDAT - FLAT FILE STATIC CONFIGURATION DATA DSECT FUNCTION: DESCRIBES THE STATIC CONFIGURATION INFORMATION WHICH MAY BE GENERATED TO THE FLAT FILE BY THE VOLUME REPORT UTILITY STRUCTURE SLUVCDAT CHARACTER -RESERVED- RECORD TYPE (C’C’) CHARACTER...
Page 602 Table 59. SLUVCDAT Record Format (Continued) 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 ..
Page 603 Cross Reference Offset Name Value CFGCCPFX 000003 CFGCHKEP CFGCMDPF 000001 CFGDDISP 000001 CFGDDNSC CFGDDSCR CFGDISVF CFGENGLS CFGFLAG1 000001 CFGFRNCH CFGGERMN CFGITALN CFGLANG 000001 CFGLIBFX CFGLNGTH CFGMXLSM CFGNMACS 000002 CFGSCRAL CFGSCRBL CFGSCRLB 000001 CFGSCRNA CFGSCRNL CFGSCRNS CFGSCRSL CFGSMFTY 000001 CFGTOTCA 000002 CFGTOTDR 000002 CFGTOTLS...
Page 604: Sluvhdat
SLUVHDAT Note: Field HSTLIBEN contains only the first 16 ACS esoterics. Table 60. SLUVHDAT Record Format Type Length Label Description SLUVHDAT - FLAT FILE HOST INFORMATION DSECT FUNCTION: DESCRIBES THE HOST INFORMATION WHICH MAY BE WRITTEN TO THE FLAT FILE BY THE VOLUME REPORT UTILITY STRUCTURE SLUVHDAT...
Page 605 Table 60. SLUVHDAT Record Format (Continued) 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 ..
Page 606 Cross Reference Offset Name Value HSTDEAD HSTDELAY HSTFLAG1 000001 HSTFLAG2 000001 HSTFLAG3 000001 HSTFXLEN HSTHNAME 000008 HSTHOSLN HSTHOSTS HSTHSTAC HSTINDEX 000001 HSTLIBEN 000008 HSTNHOST 000002 HSTNONEN 000008 HSTPRIAC HSTRCVRH HSTRCVRR HSTR110 HSTR120 HSTR200 HSTR201 HSTR210 HSTR400 HSTR410 HSTSBYAC HSTSHDAC 576 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 607: Sluvidat
SLUVIDAT Table 61. SLUVIDAT Record Format 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. STRUCTURE SLUVIDAT CHARACTER -RESERVED- RECORD TYPE (C’I’) BITSTRING CDSRCVRY CDS RECOVERY OPTIONS...
Page 608 Table 61. SLUVIDAT Record Format (Continued) Type Length Label Description CHARACTER CDSDSN CDS DATASET NAME (2C) CHARACTER CDSVOL CDS VOLSER (32) HEXSTRING -RESERVED- *** RESERVED *** (34) CHARACTER CDSUNIT CDS UNIT NAME (3C) HEXSTRING CDSSWCNT CDS SWITCH COUNT (3E) HEXSTRING -RESERVED- *** RESERVED *** (40)
Page 609 Cross Reference Offset Name Value CDSALL CDSBDATE 000008 CDSBOTH CDSBTIME 000008 CDSCDATE 000008 CDSCTIME 000008 CDSDSN 000044 CDSENQNM 000008 CDSINFOL CDSJOURN CDSLEVEL 000008 CDSLNGTH CDSNAMES 000240 CDSNONE CDSRCVRY 000001 CDSRDATE 000008 CDSRSVD1 000004 CDSRTIME 000008 CDSSECND CDSSTDBY CDSSWCNT 000002 CDSUNIT 000008 CDSVOL 000006...
Page 610: Sluvsdat
SLUVSDAT Table 62. SLUVSDAT Record Format 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. STRUCTURE SLUVSDAT CHARACTER...
Page 611 Cross Reference Offset Name Value STNACS 000001 STNADDRS 000003 STNADENL STNCUA 000002 STNENTLN STNFLAG 000001 STNFXLEN STNHINDX 000001 STNONLIN STNSTNS Appendix C. Record Formats 581 1st ed., 6/30/04 - 312579601...
Page 612: Sluvvdat
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.
Page 613 Table 63. SLUVVDAT Record Format (Continued) Type Length Label Description (D9) CHAR CONST VOLMEDTR (X’D9’) STK1R MEDIA ‘R’ ‘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...
Page 614 Table 63. SLUVVDAT Record Format (Continued) Type Length Label Description (1A) CHARACTER VOLHMCEL DECIMAL NUMBER OF THE COLUMN WITHIN VOLHMROW WHERE THE VOLUME RESIDES. (1C) CHARACTER VOLSPLBL VOLUME SUBPOOL LABEL TYPE ‘SL’ (E2D3) CHAR CONST VOLSPSL STANDARD LABEL ‘NL’ (D5D3) CHAR CONST VOLSPNL NON-LABELLED...
Page 615 Table 63. SLUVVDAT Record Format (Continued) Type Length Label Description (44) CHARACTER VOLDTINS DATE VOLUME INSERTED INTO THE LIBRARY FORMAT DETERMINED BY VOLD4YR (4C) CHARACTER VOLTMINS TIME VOLUME INSERTED INTO THE LIBRARY (HH:MM:SS) (54) CHARACTER VOLDTSEL DATE VOLUME LAST SELECTED FORMAT DETERMINED BY VOLD4YR (5C)
Page 616 Table 63. SLUVVDAT Record Format (Continued) 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 ..
Page 617 Table 63. SLUVVDAT Record Format (Continued) Type Length Label Description (7B) HEXSTRING -RESERVED- * RESERVED (7E) HEXSTRING VOLSRCE SOURCE LOCATION (84) HEXSTRING VOLDEST DESTINATION LOCATION (8A) CHARACTER VOLLILSM “LOST IN” LSM (8C) CHARACTER VOLRECC RECTECH CHAR FORM (94) CHARACTER VOLMEDC MEDIA CHAR FORM (9C) LENGTH...
Page 618 Table 63. SLUVVDAT Record Format (Continued) Type Length Label Description HEXSTRING -RESERVED- RESERVED HEXSTRING VOLSDIDX DRIVE INDEX NUMBER HEXSTRING -RESERVED- RESERVED BITSTRING VOLSDFLG DRIVE FORMAT FLAG 1111 1111 X’FF’ VOLSDFIX DRIVE IS DRIVE INDEX FORMAT HEXSTRING -RESERVED- RESERVED FOR “OTHER” TYPES, THIS RECORD IS TREATED AS IF THE VOLUME WERE ERRANT. 588 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 619 Cross Reference Offset Name Value VOLDEST 000006 VOLDTINS 000008 VOLDTMNT 000008 VOLDTSEL 000008 VOLD4YR VOLERACT VOLERDSC VOLERHSC VOLERLIL VOLERLSC VOLERMNT VOLERSSC VOLEXLBL VOLEXRD VOLFLAG1 000001 VOLFLAG2 000001 VOLFLAG3 000001 VOLHMACS 000002 VOLHMCEL 000002 VOLHMLOC 000014 VOLHMLSM 000002 VOLHMPNL 000002 VOLHMROW 000002 VOLIELEN VOLINUSE...
Page 620 Offset Name Value VOLITRTN 000001 VOLITTAG 000001 VOLITUSE VOLITVOL VOLLILSM 000002 VOLLNGTH VOLMEDC 000008 VOLMEDIA 000001 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’...
Page 621 Offset Name Value VOLRRCNL VOLRRDEJ VOLRRERR VOLRRMCT VOLRRMNT VOLRRSCA VOLRRSCD VOLRRSLV VOLRRSRE VOLRRSUA VOLRRVDL VOLSACSN 000001 VOLSCAP ‘CVAL’ VOLSCELL ‘CVAL’ VOLSCLOC 000002 VOLSCOLN 000001 VOLSCR VOLSDFIX VOLSDFLG 000001 VOLSDIDS 000001 VOLSDNUM 000001 VOLSDPNL 000001 VOLSDRIV ‘CVAL’ VOLSEL VOLSELCT 000004 VOLSER 000006 VOLSLSMN 000001...
Page 622 Offset Name Value VOLSPNLN 000001 VOLSPNON ‘CVAL’ VOLSPNSL ‘CVAL’ VOLSPSL ‘CVAL’ VOLSRCE 000006 VOLSROWN 000001 VOLSTYPE 000001 VOLTDINS 000004 VOLTDMNT 000004 VOLTDSEL 000004 VOLTMINS 000008 VOLTMMNT 000008 VOLTMSEL 000008 592 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 623: Batch Api Records
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...
Page 624: Batch Api Record Formats
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 Type Length Label Description SLUVDDAT - QCDS DRIVE INFORMATION DSECT FUNCTION: MAPS THE DRIVE DATA PRODUCED BY THE QCDS READ REQUEST...
Page 625 Table 65. SLUVDDAT Record Format (Continued) Type Length Label Description (F0F1) CHAR CONST UVD984B4 T9840B ACTING AS A 3490E ‘01’ ‘07’ (F0F7) CHAR CONST UVD984B5 T9840B ACTING AS A 3590 (F0F9) CHAR CONST UVD994B4 T9940B ACTING AS A 3490E ‘09’ ‘10’...
Page 626 Offset Name Value UVDFLAG2 000001 UVDFLAG3 000001 UVDIDACS 000001 UVDIDLSM 000001 UVDIDNUM 000001 UVDIDPNL 000001 UVDLEN UVDLUNIT 000002 UVDNOLMU FFFF UVDNSCR UVDNUNIT 000002 UVDOPRQ UVDRACF UVDREDW ‘CVAL’ UVDRT 000001 UVDSCR UVDSILV ‘CVAL’ UVDTIMB ‘CVAL’ UVDTMS7 UVDTYPE 000002 UVDUNITN 000002 UVDV5310 UVD3490E ‘CVAL’...
Page 627 Offset Name Value UVD994B5 ‘CVAL’ Appendix C. Record Formats 597 1st ed., 6/30/04 - 312579601...
Page 628: Sluvpdat
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 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.
Page 629 Table 66. SLUVPDAT Record Format (Continued) Type Length Label Description (20) SIGNED-HWORD UVPLPRIO LENGTH OF CAP PRIORITY ELEMENTS (22) HEXSTRING UVPPRITY(16) CAP PRIORITY ELEMENTS, BY HOST INDEX (32) HEXSTRING UVPPANEL PANEL NUMBER OF CAP (33) BITSTRING UVPTYPE TYPE OF CAP: 1...
Page 630 Cross Reference Offset Name Value UVPCIM UVPCLIP UVPFLAG1 000001 UVPFLAG2 000001 UVPF1ACT UVPF1AUT UVPF1LNK UVPF1ONL UVPF1REC UVPF2CLN UVPF2DRA UVPF2EJT UVPF2ENT UVPF2IDL UVPHOST 000008 UVPHOSTI 000001 UVPID 000003 UVPJOBN 000008 UVPLEN UVPLPRIO 000002 UVPNCELL 000002 UVPNCOLS 000001 UVPNMAGC 000001 UVPNMAGS 000001 UVPNPRIO 000002 UVPNROWS...
Page 631 Offset Name Value UVPTWSTD UVPTYPE 000001 UVP9740 Appendix C. Record Formats 601 1st ed., 6/30/04 - 312579601...
Page 632 602 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 633: Appendix D. Logging Acs Robotics Motion
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: •...
Page 634: Permanent Motion Errors
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.
Page 635: How Information Is Logged
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. Such a record is called an LLG6 record. Refer to Appendix C, “Record Formats” on page 497 to see the record layout for LLG6.
Page 636 Table 67. Format for Total Motions and Temporary Error Counts (Continued) Initiated and Temporary Error Motion Software Error Record BYTE # Description of Field 46-46 LSM Configuration Flag 1st Byte X’80’ - LSM 0 exists if flag is on X’40’ - LSM 1 exists if flag is on X’20’...
Page 637 • if the Record Type Field (bytes 642-643) has a value of X’6501’, • the StorageTek identifier (X’FEEDFACE’ at bytes 644-647) is present, and • the character ‘H’ appears at the byte 113 location. Appendix D. Logging ACS Robotics Motion 607...
Page 638: Table 68. Record Format For A Hard Failure
These records, regardless of whether the hard fail indicator is turned on, are LLG1 records. Table 68. Record Format for a Hard Failure Motion Hard Fail Software Error Record BYTE # Description of Field 00-31 Standard HSC LOGREC header 00-00 X’40’...
Page 639: Logging Interval
114-641 Reserved 642-643 Record type X’6501’ 644-647 StorageTek identifier X’FEEDFACE’ 648-651 Timestamp Logging Interval When LMU 3.0 or 9315/9330 1.0 µ-software is properly installed in the ACS, the HSC identifies hard fails in LLG1 records and records robotic motion and temporary error counts in LLG6 records written to SYS1.LOGREC.
Page 640: Single-Host Environment
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.
Page 641: Lmu Response Codes
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.
Page 642: Invalid Parameter Error Codes: 0101 - 0127
Invalid Parameter Error Codes: 0101 - 0127 Table 69. LMU Response Codes 0101 thru 0127 Response Description Vw X Resp 0101 Bad primary LSM 0102 Bad secondary LSM 0105 Undefined option or modifier 0106 Invalid LSM 0107 Invalid panel 0108 Invalid row 0109 Invalid column...
Page 643: Configuration Error Codes: 0201 - 0203
Configuration Error Codes: 0201 - 0203 Table 70. LMU Response Codes 0201 thru 0203 Response Description Vw X Resp 0201 LSM is not in static configuration 0202 Drive does not exist 0203 CAP does not exist CAP Procedural Error Codes: 0301 - 0310 Table 71.
Page 644: General Procedural Error Codes: 0401 - 0427
General Procedural Error Codes: 0401 - 0427 Table 72. LMU Response Codes 0401 thru 0427 Response Description Vw X Resp 0401 LSM not ready if unlabeled or bypass label if not VARY and LSM offline else add to Temp Outage Queue 0402 LSM in maintenance mode 0403...
Page 645: Lmu Lan Interface Error Codes: 0501 - 0512
Table 72. LMU Response Codes 0401 thru 0427 (Continued) Response Description Vw X Resp 0426 Drive not rewound 0427 Cartridge not mounted LMU LAN Interface Error Codes: 0501 - 0512 Table 73. LMU Response Codes 0501 thru 0512 Response Description Vw X Resp 0501...
Page 646: Lmu Logical Error Codes: 0601 - 0620
LMU Logical Error Codes: 0601 - 0620 Table 74. LMU Response Codes 0601 thru 0620 Response Description Vw X Resp 0601 Unknown allocation request 0602 Bad qualifier byte 0 0603 Bad qualifier byte 1 0604 Bad qualifier byte 2 0605 LSM online 0606 Offline pend overridden...
Page 647: Lsm Robotics Error Codes: 0701 - 0718
LSM Robotics Error Codes: 0701 - 0718 Table 75. LMU Response Codes 0701 thru 0718 Response Description Vw X Resp 0701 Arm not operational 0702 Hand not operational 0703 PTP not operational PTP does not exist CAP is not operational 0707 Necessary elements inoperational...
Page 648: Lsm Hardware Error Codes: 0801 - 0809
LSM Hardware Error Codes: 0801 - 0809 Table 76. LMU Response Codes 0801 thru 0809 Response Description Vw X Resp 0801 LSM didn’t respond to request 0804 CAP unlock solenoid has over-currented 0805 Unlock CAP failed 0806 Lock CAP failed 0807 Drive not communicating 0808...
Page 649 Table 77. LMU Response Codes 0901 thru 0977 (Continued) Response Description Vw X Resp 0921 Bad panel, row, or column 0922 Arm currently reserved 0923 CAP currently reserved 0924 First Master Pass-Thru-Port reserved 0925 Second Master Pass-Thru-Port reserved 0926 Playground currently reserved 0943 LSM is online 0944...
Page 650: Drive Error Codes: 1001 - 1011
Table 77. LMU Response Codes 0901 thru 0977 (Continued) Response Description Vw X Resp 0976 Can’t rewind 0977 Can’t unload 0978 Drive cannot honor write protected 0979 Drive currently reserved Drive Error Codes: 1001 - 1011 Table 78. LMU Response Codes 1001 thru 1011 Response Description Vw X Resp...
Page 651: Appendix E. Remote-Linked Libraries
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., 6/30/04 - 312579601...
Page 652: Configuration 1
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 PRIMARY SECONDARY STANDBY CONTROL CONTROL CONTROL DATA SET DATA SET DATA SET LEGEND:...
Page 653: Configuration 2
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...
Page 654: Configuration 3
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
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 OPERATING...
Page 656: Configuration 5
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
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.
Page 659: Appendix F. Batch Application Program Interface (Api) 629
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).
Page 660: Addresses And Registers
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.
Page 661: Syntax
• Register (15): stores QCDS request return codes. Syntax The syntax for the QCDS request is: label SLSUREQ QCDS ,REQUEST=request ,TYPE=type ,BUFFER=buffer ,BUFLEN=buflen ,TOKEN=token ,DDNAME=ddname ,UCALADR=rtnaddr ,MF= (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 specifies the host information record area specifies the Multi-Volume Cartridge record area specifies the station record area specifies the volume record area 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.
Page 663: Qcds Programming Considerations
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.
Page 664: Return Codes
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.
Page 665: Sample Qcds Requests
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.
Page 666: Figure 33. Sample 1 - Automatic Cds Allocation
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.
Page 667 WKFLATDD(KFLATDDL),KFLATDD Initialize the working R4,WKFLATDD storage version of the DCB from the OPEN ((R4),(OUTPUT)) copy in the constants area. * Use QCDS OPEN to automatically allocate the current primary CDS * and open the VTV record area: OPENVOL Open CDS VTV record area: SLSUREQ QCDS, REQUEST=OPEN, DDNAME==CL8'CDS1',...
Page 668 * Inner loop - process each VTV record in the response area: VOLPROC Over all VTV records in reply: ... process VTV record here ... WKFLATDD,((R8)) R8,VDRECLEN(,R8) Pointer to next VTV record R9,VOLPROC Process next VTV record CHECKEOA DS Check for more VTV records WKRDRC,=A(SLURRDEA) VTV end-of-area? READVOL No, read more VTV records...
Page 669: Mapping Macros
* 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 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 MVS register save area WKUCAL...
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., 6/30/04 - 312579601...
Page 671: Figure 34. Sample 2 - Reading Acs And Drv Together
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.
Page 672 * OPEN ACS AND DRIVE RECORD AREAS AND MAP THE RESPONSE AREAS: OPEN 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...
Page 673 * CONDITIONALLY BRANCH TO CLOSE LABEL WHEN AN APPROPRIATE * LOOP TERMINATION CONDITION HAS BEEN SATISFIED (NOT SHOWN). PROCESS REPEAT MAIN PROCESSING LOOP * CLOSE THE ACS AND DRIVE RECORD AREAS: CLOSE CLOSE ACS AND DRIVE RECORD AREAS: SLSUREQ QCDS, CLOSE THE ACS RECORD AREA REQUEST=CLOSE, TYPE=ACS,...
Page 674: Output Description
* MAPPING MACROS: SLSREGS REGISTER EQUATES SLSUREQM , SLSUREQ MAPPING MACRO SLUVADAT , 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).
Page 675: Slsureqm Macro
SLSUREQM Macro The SLSUREQM mapping macro must be specified in any assembly that uses the SLSUREQ macro. Syntax label SLSUREQM PRO= 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., 6/30/04 - 312579601...
Page 676: Batch Api Mapping (Slsureqm) Macro
Batch API Mapping (SLSUREQM) Macro Table 83. SLSUREQM Record Format 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. STRUCTURE SLSUREQM PARAMETER LIST CHARACTER SLSUHDR EYE-CATCHER FIELD:...
Page 677 Table 83. SLSUREQM Record Format (Continued) Type Length Label Description A-ADDR SLSUQCDB QCDS RESPONSE AREA BUFFER ADDRESS (10) SIGNED-FWORD SLSUQCDL QCDS RESPONSE AREA BUFFER LENGTH (14) A-ADDR SLSUQCDD QCDS INPUT CDS DDNAME POINTER (18) CHARACTER SLSUQDSN QCDS INPUT CDS DATA SET NAME (44) CHARACTER...
Page 678 Table 83. SLSUREQM Record Format (Continued) Type Length Label Description SIGNED-FWORD SLURQCDO OFFSET TO QCDS LIBRARY ELEMENT RECORD SECTION FROM START OF REPLY HEADER. QCDS OPEN RETURN CODES: (00) CONST SLUROPOK RECORD AREA WAS OPENED SUCCESSFULLY. (04) CONST SLUROPAO OPEN FAILED - ATTEMPT TO OPEN A RECORD AREA THAT IS ALREADY OPEN.
Page 679 Table 83. SLSUREQM Record Format (Continued) Type Length Label Description (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. (08) CONST SLURRDIT READ FAILED - INVALID TOKEN VALUE.
Page 680 Table 83. SLSUREQM Record Format (Continued) Type Length Label Description (10) CONST SLURCLIO CLOSE FAILED - I/O ERROR WHILE ACCESSING THE ASSOCIATED CDS. (10) LENGTH SLURRHLN LENGTH OF REPLY HEADER. (10) AREA SLURFRS START OF VARIABLE-LENGTH FORMATTED RECORD SEGMENT. 650 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 681 Cross Reference Offset Name Value SLSUACSA SLSUARAN SLSUCAPA SLSUCDSA SLSUCFGA SLSUDRVA SLSUHDR 000004 SLSUHSTA SLSUID ‘CVAL’ SLSULN SLSUMVCA SLSUQCDA 000001 SLSUQCDB 000004 SLSUQCDC SLSUQCDD 000004 SLSUQCDK 000004 SLSUQCDL 000004 SLSUQCDO SLSUQCDR SLSUQCDS SLSUQCDT 000001 SLSUQDSN 000044 SLSURT 000001 SLSUSTAA SLSUVER 000001 SLSUVN SLSUVOLA...
Page 682 Offset Name Value SLURCLOK SLURCLRA SLURFRS 000004 SLURHDR 000004 SLURHSCV 000002 SLURID ‘CVAL’ SLUROPAO SLUROPDA SLUROPDD SLUROPDM SLUROPIO SLUROPIT SLUROPNA SLUROPOK SLUROPRA SLURQCDN 000004 SLURQCDO 000004 SLURQCRT SLURRDBA SLURRDEA SLURRDIB SLURRDIL SLURRDIO SLURRDIT SLURRDNO SLURRDOK SLURRDRA SLURRHLN SLURRPLY 000001 SLURRQPL SLURRQRT SLURVER 000001...
Page 683 Appendix F. Batch Application Program Interface (API) 653 1st ed., 6/30/04 - 312579601...
Page 684 654 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 685: Glossary
Glossary Terms are defined as they are used in the text. If you intervention. This is the normal operating mode of an cannot find a term here, check the index. LSM that has been modified online. AC— Alternating current. basic direct access method (BDAM)— An access method used to directly retrieve or update particular access method—...
Page 686 CAPid— A CAPid uniquely defines the location of a Central Support Remote Center (CSRC)— See CAP by the LSM on which it resides. A CAPid is of Remote Diagnostics Center. the form AA:LL:CC where AA is the ACSid (00-FF CFT— Customer Field Test. hexadecimal), LL is the LSM number (00-17 hexadecimal), and CC is the CAP number.
Page 687 control data set recovery area— A portion of the data compaction— An algorithmic data-reduction CDS reserved for maintaining integrity for updates technique that encodes data from the host and stores that affect multiple CDS blocks. it in less space than unencoded data. The original data is recovered by an inverse process called control data set subfile—...
Page 688 device group— A subset of the eligible devices. all other transports contain up to four transports per Device groups are defined by esoteric unit names but panel. also may be created implicitly if common devices drive prioritization— (previously referred to as exist in different device groups.
Page 689 ECCST— (1) A value that can be specified on the EPO— Emergency Power Off. MEDia parameter and that includes only enhanced EREP— Environmental Recording, Editing, capacity cartridge system tapes. (2) An alias of Printing. ECART. (3) See Enhanced Capacity Cartridge System Tape.
Page 690 frozen panel— A panel to which cartridges cannot operating system and the rest of the automated be moved. This restriction includes allocating new library. cartridge locations on a panel as a result of: host system— A data processing system that is used •...
Page 691 programs at IPL execution. Devices running keyword parameter— In command and utility µ-software reload the functional µ-software usually syntax, operands that include keywords and their from a floppy diskette at IPL execution. related values (See positional parameter). initial value— A value assumed until explicitly Values are concatenated to the keyword either by an changed.
Page 692 LMUPDEF— An HSC command used to load the definition data set that contains LMUPATH control machine initiated maintenance— See ServiceTek. statements. magnetic recording— A technique of storing data load point— The beginning of the recording area on by selectively magnetizing portions of a magnetic tape.
Page 693 media capacity— The amount of data that can be attempt to execute the cleaning process. See also contained on storage media and expressed in bytes of spent cleaning cartridge. data. over-use cleaning cartridge— A cartridge that has a media mismatch— A condition that occurs when usage (select) count over the MAXclean value (see the media value defined in a VOLATTR control over-limit cleaning cartridge) or that has used up its...
Page 694 CAP (PCAP)— A one-cell CAP that is part Diagnostics Center at StorageTek. RDC operators of an enhanced CAP. A PCAP allows a user to enter can access and test StorageTek systems and software, or eject a single cartridge that requires immediate through telecommunications lines, from remote action.
Page 695 problem impacts operations. Customers can set be used to clean tape transports. See also over-limit maintenance threshold levels. cleaning cartridge. servo— A device that uses feedback from a sensing SSD— Solid state disk. element to control mechanical motion. STAM— See Shared Tape Allocation Manager. Shared Tape Allocation Manager (STAM)—...
Page 696 specified type of 9840 cartridge or recording System Control Program— The general term to technique. STK1R can be abbreviated as R. describe a program which controls access to system resources, and allocates those resources among STK1U— Value that can be specified on the MEDia executing tasks.
Page 697 Virtual Tape Storage Subsystem (VTSS)— The reading data from the tape. DASD buffer containing virtual volumes (VTVs) and virtual drives (VTDs). The VTSS is a StorageTek TREQDEF— An HSC command that is used to load RAID 6 hardware device with microcode that the definition data set that contains TAPEREQ enables transport emulation.
Page 698 18-track— A recording technique that uses 18 tracks transports that provide read/write capability for on the tape. The tape is written in only the forward 18-track recording format. The StorageTek 4480 motion. Cartridge Subsystem is equivalent to a 3480 device.
Page 699 9840s can be defined in 10-drive and 20-drive panel configurations. The 9840 can perform as a standalone subsystem with a cartridge scratch loader attached, or it can be attached to a StorageTek ACS. T9840B—The StorageTek cartridge transport that reads and writes T9840B cartridges.
Page 700 670 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 701: Index
Index DIAGScan Numerics EMPTYCel INTRANs 4480 Cartridge Subsystem, defined Audit utility 4490 Cartridge Subsystem, defined actions permitted 9490 Cartridge Subsystem, defined function 9490EE Cartridge Subsystem, defined invoking JCL examples 9840 Cartridge Subsystem, defined JCL requirements media type mismatch conditions output description overview abend codes parameters...
Page 702 backup, CDS into the library loading Base service level, description for immediate use in new LSM Batch Application Program Interface (API) for later use in new LSM overview CCWTRACE CP command QCDS request addresses and registers CDSDEF control statement function example invoking overview...
Page 703 control data set definition control statement Unit Attribute Definition (UNITDEF) Volume Attribute (VOLATTR) control statement continuation conventions Volume Attribute Definition (VOLDEF) control statements definition data set control statements CDS Definition (CDSDEF) LMU path (LMUPATH) continuation LMU path definition (LMUPDEF) EXECParm Scratch subpool (SCRPDEF) Journal Definition (JRNDEF) License Key Definition (LKEYDEF)
Page 704 JCL example JCL requirements output description ECART, defined parameters ECCST, defined prerequisites Eject cartridge utility syntax invoking disconnected mode, defined JCL examples dismount JCL requirements abnormal output description processing overview parameters DISMount command syntax Dismount parameter EJect command Display command EJect parameter DOMed, defined Eject utility...
Page 705 Scratch Subpool control statement SCRPDEF command and control statement selective audit Helical, defined 1 ACS, 2 LSMs w/CAPid, JCL for Host Software Component (HSC) with panel/discrepancy list, JCL for abend codes TAPEREQ control statement architecture TREQDEF control statement control statements Unit Attribute Definition (UNITDEF) control statement defined UNITATTR control statement...
Page 706 setting Unselect utility Volume Report utility Job control Language (JCL) Move utility Improved Cartridge Recording Capability (ICRC), defined Journal command Index, defined Journal Definition (JRNDEF) control statement INISH deck, defined example overview Initial Microprogram Load (IML), defined parameters Initial Program Load (IPL), defined syntax initial value, defined Journal offload utility...
Page 707 MONITOR SITEno MOVe syntax OPTion LMU See Library Management Unit RECover LMUPATH control statement RELease parameters SENter SRVlev LMUADDR STOPMN syntax SWitch TRace LMUPATH, defined Vary LMUPDEF control statement VIew examples Warn parameters Library Control Unit (LCU), defined HOSTID Library Management Unit (LMU) UNIT defined VOLume...
Page 708 SLSSCAPJ, SMF CAP Eject Record MOVe utility SLSSCAPN, SMF CAP Enter Record Move utility SLSSDJLR, LOGREC Database/Journaling considerations SLSSFHDR, SMF Record Header invoking SLSSHLG1, LOGREC Host Communications Format JCL examples SLSSLHDR, LOGREC Header Layout JCL requirements SLSSLLG1, LOGREC LMU Driver Format output description SLSSLLG2, LOGREC LMU Driver Format overview...
Page 709 command-name OUTput COMMPath Output comp-list panel comp-name PASSTHRU dataset.name PGMI DDname PLaygrnd Defer prefvlue DELete Primary devaddr PRIVAT dev-id PROGram or PGMname dev-list dev-range Readonly DIAGScan RECtech Dialog REpath DISCmsg Dismount SCRatch DRive Scratch SCRDISM SCRTCH DUmp SCRtech EJctauto SEcndry EJect SMSAcsr EJLimit...
Page 710 Journal Definition (JRNDEF) precedence of VOLATTR and TAPEREQ statements License Key Definition (LKEYDEF) primary CDS License Key Information (LKEYINFO) defined options print overview a list of volumes/locations in an LSM processing library activities report Reconfiguration CDS Definition (RECDEF) control statement priority CAP (PCAP), defined Scratch Subpool programming/operational...
Page 711 SLUVHDAT, Flat File Host Information DSECT SLUVIDAT, Flat File CDS Information DSECT SLUVPDAT, Batch API CAP Information DSECT SLUVSDAT, Flat File ACS Station Address DSECT abend codes SLUVVDAT, Flat File Volume Data DSECT external trace facility internal trace table RECover Host command messages recovery SET TRACE command...
Page 712 device numbers for drives SLSSBLOS, SMF Macro function SLSSCAPJ, SMF Macro invoking SLSSCAPN, SMF Macro JCL requirements new host parameters SLSSDJLR, LOGREC Database/Journaling LIKEHOST SLSSDJLR, LOGREC Macro NEWHOST SLSSFHDR, SMF Macro output description overview SLSSHLG1, LOGREC Macro parameters SLSSLHDR, LOGREC Macro LIKEHOST SLSSLLG1, LOGREC Macro NEWHOST...
Page 713 SRVlev command Performance log reblocker syntax Reconfiguration CDS Definition (RECDEF) control statement stand-alone utilities Reconfiguration CDS Definition (RECDEF)control statement standard (4410) LSM, defined RECover Host command standard CAP, defined RELease CAP command standby CDS, defined REPLace utility standby LMU, defined Restore utility SCRAtch standby, defined...
Page 714 T9840C Cartridge Subsystem, defined parameters syntax T9940A Cartridge Subsystem, defined Unselect utility T9940B Cartridge Subsystem, defined invoking Tape Management Interface (TMI), description JCL example JCL requirements TAPEREQ control statement output description disabling overview example parameters overview syntax parameters PROGram/PGMname utilities syntax ACS UTIL exec usage...
Page 715 CP and CMS operators and utility users overview ZCART, defined Zeroscr parameter tape management system (TMS) VOLDEF command and control statement examples VOLSER defined ranges and lists volume defined specifying Volume Attribute (VOLATTR) control statement disabling examples overview parameters syntax usage Volume Attribute Definition (VOLDEF) control statement examples...
Page 716 686 VM/HSC 6.0 System Programmer’s Guide 1st ed., 6/30/04 - 312579601...
Page 718 Printed in U.S.A.

StorageTek Host Software Component 6.0 System Programmer's Manual

What's New with this Release

Preface

Chapter 1. System Description

Chapter 2. Host Software Component Functions

Chapter 3. HSC Control Statements and HSC Start Procedure

Chapter 4. Utility Functions

Quick Links

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for StorageTek Host Software Component 6.0