Add IBM i Systems and Runtime Parameters - ironstream_for_micro_focus_universal_discovery - 6.3

Ironstream for Micro Focus® Universal Discovery for IBM i Administration

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream for Micro Focus® Universal Discovery
Version
6.3
Language
English
Product name
Ironstream for Micro Focus Universal Discovery for IBM i
Title
Ironstream for Micro Focus® Universal Discovery for IBM i Administration
Copyright
2021
First publish date
2007
ft:lastEdition
2023-08-23
ft:lastPublication
2023-08-23T16:21:59.136387

The Task Manager will define IBM i systems to be discovered.

  1. Start the Task Manager: Start->Programs->EView Technology->EView 400->Task Manager

  2. Select Add Node and enter the fully qualified name of the IBM i system to be discovered. The name must be able to be resolved through the existing name service (for example, DNS or an entry in the Windows’ system32\drivers\etc\hosts file).

  3. Select the new node name in the list and click Edit Node to modify any of the configuration parameters as explained below (or hovering the mouse pointer over the parameter name in the window).

Figure 3-13: Ironstream Configuration Parameters

The node configuration parameters are described in Table 3-1. Many of the parameters listed are not used when the agent is being used only for DDMA discovery. All parameters are listed as they are required for compatibility when the agent is used for Operations Management. In environments where the agent is used for both Operations Management and discovery, the agent parameters should ONLY be distributed from the Operations Management server.

Table 3-1: Ironstream Node Parameters

Parameter

Description

Valid Values

EV400_ADDMSG_FIELDS

(IS NOT USED FOR DISCOVERY)

Indicates whether Ironstream will send the Program Name and Message Type fields in the messages that are sent to the OMW.

YES – The Ironstream message server will send the “Program Name” and “Message Type” fields in its messages to the OMW. These fields were added in the EV/400 Version 2.0 and will need to be accommodated in any existing template conditions that were written for Version

1.0 of the product.

NO – Use this option if you are using message template conditions from EV/400 Version 1.0 and do not wish to modify those existing templates to utilize the new fields.

Default - NO

EV400_AS400_ADDR

Fully qualified network name of IBM i where the Ironstream agent component is installed.

Name of IBM i managed node Default - None

EV400_AS400_CMD_PORT

TCP port number assigned to the Ironstream Command Server process.

Any unused port number on the IBM i Agent between 1025 and 65535.

Default - 8001

EV400_AS400_CMD_RSP_PO RT

TCP port number assigned for communication between the Ironstream Message Server Process and Command Server Process

Any unused port number on the OMW server between 1025 and 65535.

Default – 8003*

EV400_AS400_MSG_PORT

TCP port number assigned to the Ironstream Master Message Server process.

Any unused port number on the IBM i Agent between 1025 and 65535.

Default - 8000

EV400_AS400_SERVER_POR T

A TCP port number reserved for inter-process communications on the IBM i Agent.

Any unused port number on the IBM i Agent between 1025 and 65535.

Default - 8002

EV400_CMD_CLIENT_PORT

A TCP port number used by the Command Server process to communicate with the Master Message Server process. This port number must be unique on the OMW server where the Command Server and Master Message Server processes are running.

Any unused port number on the OMW server between 1025 and 65535.

Default – 8004*

EV400_CMD_SERVER_ADDR

The name of the OMW server where the Command Server process is to run.

A Windows server name. Default - The OMW server name

EV400_CMD_TIMEOUT

The amount of time to wait for an command response (in seconds).

An integer greater than or equal to 1 (second).

Default - 30

EV400_CONF_FTP_USER

A user ID on the IBM i Agent that has the authority to store configuration files in the EVIEW library. (See note on page 11.)

If this field is left blank, the configuration utility will prompt you for a user ID when it is making its ftp connection to the IBM i.

An IBM i user ID (up to 10 characters) or blank.

Default - ov400user

EV400_DISTRIBUTION_MET HOD

The method to use for distributing configuration data to the IBM i LPAR.

FTP – Use ftp for distribution.

HOST – Use IBM i Host Services. The IBM i Host Services job must be running on the IBM i Agent.

Default - FTP

EV400_LICKEY

License key for the managed node.

To obtain a license key, contact Precisely Support. (See the Installation Guide.)

Valid license key Default - None

EV400_MONITOR_QHST

(IS NOT USED FOR DISCOVERY)

Indicates whether the Ironstream IBM i Agent should monitor for messages that are sent to the IBM i QHST system history log. If set to “YES”, then verify that the EV400_QHST_MON_FREQ field is greater than 0.

YES or NO

Default - YES

EV400_MON_AUDJRNL

(IS NOT USED FOR DISCOVERY)

A list of two-character entry types from the QAUDJRN that should be forwarded from the IBM i Agent.

Entry types are separated by commas.

See IBM i documentation (such as the IBM i Security Reference) or Appendix E for descriptions of journal entry types.

AD, AF, AU, CA, CD, CO, CP, DO, DS, NA,

OW, PA, PG, PW, ST, SV, VA, VP, VU, ZC, ZR

