HP LCS60 manual Initial Parms Field, Table A-3 Program Arguments Specification

srvtab

Initial Parms Field

The initial parms field (fixed program arguments field) of a server table entry speci- fies the initial (fixed) arguments for the invoked program. The colon-separated arguments from the server table will be passed to the invoked program starting as the zero argument. If the flag is present in the server table entry, additional arguments obtained from the incoming remote execution channel will follow the initial arguments when the program is invoked.

Initial arguments may consist of, or be embedded with, one or more tokens (sometimes referred to as special codes) that may be used to substitute information from the dialstring. Each token is a two-character string consisting of a percent sign (%), followed by a single alphabetic character. Invalid tokens are silently removed and are not expanded.

Table A-3 summarizes the values and descriptions of the allowed substitution tokens. Since some older versions of the Datakit II VCS common controller do not support certain features, the substitution string may turn out to be null.

Table A-3: Program Arguments Specification
________________________________________________________________________
⎜		⎜	Description	⎜
_Specification		⎜		⎜
⎜
⎜	%b	⎜ The baud rate of the calling terminal. This token is not expanded if the incoming		⎜
⎜		⎜ call did not originate from a port providing baud rate information. (For example,		⎜
⎜		⎜ hosts currently do not provide this.)		⎜
⎜	%c	⎜ Originating channel number of the call being serviced.		⎜
⎜	%d	⎜	The dialed server name (for example, host). This does not include the period or	⎜
⎜		⎜		⎜
_		⎜	anything after it.	⎜
⎜
⎜	%e	⎜ The service field of the dialstring (for example, pupu).		⎜
⎜	%f	⎜		⎜
⎜		⎜ The originating-group name of the caller (for example, lc/sporty/hotrod).		⎜

Appendix A

Issue 3 A-7