HELP: Preventing concurrent jobs from using the same input file.
- From: "Catch_22" <catch_20_2@xxxxxxxxxxx>
- Date: 22 Nov 2005 20:25:23 -0800
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.
I did post this in the cobol usergroup though found this subsequently
..... I'm sorry if this has caused any problems.
Regards,
Ian.
.
- Prev by Date: Re: displaying hexadecimal content of a field in COBOL
- Next by Date: Re: SYS1.UADS - when is it read?
- Previous by thread: What were RACF profile classes $INT
- Next by thread: Master Catalog
- Index(es):
Relevant Pages
|
