|
Our partner "dropped" the DDS off in one of their IFS directories for us to retrieve and bring back to our 400...it was NOT in their qsys.lib but rather some random directory/folder.
Do you know the exact command that they used to copy the file?
Once we received the file, our goal was to get the data into one of our 400 libraries (qsys.lib) so we could examine the information accordingly. When we tried a GET from our partners box to a library in OUR Qsys.lib directory, the file transferrred in gobble-de-gook when we did a simple runqry command to view it.
The "gobbledy-gook" is likely some result of EBCDIC to ASCII translation.
And even if it worked, how would the system have "remembered the DDS" file positions...as this file is most definetly not meant to be transferred in a "flat record" format (1 long field).
So how can we retrieve a DDS-field delimited file from a non Qsys.lib IFS directory and restore it on our box and into a standard library within qsys.lib with the DDS definitions in tact?
They create the save file like this:
CRTSAVF FILE(mylib/mysavf) SAVOBJ OBJ(TheFile) LIB(TheLib) DEV(*SAVF) SAVF(mylib/mysavf)
Then they can use FTP to put it into the IFS:
FTP RMTSYS(localhost) <userid & password> ftp> namefmt 1 ftp> cd /ifsdir ftp> binary ftp> get /qsys.lib/mylib.lib/mysavf.file /ifsdir/myfile.savf ftp> quit
Then you can get it from their system via FTP:
FTP RMTSYS(theirsystem) <userid & password> ftp> namefmt 1 ftp> cd /ifsdir ftp> binary ftp> get myfile.savf /qsys.lib/mylib.lib/mysavf.savf ftp> quit
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.