StorageTek Host Software Component 6.0 System Programmer's Manual

Host Software Component

(VM Implementation)

System Programmer’s Guide

Release 6.0

312579601

Information contained in this publication is subject to change without notice. Comments concerning the contents of this
publication should be directed to:

Global Learning Solutions
Storage Technology Corporation
One StorageTek Drive
Louisville, CO 80028-3526
USA

[e-mail]

Export Destination Control Statement

These commodities, technology or software were exported from the United States in accordance with the Export
Administration Regulations. Diversion contrary to U.S. law is prohibited.

Restricted Rights

Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1)
and (2) of the Commercial Computer Software - Restricted Rights at FAR 52.227-19 (June 1987), as applicable.

Limitations on Warranties and Liability

Storage Technology Corporation cannot accept any responsibility for your use of the information in this document or
for your use in any associated software program. You are responsible for backing up your data. You should be careful
to ensure that your use of the information complies with all applicable laws, rules, and regulations of the jurisdictions
in which it is used.

Warning: No part or portion of this document may be reproduced in any manner or in any form without the written
permission of Storage Technology Corporation.

Proprietary Information Statement

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.

First Edition, June 30, 2004

Part Number 312579601

EC 128976

StorageTek and the StorageTek logo are trademarks or registered trademarks of Storage Technology Corporation. Other
products and names mentioned herein are for identification purposes only and may be trademarks of their respective
companies.

 2004 Storage Technology Corporation. All rights reserved.

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

iv VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Contents

What’s New With This Release? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii

Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii

Organization of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii

How to Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii

References to HSC Product Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix

Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix

StorageTek HSC Publications - VM environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix

Miscellaneous Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxix

Reader’s Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix

StorageTek Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix

Chapter 1. System Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Automated Cartridge System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Host Software Component Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

HSC Subsystem Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

HSC Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

VM Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Virtual Machine Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

HSC and Automated Cartridge System Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Automated Mount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Automated Dismount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Dual LMU Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

User Control of HSC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 2. Host Software Component Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Overview of HSC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Automatic Functions of the HSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Facilities Available for User Control of HSC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Installation Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Initialization/Termination Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

HSC Service Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Media Type and Recording Technique Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

MEDia and RECtech Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Model Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Contents v

1st ed., 6/30/04 - 312579601

Matching VOLATTR and TAPEREQ Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Precedence of VOLATTR and TAPEREQ Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Mount/Dismount Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Mount Processing for Specific Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Mount Processing for Scratch Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Dismount Processing for Library Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Abnormal Mounts/Dismounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Volume/Cell Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Cartridge Access Port (CAP) Processing Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Near Continuous Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Using Multiple CDS Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Automatic Recognition of Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Using the SET Utility Instead of LIBGEN and Reconfiguration . . . . . . . . . . . . . . . . . . . . . 50

Defining a New Configuration to Avoid Future Reconfigurations . . . . . . . . . . . . . . . . . . . . 51

Defining Planned ACSs with no Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Changing Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Using CDS Rename/Relocate/Expand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Swapping Library Transports - New Model Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Common Recovery Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Control Data Set Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Control Data Set Recovery Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

User Control of Control Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Command Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Controlling LSM Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Controlling CAP Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Viewing the Interior Components of an LSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Utility Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

LMU Server Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Dual LMU Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Dynamic LMU Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Recovery Maintenance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

HSC Port Number Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Multiple TCP/IP Stack Implications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Transitioning Between 3270 and TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Recovering TCP/IP Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Configuring VM for TCP/IP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Communication Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Host-to-Host Communications Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Tape Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Batch Application Program Interface (API) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 3. HSC Control Statements and HSC Start Procedure . . . . . . . . . . . . . . . . . . . . . 83

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

PARMLIB Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Defining PARMLIB Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Processing PARMLIB Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

vi VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Options Offered by PARMLIB Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Control Statement Continuation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

CDS Definition (CDSDEF) Control Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

EXECParm Control Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Journal Definition (JRNDEF) Control Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

LKEYDEF Command and Control Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

License Key Information (LKEYINFO) Control Statement . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Reconfiguration CDS Definition (RECDEF) Control Statement . . . . . . . . . . . . . . . . . . . . . . 98

Scratch Subpool Control Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Definition Data Set Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Options Offered by Definition Data Set Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . 104

