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. ----------------------------------------- The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. The information may also constitute a legally privileged confidential communication. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you ---------------------------------------------------------------------- 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
