IBM TS7700 Series Operator Informational Messages White Paper Version 2.0.1

Transcription

1 Apr 13, 215 IBM TS77 Series Operator Informational Messages White Paper Version 2..1 Dante Pichardo Tucson Tape Development Tucson, Arizona

2 Apr 13, 215 Introduction During normal and exception processing within an IBM tape library, intervention or action by an operator or storage administrator is sometimes required. IBM tape libraries have an optional facility that causes a z/os console message, CBR375I, to be displayed when intervention or action is needed. The intervention or action may require immediate attention to continue library processing or may be something that can be handled at a later time. The purpose of this white paper is to list the intervention or action messages that are generated and to indicate the importance of each message in regards to how they need to be handled. The white paper is targeted for the following customer personnel: System Operators System Administrators Summary of Changes This is the initial version of the document. April 16, 212 Added new host console messages August 1, 212 Added host console message for auto-removal completion September 4, 212 Added host console message AL512 and AL513 December 6, 212 Update for ETC, Hydra 3. January 31, 212 Set correct version number to 1.6April 16, Version 1.7 Added host console message AL514 July 1, 213 Added new host console messages for H3.1 July 26, 213 Version Added Trigger Type (TT) column. Included CBR messages other than CBR375I to the end of the document. March 26, 214 Added TT for H3.1 May 8, 214 Added AL12, AL13, AL515 and AL516 for H3.2 Sep 17, 214 Added G35 for H3.2 Apr 13, 215 Added new RAS interventions for H3.2 Configurations Supported All currently supported ESCON/FICON attached IBM tape libraries, including native partitions and those with Virtual Tape Servers or Virtualization Engines as well as their associated library manager, generate notifications to their attached hosts to inform the customer of conditions or events that have occurred within the product. Those libraries are the 3494 and the TS35 (aka 3584) with a However, not all messages are generated by all level of code on all products. Copyright 28, 215 IBM Corporation Page 2 of 29

3 Apr 13, 215 Intervention and Informational Message Overview During normal and exception processing within a library with a library manager or the TS77 associated with a library, these products may encounter conditions or events that require some level of action by an operator. As these conditions or events are encountered, a message text, called an intervention message, is logged. An operator can monitor and view the intervention messages through the TS77 web interface. Optionally, the text associated with the intervention message can be sent to all hosts that are attached to the subsystem in the form of a message. To send all intervention messages to the hosts attached to its associated native drive controller, TS77 or VTS products, go to the Events panel and click the Enable Host Notification button in the Actions menu, then click OK in the confirmation dialog. See below for an example of the Events panel displayed through the web interface: Copyright 28, 215 IBM Corporation Page 3 of 29

4 Apr 13, 215 The default is to not send the messages, so if you want them to be sent, you will need to enable it as described above. The TS77 and VTS products may also generate informational messages. These messages provide information about an operation that is taking place within the product and may or may not require operator action. Informational messages are always sent to the hosts attached to the product. If the TS77 generating the message is a member of a Grid, the message is sent to all hosts that are attached to all of the TS77s in the Grid configuration. If the VTS is a member of a Peer-to-Peer VTS, the message is sent to all hosts attached to the Virtual Tape Controllers of that PTP VTS. Only the z/os platform currently supports receiving the messages and generates the following host console message: CBR375I Message from library library-name: message-text Where library-name identifies the source of the message. Messages can come from a native library partition, standalone VTS or the composite or distributed libraries in a TS77 or a PTP VTS. This is the eight character library name that had been previously defined through the library definitions panels through z/os. The message-text contains the information being provided. Included in the message-text is a five character message ID field that may be examined by message automation software to filter or route specific messages. The message text can be up to 24 characters in length. In the following table, the intervention and informational messages are defined. For each message, an impact code based on the action required and potential to impact operations is assigned as follows: Impact Code Impact Description Action Critical C Operations in the reporting TS77/VTS/ are stopped, all jobs allocated may fail. action Serious Impact Warning S I W Information M One or more jobs may fail, some logical volumes may be inaccessible, mounts are suspended, performance may be degraded No immediate impact to operations, but ejects cannot proceed, input station processing problem, early warning for serious type interventions including performance degradation, copies may not be performed or are degraded. No immediate impact to operations, redundant resource lost, installation/configuration problem or change, drive cleaning may be impacted Informational message about operations in the TS77/VTS/library Immediate operator, system administrator or service representative Important to examine message, take action as needed Examine message as time allows Examine message as time allows Log for historical review Copyright 28, 215 IBM Corporation Page 4 of 29

5 Apr 13, 215 The product area associated with the message is also listed and could be used when deciding who to evaluate the message. The product areas are: - regarding the physical library Media - regarding a physical tape cartridge Tape Drive - regarding a physical tape device - regarding the library manager code and hardware VTS/TS77 - regarding the VTS or TS77 code and hardware Control Unit - regarding the control unit code or hardware Refer to the IBM 3953 Model L5 Operator s Guide or the IBM TotalStorage 3494 Tape Operator s Guide for the probable cause for the intervention condition and the actions required for resolution. In the message text, n s, m s, x s, y s and z s are replaced with values specific for the message. TT Trigger Type This column provides guidelines for which interventions or events may want to be monitored by host automation. The column indicates if the event is a setting of a condition ( C or S ) or a clearing of a condition ( c or r ). The column also indicates whether the intervention or event is a customer ( C and c ) responsibility or an IBM ( S and r ) responsibility. C Customer responsibility Condition is set c Customer responsibility Condition is cleared S IBM responsibility Condition is set Notify IBM r IBM Responsibility Condition is reset Notify IBM Blank requires no trigger. None M VTS/TS77 None M VTS/TS77 None W VTS/TS77 None M VTS/TS77 VTS Database Backup written to Physical Tape RSG632. Temporary Conflict for Volser xxxxxx - LM paused or long drive op ERROR - Drive types in VTS are mixed or cannot ID drives Checkfiles created on virgin VTS system AL M C AL1 M c AL4 M S AL5 M r VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 Uncopied data of xxxx GB above low warning limit of yyyy GB. No longer above uncopied data low warning limit of yyyy GB. Available physical drives of nn is below low limit of xx. Available physical drives no longer below low limit of xx. Copyright 28, 215 IBM Corporation Page 5 of 29

