Kirk Talman 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.
IMHO, unserialized use of a PDS that's being compressed is a big
mistake! I suggest you a) compress the PDS with DISP=OLD (SYSDSN
exclusive), b) use an alternate serialization mechanism of some kind, or
c) convert the library to PDSE and stop compressing it altogether.
--
.-----------------------------------------------------------------.
| Edward E. Jaffe | |
| Mgr, Research & Development | [EMAIL PROTECTED] |
| Phoenix Software International | Tel: (310) 338-0400 x318 |
| 5200 W Century Blvd, Suite 800 | Fax: (310) 338-0801 |
| Los Angeles, CA 90045 | http://www.phoenixsoftware.com |
'-----------------------------------------------------------------'
----------------------------------------------------------------------
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
