Altering default FTP server directory

[BiggerJim]

My system disc is a bit small, so I wish to use a second disc to host the default ftp server directory. I've changed the default device for ANONYMOUS using AUTHORIZE, but it appears that the ftp service starts before my mount /system dka100: data command near the top of my SYS$STARTUP:SYSTARTUP_VMS.COM file. So the ftp service doesn't start.

If I run @sys$MANAGER:TCPIP$CONFIG and stop and start the TCPIP services, ftp works OK, but I'd prefer not to have to do this. How do I mount DKA100: before the FTP server tries to start? Or maybe change the FTP server default directory after it starts?

Also, I'd like to set the default directory to dka100:[000000.ANONYMOUS] rather than dka100:[ANONYMOUS]. Is there a way of doing this too?

[support_s]

System recommended content:

1. How to connect to the OSS API of FTP by default

2. How can I set the Guardian API as the default for FTP?

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[BiggerJim]

I'm sorry, I'm a bit of an OpenVMS nuub, but don't see how those links answer my question?

[BiggerJim]

RUN SYS$SYSTEM:AUTHORIZE
UAF> modify anonymous /dev=dka100:
UAF> modify anonymous /dir=[000000.anonymous]

now I just need to find out how to mount a drive before the FTP server starts up.

[Steven Schweda]

> I'm sorry, I'm a bit of an OpenVMS nuub, but don't see how those links
> answer my question?

   "User" support_s is a computer program with minimal actual insight.
You're not the first to notice.

      https://community.hpe.com/t5/x/x/m-p/7164805#M105638

> My system disc [...]

      tcpip show version

> [...] it appears that the ftp service starts before my mount /system
> dka100: data command near the top of my SYS$STARTUP:SYSTARTUP_VMS.COM
> file. [...]

   "appears"?  Actual evidence might be more helpful than your
conclusion.

   My MOUNT stuff happens near the top of my SYSTARTUP_VMS.COM (about
10% in), and my TCPIP happens near its end (about 75% in), so I wouldn't
expect to see this even if my ANONYMOUS directory were off-system-disk.

> Also, I'd like to set the default directory to
> dka100:[000000.ANONYMOUS] rather than dka100:[ANONYMOUS]. [...]

   I'll bite.  Why?

> [...] How do I mount DKA100: before the FTP server tries to start?
> [...]

   Do the MOUNT earlier?  Start the TCPIP stuff later?

   Who mounts the disk where?  Who starts the TCPIP stuff where?

   Look for "mount" in SYS$MANAGER:SYLOGICALS.COM for some (different
but) possibly relevant examples of earlier-than-usual disk mounting.

Configure the FTP service so that it's disabled, and then start it
explicitly at some place in SYSTARTUP_VMS.COM after the MOUNT (and the
TCPIP start)?

   My ANONYMOUS "Default:" is "SYS$SYSDEVICE:[ANONYMOUS]", so I never
have this problem, so I know nothing, but I'd expect any typical TCPIP
start to occur after the MOUNTs.  The only plausible guess I've
generated so far to explain your trouble is that you enabled some
cluster-over-IP option (with which I also have no experience), and that
that causes the TCPIP stuff to get started so early that any MOUNT in
SYSTARTUP_VMS.COM would be too late.  (But what do I know?)

[Volker Halle]

Put your mount commands into SYCONFIG.COM or SYLOGICALS.COM; if you want it executed BEFORE SYSTARTUP_VMS.COM starts.

Also consider using 'MOUNT/SYSTEM/NOASSIST DKA100: label' and make sure a SET NOON is included at the beginning of that procedure, so it won't abort your startup in case of a (fatal) error during MOUNT

Also note that DKA100:[000000.ANONYMOUS] is the same as DKA100:[ANONYMOUS]  - 000000.DIR is the master file directory of your disk, into which all top-level directories are entered. There is no need to prefix a top-level directory with [000000]

Volker.

[Steven Schweda]

> [...] the default ftp server directory. [...]

   Also, it might be better not to think of "the default
device[/directory] for [user] ANONYMOUS" as "the default ftp server
directory".

   The properties of user ANONYMOUS are the properties of user
ANONYMOUS, not those of the FTP server.  The properties of the FTP
server are what you get from, say:

      tcpip show service /full ftp

(which mentions SYS$SYSDEVICE:[TCPIP$FTP], for example), or those of
user TCPIP$FTP.

>    I'll bite. Why?

   Still a mystery.