Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-05 Thread Sankaranarayanan, Vignesh 
That. Is. Excellent!

– Vignesh
Mainframe Infrastructure

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Dan D
Sent: Saturday 05-May-2018 20:31
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

A very long time ago (over 30 years ago) I worked for a service bureau.\ They 
had specific naming standards for their libraries when products were installed 
(ie. SYSx.product.V01R03.LOADLIB).

We couldn't have our customers continually changing JCL unless they wanted a 
different version than what was installed so we created a system tool called 
"Virtual Dataset Names".

This worked very similar to how ALIAS names works although there was no "must 
be in the same catalog" restriction.

When the system was IPL'd (or later via a special operator command) a table was 
loaded into CSA that contained the REAL dataset name, the VIRTUAL name and the 
various versions that were available.  One of the versions was marked as the 
default.
We used the IGG026DU catalog front-end exit (which I believe is now used by 
DFSMSHSM) to intercept catalog lookups and replace the REAL name that is being 
located with the VIRTUAL name.  It would scan SWA and check if an ACCT= was 
specified on the EXEC statement.  If so, the 1st operand was used to overriding 
VERION for all datasets within that step.
Example:
 //step50 exec pgm=iefbr15,ACCT=V5R3
 //DD1dd  dsn=sys1.sortlib,disp=shr
If SYS1.SORTLIB is in the table and it's virtual name is PROD.?.SORTLIB and it 
had a list of versions, V1R0 being the alias, DD1 would be translated to 
PROD.V5R3.SORTLIB as ACCT=V5R3 was specified.  If it wasn't DD1 would be 
PROD.V1R0.SORTLIB.

Our customers loved this as they could test NEW versions of products before 
they became the default.

If someone has the time, maybe they could take on this project and re-write 
this cool tool ;-)

Dan

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

MARKSANDSPENCER.COM

 Unless otherwise stated above:
Marks and Spencer plc
Registered Office:
Waterside House
35 North Wharf Road
London
W2 1NW

Registered No. 214436 in England and Wales.

Telephone (020) 7935 4422
Facsimile (020) 7487 2670

www.marksandspencer.com

Please note that electronic mail may be monitored.

This e-mail is confidential. If you received it by mistake, please let us know 
and then delete it from your system; you should not copy, disclose, or 
distribute its contents to anyone nor act in reliance on this e-mail, as this 
is prohibited and may be unlawful.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-04 Thread Seymour J Metz 
An alias entry in a PDS directory doesn't point to the base name, it points to 
the actual member. And, yes, I know about load modules, but what the link 
editor/binder puts in the user halfwords doesn't count.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of 
John McKown <john.archie.mck...@gmail.com>
Sent: Thursday, May 3, 2018 2:16 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

On Thu, May 3, 2018 at 1:06 PM, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:

> On Thu, 3 May 2018 15:22:22 +, Seymour J Metz wrote:
>
> >That was my point; if you need it at IPL time and it's cataloged in a
> user catalog, you need an explicit volume serial.
> >
> I'm (slowly) coming to grasp that.  At IPL time, the CAS is not
> initialized and
> user catalogs can not be searched.  So data sets needed during IPL must
> either
> be catalogued in the master cat or accessed by explicit volume serial.
>
> But in the case that impacted me many years ago, I wanted both the alias
> and
> the related DSN in different user cats.  I didn't need either during IPL
> (not my
> job) and in user cats they couldn't be accessed during IPL.  It still
> disconcerts me
> that after CAS initialization a user cat can't be searched for the alias
> and the HLQ
> of that alias could not identify a possibly different user cat to search
> for the
> related DSN.
>
> (Ih another case I would have found it useful to have an alias of an
> alias.  That,
> also, should be supported.)
>
> --gil
>
>
​This is disconcerting to me too. But I can envision what might be
happening. The logic to me would be something like:

1) Find catalog in which A.B.C exists according to the standard search order
2) Read entry for A.B.C in that catalog​.
3) If alias, find the base related-to entry in the catalog.

This reminds me a bit of BPAM. Suppose you have member A, but not B, in
PDS1. Now suppose you have B in PDS2 as an alias to A (in PDS2). If you ask
for member B then you get A in PDS2, not the PDS1 version. Granted, I don't
think that BPAM actually uses the A entry in PDS2 for anything when you
reference B, but I can easily be wrong. I'm speaking conceptually. The way
you & I want it to work is like a UNIX symlink (which can traverse to
another filesystem), but it is working more like a hard link (which cannot
span filesystems).


--
We all have skeletons in our closet.
Mine are so old, they have osteoporosis.

Maranatha! <><
John McKown

--
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

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-03 Thread John McKown 
On Thu, May 3, 2018 at 1:06 PM, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:

> On Thu, 3 May 2018 15:22:22 +, Seymour J Metz wrote:
>
> >That was my point; if you need it at IPL time and it's cataloged in a
> user catalog, you need an explicit volume serial.
> >
> I'm (slowly) coming to grasp that.  At IPL time, the CAS is not
> initialized and
> user catalogs can not be searched.  So data sets needed during IPL must
> either
> be catalogued in the master cat or accessed by explicit volume serial.
>
> But in the case that impacted me many years ago, I wanted both the alias
> and
> the related DSN in different user cats.  I didn't need either during IPL
> (not my
> job) and in user cats they couldn't be accessed during IPL.  It still
> disconcerts me
> that after CAS initialization a user cat can't be searched for the alias
> and the HLQ
> of that alias could not identify a possibly different user cat to search
> for the
> related DSN.
>
> (Ih another case I would have found it useful to have an alias of an
> alias.  That,
> also, should be supported.)
>
> --gil
>
>
​This is disconcerting to me too. But I can envision what might be
happening. The logic to me would be something like:

1) Find catalog in which A.B.C exists according to the standard search order
2) Read entry for A.B.C in that catalog​.
3) If alias, find the base related-to entry in the catalog.

This reminds me a bit of BPAM. Suppose you have member A, but not B, in
PDS1. Now suppose you have B in PDS2 as an alias to A (in PDS2). If you ask
for member B then you get A in PDS2, not the PDS1 version. Granted, I don't
think that BPAM actually uses the A entry in PDS2 for anything when you
reference B, but I can easily be wrong. I'm speaking conceptually. The way
you & I want it to work is like a UNIX symlink (which can traverse to
another filesystem), but it is working more like a hard link (which cannot
span filesystems).


-- 
We all have skeletons in our closet.
Mine are so old, they have osteoporosis.

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-03 Thread Paul Gilmartin 
On Thu, 3 May 2018 15:22:22 +, Seymour J Metz wrote:

