BrightStor CA-1 Tape Management

Transcription

1 BrightStor CA-1 Tape Management Message Guide 5.2 SP04 R8J2L052MGE

2 This documentation and related computer software program (hereinafter referred to as the Documentation ) is for the end user's informational purposes only and is subject to change or withdrawal by Computer Associates International, Inc. ( CA ) at any time. This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties. Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies. This right to print copies is limited to the period during which the license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user's responsibility to return to CA the reproduced copies or to certify to CA that same have been destroyed. To the extent permitted by applicable law, CA provides this documentation as is without warranty of any kind, including without limitation, any implied warranties of merchantability, fitness for a particular purpose or noninfringement. In no event will CA be liable to the end user or any third party for any loss or damage, direct or indirect, from the use of this documentation, including without limitation, lost profits, business interruption, goodwill, or lost data, even if CA is expressly advised of such loss or damage. The use of any product referenced in this documentation and this documentation is governed by the end user's applicable license agreement. The manufacturer of this documentation is Computer Associates International, Inc. Provided with Restricted Rights as set forth in 48 C.F.R. Section , 48 C.F.R. Sections (c)(1) and (2) or DFARS Section (c)(1)(ii) or applicable successor provisions. Ninth Edition, February Computer Associates International, Inc. (CA) All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

3 Contents About This Guide v Chapter 1. Console Messages and Replies Message Variables Message Identifiers I/O Module Codes Chapter 2. Utility Report Messages CBRUXENT and CBRUXEJC Messages CTSDEU Messages CTSPMTST Messages CTSTAPER Messages DYNCOMM Messages DYNFORMT Messages DYNSYNC Messages DYNUPDTE Messages TMSAGGR Messages TMSAUDIT Messages TMSBINQ Messages TMSBLDUE Messages TMSCKDTM Messages TMSCKLVL Messages TMSCLEAN Messages TMSCLNOA Messages TMSCONVR Messages TMSCOPY Messages TMSCTLG Messages TMSCYCLE Messages TMSDATA Messages TMSDELET Messages TMSEARL Messages TMSEXPDT Messages TMSFORMT Messages TMSGRW Messages TMSINIT Messages TMSINITD Messages TMSMERGE Messages TMSMULV Messages TMSOSCAT Messages Contents iii

4 2.32 TMSPTRS Messages ERR01 Through ERR ERR68 Through ERR TMSPULL Messages TMSREMOV Messages TMSRPI Messages TMSSMSUP Messages TMSSPLIT Messages TMSSTATS Messages TMSTPNIT Messages TMSUDSNB Messages TMSUNCAT Messages TMSUPDTE Messages TMSVMEDT Messages TMSVMUPD Messages TMSVMVLT Messages Chapter 3. Abend Codes IEFTMS50 - Realtime Abends xx-rc INVALID DATA SET NAME xx-rc UNABLE TO PROCESS A SECONDARY DATA SET xx-rc Invalid Multivolume or DSNB Pointers and Specification Errors xx-rc EOV - INPUT ONLY xx-rc MIXED EXPIRATION DATE DISALLOWED xx-rc PASSWORD PROTECTION xx-rc DEMOUNT FOR WHICH A REMOUNT WILL NOT SATISFY THE REQUEST xx-rc CA-1 HAS NOT BEEN INITIALIZED xx-rc SECURITY VIOLATION Axx-rc CTSDATE OR CTSPM ERRORS IEFTMS70 - TMC/AUDIT I/O Abends yy-rc INVALID RESIDENT MODULE yy-rc IPL REQUIRED yy-rc ALL AVAILABLE DSNBS USED yy-rc UNABLE TO PROCESS DSNBS yy-rc INVALID PARAMETER LIST yy-rc ALLOCATION OF TMC AND AUDIT yy-rc INITIALIZATION: INVALID CONTROL RECORDS yy-rc AUDIT DATA SET BACKUP REQUIRED yy-rc UPDATE ACCESS TO THE TMC NOT AUTHORIZED Dyy-rc I/O ERROR ON AUDIT Eyy-rc I/O ERROR ON TMC IEFTMS71 - TMSINIT Abend Process IEFTMS83 - SMF Abend BrightStor CA-1 User Abends System Abends BrightStor CA-1 Common Condition Codes iv Message Guide

5 About This Guide This publication contains the console messages, report messages, system abends, and user abends most frequently encountered during BrightStor BrightStor CA-1 Tape Management operations. It is intended to serve as a reference for WTO/WTOR messages and replies, messages issued by BrightStor CA-1 utility reports, and to assist in problem determination and error recovery. Topics discussed in this guide include: Console messages related to the BrightStor CA-Dynam/T interface, BrightStor CA-1 initialization, backup and restore operations, tape mounts, and externally managed tapes. Messages issued by BrightStor CA-1 utility reports. These messages were formally in the BrightStor CA-1 Utilities and Reports Reference Guide. SVC abends, and BrightStor CA-1 user abends, providing details on any unique return/condition codes and their meanings. A chapter about troubleshooting BrightStor CA-1: problem determination and resolution. Each message, abend, and code is accompanied by a brief explanation and the appropriate response or recommended action for recovery. For other error conditions or failures not related to the messages and abends discussed in the first three chapters in this guide, see the Troubleshooting chapter located in the BrightStor CA-1 Tape Management 5.2 Systems Programmer Guide. Note: Messages unique to converting to BrightStor CA-1 Version 5.2 are described in the BrightStor CA-1 Release Guide. About This Guide v

6 Organization Chapter Description 1 Contains the text for BrightStor CA-1 console messages, the reason a message is produced, and the action required in response. 2 Contains the text for BrightStor CA-1 utility report messages, the reason a message is produced, and the action required in response. 3 Describes system and user abends, the reason for the abend, and the action required in response. vi Message Guide

