I have a little utility I wrote using Scott Klement's FTP API to simplify
the FTP process between IBM i boxes. You tell it what object to send, and
where to send it, and the utility takes care of creating save files on the
local and remote side, saving the object, and restoring it on the other
end. This worked great for a while until our system engineers started
messing with authorities, and now no one knows how to set up the
authorities to make it work again. They keep telling me that the only way
to make it work is to give the user *ALLOBJ. I am skeptical about that, but
I don't know what authority is required.
The problem arises when I try to create the save file in QTEMP on the
remote side. I do that using FTP's RCMD sub command. What I am getting is
550 Request rejected.
I can't really find anything in the documentation concerning special
authorities required by the RCMD subcommand. I did find something
recommending that it be restricted using an exit, but we have no exit
programs registered. So I am at a loss. I can create the save file from the
command line, but not from the RCMD command which is supposed to act like a
command line according to this:
- FTP provides remote-command capability, just as advanced
program-to-program communications (APPC) and IBM i Access for Windows do.
The RCMD (Remote Command) FTP-server subcommand is the equivalent of having
a command line on the system. Before you allow FTP, you must ensure that
your object security scheme is adequate. You can also use the FTP exit
program to limit or reject attempts to use the RCMD subcommand. FTP exit
programs describes this exit point and provides sample programs.
Does anyone know of any authority requirements for the RCMD subcommand for
the IBM i FTP server? Or where I can look to find more information?
midrange.com
