OPTIONS

The OPTIONS control statement allows the specification of CA SMF Director program product options. The OPTIONS statement can be used as a standalone statement or can appear after the COMPILE CONFIGURATION STORE control statement. This statement must also be within the definition of a new configuration or the updating of an existing configuration. If you are unsure about the current configuration definitions, use the LISTC SID (sidid) or LISTC All command for a list of current parameter values. Use this list for a configuration during the process to add OPTIONS values. When you are updating a configuration, any values that are not explicitly defined for a particular configuration contain default values.
smfd
The OPTIONS control statement allows the specification of CA SMF Director program product options. The OPTIONS statement can be used as a standalone statement or can appear after the COMPILE CONFIGURATION STORE control statement. This statement must also be within the definition of a new configuration or the updating of an existing configuration. If you are unsure about the current configuration definitions, use the LISTC SID (sidid) or LISTC All command for a list of current parameter values. Use this list for a configuration during the process to add OPTIONS values. When you are updating a configuration, any values that are not explicitly defined for a particular configuration contain default values.
The standalone OPTIONS statement is valid only if there are existing configurations that are defined. Any values that are not explicitly coded in standalone OPTIONS statements remain unchanged and contain previous values.
This example shows output from a successful update of OPTIONS values.
Statement Format:
OPTIONS
►►─ OPTIONS ─ SDAY(hhmm) ─ MAXLINES(nnn) ─┬───────────────┬───────────────────►                                           ├─ NOAUTODEL ◄ ─┤                                           └─ AUTODEL ─────┘  ►─┬─────────────┬─ SITE(name) ─
┬───────────────────────────┬───┬───────────────────────────┬──►
   ├─ NODYNAM ◄ ─┤              ├─ PDEVN( ─┬─ dname ─┬─ ) ──┤   └─ PSTORC( ─┬─ class──┬─ ) ─┘    ├─ DYNAM ─────┤              │          └─ NONE ──┘                      └─ NONE ──┘    └─ DYNAMVTS ──┘             
                                          
 ►─┬───────────────────────────┬──────────────────────────────────────────────►    ├─ ADEVN( ─┬─ dname ─┬─ ) ──┤└─ ASTORC( ─┬─ class ─┬─ ) ──┤    │          └─ NONE ──┘                   └─ NONE ──┘│  ►─┬───────────────────────────┬──────────────────────────────────────────────►    ├─ PMGMTC( ─┬─ class ─┬─ )──┤└─ PDATAC( ─┬─ class ─┬─ ) ──┤    │          └─ NONE ──┘                   └─ NONE ──┘      │  ►─┬───────────────────────────┬──────────────────────────────────────────────►    ├─ AMGMTC( ─┬─ class ─┬─ )──┤└─ ADATAC( ─┬─ class ─┬─ ) ──┤    │           └─ NONE ──┘                  └─ NONE ──┘      │  ►─┬──────────────┬─┬────────────────────┬────────────────────────────────────►    └─ OVERLAP(n) ─┘ └─ MAXFILESONVOL(n) ─┘  ►────COPIES( ─┬─ 1 ◄ ─┬─ ) ──────┬─────────────┬──────┬───────────────┬──────►                └─ 2 ───┘          ├─ NOCATLG ◄ ─┤      ├─ SCRATCH ─────┤                                   └─ CATLG ─────┘      └─ NOSCRATCH ◄ ─┘  ►─┬─────────────────┬─┬────────────────────────┬─┬─────────────────┬─────────►    ├─ EXPDT(yyyddd) ─┤ ├─ AEXPDT(yyyddd) ◄ ─────┘ └─ TRTCH(value) ──┘    └─ RETPD(nnnn) ───┘ └─ ARETPD(nnnn) ─┘  ►─┬──────────────────────┬────────────────────────────┬──────────────────────►    └─ ATRTCH(value) ─┘    └─ DAYSTACK( ─┬─ NO ◄ ─┬─ ) ─┘                                         └─ YES ──┘  ►─┬────────────────────────────┬─┬─────────────────────────────┬─────────────►    └─ PDSNLARGE( ─┬─ NO ◄ ─┬─) ─┘ └─ ADSNLARGE( ─┬─ NO ◄ ─┬─ ) ─┘                   └─ YES ──┘                     └─ YES ──┘  ►─┬────────────────────┬─────────┬───────────────────┬───────────────────────►    ├─ NOPREFIX ◄ ───────┤         ├─ NOAPREFIX ◄ ─────┤    └─ PREFIX(prefix) ───┘         └─ APREFIX(prefix) ─┘ ►─┬─────────────────────────┬─┬─────────────────────────────┬─────────────►   └─ WTOERR( ─┬─ NO ◄ ─┬─) ─┘               └─ YES ──┘  ►─┬───────────────────────┬──────────────────────────────────────────────────►    └─ FALLBACK(────────────┬──*────┬─)──┘               └ (mmddyy|000000 hhmm) ┘      ►─┬────────────────────────────┬───────────────────────────── . ─────────────►◄    ├─ NOSERVICEDESK ◄ ──────────┤     ├─ SERVICEDESK ──────────────┤     └─┤ SERVICEDESK parameters ├─┘ 