6 Apr 13, 215 VTS/TS77 Available physical scratch volumes nnn below low limit of xxx for AL6 M C pool yy. VTS/TS77 Available physical scratch no longer below low limit of xxx for pool AL7 M c yy. VTS/TS77 AL8 M C Resident data of nnnn GB above low warning limit of xxxx GB. VTS/TS77 AL9 M c No longer above resident data low warning limit of xxxx GB. Distributed xx has a total pending inbound copy backlog of AL1 M C TS77 yyyy GB which is above the low warning limit of zzzz GB Distributed xx has successfully fallen below the inbound AL11 M c TS77 copy backlog low warning limit of zzzz GB TS772 Sum of resident data in tape partitions of nnnn GB above low AL12 M C Tape Attach warning limit of xxxx GB. TS772 Sum of resident data in tape partitions no longer above low warning AL13 M c Tape Attach limit of xxxx GB. VTS/TS77 AL2 M Database Backup written to Encrypted Physical Tape vvvvvv. VTS/TS77 TS774 is unable to communicate with at least one Encryption Key AL21 M C VTS/TS77 AL5 M C Uncopied data of nnnn GB above high warning limit of xxxx GB VTS/TS77 AL51 M c No longer above uncopied data high warning limit of xxxx GB. VTS/TS77 AL54 M S Available physical drives of nnn is below critical limit of xxx. VTS/TS77 AL55 M r Available physical drives no longer below critical limit of xxx. VTS/TS77 Available physical scratch volumes nnn below critical limit of xxx AL56 M C for pool yy. VTS/TS77 Available physical scratch no longer below critical limit of xxx for AL57 M c pool yy. VTS/TS77 AL58 M C Resident data of xxxx GB above high warning limit of yyyy GB. VTS/TS77 AL59 M c No longer above resident data high warning limit of yyyy GB. Distributed xx has a total pending inbound copy backlog of AL51 M C TS77 yyyy GB which is above the critical warning limit of zzzz GB Distributed xx has successfully fallen below the inbound AL511 M c TS77 copy backlog critical warning limit of zzzz GB AL512 M TS77 Auto removal of volumes has completed on this disk only cluster. Physcial volume xxxxxx from <cluster name or library id> has been AL513 M TS77 erased AL514 M TS77 BVIR volume map exceeds <maximum number of records> records AL515 M C AL516 M c TS772 TS772 Sum of resident data in tape partitions of nnnn GB above high Sum of resident data in tape partitions no longer above high warning Tape Attach Tape Attach warning limit of xxxx GB. limit of xxxx GB. G1 M VTS/TS77 Service preparation has started for distributed library xx. G2 M VTS/TS77 Service preparation has completed for distributed library xx. Copyright 28, 215 IBM Corporation Page 6 of 29

7 Apr 13, 215 G3 W VTS/TS77 G4 M VTS/TS77 G5 I VTS/TS77 G6 M VTS/TS77 G7 W VTS/TS77 G8 W VTS/TS77 G9 S S G1 S S G11 M r G12 W G13 S S G14 M r G15 M r G2 G21 G22 M M M G23 S S G24 S S G25 S S G26 S S G27 M r VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 Service preparation has failed for distributed library xx. Service preparation has exited for distributed library xx. Distributed library xx has entered the immediate deferred state. Distributed library xx has exited the immediate deferred state. A user at library xx has enabled Read/Write takeover against library yy. A user at library xx has enabled Read-Only takeover against library yy. Autonomic ownership takeover manager within library xx has determined that library yy is unavailable. The Read/Write ownership takeover mode has been enabled. Autonomic ownership takeover manager within library xx has determined that library yy is unavailable. The Read-Only ownership takeover mode has been enabled. Ownership takeover mode within library xx has been automatically disabled now that library yy has become available. A user at library xx has disabled the ownership takeover mode within the grid against library yy. xx has experienced an unexpected outage with its peer library yy. yy may be unavailable or a communication issue may be present. xx is now available to the peer library yy. xx has restored communication and is now available to the peer library yy. xx has taken over ownership of volume yyyyyy from library zz using a read/write takeover mode. mmmmmm total volumes have been taken over from peer clusters. xx has taken over ownership of volume yyyyyy from library zz using a read-only takeover mode. mmmmmm total volumes have been taken over from peer clusters. xx has reconciled volume yyyyyy against library zz with respect to ownership takeover. mmmmmm total volumes remain in the takeover state against one or more peer libraries. xx has moved volume yyyyyy into the damaged state due to ownership takeover conflict. mmmmmm total volumes now exist in the damaged state. xx has moved volume yyyyyy into the damaged state due to token corruption. mmmmmm total volumes now exist in the damaged state. xx has moved volume yyyyyy into the damaged state due to disaster recovery. mmmmmm total volumes now exist in the damaged state. xx has moved volume yyyyyy into the damaged state. mmmmmm total volumes now exist in the damaged state. xx has moved volume yyyyyy out of the damaged state and into the insert category. mmmmmm total volumes remain in the damaged state. Copyright 28, 215 IBM Corporation Page 7 of 29