7 Summary of Revisions Each of the following Version 5.2 enhancements for BrightStor CA-1 are described in detail in the new set of documentation issued for this version. Product Changes and Enhancements Enhancement topics are listed in alphanumeric order. For additional information on the new BrightStor CA-1 Version 5.2 enhancements see the BrightStor CA-1 Tape Management Release Guide. About This Guide vii

8 Summary of Revisions for Service Pack 4 Component Enhancements BrightStor CA-1 Tape Management Version 5.2 Service Pack 4 includes both current maintenance as well as new features. The Service Pack tape is in the standard OS/390 Computer Associates format which provides the ability to only apply maintenance to an existing BrightStor CA environment or to perform a full install of the product with all maintenance integrated into the install libraries. CBRUXVNL Exit Data Erase Utility (CTSDEU) This feature provides a new sample exit for IBM 3494 and 3494/VTS tape libraries (robots). Allows you to erase residual data on tape cartridges for security purposes. Because the new tape media types, such as the IBM 3590 contain servo tracks that can be damaged if a degauss is performed. This utility allows a security erase to be performed on a tape without damaging the servo tracks. Support for Blocking the Tape Management Catalog (TMC) Tape Inquiry (TI) Display Documentation Allows you to increase the number of volume and DSNB records defined to the TMC by providing support for a blocked TMC. The Tape Inquiry (TI) display allows ISPF users to perform a quick lookup of CA-1 TMC data for cataloged data sets using the ISPF 3.4 Data Set List display. The new, easy to read display returns essential information from the CA-1 TMC organized into groups of related fields. Adobe Acrobat PDFs and IBM Books are provided for easy access and printing. The Systems Programmer Guide contains the "Troubleshooting" information previously found in the installation guides. The Master Index is no longer provided as the PDF and Book formats provided offer greater searching capabilities. viii Message Guide

9 Messages New messages have been added to support the CBRUXVNL exit and the CTSDEU utility. About This Guide ix

10 Summary of Revisions for the Sixth Edition The following EDM messages have been added to the TMSTMSTV message identifiers: TMSTMSTV-00 TMSTMSTV-1C TMSTMSTV-20 x Message Guide

11 Summary of Revisions for the Fifth Edition An ERR99 message covering next fields with the same DSNB number as CURDNSB has been added to TMSOSCAT. About This Guide xi

12 Summary of Revisions for the Fourth Edition Removed New messages have been added to the: Abend code - 4yy-rc Invalid Parameter List and 5yy-rc Console messages - Common Tape System (CTS) Operating System Intercepts (OSI) Utility Report messages - CTSPMTS7 All references to Fujitsu and MSP. xii Message Guide

13 Summary of Revisions for the Third Edition Technical changes are indicated by a revision bar ( ) in the margin next to the changed text. Chapter 1, "Console Messages and Replies", contains the following new messages/changes: CA$F002E informs of a missing or invalid DDNAME in the CTS batchjob. CA$F011E, CA$F012E, CA$F013E, CA$F014E, CA$F015E, and CA$F016E have been added for documentation regarding the online label interface (LAB). CA$F130E provides the only valid parameters for TMSINITD. CA$F141E, CA$F152E, CA$F178E, and CA$F204I have been added to document errors in the scratch subpool interface. CA$F808E CMD REJECT OR FILE PROTECTION gives further explanation on possible causes for this message. CAG8001E pertains to the inability to obtain a work area. (OSI) CAG8009E indicates the OSI specified received an invalid return code from the called API. CAL05235 gives further explanation for the message and how to resolve it. CTSDATE01 now provides the return and reason codes. IEFTMS33 notifies that SMF is not active and thus, the CA-1 realtime catalog intercept is no longer active. Chapter 3, "Abend Codes", has the following additions: CA-1 Common Condition Codes Code 4054 Code 4061 About This Guide xiii

14 Summary of Revisions for This Edition AIVS Catalog Control Component Enhancements Allows BrightStor CA-1 to track foreign tapes and tapes with duplicate volsers. This is done by assigning a unique external label from a range predefined to the TMC, and cataloging the file(s) to this external label. At mount time, the mount message contains both the external and internal label. At mount validation time, the difference between the internal VOL1 label and the requested volser is resolved through a new intercept. A new intercept has been introduced which allows the realtime tracking of BrightStor CA-1 controlled tape files. Whenever a catalog or uncatalog operation takes place to a tape volume, the TMC is updated. The result is that TMSCTLG no longer has to be run either in locate mode or by using IDCAMS listings. BrightStor CA-1 now monitors tape CATLG/UNCATLG activity using an SMF exit and records the status in the TMC. Generation data set support is provided for use with ICF catalogs when a generation data set is uncataloged, or it is rolled off when a new generation is cataloged and the GDG limit has been reached. TMSAUDIT has had several new exception records created by TMSSMF83 added to the TYPE control statement. TMSCLEAN has been significantly rewritten with Version 5.2. Nearly all changes were done in the portion of the code dealing with the SCRATCHLIST process. One of the biggest changes is that TMSCLEAN simply reads the TMC looking for eligible volumes and then passes the volsers to a subroutine called TMSSCR which actually performs the scratch process. The CLEAN parameter, cleaning criteria, and the SYSIN control statement to control OUTCODE tapes have been moved to a separate utility. The SCRATCHLIST parameter marks expired tapes available for use and produces a flat file used to produce the Scratch and Clean Listing. The function of TMSCTLG moves to TMSCLEAN if the new system option OCTLG is set to N. This option indicates if the old TMSCTLG program should be used or the new catalog processing in TMSCLEAN. The UNCATA option has been changed to include a default of G (for GDG). A new option SCRCAT controls if data sets currently cataloged should be allowed to go scratch. The handling of foreign tapes has been changed. If a tape goes scratch and has the new FOREIGN indicator set (TMC field FLAG4 bit X'04'), that volume is put into delete status. xiv Message Guide

