Ok,
1 ) I did deleted the alias pointing to the usercatalog.- RC-0 and Alias
did not appear in listcat against the NON-VSAM dataset.
2 ) Again I defined with same name relating to the Non Vsam Dataset - RC-0
3 ) Listcat against the NON-VSAM dataset shows me the Alias which I defined
in previous step.
4 ) Here Alias and NON-vsam are pointing towards the same Usercatalog.
5 ) All the required options are enabled under ISPF 3.4 browse option.
6 ) The usercatalog is very much connected to the correct master catalog.
7 ) Usercatalog is sitting on the SMS managed volume.
But not sure why the system isn't recognizing the alias which was defined.
On Wed, Aug 21, 2013 at 9:05 PM, Skip Robinson <jo.skip.robin...@sce.com>wrote:
> Sorry about that. NSCR is valid only for DEL NONVSAM. Not for alias. Leave
> out that operand. No ill consequences.
>
> .
> .
> JO.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 626-302-7535 Office
> 323-715-0595 Mobile
> jo.skip.robin...@sce.com
>
>
>
> From: mf db <dbajava...@gmail.com>
> To: IBM-MAIN@LISTSERV.UA.EDU,
> Date: 08/21/2013 08:26 AM
> Subject: Re: Deleting Alias
> Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
>
>
>
> The NOSCRATCH does not takes up :
>
> DEL xxxx.linklib ALIAS CATALOG(ICF.UCAT.CAT2) NOSCRATCH
>
> IDC3226I INCONSISTENT PARAMETERS INVOLVING 'NOSCRATCH'
>
>
> On Wed, Aug 21, 2013 at 8:41 PM, Skip Robinson
> <jo.skip.robin...@sce.com>wrote:
>
> > Catalog aliases (as opposed to PDS member aliases) have two different
> > uses.
> >
> > 1. By far the most common is high-level-qualifier such as TSO userid. In
> > this case, the alias itself lives in the master catalog and
> > points--RELATEs--to a user catalog that contains one or more actual DSNs
> > that all begin with the HLQ. To delete such an alias, you *must not*
> name
> > the user catalog in the command because user cat name is just part of
> the
> > entry you are deleting. You are deleting the alias (implicitly) from the
> > master catalog.
> >
> > DEL 'hlq' ALIAS
> >
> > 2. A less common usage but one we deploy to manage ServerPac data sets
> > relates a fully qualified DSN in a user catalog to a different name. For
> > example:
> >
> > 'OSR13.SYS1.LINKILIB' is defined in 'MVSR13.ICF.MASTER' as
> > pointing--RELATing--to 'SYS1.LINKLIB' on the SMPE target volume. In
> order
> > for this to work, there must still be an HLQ alias 'OSR13'
> > pointing--RELATing--to the user catalog as in (1). To delete the fully
> > qualified alias data set name from the user catalog, you must name the
> > user catalog because that's where the alias entry actually lives.
> >
> > DEL 'fully-qualified-name' ALIAS CAT('usercat-name') NOSCRATCH
> >
> > I threw in NOSCRATCH because otherwise your actual data set will
> > disappear. Unless that's what you want.
> >
> > 3. If you are getting 'duplicate name' when you try to redefine the
> alias,
> > then you did not actually delete the alias in the first place. That
> would
> > be the result of including user cat name in the command in (1) above.
> The
> > command would fail, and the alias would remain in the master catalog.
> >
> > .
> > .
> > JO.Skip Robinson
> > Southern California Edison Company
> > Electric Dragon Team Paddler
> > SHARE MVS Program Co-Manager
> > 626-302-7535 Office
> > 323-715-0595 Mobile
> > jo.skip.robin...@sce.com
> >
> >
> >
> > From: mf db <dbajava...@gmail.com>
> > To: IBM-MAIN@LISTSERV.UA.EDU,
> > Date: 08/21/2013 07:40 AM
> > Subject: Re: Deleting Alias
> > Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
> >
> >
> >
> > Elardus,
> >
> > I tried viewing via ISMF and I could see the alias entry pointing the
> same
> > usercatalog, but when I type Browse agains the alias I get a message as
> > "Dataset not catalogued"
> >
> >
> > On Wed, Aug 21, 2013 at 8:01 PM, Paul Gilmartin
> > <paulgboul...@aim.com>wrote:
> >
> > > On Wed, 21 Aug 2013 07:17:27 -0700, Lizette Koehler wrote:
> > > >
> > > >DEF TED.MY.FILE ALIAS RELATE(BOB.MY.FILE) then both BOB hlq and TED
> > hlq
> > > >must be in MYUCAT1
> > > >
> > > You can control which catalog the TED alias is created in, but if the
> > > catalogs are different you lose either way. If you create TED in
> > > BOB's catalog, catalog search fails to find TED; if you create TED
> > > in its proper catalog, catalog search fails to find BOB.
> > >
> > > >I may have that backwards, but it is close. Bottom line, the example
> > IBM
> > > >has in the book for doing this is very bad. I will be opening a
> request
> > > for
> > > >updating that to a more reasonable example. ...
> > > >
> > > Rather, that should be a Requirement that it be done right, not
> > > a RCF for documentation that it is done wrong.
> > >
> > > > ... Second, from the document it
> > > >appears that the HLQs should be in the same UCAT. At least that is
> my
> > > >understanding from reading the IBM doc (which is very nebulous at
> > best).
> > > >And I do not believe that you are required to use the CAT parameter
> in
> > the
> > > >DEF ... ALIAS RELATE(....) function
> > >
> > > -- gil
>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
