TPF Continuous Data Collection Client for TPF v. 1.4.8 Current CDC Client APAR: PJ32343 CDC Client APAR History: PJ31424 PJ31568 PJ31540 PJ31437 PJ31144 PJ30885 PJ30979 PJ30946 PJ30841 PJ30609 PJ30503 PJ30465 PJ30251 PJ30137 The CDC client is a Java based application. Although Java based, it has been tested and developed only for the Windows XP/2000 platform. More information can be found in the “Transaction Processing Facility System Performance and Measurement Reference”. ________________________________________________________________________ Contents: A. Changes B. Requirements C. Setup D. Running the CDC Application E. Interpreting CDC Data F. Modifying the source code G. Trademarks ________________________________________________________________________ A. Changes: PJ32343: * Update to periodically force a close of the connecection to the real-time MQ * queue on TPF. The connection will not last more than 30 seconds. This is done * to eliminate a long-running MQ ECB for the connection which was preventing * ZOLDR ACCEPTs from completing. PJ31424: * Added support for displaying defined LODIC CPU utililization classes. This metric is only available under z/TPF, not TPF 4.1. PJ31568: * Added branch relative target check mode switch to the system trace table. This metric is only available under z/TPF, not TPF 4.1. PJ31540: * Added DASD Service Time to the display. This metric is only available under z/TPF, not TPF 4.1. PJ31437: * Added "Enhanced" Channel Utilization to the collector/display. This metric is only available under z/TPF, not TPF 4.1. PJ31144: * Added subsystem lethal utility switches and system trace information to the display PJ30885: * Added LPAR utilization reporting to the collector/display. This metric is only available under z/TPF, not TPF 4.1 PJ30979: * Added “Channel Utilization” to the collector/display. This metric is only available under z/TPF, not TPF 4.1 PJ30946: * Corrected error when querying core blocks using DB2 * Corrected AM/PM error in the query window * Fixed an issue with the decoupled collection/refresh rate * Fixed IndexOutOfBoundsException in CDCBeanChart * Mapped device pools correctly PJ30841: * Corrected memory consumption error in the CDCJfreeChart class * If using the jfreechart package, it is necessary to update the package to jfreechart-1.0.0 PJ30609: * The client is now capable of monitoring both z/TPF and TPF 4.1 * The screen refresh rate has been decoupled from the host collection rate PJ30503: * DB2 timestamps are now used when querying against a DB2 database * The CDCDB2TableDefUpdates.java class is now obsolete PJ30465: * Changed the way TPFMQ information is displayed * Improved GUI performance when querying a database for historical data * Added a progress bar to the query display * CDC now requires SWT library version 3.1. See the requirements section for more details * If using the jfreechart package, it is necessary to update the package to jfreechart-1.0.0-rc1 * Installation naming convention for the jfreechart package has changed. See the requirements section for more details * CDC class files are now bundled in with the tpf_cdc.jar file PJ30251: * CDC now uses a uniquely named queue per LPAR in loosely coupled environment: CDCRTQ. (for example, CDCRTQ.A, CDCRTQ.B, and so on). PJ30137: * Corrected handling of the shutdown indicators in the CDC client and updated the CDCHeader class. B. Requirements: * The latest Sun 1.4.2_X or 1.5.X JRE (Multilanguage support). For download and installation instructions please reference: http://java.sun.com * In order for the CDC client to communicate correctly with TPF host, it is necessary that the JRE contain the charsets.jar file in its \lib directory. If this file is not present, the following error will occur: java.io.UnsupportedEncodingException: Cp500 Try installing the Java SDK instead of the standalone JRE. This should include the charsets.jar file. * The graphical user interface (GUI) components are built on top of the Eclipse Standard Widget Toolkit (SWT): http://www.eclipse.org. Please follow the “downloads” link to the left of the page. The CDC client requires the “SWT Binary and Source” download for version 3.1.0. * The client communicates to TPF through the use of WebSphere MQ, version 5.3 client for Windows. Download is free at: http://www-1.ibm.com/support/docview.wss?rs=203&uid=swg24006105&loc=en_US&cs=utf-8&lang=en C. Setup: 1. Create a folder in which to extract the files in tpf_cdc.zip (example: C:\TPFCDC) 2. The SWT binary zip file (swt-3.1-win32-win32-x86.zip) contains three DLL files, (swt-awt-win32-3138.dll, swt-gdip-win32-3138.dll, swt-win32-3138.dll), and “jar” file (swt.jar). Extract these files into the directory that was just created. 3. The WebSphere MQ contains two necessary “jar” files for CDC, (com.ibm.mq.jar, connector.jar). Copy these files to the CDC directory. 4. The CDC client come pre-packaged with the same charts as the previous sample version (s11_chart.jar). A user exit (abstract Java class, CDCChart.java) has been provided so that the user may implement and use any Java chart package desired. The implementation of the s11_chart.jar package also serves as a sample on how to implement the abstract class. Another sample implementation of CDCChart.java has been provided using the JFreeChart package. The JFreeChart package is NOT PROVIDED WITH THE CDC PRODUCT. The user will use the JFreeChart package at his/her own risk. IBM is not responsible or liable nor provides any warrantee/guarantee for the JFreeChart package. The package is available under the LGPL: http://www.jfree.org/jfreechart/. If it is decided to use these charts, the release that has been tested is jfreechart-1.0.0. The package will contain 2 “jar” files that need to be copied into the CDC directory that was created earlier ( jfreechart-X.X.jar, jcommon-X.X.jar). Rename these to jfreechart.jar and jcommon.jar respectively. 5. If DB2 is used as the storage medium and the user wishes to retrieve historical data through the client, the DB2 Administration Client will need to be installed on the workstation the client resides on, and the database will need to be configured through the configuration assistant: http://www-306.ibm.com/software/data/db2/udb/support/downloadv7.html#WINDOWS. The db2java.zip file that is installed with DB2 needs to be copied over into the CDC directory. D. Running the CDC Application: A Windows batch file (cdc.bat) is provided to start off the application. If everything is setup correctly, once the batch file is executed, the CDC configuration dialog box should appear. The application is meant to monitor one TPF complex (loosely coupled or stand alone) at a time. By monitoring only one complex, there would only be one CPU B, C, D, etc. per CDC application instance. If more than one complex is to be monitored, please initiate a second instance of the application. For all connectivity setup/options needed for TPFMQ/WebSphere MQ queues and channels, please see the “TPF System Performance and Measurement Reference” documentation on the TPF Information Center. E. Interpreting CDC data: The CDC client provides two ways of displaying the data it receives from the host: a) Real-time values b) Mean values over a certain time period How the data is presented can be configured through the CDC configuration dialog. The dialog allows the user to: a) Turn debug messages on. These will flow to standard out b) Set a time window for rolling min, max, mean values (real time display) c) Or decouple the screen refresh rate from the host collection rate (averages over a time period) If the user decouples the screen refresh rate from the host collection rate, the rolling time window for the min, max, mean values is no longer in effect. The min, average, and max values displayed are for the time span at which the screen is refreshed. If the screen refresh rate is not decoupled from the host collection rate and the time window for rolling min, max, mean vales is set to one (1) minute, the application will present a real time display of the data (instantaneous values) in addition to the min, max, mean values for the last minute. If it is set to 15, the min, max, mean values are always for the last 15 minutes. If the user decides to decouple the screen refresh rate from the host collection rate, the time window for the min, max, mean is no longer in effect. Instead, the user specifies how often the screen should be refreshed (minimum of one (1) minute, maximum of thirty (30)). Instantaneous values are no longer shown. Only min, max, and mean values for the refresh time specified are displayed. So if the refresh time is set to once every minute and the host collects the data every five (5) seconds, then the client would have twelve (12) observations for every minute. It would display the min, max, and mean for those twelve (12) observations every minute. It would then discard those observations and start a new for the next minute. When decoupling the screen refresh rate from the host collection rate keep the following things in mind: a) For the CDC Summary Window, all values shown are mean values for the time span of the last screen refresh (including all values in the LPAR tab) b) For the CDC Detail Window for an TPF LPAR, interpret the values on the tabs as follows: i) System Summary: All values NOT listed as min, max, mean are mean values for the time span of the last screen refresh, EXCEPT the MQ Summary table ii) Subsystems: All values NOT listed as min, max, mean are mean values for the time span of the last screen refresh iii) System TCP/IP and MQ Data: ALL values are instantaneous. They represent the values collected at the time the screen refreshed iv) SSU Msgs, MPIF, LODIC, Tape, and DASD: The MPIF, Tape, and DASD tables all contain instantaneous values. The ECB Priority Class, Time Slice, and Subsystem User Messages tables contain mean values v) I-Stream and Shutdowns: All values NOT listed as min, max, mean are mean values for the time span of the last screen refresh, EXCEPT System Shutdown Count table, where the values are rolling count for the duration of the client application vi) Channel Utilization: All values are mean values for the time span of the last screen refresh F. Modifying the source code: Full source is provided with the application and included in the tpf_cdc.jar file. The application was developed using the Eclipse 3.1 IDE, although the user can use which ever IDE is preferred. There is a user exit provided on the TPF host CDC application in segment CDCA (for detailed information, please refer to the TPF CDCA segment). This allows users to collect their own data. This data is then passed on to the client in binary format. The client only reads the data and stores it into a Java byte array. It is up to the user to parse the data and display it in the GUI. If the CDCA user exit is implemented on TPF, the user may wish to do the following in the client: * Implement correct parsing for their information (see com.ibm.tpf.cdc.CDCMqCommModel.java, search for CDCA) * Provide a GUI representation for their data in the CDC client F. Trademarks: The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM DB2 DB2 Client Action Enablers DB2 Universal Database Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others. © Copyright IBM Corp. 2004, 2007