A fix is available
APAR status
Closed as new function.
Error description
HDPC support of the IMSDALIB DD statement
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: IBM IMS High Performance Pointer Checker for * * z/OS Version 3 Release 1 (FMID=HPC2310) * * users who run HD Pointer Checker in * * stand-alone jobs. * **************************************************************** * PROBLEM DESCRIPTION: This APAR enables HD Pointer Checker to * * support the IMSDALIB DD statement. * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** This APAR enables HD Pointer Checker in stand-alone jobs to support the IMSDALIB DD statement that specifies DFSMDA members for dynamically allocating the database data sets of non-HALDBs and RECON data sets. This DD statement is optional and effective when you specify EXEC PGM=FABPPC00. When you specify EXEC PGM=FABPPC00, all the data sets in the STEPLIB concatenation, including the MDA library, must be APF-authorized. If you do not want to APF-authorize the MDA library, use the IMSDALIB DD statement to specify the MDA library. If DFSMDA members are found in both the STEPLIB DD and the IMSDALIB DD, the DFSMDA member found from the IMSDALIB DD is used. Note: After applying this APAR, IMSACB DD need to be specified even when HD Pointer Checker runs in the DBB region and the IMS managed ACBs function is enabled.
Problem conclusion
Temporary fix
Comments
Documentation Changes: Note: The Part and Chapter numbers are those of the PDF file. The documentation is modified as follows: ================================================================ IMS High Performance Pointer Checker for z/OS, V3R1, User's Guide (SC19240103) ================================================================ >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Part 2. HD Pointer Checker utility >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ---------------------------------------------------------------- Chapter 4. Using the HD Pointer Checker processor ---------------------------------------------------------------- - Restrictions and considerations - Restrictions and considerations for running HD Pointer Checker when the IMS managed ACBs function enabled ---------------------------------------------------------------- << The description has been changed as follows: >> The following restrictions apply when the IMS managed ACBs function is enabled. - When the IMS managed ACBs function is enabled, HD Pointer Checker cannot run in the ULU or DLI region. - You must specify the IMSACB DD statement whether the IMS managed ACBs function is enabled or not. For information about the IMS managed ACBs function, see the topic "IMS management of ACBs enhancement" in IMS V14 Release Planning. ---------------------------------------------------------------- - Job control language - FABPMAIN DD statements - DD statements for PROC TYPE=ALL/SCAN/CHECK/BLKMAP ---------------------------------------------------------------- << The following entries in Table 6, 9, 12, and 14. Input and output DD statements have been changed: >> DD name Use PDS Need Aditional requirements -------- ----- --- -------- ------------------------------------ IMSACB Input PDS Optional You must specify this DD statement when the job runs in the DBB region. -------- ----- --- -------- ------------------------------------ IMSDALIB Input PDS Optional This data set contains the DFSMDA members for dynamically allocating the database data sets of non-HALDBs and RECON data sets. When you specify EXEC PGM=FABPPC00 and you do not want to APF-authorize the MDA library, use the IMSDALIB DD statement to specify the MDA library This DD statement is effective when you specify EXEC PGM=FABPPC00. Otherwise, this DD statement is ignored. -------- ----- --- -------- ------------------------------------ DFSHDBSC Input Optional This data set is required when HD Pointer Checker processes an IMS catalog database that is not registered in the RECON data sets. If you omit this DD statement, the DFSHDBSC data set is dynamically allocated by the DFSMDA member in the MDA library on the STEPLIB DD statement. ---------------------------------------------------------------- - Job control language - FABPMAIN DD statements - DD statement description ---------------------------------------------------------------- STEPLIB DD : The library that contains the DFSMDA members for dynamic allocation (optional) <<The following description has been added:>> Tip: If you specify EXEC PGM=FABPPC00 and you do not want to APF-authorize the library that contains the DFSMDA members for the database data sets of non-HALDBs and RECON data sets, specify the MDA library on the IMSDALIB DD statement. Requirement: To use the DFSMDA member for allocating the IMS catalog partition definition data set (DFSHDBSC), specify the MDA library on the STEPLIB DD statement. : <<The descriptions for the following DD statements have been changed:>> IMSACB DD This optional input data set is an IMS.ACBLIB (partitioned data set). You must code this DD statement if HD Pointer Checker runs in a DBB region. DFSHDBSC DD This optional input data set is the IMS catalog partition definition data set. When you run HD Pointer Checker for an IMS catalog database that is not registered in the RECON data set, you must specify the data set in which the IMS catalog database is defined. If you omit this DD statement, the DFSHDBSC data set is allocated dynamically by the DFSMDA member. In this case, the DFSMDA member found from the STEPLIB DD is used for dynamic allocation. RECONx DD These optional data sets make up the DBRC RECON data sets. RECON data sets are required when you run HD Pointer Checker against a HALDB or when you want to have image copy data sets allocated dynamically. If you omit these DD statements, the RECON data set are allocated dynamically by the DFSMDA member. In this case, th DFSMDA member found from the STEPLIB DD or IMSDALIB DD is used for dynamic allocation. If DFSMDA members are found in both the STEPLIB DD and the IMSDALIB DD, the DFSMDA member found from the IMSDALIB DD is used. <<The description about IMSDALIB DD has been added:>> IMSDALIB DD This optional input data set contains the DFSMDA members for dynamically allocating the database data sets of non-HALDBs and RECON data sets. This DD statement is effective when you specify EXEC PGM=FABPPC00. Otherwise, this DD statement is ignored. When you specify EXEC PGM=FABPPC00, all the data sets in the STEPLIB concatenation, including the MDA library, must be APF-authorized. If you do not want to APF-authorize the MDA library, use the IMSDALIB DD statement to specify the MDA library. If DFSMDA members are found in both the STEPLIB DD and the IMSDALIB DD, the DFSMDA member found from the IMSDALIB DD is used. ---------------------------------------------------------------- - Job control language - Dynamic allocation for database data set and image copy data set ---------------------------------------------------------------- Database data sets of non-HALDBs << The description has been changed as follows: >> The database data sets of the HDAM, HIDAM, HISAM, SHISAM, and index databases are dynamically allocated by use of the DFSMDA member in the MDA library. When you specify EXEC PGM=FABPPC00, specify the MDA library on the STEPLIB or the IMSDALIB DD statement. All the data sets that are defined in the STEPLIB concatenation, including the MDA library, must be APF-authorized. If you do not want to APF-authorize the MDA library, use the IMSDALIB DD statement to specify the MDA library. If DFSMDA members are found in both the STEPLIB DD and the IMSDALIB DD, the DFSMDA member found from the IMSDALIB DD is used. When you specify EXEC PGM=DFSRRC00, specify the MDA library on the STEPLIB DD statement. The MDA library does not require APF-authorization. If you specify the IMSDALIB DD statement, the IMSDALIB DD statement is ignored. The NODYNALLOC statement in DFSVSMxx member is not referred to. : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Part 8. Troubleshooting >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ---------------------------------------------------------------- Chapter 37. Messages and codes - HD Pointer Checker messages and codes - HD Pointer Checker messages ---------------------------------------------------------------- << The following new messages have been added: >> FABP3667E DBRC IS REQUIRED TO PROCESS HALDB Explanation: To process a HALDB or an IMS catalog database that is registered in the RECON data set, DBRC must be activated. System action: HD Pointer Checker issues a USER 3667 abend. User response: Specify Y for the 14th parameter of the EXEC statement and rerun the job. FABP3868E DD NOT FOUND FOR DB dbname DD ddname Explanation: The indicated DD statement is not found in the JCL stream, the DFSMDA member, or the RECON data set. The DD statement for the indicated database must be provided. System action: HD Pointer Checker issues a USER 3868 abend. User response: Add the missing DD statement to the JCL and rerun the job. If you want to dynamically allocate the database data set, make sure that a valid DFSMDA member exists and then rerun the job. If no valid DFSMDA member exists, create a DFSMDA member for the database data set and rerun the job. FABP3869E FIND FAILED FOR DDNAME ddname MEMBER member. RC=rc RSN=rsn Explanation: The FIND macro failed for the indicated member. This message contains the member name and the DD statement that points to the data set that contains this member. RC and RSN are the return and reason code from the FIND macro. System action: HD Pointer Checker issues a USER 3869 abend. User response: Refer to z/OS DFSMS Macro Instructions for Data Sets for the explanation of the return and reason codes. Correct all errors and rerun the job. If the problem remains, save the entire run listing (including the dump, JCL, and all reports from IMS HP Pointer Checker), and contact IBM Software Support. FABP3870E READ ERROR FOR DDNAME ddname MEMBER member Explanation: The READ macro failed to read a member. This message contains the member name and the DD statement that points to the data set that contains this member. System action: HD Pointer Checker issues a USER 3870 abend. User response: Locate the MVS system message that describes the I/O error and correct the error. Then rerun the job. If the problem remains, save the entire run listing (including the dump, JCL, and all reports from IMS HP Pointer Checker), and contact IBM Software Support. FABP3871E MEMBER member WAS NOT FOUND IN ddname DD Explanation: The indicated member does not exist in the data set that is pointed to from the indicated DD statement. System action: HD Pointer Checker issues a USER 3871 abend. User response: Specify the correct data set and rerun the job. FABP3872E FAILED IN PARTITION SELECTION; REQUEST=function, RC=rc Explanation: HD Pointer Checker received an error return code from the HALDB Partition Selection exit routine. function is the requested function and rc is the return code from the HALDB Partition Selection exit routine. System action: HD Pointer Checker issues a USER 3872 abend. User response: Specify the correct HALDB Partition Selection exit routine in the library that is concatenated to the STEPLIB DD statement and rerun the job. FABP3873E DB dbdname IS NOT REGISTERED IN RECON Explanation: The indicated database is not registered in RECON. System action: HD Pointer Checker issues a USER 3873 abend. User response: Ensure that the following resources are correctly specified in the JCL. Then rerun the job. - The name of the database is specified on the DB parameter of the DATABASE statement. - The DBDLIB data set is specified on the IMS DD statement or the ACBLIB data set is specified on the IMSACB DD statement. - The correct RECON data sets are specified. FABP3874E NO PARTITIONS ARE REGISTERED IN RECON FOR HALDB dbdnam Explanation: The partitions of the indicated HALDB are not registered in RECON. System action: HD Pointer Checker issues a USER 3874 abend. User response: Ensure that the following resources are correctly specified in the JCL. Then rerun the job. - The name of the database is specified on the DB parameter of the DATABASE statement. - The DBDLIB data set is specified on the IMS DD statement or the ACBLIB data set is specified on the IMSACB DD statement. - The correct RECON data sets are specified. FABP3875E DB dbdname PART partname IS NOT REGISTERED IN RECON Explanation: In the RECON data set, the indicated partition is not registered as a partition of the indicated database. System action: HD Pointer Checker issues a USER 3875 abend. User response: Specify the correct partition name on the PART parameter of the DATABASE statement and the correct RECON data sets. Then rerun the job. FABP4028I IMSDALIB DD STATEMENT IS IGNORED Explanation: HD Pointer Checker ignored the IMSDALIB DD statement because PGM=DFSRRC00 is specified on the EXEC statement. System action: Processing continues. User response: If you want to allocate the database data sets of the non-HALDB dynamically, specify the MDA library in either of the following ways: - Specify the MDA library on the STEPLIB DD statement. - Change the PGM parameter of the EXEC statement to FABPPC00. << The explanation section of message FABP3840E has been updated as follows: >> FABP3840E UNSUPPORTED LEVEL OF IMS IS BEING USED: mmm IMS LEVEL OF THIS RUN Explanation: The version of the IMS RESLIB that is found in the STEPLIB or JOBLIB concatenation is not supported. mmm represents the IMS level. System action: HD Pointer Checker issues a USER 3840 abend. User response: You must run HD Pointer Checker with the correct version of IMS.
APAR Information
APAR number
PI70429
Reported component name
IMS POINTER CHE
Reported component ID
5655E0900
Reported release
310
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function / Xsystem
Submitted date
2016-10-10
Closed date
2016-10-21
Last modified date
2016-11-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI41789
Modules/Macros
FABPACBL FABPALLC FABPCALC FABPCDBI FABPCDDL FABPLINK FABPMAIN FABPMSGT FABPPC00 FABPURTO HPC2310J
| SC19240103 |
Fix information
Fixed component name
IMS POINTER CHE
Fixed component ID
5655E0900
Applicable component levels
R310 PSY UI41789
UP16/10/25 P F610
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":"SSCX89G","label":"IMS HP Pointer Checker"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 November 2016