DISC directive

The DISC directive is used to set discovery parameter values. This directive can be used to specify or limit the scope of discovery.

You can use this parameter, for example, to restrict discovery to only CICS® resources, allowing the CICS support group to run CICS-only discovery independent of other discovery processes.

If you set DISC to yes, and debug to 1 (or ON), you can see what is discovered in the DLALOG file. Discovered resources are shown in output books (in xml files) only if you also set FILT INCLUDE for associated values, as illustrated in the following examples:

DISC DB2.IFI YES
FILT DB2.IFI INCLUDE

The default for most DISC statements is YES.

Syntax: DISC index value

Supported indexes and the values of the indexes are as follows:

DB2, IMS, CICS, MQ, WEBSPHERE, and STORAGE

The following DISC (discovery) statements not only result in discovery, but also create these high-level resources in the books. DISC DB2 YES, DISC IMS YES, DISC CICS YES, DISC MQ YES, DISC WEBSPHERE YES, DISC STORAGE YES. As explained in the latest IZDCDEF customization sample, high-level Subsystems are both DISCovered and FILT Included by DISC yes (for example,

DISC
MQ YES

). Lower-level resource types require both a DISC DB2 YES and a FILT DB2 INCLUDE statement.

The default is Yes.

CUSTOMSERVER

Yes to list and No not to list all address spaces that are available for custom server processing. Only address spaces that have a listening IP port qualify as a possible custom server resource.

The default is Yes.

DB2

The DB2 DISC directive controls the discovery of the highest-level resources (discovery subsystems). By including the default of Yes, all Db2® resources are discovered. A setting of No excludes the discovery of all Db2 resources.

The default is Yes.

DB2.jobprefix

Yes to include and No to exclude Db2 discovery for a specific Db2 subsystem.

The default is Yes.

DB2.DATABASE

Yes to include and No to exclude Db2 database discovery.

The default is No.

DB2.GROUP

Yes to include and No to exclude Db2 group discovery. Db2 group discovery is required to populate the Db2 VersionString attribute.

Authority to issue GROUP statements against these Db2 resources is required to use this option. DSNREXX must be bound to each Db2 instance where GROUP discovery is required. See the Db2 customization section for a list of customization requirements for all Db2 systems where discovery is run.

The default is Yes.

DB2.IFI

Yes to include and No to exclude DB2 IFI discovery routines.

DB2 IFI discovery is required to discover Db2 group resources and relationships. Authority to issue Db2 DISPLAY DB and DISPLAY GROUP commands is required to use this option.

The default is Yes.

DB2.SQL

Yes to include and No to exclude DB2 SQL discovery routines. If you set DB2.SQL to Yes, the following attributes are discovered:

SYSIBM.SYSDATABASE/SysdatabaseMaxAlterdts attribute
SYSIBM.SYSTABLESPACE/SystablespaceMaxAlterdts attribute
SYSIBM.SYSTABLES/SystablesMaxAlterdts attribute
SYSIBM.SYSINDEXES/SysindexesMaxAlterdts attribute
SYSIBM.SYSCOLUMNS/SyscolumnsMaxAlterdts attribute
SYSIBM.SYSROUTINES/Stored Procedures attributes

Authority to issue SQL statements against these Db2 resources is required to use this option. DSNREXX must be bound to each Db2 instance where SQL discovery is required. See the Db2 customization section for a list of customization requirements for all Db2 systems where discovery is run.

The default is Yes.

DB2.TABLESPACE

Yes to include and No to exclude Db2 tablespace discovery.

The default is Yes.

DB2.BUFFERPOOL

Yes to include and No to exclude the discovery of buffer pools that belong to Db2 subsystems. You must also set DB2 and DB2.SQL to Yes, otherwise the buffer pools are not discovered.

DB2.WZP

Yes to include and No to exclude the discovery of DB2 DSNZPARM data. You must also set DB2 and DB2.SQL to Yes, otherwise DB2 DSNZPARM data is not discovered.

In addition to the authorizations that are required for the SQL scope, the MONITOR1 and MONITOR2 privileges are required for this scope. See Db2 customization for a list of customization requirements for all Db2 systems where discovery is to be run.

WEBSPHERE