SERVICEDESK parameters
►►─┬─────────────────────┬─┬────────────────────┬─────────────────────────────►    └─ SDHIGHSEVERITY(n) ─┘ └─ SDLOWSEVERITY(n) ─┘  ►─┬─────────────────────────┬─┬───────────────────────────────┬──────────────►◄    └─ SDURL( ─┬─ url ──┬─ ) ─┘ ├─ SDUSERID( ─┬─ user ID ─┬─ ) ─┤               └─ NONE ─┘       │             └─ NONE ────┘     │                                └─ SDPASSWORD(password) ────────┘
Operands and Descriptions:
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 parameter is not coded, a day is considered as starting at midnight (0000).
Note
: The 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 a JTO parameter gives a specific starting or ending time. :
Example: 
If the option SDAY(0600) is in effect, the command
EXTRACT ALL FROM(040208) TO(040608) 
This command causes the extraction of all SMF data from 0600 on April 2, 2008 up to, but not including, 0600 on April 7, 2008.
MAXLINES(nnn)
Specifies the maximum number of lines per page for CA SMF Director SYSPRINT output. "nnn" can be a numeric value from 0 or 10 through 255. The default is 0, which breaks pages every 60 lines.
AUTODEL|
NOAUTODEL
Identifies if CA SMF Director performs the auto-delete feature. If AUTODEL is specified, this product scans the SCDS file for any SMF inventory entries referencing history files. The scan is looking history files that have expired at least three days earlier. If any entries exist, they are deleted from the SCDS and the system catalog entry is deleted too, if it exists. The default is NOAUTODEL.
If an expired history file is on DASD, it is deleted from the volume on which it resides. If it was on DASD but the file has been archived, this product performs the HDELETE operation to delete it from the archive.
The AUTODEL function decides if a history file has expired, based on the file expiration date. The date was set when the file was created and not on the current setting of the RETPD or ARETPD option.
This operand is a global option only. This option can be overridden by setting the EXPDT/RETPD operands on a system-by-system or stream-by-stream basis on the DUMPOPTIONS or STREAMOPTIONS statements.
DYNAM|
NODYNAM
|DYNAMVTS
Controls if this product dynamically allocates history files when performing dump, extract, and print operations:
  • DYNAM allows the dynamic allocation of history files for all dumps and EXTRACT/PRINT operations.
  • (Default) 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. However, this option suppresses the dynamic allocation of output history files from dump operations.
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. For example. PSTORC, and ASTORC. For more information, see the descriptions of the PSTORC and ASTORC operands.
  • The NODYNAM option can cause problems involving incorrect mount messages at installations that employ virtual tape. The DYNAMVTS option can be used to avoid this problem while maintaining control over allocation of output history files during dumps.
  • If the logstream or substream recorded SMF data is managed with any defined configuration, DYNAM must be specified.
