Control Statements and Tables › CA JARS Control Statements › OPTION Statement

OPTION Statement

The OPTION statement is used to invoke specific CA JARS options and features. Its use is optional. Customers outside of the United States can choose to use a currency symbol other than $, or to report times and dates with delimiters other than : and /. The OPTION statement is the mechanism for defining the additional features desired. This is a global statement; that is, the set code must be blank, as this statement applies to the entire job (all reports in the run).

The OPTION parameters are:

• The Snap Limit option allows the user to alter the limit of records to be snapped. Input SMF data rejected as invalid is displayed on the SNAPDUMP output file by means of the SNAP macro instruction. A limit of 10 is placed on the number of SNAPs that are issued in a single run. In position 10 code a decimal number that is one greater than the number of SNAPs desired. The default is 0011, which permits 10 SNAPs in a single run. Zero (0) removes the limit of the number of records that will be SNAPed.
• The CONFIG/CONFIGX option causes CA JARS to determine I/O device type from the information available in the SMF data in the absence of a CONFIG/CONFIGX Table entry for a given device address/device number. This capability may be of value to users for a variety of reasons, such as data from more than one system where the same device addresses are not the same device type, or when there are more devices than the maximum allowed by this product.

  0

  Causes CA JARS to rely on the CONFIG/CONFIGX Table alone.

  1

  Causes CA JARS to search the CONFIG/CONFIGX Table first, then if no entry is found, to rely on the generic SMF device information. This is the default.

  There are several reasons why CONFIG/CONFIGX statements may need to be used:

  • The channel equate feature should still be used to identify those devices which may be accessed through more than one address.
  • The logic of the System Use Disk And Tape Activity Report and the Resource Utilization Graph depend on the presence of CONFIG/CONFIGX Table entries.
• The SMF record option is supplied to support users who do not produce SMF type 30 Interval records. Setting this switch to 1 will cause CA JARS to ignore SMF type 30 records, and process SMF type 4/5 records instead. By default, the SMF type 30 records are processed, and the SMF type 4/5 records are ignored.
• The Program Bucket option increases the name limit for the Program Activity Analysis Report. Depending on main memory availability, up to 3,000 different program/job names can be processed successfully in generating this report. To increase this capability, code the desired new limit value here. The maximum is 9999.
• The Service Limit Scale Factor permits the user to adjust the service units reported by a factor in order to avoid a data element overflow. Installations whose SRM factors are specified in such a way that service units accumulate numbers that are too large, may encounter data element overflow problems in several areas when processing large amounts of data. Possible occurrences of these kinds of problems may be prevented by activating logic which divides service units at the step level by a user-specified scaling factor. To set a value for this scaling factor, code the 7 digit decimal number desired. For example: 0001000 equals 1,000. The default value is 0000000.
• The Turnaround Calculation option provides for selecting alternative methods for calculating turnaround time, which some installations may find preferable. Zero (0) is the default. Code one of the following:

  0  TURNAROUND TIME = JOB PURGE TIME - READER START TIME(default)
  
  1  TURNAROUND TIME = JOB TERMINATION TIME - READER START TIME(method 1)
  
  2  TURNAROUND TIME = LAST WRITER END TIME - JOB START TIME(method 2)
  

• The Comma Option and the PERIOD option, together, cause the reversal of the use of commas and periods in numeric fields on User-Defined Reports. The number 8,234.00 becomes 8.234,00 following European conventions. Any character may replace a comma or a period in numeric fields, by coding the desired character(s) here.
• The Time option allows the format of time fields to be changed. Hours-minutes-seconds are normally edited as HHHH.MM.SS. It is possible to replace the period (.) as a separator by coding the desired character. The default is a period.
• The Date option permits the user to replace the / in dates on User-Defined Reports with any delimiter. For example, some users may prefer to have dates edited as YY.MM.DD instead of YY/MM/DD (the default).
• The Currency $ option provides customers with report currencies other than dollars. CA JARS assumes the use of hexadecimal 5B for a currency symbol (usually a dollar sign). Installations electing to use a different character may code the desired character here. The default is a dollar sign ($).
• The SMF format changed with MVS/XA (release 2.1.2). An option allows CA JARS to process SMF records before MVS/XA 2.1.2 (default) or, if coded 1, process MVS/XA 2.1.2 or above.
• The DSA Extract option, if coded Y (yes), permits the user to execute the extract routine of the CA JARS/DSA Option Interface. N is the default that prohibits the execution of the extract routine.
• The Processor Count option is used to override the dynamic calculation of the number of processors in the system. It only affects the Computer Utilization Summary Report and the CPU Activity Report.
• The DB2 Extract option, if coded Y (yes), permits the user to execute the extract routine of the DB2 Interface. N is the default; it prohibits the execution of the extract routine.

  Note: This option should not be confused with the EXTDATA control statement DB2 option which produces EXTDATA records.

