Latest Maintenance Release for CA MICS r12.7
8622
24 May 2019
24 May 2019
PRODUCT CHANGE: ACT7270 DATE: October 15, 2011 SUBJECT: Enhancement to Charging Element Definition Panel and MICF Abstracts/Samples Additions PREREQUISITES: ACT7255 BAS7705 COREQUISITES: (DB26799) SUPERSEDES: ACT7256 DESCRIPTION: This product change includes the following solutions for the CA MICS Accounting and Chargeback Option: o Enhanced Charging Elements Definition and Computation Code Panels o Add Abstracts and Sample Reports for MICF Inquiries o Update to Algorithm Specification panel and Rate Report o New Computation Code for DB2 CPU Time o The DAY199 Step Abends With U0300 When All Input Journal Files are Empty or Missing o Charging Algorithms are not Called More Than Once o Control Variables for External File Interface Supported o Qualification Groups that are Assigned to Duplicate Charging Algorithms can be Updated o Minor Documentation Changes Details associated with these solutions are provided below. o Enhanced Charging Elements Definition and Computation Code Panels This product change introduces a line command 'V' to browse the data dictionary description of the data element that is associated with the Computation Code in the Charging Elements Definition, and Computation Code panels. (0150) o Add Abstracts and Sample Reports for MICF Inquiries Updates have been made to add abstracts and sample reports for MICF inquiries. This update provides a means to view documentation and sample reports before executing the inquiries. (0148) o Update to Algorithm Specification panel and Rate Report The raw data metric used to populate data element Accumulated CPU Time zIIP-Eligible Work, (DSUELGZP), is no longer available beginning with DB2 Version 10.1. For DB2 Version 10.1, DSUELGZP is set to zero. Computation Codes 1261 and 1262 include DSUELGZP. Therefore, the Accounting and Chargeback Algorithm Specification panel is updated to generate informational messages when either of these Computation Codes are selected for charging. Also, the Accounting and Chargeback Rate report has been updated to notify customers if duplicate charging will occur when two or more DB2 Computation Codes are selected. (0149) o New Computation Code for DB2 CPU Time A new Computation Code, 1206, is added to simplify CPU time charging for DB2 transactions whose CPU time is not recorded by other address spaces such as CICS, IMS, BATCH, and TSO. - DB2 User Activity File (DB2DSU) file Comp Charging Code Element Label ---- -------- --------------------------------- 1206 DSUCPODB CPU Time Only on a DB2 TCB NOTE: Using both this new Computation Code 1206, as well as Computation Code 1203 (DSUCPUTM - Accumulated CPU Time) can cause duplicate charging. For additional information on how to avoid DB2 duplicate charging, refer to the CA MICS Accounting and Chargeback Guide, Section 3.2.2. (0147) o The DAY199 Step Fails With U0300 When All Input Journal Files are Empty or Missing When all input journal files are empty or missing, the DAY199 step does not fail with the U0999 abend code and a SASLOG WARNING message "Variable WORKAREA has already been defined as numeric". It now fails simply with the U0300 abend code indicating that a restart with SYSPARM=NODATA is the appropriate way to handle this kind of situation. (0143) o Charging Algorithms are not Called More Than Once Charging algorithms are only called once, eliminating duplicate charges due to incorrect multiple calls. (0144) o Control Variables Supported for External File Interface When a Control Variable name is entered for an External File Interface (EFI) on the Algorithm Specification (MAFIACTJ) panel, it will be supported after values and rates are entered and the CA MICS Accounting Algorithm Generator (MAGRUN) has executed. (0145) o Qualification Groups that are Assigned to Duplicate Charging Algorithms can be Updated A Qualification Group that has been assigned to multiple charging algorithms where duplicate charges are possible can be updated by selecting it from the Qualification Groups - Group Specification (MWF;4;2;3;9) panel. After entries are added, deleted, or modified, one is given the choice of accepting or not accepting the changes. (0146)
PRODUCT CHANGE: AUM6450 DATE: March 16, 2010 SUBJECT: Remove SAS/C Dependency PREREQUISITES: AUM6430 BAS7630 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for CA MICS Analyzer Option for MeasureWare: The raw data file parser (the INFILE exit AUMAIFUE) routine is rewritten and made compliant with the IBM XL C compiler to eliminate its dependency on the SAS/C specific toolkit. (0038)
PRODUCT CHANGE: BAS7676 DATE: April 4, 2011 SUBJECT: Q&R Recursive Macro Variable References and Cumulative Q&R Maintenance PREREQUISITES: BAS7680 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solutions for the CA MICS Q&R Workstation: o Eliminated Recursive Macro Variable References o Provided Code to Calculate MEAN Values o Prevented Q&R Mainframe Server Abend S522 o Provided a Symbolic JCL Parm for Q&R Parm Specification o Corrected the Q&R Option to Force Abort on Empty File o Corrected Q&R Input File Observation Count Checking Details associated with these solutions are provided below: o Eliminated Recursive Macro Variable References Recursive macro variable references were detected in 2 Q&R z/OS macros by SAS version 9.2. These and the return code 4 in the RC column of the Display Output window that they caused are eliminated. (0308) o Provided Code to Calculate MEAN Values When a MEAN statistical value is requested by a Q&R summarization step that is processing a non-MICS (not in a CA MICS data base) file, the base platform code now includes the necessary code to calculate the MEAN. In addition, the ID statement of SAS PROC SUMMARY, used by Q&R summarization to include all non-numeric data elements in the output data set, is activated. (0316) o Prevented Q&R Mainframe Server Abend S522 The EXEC statement parameter TIME=NOLIMIT is now specified to prevent the Q&R mainframe server from abending due to a continuous wait state exceeding the installation's time limit for such. (0318) o Provided a Symbolic JCL Parm for Q&R Parm Specification Some installations need to run more than one Q&R mainframe server where each instance requires a different set of execution parameters. A symbolic JCL parameter named MQRPARMS has been provided for this purpose. Thus, a set of MQR parameters can be placed in any member in sharedprefix.MICS.PARMS, and then this member can be equated to MQRPARMS on the EXEC statement in the MQRHOST job. For example: //MQREXEC EXEC MICSSVR,MQRPARMS=MQRPARM2, (0319) o Corrected the Q&R Option to Force Abort on Empty File The provision to abort the execution of a query with ABEND code U0300 when any input file is empty is corrected so that inappropriate U0300 abends do not occur. (0320) o Corrected Q&R Input File Observation Count Checking All files specified for input to query steps File Selection, Concatenation, and Merge are now checked to alert the user of files that may contain no observations. (0321)
PRODUCT CHANGE: BAS7677 DATE: February 24, 2011 SUBJECT: New CA MICS Reporting User Guide and Cumulative Maintenance PREREQUISITES: BAS7680 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solutions for the CA MICS base platform: o Created a New CA MICS Reporting User Guide o Corrected INCRccc Processing of SMF Director Input o Corrected Dialog Errors After Global Parm Modification o Added Abstract and Sample Report for MTILD7 Inquiry o Corrected One or Two Character SYSID Values o Miscellaneous Documentation and Message Text Corrections Details associated with these solutions are provided below: o Created a New CA MICS Reporting User Guide A new guide has been written to show users how to meet the challenges of providing information that affects IT management decisions. It provides an overview of basic reporting features and tools, along with some common SAS language and CA MICS-based facilities that will assist them in retrieval and reporting. (0601) o Corrected INCRccc Processing of SMF Director Input After application of product change BAS7611, first delivered with r12.5, the incremental update job (INCRccc) for a component may create a WORK.TMPJHL data set with variables containing null values. This occurs only when input is being supplied by the SMF Director interface. This error is corrected. (0588) o Corrected Dialog Errors After Global Parm Modification After application of product change BAS7540, first delivered with r12 SP2, dialog errors may be obtained when exiting from the option to modify "CA MICS Global Parameters for ISPF Applications" (MWF;5;0;2). These errors are corrected. (0612) o Added Abstract and Sample Report for MTILD7 Inquiry The abstract and sample report for MICF inquiry MTILD7 (MTI Components: Elements) are added. (0616) o Corrected One or Two Character SYSID Values The SAS format in prefix.MICS.MUOLIB named $SYSID is now correctly generated when a logical SYSID specified in either sharedprefix.MICS.PARMS(CPLXSID) or prefix.MICS.PARMS(SYSID) is only 1 or 2 characters long. This ensures that the SYSID data element is assigned such a short value correctly. (0617)
PRODUCT CHANGE: BAS7683 DATE: September 12, 2011 SUBJECT: MICF Reporting Job Stream and Q&R Integration PREREQUISITES: BAS7680 COREQUISITES: BAS7690 SUPERSEDES: BAS7691 DESCRIPTION: This product change includes the following solutions for the CA MICS base platform: o MICF Web Publishing CSV Output o Q&R Integration o Reporting Job Stream Global Options o Reporting Job Stream WORK Data Set Name Incorrect o Reporting Job Stream Erroneously Indicates no Report on Failed Inquiry o Eliminated User Reporting Job stream Contention o Prevented Orphaned Production Reporting Cycle 0 Details associated with each of these solutions are provided below: o MICF Web Publishing CSV Output The MICF Web Publishing (MWP) feature takes the output from MICF inquiries executed within a MICF reporting job stream and converts it to HTML for presentation using a standard web browser. This feature has been enhanced to optionally write the CSV as well as the MICSLOG and SASLOG to the HFS/zFS directory. (0628) o Q&R Integration The Q&R Integration feature writes MICF inquiry output generated from a production or user reporting job stream in a HFS/zFS directory structure compatible with the CA MICS Q&R Workstation. Note: The entire Q&R Workstation product (client/distributed server/mainframe server) must be upgraded to release 12.7 in order for Q&R to process the HFS/zFS files. This integration provides the following benefits: . The Q&R directory structure, coupled with the ability to map the Q&R HFS/zFS directory as an additional drive to the Q&R distributed server, allows the CA MICS utility RMWSLOAD to read directly from the HFS/zFS directory without moving the data to the distributed server for publication of chart and report output. . The Q&R directory structure also facilitates direct viewing of the directory from Q&R Output Retrieval. You do not need to run RMWSLOAD to access job stream output unless you are ready to publish to your web server. This lets you generate View Definition Files to perfect the appearance of the chart prior to publication. . Sharing the HFS/zFS directory between your z/OS Unix (USS) environment and Microsoft Windows lets you publish all your MICF web publishing and Q&R charts to one web server, Microsoft Internet Information Services (IIS). Refer to the MICF Reference Guide or the MICF User Guide for more information on the requirements to use the Q&R Integration feature. (0629) o Reporting Job Stream Global Options Additional options have been added to the shared MICF options for use in the reporting job streams. This enables options to be defined once and then used as the default for new reporting job stream definitions. See the MICF Reference Guide for details related to the shared MICF options. (0630) o Reporting Job Stream WORK Data Set Name Incorrect BAS7630 added the ability to define work space for the production and user reporting job streams at both the job stream and inquiry levels. When viewing or modifying the Work File definition at the job stream level, the panel may erroneously display the name of the data set that precedes it in the job stream data set allocation parameter list, and has been corrected. (0620) o Reporting Job Stream Falsely Indicates no Report on Failed Inquiry A reporting job stream may fail to update the catalog table to indicate the existence of report output when the inquiry ultimately abends, or completes with a return code 8. An attempt to view the inquiry output from MWF 2.1 - Reports and Graphics, indicates no report was produced. However, a report may have been produced and copied to the MWFPDS library as expected, but the catalog is not updated, making the report output unavailable through MWF. (0635) o Eliminated User Reporting Job stream Contention With the User Reporting Automated Inquiry Generation option, a MICF user can add one or more inquiries and then submit the corresponding job stream using the G (Generate) line command in the same MICF session. Contention that causes the job stream to fail results between that job and the MICF session. This contention is now prevented from occurring under all conditions. (0514) o Prevented Orphaned Production Reporting Cycle 0 The Production Reporting cycle 0 data set which becomes orphaned immediately after being created, is no longer created. Consequently, Production Reporting data sets will be named only in the range of cycle 1 to the maximum reporting cycle number. (0622)
PRODUCT CHANGE: BAS7685 DATE: February 15, 2012 SUBJECT: Automatic File Cycle Selection Positioning PREREQUISITES: BAS7680 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for the CA MICS base platform: New support for recording the low and high time stamps of the CA MICS component's input data by data file cycle is implemented. MICF inquiry BASLA6 is delivered to report on the ADMCYC file. It provides a list of which date and time ranges can be found in which cycles across the timespans. This will make selection of the right data file cycles for reporting automatic and can lower resource consumption by processing only the desired data file cycles. This product change is the first step in implementing "Automatic File Cycle Selection" for reporting, meaning that in the future selection by date and time will automatically set the correct cycles for the date and time range selected. (0657)
PRODUCT CHANGE: BAS7690 DATE: December 15, 2011 SUBJECT: Q&R Workstation 12.7 Support PREREQUISITES: BAS7680 BAS7676 BAS7693 BAS7697 COREQUISITES: BAS7683 SUPERSEDES: None DESCRIPTION: This product change includes the following enhancements for the CA MICS Base Platform: o Q&R Workstation 12.7 Support Details associated with these enhancements are provided below: o Q&R Workstation 12.7 Support This product change upgrades the Q&R Mainframe Server to 12.7. Q&R Mainframe Server 12.7 is compatible with Q&R Workstation 12.6 and Q&R Workstation 12.7. - The CA MICS Mainframe Server is upgraded to submit individual batch jobs for each Q&R submitted query, which enables concurrent query execution. (0641) - The CA MICS Mainframe Server now provides the use of individual mainframe security credentials if requested. (0642) - The CA MICS Mainframe Server has been modified to save the query code from a Q&R composed query, directly to a partitioned data set. This facilitates inclusion in a MICF reporting job stream. (0643) - The CA MICS Mainframe Server has been enhanced with the ability to notify the Q&R Distributed Server when a MICF reporting job stream has completed. This provides the Q&R Distributed Server with the information it needs to automatically execute a "Publish Output to Q&R Web Reporting", RMWSLoad job, when the MICF reporting job stream completes. (0645) - A new CA MICS complex level library, sharedprefix.MICS.MQR.TEMPLATE, has been defined to store templates used by the CA MICS Mainframe Server for query execution. (0644) - A new complex level JCLGEN job, JCLGEN3, is delivered to create the templates used by the CA MICS Mainframe Server based on the MICS Administrator selected parameters defined in sharedprefix.MICS.PARMS(JCLDEFC). (0646) - An additional member, MQRUTAB has been added to sharedprefix.MICS.PARMS. This member is read by the CA MICS Mainframe Server and contains the dynamic JCL parameter values needed for each Q&R user to execute queries. (0650) - A new CA MICS job, TMPLTJOB, is created to copy the templates generated by JCLGEN3 to the CA MICS template library. (0648) - Various updates have been made to the CA MICS Planning, Installation, Operation and Maintenance Guide in support of Q&R Workstation 12.7. (0649)
PRODUCT CHANGE: BAS7691 DATE: September 13, 2011 SUBJECT: MICF 2.6 Creates New Private Inquiry Catalog Table PREREQUISITES: BAS7675 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for the CA MICS base platform: MICF Option 2.6, Automatic Inquiry Generation, erroneously creates a new Private Inquiry Catalog Table, ICFICTL, in the user's private tables data set. The default name for this data set is userid.MICS6.USER.TABLES. This problem is caused by a blank value in the variable ICFUTABL that is used to locate the private user tables data set. Since the user tables data set is not found, code is executed to create a new table, and that code has the correct non-blank value. Consequently, that code is successful in creating a new ICFICTL Private Inquiry Catalog Table. This causes any inquiries that previously existed to be lost. This problem becomes evident when you use MICF Option 2.2 to display the Private Inquiry Catalog after using MICF Option 2.6. The display only reflects the inquiries just added using the MICF 2.6 option.
PRODUCT CHANGE: BAS7693 DATE: January 5, 2012 SUBJECT: PSP Prerequisite Order When Corequisite Was Specified and Cumulative Maintenance PREREQUISITES: BAS7660 COREQUISITES: None SUPERSEDES: BAS7686 DESCRIPTION: This product change includes the following solutions for the CA MICS base platform: o Corrected PSP Prerequisite Order When Corequisite Was Specified o Corrected Total Used Percent on File Summary Report o Corrected SAS Format/Informat Print Utility EXEC Mode o Corrected Text of Message BAS00197E o Minor Documentation and Message Text Updates Details associated with these solutions are provided below: o Corrected PSP Prerequisite Order When Corequisite Was Specified When a PSP prerequisite chain includes a product change that also specifies a corequisite, that product change is now applied in the required order. (0623) o Corrected Total Used Percent on File Summary Report The value reported as the total Used Percentage for each information area is now correct on the CA MICS Database Utilization Facility's report with the following multi-line title: CA MICS Space Utilization and Reporting Database Space Utilization File Summary (0624) o Corrected SAS Format/Informat Print Utility EXEC Mode The execution mode for the CA MICS Administrator utility entitled SAS Format/Informat Print Utility is now properly pre-set to BATCH mode. (0625) o Corrected Text of Message BAS00197E The text of message BAS00197E now says that a file specified on a MULTWORK or NOMULT statement is not valid as opposed to unknown since even a known file may be invalid. (0614)
PRODUCT CHANGE: BAS7694 DATE: December 14, 2011 SUBJECT: IPV6 Macro Ownership Change PREREQUISITES: BAS7630 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for the CA MICS base platform: This product change corrects the problem with product change SMF6935, a test PTF, or SMF6940, published as RO38354, where DAILY job step DAY030 or incremental update job step INCRSMF fail with ABEND code U0999. Because the CA MICS macro IPV6 is now used by more than one CA MICS component, it is redelivered with the base platform to make it available for all CA MICS optional products. (0640)
PRODUCT CHANGE: BAS7697 DATE: January 31, 2012 SUBJECT: SAS Version 9.3 Support PREREQUISITES: BAS7680 COREQUISITES: None SUPERSEDES: BAS7695 DESCRIPTION: This product change includes the following enhancements for the CA MICS Base Platform: o SAS Version 9.3 Support ******************** IMPORTANT *********************** * Before upgrading to SAS 9.3, view MBAS problem entry * * 626 for the latest information regarding SAS 9.3 and * * any required SAS hot fixes. * ******************** IMPORTANT *********************** Details associated with these enhancements are provided below: o SAS Version 9.3 Support includes the following enhancements: - The SAS version check has been expanded to include SAS version 9.3. - A new SAS system option, VALIDMEMNAME has been added to the configuration members. - The SAS MVS Environment File, TKMVSENV, is now supported within the JCL. - Several CA MICS Base Platform modules have been changed to eliminate potential SAS errors that appear for the first time with SAS version 9.3.
PRODUCT CHANGE: BAS7699 DATE: May 1, 2012 SUBJECT: Consolidated Maintenance PREREQUISITES: BAS7680 COREQUISITES: None SUPERSEDES: BAS7681 BAS7687 BAS7688 BAS7689 BAS7692 BAS7694 DESCRIPTION: This product change includes the following solutions for the CA MICS base platform: o Added a Warning About Picture Output Formats o Corrected the Current Operation Displayed by Operational Status and Tracking o Corrected MAUPDTE S0C4 ABEND o Corrected First DAILY for Unit ABEND U0999 o Corrected CBSSLCT Limit of 9 $PRMID Control Statements o Improved the Checkpoint Date Range Delete Logic o Corrected Status Information for Standalone Archive Tape Processing Jobs o Corrected The Hardware and SCP Analyzer Guide Table of Contents o Changed Component Ownership of Macro IPV6 o Minor Documentation Changes Details associated with these solutions are provided below: o Added a Warning About Picture Output Formats One of the default MICF print options is to round subtotals before printing. This is not valid when the output format being used contains a PICTURE clause. The CA MICS-supplied MAPCT and various MONEY formats are of this type. To help prevent the invalid combination of ROUND and any PICTURE formats for a report generated by a MICF inquiry, a warning has been added to the panels involved. (0618) o Corrected the Current Operation Displayed by Operational Status and Tracking After a stand-alone AUDIT, HISTW or HISTM job for a unit submitted from the MWF Operational Status and Tracking feature completes, the line for the unit on the feature's display is incorrect. This error is corrected. (0619) o Corrected MAUPDTE S0C4 ABEND After the application of product change BAS7660, first delivered on r12.6 (PSP1104), the MAUPDTE program used by CA MICS maintenance may abend with code S0C4. This error is corrected. (0627) o Corrected DAILY for Unit ABEND U0999 After application of BAS7651, first delivered with r12.6, the DAILY (or INCRccc) job for a unit being executed for the first time, and with SMF Director input, abends with code U0999. This error is corrected. (0632) o Corrected CBSSLCT Limit of 9 $PRMID Control Statements The CA MICS maintenance program CBSSLCT now permits a maximum of 99 incoming $PRMID control statements. (0633) o Improved the Checkpoint Date Range Delete Logic Timestamp analysis of the CA MICS checkpoint logic prevents the reprocessing of previously processed raw data, in the event they are accidentally re-input to the DAILY job. For components processing SMF data, the timestamps are accurate to the SMF header granularity of 1/100th of a second. With today's high speed processors and the 1/100th of a second granularity, it is common to see 10 or more consecutive SMF records that share an identical timestamp value. When the SMF dump process splits a group of records sharing the same timestamp, so that some will be processed by CA MICS today and the remainder tomorrow, tomorrow's records have been date-range deleted. (Note that this does not occur when CA SMF Director is in use.) This product change improves the checkpoint logic so that incoming records with a timestamp equal to the high timestamp in the checkpoint data set are not deleted when appropriate. Note that full implementation of this change requires a companion change in the CA MICS data integration components that are sensitive to this situation. (0634) o Corrected Status Information for Standalone Archive Tape Processing Jobs If the execution of a standalone archive tape processing job (AUDIT, HISTW, HISTM) was problematic, the Run Status Report produced by the last job step and the corresponding message in the MWF Operational Status and Tracking JOBLOG display now give clear indication of this. (0636) o Corrected The Hardware and SCP Analyzer Guide Table of Contents Page numbers greater than 999 in the table of contents of any CA MICS guide are no longer displayed truncated. (0639) o Changed Component Ownership of Macro IPV6 Because the CA MICS macro IPV6 is now used by more than one CA MICS component, it is redelivered with the base platform to make it available for all CA MICS optional products. (0640)
PRODUCT CHANGE: BAS7704 DATE: March 8, 2012 SUBJECT: New CTC Device Type Codes and DSNTYPE=LARGE Specification PREREQUISITES: BAS7630 COREQUISITES: None SUPERSEDES: BAS7706 DESCRIPTION: This product change includes the following solutions for the CA MICS base platform: o Added New z196 Device Type Codes o Updated Extended Built-in Functions Table o Permitted Specification of DSNTYPE=LARGE for Dynamic Allocation in MWF Details associated with these solutions are provided below: o Added New z196 Device Type Codes New z196 device type codes are added to the $DEVTYPS format so that they will be recognized by CA MICS data integration components such as RMF, SMF, SRL and VCA. (0637) o Updated Extended Built-in Functions Table Updates made via BAS7555 to bring the Extended Built-in Functions table in sharedprefix.MICS.LOAD(MADA) up-to-date with current versions of ISPF are restored. These updates were lost when product change BAS7585 was applied. (0652) o Permitted Specification of DSNTYPE=LARGE for Dynamic Allocation in MWF The specification of DSNTYPE=LARGE is now recognized by MWF whenever it is given as an allocation parameter for data sets being allocated dynamically. (0653)
PRODUCT CHANGE: BAS7705 DATE: March 8, 2012 SUBJECT: CA MICS Maintenance Level Setting PREREQUISITES: BAS7676 BAS7677 BAS7680 BAS7683 BAS7685 BAS7690 BAS7691 BAS7693 BAS7697 BAS7699 BAS7704 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for the CA MICS base platform: CA MICS maintenance level setting to end release 12.6 plus minor documentation updates. (0658)
PRODUCT CHANGE: CAP6491 DATE: January 13, 2011 SUBJECT: Consolidated Maintenance PREREQUISITES: CAP6485 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solutions for the CA MICS Capacity Planner Option: o Capacity Adjustment is Active for the WLM Workload Planning Sample Application o TOTCPUTM has Correct Values in the WLM Workload Planning Sample Application o Allow a User to Skip the Event Warning Panel o Resource Component Analysis Job Completes with RC=0 o Workload Characterization Using SAS Job completes with RC=0 o Data From the Desired Number of Days are Selected on DAYNAME for Resource Element Files o Workload Characterization Using Neugents Job Completes with Condition Code 0 o Documentation Updates Details associated with these solutions are provided below. o Capacity Adjustment is Active for the WLM Workload Planning Sample Application The Capacity Adjustment feature allows one to specify the CPU capacity values for a base system and to have the CPU capacity of a new system expressed in terms of the base system. This feature is now active for the WLM Workload Planning Sample Application. The following variables are now defined and populated in the capacity data base: WKLDASRB - Adjusted Workload SRB Time WKLDATCB - Adjusted Workload TCB Time WKLDATCP - Adjusted Workload SRB & TCB Time WKLDACPU - Adjusted Workload Total CPU Time (0075) o TOTCPUTM has Correct Values in the WLM Workload Planning Sample Application The TOTCPUTM now reports the correct total CPU time for a defined workload in the WLM Workload Planning. (0076) o Allow a User to Skip the Event Warning Panel It is now possible to suppress the Event Warning Panel when it is no longer needed for a particular inquiry. (0077) o Resource Component Analysis Job Completes with RC=0 The Resource Component Analysis job completes with a condition code 0 and does not display a WARNING message indicating that the length of character variable DEPVAR has already been set. (0078) o Workload Characterization Using SAS Job completes with RC=0 The Workload Characterization Using SAS job completes successfully so that it produces the report showing descriptive and clustering statistics. (0079) o Data From the Desired Number of Days are Selected on DAYNAME for Resource Element Files When building a Resource Element File with summarization on DAYS and DAYNAME, it is possible to restrict the days selected by coding the weekday names on the DAYNAME line of the "Insert Common Data Selection" panel. If data for the specified weekdays are available on the input datasets, they will be written to the capacity planning data base. (0081) o Workload Characterization Using Neugents Job Completes with Condition Code 0 The job generated by the Workload Characterization Using Neugents Technology from the MWF panel 4;3;2;1 always completes with a condition code 0. (0082)
PRODUCT CHANGE: CAP6492 DATE: February 7, 2012 SUBJECT: Consolidated Maintenance PREREQUISITES: BAS7705 CAP6491 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solutions for the CA MICS Capacity Planner Option: o Enabled Message CAP01150T. o Corrected Simple Regression Analysis Panel Length o Corrected a Dialog Error On File and Data Element Selection Panel o Corrected Loop in Panel CAPG141 o Corrected Resource Element Panel Error Message o Corrected Sample Planning Application Menu Help Panels o Corrected Sample Planning Application Initialization Error Message o Updated z/VM Processor Planning Sample Application o Minor Documentation Updates Details associated with these solutions are provided below. o Enabled Message CAP01150T. A job being run to initialize or update a capacity planning database file that encounters the condition where none of the incoming observations meet the selection criteria will now issue message CAP01150T stating that "no observations met selection criteria". (0083) o Corrected Simple Regression Analysis Panel Length The MICF Dialog Assist error panel is no longer encountered when invoking the Simple Regression Analysis option for workload forecasting. (0084) o Corrected a Dialog Error On File and Data Element Selection Panel The use of question mark support in the Name field of panel CAPG140 entitled CA MICS File and Data Element Selection no longer results in a dialog error when a database ID is not specified. (0085) o Corrected Loop in Panel CAPG141 Panel CAPG141 entitled CA MICS File Selection no longer loops when the user selects more than one database ID before pressing ENTER. Also, the full range of 14 database IDs can now be added to the list of selected IDs on this panel. (0086) o Corrected Resource Element Panel Error Message The ISPF error message displayed on panel CAPG140 entitled CA MICS File and Data Element Selection is correct when the specified input timespan does not allow for the setting of a particular control data element. (0087) o Corrected Sample Planning Application Menu Help Panels All help panels supporting the sample planning applications are updated and synchronized with the options on the Sample Planning Applications menu panel. (0088) o Corrected Sample Planning Application Initialization Error Message When a sample planning application cannot initialize because one or more of the required data elements is not active, the correct error message is displayed. (0089) o Updated z/VM Processor Planning Sample Application Several data elements are no longer valid z/VM data elements and have been removed from the CA MICS Analyzer Option for VM/CMS's System Global Data (VMXSGP) file. The following CA MICS elements are removed from the z/VM Processor Planning sample application: SGPACTVF - Active Vector Facility Users SGPFSTOR - Free Storage Available and In Use SGPFSYUD - Size of System Free Storage in Use SGPFVRUD - Size of V=R Free Storage in Use SGPPCFSU - CP Free Storage Utilization SGPPSVRF - V=R Free Storage Utilization SGPVFLOD - Count of Vector Facility Loads SGPVFOTM - Vector CP Time Used to Switch Users SGPVFVTM - Vector User Time Used while in SIE mode SGPVRFRE - System V=R Free Storage Area Size (0090)
PRODUCT CHANGE: CIC6730 DATE: June 15, 2011 SUBJECT: Support for CICS Transaction Server Release 4.2 PREREQUISITES: CIC6720 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for the CA MICS Resource Management Analyzer Option for CICS: The data elements have been added to both the CICS Application Unit Activity (CICCAU) and CICS User Activity (CICCSU) files to support the new SMF record type 110 subtype 01 performance class metrics introduced by CICS Transaction Server Release 4.2 (CICS 6.7.0). The new elements are listed in Appendix A of this document. See the data dictionary entries for detailed data element information. In addition, minor documentation updates have been made. (0218)
PRODUCT CHANGE: CIC6735 DATE: June 15, 2011 SUBJECT: Support for CICS Transaction Gateway Release 8.0 PREREQUISITES: CIC6715 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for the CA MICS Analyzer Option for CICS: This product change adds new Gateway Daemon Statistics data elements to the Gateway Server Activity (GSA) file in support of CICS Transaction Gateway release 8.0. GSAEXITR - Number of CICS request exit calls GSAHSTNM - CICS Transaction Gateway host name GSAPKNBR - Peak number of XA transactions GSASRVNM - Default server name GSASYNRT - SYNCONRETURN transactions that failed GSAXATHA - XA transactions completed for HA group (0217)
PRODUCT CHANGE: CIC6740 DATE: October 15, 2011 SUBJECT: Performance Improvements and Consolidated Maintenance PREREQUISITES: BAS7705 CIC6730 CIC6735 COREQUISITES: None SUPERSEDES: CIC6722 CIC6736 DESCRIPTION: This product change includes the following solution for the CA MICS Resource Management Analyzer Option for CICS: o Performance Improvements o Add Abstracts and Sample Reports for MICF Inquiries o Activated Audit Archiving for the CICCSU File o Eliminated Warning About the Array CHAR o Reduced CPU Time Consumed by TRANSLATE function o Activated CSYTSQCR and CSYTSQEC in Higher Timespans o Changed DATATYPE for CSYNRTSK and CSYAMXT Elements o Updated Miscellaneous Data Dictionary Text o Corrected Miscellaneous Documentation o Minor Documentation Changes Details associated with these solutions are provided below. o Performance Improvements This product change simplifies code to improve performance. Support for CICS Transaction Server (CTS) Releases prior to CTS 2.2 has been dropped. (219) o Add Abstracts and Sample Reports for MICF Inquiries Updates have been made to add abstracts and sample reports for MICF inquiries. This update provides the means to view documentation and sample report before executing the inquiries. (220) o Activated Audit Archiving for the CICCSU File The following CICS database file, appropriate for accounting purposes, now has audit archiving activated by default: CICCSU - CICS User Activity File This update is being made in sharedprefix.MICS.GENLIB(CICGENIN) so that your present audit archive setting may be changed. One of the system modification steps for this product change gives you relevant instructions. (0212) o Eliminated Warning About the Array CHAR The following message found in the SAS log of the DAY040 job step is eliminated: WARNING: The array CHAR has the same name as a SAS-supplied or user-defined function. Parenthesized references involving this name have been treated as array references and not function references. (0213) o Reduced CPU Time Consumed by TRANSLATE function The CPU-expensive TRANSLATE function is used in the generated prefix.MICS.USER.SOURCE(#CICMSAC) member. At this location, it may be executed millions of times in a single DAY040 job step execution. The CPU cost of executing this function here has been reduced. (0214) o Activated CSYTSQCR and CSYTSQEC in Higher Timespans In the CICS System Activity (CICCSY) file, the following data elements are now active in the DAYS and higher timespans: CSYTSQCR - Number of TS Queues Created CSYTSQEC - Number of TS Queue Extension Created (0215) o Changed DATATYPE for CSYNRTSK and CSYAMXT Elements In the CICS System Activity (CICCSY) file, the following data elements are changed to DATATYPE R (retained): CSYNRTSK - Current Number of Tasks CSYAMXT - Current Tasks Eligible for Dispatch (0216)
PRODUCT CHANGE: DB26792 DATE: May 16, 2011 SUBJECT: Correct Data Elements Initialization PREREQUISITES: DB26790 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for CA MICS Analyzer Option for DB2: The following MICS common data elements are correctly initialized to a character data-type: DB2ACE - Agent Control Element DB2AUTH - Authorization Identifier DB2CORR - Correlation Identifier DB2LUNAM - Logical Unit NAME DB2OPID - Original Operator ID DB2PTASK - Special Transaction Type Identifier DB2UNIQ - DB2 Instance Number UOWID - Unit of Work ID (0165)
PRODUCT CHANGE: DB26794 DATE: May 26, 2011 SUBJECT: Buffer Pool Elements are Populated Correctly PREREQUISITES: DB26790 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for CA MICS Analyzer Option for DB2: Elements that report the buffer pool totals in the DB2 Plan Activity (DB2DSP) and DB2 User Activity (DB2DSU) files are populated correctly. All the elements in the DB2 Buffer Pool Activity (DBPDSB) file are populated correctly. (0172)
PRODUCT CHANGE: DB26795 DATE: April 15, 2011 SUBJECT: Workfile Storage Metrics, Performance Improvements and Consolidated Maintenance PREREQUISITES: DB26790 COREQUISITES: None SUPERSEDES: DB26791 DB26792 DESCRIPTION: This product change includes the following solutions for the CA MICS Analyzer Option for DB2: o Provided Support for Workfile Storage Metrics o All Duplicate Observations are Deleted from the Data Base Files o Eliminated Unneeded Overhead on Sorts for DB2DPP o Improve Performance of Code that Assigns SYSID o Activated Buffer Pool Metrics for Q&R Reporting o Corrected Data Elements Initialization Details associated with these solutions are provided below. o Provided Support for Workfile Storage Metrics Starting with DB2 version 9 release 1, new metrics were introduced to the DB2 statistics record section to provide values that correspond to how the workfile (WF) database is used. In support of this implementation, the following data elements are added to the DB2 Database Activity file as follows: DSDIMAC - Curr Active DM In-Memory Workfiles DSDIMAH - Hi-Watermark Cnt Max DM In-Mem WFs DSDIMSC - Total Used Space DM In-Mem Workfiles KB DSDIMSH - Hi-Watermark Cnt Max Space DM In-Mem WFs DSDRCCD - Committed Delete Read - Rows Accessed DSDRCCI - Committed Insert Read - Rows Skipped DSDRCCU - Committed Update Read - Rows Accessed DSDSIAC - Count of Curr Active Sort In-Mem WFs DSDSIAH - Hi-Watermark Cnt Max Sort In-Mem WFs DSDSISC - Tot Space Used Curr Active Sort In-Mem DSDSISH - Hi-Watermark Cnt Max Space Sort In-Mem DSDW4K - Curr 4KB Tablespace Storage Used KB DSDW32K - Curr 32KB Tablespace Storage Used KB DSDWCTO - Curr Total Workfile Storage Used KB DSDMXWF - Max Allow Per Agent Storage Use Limit KB DSDWFMU - Max Total Workfile Storage Ever Used KB DSDWFNE - Times Max Allow Storage Limit Exceeded DSDWFP1 - Times 32KB Page TS Used Instead of 4KB DSDWFP2 - Times 4KB Page TS Used Instead of 32KB DSDWFRHG - Max RID Blocks Stored to Workfile DSDWFRCU - Curr RID Blocks Residing in Workfile (0163) o All Duplicate Observations are Deleted from the Data Base Files For each of the following files, all duplicate observations are deleted during the first sort of the work files that will populate them. DBPDBP - DB2 Plan Buffer Pool Activity File DBPDBU - DB2 User Buffer Pool Activity File DB2DDP - DB2 Plan DDF Activity File DB2DDU - DB2 User DDF Activity File DB2DPP - DB2 Package/DBRM Activity File DB2DSP - DB2 Plan Activity File DB2DSU - DB2 User Activity File (0160) o Eliminated Unneeded Overhead on Sorts for DB2DPP The 'NODUP EQUALS' appears only on the first sort for the DB2 Package/DBRM Activity (DB2DPP) file. (0161) o Improve Performance of Code that Assigns SYSID There is a performance improvement in the code that assigns the System Identifier (SYSID) values based on Originating System Identification (ORGSYSID) values. (0162) o Activated Buffer Pool Metrics for Q&R Reporting The following Buffer Pool metrics were activated, in all timespans, in support of the enhanced graphical reporting with the CA MICS Query and Reporting (Q&R) DB2 sample reports: File: DB2 Plan Buffer Pool Activity (DBPDBP) DBPDPF - No. Times Dynamic Prefetch Req File: DB2 User Buffer Pool Activity (DBPDBU) DBUDPF - No. Times Dynamic Prefetch Req (0164) o Corrected Data Elements Initialization The following CA MICS common data elements are correctly initialized to a character data type: DB2ACE - Agent Control Element DB2AUTH - Authorization Identifier DB2CORR - Correlation Identifier DB2LUNAM - Logical Unit NAME DB2OPID - Original Operator ID DB2PTASK - Special Transaction Type Identifier DB2UNIQ - DB2 Instance Number UOWID - Unit of Work ID (0165)
PRODUCT CHANGE: DB26799 DATE: July 18, 2011 SUBJECT: Correct Values for Selected Elements and Consolidated Maintenance PREREQUISITES: DB26792 DB26794 DB26795 COREQUISITES: None SUPERSEDES: DB26783 DB26797 DESCRIPTION: This product change includes the following solutions for CA MICS Analyzer Option for DB2: o DPPTELPT Populated for DB2 v8.1 and Above o The DAY065 and INCR065 Steps Complete with RC=0 o Deactivate Certain Retained Elements in Higher Timespans for the DBPDBP File o Correct and Delete Element names in Appendix B of the CA MICS DB2 Analyzer Guide o DSUWLGTM and DSPWLGTM are Populated Correctly o DSPCPODB, DSPXSODB, DSUCPODB, and DSUXSODB Have Correct Values o Minor Documentation Updates and Label Changes Have Been Made Details associated with these solutions are provided below. o DPPTELPT Populated for DB2 v8.1 and Above The Comprehensive Elapsed Time (DPPTELPT) element is still populated for DB2 v8.1 and above. (0167) o The DAY065 and INCR065 Steps Complete with RC=0 The DAY065 and INCR065 complete with condition code 0 even when the following options are active in sharedprefix.MICS.PARMS(MABATCH): DKRICOND=WARN DKROCOND=WARN (0168) o Deactivate Certain Retained Elements in Higher Timespans for the DBPDBP File The following retained elements are shipped inactive in the higher timespans of the DB2 Plan Buffer Pool Activity (DBPDBP) file: DB2ATNM - Active Trace Number Mask DB2AUTH - Authorization Identifier DB2CONN - Connection Identifier DB2CORR - Correlation Identifier DB2DSGN - Data Sharing Group Name DB2DSTSN - Destination Sequence Number DB2ISEQ - Instrumentation Sequence Number DB2LUNAM - Logical Unit NAME DB2MEMN - DB2 Member Name DB2NETID - Network ID DB2OPID - Original Operator ID DB2REQID - DB2 Requestor Location ID DB2STCK - DB2 Store Clock At End Event DB2THDTY - DB2 Thread Type (0169) o Correct and Delete Element names in Appendix B of the CA MICS DB2 Analyzer Guide The index of Appendix B displays the corrections for the following element names in the DB2 Package/DBRM Activity (DB2DPP) file. The correct names appear below in parentheses: DB2WLCTM (DPPWLCTM) DB2WLGTM (DPPWLGTM) DB2WLLTM (DPPWLLTM) DB2WLPTM (DPPWLPTM) DB2WTOTM (DPPWTOTM) For the DB2 Plan Activity (DB2DSP) file, Appendix B displays the correct names as given in parentheses for the following element names: DB2MGPGX (DSPMGPGX) DB2MPFRX (DSPMPFRX) DB2MSPUX (DSPMSPUX) DB2MSRDX (DSPMSRDX) DB2MSWRX (DSPMSWRX) Also, the element name DB2PEDTM no longer appears for the DB2DSP and DB2DSU files in Appendix B. (0173) o DSUWLGTM and DSPWLGTM are Populated Correctly The Accum Wait Time for Log Write IO (DSUWLGTM,DSPWLGTM) elements are populated correctly. (0174) o DSPCPODB, DSPXSODB, DSUCPODB, and DSUXSODB Have Correct Values The CPU Time Only on a DB2 TCB (DSPCPODB, DSUCPODB) elements and the DB2 Only and Non zIIP-Eligible CPU Time (DSPXSODB, DSUXSODB) elements do not include CPU time that has been reported for batch jobs. (0176)
PRODUCT CHANGE: DB26810 DATE: October 11, 2011 SUBJECT: Performance Enhancements and Consolidated Maintenance PREREQUISITES: DB26790 COREQUISITES: None SUPERSEDES: DB26791 DB26792 DB26794 DB26795 DB26796 DB26797 DB26799 DB26801 DB26802 DB26803 DESCRIPTION: This product change includes the following solutions for the CA MICS Analyzer Option for DB2: o DB2 Daily Processing Performance Improvements o Removed Support for DB2 6.1 and DB2 7.1 o Correctly Initialize Common Data Elements o Correctly Populate DB2 Version 9.1 Data Elements o Correctly Populate DB2DSU and DB2DSP Buffer Pool Data Elements o Provide Support for Workfile Storage Metrics o Improve Deletion of Duplicate Observations o Eliminated Unneeded Overhead on DB2DPP Sorts o Activated Buffer Pool Metrics for Q&R Reporting o Compressed SMF Record Support o Corrected Data Elements DSUWLGTM and DSPWLGTM o DPPTELPT Populated for DB2 v8.1 and Above o The DAY065 and INCR065 Steps Complete with RC=0 o Deactivate Some DBPDBP File Retained Elements in Higher Timespans o Metrics no Longer Available Set to a Missing Value. o Correct and Delete Element Names in Appendix B of the CA MICS Analyzer Option for DB2 Guide o Corrected Values for Data Elements DSPCPODB, DSPXSODB, DSUCPODB, and DSUXSODB o Corrected Values for Data Elements fffPCWRP, fffPCWMP, and fffPCWDP in DB2DSU and DB2DSP Files o Add New CPU-time to Service Unit Conversion Factors o Assign Values to DB2PTASK and DB2THDTY in DB2DPP File o Correct Data Element Values in DB2DSD, DBPDSB, DB2DDU, and DB2DDP for DB2 v10.1 o Variable DB2ISEQ Not Found Messages no Longer Appear in the SASLOG o Minor Documentation Updates Details associated with these solutions are provided below. o DB2 Daily Processing Performance Improvements - The CA MICS DB2 format routine (DYDB2FM1), is enhanced to split most of the raw data read up into separate SAS modules based on DB2 version. This eliminates numerous release checking statements, resulting in improved processing performance and ease of maintenance. - The buffer pool and shared buffer pool sections are now processed simultaneously while in memory, resulting in the elimination of several sorts and a merge step. - Taking advantage of a raw data pattern, where well over 90% of the time, a DB2 package record is immediately followed by the corresponding DB2 thread record. The DYDB2FM1 format routine is updated to hold package information in internal arrays, and to transfer information from the thread record to the package data prior to outputting to the DB2 package work file. This improved the match up reliability. Previously, all DB2 package and thread work files were sorted and merged after the initial raw data read-up to perform this information transfer. With this enhancement, only a small number of package and thread records (those that do not follow the typcial raw data pattern) need to go through the additional sort and merge, resulting in significant processing savings. - Conditional initialization of data elements, along with several other code optimization techniques, were implemented to contribute to addtional CPU and elapsed time reductions. associated with subsequent I/O operations. Due to significant code restructuring, both the sharedprefix.MICS.SOURCE(DYDB2FM1), and sharedprefix.MICS.MACAUTOS(DB2DPPIN) modules are redelivered with this product change. If you have made local modifications to these modules, you must determine how to re-implement the updates in the restructured modules. (182) o Removed Support for DB2 6.1 and DB2 7.1 The analyzer no longer accepts or proceses DB2 data generated by releases earlier than DB2 Version 8.1. (182) o Correctly Initialize Common Data Elements The following MICS common data elements are correctly initialized to a character data-type: Data Element Data Element Label -------- ------------------------------------- DB2ACE - Agent Control Element DB2AUTH - Authorization Identifier DB2CORR - Correlation Identifier DB2LUNAM - Logical Unit NAME DB2OPID - Original Operator ID DB2PTASK - Special Transaction Type Identifier DB2UNIQ - DB2 Instance Number UOWID - Unit of Work ID (0165) o Correctly Populate the following DB2 Version 9.1+ Data Elements Data Element Data Element Label -------- ------------------------------------- DSDMXXML - MAX Storage Used for XML Values DSDRFCHD - # FETCHED ROWS DSDRNSTD - # INSERTED ROWS DSDRUDTD - # UPDATED ROWS DSDRDLTD - # DELETED ROWS fffALTJR - Number of Alter Jar fffMERGE - Number of Times Merge Statement Executed fffTRTBL - Number of Times Truncate Table Executed fffCRROL - Number of Create Role fffDRPRO - Number of Drop Role fffCRCTX - Number of Create Trusted Context fffALTTC - Number of Alter Trusted Context fffDRPTX - Number of Drop Trusted Context fffRNIX - Number of Rename Index Where fff is equal to DSU or DSP (181) o Correctly Populated DB2DSU and DB2DSP Buffer Pool Elements Data elements that report the buffer pool totals in the DB2 Plan Activity (DB2DSP) and DB2 User Activity (DB2DSU) files are populated correctly when NOBPELEMENT is specified in sharedprefix.GENLIB(DB2GENIN). All the data elements in the DB2 Buffer Pool Activity (DBPDSB) file are populated correctly. (0172) o Provide Support for Workfile Storage Metrics Starting with DB2 version 9 release 1, new metrics were introduced to the DB2 statistics record section to provide values that correspond to how the workfile (WF) database is used. In support of this implementation, the following data elements are added to the DB2 Database Activity file Data Element Data Element Label -------- ------------------------------------- DSDIMAC - Curr Active DM In-Memory Workfiles DSDIMAH - Hi-Watermark Cnt Max DM In-Mem WFs DSDIMSC - Total Used Space DM In-Mem Workfiles KB DSDIMSH - Hi-Watermark Cnt Max Space DM In-Mem WFs DSDRCCD - Committed Delete Read - Rows Accessed DSDRCCI - Committed Insert Read - Rows Skipped DSDRCCU - Committed Update Read - Rows Accessed DSDSIAC - Count of Curr Active Sort In-Mem WFs DSDSIAH - Hi-Watermark Cnt Max Sort In-Mem WFs DSDSISC - Tot Space Used Curr Active Sort In-Mem DSDSISH - Hi-Watermark Cnt Max Space Sort In-Mem DSDW4K - Curr 4KB Tablespace Storage Used KB DSDW32K - Curr 32KB Tablespace Storage Used KB DSDWCTO - Curr Total Workfile Storage Used KB DSDMXWF - Max Allow Per Agent Storage Use Limit KB DSDWFMU - Max Total Workfile Storage Ever Used KB DSDWFNE - Times Max Allow Storage Limit Exceeded DSDWFP1 - Times 32KB Page TS Used Instead of 4KB DSDWFP2 - Times 4KB Page TS Used Instead of 32KB DSDWFRHG - Max RID Blocks Stored to Workfile DSDWFRCU - Curr RID Blocks Residing in Workfile (0163) o Improved Deletion of Duplicate Observations For each of the following files, all duplicate observations are deleted during the first sort of the work files that will populate them. File File Label ------ ------------------------------------- DBPDBP - DB2 Plan Buffer Pool Activity File DBPDBU - DB2 User Buffer Pool Activity File DB2DDP - DB2 Plan DDF Activity File DB2DDU - DB2 User DDF Activity File DB2DPP - DB2 Package/DBRM Activity File DB2DSP - DB2 Plan Activity File DB2DSU - DB2 User Activity File (0160) o Eliminated Unneeded Overhead on DB2DPP Sorts The 'NODUP EQUALS' appears only on the first sort for the DB2 Package/DBRM Activity (DB2DPP) file. (0161) o Activated Buffer Pool Metrics for Q&R Reporting The following Buffer Pool metrics were activated, in all timespans, in support of the enhanced graphical reporting with the CA MICS Query and Reporting (Q&R) DB2 sample reports: File: DB2 Plan Buffer Pool Activity (DBPDBP) DBPDPF - No. Times Dynamic Prefetch Req File: DB2 User Buffer Pool Activity (DBPDBU) DBUDPF - No. Times Dynamic Prefetch Req (0164) o Compressed SMF Record Support DB2 Release 10.1 provides the ability to create compressed SMF 100 and 101 records, providing a substantial reduction in space used to store the data. This product change supplies a new Input File User Exit, DB2CIFUE, to expand any compressed records encountered prior to the SAS read up routines. (166) o Corrected Data Elements DSUWLGTM and DSPWLGTM The Accum Wait Time for Log Write IO (DSUWLGTM,DSPWLGTM) data elements are populated correctly. (0174) o DPPTELPT Populated for DB2 v8.1 and Above The Comprehensive Elapsed Time (DPPTELPT) element is still populated for DB2 v8.1 and above. (0167) o The DAY065 and INCR065 Steps Complete with RC=0 The DAY065 and INCR065 complete with condition code 0 even when the following options are active in sharedprefix.MICS.PARMS(MABATCH): DKRICOND=WARN DKROCOND=WARN (0168) o Deactivate some DBPDBP File Retained Elements in Higher Timespans The following retained elements are shipped inactive in the higher timespans of the DB2 Plan Buffer Pool Activity (DBPDBP) file: Data Element Data Element Label -------- ------------------------------------- DB2ATNM - Active Trace Number Mask DB2AUTH - Authorization Identifier DB2CONN - Connection Identifier DB2CORR - Correlation Identifier DB2DSGN - Data Sharing Group Name DB2DSTSN - Destination Sequence Number DB2ISEQ - Instrumentation Sequence Number DB2LUNAM - Logical Unit NAME DB2MEMN - DB2 Member Name DB2NETID - Network ID DB2OPID - Original Operator ID DB2REQID - DB2 Requestor Location ID DB2STCK - DB2 Store Clock At End Event DB2THDTY - DB2 Thread Type (0169) o Metrics no Longer Available Set to a Missing Value. Many metrics no longer available in DB2 10.1 are set to a missing value. (183) o Corrected and Deleted Element names in Appendix B of the CA MICS Analyzer Option for DB2 Guide The index of Appendix B displays the corrections for the following data element names in the DB2 Package/DBRM Activity (DB2DPP) file. The correct names appear below in parentheses: DB2WLCTM (DPPWLCTM) DB2WLGTM (DPPWLGTM) DB2WLLTM (DPPWLLTM) DB2WLPTM (DPPWLPTM) DB2WTOTM (DPPWTOTM) For the DB2 Plan Activity (DB2DSP) file, Appendix B displays the correct names as given in parentheses for the following element names: DB2MGPGX (DSPMGPGX) DB2MPFRX (DSPMPFRX) DB2MSPUX (DSPMSPUX) DB2MSRDX (DSPMSRDX) DB2MSWRX (DSPMSWRX) Also, the element name DB2PEDTM no longer appears for the DB2DSP and DB2DSU files in Appendix B. (0173) o Corrected Values for Data Elements DSPCPODB, DSPXSODB, DSUCPODB, and DSUXSODB The CPU Time Only on a DB2 TCB (DSPCPODB, DSUCPODB) elements and the DB2 Only and Non zIIP-Eligible CPU Time (DSPXSODB, DSUXSODB) elements delivered with DB26790 could have included CPU time from batch jobs using DB2 connection types 'DB2 Call Attach' or 'DB2 Utilities'. This change removes those types from the assignment of these elements. CA MICS does not deliver Accounting Computation Codes for these elements for charging, however if you created your own Computation Codes for these elements, and you bill CPU time from the BATJOB file, you could have been double billing. If you keep Detail level files to DB2DSU or DSUDSP, an optional retrofit job is provided to adjust these elements to there proper value.. It is not possible to adjust the Days and higher timespans because the Connecting System Type Code (fffCATYP) data element is not available. (0176) o Corrected Values for Data Elements fffPCWRP, fffPCWMP, and fffPCWDP in the DB2DSU and DB2DSP Files The following data elements could have inflated values at DAYS and higher timespans in the DB2DSU and DB2DSP files: Data Element Data Element Label -------- ------------------------------------- DSUPCWRP - Replaced Per Parsed Dyna Stmnts DSUPCWMP - Matched Per Parsed Dyna Stmnts DSUPCWDP - Duplicate Per Parsed Dyna Stmnts DSPPCWRP - Replaced Per Parsed Dyna Stmnts DSPPCWMP - Matched Per Parsed Dyna Stmnts DSPPCWDP - Duplicate Per Parsed Dyna Stmnts The derivation for these data elements is now defined in the DB2GENIN, so they are calculated correctly during summarization in all timespans. The SAS length of these elements is also reduced from 6 bytes in the Detail timespan and 8 bytes in Days and higher timespans, to 3 bytes in all timespans. (180) o Add New CPU to Service Unit Conversion Factors New SU:CPU Conversion Factor (DSUSUFC, DSPSUFC) data elements have been added to the DB2 User tivity Activity (DB2DSU) and DB2 Plan Activity (DB2DSP) files, respectively. These new elements are delivered turned off. If you have a need to convert CPU-time to Service Units, activate them in the sp.GENLIB(DB2GENIN). CPU seconds can be converted to service units by multiplying them by the values in DSUSUFC or DSPSUFC. The existing conversion factor data elements DSUSUCV and DSPSUCV, are assigned a new label: 'Raw SU:CPU-second 'Raw SU:CPU-second Conversion Factor'. (0177) o Assign Values to DB2PTASK and DB2THDTY in DB2DPP In all or at least most of the cases where the Special Transaction Type Identifier (DB2PTASK) and the DB2 Thread Type (DB2THDTY) elements had missing values in the DB2 Package/DBRM Activity (DB2DPP) file, correct values are now being assigned. (0178) o Correct Data Element Values in DB2DSD, DBPDSB, DB2DDU, and DB2DDP for DB2 v10.1 Elements in the DB2 Buffer Pool Activity (DBPDSB) and DB2 Data Base Activity (DB2DSD) files that are populated from the Buffer Manager Statistics Block in the SMF type 100 record have correct values. If the records have been coming from DB2 V10.1, the values of the data elements in question are no longer inflated by a factor of 256. DB2RLOCN is now populated correctly in the DB2 User DDF Activity (DB2DDU) and DB2 Plan DDF Activity (DB2DDP) files. (0179) o Variable DB2ISEQ Not Found Messages no Longer Appear in the SASLOG The SASLOG message Variable DB2ISEQ not found no longer appears when ESSENTIAL ONLY is specified in sharedprefix.MICS.PARMS(CPLXDEF) or on the the COMPOPT or FOPT statements for all or some of the files in sharedprefix.MICS.GENLIB(DB2GENIN). Moreover, all of the duplicate observations are removed from the following files: DB2DSU - DB2 User Activity File DB2DSP - DB2 Plan Activity File DB2DDU - DB2 User DDF Activity File DB2DDP - DB2 Plan DDF Activity File DBPDBU - DB2 User Buffer Pool Activity File DBPDBP - DB2 Plan Buffer Pool Activity File (0184)
PRODUCT CHANGE: DB26812 DATE: March 14, 2012 SUBJECT: Enhance Duplicate Data Deletion PREREQUISITES: DB26810 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for the CA MICS Analyzer Option for DB2: After application of DB26810, if the raw data input to an incremental or DAILY update contains duplicate SMF 101 records, not all of the duplicate records may be deleted. This problem can impact the following database files: DSBDBP - DB2 Plan Buffer Pool Activity DSBDBU - DB2 User Buffer Pool Activity DB2DDP - DB2 Plan DDF Activity File DB2DDU - DB2 User DDF Activity File DB2DPP - DB2 Package/DBRM Activity File DB2DSP - DB2 Plan Activity File DB2DSU - DB2 User Activity File (0187)
PRODUCT CHANGE: DB26815 DATE: January 11, 2012 SUBJECT: Resolve Orphaned Package Continuation Records PREREQUISITES: DB26810 DB26812 BAS7705 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for the CA MICS Analyzer Option for DB2: There were circumstances where overflow package data might be orphaned, and may or may not get the DB2PTASK and DB2THDTY assigned properly. This has been corrected. (0188)
PRODUCT CHANGE: IDM6570 DATE: August 15, 2011 SUBJECT: CA IDMS Version 18.0 Support, Performance Improvements and Consolidated Maintenance PREREQUISITES: BAS7680 IDM6540 COREQUISITES: None SUPERSEDES: IDM6551 IDM6552 IDM6553 IDM6560 IDM6565 DESCRIPTION: This product change includes the following solutions for the CA MICS Analyzer Option for IDMS: o Provided Support for CA IDMS Version r18 o Added Common TRANSTS and TRANETS Data Elements o Improved Sort Performance o Replaced SAS Proc Calendar Step Code with Base SAS Code o Obsoleted MICSVER Data Element o Corrected Comment in Incremental Update JCL o Corrected Errors in Dictionary Definitions o Added Instructions for Running MBO Reports o Minor Documentation Updates Details associated with these solutions are provided below. o Provided Support for CA IDMS Version r18 - This product change updated version release check code in support of the CA IDMS Version r18 SMF data. - CA IDMS Version r18 added support for a "Job Name for CV Region" (IDMJBNAM) metric that is added, as a common data element, to the following CA MICS Analyzer for IDMS Option files: Files: IDMS System Work File (IDMSSW) IDMS System Activity File (IDMSSY) IDMS User Activity File (IDMSUA) IDMS Application Unit Activity File (IDMSAU) IDMS User Application Counts File (IDMSAC) IDMS System Incident File (IDMSIN) IDMS System Calendar File (IDMSCL) (0057) o Added Common TRANSTS and TRANETS Data Elements Transaction Start Time Stamp (TRANSTS) and Transaction End Time Stamp (TRANETS) common data elements are added to provide greater date and time stamp precision. The following CA MICS Analyzer for IDMS Option files are updated to include these additional data elements: File: IDMS User Activity (IDMSUA) TRANSTS - Transaction Start Time Stamp TRANETS - Transaction End Time Stamp File: IDMS Application Unit Activity (IDMSAU) TRANSTS - Transaction Start Time Stamp TRANETS - Transaction End Time Stamp File: IDMS User Application Counts (IDMSAC) TRANSTS - Transaction Start Time Stamp TRANETS - Transaction End Time Stamp (0056) o Improved Sort Performance The 'NODUP EQUALS' parameter values are no longer part of sort calls where they are not needed. The 'NODUP EQUALS' is still called on the first sort of the input data so that unwanted duplicates are removed. Removing 'NODUP EQUALS' from subsequent sorts improves performance of the DAY045 step of the DAILY job and of the INCRIDM job. (0054) o Replaced SAS Proc Calendar Step Code with Base SAS Code The Daily IDM Management Objective report source code has been updated to replace the SAS procedure "Proc Calendar" with CA MICS Base architectured SAS code alternative. (0055) o Obsoleted MICSVER Data Element The CA MICS Version Number (MICSVER) data element is obsoleted because it has no further use in the CA MICS product line. (0048) o Corrected Comment in Incremental Update JCL The comment in prefix.MICS.CNTL(INCRIDM) is corrected to identify the job as the incremental update rather than a daily processing step. (0051) o Corrected Errors in Dictionary Definitions Outdated references to Cullinet have been removed. Data element derivations have been corrected to point to the SMF source fields. Superfluous comments have been removed from usage notes. Type designations have been changed to conform to accepted standards. (0052) o Added Instructions for Running MBO Reports Instructions for running MBO reports have been added to the CA MICS Analyzer Option for CA IDMS Guide. (0053)
PRODUCT CHANGE: IDM6571 DATE: April 15, 2012 SUBJECT: Correct Significance Issue with Time Stamps PREREQUISITES: IDM6570 BAS7705 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change provides the following solutions for the CA MICS Analyzer Option for CA IDMS: Length of intermediate data elements Start Time Stamp (work) (SSWSTART) and End Time Stamp (work) (SSWEND) is increased to 8 so that the Transaction Start Timestamp (TRANSTS) and Transaction End Timestamp (TRANETS) are accurate to the nearest microsecond. (0059)
PRODUCT CHANGE: IMS6614 DATE: August 10, 2011 SUBJECT: Corrected Values in IDBGU, IDBGN, IDBISRT and IDBDLET PREREQUISITES: IMS6610 COREQUISITES: None SUPERSEDES: IMS6598 IMS6612 DESCRIPTION: This product change includes the following solutions for the CA MICS Analyzer Option for IMS: o Corrected Values in IDBGU, IDBGN, IDBISRT and IDBDLET o Unknown Version of Mainview/IMS Data Detected o Corrected Loop in IMSLDR20 at or Near 76F4 After IMS6610 is Applied o Corrected S0C4 ABEND in IMSLOGV6 at or Near 73F6 After IMS6610 is Applied o Corrected S0C7 ABEND in IMSLDR20 at 1674 After IMS6610 is Applied o Corrected S002-18 ABEND in IMSLDR20 at 83E0 After IMS6610 is Applied o Corrected U300-10 ABEND in IMSLDR20 at 8794 After IMS6610 is Applied o Corrected Input Suspend File Counts After IMS6610 is Applied Details associated with these solutions are provided below. o Corrected Values in IDBGU, IDBGN, IDBISRT and IDBDLET The following data elements contain correct values when processing Mainview for IMS Release 4.2 and above: IDBGU - Data Base Get Uniques IDBGN - Data Base Get Nexts IDBISRT - Data Base Inserts IDBDLET - Data Base Deletes (0110) o Unknown Version of Mainview/IMS Data Detected Support has been added to recognize Mainview/IMS V4.5 and V4.6 thereby eliminating warning message: "Unknown version of Mainview/IMS data has been detected" (0111) o Corrected Loop in IMSLDR20 at or Near 76F4 After IMS6610 is Applied The incorrect identification of a Fastpath utility region as a Fastpath transaction region caused looping during type x'07' record processing. This has been corrected. (0112) o Corrected S0C4 ABEND in IMSLOGV6 at or Near 73F6 After IMS6610 is Applied An invalid table pointer is being passed to the message writer routine when an unknown version of Mainview/IMS is detected. (0113) o Corrected S0C7 ABEND in IMSLDR20 at 1674 After IMS6610 is Applied During an IMS region restart/recovery processing certain packed fields in the transaction statistics have not been properly initialized casing a S0C7 abend. This is now corrected by forcing a valid sign on the fields. (0114) o Corrected S002-18 ABEND in IMSLDR20 at 83E0 After IMS6610 is Applied Some MICS IMS Analyzer units still contain JCL for the suspend file specifying an LRECL of 512 bytes. Suspend file records have been enlarged with IMS6610 which will cause an S002-18 abend during processing. This has been corrected in the IMSLDR20 module. (0115) o Corrected U300-10 ABEND in IMSLDR20 at 8794 After IMS6610 is Applied IMS log record type 67D0 can output a pseudo-spanned record which can cause a U0300-10 abend in IMSLDR20. These are not true spanned records and are now discarded since they are not processed by the IMS Analyzer. (0116) o Corrected Input Suspend File Counts After IMS6610 is Applied Support has been added to migrate suspend file records to the IMS6610 level from the IMS6590 level. Note: This problem does not occur when only processing Mainview for IMS log data. (0117)
PRODUCT CHANGE: IMS6630 DATE: December 15, 2011 SUBJECT: Support for Processing IMS Version 12 Log Data and Consolidated Maintenance PREREQUISITES: BAS7705 IMS6614 COREQUISITES: (LDE6630) SUPERSEDES: IMS6577 IMS6612 IMS6615 DESCRIPTION: This product change includes the following solutions for the CA MICS Analyzer Option for IMS: o Support for Processing IMS Version 12 Log Data o CP and zAAP CPU Time Elements Added with IMS Version 12 o WFI FastFlush Expedited Transaction Flush o USECPUOLD Parameter to Retrograde Transaction CPU Time o User ID Field Contains Lower Case or Mixed Case Details associated with these solutions are provided below. o Support for Processing IMS Version 12 Log Data Support has been added for processing IMS Version 12 log data. (0122) o CP and zAAP CPU Time Elements Added with IMS Version 12 Four new data elements, ISUTMCP, ISUMXCP, ISUTMZAP and ISUMXZAP, have been added to contain the amount of CPU time consumed by transactions. The new data elements enumerate the CPU time accumulated on the CP and zAAP engines. This data was introduced with IMS Version 12. Refer to Appendix A for a list of new data elements. (0121) o WFI FastFlush Expedited Transaction Flush A new IMSOPS parameter, FASTWFI/NOFASTWFI, has been added to facilitate immediate flushing of WFI transactions. This feature is added for the benefit of users that take advantage of large numbers of never-ending WFI transactions which can cause serious virtual storage constraints. (0120) o USECPUOLD Parameter to Retrograde Transaction CPU Time A new IMSOPS parameter, USECPUOLD, has been added to allow users to force the use of the old transaction CPU time value. This value was obtained from the DLRTIME field of the IMS type x07 record. Beginning in IMS Version 10 a new CPU time field was introduced, DLREXTIM. The CPU time collected in this new field is generally somewhat greater than that of the old field. According to IBM documentation this is actually due to a better and more accurate CPU time collection within IMS. If users are not satisfied with the increased CPU time, specification of the USECPUOLD parameter will cause the old CPU time value to be used. (0119) o User ID Field Contains Lower Case or Mixed Case The RACFUSID field in full function transactions and the USER field in fastpath transactions may contain lower case values for OTMA originated transactions. This may cause problems with user accounting routines. This has been corrected to translate the RACFUSID and USER fields to upper case characters from lower case characters by default. A new IMSOPS parameter, FOLDUID/NOFOLDUID has been added to control whether or not the RACFUSID field is converted to upper case. (0118)
PRODUCT CHANGE: LDE6630 DATE: December 15, 2011 SUBJECT: Support for Processing IMS Version 12 Log Data PREREQUISITES: BAS7705 LDE6610 COREQUISITES: (IMS6630) SUPERSEDES: None DESCRIPTION: This product change includes the following solutions for the CA MICS IMS Log Extractor: o Support for Processing IMS Version 12 Log Data o WFI FastFlush Expedited Transaction Flush o User ID Field Contains Lower Case or Mixed Case Details associated with these solutions are provided below. o Support for Processing IMS Version 12 Log Data Support has been added for processing IMS Version 12 log data. (0018) o WFI FastFlush Expedited Transaction Flush A new LDE parameter, FASTWFI/NOFASTWFI, has been added to facilitate immediate flushing of WFI transactions. This feature is added for the benefit of users that take advantage of large numbers of never-ending WFI transactions which can cause serious virtual storage constraints. (0017) o User ID Field Contains Lower Case or Mixed Case The RACFUSID field in full function transactions and the USER field in fastpath transactions may contain lower case values for OTMA originated transactions. This may cause problems with user accounting routines. This has been corrected to translate the RACFUSID and USER fields to upper case characters from lower case characters by default. A new LDE parameter, FOLDUID/NOFOLDUID has been added to control whether or not the RACFUSID field is converted to upper case. (0016)
PRODUCT CHANGE: MQS6630 DATE: December 17, 2011 SUBJECT: WebSphere MQ 7.1 Support and Enhancements PREREQUISITES: MQS6620 BAS7705 COREQUISITES: None SUPERSEDES: MQS6621 MQS6625 MQS6626 DESCRIPTION: This product change includes the following solutions for the CA MICS Analyzer Option for MQSeries: o Added New Data Elements for WebSphere MQ for z/OS 7.x o Updated WebSphere MQ Release Validation for 7.1 o Added TAACHNLC to Sort Sequence Key o Added TAAFLAG to MQATAA File o Added MQSREL to all Files o Observations Missing from MQSCMS File o Eliminated Creation of Erroneous SAS Files o Corrected Specification of Inquiry Exec-time Parameters o Minor Documentation Updates Details associated with these solutions are provided below. o Added New Data Elements for WebSphere MQ 7.x The support for new metrics added with WebSphere MQ for z/OS release 7.0: - Data elements added to the Message Manager Statistics (MQSMMS) file that provide statistics related to the publish and subscribe features. - Data elements added to the Log Manager Statistics (MQSLMS) file that provide statistics about compression and decompression of messages data. - Data elements are added to the Task Accounting Activity (MQATAA) file that provide statistics about the publish, subscribe, and topic features, as well as the MQSUB, MQSUBRQ, MQCNTL, and MQSTAT commands. - Data elements are added to the Queue Accounting Activity (MQAQAA) file that provide statistics about queue suspend time and counts of MQOPEN and MQCLOSE commands as well as MQCB command CPU and elapse times, publications count, and Topic CPU times for MQCLOSE, MQOPEN, MQPUT, and MQPUT1 commands. ******************** IMPORTANT NOTE ******************** *** *** *** Data elements Total Queue CPU Time (TAAQCPTM and *** *** QAAQCPTM) represent the sum of several queue *** *** related CPU times. A new data element introduced*** *** with WebSphere MQ Version 7.0.1, Total CPU Time *** *** MQCB (QAACBCTM), is added to the sum. If you *** *** charge for the fffQCPTM data elements using the *** *** CA MICS Accounting and Chargeback Computation *** *** Codes 2730 (MQATAA file) or 2738 (MQAQAA file), *** *** you may see slight increase in charges due to *** *** the addition of this new type of CPU time to *** *** the Total Queue CPU Time data elements. *** *** *** ******************** IMPORTANT NOTE ******************** The new and updated data elements are listed in Appendix A. For more information about the data elements, see the data dictionary entries in Appendix B of the CA MICS Analyzer Option for MQSeries Guide. (0092) o Updated WebSphere MQ Release Validation for 7.1 The release validation code is updated to recognize data generated by WebSphere MQ for z/OS 7.1. (0090) o Added TAACHNLC to Sort Sequence Key The granularity of the Channel Path Activity (MQA_CH) file is improved by adding the Channel Connection Name (TAACHNLC) data element to the file sequence keys. (0091) o Added TAAFLAG to MQATAA File A new data element, WTAS Flag (TAAFLAG), is added to Task Accounting (MQATAA) file. The CA MICS Analyzer Option for MQSeries uses this flag to determine the status of the task end record. (0093) o Added MQSREL to all Files A new data element, WebSphere MQ Version (MQSREL), is added to all the component files. (0094) o Observations Missing from MQSCMS File The error causing the MQS Coupling Facility (MQSCMS) file to miss observations for one or more coupling facility structures is corrected. (0095) o Eliminated Creation of Erroneous SAS Files The SAS data step where DETAIL.MQA_CH file is created also created erroneous SAS WORK.RETAIN, WORK.ROUTINE and DYMQSFMT files. The code is corrected to eliminate the problem. (0098) o Corrected Specification of Inquiry Exec-time Parameters After application of product change BAS7630, first delivered with r12.5, the administrator may be unable to define execution-time parameters for an inquiry specified to be run in a Production Reporting jobstream. A Dialog Assist error panel is displayed. This error is corrected. (0089)
PRODUCT CHANGE: PWR6390 DATE: October 1, 2011 SUBJECT: VSE/POWER Version 9.1 Support and MICF Abstract and Sample Members for MBO Reports PREREQUISITES: PWR6380 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change provides the following solutions for the CA MICS Analyzer Option for VSE/POWER: o Provided VSE/POWER Version 9.1 Support o Add MICF Abstracts and Samples for MBO Reports Details associated with these solutions are provided below: o Provided VSE/POWER Version 9.1 Support The code that checks the release level information has been updated to support processing of VSE/POWER 9.1 account data. (0018) o Add MICF Abstracts and Samples for MBO Reports Updates have been made to add missing Management Objective report abstracts and samples to the MICF catalog display. This provides the means to view documentation and sample reports before running the inquiries. (0019)
PRODUCT CHANGE: RMF6925 DATE: September 15, 2011 SUBJECT: Old Technology Removal, Product Enhancements, and Consolidated Maintenance PREREQUISITES: RMF6920 COREQUISITES: None SUPERSEDES: RMF6921 RMF6922 DESCRIPTION: This product change includes the following solutions for the CA MICS Hardware and SCP Analyzer: o Old Technology Removal o SCPPAG File Data Elements' Definitions Changed o Enhanced RMF Summary Report o Added Abstracts and Samples for MICF Inquiries and MBO Reports o Corrected Specification of Inquiry Exec-time Parameters o Improved MICSLOG Messages o CPUBPS, CPUSUBPS, and CPUZPBPS Populated Correctly Details associated with these solutions are provided below. o Old Technology Removal As previously announced in RMF6710 (PSP0410) and RMF6850 (PSP0804) product changes, information related to obsolete technology and unsupported operating systems' releases is removed from the CA MICS Hardware and SCP Analyzer. This project is comprised of: - Dropped Support For Pre-z/OS Version 1 Release 5 Data Support for records generated by systems executing at z/OS Version 1 Release 4 or below is dropped from the CA MICS Hardware and SCP Analyzer. The type of the RMF00106 message in the DAY020 daily update MICSLOG is changed from warning (suffix W) to informational (suffix I). This message now means that records from an obsolete RMF version have been found and that they will not be processed. Additionally, the processing and exploitation of the following files is removed from the product: HARCUA - Control Unit Activity File SCPDMA - Domain Activity File SCPDMT - Domain Control File SCPPGA - Performance Group Activity File SCPPPA - Performance Period Activity File SCP_RG - Report Perf Group Activity File Other data elements related to obsolete technologies are also removed from the active files in the CA MICS database. All these data elements are listed in Appendix A. - Individual Processor Measurements Dropped From HARCPU File The set of individual processor measurements (up to 16) controlled by the CPUIDx/NOCPUID keyword of the OPTION statement in sharedprefix.MICS.GENLIB(RMFGENIN) is removed from the CPU Activity (HARCPU) file. - Sharedprefix.MICS.GENLIB(RMFGENIN) OPTION Statement Removed The OPTION statement is removed from sharedprefix.MICS.GENLIB(RMFGENIN). As a result, all data elements and files previously controlled by the PRSM/NOPRSM, CF/NOCF, and GOAL/NOGOAL keywords are only tailored by their respective FILE or NAME/NAMX statements. For more information about file tailoring, see section 7.2 of the CA MICS Hardware and SCP Analyzer Guide. - Existing MICF Inquiries Updated The following inquiries from the CA MICS Information Center Facility (MICF) shared inquiry catalog are updated to remove obsolete technology references: RMFCDA - Daily Logical Control Unit Activity RMFED1 - CPU and ASID Activity (.CSV) RMFED3 - Paging Activity (.CSV) RMFED4 - Top N Active DASD Activity (.CSV) RMFED5 - Top-4 CPU Busy Comparison (.CSV) RMFPDA - Daily Logical Control Unit Activity RMFTDI - Performance Trending Data Extract - Obsolete MICF Inquiries Deleted The following obsolete inquiries are deleted from the CA MICS Information Center Facility (MICF) shared inquiry catalog: RMFED2 - MVS Performance Group Activity (.CSV) RMFED6 - MVS Top-9 Performance Groups (.CSV) RMFLDE - Daily Channel Utilization Analysis RMFLDI - Daily System, Demand and Swap Paging RMFLPI - Post Processor Workload Activity Report RMFLWA - Weekly Track of JES Real Memory Use (0318) o SCPPAG File Data Elements' Definitions Changed Several data elements in the Paging Activity (SCPPAG) file are changed from non-essential (NAMX) to essential (NAME) to make them universally available for the "RMFFRM - zOS Central Storage Daily Frame Use" query. This query is in the CA MICS Query Library included with release 12.6 of CA MICS Q&R. The updated data elements are listed in Appendix A. (0319) o Enhanced RMF Summary Report New columns providing the maximum/average number of APPC/MVS transaction scheduler (ASCH) as well as OMVS (USS) address spaces that were active during each measurement interval are added to the RMF Summary Report (RMFLPH) MICF inquiry. The obsolete "SERVICE RATE" and "TRANS RATE" columns are removed. (0317) o Added Abstracts and Samples for MICF Inquiries and MBO Reports Updates have been made to add Management by Objective (MBO) reports' abstracts and samples to the MICF catalog display. Abstracts for MICF inquiries are also added. This provides the means to view documentation and sample reports before running the inquiries. (0316) o Corrected Specification of Inquiry Exec-time Parameters After application of product change BAS7630, first delivered with r12.5, the administrator may be unable to specify execution-time parameters for an inquiry selected to be run in a Production Reporting jobstream. A Dialog Assist error panel is displayed. This error is corrected. (0313) o Improved MICSLOG Messages The DAY020 job step MICSLOG no longer uses message RMF00100I because it duplicates the information in the cross-data integration component standard message BAS00326I. Also, message RMF00107I is replaced with standard message BAS00357I. (0314) o CPUBPS, CPUSUBPS, and CPUZPBPS Populated Correctly In the CPU Activity (HARCPU) file, the data elements Partition Processor Weight (CPUBPS), Partition zIIP Processors Weight (CPUSUBPS), and Partition zAAP Processors Weight (CPUZPBPS) are populated correctly. Their values are all based on the values of the Partition Processor Weight (IPUBPS) element of the Individual Processor Activity (HARIPU) file. CPUBPS carries the maximum value of IPUBPS for CP processors. CPUSUBPS carries the maximum value of IPUBPS for zIIP processors. CPUZPBPS carries the maximum value of IPUBPS for zAAP processors. (0315)
PRODUCT CHANGE: RMF6930 DATE: January 04, 2012 SUBJECT: IBM CPU Measurement Facility Support of 113 Records PREREQUISITES: RMF6925 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for the CA MICS Hardware and SCP Analyzer: o SMF Type 113 IBM CPU Measurement Facility Support Support is provided for the SMF type 113 subtype 2 Hardware capacity, reporting, and statistics interval record generated by the IBM Hardware Instrumentation Services (HIS)CPU Measurement Facility (CPU MF). This support adds four new database files to the RMF Component: o CPU Measurement Facility Suspend (HARCMX) File o CPU Measurement Facility Engine (HARCME) File o CPU Measurement Facility EngType (HARCMT) File o CPU Measurement Facility LPAR (HARCML) File The HARCMX file is for internal use and provides continuity between CA MICS daily and incremental update jobs, supporting the requirement to perform delta processing of the cumulative SMF type 113 counter fields in contiguous interval records. The HARCME, HARCMT, and HARCML files provide individual logical processor level (HARCME), processor type level (CP, zIIP, zAAP), and LPAR level information about Central Processor Complex (CPC) hardware cache and memory use, cryptographic co-processor activity, Translation Look-aside Buffer (TLB) activity, CPC machine cycles used to process instructions, and penalty cycles related to cache and TLB misses. Each file contains over 200 data elements, including numerous derived data elements that can be used to determine the efficiency of LPAR exploitation of the CPC cache hierarchy and for capacity analysis studies. These new files and their summarization keys and data elements are described in Appendix A. (0326)
PRODUCT CHANGE: RMF6940 DATE: December 15, 2011 SUBJECT: z/OS Version 1 Release 13 Exploitation, and Product Enhancements PREREQUISITES: RMF6930 COREQUISITES: None SUPERSEDES: RMF6924 DESCRIPTION: This product change includes the following solutions for the CA MICS Hardware and SCP Analyzer: o z/OS Version 1 Release 13 Exploitation o CPU Reporting Enhancements for z/OS Systems Running as z/VM Guests o New Hiperdispatch Indicator in HARCPU, HARIPU, HARLPC, and HARVPA Files o Swap Data Sets References Removed o Documentation Updates Details associated with these solutions are provided below. o z/OS Version 1 Release 13 Exploitation This product change includes the following enhancements for z/OS Version 1 Release 13: - z/OS Version 1 Release 13 Validation The release validation module is updated to recognize RMF data generated by z/OS Version 1 Release 13 systems. - WLM Promotion Monitoring Enhancement The following new data element is added to the Service Class Resource Consumption (WLMSEC) and Report Class Resource Consumption (WLM_EC) files: Element Label -------- ---------------------------------- SECSPDTM Total CPU Time Promoted Supervisor Additionally the Workload Activity Goal Mode (RMFLPM) report is enhanced to show the CPU time consumed by work units that have been promoted by the z/OS supervisor to a higher dispatching priority than the one assigned by WLM. - WLM Response Time Distribution Analysis Enhancements Detailed response time data is now available in the Service Class Response Time (WLMSEM) and Report Class Response Time (WLM_EM) files for service/report class periods with an execution velocity goal. This information is provided in the response time distributions of the Workload Activity Goal Mode (RMFLPM) report, for each system in a Sysplex, when the new "Response Times" option (defaulting to YES) is specified in the RMFLPM inquiry's Extended Option panel. - Paging Activity Analysis Enhancements New data elements are added to the Paging Activity (SCPPAG) file, providing information about the size of the large frame area (LFAREA), unused 1 megabyte fixed frames, and logical swaps. Additionally, descriptions of several data elements in the SCPPAG file are updated for clarification. Finally, the Paging Activity (RMFLPG) report is updated to provide a more current picture of the storage distribution. Note that the old technology expanded storage information is removed from the report. - New CICS TOR Management Indicator in SCPARD File A new CICS TOR Response Time Management (ARDCTOR) data element is added to the Address Space Activity (SCPARD) file. The data element indicates that the address space is a CICS TOR that matches a classification rule in the WLM policy which allows managing the region based on its goals and verifies that transactions are reported for management of the CICS AORs. The new and updated data elements are listed in Appendix A. For more information about data elements, see the data dictionary entries in Appendix B of the CA MICS Hardware and SCP Analyzer Guide. For examples of the updated reports, see section 3.1.1 of the CA MICS Hardware and SCP Analyzer Guide. (0320,0322) o CPU Reporting Enhancements for z/OS Systems Running as z/VM Guests With IBM APAR OA35675, the SMF type 70 subtype 1 CPU Activity record is enhanced for z/OS systems running as z/VM guests. When the new RMF Monitor I VMGUEST option is active, dispatch times for the guest systems are provided, as well as simplified partition and logical processor data sections. In support of this APAR, the following enhancements to the CPU Activity (HARCPU), Individual Processor Activity (HARIPU), PR/SM LPAR Config/Activity (HARLPC), and PR/SM Logical Proc Activity (HARVPA) files are provided: - A new data element, Intvls with z/VM Guest Data Available (fffDIAGV), where fff stands for CPU, IPU, LPC, or VPA, is added to indicate that the system is a z/OS LPAR running as a z/VM guest and that simplified PR/SM information is available. - The Logical Partition Type (PRSMLPTP) data element can now take on the value "VMSystem" for the PHYSICAL partition, indicating that this partition's data describes the activity of the z/VM partition itself. Additionally, logical partition and logical processor information about the z/OS guest and z/VM partitions is available in the CPU Activity (RMFLPA) report. (0323) o New Hiperdispatch Indicator in HARCPU, HARIPU, HARLPC, and HARVPA Files A new Hiperdispatch Support Indicator (PRSMHIPS) data element is added to the CPU Activity (HARCPU), Individual Processor Activity (HARIPU), PR/SM LPAR Config/Activity (HARLPC), and PR/SM Logical Proc Activity (HARVPA) files. This indicator allows better readability of the CPU Activity (RMFLPA) report for systems that do not support Hiperdispatch mode. (0324) o Swap Data Sets References Removed All references to swap data sets, unsupported with z/OS, are removed from the product. Note that the label of the Page/Swap Data Set Activity (SCPPSD) file is changed to Page Data Set Activity File. (0325) o Documentation Updates References to old technologies are removed from data dictionary members.
PRODUCT CHANGE: RMF6945 DATE: February 6, 2012 SUBJECT: CA MICS Hardware and SCP Analyzer Maintenance Level Set for r12.7 PREREQUISITES: BAS7705 RMF6940 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for the CA MICS Hardware and SCP Analyzer: A level-setting product change to close off maintenance for the end of the CA MICS r12.7 development cycle. (0328)
PRODUCT CHANGE: SMF6922 DATE: April 6, 2011 SUBJECT: Specification of Inquiry Execution-time Parameters and Cumulative Maintenance PREREQUISITES: SMF6920 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solutions for the CA MICS Batch and Operations Analyzer: o Corrected Specification of Inquiry Exec-time Parameters o Activated Saving of Inquiry Execution-time Parameters o Improved BAT_SA Delta Processing Details associated with these solutions are provided below: o Corrected Specification of Inquiry Exec-time Parameters After application of product change BAS7630, first delivered with r12.5, the administrator may be unable to define execution-time parameters for an inquiry specified to be run in a Production Reporting jobstream. A Dialog Assist error panel is displayed. This error is corrected. (0217) o Activated Saving of Inquiry Execution-time Parameters Execution-time parameters specified by a user are now saved for the following 2 inquiries: SMFLS1 - Address Space zAAP CPU Activity SMFLS2 - Address Space zIIP CPU Activity (0218) o Improved BAT_SA Delta Processing With a further refinement after product change SMF6910, the System Address Space Activity (BAT_SA) file will have fewer overstated values. Note the following concerns: Since many system address spaces have the same JOB name and address space identification (ASID) across an IPL boundary, it is occasionally impossible to determine for certain that a new JOB has begun. This interferes with delta processing for file BAT_SA. Large values for some data elements like PGMACTTM are correct when a system address space is encountered in the input SMF data for the first time and delta processing is not invoked. (0219)
PRODUCT CHANGE: SMF6926 DATE: December 16, 2011 REVISED: April 30, 2012 SUBJECT: BATSPL File Updates and MICF Abstracts/Samples Additions PREREQUISITES: SMF6920 COREQUISITES: None SUPERSEDES: SMF6925 DESCRIPTION: This product change includes the following solutions for the CA MICS Batch and Operations Analyzer: o Batch User Spool Activity (BATSPL) file is Updated o Add MICF Abstracts and Samples for CSVs and MBO Reports Details associated with these solutions are provided below: o Batch User Spool Activity (BATSPL) file is Updated - Subsystem Identifier (SUBSYSID) and Device Name (DEVNAME) data elements are now sequence fields. (220) - SUBSYSID is updated to contain 'VPS' when a SMF type 6 record is generated by VTAM Printer Support (VPS). A SMF type 6 record is identified as VPS when data element UCS Image ID (SPLUCSID) contains the value of 'VPS'. (221) o Add MICF Abstracts and Samples for CSVs and MBO Reports Updates have been made to add Management Objective report abstracts and samples to the MICF catalog display. Abstracts for CSV extracts are also added. This provides the means to view documentation and sample reports before running the inquiries. (222)
PRODUCT CHANGE: SMF6930 DATE: June 10, 2011 SUBJECT: JOBGROUP Target Turnaround Time Allows Seconds Expression PREREQUISITES: SMF6920 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solutions for the CA MICS Batch and Operations Analyzer: Seconds now can be expressed in the target turnaround time definition in the GROUP statement in prefix.MICS.PARMS(JOBGROUP). The GROUP statement is updated using one of the following formats: GROUP nnn mmmmmm sf 'descriptive text' or GROUP nnn mmmmmm:ss sf 'descriptive text' The JOBGROUP routines will behave exactly as before if using the same prefix.MICS.PARMS(JOBGROUP) GROUP parameters to define target turnaround time after SMF6930 is applied. Refer to section 7.3.2.3 GROUP Statements in the CA MICS Batch and Operations Analyzer Guide for more information. (0223)
PRODUCT CHANGE: SMF6940 DATE: October 21, 2011 SUBJECT: z/OS 1.13 Enhancements and Consolidated Maintenance PREREQUISITES: BAS7680 SMF6920 COREQUISITES: None SUPERSEDES: SMF6935 DESCRIPTION: This product change includes the following solutions for the CA MICS Batch and Operations Analyzer: o z/OS Version 1 Release 13 Enhancements o Change Initiator CPU Time Elements to Essential o JOBCOPY and JOBSCAN Accumulated o Right Justify JESJOBNO Details associated with these solutions are provided below: o z/OS Version 1 Release 13 Enhancements This product change includes the following enhancements for z/OS Version 1 Release 13: - New Logstream Reporting Information Added to OPSOPI File New data elements which represent System Maintenance Facilities (SMF) logstream storage allocations and usage are added to the Operations Incident (OPSOPI) file. The new data elements are derived from the new Logstream Statistics section added to the SMF type 23 record. - SPLIPADR is Updated for IPV6 Data element TCP/IP Trans Destination Address (SPLIPADR) is updated to contain the IPV6 IP address derived from field SMF6IPV6 in the File Transfer Section of IBM's Print Services Facility (PSF), SMF type 6 record. - New Specialty Engine Data Elements in BATMUG File New data elements with normalization factors, and the CPU time used when products are dispatched on zIIP or zAAP specialty engines are added to the Measured Usage (BATMUG) file. - Performance Indicators Added to Step and Job Files Address Space Has Incomplete Data (fffASPIN) and Address Space Class Rule Matched (fffASCRM) are added to the step-level and job-level files. - New Missed I/O Activity Data Elements Added to Step and Job Files Data elements Missed EXCPS (fffMSEXP) and Missed Device Connect Time (fffMSDCT) are added to the step-level and job-level files. Refer to Appendix A for a list of the new and updated data elements, and for detailed data element information, see the data dictionary entries. (0224) o Change Initiator CPU Time Elements to Essential Six initiator CPU time data elements data elements are now defined as essential in step-level and job level files in sharedprefix.MICS.GENLIB(SMFGENIN). Step-level files: PGMICPTM - Initiator CPU Time PGMISRTM - Step Initiator SRB Time PGMITCTM - Step Initiator TCB Time Job-level files: JOBICPTM - Initiator CPU Time JOBISRTM - Job Initiator SRB Time JOBITCTM - Job Initiator TCB Time (0225) o JOBCOPY and JOBSCAN Accumulated Data elements TYPRUN=COPY Specified (JOBCOPY) and TYPRUN=SCAN Specified (JOBSCAN) are now accumulated rather than retained. (0226) o Right Justify JESJOBNO When JES Job Number (JESJOBNO) is less than 7 digits, it is right justified to align with 7 digit JES job numbers in PROC PRINT listings and reports. After SMF6940 is applied, if you do any reporting which uses database files from multiple cycles, JESJOBNO will be misaligned in your reports. Ad hoc SAS code which selects observations or does comparisons based on JES Job Number (JESJOBNO), should either use the LEFT function, or imbed blanks at the beginning of the JESJOBNO literal if the job number is less than 7 digits. (0227)
PRODUCT CHANGE: SMF6943 DATE: January 13, 2012 SUBJECT: AUDIT ARCHIVE Abend U0999 After SMF6940 PREREQUISITES: SMF6940 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for the CA MICS Batch and Operations Analyzer: The AUDIT ARCHIVE stand-alone job or the AUDIT ARCHIVE job step in the WEEKLY job may abend with code U0999. This occurs only when the Batch User Job Activity File (BATJOB) is included in the archive. (0232)
PRODUCT CHANGE: SMF6945 DATE: January 31, 2011 SUBJECT: CA MICS Batch and Operations Analyzer Level Set for r12.7 PREREQUISITES: BAS7705 SMF6922 SMF6926 SMF6930 SMF6943 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for the CA MICS Batch and Operations Analyzer: A level-setting product change to close off maintenance for the end of the CA MICS r12.7 development cycle. (0233)
PRODUCT CHANGE: TAP7058 DATE: July 22, 2011 SUBJECT: Incorrect Data Element Values in HHA Files PREREQUISITES: TAP7051 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solutions for the CA MICS Tape Analyzer Option: o Corrected Missing Values in HVTHHA File Data Elements o Corrected Allocation of Drive and Mount Statistics o Minor Message Text Updates Details associated with these solutions are provided below: o Corrected Missing Values in HVTHHA File Data Elements In a TS77xx hybrid environment where some TS77xx clusters do not contain physical tape devices, SAS missing values have been found in the Recording Interval Time (DURATION) and Number of Recording Intervals (INTERVLS) data elements in the Hydra Hnode Activity (HVTHHA) file. This error is corrected. (0028) o Corrected Allocation of Drive and Mount Statistics In a TS77xx hybrid environment where some TS77xx clusters do not contain physical tape devices, Physical drive and mount statistics have been found in the Hydra Hnode Activity (HVTHHA) file for a cluster (HVTCLID) that does not have physical devices attached. Conversely, a cluster having devices attached may not show any drive or mount statistics. This error is corrected. (0029)
PRODUCT CHANGE: TAP7070 DATE: September 21, 2011 SUBJECT: Support for TS7700 Statistical Format v2.0 PREREQUISITES: TAP7054 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solutions for the CA MICS Tape Analyzer Option: o Support for TS7700 Statistical Format v2.0 o Minor documentation updates Details associated with these solutions are provided below. o Support for TS7700 Statistical Format v2.0 Support for IBM Virtualization Engine TS7700 Series Statistical Data Format v2.0. - Three new fields have been added to the data and are carried in the database. - Added protection against unexpected new versions of TS7700 input data. When data from an unexpected version is encountered in the raw data, message VTS00054E will be written to the MICSLOG and the records rejected. See "APPENDIX A" for a complete list of all data elements affected with this change. (30)
PRODUCT CHANGE: TAP7075 DATE: December 29, 2011 SUBJECT: Support for TS7700 Statistical Format v2.0a PREREQUISITES: TAP7070 TAP7058 BAS7705 COREQUISITES: None SUPERSEDES: TAP7074 DESCRIPTION: This product change includes the following solution for the CA MICS Tape Analyzer Option: Support for IBM Virtualization Engine TS7700 Series Statistical Data Format v2.0a. (32)
PRODUCT CHANGE: TDM6297 DATE: December 16, 2011 SUBJECT: Missing Source Members Cause DAILY Job Abends PREREQUISITES: TDM6295 BAS7705 COREQUISITES: None SUPERSEDES: TDM6296 DESCRIPTION: This product change includes the following solution for the CA MICS Application Extension Option for Tandem. Two sharedprefix.MICS.SOURCE members missing from product change TDM6295, first delivered with R12.5, are now delivered. The absence of these members causes the abend of DAILY jobs processing ZMS style measure data. (0021)
PRODUCT CHANGE: VCA6680 DATE: October 15, 2011 SUBJECT: New Volume Serial and Extended Format Data Elements PREREQUISITES: VCA6654 BAS7705 COREQUISITES: VCC6680 SUPERSEDES: None DESCRIPTION: This product change includes the following solutions for the CA MICS Space Analyzer Option: o New First Volume Data Element in the HSMMIG and HSBBAC Files o New Extended Format Data Element in VCA_VS File o Minor Documentation Updates Details associated with these solutions are provided below. o New First Volume Data Element in the HSMMIG and HSBBAC Files Data Element First Volume Serial - Migrate (MIGFSTVS) is added to the Migrated Data (HSMMIG) file. Data element First Volume Serial - Backup (BACFSTVS) is added to the Backup Data (HSBBAC) file. These data elements represent the first source volume serial of migrated or backup data sets. (0088) o New Extended Format Data Element in the VCA_VS File Data Element Extended Format Data Set (DAAEFDS) is added to the VSAM Data Set Allocation (VCA_VS) file. (0089)
PRODUCT CHANGE: VCC6680 DATE: October 15, 2011 SUBJECT: New Data Elements and Consolidated Maintenance PREREQUISITES: VCC6550 BAS7705 COREQUISITES: VCA6680 SUPERSEDES: VCC6552 VCC6554 VCC6556 VCC6558 VCC6561 DESCRIPTION: This product change includes the following solutions for the CA MICS Space Collector Option: o S0C4 ABEND in DCB Open Exit in VCCNTRL o New First Volume Data Elements in HSMMIG and HSBBAC Files o New Extended Format Data Element in the VCA_VS File o Master Catalog Excluded from Processing o Correction to the VCCAEXIT Sample User Exit o VVDS and BCS Data Sets Scan Details associated with these solutions are provided below. o S0C4 ABEND in DCB Open Exit in VCCNTRL A S0C4 ABEND may occur in the DCB open exit in VCCNTRL. This has been corrected. (0139) o New First Volume Data Elements in HSMMIG and HSBBAC Files Data elements First Volume Serial - Migrate (MIGFSTVS) is added to Migrated Data (HSMMIG) file and First Volume Serial - Backup (BACFSTVS) is added to Backup Data (HSBBAC) file. These data elements represent the first source volume serial of migrated or backup data sets. (0137) o New Extended Format Data Element in the VCA_VS File Data Element Extended Format Data Set (DAAEFDS) is added to the VSAM Data Set Allocation (VCA_VS) file. (0136) o Master Catalog Excluded from Processing When the master catalog resides on a PPRC secondary volume, it is not correctly identified during UCBSCAN processing when the device is defined on Subchannel Set 1. Scan processing has been updated to also look for "special" devices which include 3390S and 3390D device types. (0135) o Correction to the VCCAEXIT Sample User Exit After application of VCC6530, first delivered with r12 SP4 (PSP0904), the sample user exit (VCCAEXIT) points to the buffer prefix rather than the output record buffer. This product change corrects the error. (0134) o VVDS and BCS Data Sets Scan After application of VCC6550, if an EXCLUDECAT statement was specified and no EXCLUDVVDS statement was present, VVDS data sets were not scanned during VSAM scan processing. If an EXCLUDVVDS statement was specified and no EXCLUDECAT statement was present, BCS catalogs were not scanned. This has been corrected. (0133)
PRODUCT CHANGE: VMC6632 DATE: March 18, 2011 SUBJECT: Correct Negative Values in VMXVXU and VMXSGP Data Elements PREREQUISITES: BAS7680 VMC6630 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change provides the following solution for the CA MICS Resource Management Analyzer Option for VM/CMS: When duplicate monitor data is processed in the CA MICS DAILY job step DAY080, negative values can be produced in several data elements of the User Activity Sample Data (VMXVXU) file and one data element of the System Global Data (VMXSGP) file. The condition causing the negative values has been corrected for the following data elements: VMXSGP - System Global Data File SGPPAXWT - Pages Written to XSTOR for Private Addr VMXVXU - VMX User Activity Sample Data File VXUCONIO - Start Requests to Virtual Console VXUCTMIG - Pages Migrated to DASD from XSTOR VXUCTXRD - Number of PAGINs VXUCTXWT - Number of PAGOUTs VXUDASIO - Start Requests to Virtual DASD VXUMDCIA - Count of SSCHs Avoided by MDC Read Hits VXUPGFLT - Page Faults VXUPGSPL - Pages Spooled VXUPGRIO - Page Read I/Os Issued VXUPGWIO - Page Write I/Os Issued VXUSFIUC - Data Successfully Sent by IUCV From User VXUSPRIO - Spool Read I/Os Issued VXUSTIUC - Data Successfully Sent by IUCV To User VXUTTIME - Total CPU Time Used VXUTVPTM - Total Virtual CPU Time on Primary Processor VXUTVSTM - Total Virtual CPU Time on Secondary VXUVSPTM - Virtual + Simulation CPU Time on Primary VXUVSSTM - Virtual + Simulation CPU Time on Secondary VXUVTIME - Virtual CPU Time Used (0085)
PRODUCT CHANGE: VMC6633 DATE: June 2, 2011 SUBJECT: Correct VMC CGEN failure after VMC6630 PREREQUISITES: VMC6630 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change provides the following solution for the CA MICS Resource Management Analyzer Option for VM/CMS: If the ECPMF or NOECPMF keyword if not specified on the OPTION statement in sharedprefix.MICS.GENLIB(VMCGENIN), it will default to NOECPMF. (0086)
PRODUCT CHANGE: VMC6634 DATE: November 7, 2011 SUBJECT: Prevent ABEND on Missing VMCINTTS Element PREREQUISITES: VMC6630 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change provides the following solution for the CA MICS Resource Management Analyzer Option for VM/CMS: The DAILY no longer fails with a U0999 ABEND "BY variables not properly sorted error" for file WORKnn.VMXCPZ00 or WORK.VMXCPZ00. (0087)
PRODUCT CHANGE: VMC6650 DATE: November 30, 2011 SUBJECT: z/VM 6.2 Support PREREQUISITES: VMC6630 COREQUISITES: None SUPERSEDES: VMC6636 DESCRIPTION: This product change provides the following solutions for the CA MICS Analyzer Option for VM/CMS: o z/VM 6.2 Support o Channel Subsystem ID populated in VMXCPM file o New z/VM 6.2 Related Data Elements Added o VMXLPA & VMXLS1/2/3 Inquiries Handle Missing Files Details associated with these solutions are provided below: o z/VM 6.2 Support The VM release validation module is updated to properly identify MONITOR data generated by VM systems running z/VM Version 6 Release 2. Data element VM System Release Level (VMLEVEL) is set to 'z/VM V6 R2.0' when z/VM Version 6 Release 2 monitor data is processed. (88) o Channel Subsystem ID populated in VMXCPM file Commencing with VM 6.2, the Channel subsystem (CSS) ID is available in the Monitor Domain, System Configuration record. The CSS ID value is populated in the VM Channel Path Measurement (VMXCPM) file's VMXCSSID key sequence field. (90) o New z/VM 6.2 Related Data Elements Added New guest relocation and z/VM 6.2 related data elements are added to the following files: VMXLCP - VMX Logical Processor Activity File VMXSCF - VMX System Configuration File VMXSGP - VMX System Global Data File VMXVXF - VMX User Data Configuration File VMXVXT - VMX User Transaction Data File VMXVXU - VMX User Activity Sample Data File See Appendix A for a list of new data elements, and refer to the data dictionary entries for detailed data element information. (91) o VMXLPA & VMXLS1/2/3 Inquiries Handle Missing Files The following inquiries read input from the VM Channel Path Measurements (VMXCPM) file: VMXLPA - VM Channel Path Activity Report VMXLS1 - VM Channel Path Load Analysis VMXLS2 - VM FICON Channel Path Load Analysis VMXLS3 - VM HiperSocket Channel Path Activity When the input file does not exist in the associated unit database being accessed, the inquiry terminates with ABEND code U0998 and an appropriate message in the MICS log. (0089)
PRODUCT CHANGE: VMC6655 DATE: February 16, 2012 SUBJECT: CA MICS Analyzer for VM/CMS Level Set for r12.7 PREREQUISITES: BAS7705 VMC6632 VMC6633 VMC6634 VMC6650 COREQUISITES: None SUPERSEDES: None DESCRIPTION: This product change includes the following solution for the CA MICS Analyzer for VM/CMS: A level-setting product change to close off maintenance for the end of the CA MICS r12.7 development cycle. (0094)