Using the ev390hostcmd Command Interface - ironstream_for_micro_focus_omi - 7.2

Ironstream for Micro Focus® OMi for IBM Z® Administration

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

Automatic and operator-initiated actions may consist of native z/OS commands as well as scripts or programs. z/OS commands may be incorporated into scripts by using the ev390hostcmd utility, which is located in the bin subdirectory of the Ironstream installation path. The format of ev390hostcmd is:

ev390hostcmd <type> <command>.<zOS_node>

where:

Format Parameter Description

<type>

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

30 = VTAM commands. The command is sent to a VTAM Secondary Program Operator (SPO) appl defined for VP390 on the mainframe. The VP390 mainframe job must have at least one SPO subtask defined.

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 page Error! Bookmark not defined. for the syntax of a type 46 command. The VP390 mainframe job must have an OSINFO subtask defined.

50 = NetView commands. The command is sent to IBM NetView/390 or CA SOLVE:NETMASTER via the Program-to-Program Interface (PPI). The VP390 mainframe job must have the PPI 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_node>

The z/OS node on which the command is to be executed. Use the IP name of the mainframe LPAR as given when the node was defined in the Ironstream Configuration Tool web page. When building an OMi automatic action response to an incoming message, this value is available in the variable

<$MSG_NODE_NAME>.

Examples:

  • Send a VTAM command to the mainframe named myhost.mysite.com to display the major nodes:

ev390hostcmd 30 DISPLAY NET,MAJNODES.myhost.mysite.com
  • 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

(In previous Linux/Unix versions, the ev390hostcmd program was named vp390hostcmd. A symbolic link for the old name exists in the bin directory to allow scripts and commands written for previous versions to run without modification.)