VISFILE

Syntax explanations

1. TYPE=NONE indicates that you do not want to create a Visualizer file.
2. GMTOFF is used to specify the time stamps for the Visualizer file. 
   • GMTOFF=<offset> indicates that for your Visualizer file timestamps, you want to use a different GMT offset specified or used by default in the SDATE command. Offset can range from -13.0 to +13.0. Fractional parts of an hour are also allowed. 
   • LOCAL specifies that time stamps are converted to the LOCAL time of the machine where the UIE job runs.  
   • SMFTZ specifies that time stamps are converted to the time zone found in the RMF type 70 record.  All data processed in the UIE batch job should be in the same time zone.
3. EXCLUDETBL=<comma-separated list> indicates that you would like to exclude the specified Visualizer table(s) to decrease the size of the VISFILE. Possible values are: JOBS, APPLDETAIL, DEVICEDETAIL, CHANNELS, STORSUB.
4. INCLUDETBL=<comma-separated list> indicates that you would like to create additional Visualizer tables. Possible values are CPMDCTD, CRYPTOD, DEVTOP, IMSDBD, IMSLOGD, IMSSTORD, JOBD, PRINTRD, SUBSYSDSN, SUITEDSN, SYSPCIED, TRANDETAIL, WKLTOP, and XCFPSD.

   • CPMDCTD indicates that UIE can generate a CPU Measurement Facility Counters table. This table contains CPU counter metrics from the SMF type 113-1 records.

   • CRYPTOD indicates that UIE can generate a Crypto Coprocessors table. This table contains metrics about each crypto co-processor.  The data for this table comes from the RMF type 70 subtype 2 records.                       

   • DEVTOP indicates that UIE can generate the DASD top 10 tables DEVTOP10, DEVRES10, DEVIOS10, and DEVACT10. Because these tables require extra resources to create and sort the data, they are not created by default.
   • JOBD indicates that UIE can generate a new Dynamic Job table. This table contains information similar to the JOBS table. The difference is that in the JOBS table, each job, no matter how long, is represented by one record, but in the JOBD table the activity of each job, in each Visualizer interval, is represented by a separate record. This enables you to compare CPU consumption for different jobs for a particular interval.

   • Visualizer uses the JOBD table to create several new graphs, such as:

     • Most Active Jobs in Selected System(s)
     • Most Active jobs in Selected Suite(s)
     • Most Active Jobs in Selected Service Class(es)
     • Most Active Jobs in Selected Report Class(es)

     ​​​​​

     Warning

     Important

     ​Specify the JOBD parameter if you want to collect information for use in Job/STC reports in the BMC AMI Cost Management product.

     ​

     The JOBD table can be very large, therefore, it is not created by default.

     Warning

     Important

     You can use commands CUTJOBDURN and CUTJOBCPU to decrease the size of JOBD table. The CUTJOBDURN and CUTJOBCPU parameters are applied to the whole job, not just to the activity in an individual interval.

   • IMSDBD indicates that UIE can generate an IMS subsystem DB I/O Activity table. This table contains metrics about IMS database I/O activity. The data for this table comes from the BMC AMI Ops Monitor for IMS Online SMF Statistics records.

   • IMSLOGD indicates that UIE can generate an IMS Subsystem Log and Latch activity table. This table contains metrics for IMS Log and Latch usage. The data for this table comes from the BMC AMI Ops Monitor for IMS Online SMF statistics records.

   • IMSSTORD indicates that UIE can generate an IMS Subsystem Storage and Pool Activity table. This table contains metrics for IMS storage and pool usage. The data for this table comes from the BMC AMI Ops Monitor for IMS Online SMF Statistics records.      

   • PRINTRD indicates that UIE can generate the Printers (static) and Printer Metrics tables. These tables contain detailed information about all printers, including the count of print lines and pages.

   • SUBSYSDSN indicates that UIE can generate a Subsystem by Data Set table. This table contains information about the data sets being used by each subsystem. Because this table can be very large, it is not created by default.
   • SUITEDSN indicates that UIE can generate a Suite by Data Set table. This table contains information about the data sets being used by each suite. Because this table can be very large, it is not created by default.
   • SYSPCIED indicates that UIE can generate a PCIE Performance Metrics by System table. This table contains metrics about PCIE performance (zEDC).
   • TRANDETAIL indicates that UIE can generate a new Application Transaction table. This table contains detailed information about each transaction in each application. Transaction is defined as:
     • CICS—Transaction name
     • DB2—Based on the connection type, this is the correlation ID for subsystem types, plan name for non subsystem types
     • IMS—PSBname

     • MQ—Correlation ID

       Warning

       Important

       Subsystem transaction IDs may contain special characters, including the following values:

       $ @ # . / - _ % & ? ! : | " = ¬ , ; < >

       Special characters contained in a transaction name are written to the Visualizer file with the exception of the comma, which is a reserved character for the Automator population process. A comma is converted to a left curly bracket { when the transaction name is written to the Visualizer file.  

       If you have a large number of unique transactions, the transaction detail option can generate a large volume of data. This results in a larger Visualizer file and a larger Visualizer database. You can also specify that UIE only create transaction detail for specific applications. For more information, see APPL.

   • WKLTOP indicates that UIE can generate the Workload top 10 tables RPGTOP10 and WKLTOPD. Because these tables require extra resources to create and sort the data, they are not created by default.
   • XCFPSD indicates that UIE can generate an XCF Metrics by Path table. This table contains data for XCF (Cross System Coupling Facility) message traffic between signaling paths connecting the host system and the connected system.

Rules

If the GMTOFF=<offset> parameter is not used, it is assumed to be the same as the SDATE command.

Examples

By default, UIE generates interval timestamps in the VISFILE with the same GMT offset, which was specified in the SDATE command or used by default. However, at times, you might need to generate VISFILE timestamps with a different GMT offset. For that purpose, you can use the GMTOFF parameter. This parameter does not affect the specification of the processing interval, which is defined by the SDATE, STIME, EDATE, and ETIME commands.