×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I've had jobs fail with the 3029 message in the joblog, reason was BRMS IFS save had the IFS locked.
Our normal IFS save is 10 to 15 minutes, but if an LPAR had a much larger IFS, I could see the lock window being much large with greater chance of app failures due to IFS locks, resulting in 3029.
Paul
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of James H. H. Lampert
Sent: Friday, January 15, 2021 4:59 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: No longer stuck, but more "busy" messages.
The same batch job that I described as being inexplicably "stuck" has resumed processing, but . . .
Both before and after it got stuck, it was attempting to rename IFS objects with the Qp0lRenameKeep system API, and getting error 3029
("EBUSY") every single time. And nobody can explain why it would be getting them now. Earlier, there was a long-running backup job in progress that was the accepted explanation. But that's no longer running, and I'm still getting "busy" every time.
--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