Defining LMU Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Defining Tape Request Attributes (TAPEREQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Defining Unit Attributes (UNITATTR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Defining Volume Attributes (VOLATTR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Identifying the Definition Data Sets (OPTION TITLE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Control Statement Continuation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

LMUPATH Control Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

LMUPDEF Command and Control Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

OPTion TITLE Control Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Scratch Subpool Definition (SCRPDEF) Command and Control Statement . . . . . . . . . . . . . 115

Tape Request (TAPEREQ) Control Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Tape Request Definition (TREQDEF) Command and Control Statement . . . . . . . . . . . . . . . 133

Unit Attribute (UNITATTR) Control Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Unit Attribute Definition (UNITDEF) Command and Control Statement . . . . . . . . . . . . . . . 140

Volume Attribute (VOLATTR) Control Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Volume Attribute Definition (VOLDEF) Command and Control Statement . . . . . . . . . . . . . 154

Creating an SLKJCL File for Starting the HSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

/PARM Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

/PARM Statement Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

HSC Startup Job (ACS SLKJCL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Starting HSC Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Modifying LSMs Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Specifying CAP Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Configuration Mismatches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Multiple Hosts Startup Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Starting the HSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Initializing the HSC to the Full Service Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Initializing the HSC to the Base Service Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Chapter 4. Utility Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Overview of Library Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Selecting a Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Typical Use of Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Control Statement Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Utility Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Contents vii

1st ed., 6/30/04 - 312579601

Utility Environmental Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

ACS UTIL Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

CMS Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

SCP Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

JCL and Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

SCP Batch Job Control Language (JCL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Submitting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Utility Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Sample SCP Batch Job File - JCL and Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Utility Administrator (SLUADMIN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

How to Invoke SLUADMIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

How to Invoke Utility Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

SLUADMIN Program Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Reports Created by Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Report Headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Parameters Controlling Report Headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Stand-Alone Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Activities Report Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

SLUACTV EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Utility Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Invoking the Activities Report Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Control File Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Audit Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Media Type Mismatch Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Actions Permitted During an Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

How the AUDIt Utility Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Concurrent Audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Utility Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Invoking the Audit Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

JCL Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Backup Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Reasons for Running the BACKup Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

How the BACKup Utility Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Backup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

When CDS Copies Are Split Among Hosts After an Error . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Utility Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

viii VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Invoking the BACKup Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

JCL Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

How to Restart Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Related Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Database Decompile (LIBGEN) Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Reasons for Running the Database Decompile Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

How the Database Decompile Utility Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Utility Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Invoking the Database Decompile Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

JCL Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Directory Rebuild Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Reasons for Running the Directory Rebuild Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

How the Directory Rebuild Utility Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Utility Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Invoking the Database Decompile Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

JCL Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Eject Cartridge Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Utility Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Invoking the Eject Cartridge Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

JCL Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Enter Cartridges Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

CAP Operating Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Utility Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Invoking the Enter Cartridges Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

JCL Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Contents ix

1st ed., 6/30/04 - 312579601

Journal Offload Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Utility Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Invoking the Journal Offload Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

JCL Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Move Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

MOVe Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Utility Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Invoking the Move Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

JCL Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Performance Log Reblocker Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Syntax (CMS Statement) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Invoking the Performance Log Reblocker Utility in CMS . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Invoking the Performance Log Reblocker Utility in MVS . . . . . . . . . . . . . . . . . . . . . . . . . . 264

JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Reconfiguration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Reasons for Running the Reconfiguration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Considerations Before Running Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

DASD Considerations in a VM-only Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

How the Reconfiguration Utility Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Running a Successful Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Restore Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Reasons for Running the RESTore Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

How the RESTore Utility Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Special Considerations for Control Data Sets Processing Independently . . . . . . . . . . . . . . . 277

Utility Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Invoking the Restore Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

JCL Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

How to Handle BACKup/RESTore Discrepancies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Scratch Redistribution Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

How the Scratch Redistribution Utility Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Utility Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

x VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Invoking the Scratch Redistribution Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

JCL Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Scratch Update Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Utility Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Invoking the Scratch Update Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

JCL Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

SET Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

How the SET Utility Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Considerations Before Running the SET Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Summary of SET Utility Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Utility Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Invoking the Set Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

JCL Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Unselect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

Utility Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Invoking the Unselect Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

JCL Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Volume Report Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Media Type and Recording Technique Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Utility Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

JCL/Parameter File Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

JCL/Parameter File Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Invoking the Volume Report Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

JCL Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

Chapter 5. Problem Determination, Diagnostics, and Recovery . . . . . . . . . . . . . . . . . . . . 347

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

HSC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Contents xi

1st ed., 6/30/04 - 312579601

SCP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

HSC ABEND Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

SCP ABEND Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Software Trace Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

CP Trace Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

CCWTRACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

VM (CP) Debug Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

SCP SET TRACE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

SCP Internal Trace Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

IPARML (IUCV Parameter List) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

IUCV Interrupt Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

Diagnostic Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

SCP Trace Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

Supervisor Call and Abnormal End Dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

Error Recording Data Set Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

SCP External Trace Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

SCP Trace Formatter Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

Supervisor Call (SVC) Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

SCP GTRACE Emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372

HSC Internal Trace Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

HSC TRACE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Diagnostic Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

VM (CP) Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

SCP Debug Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

Setting Initialization Sequence Break-Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

SCP Diagnostic Subsystem Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

HSC Diagnostic Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

CDS Recovery Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

Control Data Set Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

Dump Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391

Type of Dumps Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391

How to Request a Dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391

What to do When a Dump Occurs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

Dump Analysis Using SLUIPCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

Major SCP Data Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400

Diagnostic Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

Common Dump Analysis Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

Chapter 6. Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

How Library Activity Affects Library Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

How Systems Programmers Control Library Performance . . . . . . . . . . . . . . . . . . . . . . . . . . 412

How Operators Control Library Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412

Monitoring Library Activity and Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412

Using the Activities Report Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412

xii VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Using the Performance Measurement and Predictive Maintenance System (PM2) . . . . . . . . 413

Redistribute Scratch Volumes in the Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

Maintain Quantities of Scratch Cartridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

Define CAP Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

Use SMF Records to Collect Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415

Use PARMLIB to Define Static Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415

Define High Dispatching Priority for the HSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

Set High-Performance Host-to-Host Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

Detailed Information about Host-to-Host Communications . . . . . . . . . . . . . . . . . . . . . . . . . . 417

Functioning of Host-to-Host Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

Designation of Communication parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

Define Secondary and Standby Control Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419

Limit View Time to Maintain High Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419

Excessive Use of VIew Command Affects Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

How to Monitor Usage of the VIew Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

Advantages of Using the VIew Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

Loading Cartridges Into the Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422

Loading Cartridges for Immediate Use in a Newly Installed LSM . . . . . . . . . . . . . . . . . . . . 422

Loading Cartridges for Later Use in a Newly Installed LSM . . . . . . . . . . . . . . . . . . . . . . . . . 422

Reduce Pass-Thrus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422

Unavoidable Pass-Thrus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

Unnecessary Pass-Thrus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

Scheduled Pass-Thrus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

Ways to Reduce Pass-Thru Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

Reduce Operator Intervention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

ACSPROP EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

Usage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

Reduce Scheduling Contention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

Use Performance Log Reblocker to Format Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

Use the Audit Utility Effectively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

Use LSMs as Scratch Loaders in a Mixed ACS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428

Appendix A. Macros, Control Statements, Utilities, and Commands Syntax Reference 429

Syntax Flow Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

Specifying Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

Delimiters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

Flow Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

Single Required Choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

Single Optional Choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

Repeat Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

Syntax Continuation (Fragments) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432

Library Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433

Contents xiii

1st ed., 6/30/04 - 312579601

How to Specify a CAPid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434

CAPid Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434

Ranges And Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436

Control Statement Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

MEDia, RECtech, and MODel Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441

LIBGEN Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444

SLIACS macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445

SLIALIST macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445

SLIDLIST macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445

SLIDRIVS macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445

SLIENDGN macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445

SLILIBRY macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446

SLILSM macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

SLIRCVRY macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

SLISTATN macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

HSC Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

Control Data Set Definition (CDSDEF) control statement . . . . . . . . . . . . . . . . . . . . . . . . . . 448

EXECParm control statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

Journal Definition (JRNDEF) control statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

LKEYDEF command and control statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449

LKEYINFO control statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449

LMUPATH control statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449

LMU Path Definition (LMUPDEF) command and control statement . . . . . . . . . . . . . . . . . 449

OPTion control statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450

Reconfiguration Definition (RECDEF) control statement . . . . . . . . . . . . . . . . . . . . . . . . . . 450

Scratch Subpool (SCRPOol) control statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450

Scratch Subpool Definition (SCRPDEF) command and control statement . . . . . . . . . . . . . 451

Tape Request (TAPEREQ) control statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451

Tape Request (TAPEREQ) control statement (continued) . . . . . . . . . . . . . . . . . . . . . . . . . . 452

Tape Request Definition (TREQDEF) command/control statement . . . . . . . . . . . . . . . . . . . 453

Unit Attribute (UNITATTR) control statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453

Unit Attribute Definition (UNITDEF) command/control statement . . . . . . . . . . . . . . . . . . . 454

Volume Attribute (VOLATTR) control statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454

Volume Attribute (VOLATTR) control statement (continued) . . . . . . . . . . . . . . . . . . . . . . . 455

Volume Attribute Definition (VOLDEF) command/control statement . . . . . . . . . . . . . . . . . 456

Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457

ACTIvities Report utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457

AUDIt utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457

BACKup utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

Database Decompile (LIBGEN) utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

Directory Rebuild (DIRBLD) utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

EJECt utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

EJECt utility (continued) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459

Enter Cartridges utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459

Journal OFFLoad utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460

MOVe utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460

xiv VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Reconfiguration utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460

REPLace utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460

RESTore utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461

SCRAtch utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461

Scratch Redistribution (SCREdist) utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462

SET utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463

UNSCratch utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464

Unselect utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464

Volume Report (VOLRpt) utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465

Operator Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

CAP Preference (CAPPref) command and control statement . . . . . . . . . . . . . . . . . . . . . . . . . 466

CDs Enable/Disable command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

CLean command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

Communications Path (COMMPath) command and control statement . . . . . . . . . . . . . . . . . 467

DISMount command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467

Display command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468

DRAin CAP command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476

EJect command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476

ENter command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478

Journal command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478

MODify command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478

MONITOR command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478

Mount command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479

Mount/Dismount Options (MNTD) command and control statement . . . . . . . . . . . . . . . . . . 480

MOVe command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481

OPTion command and control statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482

RECover Host command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482

RELease CAP command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482

SENter command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483

SRVlev (Service Level) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483

Stop Monitoring (STOPMN) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483

SWitch command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483

TRace command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484

TRACELKP command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484

Vary Station command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484

VIew command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485

Warn command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486

HSC Diagnostic Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487

LIst command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487

TRace command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487

SCP Operator Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488

* (comment) Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488

AUTHorize Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488

CANCEL command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488

CP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488

DEFine Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488

Contents xv

1st ed., 6/30/04 - 312579601

DUMP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488

FILE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489

HELP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489

Modify Command (SCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489

Query Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489

Reply Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490

SET Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490

SLK Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492

STArt Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492

STOP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492

STOPSCP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492

SUBSYS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492

GCS Component Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493

SLKGCS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493

CMS Operator Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494

ACS EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494

CMS HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494

Appendix B. CP Commands and DIAGNOSE Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

CP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

CP Programming Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

IUCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496

Appendix C. Record Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

Mapping Macros for SMF Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498

Mapping Macros for LOGREC Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498

Mapping Macros for Volume Report and Batch API Records . . . . . . . . . . . . . . . . . . . . . . . 498

Mapping Macros for Batch API Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498

SMF Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499

SMF Mapping Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499

SMF Record Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500

SLSDVAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500

SLSSFHDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501

SLSSBLOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506

SLSSCAPJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508

SLSSCAPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509

SLSSVSTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510

SLSSMLSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512

SLSSLSB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513

SLSSMF07 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515

SLSSMF08 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523

LOGREC Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525

LOGREC Mapping Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525

LOGREC Record Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526

xvi VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

SLSSLHDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526

SLSSVLG1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

SLSSBLOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533

SLSSLLG1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535

SLSSLLG2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540

SLSSLLG3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542

SLSSLLG4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543

SLSSLLG5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545

SLSSLLG6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548

SLSSDJLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553

SLSSPSWI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555

SLSSRL00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557

SLSSRL01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558

SLSSHLG1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559

Volume Report and Batch API Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562

Volume Report and Batch API Mapping Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562

Volume Report and Batch API Record Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563

SLUVADAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563

SLUVCDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571

SLUVHDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574

SLUVIDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577

SLUVSDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580

SLUVVDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582

Batch API Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593

Batch API Mapping Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593

Batch API Record Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594

SLUVDDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594

SLUVPDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598

Appendix D. Logging ACS Robotics Motion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603

Information Being Logged . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603

Robotics Motion Start Counts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603

Temporary Motion Error Counts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603

Permanent Motion Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604

How Information is Logged . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605

Logging Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609

Single-Host Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610

Multi-Host Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610

LMU Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611

Invalid Parameter Error Codes: 0101 - 0127 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612

Configuration Error Codes: 0201 - 0203 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613

CAP Procedural Error Codes: 0301 - 0310 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613

General Procedural Error Codes: 0401 - 0427 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614

LMU LAN Interface Error Codes: 0501 - 0512 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615

LMU Logical Error Codes: 0601 - 0620 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616

Contents xvii

1st ed., 6/30/04 - 312579601

LSM Robotics Error Codes: 0701 - 0718 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617

LSM Hardware Error Codes: 0801 - 0809 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618

LSM Logical Error Codes: 0901 - 0977 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618

Drive Error Codes: 1001 - 1011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620

Undefined Response Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620

Appendix E. Remote-linked Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621

Configuration 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622

Configuration 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623

Configuration 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624

Configuration 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625

Configuration 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626

Programming and Operational Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627

Appendix F. Batch Application Program Interface (API) . . . . . . . . . . . . . . . . . . . . . . . . . . 629

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629

QCDS Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629

How QCDS Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629

Invoking QCDS (SLSUREQ Macro) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629

Addresses and Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631

QCDS Programming Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633

Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634

Sample QCDS Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635

Output Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644

SLSUREQM Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645

Batch API Mapping (SLSUREQM) Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

xviii VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Figures

Figure 1. HSC Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Figure 2. Virtual Machine Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Figure 3. Shared Library Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Figure 4. HSC/Automated Cartridge System Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Figure 5. HSC Command Functions Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Figure 6. Utility Functions Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Figure 7. HSC Communication Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Figure 8. HSC Communication Methods Between Multiple Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Figure 9. Activities Report Utility Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Figure 10. AUDIt Utility Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Figure 11. BACKup Utility Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Figure 12. Database Decompile Utility Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Figure 13. EJECt Cartridge Utility Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Figure 14. Enter Cartridge Utility Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Figure 15. Journal Offload Utility Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Figure 16. MOVe Utility Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Figure 17. Restore Utility Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Figure 18. Scratch Redistribution Utility Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Figure 19. Scratch Update Utilities Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

Figure 20. Unselect Utility Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Figure 21. Volume Report SUMMary(TOTal) Sample Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Figure 22. Volume Report Utility SUMMary(SUBpool) Sample Output . . . . . . . . . . . . . . . . . . . . . . . . 344

Figure 23. HSC Internal Trace Table Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

Figure 24. Control Data Set Recovery Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

Figure 25. Command, Message and Trace Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

Figure 26. SCP Task/Job Data Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

Figures xix

1st ed., 6/30/04 - 312579601

Figure 27. Subsystem Data Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

Figure 28. Using LSMs as Scratch Loaders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428

Figure 29. Configuration 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622

Figure 30. Configuration 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624

Figure 31. Configuration 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625

Figure 32. Configuration 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626

Figure 33. Sample 1 - Automatic CDS Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636

Figure 34. Sample 2 - Reading ACS and DRV Together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641

xx VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Tables

Table 1. HSC Command Execution at Base and Full Service Levels . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Table 2. Utility Execution at Base and Full Service Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Table 3. MODel/RECtech Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Table 4. HSC/LMU Validity Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Table 5. TAPEREQ MEDia Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Table 6. TAPEREQ RECtech Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Table 7. VOLATTR MEDia Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Table 8. VOLATTR RECtech Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Table 9. Utilities Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Table 10. HSC Utilities and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Table 11. SLUADMIN Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Table 12. Label Descriptions for Devices in Output LIBGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Table 13. I/O Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Table 14. HSC State to Run SET Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Table 15. SET Utility Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Table 16. Mapping of Command Prefix Codes to Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

Table 17. HSC State/SET SLIDRIVS Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Table 18. SLSVA Effect on Volume Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Table 19. IUCV Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

Table 20. SVC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

Table 21. FIDs Used by SCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372

Table 22. Format of HSC Internal Trace Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

Table 23. HSC GTRACE USR Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Table 24. Subcommands for the SCAN Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

Table 25. VIEW-able SCP Data Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

Table 26. VIEW-able HSC Data Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

Tables xxi

1st ed., 6/30/04 - 312579601

Table 27. SLLUIPCS Print Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400

Table 28. Performance Parameters Controlled by PARMLIB Control Statements . . . . . . . . . . . . . . . . 415

Table 29. MEDia, RECtech, and MODel Cross-reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441

Table 30. Key to Record Format Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498

Table 31. Mapping Macros for SMF Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499

Table 32. SLSDVAR Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500

Table 33. SLSSFHDR Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501

Table 34. SLSSBLOS Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506

Table 35. SLSSCAPJ Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508

Table 36. SLSSCAPN Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509

Table 37. SLSSVSTA Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510

Table 38. SLSSMLSM Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512

Table 39. SLSSLSB Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513

Table 40. SLSSMF07 Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515

Table 41. SLSSMF08 Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523

Table 42. Mapping Macros for LOGREC Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525

Table 43. SLSSLHDR Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526

Table 44. SLSSVLG1 Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

Table 45. SLSSBLOG Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533

Table 46. SLSSLLG1 Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535

Table 47. SLSSLLG2 Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540

Table 48. SLSSLLG3 Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542

Table 49. SLSSLLG4 Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543

Table 50. SLSSLLG5 Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545

Table 51. SLSSLLG6 Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548

Table 52. SLSSDJLR Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553

Table 53. SLSSPSWI Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555

Table 54. SLSSRL00 Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557

Table 55. SLSSRL01 Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558

Table 56. SLSSHLG1 Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559

Table 57. Mapping Macros for Volume Report and Batch API Records . . . . . . . . . . . . . . . . . . . . . . . 562

Table 58. SLUVADAT Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563

Table 59. SLUVCDAT Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571

xxii VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Table 60. SLUVHDAT Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574

Table 61. SLUVIDAT Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577

Table 62. SLUVSDAT Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580

Table 63. SLUVVDAT Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582

Table 64. Mapping macros for Batch API Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593

Table 65. SLUVDDAT Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594

Table 66. SLUVPDAT Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598

Table 67. Format for Total Motions and Temporary Error Counts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605

Table 68. Record Format for a Hard Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608

Table 69. LMU Response Codes 0101 thru 0127 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612

Table 70. LMU Response Codes 0201 thru 0203 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613

Table 71. LMU Response Codes 0301 thru 0310 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613

Table 72. LMU Response Codes 0401 thru 0427 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614

Table 73. LMU Response Codes 0501 thru 0512 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615

Table 74. LMU Response Codes 0601 thru 0620 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616

Table 75. LMU Response Codes 0701 thru 0718 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617

Table 76. LMU Response Codes 0801 thru 0809 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618

Table 77. LMU Response Codes 0901 thru 0977 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618

Table 78. LMU Response Codes 1001 thru 1011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620

Table 79. LMU Response Code xxxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620

Table 80. Programming and Operation Precautions for Remote-linked Libraries . . . . . . . . . . . . . . . . . 627

Table 81. Batch API Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634

Table 82. Library Element Record Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644

Table 83. SLSUREQM Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646

Tables xxiii

1st ed., 6/30/04 - 312579601

xxiv VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

What’s New With This Release?

HSC 6.0 includes the following enhancements and modifications:

Enhancement/Modification

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

Operator’s Guide

Chapter 2, CAPPref, DRAin, EJect,
ENter, MODify, MOVe, RELease
CAP, VIew commands

Appendix B, HSC Support of the
SL8500

System Programmer’s Guide

Chapter 2, Mixing Media Types
and Recording Techniques

Publication(s)/

Primary Locations

Greater than 16 LSM support for each ACS. A maximum of 24 LSMs can be
specified.

A single license key can now enable multiple products. Installation Guide

Chapter 4, AUDIt , EJECt
Cartridge, Initialize Cartridge
utilities

Installation Guide

Chapter 6, SLIACS macro,

Operator’s Guide

Chapter 1

Chapter 8

System Programmer’s Guide

Chapter 3, LKEYDEF and
LKEYINFO control statements

What’s New With This Release? xxv

1st ed., 6/30/04 - 312579601

Enhancement/Modification

Publication(s)/

Primary Locations

The HSC mount/dismount component has been changed to allow any host to
mount or dismount a volume. Previously, only the mounting host could perform

System Programmer’s Guide

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
the VOLFLAG2 field. Under “FOR ERRANT VOLUMES,” the following has
been added:

VOLERMNT EQU X’02’ VOLUME IS MOUNTED. Mounted volumes

System Programmer’s Guide

Appendix C

now appear as “errant,” and the VOLERACT and VOLERMNT flags will be on.

Support for the T9840C and T9940B ESCON-connect drives. Installation Guide

Chapter 6, SLIDRIVS macro

Chapter 12, External Media
Requirements

Operator’s Guide

Chapter 2

System Programmer’s Guide

Chapters 3 and 4, Appendix D

Message changes, additions and deletions. Messages and Codes Guide

Chapter 2

xxvi VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Preface

Scope

This guide provides information about the Storage Technology Corporation
(StorageTek®) Host Software Component (HSC) and its use with the Automated
Cartridge System. Reference information is provided for systems programmers to install,
debug, and provide systems support to users of the HSC and the automated library

Intended Audience

This guide is intended primarily for systems programmers responsible for installing and
maintaining HSC software at their library sites. Library operators and computer system
administrators may also find information contained in this guide to be useful for reviewing
or understanding HSC system concepts.

Users responsible for installation and maintenance of HSC software involving the
technical details should be familiar with the following software topics:

• VM operating system

• ACF/VTAM functions and principles

•VMFMERGE.

Organization of This Guide

This guide contains the following chapters and appendices:

• Chapter 1, “System Description” provides a general overview of the Automated
Cartridge System (ACS) and the Host Software Component (HSC).

• Chapter 2, “Host Software Component Functions” describes major functional
components of the HSC. Items and functions described include: installation tasks,
initialization/termination, mount/dismount, volume/cell control, Cartridge Access
Port (CAP) processing, recovery, control data set renaming, commands, utilities,
LMU server, host-to-host communications, and tape management interface.

• Chapter 3, “HSC Control Statements and HSC Start Procedure” describes how
to define parameter library (PARMLIB) control statements and how to start HSC
execution.

Preface xxvii

1st ed., 6/30/04 - 312579601

• Chapter 4, “Utility Functions” describes control statement conventions for the
utilities and presents an overview description, syntax, JCL requirements, JCL
examples and a description of output for each utility. Example reports are shown for
those utilities producing activity-type reports.

• Chapter 5, “Problem Determination, Diagnostics, and Recovery” provides
overall diagnostic capabilities supported by the Host Software Component including
tracing, dumps, and logging failures.

• Chapter 6, “Performance Considerations” contains details on utilities and other
features that are available for use in refining overall library performance. Utility
syntax and parameter descriptions are included.

• Appendix A, “Macros, Control Statements, Utilities, and Commands Syntax
Reference” is a reference section containing: syntax conventions, LIBGEN macros,
parameter library (PARMLIB) control statements, utilities, and operator commands.

• Appendix B, “CP Commands and DIAGNOSE Codes” lists all CP commands
and DIAGNOSE codes that may be issued by the VM HSC.

• Appendix C, “Record Formats” contains record layouts for control data set
records, SMF records, and LOGREC records.

• Appendix D, “Logging ACS Robotics Motion” contains information about logging
library robot motions. Included is the type of information that can be logged, how
information is logged, and LMU response codes.

• Appendix E, “Remote-linked Libraries” presents typical remote-linked library
configurations, programming considerations, and operational considerations.

• Appendix F, “Batch Application Program Interface (API)” explains how to
retrieve CDS library element information in batch mode.

A glossary and index are also included.

How to Use This Guide

This guide may be read entirely; however, it is more important that you familiarize
yourself with the overall organization and location of various information for reference
purposes.

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. The HSC Installation Guide is used when installing the
HSC and may be referred to later. The remainder of the guide contains reference
information that you will refer to as needed.

xxviii VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

References to HSC Product Releases

For purposes of convenience, the HSC Release 6.0.0 product is referred to as HSC 6.0
throughout all guides of the HSC documentation set.

Related Publications

The following documents are referenced in this guide. Additional information may be
obtained on specific topics relating to the Automated Cartridge System from these
publications.

StorageTek HSC Publications - VM environment

• Installation Guide

• Operator’s Guide

• System Programmer’s Guide

• Interface to Tape Management Systems

• Messages and Codes Guide

• SCP Messages and Codes Guide

Miscellaneous Publications

• A Guide to Magnetic Tape Management

• Automated Cartridge System Hardware Operator’s Guide

• Hardware Operator’s Guide

• Requesting Help from Software Support

• Nearline Physical Planning Guide

• Physical Planning Guide

Reader’s Comments

We would like to know what you think about this book. E-mail your comments to
Software Information Development directly. Our Internet address is:

[e-mail]

Be sure to include the document title and number with your comments.

StorageTek Product Support

StorageTek Customer Services provides 24-hour assistance for questions or problems
related to StorageTek products. Calls from our customers receive immediate attention
from trained diagnostic specialists.

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.

Preface xxix

1st ed., 6/30/04 - 312579601

xxx VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Chapter 1. System Description

Automated Cartridge System Overview

The StorageTek Automated Cartridge System (ACS), called the library, is an automated
storage and retrieval facility for tape cartridges. The library incorporates the Host
Software Component (HSC) to accomplish automated mounting and dismounting of
resident cartridges for the library-attached cartridge transports. The library may be
attached to a maximum of 16 CPUs (hosts) with an HSC installed on each attached host
system.

The library consists of four major elements:

• Host Software Component (HSC)— functions as the interface between the host
operating system, and if applicable, a tape management interface (TMI).

• Library Storage Module (LSM)— contains storage cells for tape cartridges. The
storage capacity of an LSM depends upon the LSM model. There are several LSM
models available:

- Standard (Model 4410)

- PowderHorn (Model 9310)

- WolfCreek (Model 9360), which includes:

- 9360-100 (1,000 cartridge capacity)

- 9360-075 (750 cartridge capacity)

- 9360-050 (500 cartridge capacity)

- TimberWolf (Model 9740)

- StreamLine (Model 8500).

An attached Library Control Unit (LCU) with associated electronics controls LSM robot
movement. The LSM access door, contains a Cartridge Access Port (CAP), for entering or
removing tape cartridges from the LSM. The types of CAPs available, depending upon
how the LSMs are configured in an ACS, include:

- Standard and Enhanced CAP used in standard (4410) and PowderHorn (9310)
LSMs.

- WolfCreek (9360) standard 20-cell and optional 30-cell CAPs. The WolfCreek
LSM holds approximately 500, 750, or 1000 cartridges depending on the
number of cartridge drives, pass-thru ports, and CAPs installed.

Chapter 1. System Description 1

1st ed., 6/30/04 - 312579601

- TimberWolf (9740) 10-cell removable magazine or 14-cell permanent rack
CAP

- StreamLine (8500) includes 3, 13-cell removable magazines. An optional
39-cell CAP can be added.

The complete inventory of each LSM and the storage location for each cartridge is
contained in the library control data sets maintained by the HSC.

• Library Management Unit (LMU)— controls the Library Storage Modules
(LSMs) in the ACS. The LMU interprets the commands from the host and relays the
instructions to an LSM for execution. One LMU can control up to 24 LSMs.

• Tape Cartridge Subsystem— consists of the tape cartridge drives containing tape
transports where tape cartridges are placed by the robot for read or write operations.

2 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Host Software Component Overview

The HSC performs a variety of functions including:

• assisting the tape management system in device allocation

• processing mount and dismount requests

• delivering library mount/dismount instructions to the LMU via a terminal control
unit

• providing exits at key points

• providing for operator control of the library through a set of operator commands and
utility programs

• determining the LSM location of each library cartridge from the library control data
set (CDS).

• providing a programmatic interface for library control.

Integrity of the control data set can be assured through the following techniques employed
at an installation:

• allocating secondary (shadow) and standby data sets in addition to the primary
control data set

• scheduling regular backups of the control data sets

• utilizing journal data sets to log library transactions.

After processing a mount or dismount request from the tape management system, the HSC
issues cartridge movement requests to an LMU station via the terminal control unit. The
LMU relays information to the Library Control Unit (LCU) enabling the robot in the LSM
to locate and mount/dismount the requested cartridge.

In a dual LMU environment when the master LMU fails, the standby LMU takes over. The
standby LMU completes the work in progress and services all future ACS requests.

Chapter 1. System Description 3

1st ed., 6/30/04 - 312579601

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.

• Common Components — Common components provide distinct functions required
by the external and common components. The common components consist of the
mount/dismount components, the CAP component, and the recovery component.

• Control Components — Control components provide logical control over system
entities used by both common components and external components. The control
components consist of the volume/cell control component and the configuration
control component.

• Server Components — The server components provide physical control of system
entities for the control components. The server components consist of the data base
server, the LMU server, the WTO component, and the address space communications
server.

HSC Architecture

Note: In this discussion, address space refers to a virtual machine.

Figure 1 on page 5 displays external components located in the user’s address space on the
left side, and other HSC components located in the HSC’s address space on the right side.

Note: The initialization/termination external component resides entirely in the HSC
address space.

The Address Space Communications Server spans the user’s address space and the HSC
address space. It handles requests from components in the user’s address space that require
services from components located in the HSC’s address space.

The following section briefly describes the functions of each external component.

Operator Command component

Batch Utilities external component

The operator command component receives control from other virtual machines to
process an HSC command or to call upon services in the HSC.

The utility component exists mostly within the service machine. However, a few
utilities execute in the invoker’s CMS virtual machine.

4 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

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

ADDRESS

SPACE

HSC ADDRESS SPACE

HSC STARTUP

COMMAND

(S SLS)

SUBSYSTEM

COMMANDS

BATCH

UTILITIES

TAPE

MANAGEMENT

INTERFACE

(TMI)

INITIALIZATION

/TERMINATION

APPLICATIONS

A
D
D
R
E
S
S

S
P
A
C
E

C
O
M
M
U
N

I
C
A
T

I
O
N
S

S
E
R
V
E
R

OPERATOR

COMMANDS

COMMON

MOUNT/

DISMOUNT

DATA
BASE

SERVER

COMMON

SERVICES

CONTROL

VOLUME/

CELL

CONTROL

SERVERS

UTILITIES TMI

COMMON

CAP

COMMON

PROCESSING

LMU

SERVER

COMMON

CONFIGU-

RATION

CONTROL

RECOVERY

WTO

COMMUNI-

COMPONENT

COMMON

CATIONS

Figure 1. HSC Architecture

C46096

Chapter 1. System Description 5

1st ed., 6/30/04 - 312579601

VM Environment

The VM version of the HSC product is the implementation of the ACS Host Software
Component (HSC) product on VM. The principal interfaces and components under VM
are:

• VM Operating System (CP and CMS)

• The System Control Program (SCP)

• The Host Software Component (HSC)

• The tape management system (TMS)

• Operators and utility users.

VM Operating System (CP and CMS)

VM HSC requires relatively few system services. The VM system services that are used
are:

• Spool files

• Inter-User Communications Vehicle (IUCV)

• IUCV-based services *MSG and *BLOCKIO

• Diagnose

CMS

•RSCS

• VMDUMP Storage Dumps

• Interactive Problem Control System (IPCS) for VM/SP, or Dump Viewing Facility
for VM/XA and VM/ESA

• CMS (at initialization only).

The first portion of the SCP initialization process is executed under CMS. During this time
various files are read and some control data set locations are noted for reference. After the
program modules have been loaded into storage and the major control blocks have been
created, CMS is replaced by the SCP.

6 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

System Control Program (SCP)

The service virtual machine executes a proprietary System Control Program which
provides a small subset of MVS services that include the following major components:

• Storage management

• Device management

• File management

• Task management

• Job management

• Processor management

• Communication

• Inter-machine communication

• Task recovery/termination.

Storage Management

The storage managed by the SCP is a single ‘‘real’’ storage range; no virtual storage
management is performed. The maximum amount of storage that is available to a user is
16 megabytes, but in actual practice 8 megabytes may be sufficient. Any paging or page
faults are managed by VM and are transparent to the virtual machine. The SCP associates
storage keys with ‘‘JOBS’’. VM job steps are mapped to unique storage keys. Storage
Management is a matter of managing available storage and allocating and deallocating
storage through standard macro calls.

Device Management

This component has exclusive control over SCP driven I/O activity to virtual devices.
IUCV is the interface to the DASD data sets which are accessed through requests to the
CP BLOCKIO service (using device I/O mainly for the Reserve-Release mechanism).
Other devices include several spool files for console, diagnostic, and performance logs,
and DASD I/O for minimal use. Also included with this component is the function of
logging unsuccessful attempts to log errors to the Error Recording Data Set (ERDS).

File Management

The SCP supports several access methods:

• Sequential (BSAM/QSAM) for spooled unit record input/output and DASD
input/output

• Direct (BDAM) for data base manipulation.

BSAM/QSAM is supported through EXCP processing of channel control word (CCW)
chains. BDAM files are accessed through IUCV communication to CP DASD BLOCKIO.
The requests are converted from a relative block to a physical block on DASD which is
passed to BLOCKIO.

No DASD file allocation is performed. All DASD data sets must be preallocated
OS-format data sets or CMS ‘‘reserved’’ minidisks.

Chapter 1. System Description 7

1st ed., 6/30/04 - 312579601

Task Management

Multi-tasking is provided by the SCP to support the MVS-type task requests such as
POST, WAIT, ATTACH, etc. that the HSC expects. All modules are made resident at the
time of initialization. Also included in this component is the processing of System
Management Facility (SMF) records for output to a spool file.

Job Management

Most utilities are executed within the SCP environment as batch jobs punched by other
virtual machines. Special job statements define both the resources to be used and the
parameters to be passed to the desired program.

Processor Management

This component handles the resources of the virtual processor, including:

• interrupt handlers

• timer management

• IUCV paths and messages

• event tracing.

This component also handles authorization checking and PSW mode changing. Interrupts
consist of common processing, a first level handler which usually sorts out the interrupt
subtypes, and a second level handler which does the bulk of the processing. Timer services
include the TOD clock, the TOD clock comparator, and the CPU timer. Tracing includes
an internal table and a task which writes records to a spool file.

Communication

Standard MVS-type WTO/R and related operator communications are also supported,
with limitations on the routing and descriptor codes. The QEDIT interface, ECBs, and
various queues provide for inter-task communication.

Inter-Machine Communication

The Inter-User Communication Vehicle (IUCV) is a closed-loop technique used in VM to
communicate between users. A user sends an IUCV message and waits for a reply. This
service is used to transfer data between the HSC and the TMS.

Additionally, IUCV is used to access the BLOCKIO and MESSAGE system services. The
message service (*MSG) is used to intercept SMSG communications from operators.CP
DASD BLOCKIO forms the foundation of the SCP BDAM access method. BLOCKIO
reads and writes data to any DASD device with device independence, but the SCP must be
aware of the device type, especially when the data set is shared with an MVS host.

8 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Task Recovery/Termination

Task recovery is concerned with resource recovery, possible retry operations, and the
logging of software-detected errors. Terminations can be considered a special case of
recovery where resources must still be recovered but no retry or logging is necessary. The
SCP supports the most common ESTAE and ESTAI options and major SDWA fields.
Recovery includes a disabled and enabled (scheduled task) mode. The resources being
recovered are files to be closed, storage to be released, tasks to be terminated, and
messages and scheduled interrupts to be cancelled.

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.

Tape Management System (TMS)

The TMS uses the IUCV interface to communicate with the virtual machine. It provides a
front end between the HSC and the user, and provides allocation, mount, and scratch pool
services. The HSC provides the TMS with mount/dismount service and assists it in
allocation for those volumes and drives which are under library control.

Note: In this document ‘‘TMS’’ is used to refer to any tape management system and not
any particular product.

Operators and Utility Users

Operators use CP SMSG to communicate with the SCP via the CP Message System
Service (*MSG). Utility users communicate with the SCP via punch spool files containing
special control statements. The authorization services allows only specified users to access
either of these interfaces; unauthorized users are disconnected from the service machine
when any attempt is made to communicate with the subsystem.

Virtual Machine Configuration

Within a VM host system the following virtual machines (users) exist:

• operator(s)

• ACS service machine (SCP and HSC)

• TMS service machine

• administrator(s)

• TMS requestors.

Various illustrations are provided to show relationships. Figure 2 on page 11 illustrates the
relationship of users to each other and the virtual machine and hardware relationships.

Figure 3 on page 12 illustrates how the library data sets may be shared by multiple,
dissimilar host systems.

Chapter 1. System Description 9

1st ed., 6/30/04 - 312579601

HSC and Automated Cartridge System Interaction

After the HSC is started and the tape management system (TMS) service machine has
begun a dialog, mount or dismount requests are processed from the TMS, and the library
control data set is used to determine the location of the requested cartridge
(library-controlled or nonlibrary).

The library control data set is created on a DASD volume when you perform a data set
initialization during installation. Figure 4 on page 14 shows that it is necessary to share the
control data set between all hosts requiring access to the library.

10 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

VM HOST A

TMS

REQUESTOR

(CMS)

NONLIBRARY

TAPE

DRIVE

LSM

CD

TMS

SERVICE

MACHINE

PRIMARY
CONTROL
DATA SET

SECONDARY

CONTROL
DATA SET

ADMINISTRATOR

ADMINISTRATOR

(CMS)

STANDBY
CONTROL
DATA SET

LMU

TERMINAL
CONTROL

3174/3274

UNIT

HSC

ACS
SERVICE
MACHINE

SCP

RSCS

LMU

OPERATOR

OPERATOR

(CMS)

VM HOST B

OPERATOR

Figure 2. Virtual Machine Relationships

RSCS

ADMINISTRATOR

C27925

Chapter 1. System Description 11

1st ed., 6/30/04 - 312579601

VM/XA HOST VM/SP HOST

MVS HOST

ACS

MVS/XA

GUEST

JOURNAL

JOURNAL

SERVICE

MACHINE

Figure 3. Shared Library Data Sets

Automated cartridge mounts/dismounts are performed in response to calls to the tape
management interface. The HSC determines that a mount/dismount is required for a
volume under automated library control (cartridge resides in an LSM storage cell), and it
communicates with the appropriate LMU.

ACS

SERVICE

MACHINE

PRIMARY

CONTROL

DATASET

MVS/XA

(JES2 OR JES3)

SECONDARY

CONTROL

DATASET

STANDBY

CONTROL

DATASET

JOURNALJOURNAL

C29335

If the request is for a mount, the following information is communicated to the LMU:

• the LSM and panel/row/column in which the volume resides

• the destination LSM (where the volume is to be mounted on a transport).

If all drives in an LSM are busy, a cartridge can be moved to another LSM to satisfy the
mount request. This action is performed without operator intervention, since the pass-thru
port (PTP) makes the cartridge available to the attached LSM.

If the request is for a dismount, this information is passed to the LMU:

• the LSM, cartridge drive, and transport in which the volume resides

• the destination (storage cell, CAP, or PTP) of the cartridge.

12 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Automated Mount

Figure 4 on page 14 shows the LMU communicating with the LSM through LAN 0. In this
illustration, LAN 1 is represented as the backup used in case of a LAN 0 failure.

Note: The HSC can select either LAN for communications with the LSM(s). Whichever
LAN is not picked becomes the backup.

Within the LSM, the robot’s hands are positioned to the correct panel/row/column
cartridge location. The external Tri-Optic label is verified by the robot’s vision system, the
robot’s hand extends, and the hand grasps the cartridge from its storage cell. The robot’s
hand retracts with the cartridge and the robot moves to the appropriate position.

(PTP cell or transport). The robot hand extends and the cartridge is positioned and released
at its destination (PTP cell or transport).

If the destination is a PTP cell, the cartridge is made available to the adjacent LSM, and
the process repeats until the cartridge is placed in a transport.

Automated Dismount

An automated dismount is the reverse of the mount procedure. The LMU communicates
with the LSM via the LAN, and the robot’s hands are positioned at the transport to be
dismounted. The external Tri-Optic label is verified using the vision system. A hand is
extended and the cartridge is grasped from the transport. The hand retracts with the
cartridge and the robot is moved to the cartridge’s destination. The hand is extended and
the cartridge is positioned and released into the storage cell.

Chapter 1. System Description 13

1st ed., 6/30/04 - 312579601

PRIMARY

CONTROL

DATA SET

SECONDARY

CONTROL
DATA SET

STANDBY
CONTROL
DATA SET

JOURNALS

HOST 1 HOST 2

3274

CONTROL UNIT (0)

HOST 3

3274

CONTROL (7)

HOST 16

(STATIONS 1 - 16) (STATIONS 1 - 16)

LMU 0

LAN 0 LAN 0LAN 1 LAN 1

LOCAL

AREA

NETWORK

LMU 255

LOCAL

AREA

NETWORK

LSM 0

CD CD

ACS 0

Figure 4. HSC/Automated Cartridge System Interaction

14 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

LSM 0LSM 15 LSM 15

CD CD

ACS 255

C27409

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. For more information about the MNTD Float command,
refer to Chapter 2, ‘‘Commands, Control Statements, and Utilities’’ in the HSC
Operator’s Guide.

• If the MNTD Float command is set to OFF, the cartridge is passed through to the
origin LSM and placed into its originating cell location. For more information about
the MNTD Float command, refer to Chapter 2, ‘‘Commands, Control Statements,
and Utilities’’ in the HSC Operator’s Guide.

• If the LSM is full, the cartridge is passed thru to another LSM and placed in any cell
location.

• A temporary enter on a mount operation means an eject upon dismount (the cartridge
does not remain in the LSM).

The library control data set is automatically updated to reflect the new location of the
cartridge.

Dual LMU Environment

In a dual LMU environment, the HSC maintains contact with both LMUs. Both LMUs are
varied online. One LMU functions as the master LMU and the other functions as the
standby LMU. Requests and responses are channeled through station paths on the master
LMU. Paths on the standby LMU are online, but not used.

The master LMU continually informs the HSC of the status of the standby LMU. The
HSC informs the operator when status changes.

The standby LMU constantly polls the master LMU. If the master LMU fails, the standby
LMU informs the HSC that status has changed. The standby becomes the master. The
HSC also informs the operator that the previous master LMU is not communicating.

At switchover, the HSC:

• notifies the operator that switchover is occurring

• verifies the configuration for the LMU

• sends the new master LMU all the work that was in progress

• terminates ENTER operations.

After switchover, the HSC sends the new master all ACS requests.

Switchover should not affect movement in process. All moves should complete. If not, the
cartridges become errant and are found when the LSMs perform ‘‘quick initialization’’
processing. ENTER operations must be restarted after switchover.

Chapter 1. System Description 15

1st ed., 6/30/04 - 312579601

User Control of HSC Functions

Various controls are in place in the HSC software to permit you to select how the HSC
functions. Macros, Utilities, and PARMLIB control statements are normally used by the
systems programmer to tune and customize the system. Commands are normally invoked
by a systems operator in the performance of daily operations tasks. A description of the
function of each of these available controls follows.

Macros

Macros are provided primarily to help you set up the library software configuration
or library generation (LIBGEN).Refer to Chapter 6, ‘‘Creating the Library
Configuration File (LIBGEN)’’ in the HSC Installation Guide for detailed
information about the LIBGEN macros and how they are used to configure a library.

Utilities

Utilities are provided to allow you to manage library resources. The utilities enable
you to dynamically:

• perform maintenance on control data sets

• control cartridge and scratch volume functions

• produce performance, activity, and inventory reports relating to a library.

Refer to Chapter 4, “Utility Functions” on page 169 for detailed information about
the HSC utilities and how they are used to manage library resources.

PARMLIB Control Statements

PARMLIB control statements are provided to enable you to set initial values for
system functions at HSC initialization. The PARMLIB control statements define
HSC functions such as:

• host-to-host communications parameters

• definition of scratch subpools

Note: Refer to “Options Offered by PARMLIB Control Statements” on page 84
for an important warning about defining scratch subpools.

• data set definitions including: the primary, secondary, standby control data sets,
and journals

• extended parameter list for startup.

Refer to “PARMLIB Control Statements” on page 83 for detailed information about
the control statements and usage.

16 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Commands

Operator commands are available for Systems Operators to use in daily library
operation to perform various tasks. Commands perform such functions as:

• assigning a preference to a specific cartridge access port (CAP)

• displaying system status, such as control data set status, ACS, LSM, and
volume status

• entering, ejecting, mounting, and dismounting cartridges

• setting of system parameters.

Refer to the HSC Operator’s Guide for information about HSC operator commands
and usage.

Chapter 1. System Description 17

1st ed., 6/30/04 - 312579601

18 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Chapter 2. Host Software Component Functions

Overview of HSC Functions

This chapter describes the basic function of the HSC. Functions for each of the HSC
components fit within the architecture structure presented in Figure 1 on page 4. Not all of
the components of the architecture structure have functions directly visible to you. Only
those HSC functions that you can control or those that are operationally apparent are
described in this chapter.

System functions relating to HSC architecture components represented in Figure 1 on
page 5 include:

• installation

• initialization/termination

• mount/dismount processing

• volume/cell control

• CAP processing

• common recovery

• command

• utility

• LMU server

• communications

• tape management interface (TMI)

• batch application program interface.

The Automated Cartridge System provides the facilities and software to perform various
functions with or without operator intervention. Such major system functions are
described in this chapter.

Automatic Functions of the HSC

Among the functions handled automatically by the HSC are:

• mounting and dismounting of cartridges

• automatic and manual operating modes

• handling of abnormal situations occurring during mounting or dismounting of
cartridges

• Cartridge Access Port processing to allow the operator to enter or remove cartridges

• tape management system assistance

Chapter 2. Host Software Component Functions 19

1st ed., 6/30/04 - 312579601

• automatic cleaning of tape transports with cleaning cartridges under the control of
the HSC and the library

• restricting the write access to volumes in the library through the Virtual Thumbwheel
feature

• dual LMU support

• control data set recovery.

Facilities Available for User Control of HSC Functions

There are facilities available for system programmers and operators to use to control
various system functions. These include:

•macros

• utilities

• PARMLIB control statements

• operator commands.

Installation Functions

Installation functions pertain to installation or reconfiguration processing for the HSC
subsystem. Since these topics are extensive, they are presented in a separate document.
The HSC Installation Guide presents detailed information about installation planning and
instructions, including:

• Planning the configuration

• Performing preinstallation procedures

• Installing HSC software

• Defining the library configuration (LIBGEN)

• Defining PARMLIB control statements

• Initializing the control data sets

• Verifying library generation

• Starting HSC execution

• Testing the installation

• Planning and executing cartridge migration into the library

• Migration planning

• Performing library modifications.

20 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

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. Operation flexibility is provided at a base service level
to tolerate failures in certain isolated areas without impacting the functions of other
sections of the HSC or your entire data center. Overall, this fault-tolerant HSC gives you
greater availability of your automated library and lessens the need to shutdown and
reinitialize. The HSC subsystem operates at two service levels:

Base service level

provides minimal functionality keeping the HSC running while having the capability
of applying software maintenance or altering the subsystem parameters at the same
time. This level is the lower level of functionality.

Full service level

provides full functionality of the HSC.

Normally the HSC initializes to the full service level when started. HSC can be started at
the base service level by specifying the BASE parameter in the startup SLKJCL file. Refer
to “Initializing the HSC to the Base Service Level” on page 129 for more information
about HSC startup.

Description of Base Service Level

The base service level is the nucleus of the HSC subsystem. It involves the functions
necessary to execute as an extension of the operating system. The service level and its
functions satisfy the requirements defined by the operating environment in place at the
time of execution. Base service level functions include the capabilities to:

• issue subsystem commands

• execute certain utilities

• access the control data sets

• support the operating system interfaces and front-ends and maintain HSC
host-to-host communications.

All operator commands can be issued with the HSC executing at the base service level.
However, the commands which involve library hardware cannot perform their function
completely. Table 1 on page 21 indicates which commands have complete functionality at
the base service level.

Table 2 on page 22 indicates which utilities can be executed at the base service level.

Chapter 2. Host Software Component Functions 21

1st ed., 6/30/04 - 312579601

Description of Full Service Level

The full service level of operation for the HSC provides all of the functions available and
necessary to invoke and sustain complete library operations. These functions include:

• mount/dismount processing

• CAP processing

• cartridge and cell inventory management

• LMU access

• library resource recovery

• support for utilities which require services from the hardware

• support for the tape management interface.

At initialization, the HSC builds data areas, loads program modules, and sets up the
required operating system services to support the two service levels of operation.
Termination of the HSC, including normal termination and abnormal termination through
abends removes the service level structure and services.

For example, on your system with the HSC operating at full service level, all commands,
utilities, etc. are fully functional. Should you decide to manually intervene by issuing the
Service Level command (SRVlev) to change from full to base service level, the
functionality of the HSC is reduced. Refer to ‘‘Adding SMF Parameters’’ in the HSC

Installation Guide.

Conversely, you can change the base service level operation to full service level.

22 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Table 1. HSC Command Execu t io n at Base and Full Service Levels

Service Level Execution

Command

Base Full

CAPPref NO YES

CDs YES YES

CLean NO YES

COMMPath YES YES

DISMount NO YES

Display

YES

*

YES

DRAin NO YES

EJect NO YES

ENter NO YES

Journal YES YES

LIst YES YES

MNTD NO YES

MODify (F) NO YES

MONITOR (MN) YES YES

Mount NO YES

MOVe NO YES

OPTion YES YES

RECover NO YES

RELease NO YES

SENter NO YES

SRVlev YES YES

STOPMN (PM) YES YES

SWitch NO YES

TRace YES YES

TRACELKP YES YES

Vary NO YES

VIew NO YES

Warn NO YES

* Display options that require hardware interaction are not valid at the base
service level.

Chapter 2. Host Software Component Functions 23

1st ed., 6/30/04 - 312579601

Table 2. Utility Execution at Base and Full Service Levels

Service Level Execution

Utility

Base Full

AUDIt NO YES

BACKup YES YES

EJECt NO YES

ENTEr NO YES

LIBGen YES YES

MOVe NO YES

OFFLoad YES YES

REPLaceall YES YES

RESTore NO NO

SCRAtch YES YES

SCREdist NO YES

SET YES YES

UNSCratch YES YES

UNSElect YES YES

VOLRpt YES YES

24 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

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.

Starting the HSC Subsystem at Base Service Level

If the HSC and the library are new to your data center, you may want to install the HSC
software and start the subsystem at the base service level before your library hardware is
physically installed. Starting the HSC at the base service level allows you to perform
many of the preliminary tasks involved in configuring your library and performing
preliminary tests on basic operation.

Normally the HSC subsystem is initialized to the full service level when started. The HSC
can be started at the base service level only by specifying the BASE parameter in the
startup SLKJCL file. Then, the Service Level (SRVlev) command can be used to bring the
HSC to full service level whenever you are ready.

Refer to “Initializing the HSC to the Base Service Level” on page 129 for information
about setting the service level at HSC initialization.

Chapter 2. Host Software Component Functions 25

1st ed., 6/30/04 - 312579601

Media Type and Recording Technique Processing

When a job requests specific media type and recording technique, the HSC uses
information provided by TAPEREQ control statements to select a cartridge with the
appropriate media type and influence the tape management system to allocate a transport
with the requested recording technique.

26 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

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. Parameter values associated with MEDia and RECtech, and their
hierarchy, are shown in the following figure:

MEDIA TYPES RECORDING TECHNIQUES

18TRACK

LONGITUD

HELICAL

STK1

STK2

STANDARD

ECART

ZCART

DD3

STK1R

STK1U

STK2P

STK2W

DD3A

DD3B

DD3C

DD3D

LONGITUD

36TRACK

HELICAL DD3

STK1R34

STK1R35

STK1RA

STK1RA34

STK1RA35

STK1RB

STK1RB34

STK1R

STK1RB35

STK1RAB

STK1RAB4

STK1RAB5

STK1RC

STK1RC34

STK1RC35

STK2P34

STK2P35

STK2P

STK2PA

36ATRACK

36BTRACK

36CTRACK

STK2PA34

STK2PA35

STK2PB

STK2PB34

STK2PB35

Chapter 2. Host Software Component Functions 27

1st ed., 6/30/04 - 312579601

Model Parameter

The MODel parameter is specified on the TAPEREQ and UNITATTR statements. MODel
values are processed as if they were RECtech values. UNITATTR control statements do
not use the RECtech parameter. Table 3 shows the relationship between MODel and
RECtech parameters.

Table 3. MODel/RECtech Translation

MODel Resulting RECtech

4480 18track

4490 36Atrack

9490 36Btrack

9490EE 36Ctrack

SD3 DD3

9840 STK1R34

984035 STK1R35

T9840B STK1RB34

T9840B35 STK1RB35

T9840C STK1RC34

T9840C35 STK1RC35

T9940A STK2PA34

T9940A35 STK2PA35

T9940B STK2PB34

T9940B35 STK2PB35

28 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Matching VOLATTR and TAPEREQ Statements

The type of request (specific or nonspecific) determines whether the HSC uses media type
and recording technique information from the VOLATTR statement or the TAPEREQ
statement. (See “Precedence of VOLATTR and TAPEREQ Statements” for additional
information.)

The statements are searched until matches are found for both the media type and recording
technique. The first control statement that matches the selection (input) criteria is used;
there is no attempt to determine the ‘‘best’’ match.

Since MEDia and RECtech parameters may or may not be specified on a single
TAPEREQ or VOLATTR control statement, one of the following conditions results:

• Both media type and recording technique are provided by one control statement.

• Media type is provided by one TAPEREQ statement and recording technique is
provided by another TAPEREQ statement.

• Media type is provided by one VOLATTR statement and recording technique is
provided by another VOLATTR statement.

• Media type is provided by a VOLATTR statement and recording technique is
provided by a TAPEREQ statement.

• Media type is provided by a TAPEREQ statement and recording technique is
provided by a VOLATTR statement.

As a result of determining the precedence of media and recording technique information
between the VOLATTR and TAPEREQ statements, ‘‘final’’ media type and recording
technique values are produced. The final media type and recording technique are
compared to the aggregate media type and recording technique of the EDL. If an
inconsistency is detected, a message is issued to this effect, and the media type and
recording technique of the EDL are used. If the final media and recording technique are
consistent with the 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.

Chapter 2. Host Software Component Functions 29

1st ed., 6/30/04 - 312579601

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
the TAPEREQ statement.

If the VOLATTR statement provides a value for RECtech, then that recording technique is
used, but the TAPEREQ statement can ‘‘refine’’ the RECtech value. For example, the
VOLATTR statement specifies a recording technique of 36track, and the TAPEREQ
statement specifies 36Btrack, then 36Btrack is used.

Nonspecific Volume Requests

Note: When mixing media types, the user must define VOLATTR statements because
scratch counts are determined entirely from VOLATTR information.Accurately defined
VOLATTR statements are critical for correct processing of nonspecific volume requests.

The HSC analyzes the TAPEREQ information to determine the required media type and
recording technique, and then tries to locate available scratch volumes in the library that
match these values. If no matching scratch volumes are available, HSC rejects the request.

Scratch Selection

Scratch volumes are segregated by means of scratch subpooling with VOLATTR
statements. Assuming that requested subpool definitions do not conflict with the
applicable VOLATTR statements, the HSC provides the following services to satisfy a
request:

• If scratch volumes are segregated by defining subpools and specifying VOLATTR
statements, the HSC ensures that a volume with the appropriate media type is
selected from the correct subpool.

• If scratch volumes are segregated only by defining subpools, the HSC selects a
standard cartridge from the correct subpool. A standard cartridge is selected because
this is the default when VOLATTR statements are not defined.

• If volumes are segregated only by specifying VOLATTR statements, the HSC
ensures that a volume with the appropriate media type is selected.

30 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

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:

• there are no scratch cartridges in the ACS

• there are no scratch cartridges in the requested subpool in the ACS

• there are no scratch cartridges of the requested media type or recording technique in
the ACS

• there are no scratch cartridges of the requested media type or recording technique in
the requested subpool in the ACS.

The message identifies the media type (MMMMMMMM), recording technique
(RRRRRRRR), and subpool (SSSSSSSS) of the scratch shortage.

Note: If the subpool name indicates “SUBPOOL 0”, this means one of the following:

• scratch subpooling is in effect and no subpool was specified

• scratch subpooling is not in effect.

If the recording technique specified in the request is 18-track, then the media type must be
standard capacity with a recording technique of 18track, LONGItud, or not specified.

Chapter 2. Host Software Component Functions 31

1st ed., 6/30/04 - 312579601

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.

If a scratch volume is requested from a specific subpool, then a scratch cartridge of the
requested media type must be entered into that subpool in the ACS.

32 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Mount/Dismount Functions

Mount and dismount functions consist of the following processing:

• mounting specific volumes

• mounting scratch volumes

• dismounting library volumes

• handling abnormal mounts and dismounts

• virtual thumbwheel (VTW)

• automated tape transport cleaning.

The mount/dismount component receives the request sent by the tape management
interface component and makes the mount/dismount of cartridges occur.

Each mount/dismount function is described in this section.

Several options exist to allow users to specify how they want mount/dismount to react in
various situations. Refer to the ‘‘MNTD (Mount/Dismount Options) Command and
Control Statement’’ in the HSC Operator’s Guide for a description of these options.

Mount Processing for Specific Volumes

The HSC determines when a library volume is to be mounted on a library-controlled
transport. It maintains a record of the library location for each cartridge and instructs the
LMU to mount the requested cartridge on the selected transport.

Mount processing occurs as a result of:

• the tape management system (TMS) interpreting a request for library transports

• issuance of the HSC operator Mount command

• change of the HSC from base service level to full service level

• startup of an HSC subsystem

• a clean request.

A volume may be temporarily or permanently entered into the library to satisfy a mount on
a library transport. If a volume is temporarily entered into an LSM, a notation is made in
the library control data set for this volume to be automatically ejected, via a CAP, when
the volume is dismounted.

Chapter 2. Host Software Component Functions 33

1st ed., 6/30/04 - 312579601

Mount Processing for Scratch Volumes

To process scratch mount requests, the HSC determines which volumes within an LSM
are considered as scratch volumes. The HSC makes the determination from information
contained in the library control data set.

Note: A scratch tape is marked as nonscratch when it is mounted even if it is not written
on.

Normally, only requests for nonspecific VOLSERs and the appropriate label type (as
defined in the LIBGEN) are considered as requests for scratch volumes. However, the
HSC allows selection of scratch volumes from different scratch subpools and different
label types via interaction with the TMI.

In addition, other means are available for controlling scratch volume activity. These are at
the operator command and programmer utility levels. Refer to “Scratch Subpool
Management” on page 39 for more information.

To minimize pass-thru movement of the scratch cartridges, the HSC always orders drives
for selection in ascending order by scratch count.

The scratch status of cartridges listed in the library control data set is updated through the
use of the Scratch Update utility. The Scratch Update function accepts a list of volume
serial numbers for addition to, or deletion from the control data set’s list of scratch
volumes. If desired, the entire scratch list may be deleted by using the Scratch Update
utility.

Dismount Processing for Library Volumes

The HSC determines when a library volume is to be dismounted from a library transport.
Dismount processing occurs as a result of:

• a tape management interface request identifying library transports, or

• issuance of the HSC operator DISMount command

• the completion of a clean operation.

The MNTD Float command is useful for influencing cartridge exchange operations and
returning cartridges to their original cells or to new cells after a mount/dismount request
has been completed.

If the MNTD command Float option is on (i.e., MNTD Float(ON)), when a volume is
passed to a transport in another LSM, dismount processing frees the original cell location
and assigns the volume to a cell in the same LSM as the transport as long as empty cells
exist. If no empty cells exist, a location is chosen in the nearest LSM with free cells or
volumes can be forced to their original home cell at dismount time.

If Float is off, the HSC returns the volume to its original home cell location.

The MNTD SCRDISM parameter allows scratch volumes mounted in a WolfCreek LSM
to be archived either in the same WolfCreek LSM or in the next largest storage device (the
9310 LSM).

34 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

The MNTD PASSTHRU parameter works with SCRDISM by setting the maximum
number of pass-thrus that can occur for a cartridge that is to be archived.

Refer to the ‘‘MNTD (Mount/Dismount Options) Command and Control Statement’’ in
the HSC Operator’s Guide for a description of all the options associated with this
command.

If the dismount occurs for a temporary volume, the volume is ejected through a CAP, and
a message informs the operator to retrieve the cartridge.

You can intervene in how the HSC controls library operation. Tape cartridge movement, as
well as many other functions, can be controlled to function in ways that you prefer. Refer
to Chapter 4, “Utility Functions” on page 131 for information about utilities that can be
used to control HSC operation of the library. Refer to the HSC Operator’s Guide for
information about operator commands that can be used for controlling library operation.

Abnormal Mounts/Dismounts

The HSC handles abnormal situations through communication with the operator so
intervention may take place to accomplish the mount. The following examples indicate the
types of situations in which this communication takes place:

• The transport is in an ACS, but the volume is not. The HSC issues a WTOR.

The operator may:

- reply that the mount request is to be ignored and the TMS request is canceled

- reply that the volume is to be permanently entered into the library

- reply that the volume is to be temporarily entered into the library

- enter the volume and the HSC automatically retries the volume lookup.

• The volume and/or transport resides in a manual mode LSM.

- All mount and dismount requests are queued until either a response is made to
one of the manual mode WTORs or the LSM is returned to automatic mode. At
this point, all queued requests are processed.

- A console interaction (WTOR) is provided to indicate the VOLSER’s location.

- When a transport’s LSM is in manual mode or the robotic control path to the
LSM is inoperative, operator intervention is requested to assist in performing
the mount.

- When the transport being dismounted is in a manual mode LSM, the operator is
requested to dismount the cartridge and to remove it from the LSM. The volume
is deleted, or the operator may be asked if the volume is to be deleted, from the
control data set.

The volume may be deleted from the control data set depending on the setting
of the MNTD command. A delete occurs unconditionally if MNTD
Dismount(Auto) is entered. Otherwise, a reply is required.

Chapter 2. Host Software Component Functions 35

1st ed., 6/30/04 - 312579601

• The TMS is unsatisfied with the scratch cartridge provided.

- The HSC dismounts the current volume, removes it from the scratch list, and
mounts another scratch volume.

Virtual Thumbwheel (VTW)

Virtual thumbwheel is the HSC function that allows read-only access to a cartridge in an
ACS. Normally cartridges are stored in the library with the physical cartridge thumbwheel
enabled for writing. There are circumstances where it is desirable to allow enforced
read-only access to a volume without removing the volume from the LSM, changing the
physical thumbwheel, and reentering it.

The HSC may, via the VM HSC Tape Management Interface (TMI) or by operator
command, cause a volume to be mounted while instructing the transport to allow
read-only access to the volume by simulating that the thumbwheel is in a read-only state.
In this virtual thumbwheel mode, the transport ignores the fact that the volume might be
physically enabled for writing.

The transport never writes on a cartridge that is physically write-protected.

Tape Management Interface

The TMI utilizes virtual thumbwheel when the PROTECT parameter is specified with
MOUNT requests. Refer to the HSC Interface to Tape Management Systems Manual for
interface details.

HSC Mount Command Support

The Mount command provides support for virtual thumbwheel. The Readonly operand for
the Mount command enables a volume to be mounted with the virtual thumbwheel set to
write protect.

Example of Mount Command with Readonly Operand

MOUNT VOL001,B00,,READONLY

Note: Operands for operator commands are positional. In the example above, two
commas must follow the drive operand to indicate that the host-id operand is not specified.

Refer to the HSC Operator’s Guide for details on the HSC Mount command.

36 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Tape Transport Cleaning

The HSC allows you to automate the cleaning process or to manually clean
library-attached tape transports. When a library transport needs to be cleaned, it informs
the LMU, which broadcasts a ‘‘drive needs cleaning’’ message to all connected hosts.

The LMU broadcast causes the HSC to issue a console message indicating that a transport
needs cleaning. Until a cleaning cartridge is loaded, future mounts continue to initiate this
message. If auto-cleaning is disabled, HSC processing is complete, and the transport must
be cleaned manually. To manually clean a transport, see “Manual Tape Transport
Cleaning” on page 37 for more information.

Note: The initial value for transport cleaning is for automated cleaning to be disabled.

Automated Tape Transport Cleaning

If auto-cleaning is enabled, the HSC sets the transport to ‘‘needs cleaning’’ status. The
next time a mount is issued for that tape transport, the following cleaning process is
invoked prior to mounting the requested cartridge:

1. The HSC selects a cleaning cartridge from the pool of cleaning cartridges in the LSM
that contains the tape transport that needs cleaning (or from the closest LSM that
contains a compatible cleaning cartridge).

2. The cleaning cartridge is mounted.

3. The tape transport is cleaned.

4. The cleaning cartridge is dismounted.

When the cleaning process is complete, the original requested cartridge is mounted on the
transport.

Notes: If auto-cleaning is enabled, cleaning can also be scheduled for a transport by
issuing the CLean command. See “Activating Automated Cleaning” for additional
information.

Activating Automated Cleaning

The MNTD AUtocln command is used to turn auto-cleaning on or off on a host-by-host
basis.

The following example shows how to activate automatic cleaning.

MNTD AUTOCLN(ON)

Notes: It is probably more useful to have automated cleaning on for all hosts in a JES2
installation unless library transports are allocatable only by some hosts. In a JES3
environment, most mounts are done by the global processor and auto-cleaning should be
set on for at least the global processor.

Chapter 2. Host Software Component Functions 37

1st ed., 6/30/04 - 312579601

Once auto-cleaning is activated, the CLean command can be issued to initiate cleaning of
specified drives on specified hosts.

An example of issuing the CLean command is:

CLEAN 582 HSTA

Notes:

1. The MNTD AUtocln command must be set to ON before attempting to use the
CLean command.

2. The CLean command sets the transport to ‘‘needs cleaning’’ status. The cleaning
process is not initiated until the next mount is issued against the transport. Refer to
the HSC Operator’s Guide for an explanation of the CLean command.

Identifying Cleaning Cartridges

Cleaning cartridges are identified to the HSC by a unique three-character alphabetic
prefix in their volser. All cartridges identified with that prefix make up a pool of
cleaning cartridges in each LSM.

The parameter CLNPRFX, contained in the LIBGEN SLILIBRY macro, specifies
the volser prefix for cleaning cartridges. CLNPRFX must be three alphabetic
characters, and identifies cleaning cartridges associated with the library. The default
is CLN. Refer to ‘‘SLILIBRY Macro’’ in the HSC Installation Guide for additional
information.

Notes:

1. Any cartridges identified by the cleaning prefix are treated exclusively as
cleaning cartridges; they cannot be scratched or initialized by HSC utilities.

2. Extra overhead can be avoided if the range of cleaning cartridge volsers in an
LSM and ACS is both narrow and dense. For example, if three cleaning
cartridges are in a single LSM, labels of CLN020, CLN021 and CLN022 would
cause less processing overhead than if they were labeled CLN001, CLN501 and
CLN901.

3. The cleaning prefix can be changed using the SET CLNPRFX utility. However,
before the cleaning prefix is changed, all cleaning cartridges must be ejected
from all ACSs. See the description of the SET utility for the complete
procedure. Cleaning Media and Drive Compatibility Tape transports must be
cleaned with cleaning cartridges of a compatible cleaning media type.
Longitudinal transports must be cleaned with longitudinal cleaning media,
RedWood transports must be cleaned with helical cleaning media (DD3D), and
9840 transports must be cleaned with 9840 cleaning media (STK1U).

4. Different cleaning cartridge media types may have different maximum cleaning
usage limits. Grouping cleaning cartridges of different media types into
different volser ranges makes it easier to specify these limits with the

38 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

VOLATTR control statement MAXclean parameter(s). For example, if the
helical cleaning cartridges have volsers between CLN500 and CLN599, the
following VOLATTR statement can be used to set a different maximum
cleaning usage limit for this range of helical cleaning cartridges: VOLATTR
SERial(CLN500-CLN599) MAXclean(nn)

5. Contact your StorageTek Customer Services Engineer for appropriate
MAXclean values for different cleaning media types. Limits on the Use of
Cleaning Cartridges Cleaning cartridges should only be used a limited number
of times. The MNTD MAXclean command globally specifies how many
cleaning operations are allowed before a cleaning cartridge should be removed
from the ACS and replaced (the default is 100 uses). This maximum cleaning
usage limit can be different for different cleaning media. Use the VOLATTR
MAXclean parameter to specify a different maximum cleaning limit for
different cleaning cartridge media.

6. Refer to ‘‘MNTD (Mount/Dismount Options) Command and Control
Statement’’ in the HSC Operator’s Guide and to “Volume Attribute
(VOLATTR) Control Statement” on page 110 for additional information about
the MAXclean value.

7. Ejecting and reentering used cleaning cartridges should be avoided. When a
cartridge is ejected and reentered, its select count is set to zero. The select count
is used to track the number of times a cleaning cartridge has been used. Used
cleaning cartridges which are reentered will be used more times than specified
by the applicable MAXclean value. Each cleaning media type is used in a
different way to clean tape transports. Some media types use the same cleaning
surface many times, while other media types use the cleaning surface only once.
Some media types use the cleaning surface only a few times before they are
unable to clean a tape transport.

When a cleaning cartridge is no longer able to adequately clean a tape transport, it is
over-use.

Over-use (Over-limit and Spent) Cleaning Cartridges

An over-use cleaning cartridge means either that the usage (select) count is over the
MAXclean value (‘‘over-limit’’) or all of its cleaning surface is used or ‘‘spent.’’

•An over-limit cleaning cartridge has been used more than the value (limit) specified
by either the MNTD MAXclean or VOLATTR MAXclean settings. This cleaning
cartridge may not be able to adequately clean a tape transport. If an over-limit
cleaning cartridge is mounted on a tape transport, the cleaning process is attempted
and may succeed.

•A spent cleaning cartridge’s cleaning surface is completely used up or exhausted and
can no longer be used for cleaning. When the HSC detects a spent cleaning cartridge,
it will not be mounted on a transport during automated tape transport cleaning.

Over-use cleaning cartridges should be removed from the LSM and replaced with new
cleaning cartridges. By default, the HSC ejects all over-use cleaning cartridges that it finds

Chapter 2. Host Software Component Functions 39

1st ed., 6/30/04 - 312579601

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.

Options for this command include:

ON

Use this option when operators are available to remove cleaning cartridges from a
CAP during automated tape transport cleaning. ON is the initial value for the HSC.
MSg Use this option when operators are available to respond to console messages
during automated tape transport cleaning.

OFf

With this option, no operator intervention is required for automated tape transport
cleaning.

When the HSC is searching for a cleaning cartridge to clean a tape transport, it skips all
over-use cleaning cartridges that are detected in the ACS until it finds a compatible
cleaning cartridge.

If no compatible cleaning cartridges are found in the ACS, the HSC prompts the operator
to enter a cleaning cartridge or skip the clean process.

If compatible over-limit cleaning cartridges are found in the ACS, the HSC acts based on
the MNTD EJctauto setting.

• If MNTD EJctauto(ON) or (MSg) are set, an operator prompt is issued. The operator
can reply to use one of these over-limit cleaning cartridges, enter a cleaning
cartridge, or skip the clean process.

• If MNTD EJctauto(OFf) is set, a compatible over-limit cleaning cartridge is
automatically selected to clean the transport.

When the clean process is finished, the cleaning cartridge is dismounted from the tape
transport. If the cleaning cartridge is over-use (over-limit or spent), the HSC acts based on
the MNTD EJctauto setting.

• If MNTD EJctauto(ON) is set, the cleaning cartridge is automatically ejected from
the ACS.

• If MNTD EJctauto(MSg) is set, an operator prompt is issued. The operator can reply
to eject the cleaning cartridge from the ACS or keep the cleaning cartridge in the
ACS.

• If MNTD EJctauto(OFf) is set, the cleaning cartridge is automatically kept in the
ACS.

40 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

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. While there is no minimum number of cleaning cartridges,
optimally, each LSM should contain multiple cleaning cartridges for each type of transport
attached to the LSM. This ensures that automated cleaning avoids pass-thrus for cleaning
cartridges.

If all transports in an LSM are scheduled for cleaning at the same time (by a scheduled or
operator-entered CLean command), each LSM should contain one cleaning cartridge for
every tape transport attached to the LSM.

Managing cleaning cartridges is especially important when automatic ejection of over-use
cleaning cartridges has been disabled by the MNTD EJctauto command. On a regular
basis, these cleaning cartridges must be identified, ejected from the ACS, and replaced
with new cleaning cartridges.

Use the Volume Report utility to identify over-use cleaning cartridges. Select the cleaning
cartridges by volser range and sort the output by use:

VOLRpt VOLser(CLN000-CLN999) SORT(USE) DEScend

The ‘‘Cln Use’’ column on the report identifies:

N = Not usable cartridges (including spent cleaning cartridges)

M = Over MAXclean, for over-limit cleaning cartridges

Spent and over-limit cleaning cartridges are also identified on the SLSCDATA flat file
requested by the VOLDATA parameter. Volume data is mapped by the SLUVVDAT
macro. Volumes that are not usable (i.e., spent) are identified by VOLNOUSE. The
MAXclean value that applies to a cleaning cartridge is carried in the VOLMXCLN field.

Manual Tape Transport Cleaning

If auto-cleaning is disabled, tape transports must be cleaned manually. This process can be
performed without entering the LSM.

Two methods that may be used to accomplish this task are:

• issue a Mount command to mount a cleaning cartridge on the transport. When
cleaning is complete, enter a DISMount command to remove the cleaning cartridge
from the transport.

• use an automated operations package to mount and dismount the correct cleaning
cartridge(s) on the transport(s). Coordination and setup is required to implement this

Chapter 2. Host Software Component Functions 41

1st ed., 6/30/04 - 312579601

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

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. The destination for the volume(s) may be within the same
LSM or different LSM(s). The Volume Move function provides you with the capability to
move volumes at your discretion. Volume movement may be required because of:

• changes in your library hardware configuration. Addition of tape transports or LSMs
to a library configuration often requires that volumes be moved to accommodate the
new hardware configuration. Panels can be frozen to prevent allocation of new
volumes to those panels. It is not necessary to move volumes that reside on a panel
before it is frozen, however, volumes should be moved off frozen panels that will be
changed.

• the need to achieve better control over library tape activity.

Volumes can be moved by any of the following methods:

• MOVe operator command

• MOVe utility

• tape management interface MOVE request

• Scratch Redistribution utility.

These methods provide you with the operational flexibility often needed within a library
installation.

Chapter 2. Host Software Component Functions 43

1st ed., 6/30/04 - 312579601

Scratch Subpool Management

Management of scratch subpools within the library is an important function affecting
library performance and your ability to have greater control over scratch volume activity.

You can effectively manage your scratch subpools by several available means. These
include:

• Defining subpool information in a PARMLIB control statement — Scratch
subpools can be defined using the Scratch Subpool (SCRPOol) PARMLIB control
statement.

SCRPOol permits you to enter the following information for each subpool:

- a subpool name

- the range of volume serial numbers

- the label type

- the HOSTID.

• Enabling scratch subpools — Scratch subpools specified by SCRPOol are defined
in the SLSSYSxx command list and are executed when the HSC is initialized. Refer
to “Scratch Subpool Control Statement” on page 80 for detailed information on how
to implement scratch subpooling using the SCRPOol control statement. (The syntax
for the SCRPOol PARMLIB control statement is also shown in Appendix A,
“Macros, Control Statements, Utilities, and Commands Syntax Reference” on page

387)

• Defining subpool information using the TMI — Refer to the HSC Interface to
Tape Management Systems Manual for more information.

• Specifying scratch subpool parameters with operator commands — Several
commands are available for controlling scratch subpools. Complementing these
commands are scratch subpool parameters in two utilities. The syntax for each
operator command is contained in Appendix A, “Macros, Control Statements,
Utilities, and Commands Syntax Reference” on page 387.

The commands that can be used to display scratch subpool information include:

- Display SCRatch and Display THREShold commands

- Warn command.

Commands that include scratch subpool parameters are:

- EJect

-ENter

- Mount.

Utilities that include scratch subpool parameters are:

- Scratch Redistribution (SCREdist) control statement

- ENTEr utility

- EJECt utility.

44 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Refer to Chapter 2, ‘‘Commands, Control Statements, and Utilities’’ in the HSC
Operator’s Guide for detailed information about operator commands and to Chapter

4, ‘‘Utility Functions’’ for information about utilities.

Scratch Threshold Task Restart

The scratch threshold task is a function within the HSC that maintains a count of scratch
volumes that are available within a library. Should this task fail, the HSC is unaware of the
number of scratch volumes available. Thus, a failure of this task could result in impairing
any library processing relying on scratch volumes.

The HSC provides automatic recovery and reinstatement of this task if a failure occurs.
This recovery and reinstatement is transparent to users except for a message displayed on
the system console indicating that the task is reinstated.

In the event, because of unusual circumstances, that the task is not reinstated, a message
on the system console also informs you of the condition and appropriate action to take.

Refer to Chapter 2, ‘‘Commands, Control Statements, and Utilities’’ in the HSC
Operator’s Guide for information about the Warn operator command used to dynamically
modify scratch threshold values.

Chapter 2. Host Software Component Functions 45

1st ed., 6/30/04 - 312579601

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. At some points, operator interaction
is required. Refer to your ACS hardware operator’s guide for more information about
CAPs.

CAP processing functions described in this section include:

• entering cartridges into the library using the ENter command or ENTEr utility

• ejecting cartridges from the library using either the EJect command or EJECt utility

• CAP exception processing

• releasing an allocated CAP.

Enter and eject operations are accomplished concurrently with other normal LSM
operations: automated mounts, automated dismounts, cartridge exchanges, etc.

For multiple CAPs, each enter and eject operation is processed separately. The user can
run concurrent tasks against CAPs on a single LSM.

PCAPs are used for single cartridge enter and eject operations. These are controlled by the
user through the Tape Management Interface (TMI). Refer to the Interface to Tape
Management Systems Manual.

Operator commands and detailed instructions for controlling CAP processing functions
are described in the HSC Operator’s Guide; utilities are discussed in Chapter 4, ‘‘Utility
Functions’’ in this document.

Entering Cartridges into the Library

To enter cartridges into the library, execute the HSC ENter command, SENter command,
or ENTer utility and identify which CAP is to be used for the operation. Specifying the
cap-id is optional for the ENter command. Following the procedures described in Chapter
3, ‘‘Operating an Automated Cartridge System’’ in the HSC Operator’s Guide, open the
CAP door, place cartridges into the CAP cells, and close the CAP door.

The CAP automatically locks when the door is pushed closed. The robot scans the
Tri-Optic label (must be unique) of a cartridge, and the cartridge is moved by the robot to
an empty cell in one of the LSM panels.

For a CAP in automatic mode, do not issue an ENter command. The operator need only
open the door, insert cartridges, and close the door. No other operator intervention is
required.

46 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Ejecting Cartridges from the Library

Cartridges are ejected from the library by using either the EJect command or the EJECt
utility. Either a single cartridge, a range of cartridges, or a list of cartridges can be
identified for removal from the library. The robot locates the appropriate storage cell,
withdraws the cartridge from its cell, and moves it to an available cell in a CAP.

The operator must remove cartridges from the library through the CAP. All cartridges
contained in the CAP must be removed once they are placed in the CAP by the robot.
Refer to Chapter 3, ‘‘Operating an Automated Cartridge System’’ in the HSC Operator’s
Guide for operator procedures for CAP processing.

CAP Mode Considerations

Unlike manual mode CAPs which are allocated for enters from specific hosts, automatic
mode CAPs may be serviced by any active host. Placing a CAP in automatic mode
improves CAP performance and is best utilized when:

• operator intervention is not required

• it is acceptable to receive and respond to HSC WTORs from any active host console.

Entering cartridges that require operator intervention may create problems in library
configurations utilizing automatic mode CAPs, especially if you enter many cartridges
without external Tri-Optic labels. WTORs are issued by the host currently servicing the
automatic mode CAP which may present an inconvenience if you are expecting the
WTORs at a specific host console, but they are being directed to an unattended host
console. If you require WTORs to be returned to a specific host console, you must allocate
one or more manual mode CAPs and use the Enter command from that host.

CAP Exception Processing

Enter and eject processes are based on a cartridge-by-cartridge basis. This affords a
significant amount of isolation between requests. However, in certain cases redundant
errors may be incurred due to abnormal conditions external to an individual request.
Mechanisms have been provided to help when these situations arise:

• Releasing a CAP may be necessary to free up cartridge and CAP resources and to
end an enter or eject process.

• Modifying a CAP offline isolates it from being used until the error is corrected.

• The next use of the CAP invokes CAP cleanup and recovery, which requests that the
operator check the CAP for cartridges.

Note: If an enter process has not moved all cartridges from a CAP or an eject process has
moved cartridges to the CAP when a release occurs, the cartridges are left in the CAP but
are not in the control data set. Refer to Chapter 3, ‘‘Operating an Automated Cartridge
System’’ in the HSC Operator’s Guide for more details.

Chapter 2. Host Software Component Functions 47

1st ed., 6/30/04 - 312579601

Releasing an Allocated CAP

The RELease cap-id operator command allows you to release a CAP that is allocated to a
failed host.

A CAP can be left allocated to a system if the HSC terminated without recovery while the
CAP is active.

When you issue the command, appropriate messages inform you of conditions and actions
to take. You are prompted by an initial message to confirm or terminate release of the
specified CAP. This confirmation prevents the release of a CAP that is currently being
used by the system.

This feature is of significant importance to you by giving you control to release a CAP
without having to recycle all of the HSCs that share control data sets.

Refer to Chapter 2, ‘‘Commands, Control Statements, and Utilities’’ in the HSC
Operator’s Guide for detailed information about the RELease CAP command.

48 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

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

• automatic recognition of configuration changes

• using the SET utility instead of LIBGEN and reconfiguration

• defining a new configuration to avoid future reconfigurations

• defining planned ACSs with no stations

• changing panels

• using CDS rename/relocate/expand.

In addition, several other timesaving benefits are described in other places in the HSC
documentation set. These are:

• converting the CDS level from 2.0 to 2.1 while HSC 2.0.1 remains active. Refer to
the HSC Installation Guide, ‘‘CDS Conversion Requirements (Up-Level
Migration),’’ in Appendix D, ‘‘Migration and Coexistence Processes.’’

• resolving LSM and panel type configuration mismatches. Refer to either the HSC
Installation Guide, ‘‘Configuration Mismatches,’’ in Chapter 8, ‘‘HSC Initialization’’
or see the HSC System Programmer’s Guide, “Configuration Mismatches” on page

163.

• changing drive panel types without running a reconfiguration. Refer to the HSC
System Programmer’s Guide, “SET Device Numbers for Drives” on page 405.

• automatic internal cold start for HSC 2.0.1 and later releases. Refer to either the HSC
Installation Guide, ‘‘Starting HSC Execution’’ in Chapter 7, ‘‘Initializing the HSC’’
or see the HSC System Programmer’s Guide, “Starting HSC Execution” on page 225.

• suppressing the ‘‘ACS Disconnected’’ message to allow for future hardware
expansion. Refer to the HSC Operator’s Guide, ‘‘OPTION Command and Control
Statement,’’ in Chapter 2, ‘‘Commands, Control Statements, and Utilities.’’

Using Multiple CDS Copies

When multiple copies of the CDS are defined and enabled, the HSC automatically
recovers from errors on one of these copies. In a multiple-host environment, CDS
recovery is coordinated among the HSCs on all hosts.

• When there is a mismatch between information on the same block on the primary and
secondary CDS copy, the HSC automatically selects the most recent copy. When the
CDS is updated, the modified block is written to both the primary and secondary
CDS copies.

• If a secondary CDS copy is active, and a failure occurs in accessing the current
primary CDS copy, the HSC automatically makes the secondary CDS copy the

Chapter 2. Host Software Component Functions 49

1st ed., 6/30/04 - 312579601

primary copy. If a standby CDS copy is active, the new primary CDS copy is copied
over the standby CDS copy, and the standby becomes the new secondary copy.

• If a standby CDS copy is active, and a failure occurs in accessing the secondary CDS
copy, the current primary CDS copy is copied over the standby CDS copy, and the
standby becomes the new secondary copy.

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). CDS
copies should be located on different DASD volumes for redundancy.

For more details about automatic CDS recovery, refer to “Control Data Set Recovery” on
page 49 and “CDS Recovery Capabilities” on page 439.

Automatic Recognition of Configuration Changes

Some changes to the library configuration are automatically recognized by the HSC.

Automatic Update of LSM from 4410 to 9310

When an LSM comes online, the LSM type is reported to the HSC by the LMU. If the
LSM is defined in the CDS as a 4410, but it is actually a 9310 (PowderHorn), the LSM
type is automatically updated in the CDS. Thus, an LSM upgrade from a 4410 to a 9310 is
automatically recognized and recorded in the CDS without running the Reconfiguration
utility.

Note: Replacing a 9310 with a 4410 LSM does not result in an automatic update of
the LSM type. (In some cases the hardware report of this change may not be
accurate.)

If an LSM is defined to the HSC as a 9310, but it is actually a 4410, the HSC
manages it without problems, since the panel configurations and LMU requests and
responses are the same for 4410 and 9310 LSMs. However, HSC preferencing by
LSM type will not work correctly using MNTD SCRDISM(CURRENT/ARCHIVE)
for scratch dismount requests.

Run-time Recognition of 9740 CAP Configuration

The 9740 CAP can either be a 14-cell array, or it can hold a 10-cell removable magazine.
The HSC recognizes the current CAP size when the LSM is modified online. This allows
the user to change the 9740 CAP configuration without running the Reconfiguration utility
or recycling the HSC.

Using the SET Utility Instead of LIBGEN and Reconfiguration

Changing a configuration using the Reconfiguration utility requires a global outage. Many
of the changes made by the SET utility can be performed while HSC subsystems are up

50 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

that are not directly affected. Then, these subsystems can be recycled (brought down and
then restarted) to pick up the changed information. Cycling the affected HSCs can be done
at a convenient time, with only one HSC down at a time. This permits an HSC server to
remain up, servicing requests from clients.

Note: In many instances, the SET utility can run while HSC subsystem(s) are active.
However, some SET options require that the HSC(s) affected must be down, e.g.,
SET HOSTID.

In most cases, the LSM and/or ACS affected must remain offline until HSCs on
affected hosts are recycled, e.g., when deleting or changing drive unit addresses with
SET SLIDRIVS.

In most cases, all affected HSCs must be recycled to reinitialize and support the new
configuration. Refer to “SET Utility” on page 392 for restrictions on the specific
SET options and processes to follow when making configuration changes.

Defining a New Configuration to Avoid Future Reconfigurations

When you define a new configuration with LIBGEN, you can add some flexibility to
avoid running reconfigurations in the future.

• If additional hosts may be added later, define dummy host IDs now.
Entries for future hosts can be defined in the SLILIBRY macro,

HOSTID=(host0,...,host15) parameter. For example, host IDs of FREE1, FREE2,

and FREE3 could be defined. Then, the SET utility HOSTID option can be used to
change these ‘‘reserved’’ host IDs to the new ones being added to the configuration.

SET HOSTID(newhost),FORHOST(FREE1)

• When a CDS is created, it is desirable to allocate more then the minimum amount of
space. The free blocks can be used later when additional drives are added.

Defining Planned ACSs with no Stations

The HSC allows users to define an ACS without specifying station addresses (refer to the
SLIACS macro in the HSC Configuration Guide).

Using this feature means that a planned ACS can be placed into the LIBGEN/SLICREAT
process and remain disconnected without generating message SLS1664A (

disconnected’’

suppress SLS1664A.

If planned ACSs have been defined previously with dummy station addresses, these
stations can be removed using the SET SLISTATN utility. In this case, the user does not
specify any output stations. Refer to “SET LMU Station Address Numbers” on page 408
for more details.

When the planned ACS becomes available, SET SLISTATN can be used to add stations
for the ACS. The ACS can then be brought online without recycling the HSC.

) or requiring the user to enter the OPTion DISCmsg command to

‘‘ACS AA is

Chapter 2. Host Software Component Functions 51

1st ed., 6/30/04 - 312579601

Changing Panels

The following procedures describe methods to make changes to panels. These include
changing panels types in an LSM and removing cartridges to facilitate hardware changes.

• To change panel types in an LSM:

SET FREEZE(ON),FORLSMID(aa:ll),FORPANEL(pp)

MOVe Flsm(aa:ll) Panel(pp) TLsm(aa:ll)

1. Use the SET utility to freeze the panel, preventing any additional cartridges

from being moved to it. This prohibits new cartridge home cell locations from
being allocated on the frozen panel.

2. Use the MOVe utility or the MOVe or EJect commands to move all cartridges

off the panel being changed.

Because the panel has been frozen, cartridges cannot be moved to it, and it will
remain empty.

3. Change the panel type, either using the SET SLIDRIVS utility to change

between standard and wide drive panels or running the 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.

4. After the hardware changes are complete, unfreeze the panel, if it is still frozen.

SET FREEZE(OFf),FORLSMID(aa:ll),FORPANEL(pp)

Notes:

1. If a frozen panel type is changed by the Reconfiguration utility, the new
panel is not frozen. Frozen panels that did not change remain frozen after a
reconfiguration.

2. When SET SLIDRIVS is used to change panel types, SET FREEZE(OFf)
can follow the SET SLIDRIVS statement.

52 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

• To remove cartridges from rows on panel(s) to facilitate hardware (e.g., cabling)
changes:

1. Use the SET utility to freeze the panel, preventing any additional cartridges
from being moved to it. This prohibits new cartridge home cell locations from
being allocated on the frozen panel.

SET FREEZE(ON),FORLSMID(aa:ll),FORPANEL(pp)

2. Use the MOVe utility or the MOVe or EJect commands to move all cartridges
off the panel rows being changed.

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.

SET FREEZE(OFf),FORLSMID(aa:ll),FORPANEL(pp)

Chapter 2. Host Software Component Functions 53

1st ed., 6/30/04 - 312579601

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.

For a rename or relocation operation, the CDS must be disabled (inactive) on all HSC
hosts to ensure that no active HSC hosts attempt to update or read the target CDS copy
during a rename or relocation activity. When using the CDS EXpand function, all CDS
copies are reformatted at the same time, so all CDSs must be enabled (active) on all hosts.

CDs Command

The CDs operator command provides rename, relocation, and expand capabilities. Refer
to the “Commands, Control Statements, and Utilities” chapter in the HSC Operator’s
Guide for a description of the keywords used to perform these operations.

Renaming/Relocating a CDS - Scenarios

To rename and relocate a CDS copy, only one copy of the CDS must be disabled at a time.
For example,

CDS DISABLE DSN(ACS.DBASEOLD)

Renaming a CDS Copy

Before you enable the renamed CDS copy, assume only one CDS has been disabled using
the CDs Disable command (see above), and ACS.DBASEOLD is renamed to
ACS.DBASECPY. The inactive (disabled) data set is then enabled using the following
command:

CDS ENABLE DSN(ACS.DBASECPY)

If the Enable command fails for the renamed CDS, CDS definitions are restored to what
they were before the command was issued. Users must modify CDSDEF control
statements to keep them consistent with the active CDS.

Renaming and Relocating a CDS Copy

To relocate a CDS copy with the CDS Enable command, the user must first create a data
set containing the appropriate CDS attributes: a fixed, 4096-byte record, single extent,
physical sequential file. Optionally, users may rename the CDS.

The data set can be created using JCL as shown for the SLICREAT job discussed in the
HSC Configuration Guide or using the TSO 3.2 Data Set Utility facility.

54 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Note: TSO 3.2 may create a single extent data set even when no secondary quantity is
specified.

It is not necessary to initialize the CDS copy, that is, you do not have to execute
SLICREAT or copy another CDS copy to the new data set.

Assume that ACS.DBASECPY has been disabled and deleted (or uncataloged), and
ACS.DBASENEW has been allocated and cataloged. The following command enables
the renamed and relocated CDS:

CDS ENABLE DSN(ACS.DBASENEW) NEWLOC

Note: MVS uses catalog services to resolve the volume and unit definitions, if not
specified.

If a rename or relocate operation fails, CDS definitions are restored to what they were
before the command was issued. Users must modify CDSDEF control statements to keep
them consistent with the active CDS.

Relocating an Uncataloged CDS Copy

Assume that ACS.DBASECPY has been disabled and deleted (or uncataloged), and
ACS.NOTCATLG has been allocated and cataloged. The following command relocates
an uncataloged CDS copy:

CDS ENABLE DSN(ACS.NOTCATLG) NEWVOL(HSC001),NEWUNIT(ABC)

Users must modify CDSDEF control statements to make them consistent with the CDS
definitions in this command. If a rename or relocate operation fails, CDS definitions are
restored to what they were before the command was issued.

Note: The NEWVOL and NEWUNIT parameters are required for VM.

Expanding a CDS - Scenario

Before expanding all CDSs, each CDS must be disabled one at a time and created with a
larger space allocation in the JCL. Then, all CDS copies must be enabled before issuing
the following command:

CDS EXPAND

Chapter 2. Host Software Component Functions 55

1st ed., 6/30/04 - 312579601

Warning: StorageTek recommends backing up all CDS copies prior to issuing the
CDS EXpand command. Failures during the expand operation usually cause the
CDS to be unusable. It is important to back up the CDS before invoking the CDS
EXpand command to insure that the latest copy of the CDS is available in case of a
failure during the expand operation.

The number of formatted blocks in the CDS remains constant for all copies of the CDS
regardless of the physical space allocated for CDS copies. The number of formatted
blocks is determined by the maximum number of 4096 blocks that can be written in the
smallest CDS copy.

Users must modify CDSDEF control statements to make them consistent with the CDS
definitions in this command.

56 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Swapping Library Transports - New Model Types

When you physically upgrade or change tape transports, a mismatch can occur between
the model types stored in the CDS and the updated model types specified in the UNITDEF
command. If this situation arises, you receive an error message:

SLS1628I UNITDEF: Record 1 ...MODEL is incompatible with UNIT

Follow this procedure to avoid the problem:

1. Terminate the HSC on all hosts by issuing the MVS STOP command.

2. Physically replace the tape transports.

3. Run the SET SLIDRIVS utility to omit the device numbers being replaced. It is only
necessary to specify the device numbers being replaced, not all device numbers on
the panel. Example:

SET SLIDRIVS(,,,,,,2307,2308,2309,230A),FORLSMID(0000),FORPANEL(01)

4. Run SET SLIDRIVS again to add the device numbers back in. This action clears the
model type in the CDS and allows the UNITDEF command to load at HSC startup.
Example:

SET SLIDRIVS(2301,2302,2303,2304,2305,2306,2307,2308,2309,230A),+
FORLSMID(0000),FORPANEL(01)

5. Update the UNITATTR statements to reflect the new model type.

6. Start the HSC on one host by executing the HSC start procedure.

7. When the HSC reaches the full service level, start the HSC on all remaining hosts.

Chapter 2. Host Software Component Functions 57

1st ed., 6/30/04 - 312579601

Common Recovery Functions

Common recovery functions consist of information gathering from the control data sets
and journals, and processing to recover from a database or hardware failure.

The most vital recovery function is control data set recovery which is described in this
section.

Control Data Set Recovery

Control data sets contain valuable information required for the HSC software and the
library to function. The control data sets contain:

• inventory information on all volumes in a library

• the library configuration, including how many ACSs, LSMs, tape transports, etc.

• information about library hardware resource ownership across multiple processors

• information for controlling the communication link between HSC subsystems
running on multiple processors.

The HSC subsystem has the capability of operating with several control data sets and
journals simultaneously:

• Primary control data set — This data set is required for every installation

• Secondary control data set — This data set is optional, but highly recommended

• Standby control data set — This data set is strictly optional, but also recommended

Note: The SLIRCVRY LIBGEN macro TCHNIQE parameter determines how many
CDS copies will be initialized by the SLICREAT program and whether or not
journals will be initialized by SLICREAT. Refer to ‘‘SLIRCVRY Macro’’ in the HSC
Installation Guide for more information.

The number of CDS copies used by the HSC is dependent on the number of CDS
copies defined in the CDSDEF PARMLIB control statement. It is not determined by
the TCHNIQE parameter.

The HSC uses all of the CDS copies defined in the CDSDEF control statement
(whether this includes more or less CDS copies than are specified by the TCHNIQE
parameter). However, if journaling is specified by the TCHNIQE parameter, journals
must be defined for successful HSC initialization.

• Journals — Two journals per host are kept to record library transactions. Each
journal contains a record of changed data. The changed data consists only of bytes of
data that have been changed. The record is made at the time the transaction occurs.
The journals can be applied to a backup control data set, for recovery purposes, to
make the control data set current.

Note: Journals are optional and are no longer a recommended recovery method.
Secondary and standby data sets provide a faster and more reliable method for
ensuring CDS integrity.

58 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Control data sets can be accessed by different hosts and are kept synchronized. In event of
a failure, the BACKup and RESTore utilities can be used to perform extensive error
checking and synchronization of the data. A backup control data set and journals are used
to reconstruct the control data sets.

The integrity of the control data sets is extremely important. In multiple processor
environments, data set integrity is much more difficult to maintain. Because of this, the
HSC subsystem is designed to keep the control data sets intact and configured to recover
from failures. Features such as shadowing for the control data set, journaling, backup and
restore were previously in place in prior releases to maintain data set integrity.

Control Data Set Recovery Techniques

There are several techniques to accomplish control data set recovery. These techniques
are:

• dynamic recovery of CDS errors (when possible)

- switch

- internal CDS directory rebuild

- standby CDS copy.

• diagnostic information on CDS errors, error detection, and correction of the CDS
through the BACKup and RESTore utilities

• the ability of the HSC to continue running on one copy of the CDS

• user control of enabling and disabling control data sets with operator commands

• automatic communication with other hosts in a complex when control is switched
from one CDS to another.

User Control of Control Data Sets

The HSC offers flexibility for definition and control of control data sets. User control of
these data sets includes:

• allocation of data sets at initialization

• ability to dynamically enable or disable the library control data sets

• reassigning control data set names in the Database Heartbeat record.

Allocation of Control Data Sets

Control data sets are defined at HSC initialization by PARMLIB control statements rather
than defined by JCL. These definitions are invoked at HSC initialization and remain set
until HSC termination. The definitions cannot be altered without HSC shutdown and
restart.

Refer to “PARMLIB Control Statements” on page 67 for detailed information about
PARMLIB control statements.

Chapter 2. Host Software Component Functions 59

1st ed., 6/30/04 - 312579601

Dynamic Enable/Disable of Control Data Sets

Operator commands are supplied to give you control over which data sets the HSC is
utilizing. This functionality is particularly useful in a multiple-processor environment.

Before attempting to enable or disable any data set, you can use the Display CDS
command to display the current status of the control data sets.

The commands to enable or disable a control data set can be issued without halting HSC
execution or disrupting any running HSC.

Refer to Chapter 2, ‘‘Commands, Control Statements, and Utilities’’ in the HSC
Operator’s Guide for detailed information about operator commands for enabling or
disabling control data sets.

Reassigning Control Data Set Names in Database Heartbeat Record

The names of the control data sets are recorded by the HSC in the Database Heartbeat
(DHB) record to identify the correct primary, secondary and standby control data sets.
When HSC is initialized, it assigns its control data set copies as primary, secondary and
standby based on the Database Heartbeat record, not on the assignment in the CDSDEF
PARMLIB statement.

When HSC systems are running, the assignment of specific control data sets as primary,
secondary and standby happens automatically and is not normally of concern.

Either of the following procedures can be used to change the assignment of control data
sets as primary, secondary and standby in the Database Heartbeat record.

• Procedure using CDS Disable and CDS Enable commands:

1. Use CDS Disable and CDS Enable commands to rotate the control data sets into

the desired sequence.

2. Use the Display CDS command to view the current status and assignment of the

control data sets.

For example, to switch the assigned order of a primary control data set (with

DSN=SLS.DBASE1) and a secondary control data set (with DSN=SLS.DBASE2):

1. Issue the command:

DISPLAY CDS

to view the current control data set status and assignments.

2. Make the current secondary control data set the new primary control data set by

issuing the command:

CDS DISABLE PRIMARY

60 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

3. Make SLS.DBASE2 the new secondary control data set by issuing the
command:

CDS ENABLE DSN=SLS.DBASE2

4. Issue the command:

DISPLAY CDS

to view the current control data set status and assignments.

• HSC BACKup and HSC RESTore procedure:

1. Stop the host software on all hosts.

2. Backup the control data set with the HSC BACKup utility.

3. Restore the control data set with the HSC RESTore utility. This will clear the
control data set information in the Database Heartbeat record.

4. Start an HSC system, specifying the desired primary, secondary, and standby
control data sets in the CDSDEF PARMLIB statement. During HSC 2.0 or
higher initialization, the control data sets assigned as primary, secondary and
standby will be recorded in the Database Heartbeat record.

Chapter 2. Host Software Component Functions 61

1st ed., 6/30/04 - 312579601

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
Mount
MOVe
MNTD
SCRPOol
Warn

CAP

CAPPref
Display
DRAin
EJect
ENter
MODify
OPTion
RELease
SENter

LMU

Display
SWitch
Vary

ACS

Display
SWitch

Figure 5. HSC Command Functions Overview

LSM

Display
MODify
VIew
OPTion (Viewtime)

TAPE TRANSPORTS

ALLOC (MVS only)
CLean
DISMount
Mount
MNTD

HOST/HSC

CDs
COMMPath
Display
OPTion (Dialog)
RECover
RETry J3init (MVS/JES3 only)
SRVlev
Trace
TRACELKP
UEXIT (MVS only)

CONSOLE

Display
OPTion
MONITOR (MVS only)
STOPMN (MVS only)

C29358

62 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Controlling LSM Operating Mode

The operating mode for any LSM is controlled by using the MODify command to place
the LSM online or offline. An LSM operating mode is a relationship between an LSM and
all attached hosts. The two LSM operating modes are:

• automatic – the LSM is online to all hosts.

• manual – the LSM is offline to all hosts.

When an LSM is online, the LSM is in the automatic mode, meaning that the robot is fully
operational. When an LSM is offline, the LSM is in manual mode.

Refer to the HSC Operator’s Guide, Chapter 4, ‘‘Managing Library Resources,’’ for
procedures describing how to operate an LSM in manual or automatic mode.

Controlling CAP Operating Mode

The operating mode for CAPs is controlled by the CAPPref and MODify commands. The
four CAP operating modes are:

• automatic – the user can enter cartridges into an LSM without using HSC commands
or utilities.

• manual – the user must issue HSC commands and utilities to use the CAP.

• online – the CAP is online to all hosts.

• offline – the CAP is offline to all hosts.

Refer to the HSC Operator’s Guide, Chapter 3, ‘‘Operating an Automated Cartridge
System,’’ for a description of CAP modes and Chapter 4, ‘‘Managing Library Resources,’’
for procedures describing how to operate an LSM in manual or automatic mode.

Viewing the Interior Components of an LSM

Should you have a need to determine the state of a tape transport or any other component
inside of an LSM, you can use the VIew command to ‘‘see’’ inside of an LSM for visual
inspection of a tape transport, pass-thru port, storage cell, CAP, or playground cell.

Using the VIew command offers benefits; you do not need to:

• vary tape transports offline

• modify the LSM offline

• physically open the LSM access door to inspect the inside of the LSM

• disable the LSM for minutes at a time.

Note: This feature is standard on a model 4410 (Cimarron) or 9310 (PowderHorn) LSM.
A 9360 (WolfCreek) LSM requires an optional vision system. The SL8500 library does

not provide viewing capability.

Chapter 2. Host Software Component Functions 63

1st ed., 6/30/04 - 312579601

Using the VIew command to Inspect an LSM Component

When you issue the VIew command, you direct the vision system to focus on an item
inside of the LSM for a specified length of time. Upon entering the command, the
following events occur:

• A VIew request is sent to the controlling LMU.

• A WTOR is displayed on the console when the camera is in position; the message
indicates which camera/robot hand is focused on the specified object.

Note: If you respond to the message before the expiration of the requested time
interval, the VIew request is cancelled. Refer to the OPTion command and the
Viewtime parameter for controlling the view interval. The HSC Operator’s Guide,
Chapter 2, ‘‘Commands, Control Statements, and Utilities,’’ describes the operator
commands.

• The message on the console is DOMed.

• Optionally, a subtype 8 SMF record is written. The record includes the length of time
that the camera was held in a static position for this particular VIew command. Refer
to Appendix C, “Record Formats” on page 445 for more information on SMF
records.

64 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

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” on page 131 for detailed descriptive information
about all HSC utilities, including description, syntax and parameters, JCL requirements
and examples, and samples of output.

Chapter 2. Host Software Component Functions 65

1st ed., 6/30/04 - 312579601

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. The operator is also
notified when the LMU designated as the standby fails.

If the Master LMU Fails

When the master LMU fails:

• the standby LMU detects the failing master and informs the HSC

• the HSC reports the failure by issuing a message

• the HSC reacts as necessary to recover and continue processing mounts and
dismounts.

If the Standby LMU Fails

The standby LMU constantly polls the master. The master LMU acknowledges this
polling.

In the communications between the HSC and the master LMU, the master, as part of its
acknowledgment, informs the HSC of the status of the standby. The standby LMU is either
ready or not ready.

The master LMU thinks that the standby is ready if the standby has polled the master in
the required time interval. If the standby LMU has not polled the master in the required
time interval, the master informs the HSC that the standby is not ready.

The HSC issues an outstanding message. This informs the operator of the status change
(not ready) in the standby LMU.

Operator Control of LMUs

A library operator can control which LMU is operating with the SWitch command. When
the SWitch command is issued, all hosts connected to the ACS are affected.

If after entering a SWitch command, the new master LMU fails and the switchover does
not occur in 20 seconds, the HSC attempts to resume working with the old master. (The
HSC has been waiting for the standby LMU to take over as the master LMU, but the
switch did not take place.)

If the SWitch command fails, the system issues an error message. The operator can force
the completion of the command-generated switchover either by:

• manually re-IPLing the master LMU, or

• powering off the master LMU. 2

66 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

LMU Switchover Messages

The HSC Messages and Codes Guide contains all the messages appropriate to the LMU
switchover process.

After an LMU Switch Occurs

After a switch of LMUs occurs and the LSMs have finished quick initialization
procedures, all cartridge motion requests are re-driven and completed. If a motion request
cannot be completed, the cartridge in question is made errant.

Note: ENter and EJect operations may need to be restarted after a switchover.

HSC/LMU Software Combinations

Table 4 describes the various possible combinations of HSC software with LMU
microcode and installed hardware. The table indicates valid combinations.

Table 4. HSC/LMU Validity Matrix

HSC

Version

LMU

Version

LMUs Powered

Number of

Up

Val id

Combination

Functionality Available

1 Yes New HSC features are available. Dual LMU

can be configured

1.2 +

ECap SPE

3.2
2 Yes New HSC features are available. Dual LMU

occur.

must be configured
automated.

1 Yes New HSC features are available. Dual LMU

can be configured
occur.

1.2 or later 3.6 or later
2 Yes New HSC features are available. Dual LMU

must be configured
automated.

1 Yes New HSC features are available. Dual LMU

can be configured
occur.

2.0 or later

9315/30 1.0

or later.

2 Yes New HSC features are available. Dual

LMU must be configured
be automated.

* Configuration of dual LMU is done by a StorageTek Customer Services Engineer (CSE).

*

, but switchover cannot

*

. Switchover can be

*

, but switchover cannot

*

. Switchover can be

*

, but switchover cannot

*

. Switchover can

Chapter 2. Host Software Component Functions 67

1st ed., 6/30/04 - 312579601

Adding New Stations to an ACS

The following is an example of JCL for the SET utility that can be used as a pattern for
adding new stations to an ACS without requiring a reconfiguration.

Note: Update LIBGEN control statements to make changes permanent. You do not have
to execute the Reconfig utility to implement these changes. Refer to “Reconfiguration
Utility” on page 225 for more information about reconfiguration.

JCL to Add New Stations to an ACS

//HSCUPDAT JOB (acctno),’LMU STATIONS’,MSGCLASS=1,CLASS=A,
// MSGLEVEL=(1,1)
//STEP0 EXEC PGM=SLUADMIN
//* The following DD is the HSC STEP library
//STEPLIB DD DSN=SLS.PROD.LINKLIB,DISP=SHR
//SLSPRINT DD SYSOUT=*
//* The following DD statement identifies the HSC primary CDS
//SLSCNTL DD DISP=SHR,DSN=SLS.DBASE1
//* The following DD statement identifies the HSC primary CDS
//SLSCNTL2 DD DISP=SHR,DSN=SLS.DBASE2
//SLSIN DD *
SET SLISTATN(0CD,0CE,0D0,0D1) FORACS(0) FORHOST(HST1)
SET SLISTATN(0CD,0CE,0D0,0D1) FORACS(0)
//

Notes for the Example

1. The first SET control statement defines the listed stations for only one host.

Note: All stations must be specified (not just the new ones).

2. The second SET control statement defines the listed stations for all hosts.

Note: All stations must be specified (not just the new ones).

3. The following are installation dependent:

- SLSCNTL data set

- SLSCNTL2 data set

- station identifiers

- ACS numbers

-host IDs.

4. The standby CDS is not required for this JCL.

68 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601

Reconstructing a LIBGEN

The Database Decompile (LIBGEN) utility can be used to reconstruct a LIBGEN,
reflecting the true configuration of your HSC subsystem if for some reason your LIBGEN
has been lost.

Refer to “Database Decompile (LIBGEN) Utility” on page 184 for details on how to use
the Database Decompile utility.

Chapter 2. Host Software Component Functions 69

1st ed., 6/30/04 - 312579601

Dynamic LMU Connection

LMU network connections can be defined dynamically to TCP/IP addresses using the
LMUPATH and LMUPDEF control statements.

Note: For information on implementing TCP/IP connections, refer to the LMUPATH
and LMUPDEF control statements in Chapter 3, “HSC Control Statements and HSC
Start Procedure” and to display information about the LMUPDEF data set, refer to
Display LMUPDEF in the HSC Operator’s Guide.

In addition to the control statements, the following informational and procedural topics are
discussed in this section:

• security administration considerations

• recovery maintenance requirements

• HSC port number assignments

• multiple TCP/IP stack implications

• transitioning between 3270 and TCP/IP

• recovering TCP/IP communications

• configuring VM for TCP/IP support.

Recovery Maintenance Requirements

Two sets of PTFs must be applied to allow the recovery processes described in
“Recovering TCP/IP Communications” on page 73 to function correctly:

• for HSC 4.0, L1H10KE and L1H10LC

• for HSC 4.1, L1H10L4 and L1H10LE.

These PTFs contain HOLDDATA that describes new messaging and station status during
recovery.

For HSC release levels later than HSC 4.0 and 4.1, these enhancements are included in the
base FMID.

HSC Port Number Assignments

The 9330 TCP/IP LMU listens on ports 50001 through 50016. The port assignment used
by the HSC is determined by adding the host index number within the CDS to 50000, i.e.,

host index number + 50000

Users can find out the host index number of the system(s) running the HSC by entering:

Display CDS

Part of the output from this command displays hostids using this CDS. The first hostid in
the list represents host index number 1, the second host index number 2, and so forth.

70 VM/HSC 6.0 System Programmer’s Guide

1st ed., 6/30/04 - 312579601