A fix is available
APAR status
Closed as program error.
Error description
When using the actual archive logs for disaster recovery, and When copying from tape to DASD during DR, the ssidYCPL step generates this message because of missing VOLSER information - IKJ56228I DATA SET xxx.yyy.zzz.A000ijk NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED. xxx@YCPL - Error allocating Tape Archive Log Dataset This occurs because the archive logs are deleted from the catalog in the ssidDELA step, but the ssidCPYL step does not preserve the tape volume in this case. The fix will only affect NEW archive logs created since the last time the DR local site collection job has been run. Any archive logs created before the user last ran the collection will still reveive the error whent the job runs at the DR site to copy them to DASD. So if the user needs any archive logs that were created before the last archive collection job at the DR site to be copied to DASD they will have to delete all rows from the table DR_ARCHIVE_LOGS00 before running the collection again.
Local fix
Possible workarounds for this issue: 1. Set "Copy Archive Logs to DASD" to 0 days and 0 hours. This will elongate the recovery time at the DR site, but will bypass the step of copying archive logs from tape to dasd (thus avoiding the error). 2. Create a copy of the archive logs on tape for DR purposes by setting "Archive Logs used at DR" to "C" for copied.
Problem summary
**************************************************************** * USERS AFFECTED: DB2 Recovery Expert for Z/OS. * **************************************************************** * PROBLEM DESCRIPTION: When using the actual archive logs for * * disaster recovery, and when copying * * from tape to DASD during DR, the * * ssidYCPL step generates this message * * because of missing VOLSER information - * * IKJ56228I DATA SET xxx.yyy.zzz.A000ijk * * NOT IN CATALOG OR CATALOG CAN NOT BE * * ACCESSED. xxx@YCPL - Error allocating * * Tape Archive Log Dataset. This occurs * * because the archive logs are deleted * * from the catalog in the ssidDELA step, * * but the ssidCPYL step does not preserve * * the tape volume in this case. The fix * * will only affect NEW archive logs * * created since the last time the DR * * local site collection job has been run. * * Any archive logs created before the * * user last ran the collection will * * still receive the error when the job * * runs at the DR site to copy them * * to DASD. So if the user needs any * * archive logs that were created before * * the last archive collection job at the * * DR site to be copied to DASD they will * * have to delete all rows from the table * * DR_ARCHIVE_LOGS00 before running the * * collection again. * **************************************************************** * RECOMMENDATION: APPLY the PTF. * **************************************************************** Code has been changed to correct this condition.
Problem conclusion
APPLY the PTF.
Temporary fix
Comments
APAR Information
APAR number
PK66371
Reported component name
DB2 REC EXPERT
Reported component ID
5697H7400
Reported release
210
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-05-20
Closed date
2008-08-12
Last modified date
2008-09-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
ARY@BACK
Fix information
Fixed component name
DB2 REC EXPERT
Fixed component ID
5697H7400
Applicable component levels
R210 PSY UK38894
UP08/08/16 P F808
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVQTW","label":"Db2 Recovery Expert"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.1.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 September 2008