>That was my point; if you need it at IPL time and it's cataloged in a user 
>catalog, you need an explicit volume serial.
> 
I'm (slowly) coming to grasp that.  At IPL time, the CAS is not initialized and
user catalogs can not be searched.  So data sets needed during IPL must either
be catalogued in the master cat or accessed by explicit volume serial.

But in the case that impacted me many years ago, I wanted both the alias and
the related DSN in different user cats.  I didn't need either during IPL (not my
job) and in user cats they couldn't be accessed during IPL.  It still 
disconcerts me
that after CAS initialization a user cat can't be searched for the alias and 
the HLQ
of that alias could not identify a possibly different user cat to search for the
related DSN.

(Ih another case I would have found it useful to have an alias of an alias.  
That,
also, should be supported.)

--gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-03 Thread Seymour J Metz 
That was my point; if you need it at IPL time and it's cataloged in a user 
catalog, you need an explicit volume serial.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of Tom 
Marchant <000a2a8c2020-dmarc-requ...@listserv.ua.edu>
Sent: Thursday, May 3, 2018 8:34 AM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

On Wed, 2 May 2018 16:14:28 +, Seymour J Metz wrote:

>>True, but the APF list entries include the volume serial on which the data
>> set resides, or they specify "SMS". In either case, the catalog entries are
>> not needed at IPL time, so APF listed data sets can be cataloged in a
>> user catalog.
>
>How do you build the DEB for the link list when LNKAUTH=APFTAB is specified if
>the volume serial is not specified and the data set is cataloged in a user 
>catalog?

If you have a link list containing data sets cataloged in a user catalog, and 
the
volume serial is not specified in the link list specification, that link list 
must have
been created after IPL when user catalogs are available.

--
Tom Marchant

--
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

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-03 Thread Tom Marchant 
On Wed, 2 May 2018 16:14:28 +, Seymour J Metz wrote:

>>True, but the APF list entries include the volume serial on which the data 
>> set resides, or they specify "SMS". In either case, the catalog entries are 
>> not needed at IPL time, so APF listed data sets can be cataloged in a 
>> user catalog.
>
>How do you build the DEB for the link list when LNKAUTH=APFTAB is specified if 
>the volume serial is not specified and the data set is cataloged in a user 
>catalog?

If you have a link list containing data sets cataloged in a user catalog, and 
the 
volume serial is not specified in the link list specification, that link list 
must have 
been created after IPL when user catalogs are available.

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-02 Thread Seymour J Metz 
>True, but the APF list entries include the volume serial on which the data 
> set resides, or they specify "SMS". In either case, the catalog entries are 
> not needed at IPL time, so APF listed data sets can be cataloged in a 
> user catalog.

How do you build the DEB for the link list when LNKAUTH=APFTAB is specified if 
the volume serial is not specified and the data set is cataloged in a user 
catalog?


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of Tom 
Marchant <000a2a8c2020-dmarc-requ...@listserv.ua.edu>
Sent: Wednesday, May 2, 2018 9:42 AM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

On Wed, 2 May 2018 08:14:43 +, Gibney, Dave wrote:

>Well, you can't (to the best of my knowledge) use things depending on
>user catalogs at the time that the IPL LPA or Linklst are built. And the
>name in the APF list has to be the real name on the volume.

True, but the APF list entries include the volume serial on which the data
set resides, or they specify "SMS". In either case, the catalog entries are
not needed at IPL time, so APF listed data sets can be cataloged in a
user catalog.

>I don't know the effect of STEPLIBing a job or STC via an non-VSAM
>alias to a dataset that is correctly APF authorized by it's real name.
>I think that should actually work.

It does.

>Playing post IPL games with SETPROG might get you what you want,
>but will be need additional attention maintaining the Commands and
>likely be more prone to error.

I wouldn't call it "games". I have created a new LNKLST set after IPL
and it works quite well. There is no reason the OP couldn't create a
PROGxx member that contains, for example,

LNKLST DEFINE NAME(ADD.USERCAT.DS) COPYFROM(CURRENT)
LNKLST ADD NAME(ADD.USERCAT.DS) DSNAME(B.LOAD)
LNKLST ACTIVATE NAME(ADD.USERCAT.DS)

and issue SET PROG=xx. From then on, any new address space
uses the new LNKLST set, and have the added library available.

I would expect that the system is up far enough for this to work
correctly at the time COMMNDxx members are processed, so
that the SET PROG=xx command can be in COMMNDxx. I don't
know if my expectation would be correct.

Note that as coded above, the ADD puts the data set at the
bottom of the LNKLST. You can put it somewhere else.

--
Tom Marchant

>
>> -Original Message-
>> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On
>> Behalf Of Sankaranarayanan, Vignesh
>> Sent: Tuesday, May 01, 2018 8:12 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias
>>
>> Hi Dave,
>>
>> I wouldn’t dare change the structuring at this point without fully
>> understanding why it is the way it is; which may very well be because of
>> something that happened twenty years ago.
>>
>> – Vignesh
>> Mainframe Infrastructure
>>
>> -Original Message-----
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
>> On Behalf Of Gibney, Dave
>> Sent: Wednesday 02-May-2018 03:00
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias
>>
>> I hate to add to the complexity. I don't like the OP's naming
>> plans/conventions at all.
>>
>> But, he can have what he wants. It is the IPL time linklst that isn't going 
>> to
>> have such fancy thigs and access to usercats available. He can IPL with a
>> minimal, perhaps even IBM only LPA/LINKLST/APF and then, once the
>> system is far enough up that that full catalog services are available, use
>> SETPROG to "enhance" these resources.
>>
>> I am not saying this is a good idea, although I have considered using this 
>> idea
>> in a more limited manner for a couple ISV's

--
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

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-02 Thread Tom Marchant 
On Wed, 2 May 2018 08:14:43 +, Gibney, Dave wrote:

>Well, you can't (to the best of my knowledge) use things depending on 
>user catalogs at the time that the IPL LPA or Linklst are built. And the 
>name in the APF list has to be the real name on the volume.

True, but the APF list entries include the volume serial on which the data 
set resides, or they specify "SMS". In either case, the catalog entries are 
not needed at IPL time, so APF listed data sets can be cataloged in a 
user catalog.

>I don't know the effect of STEPLIBing a job or STC via an non-VSAM 
>alias to a dataset that is correctly APF authorized by it's real name. 
>I think that should actually work.

It does.

>Playing post IPL games with SETPROG might get you what you want, 
>but will be need additional attention maintaining the Commands and 
>likely be more prone to error.

