Re: FTP and long SYSCMD question

[Jim Essinger <dilbernator@xxxxxxxxx>]

Thanks Vern,

What I'm doing is inserting a copy process to the test system at month ends
and once a week on Friday into an existing process.  This will only be in
place until we go live with what is now test, and that will happen at the
end of November.  If I were doing this nightly and it were to stay for a
long time, I would look into changing to a savrst.

If I do a SavRst on the production partition, is there a savf left after the
restore to the test partition that I can move to tape at a later date (like
the next morning)?  That is what we are doing now, and I am just using the
savf that is already there, and copying it over to the test system.

So the existing process -

savlib to a savf
save the savf to a tape next morning.

I added FTP get from the test system once a week on Friday.

Jim

On Fri, Oct 2, 2009 at 12:22 PM, Vern Hamberg <vhamberg@xxxxxxxxxxx> wrote:

> Just an FYI - the SAVRSTxxx commands do everything you are doing, I
> believe. Replace your remote command and SAVLIB with SAVRSTLIB and it's
> all done for you. There is no need for additional software on the remote
> box - just install the ObjectConnect option of the local OS and you are
> good. You will have to set up an AnyNet controller, I think - it's been
> too long and I forget. Maybe on both ends, but not sure of that.
>
> And this doesn't require you to send a remote command - the same trigger
> you use now would fire off the SAVRSTLIB. No FTP scripts with all their
> difficulties, etc.
>
> But I'm probably missing something here.
>
> Glad you got things working, though!
>
> Vern
>
> Jim Essinger wrote:
> > Vern, (and all)
> >
> > Thanks for the ideas.  This job has been designed to be driven from the
> > receiving (test) computer side. When the process on the production system
> > gets to a certain point, it runs a remote command on the test system that
> > starts the FTP get of save files, then starts the conversion. The
> libraries
> > being restored are already saved to a savf as part of the end day
> process,
> > and doing another SAVRSTxxx command would make the process longer. If
> there
> > are commands on the receiving side to do a similar thing ....
> >
> > I fixed my problem by writing a cl program to submit the restore for each
> > library, then called that program passing the library name.
> >
> > Call pgm(MyRestore) parm('LibA')
> >
> > In the CL I used the SELECT - WHEN &LIBRARY = 'LibA'  to check which
> > library, then submitted the restore, and ended the CL program.  The FTP
> > issued the next GET command - rinse - repeat.
> >
> > It gets the job done, but thinking about it now, I might have been able
> to
> > plug the library name into a generic submit restore command.  It would
> > depend on if the restore was submitted with all the same parms, which I
> > don't remember at this point.
> >
> > Jim
> >
> > On Mon, Sep 28, 2009 at 5:33 PM, Vern Hamberg <vhamberg@xxxxxxxxxxx>
> wrote:
> > > Jim
> > >
> > > Have you considered using the ObjectConnect feature of the OS? It is a
> > > free option of the operating system (option 22). It gives you some very
> > > nice commands, like
> > >
> > > SAVRST      QSYS        Save Restore
> > > SAVRSTCFG   QSYS        Save Restore Configuration
> > > SAVRSTCHG   QSYS        Save Restore Changed Objects
> > > SAVRSTDLO   QSYS        Save Restore Doc/Lib Object
> > > SAVRSTLIB   QSYS        Save Restore Library
> > > SAVRSTOBJ   QSYS        Save Restore Object
> > >
> > > I have set up AnyNet to handle the transfers - have not started the
> > > QSNADS subsystem, so I don't think that is needed, at least explicitly.
> > >
> > > The SAVRSTLIB, SAVRSTCHG, and SAVRSTOBJ commands have a way to change
> > > the target library, they bundle up whatever has to be saved into a SAVF
> > > under the covers and restore it on the remote system. At least it looks
> > > that way to me by how it behaves.
> > >
> > > SAVRST does not seem to have a way to modify the directory to restore to
> > > - at least on V5R1.
> > >
> > > It's really very nifty, IMHO. Use it all the time on our network.
> > >
> > > HTH
> > > Vern
> > >
> > > Jim Essinger wrote:
> > >
> > > > Greetings IT GURUs,
> > > >
> > > > Background:
> > > >
> > > > V5R4 on both i5/os machines/partitions.
> > > >
> > > > I have a process that uses FTP to get save files of libraries from one
> i
> > > > partition to another, and I want to submit a restore job after each
> > > library
> > >
> > > > is successfully transferred.  I have "get LibOne (R' to get the save
> file
> > > > and replace the existing file.  I want to do a 'syscmd sbmjob cmd
> rstobj
> > > > obj(*all) savelib(LibOne) dev(*safv) objtype(*file) savf(backup/LibOne)
> > > > mbropt(*all) alwobjdif(*all) job(JobName) jobd(myjobd) jobq(*jobd)
> > > > jobpty(*jobd)' (extra parms added for clarity and to make the command
> > > > longer).
> > > >
> > > > Questions:
> > > >
> > > > If the command is too long for the FTP line, is there a continuation
> > > > indicator like the plus sign (+) in CL source that will recognize the
> > > > following line as part of the command from the previous line?
> > > >
> > > > What is the max length of a record that FTP can process?  The record
> > > length
> > >
> > > > of the current script file is 132.
> > > >
> > > > Is there another way to run a submit job command (other than writing a
> > > > program for each of 50 libraries) to get the submit job command to
> > > process?
> > >
> > > > Thanks!
> > > >
> > > > Jim
> > > --
> > > 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 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.