This chapter lists the MultiNet logicals in alphabetical order.
|
FILTER_SERVER_CONFIG
If set, overrides the MULTINET:FILTER_SERVER_CONFIG.TXT filename for the configuration file for the IPS FILTER_SERVER process. |
|
|
KEYBD
Tests the individual TN3270 mapping statements for a specified keyboard type. Keyboard types are specified in the MAP3270.DAT file. The MAP3270 logical name specifies the name for this file. |
|
|
MAP3270
Specifies the name of the TN3270 key mapping file. The default is MULTINET:MAP3270.DAT. |
|
|
MULTINET
The top-level MultiNet directory. Defined in START_MULTINET.COM. This logical name should not be modified. |
|
|
MULTINET_ANONYMOUS_FTP_CONTROL
Set to "-" to permit use of the FTP PUT command into an ANONYMOUS account. Set by system manager. |
|
|
MULTINET_ANONYMOUS_FTP_DIRECTORY
Indicates the anonymous FTP directory. Defined in START_MULTINET.COM and set by system manager with the command:
NET-CONFIG>SET ANONYMOUS-FTP-DIRECTORY |
|
|
MULTINET_ANONYMOUS_PASSWORD
Specifies the password for the anonymous FTP account by a remote user. Defined in FTP_SERVER.COM by the command:
$ MULTINET FTP /SERVER /GET_REMOTE_INFO |
|
|
MULTINET_ANONYMOUS_USERNAMES
This logical will allow users to use names which are not anonymous, but have the same anonymous account behavior. The MULTINET_ANONYMOUS_USERNAMES logical usage is shown in the following example:
$ DEFINE /SYSTEM /EXEC MULTINET_ANONYMOUS_USERNAMES _$ “anonymous,user1,user2,..."
If you define this logical as shown in the preceding example and set the “user1,user2,...” accounts using the same password as the anonymous account, then the FTP server will treat “user1,user2,...” as an anonymous type of user. |
|
|
MULTINET_CLUSTER_SERVICE_CPU_RATING
Enables cluster service CPU rating. Set by system manager. |
|
|
MULTINET_CLUSTER_SERVICE_NAMES
Defines the cluster service name list used for DNS load balancing. Defined in START_MULTINET.COM and set by system manager with the command:
NET-CONFIG>SET CLUSTER-SERVICE-NAMES
|
|
|
MULTINET_CLUSTER_SERVICE_STATIC_RATING
Enables cluster service static rating. Set by system manager. |
|
|
MULTINET_COMMON_ROOT
Defines the MultiNet cluster common rooted directory. Defined in START_MULTINET.COM. This logical should not be modified. |
|
|
MULTINET_DISABLE_SPAWN
Disables the ability to use SPAWN, ATTACH, or PUSH in all MultiNet applications. Set by user or system manager. |
|
|
MULTINET_DIRECTORY_MESSAGE_FILENAME
Defines the name of the file you want displayed when a session enters a directory. For example:
$ DEFINE/SYSTEM/EXECUTIVE MULTINET_DIRECTORY_MESSAGE_FILENAME example.txt
|
|
|
MULTINET_FILTER_SERVER_TQELM
Defines the TQELM quota for the FILTER_SERVER process for IPS. |
|
|
MULTINET_FILTER_SERVER_ASTLM
Defines the ASTLM quota for the FILTER_SERVER process for IPS |
|
|
MULTINET_FILTER_SERVER_MBX_MSGS
Defines the maximum number of messages (e.g., events being logged by instrumented processes) the FILTER_SERVER mailbox can hold. This is set to 400 by default. If set too small, processes may enter MUTEX and/or RWMBX state. |
|
|
MULTINET_FILTER_SERVER_QUOTA_CHECK
If set, the FILTER_SERVER process for IPS will periodically check its TQELM and ASTLM quotas to see if they are in danger of running out (90% or more consumed). |
|
|
MULTINET_FILTER_SERVER_QUOTA_CHECK_TIME
If MULTINET_FILTER_SERVER_QUOTA _CHECK is defined, this defines the time, in seconds, between quota checks. The default is 15 minutes if this logical is not defined. |
|
|
MULTINET_FTP_221_REPLY
Defines a message to appear when a user ends the FTP session. If you do not define this logical, MultiNet uses the default message instead. You can define a text string or file. For example:
$ DEFINE/SYSTEM/EXECUTIVE MULTINET_FTP_221_REPLY -
When the user closes the FTP connection, this message appears:
221 Connection to FTP server has been closed |
|
|
MULTINET_FTP_230_REPLY
Defines a message to appear when a user successfully logs in. If you do not define this logical, MultiNet uses the default message instead. As with MULTINET_FTP_221_REPLY, you can define a text string or file. For example:
$ DEFINE/SYSTEM/EXEC MULTINET_FTP_230_REPLY "Login successful"
Now, when the user logs in using FTP, the following message appears:
230 Login successful |
|
|
MULTINET_FTP_421_REPLY
Defines a message sent when a user connects to the server but should not log in. After sending the message, the connection closes. For example, define this logical to prevent FTP access for a short time period. Be sure to de-assign the logical after this period to allow FTP access again. You can define a text string or file. For example:
$ DEFINE/SYSTEM/EXECUTIVE MULTINET_FTP_421_REPLY -
When the user connects to the host through FTP, this message appears and then the connection closes:
421 System maintenance in progress until 17:30 |
|
|
MULTINET_FTP_ACCOUNTING_HOST
The name of the IP address of the system running the accounting program. |
|
|
MULTINET_FTP_ACCOUNTING_PORT
The port number that the program was set up to listen on. |
|
|
MULTINET_FTP_ADDRESS
Set by the FTP server to the remote user's IP address. Defined in FTP_SERVER.COM by the command:
$ MULTINET FTP /SERVER /GET_REMOTE_INFO
|
|
|
MULTINET_FTP_ALL_VERSIONS
Requests the NLST and LIST commands to display all version numbers. If this logical is defined, the logical name MULTINET_FTP_STRIP_VERSION has no effect.
MULTINET_FTP_ALL_VERSIONS is ignored if the FTP server is in UNIX emulation mode. |
|
|
MULTINET_FTP_ANNOUNCE
Provides a SYS$ANNOUNCE-style message along with the "220" banner at connect time. Define this logical name in a fashion similar to SYS$ANNOUNCE, using one of these commands:
$ DEFINE /SYSTEM MULTINET_FTP_ANNOUNCE "message_text"
In the following version, the announcement is in the specified file:
$ DEFINE /SYSTEM MULTINET_FTP_ANNOUNCE "@file_spec" |
|
|
MULTINET_FTP_ANONYMOUS_230_REPLY
Defines a message to appear when an ANONYMOUS user successfully logs in. If you do not define this logical, MultiNet uses the default message instead. As with MULTINET_FTP_230_REPLY, you can define a text string or file. For example:
$ DEFINE/SYSTEM/EXEC MULTINET_FTP_ANONYMOUS_230_REPLY -
Now, when a user logs in using the ANONYMOUS account, the following message appears:
230 ANONYMOUS login successful |
|
|
MULTINET_FTP_DELAY_TRANSFER_NEGOTIATION
The FTP client does not attempt to negotiate STRU O VMS transfer mode until after you have logged into the remote system successfully. |
|
|
MULTINET_FTP_DISALLOW_UNIX_STYLE
Controls whether UNIX-style filename parsing is done. The default value for MULTINET_FTP_DISALLOW_UNIX_STYLE is true (T), UNIX-style filename parsing is not handled. If you want UNIX-style filename parsing, you must define this logical as FALSE. When UNIX-style parsing is enabled, it is not normally done until a CD command has been done with a directory specification that contains a “/” in it. For example:
FTP> cd ../my_directory
For some FTP clients (MultiNet is one of them) you will have to enclose the directory specification in quotes (“”) when it contains the “/” to prevent the client from attempting to parse it.
To exit UNIX-type filename parsing, use a CD command with either the “[” or “<” character in the directory specification. For example:
FTP> cd [-.my_directory] $ DEFINE/SYSTEM/NOLOG/EXEC MULTINET_FTP_DISALLOW_UNIX_STYLE FALSE
Some graphical display FTP clients expect the output of directory commands to be in a UNIX system format. To enable this UNIX format, use the following either at the system level or in the user's LOGIN.COM:
$ DEFINE MULTINET_FTP_DISALLOW_UNIX_STYLE FALSE
and
$ DEFINE MULTINET_FTP_UNIX_STYLE_BY_DEFAULT ANYTHING
|
|
|
MULTINET_FTP_DISALLOW_WILDCARD_DELETES
Disallows the new functionality of accepting wildcards on delete. This may be done at the process, group, or system level. |
|
|
MULTINET_FTP_DODROP1DOT
Overrides an FTP default of renaming files by changing the final dot (.) to $5N. This logical drops the final dot and does NOT add $5N. |
|
|
MULTINET_FTP_DONT_REPORT_FILESIZE
When this logical is defined, the estimate of the number of bytes to be transmitted is not included in the 150 reply line to a GET operation. |
|
|
MULTINET_FTP_FAST_TIMEOUT
This logical is equivalent to setting the logicals MULTINET_NAMESERVER_RETRANS and MULTINET_NAMESERVER_RETRY for the FTP server process to 5 and 2 respectively. This helps the FTP server start up faster when DNS PTR records for the client are defined improperly or do not exist. |
|
|
MULTINET_FTP_HOSTNAME
Set by the FTP server to remote user's hostname. Defined in FTP_SERVER.COM by the command:
$ MULTINET FTP /SERVER /GET_REMOTE_INFO
|
|
|
MULTINET_FTP_LOCAL_ADDRESS
Set by the FTP server to remote user's local address. Defined in FTP_SERVER.COM by the command:
$ MULTINET FTP /SERVER /GET_REMOTE_INFO
|
|
|
MULTINET_FTP_LOG_ALL_USERS
Logs commands and responses for all users. |
|
|
MULTINET_FTP_LOGFILE
Specifies the name of a log file. This is good if you suspect break-ins to the FTP server. For example:
$ DEFINE/SYSTEM/EXECUTIVE MULTINET_FTP_LOGFILE -
If this logical exists, the FTP server writes a record to the specified file each time a user attempts to log in. Each record includes the date and time, the remote host's internet address, and whether the login succeeded. |
|
|
MULTINET_FTP_LOWERCASE_MPUT
The logical MULTINET_FTP_LOWERCASE_MPUT can be set to True, Yes or 1 (the number one) to cause filenames from an MPUT command to be converted to lowercase. Setting this logical to True preserves behavior in prior versions of MultiNet. The new behavior (retaining the case of filenames) provides better functionality for ODS-5 disks with case sensitive file naming on VMS V7.3-1 and later. |
|
|
MULTINET_FTP_LOWERCASE_NLST
The logical MULTINET_FTP_LOWERCASE_NLST can be set to True, Yes or 1 (the number one) to cause the filenames presented as a result of the NLST command to be converted to lowercase when not operating in UNIX mode. Setting this logical to True preserves behavior in prior versions of MultiNet. The new behavior (retaining the case of file names) provides better functionality for ODS-5 disks with case sensitive file naming on VMS V7.3-1 and later. |
|
|
MULTINET_FTP_MAXIMUM_IDLE_TIME
Defines the length of time before an idle FTP server connection times out. The value is set in seconds (default: 300 seconds). If set to 0 (zero), timeouts are disabled. Set by system manager. |
|
|
MULTINET_FTP_MAX_PRE_ALLOCATION
This logical limits the size that the file will be pre-allocated to when file size information is available at transfer time. This can be important when transferring very large files as it can take a long time to pre-allocate the file at the start of the transfer and timeout routines in FTP and/or firewalls may cause connections to be dropped. This logical does not have any effect for STRU OVMS transfers of Indexed, Contiguous, or Contiguous Best Try files; these files need to have accurate allocation size information at the start of the transfer. |
|
|
MULTINET_FTP_MAXREC
The FTP client and the FTP server normally check the record size of an ASCII transfer and disallow more than 8192 byte records (as a sanity check). However, you can define the MULTINET_FTP_MAXREC logical to override the default of 8192. The definition of the MULTINET_FTP_MAXREC logical is commented out but defined in the FTP_CONTROL.COM file as follows:
$ DEFINE/SYSTEM/NOLOG/EXEC MULTINET_FTP_MAXREC 8192
Note that the maximum record size supported by OpenVMS is 65535. |
|
|
MULTINET_FTP_NO_PASV_SECURITY
Defining this logical to True, Yes or 1 (the number one) will disable security checks by the FTP server when performing passive transfers. The security check is to verify that the IP address of the system that connects to the data port is the same as the system that is connected to the command port. |
|
|
MULTINET_FTP_NONPASV
If the MULTINET_FTP_NONPASV logical name is defined, then the FTP client will start-up in PASSIVE OFF mode. The default client behavior is PASSIVE ON. |
|
|
MULTINET_FTP_OBSERVE_VMS_PROTECTION
Causes RENAME to observe the file protection. |
|
|
MULTINET_FTP_ONLY_BREAK_ON_CRLF
If this logical is defined and an ASCII file is transferred, a new line is created in the file upon receipt of a carriage return/line feed sequence. If this logical is not defined and an ASCII file is transferred, a new line is created in the file upon receipt of either a carriage return/line feed sequence or a line feed. The logical is not defined by default. |
|
|
MULTINET_FTP_PASSWORD_WARNING_MESSAGE
Defines the message users see when their password is going to expire. |
|
|
MULTINET_FTP_PASSWORD_WARNING_TIME
Uses the VMS delta time to specify the minimum remaining lifetime for the user's password. |
|
|
MULTINET_FTP_RECEIVE_THRESHOLD
Specifies the amount of buffer space that can be used to buffer transmitted data on the data socket. The default value if 6144. If this logical is defined and it begins with a /, then it specifies the fraction of the window size. If only a fraction is specified, then it indicates the number of bytes to be used. The ? in the logical represents where defined values go.
$ DEFINE/SYSTEM/EXECUTIVE MULTINET_FTP_RECEIVE_THRESHOLD ?
|
|
|
MULTINET_FTP_SEMANTICS_FIXED_IGNORE_CC
When this logical is defined to TRUE, then GET operations of fixed length records file will not have a CR>LF> added to the end of each record. |
|
|
MULTINET_FTP_SEMANTICS_VARIABLE_IGNORE_CC
When this logical is defined to TRUE, files with variable length records and carriage return carriage control will NOT have a new line character inserted after each line when the file is transferred in image mode. The logical is not defined by default. |
|
|
MULTINET_FTP_STOU_OLDNAME
This logical causes the STOU command to use the old file name instead of creating a new one. Following is an example of this logical name usage:
$ DEFINE/SYS/EXE MULTINET_FTP_STOU_OLDNAME "ANYTHING"
|
|
|
MULTINET_FTP_SERVER_LOG_LIMIT
Specifies that log files be retained. Set this logical to a dash (-) to retain all log files, or specify a number in the range of 1 to 32000.
Directory size restrictions limit the number of potential files that can actually be created. If you do not specify a number or value, one log file is created or over-written for each FTP session. Use the DCL PURGE command to delete unneeded log files. The following example specifies that 42 log files be retained:
$ DEFINE MULTINET_FTP_SERVER_LOG_LIMIT 42
|
|
|
MULTINET_FTP_SERVER_RELAXED_PORT_COMMAND
By default the MultiNet FTP server checks the IP address given in the port command and does not make the connection if the IP address does not match that of the control connection. This can be disabled by defining this logical. |
|
|
MULTINET_FTP_SIZE_BEFORE_GET
If this logical is defined to FALSE, NO, or 0 (zero) the SIZE command will not be sent before the GET command for a file. When the logical is not defined, or is defined to a value other than FALSE, NO, or 0, the SIZE command is sent. If a value is returned, it is used to preallocate the file and in progress calculations. Some FTP servers leave the file open accidentally after the SIZE command. |
|
|
MULTINET_FTP_STATISTICS_IN_HHMMSS
Turns on, off, or toggles (the default) STATISTICS mode. In STATISTICS mode, FTP displays timing statistics about the transfer upon completion. If this logical is defined with either 1, T, or Y, then the elapsed time displays in HH:MM:SS format if statistics are requested using the STATISTICS mode. |
|
|
MULTINET_FTP_STRIP_VERSION
If the FTP server is in UNIX mode, the SYST command displays the banner “UNIX MultiNet Unix Emulation.” If the FTP server is in VMS mode, the SYST command displays the equivalence string associated with the MULTINET_FTP_SYST_BANNER logical name (if defined). Otherwise, the SYST command displays “VMS MultiNet Vx.y(rev),”:
Vx.y is the MultiNet version number.
(rev) is the revision number of the FTP server.
This logical is ignored if the FTP server is already in UNIX mode. |
|
|
MULTINET_FTP_SYST_BANNER
Specifies the value to be sent in response to a SYST command seeking the FTP server operating system. The default response is VMS Multinet FTP Server Version, but you can specify your own response by defining this logical name to have your response text as its equivalence string. |
|
|
MULTINET_FTP_UNIX_STRIP_VERSION
Instructs the FTP server to strip the file version numbers from its UNIX-style listings. Set this logical to TRUE in the system logical name table (if you want it defined system-wide), or in individual users' LOGIN.COM files. |
|
|
MULTINET_FTP_UNIX_STYLE_BY_DEFAULT
Instructs the FTP server to emit UNIX-style listings by default. Otherwise, the server bases its decision to emit UNIX-style listings on the commands it receives from the client. |
|
|
MULTINET_FTP_UNIX_STYLE_CASE_INSENSITIVE
Allows UNIX style filename handling to be case insensitive. |
|
|
MULTINET_FTP_UNIX_YEAR_OLD_FILES
Displays the creation month, day, and year of a file for a UNIX mode directory if the file is older than 1 year (365 days). You can define the logical at the system level to affect how all users on the system see the file's date, or in the user's login.com file if only some users define this format. |
|
|
MULTINET_FTP_USE_SRI_ENCODING_ON_ODS5
This logical
allows use of SRI encoding of UNIX-style file names on ODS-5 disks. When this
logical is defined to 1, TRUE
or YES, the SRI file name encoding used for
UNIX-style file names on
MULTINET_FTP_UNIX_STYLE_BY_DEFAULT TRUE MULTINET_FTP_UNIX_STYLE_CASE_INSENSITIVE FALSE MULTINET_FTP_USE_SRI_ENCODING_ON_ODS5 TRUE |
|
|
MULTINET_FTP_WINDOW_SIZE
Allows you to change the default window size in the same manner as the /WINDOW_SIZE qualifier. |
|
|
MULTINET_FTP_VAM_AUTH_METHOD
This logical specifies the authentication method to use with Process Software’s VMS Authentication Module. If the user does not have the VAM_LGI_method rights identifier, then traditional password authentication is used. The user needs to have the FTP rights identifier for VAM to authorize them. The UCXQIO service should be defined as an auxiliary service when this is used to avoid a dead lock condition.
$ DEFINE/SYSTEM/EXECUTIVE MULTINET_FTP_VAM_AUTH_METHOD LDAP
|
|
|
MULTINET_FTP_VAM_REQUIRED
If this logical is defined, then traditional password authentication is not allowed for users that do not have the VAM method specified by MULTINET_FTP_VAM_AUTH_METHOD.
$ DEFINE/SYSTEM/EXECUTIVE MULTINET_FTP_VAM_REQUIRED TRUE
|
|
|
MULTINET_HOST_ALIASES
Specifies the host alias table file. Each line has the form: alias hostname. Set by user or system manager. |
|
|
MULTINET_HOST_NAME
The official host name of the local system. Defined in START_MULTINET.COM and set by system manager with the command:
NET-CONFIG>SET HOST-NAME
|
|
|
MULTINET_IMAP_UPDATE_LOGIN_TIME
Updates the last non-interactive login field in SYSUAF for each IMAP login. |
|
|
MULTINET_IMAPD_LOGLEVEL
Enables additional logging for debugging purposes. Output is written to the file MULTINET:IMAP_SERVER.LOG. By default, this logical is unassigned. IMAP events normally are logged to SYSLOG.
$ MULTINET_IMAPD_LOGLEVEL=0
|
|
|
MULTINET_IMAPD_MESSAGE_ONE
By default, an informing message of This message cannot be retrieved is sent to the user when the processing message is too big. |
|
|
MULTINET_IMAPD_MESSAGE_SIZE_LIMIT
This logical limits the size of the mail that IMAP processes. |
|
|
MULTINET_IP_CLUSTER_ALIASES
The cluster failover IP address list. Defined in START_MULTINET.COM and set by system manager with the command:
NET-CONFIG>SET IP-CLUSTER-ALIASES
|
|
|
MULTINET_IPP_CONFIG
Specifies one or more of the qualifiers described in the Chapter 16 of the MultiNet for OpenVMS Administrator’s Guide. These qualifiers are not case sensitive. Underscores (_) in the qualifier names are optional. Each may be abbreviated as long as the result is not ambiguous. There is no default. This logical provides defaults that may be overridden by the queue-specific configuration logical, MULTINET_IPP_queuename_CONFIG, for a given queue. |
|
|
MULTINET_IPP_DEFAULT_DOCUMENT_FORMAT
Specifies a string to use as the document format, unless specified differently for a given queue or print job. The actual document format used on a given job must be a valid MIME media type, supported by the printer to which the job is sent. The default is "text/plain". |
|
|
MULTINET_IPP_IGNORE_DESCRIPTION
If this logical is defined, the symbiont ignores the /DESCRIPTION strings for all IPP queues. This allows use of /DESCRIPTION for other information without affecting the symbiont. Configuration of the symbiont must be done through use of the MULTINET_IPP_CONFIG logical, or the queue-specific logical, MULTINET_IPP_queuename_CONFIG if MULTINET_IPP_IGNORE_DESCRIPTION is defined. The value of the equivalence string for MULTINET_IPP_IGNORE_DESCRIPTION is not important. The existence or non-existence of the logical is all that is checked. This logical provides defaults that may be overridden by the queue-specific configuration logical, MULTINET_IPP_queuename_IGNORE_DESCRIPTION, for a given queue. |
|
|
MULTINET_IPP_JOB_RETRY_DELAY
Specifies, as an OpenVMS delta time specification, the length of time to hold a job when it is re-queued due to a temporary problem. The default value is "0 00:10:00.00" (10 minutes). |
|
|
MULTINET_IPP_MAX_LOG_BYTES
Specifies how many bytes of data will be logged by the send and receive routines when running with logging level set to DETAILED_TRACE. The value is an integer. A negative value sets the limit to infinite (all data will be logged). A value of zero turns off inclusion of data to the log file. A positive value sets the actual number of bytes logged, and any additional data is ignored. The default action is to log all data. |
|
|
MULTINET_IPP_MAX_STREAMS
Specifies the number of streams (queues) that each IPP symbiont process can handle. This is an integer from 1 to 16. The default is 16. |
|
|
MULTINET_IPP_LOG_LEVEL
Specifies one of the logging level values, and is used to determine how serious a message must be before it is written to the log file. Only those messages marked as this level, or as a more serious level, are logged. The default is JOB_TRACE. |
|
|
MULTINET_IPP_LOGFILE
Specifies the name of the log file. All queues from all symbiont processes will share this file unless there are individual queue overrides. The default is to create the log file in the default spool directory, with the name IPP_SYMBIONT_pid.LOG. |
|
|
MULTINET_IPP_OPCOM_LEVEL
Specifies one of the logging level values, and is used to determine how serious a message must be before it is sent to OPCOM. Only those messages marked as this level, or as a more serious level, are sent. The default is INFO. |
|
|
MULTINET_IPP_OPCOM_TERMINAL
Specifies the OPCOM operator "terminal" to send OPCOM messages to. Permissible values are listed later in this section. The default is the "PRINT" operator. |
|
|
MULTINET_IPV6_SERVICES
When this logical is defined (/SYSTEM) the MultiNet MASTER SERVER will create services that have their socket-family set to AF_INET6 as IPv6 services whether or not there are IPv6 services present on the system. If the logical is not defined, then services with a socket-family of AF_INET6 will be started as if the socket-family was AF_INET if there are no IPv6 interfaces on the system. |
|
|
MULTINET_LOCALDOMAIN
Your DNS local domain name; used by hostname lookup routines. Defined in START_MULTINET.COM and set by system manager with the command:
NET-CONFIG>SET LOCAL-DOMAIN
This name can be a maximum of 255 bytes in length. |
|
|
MULTINET_ADD_EOR MULTINET_LPD_queue>_ADD_EOR
Specify that an EOR marker is to be added to the end of each input
record, and what the value of that marker is to be. The marker is specified
as either a two-digit HEX number, beginning with "0x",
or the actual ASCII character to use.
|
|
|
MULTINET_LPD_queuename_typechar_parametername
Specifies the queue, file type, and print job parameters associated with a print queue. The MULTINET_LPD_* logical names are found in the MULTINET_PRINTER_TABLE logical name table.
Use an asterisk in a logical name to match any queue name, typechar, or parameter name. The formats for these logical names are:
1. MULTINET_LPD_*_*_ parametername The default for all queues and all file types.
2. MULTINET_LPD_queuename_*_ parametername The default for a specific queue and for all types on that queue.
3. MULTINET_LPD_queuename_typechar_ parametername The parameter for a specific queue and file type.
4. MULTINET_LPD_*_typechar_ parametername The default for all queues with a specified file type. |
|
|
MULTIENT_LPD_DEFAULT_USERNAME
The user name used by the LPD server for printing files on behalf of users who do not have a local account. If this logical is not defined, only remote users with the same local user name will be able to print files. Defined in START_MULTINET.COM and set by system manager with the command:
NET-CONFIG>SET LPD-DEFAULT-USERNAME
|
|
|
MULTINET_LPD_EMBED_CC
Turns on CC embedding. Value is the spec for the CC longword if it’s an 8 digit hex number, beginning with “0x”, otherwise it just enables embedding of the default CC as handed to the Input_Filter routine if the value is 1/T/Y.
The 8 digit hex number consists of four bytes, each of which specifies a different aspect of the CC. From lowest order byte to highest:
Byte 1:
Repeat count for Leading CC
The CC values are the actual ASCII character code value, except that zero is not "NUL", but is used to specify the sequence "CRLF".
$ DEFINE MULTINET_LPD_EMBED_CC "0x0D010A01"
Says to prefix each record with a LF, and follow it with a CR.
$ DEFINE MULTINET_LPD_FOOBAR_EMBED_CC "Y"
Says to embed the default CC for each record, as specified in the OpenVMS Utility Routines manual. For a Carriage-Return Carriage Control file this is a leading LF, trailing CR, with special handling around FF characters.
|
|
|
MULTINET_LPD_KEEPALIVE
Turns on keepalives when making socket connections. To enable this behavior, use one of these values: 1, y, Y, t, or T. |
|
|
MULTINET_LPD_MAXSTREAMS
Specifies the maximum number of streams each symbiont process will handle. |
|
|
MULTINET_LPD_PROXY
You can set up logical names to map remote LPD users to local users through a mechanism known as proxy access. Using logical names is useful when you want to receive LPD print jobs from a UNIX system on which the user names and UIDs on the client and server are completely uncoordinated. |
|
|
MULTINET_LPD_SYMBIONT_CONNECT_TIMERS
Controls timer retry intervals. |
|
|
MULTINET_LPD_SYMBIONT_DEBUG
Generates a log file with LPD. |
|
|
MULTINET_LPD_SYMBIONT_FILTER_ENABLED
Define as 1/t/y to enable the input filter code.
$ DEFINE MULTINET_LPD_SYMBIONT_FILTER_ENABLED Y
|
|
|
MULTINET_LPD_SYMBIONT_LFTAIL
Allows reversion of legacy behavior of terminating jobs with an <LF> rather than <CR>. To enable this behavior, use one of these values: Y, T, or 1. |
|
|
MULTINET_LPD_SYMBIONT_RESOURCE_TIMERS
Specifies the initial and maximum resource retry delay times. |
|
|
MULTINET_LPD_SYMBIONT_RETRY_INTERVAL
When the symbiont cannot connect to the remote system, or the remote LPD server reports insufficient resources for printing a job, the symbiont requeues the job for a later attempt. Requeue attempts are reported directly to the user who submitted the print job. The requeue time is controlled through logical names; you can control the length of time a job will wait before being attempted again after a connection failure by defining a logical name as follows:
$ DEFINE /SYSTEM MULTINET_LPD_SYMBIONT_RETRY_INTERVAL "delta-time"
The default value is "0 00:10:00.00," or ten minutes.
You can control the maximum amount of time that should elapse before the symbiont gives up on a job with this command:
$ DEFINE /SYSTEM MULTINET_LPD_SYMBIONT_MAX_RETRY_INTERVAL "delta-time"
The default value is "0 02:00:00.00", or two hours.
You must specify the delta-time values within quotation marks, and with a space separating the number of days from the number of hours, so the symbiont can process them correctly. |
|
|
MULTINET_LPQ_DISPLAY_FORMAT
Specifies the format in which the LPD server returns OpenVMS print queue information. The only current value is "UNIX". If not defined, the information is returned in OpenVMS print queue format. Set by system manager. |
|
|
MULTINET_MATCH_PROGRAM_AND_VERSION
When set, incoming GETPORT() calls from clients will have the program AND the version checked when returning a port. If no program and no version of the type requested are running, a port of 0 (zero) is returned. |
|
|
MULTINET_NAMESERVERS
The DNS (Domain Name System) name server IP address list. Defined in START_MULTINET.COM and set by system manager with the command:
NET-CONFIG>SET DOMAIN-NAMESERVERS
|
|
|
MULTINET_NAMESERVER_RETRANS
Defines the number of seconds between DNS requests if no response is received from the server. Defined in START_MULTINET.COM and set by system manager with the command:
NET-CONFIG>SET NAMESERVER-RETRANSMISSION
|
|
|
MULTINET_NAMESERVER_RETRY
Defines the number of retransmissions made to a DNS nameserver before a DNS lookup fails. Defined in START_MULTINET.COM and set by system manager with the command:
NET-CONFIG>SET NAMESERVER-RETRANSMISSION
|
|
|
MULTINET_NLPx_REMOTE_PRINTER
If you want an extra blank line on each page and, consequently, an extra blank page when the bottom margin has been reached, set this logical to include the configuration parameter DOLFFF=Y. Depending on your printer, it may be desirable to keep the behavior and not have the extra blank line and extra blank page. |
|
|
MULTINET_NTP_CONFIGFILE
Specifies the full file name of the NTP configuration file in those cases where the default value of MULTINET:NTP.CONF isn't acceptable for some reason. This system logical is used by the NTP server at startup time to override the hard-coded default for the configuration file name. Use is optional. See the MultiNet Installation & Administrator's Guide, Chapter 14, for more information about the NTP.CONF file and its uses. |
|
|
MULTINET_NTP_LOGFILE
Specifies the name of the name of the NTP server log file if the default value of MULTINET:NTPD.LOG isn’t acceptable for some reason. This system logical is used by the NTP server at startup time to override the hard-coded default for the server log file file name. Use is optional. You can also use the LOGFILE option in the configuration file to specify a different log file name, but since this processing happens later in the startup sequence, some initial outputs may still go to the default log file. The MULTINET_NTP_LOGFILE logical is checked prior to first opening of the log file and avoids this problem. |
|
|
MULTINET_NTYSMB
MultiNet must be started before NTY devices can be created or MULTINET_NTYSMB print queues can be initialized or started.
System managers using the OpenVMS queue manager's Autostart capability must leave Autostart disabled until after MultiNet is started and NTY devices have been set up.
To set up a print queue with MULTINET_NTYSMB:
The following is an example of a print queue set up to an HP LaserJet printer with a JetDirect card.
$ NTYCP := MULTINET:NTYCP
|
|
|
MULTINET_NTYSMB_DEBUG
Enables various debug options. |
|
|
MULTINET_NTYSMB_*_MAXTIMERMSG
Specifies the message to be issued when the connection timer hits the maximum value. |
|
|
MULTINET_NTYSMB_TIMERS
Corrects timer handling in the case where the maximum timeout is reached. The timers are controlled by two values taken from the equivalence string for the MULTINET_NTYSMB_TIMERS logical name, initial and ceiling. The values for initial and ceiling are given in seconds. The initial value is how soon, after the first connection attempt fails, the symbiont is to retry the connection. On subsequent connection failures, the symbiont backs off its retries exponentially, until it’s only retrying every ceiling seconds. By default, initial is 10 seconds and ceiling is 7200 seconds (2 hours). The NTYSMB symbiont never gives up on a job. Define the logical name as:
$ DEFINE /SYSTEM /EXEC MULTINET_NTYSMB_TIMERS “initial ceiling”
· Zeros out channel information in case a write request is received when a shutdown or close is in progress. · Fixes queue shutdown when a timed retry is outstanding and a STOP/REQUEST is issued against the queue. · Corrects I/O synchronization problems where data could be sent to the printer out of order. |
|
|
MULTINET_PCNFSD_PRINTER_LIMIT
Use this logical to determine if the returned packet size is to be limited (takes a number for its value, in bytes). If this logical is not defined, MultiNet determines the size of the packet at run time. For example:
$ DEFINE/SYSTEM/EXECUTIVE MULTINET_PCNFSD_PRINTER_LIMIT 45000
|
|
|
MULTINET_PCNFSD_QUEUE_TYPES
Use this logical to select the type of queues you want returned. Define the queues to be a comma-separated list of these valid queue types: GENERIC, PRINTER, SERVER, SYMBIONT, and TERMINAL.
$ DEFINE/SYSTEM/EXECUTIVE MULTINET_PCNFSD_QUEUE_TYPES "PRINTER"
|
|
|
MULTINET_POP3_CACHE_SIZE
Specifies the POP (Post Office Protocol) cache size in bytes. Folder in which to put read mail. Set by user or system manager. |
|
|
MULTINET_POP3_FLAGS
Special POP3 capabilities are indicated by each bit position in this logical name value. Possible values are:
1 - Read only messages from the NEWMAIL folder that are marked as new. 2 - Move messages from the NEWMAIL folder after they are read. 4 - Release the POP client before OpenVMS mailbox is actually closed. 16 - Remove the "NODE::" portion of the "From:" address. 32 - Save deleted messages in the folder specified by MULTINET_ POP3_DEST_FOLDER 64 - Build message headers from OpenVMS Mail "From" line. 128 - Compress mail box, but delete all versions of MAIL.OLD in the MAIL directory.
Combine values by adding the numeric values together. For example, 7 enables values 1, 2, and 4. Set by user or system manager. |
|
|
MULTINET_POPx_SOURCE_FOLDER
Specifies the folder from which mail should be read. Set by user or system manager. |
|
|
MULTINET_PRINTER_NO_OPCOM
Disables OPCOM messages from the LPD symbiont. |
|
|
MULTINET_PRINTER_queuename_ALLOW_USER_SPEC
If defined with an equivalence string of "Y", "T" or "1", the user can specify the ADDRESS and PRINTER values for the print job on the PRINT command, in the /PARAMETERS qualifier. In addition, specifying this logical will result in requeue retries, rather than the default timed retries when there is a problem with a connection. If this logical is not defined, or is defined with some other equivalence string, the ADDRESS and PRINTER parameters entered on the PRINT command by the user will be ignored, and timed retries will be performed. |
|
|
MULTINET_PRINTER_queuename_DEFAULT_FILTER
Allows you to specify the print filter character to use instead of "f" on the specified LPD queue. Declare the alternative, normal print filter character as follows:
$ DEFINE /TABLE=MULTINET_PRINTER_TABLE -
queuename is the name of the queue for which you are modifying the print filter character, and character is the character to be used. You may override both the default character and the alternative character by including the /PARAMETER=(FILTER="character") qualifier on your print request (assuming the logical MULTINET_PRINTER_queuename_ALLOW_USER_SPEC is defined appropriately. |
|
|
MULTINET_PRINTER_queuename_NO_FFLF_DEFAULT
USER_LPD_CLIENT.C supports the addition of a linefeed after a formfeed. Use logical names and print parameters to control the behavior. |
|
|
MULTINET_PRINTER_queuename_PASSALL_FILTER
Allows you to specify the print filter character to use instead of "v" on the specified LPD queue. Declare the alternative, passall print filter character as follows:
$ DEFINE /TABLE=MULTINET_PRINTER_TABLE -
queuename is the name of the queue for which you are modifying the passall print filter character, and character is the character to be used. You may override both the default character and the alternative passall character by including the /PARAMETER=(FILTER="character") qualifier along with the /PASSALL qualifier on your print request (assuming the logical MULTINET_PRINTER_queuename_ALLOW_USER_SPEC is defined appropriately). |
|
|
MULTINET_PRINTER_queuename_SUPPRESS_REMOTE_BANNER
When defined, does not include the “L” command in the control file to request a banner page. |
|
|
MULTINET_PRINTER_queuename_RETAIN_CR_DEFAULT
Allows you to specify the disposition of CR characters in CRLF sequences on the specified LPD queue. Change CR processing on the queue as follows:
$ DEFINE/TABLE=MULTINET_PRINTER_TABLE -
queuename is the name of the queue for which you are modifying the CR disposition, and boolean indicates whether or not CR characters are to be retained in CRLF sequences included in text sent to the remote system for printing. You may override both the default CR disposition and the alternative disposition by including the /PARAMETER=(RETAIN_CR = "boolean") qualifier on your print request (assuming the logical MULTINET_PRINTER_queuename_ALLOW_USER_SPEC is defined appropriately). |
|
|
MULTINET_PRINTER_queuename_SUPPRESS_FF
Controls whether CRFF is added to jobs. |
|
|
MULTINET_PRINTER_TABLE
Defines a logical name table allowing control of job queueing parameters used when entering a job in the OpenVMS queueing system. The logicals contained in this table have the name format of:
MULTINET_LPD_queuename_typechar_parametername
When a value is omitted (indicating all values of that type), an asterisk is inserted in the logical name. |
|
|
MULTINET_PSIx_CHARGE
Determines who to charge for calls. If set to the value "US," incoming calls with reversed charges will be accepted and outgoing calls will not be made with charges reversed. If set to the value "THEM" incoming calls with charges reversed are refused. An attempt is made to reverse charges on all outgoing calls. |
|
|
MULTINET_PSIx_CUG
Allows an interface to be associated with a closed user group to restrict unwanted access. |
|
|
MULTINET_PSIx_IDLE
Determines the connection idle time interval (in seconds) on a per-interface basis. A timer will expire every n seconds and check for any activity on the interface. If there has been no activity since the last time-out, the X.25 connection for this interface will be cleared. |
|
|
MULTINET_PSIx_LOCAL
Specifies the endpoints of the X.25 connection in the following format:
[network.]DTE
DTE is the endpoint address to which the local of remote IP address is bound and network is the optional network name. The network for this interface must be specified if it is different from the PSI default, as specified by the logical PSI$NETWORK. |
|
|
MULTINET_PSIx_NOOUT
Specifies that the identified interface will not initiate an outgoing call under any circumstances. |
|
|
MULTINET_PSIx_PEER
Specifies the endpoints of the X.25 connection in the following format:
[network.]DTE
DTE is the endpoint address to which the local of remote IP address is bound, and network is the optional network name. The network for this interface must be specified if it is different from the PSI default, as specified by the logical PSI$NETWORK. |
|
|
MULTINET_PSIx_PKTSIZE
Specifies the packet size for an outgoing call, where the packet size requested is different from the default for the PSDN. A value of zero causes the default value to be used. |
|
|
MULTINET_PSIx_REVCHG
Specifies that this interface will accept incoming calls with charges reversed. |
|
|
MULTINET_PSIx_WINDOW
Specifies the sliding window size for a connection. This is a value in the range of 1 to 127 (subject to further restrictions by the PSDN). A value of zero causes the default value to be used. |
|
|
MULTINET_RMT_TAPE_DEVICE
The default OpenVMS tape drive used by the RMT server. Defined in START_MULTINET.COM and set by system manager with the command:
NET-CONFIG>SET DEFAULT-RMT-TAPE-DEVICE
|
|
|
MULTINET_ROOT
The MultiNet rooted directory search path. Defined in START_MULTINET.COM. This logical should not be modified. |
|
|
MULTINET_RSHELL_ADDRESS
Set by the MultiNet RSHELL server to the IP address of the system originating an RSHELL (rsh/rexec) session; the value is only available after the system-wide login procedure and the user's LOGIN.COM have processed. |
|
|
MULTINET_RSHELL_ALLOW_CAPTIVE
Set to TRUE to permit R service into captive OpenVMS accounts. Set by system manager. The default is not enabled. |
|
|
MULTINET_SCP2_CONNECT_TIMEOUT
Defines a number specifying how long SCP2 should wait for a response to the INITIALIZE command from the server program. This is a VMS delta time number. The default is 5 minutes. |
|
|
MULTINET_SCP2_VMS_MODE_BY_DEFAULT
When defined to TRUE, YES, or 1, chooses the /VMS qualifier if /TRANSLATE_VMS or /NOVMS has not been specified. |
|
|
MULTINET_SERVER_ASTLM
Defines the maximum number of ASTs that can be outstanding. The default value is 200. |
|
|
MULTINET_SERVER_BIOLM
Defines the maximum number of buffered I/O operations at one time. The default value is 200. |
|
|
MULTINET_SERVER_BYTLM
Defines the amount of memory, in bytes, for buffered I/O operations. The default value is 1000000. |
|
|
MULTINET_SERVER_DIOLM
Defines the maximum number of buffered I/O operations at one time. The default value is 200. |
|
|
MULTINET_SERVER_ENQLM
Defines the maximum number of locks that can be outstanding. The default value is 2048. |
|
|
MULTINET_SERVER_FILLM
Defines the maximum number of files that the MULTINET_SERVER can have open. The default value is 200. |
|
|
MULTINET_SERVER_PAGEFILE
Defines the maximum number of pages that can be allocated in the paging file for the process. The default value is 400. |
|
|
MULTINET_SERVER_PRCLM
Defines the maximum number of subprocesses that can be created. The default value is 10. |
|
|
MULTINET_SERVER_TQELM
Defines the maximum number of timer queue entries created. The default value is 200. |
|
|
MULTINET_SERVER_WSEXTENT
Defines the maximum number of pages that the MULTINET_SERVER can increase its physical size to. The default value is 400. |
|
|
MULTINET_SERVER_WSLIMIT
Defines the maximum number of pages in the working set of the MULTINET_SERVER. The default value is 400. |
|
|
MULTINET_SERVER_WSQUOTA
Defines the maximum number of pages that the MULTINET_SERVER can increase its working set to. The default value is 400. |
|
|
MULTINET_SFTP_CASE_INSENSITIVE
This logical causes SFTP to treat filenames in a case insensitive manner when it is defined to TRUE, YES, or 1 (the number one). |
|
|
MULTINET_SFTP_DEFAULT_FILE_TYPE_REGULAR
If this logical is defined to TRUE, YES or 1 (the number one), then the SFTP server will use a default file type of REGULAR instead of UNKNOWN for OPEN operations. This can correct problems with filenames without a . (dot) in them getting .dir added to them. The filename will appear with a . at the end of the name in directory listings |
|
|
MULTINET_SFTP_FILE_ESTIMATE_THRESHOLD
This logical controls the minimum number of blocks that a text file must be for an estimated transfer size to be returned instead of an exact size. The default is to estimate the transfer size for all text files |
|
|
MULTINET_SFTP_FALLBACK_TO_CBT
When defined to TRUE, YES, or 1 (the number one) and a VMS file transfer is being performed, creates a Contiguous file if that file has Contiguous characteristics. The file will be created as Best Try if there is insufficient space to create it as Contiguous. |
|
|
MULTINET_SFTP_IDLE_TIMEOUT
This logical can be used to specify the number of minutes for an SFTP server process to remain active without exchanging commands or data with the SFTP client. The default is no timeout. |
|
|
MULTINET_SFTP_MAXIMUM_DEVICES
The logical MULTINET_SFTP_MAXIMUM_DEVICES controls the amount of information about mounted devices that is returned to the SFTP client when the SFTP server starts. This information is used in the display of the LSROOTS command. The default value is 5, which allows information on up to 5 mounted disk devices to be returned. Higher numbers will allow more information to be returned, and -1 will return all information. A caution if your system has a large number of mounted devices: some customers experienced hangs when information about a large number of devices was returned. Since this information is not necessary for the proper function of SFTP, Process Software has chosen to limit the amount of information that is returned to avoid the potential hang. |
|
|
MULTINET_SFTP_MAXIMUM_PROTOCOL_VERSION
This logical can be used to limit the version of the SSH File Transfer Protocol that the SFTP client and server use. This can sometimes provide a work-around for problems encountered with different implementations of the protocol. The default value is 4. Protocol versions 2 and 3 are also used by popular implementations. |
|
|
MULTINET_SFTP_NEWLINE_STYLE
This logical controls the newline style that SFTP uses. Which can be helpful in transferring text files. The values are: UNIX <lf>, VMS <lf>, MAC <cr>. If the logical is not defined, or defined to any other value, then <cr><lf> will be used for the text line separator as documented in the SSH File Transfer specification. |
|
|
MULTINET_SFTP_ODS2_SRI_ENCODING
This logical controls whether or not SRI encoding is used for filenames on VMS ODS-2 disks. If the logical is not defined, or is defined to TRUE, YES, or 1 (the number one) then SRI encoding is used on ODS-2 disks for filenames that contain uppercase letters and special characters. |
|
|
MULTINET_SFTP_RETURN_ALQ
When defined to TRUE, YES, or 1 (the number one) and files are being transferred in VMS mode, returns the Allocation Quantity for the file. This is disabled by default because copying a small file from a disk with a large cluster size to a disk with a small cluster size causes the file to be allocated with more space than necessary. You have the option of retaining the allocated size of a file if it was allocated the space for a reason. Indexed files require that the allocation quantity be included in the file attributes; this is handled by SCP2/SFTP-SERVER2. |
|
|
MULTINET_SFTP_SEND_VENDOR_ID
When defined to NO, FALSE or 0 (the number zero) the SFTP2 client will NOT send the extended command vendor-id upon completion of version negotiation with the server. |
|
|
MULTINET_SFTP_TRANSLATE_VMS_FILE_TYPES
This is a bit mask that determines which VMS file types should be translated when not operating in VMS mode.
Bit 0 (1) =
FIXED The values are:
0 (zero) =
NONE
Note that this logical affects SCP2 as well as the server, as SCP2 has the server built into it for handling local file access. |
|
|
MULTINET_SFTP_VMS_ALL_VERSIONS
This logical controls whether or not all versions of a file are returned. The values TRUE, YES or 1 (the number one) will cause all versions to be returned, any other value is to only return the name of the file without a version. The default is to return only one filename without the version number. |
|
|
MULTINET_SFTP_VMS_MODE_BY_DEFAULT
When defined to TRUE, YES, or 1, this logical chooses the /VMS qualifier if /NOVMS has not been specified. |
|
|
MULTINET_SFTP_username_CONTROL
This logical can be defined /SYSTEM to any combination of NOLIST, NOREAD, NOWRITE, NODELETE, NORENAME, NOMKDIR, NORMDIR to restrict the operations that the user can perform with the SFTP server. NOWRITE will disable PUT, DELETE, RENAME, MKDIR, RMDIR, NOREAD will disable GET and LIST. |
|
|
MULTINET_SFTP_username_ROOT
This logical can be defined /SYSTEM to restrict the user to the directory path specified. Subdirectories below the specified directory are allowed. |
|
|
SSH_SFTP_LOG_SEVERITY, SSH2_SFTP_LOG_FACILITY
The logical SSH_SFTP_LOG_SEVERITY can be defined /SYSTEM to 20000 to log file transfers or 30000 to log all SFTP operations. The logical SSH2_SFTP_LOG_FACILITY must also be defined /SYSTEM to specify the logging class that is used with OPCOM. Values below 5 will use the network class; 5 will use OPER1, 6 will user OPER2, etc. The maximum value that can be specified is 12, which will use OPER8. |
|
|
MULTINET_SEARCHDOMAINS
Specifies a space-separated list of domain names the MultiNet resolver appends to non-dot-terminated names. The search list can be up to 511 bytes in length. The maximum number of domains to search is 6.
Example:
$ DEFINE/SYSTEM/EXECUTIVE
MULTINET_SEARCHDOMAINS -
$ MULTINET NSLOOKUP/DEBUG john.whorfin
These commands will look up john.whorfin, then john.whorfin.widgets.yoyodyne.com, then john.whorfin.ajax.com, and finally john.whorfin.yoyodyne.com. |
|
|
MULTINET_SERVER_PRIORITY
The process priority at which the MultiNet master server process (MULTINET_SERVER) should run. Set by system manager before MultiNet is started. |
|
|
MULTINET_SMTP_A1_NAME
Changes the name of the ALL-IN-1 IOS gateway mailbox. The default value is A1. |
|
|
MULTINET_SMTP_A1_DOMAIN
Specifies the RFC-822 domain associated with the ALL-IN-1 IOS gateway. Use the domain you specified when configuring your SMTP/MR gateway. |
|
|
MULTINET_SMTP_ACCOUNTING_HOST
The name of the IP address of the system running the accounting program. |
|
|
MULTINET_SMTP_ACCOUNTING_PORT
The port number that the program was set up to listen on. |
|
|
MULTINET_SMTP_AM_NAME
Changes the name of the ALL-IN-1 MAIL gateway mailbox. The default value is AM. |
|
|
MULTINET_SMTP_AM_DOMAIN
Specifies the RFC-822 domain associated with the ALL-IN-1 MAIL gateway. Use the domain you specified when configuring your SMTP/MR gateway. |
|
|
MULTINET_SMTP_DELIVERY_RECEIPTS
Set this logical to TRUE for the MultiNet SMTP subsystem to generate a delivery receipt mail message to the originator when a message is delivered to a local user. Set by system manager. |
|
|
MULTINET_SMTP_ENVELOPE_FROM_HOST
When defined the value is used for the host name instead of the actual host name when sending the MAIL FROM: line to the remote server. This is useful if there are multiple independent systems that send mail that you would like to appear to be a single system. |
|
|
MULTINET_SMTP_FORWARDER
Identifies the host to which mail should be forwarded if the local host cannot deliver a particular mail message (for any reason). The message then becomes the responsibility of the forwarder host for final delivery. Defined in START_MULTINET.COM and set by system manager with the command:
MAIL-CONFIG>SET SMTP-FORWARDER
|
|
|
MULTINET_SMTP_FROM_HOST
Allows you to change the host name that appears in your return address on outgoing mail. Normally, the host name you choose must be a "local" host name; that is, it must be one of the registered SMTP host name aliases on the system (either from the SMTP-HOST-NAMES setting or the HOST-ALIAS-FILE). If it is not a known alias, the setting is ignored.
If you define the host name in executive mode, however, MULTINET_SMTP_FROM_HOST can be any arbitrary host name. The name is not checked against the SMTP host name.
This feature lets users from different administrative entities within an organization have return addresses that reflect the names of those entities. To enable this feature:
1. Set up MX records in DNS so mail is routed to the local host for each separate host name. For information about MX records, see the discussion of zone files in the Administrator's Guide. 2. Set up SMTP-HOST-NAMES or the HOST-ALIAS-FILE with a list of host names. 3. Define the logical name MULTINET_SMTP_FROM_HOST for each user. Base the value for this logical name on an aspect of the department or organization to which the user belongs. |
|
|
MULTINET_SMTP_HOST_ALIAS_FILE
Specifies the name of an alternate SMTP host alias file. The default is MULTINET:SMTP_HOST_ALIASES). |
|
|
MULTINET_SMTP_HOST_NAME
Specifies the host name to be used in the return address of mail sent from the local host. The local host also accepts mail sent to this host name. Defined in START_MULTINET.COM and set by system manager with the command:
MAIL-CONFIG>SET SMTP-HOST-NAME
|
|
|
MULTINET_SMTP_INCOMING_MSGSIZE_LIMIT
Rejects an oversized incoming message. This logical can be defined as:
S
“Small =1 MB
The default for this logical is not defined, which means that no size limit checking is performed. If the logical is defined, when the message size is detected over the defined limit, the message will be rejected.
In the following example, any mail messages over 10 MB will be rejected:
$ define/sys/exe MULTINET_SMTP_INCOMING_MSGSIZE_LIMIT “M”
The size that the SMTP server checks is the size of the data received in the data channel; it may be different from the actual message size. This is especially true when the message has an attachment. In this case, the attachment will be encoded and the data size will be the message size plus the encoded attachment data size. |
|
|
MULTINET_SMTP_IGNORE_INTERFACE_NAMES
When defined (as /SYSTEM, or any value), the MultiNet SMTP mail delivery procedure does not compare the destination address with the addresses of the interfaces on the system to determine if the message could be delivered locally. |
|
|
MULTINET_SMTP_LOG
Enables logging for SMTP. |
|
|
MULTINET_SMTP_MAXIMUM_822_TO_LENGTH
The default header length is 1024 characters. This logical can be used to override the 1024 byte default length of the To: and Cc: header fields. The logical can set the maximum length to anywhere from 256 to 65535. |
|
|
MULTINET_SMTP_ALLOW_MIME_SEND
If this logical is defined to be Y, T, or 1 then if the first line of the message file being send starts with the mime tag, the blank line at the end of the header information is suppressed so that the header lines in the message file will be seen as header lines rather than message body. The value of the mime tag can be controlled with the MULTINET_SMTP_MIME_TAG logical. |
|
|
MULTINET_SMTP_MIME_TAG
Defines the
string to look for at the start of the first line of the message file when
the MULTINET_SMTP_ALLOW_MIME_SEND logical is
defined. The default value is |
|
|
MULTINET_SMTP_MRGATE-NAME
Changes the name of the Message Router gateway mailbox. The default value is MRGATE. |
|
|
MULTINET_SMTP_POSTMASTER
Identifies the user to whom bounced mail messages should be delivered if they cannot be returned to the originator. Defined in START_MULTINET.COM and set by system manager with the command:
MAIL-CONFIG>SET SMTP-POSTMASTER
|
|
|
MULTINET_SMTP_QUEUE
Specifies the SMTP queue name. May point to an OpenVMS server queue or to a generic queue if the value of this logical is greater than 1. Defined in START_SMTP.COM (which is invoked from START_MULTINET.COM). |
|
|
MULTINET_SMTP_QUEUE_COUNT
Specifies the number of SMTP processing queues (default is 1) on the local system. Set by system manager before MultiNet is started. |
|
|
MULTINET_SMTP_RETRY_INTERVAL
Defines the time (in minutes) to wait before attempting to resend a message that could not be delivered (default: 30 minutes). This value should be in OpenVMS delta-time format. Delivery failure may occur because the remote host is down or unreachable because of a network outage. Set by system manager. |
|
|
MULTINET_SMTP_RETURN_INTERVAL
Defines the maximum length of time to wait before returning a message to its sender if it cannot be delivered (default: 4 days). This value should be in OpenVMS delta-time format. Set by system manager. |
|
|
MULTINET_SMTP_SEND_CLASS
Defines the message class used for interactive messages delivered via the SMTP SEND, SAML, or SOML commands (default: USER16). This type of message can be created with the MULTINET SEND command. See also, SET BROADCAST. Set by system manager. |
|
|
MULTINET_SMTP_SERVER_DISABLE_VRFYEXPN
Disables VRFY and EXPN processing. Define it to have some non-zero value to disable the requisite functions. The following values may be combined to specify which function:
1 to disable VRFY 2 to disable EXPN 3 to disable both VRFY and EXPN |
|
|
MULTINET_SMTP_SYMBIONT_LOG
Enables additional logging for debugging purposes. |
|
|
MULTINET_SNMP_MAX_CONNECTIONS
This logical controls the maximum number of connections that the SNMP Agent will ask the MultiNet kernel for. The default value is 256, the maximum value is 3276. This value can be set in MULTINET CONFIGURE/NETWORK |
|
|
MULTINET_SNMP_MAX_ROUTES
This logical controls the maximum number of routes that the SNMP Agent will ask the MultiNet kernel for. The default value is 256, the maximum value is 2978. This value can be set in MULTINET CONFIGURE/NETWORK |
|
|
MULTINET_SOCKET_LIBRARY
The MultiNet socket library. Defined in START_MULTINET.COM. This logical name should not be modified. |
|
|
MULTINET_SOCKET_TRACE
This logical is useful for debugging applications which call TCP/IP library routines. The value 1 does tracing for control and information routines. (No reads or writes); the value 2 traces read routines and the value 4 traces write routines. These values can be ORed together to get any combination of control, read and write tracing. When the logical is defined to a non-numeric value it is assumed to be a file specification to write a trace for all routines. The default value for the file created is SYS$SCRATCH:MULTINET_SOCKET_pid.so that separate files are created for each process when the logical is visible to multiple processes. The logical can be defined to be just a directory specification to get multiple traces in a single directory. |
|
|
MULTINET_SPOOL
The MultiNet spool directory used to spool incoming LPD print files and incoming and outgoing SMTP messages. Defined in START_MULTINET.COM and set by system manager with the command:
NET-CONFIG>SET SPOOL-DIRECTORY
|
|
|
MULTINET_SSH_ACCESS_CHECK_OLD_STYLE
Use the NETWORK access mask instead of the REMOTE access mask to determine access during login |
|
|
MULTINET_SSH_ACCESS_USE_LOCAL
Use the LOCAL login mask to allow logins instead of the NETWORK or REMOTE masks in SYSUAF |
|
|
MULTINET_SSH_ACC_REJ_LOG_FILE
If the user has set a log file to log connection accept and reject messages, this logical will be defined and will provide the name of the log file. This logical is set by using the SET LOG-FILE keyword in MULTINET CONFIGURE/SERVER, and should not be modified directly by the user. |
|
|
MULTINET_SSH_ALLOW_EXPIRED_PW
Allows logging in to an account when the account's password has expired due to pwdlifetime elapsing. This applies to all users and circumvents normal VMS expired-password checking, and therefore should be used with caution. An entry is made into the SSH_LOG:SSHD.LOG file when access is allowed using this logical name. In addition, the logical name MULTINET_SSHpid_PWDEXP is defined in the logical name table LNM$SSH_LOGICALS, where pid is the process-id of the user. |
|
|
MULTINET_SSH_CMD_FILE_DIR
Defines the location the temporary files used when executing a remote SSH command are placed. This must be used with caution, as the directory must allow full WORLD access.
The logical name must not translate to SYS$LOGIN, due to the state of the child process that will be executing the remote command at the time the command procedure is created. |
|
|
MULTINET_SSH_ALLOW_PREEXPIRED_PW
Allows logging in to an account when the password has been pre-expired. This applies to all users and circumvents normal VMS expired-password checking, and therefore should be used with caution. An entry is made into the SSH_LOG:SSHD.LOG file when access is allowed using this logical name. In addition, the logical name MULTINET_SSHpid_PWDEXP is defined in the logical name table LNM$SSH_LOGICALS, where pid is the process-id of the user. |
|
|
MULTINET_SSH_DISPLAY_SYS$ANNOUNCE
The SSH v1 protocol does not allow for the display of SYS$ANNOUNCE prior to logging in. If this logical is set, the contents of SYS$ANNOUNCE is displayed immediately after successful authentication and prior to the display of the contents of SYS$WELCOME. |
|
|
MULTINET_SSH_ENABLE_SSH1_CONNECTIONS
When set, enables the system to process SSH1 connections. |
|
|
MULTINET_SSH_ENABLE_SSH2_CONNECTIONS
When set, enables the system to process SSH2 connections. |
|
|
MULTINET_SSH_KEYGEN_MIN_PW_LEN
Defines the minimum passphrase length when one is to be set in SSHKEYGEN. If not defined, defaults to zero. |
|
|
MULTINET_SSH_LOG_ACCEPTS
When set, causes the server to log successful connection requests as either an OPCOM message or a line in a log file. Specified by the SET LOG-ACCEPT command in MULTINET CONFIGURE/SERVER. Note that the server does not use the information set in the ACCEPT-HOSTS keyword in CONFIGURE/SERVER. Rather, it uses the AllowHosts and DenyHosts keywords in the SSH server configuration file. Also, a successful connection request doesn't equate to a successful authentication request. This logical should not be modified directly by the user. |
|
|
MULTINET_SSH_LOG_FILE
Define the default file specification for the SSH server log file. The default is SSH_LOG:SSHD.LOG. |
|
|
MULTINET_LOG_MBX
Points to the OpenVMS mailbox used to log connection accept and reject messages. This must not be modified by the user. |
|
|
MULTINET_SSH_LOG_REJECTS
When set, causes the server to log rejected connection requests as either an OPCOM message or a line in a log file. Specified by the SET LOG-REJECT command in MULTINET CONFIGURE/SERVER. Note that the server does not use the information set in the REJECT-HOSTS keyword in CONFIGURE/SERVER. Rather, it uses the AllowHosts and DenyHosts keywords in the SSH server configuration file. This logical should not be modified directly by the user. |
|
|
MULTINET_SSH_MAX_SESSIONS
Set this to the maximum number of concurrent SSH sessions you want to allow on the server system. The limit is between 1 and 9999. It defaults to 9999 if it is not defined. The suggested place to set this is in START_SSH.COM. SSH must be restarted to use the new value if it is changed. |
|
|
MULTINET_SSH_PARAMETERS_n
Parameters used to start SSHD_MASTER. They are made up from parameters set in MULTINET CONFIG/SERVER. |
|
|
MULTINET_SSH_NEW_STATUS_CODES
If defined, Multinet SSH, with the exception of SCP and SFTP2, will use more meaningful status codes than those previously provided. |
|
|
MULTINET_SSH_USE_SYSGEN_LGI
If defined /SYSTEM causes SSHD to use the VMS SYSGEN value of LGI_PWD_TMO to set the login grace time, overriding anything specified in the command line or the configuration file. |
|
|
MULTINET_SSH2_HOSTKEYS_DIR
Points to the directory that contains the SSH2 host keys. Normally set to MULTINET_SPECIFIC_ROOT:[MULTINET.SSH2]. |
|
|
MULTINET_SSH2_KNOWNHOSTS_DIR
Points to the directory that contains SSH2 public host keys from systems known to this system. Normally set to MULTINET_SPECIFIC_ROOT:[MULTINET.SSH2.KNOWNHOSTS]. |
|
|
MULTINET_SSH_SCP_SERVER_DEBUG
Enables
debugging messages for the SCP-SERVER1 image that
provides service to SCP commands that use the RCP over SSH2 protocol
(OpenSSH). When this is defined, the file |
|
|
MULTINET_SSH_SFTP_SERVER_DEBUG
Enables debugging messages for the SFTP-SERVER2 image that provides service to SCP2 commands that use the SFTP protocol. When this is defined, the file SFTP-SERVER.LOG is created in the user’s login directory. These files are not purged. Larger values yield more debugging information |
|
|
MULTINET_STREAM_DEAD_LINK_TIMEOUT
Controls dead link detection and handling. |
|
|
MULTINET_STREAM_queuename_DEAD_LINK_TIMEOUT
Controls dead link detection and handling. |
|
|
MULTINET_STREAM_SYMBIONT_DEBUG
Generates a log file with STREAM. |
|
|
MULTINET_STREAM_SYMBIONT_TIMERS
Sets the initial and the maximum time to wait before retrying the connection. For example, if you defined the logical as follows it would retry the connection after 1 second and double the time between subsequent retries until it reached the maximum of 10 seconds. |
|
|
MULTINET_SVCORDER
Contains the list of services used in the order specified.
Use the values bind,local (the default if the logical is not defined) and local,bind (which uses the Hosts database first, then DNS if the lookup fails). |
|
|
MULTINET_TELNET_AUTH
Determines the authentication behavior of the Kerberos 5 Telnet Server. There are 3 possible values: ALLOWED, REQUIRED, and DISABLED. The default is DISABLED; a login prompt will result. When the value is REQUIRED, any user without a valid Kerberos V5 Ticket Granting Ticket (TGT) will be rejected. If the value is ALLOWED, the user can log-in to the server with or without a valid Kerberos V5 TGT (with a login prompt resulting if no TGT). |
|
|
MULTINET_TELNET_NEGOTIATION_PORTS
Defines the list of remote TCP port numbers for which the TELNET client will perform TELNET option negotiations (default: TELNET options are only negotiated if you connect to the TELNET server port-TCP port number 23). This logical name can be useful when using TELNET to connect systems that provide interactive terminal services on TCP port numbers other than 23; the TELNET /PORT command can be used to specify a port number other than 23. The value defined is a comma-separated list enclosed in double quotes. Set by user or system manager. |
|
|
MULTINET_TELNET_PORT
Determines the port number the Kerberos 5 Telnet Server will listen on for incoming telnet connections. The default is 23. |
|
|
MULTINET_TELNET_PRINT_ESCAPE_CHARACTER
Determines whether the escape character is displayed when a TELNET connection is established to a remote system. |
|
|
MULTINET_TFTP_DEFAULT_DIRECTORY
Defines the default TFTP server directory. Defined in START_MULTINET.COM and set by system manager with the command:
NET-CONFIG>SET TFTP-DIRECTORY
|
|
|
MULTINET_TIMEZONE
Defines the current timezone (not adjusted for Daylight Savings Time). Defined in START_MULTINET.COM and set by system manager with the command:
NET-CONFIG>SET TIMEZONE
|
|
|
MULTINET_TN3270_APPLICATION_KEYPAD
Enables or disables use of the OpenVMS system application keypad. The default is ON. |
|
|
MULTINET_TN3270_LANGUAGE
Specifies the name of a regional language associated with a keyboard type. For example, for a UK EBCDIC keyboard mapped into the HP multinational character set, this logical is set to the arbitrary UK_ENGLISH_DEC_MULTI value.
The name specified for this logical must agree with the mapping definition name supplied in the respective translation table file. The MULTINET_TN3270_TRANSLATION_TABLES logical name points to the translation file name; MULTINET_TN3270_LANGUAGE points to the individual mappings within the translation table.
Examples of translation tables may be found in the file MULTINET:TN3270.TRANSLATION. |
|
|
MULTINET_TN3270_TRANSPARENT_MODE
Enables or disables the transparent mode depending on whether you are accessing an IBM 7171 ASCII device controller. This logical name is enabled automatically when transparent mode information is received from an IBM host. |
|
|
MULTINET_TN3270_TRANSLATION_TABLES
Specifies the name of the current translation table file. The specified file resides in the MULTINET: directory. This logical points at the file name, and MULTINET_TN3270_LANGUAGE points at the individual mapping definitions within the file. |
|
|
MULTINET_USER_ACCESS
Customizes USER_ACCESS.C user exit for client application auditing and access control. See USER_ACCESS.C in the MULTINET_ROOT: [MULTINET.EXAMPLES] directory for more details. Set by system manager. |
|
|
MULTINET_VMSMAIL_HEADER_CONTROL
Specifies which RFC 822 headers to include in messages delivered to local OpenVMS MAIL users. Possible values are
ALL - includes all RFC 822 headers
MAJOR (the default) - all Received: and Return-Path: headers are to be set by the system manager.
NONE - all headers are to be excluded except those with direct counterparts within OpenVMS MAIL (To:, Cc:, Subj:, From:). |
|
|
MULTINET_VMSMAIL_LOCASE_USERNAME
Lowers the case of usernames in outbound messages automatically. |
|
|
MULTINET_VMSMAIL_REPLY_CONTROL
Determines whether the OpenVMS MAIL return address of an SMTP message is obtained from the RFC 822 From: line instead of the SMTP MAIL FROM: (the default) address. If you want OpenVMS MAIL addresses to have the return address set from the RFC 822 From: header, define this logical name with the value REPLY-TO,FROM. Set by system manager. |
|
|
MULTINET_WHOIS_DEFAULT_SERVER
Defines the default host name for the WHOIS command (default: RS.INTERNIC.NET). Defined in START_MULTINET.COM and set by system manager with the command:
NET-CONFIG>SET WHOIS-DEFAULT-SERVER
|
|
|
MULTINET_XGATEWAY_DEBUG_LEVEL
Defines the debugging level of the X11-Gateway, and enables broadcast of debugging messages to NETWORK class operator terminals. Set by system manager. |
|
|
MULTINET_XGATEWAY_DECNET_nn_HOSTNAME
Defines the TCP/IP X Windows server host name for the local DECnet X server number nn. Set by system manager. |
|
|
MULTINET_XGATEWAY_DECNET_nn_SERVER
Defines the remote TCP/IP X Windows server number for the local DECnet X server number nn. This logical name is optional. The default is 0. Set by system manager. |
|
|
MULTINET_XGATEWAY_TCPIP_nn_HOSTNAME
Defines the DECnet X Windows server host name for the local TCP/IP X server number nn. Set by system manager |
|
|
MULTINET_XGATEWAY_TCPIP_nn_SERVER
Defines the remote DECnet X Windows Server number for the local TCP/IP server number nn. This logical name is optional. The default is 0. Set by system manager. |
|
|
SSH_DIR
Points to the directory where the SSH1 configuration, master server log file, and host key files are kept. Normally, this is MULTINET_SPECIFIC_ROOT:[MULTINET]. It is defined in START_SSH.COM. |
|
|
SSH_EXE
Points to the directory where SSH executables are kept. Normally, this is MULTINET_COMMON_ROOT:[MULTINET]. It is defined in START_SSH.COM. |
|
|
SSH_LOG
Points to the directory where the log files are kept. Normally, this is MULTINET_COMMON_ROOT:[MULTINET]. It is defined in START_SSH.COM. |
|
|
SSH_TERM_MBX
Mailbox used by SSHD_MASTER to receive termination messages from SSHD daemon processes. Do not change this logical name. This is created by the SSHD_MASTER process. |
|
|
SSH2_DIR
Points to the directory that contains SSH2-specific files on the system. Normally, this is MULTINET_SPECIFIC_ROOT:[MULTINET.SSH2]. |
|
|
TCPIP$INET_HOSTADDRn
One logical for each interface with the IP address for that interface. |
|
|
TCPIP$SCTP_SHR
Set to the location of an image with entry points matching the image of SCTP library routines on TCP/IP Services. |
|
|
UCX$INET_HOST, TCPIP$INET_HOST
Set to include the host name of the primary interface automatically. |
|
|
UCX$INET_HOSTADDR, TCPIP$INET_HOSTADDR
Set to contain the IP address of the primary interface automatically. |
|
|
UCX$ACCESS_SHR, TCPIP$ACCESS_SHR
Set to the location of an image with entry points matching the image on TCP/IP Services. |
|
|
UCX$BIND_DOMAIN, TCPIP$BIND_DOMAIN
Set automatically to the default domain for name resolution. |
|
|
UCX$BIND_SERVER000, TCPIP$BIND_SERVER000
Set automatically to the first name server defined. There may be up to 4 name servers defined with the logicals TCPIP$BIND_SERVER001, TCPIP$BIND_SERVER002, TCPIP$BIND_SERVER003. |
|
|
UCX$DEVICE, TCPIP$DEVICE
Defined automatically to be _BG0: which is a device compatible with TCP/IP Services. |
|
|
UCX$INET_DOMAIN, TCPIP$INET_DOMAIN
Set to include the domain of the primary interface automatically. |
|
|
UCX$IPC_SHR, TCPIP$IPC_SHR
Set to MULTINET:UCX$IPC_SHR.EXE, which is the location of an image containing entry points that are compatible with the image in TCP/IP Services. |
|
|
UCX$RPC, TCPIP$RPC
Set to MULTINET_COMMON_ROOT:[MULTINET.INCLUDE.RPCXDR], which is the location of an image containing entry points that are compatible with the image in TCP/IP Services. |
|
|
UCX$RPCXDR_SHR, TCPIP$RPCXDR_SHR
Set to MULTINET:UCX$RPCXDR_SHR.EXE, which is the location of an image containing entry points that are compatible with the image in TCP/IP Services. |