15 Files controlled by LDATE/ddd or CATLG/ddd have their expiration dates changed even when they reside at an off-site location. TMSCLNOA is a new component which marks volumes that need to be cleaned and sent off-site. This is an optional step that can be run after TMSCLEAN and before the Advantage CA-Earl reports. TMSCONVR has been moved into the BrightStor CA-1 Utilities and Reports Reference Guide from the CA-1 Conversion Guide. This is a batch utility program which reformats any machine-readable data set into one of three possible formats. Depending on the format selected, the output record formats are TMSUPDTE control statements, TMSEXPDT Retention Data Set (RDS) control statements, or TMRECORD (TMC record) format. TMSDATA is a new component which produces sequential data sets from TMC volume records and data set name block (DSNB) records. TMSINIT has added a new option called SECWTO which controls if the WTOR to ask for the user ID/password should be issued. TMSMERGE has added three new SYSIN control statements to support merging of other BrightStor CA-1 data centers with matching volsers or foreign volumes already defined to a Version 5.2 TMC. AIVS=xxxxx FOREIGN=yyyyyy CATALOG=NEVER/AIVS/ALWAYS TMSOSCAT has been changed to report and correct errors based on the new catalog indicator, OCATLG. In addition to reporting on the difference between the TMC and the operating system catalogs, TMSOSCAT can be used to ensure the new TMISCAT TMC FLAG4 bit X'08' and DSNBISCA DSNB FLAG1 bit X'08' are set on for all files currently cataloged. Due to these changes, new parameters have been added to the JCL and enhancements have been made to the Catalog Control statements. New reports have replaced the TMS Report 17 used in Version 5.1. The TMSOSCAT control statements that define report content (R=, LIST=) have been replaced with new parameters. You must revise your TMSOSCAT control statements to use the new parameters if defaults are not accepted. TMSSECUR (online security module) has added two new options, LOGSVC and AUDB4, for security processing. LOGSVC indicates if external security system logging is needed. AUDB4 indicates if an extra BrightStor CA-1 audit record should be written containing the before image of the volume/dsnb record being updated. TMSTPNIT has been enhanced to provide further verification message processing options. TMSVMEDT has added two additional control statements. The Volume (VOL=) and Cataloged Data Set Name (CDSN=) control statements designate specific volume or volume sets that need to be moved to an off-site location. The Vaulting with AND conditions pattern has been changed. About This Guide xv

16 Database Fields Five new fields have been added under FLAG4 in TMMTMREC as follows: TMACVOLI (ACV) reflects that the internal and external volser do not match. TMDEGAU (DEG) reflects that all residual data have been erased. TMISCAT (OSC) reflects the MVS catalog status of the first file on the volume. TMNRS (NRS) is set to indicate this is a foreign volume. TMVSR (VSR) shows that a vaulted volume is eligible to be returned from the vault if no entry for it is found in the VPD. Two new flag byte fields, FLAG5 and FLAG6, have been defined for future use. The size of the existing TMB1DIS (B1 Disclosure Label) and TMB1INT (B1 Integrity Label) have each been reduced from four bytes to three to provide the new flag byte fields. TMACTVL1 (ACTVL1) and TMACTVL2 (ACTVL2) have been created to store the internal volser if different from the external volser. The DSNBISCA (OSC) field has been added to TMMDSNB FLAG1. Installation Options Module Changes An alphabetical listing of the user modifiable fields has been added to the BrightStor CA-1 options section located in the BrightStor CA-1 Systems Programmer Guide. Modules Added CTSPRINT has been added to the CTS library as a supplement to TMSPRINT processing. TMSUX2A added a new function code for the obtain volser process to be used from TMSOCEPR and TMS0MODV. Modules Moved/Renamed EDM detection has been moved and renamed CTSEDMLK or CTMEDLK. TMSARCTV is now a user distributed source module. TMSINITD is now the front-end for the CTS module CTSINITP. TMSINITE has been moved to CTS as CTSINITE. TMSMSGEX and TMSMSGLC have been moved and renamed CTSMSGEX and CTSMSGLC respectively. Modules Removed TMSOCE42 has been removed as it is a duplicate to TMSOCE22. xvi Message Guide

17 MVS Systems Library O/C/EOV Intercepts Realtime Stacking Scratch Subpool Changes Security Features SPLIT/MERGE Docview format documentation for BrightStor CA-1 Version 5.2 is no longer available. It has been replaced by the MVS Systems Library, a multi-product CD-ROM documentation set in IBM BookManager format. A new intercept has been added to support the AIVS feature. AIVS=xxxxxx allows a request for volume (the external volser) to be processed by DFP/Open processing even though the ACTVOL (actual internal volser) is different. It also allows a scratch subpool request to be done using a new VOL=SER=poolid specification which is satisfied by any scratch tape in the requested scratch pool. The existing OPEN for Output indicator is turned off at close time. This allows TMSCLEAN to bypass changing the expiration date for tapes under Catalog Control when they are still in the process of being created. This major new feature of BrightStor CA-1 allows users to stack multiple files on output volumes without making JCL changes, thereby increasing volume utilization. (This feature is provided in maintenance after the initial 9609 genlevel of Version 5.2.) Support has been added to allow scratch subpool assignments to be based on retention and JCL specified by coding the pool-id in the VOL=SER= field. The only limitation is that the pool-id must be 6 characters in length for the JCL method to be used. TMSINIT security has been improved by preventing unauthorized operators or users from activating, deactivating, reinitializing or placing BrightStor CA-1 into batch active status. Audit Before (AUDB4) - See System Options below Log Service Processing (LOGSVC) - See System Options below Recreate (RECRE8) - See System Options below WTOR in TMSINIT (SECWTO) - See System Options below These utilities are used to allow data from one TMC to be merged into another TMC. With the new duplicate volser support, when a conflict is found, the tape has a unique external volser assigned to it. At the same time, the file name can be cataloged to the external volser. When the data is read for input, it is called for by its unique external volser. The O/C/EOV intercept allows the difference in the VOL1 and the file is read. About This Guide xvii

