On the target system no one created the corresponding SAVF, so the
intended SAVF landed as a PF and there is no way to restore our missing
LIBRARY via RSTLIB.
Is there any way to convert the PF into a SAVF?
Thanks in advance.
Pre-create the *SAVF, and resend the original into the *SAVF, specifying
(REPLACE. If the transfer is huge and slow, you may be able to get away
with doing an ftp transfer from/to localhost.
Sadly, this doesn't seem to be as simple as changing an attribute
someplace.
--
72. If all the heroes are standing together around a strange device and
begin to taunt me, I will pull out a conventional weapon instead of
using my unstoppable superweapon on them.
--Peter Anspach's list of things to do as an Evil Overlord
Try the following (never tried):
* create a save file on the target server
* open an ftp session on the target server and connect to itself (using
localhost)
* move to a binary transfer mode
* try to transfer from the physical to the save file
>
> Thanks in advance.
>
>
--
Cordialement
Marc Rauzier
(pour me r�pondre, ne pas utiliser le from mais le reply-to)
Hi,
you can create the save file during FTP connection if you want :
lcd locallib
cd savelib
quote rcmd crtsavf savelib/ftpsavf
(savf ftpsavf is created into savelib library)
bin
put localsavf ftpsavf
(data of locallib/localsavf are transferred into savelib/ftpsavf)
quote rcmd. rstobj...
(you can restore objects)
best regards,
FF
Avoid that issue by using the NAMEFMT 1 which allows specifying
the type of file to create; i.e. PUT MySavF TheFile.SAVF would
ensure the target of the PUT was a save file. For example:
FTP targetsys
.. login ..
quote site namefmt 1
bin
PUT MYLIB/MYSAVF /QSYS.LIB/QGPL.LIB/TheFile.SAVF
> Is there any way to convert the PF into a SAVF?
>
Any program that can read & write the 528-byte records in binary
more can copy the data from the physical database file into the
save\restore save device file. That includes the FTP subcommands
GET & PUT.
Regards, Chuck
I hope the original poster was also successful.
Bob