A fix is available
APAR status
Closed as new function.
Error description
The following new functions will be provided: - When HALDB primary index or ILDS is to be built, Index Builder issues DB authorization requests with EXCLUSIVE access intent for the HALDB partition, instead of READ access intent. - If 'DBAUTH YES,RECOV' is specified, Index Builder issues the CHANGE.DBDS RECOV command to turn on the RECOVERY_NEEDED flag before requesting DB authorization. Here, 'RECOV' is a new keyword for the DBAUTH control statement.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IMS Index Builder for z/OS, * * Version 3 Release 1 (FMID=H22O310) * **************************************************************** * PROBLEM DESCRIPTION: This APAR fixes the following problems: * * 1. When HALDB primary index or ILDS is * * to be built, Index Builder issues DB * * authorization requests with EXCLUSIVE * * access intent for the HALDB partition, * * instead of READ access intent. * * * * 2. If 'DBAUTH YES,RECOV' is specified, * * Index Builder issues the CHANGE.DBDS * * RECOV command to turn on the * * RECOVERY_NEEDED flag before requesting * * DB authorization. * * * * 3. If the DBRC API call fails in the * * initialization phase, MSGIIUB063E and * * MSGIIUB100E REASON 131 should be * * issued. * * IIUB063E DBRC API ERROR: FUNC=func * * RC=xxxxxxxx RSN=yyyyyyyy * * IIUB100E INDEX BUILDER INIT FAILURE * * - REASON=131 * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR fixes the problems listed in the Problem Description field.
Problem conclusion
Temporary fix
Comments
This APAR fixes the problems listed in the Problem Description field. ======== = NOTE = ======== After applying this maintenance, if BLD_PRIMARY, BLD_ILDS, or BLD_ALL is specified for a HALDB, the exclusive (EX) access is requested for each HALDB partition, instead of the read (RD) access, in the DBRC authorization process. During the index build process, any other IMS subsystem cannot access to the HALDB partitions. The DBRC authorization is released during the IMS region clean-up. After that, the DBRC NOTIFY commands are issued. If 'DBAUTH YES,RECOV' is specified, 'RECOV' option prevents other IMS subsystems from obtaining the DBRC authorization for the duration between IMS region clean-up and the DBRC NOTIFY commands by turning on the RECOVERY NEEDED flag. ======================== = Documentation Change = ======================== IBM IMS Index Builder for z/OS, V3R1, User's Guide (SC18-9101-04) should be changed as follows: ================================================================ 2.2.2 IMS Index Builder input control statements 2.2.2.2 Optional control statements 2.2.2.2.2 DBAUTH control statement The DBAUTH control statement specifies whether IMS Index Builder issues the IMS DBRC authorization request for the prime database and the indexes to prevent transactions and programs from updating the database. D - Read (RD) access is requested for the prime database or D the prime HALDB partitions to be scanned. D If DFSURWF1, HPSRSIDX, or HPSRWFP is used as the input, D no request is issued. D D If the RECOVERY NEEDED flag is turned on for the prime D database or the prime HALDB partition, exclusive (EX) D access is requested D D - Exclusive (EX) access is requested for each index or each D PSINDEX partition to be built. | Table a and Table b show the access intent of the IMS DBRC | authorization request; exclusive (EX) or read (RD). | | Table a. Access intent for prime database and indexes | (non-HALDB) | +---------------+-----------+--------------+-----------+ | | |Prime |HIDAM |Secondary | | | PROC control |database |primary index |index | | | statement | | | | | +---------------+-----------+--------------+-----------+ | | BLD_SECONDARY |RD (*1) |n/a |EX | | +---------------+-----------+--------------+-----------+ | | BLD_PRIMARY |RD |EX |n/a | | +---------------+-----------+--------------+-----------+ | | BLD_ALL |RD |EX |EX | | +---------------+-----------+--------------+-----------+ | (*1) If DFSURWF1 or HPSRSIDX is used as the input, no request | is issued for the primary database. | | Table b. Access intent for prime database and indexes (HALDB) | +---------------+------------+-------------+ | | |Prime HALDB |PSINDEX | | | PROC control |partition |partition | | | statement | | | | +---------------+------------+-------------+ | | BLD_SECONDARY |RD (*1)(*2) |EX | | +---------------+------------+-------------+ | | BLD_PRIMARY |EX |n/a | | +---------------+------------+-------------+ | | BLD_ILDS |EX |n/a | | +---------------+------------+-------------+ | | BLD_ALL |EX |EX | | +---------------+------------+-------------+ | (*1) If HPSRWFP is used as the input, no request is issued | for the prime HALDB partitions. | (*2) If the RECOVERY NEEDED flag of the primary index or ILDS | is on, exclusive (EX) access is requested. __________________________________________________________ | | | _YES____________ | | | |_,RECOV_| | | | >>__DBAUTH__|_NO_____________|_______________________>< | | | |_________________________________________________________| DBAUTH Specifies that this is a DBAUTH statement. YES IMS Index Builder issues the DBRC authorization request. | RECOV | Before requesting the DBRC authorization, IMS Index Builder | issues the CHANGE.DBDS RECOV command to turn on the RECOVERY | NEEDED flag for primary index, secondary index or ILDS to be | built, excluding a PSINDEX partition for which the PARTITION | INIT NEEDED flag is YES. | The DBRC authorization is released during the IMS region | clean-up. After that, the DBRC NOTIFY commands are issued. | This option prevents other IMS subsystems from obtaining | the DBRC authorization for the duration between IMS | region clean-up and the DBRC NOTIFY commands. NO IMS Index Builder does not issue the DBRC authorization request. If the DBAUTH statement is not specified, YES is the default. If DBRC=N is specified on the INPUT control statement, no DBRC authorization request is issued even if DBAUTH YES is specified. Note: The longest possible time that IMS Index Builder can wait for a response from DBRC is 30 minutes. Tip: You can override the default value in the runtime parameters module. See the explanation of the IIURDFLT DBAUTH entry in "Defining runtime parameters" in topic 2.4. ---------------------------------------------------------------- 3.4 IMS Index Builder messages IIUB063E DBRC API ERROR: FUNC=function RC=xxxxxxxx RSN=yyyyyyy | Explanation: An error is detected in an IMS DBRC API call. | xxxxxxxx and yyyyyyyy are return and reason codes of each | function of the IMS DBRC API, in hexadecimal. | The meanings of the codes are described in the IMS System | Programming APIs. | The DBRC message (DSPxxxxxxx) can be printed in the IIUSNAP | data set or IIUSTAT data set. | System Action: Processing stops. | User Response: Correct the error and rerun the job. ---------------------------------------------------------------- | IIUB092I DBD= dbdname|(RECON) | Explanation: This message follows the IIUB063E message and | shows the database name for which IMS DBRC API call failed. | System Action:None. | User Response:None. ---------------------------------------------------------------- | IIUB093I COMMAND=command | Explanation: This message follows the IIUB063E message and | shows the DBRC command for which IMS DBRC API call failed. | System Action:None. | User Response:None. ---------------------------------------------------------------- ---------------------------------------------------------------- 3.3.3 IMS Index Builder initialization phase secondary reason codes (The reason code 131 is added.) ---------------------------------------------------------------- | 131 DBRC API FAILURE | |Explanation: Failed in the IMS DBRC API call. |User Response: See the IIUB063E message. ---------------------------------------------------------------- ================= End of Documentation Change ==================
APAR Information
APAR number
PM92801
Reported component name
IMS INDEX BUILD
Reported component ID
5655E2400
Reported release
310
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-07-11
Closed date
2013-09-11
Last modified date
2013-10-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK97467
Modules/Macros
H22O310J IIUBDAPI IIUBIBCD IIUBINIT IIUBMSGS IIUBSTMS IIUDYN00 IIUIFS3A IIUIFS3B IIUIFS32 IIUIFS33 IIUIFS39 IIUMMSGR IIUPDBRC IIUSIBCD IIUSTART IIUTXT00
| SC18910104 |
Fix information
Fixed component name
IMS INDEX BUILD
Fixed component ID
5655E2400
Applicable component levels
R310 PSY UK97467
UP13/09/13 P F309
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":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89M","label":"IMS Index Builder"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 October 2013