WEBSPHERE: The WebSphere® DISC directive controls the discovery of the highest-level resources (discovery subsystems). Set the DISC directive to Yes to include and No to exclude WebSphere subsystems if it is the first entry in a DISC or FILT statement.
The default is Yes.
WEBSPHERE.jobprefix: Yes to include and No to exclude WebSphere discovery for a specific WebSphere subsystem.
The default is Yes.

IMS

IMS: The IMS DISC directive controls the discovery of the highest-level resources (discovery subsystems). Set the DISC directive to Yes to include and No to exclude IMS subsystems if it is the first entry in a DISC or FILT statement.
The default is Yes.
IMS.jobprefix: Yes to include and No to exclude IMS discovery for a specific IMS subsystem. A setting of Yes discovers all IMS subsystems.
The default is Yes.
IMS.DATABASE: Yes to include and No to exclude IMS database discovery and IMS DatabasesChecksum attribute.
The default is Yes.
IMS.DEPREG: Yes to include and No to exclude IMS dependent region discovery.
The default is Yes.
IMS.PROGRAM: Yes to include and No to exclude IMS program discovery and IMS ProgramsChecksum attribute.
The default is Yes.
IMS.TRANSACTION: Yes to include and No to exclude IMS transaction discovery and IMS TransactionsChecksum attribute.
The default is Yes.

MQ

MQ: The MQ DISC directive controls the discovery of the highest-level resources (discovery subsystems). Set the DISC directive to Yes to include and No to exclude MQ subsystems when it is the first entry in a DISC or FILT statement.
The default is Yes.
MQ.jobprefix: Yes to include and No to exclude MQ discovery for a specific MQ subsystem.
The default is No.
MQ.PROCESS: Yes to include and No to exclude MQ discovery for a specific MQ process.
The default is Yes.
MQ.PROCESS.jobprefix: Yes to include and No to exclude MQ discovery for a specific MQ process.
The default is No.
MQ.QUEUE: Yes to include and No to exclude MQ queues.
The default is Yes.
MQ.QUEUE.jobprefix: Yes to include and No to exclude MQ discovery for a specific MQ queue.
The default is No.
MQ.QUEUE_ALIAS: Yes to include and No to exclude MQ discovery for a specific MQ queue.
The default is No.
MQ.QUEUE_ALIAS.jobprefix: Yes to include and No to exclude MQ discovery for a specific MQ queue.
The default is No.
MQ.QUEUE_LOCAL: Yes to include and No to exclude MQ discovery for a specific MQ queue.
The default is No.
MQ.QUEUE_LOCAL.jobprefix: Yes to include and No to exclude MQ discovery for a specific MQ queue.
The default is No.
MQ.QUEUE_REMOTE.jobprefix: Yes to include and No to exclude MQ discovery for a specific MQ queue.
The default is No.
MQ.QUEUE_MODEL: Yes to include and No to exclude MQ discovery for a specific MQ queue.
The default is No.
MQ.QUEUE_MODEL.jobprefix: Yes to include and No to exclude MQ discovery for a specific MQ queue.
The default is No.
MQ.QUEUE_REMOTE: The default is No.

CICS

CICS: The CICS DISC directive controls the discovery of the highest-level resources (CICS regions). Set the DISC directive to Yes to include and No to exclude CICS regions if it is the first entry in a DISC or FILT statement.
The default is Yes.
CICS.jobprefix: Yes to include and No to exclude CICS discovery for a specific CICS subsystem.
The default is Yes.
CICS.PROGRAM: Yes to include and No to exclude CICS program discovery and CICS ProgramsChecksum attribute.
The default is Yes.
CICS.TRANSACTION: Yes to include and No to exclude CICS transaction discovery and CICS TransactionsChecksum attribute.
The default is Yes.
CICS.FILE: Yes to include and No to exclude CICS file discovery and CICS FilesChecksum attribute.
The default is Yes.

STORAGE

STORAGE: The STORAGE DISC directive controls the discovery of the highest-level resources (discovery subsystems). Set the DISC directive to Yes to include and No to exclude STORAGE subsystems if it is the first entry in a DISC or FILT statement.
The default is Yes.
STORAGE.VOLUME: Yes to include and No to exclude storage discovery routines.
The default is Yes.