Re: IFS support in ACS - 1.6.1.1

All this is true, but we digress - Fred found history log entries that showed that SAV was used on the source machine and RST on the destination machine.

The Getting Started for ACS clearly states that QFileSvr.400 is used in the IFS support - the most likely way it is used is with a SAVF. Confirmation of this either has to come from IBM or from history logs, if those actions are logged there.

I would still like IBM not to use SAV/RST for non-library objects that can be copied or moved using QFileSvr.400. I don't have authority to those - I think it should be OK for me as a developer to have it, at least on the development box, but it isn't that way yet. I can see restricting it on a production LPAR.

Again, I digress - what are the IFS file types that can't be moved or copied using QFileSvr.400? I suppose directories, and maybe remote stuff, such as through NFS mounts or QNTC? And maybe soft links?

Vern

On 12/6/2016 9:33 AM, Rob Berendt wrote:

There's a difference between SAVRST and the API. The API is on all
systems.

Again, QFileSvr.400 may not transfer the authorities, etc.

And, QFileSvr.400 will NOT work for all objects outside of the /QSYS.LIB
file system. There are size limitations, etc. It actually got to be so
limiting that some have stopped using it.


Rob Berendt
-- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com From: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> Date: 12/06/2016 10:27 AM Subject: Re: IFS support in ACS - 1.6.1.1 Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> I'm pretty certain that API is not used - I received a message that I am not authorized to the RST command, so I assume it actually was in use. Fred Keith posted what looks like confirmation of the use of SAV/RST - I then suspect that QFileSvr.400 is in the mix for transferring the SAVF. Fred did not say he saw anything in the log about that. SAVRST would be lovely, except that it might not be on some systems - I know we don't have it installed - no idea why - some kind of history, I guess. Cheers Vern On 12/6/2016 9:14 AM, Rob Berendt wrote:

There is an API used by some saves. In which blocks of data are
processed. One example of it's use is the special command SAVRST. So
they grab a chunk of data, and they do not save it to media or save

files.

They take that chunk and actually start the restore on the target
machine. There are a few benefits to this:
- The save/transfer/restore are all running at the same time in

parallel.

Instead of save, transfer, restore.
- No save file on both the source and target eating up space, even if

only

temporarily.
This API is publicly available.


Rob Berendt

-- 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. Please contact support@xxxxxxxxxxxx for any subscription related questions. Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
-- 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. Please contact support@xxxxxxxxxxxx for any subscription related questions. Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD