IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Problem creating ALIAS


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
bhavin.mehta

New User


Joined: 25 Jun 2012
Posts: 34
Location: India

PostPosted: Tue Nov 26, 2013 8:59 pm
Reply with quote

@enrico-sorichetti:
Initially I created Alias as below
Code:

 DEFINE ALIAS -
  (NAME('MYNAME') -
           RELATE('CATALOG.SYS.USER'))


Which went successfully, and I could see 'MYNAME' in 3.4 with Vol as '*ALIAS'.

Then I tried the below:-
Code:

 DEFINE ALIAS -
  (NAME(MYNAME.A.CLIST) -
   RELATE(RACFID.A.CLIST) -
   CATALOG('CATALOG.SYS.USER'))


The above job failed!!!
Code:

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?
Back to top
View user's profile Send private message
Pete Wilson

Active User


Joined: 31 Dec 2009
Posts: 495
Location: London

PostPosted: Tue Feb 18, 2014 8:54 pm
Reply with quote

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.
Back to top
View user's profile Send private message
steve-myers

Active Member


Joined: 30 Nov 2013
Posts: 882
Location: The Universe

PostPosted: Tue Feb 18, 2014 10:19 pm
Reply with quote

  • 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)
Back to top
View user's profile Send private message
nevilh

Active User


Joined: 01 Sep 2006
Posts: 262

PostPosted: Wed Feb 19, 2014 9:20 pm
Reply with quote

Do you have access to RACFID.A.CLIST?
Back to top
View user's profile Send private message
Pete Wilson

Active User


Joined: 31 Dec 2009
Posts: 495
Location: London

PostPosted: Wed Feb 19, 2014 10:03 pm
Reply with quote

Is 'CATALOG.SYS.USER' your Mastercatalog or a Usercatalog btw?
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts problem in select max when executing ... IMS DB/DC 6
No new posts Sysncsort - Justification problem SYNCSORT 6
No new posts XML Parsing in COBOL creating "h... COBOL Programming 0
No new posts Creating additional seqnum/Literal wh... DFSORT/ICETOOL 4
No new posts Creating a single-record file with CO... DFSORT/ICETOOL 8
Search our Forums:

Back to Top