APAR status
Closed as program error.
Error description
IMS DRF V3R1 SUPPORT FOR IMS VERSION 10 INPUT DATA SETS Additional symptoms: Fixes problem reported in R210 APAR PK36640 and PK36327 KEYWORDS: IMSV10TGT/K
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IMS Database Recovery Facility * * Version 3 Release 1 which also use IMS * * Version 10 Release 1. * **************************************************************** * PROBLEM DESCRIPTION: DRF V3R1 does not support database * * recoveries which require log data * * created by IMS V10. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** Recovery of IMS databases which are updated by IMS V10 is not supported by DRF because the mapping for IMS V10 log records is not included in the base code.
Problem conclusion
This APAR and PTF provide the support for recovery of database data sets and fast path areas which have been updated by IMS V10. - FRXRRR, FRXRBUF0, FRXRLRA0, and FRXUORM0 are changed to use the IMS V10 log record mapping. - FRXEDRF, FRXEWSP, FRXRWSP, and FRXEDRF0 are changed to support a new DBRCGRP EXEC parameter for IMS V10 Parallel RECON Access. - FRXEDRF, FRXEGRM, FRXESYS, FRXEWSP, FRXRWAE, FRXRWCE, FRXRWSP, FRXVWSP, FRXEDRF0, FRXEPSS0, FRXVASD0, FRXVSTA0, and FRXVSTA1 are changed to support a new IMS V10 capability for large data set type. This adds a new DSNTYPE keyword which users may specify a BASIC or LARGE option. The value specified here is passed to HPIC during image copy generation. - FRXEDRF, FRXEGRM, FRXESYS, FRXEWSP, FRXRWAE, FRXRWCE, FRXRWSP, FRXVWSP, FRXEPSS0, FRXTSPR0, and FRXVASD0 are changed to support two new DFSPREC0 keywords introduced with IMS V10 (ILEF and BOTHF). - FRXAWEX, FRXRVRA, FRXIDYN0, FRXMSTR0, FRXYALL0, and FRXYUNA0 are changed to prevent the tape drive request logic (TAPECHK) from being invoked during image copy caching process (CACHE). Tape drive request is required only when the image copies are being opened for reading. During caching, the image copies only goes through deferred allocation and managed by VTS. They are not opened by DRF for reading during this process. They are also changed to remove code that coordinated the access of log and change accumulation data sets with the tape device requests from subordinate address spaces. This was meant to help prevent the subordinate address spaces from exceeding the number of available tape devices when they are in use by log and CA data sets. It was later determined that the image copy data set read process always occurs after all log and CA data sets are processed. The image copy caching process occurs in parallel to the log and CA read process, however, caching does not require to follow the tape device request logic. - FRXGRDS0, FRXIRTH0, and FRXPSDS0 are changed to report if Flash Copy data sets are used as input to recovery. - The following modules are recompiled using IMS V10 macros and to pick up enhancements mentioned above: FRXADF00, FRXADM10, FRXADM20, FRXCAMG0, FRXCARD0, FRXCBDM0, FRXDAQS0, FRXDDCD0, FRXDDCR0, FRXDEST0, FRXDRQI0, FRXDTIN0, FRXDTRM0, FRXEDSG0, FRXEGRM0, FRXEPCC0, FRXEPIC0, FRXEPQS0, FRXGAPI0, FRXGRDM0, FRXGRPT0, FRXGUOW0, FRXHBUF0, FRXICAI0, FRXICLI0, FRXICTL0, FRXIIOM0, FRXIOCN0, FRXIOSM0, FRXISMS0, FRXISMU0, FRXIVCN0, FRXIVSM0, FRXLACR0, FRXLACR1, FRXLACR2, FRXLBLD0, FRXLGET0, FRXLMRG0, FRXLNOT0, FRXLPD00, FRXLPST0, FRXLSCH0, FRXLSE15, FRXLSE35, FRXLSRT0, FRXLSRT1, FRXLSRT2, FRXLSTR0, FRXLSTS0, FRXMDBD0, FRXMINI0, FRXMINI1, FRXMSTP0, FRXMSTR1, FRXMTRM0, FRXMTRM1, FRXPDIR0, FRXPDIS0, FRXPDSR0, FRXPDSS0, FRXPSDR0, FRXQBIN0, FRXQBUF0, FRXRABD0, FRXRCHK0, FRXRCTL0, FRXRDTH0, FRXREOD0, FRXRLSR0, FRXSDR00, FRXSDR10, FRXSINI0, FRXSINI1, FRXSTRM0, FRXSTRM1, FRXTAPI0, FRXTAS00, FRXTAU00, FRXTPIB0, FRXTPPR0, FRXTSIB0, FRXTSPR0, FRXUAPI0, FRXVADD0, FRXVAUT0, FRXVCLN0, FRXVCMD0, FRXVDIS0, FRXVRCV0, FRXVREM0, FRXVSTA2, FRXVSTO0, FRXVVER0, FRXWRTN0, FRXWSPL0, FRXWSPM0, FRXYADY0, FRXYUDY0 ----------------------------------------------------------- ----------------------------------------------------------- The following DOC changes are required in SC18-9407-00: IBM IMS Database Recovery Facility for z/OS User's Guide and Reference Version 3 Release 1 - In Chapter 3: Defining and tailoring the IMS Database Recovery Facility environment, and... In Chapter 5: Starting the IMS Database Recovery Facility the syntax diagrams are changed to include the ILEF and BOTHF options: |_(_ _HALDB_(_ _ILE___ __),__)_| | |_ILEF__| | | |_INDEX_| | | |_BOTH__| | | |_BOTHF_| | - In Chapter 3: Defining and tailoring the IMS Database Recovery Facility environment, and... In Chapter 5: Starting the IMS Database Recovery Facility the syntax diagrams are changed to include the DSNTYPE option between the DSN2 and SPACE options: |_DSN2_(_variables*_)_,______________| | _BASIC_ | |_DSNTYPE(_|_LARGE_|_),______________| |_SPACE(_ _ _CYL,_ ____________ _),__| - In Chapter 3: Defining and tailoring the IMS Database Recovery Facility environment, in the section titled Specifying the Required JCL Statements, add the following after the description for BPECFG=nnn: DBRCGRP=nnn Specifies the 1-3 character identifier (ID) assigned to a group of DBRC instances that access the same RECON data set in an IMSplex. The DBRCGRP ID must be unique. If no DBRCGRP ID is specified, and the DBRC SCI Registration exit routine (DSPSCIX0) is not being used, a value of '001' is used - In Chapter 5: Starting the IMS Database Recovery Facility Update the following to include ILEF and BOTHF: IB ... ... HALDB(ILE|ILEF|INDEX|BOTH|BOTHF) ... ILEF Rebuilds only the ILDS of the specified partition by using the free space option. DFSPREC0 must have five z/OS data spaces available for processing if you select the free space option. ... BOTHF Rebuilds both the primary index and the ILDS of the specified partition. Rebuilds the ILDS by using the free space option. The utility must have five z/OS data spaces available for processing if you select the free space option. ...
Temporary fix
Comments
APAR Information
APAR number
PK32674
Reported component name
IMS DB RECOVERY
Reported component ID
5655I4400
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2006-10-09
Closed date
2007-03-09
Last modified date
2010-08-30
APAR is sysrouted FROM one or more of the following:
PK31981
APAR is sysrouted TO one or more of the following:
UK22906
Modules/Macros
FRXADF00 FRXADM10 FRXADM20 FRXAWEX FRXCAMG0 FRXCARD0 FRXCBDM0 FRXDAQS0 FRXDDCD0 FRXDDCR0 FRXDEST0 FRXDRQI0 FRXDTIN0 FRXDTRM0 FRXEDRF FRXEDRF0 FRXEDSG0 FRXEGRM FRXEGRM0 FRXEPCC0 FRXEPIC0 FRXEPQS0 FRXEPSS0 FRXESYS FRXEWSP FRXGAPI0 FRXGRDM0 FRXGRDS0 FRXGRPT0 FRXGUOW0 FRXHBUF0 FRXIAUX FRXICAI0 FRXICLI0 FRXICTL0 FRXIDYN0 FRXIIOM0 FRXIOCN0 FRXIOSM0 FRXIRTH0 FRXISMS0 FRXISMU0 FRXIVCN0 FRXIVSM0 FRXLACR0 FRXLACR1 FRXLACR2 FRXLBLD0 FRXLGET0 FRXLMRG0 FRXLNOT0 FRXLPD00 FRXLPST0 FRXLSCH0 FRXLSE15 FRXLSE35 FRXLSRT0 FRXLSRT1 FRXLSRT2 FRXLSTR0 FRXLSTS0 FRXMDBD0 FRXMINI0 FRXMINI1 FRXMSTP0 FRXMSTR0 FRXMSTR1 FRXMTRM0 FRXMTRM1 FRXPDIR0 FRXPDIS0 FRXPDSR0 FRXPDSS0 FRXPSDR0 FRXPSDS0 FRXQBIN0 FRXQBUF0 FRXRABD0 FRXRBUF0 FRXRCHK0 FRXRCTL0 FRXRDTH0 FRXREOD0 FRXRLRA0 FRXRLSR0 FRXRRR FRXRVGB FRXRVRA FRXRWAE FRXRWCE FRXRWSP FRXSDR00 FRXSDR10 FRXSINI0 FRXSINI1 FRXSTRM0 FRXSTRM1 FRXTAPI0 FRXTAS00 FRXTAU00 FRXTPIB0 FRXTPPR0 FRXTSIB0 FRXTSPR0 FRXUAPI0 FRXUORM0 FRXVADD0 FRXVASD0 FRXVAUT0 FRXVCLN0 FRXVCMD0 FRXVDIS0 FRXVRCV0 FRXVREM0 FRXVSTA0 FRXVSTA1 FRXVSTA2 FRXVSTO0 FRXVVER0 FRXVWSP FRXWRTN0 FRXWSPL0 FRXWSPM0 FRXYADY0 FRXYALL0 FRXYUDY0 FRXYUNA0
| SC18940700 |
Fix information
Fixed component name
IMS DB RECOVERY
Fixed component ID
5655I4400
Applicable component levels
R310 PSY UK22906
UP07/03/14 P F703
[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX88Z","label":"IMS Database Recovery Facility"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0"}]
Document Information
Modified date:
09 November 2020