RE: Object lock culprits

I had already considered the MONMSG to be my only resort.  Unfortunately
it does not (I don't believe nor does IBM) return control back to the CL
so that I may perform these tasks until after the CPYLIB command
completes.  It takes over an hour for the CPYLIB to complete.

I will, however try *SECLVL since I'm set at LOG(4 00 *NOLIST)...

Thanks.
:-)

-----Original Message-----
From: Joe Giusto [mailto:JGiusto@patuxent.com]
Sent: Friday, January 15, 1999 7:40 AM
To: 'MIDRANGE-L@midrange.com'
Subject: RE: Object lock culprits


You should be able to MONMSG on the CPYLIB command.  If error, loop
thorough
RCVMSG and look for the ones that say the object is locked.  Then to the
WRKOBJLCK. 

Also, you may be able to set job logging to (4 00 *SECLVL) and view the
job
log after it fails, it should tell you what job locked the objects.  I
am
not sure if this is done for all commands but I know I have seen it
sometimes.


Joe Giusto II
Patuxent Publishing Company
 <mailto:jgiusto@patuxent.com> mailto:JGiusto@patuxent.com
http://www.lifegoeson.com <http://lifegoeson.com> 


        -----Original Message-----
        From:   Don [SMTP:dr2@cssas400.com]
        Sent:   Thursday, January 14, 1999 6:49 PM
        To:     Roger Boucher
        Cc:     MIDRANGE-L@midrange.com
        Subject:        Re: Object lock culprits



        From a cpylib I'm at a loss...but from a crtdupobj you can
monmsg
then
        wrkobjlck...but I'm not sure how to rtv the lst of obj's that
don't
make
        the cpylib....but it would stand to reason that it's in SOME
usrspc
        somewhere and a quickie MI routine should bring them to
light....
Bruce?

        Don in DC

        On Thu, 14 Jan 1999, Roger Boucher wrote:

        > I am running a CPYLIB and the last few nights I have found
that
there
        > have been some object locks which are preventing some of my
data
files
        > from copying.  This is a process that has been in place for
awhile
        > without any such problems and there are no users on the system
(QINTER
        > is ended).  I am trying to find a way to determine what is
locking
these
        > files AT THE TIME THEY ARE BEING LOCKED.  I think I already
know
the
        > answer... tough bananas... but anyone have any ideas?
        > 
        > Thank you for your consideration.
        > +---
        > | This is the Midrange System Mailing List!
        > | To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
        > | To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
        > | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
        > | Questions should be directed to the list owner/operator:
david@midrange.com
        > +---
        > 

        +---
        | This is the Midrange System Mailing List!
        | To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
        | To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
        | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
        | Questions should be directed to the list owner/operator:
david@midrange.com
        +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---