8 Apr 13, 215 G3 I S VTS/TS77 G31 M r VTS/TS77 G32 M C VTS/TS77 G33 M c VTS/TS77 G34 M VTS/TS77 G35 S C VTS/TS77 xx Pri,Alt,Pri2,Alt2 Grid Link are degraded. (degraded Grid link port is also reported) All grid links for this cluster have left the degraded state. XX copies have been queued for over 24 hours. Check Incoming Copy Queue on the MI for details. Distributed xx has entered the synchronous deferred state due to volser yyyyyy. Distributed xx has exited the synchronous deferred state. Distributed xx mount failed due to excessive large volume mounts. OP1 S C The convenience I/O station should be empty but is not, visually check the station. OP2 S S A cartridge has been dropped. OP3 I C * The convenience I/O station is full. OP4 I C * The virtual library is full. OP5 S C Media A duplicate volser (xxxxxx) was ejected to the convenience I/O station. OP6 I C Media A duplicate volser (xxxxxx) was left in the convenience I/O station. OP7 I C Media A VOLSER (xxxxxx) with an unknown media type has been ejected to the convenience I/O station. OP9 I C Media OP1 I C OP11 I S Media An invalid VOLSER (xxxxxx) has been ejected to the convenience I/O station. During an Inventory Update operation, VOLSER (xxxxxx) was ejected to the convenience I/O station because there were no free cells. An error occurred for cartridge xxxxxx during insert from convenience I/O slot number yy to cell: Rack number: nn Rack column: mm Rask row: zz OP12 I C Media An unreadable volser was left in high-capacity input rack cell yyyy. OP13 I C Media The cartridge label located at cell (rack number:nn, rack column:mm, rack row:zz) has an unknown media type. OP14 I C Media An invalid volser (xxxxxx) was left in the convenience I/O station. OP15 I C Media The cartridge label located at cell (rack number:nn, rack column:mm, rack row:zz) is unreadable. OP16 I C Media The cartridge label located at cell (rack number:nn, rack column:mm, rack row:zz) is Invalid. OP17 S S Tape Drive A load or unload failure has occurred on device: nnnn OP18 I C Media Target Storage Pool nn is out of physical volumes. OP19 I S Media VOLSER xxxxxx is damaged. OP2 I C * The convenience I/O station door is open. OP21 I C * The convenience I/O station door is open. OP22 S S Media Unknown intervention for condition xxxxxx OP23 S C Media Volser (xxxxxx) could not be put away. It was ejected to high- Copyright 28, 215 IBM Corporation Page 8 of 29

9 Apr 13, 215 capacity output rack cell: yyyy. OP24 I C A duplicate VOLSER has been found at cell nnn. OP25 S S OP26 S S A cartridge has been dropped. A duplicate VOLSER has been found at cell nnn.a cartridge could not be released from gripper x, accessor y. OP27 S Pool nn is defined with a different media class and was reset to match. OP28 C,S Note 1 S An emergency stop has occurred. OP29 S C Media Damaged volser (xxxxxx) ejected to the convenience I/O station. OP3 S C Media Cartridge (xxxxxx) has been left in uninstalled device. OP31 I S Tape Drive Device xxx is not ready. OP32 I S Tape Drive Device xxx is reporting an element address of zero. Call service. OP33 I C High capacity input station should be empty but is not. OP34 I C Media A mislabeled cleaner cartridge has been left in device xxx feed slot. Remove the cartridge. OP35 W S Tape Drive A recoverable error occurred on device xxx. A service call may be needed if the error persists. OP36 W C Media A cartridge containing invalid media has been left in device xxx feed slot. Remove the cartridge. OP37 W C Media An invalid media volser <xxxxxx> has been ejected to the convenience I/O station. OP38 S C Media A cartridge or cartridge label located at cell x y zz is upside-down. OP39 S C Media A duplicate Volser has been found at cell yyyy. OP4 S C Media The cartridge label located at cell yyyy is unreadable. OP41 S C Media The cartridge label located at cell yyyy is invalid. OP42 C,S Note 1 S The system has failed. A service call is required. OP43 C S * The accessor or gripper configuration has changed. The 3494 must be retaught. OP44 I C * The top two I/O station cells are inaccessible. Move cartridges to cell 3. OP45 S C Volser xxxxxx cannot be removed from its home location.. OP46 I C Volser (xxxxxx) cannot be removed from the high-capacity station cell: yyyy. OP47 I S Tape Drive The device xxxxxx has failed and a service call is required to correct the problem. OP48 I C Media A volser xxxxxx has an incorrect media type on the external label. OP49 S S Media OP5 S S Media A physical device's install status or online status has changed for a device attached to the TS77 Virtualization Engine. Control of this physical device has been switched to the node on this cluster (the cluster where the operator intervention is listed). OP51 W Media * The library is out of HPCT cleaner cartridges. OP52 S C Media A volser (xxxxxx) with an unknown media type has been ejected to the convenience I/O station. OP53 S C Media A volser (xxxxxx) with an unknown media type has been ejected to high-capacity output facility cell: yyyy. OP54 I C Media Volser (xxxxxx) cannot be removed from convenience I/O station. OP55 I C VTS/TS77 Free storage threshold has been crossed for VTS z. OP56 I C Media A volser (xxxxxx) with an unknown media type has been left in the Copyright 28, 215 IBM Corporation Page 9 of 29

10 Apr 13, 215 convenience input station. OP57 I C Media A volser (xxxxxx) with an unknown media type has been left in the high-capacity input station. OP58 S C Media An invalid volser (xxxxxx) has been ejected to the convenience I/O station. OP59 S C Media The cartridge label located at cell yyyy has an unknown media type. OP6 S C Media During an Inventory Update operation, volser xxxxxx was ejected to the convenience I/O station because there were no free cells. OP61 S C Media During an Inventory Update operation, volser xxxxxx was ejected to the high capacity station because there were no free cells. OP62 C,I Note 1 S Power failure on accessor x. A service call is required. OP63 C TS77 Limited Cache Free Space W OP64 W S Dual Write has failed. A service call is required. OP65 C TS77 Out of Cache Resource. VTS/TS77 * One or more volumes have been inserted into the library and OP66 M marked unassigned. Eject failed for volser xxxxxx. This operation was initiated by the OP67 I Media. OP68 M OP69 W OP7 W A hard drive has failed. Call service. A switch has completed. This switch was initiated A switch has completed. This switch was due to an by the operator. error. OP71 W Mirroring disabled. Call service. is operational but degraded. Or LM-x mirroring disabled. Call service. is operational but degraded. OP72 C S Barrier door A is not fully retracted. Call service. OP73 C S Barrier door B is not fully retracted. Call service. OP74 S Control unit on port xx requires a higher level of. OP75 I Database discrepancies have been found. Call service. is still operational. OP76 S S Media Volser xxxxxx cannot be found. Check home cell: yyyy and accessor A, gripper 1. OP77 S S Media Volser xxxxxx cannot be found. Check home cell: yyyy and accessor A, gripper 2. OP78 S S Media Volser xxxxxx cannot be found. Check home cell: yyyy and accessor B, gripper 1. OP79 S S Media Volser xxxxxx cannot be found. Check home cell: yyyy and accessor B, gripper 2. OP8 W OP81 C S OP82 I S Media OP83 I S Media Error writing to dual write log (on A or B). An emergency stop has occurred, or accessor A or B has failed. A service call is required. Volser xxxxxx left in convenience I/O slot nn due to vision system failure. Volser xxxxxx left in high capacity rack cell xx y zz due to vision system failure. Copyright 28, 215 IBM Corporation Page 1 of 29

