Huh? I tried -password, and got the same results as those who tried -N. As
to -N, looks like the author of the 'jcl' knows ftp on other platforms, and
made an assumption about HP ARPA ftp. No real reason to keep it in there,
unless your audit standards make it too much trouble to change ;-) . Is the
'jcl' working?

On other platforms, -n can be useful. For instance, we use -n on the NT
client side because it does not like to be fed a username to the "User
(HOST:(none)):" prompt in batch, and we are not enthusiastic about
maintaining netrc files on our NT workstations. But this is peculiar to NT
ftp, and another work around is to feed the user prompt a blank line, which
it will accept with an error message Login failed. In either case, we then
have the command file issue "user <username>" and password. We also redirect
output to a file for a quasi-standard list, and use -v to turn verbose off
during log on so the password is not in the log, even though it is in the
batch file.

> -----Original Message-----
> From: Jeff Kell [SMTP:[log in to unmask]]
> Sent: Thursday, October 15, 1998 7:47 PM
> To:   [log in to unmask]
> Subject:      Re: Running FTP
>
> I'm not sure!  There is also "-password" which disallows FTP access to a
> user.account that has no password(s) on the user/group/account.
>
> Jeff Kell <[log in to unmask]>