Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support. BMC recommends upgrading to the latest version of the product.

IND$Detect configuration parameters

You can use the IND$Detect (formerly IND$defender) parameters to configure the use of the IBM PC 3270 File Transfer Program, commonly known as IND$FILE. These parameters do not use a statement-type name or continuations, and the configuration statement can be as long as required.

For information about general parameter syntax, see Parameter-file-statements.

IND$Detect_6.2.png

Parameter

Description

ALLOCwith(""|"additionalBPXWDYNParameters")

Specifies additional BPXWDYN parameters to use when allocating the library that contains the IBM IND$FILE

Example

If the library is an cataloged data set on volume SYS002, enter ALLOC(VOLSER(SYS002)).

You can enter multiple BPXWDYN parameters, separated by one or more blanks, enclosing the entire string in double quotation marks. Do not use any BPXWDYN parameters that include or conflict with ALLOC, DD, DSN, REUSE, SHR, or MSG.

For more information about BPXWDYN, see IBM documentation.

If you omit ALLOCwith, the default is "" (null string) (that is, no additional parameters).

INSTance(8|instance)

Specifies the BMC AMI Datastream for z/OS instance number for the API

Unless you specify SENDto(API), this parameter is validated but otherwise ignored. Enter a number from 8 to 255. 

For information about BMC AMI Datastream instances, see START-command. 

If you omit INSTance, the default is 8 (eight).

LIBrary(SYS1.CMDLIB|libraryName)

Specifies the name of the PDS or PDSE containing IBM IND$FILE, APVUFILE, or both

Enter a z/OS data set name of 1 to 44 characters.

If you omit LIBrary, the default is SYS1.CMDLIB.

PROGram(aliasName|programName)

Specifies the name of the IBM IND$FILE or APVUFILE program

Use this parameter only if you have renamed the IBM IND$FILE, APVUFILE, or both. Enter a name of 1 to 8 characters.

If you omit PROGram, the default is the alias name by which IND$Detect is invoked (normally IND$FILE or APVUFILE).

SENDto(SMF|API)

Specifies the destinations to which IND$FILE events should be sent

Enter API, SMF, or both separated by one or more blanks:

  • API—Events are sent to the specified or default BMC AMI Datastream instance as API1 events of Major Type CZ1MajCorMisc, Minor Type 2, subtype 1.
  • SMF—Events are written as user SMF records of the type specified (or the default type), and subtype 1.

If you omit SENDto, the default is SMF.

SMF(202|recordType)

Specifies the SMF record type number for IND$FILE events

This parameter is validated but otherwise ignored unless you specify SENDto(SMF) or allow it is the default value. Enter a number from 128 to 255. You can enter the number as a decimal integer, or in hexadecimal by using either mainframe (X'CA') or C format (0xca).

If you omit SMF, the default is 202.

TRACE(traceSpecifications)

Specifies that IND$Detect should output trace messages to the 3270 terminal session

Important

Use trace messages only for diagnostic purposes because these messages are generally inconsistent with the actual use of IND$FILE. Particularly, TRACE(PARMs) might interfere with the effective use of IND$FILE.

The two trace options that might be relevant to IND$Detect are MISC and PARMs. You can use one or both of these options separated by one or more blanks.

For more informaiton about TRACE, see OPTIONS Statement. 

Related topics

Command-and-syntax-reference

Customizing-IND-Detect-to-report-IND-FILE-activity

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*