I wouldn't call it "games". I have created a new LNKLST set after IPL 
and it works quite well. There is no reason the OP couldn't create a 
PROGxx member that contains, for example,

LNKLST DEFINE NAME(ADD.USERCAT.DS) COPYFROM(CURRENT)
LNKLST ADD NAME(ADD.USERCAT.DS) DSNAME(B.LOAD)
LNKLST ACTIVATE NAME(ADD.USERCAT.DS)

and issue SET PROG=xx. From then on, any new address space 
uses the new LNKLST set, and have the added library available.

I would expect that the system is up far enough for this to work 
correctly at the time COMMNDxx members are processed, so 
that the SET PROG=xx command can be in COMMNDxx. I don't 
know if my expectation would be correct.

Note that as coded above, the ADD puts the data set at the 
bottom of the LNKLST. You can put it somewhere else.

-- 
Tom Marchant

>
>> -Original Message-
>> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On
>> Behalf Of Sankaranarayanan, Vignesh
>> Sent: Tuesday, May 01, 2018 8:12 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias
>> 
>> Hi Dave,
>> 
>> I wouldn’t dare change the structuring at this point without fully
>> understanding why it is the way it is; which may very well be because of
>> something that happened twenty years ago.
>> 
>> – Vignesh
>> Mainframe Infrastructure
>> 
>> -Original Message-
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
>> On Behalf Of Gibney, Dave
>> Sent: Wednesday 02-May-2018 03:00
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias
>> 
>> I hate to add to the complexity. I don't like the OP's naming
>> plans/conventions at all.
>> 
>> But, he can have what he wants. It is the IPL time linklst that isn't going 
>> to
>> have such fancy thigs and access to usercats available. He can IPL with a
>> minimal, perhaps even IBM only LPA/LINKLST/APF and then, once the
>> system is far enough up that that full catalog services are available, use
>> SETPROG to "enhance" these resources.
>> 
>> I am not saying this is a good idea, although I have considered using this 
>> idea
>> in a more limited manner for a couple ISV's

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-02 Thread John Eells 

Sankaranarayanan, Vignesh wrote:

Hi Dave,

I wouldn’t dare change the structuring at this point without fully 
understanding why it is the way it is; which may very well be because of 
something that happened twenty years ago.


For testing stuff like this, ZONECOPY can be your friend.  Make a copy 
of the zone.  Play with things like UCLIN, ZONEEDIT, etc. to your 
heart's content and see what happens.  But don't use the copy to 
actually install anything (that is, no APPLY or ACCEPT), since the 
intent is "play with it now, delete it afterward."  Right after the 
ZONECOPY, a ZONEEDIT to point the DDDEFs in to Outer Space before 
playing with things further is not a terrible idea, in fact.


--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-02 Thread Gibney, Dave 
Well, you can't (to the best of my knowledge) use things depending on user 
catalogs at the time that the IPL LPA or Linklst are built. And the name in the 
APF list has to be the real name on the volume.

I don't know the effect of STEPLIBing a job or STC via an non-VSAM alias to a 
dataset that is correctly APF authorized by it's real name. I think that should 
actually work.

Playing post IPL games with SETPROG might get you what you want, but will be 
need additional attention maintaining the Commands and likely be more prone to 
error.

> -Original Message-
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On
> Behalf Of Sankaranarayanan, Vignesh
> Sent: Tuesday, May 01, 2018 8:12 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias
> 
> Hi Dave,
> 
> I wouldn’t dare change the structuring at this point without fully
> understanding why it is the way it is; which may very well be because of
> something that happened twenty years ago.
> 
> – Vignesh
> Mainframe Infrastructure
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Gibney, Dave
> Sent: Wednesday 02-May-2018 03:00
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias
> 
> I hate to add to the complexity. I don't like the OP's naming
> plans/conventions at all.
> 
> But, he can have what he wants. It is the IPL time linklst that isn't going to
> have such fancy thigs and access to usercats available. He can IPL with a
> minimal, perhaps even IBM only LPA/LINKLST/APF and then, once the
> system is far enough up that that full catalog services are available, use
> SETPROG to "enhance" these resources.
> 
> I am not saying this is a good idea, although I have considered using this 
> idea
> in a more limited manner for a couple ISV's
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-
> m...@listserv.ua.edu]
> > On Behalf Of Tom Marchant
> > Sent: Tuesday, May 01, 2018 12:47 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias
> >
> > On Tue, 1 May 2018 10:37:37 -0500, Paul Gilmartin
> > <paulgboul...@aim.com> wrote:
> >
> > >On Tue, 1 May 2018 08:22:08 +0300, Alan(GMAIL)Watthey wrote:
> > >>
> > >>However, with a bit of extra work you can use SYMBOLICRELATE type
> > >>alias
> > >instead and that is allowed to go in a different catalog (see OA52218).  
> > >...
> > >>
> > >And to this end catalog should support specifying SYMBOLICRELATE with
> > >no need to have an actual substitutable symbol in the alias name.
> > >That would eliminate the need for (some of) the extra work.
> >
> > Not for the OP's problem. He wants to define most of his data sets in
> > a Usercat, but those that are in LNKLST, he wants to define in the
> > Master Catalog. He could create an alias in the master using
> > SYMBOLICRELATE, but he cannot include that alias in the LNKLST.
> >
> > --
> > Tom Marchant
> >
> > --
> > 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
> 
> MARKSANDSPENCER.COM
> 
>  Unless otherwise stated above:
> Marks and Spencer plc
> Registered Office:
> Waterside House
> 35 North Wharf Road
> London
> W2 1NW
> 
> Registered No. 214436 in England and Wales.
> 
> Telephone (020) 7935 4422
> Facsimile (020) 7487 2670
> 
> www.marksandspencer.com
> 
> Please note that electronic mail may be monitored.
> 
> This e-mail is confidential. If you received it by mistake, please let us know
> and then delete it from your system; you should not copy, disclose, or
> distribute its contents to anyone nor act in reliance on this e-mail, as this 
> is
> prohibited and may be unlawful.
> 
> --
> 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

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-01 Thread Sankaranarayanan, Vignesh 
Hi Dave,

I wouldn’t dare change the structuring at this point without fully 
understanding why it is the way it is; which may very well be because of 
something that happened twenty years ago.

– Vignesh
Mainframe Infrastructure

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Gibney, Dave
Sent: Wednesday 02-May-2018 03:00
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

I hate to add to the complexity. I don't like the OP's naming plans/conventions 
at all.

But, he can have what he wants. It is the IPL time linklst that isn't going to 
have such fancy thigs and access to usercats available. He can IPL with a 
minimal, perhaps even IBM only LPA/LINKLST/APF and then, once the system is far 
enough up that that full catalog services are available, use SETPROG to 
"enhance" these resources.

