RE: Object lock

Sorry, stupid question thanks!

-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Stefan Tageson
Envoyé : mardi 24 février 2009 10:46
À : 'Midrange Systems Technical Discussion'
Objet : RE: Object lock

Wrkobjlck output(*print) ?

Regards



Stefan Tageson

AddconIT AB

Cell : +46 (0) 732 36 99 34

stefan.tageson@xxxxxxxxxxx



-------------------- Internet e-Mail Disclaimer --------------------

This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you are not the intended recipient you are notified that any use, disclosure, copying or distribution of the information is prohibited. In such case, you should destroy this message and kindly notify the sender by reply e-mail.The views expressed in this e-mail and any attachments are personal and, unless stated explicitly, do not represent the views of AddconIT. Furthermore, AddconIT will not be bound by this e-mail.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: Tuesday, February 24, 2009 10:36 AM
To: Midrange Systems Technical Discussion
Subject: Object lock

Hi,

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?

Thanks

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.