RE: savf files

["Jones, John (US)" <John.Jones@xxxxxxxxxx>]

You'll need to 'restore' the objects out of the save file.

Depending on how the objects were saved (SAV, SAVOBJ, SAVLIB, etc.) the
restore command will be different.  Enter RST* or GO RESTORE on the
command line to see all of the restore commands.  

With any of the restore commands except RST, specify a device of *SAVF,
press Enter, and you'll see additional fields to specify the library &
name of the save file.  With RST, you'll set the device to
'/QSYS.LIB/savflibrary.LIB/thesavfile.FILE'

You can see the contents of the savf file by displaying it: DSPSAVF
savflibrary/thesavfile


John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787  F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: dpalme@xxxxxxxxxxx [mailto:dpalme@xxxxxxxxxxx] 
Sent: Wednesday, February 16, 2005 9:22 AM
To: Midrange Systems Technical Discussion
Subject: savf files 

Would someone be kind enough to explain to me how to "un" pack a save
file once it has been transferred to the 400? 

I have never used these and so far searching on the iseries website I'm
finding a lot of gobbily gook as far as information is concerned.
--
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.




This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in future then please respond to the sender to this effect.