Re: [Bulk] Urgent: Copying *SAVF to IFS

Alan:

Why not just use the CPY command?

Suppose you have a save file named SAVF in QTEMP, and you want to copy it to the IFS in the "/tmp" directory as "savf.savf" ...

CPY OBJ('QSYS.LIB/QTEMP.LIB/SAVF.FILE') TOOBJ('/tmp/savf.savf')

To copy from that same IFS back to a save file:

CPY OBJ('/tmp/savf.savf') TOOBJ('QSYS.LIB/QTEMP.LIB/SAVF.FILE')

If the save file already exists and you want to replace the contents, use:

CPY OBJ('/tmp/savf.savf') TOOBJ('QSYS.LIB/QTEMP.LIB/SAVF.FILE') REPLACE(*YES)


I find this method is much easier than trying to use CPYTOSTMF and CPYFRMSTMF.

HTH,

Mark S. Waterbury

> On 6/17/2015 11:23 AM, Alan Cassidy wrote:

This is urgent, exec-deadline today to automate this. I'm trying to use CPYTOSTMF to copy save files to the IFS.

I thought this step straightforward. Here's the command (object names changed):

CPYTOSTMF
FROMMBR('/QSYS.LIB/DTALIB.LIB/SAVEFNAME.FILE')
TOSTMF('/BACKUP_TEST')
STMFOPT(*REPLACE)
CVTDTA(*NONE)

The names are double-checked correct. What am I missing?

I'm getting this diagnostic message:

Message ID . . . . . . : CPFA0A2 Severity . . . . . . . : 40
Message type . . . . . : Diagnostic
Date sent . . . . . . : 06/17/15 Time sent . . . . . . : 11:17:53

Message . . . . : Information passed to this operation was not valid.
Cause . . . . . : Possible causes:
--The operation could not use the data passed to it.
--A name may not be correct.
--Directory was expected, but a file was specified.
--File was expected, but a directory was specified.
--The function requested is not supported by the file system.
Recovery . . . : Check the input data to determine the cause of the
problem. Correct the error, and retry the operation.
Technical description . . . . . . . . : If you were attempting an operation
on a user-defined file system (UDFS), the name may have been incorrect
because it was not one of the following:

Thanks to all,
Alan