18 Once the file is expired, it is required that the tape be reinitialized prior to its use for output processing. After reinitialization, the internal and external labels match. System Options ADGDG indicates if ADSM pseudo GDGs should be treated as regular GDGs by the vaulting system. AUDB4 controls processing whenever BrightStor CA-1 attempts to update a TMC record for either volume or DSNB type. LOGSVC indicates if external security logging should be performed for successful SVC I/O operations to the TMC or Audit files. OCTLG indicates if the old TMSCTLG utility should still be used (not all systems sharing the TMC have been upgraded to Version 5.2). RECRE8 indicates if BrightStor CA-1 should remove or keep volumes not used during recreate processing. SECWTO controls if WTORs should be issued when TMSINIT is executed as a started task to ensure the operator attempting to reinitialize, stop, or make BrightStor CA-1 batch-active is authorized to perform the desired function. SCRCAT indicates if in addition to the expiration date, TMSCLEAN should analyze the new catalog indicator prior to selecting volumes for scratch processing. UXSCR indicates if the new scratch exit module (TMSXSCR) invoked to scratch volumes should call the optional user exit. The DSSN (Data Set Security DDname) and XMSG (Specific Mount Message) under TMOOPT have been removed. Troubleshooting A Collecting Diagnostic Data table has been added to assist the user. Information has been added regarding accessing the CA home page on the Internet for additional CA products and services. Several changes have been made to the following: Accessing the Online Client Support System Product Versions and Maintenance Requesting Enhancements User Exits All existing realtime user exits have been renamed from TMSUX1x to TMSUX2x with the following exceptions: TMSUX1D is now CTSUXEDM TMSUX1G is now CTSUX1G TMSMSGEX is now CTSMSGEX xviii Message Guide

19 Vault Management System All clients are required to review their existing exits for applicability and assemble, and relink with the new names. This change is required because most of the BrightStor CA-1 exits must be 31-bit addressable and may have new parameter lists. Two new parameters have been added that allow you to designate a specific volume or volume sets that need to be moved to an off-site location without regard for rules. An additional Vault Pattern Example has been added which shows VOL=, CDSN= and DSN= patterns. About This Guide xix

20 Publications The following documentation is supplied with BrightStor CA-1. These manuals are intended to help you learn how to use the product and serve as a reference when problems develop or when you want to expand product use. xx Message Guide

21 BrightStor CA-1 Publications Title CA-ACTIVATOR BrightStor CA-1 Installation and Maintenance Guide BrightStor CA-1 Systems Programmer Guide BrightStor CA-1 Administrator and Operator Guide BrightStor CA-1 General Information Guide Description Describes how to install BrightStor CA-1 using the CA-ACTIVATOR installation driver. Detailed installation considerations and data set storage requirements are supplied to ensure the installer has everything needed before starting the installation. Installation instructions are organized in a detailed, step-by-step procedure. This guide applies only to MVS. Describes how to install BrightStor CA-1 using SMP/E, but without the assistance of CA-ACTIVATOR. Detailed installation considerations and data set storage requirements are outlined to ensure the installer has everything needed before starting the installation. Installation instructions are organized in a detailed, step-by-step procedure. Supplies the systems programmer with the technical information needed to implement and maintain the BrightStor CA-1 system. The guide describes the functional operation of BrightStor CA-1 and provides detailed information on specific BrightStor CA-1 features, programs, macros, user exits, and TMC and Audit data set maintenance. Provides the system administrator, tape librarian and operator with the information needed to run BrightStor CA-1 on a daily basis. The guide discusses daily batch processing, tape library maintenance, Auxiliary Disposition, tape processing, the Vault Management System (VMS), online inquiry and update, and the Common Tape System (CTS) component. Provides a system overview for anyone interested in learning about BrightStor CA-1. This overview describes the features and functions of BrightStor CA-1, such as realtime processing, tape data set retention, online inquiry and update, tape library maintenance, product and security interfaces, and scratch pool management. About This Guide xxi

22 Title BrightStor CA-1 Utilities and Reports Reference Guide BrightStor CA-1 Message Guide BrightStor CA-1 Release Guide Description Reference for all users of BrightStor CA-1. This publication identifies each utility's purpose, JCL and parameter information, control statement specifications, and hardcopy output. The BrightStor CA-1 modules which generate reports are presented alphabetically with complete descriptions of the reports they produce. Field descriptions are included to aid in interpreting the information contained in each report. Contains WTO/WTOR messages and replies, messages issued by BrightStor CA-1 utilities, and system and user abends most frequently encountered during BrightStor CA-1 operations. Each message or code is accompanied by a brief explanation and the appropriate response or recommended action. (Formerly the CA-1 Conversion Guide.) Contains all the information you need to successfully convert to BrightStor CA-1 Version 5.2 from another tape management system or from an earlier version of BrightStor CA-1. Contains descriptions of all conversion utilities and messages issued by these utilities. Related Publications All manuals are updated as required. Instructions accompany each update package. The following publications relate to BrightStor CA-1 and are available from Computer Associates: Title CA Common Services for z/os and OS/390 documentation CA Reference Guide, CAIENF Utilities section Description Various manuals specific to your operating system provide information on installing CA Common Services for z/os and OS/390 with CA-ACTIVATOR, installing CA Common Services for z/os and OS/390 without CA-ACTIVATOR, operating instructions for using and maintaining the CA Common Services for z/os and OS/390, and messages and codes for the CA Common Services for z/os and OS/390. Provides operating instructions for the CAIENF facilities. xxii Message Guide