ALL – All of the above NONE – None of the above Default - NONE

EV400_MON_RESOURCES

(IS NOT USED FOR DISCOVERY)

Indicates whether the Ironstream IBM i Agent should monitor the status of IBM i resources (lines, controllers, and devices).

This function is not used for discovery and should always be set to "NO".

YES or NO

Default - NO

EV400_MSG_DISTRIB

(IS NOT USED FOR DISCOVERY)

Should the IBM i Agent send its collected messages to all OMW servers that are in contact with it? (If “NO”, then specify in the EV400_PRIMARY_SERVER field

which OMW server is the primary recipient of messages.)

YES – Send unsolicited IBM i messages to all Ironstream servers that are in contact with this agent.

NO – Send unsolicited messages only to the primary server.

Default - YES

EV400_MSG_SERVER_ADDR

The name of the Windows server where the Master Message Server process is to run.

A Windows server name Default - The OMW server

EV400_PATH

(IS NOT USED FOR DISCOVERY)

The Ironstream installation directory on the OMW server.

Ironstream home directory

Default - \Program Files\EView Technology\EView 400\

EV400_PERF1

(IS NOT USED FOR DISCOVERY)

Specifies whether the performance gathering function will be activated on the IBM i Agent to gather the data for performance group 1. See Appendix D for the list of metrics collected in group 1.

YES – Activate the performance gathering function on the IBM i Agent.

NO – Do not activate performance data gathering for group 1.

Default - NO

EV400_PERF1_INT

(IS NOT USED FOR DISCOVERY)

The interval, in minutes, at which group 1 performance data is collected on the IBM i Agent and forwarded to the OMW server.

This field is only needed if EV400_PERF1 is set to "YES".

An integer greater than or equal to 1 (minute).

Default - 5

EV400_PERF2

(IS NOT USED FOR DISCOVERY)

Specifies whether the performance gathering function will be activated on the IBM i Agent to gather the data for performance group 2.

See Appendix D for the list of metrics collected in group 2.

YES – Activate the performance gathering function on the IBM i Agent.

NO – Do not activate performance data gathering for group 2.

Default - NO

EV400_PERF2_INT

(IS NOT USED FOR DISCOVERY)

The interval, in minutes, at which group 2 performance data is collected on the IBM i Agent and forwarded to the OMW server.

This field is only needed if EV400_PERF2 is set to "YES".

An integer greater than or equal to 1 (minutes).

Default - 30

EV400_PRIMARY_SERVER

(IS NOT USED FOR DISCOVERY)

The fully qualified name of the primary OMW server to receive messages from this agent.

Although multiple OMW servers may be connected to the IBM i Agent at one time, only the server named here will receive unsolicited IBM i messages.

This field is only necessary when the EV400_MSG_DISTRIB

parameter is “NO”.

An Ironstream server name Default - null

EV400_QHST_MON_FREQ

(IS NOT USED FOR DISCOVERY)

Frequency (in seconds) that the Ironstream agent collects new messages from the QHST system history log.

This field is only necessary when the EV400_MONITOR_QHST

parameter is “YES”.

An integer greater than or equal to 1 (seconds)

Default - 5

EV400_USE_MWA

(IS NOT USED FOR DISCOVERY)

Indicates whether OVPA is installed and being used for storing collected IBM i performance data.

YES – OVPA is installed and being used. NO - OVPA is not installed.

Default - NO

EV400_WORK_AREA

(IS NOT USED FOR DISCOVERY)

Specifies where Ironstream places temporary work files on the OMW server.

Any existing directory on the OMW server

Default - \temp

EV400_VP400CS_TRACE

Set tracing level for the command server (ev400cs).

Multiple values can be added together in hexadecimal.

0 - No tracing output enabled 0001 - general program trace enabled 0002 - internal tracing enabled

0004 - program detail tracing enabled 0008 - warning messages enabled 0010 - error tracing enabled

0020 - dump output enabled 0040 - loop tracing enabled 0080 - verify tracing enabled

Default - 0

EV400_VP400MMS_TRACE

Set tracing level for the master message server (ev400mms).

Multiple values can be added together in hexadecimal.

0 - No tracing output enabled 0001 - general program trace enabled 0002 - internal tracing enabled

0004 - program detail tracing enabled 0008 - warning messages enabled 0010 - error tracing enabled

0020 - dump output enabled 0040 - loop tracing enabled 0080 - verify tracing enabled

0100 - log messages sent to OMW 0200 - log performance records

Default - 0

EV400_VP400HOSTCMD_TRA CE

Set tracing level for the host command client ev400hostcmd process.

Multiple values can be added together in hexadecimal.

0 - No tracing output enabled 0001 - general program trace enabled 0002 - internal tracing enabled

0004 - program detail tracing enabled 0008 - warning messages enabled 0010 - error tracing enabled

0020 - dump output enabled 0040 - loop tracing enabled 0080 - verify tracing enabled

Default - 0

EV400_EVCMSG_TRACE

Set tracing level for the agent message TCP task (EVCMSG).

Multiple values can be added together in hexadecimal.

