CA just issued a HYPER notification to hold installing IBM PTF UA40878.
The CA notification and IBM APAR OA24573 are appended.
Best Regards,
Sam Knutson, GEICO
System z Performance and Availability Management
mailto:[EMAIL PROTECTED]
(office) 301.986.3574
"Think big, act bold, start simple, grow fast..."
CA HYPER Notification
Subject: CA PML SOLUTION NOTIFICATION - RI00049
Title: THE STARTING OF CAS9 UNDER Z/OS 1.9 WITH IBM
Product: CAIRIM
Release: 1.0
Opsys: OS
Solution #: 429
https://support.ca.com/irj/portal/SolutionResults?aparNo=RI00049&actionI
D=4
Description:
PRODUCT: CAIRIM-MVS RELEASE: 1.0
PEA #: RI00049 DATE: 29 MAY 2008
***** Product Error Alert *****
PROBLEM DESCRIPTION: The starting of CAS9 under z/OS 1.9 with IBM
PTF UA40878 applied can result in address spaces terminating End
Of Memory with abend S0C4's in SMF processing. UA40878 is the
PTF for IBM APAR OA24573.
HYPER: YES
DISTRIBUTION CODE: A (A=Available, I=Internal)
PROBLEM RESOLUTION:
CA strongly recommends that the PTF for OA24573 not be applied at this
time. A resolution for this problem is currently under investigation.
IBM APAR
APAR Identifier ...... OA24573 Last Changed ........ 08/05/29
24-BIT ADDRESSING INTO SMFEWTM RETURNS WITH 31-BIT ADDRESSING
Symptom ...... AB ABEND0C4 Status ........... CLOSED PER
Severity ................... 2 Date Closed ......... 08/05/16
Component .......... 5752SC100 Duplicate of ........
Reported Release ......... 740 Fixed Release ............ 999
Component Name 5752 SMF SCHEDU Special Notice
Current Target Date ..08/07/10 Flags
SCP ...................
Platform ............
Status Detail: SHIPMENT - Packaged solution is available for
shipment.
PE PTF List:
PTF List:
Release 740 : UA40878 available 08/05/28 (1000 )
Release 750 : UA40900 available 08/05/29 (1000 )
Parent APAR:
Child APAR list:
ERROR DESCRIPTION:
1. When an application issues the SMFEWTM macro in 24 bit mode
with BRANCH=YES, the return from the macro will be in 31 bit
addressing mode. This could lead to an abend0C4 since the
program issuing the SMFEWTM will then be running in 31bit
mode rather than the expected 24bit mode.
2. When an application issues the SMFEWTM macro in 24 bit mode
with BRANCH=NO and the required WRKAREA parameter is not
specified, SMF will provide a default workarea above the
16 MB line. IEEMB830 will then try to access that workarea
in 24 bit mode, and could receive an abend0C4 since it will
be looking at a page below the 16 MB line, which may not be
Getmained, or (if Getmained) may not be in the proper key.
Both of these problems only exist at z/OS 1.9 and above.
Additional Keywords:
24bit 31bit, AMODE24 AMODE31, 16MB
LOCAL FIX:
Insert a SAM24 instruction immediately after the SMFEWTM.
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: HBB7740 and above installations *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4 for 24-bit callers of SMFEWTM *
****************************************************************
* RECOMMENDATION: *
****************************************************************
ABEND0C4 conditions may result when calling the SMFEWTM
service used for writing SMF records. This can happen for two
reasons:
1. For BRANCH=YES callers, the addressing mode on return from
the SMFEWTM service is 31-bit, even though the caller may
have been running in 24-bit mode.
2. For BRANCH=NO callers, the SMFEWTM default parameter list
is created in 31-bit storage, even for 24-bit callers.
See the Error Description section of the submitter text of
this APAR for more information about ABEND0C4 conditions
following a call to SMFEWTM.
PROBLEM CONCLUSION:
For the reasons identified:
1. SMFEWTM return processing will be changed so that the
caller's addressing mode is reinstated upon return to
its caller.
2. The SMFEWTM default parameter area will be built in
24-bit storage. In this way, it will be addressable by
both 24-bit and 31-bit callers.
TEMPORARY FIX:
COMMENTS:
MODULES/MACROS: IEEMB8G8 IEEMB838
SRLS: NONE
RTN CODES:
CIRCUMVENTION:
MESSAGE TO SUBMITTER:
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Jim Mulder
Sent: Tuesday, April 08, 2008 3:40 AM
To: [email protected]
Subject: Re: SMFEWTM
IBM Mainframe Discussion List <[email protected]> wrote on 04/07/2008
05:53:41 PM:
> Then I will have to check if this intercept routine may be the guilty
one.
>
> Thanks Jim, for putting me on track.
> And thanks Chuck for the specific reference to a product.
>
> I am just responsible for the application that suffered. I will ask
> the systems
> people tomorrow if they have the named product installed.
>
I have reproduced the problem with a testcase on a z/OS 1.9 test
system with no intercept routines, so there is a problem in z.OS 1.9
with calls to SMFEWTM in 24-bit addressing mode. Your systems people
have already opened a PMR, so we can deal with this through
the normal support process.
Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
