Inquisitor program parameters and files

The Inquisitor program has mandatory and optional parameters that affect how data is collected. The program uses some mandatory files as well as some optional files.

Table 1. Parameter settings for the Inquisitor
Parameter Description
DSNMSG Requests that messages relating to processed data sets, which might otherwise be suppressed, are to be logged in the SYSPRINT report.
PGMMSG Requests that messages relating to processed programs, which might otherwise be suppressed, are to be logged in the SYSPRINT report.
ALLMSG Requests both DSNMSG and PGMMSG message logging.
NOAPF Specifies that the Inquisitor is to run in an environment which is not APF authorized.
NOHOST Requests that the call to HZAPHOST to collect the TCPIP host name and IP address is bypassed.
OLDTAG Specifies that tag data members created by program HZATAGP will not be ignored, but should be processed so that the tag data can be imported into the LKB.
SID=

The value is up to 4 characters long, and specifies the system identifier to be contained in the data output from the Inquisitor. If the SID identifier override is omitted, the system

SMF identifier is used. The SID parameter setting is used when the SMF system identifier of a system is not unique. For example: SID=SYS2

PLX=

The parameter is used to identify if the Inquisitor data being collected is part of a SYSPLEX with fully shared DASD. The value is either Y or N.

If the PLX parameter is not used, the default value of N is created in the Inquisitor header record.

PLEXNAME=

The value is up to 8 characters long, and specifies the sysplex identifier to be contained in the data output from the Inquisitor. If the PLEXNAME identifier override is omitted, the actual sysplex name is used. The primary purpose of the PLEXNAME parameter is to provide a means for controlling the scope of sysplex-wide inventory updates.

LLQ=

This parameter is used to specify a suffix string made up of one or more data set name qualifiers to be appended to the data set name of the HZAPZIP and HZAPOUT data set. Its maximum length is 44 characters. It may contain both static and dynamic system symbols, and the user symbols &SMF. (SMF system identifier) and &SYSLPAR. (LPAR name) supplied by the Inquisitor. Use the LLQ setting when you need to create uniquely named data sets without changing the JCL.

Table 2. Files used by the Inquisitor
Filename Description
SYSPRINT A mandatory report file.
TAGREP An optional report file that summarizes tag data collected by the Inquisitor.
SYSIN

A mandatory request input file. It processes fixed length, variable length, and undefined record formats. Records shorter than 72 bytes will be logically extended by the Inquisitor with blanks.

HZAPZIP

An optional output file that contains compressed Inquisitor data. It is written using a variable length record format. You must provide DCB information to ensure optimal use of DASD space.

Use of this output file format is required to perform import processing to use the Linux for Z import and reporting tools. Data must be transferred in BIN format only.

HZAPOUT

An optional output file that contains uncompressed Inquisitor data. It is not specified in the packaged sample, as the use of HZAPZIP is preferred, due to its reduced space requirements. HZAPOUT also contains variable length records. The program supplies the appropriate LRECL. By default, system determined block size is used.

If you want to direct the Inquisitor output to a compressible extended-format data set, then you should use the HZAPOUT file. The HZAPZIP file employs update-in-place processing, which prevents the use of DFSMS compression.

MCDS

An optional file that allocates the DFHSM MCDS data set, and is required if any requests contain the REMIGRATE or NOML2 operands. Further, if supplied for other requests, you can use it to avoid recalling data sets which are not load libraries. If the DFHSM MCDS is spread over more than one data set, use the DD names MCDS2, MCDS3, and MCDS4 consecutively. This allocates all the MCDS data sets in key range order.

ABRIN

An optional SYSIN file belonging to the FDRABRP utility program that is required if any requests contain the ABRMIG or ABRARC operands. It is primed by the Inquisitor during execution. For this reason, a single track VIO file is an ideal allocation.

ABRPRINT

An optional SYSPRINT file belonging to the FDRABRP utility program that is required if any requests contain the ABRMIG or ABRARC operands. It is an output-only file, and is not processed by the Inquisitor.