Re: Limit to number of objects that can be allocated by a job?

A quick search didn't turn up any reference to a lock limit...

But consider that a save job can have hundreds of thousands of
object locks...

I doubt you'd see an issue. AFAIK, a lock is a lock, doesn't matter what
level.

However, I'd be real curious as to why you need an exclusive lock to
hundreds of objects at once.
That to me seems like a bad idea.

HTH,
Charles

On Fri, Oct 25, 2024 at 1:29 PM Dan Bale <dan.bale@xxxxxxxxxxxxxxxxxxxxx>
wrote:

Google was not my friend.

I'm writing a program that needs to allocate (via ALCOBJ *EXCL) a number
of files. Looking at a scenario where it could need to allocate ~250
files, but it could be more for other scenarios. Is there documentation
available that describes such a limit at the job level?

- Dan

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