Subtasks - ironstream_for_servicenow_discovery_1 - 7.5

• The OSI subtask will accept various requests from the Ironstream Proxy 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 Proxy 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 Proxy 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 this 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 Proxy 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.