Sysview for Db2 user kicked back to ISPF without any indication of a problem when selecting view active threads (option 5)

Products

• SYSVIEW Performance Management Option for DB2 for z/OS

Issue/Introduction

Upgraded Sysview Performance Management Option for Db2 for z/OS (IDB2) to the new release.
Currently, all users are able to use all functions within IDB2 except for one uer who is unable to perform
View Active Threads (Option 5).  

This one user gets kicked out of IDB2 (back to ISPF main menu) when selecting option 5 to View Active Threads.
This user can perform all other functions in IDB2 except for viewing active threads.

Cause

The cause of this problem lies within the IDB2 VSAM Profile Dataset.  It is unknown how the record associated
with the impacted user in the VSAM Profile Dataset got corrupted, but this is causing the problem.

Resolution

The correction to this problem is to either create a brand new VSAM Profile Dataset or to use a product that
can edit the VSAM Profile Dataset like File Master, and delete the row associated with the impacted user.

Additional Information

The IDB2 VSAM Profile dataset is allocated in the INSIGHT Clist.  Also, in the IDB2 hlq.SOURCE library the member IDVSAMSY
can be used to allocate a new Profile Dataset.