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 HSIXMSG each time a directory is opened or closed.
PGMMSG Requests that a message is written to HSIXMSG each time an executable file is processed.
ALLMSG Requests both PTHMSG and PGMMSG message logging.
NOHOST Requests that the call to HSIPHOST 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 identifier of a system is not unique. For example: SID=SYS2
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.
PACK= The value is a single decimal digit (0-9) and specifies the level of compaction that will be used to write zipped output. The value of 0 specifies that shrink will be used. Values in the 1 to 9 range specify the compaction level of deflate to be used. PACK=1 is the program default.
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 HSIXZIP and HSIXOUT 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
HSIXMSG Report file used by HSIXINQ.
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.
HSIXZIP 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.

In the case where HSIXOUT is not allocated and HSIXZIP processing encounters an S213-C8 abend, the UNIX Inquisitor will attempt to write uncompressed output to this file, overriding the LRECL as appropriate.
HSIXOUT 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 HSIPZIP is preferred, due to its reduced space requirements. HSIXOUT 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 HSIXOUT file. The HSIXZIP file employs update-in-place processing, which prevents the use of DFSMS™ compression.
HSIXROOT 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 HSIXROOT is not allocated or empty, then a forward slash (/) is the only root directory processed.
HSIXOMIT 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 HSIXROOT and HSIXOMIT files have the following characteristics and attributes in common:
  • There is no requirement for the file to be allocated.
  • The file might be empty or allocated to DUMMY.
  • The file might contain fixed length or variable length records.
  • Records must not contain more than 1024 bytes of data.
  • Blank records are deemed to be comments and discarded.
  • Leading and trailing blanks are discarded when the directory name is extracted.
  • UNIX directory names may contain embedded blanks.
  • The entire record is parsed so do not use sequence numbers.
  • Records with an asterisk as the first non-blank are deemed to be comments and discarded.
  • If the directory path does not end in a slash, then one is appended.