Re: Fw: INFOPAC

[Kem King]

Ron  Sam,
The official response from IBM was to fix the application code and clear out
any GETMAIN'd storage before using it.  

I found the IBM APAR OA27291 from a previous post by Sam.  This APAR only
provides a new workaround to the GETMAIN macro change.
The ASG incident was # 674406 and was resolved by their Mobius developer who
provided a small zap to module JCLEXIT that now clears its storage before
using it.  We've been running INFOPAC-JCL for two days now without anymore
S0C4 abends, so the pmr and ASG incident were closed.

Kem King

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Fw: INFOPAC

[Kem King]

We just resolved a similar issue with Infopac-JCL dumping with S0C4's while
testing on z/OS 1.10 lpar.  I too opened a pmr with IBM and ASG.  And after
MUCH research we found that the Infopac code was not clearing GETMAIN'd
storage before using it, which caused the dump.  

I also found APAR OA2791 which described it very clearly as an undocumented
change to the GETMAIN macro.  The APAR offers a new DIAGnn option to bypass
the new feature.  

I was able to get the Mobius developer at ASG to offer a zap which cleared
the storage and thus, resolved our problem.  It sounds like you may be
affected by the same issue.

Hope this helps,
Kem King 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html