• The Suspense option invokes the suspense file feature and controls its logic. In general, once invoked, this feature causes all jobs that are missing certain types of SMF records to be written to a suspense file and reprocessed in a subsequent execution. If a suspense option of 1 is specified, all jobs (and TSO sessions) missing the job purge record (SMF type 26), are suspended. If a suspense option of 2 is specified, all jobs (and TSO sessions) missing the job termination record (SMF type 30-5) are suspended, unless the job consists of only output writer records (SMF type 6), in which case it is processed as though the job termination record is present. EXTDATA records are also processed through the suspend logic and can therefore be written to the suspense file.

  Note: In order to read the suspense file, it must be concatenated to the CAIJSSMF dd statement which must contain at least one SMF record. See the section Using the Suspense File Feature in the "Operating Instructions" chapter for additional details and background information.

• The Suspend Limit is used to force the processing of jobs after a specified number of days, regardless of what types of records are present or absent. This value is relevant only if a 1 or 2 has been specified for the suspense option, and it defaults to 9 days. The difference between a job's reader start date and the current date is calculated and compared to the suspend limit. If the difference is greater than the suspend limit, the job/session is processed and not suspended.
• The IBM NETVIEW Extract option, if coded Y (yes) lets you capture session monitor records, SMF type 39, for later CA JARS Wizard processing. N (No), the default, stops the production of records that can be used by CA JARS Wizard, but does not preclude the production of EXTDATA records based on the SMF Type 39 records. For more information on generating EXTDATA from the NetView Interface, see the EXTDATA Statement section.
• The CPU Position option can be a number from 1 through 4. This indicates where the CPUID should be picked up from within the SYSID field in SMF records. A specification of 1 indicates the first character, 4 the fourth character.
• The Flushed Step option allows the user to select whether flushed steps, identified by SMF30STI having low-order bit set on, should be processed or not. If the option is set to Y then flushed steps are retained.
• The Print Line Length option can be set up to 255 to allow for printers with that carriage width, or for laser printers with lengths up to 255. The default print line length is 132. When setting this option to a value other than 132, the CAIJSPRT, or other print DD statement must have the LRECL specified to the DCB parameter. For example:

  CAIJSPRT  DD  SYSOUT=*,DCB=(LRECL=255,BLKSIZE=2550,RECRM=FB)
  

• The Ignore SMF30 Intervals option causes any SMF30 Subtype 2 or 3 records to be completely ignored in the building of either EXTDATA or Account records. Default processing uses interval records in preference to Step End (Subtype 4) records. By setting the option to Y, only information from SMF30 Subtype 4 records is utilized.
• The % of Total Charge option allows the user to specify whether the field '% of Total Charge,' which is ODE 42, should be calculated at either Detail or Summary levels. The default is Detail.
• The Summarize Display I/O option is used in cases where many Display Devices are allocated. This option causes all Display Devices to be consolidated, thus taking up only one I/O Table entry, giving more space for the other devices, and eliminating the table overflows.
• The Device Connect option collects and totals Device Connect Time (in 1/1000ths of a second) instead of EXCPs, thus giving the user the ability to report and charge on Device Connect Time. Please note that this option affects any chargeback algorithms you now have in place that use Device EXCP counts. If you want to charge or report on EXCPs and Device Connect, both fields are maintained on EXTDATA records.

  Note: This option is not available for FACOM Input SMF data. If the FACOM Input SMF option (position 67) is specified, then the Device Connect option is forced to N (no).

• The Initiator CPU option causes the fields TCB, CPU Time, and SRB CPU Time to contain not only the base CPU Time, but also the initiator timings.
• The Vector CPU option causes accumulation of the Vector CPU fields from SMF30 records. These are the:
  • Vector CPU Time
  • Initiator Vector CPU Time
  • Vector Affinity
  • Initiator Vector Affinity

  These times are accumulated and added to the field Total CPU Time.

