Why is CAS9 assigned to the default user ++++++ even though it is assigned to another userid on the production lpar?
On the production lpar, it is assigned to the user CAS9.
Is there anything to be changed from CAS9 side or it is completely security problem?
COMMON SERVICES 15.0 - z/OS supported releases -
There can be several causes of this problem:
1. From a Security perspective, if CAS9 task starts before any given ESM, it will be unable to find a matching STC user for it.
So the CAS9 STC must be started after the full security product initialization.
2. A userid must be associated to the CAS9 STC.
If the userid is missing, CAS9 will be assigned to the default user ++++++