Digital Equipment RapidPrint 500, Reference Manual

Page: 37 / 192

Getting Started Maintenance Issues
3 - 9
3.2.7.2.3 Configuring the RapidPrint 500
To configure the RapidPrint 500 to use the commands in the configuration file, use the Source
command. If the configuration file must be downloaded each time the RapidPrint 500 boots, the
filename must be specified using the
Set/Define Server Startupfile command.
The configuration filename is generally of the form “host*filename”, where host can be a TCP/IP,
VMS, or NetWare node name. The asterisk should be replaced with colons or a backslash as fol-
lows: use one colon (:) for a TCP/IP host, two colons (::) for a LAT host, and one backslash (\) for a
NetWare host.
For example, to download the file “config.cmd” from TCP/IP host TROUT at IP address 192.0.1.5,
the following command would be used:
Figure 3-13: Downloading from a TCP/IP Host
Figure 3-14 displays the command needed to download a startup file with the same filename from
NetWare host BASS:
Figure 3-14: Downloading from a NetWare Fileserver
Figure 3-15 displays the command needed to download a startup file with the same filename from
VMS host PIKE:
Figure 3-15: Downloading from a VMS Host
3.2.7.2.4 Download Sequence
If the configuration file cannot be downloaded at boot time, the server’s behavior depends on the
setting of the Retry limit. If the retry limit is zero, the RapidPrint 500 will wait forever until it can
download the file. Otherwise it will try retry times and then continue booting. The command to
specify the file and the number of retry attempts looks like the following:
Figure 3-16: Defining the Startupfile
NOTE: The server is NOT usable while retrying the download.
If the startupfile is not readable, or if there is a problem with the file and the server cannot boot
fully, the server is still accessible via the NCP/TSM and Telnet console ports.
Scripts written for TSM should work unchanged, with the possible exception of privileged mode.
Set Privileged cannot be used in either a Source or Startupfile file, so the command must be
removed from any TSM scripts that are to be used with Startupfile.
Local> DEFINE SERVER STARTUP “192.0.1.5:config.cmd”
Local> DEFINE SERVER STARTUP “BASS\SYS:\LOGIN\config.cmd”
Local> DEFINE SERVER STARTUP “PIKE::config.cmd”
Local> DEFINE SERVER STARTUPFILE “filename” RETRY 10