BASEMAN Configuration Syntax

XPNET Manager, which is part of the Prognosis for ATM/POS product suite, uses the BASEMAN Configuration to obtain information about the XPNET system and the particular NCP (Netware Core Protocol) server that it is to communicate with. The data elements are required for communication via SERVERCLASS_SEND to the NCP server and to allow access to XPNET information.

Details of the syntax required for the Prognosis BASEMAN Configuration is shown below:

SUBSYS BASEMAN
[MIN-INT (<n>)]
[MIN-STATS-INT (<n>)]
[STATUS-OPTIMIZED ({Y|N})]
[ADD RES-NODE (<resource-node>, <pathmon-name>, <serverclass-name>)]

Syntax Elements

MIN-INT

Specifies the minimum length of time in seconds to perform one cycle of the Prognosis XPNET Manager data collection. This statement can occur only once in the configuration. The collection of data will be spread out across the specified interval. Intervals are not aligned to a wall clock time.

Understanding that Prognosis gets its information from XPNET by sending Open Network Control Facility (ONCF) requests to the Network Control Point (NCP) server is important since each send requires I/O from the NCP server. If MIN-INT is set too low, the NCP server will put an excessive burden on the system trying to respond to all the requests. The interval should not be set at less than 5 minutes, preferably more.

MIN-STATS-INT

Specifies the minimum length of time in seconds to perform one cycle of the Prognosis XPNET Manager STATISTICS data collection. This statement can occur only once in the configuration. It is recommended to set this parameter to a value higher than the MIN-INT value. If MIN-STATS-INT is not specified, the value is set to the MIN-INT value. The collection of data will be spread out across the specified interval. Intervals are not aligned to a wall clock time.

STATUS-OPTIMIZED

Determines if the Prognosis XPNET Manager should run in optimized mode or not, Y (yes) or N (no). Running in optimized mode means that the collector uses the facility to send 'group'-commands for the STATUS data collection rather than sending the commands individually to each object. The default is Y (yes). See the Configuration topic and the Optimization Configuration Summary topic in the Prognosis for Payments guide for further details about the optimization settings.

ADD RES-NODE

<resource-node>

Specifies the XPNET resource node to be used for data collection.

<pathmon-name>

Identifies the pathway system that contains the NCP server process.

<serverclass-name>

This is normally set to "SERVER-NCP" for the NCP server under pathmon.

The NCP server is actually a Pathway server and Prognosis XPNET Manager needs information about the server class and pathway system information in order to establish a connection. The <pathmon-name> parameter is the process name assigned to the PATHMON process. This variable identifies the pathway system that contains the NCP server process. Commands from Prognosis XPNET Manager are passed through the NCP server process to the XPNET process. The ADD RES-NODE statement can appear multiple times in the configuration, see the 'Multiple XPNET Resource Nodes' section for details.

Multiple XPNET Resource Nodes

The BASEMAN Configuration is designed to allow for more than one XPNET resource node to be queried. To add another XPNET resource node include an additional ADD RES-NODE statement with the appropriate field values for the extra node. An example of such a configuration is shown below.

SUBSYS BASEMAN
MIN-INT (60)
ADD RES-NODE (P1A^GATE,$TPMN, SERVER-NCP)
ADD RES-NODE (P1B^GATE,$TPMN, SERVER-NCP)
For each resource node added to the BASEMAN Configuration, a corresponding Prognosis Configuration entry needs to be made in order to allow Prognosis access to the NCP server. See PASSWORDS Configuration Syntax for details.
Provide feedback on this article