|
Hi Todd -
For the second time in a few days, we have received this error when trying to delete a data area within a batch job. The data area is created in the submitting program. Then a new program is submitted. The submitted program checks for the data area, retrieves its value, and is supposed to delete the data area. It has worked fine for a number of years.
I used to run into the same kind of problem with changing data areas (CHGDTAARA). Something would have it locked long enough to cause a halt, but not long enough to find out what job was holding the lock. I suspect the disaster recovery software.
I added ALCOBJ/DLCOBJ pairs around all data area changes, and also around most retrieves of data areas that get changed by programs, with a 60 second wait time. Lock type *EXCL if changing (the same would apply for deleting), *SHRNUP if retrieving. No more problems.
Ken http://www.ke9nr.net/ Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.