A fix is available
APAR status
Closed as program error.
Error description
If the HISTORY data set contains data for HALDBs, Space Monitor reports wrong values for the HALDBs in the %SZ field of the Space Analysis by Data Set report and the Space Monitor Exception report after HALDBs are changed to OSAM8G.
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 Space Monitor and DB * * Historical Data Analyzer. * **************************************************************** * PROBLEM DESCRIPTION: Space Monitor as a stand-alone utility * * reports wrong values for HALDBs in the * * %SZ field of the Space Analysis by Data * * Set report and the Space Monitor * * Exception report. * * * * DB Historical Data Analyzer incorrectly * * reports data set groups for HALDBs as * * numeric values in the HD Analysis * * report and the HD Pointer Checker * * Summary report. * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** When the following conditions are met, HD Pointer Checker with HISTORY=YES stores the wrong OSAM8G or NOOSAM8G information for the HALDBs into the HISTORY data set after changing the HALDBs from NOOSAM8G to OSAM8G or from OSAM8G to NOOSAM8G: - APAR/PTF PI27563/UI24016 has been applied. - The HISTORY data set has already contained data for the HALDBs. As the result, when you run Space Monitor as a stand-alone utility, Space Monitor uses the incorrect maximum data set size for the HALDBs and reports wrong values for the HALDBs in the %SZ field of the Space Analysis by Data Set report and the Space Monitor Exception report. DB Historical Data Analyzer wrongly reports the following for HALDB OSAM8G: - data set groups as numeric values and the EPSCHK= option value as N/A in the HD Analysis report. - data set groups as numeric values the HD Pointer Checker Summary report. **** Note **** After applying this APAR and before running Space Monitor as a stand-alone utility and DB Historical Data Analyzer, you must run HD Pointer Checker for the HALDBs with HISTORY=YES to store the correct OSAM8G or NOOSAM8G information into the HISTORY data set.
Problem conclusion
The following modules have been modified to fix the error: FABPUPHR, FABGANAL, FABGSUMM
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PI58614
Reported component name
IMS POINTER CHE
Reported component ID
5655E0900
Reported release
310
Status
CLOSED PER
PE
YesPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-03-06
Closed date
2016-03-31
Last modified date
2016-05-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI36672
Modules/Macros
FABGANAL FABGSUMM FABPUPHR
Fix information
Fixed component name
IMS POINTER CHE
Fixed component ID
5655E0900
Applicable component levels
R310 PSY UI36672
UP16/04/02 P F604 «
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:
04 May 2016