Performance Toolkit for VM Feature: FL 440 Offer

An ABEND in the Performance Toolkit MODULE was reported on 14 January 2007 which potentially can affect every Performance Toolkit customer. This was a forced ABEND which occurred when the system TOD clock rolled from X'BFxxxxxx xxxxxxxx' to X'C0xxxxxx xxxxxxxx'. It appears the ABEND was added as a debugging aid quite some time ago and was never removed. APAR VM64152 was created to correct this ABEND on Performance Toolkit for VM Function Levels 510 and 520. The APAR was closed on 17 January 2007 and the following PTFs are available:

Function Level APAR PTF Description
520 VM64152 UM31957 PERFKIT ABENDS WITH DMSABE141T OPERATION EXCEPTION OCCURRED
510 VM64152 UM31956 PERFKIT ABENDS WITH DMSABE141T OPERATION EXCEPTION OCCURRED

Since Performance Toolkit for VM Function Level 440 is no longer supported by IBM, there is no official PTF available for this problem. However, since this problem can affect every FL440 customer, we are making available an updated copy of the FL440 PERFKIT MODULE. This is a one-time only offering to aid customers in their migration from z/VM 4.4.0 and Performance Toolkit for VM FL440 to a supported release and function level. The instructions for obtaining and installing this updated MODULE follow below.

Before you install the Performance Toolkit code, please read through all the instructions.


Planning

Here are a few things you need to know before you install this update to the z/VM 4.4.0 Performance Toolkit code:

  • z/VM 4.4.0 and Performance Toolkit for 4.4.0 are both out-of-service. No service beyond the last z/VM 4.4.0 RSU is available for either of these products.

  • The update you are about to download and install is a one-time offering to correct an ABEND situation.

  • To continue receiving support and service for Performance Toolkit, you must be running a currently supported release of the feature. Refer to VM End of Service Effective Dates for a list of currently supported z/VM releases.

Now, you are ready to download the updated Performance Tooklit MODULE and install it on your system.

 


Download the code

Get the new MODULE

  1. Download the code. to your work station.
  2. Upload the VMARC from your work station to your z/VM 4.4.0 system. You must transfer the VMARC file in binary format.

Unpack the VMARC file

You must have a copy of the VMARC MODULE to unpack the PKSEGOUT VMARC file. To get a copy of the VMARC MODULE, see the VM download information.

  1. Access the minidisk or SFS directory, where the VMARC file is stored, as file mode A.

  2. Convert the PTK440 VMARC file to the CMS VMARC format:
    pipe < ptk440 vmarc a
         | fblock 80 00
         | > ptk440 vmarc a f 80
    

  3. Unpack and expand the PTK440 VMARC file:
    vmarc unpk ptk440 vmarc a
    

    This VMARC UNPK will place one file on filemode A. This is the replacement PERFKIT MODULE

    • PERFKIT MODTD440

    This file will be used in the next step, Install using VMSES/E

  4. Reaccess your 191 disk as file mode A.


Install using VMSES/E

  1. Log on to the Performance Toolkit user ID.
    logon 4vmptk40
    

  2. Ensure your LOCALMOD disk has at least 5 available cylinders of 3390 DASD space (or equivalent) to hold the local modifications for the Performance Toolkit MODULE.

  3. Access the minidisk or SFS directory containing the PERFKIT MODTD440 file.

  4. Install this file as a VMSES/E local modifications.
    vmfsetup 4vmptk40 perftk
    vmfrepl perfkit module 4vmptk40 perftk
            perfkit modtd440 fm ( $SELECT LOGMOD
            td440 OUTMODE LOCALMOD
    vmfbld ppf 4vmptk40 perftk (serviced
    
    fm in the commands above is the file mode where the PERFKIT MODTD440 resides.
Go to Verify the install to make sure the Performance Toolkit code was installed properly.

 


Verify the install

To verify that the install process completed successfully:

  1. IPL CMS.
  2. Start Performance Toolkit.
    perfkit
    
  3. The first message you see should read
    FCXBAS500I Performance Toolkit for VM FL440 VERN440
    
    If it does, then you are running with the updated copy of the MODULE.