# BASEstartm Classic DAS
for OMNItm Software
Installation and User's Guide

Previous | Contents | Index

## 2.3.3 Tuning ILAN$DEVSRV

The installation procedure provides a replacement for the ILAN startup file, ILAN$SYSTEM_STARTUP.TEMPLATE. The new file has been provided because the ILAN$DEVSRV image using the DAS for OMNI software needs additional quotas and privileges. The values used in the provided startup file are valid for a typical configuration and may be more or less than is actually required for your installation.

Note If quotas are not set properly, it is likely that the ILAN$DEVSRV process will ACCVIO or otherwise fail with very little diagnostic information provided. If you find that the ILAN$DEVSRV process is ACCVIOing soon after enabling devices or soon after startup, monitor the process using SHOW PROCESS/QUOTA/ID=XXXXXXXX to determine which quota the process is running low on.

SYSGEN parameters may also need adjusting. Parameters which may need modifying include the following:

- CHANNELCNT
- VIRTUALPAGECNT

BASEstar Classic parameters may also need adjusting, depending on the number of devices configured. Parameters which may need modifying include the following:

- ILAN$MAX_DEVICES
- ILAN$MAX_OUT_REQUESTS
- ILAN$MAX_SPT_REQUESTS
- ILAN$MAX_DSEC_SIZE

See BASEstar Classic Configuration and Tuning Guide for details on changing BASEstar Classic parameters.

## 2.3.4 Defining OMNI Constants

A BASEstar Classic parameter is used to configure the maximum number of OMNI devices that can be created. This parameter is created as part of the DAS installation. To change the value of this parameter, change the value using the BASEstar Classic CLI. Then stop and restart BASEstar Classic to to enable the DAS to use the new parameter value. Table 2-8 lists the default and maximum value for this parameter.

Table 2-8 BASEstar Classic Parameters
Parameter | Default Value | Max Value
--- | --- | ---
ILAN$OMNI_MAX_DEVICES | 64 | 500

## 2.3.5 Setting the SPT Block Parameter

The ILAN$MAX_SPT_REQUESTS parameter specifies the total number of blocks that can be allocated in the SPT (support) global section. DASes use blocks in the global section for storing data structures and for doing device I/O. The SPT global section is sized by calculating the number of SMALL, MEDIUM, LARGE and EXTRA LARGE blocks that the section should contain. Some blocks remain for the life of a device and some are allocated and deallocated for each I/O operation. Table 2-9 shows the static blocks of each size that are used by the DAS.

Table 2-9 SPT Static Block Sizes
Block Size | Quantity1 | Block Type
--- | --- | ---
MEDIUM | 2 | Device
SMALL | 1 | Device 2
| 1 | Unsolicited point 2
| 1 | DAS

1Quantity is quantity per device, per point, etc.
2Only created if the device is marked "unsolicited".

Table 2-10 shows the dynamic blocks of each size that are used by the DAS. These blocks are created and deleted as the device does I/O. The DAS also allocates and deallocates virtual memory to store control information when doing device I/O.

Table 2-10 SPT Dynamic Block Sizes
Block Size | Quantity1 | I/O Type
--- | --- | ---
SMALL | 1 | Any

1Quantity is quantity per I/O.

The size of the SPT global section can be tuned by changing the percentage of each kind of block that is created. Refer to the BASEstar Classic Configuration and Tuning Guide for instructions on changing the percentage of each size of block that is created in the global section.

## 2.3.6 Setting Up Shop Floor Equipment

To set up your shop floor equipment, see the documentation for your specific MMS, SINEC-S7, SINEC-AP or SINEC-H1 compliant device.

When configuring MMS devices be sure to note the PSAP, SSAP, TSAP and NSAP.

When configuring SINEC-S7, SINEC-AP or SINEC-H1 devices be sure to note the TSAP.

Previous | Next | Contents | Index