Re: copy from/to qntc

[tim <iseriesstuff@xxxxxxxxx>]

Further update.

I copied the file from the qntc to my ifs and tried the cp command and 
it worked.

So im guessing has something to do in where the copy file coming from.

I will continue to play around and see if i can get it to work.

Any other suggestions based on my new findings would be great.

On 6/5/2015 11:48 AM, Scott Klement wrote:
> Tim,
>
> Are you sure that it's valid to copy data into a save file (savf) 
> using the 'cp' command?
>
> I know that under the covers if I were writing a program to write to a 
> save file, I'd have to use record-based I/O with a particular record 
> length or it would give me an error.  The "cp" command is the Unix 
> copy, which normally would have no concept whatsoever of record-based 
> I/O, as Unix systems don't have record-based files.
>
> This is all speculation, of course, I haven't looked into the 
> internals of the 'cp' command on IBM i...  I'm just guessing that they 
> haven't added special code to account for save files.
>
> Have you considered trying CPYTOSTMF/CPYFRMSTMF instead of 'cp'? That 
> might be an easy solution if I'm right...
>
>
> On 6/5/2015 8:24 AM, tim wrote:
> > we have a backup process that copies data to QNTC as follows:
> >
> > CHGVAR  VAR(&TODIR) VALUE('/qntc/10.0.0.149/iseries/thu/ourlibrary'
> >
> > CLRSAVF QGPL/FTPLIB
> >
> > SAVLIB     LIB(ourlibrary) DEV(*SAVF) SAVF(QGPL/FTPLIB) +
> >                          SAVACT(*SYSDFN) SAVACTWAIT(30 30 30) +
> >                          SAVACTMSGQ(QSYSOPR) ACCPTH(*YES) +
> >                          OMITOBJ((CSFH) (CF)) +
> > OUTPUT(*PRINT)
> >
> > chgvar &c ('cp /qsys.lib/qgpl.lib/ftplib.file' *bcat &TODIR)
> > STRQSH  CMD(&c)
> >
> > now when i try to copy the data back i get following msg:
> >
> > STRQSH CMD('cp /qntc/10.0.0.149/iseries/thu/ourlibrary
> > /qsys.lib/qgpl.lib/ftplib.file')
> >
> > cp: 001-2104 Error found reading from file
> > /qntc/10.0.0.149/iseries/thu/ourlibrary.
> > The value specified for the argument is not correct.
> > Press ENTER to end terminal session.
> >
> > any ideas?