23 Other Related Publications Disclaimer The following publications are not available from Computer Associates, but are referenced in the BrightStor CA-1 documentation set and are recommended reading: IBM Publications Principles of Operation MVS Interactive Problem Control System (IPCS) Messages and Codes MVS Message Library: System Messages MVS SPL: Initialization and Tuning MVS Catalog Administration Guide MVS Utilities MVS Administration: Macro Instruction Reference MVS Tape Labels MVS Data Facility Product Version 2: Customization SMP/E User's Guide SMP/E Reference SMP/E Messages and Codes SMP/E General Information Manual JES3 SPL: User Modifications and JES3 Macros DFHSM System Programmer's Reference DFHSM Installation and Customization Guide MVS Programming Library: Debugging Handbook All sample code, JCL, and reports that are provided in this guide are intended as reference aids only. No warranty of any kind is made of the completeness or correctness of these samples for your specific installation environment. If you wish to use any of these samples at your site, be sure to adjust them to your specific site standards. About This Guide xxiii

24 xxiv Message Guide

25 Chapter 1. Console Messages and Replies This chapter describes the console messages issued by BrightStor CA-1. Each is accompanied by the reason for the message and any action recommended for problem resolution. Messages are presented in this chapter in alphabetical order by message prefix. Chapter 1. Console Messages and Replies 1-1

26 1.1 Message Variables 1.1 Message Variables The following symbols are used to represent variables within the message text: Symbol cde data dddd dsname expdt fsq hook modulename nn nxx nyy rc rpathid sname spathid uuuu vseq vvvvvv Definition NOT SCRATCH code A parameter or option value Tape drive or device address number JFCB data set name (last 17 characters) Expiration date File sequence number Operating system intercept originating call Module from which the error originated MVS console message number BrightStor CA-1 abend code and BrightStor CA-1 SVC number BrightStor CA-1 abend code and BrightStor CA-1 SVC number Return code indicating a specific occurrence Receiving queue identification (BrightStor CA-Dynam/T interface) Subsystem name Sending queue identification (BrightStor CA-Dynam/T interface) Unit Volume sequence number Volume serial number 1-2 Message Guide

27 1.2 Message Identifiers 1.2 Message Identifiers Messages in this chapter are listed alphanumerically according to message ID. The table that follows indicates the issuing module or function according to message ID. An asterisk (*) indicates any group of letters or numbers may follow. Message ID CA$F000R CA$F001E through CA$F032I CA$F1* through CA$F9* CAG8* CAL0TN01 through CAL0TN07 CAL052C$ CAL052SF CAL05201 through CAL05238 CTSDATE01 CTSPM001 CTSSMS* CTS001 through CTS009 IEBDYN* IEBTMS1 through IEBTMS3 IEBTMS4 IEBTMS10 through IEBTMS11 IEBTMS50 through IEBTMS56 IEBTMS97* IECTMS* IEETMS* IEFTMS0 through IEFTMS19 IEFTMS20 IEFTMS21 IEFTMS22 through IEFTMS26 IEFTMS27 IEFTMS28 Issuing module/function Common Tape System (CTS) Online label interface (LAB) Common Tape System (CTS) Operating System Intercepts (OSI) TMSTPNIT BrightStor CA-1 Security Processor L052INIT CTSDATE CTSPM SMS Mount messages BrightStor CA-Dynam/T interface TMSTPPRO TMSLBLPR TMSAGGR TMSCOPY Online label interface (LAB) Realtime processing Online Inquiry/Update TMSINIT TMSSVC BrightStor CA-1 TMSINIT BrightStor CA-1 SVC BrightStor CA-1 QSAM interface Chapter 1. Console Messages and Replies 1-3

28 1.2 Message Identifiers Message ID IEFTMS29 IEFTMS30 IEFTMS31 through IEFTMS32 IEFTMS50 IEFTMS51 through IEFTMS60 IEFTMS68 IEFTMS70 IEFTMS99 TMAPInnn TMSARCTV* TMSDBS* TMSSMF* TMSTMSTV* TMS001 through TMS009 Issuing module/function TMSINIT BrightStor CA-1 QSAM interface TMSINIT Realtime SVC abends TMSFORMT/TMSCOPY TMSINIT TMS/Audit I/O abends BrightStor CA-1 Realtime processing External data manager Data base services SMF exit (TMSSMF83) External data manager Mount messages 1-4 Message Guide

