DataSets

Figure 1. Syntax

1 DAtasets (
1+ ,
2.1  IDIHIST (  data-set-name )
2.1  IDIVSxxx (  data-set-name )
2.1  IDIEXEC ( + , data-set-name )
2.1  IDIMAPS (  data-set-name )
2.1  IDIDOC (  data-set-name )
2.1  IDIDOxxx (  data-set-name )
2.1  IDIVIEWS ( + , data-set-name )
2.1  IDIADATA ( + , data-set-name )
2.1  IDIJAVA ( + , path-name )
2.1  IDILC ( + , data-set-name )
2.1  IDILCOB ( + , data-set-name )
2.1  IDILCOBO ( + , data-set-name )
2.1  IDISYSDB ( + , data-set-name )
2.1  IDILANGX ( + , data-set-name )
2.1  IDILPLI ( + , data-set-name )
2.1  IDILPLIE ( + , data-set-name )
2.1  IDIDSECT ( + , data-set-name )
2 )
The DataSets option specifies as suboptions the DDnames and their associated data set names that are to be dynamically allocated byFault Analyzer.
IDIHIST
The name of the PDS or PDSE history file where the fault entry is to be or was written. Default value is IDI.HIST.
IDIEXEC
The name of one or more PDS or PDSE data sets containing REXX user exits.
IDIMAPS
The name of the PDS or PDSE data set containing data area mappings provided with Fault Analyzer for z/OS®. Default value is IDI.SIDIMAPS.
IDIDOC
The name of the distributed book index and override PDS or PDSE data set. Default value is IDI.SIDIDOC1.
IDIDOxxx
The name of an extra distributed book index and override PDS or PDSE data set for a multicultural support feature, where xxx is a valid language ID for the Language option, other than ENU, for example, IDIDOJPN. The data set specified is only used when the equivalent Language option is in effect. No default value is provided.
IDIVSxxx
The name of the VSAM KSDS message and abend code explanation repository, where xxx is a valid language ID for the Language option, for example, IDIVSENU. For values of xxx other than ENU, the data set specified is only used when the equivalent Language option is in effect. Default value is IDI.IDIVSENU.
IDIVIEWS
The name of one or more PDS or PDSE data sets containing members defining the fault history files to be viewed in a single ISPF display.
IDIADATA
The name of one or more sequential or PDS or PDSE data sets holding assembler SYSADATA files.

For details about required data set attributes for this DDname, see Compiler listings and side file attributes.

IDIJAVA
One or more HFS path names to be used when searching for Java source code.

By default, path names specified through this option are concatenated ahead of the Java class paths. However, if the special value -DROPCP- is encountered anywhere within an IDIJAVA specification, then only the path names specified in the IDIJAVA DDname are searched. For example, the following specification will result in only the path names /a/b/c and /d/e/f being searched, ignoring the Java class paths:

DataSets(IDIJAVA(/a/b/c,-dropcp-,/d/e/f))

If the following IDIJAVA statement is specified, Java source code is not searched for.

DataSets(IDIJAVA(-dropcp-))

Path names must start with a slash (/) and may optionally be surrounded by single quotation marks.

If the path name includes single quotation marks, commas, or blanks, it must also be surrounded by single quotation marks. Any single quotation marks within the path name must be specified doubled up. For example, the path name /a/b', c must be specified as follows:

'/a/b'', c'

The maximum length of each path name, excluding any surrounding single quotation marks, is 1023 characters.

Path names are case sensitive. The -DROPCP- keyword is not case sensitive.

IDILC
The name of one or more sequential or PDS or PDSE data sets holding C compiler listings.

For details about required data set attributes for this DDname, see Compiler listings and side file attributes.

IDILCOB
The name of one or more sequential or PDS or PDSE data sets holding COBOL compiler listings (other than OS/VS COBOL).

For details about required data set attributes for this DDname, see Compiler listings and side file attributes.

IDILCOBO
The name of one or more sequential or PDS or PDSE data sets holding OS/VS COBOL compiler listings.

For details about required data set attributes for this DDname, see Compiler listings and side file attributes.

IDISYSDB
The name of one or more sequential or PDS or PDSE data sets containing COBOL or Enterprise PL/I SYSDEBUG side files, or XL C/C++ MDBG side files. (These side files are created when compiling a COBOL program with the TEST(,,SEPARATE) option. MDBG side files are created using the CDADBGLD utility.)

For details about required data set attributes for this DDname, see Compiler listings and side file attributes.

IDILANGX
The name of one or more sequential or PDS or PDSE data sets holding LANGX side files.

For details about required data set attributes for this DDname, see Compiler listings and side file attributes.

IDILPLI
The name of one or more sequential or PDS or PDSE data sets holding PL/I compiler listings (other than Enterprise PL/I).

For details about required data set attributes for this DDname, see Compiler listings and side file attributes.

IDILPLIE
The name of one or more sequential or PDS or PDSE data sets holding Enterprise PL/I compiler listings.

For details about required data set attributes for this DDname, see Compiler listings and side file attributes.

IDIDSECT
The name of one or more PDS or PDSE data sets, containing assembler macro or DSECT copybooks that are to be used with the interactive reanalysis DSECT command. For details, see Mapping storage areas using DSECT information.

IDIHIST, IDIEXEC, IDIMAPS, IDIDOC, IDIVSxxx, and IDIDOxxx have only one data set name value, and a second specification replaces, rather than accumulates. Multiple specifications of the other DataSets suboptions are cumulative and all the data sets, wherever they have been specified, are included in the final logical concatenation of the respective DDname.

To specify a DUMMY data set for any DDname, a data set name of NULLFILE can be used.

The names of compiler listing or side file data sets used during real-time analysis are saved with the fault entry in the history file and are automatically used if reanalysis is performed. Therefore, there is generally no need to specify data sets using the DataSets option for reanalysis, unless a compiler listing or side file that was not available during real-time analysis is to be made available.