A fix is available
APAR status
Closed as new function.
Error description
NEW FUNCTION FIXCAT: ZOS0204C/K ZOS0205C/K
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: OAM Object Support Customers. * **************************************************************** * PROBLEM DESCRIPTION: New Function - Toleration APAR for * * OAM support of V2R3. * * *Warning* - Review Comments and II14842 * * before application. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
Temporary fix
Comments
ZOS0203C/K **Warning** Information APAR II14842 should be reviewed before applying OA51129. If II14842 precautions are not observed then there may be a potential loss of object addressability. In OA51129, significant changes were made to the way OAM handles collection entries (catalog no longer used) that may surface an existing collection entry out of synch condition that may be present in your environment between the catalog and DB2 collection table. This out of synch condition is most likely caused by manual modification of the DB2 collection table. (at any point in time) Please review II14842 for additional details. ---------------------------------------------------------------- The z/OS MVS System Messages, Vol 4 (CBD-DMO) section: "CBR Messages" will be updated as follows: Publication numbers: SA38-0671-01 for V2R1 SA38-0671-04 for V2R2 Note: All catalog and audit references removed. =============== The following messages deleted ================ CBR0437I CBR9027I CBR9028I CBR9030I CBR9033I CBR9034I CBR9035I CBR9036I CBR9107I CBR9110I CBR9111I CBR9112I CBR9113I CBR9114I CBR9115I CBR9116I CBR9809I =============== Update to message CBR0436I ===================== CBR0436I CHGCOL unsuccessful for collection collection-name. Collection not found in DB2 | Error attempting to locate collection in DB2 | Error defining collection to DB2 | Error returned from DB2 services | Error returned from PC routine | internal error occurred when processing CHGCOL request | OLDSCN does not match DB2 | OLDMCN does not match DB2 | SGN does not match DB2 | Error attempting to delete collection in DB2}. Return code = return-code, Reason code = reason-code. Explanation: The OAMUTIL CHGCOL request ended in error. The specific errors are displayed and explained: Collection not found in DB2 An attempt was made to update an existing collection definition in DB2; however, the collection is not defined in DB2. Return-code indicates the return code from DB2 services, and reason-code indicates the SQL error returned from DB2 services. Error attempting to locate collection in DB2 An attempt was made to locate an existing collection definition in DB2; however, an error occurred other than the collection is not found. Return-code indicates the return code from DB2 services, and reason-code indicates the SQL error returned from DB2 services. Error defining collection to DB2 An error occurred while attempting to define a collection to DB2. Return-code indicates the return code from DB2 services, and reason-code indicates the SQL error returned from DB2 services. Error returned from DB2 services An error was returned from DB2 services. Return-code indicates the return code from DB2 services, and reason-code indicates the SQL error returned from DB2 services. Error returned from PC routine An error was returned from the OAM PC routine. Return-code and reason-code are IBM internal. Internal error occurred when processing CHGCOL request - If return-code = 16 and reason code = 8, an error occurred while establishing a recovery routine. - If return-code = 16 and reason code = 12, an ABEND occurred when attempting to process the CHGCOL request. OLDSCN does not match DB2 The value for OLDSCN specified on the OAMUTIL CHGCOL command does not match the default storage class that is currently defined in DB2. Return-code is set to eight, and reason-code is set to zero. OLDMCN does not match DB2 The value for OLDMCN specified on the OAMUTIL CHGCOL command does not match the default management class that is currently defined in DB2. Return-code is set to eight, and reason-code is set to zero. SGN does not match DB2 The value for SGN specified on the OAMUTIL CHGCOL command does not match the storage group name that is currently defined in DB2. Return-code is set to eight, and reason-code is set to zero. Error attempting to delete collection in DB2 An attempt to delete an existing collection definition in DB2 failed. Return-code indicates the return code from DB2 services, and reason-code indicates the SQL error returned from DB2 services. System action: The OAMUTIL CHGCOL request did not complete successfully. User response: Investigate the cause of the indicated error, and resubmit the OAMUTIL CHGCOL request when the error is resolved. Source: Object Access Method (OAM) Routing Code: - Descriptor Code: - --------------------------------------------------------------- The z/OS DFSMSdfp Diagnosis section: "OAM diagnostic aids" sub section: "OSREQ return and reason codes" to be updated as follows: Publication numbers: SC23-6863-00 for V2R1 SC23-6863-01 for V2R2 Note: Catalog references removed. ========== The following reason codes to be deleted ============ Return code=12, Reason code=B4xx01zz Description: Collection is not defined in catalog (on any request other than a store). Return code=12, Reason code=B4xx02zz Description: Collection is not defined in catalog but is defined in collection identifier table (store only). Return code=12, Reason code=B4xx03zz Description: Collection definition in catalog is incomplete and collection is not defined in collection identifier table (for example, IDCAMS was used to create a collection catalog entry that did not previously exist). ========== The following reason code to be added =============== Return code=12, Reason code=B4xx04zz Description: Collection is not defined in collection identifier table (on any request other than a store). ×**** PE17/05/10 FIX IN ERROR. SEE APAR OA52831 FOR DESCRIPTION ×**** PE17/08/04 FIX IN ERROR. SEE APAR OA53620 FOR DESCRIPTION ×**** PE17/08/04 FIX IN ERROR. SEE APAR OA53620 FOR DESCRIPTION ×**** PE19/03/21 FIX IN ERROR. SEE APAR OA57167 FOR DESCRIPTION ×**** PE19/03/21 PTF IN ERROR. SEE APAR OA57167 FOR DESCRIPTION
APAR Information
APAR number
OA51129
Reported component name
OBJECT ACCESS M
Reported component ID
5695DF180
Reported release
210
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-08-24
Closed date
2017-03-17
Last modified date
2021-03-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA91366 UA91367
Modules/Macros
CBRHDASD CBRHDDEL CBRHGSGS CBRHOBJP CBRHOPCB CBRHORCL CBRHRSOR CBRHSGDP CBRHSMSI CBRHSMSS CBRHTBSV CBRICMMN CBRIQUE CBRISTO CBRSAMIV CBRSMGM0 CBRSMGU0 CBRUCOLN
SA38067101 | SA38067104 | SC23686300 | SC23686301 |
Fix information
Fixed component name
OBJECT ACCESS M
Fixed component ID
5695DF180
Applicable component levels
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"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"210"}]
Document Information
Modified date:
05 March 2021