|
Rob, I am using absolute paths, so maybe the curdir problem is not the problem I don't know for sure that the way I described it is why it happened, but it's the only thing I can think of that could get reset on a signoff/signon. On 10/18/06, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:
Would it be better to use absolute paths versus relative paths? For example, instead of copying to TOSTMF('rob/myfile.txt') use TOSTMF('/home/rob/myfile.txt') and start with the slash? Might want to change the logging level of the job to get more messages. 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 10/18/2006 10:36 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc Subject display current directory level Hey all, A user had a problem today where a CPYTOIMPF command in a CLP failed, I think because the file already existed and the user no authority to replace. I'm assuming this, because of course the job log only showed the CPC2957 - no records copied error. After dumping the program to get the path, and checking, I deleted the existing file and had her try again, and got the same error (CPC2957 - no records copied). I had her log on to another session and key the command manually, and it worked fine. Signing off and relogging on fixed the problem with the initial session, and I can't think of any reason why this would happen, except an educated guess that somehow the session that had the original error left her in the equivalent of WRKLNK '/directory/dir/*' which kept her from copying to '/directory/dir/directory/dir/' - if that makes any sense. my question is, is there any place to look at a job and determine the level of IFS directory it is currently sitting at? or any other ideas why this error caused that session to be unusable for CPYTOIMPF? 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-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.