29 1.2 Message Identifiers CA$F000R CA$F005E CA$F000R CA$F001E CA COMMON TAPE SYSTEM COMMANDS? Explanation: This message appears when the WTOR option is specified. Commands to CTS can be entered as a reply to this message. User Response: Enter desired CTS commands. REQUIRED MODULE MISSING - xxxxxxxx Explanation: The module listed in the message cannot be located. User Response: Verify that the module listed in the message resides on a library in your STEPLIB or link list and restart CTS. CA$F002E REQUIRED DDNAME MISSING OR INVALID - xxxxx Explanation: CTS was started as a batch job instead of a started task. As a batch job, CTS does not intercept label requests via ENF/CCI. User Response: If you desire to run CTS as a batch job, then add the input ddname and input control statements as documented in Chapter 10 of the BrightStor CA-1 Administrator and Operator Guide. CA$F003E CA$F004E CA$F005E OPEN UNSUCCESSFUL ON FILE - xxxxxxxx Explanation: An OPEN was unsuccessful for the file listed in the message. User Response: If this message is accompanied by message CA$F004E, see that message for additional information; otherwise, ensure that the file's DD statement is coded properly in the JCL and restart CTS. TAPEDB ERROR OCCURRED - FN=xxxx,RC=xxxx,RS=xxxx,FB=xxxx Explanation: An error occurred processing the BrightStor CA-1 Tape Management Catalog (TMC). The function code (FN), return code (RC), reason code (RS) and feedback (FB) are described in the message. See 1.2.1, I/O Module Codes on page User Response: Correct and restart CTS. DYNAMIC ALLOCATION ERROR ON xxxxxxxx RC=xxxx,EC=xxxx,IN=xxxx Explanation: A dynamic allocation error occurred on the DDNAME listed in the message. The dynamic allocation return code (RC), error code (EC) and information code (IN) are listed in the message. User Response: Check to ensure the DDNAME listed in the message does NOT exist in the CTS startup JCL and that the corresponding OUTPUT statement for the printer being dynamically allocated DOES exist and is coded correctly. Se the BrightStor CA-1 Administrator and Operator Guide for information on dynamically allocated label printers. See the IBM MVS/ESA System Programming Library: Application Development Guide for more information on dynamic allocation codes. Chapter 1. Console Messages and Replies 1-5

30 1.2 Message Identifiers CA$F006E CA$F012E CA$F006E CA$F007E CA$F008E CA$F009E CA$F010E VOLUME NOT FOUND ON DATABASE - xxxxxx Explanation: A VOLUME request for the volume serial number listed on the message was requested but the volume serial number does NOT exist on the TMC. User Response: Correct and resubmit the request. LABEL IMAGE ROWS xxxx OR COLUMNS xxxx INVALID Explanation: The label image processed by the output label processor contains an invalid number of ROWS or COLUMNS as listed in the message. ROWS must be from 1 to 66 and COLUMNS must be from 1 to 132. User Response: Correct, restart the LAB subtask, and resubmit the request. LABEL REQUEST PRINTER VALUE(S) INVALID - x-x-x Explanation: The three printer request fields for the label request are listed in the message above. These values relate to PRINTER1, PRINTER2 and PRINTER3 respectively. The value for each of these must be Y (to select the specific printer for output) or N (to bypass the printer). User Response: Correct, restart the LAB subtask, and resubmit the request. LABEL REQUEST WTO ROUTE CODE(S) INVALID - xxxx-xxxx-xxxx Explanation: The three WTO route codes for the label request are listed in the message above. The value for each of these must be 001 through 128 to select the specific route code or 000 to not assign a WTO route code. User Response: Correct, restart the LAB subtask, and resubmit the request. PROGRAM PARAMETER LIST IS MISSING OR INVALID Explanation: The program parameter list for either the input or output label processor is invalid. The calling sequence must contain two addresses. The first address must point to the Advantage CA-Earl label image record and the second address must point to the Advantage CA-Earl communication area. User Response: Correct, restart the LAB subtask, and resubmit the request. CA$F011E KEYWORD REQUESTED "xxxxxxxx" ALREADY PRESENT - RECORD xxxx Explanation: Keyword is already specified. User Response: None. This is an informative message. CA$F012E LABEL REQUEST MISSING FOR KEYWORD "xxxxxxxx" - RECORD xxxx Explanation: The label request is missing for the specified keyword. User Response: Supply missing label request. 1-6 Message Guide

31 1.2 Message Identifiers CA$F013E CA$F021E CA$F013E KEYWORD "xxxxxxxx" INVALID FOR THIS REQUEST - RECORD xxxx Explanation: An invalid keyword was used for this request. User Response: Supply a valid keyword. CA$F014E KEYWORD "xxxxxxxx" OR KEYWORD VALUE INVALID - RECORD xxxx Explanation: An invalid keyword or keyword value was used for this record. User Response: Supply a valid keyword or keyword value. CA$F015E LABEL LENGTH xxxx NOT = ROWS xxxx * COLS xxxx - RECORD xxxx Explanation: Label length is incorrect. User Response: Supply correct label length. CA$F016E MAXIMUM LENGTH OF xxxxxxxx VALUE EXCEEDED - RECORD xxxx Explanation: The maximum length of specified value has been exceeded. User Response: Shorten length to be less than maximum allowed. CA$F017E CA$F018I CA$F020E CA$F021E INPUT REQUEST TYPE "x" IS INVALID Explanation: The input request type listed in the message above is invalid for the label output processor. Valid request types are L (Label request), S (Spinoff request), and C (Close request). User Response: Correct, restart the LAB subtask, and resubmit the request. SPINOFF REQUEST PROCESSED SUCCESSFULLY Explanation: The label output processor received a SPINOFF request and it was processed successfully. User Response: None. This is an informative message. CCI RC=xxxx,DRC=xxxxxxxx,ERC=xxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxx Explanation: An error has occurred processing a CAICCI request. The CAICCI return code (RC), detailed return code (DRC), extended return code (ERC) and error description are listed in the message. See CA Common Services for z/os and OS/390 documentation for additional information. User Response: Ensure that CAICCI and CAIENF are active. Once the problem has been resolved, resubmit the request. CCI DESTINATION INVALID - "xxxxxxxxxxxxxxxxxxxx" Explanation: The CAICCI destination listed in the message is invalid as entered. See the BrightStor CA-1 Administrator and Operator Guide for additional information. User Response: Correct, restart the LAB subtask, and resubmit the request. Chapter 1. Console Messages and Replies 1-7

