Subtasks - ironstream_for_micro_focus_universal_discovery - 7.4

Ironstream for Micro Focus® Universal Discovery for IBM Z® Administration

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream for Micro Focus® Universal Discovery
Version
7.4
Language
English
Product name
Ironstream for Micro Focus Universal Discovery for IBM Z
Title
Ironstream for Micro Focus® Universal Discovery for IBM Z® Administration
Copyright
2022
First publish date
2007
ft:lastEdition
2023-08-23
ft:lastPublication
2023-08-23T16:22:42.216801
  • The OSI subtask will accept various requests from the Ironstream UD Probe server for information concerning the system, including CPU and job queue usage.

    • Optional Task, but required if any vp390hostcmd type 46 commands will be issued.

    • Status should be UP if configured.

  • The TCP subtask is used to connect the agent to the Master Message Server and the Command Server processes on the Ironstream UCMDB Probe server. Multiple TCP subtasks are allowed.

    • Required Task

    • Status should be UP. A capital "S" appears at the end of the SHOW STATUS line for "TCP" if both port connections are established.

  • The CMD subtask sets up the extended console used for MVS command inputs to VP390.

    • Optional Task, but required if any commands are going to be sent from the Ironstream UD Probe server back to the mainframe.

    • Status should be UP if configured.

To determine if messages/commands are flowing from or to the individual subtasks issue the following command:

F VP390,SHOW FLOW

The INFLOW and OUTFLOW columns can be monitored to check if messages are flowing into the agent or out of the agent subtasks. Note that the OUTFLOW number for the TCP subtask(s) will increment each time a heartbeat message is sent.

By observing the Inflow and Outflow values of the subtasks, you can detect if the agent is receiving messages or commands and forwarding the data over to the Ironstream UCMDB Probe server.

The "MC" column indicates how many memory allocations are outstanding for the subtask. It may show a positive number when the subtask is actively processing messages or commands, but should return to "0" when finished.

To further help in debugging a problem with the agent a DEBUG command is available to turn tracing on or off for the individual subtasks.

The command is entered as follows:

F VP390,DEBUG taskname level

where level can be 1 or 2 or 4 or any combination up to 7. For example, a 7 would include the results from 1 plus 2 plus 4.

  • Trace level of 1 shows basic message flow in and out of the subtask.

  • Trace level of 2 shows values of internal variables within subtask.

  • Trace level of 4 includes hexadecimal dumping of control blocks.

  • Trace level of 0 turns the trace off.

Note: The output of the trace data goes to the SYSPRINT DD statement. Leaving DEBUG tracing active for long periods of time could fill the output queue, especially when using the value of 7.

Example:

F VP390,DEBUG TCP-0 1

EVO595 Command entered: DEBUG TCP-0 1 EVO217 Debug for TCP-0 changed from 0 to 1

Example of data produced by the DEBUG command:

11/05 15:02:56 TCP-0 writing 14 bytes of type 25 info to 192.168.1.99

11/05 15:02:56 TCP-0 writing 14 bytes of type 27 info to 192.168.1.99

11/05 15:03:26 TCP-0 writing 14 bytes of type 27 info to 192.168.1.99

11/05 15:03:56 TCP-0 writing 14 bytes of type 27 info to 192.168.1.99 11/05 15:04:16 TCP-0 writing message to 192.168.1.99:

SGMAIN ROYM 2006/07/19 11:58 F8 0 0 00000000 70 50 MAIN STORAGE GROUP

11/05 15:04:16 TCP-0 writing message to 192.168.1.99:

VIO ROYM 2006/07/20 08:16 00 1 2000000 F3F3F9F0 0 0 VIO STORAGE GROUP

11/05 15:04:16 TCP-0 writing message to 192.168.1.99:

EOF

11/05 15:04:18 TCP-0 writing message to 192.168.1.99:

EVWRK1 SGMAIN ROYM 2006/07/19 11:59 56664 00F3F640 2707 1043 930 00 01

11/05 15:04:18 TCP-0 writing message to 192.168.1.99:

EVWRK2 SGMAIN ROYM 2006/07/19 11:59 56664 00F3F6D0 2707 756 364 00 01