Re: IEFA107I when pointing to dataset alias

Further testing indicates this works great! On Wed, May 30, 2018 at 8:08 AM Michael Babcock wrote: > I searched IBMLINK and found OA54626. ISPF option 1 works but ISPF 3.4 > does not. So my alias definition works but there is a bug which prevents > 3.4 from working. So I’m good to go! > > On

Re: IEFA107I when pointing to dataset alias

I searched IBMLINK and found OA54626. ISPF option 1 works but ISPF 3.4 does not. So my alias definition works but there is a bug which prevents 3.4 from working. So I’m good to go! On Tue, May 29, 2018 at 7:08 PM Michael Babcock wrote: > Also, if the symbol ends with an underscore, the value

Re: IEFA107I when pointing to dataset alias

Also, if the symbol ends with an underscore, the value can be longer than the symbol. On Tue, May 29, 2018 at 7:05 PM Michael Babcock wrote: > I’m at z/OS 2.2 > > On Tue, May 29, 2018 at 4:46 PM Paul Gilmartin < > 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > >> On Tue, 29 May 2018

Re: IEFA107I when pointing to dataset alias

I’m at z/OS 2.2 On Tue, May 29, 2018 at 4:46 PM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Tue, 29 May 2018 23:30:22 +0200, Lucas Rosalen wrote: > > >The ALIAS must be in the same catalog as the actual dataset. > > > Not for SYMBOLICRELATE, but only in very

Re: IEFA107I when pointing to dataset alias

On Tue, 29 May 2018 23:30:22 +0200, Lucas Rosalen wrote: >The ALIAS must be in the same catalog as the actual dataset. > Not for SYMBOLICRELATE, but only in very recent z/OS. -- gil -- For IBM-MAIN subscribe / signoff /

Re: IEFA107I when pointing to dataset alias

On Tue, 29 May 2018 16:09:54 -0500, Michael Babcock wrote: >Okay, I'm getting myself confused regarding SYMBOLICRELATE. > >I have a data set, SYS3.LINKLIB which resides in CATALOG.USERSYS. I want to >define an alias called XX35.SYS3.LINKLIB (XX35 hlq data sets reside in >CATALOG.USERTSO)

Re: IEFA107I when pointing to dataset alias

I think the alias and the resolved dataset have to be in the same catalog. Mark Jacobs Michael Babcock May 29, 2018 at 5:09 PM Okay, I'm getting myself confused regarding SYMBOLICRELATE. I have a data set, SYS3.LINKLIB which resides in CATALOG.USERSYS. I want to

Re: IEFA107I when pointing to dataset alias

The ALIAS must be in the same catalog as the actual dataset. I think you could bypass this in a very "strange" way by: 1. definig an ALIAS XX35.SYS3 in your CATALOG.USERTSO poiting to CATALOG.USERSYS. 2. Then, definig your ALIAS with the SYMBOLICRELATE in CATALOG.USERSYS. Regards, Lucas On Tue,

Re: IEFA107I when pointing to dataset alias

Okay, I'm getting myself confused regarding SYMBOLICRELATE. I have a data set, SYS3.LINKLIB which resides in CATALOG.USERSYS. I want to define an alias called XX35.SYS3.LINKLIB (XX35 hlq data sets reside in CATALOG.USERTSO) that points to the SYS3.LINKLIB data set. I've issued: DEF

Re: IEFA107I when pointing to dataset alias

From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of Dan D <zos.j...@gmail.com> Sent: Saturday, May 5, 2018 11:01 AM To: IBM-MAIN@listserv.ua.edu Subject: Re: IEFA107I when pointing to dataset alias A very long time

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

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

Re: IEFA107I when pointing to dataset alias