11 Apr 13, 215 OP84 W OP85 W OP86 W OP87 W S OP88 S C VTS/TS77 OP89 W VTS/TS77 OP9 W VTS/TS77 OP91 S S OP92 S S OP93 W S OP94 W S OP95 W S OP96 W S OP98 S S OP99 M C VTS/TS77 OP1 W C VTS/TS77 OP11 C C VTS/TS77 OP12 S C VTS/TS77 OP13 C S VTS/TS77 OP14 S S VTS/TS77 OP15 S S VTS/TS77 OP16 S C VTS/TS77 OP17 S S VTS/TS77 OP18 W S VTS/TS77 OP19 W S VTS/TS77 OP11 S S VTS/TS77 Scratch mount performance is degraded. A service call is required. Database performance is degraded. Problem detected with Token Ring connection. Call service. Logging is now disabled on LM-x. Call service. Target Storage Pool xx is out of stacked volumes for VTS y. The number of xxxxxxxx constructs has reached the maximum number allowed (yyy). The number of xxxxxxxx constructs has exceeded yyy. The maximum number allowed is zzz. The yyyyy internal LAN switch (HUB) has failed or is not configured correctly. Call service. A database error has occurred. View help panel for SQL error code xxxx. Call service. NVRAM read failure on LM-A. Call service. NVRAM write failure on LM-A. Call service. NVRAM read failure on LM-B. Call service. NVRAM write failure on LM-B. Call service. The yyyyy internal LAN switch (HUB) is not configured correctly. Call service. Volser XXXXXX was ejected during recovery processing. A read-only status physical volume xxxxxx has been ejected. * This cluster is out of empty physical volumes. A physical volume has a label error. Internal: xxxxxx, External: yyyyyy A permanent, nonrecoverable tape volume vache error has occurred. (VTS z) An orphaned virtual volume (xxxxxx) has been found. Call service. A VTS has a CHECK-1 (xxxx) failure. (VTS z). Virtual volume xxxxxx was only partially read. Virtual volume xxxxxx was not fully recovered from damaged physical volume yyyyyy. The Tape Volume Cache is degraded (xxxx). (VTS z) Database restore from volume xxxxxx failed, attempting restore from next most recent. (VTS z) Insert of virtual volume xxxxxx failed during disaster recovery. (VTS z) Copyright 28, 215 IBM Corporation Page 11 of 29

12 Apr 13, 215 OP111 S S VTS/TS77 OP112 W S VTS/TS77 OP113 C S VTS/TS77 OP114 S C VTS/TS77 OP115 S S VTS/TS77 OP116 S S VTS/TS77 OP117 W S VTS/TS77 OP118 S C VTS/TS77 OP119 OP12 S C OP121 S C OP122 S C OP123 W C OP124 S C OP125 W S OP126 W C OP127 C S OP128 C S OP13 W C OP131 I C OP132 W C OP134 M C OP135 W OP136 W S OP138 C C OP139 C C S VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 Damaged volume xxxxxx ejected during disaster recovery. Could not be read on 2 drives. (VTS z) Device serial number nnnnn has been made offline and/or unavailable by the TS77 Engine with a reason code of mmmm. A VTS does not have enough available physical drives (359x) to continue operation. (VTS z) The grid partition attempted unsuccessfully to eject a stacked volume (xxxxxx) during disaster recovery. (VTS z) The cluster attempted unsuccessfully to eject a damaged physical volume xxxxxx. VTS physical device xxx is cabled incorrectly. It has been made unavailable. (VTS z) The TS77 cannot communicate with device xxx. It has been made unavailable. (VTS z) Mount of virtual volume xxxxxx failed because physical volume yyyyyy is not in the library. (rc=rrrr) (VTS z) Database restore from volume <xxxxxx> failed. Attempting to restore from next most recent event Mount of virtual volume xxxxxx failed because physical volume yyyyyy is misplaced. (reason code= nnn) Mount of virtual volume xxxxxx failed because physical volume yyyyyy is inaccessible. Mount of virtual volume xxxxxx located on physical volume yyyyyy failed. (reason code=mmm) Physical volume xxxxxx is in read-only status due to successive media errors. Physical volume xxxxxx is unavailable The TS77 Virtualization Engine controller is degraded. Error code yyyyy. Call service. (VTS z) The TS77 Virtualization Engine requested that device xxx be made unavailable but a mount/demount is in progress. (VTS z) An invalid mixture of physical drive types was detected. * The TS77 Engine does not have enough physical drives to continue operation. Physical volume xxxxxx failed scratch mount. Its label cannot be read and the tape must be re-initialized. Stacked volume xxxxxx ejected due to incompatible media type. (VTS z) Stacked volume xxxxxx could not be ejected because the convenience I/O station is full, or the door is open. Physical volume xxxxxx is write-protected. The TS77 unsuccessfully attempted to eject write-protected physical volume xxxxxx. Physical volume xxxxxx was moved to category FF8 due to unrecovered active data. The common scratch pool (Pool ) is out of mmmm media physical volumes. Storage pool nn is out of scratch physical volumes. Copyright 28, 215 IBM Corporation Page 12 of 29

