Users cannot logon to TPX, the TPX Log shows TPXL0400 ... VSAM ERROR

Document ID:  TEC470628
Last Modified Date:  08/02/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA TPX Session Management for z/OS
  • CA STX Session Management for z/OS
  • CA Teleview Session Management for z/OS
  • CA Vman Session Management for z/OS

Releases

  • CA TPX Session Management for z/OS:Release:5.1
  • CA TPX Session Management for z/OS:Release:5.2

Components

  • CA-TPX for OS/390:TPX
Introduction:

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 information's for file sharing between TPX regions is corrupted. We call this VSI record 'record 0' in TPX. It contains information's like the volume, the catalogue where the VSAM-file resides, high-used RBA etc.

Instructions:

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.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >