Author Topic: OAM Maintenance Causes Issue With CMOD  (Read 178 times)

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 597
    • View Profile
OAM Maintenance Causes Issue With CMOD
« on: April 14, 2017, 08:57:29 AM »
OAM APAR OA51129

PROBLEM SUMMARY:                                               
****************************************************************
* USERS AFFECTED: OAM Object Support Customers.                *
****************************************************************
* PROBLEM DESCRIPTION: New Function - Toleration APAR for      *
*                      OAM support of V2R3.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************



has spawned...

CMOD APAR PI80022...

ARS0430E ARSTTT OAM ERROR: ARSMVSDW: 0000000B(0000000C-B4040400)
AFTER APPLYING OAM APAR OA51129


Ed
« Last Edit: April 14, 2017, 07:21:01 PM by Ed_Arnold »

hakan_carlberg

  • Jr. Member
  • **
  • Posts: 74
    • View Profile
Re: OAM Maintenance Causes Issue With CMOD
« Reply #1 on: April 18, 2017, 09:28:12 PM »
Hi Everyone

Some questions:                                                         
- How will it affect CMOD ?                                             
- Can I avoid the problem ?                                             
- Any Local Fix ? ( I know PI80022 doesn't say anuthing regarding "local fix", but I need to ask)                                                     
- any specific CMOD version ?

Regards
/H Carlberg

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 597
    • View Profile
Re: OAM Maintenance Causes Issue With CMOD
« Reply #2 on: April 19, 2017, 07:56:23 AM »
Håkan - always good to hear from you.

This issue was surfaced by an internal test case.

We try to save an object to a never-been-used collection name.  Before we STORE an object we try to DELETE it.  If an object was never stored in the collection, previously we got B4xx01yy on the DELETE, which CMOD treated as "doesn't exist" and proceeded with doing a STORE. 

After the OAM compatibility PTF we now receive B4xx04yy and the plan was to add that to the list of reason codes that means "doesn't exist".

However, OAM development is currently looking at this and CMOD is "standing by".

Ed

hakan_carlberg

  • Jr. Member
  • **
  • Posts: 74
    • View Profile
Re: OAM Maintenance Causes Issue With CMOD
« Reply #3 on: April 20, 2017, 07:05:22 AM »
Hi

Additional info. I've opened an PMR and asked the same question and got the answer:
"
APAR PI80022 has been closed/cancelled, there will be no code changes   
made to CMOD due to the OAM changes. APAR OA52549 has been opened by the
OAM component to deal with the issues brought on by OA51129.           
                                                                       
Any questions regarding those APARs should be directed in a PMR to the 
OAM compoenent. As far a CMOD goes, nothing is changing, PI80022 has   
been cancelled.                 
"

Regards
/H Carlberg

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 597
    • View Profile
Re: OAM Maintenance Causes Issue With CMOD
« Reply #4 on: April 20, 2017, 01:47:01 PM »
Håkan - you were too quick for me.

I was going to append that information to this thread today but you beat me to it.

Ed

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 597
    • View Profile
Re: OAM Maintenance Causes Issue With CMOD
« Reply #5 on: May 04, 2017, 12:17:46 PM »
PTFs are now available:

PTF#      Size-KB Rel PUT  Status Hiper FMID     
--------  ------- --- ---- ------ ----- ---------
UA91700       24            COR     NO  HDZ2210 
UA91701       24            COR     NO  HDZ2220