Using OSINFO System Information API Commands - ironstream_for_micro_focus_universal_discovery - 7.4

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

Product type
Product family
Ironstream > Ironstream for Micro Focus® Universal Discovery
Product name
Ironstream for Micro Focus Universal Discovery for IBM Z
Ironstream for Micro Focus® Universal Discovery for IBM Z® Administration
First publish date

The OSINFO subtask of the VP390 agent task will gather various z/OS operating system statistics and present the data in a format that can be parsed by a script. The OSINFO subtask can also be requested to run REXX programs or list information from physical sequential or partitioned datasets. OSINFO data are requested using type 46 of the ev390hostcmd utility. (See section “Sending Commands to the Agent” for syntax of ev390hostcmd.)

The OSINFO data are requested by specifying a two-digit code followed by a vertical bar and additional parameter information depending on the selected code. For example, to gather DASD information (code 01) for a volume named "disk99" on mainframe "," the ev390hostcmd syntax is:

ev390hostcmd 46 "01|"

Because the Windows/DOS shell interprets the vertical bar as a pipe symbol, the vertical bar will need to be escaped by enclosing everything after the last space inside double quotation marks.

Output lines for requests other than REXX programs or dataset listings will be returned with values separated by a vertical bar. One line will be generated for each record found, representing one job, device, etc. The last line will be the text "EOF".

Note: Codes 06, 07, and 08 require SDSF to be running on the mainframe agent and will require the extra DD cards ISFIN and ISFOUT to be uncommented in the VP390 startup JCL

Note: Codes 110, 111, 112, 113, and 114 require a temporary dataset to hold the TSO output. The dataset should be created with parameters DCB=(DSORG=PS,RECFM=FB,LRECL=1028,BLKSIZE=6144),SPACE=(TRK,(1,1,0)). This

dataset can be defined in three ways and will be searched in the following order:

  1. The dataset name is defined in the SYSIN parameter cards on a card labeled “TSOUTPUT”. The dataset must exist and be cataloged before the VP390 job is started.

  2. The dataset is defined in the VP390 startup JCL with a DDname of “TSOUTPUT”.

  3. A dataset named “EV390.TSOUTPUT” will be created when a 110-114 command is called and will persist after the VP390 job has ended.

TSO options (110-114) require that the “NETSTAT” command is not in the list of TSO authorized commands. (Verify that “NETSTAT” is not listed in the AUTHCMD section of the IKJTSOxx member of PARMLIB.)

The available OSINFO codes are: