SMFD Control Statement Reference › DUMPOPTIONS

DUMPOPTIONS

This control statement allows systems personnel to define the specifications for dumping SMF records to history files managed by CA SMF Director. The DUMPOPTIONS control statement must follow the BEGIN control statement defining the dump options for the specified system configuration. This statement must also precede the END CONFIG control statement.

Statement Format:

DUMPOPTIONS

►►─ DUMPOPTIONS ─ COPIES( ─┬─ 1 ◄ ─┬─ ) ─┬─────────────┬─┬─────────────┬──────►
                           ├─ 2 ───┤     ├─ NOCATLG ◄ ─┤ ├─ SCRATCH ◄ ─┤
                           └─ * ───┘     ├─ CATLG ─────┤ ├─ NOSCRATCH ─┤
                                         └─ UPCATLG ───┘ └─ UPSCRATCH ─┘
 ►─┬──────────────┬───────────────────────────────────────────────────────────►
   ├─ NOVERIFY ◄ ─┤
   └─ VERIFY ─────┘
 ►─┬────────────────────────┬─────────────────────────────────────────────────►
   ├─ PREFIX(─┬──*─────┬─)──┤
   ├─         └ prefix ┘    │
   └─ NOPREFIX ◄ ───────────┘
 ►─┬─────────────────────────┬────────────────────────────────────────────────►
   ├─ APREFIX(─┬──*─────┬─)──┤
   ├─          └ prefix ┘    │
   └─ NOAPREFIX ─────────────┘

 ►─┬──────────────────────┬───────────────────────────────────────────────────►
   ├─ RETPD(──┬──0 ◄ ──┬─)┤
              ├ nnnn ──┤  │
   └─         └─ * ────┘ ─┘
   ├─ EXPDT(──┬──0 ◄ ──┬─)│
              ├ yyyddd ┤  │
   └─         └─ * ────┘ ─┘

 ►─┬──────────────────────┬───────────────────────────────────────────────────►
   ├─ ARETPD(─┬──*───┬─)──┤
   ├─         └ nnnn ┘    │
   ├─ AEXPDT(─┬──*─────┬─)│
   └─         └ yyyddd ┘  ┘ 

 ►─┬───────────────────────┬──────────────────────────────────────────────────►
   └─ TRTCH(──┬──*────┬─)──┘
              └ value ┘    

 ►─┬───────────────────────┬──────────────────────────────────────────────────►
   └─ ATRTCH(─┬──*────┬─)──┘
              └ value ┘    

 ►─┬────────────────────────────────┬────────┬───────────────────┬────────────►
   ├─ LSNAME(lsname lsname ...)    ─┤        └─ FIRSTYEAR(yyyy) ─┘
   └─ SUBNAME(subname subname ...) ─┘
 ►─┬────────────────────────────────┬─────────────────────────────────────────►
   └─ MAXFILESONVOL( ─┬─ * ───┬─ ) ─┘
                      └─ n ───┘
 ►─┬────────────────────────────┬─────────────────────────────────────────────►
   └─ DAYSTACK( ─┬─ NO ◄ ─┬─ ) ─┘
                 ├─ YES ──┤
                 └─ * ────┘
 ►─┬────────────────────────────┬─┬─────────────────────────────┬─────────────►
   └─ PDSNLARGE( ─┬─ NO ◄ ─┬─) ─┘ └─ ADSNLARGE( ─┬─ NO ◄ ─┬─ ) ─┘
                  ├─ YES ──┤                     ├─ YES ──┤
                  └── * ───┘                     └── * ───┘
 ►─┬─────────────┬──────────────┬───────────────────────────┬─────────────────►
   ├─ NODYNAM ───┤              ├─ PDEVN( ─┬─ dname ─┬─ ) ──              └─ PSTORC( ─┬─ class ─┬─ ) ─┘
   ├─ DYNAM ─────┤              │          ├─ NONE ──┤                                 ├─ NONE ──┤│
   ├─ DYNAMVTS ──┤              │          └── * ────┘      │                           └── * ────┘
   └─ UPDYNAM ◄ ─┘

 ►─┬───────────────────────────┬───────────────┬────────────────┬─────── . ───►◄
   │  ADEVN( ─┬─ dname ─┬─ ) ──    └─ ASTORC( ─┬─ class ─┬─ ) ─┘┤               └─ SDAY(hhmm) ───┘ 
   │          ├─ NONE ──┤      │                       ├─ NONE ──┤
   │          └── * ────┘                                └── * ────┘│

 ►─┬───────────────────────────┬───────────────┬────────────────┬─────── . ───►◄
   │  PMGMTC( ─┬─ class ─┬─ ) ──   └─ PDATAC( ─┬─ class ─┬─ ) ─┘
   │          ├─ NONE ──┤      │                       ├─ NONE ──┤
   │          └── * ────┘                                └── * ────┘│

 ►─┬───────────────────────────┬───────────────┬────────────────┬─────── . ───►◄
   │  AMGMTC( ─┬─ class ─┬─ ) ──  └─ ADATAC( ─┬─ class ─┬─ ) ─┘
   │          ├─ NONE ──┤      │                       ├─ NONE ──┤
   │          └── * ────┘                                └── * ────┘│

 ►─┬───────────────────────┬──────────────────────────────────────────────────►
   └─ FALLBACK(────────────┬──*────┬─)──┘
              └ (mmddyy|000000 hhmm) ┘    