32 1.2 Message Identifiers CA$F022E CA$F031I CA$F022E CA$F026E CA$F027E CA$F028I CA$F029I CA$F030I CA$F031I CCI DESTINATION NOT AVAILABLE - "xxxxxxxxxxxxxxxxxxxx" Explanation: The CAICCI destination listed in the message is currently not available on the ENF/CCI network. See CA Common Services for z/os and OS/390 documentation for additional information. User Response: Correct and resubmit the request. INVALID REQUEST/VALUE - xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Explanation: The command that was issued to the LAB subtask or the parameter accompanying the command is invalid. If a command and parameter were entered, make sure they are separated by a blank and enclosed within single quotes or parentheses. (For example, 'SPINOFF PRINTER1') User Response: Correct and resubmit the request. REQUEST NOT PROCESSED - xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Explanation: The command that was issued to the LAB subtask was not processed due to a previous error. User Response: Correct and resubmit the request. LABEL PROCESSING STATUS - STARTED AT hh:mm:ss ON xxxxxxxxxx Explanation: This message is issued as a result of the STATUS command. It indicates the time and date the label processing was initiated. This message is accompanied by message CA$F029I. User Response: None. This is an informative message. VOLUME=nnnnn,DATA=nnnnn,LABEL=nnnnn,SPINOFF=nnnnn, ERRS=nnnnn Explanation: This message is issued as a result of the STATUS command. It indicates the current count of VOLUME, DATA, LABEL and SPINOFF requests that have been processed since the label processor was initiated. Additionally, an error count associated with VOLUME requests is provided. This message is preceded by message CA$F028I. User Response: None. This is an informative message. LABEL INITIALIZATION STARTED Explanation: This message is issued when the label processor is started. User Response: None. This is an informative message. LABEL INITIALIZATION COMPLETED Explanation: This message is issued when the label input processor has completed the initialization process and is ready to receive and process input requests through CA Common Services for z/os and OS/390 CAICCI. User Response: None. This is an informative message. 1-8 Message Guide

33 1.2 Message Identifiers CA$F032I CA$F130E CA$F032I LABEL PROCESSING COMPLETED Explanation: This message is issued when the label processor has closed all files and processing has terminated. User Response: None. This is an informative message. CA$F110W OVER 50 UNCATALOGS FOR GDG data.set.name Explanation: An alteration of a tape GDG caused more than 50 generations of the GDG to be uncataloged. The catalog interface of BrightStor CA-1 is limited to handle 50 uncatalog opertions at a time for performance reasons. Only the 50 oldest versions being uncataloged will get the OSC flag bit turned off automatically in the TMC. User Response: If the data sets are retained by CATALOG control and system option OCTLG is set to NO, a manual TMC update of the remaining versions is required to get the tapes expired and scratched. If necessary, use TMSOSCAT with options NODE and ISCAT to determine the orphaned records. Also, a TMSAUDIT report can be created for this purpose. An Audit exception record type EX-CLJ is written for the last GDG version which was processed. Execute TMSUPDTE or TMSUDSNB respectively to turn the OSC bits off for all newer versions which are no longer cataloged. CA$F120I CA$F121I INIE Beginning xxxxxxxx procedure Explanation: This message is issued to indicate that processing of the External Data Manager (EDM) definitions in the CAI.PPOPTION member has been initiated. The member being processed will appear in place of 'xxxxxxxx'. User Response: No action is necessary. The message is issued to provide confirmation that the correct EDM member is being processed. INIE Processing for TMSPARM member xxxxxxxx complete Explanation: This message is issued to indicate that processing of the External Data Manager (EDM) definitions in the CAI.PPOPTION member has been completed. If errors were encountered separate error messages may precede this message. The member being processed will appear in place of 'xxxxxxxx'. User Response: No action is necessary. The message is issued to provide confirmation that processing of the EDM has completed. If errors were encountered, see the specific error error message for detailed instructions. CA$F130E INIP INVALID PARAMETER Explanation: SCR=xx and NSM=xx are the only valid parameters for TMSINITD. User Response: Ensure the parameter is entered correctly. If you wish to analyze a member other than the TMOSCRxx or TMONSMxx member, use TMSINIT with the TEST parameter. Chapter 1. Console Messages and Replies 1-9

34 1.2 Message Identifiers CA$F132I CA$F152E CA$F132I CA$F133I INIP Beginning xxxxxxxx and yyyyyyyy procedure Explanation: This message is issued to indicate that processing of the scratch pool (TMOSCRxx) and scratch pool assignment (TMONSMxx) members has been initiated. The members being processed will appear in place of 'xxxxxxxx' and 'yyyyyyyy'. User Response: No action is necessary. The message is issued to provide confirmation that the correct SCR and NSM members are being processed. INIP Processing for TMSPARM member xxxxxxxx complete Explanation: This message is issued to indicate that processing of the scratch pool definitions member TMOSCRxx or scratch pool assignment member TMONSMxx has been completed. If errors were encountered, separate error messages may precede this message. The member being processed will appear in place of 'xxxxxxxx'. User Response: No action is necessary. The message is issued to provide confirmation that processing of the EDM has completed. If errors were encountered, see the specific error error message for detailed instructions. CA$F135E INIP INVALID STATEMENT SYNTAX Explanation: Syntax in TMONSM00 or TMOSCR00 is invalid. User Response: Correct the syntax of the statement. CA$F136E INIP Invalid keyword Explanation: An invalid keyword has been specified. User Response: Correct the invalid keyword that is identified in the report. CA$F141E INIP SCRPOOL not first keyword Explanation: The SCRPOOL keyword must be first. User Response: Ensure the SCRPOOL is the first keyword of the Name Control statement. This error may also be caused by a previous error in the TMOSCRxx member. CA$F144E INIP RANGE overlaps with RANGE previously defined Explanation: Ranges in TMOSCRxx overlap. User Response: Correct ranges. CA$F152E INIP PoolName not found in Scratch Subpool table Explanation: The PoolName specified in the TMONSMxx member was not found in the Scratch Subpool table. User Response: Ensure that the PoolName specified in the TMONSMxx member is defined in the TMOSCRxx member. This error may also be caused by errors in the TMOSCRxx member Message Guide

