Initially I created Alias as below
DEFINE ALIAS -
Which went successfully, and I could see 'MYNAME' in 3.4 with Vol as '*ALIAS'.
Then I tried the below:-
DEFINE ALIAS -
The above job failed!!!
IDC3018I SECURITY VERIFICATION FAILED
IDC3007I ** VSAM CATALOG RETURN CODE IS 56
IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
My questions are:
1) If I do not have access to create a file as "MYNAME.A.CLIST" (i.e. files with MYNAME as a the first qualifier) then how come first ALIAS worked? How come MYNAME got created?
2) Is there a way to create files with MYNAME as a the first qualifier?
There can be different RACF profiles at different levels of the dataset name. So there may be a specific profile for MYNAME.A.* which is restricting you.
Curious why you would want a Usercatalog alias (MYNAME) in the same catalog as a NONVSAM alias? Normally a Usercatalog Alias is in the Mastercatalogs(s) and relates to a usercatalog. A NONVSAM alias is usually define in a Usercatalog and relates to another file in the same usercatalog.
Joined: 30 Nov 2013 Posts: 847 Location: The Universe
If the first DEFINE statement worked, I suspect the security profiles for your system are wrong. Ordinary users should not be creating (or deleting, for that matter) master catalog aliases. For that matter, if MYNAME is your userid, the admins that setup your userid screwed up. Regardless, you should notify security right now.
The second DEFINE statement should have produced a three line ICH408I message in the JESMSGLG JES data set for the job. What was it? All 3 lines. If your job has gone away, you should be able to find it in your SYSLOG.
Regardless, the second DEFINE statement is wrong: the CATALOG keyword should be outside of the parens, DEFINE ALIAS(NAME(xxx) RELATE(xxx)) CATALOG(xxx)