Operands and Descriptions:

COPIES(1|2|*)

Specifies whether CA SMF Director creates a duplicate copy of the dumped SMF data (duplexing). If 1 is specified, no duplexing is performed. If 2 is specified, duplexing of the history file is performed. A duplicate index entry is also created on the SCDS file to maintain an inventory of the SMF data for the duplex file. The duplex files are placed in the alternate archive. The default is COPIES(1). We recommend setting COPIES(2) for all SMF data that are kept on a long-term basis. To use the value that is coded on the OPTIONS statement, specify COPIES(*).

NOCATLG|CATLG|UPCATLG

Indicates whether CA SMF Director catalogs the history file data set, creating an entry within the System Catalog. The default is NOCATLG. To indicate that the system being configured uses the value that is coded on the OPTIONS statement, specify the UPCATLG operand.

Notes:

• When history files are written to DASD, the CATLG option is recommended. If DASD history files are not cataloged, there is a danger that a history file can be archived and then later restored to a different volume. This action causes a S213 ABEND in a subsequent EXTRACT that attempted to access the history file. The EXTRACT looks for the file on the volume on which it originally resided.
• If the PSTORC or ASTORC option is in effect, SMS classes are used then SMS can override the NOCATLG/CATLG specification.

SCRATCH|NOSCRATCH|UPSCRATCH

Specifies whether CA SMF Director requests specific or nonspecific magnetic tape volumes when creating the history file.

SCRATCH

SCRATCH is the default. Specifying this option allows a nonspecific mount request for a scratch tape to perform when a new tape volume is needed for a history file.

NOSCRATCH

Specifying this option, selects a volume serial from the predefined pool of volumes when a new tape volume is needed for a history file. For more information, see the DUMPTAPES control statement. To indicate that the system being configured can use the value that is coded on the OPTIONS statement, specify the UPSCRATCH operand.

Notes:

• If Tape Management products such as CA 1, CA Vtape Virtual Tape System, or CA TLMS are used, SCRATCH is recommended.
• If DASD history files are used, this parameter has no direct impact. SCRATCH is recommended, as it is required for some other options.
• If logstreams or substreams are going to be dumped in this configuration, SCRATCH is required.

NOVERIFY|VERIFY

Indicates whether CA SMF Directorenables the Write Validity Check Feature if available on the device that is used to create a history file. This option ensures the integrity of the SMF data written. This product also checks the validity of the standard header on each SMF record. The record length, date, and time are all checked for validity.

NOVERIFY

This option is the default. If an error is detected, a dump of the record in question is dumped to the SYSPRINT DD statement, and processing continues.

VERIFY

