Re: SAVRST command fun...

[Jim Oberholtzer <midrangel@xxxxxxxxxx>]

Scott:  I thought that too, but it happens either way.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 12/29/2011 4:04 PM, Scott Klement wrote:
> hi Jim,
>
> This is just a guess, I've never used SAVRST.  But...
>
> Could it be because you're missing the leading slash on /QSYS.LIB?  So
> it's going to use a different file system, depending on what the CWD of
> the job is?
>
> -SK
>
>
> On 12/29/2011 3:46 PM, Jim Oberholtzer wrote:
> > >  I am trying to use the SAVRST command to push IFS objects between
> > >  machines from a program.  The program uses:
> > >
> > >  SAVRST RMTLOCNAME(&RMTSYS)                   +
> > >              OBJ(('/*') ('QSYS.LIB' *OMIT)        +
> > >                         ('/QDLS' *OMIT)           +
> > >                         ('/QFPNWSSTG' *OMIT)      +
> > >                         ('/QNTC' *OMIT))          +
> > >              CHGPERIOD(121911 000000 *ALL *ALL)   +
> > >              SAVACT(*YES)                         +
> > >              SAVACTMSGQ(*NONE)                    +
> > >              OPTION(*ALL)
> > >
> > >  This statement fails when run from a program with CPF382B which says:
> > >      Parameters not valid with multiple file systems.
> > >
> > >  If I run the exact same command from a submit job it works.
> > >  The job log in both cases show the exact same statement after the
> > >  variables have been resolved.
> > >
> > >  Any idea why this would work as a hand submitted job and not work if
> > >  called from a program?
> > >
> > >  V5R4 systems on both ends.  Communications is working well.
> > >
> --