>I've never paid that close of attention to say if it is "CLOSE"D or "FREE"D. >All I remember is when the job that was creating a new generation completed >other jobs could "access" the GDG by the relative generation.
Remember, it is the Initiator which does the ENQ/DEQ at job step allocation and unallocation, resp. So I guess it is the Initiator enqueueing on the GDG base(s) when GDSs are being used in the job. So, I further guess that the Initiator will dequeue the GDG base at the end of the last step referring to a GDS of that GDG. So it's not a question of neither CLOSE nor FREE, >As for writes/creation I never tried to use the full name. I only did it for >reads. I'm not sure how the system would handle the roll in process. I would have to verify, but when you create a data set using the full name, it is just a data set that happens to have name that looks like a GDS name. The system will not relate it to the GDG. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