When VERIFY is specified, the hardware supplied Write Validity Check feature is enabled. Any errors that are detected by CA SMF Director results in the termination of processing.

Note: This feature is obsolete but is still supported for backward compatibility.

NOPREFIX|PREFIX(prefix|*)

Specifies the high level qualifiers to be used for the primary history file data set names.

Note: When no APREFIX operand is coded, this qualifier is used for the APREFIX.

NOPREFIX

This option is the default. If NOPREFIX is specified, CA SMF Director uses SYS1.SMFDATA,

PREFIX(prefix|*)

To use the value of the PREFIX operand on the global OPTIONS statement, code PREFIX(*).

The prefix can be up to 26 characters. For more information, see the Attributes of History Files.

NOAPREFIX|APREFIX(prefix|*)

Specifies the high level qualifiers to be used for the alternate or duplex history file data set names. If NOAPREFIX is specified or this operand is not specified, the value that is specified by the PREFIX keyword is used. To use the value of the APREFIX operand on the global OPTIONS statement, code PREFIX(*).

For more information, see the Attributes of History Files.

EXPDT(0|yyyddd)|*|RETPD(0|nnnn|*)

Specifies the expiration date or retention period of the history file data sets within the primary pool. If the expiration date is specified, it must be in the Julian date format. The default is EXPDT(0) or RETPD(0) which causes CA SMF Director not to set an expiration date for the history file. To use the value of the EXPDT or RETPD operand on the global OPTIONS statement, code either EXPDT(*) or RETPD(*).

See Control Statement Language Rules for a description of two special expiration dates: 099000 and 099366.

We recommend that expiration dates or retention periods be used, as it increases the integrity of the SMF data. If the AUTODEL feature is desired, setting expiration dates or retention periods is required.

Note: When the AEXPDT|ARETPD operand is not coded, the EXPDT|RETPD specification is used for AEXPDT|ARETPD.

Note: If the PSTORC option is in effect, SMS can override the specified expiration date or retention period.

AEXPDT(yyyddd|*)|ARETPD(nnnn|*)

Specifies the expiration date or retention period of the history file data sets within the alternate pool. If the expiration date is specified, it must be in the Julian date format. For data sets created on a DASD device it requires an operator response and confirmation if the data set is to be scratched or overwritten. If AEXPDT or ARETPD is not specified, CA SMF Director uses the values that are specified for EXPDT or RETPD. To use the value of the AEXPDT or ARETPD operand on the global OPTIONS statement, code either AEXPDT(*) or ARETPD(*).

See Control Statement Language Rules for a description of two special expiration dates: 099000 and 099366.

We recommend that expiration dates or retention periods be used, as it increases the integrity of the SMF data. If the AUTODEL feature is desired, setting expiration dates or retention periods is required.

Note: If the ASTORC option is in effect, SMS can override the specified expiration date or retention period.

TRTCH(value|*)

ATRTCH(value|*)

Lets you use the z/OS JCL TRTCH parameter on dynamically allocated history files in CA SMF Director. The values of the TRTCH and ATRTCH operands are the same as the values allowed in z/OS JCL when writing an output file to tape. TRTCH is used to set the recording technique for the primary history file, while ATRTCH is used to set the TRTCH for the alternate history file.

The valid values are as follows:

NOCOMP

For cartridge tapes, writes the history file without using any data compression.

COMP

For cartridge tapes, writes the history file using the data compression.

C

Performs data conversion for history files on reel tapes.

E

Writes history files to reel tape with even parity.

ET

Writes history files to reel tape with even parity and perform the EBCDIC translation.

T

Writes history files to reel tape and perform the EBCDIC translation.

Note: Although CA SMF Director does support TRTCH options C, E, ET, and T, they are not recommended for history files.

If TRTCH or ATRTCH is not specified, the system defaults are used. These values can be set in SYS1.PARMLIB or within SMS.

To use the value of the TRTCH or ATRTCH operand on the global OPTIONS statement, code them with (*).

LSNAME(lsname lsname ...)

