A fix is available
APAR status
Closed as program error.
Error description
Recover utility on partition level fails with MSGDSNU556I on SYSCOPY entry with ICTYPE='M', STYPE='R'. Sample: RECOVER TABLESPACE DBTEST.TSTEST DSNUM 2 TOLOGPOINT ... abend: DSNU556I DSNUCASA - RECOVER CANNOT PROCEED FOR TABLESPACE DBTEST.TSTEST DSNUM 2 BECAUSE A SYSIBM.SYSCOPY RECORD HAS BEEN ENCOUNTERED WHICH HAS DBNAME=DBTEST TSNAME=TSTEST DSNUM=2 ICTYPE=M STYPE=R
Local fix
n.a.
Problem summary
**************************************************************** * USERS AFFECTED: * * All Db2 11 for z/OS and Db2 12 for z/OS * * MODIFY RECOVERY utility users. * **************************************************************** * PROBLEM DESCRIPTION: * * RECOVER utility with DSNUM fails with * * MSGDSNU556I because of a SYSCOPY * * record with ICTYPE=M STYPE=R that was * * inserted for MODIFY RECOVERY that has * * an incorrect START LRSN in a data * * sharing environment. * **************************************************************** * RECOMMENDATION: * * Apply corrective PTF when available * **************************************************************** RECOVER utility found a SYSCOPY record with ICTYPE=M STYPE=R with a START LRSN that is newer than the time of recovery. This ICTYPE=M STYPE=R TTYPE=N record was inserted for a MODIFY RECOVERY DSNUM x DELETE DATE(yyyymmdd), but the START LRSN is much newer than the DATE passed to MODIFY RECOVERY causing RECOVER to fail issuing DSNU556I and ending with RC8. A SYSCOPY record with ICTYPE=M STYPE=R TTYPE=N is inserted when MODIFY RECOVERY did not delete any record from SYSLGRNX. But, MODIFY RECOVERY incorrectly picked up a STOP LRSN value from a SYSLGRNX record and saved it as the START LRSN for the SYSCOPY record. This problem can also occur in a non-data sharing environment. Additional keywords: ZSA2
Problem conclusion
MODIFY RECOVERY code is corrected to only save the STOP LRSN of a deleted SYSLGRNX record.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PI98468
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-05-28
Closed date
2018-09-25
Last modified date
2018-11-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI58709 UI58710
Modules/Macros
DSNUMDEL DSNUBCOP
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"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":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 November 2018