I am not saying this is a good idea, although I have considered using this idea 
in a more limited manner for a couple ISV's

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Tom Marchant
> Sent: Tuesday, May 01, 2018 12:47 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias
>
> On Tue, 1 May 2018 10:37:37 -0500, Paul Gilmartin
> <paulgboul...@aim.com> wrote:
>
> >On Tue, 1 May 2018 08:22:08 +0300, Alan(GMAIL)Watthey wrote:
> >>
> >>However, with a bit of extra work you can use SYMBOLICRELATE type
> >>alias
> >instead and that is allowed to go in a different catalog (see OA52218).  ...
> >>
> >And to this end catalog should support specifying SYMBOLICRELATE with
> >no need to have an actual substitutable symbol in the alias name.
> >That would eliminate the need for (some of) the extra work.
>
> Not for the OP's problem. He wants to define most of his data sets in
> a Usercat, but those that are in LNKLST, he wants to define in the
> Master Catalog. He could create an alias in the master using
> SYMBOLICRELATE, but he cannot include that alias in the LNKLST.
>
> --
> Tom Marchant
>
> --
> 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

MARKSANDSPENCER.COM

 Unless otherwise stated above:
Marks and Spencer plc
Registered Office:
Waterside House
35 North Wharf Road
London
W2 1NW

Registered No. 214436 in England and Wales.

Telephone (020) 7935 4422
Facsimile (020) 7487 2670

www.marksandspencer.com

Please note that electronic mail may be monitored.

This e-mail is confidential. If you received it by mistake, please let us know 
and then delete it from your system; you should not copy, disclose, or 
distribute its contents to anyone nor act in reliance on this e-mail, as this 
is prohibited and may be unlawful.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-01 Thread Gibney, Dave 
I hate to add to the complexity. I don't like the OP's naming plans/conventions 
at all.

But, he can have what he wants. It is the IPL time linklst that isn't going to 
have such fancy thigs and access to usercats available. He can IPL with a 
minimal, perhaps even IBM only LPA/LINKLST/APF and then, once the system is far 
enough up that that full catalog services are available, use SETPROG to 
"enhance" these resources.

I am not saying this is a good idea, although I have considered using this idea 
in a more limited manner for a couple ISV's

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Tom Marchant
> Sent: Tuesday, May 01, 2018 12:47 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias
> 
> On Tue, 1 May 2018 10:37:37 -0500, Paul Gilmartin
> <paulgboul...@aim.com> wrote:
> 
> >On Tue, 1 May 2018 08:22:08 +0300, Alan(GMAIL)Watthey wrote:
> >>
> >>However, with a bit of extra work you can use SYMBOLICRELATE type
> >>alias
> >instead and that is allowed to go in a different catalog (see OA52218).  ...
> >>
> >And to this end catalog should support specifying SYMBOLICRELATE with
> >no need to have an actual substitutable symbol in the alias name.  That
> >would eliminate the need for (some of) the extra work.
> 
> Not for the OP's problem. He wants to define most of his data sets in a
> Usercat, but those that are in LNKLST, he wants to define in the Master
> Catalog. He could create an alias in the master using SYMBOLICRELATE, but he
> cannot include that alias in the LNKLST.
> 
> --
> Tom Marchant
> 
> --
> 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

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-01 Thread John McKown 
On Tue, May 1, 2018 at 2:47 PM, Tom Marchant <
000a2a8c2020-dmarc-requ...@listserv.ua.edu> wrote:

> On Tue, 1 May 2018 10:37:37 -0500, Paul Gilmartin 
> wrote:
>
> >On Tue, 1 May 2018 08:22:08 +0300, Alan(GMAIL)Watthey wrote:
> >>
> >>However, with a bit of extra work you can use SYMBOLICRELATE type alias
> >instead and that is allowed to go in a different catalog (see OA52218).
> ...
> >>
> >And to this end catalog should support specifying SYMBOLICRELATE with no
> >need to have an actual substitutable symbol in the alias name.  That would
> >eliminate the need for (some of) the extra work.
>
> Not for the OP's problem. He wants to define most of his data sets in a
> Usercat,
> but those that are in LNKLST, he wants to define in the Master Catalog. He
> could create an alias in the master using SYMBOLICRELATE, but he cannot
> include that alias in the LNKLST.
>

​Hum, now you _can_ do that -- have a DSN on the LNKLST in a UCAT without
specifying the VOLSER in the PROGnn member. But __ONLY IF__ you do a
SETPROG after IPL which creates a new LNKLST to be used by address spaces
which start _after_ the SETPROG is done. This does not help with LPA
modules or with modules which need to be available (perhaps via IEFSSN)
earlier in the IPL.​



>
> --
> Tom Marchant
>
>

-- 
We all have skeletons in our closet.
Mine are so old, they have osteoporosis.

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-01 Thread Tom Marchant 
On Tue, 1 May 2018 10:37:37 -0500, Paul Gilmartin  wrote:

>On Tue, 1 May 2018 08:22:08 +0300, Alan(GMAIL)Watthey wrote:
>>
>>However, with a bit of extra work you can use SYMBOLICRELATE type alias 
>instead and that is allowed to go in a different catalog (see OA52218).  ...
>>
>And to this end catalog should support specifying SYMBOLICRELATE with no
>need to have an actual substitutable symbol in the alias name.  That would
>eliminate the need for (some of) the extra work.

Not for the OP's problem. He wants to define most of his data sets in a 
Usercat, 
but those that are in LNKLST, he wants to define in the Master Catalog. He 
could create an alias in the master using SYMBOLICRELATE, but he cannot 
include that alias in the LNKLST.

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-01 Thread Paul Gilmartin 
On Tue, 1 May 2018 12:20:10 +, Sankaranarayanan, Vignesh wrote:

>.. and just stop doing everything until they deliver?
> 
Better late than never.  Or think of it as your gift to future generations of 
systems programmers.
But Walt's remarks were discouraging.

On Tue, 1 May 2018 08:22:08 +0300, Alan(GMAIL)Watthey wrote:
>
>However, with a bit of extra work you can use SYMBOLICRELATE type alias 
>instead and that is allowed to go in a different catalog (see OA52218).  ...
>
And to this end catalog should support specifying SYMBOLICRELATE with no
need to have an actual substitutable symbol in the alias name.  That would
eliminate the need for (some of) the extra work.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-01 Thread Seymour J Metz 
Of course, you can use static system symbols in the volume serial numbers.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of 
Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
Sent: Monday, April 30, 2018 10:50 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