0 - No tracing output enabled 0001 - general program trace enabled 0002 - internal tracing enabled

0004 - program detail tracing enabled 0008 - warning messages enabled 0010 - error tracing enabled

0020 - dump output enabled 0040 - loop tracing enabled 0080 - verify tracing enabled

Default - 0

EV400_EVCHCI_TRACE

Set tracing level for the agent message transfer process (EVCHCI)

  1. - disables tracing

  2. - enables tracing

Default - 0

EV400_EVC050_TRACE

Set tracing level for the agent command processor (EVC050)

  1. - disables tracing

  2. - enables tracing

Default – 0

EV400_EVCQSCAN_TRACE

Set tracing level for the agent message queue monitor (EVCQSCAN)

  1. - disables tracing

  2. - enables tracing

Default - 0

EV400_EVPERFM_TRACE

Set tracing level for the agent performance monitor process (EVPERFM)

  1. - disables tracing

  2. - enables tracing

Default - 0

EV400_EVCCTL_TRACE

Set tracing level for the API interface process (EVCCTL)

0 - disables tracing

1 - enables tracing

Default - 0

EV400_EVC070_TRACE

Set tracing level for the agent resource monitor (EVC070)

0 - disables tracing

1 - enables tracing

Default - 0

EV400_EVCCMD_TRACE

Set tracing level for the agent command TCP process (EVCCMD)

0 - disables tracing

1 - enables tracing Default - 0

EV400_EVHSTPGM_TRACE

Set tracing level for the agent history log (QHST) monitor

0 - disables tracing

1 - enables tracing Default - 0

EV400_VP400MMS_LOGSIZE

Set the maximum log size in 1K increments for the master message server (ev400mms)

1-99999 (kilobytes)

Default - 3000

EV400_VP400CS_LOGSIZE

Set the maximum log size in 1K increments for the command server (ev400cs)

1-99999 (kilobytes)

Default - 3000

EV400_CMDRSP_CODEPAGE

Set the code page to be used for converting command responses.

A value of “UTF-8” indicates that command output is not converted using any codepage. UTF-8 is the expected character set for the OM Windows tools output window.

Any codepage supported by OM and Windows such as

1252 – Latin I

932 – Japanese Shift-JIS 936 – Simplified Chinese 949 – Korean

Default – UTF-8

EV400_CMDRSP_ALT_CODE PAGE

Set an alternate code page to be used for converting command responses when EV400_CMDRSP_CODEPAGE is

set to UTF-8. This parameter is only used with the ev400hostcmd option 81.

If EV400_CMDRSP_CODEPAGE

is not set to UTF-8, this parameter is ignored.

Any valid windows code page, but in most cases the default value of 437 would be used.

Default - 437

EV400_OVOMSG_CODEPAGE

(IS NOT USED FOR DISCOVERY)

Set the code page to be used for converting messages that are sent to the OM message interface.

Any codepage supported by OM and Windows.

1252 – Latin I

932 – Japanese Shift-JIS 936 – Simplified Chinese 949 – Korean

Default - 1252

EV400_NLS_CCSID

Set the CCSID for the language library that is being used as the subsystem library for the Ironstream IBM i Agent subsystem.

Any CCSID supported on IBM i. Some typical values are:

QSYS2924 English – 37 QSYS2928 French – 297 QSYS2929 German – 273

QSYS2931 Spanish – 284 QSYS2932 Italian – 280 QSYS2962 Japanese – 5026 QSYS2986 Korean – 933

QSYS2989 Simplified Chinese – 935

Default - 37

* This port number will be incremented automatically for new nodes that are added so that the port numbers remain unique on the server.

  1. Save the parameters for this agent. The Ironstream Task Manager will save the parameters locally on the Probe server.

(Multiple node definitions may be edited at once to edit the same parameters that are not required to be unique. Select the node names while holding down the Shift key then click the Edit Node(s) button.)

  1. Select any nodes in the list of defined nodes that have the “Distributed?” box marked with a red slashed circle and click the Distribute... button to send the configuration parameters to the IBM i Agents. Multiple nodes may be selected at one time by holding down the Shift key while selecting the node names. If the EV400_CONF_FTP_USER field for a node has not been filled in, you will be prompted to enter the user ID.

Note: The IBM i User ID that is used in the distribution process must have the authority to create and modify the configuration objects in the EVIEW library and have change authority over the nine configuration objects in the library: EVCMDAUD, EVF020, EVF021, EVJOBFILT, EVPARMS, EVMSGQCFG, EVFILTRSPC, EVQCFGSPC, and EVHSTFLSPC.

  1. Select the line for the added node and click the Start button to start the Ironstream server processes for the IBM i node. (The processes on the agent side will be started in Phase 2.)

Note: Whenever a node’s configuration parameters are changed using the Add Node or Edit Node functions of the Node Configuration program, the Distributed column will be marked to remind you that there are changes that need to be distributed to the IBM i Agent.

(If a node is deleted using the Delete Node button, the node will be removed from the Ironstream list of defined nodes, but it will need to be manually removed from the OMW list of managed nodes.)