Specifies which logstreams are recording data that are managed. Each logstream must be indicated in the configuration for each system that is writing data to that logstream. Up to 21 logstreams can be indicated in one compile. If more than 21 logstreams are needed, run the compile more than once with the additional names in the LSNAME operand. These logstreams are added to the configuration being processed.

SUBNAME(subname subname ...)

Specifies any substreams that you are defining to manage SMF MAN file recorded data. By using substreams, you can define the specific recording management attributes for SMF data that is recorded to SYS1.MANx files that are based on the SMF record type. The substream names can be up to 26 characters long in a standard 8.8.8 format similar to logstream names. Unlike logstream names, the subnames cannot begin with “I” or "SYS" and must contain at least two nodes. That is, SUBNAME(VALID.NAME) is allowed but SUBNAME(INVALID) is not allowed.

FIRSTYEAR(yyyy)

Specifies the first year of data that is allowed in the history file index. During the dump, if an SMF record for this configuration has a lower year than this specified year, then the record is rejected as invalid. When adding a history file manually through ADDX, the low date also has to be higher than or equal to this year; otherwise the ADDX fails. The valid values for this option range from 1960 to the current year or 2059, whichever is lower. The default is 1960.

Note: Changing this option has no effect on history files already in the index.

MAXFILESONVOL(n|*)

Lets you override the global MAXFILESONVOL at the configuration level. (See the description of MAXFILESONVOL on the OPTIONS statement.) To use the value of the MAXFILESONVOL operand on the global OPTIONS statement, code either MAXFILESONVOL(0) or MAXFILESONVOL(*).

DAYSTACK(NO|YES|*)

Specifies whether the daystacking feature can be turned on or off. The default is NO, which turns daystacking off. To use the value of the DAYSTACK operand on the global OPTIONS statement, code DAYSTACK(*). See Features for a description of the daystacking feature.

PDSNLARGE(NO|YES|*)

Allocates the primary history file with the DSNTYPE=LARGE operand. This operand is only used for DASD history files when the DYNAM operand is specified on the OPTIONS statement; otherwise it is ignored. To use the value of the PDSNLARGE operand on the global OPTIONS statement, code PDSNLARGE(*).

Note: When a history file (HISTORY1) DD statement with DSNTYPE=LARGE is present in the DUMP JCL, then the history file is allocated with the large format attribute regardless of the PDSNLARGE specification.

ADSNLARGE(NO|YES|*)

Allocates the alternate history file with the DSNTYPE=LARGE operand. This operand is only used for DASD history files when the DYNAM operand is specified on the OPTIONS statement; otherwise it is ignored. To use the value of the ADSNLARGE operand on the global OPTIONS statement, code ADSNLARGE(*).

Note: When a history file (HISTORY2) DD statement with DSNTYPE=LARGE is present in the DUMP JCL, then the history file is allocated with the large format attribute regardless of the ADSNLARGE specification.

DYNAM|DYNAMVTS|UPDYNAM|NODYNAM

Controls whether CA SMF Director can dynamically allocate history files when performing dump, extract, and print operations. DYNAM allows the dynamic allocation of history files for all dumps and EXTRACT/PRINT operations. NODYNAM prevents the dynamic allocation of history files under any circumstances. DYNAMVTS allows the dynamic allocation of input history files to EXTRACT and the PRINT operations, but suppresses the dynamic allocation of output history files from dump operations. To indicate that the system being configured can use the value that is coded on the OPTIONS statement, use the UPDYNAM operand. The UPDYNAM is the default.

Notes:

• If the DYNAM option is in effect and a history DD statement is coded, the parameters in the DD statement override the dynamic allocation options such as PSTORC and ASTORC. See the descriptions of the PSTORC and ASTORC operands for more information.
• The NODYNAM option can cause problems involving incorrect mount messages at data centers that employ virtual tape. The DYNAMVTS option can be used to avoid this problem while maintaining control over the allocation of output history files during dumps.
• If the logstream or substream recorded SMF data is managed with this configuration, DYNAM must be active for this configuration. This can be set either by specifying DYNAM on the DUMPOPTIONS statement or by specifying UPDYNAM on this DUMPOPTIONS statement and having DYNAM coded on the enterprise-wide OPTIONS statement. We recommend that you code DYNAM on the DUMPOPTIONS statement in case the OPTIONS statement changes in the future.

