× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. June 2015

RE: Urgent: Copying *SAVF to IFS

Thanks for the help folks.

To Mike Bardin's CPYTOSTMF command example, and after using a user-ID specifically authorized to the Windows share (the same user-ID as in the IBM i), we had to add two parameter changes:

DBFCCSID( 37 )
STMFCCSID( 1252)

The job CCSID 65535 will never work, and they have recommended changing the system value QCCSID to use something more conversion-friendly. 1252 is the Windows (default?) CCSID. It's binary, and the contents are not converted, the command and file just has to have one.

Thanks again
Alan




-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Darryl Freinkel
Sent: Wednesday, June 17, 2015 7:52 PM
To: Midrange Systems Technical Discussion
Subject: Re: Urgent: Copying *SAVF to IFS

Create a virtual tape drive. It automatically saves data to the ifs. So you would get it done in 1 step.

I have done this and then copy the files to my secure servers.

Sent from my iPad

On Jun 17, 2015, at 11:23 AM, 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.

--
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.


--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.