After upgrading to a new release of CA TPX, users are assigned the default profile rather than the profile that should be assigned via the security interface.
search cancel

After upgrading to a new release of CA TPX, users are assigned the default profile rather than the profile that should be assigned via the security interface.

book

Article ID: 3964

calendar_today

Updated On:

Products

TPX - Session Management Vman Session Management for z/OS

Issue/Introduction

Upon migration to the latest TPX release, users without a VSAM record whose profile is assigned by external security (ACF2, Top Secret or RACF) revert to the default user profile coded in the SMRT.

Environment

CA TPX for z/OS

Cause

Most often the cause of this behavior is that the TPX exits that you are using have not having been reassembled with the libraries from the new release of CA TPX.

Resolution

  1. Reassemble your custom exit source code with current release macros
  2. Cycle TPX or TPXOPER RELOAD EXIT=exitname
Powered by Wolken Software