|
Just tried that and this is what we get now: Object not found. Object is /home/AGCSYSBH/agftpout/F001407415.TMP. Object not copied. Object is /QSYS.lib/AGCFTPOUT.lib/F001407415.file/SND.mbr. -----Oorspronkelijk bericht----- Van: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]Namens Vernon Hamberg Verzonden: vrijdag 11 augustus 2006 14:50 Aan: Midrange Systems Technical Discussion Onderwerp: Re: Rather urgent CPYTOSTMF problem You need to put a forward slash first in your &PATH variable, otherwise it looks in what is the user's current directory. You can look at the user profile to see what that should be - look at the help for explanation of how it works - too long to explain here. Problem here is that there is a directory with his name under /home - that is assumed to be the starting point for relative path names (those without a leading slash). Vern At 07:40 AM 8/11/2006, you wrote:
Hello Chaps and Chapesses We have an urgent problem here, we have to send messages out to clients to inform them when when cargo arrives, this has been working up until recently. The messages actually stopped around the same time we installed WDSC. (I cannot believe that this was the cause, but maybe some of you know better) Anyway the problem we are getting is when we try to do the CPYTOSTMF, the path is set up in the program as follows: CHGVAR VAR(&PATH) VALUE('QSYS.lib/' *TCAT &LIB + *TCAT '.lib/' *TCAT &OBJ *TCAT '.file/' + *TCAT 'SND.mbr') CPYTOSTMF FROMMBR(&PATH) TOSTMF(&FILENAME) + STMFOPT(*REPLACE) STMFCODPAG(*PCASCII) + ENDLINFMT(*FIXED) the program falls over with this: Object not a QSYS.LIB object. Object is /home/AGCSYSBH/QSYS.lib/AGCFTPOUT.lib/F001407322.file/SND.mbr. Object not copied. Object is QSYS.lib/AGCFTPOUT.lib/F001407322.file/SND.mbr. We cannot work out where the /home/AGCSYSBH comes from (AGCSYSBH is the user profile that submits the job, which runs all day waiting for message). Is the message telling us that the file is in the /home etc. directory or that the path is wrong? The messages are deleted so we are not sure where they were if they got there at all. Another problem is that 3rd party software sets up the message to be sent, but this has not changed for ages. TIA Steve -- 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.