|
|
| Field Name |
Format | Platform | Default | Description |
| License Authorization Fields | You should enter these fields exactly as they are supplied to you on the "PicLan-IP Authorization Sheet". | |||
| AUTH | 0 - 4294967295 | all | req | This is a generated "secret code" number that is generated for your system. |
| WEB BW AUTH | 0 - 10000 | all | req | This is the licensed Coyote Web Server bandwidth. You can set the actual bandwidth to any value up to this licensed bandwidth. |
| OTH BW AUTH | 0 - 1000 | all | req | This is the licensed PicLan-IP "other" server bandwidth. The other bandwidth is used for SMTP/POP3 mail, HTTP client, and sockets API functions. |
| AUTH DATE | mm/dd/yyyy | all | req | This is licensed end-date after which time PicLan-IP will revert to "demo mode". The field is specified in MultiValue date format and can be in any format that the OCONV(...,'D') function will process. |
| PICLAN-IP SN | 0 - 99999 | all | req | This is the assigned PicLan-IP software serial number. |
| AUTH OPTIONS | 0 - 255 | all | 0 | This fields specifies PicLan-IP optional components. It is a binary fields on up to 8 bits. Currently, only the first three bits are in use. |
| TELNET LIC | 0 - 1000 | native | 0 | This is the number of concurrent inbound telnet users licensed to access native hosts. |
| POP3 LIC | 0 - 1000 | all | 0 | This is the number of configurable POP3 mailboxes. |
| Bandwidth Settings | These fields are used to set actual, as opposed to licensed, bandwidth settings. You can use any bandwidth setting desired up to the licensed value. If you enter a value here that is higher than the licensed value, then the licensed value will take precidence. | |||
| WEB BW | 0 - 10000 | all | req | The actual outbound bandwidth for the web server |
| WEB BW SEC | 0 - 5 | all | req | The burst length for the web server in seconds. This allows the web server to instantaniously generate 'n' number of seconds of output before the bandwidth limiter kicks in. This makes the web server appear infinately fast on a LAN connection without having to license very large PicLan-IP bandwidths. |
| OTH BW | 0 - 1000 | all | req | The actual output bandwidth for the other potions of the PicLan-IP server. |
| OTH BW SEC | 0 - 5 | all | req | The burst length for the other server in seconds. |
| IP Address Settings | These settings are used to establish IP addressing parameters for PicLan-IP. On MultiValue hosts running on top of Windows NT or Unix, the only applicable field is the default IP address. On native hosts, these fields control the IP routing table and network masks as well. | |||
| ADDR | ###.###.###.### | all | req | The default IP address for the host |
| ADDR (addl entries) | ###.###.###.### | native | Native hosts can list a total of 50 IP addresses for virtual hosting applications. All addresses must be in the same sub-net structure. | |
| MASK | ###.###.###.### | native | req | The IP mask for the local network. |
| DEFAULT GATEWAY | ###.###.###.### | native | The default gateway IP address. | |
| ROUTE | addr mask gw_addr | native | You can enter multiple route entries to build a static IP routing table. Most sites that only have a single router do not need a routing table and the default gateway field can be used instead. You can enter up to 50 route entries. | |
| DNS Entries | These entries are used to control how PicLan-IP queries external DNS servers. DNS access is required for most email functions and is also used with other functions such as the HTTP cleint API. | |||
| DNS | ###.###.###.### | all | The address of DNS servers to query. If more than one server is listed, then each server will be queried in sequence until one answers or the request times out. | |
| DNS WAIT | hh:mm:ss | all | 00:00:02 | The amount of time to wait for an answer to a DNS query. |
| DNS RETRY | ### | all | 4 | The total number of queries to make to each configured DNS server. |
| DNS TIMEOUT | hh:mm:ss | all | 00:00:30 | The total amount of time to wait for a reply. |
| DNS CLEANUP | hh:mm:ss | all | 01:00:00 | The amount of time between periodic scans of the DNS cache files to delete old entries. |
| Time Zone Parameters | This field is used to set the local time zone. Currently, PicLan-IP does not automatically adjust to daylight savings time, so this field will need to be manually adjusted when daylight savings time starts and stops. | |||
| TZ ZONE | -nnnn | all | -0700 | The default is the value for Pacific Daylight time. |
| Mail Parameters | These fields control the behaviour of the SMTP mail server. | |||
| LOCAL HOST NAME | domain name | all | The domain name of this host. This is used when sending SMTP messages. Some SMTP relay agents require that this is a valid domain name. | |
| MAIL HOST | domain name or IP address |
all | opt | The name or IP address of the SMTP relay server that the PicLan-IP mail server is to use. If you leave this field blank, then the PicLan-IP mail server will send it's mail directly to the recipient by resolving DNS MX and A records. |
| MAIL TIMEOUT | hh:mm:ss | all | 00:10:00 | The amount of time that a mail stream can sit idle before timing out. |
| MAIL LONG TIMEOUT | hh:mm:ss | all | 00:20:00 | The total amount of time that a mail stream can run even if not idle before timing out. |
| MAIL CONN OUT | ### | all | 4 | The maximum number of concurrent outbound SMTP connections that PicLan-IP mail functions will open. |
| MAIL RETRY TIME | hh:mm:ss | all | 00:20:00 | The length of time between failed mail retry attempts. |
| MAIL MAX TIME | hh:mm:ss | all | 120:00:00 | The maximum amount of time that a message will be retried for. |
| MAIL WARN TIME | hh:mm:ss | all | 24:00:00 | The amount of time before a bounce warning message will be generated. |
| MAIL WARN MAX | hh:mm:ss | all | 24:00:00 | The maximum amont of time that a bounce warning message will be attempted to be delivered. |
| Process Configuration | These fields are used to configure the process that PicLan-IP uses. | |||
| SUPERVISOR | ### or * | all | req | The port number for the PicLan-IP "supervisor" process. There is only a single supervisor process. You should specify an asterisk "*" to run this process on an auto-port-assigned phantom on those systems that support the Z or PHANTOM command. |
| PROCESS | ### or # | all | req | The port number for each PicLan-IP "thread" process. You can specify up to 50 thread processes. Most systems should only specify 2 to 4 thread processes unless you have very specific application reasons requiring more than this. |
| SUPERVISOR POLL | hh:mm:ss | all | 00:00:10 | This is the amount of time between watchdog check operations. |
| SUPERVISOR TIMEOUT | hh:mm:ss | all | 00:01:30 | This is the amount of time that a thread process can run without updating it's run state. If a process takes longer than this period of time then the supervisor process will assume it is hung and log it off. |
| INITSUB | all | The name of a cataloged subroutine that is to be called when each thread process starts. This is intended to allow application code to initialize named common areas including such allowing applications to pre-open data files. | ||
| PLZ CLEANUP SUP | 0 or 1 | all (2.0.0.175 and later) | 0 | If set to 1, the supervisor, and not a thread process will cleanup old PLZ states in the PLIP.CTRL,APP.STATES file. This can eliminate a process hang on systems with very large numbers of active states. |
| System Configuration Parameters | These parameters are used to set configuration entries. They tend to be very platform dependent. | |||
| CONN | ### | native | 200 | Specifies the number of connection control blocks to allocate in the native PicLan-IP TCP/IP driver. |
| Pre version 2.0.0.170 | ||||
| DLL PATH | drive:path | WinNT | Points to the PicLan-IP
PLIP.DLL support DLL path: mvBase - C:\MVBASE\PLIP D3/NT - C:/D3DEV |
|
| DAEMON COMMAND | Unix | Start the PicLan-IP
plip_d daemon. D3/Linux - Z plip_d -z >> /var/log/plip_d_log & |
||
| Post version 2.0.0.170 | ||||
| HOST TP | NAT, WIN, UNIX | all | req | |
| COMM PATH | ...a system path ... | win, unix | req | For systems that use the plip.dll, the directory path where the DLL is located. For systems that use unix "pipes", the directory path where pipe files are located. |
| COMM ADDR | ... a system path ... | unix | req | For systems that use TCP/IP comms to the plip_d daemon, the address to connect to. |
| COMM TP | DLL, PIPE, TCP | win,unix | req | The type of comms in use to the plip_d daemon or DLL |
| Inbound TELNET Configuration | These fields are only used on native systems with inbound TELNET access configured. | |||
| TELNET PORT | ### or ###-### | native | The PicLan-IP ports that are to be reassigned to inbound TELNET service. | |
| TELNET LISTEN | more | native | See the inbound TELNET configuration page for more information. | |
| Coyote Web Server HTTP Configuration | ||||
| WWW TIMEOUT | hh:mm:ss | all | The amount of time to allow a quiet HTTP connection to remain persistent. | |
| WWW CACHE TIMEOUT | hh:mm:ss | all | The amount of time between access to re-validate content source. | |
| HTTP DIR | more | all | The definition for virtual web directories. See the Coyote configuration page for more information. | |
|
|