× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.