× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
I am doing FTP between two iSeries.  They are both running V5R1, cum
TL02071.  When I execute the following:
Enter login ID
xxx
Enter password:
yyy
namefmt 1
250  Now using naming format "1".
Server NAMEFMT is 1.
Client NAMEFMT is 1.
put /rob/spool2.txt /rob/spool2.txt
150 Sending file to /rob/spool2.txt

but mput continues to use the library system
mput /rob/spool2*.txt /rob/*
150 Sending file to member TXT in file SPOOL2 in library QGPL.

This is lousy.  The workaround is to do a
cd /rob
prior to the mput

What is even worse is that:
mput /rob/spool2*.txt /rob/*
actually copied every file in my /rob directory into QGPL:
mput /rob/spool2*.txt /rob/*
250  Now using naming format "1".
257 "/QSYS.LIB/QGPL.LIB" is current library.
150 Sending file to member TXT in file SPOOL2 in library QGPL.
150 Sending file to member TXT in file SPOOL2 in library QGPL.
150 Sending file to member TXT in file SPOOL3 in library QGPL.
150 Sending file to member JPG in file DECOY1 in library QGPL.
150 Sending file to member CSV in file LL855T01 in library QGPL.
150 Sending file to member TEST in file TEST in library QGPL.
150 Sending file to member INI in file NOTES in library QGPL.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.