RE: Help with a file allocation problem

["York, Albert" <albert.york@xxxxxxxxxxxxxx>]

I thought about that but why should I need to allocate the object for a CPYF
*ADD? And why does it immediately time out?

Albert

        -----Original Message-----
        From:   Scott Klement [SMTP:klemscot@klements.com]
        Sent:   Thursday, February 21, 2002 8:54 AM
        To:     'MIDRANGE-L@midrange.com'
        Subject:        Re: Help with a file allocation problem


        I generally use a CL program that does something like this:

             1)  call ALCOBJ with a reasonable timeout period to make sure
                     I'll have the necessary access to the file.
             2)  use MONMSG, in case the ALCOBJ fails.   If it fails, I
                     do a WRKOBJLCK with MBR(*ALL) so that the user can see
who is
                     locking the file, then go back to the ALCOBJ.
             3)  Once successfully allocated, do the CPYF
             4)  DLCOBJ so that other people can use the file again.

        This way, you're in control over the allocation situation (as
opposed to
        not finding out about it until the CPYF bombs)


        On Thu, 21 Feb 2002, York, Albert wrote:

        > I am having an intermittent problem copying a file. Below is a
fragment from
        > the job log. As you can see, the job immediately aborts with an
error. This
        > is a batch job. If I run the same job later it runs fine. Does
anyone have
        > any suggestions?
        >
        > Thanks,
        >
        > Albert York
        >
        >         02/20/02   09:44:42   QCADRV         QSYS        01BD
XU0322CL
        > Message . . . . :     6100 - CPYF FROMFILE(QTEMP/UXTXMT)
TOFILE(UXT)
        >      MBROPT(*ADD)
        >  40    02/20/02   09:44:42   QDBSIGEX       QSYS        02B7
XU0322CL
        >    Message . . . . :   Not able to allocate objects needed for
file UXT in
        >      library FILEZ member or program device UXT.

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