Selecting or creating an ADYSETxx parmlib member

Select or create an ADYSETxx parmlib member to be used at IPL. IBM® supplies three ADYSETxx members:

ADYSET00, which starts DAE and keeps 400 symptom strings in virtual storage. The IBM-supplied ADYSET00 member contains:
```
DAE=START,RECORDS(400),
    SVCDUMP(MATCH,SUPPRESSALL,UPDATE,NOTIFY(3,30)),
    SYSMDUMP(MATCH,UPDATE)
```
ADYSET00 does not suppress SYSMDUMP dumps because installation-provided programs deliberately request them. If desired, change the ADYSETxx member being used to suppress SYSMDUMP dumps.
ADYSET01, which stops DAE processing. The IBM-supplied ADYSET01 member contains:
```
DAE=STOP
```
When using the DAE Display facility's TAKEDUMP (T) action in a sysplex where DAE is active, you must change the contents of ADYSET01 to:
```
DAE=STOP,GLOBALSTOP
```
ADYSET02, which contains the same parameters as ADYSET00.

The IBM-supplied IEACMD00 parmlib member issues a SET DAE=00 command, which activates ADYSET00 during IPL. If you do not want DAE to start during IPL, change IEACMD00 to specify SET DAE=01.

For a sysplex, IBM recommends that you use the same ADYSETxx parameter values in each system. To use the same values, use a shared SYS1.PARMLIB. If your installation does not share a SYS1.PARMLIB, make the ADYSETxx and IEACMDxx members in the SYS1.PARMLIB for each system identical. A shared ADYSETxx or identical ADYSETxx members should specify SHARE(DSN) to share the DAE data set.

IBM recommends that the ADYSETxx member specify SUPPRESSALL, which requests that dumps be suppressed even though the component or program did not request dump suppression with a VRADAE key in the system diagnostic work area (SDWA). SUPPRESSALL is useful because it allows more dumps to be eligible for suppression.

In the example shown in Figure 1, the systems in the sysplex share a DAE data set, SYS1.DAESHARE, so DAE can suppress a duplicate of a previous dump from any system. This member also specifies SUPPRESSALL.

Figure 1. Example: An ADYSETxx Member for a System in a Sysplex

DAE=START,RECORDS(400),
    SVCDUMP(MATCH,SUPPRESSALL,UPDATE,NOTIFY(3,30)),
    SYSMDUMP(MATCH,UPDATE)
    SHARE(DSN,OPTIONS),
    DSN(SYS1.DAESHARE)

The ADYSET00 member specifies RECORDS(400). If your system does not suppress a dump when the matching symptom string is in the DAE data set, you might need more than 400 records in storage; the IBM Support Center can advise you.

Changing Parmlib Members to Change DAE Processing: While the system is running, change the DAE data set or parameters for the dumps by creating a new ADYSETxx parmlib member. See Changing DAE processing in a Sysplex for the operator actions needed to change the parmlib member.

There is another benefit when all the systems in a sysplex are sharing the DAE data set. That is, after DAE is started on each system using an ADYSETxx member which at least contains SHARE(DSN). One operator command can set the DAE values to be the same on all systems. This is accomplished by issuing the SET DAE= command, for an ADYSEYxx member which includes the GLOBAL parameter. ALL systems sharing the DAE data set will be effected.

In Figure 2, the following ADYSET04 member changes the DAE data set being used on all systems to SYS1.DAESH2 and changes the dump options on all systems.

Figure 2. Example: An ADYSETxx Member with GLOBAL

DAE=START,RECORDS(400),
    SVCDUMP(MATCH,SUPPRESSALL,UPDATE,NOTIFY(3,30)),
    SYSMDUMP(MATCH,UPDATE)
    SHARE(DSN,OPTIONS),
    DSN(SYS1.DAESH2)
    GLOBAL(DSN,OPTIONS)

None of the changes made using operator commands are kept across an IPL of a system. At IPL, each system will again use the member specified in IEACMD00 or the COMMNDxx member being used. To make the changes permanently effective, do one of the following:

Make the changes in ADYSET00 and the default IEACMD00 will start DAE.
Make the changes in the ADYSETxx member and update a COMMNDxx member to start the ADYSETxx using the SET DAE=xx statement. Then update the appropriate IEASYSxx member to include the CMD=xx statement. Once complete, remove the SET DAE=00 within the IEACMD00 member to ensure that the two commands do not complete out of sequence.