Re: Speed of objects unlocking and subsequent CLRLIB failing

On Mar 29, 2025, at 8:29 AM, Jim Franz <franz9000@xxxxxxxxx> wrote:

Dan,

What was running prior to the CLRLIB? Something was taking its time
finishing, releasing locks. I doubt (without really knowing) this is
because it's QTEMP...but have had multiple instances of other operations
still completing but the program has moved to the next step.
You could monmsg the clrlib and retry (after 1 second delay). What pieces
of a various commands, especially releasing resources, are asynch we don't
really know.,,
Most of my issues involved spooling resources using non-IBM spool
conversion software, and ifs files (from ftp, sftp), and use something like
retry up to 5 times with dlyjob(1) between each retry. Don't make the retry
infinite times - don't want to hang your own job.
In the above 2 cases I had to adjust the code across the system...
especially if processing many files in a loop.
Jim Franz

On Fri, Mar 28, 2025 at 10:38 PM Dan Bale <dan.bale@xxxxxxxxxxxxxxxxxxxxx>
wrote:

Had a weird issue today. A production batch job failed because CLRLIB
QTEMP was unable to delete one or more objects: CPF2161 "Cannot delete
some objects in library QTEMP." Prior to that message, that CLRLIB command
had deleted 66 objects, as confirmed by CPC2191 "Object <xxxxxxxxxx> in
QTEMP type <*zzzz> deleted." We don't know how many objects were not able
to be deleted. (The CLRLIB is done because the job continues other tasks
for which new objects are created in QTEMP.)

We don't think it was an authority issue because the job's user profile
(RBTSERVE) has *ALLOBJ authority.

We inserted a DSPLIB QTEMP *PRINT and DSPOBJD QTEMP/*ALL *FULL *PRINT just
prior to the CLRLIB QTEMP so that we could see what objects were not being
deleted. When we reran the job again, CLRLIB QTEMP worked without error
and the job completed normally.

So, what's left? One train of thought was that, since the CLRLIB QTEMP
worked after inserting the DSPLIB and DSPOBJD commands, perhaps adding
those two commands provided the operating system just enough milliseconds
to complete the process of "unlocking" the objects in QTEMP before the
CLRLIB QTEMP was executed. Someone suggested adding a DLYJOB DLY(10) just
prior to CLRLIB QTEMP as a potential solution.

Has anyone encountered this scenario before?

- Dan Bale
*** CONFIDENTIALITY NOTICE: The information contained in this
communication may be confidential, and is intended only for the use of the
recipients named above. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution, or
copying of this communication, or any of its contents, is strictly
prohibited. If you have received this communication in error, please return
it to the sender immediately and delete the original message and any copy
of it from your computer system. If you have any questions concerning this
message, please contact the sender. ***
--
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.

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