SITE(name)
'name' is an optional comment identifying the computing complex of up to 20 characters long and within quotes.
PDEVN(dname)
'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. NONE can be used to reset the device name.
Note:
When changing the PDEVN parameter from one tape unit name to another, from tape to DASD, or from DASD to tape, immediately run a TAPEINIT command against every SID defined in your SCDS.
When using DASD for history files, this parameter must only be used for non-SMS managed volumes.
Note:
When a history file (HISTORY1 or HISTcc1) DD statement with the UNIT parameter is present in the DUMP JCL, the UNIT parameter specification overrides the PDEVN option.
PSTORC(class)
'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. NONE can be used to reset the storage class.
When 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 and indicates the history file largest allowable size. SMS may not allow the allocation on the storage class that is indicated in the PSTORC operand. This operand indicates an allocation error for the history file, causing 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 and the one that we recommend.
    • Alter the ACS routines in the SMS DASD allocation by assigning no class to temporary data sets. Verify that 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 affected by these changes.
PMGMTC(class)
'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. NONE can be used to reset the storage class.
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 and indicates the history file largest allowable.size. SMS may not allow the allocation on the storage class that is indicated in the PSTORC operand. This operand indicates an allocation error for the history file, causing 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 management class that is indicated in the PMGMTC operand. 
    Note:
    This remedy is the simplest one that we recommend.
  • Alter the ACS routines in the SMS DASD allocation by assigning no class to temporary data sets. Verify that 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 that are not affected by this.
PDATAC(class)
'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. NONE can be used to reset the storage class.
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. This file is allocated in the JCL and indicates the history file largest allowable size. SMS may not allow the allocation on the storage class that is indicated in the PSTORC operand. This operand indicates an allocation error for the history file, causing 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 data class that is indicated in the PDATAC operand.
    Note:
    This remedy is the simplest one that we recommend.
  • Alter the ACS routines in the SMS DASD allocation by assigning no class to temporary data sets. Verify that 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.
    When a history file (HISTORY1 or HISTcc1) DD statement is coded for any configuration (a SID, logstream, or substream), any SMS construct parameters (STORCLAS, MGMTCLAS, or DATACLAS) that are coded in the DD statement or assigned by the operating system as defaults override the PSTORC, PMGMTC, and ADATAC specifications.
ADEVN(dname)
'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 that is used is the device name that is used for the primary pool. NONE can be used to reset the device name.
Note:
When changing the ADEVN parameter from one tape unit name to another, from tape to DASD, or from DASD to tape. Immediately run a TAPEINIT command against every SID defined in your SCDS.
  • If using DASD for history files, this parameter must only be used for non-SMS managed volumes.
    Note:
    When a history file (HISTORY2 or HISTcc2) DD statement with the UNIT parameter is present in the DUMP JCL, the UNIT parameter specification overrides the ADEVN option.
ASTORC(class)
'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. NONE can be used to reset the storage class.
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 that indicates the history file largest allowable size. SMS may not allow the allocation on the storage class that is indicated in the ASTORC operand This operand indicates an allocation error for the history file, causing the dump process to end prematurely.
To avoid this issue, here are some remedies you that 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 ASTORC operand.
      Note:
      This remedy is the simplest remedy and the one that we recommend.
    • Alter the ACS routines in the SMS DASD allocation by assigning no class to temporary data sets. Verify that 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.
AMGMTC(class)
'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. NONE can be used to reset the storage class.
If using DASD for history files, this operand allocates files only to SMS-managed volumes.
Note:
Some issues can 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 that indicates the history file largest allowable size. SMS may not allow the allocation on the storage class that is indicated in the ASTORC operand. This operand indicates an allocation error for the history file, causing 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 management class that is indicated in the AMGMTC operand.
    Note:
    This remedy the simplest and the one that we recommend.
  • Alter the ACS routines in the SMS DASD allocation by assigning no class to temporary data sets. Verify that 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.
ADATAC(class)
'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. NONE can be used to reset the storage class.
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 that is allocated in the JCL that indicates the history largest allowable size. SMS cannot allow the allocation on the storage class that is indicated in the ASTORC operand. This operand indicates an allocation error for the history file, causing 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 data 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 by assigning no class to temporary data sets. Verify that 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.
    When a history file (HISTORY2 or HISTcc2) DD statement is coded for any configuration (SID, logstream, or substream), any SMS construct parameters (STORCLAS, MGMTCLAS, or DATACLAS) that are coded in the DD statement or assigned by the operating system as defaults override the ASTORC, AMGMTC, and ADATAC specifications.
