On Thu, 19 Jan 2006 11:52:51 -0500, Kirk Talman <[EMAIL PROTECTED]> wrote:
>I own a piece of Assembler batch code that reads a parm member of a system >library managed by Endeavor. This piece of code runs many times a day on >all (10) production plexes. > >The FINE Endeavor folks have chosen to compress the library on each plex >around 5 am each day. The collisions do not, unfortunately, cause an >abend. The program "reads" the member and finds garbage, causing it to >fail in its task, returning the wrong return code. > >I am wondering if I attempt to validate the parm, and finding "garbage", >what are the conditions under which I can get the correct information? > >If I wait say 10-20 seconds, do I have to close and reopen the file before >reissuing the FIND macro for the member? Are there any other gotchas >lurking in the shadows? > >All lpars appear to be zOS 1.4. > > Opt. #1 (best opt.) Convert to PDSE and never worry about compress Opt. #2, change JCL to DISP=OLD We changed Endevor libs to PDSE years ago. The Endeavor folks used to schedule jobs to compress our Endevor controlled JES2 proclibs and cause problems. PDSE resolved that and later on we converted to dynamic proclibs after z/OS 1.2. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America and Farmers Insurance Group mailto: [EMAIL PROTECTED] Systems Programming expert at http://expertanswercenter.techtarget.com/ 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
