On Thu, 3 Jul 2008 09:24:44 +0200, Vernooy, C.P. - SPLXM wrote: > >"Al Chu" wrote in message >news:<[EMAIL PROTECTED]>... >> Hi >> >> I am not a sysprog nor an expert. >> I want to read a dataset(seq) which is created by JCL DISP=(NEW,) of a >long >> running job while the job is running. When i try to browse the dataset >using >> ISPF, I have 'dataset in use' msg. >> I tried to rename the dataset using IDCAMS ALTER in the next step >after the >> creation step and tried to read the renamed dataset, but still no >good. >> The last step is the long running step which writes some records in >the >> dataset. >> If that last step allocates the data set DISP=SHR, with the new name assigned by IDCAMS ALTER, I don't understand why it can't be read concurrently by other jobs. I don't believe ALTER leaves a persistent ENQ on the data set name.
>This is not possible. The job has the dataset exclusive and this really >means it has the dataset exlusively. > >There an other way, that might be usable for you: If the job can write >to SYSOUT i.s.o. a dataset, you can read the output it has produced with >SDSF while the job is running. > Same would be possible with a UNIX file (HFS or zFS), and access would be more generally possible than via SDSF. Or, preallocate the data set in a separate job, and allocate it only DISP=SHR in the "long running job". Or, wrap your long running step in a Rexx exec which allocates the data set dynamically SHR. The exclusive ENQ will be freed after the last step which mentions the data set name in JCL. -- gil ---------------------------------------------------------------------- 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