On Tue, 1 May 2018 02:24:55 +, Feller, Paul wrote:

>"A.**" and "B.**" can be in the same catalog.  The datasets that are in the 
>linklst or lpalist do not have to be in the master catalog.  You can use 
>VOLSER to point to the datasets.
>
One purpose of a catalog is to avoid the need to specify VOLSERs.
The design fails that purpose.

One purpose of aliases is to be able to use arbitrary alternate names
for data sets.  The design fails that purpose.

-- 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

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-01 Thread Tom Marchant 
On Tue, 1 May 2018 12:20:10 +, Sankaranarayanan, Vignesh wrote:

>.. and just stop doing everything until they deliver?

Of course not. You have to do what you have to do. But you cannot do what 
you want to do. Some choices are:

Give the vendor "B" for the HLQ and edit the JCL that they create, or rename 
the data set later. DDDEFs will need to be changed if it is maintained by SMP/E.

Specify the VOLSER for LNKLST. That wouldn't be my first choice.

-- 
Tom Marchant

>
>-Original Message-
>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
>Behalf Of Tom Marchant
>
>Contact the vendor and submit a requirement.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-01 Thread Sankaranarayanan, Vignesh 
.. and just stop doing everything until they deliver?

– Vignesh
Mainframe Infrastructure

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: 01 May 2018 12:38
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

On Tue, 1 May 2018 01:55:05 +, Sankaranarayanan, Vignesh wrote:

>What am I trying to do?
>Let's say a product installation/customisation allows only for 1 HLQ,
>so I choose B for it because
>A.** is used to host datasets that need to be LNK/LPAd.
>B.** is used to host datasets that need to be APFd or nothing at all (just 
>run-time).
>
>A.** goes direct to the MCAT and B.** goes to a CATALOG.B.UCAT

Contact the vendor and submit a requirement.

--
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

MARKSANDSPENCER.COM

 Unless otherwise stated above:
Marks and Spencer plc
Registered Office:
Waterside House
35 North Wharf Road
London
W2 1NW

Registered No. 214436 in England and Wales.

Telephone (020) 7935 4422
Facsimile (020) 7487 2670

www.marksandspencer.com

Please note that electronic mail may be monitored.

This e-mail is confidential. If you received it by mistake, please let us know 
and then delete it from your system; you should not copy, disclose, or 
distribute its contents to anyone nor act in reliance on this e-mail, as this 
is prohibited and may be unlawful.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-05-01 Thread Tom Marchant 
On Tue, 1 May 2018 01:55:05 +, Sankaranarayanan, Vignesh wrote:

>What am I trying to do?
>Let's say a product installation/customisation allows only for 1 HLQ, so I 
>choose B for it because
>A.** is used to host datasets that need to be LNK/LPAd.
>B.** is used to host datasets that need to be APFd or nothing at all (just 
>run-time).
>
>A.** goes direct to the MCAT and B.** goes to a CATALOG.B.UCAT

Contact the vendor and submit a requirement.

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-04-30 Thread Sankaranarayanan, Vignesh 
Hi Paul,

I know, it's just a site practice I guess.

- Vignesh
Mainframe Infrastructure

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Feller, Paul
Sent: Tuesday 01-May-2018 07:55
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

"A.**" and "B.**" can be in the same catalog.  The datasets that are in the 
linklst or lpalist do not have to be in the master catalog.  You can use VOLSER 
to point to the datasets.

LPALIST could look like this.
A.B.C.SOFTWARE(VOLSR1)
A.B.D.SOFTWARE(VOLSR2)

LINKLST could look like this.
LNKLST ADD  NAME(PROGPL)   DSN(A.C.D.SOFTWARE)
   VOLUME(VOLSR3)
LNKLST ADD  NAME(PROGPL)   DSN(A.C.E.SOFTWARE)
   VOLUME(VOLSR4)


Thanks..

Paul Feller
AGT Mainframe Technical Support
paul.fel...@transamerica.com
Work: (319)-355-7824
Cell: (319)-573-4821

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Sankaranarayanan, Vignesh
Sent: Monday, April 30, 2018 20:55
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

What am I trying to do?
Let's say a product installation/customisation allows only for 1 HLQ, so I 
choose B for it because
A.** is used to host datasets that need to be LNK/LPAd.
B.** is used to host datasets that need to be APFd or nothing at all (just 
run-time).

A.** goes direct to the MCAT and B.** goes to a CATALOG.B.UCAT

Because I mentioned the 1 HLQ in product customisation, I need to make sure 
that if the files are looked for in B.**, the A.** files need to be reachable 
via their alises in B.**.

Makes sense?

- Vignesh
Mainframe Infrastructure

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Monday 30-Apr-2018 23:27
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

It is best to keep everything in the same UCAT. Makes for a happy system

Could you explain what you are trying to do?

I have used SYMBLICREALTES and SYSTEM SYMBOLS to add things like release levels 
in datasets, without the user having to change the JCL

For example.  A.R111.B.C  would be related to A.B.C  which the end user always 
uses  and the R111 could be a system symbol that could be dynamically changed 
as need.


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On 
> Behalf Of Sankaranarayanan, Vignesh
> Sent: Monday, April 30, 2018 9:35 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: IEFA107I when pointing to dataset alias
>
> Hello All,
>
> Let's say I have A.DATA.SET in APF and LNK.
> I then create B.DATA.SET as an alias to A.DATA.SET
>
> NONVSAM --- A.DATA.SET
>  IN-CAT --- CATALOG.MASTER.CAT
>  HISTORY
>DATASET-OWNER-(NULL) CREATION2018.120
>RELEASE2 EXPIRATION--.000
>  VOLUMES
>VOLSERVOL001 DEVTYPE--X'3010200F' FSEQN---
> ---0
>  ASSOCIATIONS
>ALIASB.DATA.SET
>  ATTRIBUTES
>
> ALIAS - B.DATA.SET
>  IN-CAT --- CATALOG.MASTER.CAT
>  HISTORY
>RELEASE2 CREATION2018.120
>  ASSOCIATIONS
>NONVSAM-A.DATA.SET
>
>
> But when I refer to B.DATA.SET in //SYSLIB in an assemble job, I get
> --> IEFA107I JOBNAME STEPNAME SYSLIB - DATA SET B.DATA.SET NOT FOUND
>
> What gives.. ?
>
> - Vignesh
> Mainframe Infrastructure
>
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

MARKSANDSPENCER.COM

 Unless otherwise stated above:
Marks and Spencer plc
Registered Office:
Waterside House
35 North Wharf Road
London
W2 1NW

Registered No. 214436 in England and Wales.