OVERLAP(n)
'n' can be from 0 through 300 seconds, which is the maximum allowable overlap of SMF dump history files before CA SMF Director considers a file to be in an 'overlap' condition. The default is zero.
For example, assume that two SMF data history files contain these date ranges:
  • File A's date range is 09/08/00 08:00:00 - 09/08/00 12:15:45
  • File B's date range is 09/08/00 12:15:43 - 09/08/00 17:30:55
If OVERLAP(0) was specified, File B would contain overlapped data with File A. If OVERLAP(3) was specified, neither of these files would be considered to contain overlapped data.
Note
: We recommend that you observe the overlap conditions that occur and analyze them to see if they are truly overlaps. They may be records that are written with timestamps in error. These conditions are especially true with non-IBM SMF records that may be created with timestamps that do not account for leap seconds.
MAXFILESONVOL(n)
Indicates the maximum number of history files that can be written to a single tape volume. With some devices that use very large tapes, performance issues can occur if a large number of files are written to the tape. Using this operand, the number of files that are placed on one tape can be limited so that the performance issues are avoided. The value of the operand can be set to any integer value from 1 to 32760. If this operand is not specified, a default value of 300 is set.
COPIES(
1
|2)
Specifies whether this product can create a duplicate copy of the dumped SMF data (duplexing). This procedure is done if the COPIES operand is not specified for the system with the DUMPOPTIONS or stream with the STREAMOPTIONS. 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 recommended setting COPIES(2) for all SMF data that that is kept on a long-term basis.
CATLG|
NOCATLG
Indicates whether CA SMF Director catalog the history file data set, creating an entry within the system catalog, or not. The default is NOCATLG. This value can be overridden on a system basis using DUMPOPTIONS or on a stream basis using STREAMOPTIONS.
Note:
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 get archived and then subsequently restored to a different volume. That action causes a S213 ABEND in a subsequent EXTRACT that attempted to access the history file. The reason is the EXTRACT would look for the file on the volume on which it originally resided.
Note:
If the SMS operands are in use, SMS can override the NOCATLG/CATLG specification.
NOSCRATCH
|SCRATCH
Specifies whether CA SMF Director can request specific or nonspecific magnetic tape volumes when creating history files:
SCRATCH
Specifies if, this product performs a nonspecific mount request for a scratch tape. This action is done when a new tape volume is needed for a history file for all configurations that do not have a specific setting of NOSCRATCH.
NOSCRATCH
Specifies if, this product selects a volume serial from the predefined pool of volumes. This action is done when a new tape volume is needed for a history file unless the configuration has a specific setting of SCRATCH. For more information about setting up the predefined pool of tape volumes, see the DUMPTAPES control statement.
The value that is specified here is used for all configurations if UPSCRATCH is specified on the DUMPOPTIONS statement.
Notes:
  • We recommend using SCRATCH when [set the ca1tm variable for your book], [assign the variable value for vtape in your book], or [set the ttm variable for your book] are used.
  • If logstreams or substreams are going to be dumped in a configuration, SCRATCH must be set for that configuration. If streams are going to be used, we recommend that the SCRATCH operand be set in each configuration.