PDEVN(dname|NONE|*)

'dname' is the esoteric device name to be used when creating SMF history files in the primary pool. Up to eight characters can be specified. If no device name or SMS classes are specified and the DYNAM option is enabled, the system default device name is used. This default name can be set in the active ALLOCxx member of the system PARMLIB. Specify NONE to reset the device name. To use the value of the PDEVN operand on the global OPTIONS statement, code PDEVN(*).

Note: If you are changing the PDEVN parameter from one tape unit name to another, from tape to DASD, or DASD to tape, immediately run a TAPEINIT command against this SID.

If using DASD for history files, this parameter must only be used for non-SMS managed volumes.

Note: When a history file (HISTORY1) DD statement with the UNIT parameter is present in the DUMP JCL, the UNIT parameter specification overrides the PDEVN option.

PSTORC(class|NONE|*)

'class' is the IBM DFSMS storage class to be used when creating SMF history files in the primary pool. Up to eight characters can be specified. Specify NONE to reset the storage class. To use the value of the PSTORC operand on the global OPTIONS statement, code PSTORC(*).

If using DASD for history files, this operand can allocate files only to SMS-managed volumes. Some issues can arise with DASD history file allocations based on how SMS is set up at your data center. For DASD history allocations with the DYNAM option set, there must be a temporary history file that is allocated in the JCL. This temporary file indicates how large the history file can be. SMS may not allow the allocation on the storage class that is indicated in the PSTORC operand and indicates an allocation error for the history file. This error causes the dump process to end prematurely.

To avoid this issue, here are some remedies that you can use:

• Include a data set name on the history DD statement. This name can be any valid data set name that would be allocated in the storage class that is indicated in the PSTORC operand.

  Note: This remedy is the simplest remedy and the one that we recommend.

• Alter the ACS routines in the SMS DASD allocation. Assign no class to temporary data sets. The fourth node of the name is the same as the dump process JCL job name or procedure name.

  Note: These changes are only for DASD history files that are allocated with SMS. Non-DASD and non-SMS allocations are not affected by this remedy.

PMGMTC(class|NONE|*)

'class' is the IBM DFSMS management class to be used when creating SMF history files in the primary pool. Up to eight characters can be specified. Specify NONE to reset the storage class. To use the value of the PMGMTC operand on the global OPTIONS statement, code PMGMTC(*).

If using DASD for history files, this operand allocates files only to SMS-managed volumes.

Note: Some issues can arise with DASD history file allocations based on how SMS is set up at your data center.

For DASD history allocations with the DYNAM option set, there must be a temporary history file. This file is allocated in the JCL indicating the maximum size of the history files. SMS may not allow the allocation on the storage class that is indicated in the PSTORC operand and indicates an allocation error for the history file. This action causes the dump process to end prematurely.

To avoid this issue, here are some remedies that you can use:

• Include a data set name on the history DD statement. This inclusion can be any valid data set name that would be allocated in the storage class that is indicated in the PMGMTC operand.

  Note: This remedy is the simplest and the one that we recommend.

• Alter the ACS routines in the SMS DASD allocation to assign no class to temporary data sets, where the fourth node of the name is the same as the dump process JCL job name or procedure name.

  Note: These changes are only for DASD history files that are allocated with SMS. Non-DASD and non-SMS allocations are not affected by this remedy.

PDATAC(class|NONE|*)

'class' is the IBM DFSMS data class to be used when creating SMF history files in the primary pool. Up to eight characters can be specified. Specify NONE to reset the storage class. To use the value of the PDATAC operand on the global OPTIONS statement, code PDATAC(*).

If using DASD for history files, this operand allocates files only to SMS-managed volumes.

Note: Some issues may arise with DASD history file allocations based on how SMS is set up at your data center.

