|
Thanks Sudha. The problem seemed to be with the way the program was compiled. I recompiled it specifying DFTACTGRP(*YES) and it seems to be working fine now. Albert -----Original Message----- From: SRamanujan@sungardfutures.com [SMTP:SRamanujan@sungardfutures.com] Sent: Tuesday, October 22, 2002 8:58 AM To: midrange-l@midrange.com Subject: RE: Problem with OVRDBF Albert, I had a file locking problem earlier once in my batch program and was recommended to use the rclrsc if the earlier call was a rpg or if was a rpgle, to use RCLACTGRP *ELIGIBLE to unlock the file incase the earlier job still had the files open. HTH - Thanks, Sudha -----Original Message----- From: Jim Damato [mailto:jdamato@dollargeneral.com] Sent: Tuesday, October 22, 2002 9:28 AM To: 'midrange-l@midrange.com' Subject: RE: Problem with OVRDBF Just a stab in the dark... Try specifying the member. I wonder if it's successfully allocating the file but not the first member. I wonder if the member itself is depending on the job's default wait time. -Jim -----Original Message----- From: York, Albert [mailto:albert.york@nissan-usa.com] Sent: Friday, October 18, 2002 11:18 AM To: 'MIDRANGE-L@midrange.com' Subject: Problem with OVRDBF I have a batch program that occasionally gets locked out of a file. I have included a portion of the job log below. I tried to change the wait time to 10 minutes, which would allow plenty of time for the other job to finish. However, the job still only waited 120 seconds. Why isn't he OVRDBF working? Albert York 5800 - OVRDBF FILE(IBD) WAITFILE(600) 5900 - CALL PGM(XU2002) /* The CALL command contains parameters */ Lock space location operation not satisfied in specified time interval. Not able to allocate objects needed for file IBD in library FILEA member or program device IBD. Error message CPF4128 appeared during OPEN for file IBD. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.