|
Does this have to do with the long file name? I'd try using the long file name (the real name) instead of the 'forced to 8.3' file name of contra~1.txt. On Wed, 21 Jan 2004 09:52:48 -0800, "Clapham, Paul" <pclapham@xxxxxxxxxxxxx> said: > Try '/qsys.lib/tbarry.lib/contra.file', assuming that CONTRA is a > physical > file in library TBARRY. > > PC2 > > -----Original Message----- > From: Ted Barry [mailto:tbarry@xxxxxxxxxxxxxxxxxxxx] > Sent: January 21, 2004 09:37 > To: midrange-l@xxxxxxxxxxxx; rpg400-l@xxxxxxxxxxxx > Subject: Problem with CPYFRMSTMF Using Pipe(|) Delimited Data > > > CPYFRMSTMF FROMSTMF('/qopt/030502_092250/CONTRA~1.TXT') > TOMBR('/qsys.lib/tbarry.lib/CONTRA') MBROPT(*REPLACE) > > An error occurred while trying to resolve object name. > Stream file not copied. > > Message ID . . . . . . : CPFA0AE Severity . . . . . . . : 40 > Message type . . . . . : Diagnostic > Date sent . . . . . . : 01/21/04 Time sent . . . . . . : > 09:24:21 > > Message . . . . : An error occurred while trying to resolve object > name. > Cause . . . . . : The problem occurred with object > /qsys.lib/tbarry.lib/CONTRA. > Recovery . . . : Check the name to make sure it is correct. See the > job > log (DSPJOBLOG command) or press F10 (Display message job log) for > additional information. > > Any ideas? > _______________________________________________ > 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. > -- michaelr_41@xxxxxxxxxxxxxx -- http://www.fastmail.fm - Accessible with your email software or over the web
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.