13 Apr 13, 215 VTS/TS77 VOLSER xxxxxx could not be moved from Storage Pool nn to OP14 W Storage Pool mm. Error code = yyyy. VTS/TS77 OP141 I S VTS x was unable to obtain construct information for volser xxxxxx. VTS/TS77 Stacked volume xxxxxx exists in the VTS database but doesn t exist OP142 S S in the database. VTS/TS77 VTS x has completed processing the stacked volumes as part of the OP143 M Disaster Recovery inventory. VTS/TS77 Eject failed on physical volume xxxxxx that contains active data. OP144 W S Error code = nnnn. VTS/TS77 OP145 W S Unable to make stacked volume xxxxxx read-only. VTS/TS77 OP146 W S Unable to make stacked volume xxxxxx read-write. VTS/TS77 OP147 W S Stacked volume xxxxxx is in an invalid state. VTS/TS77 There are stacked volumes in the VTS database that can t be found OP148 S C in the library. OP149 C C TS77 Storage Pool nn is out of write compatible physical scratch volumes The physical volume xxxxxx has become degraded. This condition OP15 I C TS77 is the result of a media condition report. VTS/TS77 The time on the TS77 could not be adjusted. Contact your IBM OP151 W S service representative. VTS/TS77 Active data on ejected physical volume xxxxxx need to be OP152 S C recovered. VTS/TS77 OP153 S C Physical volume xxxxxx is misplaced. VTS/TS77 Pool nn has stacked volumes of wrong (opposite) media class. (VTS OP154 I C z) Device nnnn is configured incorrectly E5 must be set to OP155 I S TS77 emulate a 3592-J1A. VTS/TS77 Above threshold for uncopied data in cache, throttling possible (VTS OP16 S C z) VTS/TS77 OP161 M C Below threshold for uncopied data in cache (VTS z) The TS77 Engine has initiated auto removal of volumes has begun OP164 M TS77 on this disk-only cluster. OP165 M C TS77 One or more non-writable physical volumes were found. Copy export did not export physical volume xxxxxx because of an OP166 M C TS77 incorrect format. Unsupported media (for example: JA, JJ) is set for First Media OP167 M C TS77 and /or Second Media for Physical Volume Pools(s): xx. One or more unsupported empty media has been found and cannot OP168 I C Media OP169 C C OP17 W C VTS/TS77 VTS/TS77 OP171 W C Media be used by the installed tape drives. The 'xx' is out of cache space. The total used, 'yy' TiB, is less than 1 TiB from the total cache space or less than 5% below the total cache space, 'zz' TiB. The 'xx' has limited cache free space. The total used, 'yy' TiB, is less than 3 TiB from the total cache space or less than 15% of the total cache space, 'zz' TiB. Unsupported scratch media of type 'xxxx' were inserted into the library. Copyright 28, 215 IBM Corporation Page 13 of 29

14 Apr 13, 215 OP172 I VTS/TS77 OP173 I VTS/TS77 OP2 W C,S OP21 I c,r OP22 W C,S OP23 I c,r OP24 W C,S OP25 I c,r OP26 I C OP27 I c OP3 I S OP31 S S OP32 W C OP33 S C OP34 S S OP35 W C OP36 W C OP37 OP38 OP39 I C C VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 OP31 I TS77 OP311 I TS77 OP312 I TS77 OP313 I TS77 Automatic removal of logical volumes on this cluster has been disabled due to a small cache resident only partition size. Automatic removal of logical volumes on this cluster has been enabled by having a sufficient cache resident only partition size. The local cluster is operating in immediate copy mode and at least one copy did not finish prior to the completion of the Rewind/Unload command. All immediate deferred copy operations are complete. One or more volumes opened as part of a synchronous mode copy operation did not synchronize completely across both clusters. Synchronization across both clusters has completed for all volumes that were in the synchronous deferred state. Copy operations for the local cluster are disabled by the system. The system has enabled copy operations at the local cluster. Copy operations for the local cluster are disabled by the host. Copy operations for the local cluster are enabled by the host. One or more virtual volumes have corrupted tokens. Call service. Previous Peer-to-Peer Virtual Volume Restore did not complete. Call service. (VTS z) Volser xxxxxx is damaged. (VTS z) Volser xxxxxx is in the manual eject category. (VTS z) VTS ADSM port xx has failed. Call service. (VTS z) More than nn errors encountered for stacked volume XXXXXX. (VTS z) Pool nn has stacked volumes of different media class and was reset to default values. (VTS z) VTS attempted High Capacity Cache Option with xxxxx volumes but yyyyy volumes already exist. (VTS z) Virtualization Engine (VE) has been taught/configured incorrectly as a cluster. Cluster has been taught/configured incorrectly as a Virtualization Engine (VE) The data class nnnn was automatically created with the default actions for volume virtual volume xxxxxx The Storage Class nnnn was automatically created with the default actions for volume xxxxxx. The Management Class nnnn was automatically created with the default actions for volume xxxxxx. The Storage Group nnnn was automatically created with the default actions for volume xxxxxx. OP314 I TS77 The inhibit create command was ignored and one or more constructs were automatically created with the default actions for volume xxxxxx as a result of an imbalance of defined SMS constructs across Copyright 28, 215 IBM Corporation Page 14 of 29

15 Apr 13, 215 the Domain The maximum number of defined constructs has been reached. An OP315 I TS77 imbalance of defined SMS constructs across the domain has occurred. Default constructs were assigned for volume xxxxxx. The TS77 Engine has detected corrupted tokens for one or more OP316 C S TS77 virtual volumes. OP4 W C Media * The library is out of ETC cleaner cartridges. * xxxxx cleaner cartridge (yyyyyy) was ejected due to maximum OP41 M C Media use. xx percent of mounts performed by accessor y over the past hour OP42 W S required excessive mount recovery. Call service. xx percent of mounts performed by accessor y over the past 24 hours OP43 W S required excessive mount recovery. Call service. Device zzz required excessive mount recovery (xx percent of OP44 W S mounts) over the past hour (accessor y). Call service. Device zzz required excessive mount recovery (xx percent of OP45 W S mounts) over the past 24 hours (accessor y). Call service. OP46 W Logging is degraded on LM-x. Call service. Communication with the MasterConsole has failed (LM rc = xx, OP47 W MasterConsole rc = yy). Call service. LM-x: MasterConsole configuration has failed (rc = yy). Call OP48 W service. OP49 M TS77 The volume hold function was disabled for fast-ready category xxxx The hold/expire time has been changed to nnn hours for fast-ready OP41 M TS77 category xxxx OP411 M TS77 A fast-ready attribute was deleted for category xxxx. Volser (xxxxxx) has been returned to the station. A service cartridge OP412 W Media cannot be inserted via CIO or HCIO. Possible hard drive failure detected. View help panel for error code OP413 W = yy. Error threshold exceeded for accessor x. View help panel for error OP414 I S code = yy. VTS/TS77 During an insert/inventory the media type of volser xxxxxx did not OP415 S C match its destination pool. Volser is not assigned to a VTS. OP416 W Preferred EASH in frame xx is not responding. Call service. OP417 W Non-preferred EASH in frame xx is not responding. Call service. OP418 W Port xx on the preferred EASH in frame yy has failed. Call service. Port xx on the non-preferred EASH in frame yy has failed. Call OP419 W service. Serial Number xxxxxxx from CU/VTS on port yy does not OP42 W match the number entered during Configuration. First Storage Element xxxx from CU/VTS on port yy does OP421 W not match the element entered during Configuration. Device xxx with World Wide Node Name yy..yy is cabled OP422 W incorrectly. It is in the wrong lvirtual or physical library. A volser (xxxxxx) with an unsupported media type has been left in OP423 W C Media the convenience input station. An unreadable volser was left in the convenience I/O station, OP424 I C Media element address xxxx. Two devices (xxx, yyy) have the same serial number (zzzzzzz). Both OP425 W S Tape Drive have been uninstalled. Call service. Copyright 28, 215 IBM Corporation Page 15 of 29