Telephone (020) 7935 4422
Facsimile (020) 7487 2670

www.marksandspencer.com

Please note that electronic mail may be monitored.

This e-mail is confidential. If you received it by mistake, please let us know 
and then delete it from your system; you should not copy, disclose, or 
distribute its contents to anyone nor act in reliance on this e-mail, as this 
is prohibited and may be unlawful.

--
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

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-04-30 Thread Paul Gilmartin 
On Tue, 1 May 2018 02:24:55 +, Feller, Paul wrote:

>"A.**" and "B.**" can be in the same catalog.  The datasets that are in the 
>linklst or lpalist do not have to be in the master catalog.  You can use 
>VOLSER to point to the datasets.
>
One purpose of a catalog is to avoid the need to specify VOLSERs.
The design fails that purpose.

One purpose of aliases is to be able to use arbitrary alternate names
for data sets.  The design fails that purpose.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-04-30 Thread van der Grijn, Bart (B) 
If you can, I would recommend putting everything under B (put it in a ucat), 
limit your install libraries to your  or similar volumes and use system 
symbols for you PROGxx entries. 
Except for SYS1 all our load libraries are in ucats. All LNK or LPA libraries 
are on  and every single entry in PROGxx has VOLUME() coded (and 
every entry ins LPALSTxx has  coded as the volser)

Bart

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Sankaranarayanan, Vignesh
Sent: Monday, April 30, 2018 9:55 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

This email originated from outside of the organization.


What am I trying to do?
Let's say a product installation/customisation allows only for 1 HLQ, so I 
choose B for it because
A.** is used to host datasets that need to be LNK/LPAd.
B.** is used to host datasets that need to be APFd or nothing at all (just 
run-time).

A.** goes direct to the MCAT and B.** goes to a CATALOG.B.UCAT

Because I mentioned the 1 HLQ in product customisation, I need to make sure 
that if the files are looked for in B.**, the A.** files need to be reachable 
via their alises in B.**.

Makes sense?

- Vignesh
Mainframe Infrastructure

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Monday 30-Apr-2018 23:27
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

It is best to keep everything in the same UCAT. Makes for a happy system

Could you explain what you are trying to do?

I have used SYMBLICREALTES and SYSTEM SYMBOLS to add things like release levels 
in datasets, without the user having to change the JCL

For example.  A.R111.B.C  would be related to A.B.C  which the end user always 
uses  and the R111 could be a system symbol that could be dynamically changed 
as need.


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On
> Behalf Of Sankaranarayanan, Vignesh
> Sent: Monday, April 30, 2018 9:35 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: IEFA107I when pointing to dataset alias
>
> Hello All,
>
> Let's say I have A.DATA.SET in APF and LNK.
> I then create B.DATA.SET as an alias to A.DATA.SET
>
> NONVSAM --- A.DATA.SET
>  IN-CAT --- CATALOG.MASTER.CAT
>  HISTORY
>DATASET-OWNER-(NULL) CREATION2018.120
>RELEASE2 EXPIRATION--.000
>  VOLUMES
>VOLSERVOL001 DEVTYPE--X'3010200F' FSEQN---
> ---0
>  ASSOCIATIONS
>ALIASB.DATA.SET
>  ATTRIBUTES
>
> ALIAS - B.DATA.SET
>  IN-CAT --- CATALOG.MASTER.CAT
>  HISTORY
>RELEASE2 CREATION2018.120
>  ASSOCIATIONS
>NONVSAM-A.DATA.SET
>
>
> But when I refer to B.DATA.SET in //SYSLIB in an assemble job, I get
> --> IEFA107I JOBNAME STEPNAME SYSLIB - DATA SET B.DATA.SET NOT FOUND
>
> What gives.. ?
>
> - Vignesh
> Mainframe Infrastructure
>
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-04-30 Thread Feller, Paul 
"A.**" and "B.**" can be in the same catalog.  The datasets that are in the 
linklst or lpalist do not have to be in the master catalog.  You can use VOLSER 
to point to the datasets.

LPALIST could look like this.
A.B.C.SOFTWARE(VOLSR1)
A.B.D.SOFTWARE(VOLSR2)

LINKLST could look like this.
LNKLST ADD  NAME(PROGPL)   DSN(A.C.D.SOFTWARE)
   VOLUME(VOLSR3)
LNKLST ADD  NAME(PROGPL)   DSN(A.C.E.SOFTWARE)
   VOLUME(VOLSR4)


Thanks..

Paul Feller
AGT Mainframe Technical Support
paul.fel...@transamerica.com
Work: (319)-355-7824
Cell: (319)-573-4821

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Sankaranarayanan, Vignesh
Sent: Monday, April 30, 2018 20:55
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

What am I trying to do?
Let's say a product installation/customisation allows only for 1 HLQ, so I 
choose B for it because
A.** is used to host datasets that need to be LNK/LPAd.
B.** is used to host datasets that need to be APFd or nothing at all (just 
run-time).

A.** goes direct to the MCAT and B.** goes to a CATALOG.B.UCAT

Because I mentioned the 1 HLQ in product customisation, I need to make sure 
that if the files are looked for in B.**, the A.** files need to be reachable 
via their alises in B.**.

Makes sense?

- Vignesh
Mainframe Infrastructure

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Monday 30-Apr-2018 23:27
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

It is best to keep everything in the same UCAT. Makes for a happy system

Could you explain what you are trying to do?

I have used SYMBLICREALTES and SYSTEM SYMBOLS to add things like release levels 
in datasets, without the user having to change the JCL

For example.  A.R111.B.C  would be related to A.B.C  which the end user always 
uses  and the R111 could be a system symbol that could be dynamically changed 
as need.


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On 
> Behalf Of Sankaranarayanan, Vignesh
> Sent: Monday, April 30, 2018 9:35 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: IEFA107I when pointing to dataset alias
>
> Hello All,
>
> Let's say I have A.DATA.SET in APF and LNK.
> I then create B.DATA.SET as an alias to A.DATA.SET
>
> NONVSAM --- A.DATA.SET
>  IN-CAT --- CATALOG.MASTER.CAT
>  HISTORY
>DATASET-OWNER-(NULL) CREATION2018.120
>RELEASE2 EXPIRATION--.000
>  VOLUMES
>VOLSERVOL001 DEVTYPE--X'3010200F' FSEQN---
> ---0
>  ASSOCIATIONS
>ALIASB.DATA.SET
>  ATTRIBUTES
>
> ALIAS - B.DATA.SET
>  IN-CAT --- CATALOG.MASTER.CAT
>  HISTORY
>RELEASE2 CREATION2018.120
>  ASSOCIATIONS
>NONVSAM-A.DATA.SET
>
>
> But when I refer to B.DATA.SET in //SYSLIB in an assemble job, I get
> --> IEFA107I JOBNAME STEPNAME SYSLIB - DATA SET B.DATA.SET NOT FOUND
>
> What gives.. ?
>
> - Vignesh
> Mainframe Infrastructure
>
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

