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. To see documentation for that version, see BMC AMI Datastream for Db2 7.1.

Data set specification


Several BMC AMI Defender and CZASEND statements, parameters and commands require or allow the specification of a data set name. 

image2019-3-25_11-37-2.png

All data set specifications use a consistent format, as shown.

*

Specifies a SYSOUT data set with a class equal to the job or started task MSGCLASS. * is only available for statements, parameters and commands that specify an output data set.

member

Specifies a member name in a default PDS or PDSE. Some statements, parameters or commands do not provide a default PDS and so this option is not available in those situations. You might not use a Variable Symbol with the member format; use the DD:ddname(member) or mvs.library.name(member) format with Variable Symbols.

mvs.dataset.name

Specifies the name of a conventional MVS data set. The name need not be quoted as BMC AMI Defender never prepends a default high level qualifier (as TSO does).

mvs.library.name(member)

Specifies the name of an MVS PDS or PDSE and a member name in that library. The name need not be quoted as BMC AMI Defender never prepends a default high level qualifier (as TSO does).

/zFS/file/name

Specifies the name of a zFS file. zFS file names must be fully-qualified, that is, begin with a slash character (/).

DD:ddname

Specifies the name of a DD statement in BMC AMI Defender or CZASEND JCL.

DD:ddname(member)

Specifies the name of a DD statement in BMC AMI Defender or CZASEND JCL, and a member in the library that the DD statement references. The DD statement must specify a PDS or PDSE.

Variable symbols

For any of the DATASET operand formats except * and member you might use one or more variable symbols to cause the data set, member, file or DD name to be unique across multiple LPARs and multiple timeframes. zDefender variable symbol names begin with an ampersand and end with a period. They might be used anywhere within a DATASET parameter operand where their substitution value is valid, for instance, DATASET(CZAGENT.&SYSNAME..SYSLOG). You might use multiple variable symbols in a single operand, such as, DATASET(CZA.&SYSNAME..D&YYMMDD..T&HHMMSS..LOG(&JOBID.).

zDefender variable symbols and their substitution values are:

Variable symbol name

Substitution value

&HHMMSS.

The current time expressed as six digits representing the 24-hour clock hours, minutes and seconds. As z/OS data set node and member names must not begin with a digit, you must prefix &HHMMSS. with one or two letters, for instance, DATASET(SYSA.CZAGENT.LOG.T&HHMMSS.).

&JESNODE.

1 to 8 character JES RJE network node ID, no trailing blanks.

&JOBID.

8 character unique name assigned by JESn to the job or started task, commonly called the job number, such as, STC03685.

&LPARNAME.

1 to 8 characters that identify the originating LPAR name, no trailing blanks.

&SMFID.

1 to 4 character SMF ID of the originating machine, no trailing blanks.

&SYSNAME.

1 to 8 character system name as defined in the IEASYSxx or IEASYMxx parmlib member. See the IBM Manual MVS Initialization and Tuning Reference.

&YYMMDD.

The current date expressed as six digits representing the low-order two digits of the year, the month and the day. As z/OS data set node and member names must not begin with a digit you must prefix &YYMMDD. with one or two letters, for instance, DATASET(CZAGENT.DT&YYMMDD..SYSLOG).

&YYYYDDD.

The current date expressed as a seven digit Julian date representing the year and the day of the year from 001 to 366. As z/OS data set node and member names must not begin with a digit, you must prefix &YYYYDDD. with a letter, for instance, DATASET(CZA.LOG.D&YYYYDDD..SYSLOG).

The three date and time symbols, shaded in gray in the table here, are only available for output data sets.

The variable symbol names might be coded in upper, lower, or mixed case: &HHMMSS., &hhmmss., and &HhMmSs. are all equivalent.

The date and time variable symbols are resolved consistently for a given data set or file name, even if the substitution occurs in the immediate vicinity of midnight. That is, &YYMMDD. and &YYYYDDD. in a given data set name always represents the same date, and &HHMMSS is always a time during that date, not a time during the preceding or succeeding day.

 

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