A fix is available
APAR status
Closed as program error.
Error description
When in ICAT and configuring the CI's work datasets to not use SMS by supplying volser, unit, and HLQ, the CI still appears to force the use of SMS allocation of these dynamically allocated datasets at startup time. . From Panel KD261PN: Information for working data sets (if not SMS managed): Unit ==> SYSDA___ Volume ==> ONL20A HLQ for data sets of the OMEGAMON Server ==> TECH.OMXEDB2______ FPEV0132I MSTR DATASERVERHLQ=ISVU.OMXEDB2 FPEV0138I MSTR DATASERVERUNIT=SYSDA FPEV0139I MSTR DATASERVERVOLUME=ONL26B FPEV5009I DB2C ******************************************** FPEV5009I DB2C DB2 BIND operation failed due to dataset error: FPEV5009I DB2C Return code .......... : 00000008 FPEV5009I DB2C SMS reason code ...... : 97000000x (970-000) FPEV5009I DB2C Dataset name ......... : ISVU.OMXEDB2.DB2C.PMDBBIND.JOBSIN FPEV5009I DB2C Dataset error message : FPEV5009I DB2C +----------------------------------------------------------- FPEV5009I DB2C | SEVERE STORAGE MANAGEMENT SUBSYSTEM (SMS) ERROR. FPEV5009I DB2C +----------------------------------------------------------- FPEV5009I DB2C User action .......... : FPEV5009I DB2C +----------------------------------------------------------- FPEV5009I DB2C | VERIFY THAT BLOCK SIZE OF prefix.JCL DATASET IS FPEV5009I DB2C | 80, THEN RESTART SERVER. IF PROBLEM PERSISTS, FPEV5009I DB2C | CONTACT YOUR SYSTEM ADMINISTRATOR. FPEV5009I DB2C +----------------------------------------------------------- FPEV5009I DB2C *************************************************************** FPEV5012S DB2C CREATION OF PLAN DB2PM FAILED. SEE BIND JOB OUTPUT FPEV5002I DB2C PWH IS STOPPING
Local fix
As a temporary workaround use real device number as DATASERVERUNIT value, preceded with a slash(/). For example: . DATASERVERHLQ=ISVU.OMXEDB2 DATASERVERUNIT='/41EA' DATASERVERVOLUME='ONL14A' .
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - Batch CRD * * - Performance Warehouse users * **************************************************************** * PROBLEM DESCRIPTION: PWH bind step fails when dynamic * * datasets such as .JOBSIN are not * * managed by SMS. * **************************************************************** * RECOMMENDATION: Apply this PTF * **************************************************************** PROBLEM SUMMARY: PWH bind step fails when dynamic datasets such as .JOBSIN are not managed by SMS. PROBLEM CONCLUSION: Dynamic allocation must correctly process DATASERVERVOLUME parameter
Problem conclusion
Dynamic allocation must correctly process DATASERVERVOLUME parameter KEYWORDS :NON-SMS BIND STEP PWH JOBSIN
Temporary fix
Comments
APAR Information
APAR number
PK83978
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
410
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-02
Closed date
2009-06-16
Last modified date
2009-07-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK47482 PK89573
Modules/Macros
FPEUFYDY FPEUFYD2
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R410 PSY UK47482
UP09/06/30 P F906
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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
01 July 2009