Re: Error on CPYFRMIMPF

Thanks again Rob.

it's not my box, but a client's.  they don't use the IFS much, if at
all, so there's not going to be a big priority to fix the problem
immediately, but this will help me point out the problem.

Rick

On 1/5/06, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:
> The peach was even after I ended the offending job with ENDJOBABN, because
> I ended the job with ENDJOBABN it did not release it's locks.  Only the
> IPL did.
>
> To find the offending job I'd suggest the following:
> iSeries Navigator
>  File Systems
>   Integrated File System
>    Root
>     Find the file.
>      Right click on it and select properties
>       Use tab
>        If it's in use, it will tell you.  Then you can click the button to
> find out where.
>
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> rick baird <rick.baird@xxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 01/05/2006 08:30 AM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> cc
>
> Fax to
>
> Subject
> Re: Error on CPYFRMIMPF
>
>
>
>
>
>
> Thanks Rob.
>
> Any idea how I can find the offending job?  is there a wrkobjlck
> equivelent for the ifs?
>
> On 1/5/06, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:
> > Yes I have seen that on V5R3.  I had an IFS save that was locked.  I
> then
> > did an ENDJOBABN of that IFS save.  Thus all those critters were left
> > locked.  Started noticing the messages in various jobs that accessed the
> > IFS.  I had to IPL to resolve the issue.  Production lpar in 570.
> > Unscheduled downtime.  Getting more Windows compatible every day...
> >
> >     Aug-23-2005
> > pmr 39344,500
> >
> > Rob Berendt
> > --
> > Group Dekko Services, LLC
> > Dept 01.073
> > PO Box 2000
> > Dock 108
> > 6928N 400E
> > Kendallville, IN 46755
> > http://www.dekko.com
> >
> >
> >
> >
> >
> > rick baird <rick.baird@xxxxxxxxx>
> > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > 01/04/2006 05:16 PM
> > Please respond to
> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> >
> >
> > To
> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > cc
> >
> > Fax to
> >
> > Subject
> > Error on CPYFRMIMPF
> >
> >
> >
> >
> >
> >
> > Hey all,   has anyone else seen this?
> >
> > Got an error trying to copy a .csv from the IFS into a physical file.
> > details below:
> >
> > CPFA0D4 -  File system error occurred.  Error number 3029.
> > ...
> >   - Use DSPMSGD CPExxxx, where xxxx is the error number to display an
> > error
> > message containing more information about this error number.
> >
> > so, I looked up CPE3029:
> >
> > CPE3029 - Resource busy.
> > Cause . . . . . :   An attempt was made to use a system resource that is
> > not
> >   available at this time.
> > Recovery  . . . :   Wait for the resource to become available and try
> your
> >   request again. See any previous messages in the job log for
> information
> >   about making the resource available.
> >
> > Nothing else in the job log you wouldn't normally see in a CPYFRMIMPF.
> >
> > did a WRKLNK and the file is where I expect it to be.
> >
> > any ideas?  I don't know if CPYFRMIMPF has ever been tried on this box
> > since it was upgraded to V5R3.
> >
> > Thanks,
> >
> > Rick
> >
> > --
> > 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.
> >
> >
> > --
> > 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.
> >
> >
>
> --
> 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.
>
>
> --
> 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.
>
>