APAR status
Closed as canceled.
Error description
For 5695DF180 with D/T3495 and D/T3494 TCDB Volume Error Status Field & Software Error Category - When a hardware or software error is detected, the volume error status field in the TCDB is updated to reflect the error, and the volume may also be placed in the software error category in the library manager database. - More specifically, when a software error is detected for a scratch volume, this results in the volume being placed in the software error category in the library manager database (refer to the software volume category table in the OAM PISA for tape libraries). The setting of an error category prevents the volume from being selected for future non-specific (scratch) mount requests. In addition, the error status field in the TCDB volume record is updated to reflect the software error condition. - When a software error is detected for a private volume, this will result in an update to the volume record in the TCDB with the appropriate error status; however, since private volumes are requested by volser and not by a category value, there is no need to place private volumes in the software error category. - When a hardware error is detected (for either scratch or private volumes), the error is tracked in the library manager database and in the TCDB. Since the library manager tracks hardware related errors for volumes, there is no need to place the volume in the software error category. - There are several ways to reset the volume error status field in the TCDB and, if applicable, move the volume out of the software error category: - 1> General use programming interface CBRXLCS FUNC(CUA) can be used to change the volume's use attribute from SCRATCH to PRIVATE, PRIVATE to SCRATCH, PRIVATE to PRIVATE or SCRATCH to SCRATCH (refer to the OAM PISA for tape libraries on how to use this interface). If the only purpose of the CBRXLCS invocation is to reset the volume error status field, CBRXLCS FUNC(CUA) from SCRATCH to SCRATCH or PRIVATE to PRIVATE will accomplish this (it is not necessary to actually change the volume's use attribute). Invoking CBRXLCS FUNC(CUA) will also move a volume out of the software error category. - 2> The ISMF volume ALTER line operator or command can be used to update specific fields in the TCDB volume record, including the volume error status field. If no other changes to the volume are required, invoke ISMF ALTER to change the volume's use attribute from PRIVATE to PRIVATE or SCRATCH to SCRATCH. Changing the volume's use attribute from SCRATCH to PRIVATE, or PRIVATE to SCRATCH using ISMF ALTER will also reset the volume's error status field. Invoking ISMF ALTER against a volume record will also move a volume out of the software error category. - 3> If a volume is ejected from the library where it resides and reentered into the same library, or a different library, the volume error status field and software error category will be reset upon entry. - 4> A successful audit of a volume will reset a hardware error in the TCDB (such as misplaced volume), but it will not clear a software error in the TCDB. Since hardware errors do not result in the volume's category being changed, audit never alters the setting of a volume in the error category. If a scratch volume has a software error associated with it, a successful audit of the volume will leave the volume condition set in the TCDB and will leave the volume in the error category. - When using the DISPLAY SMS,LIBRARY command, the scratch volume counts displayed reflect the number of scratch volumes in the scratch media category(s). If a scratch volume is in the software error category, it is not included in this count because it is not considered a useable scratch cartridge. - Also keep in mind that resetting a hardware error condition in the volume's TCDB volume record will not clear the condition in the library manager database. Symptoms: MSGIEC147I 613-1C, MSGIEE763I CBRLLACS CODE=140169, MSGCBR4000I LLACS mount perminent error, MSGCBR4105i No media2 available.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
Additional information for compid 5695DF180 with D/T3494 or D/T3495.
APAR Information
APAR number
II08521
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
1995-02-27
Closed date
1995-03-03
Last modified date
1995-08-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
08 August 1995