On 28 Dec 2010 03:47:55 -0800, [email protected] (??? ?? ???) wrote:

>The reason for this request is that the specified DSNAME is a VSAM KSDS. Many 
>jobs read the file, and some update it.
>Sometimes, about once a year, a job running on the 'wrong' LPAR updates the 
>file, and corrupts it.
>The corruption is not immediately apparent, and may be discovered days or 
>weeks after it happens.
>The jobs accessing the file are both production (scheduled) jobs and one time, 
>ad hoc jobs.
>
>We have access to OPS, if that may help.

I'm wondering if it might be worth exploring having a procedure
involving two copies of that file - one for update which goes though a
strong procedure before replacing the other file.

----------------------------------------------------------------------
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

Reply via email to