Skip to: Abstract | Comments | Solution | Migration | Download
APAR NUMBER: PJ31466 PRODUCT: z/TPF FUNCTIONAL AREA: CONTINUOUS DATA COLLECTION (CDC) SHIPPED IN PUT: 3 ABSTRACT: Provide DASD service time in CDC server PACKAGE CONTENTS: Source Segments: (C) base/include/tpf/c_icdc.h (C) base/macro/icdcc.mac (C) base/macro/rcssc.mac (C) base/rt/cdcp.c (C) base/rt/cdcq.c (C) base/rt/cdcq.sqc (C) base/rt/cdcr.asm (C) base/rt/cdcs.cpp (C) base/rt/cdcx.c (C) base/rt/cdcx.sqc Object Only Binaries: None. Configuration Independent Binaries: (C) base/load/CDCO.so (C) base/load/CDCP.so (C) base/load/CDCS.so (C) base/obj/cdcp.o (C) base/obj/cdcq.o (C) base/obj/cdcr.o (C) base/obj/cdcs.o (C) base/obj/cdcx.o Support Files: base/lst/cdcp.lst base/lst/cdcq.lst base/lst/cdcr.lst base/lst/cdcs.lst base/lst/cdcx.lst base/lst/CDCO.map base/lst/CDCP.map base/lst/CDCS.map OTHER BINARIES TO BUILD: None. PREREQUISITE APARS IN APPLICATION ORDER: base/include/tpf/c_icdc.h PJ30403(1) PJ30609(2) PJ30742(2) PJ30944(2) PJ30979(2) PJ30885(2) PJ31329(3) base/macro/icdcc.mac PJ30609(2) base/rt/cdcp.c PJ30403(1) PJ30419(1) PJ30609(2) PJ30742(2) PJ30944(2) PJ30979(2) PJ30885(2) PJ31329(3) PJ31332(3) base/rt/cdcq.c PJ30609(2) PJ30742(2) PJ30979(2) PJ30885(2) PJ31332(3) base/rt/cdcq.sqc PJ30609(2) PJ30742(2) PJ30979(2) PJ30885(2) PJ31332(3) base/rt/cdcr.asm PJ30609(2) PJ31329(3) base/rt/cdcs.cpp PJ30403(1) PJ30609(2) PJ30742(2) PJ30979(2) PJ30885(2) base/rt/cdcx.c PJ30609(2) PJ30742(2) PJ30979(2) PJ30885(2) PJ31329(3) base/rt/cdcx.sqc PJ30609(2) PJ30742(2) PJ30979(2) PJ30885(2) PJ31329(3) base/load/CDCO.so PJ30609(2) PJ30742(2) PJ30979(2) PJ30885(2) PJ31332(3) base/load/CDCP.so PJ30403(1) PJ30419(1) PJ30609(2) PJ30742(2) PJ30944(2) PJ30979(2) PJ30885(2) PJ31329(3) PJ31332(3) base/load/CDCS.so PJ30403(1) PJ30609(2) PJ30742(2) PJ30979(2) PJ30885(2) base/obj/cdcp.o PJ30403(1) PJ30419(1) PJ30609(2) PJ30742(2) PJ30944(2) PJ30979(2) PJ30885(2) PJ31329(3) PJ31332(3) base/obj/cdcq.o PJ30609(2) PJ30742(2) PJ30979(2) PJ30885(2) PJ31332(3) base/obj/cdcr.o PJ30609(2) PJ31329(3) base/obj/cdcs.o PJ30403(1) PJ30609(2) PJ30742(2) PJ30979(2) PJ30885(2) base/obj/cdcx.o PJ30609(2) PJ30742(2) PJ30979(2) PJ30885(2) PJ31329(3) COMMENTS: Device service time is the time that it takes for a channel subsystem to respond to an I/O request from the z/TPF system. That is, the time from when the z/TPF system sends a start I/O request to the channel subsystem to when the channel subsystem responds back to the z/TPF system with a channel end (CE) or device end (DE). It can be very helpful to see the change in device service time at different times of the day, especially when utilities are running, which is not normally when regular data collection is running. SOLUTION: The continuous data collection (CDC) collector/server will collect and make available the average service time between sampling intervals for each logical subsystem (LSS) in the complex. This information will be made available to the CDC client on the existing MQ interface, and will be included in historical data written to individually selected CDC storage mediums: z/TPFAR, z/TPFDF, z/TPF collection support file system, and tape. The average DASD service time for the LSS will be calculated as the average for all online devices on the LSS. Offline devices will not count in the average. The rate of change for each LSS is calculated as the delta between sampling intervals of the sum of accumulated I/O time for each online device in the LSS divided by the count of I/Os for each online device in the LSS, or: AccumulatedServiceTimeCurrent - AccumulatedServiceTimePrevious -------------------------------------------------------------- AccumulatedIOcountCurrent - AccumulatedIOcountPrevious Accumulated service times are reported in microseconds. Each LSS will be identified by the Record Cache Subsystem ID (SSID=MF1SSID) in the data going over to the CDC client and CDC storage medium. The lowest online device address (SDA) on the LSS is also returned for device/LSS correlation. CDC client support for DASD service time is not included in this apar. COREQS: None. MIGRATION CONSIDERATIONS: Build and load process changes: The CDC server should be shutdown (ZCDCO STOP ...) before applying this apar, and restarted (ZCDCO START ...) after the apar code is loaded and active. Database changes: The z/TPFAR database will contain the following new table: CREATE TABLE TPFCDC.DASD_SERVICE_TIME_D ( TPF_TIME TIMESTAMP NOT NULL, DB2_PTN_NO SMALLINT NOT NULL, CPU_IND CHARACTER(1) NOT NULL, RESTART_IND SMALLINT NOT NULL, DST_SSID SMALLINT NOT NULL DEFAULT, DST_LOWSDA SMALLINT NOT NULL DEFAULT, DST_ADSTIME INTEGER NOT NULL DEFAULT, DST_RESERVED CHARACTER(4) NOT NULL DEFAULT ); CREATE UNIQUE INDEX "TPFCDC"."DASD_SERVICE_TIME_IDX" ON TPFCDC.DASD_SERVICE_TIME_D (TPF_TIME, CPU_IND, DST_SSID); BUILD COMMANDS AND INSTRUCTIONS: #maketpf commands for linux maketpf -f CDCO cdcq.o maketpf -f CDCP cdcp.o cdcq.o cdcr.o cdcx.o maketpf -f CDCS cdcs.o maketpf CDCO link maketpf CDCP link maketpf CDCS link UPDATED INFORMATION UNITS: z/TPF and z/TPFDF Migration Guide: PUT 2 and Later z/TPF System Performance and Measurement Reference See your IBM representative if you need additional information. DOWNLOAD INSTRUCTIONS: http://www.ibm.com/software/htp/tpf/pages/maint.htm APAR URL: http://www.ibm.com/software/htp/tpf/ztpfmaint/put3/PJ31466.htm APAR Package