CA TPX Session Management for z/OS

Tuesday Tip: Do you know why message "TPXL0400 ... VSAM ERROR" might appear?

  • 1.  Tuesday Tip: Do you know why message "TPXL0400 ... VSAM ERROR" might appear?

    Posted 08-22-2014 09:35 AM

    When users cannot logon to TPX and the TPX Log shows messages like

     

    TPXL0400 <date> <time> VSAM ERROR. KEY = xxxxxxx RTNCD/FDBK = 00080020 REQUEST TYPE = 00 RBA = 0000000000000000

     

    then a possible cause is that the VSAM VSI record in the TPX VSAM files which contains informations for file sharing between TPX regions is corrupted. We call this VSI record 'Record 0' in TPX. It contains informations like the volume, the catalogue where the VSAM-file resides, high-used RBA etc.

     

    To make the VSAM file useable again delete 'record 0' by using the following procedure:

    1. Shutdown all TPXs accessing the VSAM files.
    2. Execute a TPXBATCH Job which contains only this line
      RESET INTEGRITY (ADMIN1 ADMIN2 MAIL NOTES VIEW)
      This Job will delete 'record 0' from all mentioned files. A sample job can be found in TPX.SAMPLIB(BATCHINI).
    3. Restart TPX. Now 'record 0' will be rebuilt with the correct informations.
      Logon to TPX should now be possible again.