Once the Z/OS system was upgraded from 2.4 to 2.5, during the start of VANTAGE STC the following messages are displayed:
ICH408I USER(XXXX ) GROUP(xxxxx) NAME(XXXXXXX
SYS1.VVDS.VCDMP01 CL(DATASET ) VOL(TOTO01)
SYS1.VVDS.VCDMP00 CL(DATASET ) VOL(TOTO00)
INSUFFICIENT ACCESS AUTHORITY
FROM SYS1.VVDS.* (G)
INSUFFICIENT ACCESS AUTHORITY
FROM SYS1.VVDS.* (G)
ACCESS INTENT(READ ) ACCESS ALLOWED(NONE )
ACCESS INTENT(READ ) ACCESS ALLOWED(NONE )
Release : 14.1
This security check has been introduced by UJ08399 APAR.
UJ08399 ++ HOLD(UJ08399) SYS FMID(HDZ2250) REASON(ACTION) DATE(22126)
COMMENT
(****************************************************************
* Function Affected: (OA62372) *
* DFSMS *
* DFSMSdfp *
****************************************************************
* Description: *
* Update security definition *
****************************************************************
* Timing: *
* Pre-APPLY *
****************************************************************
Before applying this PTF, ensure that users running programs
that read VVDSs directly have at least read authority to the
VVDSs. Discrete profiles do not work on VVDS data sets.
Here is an example of how to give read authority to all users
via RACF generic profile:
ADDSD 'SYS1.VVDS.V*' UACC(READ)
After applying the PTF and IPLing if you receive SAF
authorization fail messages for the VVDS, this means that you
have users that do not have the needed authority. If the access
is intended, then grant those users appropriate authority via a
generic profile.
Opens of VSAM data sets are not affected by this change.).