MARKSANDSPENCER.COM

 Unless otherwise stated above:
Marks and Spencer plc
Registered Office:
Waterside House
35 North Wharf Road
London
W2 1NW

Registered No. 214436 in England and Wales.

Telephone (020) 7935 4422
Facsimile (020) 7487 2670

www.marksandspencer.com

Please note that electronic mail may be monitored.

This e-mail is confidential. If you received it by mistake, please let us know 
and then delete it from your system; you should not copy, disclose, or 
distribute its contents to anyone nor act in reliance on this e-mail, as this 
is prohibited and may be unlawful.

--
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

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-04-30 Thread Sankaranarayanan, Vignesh 
I already tried this.

Say B.** goes to CATALOG.B.UCAT, I already tried DEFINE ALIAS B.DATA.SET 
RELATE(A.DATA.SET) CATALOG(CATALOG.B.UCAT), I got an error.
This was weeks ago, so I just used the DEFALIAS without the CATALOG keyword.

– Vignesh
Mainframe Infrastructure

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Tuesday 01-May-2018 00:16
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

On Mon, 30 Apr 2018 10:57:21 -0700, Lizette Koehler wrote:

>It is best to keep everything in the same UCAT. Makes for a happy
>system
>
IBM should emphasize happy customers above happy systems.

If the OP had created B.DATA.SET, listed it and noted the catalog then deleted 
it and created the alias in that catalog, RELATEd to A.DATA.SET, would it have 
worked cleanly?

>> -Original Message-
>> From: IBM Mainframe Discussion List Sankaranarayanan, Vignesh
>> Sent: Monday, April 30, 2018 9:35 AM
>>
>> NONVSAM --- A.DATA.SET
>>  IN-CAT --- CATALOG.MASTER.CAT
>>  HISTORY
>>DATASET-OWNER-(NULL) CREATION2018.120
>>RELEASE2 EXPIRATION--.000
>>  VOLUMES
>>VOLSERVOL001 DEVTYPE--X'3010200F' FSEQN---
>> ---0
>>  ASSOCIATIONS
>>ALIASB.DATA.SET
>>  ATTRIBUTES
>>
>> ALIAS - B.DATA.SET
>>  IN-CAT --- CATALOG.MASTER.CAT
>>  HISTORY
>>RELEASE2 CREATION2018.120
>>  ASSOCIATIONS
>>NONVSAM-A.DATA.SET
>>
>>
>> But when I refer to B.DATA.SET in //SYSLIB in an assemble job, I get
>> --> IEFA107I JOBNAME STEPNAME SYSLIB - DATA SET B.DATA.SET NOT FOUND

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

MARKSANDSPENCER.COM

 Unless otherwise stated above:
Marks and Spencer plc
Registered Office:
Waterside House
35 North Wharf Road
London
W2 1NW

Registered No. 214436 in England and Wales.

Telephone (020) 7935 4422
Facsimile (020) 7487 2670

www.marksandspencer.com

Please note that electronic mail may be monitored.

This e-mail is confidential. If you received it by mistake, please let us know 
and then delete it from your system; you should not copy, disclose, or 
distribute its contents to anyone nor act in reliance on this e-mail, as this 
is prohibited and may be unlawful.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-04-30 Thread Sankaranarayanan, Vignesh 
What am I trying to do?
Let's say a product installation/customisation allows only for 1 HLQ, so I 
choose B for it because
A.** is used to host datasets that need to be LNK/LPAd.
B.** is used to host datasets that need to be APFd or nothing at all (just 
run-time).

A.** goes direct to the MCAT and B.** goes to a CATALOG.B.UCAT

Because I mentioned the 1 HLQ in product customisation, I need to make sure 
that if the files are looked for in B.**, the A.** files need to be reachable 
via their alises in B.**.

Makes sense?

- Vignesh
Mainframe Infrastructure

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Monday 30-Apr-2018 23:27
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

It is best to keep everything in the same UCAT. Makes for a happy system

Could you explain what you are trying to do?

I have used SYMBLICREALTES and SYSTEM SYMBOLS to add things like release levels 
in datasets, without the user having to change the JCL

For example.  A.R111.B.C  would be related to A.B.C  which the end user always 
uses  and the R111 could be a system symbol that could be dynamically changed 
as need.


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On
> Behalf Of Sankaranarayanan, Vignesh
> Sent: Monday, April 30, 2018 9:35 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: IEFA107I when pointing to dataset alias
>
> Hello All,
>
> Let's say I have A.DATA.SET in APF and LNK.
> I then create B.DATA.SET as an alias to A.DATA.SET
>
> NONVSAM --- A.DATA.SET
>  IN-CAT --- CATALOG.MASTER.CAT
>  HISTORY
>DATASET-OWNER-(NULL) CREATION2018.120
>RELEASE2 EXPIRATION--.000
>  VOLUMES
>VOLSERVOL001 DEVTYPE--X'3010200F' FSEQN---
> ---0
>  ASSOCIATIONS
>ALIASB.DATA.SET
>  ATTRIBUTES
>
> ALIAS - B.DATA.SET
>  IN-CAT --- CATALOG.MASTER.CAT
>  HISTORY
>RELEASE2 CREATION2018.120
>  ASSOCIATIONS
>NONVSAM-A.DATA.SET
>
>
> But when I refer to B.DATA.SET in //SYSLIB in an assemble job, I get
> --> IEFA107I JOBNAME STEPNAME SYSLIB - DATA SET B.DATA.SET NOT FOUND
>
> What gives.. ?
>
> - Vignesh
> Mainframe Infrastructure
>
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

MARKSANDSPENCER.COM

 Unless otherwise stated above:
Marks and Spencer plc
Registered Office:
Waterside House
35 North Wharf Road
London
W2 1NW

Registered No. 214436 in England and Wales.

Telephone (020) 7935 4422
Facsimile (020) 7487 2670

www.marksandspencer.com

Please note that electronic mail may be monitored.

This e-mail is confidential. If you received it by mistake, please let us know 
and then delete it from your system; you should not copy, disclose, or 
distribute its contents to anyone nor act in reliance on this e-mail, as this 
is prohibited and may be unlawful.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-04-30 Thread John McKown 
On Mon, Apr 30, 2018 at 12:02 PM, Sankaranarayanan, Vignesh <
vignesh.v.sankaranaraya...@marks-and-spencer.com> wrote:

