Can 500 profiles be assigned per user? What is the impact on the TPX VSAM databases. Is there any limitations in assignment to users?
Release: 5.4
Component: TPX for Z/Os
There is nothing in TPX code that limits the number of profiles which can be defined for a user.
There is also no limit to the number of sessions you can define in each profile.
For 'Static' or 'Half Dynamic' TPX users which are saved into the TPX ADMIN2 file please consider the following.
Since the list of profiles is appended to the user record in ADMIN2, this can cause a problem that the maximum RECORDSIZE of the TPX ADMIN2 file is too small when trying to save the record.
In the TPXLOG if this message is observed 'TPXL0400 VSAM ERROR with RTNCD/FDBK = 0008006C'.
The delivered ADMIN2 file has a maximum RECORDSIZE of 2000 bytes.
A REORG maybe needed for ADMIN2 file with a bigger maximum RECORDSIZE so that the user record with the appended profile list fits again.
The limitation here is due to VSAM's record size limit of 32k for non-spanned files.
However, bear in mind that the more profiles each user has the longer it could take to log on because of reading the VSAM file and merging the profiles for each user.
Also STORAGE is a primary consideration for overall limitations of TPX definitions (tables/profiles/sessions/users/virtual terminals).
While TPX provides for 'unlimited' definitions of TPX entities, the storage boundaries of your TPX region size
(and TPX/SMRT table storage definitions) will limit the overall information you can define for a single TPX.