35 CA$F178E INIP RANGE keyword(s) must be used after STACK, or stacking keywords Explanation: The order of keywords in the TMOSCRxx is incorrect. 1.2 Message Identifiers CA$F178E CA$F807E User Response: The RANGE keyword(s) must be coded after STACK or the stacking keywords. Recode the TMOSCRxx keywords so that the RANGE keyword(s) are the last keywords for the pool. CA$F204I JFCB NOT FOUND STACKING FAILED Explanation: The JFCB control block could not be found. User Response: Because the JFCB could not be found, Realtime Stacking could not be performed and a normal scratch subpool mount request has been issued. CA$F801E CA$F802E CA$F803E CA$F804E CA$F805E CA$F806W CA$F807E INVALID FUNCTION. Explanation: The specified function is not valid for this module. User Response: Correct and rerun. IMPROPER SEQUENCE FOR THIS FUNCTION. Explanation: This function was issued out of sequence. An example is a GET before an OPEN. User Response: Correct and rerun. SPECIFIED DDNAME NOT FOUND. Explanation: The ddname specified in the OPEN function was not found. User Response: Correct and rerun. DSN= IS NOT DSORG=oo. Explanation: This I/O program is for processing oo data sets. User Response: Select another I/O program or change the data set organization to oo. OPEN cccccc FAILED FOR FILE. Explanation: The OPEN function of type cccccc failed. User Response: Correct and rerun. GET ISSUED AFTER EOF. Explanation: CTSSIO: Calling program requested a GET after End-Of-File was reached on the data set. User Response: None. This is an informative message. ffffffff IS UNKNOWN CTL FUNCTION. Explanation: CTSSIO: The subfunction ffffffff for a control function is invalid. User Response: Correct and rerun. Chapter 1. Console Messages and Replies 1-11

36 1.2 Message Identifiers CA$F808E CA$F899I CA$F808E CMD REJECT OR FILE PROTECTION. Explanation: Tape had write protection turned on so tape could not be initialized. This may also be caused by security when the user does not have BLP update authority. User Response: Turn off write protection and rerun the job. CA$F808E CA$F809E CA$F810A CA$F811E CA$F812E CA$F813A CA$F899I MEMBER mmmmmmmm NOT FOUND ON FILE Explanation: The specified member was not found in the data set. User Response: Correct and rerun. MEMBER mmmmmmmm DIRECTORY UPDATE FAIL RC=nn. Explanation: The STOW failed for the specified member with a return code of nn. User Response: Correct and rerun. M vvvvvv ON dddd. Explanation: Tape vvvvvv is required by the tape I/O module for processing. User Response: Mount volume vvvvvv on unit dddd. EXCP FUNCTION FAILED. Explanation: The program could not execute the I/O it required. User Response: Check other messages to determine if the cause of the problem was hardware or software. Correct and rerun. INVALID TAPE LABEL DATA. Explanation: An invalid label has been detected during tape initialization processing. User Response: Correct and rerun. K vvvvvv FROM dddd. Explanation: Tape initialization processing for vvvvvv is complete on unit dddd. User Response: Remove vvvvvv from unit dddd. FN=ffffffff RC=cccccccc RS=ssssssss FB=bbbbbbbb DD=dddddddd Explanation: This message is issued to give more information about the previous error message. Where ffffffff is the requested function; cccccccc is the return code (also is R15); ssssssss is the reason code; bbbbbbbb is the feed-back; and ddddddd is the related ddname. See 1.2.1, I/O Module Codes on page User Response: Correct and rerun Message Guide

37 1.2 Message Identifiers CA$F900I CA$F973E CA$F900I CA$F910I CA$F920W CA$F969E CA$F970E CA$F971E CA$F972E CA$F973E DUMP SPINOFF IS COMPLETE Explanation: The dump data set has been spooled to SYSOUT for printing. This can be the result of a SPINOFF DUMP command or automatically when a task abnormally terminates. User Response: None. This is an informative message. DUMP SPINOFF SUSPENDED BY OPERATOR Explanation: The spooling of the dump data set to SYSOUT is terminated, because the operator issued a CANCEL DUMP command. User Response: None. This is an informative message. NO DUMP DATA PENDING Explanation: A SPINOFF DUMP command was issued and the dump data set was empty. User Response: None. This is an informative message. MISSING A REQUIRED PARAMETER. Explanation: A parameter required for the command was not specified. User Response: Correct and retry. UNKNOWN OR UNEXPECTED PARAMETER. Explanation: An internal message to task tttt was sent while processing the command. CTSCOM was unable to complete the send. User Response: Start the task if not active or issue the command to another task. PARAMETER IS TOO LARGE. Explanation: A parameter value was specified which is too large. User Response: Correct and retry. INVALID CHARACTER IN COMMAND. Explanation: Only alphanumeric and national characters are permitted on the command line. Special characters must be enclosed in '...' or (...). User Response: Correct and retry. NO DELIMITER FOUND. Explanation: No delimiter was found on the command line. User Response: Correct and retry. Chapter 1. Console Messages and Replies 1-13