> RCF time?
>
> – Vignesh
> Mainframe Infrastructure
>
>
​Reader Comment Form -- how to report a perceived error in an IBM manual.​
And I gotta watch out because RCF != RFC. RFC is "Request For Comment";
which is the way that IEEE documents internet protocols and other
documentation.

-- 
We all have skeletons in our closet.
Mine are so old, they have osteoporosis.

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-04-30 Thread Sankaranarayanan, Vignesh 
RCF time?

– Vignesh
Mainframe Infrastructure

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John McKown
Sent: Monday 30-Apr-2018 22:29
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

On Mon, Apr 30, 2018 at 11:52 AM, David W Noon < 
013a910fd252-dmarc-requ...@listserv.ua.edu> wrote:

> On Mon, 30 Apr 2018 16:34:43 +, Sankaranarayanan, Vignesh
> (vignesh.v.sankaranaraya...@marks-and-spencer.com) wrote about
> "IEFA107I when pointing to dataset alias" (in
> <DB3PR02MB038035CC3845AB536C629CF7DA820@DB3PR02MB0380.
> eurprd02.prod.outlook.com>):
>
> > Let's say I have A.DATA.SET in APF and LNK.
> > I then create B.DATA.SET as an alias to A.DATA.SET
>
> Are the A and B HLQs aliased to the same catalogue?
>
> The alias will be in the catalogue for A, and if DSN lookups for B.*
> don't go to the same catalogue then the lookup for your alias will not
> be found.
> --
> Regards,
>
>
​RCF time, I guess. I tested and you are correct (of course). But the manual 
does not say anything about the ALIAS name being required to be in the same 
catalog as the base name.​

--
We all have skeletons in our closet.
Mine are so old, they have osteoporosis.

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

MARKSANDSPENCER.COM

 Unless otherwise stated above:
Marks and Spencer plc
Registered Office:
Waterside House
35 North Wharf Road
London
W2 1NW

Registered No. 214436 in England and Wales.

Telephone (020) 7935 4422
Facsimile (020) 7487 2670

www.marksandspencer.com

Please note that electronic mail may be monitored.

This e-mail is confidential. If you received it by mistake, please let us know 
and then delete it from your system; you should not copy, disclose, or 
distribute its contents to anyone nor act in reliance on this e-mail, as this 
is prohibited and may be unlawful.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-04-30 Thread Sankaranarayanan, Vignesh 
Usually, A goes to the mastercat, B goes to a usercat.
But when I define B.DATA.SET as an alias to A.DATA.SET when specifying 
RELATE(B's UCAT), it doesn't work.

– Vignesh
Mainframe Infrastructure

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of David W Noon
Sent: Monday 30-Apr-2018 22:23
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

On Mon, 30 Apr 2018 16:34:43 +, Sankaranarayanan, Vignesh
(vignesh.v.sankaranaraya...@marks-and-spencer.com) wrote about "IEFA107I when 
pointing to dataset alias" (in
<db3pr02mb038035cc3845ab536c629cf7da...@db3pr02mb0380.eurprd02.prod.outlook.com>):

> Let's say I have A.DATA.SET in APF and LNK.
> I then create B.DATA.SET as an alias to A.DATA.SET

Are the A and B HLQs aliased to the same catalogue?

The alias will be in the catalogue for A, and if DSN lookups for B.* don't go 
to the same catalogue then the lookup for your alias will not be found.
--
Regards,

Dave  [RLU #314465]
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
david.w.n...@googlemail.com (David W Noon)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*



--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

MARKSANDSPENCER.COM

 Unless otherwise stated above:
Marks and Spencer plc
Registered Office:
Waterside House
35 North Wharf Road
London
W2 1NW

Registered No. 214436 in England and Wales.

Telephone (020) 7935 4422
Facsimile (020) 7487 2670

www.marksandspencer.com

Please note that electronic mail may be monitored.

This e-mail is confidential. If you received it by mistake, please let us know 
and then delete it from your system; you should not copy, disclose, or 
distribute its contents to anyone nor act in reliance on this e-mail, as this 
is prohibited and may be unlawful.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

2018-04-30 Thread Sankaranarayanan, Vignesh 
Hi Mike,

It's on an isolated system; no plex involved.

– Vignesh
Mainframe Infrastructure

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Michael Babcock
Sent: Monday 30-Apr-2018 22:19
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: IEFA107I when pointing to dataset alias

If the job is running in a plex, make sure the job gets run on the system where 
the alias is defined.

On Mon, Apr 30, 2018 at 11:35 AM Sankaranarayanan, Vignesh < 
vignesh.v.sankaranaraya...@marks-and-spencer.com> wrote:

> Hello All,
>
> Let's say I have A.DATA.SET in APF and LNK.
> I then create B.DATA.SET as an alias to A.DATA.SET
>
> NONVSAM --- A.DATA.SET
>  IN-CAT --- CATALOG.MASTER.CAT
>  HISTORY
>DATASET-OWNER-(NULL) CREATION2018.120
>RELEASE2 EXPIRATION--.000
>  VOLUMES
>VOLSERVOL001 DEVTYPE--X'3010200F'
>  FSEQN--0
>  ASSOCIATIONS
>ALIASB.DATA.SET
>  ATTRIBUTES
>
> ALIAS - B.DATA.SET
>  IN-CAT --- CATALOG.MASTER.CAT
>  HISTORY
>RELEASE2 CREATION2018.120
>  ASSOCIATIONS
>NONVSAM-A.DATA.SET
>
>
> But when I refer to B.DATA.SET in //SYSLIB in an assemble job, I get 
> --> IEFA107I JOBNAME STEPNAME SYSLIB - DATA SET B.DATA.SET NOT FOUND
>
> What gives.. ?
>
> - Vignesh
> Mainframe Infrastructure
>
>
> MARKSANDSPENCER.COM
> 
> Unless otherwise stated above:
> Marks and Spencer plc
> Registered Office:
> Waterside House
> 35 North Wharf Road
> London
> W2 1NW
>
> Registered No. 214436 in England and Wales.
>
> Telephone (020) 7935 4422
> Facsimile (020) 7487 2670
>
> www.marksandspencer.com
>
> Please note that electronic mail may be monitored.
>
> This e-mail is confidential. If you received it by mistake, please let 
> us know and then delete it from your system; you should not copy, 
> disclose, or distribute its contents to anyone nor act in reliance on 
> this e-mail, as this is prohibited and may be unlawful.
>
> --
> 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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN