RE: Help with a file allocation problem

Hmmmm. I don't know how someone would get a SHRNUP lock on the file. Unless
the CPYF is also running in another job (which could happen). Perhaps I
should override the file and change the WAITFILE parameter before the copy.

Albert



        -----Original Message-----
        From:   Vernon Hamberg [SMTP:vhamberg@mn.mediaone.net]
        Sent:   Thursday, February 21, 2002 9:36 AM
        To:     midrange-l@midrange.com
        Subject:        Re: Help with a file allocation problem

        If someone has a *SHRNUP on the file (or member), you could not add
to
        it.

        As for timeout, there's a WAITFILE that defaults to *IMMED. WAITRCD
        defaults to 60. Sounds like you're hit by a file lock, not a record
        lock.

        "York, Albert" wrote:
        >
        > I thought about that but why should I need to allocate the object
for a CPYF
        > *ADD? And why does it immediately time out?
        >
        >

        --
        Vern Hamberg

        Would you like to see a challenging little arithmetic puzzle
        that might get you or your kids or grandkids more interested
        in math? Go to <http://cgi.wff-n-proof.com/MSQ-Ind/I-1E.htm>

        Sillygism--

        Something is better than nothing.
        Nothing is better than a ham sandwich.
        Ergo
        Something is better than a ham sandwich.
        _______________________________________________
        This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list
        To post a message email: MIDRANGE-L@midrange.com
        To subscribe, unsubscribe, or change list options,
        visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
        or email: MIDRANGE-L-request@midrange.com
        Before posting, please take a moment to review the archives
        at http://archive.midrange.com/midrange-l.