A fix is available
APAR status
Closed as program error.
Error description
Customer is performing ARCHIVE with selection criteria. The ARCHIVE file (AF) is located on TAPE and the customer is using USE_EXISTING_SUBSET NO, or did not specify and made it default to NO. An ARCHIVE entry for the AF to be processed exists in the Optim directory however it is a mismatched one: it points to an AF which is different than the one being referenced. This may happen when the AF specified in the control statements has been created on a different DB2 subsystem and has not been imported into this current one. During the RESTORE, or SUBSET, processing in the above scenario the following ABEND S001 ABENDS001 may occur: IEC020I 001-1,RT74947E,RDB2PROC,PSDFEXTR,0DAE,Y35302, IEC020I GREGCZ.RT75874.AF1.D0180423 IEC020I NO ERROR HANDLING, (SYNAD), EXIT SPECIFIED IEF450I RT74947E RDB2PROC - ABEND=S001 U0000 REASON=00000001 CEE3250C The system or user abend S001 R=00000001 was issued. From compile unit IBDCB at entry point IBDCB at compile unit offset +00A6D61E at entry offset +00A6BD9E at address 20B2F72E. Traceback: DSA Entry E Offset Statement Load Mod 1 CEEHDSP +00004A4C CEEPLPKA 2 TrcEntry -1F69CE0E FOP4TRCE 3 IBDCB +00A6BD9E FOPIO 4 XFMIntGetXFTables +000001F0 12019 FOPZFMMN 5 xfmopen +000170AE 2952 FOPZFMMN 6 OpenInputFile +000005DC 2532 FOPMDXTR 7 DXArchiveSubset +000003E4 420 FOPMDXTR 8 CreateSubset+00000F68 3678 FOPMMUTL 9 RestoreStatement +000080CA 1751 FOPMMUTL 10 FOPMMUTL_dynamn +000025BE 797 FOPMMUTL 11 main +00004E62 1012 FOPMAIN
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Optim for z/OS users performing ARCHIVE * * RESTORE or SUBSET processing with data on * * TAPE. * **************************************************************** * PROBLEM DESCRIPTION: 1. Customer is performing ARCHIVE with * * selection criteria. The ARCHIVE file * * (AF) is located on TAPE and the * * customer is using * * USE_EXISTING_SUBSET NO * * or did not specify and made it default * * to NO. * * * * An ARCHIVE entry for the AF to be * * processed exists in the Optim directory * * however it is a mismatched one: it * * points to an AF which is different than * * the one being referenced. This may * * happen when the AF specified in the * * control statements has been created on * * a different DB2 subsystem and has not * * been imported into this current one. * * * * During the RESTORE, or SUBSET, * * processing in the above scenario * * the following ABEND S001 ABENDS001 may * * occur: * * * * IEC020I 001-1,RT74947E,RDB2PROC,PSDFEXT * * R,0DAE,Y35302, * * IEC020I GREGCZ.RT75874.AF1.D0180423 * * IEC020I NO ERROR HANDLING, (SYNAD), * * EXIT SPECIFIED * * IEF450I RT74947E RDB2PROC - ABEND=S001 * * U0000 REASON=00000001 * * * * CEE3250C The system or user abend S001 * * R=00000001 was issued. * * From compile unit IBDCB at * * entry point IBDCB at compile * * unit offset +00A6D61E at entry * * offset +00A6BD9E at * * address 20B2F72E. * * * * Traceback: * * DSA Entry E Offset Statement * * Load Mod * * 1 CEEHDSP +00004A4C * * CEEPLPKA * * 2 TrcEntry -1F69CE0E * * FOP4TRCE * * 3 IBDCB +00A6BD9E * * FOPIO * * 4 XFMIntGetXFTables * * +000001F0 12019 * * FOPZFMMN * * 5 xfmopen +000170AE 2952 * * FOPZFMMN * * 6 OpenInputFile * * +000005DC 2532 * * FOPMDXTR * * 7 DXArchiveSubset * * +000003E4 420 * * FOPMDXTR * * 8 CreateSubset+00000F68 3678 * * FOPMMUTL * * 9 RestoreStatement * * +000080CA 1751 * * FOPMMUTL * * 10 FOPMMUTL_dynamn * * +000025BE 797 * * FOPMMUTL * * 11 main +00004E62 1012 * * FOPMAIN * **************************************************************** 1. Optim processing logic is not detecting an Optim Directory entry mismatch for an ARCHIVE file on TAPE.
Problem conclusion
1. Optim processing logic will be corrected.
Temporary fix
Comments
APAR Information
APAR number
PH06190
Reported component name
OPTIM MOVE FOR
Reported component ID
5655V0700
Reported release
B70
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-12-06
Closed date
2018-12-20
Last modified date
2019-01-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
FOP00003 FOP00103 FOP00203 FOP00303 FOP00B FOP01B FOP05B FOP07B FOP08B FOP09B FOP0AB FOP0BB FOP0ITKA FOP1ODRV FOP1OSFN FOP3DTPR FOP4IPMN FOP4PEMN FOP4PMMN FOP4TRCE FOP9APIM FOP9GINF FOPCFPMN FOPCXLIB FOPD2V85 FOPD2V91 FOPD2VA5 FOPD2VNN FOPHSTM FOPIO FOPK03 FOPK05 FOPK10 FOPLUAH FOPMADDE FOPMAFCN FOPMAIN FOPMAMAI FOPMARCN FOPMCBMN FOPMCDRT FOPMCENU FOPMCMAI FOPMCMMN FOPMCOFN FOPMCOLA FOPMCOLP FOPMDBMN FOPMDDDL FOPMDMAI FOPMDPRC FOPMDXTR FOPMECMN FOPMEMAI FOPMIXMM FOPMMCMN FOPMMCMR FOPMMJBS FOPMMUNU FOPMMUTL FOPMSELM FOPMTMDB FOPMUXIM FOPODPP FOPOMN FOPRS10 FOPRS8 FOPRS9 FOPUMCBT FOPUUNLD FOPVOU FOPZFBMN FOPZFMMN FOPZMAIN FOPZSUB
Fix information
Fixed component name
OPTIM MOVE FOR
Fixed component ID
5655V0700
Applicable component levels
RB70 PSY UI60408
UP18/12/22 P F812
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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B70","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 January 2019