×
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.
Even easier than the job log - it should be an escape message and should
be monitorable - if so, then RCVMSG and get the message data - the
object name and type will be there - oh, and DSPOBJLCK does not exist,
might it be WRKOBJLCK?
There is also an API - QWCLOBJL - that is probably a simple CALL and can
return this information without resorting to reading a spooled file
(always a possibly unreliable solution, as it can change from release to
release). This API returns a list of object locks into a user space -
very workable in CL, albeit much easier in RPGLE and pointers.
HTH
Vern
James F Hawkins wrote:
A CPYF in a nightly batch job has been failing for the last couple of
weeks because the target file is in use.
What can I put in the CLP to see what's locking the object and avoid
coming to work at 2am?
If you know the object,
DSPOBJLCK (lib/obj) OUTPUT(*PRINT)
. You should be able to identify the object by looking in the joblog.
Thank you,
- Jim
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.