Inquisitor for z/OS UNIX program parameters and files

The Inquisitor for z/OS UNIX 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 Inquisitor for z/OS UNIX
Parameter Description
PTHMSG Requests that a message is written to HZAXMSG each time a directory is opened or closed.
PGMMSG Requests that a message is written to HZAXMSG each time an executable file is processed.
ALLMSG Requests both PTHMSG and PGMMSG message logging.
NOHOST Requests that the call to HZAPHOST to collect the TCPIP host name and IP address is bypassed.
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 identifierof a system is not unique. For example: SID=SYS2
OUT=

Specifies output file usage. The default value is Z.

  • A value of Z requests zipped output toHZAXZIP.
  • A value of T requests text output toHZAXOUT.
  • A value of B requests output to both HZAXZIP and HZAXOUTfiles.

PLEXNAME =

The value is up to 8 characters long, and specifies the sysplex name 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 HZAXZIP and HZAXOUT 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 for z/OS UNIX
Filename Description
HZAXMSG Report file used by HZAXINQ.
SYSPRINT Used by Language Environment (LE), which is required to be in the standard module search path, and by IDCAMS when LLQ= is specified.
SYSOUT Used by Language Environment (LE), which is required to be in the standard module search path.
HZAXZIP

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

The HZAXZIP file must never undergo any translation when being transferred, whatever the architecture of the target system. That is, only BINARY transfers are to be used to transport the file.

Use of this output file format is required to perform import processing to use the Linux for Z import and reporting tools.

HZAXOUT

An optional output file that contains uncompressed Inquisitor for z/OS UNIX data. It is not specified in the packaged sample, as the use of HZAPZIP is preferred, due to its reduced space requirements. HZAXOUT 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 for z/OS UNIX output to a compressible extended- format data set, then you should use the HZAXOUT file. The HZAXZIP file employs update-in-place processing, which prevents the use of DFSMS compression.

HZAXROOT

An optional file which can contain one or more records; each of which specifies a directory path to be considered as a root directory to be processed. If HZAXROOT is not allocated or empty, then a forward slash (/) is considered to be the only root directory to be processed.

HZAXOMIT An optional file which can contain one or more records; each of which specifies a directory path which is to be omitted from the scan. Root directories cannot be omitted.

The HZAXROOT and HZAXOMIT files have the following characteristics and attributes in common:

  • There is no requirement for the file to beallocated.
  • The file might be empty or allocated toDUMMY.
  • The file might contain fixed length or variable lengthrecords.
  • Records must not contain more than 1024 bytes ofdata.
  • Blank records are deemed to be comments anddiscarded.
  • Leading and trailing blanks are discarded when the directory name is extracted.
  • Records with an asterisk as the first nonblank are deemed to be comments anddiscarded.
  • If the directory path does not end in a slash, then one isappended.