Re: HELP - Preventing access to input files for two concurrent jobs.
- From: "William M. Klein" <wmklein@xxxxxxxxxxxxxxxxx>
- Date: Wed, 23 Nov 2005 07:34:37 GMT
Check out the
DISP=OLD
JCL parameter.
"Catch_22" <catch_20_2@xxxxxxxxxxx> wrote in message
news:1132719750.184297.129550@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> I have an issue I'm hoping to find a solution to. I work in a mainframe
> environment using z/OS.
>
> I have a program that reads in three files, it will use records from
> these files and output any records that wasn't used, to three
> corresponding output files. The input and output files are stored as
> GDGs.
>
> The issue I wish to safe guard against is an operator invoking the
> program in two different jobs at the same time. It is important that
> the input files only be used by one program at a time and that data
> used by the program is unique.
>
> I'm of the understanding that if a second job is started while the
> first is still running that the second job will wait to use the file
> being used in the first job - thus it will use data that may have
> already been used by the first job.
>
> Does anyone have any ideas on how it might be possible to prevent the
> second job from using the old GDG ..... or possibly using the next
> generation created by the first job when it has completed ?
>
> I know it's possible to prevent this happening for scheduled jobs via
> Zeke though we also have many manually executed jobs as well.
>
> Any help that people could provide would be greatly appreciated.
>
> Regards,
> Ian.
>
.
- References:
- Prev by Date: Re: Cobol books & experiences
- Next by Date: Re: Cobol books & experiences
- Previous by thread: HELP - Preventing access to input files for two concurrent jobs.
- Next by thread: Re: HELP - Preventing access to input files for two concurrent jobs.
- Index(es):
Relevant Pages
|