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



The batch job was trying CLRPFM, but it failed because the object was
locked. I was using WRKOBJLCK via 5250 to idenify the job(s) holding the
lock, but WRKOBJLCK also failed due to a lock. Normally WRKOBJLCK shows
the lock holder(s) without difficulty.

OBJECT_LOCK_INFO would be the thing to try, but it might use the system
calls under the covers as WRKOBJLCK.

Thanks


date: Thu, 13 Jan 2022 14:35:44 +0000
from: Rob Berendt <rob@xxxxxxxxx>
subject: RE: WRKOBJLCK locked?

I hate when people do this to me so I request your forgiveness in advance
by asking you if there was something in the joblog which confirms that the
error was truly due to the command WRKOBJLCK being locked.

See also:
https://www.ibm.com/docs/en/i/7.4?topic=services-object-lock-info-view
or

https://www.ibm.com/docs/en/i/7.4?topic=services-job-lock-info-table-function


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.