EXPDT(yyyddd)|RETPD(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 Julian date format. The default is EXPDT(0) or RETPD(0), which causes this product not to set an expiration date for the history file.
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, because 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 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 for configurations that do not have a specific EXPDT or RETPD. If the expiration date is specified, it must be in Julian date format. The default is EXPDT(0) or RETPD(0), which causes this product not to set an expiration date for the history file.
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, because 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 PSTORC 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. 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 a data compression.
COMP
For cartridge tapes, writes the history file with a 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.
Notes:
  • Although this product does support TRTCH options C, E, ET, and T, they are not recommended for history files.
  • If SMS is used in dynamic allocation for history files, the TRTCH setting for that history file can be changed by SMS.
    If TRTCH or ATRTCH are not specified, the system defaults are used.
DAYSTACK(
NO
|YES)
Specifies whether the daystacking feature can be turned on or off. The default is NO, which turns daystacking off. 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.
Note:
When a history file (HISTORY1 or HISTcc1) 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.
Note:
When a history file (HISTORY2 or HISTcc2) 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.
NOPREFIX
|PREFIX(prefix)
Specifies the high level qualifiers to be used for the primary history file data set names. If NOPREFIX is specified, this product uses SYS1.SMFDATA, which is the default.
See Attributes of History Files for more details. The prefix can be up to 26 characters.
NOAPREFIX
|APREFIX(prefix)
Specifies the high level qualifiers to be used for the primary history file data set names if nothing is specified for a specific stream or system. If NOAPREFIX is specified, the value of SYS1.SMFDATA is used for systems that do not have a PREFIX or APREFIX specified. The prefix can be up to 26 characters.
For more information, see the Attributes of History Files.
WTOERR(NO|YES)
Specifies whether error messages with a Return Code of 8 or higher should be written to the operator console. The default is NO. When set to YES, all critical error messages are written to the operator console in addition to their current destination.
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.
NOSERVICEDESK
|SERVICEDESK
SERVICEDESK specifies that an attempt can be made to open a Service Desk request in case of an error during SMP dump processing. NOSERVICEDESK is the default.
SDHIGHSEVERITY
Specifies the severity level of high Service Desk requests that this product can open. The value can be set to any value through 1 and 4. The value itself also becomes the lower bound for the value of SDLOWSEVERITY. If operand is not specified and the SERVICEDESK operand is specified, the value defaults to 2.
SDLOWSEVERITY
Specifies the severity level of low Service Desk requests that this product opens. The value can be set to any value between the value of SDHIGHSEVERITY and 5. The default value, if the operand is not specified is 4.
Note:
If only one severity level is desired for all CA SMF Director, the value of SDHIGHSEVERITY and SDLOWSEVERITY can be set to the same value from 1 to 4.
SDURL
Specifies an alternate URL for the Service Desk Web Service if the default Service Desk Web Service in the CA Common Services SOAP Client Service (CAISDI/soap) address space does not indicate the desired Service Desk instance. NONE can be used to reset the URL.
Note:
The URL value is case-sensitive and must be enclosed in single quotes because it contains special characters.
SDUSERID
Specifies an alternate user ID for the Service Desk Web Service if the default value set in the CA Common Services SOAP Client Service (CAISDI/soap) address space is not the correct User ID for the Service Desk. If the SDUSERID operand is coded, SDPASSWORD is required. NONE can be used to reset the user ID. If NONE is used, the alternate password for Service Desk is also reset, and the SDPASSWORD is ignored.
SDPASSWORD
Specifies an alternate password for the Service Desk Web Service if the default value set in the CA Common Services SOAP Client Service (CAISDI/soap) address space. If the SDUSERID operand is coded, SDPASSWORD is required; otherwise, it is ignored.
Note:
The operand is case-sensitive. If the operand contains special characters, it must be contained in single quotes.
Sample OPTIONS Statement:
OPTIONS AUTODEL DYNAM   PSTORC(TAPESILO)
The OPTIONS statement output:
 CA                                              AUDIT TRAIL REPORT                            SMFD       PAGE     1  CA SMF Director     12.7                                                             SYSA      27 JUL yyyy  13:23:45      COMPILE CONFIGURATION STORE.    OPTIONS AUTODEL DYNAM  PSTORC(TAPESILO) .     BEGIN CONFIG(001) SID(XAT1) NAME('C.A. HERNDON VA') .      DUMPOPTIONS COPIES(1) CATLG SCRATCH   NOVERIFY        RETPD(1095) PREFIX(ELLPH01.SF16)       ARETPD(1461)     END CONFIG(001)  .    CAF1301I  CONFIGURATION DEFINITION XAT1 REPLACED      COMPILE CONFIGURATION STORE.      BEGIN CONFIG(002) SID(XAD1) NAME('C.A. ISLANDIA TSO1') .        DUMPOPTIONS COPIES(2) CATLG NOSCRATCH NOVERIFY          ARETPD(1461) RETPD(1095)          PREFIX(ELLPH01.SF16).      END CONFIG(002)    .    CAF1301I  CONFIGURATION DEFINITION XAD1 REPLACED    CAF2900I  RUN COMPLETE