Re: Urgent: Copying *SAVF to IFS

["Mike Bardin" <mike@xxxxxxxxx>]

Usually I do

CPYTOSTMF FROMMBR('/QSYS.LIB/LIBNAME.LIB/SAVFNAME.FILE')
TOSTMF('/Dir/ifsfilename.savf') STMFOPT(*REPLACE)
CVTDTA(*NONE) ENDLINFMT(*FIXED)

many years without problems


On Wed, 17 Jun 2015 15:23:38 +0000
 Alan Cassidy <ACassidy@xxxxxxxxxxxxxx> 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
>
>
> --------------------------------------------------------------------------------
> Confidentiality Notice: This email may contain confidential 
> information or information covered under the Privacy Act, 5 USC 
> 552(a), and/or the Health Insurance Portability and Accountability 
> Act (PL 104-191) and its various implementing regulations and must be 
> protected in accordance with those provisions. It contains 
> information that is legally privileged, confidential or otherwise 
> protected from use or disclosure.  This e-mail message, including any 
> attachments, is for the sole use of the intended recipient(s). Any 
> unauthorized review, use, disclosure or distribution is prohibited. 
> You, the recipient, are obligated to maintain it in a safe, secure 
> and confidential manner. If you are not the intended recipient, 
> please contact the sender by reply e-mail and destroy all copies of 
> the original message. Thank you.
> --------------------------------------------------------------------------------
> --
> 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.