16 Apr 13, 215 OP426 W S Tape Drive Two devices (xxx, yyy) have the same element addr (zzzz). Both have been uninstalled. Call service. OP427 W S The 3584 library reported that calibration is required. OP428 S S The 3584 reported a hardware error (nnnn). Contact your IBM service representative. OP43 W The Primary Link has encountered multiple failures. Call service. OP431 Reserved OP432 Reserved OP433 M The Send Interventions to Host Console settings on the Events panel /T has been turned on. S77 OP434 M /T S77 The Send Interventions to Host Console setting on the Events panel has been turned off. OP435 W S Tape Drive Two devices (xxx;yyy) have the same serial number (zzzzzzz). Second has been uninstalled. Call service. OP436 W S Tape Drive Two devices (xxx;yyy) have the same element address (zzzz). Second has been uninstalled. Call service. OP437 S S Tape Drive Cartridge xxxxxx has been left in uninstalled device yyy. Call service. OP438 W S Tape Drive Device yyy is reporting an element address of zero. Call service. OP439 W,S The virtual tape library has lost communication with the primary C TS77 See note 2 Encryption Key Server. OP44 W,S The virtual tape library has lost communication with the alternate C TS77 See note 2 Encryption Key Server. OP441 M S Possible degradation due to 3584 TapeAlert error (nnnn). Service call Home has been generated. OP442 W C Media Physical volume xxxxxx is inaccessible. VTS/TS77 The virtual tape library has detected an inconsistency with the OP443 W S TS35. OP444 W Tape Drive LM PC has not been rebooted in 6 months. OP445 W C TS77 The primary Encryption Key Server was set to UNAVAILABLE OP446 W C TS77 The alternate Encryption Key Server was set to UNAVAILABLE OP448 M C Media More than nn errors were encountered for physical volume xxxxxx. VTS/TS77 OP449 M C Pool nn has physical volumes of the wrong media class. VTS/TS77 The media type of VOLSER xxxxxx does not match its volser range. OP45 M C The VOLSER was not assigned to a cluster. VTS/TS77 OP451 M C Encryption is enabled. No Encryption Key Server are configured. VTS/TS77 Device nnn could not encrypt data in storage pool nn (Encryption OP452 W C Key Server error mmm). VTS/TS77 Device nnnn could not append encrypted data to cartridge xxxxxx OP453 W C (Encryption Key Server error mmm). VTS/TS77 Device nnnn could not decrypt data from cartridge xxxxxx OP454 W C (Encryption Key Server error mmm). Device nnnnn is not in 3592 E5 Native mode. The Device was OP455 W S Tape Drive made unavailable.. VTS/TS77 Encryption is enabled on the virtual tape library. Device nnnnn is not OP456 W C enabled for system-managed encryption. OP457 W S Tape Drive Device nnnnn is not in 3592 J1A emulation mode. The device was Copyright 28, 215 IBM Corporation Page 16 of 29

17 Apr 13, 215 made unavailable OP458 S S TS77 An internal hardware/software error has occurred. OP459 S S TS77 A disk cache error has occurred. OP46 W S TS77 A Grid link error xxxxxx has occurred. OP461 I S Tape Drive A tape drive error: xxxxxx has occurred. OP462 I S TS77 A fibre switch error xxxxxx has occurred. OP463 W S VTS/TS77 A TSSC error has occurred. The TSSC is unable to call home. OP464 I S A library error has occurred OP465 I S VTS/TS77 An Autonomic Ownership Takeover Mode communications error occurred. The device is unable to communicate with the remote cluster. OP466 I C VTS/TS77 An Encryption Key server error xxxxxx error has occurred OP467 I S Media Tape cartridge xxxxxx is stuck in a storage cell. OP468 W The 3494 has an Event. OP469 W The 3494 is in a degraded state. OP47 M TS77 Delete Expire capability has been disabled. OP471 I C TS77 The Field Microcode Replacement tape xxxxxx cannot be used as a data cartridge. OP472 M TS77 The database backup to physical volume xxxxxx failed during the Copy Export operation as a result of a media error. OP473 M TS77 A media error occurred during the Copy Export operation and the physical volume xxxxxx has been ejected. The medium may be degraded, and should not be reused in an export pool. OP474 M TS77 OP475 M TS77 The Copy Export operation did not export physical volume xxxxxx because the primary copy for virtual volume xxxxxx is currently unavailable. Copy Export did not export virtual volume xxxxxx because it was not able to premigrate the volume to the export pool. OP476 M TS77 The event was cleared automatically. OP48 M S TS77 Service Call Home will be initiated. OP481 M S TS77 Service Call Home was initiated. OP482 M S TS77 Service Call Home was initiated with PMR number xxxxx,yyy,zzz. OP483 C S TS77 A permanent cache problem was encountered. OP484 C S TS77 A permanent cache problem was encountered. OP485 C S TS77 A 3956-CC6 permanent check was encountered. OP486 C S TS77 A CHECK1 condition was encountered. OP487 C S TS77 An adapter microcode CHECK1 condition occurred. OP488 C C TS77 A channel event occurred. OP489 C S TS77 An undetermined error occurred. OP49 C C TS77 An operator notification occurred. OP491 C S TS77 A microcode exception occurred in the ATL daemon. OP492 C S TS77 An undetermined error occurred. OP493 C TS77 An informational message was presented by CU. OP494 C C TS77 An environmental problem has occurred. OP495 C S TS77 A microcode exception occurred in the tape daemon. OP496 C S TS77 The tape daemon detected a CRC error. OP497 C S TS77 A microcode exception occurred in the tape daemon. OP498 C S TS77 A microcode exception occurred in the BATE daemon. Copyright 28, 215 IBM Corporation Page 17 of 29

18 Apr 13, 215 OP499 C S TS77 An error was detected and a Call Home has been generated OP5 M TS77 The times displayed by the local and remote clusters nnnn differ by more than 5 seconds. OP51 M TS77 nnnn logged into the Web interface. OP511 M TS77 nnnn logged out of the Web interface. OP512 M TS77 User mmmm the setting to send future events to host. OP514 M TS77 Custom Role mmmm has been changed. OP515 M TS77 SNMP settings have changed. Values are: SNMP Version: nn Enable SNMP Traps: mmmm Trap Community Name: xxxx OP516 M TS77 Stand-alone mount was initiated for volume xxxxxx on device zzz. OP517 M TS77 Stand-alone demount was initiated on device zzz. OP518 M TS77 Node nnnn has been shut down. OP519 M TS77 Custom Role mmmm has been created. OP52 M TS77 Custom Role mmmm has been deleted. OP521 M TS77 The security settings for local authentication have changed. Local Account Expiration: mmmm. The account will expire if the password is not changed in n days. OP522 M TS77 The security settings for local authentication have changed. Local Account Expiration: mmmm. OP523 M TS77 The security settings for local authentication have changed. Local Account Lock: mmmm. The account will be locked after n unsuccessful attempts to enter the password. OP524 M TS77 The security settings for local authentication have changed. Local Account Lock: mmmm. OP525 C S TS77 A TAPE DRIVE FAILURE has occurred OP526 C S TS77 A FibrePath, FibreSwitch, or FibreInterface error has occurred. OP527 M TS77 Stand-alone mount for volume xxxxxx on device zzz completed successfully. OP528 M TS77 Stand-alone demount for volume xxxxxx on device zzz completed successfully. OP529 W TS77 Stand-alone mount for volume xxxxxx on device zzz failed with error code nnnn. OP53 W TS77 Stand-alone demount for volume xxxxxx on device zzz failed with error code nnnn. OP531 W C, S TS77 The network connection on grid port xx with IP address: n.m.y.z experienced a possible loss of connectivity. OP532 C C, S TS77 The network connection on grid port xx with IP address: n.m.y.z is not responding. OP533 M C, S TS77 The connection of local cluster to remote cluster nnnn with remote port xx and IP address: n.m.y.z of the remote cluster was unavailable for a brief time. OP534 W C, S TS77 The connection of local cluster to remote cluster nnnn with remote port xx and IP address: n.m.y.z of the remote cluster is losing packages, or the connection was unavailable. OP535 C C, S TS77 The connection of local cluster to remote cluster nnnn with remote port xx and IP address: n.m.y.z of the remote cluster, was not available. OP536 C S TS77 The link to remote cluster: nnnn with IP address: n.m.y.z is in the offline state. OP537 M C, S TS77 The connection of local cluster to remote cluster nnnn with remote port xx and remote IP address: n.m.y.z was unavailable for a brief time or because the local cluster was unable to retrieve the status of Copyright 28, 215 IBM Corporation Page 18 of 29

19 Apr 13, 215 the remote adapter. OP538 W C, S TS77 The connection of local cluster to remote cluster nnnn with remote port xx and remote IP address: n.m.y.z was not available, because the local cluster reports the status of the remote adapter as not available. OP539 C S TS77 The connection of local cluster to remote cluster nnnn with remote port xx and IP address: n.m.y.z of the remote cluster was not available, because the state of the remote adapter appears as Failed. OP54 C C, S TS77 The link to remote cluster: nnnn With IP address: n.m.y.z is in the offline state. NTC (Network Traffic Controller) reports link state: mmmm OP541 W C, S TS77 Degraded state to gateway IP: gateway IP address. OP542 C C, S TS77 Failed state to gateway IP:gateway IP address. OP543 W C, S TS77 The primary and alternate grid adapters have different speeds: Primary nnnn link speed is: xxx Alternate mmmm link speed is: yyy OP544 C S TS77 The primary grid Ethernet adapter nnnn is down. OP545 C S TS77 The alternate grid Ethernet adapter nnnn is down. OP546 M S TS77 Could not retrieve the date on cluster nnnn. OP547 C C, S TS77 A time synchronization failure was detected between cluster nnnn and Cluster mmmm. OP548 W S TS77 There is no communication with one or more clusters in the Grid. OP549 W TS77 One or more clusters in the Grid are in Service status. OP55 C C TS77 Service Call Home, TSSC was unable to generate a PMR number OP551 C S TS77 A permanent cache problem was encountered. OP552 C S TS77 A temporary cache problem was encountered. OP553 C S TS77 The cache has an unreadable sector. OP554 C S TS77 A cache power supply has failed. OP555 C S TS77 A cache power or fan assembly has failed. OP556 C S TS77 The cache has lost redundancy. OP557 C S TS77 A problem exists with the cabling or drive path inside the cache enclosure. OP558 C S TS77 A cache component has failed or been removed. OP559 C S TS77 A cache controller has failed or been removed. OP56 C S TS77 An environmental service module (ESM) canister in the cache has failed or been removed. OP561 C S TS77 A cache drive is missing. OP562 C S TS77 A cache drive is in a degraded state. OP563 C S TS77 A cache disk has reported errors. OP564 C S TS77 A cache RAID array has failed drives. OP565 C S TS77 An unsupported number of drive enclosures exists on a cache loop. OP566 C S TS77 The reported data rate of a cache drive channel is outside the expected range. OP567 C S TS77 The data rate could not be obtained on a drive channel for the cache. OP568 C S TS77 An incorrect number of enclosures exists on a cache loop. OP569 C S TS77 The number of enclosures on a cache loop cannot be determined. OP57 C S TS77 Mismatched drives exist in a cache array. OP571 C S TS77 Disk operation in the cache is degraded. OP572 C S TS77 Network errors were detected while connecting to the cache. OP573 C S TS77 An unreadable sector exists in the cache. OP574 C S TS77 A parity error occurred in the cache. OP575 C S TS77 A cache media error occurred. OP576 C r TS77 A temporary cache problem was encountered. Copyright 28, 215 IBM Corporation Page 19 of 29