For DASD history allocations with the DYNAM option set, there must be a temporary history. This file is allocated in the JCL that indicating the maximum size of the history files. SMS may not allow the allocation on the storage class that is indicated in the PSTORC operand and indicates an allocation error for the history file. This action causes the dump process to end prematurely.

To avoid this issue, here are some remedies that you can use:

• Include a data set name on the history DD statement. This can be any valid data set name that would be allocated in the storage class that is indicated in the PDATAC operand.

  Note: This remedy is the simplest and the one that we recommend.

• Alter the ACS routines in the SMS DASD allocation to assign no class to temporary data sets, where the fourth node of the name is the same as the dump process JCL job name or procedure name.

  Note: These changes are only for DASD history files that are allocated with SMS. Non-DASD and non-SMS allocations are not affected by this remedy.

ADEVN(dname|NONE|*)

'dname' is the esoteric device name to be used when creating SMF history files in the alternate pool. Up to eight characters can be specified. If no device name or SMS classes are specified and the DYNAM option is enabled, the default device name used is the device name used for the primary pool. Specify NONE to reset the device name. To use the value of the ADEVN operand on the global OPTIONS statement, code ADEVN(*).

Note: If you are changing the ADEVN parameter from one tape unit name to another, from tape to DASD, or DASD to tape, immediately run a TAPEINIT command against this SID.

If using DASD for history files, this parameter must only be used for non-SMS managed volumes.

Note: When a history file (HISTORY2) DD statement with the UNIT parameter is present in the DUMP JCL, the UNIT parameter specification overrides the ADEVN option.

ASTORC(class|NONE|*)

'class' is the IBM DFSMS storage class to be used when creating SMF history files in the alternate pool. Up to eight characters can be specified. Specify NONE to reset the storage class. To use the value of the ASTORC operand on the global OPTIONS statement, code ASTORC(*).

If using DASD for history files, this operand allocates files only to SMS-managed volumes.

Note: Some issues may arise with DASD history file allocations based on how SMS is set up at your data center.

For DASD history allocations with the DYNAM option set, there must be a temporary history file. This file is allocated in the JCL that indicating the maximum size of the history files. SMS may not allow the allocation on the storage class that is indicated in the ASTORC operand and indicates an allocation error for the history file. This action causes the dump process to end prematurely.

To avoid this issue, here are some remedies that you can use:

• Include a data set name on the history DD statement. This can be any valid data set name that would be allocated in the storage class that is indicated in the PSTORC operand.

  Note: This remedy is the simplest and the one that we recommend.

• Alter the ACS routines in the SMS DASD allocation to assign no class to temporary data sets, where the fourth node of the name is the same as the dump process JCL job name or procedure name.

  Note: These changes are only for DASD history files that are allocated with SMS. Non-DASD and non-SMS allocations are not affected by this remedy.

AMGMTC(class|NONE|*)

'class' is the IBM DFSMS management class to be used when creating SMF history files in the alternate pool. Up to eight characters can be specified. Specify NONE to reset the storage class. To use the value of the AMGMTC operand on the global OPTIONS statement, code AMGMTC(*).

If using DASD for history files, this operand allocates files only to SMS-managed volumes.

Note: Some issues may arise with DASD history file allocations based on how SMS is set up at your data center.

For DASD history allocations with the DYNAM option set, there must be a temporary history file that is allocated in the JCL that indicating the maximum size of the history files. SMS may not allow the allocation on the storage class that is indicated in the ASTORC operand and indicates an allocation error for the history file. This action causes the dump process to end prematurely.

To avoid this issue, here are some remedies that you can use:

• Include a data set name on the history DD statement. This name can be any valid data set name that would be allocated in the storage class that is indicated in the AMGMTC operand.

  Note: This remedy is the simplest and the one that we recommend.

• Alter the ACS routines in the SMS DASD allocation to assign no class to temporary data sets, where the fourth node of the name is the same as the dump process JCL job name or procedure name.

  Note: These changes are only for DASD history files that are allocated with SMS. Non-DASD and non-SMS allocations are not affected by this remedy.

