DataSets option data set name substitution symbols

All data set names that are specified with the DataSets option can contain standard MVS™ symbols. These are resolved before any DDname-specific symbol substitution is performed by Fault Analyzer.

In Permitted data set name substitution symbols by DDname, an X indicates permitted symbols that can be used as part of the data set names for each DDname:

Table 1. Permitted data set name substitution symbols by DDname
DDname	&PGM.	&SYSUID.	&TSOPFX.	&USERID.	&SYSNAME.
IDIHIST					X
IDIVSxxx					X
IDIEXEC				X (Note 1)	X
IDIMAPS					X
IDIDOC					X
IDIDOxxx					X
IDIVIEWS (Note 2)		X	X		X
IDIADATA	X	X (Note 3)	X (Note 3)	X	X
IDIJAVA	X	X (Note 3)	X (Note 3)	X	X
IDILC	X	X (Note 3)	X (Note 3)	X	X
IDILCOB	X	X (Note 3)	X (Note 3)	X	X
IDILCOBO	X	X (Note 3)	X (Note 3)	X	X
IDISYSDB	X	X (Note 3)	X (Note 3)	X	X
IDILANGX	X	X (Note 3)	X (Note 3)	X	X
IDILPLI	X	X (Note 3)	X (Note 3)	X	X
IDILPLIE	X	X (Note 3)	X (Note 3)	X	X
IDIDSECT				X	X

Notes:

1: No value is available for the &USERID. variable when performing MVS™ dump analysis. (See File->Analyze MVS Dump Data Set.)
2: These symbols can be used in the data set names that are specified in the IDIVIEWS suboption of the DataSets option, as well as in the data set names that are specified in the individual view members contained within the IDIVIEWS data sets. For details, see Setting up views.
3: Substitution of these symbols is only performed during interactive reanalysis.

The available symbols on a given MVS™ system can be displayed with the MVS™ operator command D SYMBOLS.

If, at the time of performing symbol value substitution, a value for a symbol is unavailable, any data set names that include that symbol are ignored. An example of this ignoring is the &USERID. variable mentioned in the preceding note.

All symbol names specified must include the ending period, unless the symbol name is at the very end of a data set name. The symbol name, including the leading ampersand (&) and the ending period is replaced by the symbol value. Hence, if a symbol name is specified immediately ahead of a data set qualifier delimiter (period), then two consecutive periods must be specified, for example "&SYSUID..LISTINGS".

Data set names containing symbols do not cause errors during Fault Analyzer processing if, after their substitution, the data sets cannot be found, unless the data set is critical to the analysis.

Substitution symbols:

&PGM.

All instances of this symbol are substituted by the current program name when Fault Analyzer is searching for compiler listings or side files. To use this functionality, compiler listings or side files in sequential data sets can be stored with a naming convention that includes the program name.

For example, if the compiler listings for programs P1 and P2 are stored in the data sets FRED.LISTING.P1 and FRED.LISTING.P2 respectively, then these can both be located by Fault Analyzer by specifying "FRED.LISTING.&PGM." for the appropriate DDname in the DataSets option.

&SYSUID.

All instances of this symbol are substituted by the TSO user ID under which the Fault Analyzer ISPF interface is being used. By using this symbol in data set names that are specified in the IDICNF00 parmlib member, automatic user-specific access to private data sets can be provided, given that an appropriate data set naming convention is adhered to by the installation.

For example, specify the option

DataSets(IDIVIEWS(&SYSUID..VIEWS,PROD.VIEWS))

in the IDICNF00 parmlib member. Then all users of the Fault Analyzer ISPF interface for whom a data set named user-id.VIEWS exist, where user-id is the user's TSO user ID, can place private Fault Analyzer View definitions in this data set. These definitions either complement any installation-wide definitions in the PROD.VIEWS data set, or override them.

&TSOPFX.

All instances of this symbol are substituted by the TSO profile prefix for the user under which the Fault Analyzer ISPF interface is being used. By using this symbol in data set names that are specified in the IDICNF00 parmlib member, automatic user-specific access to private data sets can be provided, given that an appropriate data set naming convention is adhered to by the installation.

For example, specify the option

DataSets(IDIVIEWS(&TSOPFX..VIEWS,PROD.VIEWS))

in the IDICNF00 parmlib member. Then all users of the Fault Analyzer ISPF interface for whom a data set named tso-prefix.VIEWS exist, where tso-prefix is the user's TSO profile prefix, can place private Fault Analyzer View definitions in this data set. These definitions either complement any installation-wide definitions in the PROD.VIEWS data set, or override them.

&USERID.

All instances of this symbol are substituted by the user ID under which the abend occurred.

&SYSNAME.

All instances of this symbol are substituted by the system name from CVTSNAME, as at the time of substitution.