• The I/O Interrupt CPU option causes the accumulation of I/O interrupt time from SMF30 records. This field is added to the Total CPU Time field.
• The RCT CPU option accumulates the Region Control Task CPU time, and adds it into the Total CPU Time field.
• The Hiperspace CPU option causes the Hiperspace CPU Time from the SMF30 record to be accumulated into the Total CPU Time field.

  Note: This option is not available for FACOM Input SMF data. If the FACOM Input SMF Option (position 67) is specified then the Device Connect Option is forced to be N (no).

  Note: The CPU options specified in OPTION statement positions 53 through 57 can cause differences in charges if turned on. If all options were turned on, the following would be the calculations for the CPU Time fields.

  CPU Time (SRB) = SRB CPU Time + SRB Initiator CPU Time
  CPU Time (TCB) = TCB CPU Time + TCB Initiator CPU Time
  Total CPU Time = SRB CPU Time + SRB Initiator CPU Time +
                   TCB CPU Time + TCB Initiator CPU Time +
                   Vector CPU Time + Initiator Vector CPU Time +
                   Vector Affinity Time + Initiator Vector Affinity Time +
                   I/O Interrupt Time + Region Control Time +
                   Hiperspace Time.
  

• The SMF30 APPC option takes information for APPC tasks from SMF30 records and places the Send and Receive counts in the TPUT and TGET fields.

  Note: This only applies to APPC tasks. To charge for these fields the APPCRATE must be used.

• The SMF33 APPC option takes information from SMF33 records. These new records have a processing ID of R and are identified by Byte 266 of the Account record set to:

  I

  Inbound

  O

  Outbound

  T

  Transaction

• The CA JARS Resource Management for CICS option 6.2 allows this product to create EXTDATA records for CA JARS Resource Management for CICS Option without preprocessing through the Translate program. See the CA JARS Resource Management for CICS 6.2 User Guide for more information on this option.
• The CA JARS Resource Management for CICS options (positions 63 thru 66) are used in conjunction with the SMF Processor (CAUXEXT) to produce EXTDATA records from CA JARS Resource Management for CICS data.
• The FACOM Input SMF option must be set to Y (yes) for users processing FACOM input SMF data.
• The TCP/IP Connect option allows users to determine whether they receive TCP/IP Connect time for Socket API records. If the TCP/IP option is specified, the records are sorted, which uses more processing time.
• The Service Desk option tells CA JARS to try to open a CA Service Desk request if a product failure occurs. CA JARS will attempt to open the request if the abend code is not 0C7, 0C9, or any completion code ending in 22 or 37 (such as an ABEND722 or ABENDB37). The values for the setting are as follows:

  N

  Service Desk requests will not be opened. (This is the default.)

  Y

  CA JARS will attempt to open Service Desk requests.

• The Unnormalized CPU option only affects customers with processors that utilize the Static Power Saving or Cycle Steering features. When the Static Power Saving feature is present, you can reduce processor power consumption, which also reduces processor speed. The values for the setting are as follows:

  N

  CA JARS will “normalize” or adjust Account File/History File and EXTDATA CPU times to their nominal values, reflecting the amount of CPU time that would have been consumed in full power mode. Normalized or adjusted CPU time is recommended in order to produce repeatable CPU time values for a given unit of work, as well as to provide equitable billing if CPU times are used in Chargeback processing. (This is the default.)

  Y

  CPU times will reflect the raw CPU times collected by SMF.

When the default is taken for Unnormalized CPU (or N is specified) the following CPU time fields will be adjusted:

The EXTDATA fields are as follows:

• EXT30_CPT
• EXT30_CPS
• EXT30_ICU
• EXT30_ISB
• EXT30_JVU
• EXT30_IVU
• EXT30_IIP
• EXT30_RCT
• EXT30_HPT
• EXT30_ASR
• EXT30_ENC
• EXT30_DET
• EXT30_CEP
• EXT30_IFAT
• EXT30_IFAE
• EXT30_IFAD
• EXT30_ICPT
• EXT30_ICPE
• EXT30_ICPS
• EXT30_CEPI
• EXT30_TM_ON_ZIIP
• EXT30_ENCL_TM_ON_ZIIP
• EXT30_DEPN_TM_ON_ZIIP
• EXT30_TM_ZIIP_ON_CP
• EXT30_ENCL_TM_ZIIP_ON_CP
• EXT30_DEPN_TM_ZIIP_ON_CP
• EXT30_ENCL_TX_ZIIP_QUAL
• EXT30_DEPN_TX_ZIIP_QUAL
• EXT30_CRP
• EXT30_ICU_T
• EXT30_ICU_I
• EXT30_ISB_T
• EXT30_ISB_I
• EXT89_UCT
• EXT89_USR