On Sat, 5 May 2018 13:45:45 -0500, Mike Schwab wrote: >IBM did a one test library addition for PDSE for COBOL 5 > Details (or citation)? Is this a facility peculiar to COBOL? PDSE only, or old-fashioned PDS? >On Sat, May 5, 2018 at 10:01 AM, Dan D wrote: >> A very long time ago (over 30

Re: IEFA107I when pointing to dataset alias

IBM did a one test library addition for PDSE for COBOL 5 On Sat, May 5, 2018 at 10:01 AM, Dan D wrote: > 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.

Re: IEFA107I when pointing to dataset alias

On Sat, 5 May 2018 10:01:23 -0500, Dan D wrote: >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

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

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

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

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

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

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.

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

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 li

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

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

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

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

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

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

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

Re: IEFA107I when pointing to dataset alias

John Eells wrote: Previously, I wrote: (* Let's leave SYMBOLICRELATE out of it for now, until we all understand the basics. Likewise, we can work our way up to what happens before Catalog processes aliases and PATHENTRY entries for VSAM data seats, if necessary.) So now, let's look at what

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

nframe 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

Re: IEFA107I when pointing to dataset alias

Hello Vignesh, The ALIAS entry does not point to a UCAT - it points to the MCAT NVSAM entry. What is the MLA value set to in your LOADxx member SYSCAT statement? What other entries do you have for B.** in your MCAT? These could be obscuring your ALIAS entry. > NONVSAM --- A.DATA.SET >

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

[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

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

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

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

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

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

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

Re: IEFA107I when pointing to dataset alias

Data set aliases have confused people for a long time. There are two basic kinds of aliases, user catalog connector aliases and data set aliases. Let's start with user catalog connector aliases. These are the ones where what is specified on RELATE is a user catalog. User catalog connector

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

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

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

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

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

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

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

: 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

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

Re: IEFA107I when pointing to dataset alias

: 01 May 2018 3:59 am Subject: Re: IEFA107I when pointing to dataset alias On Mon, 30 Apr 2018 12:32:26 -0500, Paul Gilmartin <paulgboul...@aim.com> wrote: >There ought to be an RFE tnat when the lookup fails in B's catalog the search >should >be re-driven from A's catalog. How coul

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

] 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(VO

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

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

: 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

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

erica.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 point

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

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

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

: 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

Re: IEFA107I when pointing to dataset alias

On Mon, 30 Apr 2018 12:32:26 -0500, Paul Gilmartin wrote: >There ought to be an RFE tnat when the lookup fails in B's catalog the search >should >be re-driven from A's catalog. How could that possibly work? I reference B.DATA.SET and so the system goes to the catalog

Re: IEFA107I when pointing to dataset alias

On Mon, 30 Apr 2018 13:28:57 -0500, John McKown wrote: >On Mon, Apr 30, 2018 at 1:11 PM, Steve Smith wrote: >> >> btw, it's not valid to put a macro library in the APF or linklist. Nor to >> try to use a load library as a macro library. >> >​Hum, now wouldn't it be "interesting" if you could use

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

Re: IEFA107I when pointing to dataset alias

On Mon, Apr 30, 2018 at 1:11 PM, Steve Smith wrote: > You are entangling non-VSAM aliases and Usercat aliases. > > Non-VSAM aliases are always created in the same catalog as the related > name. However, catalog look-up will use relevant catalog aliases to > determine where

Re: IEFA107I when pointing to dataset alias

You are entangling non-VSAM aliases and Usercat aliases. Non-VSAM aliases are always created in the same catalog as the related name. However, catalog look-up will use relevant catalog aliases to determine where the name is cataloged. Probably, you need to specify the proper catalog (i.e. the

Re: IEFA107I when pointing to dataset alias

bOn Mon, Apr 30, 2018 at 12:41 PM, Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Mon, 30 Apr 2018 12:15:26 -0500, Steve Horein > wrote: > > >In the DEFINE ALIAS doc here (for reference): >

Re: IEFA107I when pointing to dataset alias

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

Re: IEFA107I when pointing to dataset alias

On Mon, 30 Apr 2018 12:15:26 -0500, Steve Horein wrote: >In the DEFINE ALIAS doc here (for reference): >https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.idai200/da6i2100.htm >and here (for detail):

Re: IEFA107I when pointing to dataset alias

On Mon, 30 Apr 2018 11:59:18 -0500, John McKown wrote: >> >> 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. >> >​RCF time, I guess.

Re: IEFA107I when pointing to dataset alias

On Mon, Apr 30, 2018 at 12:15 PM, Steve Horein wrote: > In the DEFINE ALIAS doc here (for reference): > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/ > com.ibm.zos.v2r2.idai200/da6i2100.htm > and here (for detail): >

Re: IEFA107I when pointing to dataset alias

4: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>): > > > >

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

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

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

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

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 point

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

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

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 hav

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

] 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, > &

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

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