Re: BATCH FTP question

On 19-Feb-2015 15:16 -0600, Ken Sims wrote:

On Thu, 19 Feb 2015 08:52:13 -0600, CRPence wrote:

<<SNIP>>
The IBM i as FTP client can accept the USER subcommand with the
usrid and pwd coded exactly like shown in the OP; but only because
there is a prior line of INPUT.
<<SNIP>>

I have a command wrapper of my own around IBM's FTP command. I take
the script member and make a modified version such that I log into
localhost (successful or not doesn't really matter) then CLOSE that
connection, then start running the commands from the specified
script.

Perhaps already understood or just of no concern, for the benefit of anyone else that might consider pursuing that path, FWiW:

If the user-id specified on the connection to the localhost is a valid User Profile name from that local system [presumably the value is obtained from a passed-in value], then a login failure could matter; i.e. a failed login attempt gets logged and counted against that user as an invalid sign-on attempt. Even if that effect is not a concern, what appear as legitimately formed credentials to the localhost as IBM i FTP server and for which a failed login is the effect, the server *stalls* the processing for a couple seconds as a means to discourage intrusion attempts; there would seem no reason to code intentionally, a delay in the start of the processing.?

That way the specified script can start with OPEN followed by USER.

FWiW: The original script could be composed with the first line coded as junk, the second line coded with CLOSE, and *then* continue with the OPEN and USER subcommands. The following FTP subcommand script to reach the valid login, which purposely ensures no valid UsrPrf name is provided as the first token on the first line of input [because that first token on the first line of input is presumed by the FTP client to be for login credentials], for example:

*N *N
noop prv line gives TCP11F2 "501 User name not valid..."
close
open <RmtSys>
user <UserID> <Pwd>