Sending Commands to the Agent - 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 Mainframe Discovery Adapter utilizes the UD Probe server interface to communicate requests to the Ironstream agent on the IBM Z systems. The UD Probe server interface provides the capability to request the agent to execute z/OS console commands, subsystem commands, reply to outstanding WTORs, execute REXX programs and requests other information via the Ironstream mainframe agent.

The ev390hostcmd is the interface to the Ironstream UD Probe server for executing mainframe commands, subsystem commands, REXX programs or requesting information via the Discovery agent. The format of ev390hostcmd is:

ev390hostcmd <type> <command>.<zOS_system_name>

where:

variable

Description

<type>

Specifies a code to direct where the command should be executed on the mainframe. Three codes are valid:

40 = z/OS (MVS) commands. The command is sent to a MCS console defined for VP390 on the mainframe. The VP390 mainframe job must have a CMD subtask defined.

45 = z/OS (MVS) commands that do not return a response. This is the same as a Type 40 code, except the ev390hostcmd does not wait for a response message with this option.

46 = z/OS system information commands. The command instructs the VP390 mainframe task to gather specific z/OS system information such as CPU usage or JES2 job queue contents. See section “Sending Commands to the Agent” for the syntax of a type 46 command. The VP390 mainframe job must have an OSINFO subtask defined.

<command>

The command text, syntax dependent on the type. The first period (.) encountered is used to mark the end of the command. If the command text has a period in it, enter two periods to signify that it is not the end of the command. See the example below.

<zOS_system>

The IBM Z system on which the command is to be executed. Use the IP name of the mainframe domain. This name must match the name of the IBM Z system that was configured in the Ironstream Configuration Tool.

Examples:

  • Send an MVS command to the mainframe named myhost.mysite.com to display the system time:

ev390hostcmd 40 D T.myhost.mysite.com
  • Send an MVS command to the mainframe named myhost.mysite.com to start a job named MYJOB with a job identifier of MYIDENT (note that the period between MYJOB and MYIDENT must be doubled to signify that it is not the end of the command):

ev390hostcmd 45 S MYJOB..MYIDENT.myhost.mysite.com