Re: Moving savf files between machines

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Everyone has ObjectConncect available - it's an option of SS1 and is 
free. This gives you the SAVRST* commands - SAVRSTOBJ can copy any 
object or set of objects to another system - same parameters basically 
as SAVOBJ. Similarly, SAVRSTLIB for libraries.

A SAVF being an object, SAVRSTOBJ could move it nicely.

There are some caveats - maybe dealing with SNADS, but that may be resolved.

Vern

On 2/28/2012 5:06 PM, Musselman, Paul wrote:
> Dang!  That replaces 2 CLP, 2 RPG,&  2 ICF Files that Evoke a QAPPC connection between our systems to create -our- SNDSAVF command!  Of course, our objects were last compiled in 1992, and the source has dates of 1989...
>
> It still works just fine, so we haven't had to search for other ways of making it work!
>
> Paul E Musselman
> PaulMmn@xxxxxxxxxxxxxxxxxxxx
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of McGovern, Sean
> Sent: Tuesday, February 28, 2012 8:27 AM
> To: Midrange Systems Technical Discussion
> Subject: RE: Moving savf files between machines
>
> My userid and password is in sync across all our LPARs. I also have a SAVF named SAVF in my library on all LPARS.
>
> I then create a command on each LPAR that will move the SAVF to different LPARS.
>
> For example...
>
> SNDSAVF LPAR(xxx)
>
> ...the command just...
>
> MD         DIR('/qfilesvr.400/xxx')
>
> CPY      OBJ('/QSYS.LIB/mylib.LIB/SAVF.FILE') TODIR('/QFILESVR.400/xxx/QSYS.LIB/mylib.LIB') FROMCCSID(*OBJ) TOCCSID(*CALC) REPLACE(*YES)