ADATAC(class|NONE|*)

'class' is the IBM DFSMS data class to be used when creating SMF history files in the alternate pool. Up to eight characters can be specified. Specify NONE to reset the storage class. To use the value of the ADATAC operand on the global OPTIONS statement, code ADATAC(*).

If using DASD for history files, this operand allocates files only to SMS-managed volumes.

Note: Some issues may arise with DASD history file that is allocations based on how SMS is set up at your data center.

For DASD history allocations with the DYNAM option set, there must be a temporary history file that is allocated in the JCL indicating the maximum size of the history files. SMS may not allow the allocation on the storage class that is indicated in the ASTORC operand and indicates an allocation error for the history file. This action causes the dump process to end prematurely.

To avoid this issue, here are some remedies that you can use:

• Include a data set name on the history DD statement. This name can be any valid data set name that would be allocated in the storage class that is indicated in the ADATAC operand.

  Note: This remedy is the simplest and the one that we recommend.

• Alter the ACS routines in the SMS DASD allocation to assign no class to temporary data sets, where the fourth node of the name is the same as the dump process JCL job name or procedure name.

  Note: These changes are only for DASD history files that are allocated with SMS. Non-DASD and non-SMS allocations are not affected by this remedy.

  If a history file (HISTORYn) DD statement is coded for the configuration, any SMS construct parameters (STORCLAS, MGMTCLAS, or DATACLAS) that are coded in the DD statement or assigned by the operating system as defaults will override the PSTORC, PMGMTC, PDATAC, ASTORC, AMGMTC, and ADATAC specifications.

SDAY(hhmm)

Specifies the hour (hh) and minute (mm) that CA SMF Director is to treat as the logical start of a day. If this operand is not coded, days start at the value indicated in the OPTIONS statement for this configuration. If no value is set, the value defaults to midnight, which is coded as SDAY(0000).

Note: The global SDAY value is used to determine the starting and ending times for all EXTRACT and PRINT requests. The exception is when the FROM, JFROM, TO, or JTO operand gives a specific starting or ending time. The value that is specified here is used for the daystacking feature only.

FALLBACK(mmddyy|000000 hhmm)

This operand is used to set the date, hour, and minute when clocks fall back one hour when daylight savings time ends. The first value in the operand indicates the date as a two-digit month, two digit day and two digit year, with the year representing the years 1960 through 2059. A special date value of 000000 can be used to deactivate the operand.

The time value set indicates the time of day when the clock is set back. For example, if the clock change is at 3 AM to set the time back to 2 AM, code the second value as 0300.

Sample DUMPOPTIONS Statement:

COMPILE CONFIGURATION STORE.
  BEGIN CONFIG(002) SID(XE96) NAME('C.A. XE96')
    DUMPOPTIONS COPIES(2) NOCATLG SCRATCH NOVERIFY
      RETPD(002) ARETPD(001) PREFIX(SYSPROG.CASMF.XE96)
      LSNAME(IFASMF.ALL,IFASMF.T30,IFASMF.RMF)
      TRTCH(NOCOMP) ATRTCH(COMP).
  END CONFIG(002).

DUMPOPTIONS statement output:

CA                                              AUDIT TRAIL REPORT                            SMFD       PAGE     1
 CA SMF Director     12.7                                                           SYSA      19 SEP yyyy  10:40:51
 
 
  COMPILE CONFIGURATION STORE .
 
  BEGIN CONFIG(002) SID(XE96) NAME('C.A. XE96') .
 
  DUMPOPTIONS COPIES(2) NOCATLG SCRATCH NOVERIFY
  RETPD(002) ARETPD(001) PREFIX(SYSPROG.CASMF.XE96)
  LSNAME(IFASMF.ALL,IFASMF.T30,IFASMF.RMF)
  TRTCH(NOCOMP) ATRTCH(COMP).
 
  END CONFIG(002)  .
CAF1301I  CONFIGURATION DEFINITION XE96 STORED