20 Apr 13, 215 OP577 C S TS77 The cache has an unreadable sector. OP578 C S TS77 A cache power supply has failed. OP579 C S TS77 A cache power or fan assembly has failed. OP58 C S TS77 The cache has lost redundancy. OP581 C S TS77 A problem exists with the cabling or drive path inside the cache enclosure. OP582 C S TS77 A cache component has failed or been removed. OP583 C S TS77 A cache controller has failed or been removed. OP584 C S TS77 An environmental service module (ESM) canister in the cache has failed or been removed. OP585 C S TS77 A cache drive is missing. OP586 C S TS77 A cache drive is in a degraded state. OP587 C S TS77 A cache disk has reported errors. OP588 C S TS77 A cache RAID array has failed drives. OP589 C S TS77 An unsupported number of drive enclosures exists on a cache loop. OP59 C S TS77 The reported data rate of a cache drive channel is outside the expected range. OP591 C S TS77 The data rate could not be obtained on a drive channel for the cache. OP592 C S TS77 An incorrect number of enclosures exists on a cache loop. OP593 C S TS77 The number of enclosures on a cache loop cannot be determined. OP594 C S TS77 Mismatched drives exist in a cache array. OP595 C S TS77 Disk operation in the cache is degraded. OP596 C S TS77 Network errors were detected while connecting to the cache. OP597 C S TS77 An unreadable sector exists in the cache. OP598 C S TS77 A parity error occurred in the cache. OP599 C S TS77 A cache media error occurred. OP6 W,S Control S See note 2 Unit A temporary cache problem was encountered. OP61 C S TS77 The cache has an unreadable sector. OP62 C S TS77 A cache power supply has failed. OP63 C S TS77 A cache power or fan assembly has failed. OP64 C S TS77 The cache has lost redundancy. OP65 C S TS77 A problem exists with the cabling or drive path inside the cache enclosure. OP66 C S TS77 A cache component has failed or been removed. OP67 C S TS77 A cache controller has failed or been removed. OP68 C S TS77 An environmental service module (ESM) canister in the cache has failed or been removed. OP69 C S TS77 A cache drive is missing. OP61 C S TS77 A cache drive is in a degraded state. OP611 C S TS77 A cache disk has reported errors. OP612 C S TS77 A cache RAID array has failed drives. OP613 C S TS77 An unsupported number of drive enclosures exists on a cache loop. OP614 C S TS77 The reported data rate of a cache drive channel is outside the expected range. OP615 C S TS77 The data rate could not be obtained on a drive channel for the cache. OP616 C S TS77 An incorrect number of enclosures exists on a cache loop. OP617 C S TS77 The number of enclosures on a cache loop cannot be determined. OP618 C S TS77 Mismatched drives exist in a cache array. OP619 C S TS77 Disk operation in the cache is degraded. OP62 C S TS77 Network errors were detected while connecting to the cache. OP621 C S TS77 An unreadable sector exists in the cache. Copyright 28, 215 IBM Corporation Page 2 of 29

21 Apr 13, 215 OP622 C S TS77 A parity error occurred in the cache. OP623 C S TS77 A cache media error occurred. OP624 C S TS77 An error was detected in the disk cache. OP625 C S TS77 A system reboot interrupted a call home. OP626 C S TS77 One or more issues on the system have persisted for longer than 24 hours. OP627 C S TS77 There is a problem with network communication required for autonomic ownership takeover. OP628 C S TS77 The cache controller is not configured. OP629 C S TS77 The cache file system is inefficiently allocating its available space. OP63 C S TS77 There is a problem with the network fail over code. OP631 C S TS77 The error detection feature has restarted five times in 24 hours. OP632 C S TS77 The available memory is not configured correctly. OP633 C S TS77 A CPU has failed. OP634 C S TS77 Port on the customer network has failed. OP635 C S TS77 Port 1 on the customer network has failed. OP636 C S TS77 Both Ethernet routers have failed. OP637 C S TS77 The primary Ethernet router has failed. OP638 C S TS77 The alternate Ethernet router has failed. OP639 C S TS77 The Network Time Protocol (NTP) server is not responding. OP64 C S TS77 A port in an Ethernet router has failed. OP641 C S TS77 A port in an Ethernet router shows increasing errors. OP642 C S TS77 Communication between the disk cache and the primary switch has failed. OP643 C S TS77 Communication between the disk cache and the alternate switch has failed. OP644 C TS77 One or more arrays are not encrypted. OP645 C TS77 This is a cache Call Home test. OP646 W C TS77 OP647 C C,S OP648 I C,S OP649 C S OP65 W S OP651 I S OP652 I S OP653 I S OP654 C S OP655 W S OP656 C S OP657 W S VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 VTS/TS77 Encryption is enabled on the virtual tape library. Device xxxxxxx is not encryption-capable. The device was made unavailable. Host adapter 'xx' is offline. The link 'xx' to host adapter 'yy' is unavailable. No IBM media changer devices were found on the system. The system identified 'xxxx' IBM media changer devices. This is an incorrect number of devices. The IBM media changer 'xxxx' is in an unknown state. The fibre channel adapter for tape interface 'xx' cannot be identified. The drive name 'xx' does not match port 'yy'. Drives could not be configured on a 359 or 3592 tape drive. The physical tape SCSI device 'xxxx' is in the state: 'yyyy'. Primary and alternate paths for tape SCSI device 'xxxx' are unavailable. The tape drive device 'xxxx' is shown as 'yyyy' in the cluster. Copyright 28, 215 IBM Corporation Page 21 of 29