Re: Heads Up: OA17292 Data Loss with VSAM LSR Hiperspace

2006-08-03 Thread Jousma, David 
Here is the text from IBMLINK

APAR Identifier .. OA17292  Last Changed  06/08/03
  HIPERSPACE BUFFERS ARE NOT INVALIDATED AFTER IMS NOTIFY
 
 
  Symptom .. IN INCORROUT Status ... OPEN
  Severity ... 1  Date Closed .
  Component .. 5695DF106  Duplicate of 
  Reported Release . 1K0  Fixed Release 
  Component Name DFSMS VSAM MEDA  Special Notice   HIPER
  Current Target Date ..06/08/02  Flags
  SCP ...
  Platform  PERVASIVE  DATALOSS
 
  Status Detail: DESIGN/CODE - APAR solution is being designed
   and coded.
 
  PE PTF List:
 
  PTF List:
 
  Tentative Affected Releases and Current Relief Available:
  Release 1K0   : Relief is available in the form of: AA17292
 
 
  Parent APAR:
  Child APAR list:
 
 
  ERROR DESCRIPTION:
  IMS issues a macro interface to VSAM to invalidate a particular
  buffer in the LSR buffer pool.  If the buffer resides in a
  hiperspace buffer, it is not invalidated and can lead to lost
  updates if that address space later uses that downlevel copy
  of the buffer.  The external symptoms can be 'pointer checker'
  errors, ABENU0852 and ABEND0849.
 
  The problem only affects IMS applications using IRLM Notify that
  have hiperspace buffers in the LSR pool.  It does not affect
  those IMS users of cross invalidate using the coupling facility.
 
  IMS is the only user of this function.  No other VSAM users are
  affected.
 
  ADDITIONAL SYMPTOMS:
  ABEND0C4 in IDA019XV
  msgDFS629I PSW AT ERROR = 077C2000 82D79960  SYS1
  msgDFS629I MODID = UNKNOWN   EPA = UNKNOWN   SYS1
 
 
 
  LOCAL FIX:
  Remove hiperspace buffers from the LSR pool definition.
  To do this, look in the IMS startup parms under DFSVSAMP DD or
  the DFSVSMxx member.Remove any HSO,HSR, HSn subparms from
  VSRBF= control statments. 



Dave Jousma
Principal Systems Programmer
[EMAIL PROTECTED]
616.653.8429


-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Chase, John
Sent: Thursday, August 03, 2006 2:52 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Heads Up: OA17292 Data Loss with VSAM LSR Hiperspace


Did that answer originate from DFSMS support? or CICS Support?

-jc-


This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.

--
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

Re: Heads Up: OA17292 Data Loss with VSAM LSR Hiperspace

2006-08-03 Thread Mark Zelden 
On Thu, 3 Aug 2006 12:00:27 -0500, Brian Peterson
<[EMAIL PROTECTED]> wrote:


>The APAR text mentions IMS as being exposed.  The defect, however, is
>within VSAM.  I do not know if other VSAM LSR exploiters (such as CICS) are
>affected.  I have asked that question.
>

That APAR says this (at least it does now):

===
  The problem only affects IMS applications using IRLM Notify that
  have hiperspace buffers in the LSR pool.  It does not affect
  those IMS users of cross invalidate using the coupling facility.
 
  IMS is the only user of this function.  No other VSAM users are
  affected.
===

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group
mailto: [EMAIL PROTECTED]
z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

--
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

Re: Heads Up: OA17292 Data Loss with VSAM LSR Hiperspace

2006-08-03 Thread Chase, John 
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Brian Peterson
> On Thu, 3 Aug 2006 12:00:27 -0500, Brian Peterson wrote:
> 
> >   I do not know if other VSAM LSR exploiters (such as CICS) 
> >are affected.  I have asked that question.
> 
> The question's answer is "IMS and VSAM only are exposed.  
> CICS is not."

Did that answer originate from DFSMS support? or CICS Support?

-jc-

--
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

Re: Heads Up: OA17292 Data Loss with VSAM LSR Hiperspace

2006-08-03 Thread Brian Peterson 
The question's answer is "IMS and VSAM only are exposed.  CICS is not."

Brian

On Thu, 3 Aug 2006 12:00:27 -0500, Brian Peterson 
<[EMAIL PROTECTED]> wrote:

>   I do not know if other VSAM LSR exploiters (such as CICS) are
>affected.  I have asked that question.
>

--
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