|
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. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.