IBM MAINFRAME HELP & SUPPORT FORUMS
Technical Forums for IBM Mainframe Applications like COBOL, JCL, CICS, DB2, FileAid, DFSORT, Endevor, Xpediter, CoolGen, CA-7&11, AbendAid, IMS, IDMS, PL/I, MqSeries, SyncSort, Assembler, ChangeMan, Easytrieve, InterTest, REXX, CLIST etc...
 

problem in viewing the alias name

THIS IS AN ARCHIVE FORUM: CLICK HERE TO GO TO THE ORIGINAL TOPIC

 
       IBMMAINFRAMES.com - IBM Mainframe Support Forums Index -> TSO/ISPF
View previous topic :: View next topic  
Author Message
sailaja.sn



Joined: 14 Jul 2008
Posts: 4
Location: Chennai

Posted: Mon Jul 14, 2008 2:31 pm    Post subject: problem in viewing the alias name  

I have tried creating the alias name for a dataset by using
"DEFINE ALIAS( NAME("aliasds") RELATE ('"realds')" . It works fine. But I am not able to view the aliasds using 3.4. Is this possible? can u provide me sample algorithm to create and view the alias name for a dataset.

Thanks,
Sailaja
[/Search]
Back to top  
Aaru



Joined: 03 Jul 2007
Posts: 1136
Location: Mumbai - India

Posted: Mon Jul 14, 2008 2:51 pm    Post subject: Reply to: problem in viewing the alias name  

sailaja,

Alias can be created using IDCAMS - DEFINE ALIAS. You can open the ALIAS in 3.4 and the dataset mentioned in RELATE would be opened.

Let me know if i have misunderstood your question.
Back to top  
expat



Joined: 14 Mar 2007
Posts: 3509
Location: Brussels once more ...

Posted: Mon Jul 14, 2008 2:58 pm    Post subject:  

It has worked OK for me in the past. ANd have just tested again, and it works perfectly.

Please post your code qand output.
Back to top  
sailaja.sn



Joined: 14 Jul 2008
Posts: 4
Location: Chennai

Posted: Mon Jul 14, 2008 3:52 pm    Post subject:  

Hi,
address TSO
aliasds = 'cfb1.srcedat1'
"DEFINE ALIAS( NAME("aliasds") RELATE('"NUNAS66.PRIME.QBBBF.SOURCE.DATA"'))"
exit

This creates the alias ds as 'NUNAS66.cfb1.srcedat1'. It is appending my UserID as the high qual for the dataset. I was also able to view the ds 'NUNAS66.cfb1.srcedat1'. But my intention is to create the dataset without that higher qual. So i ran the rexx by insrting the quotes for the aliasds variable as such
"DEFINE ALIAS( NAME('"aliasds"') RELATE('"NUNAS66.PRIME.QBBBF.SOURCE.DATA"'))" . Now it is saying that the alias is created but when I am trying to virw the cfb1.srcedat1 in 3.4 , it is saying that the 'Dataset Not Cataloged'.

So could me please assist me in solving the issue.

Thanks & regards,
Sailaja
Back to top  
expat



Joined: 14 Mar 2007
Posts: 3509
Location: Brussels once more ...

Posted: Mon Jul 14, 2008 5:06 pm    Post subject:  

Have you tried running with TRACE I to see exactly what is happeneing.

My code works perfectly.
Back to top  
sailaja.sn



Joined: 14 Jul 2008
Posts: 4
Location: Chennai

Posted: Mon Jul 14, 2008 5:37 pm    Post subject:  

I noticed that the alias files are created as VSAM files for the datasets having the higher qual as 'CFB1' eventhough the base dataset is a non VSAM ds. So I was not bale to view them at my env. Is there any other alternative way by which I can create alias datasets as non VSAM files.
Back to top  
expat



Joined: 14 Mar 2007
Posts: 3509
Location: Brussels once more ...

Posted: Mon Jul 14, 2008 5:40 pm    Post subject:  

My alias shows up as Code:
xx.JCL.SECOND                                       *ALIAS
when I use 3.4
Back to top  
Robert Sample



Joined: 06 Jun 2008
Posts: 891
Location: Atlanta, GA

Posted: Mon Jul 14, 2008 6:29 pm    Post subject:  

You can define an alias via IDCAMS in batch.

TSO HELP DEFALIAS indicates the syntax is ALIAS(NAME('name') and from what you've posted it's hard to tell if you've used single quotes or double quotes in your command. If double quotes were used, that would explain the user id prefix -- normally TSO will prefix a dataset name with your user id UNLESS you use single quotes around the name.

And depending on how your site is set up, you may be required to use a user catalog with the CATALOG option of the DEFINE ALIAS. If not used when needed, the alias may be defined in the wrong catalog and access attempts could fail when the high level qualifier's catalog is searched and the dataset not found.
Back to top  
 
       IBMMAINFRAMES.com - IBM Mainframe Support Forums Index -> TSO/ISPF
Page 1 of 1
THIS IS AN ARCIVE FORUM IN READ ONLY MODE. IF YOU WANT TO ASK YOUR DOUBTS USE THE ACTUAL FORUM