In a recent note, Howard Brazee said: > Date: Mon, 7 May 2007 08:36:38 -0600 > > Is this related to the intermittent problem of editing a member > exiting from it, submitting JCL that uses, and then having the JCL > wait until we log off before it knows we're done with it? > Is this a JCLLIB member, or any other data member?
Does the Reader stall until you log off, or do you see an outdated instance of the member? I can envision this happening with a PDSE, given PDSE's LUW isolation protocol; less likely with a traditional PDS. Does the Reader/Converter hold JCLLIB open for extended times? Is there a way to refresh the Reader's view of directories in the JCLLIB concatenation? It's my understanding that a task's view of PDSE directory entries is frozen until that task closes the library. I'm puzzled that synchronizing requires ending the updating task rather than the reading task. Etc. -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
