Previous Topic

Next Topic

Book Contents

Book Index

Special global IOAGATE parameters

Certain IOAGATE parameters cannot be set by means of ICE. You can only set these special IOAGATE parameters by adding them manually to the GATEWAY section of ECAPARM.

Table 42 Special CCM parameters

Parameter

Description

MAXNOSIB

The maximum number of Service Instance Blocks (SIBs) dedicated by IOAGATE.

IOAGATE dedicates a Service Instance Block (SIB) for each incoming or outgoing message. For that purpose, IOAGATE pre-allocates a pool of SIBs.

The default number of SIBs in the pool is 10,000, and the maximum is 32,767. You can use this parameter to increase the number of pre-allocated SIBs.

The default number is usually adequate for all purposes, and BMC recommends that you do not increase it without first taking steps to ensure that there is no SIB accumulation problem that could be solved without increasing the number.

SELFTEST

The interval between IOAGATE internal validation tests.

At regular intervals, IOAGATE performs internal tests to validate various control blocks. By default, these tests are performed every 3 seconds. By means of this parameter, you can change the length of the intervals between tests.

Valid values are from 1 through 300 seconds.

These tests involve only small increases in computer overhead. BMC recommends that you do not increase this value unless it is essential to reduce IOAGATE computer consumption to an absolute minimum even when IOAGATE is idle.

RECVTEST

The interval between IOAGATE internal scans to check if recovery action is needed.

At regular intervals, IOAGATE performs internal scans to check whether any action is required to recover failed application server address spaces or subtasks. By default, these tests are performed every 5 seconds. By means of this parameter, you can change the length of the intervals between tests.

Valid values are from 1 through 300 seconds.

Increasing the value of this parameter can slightly decrease computer overhead.

TRACE

This parameter is for use in tracing IOAGATE initialization on request by BMC Customer Support.

Valid values are:

  • PARM – For tracing IOAGATE processing of ECAPARM during initialization.
  • MAP – For tracing IOAGATE processing of the network map during initialization.
  • NO – No tracing is performed during initialization in relation to either ECAPARM or the network map. Default.

Parent Topic

Step 20.2 – Configure IOAGATE parameters