Re: Catalog manipulation (was RE: DFDSS QUESTION - SEMI URGENT - EXPLANATION)
On Mon, 16 Jun 2014 22:20:33 -0500, Joel C. Ewing wrote: It certainly doesn't make sense to go to the overhead of creating a new USERCAT rather than a new alias to an existing USERCAT for each new TSO user -- unless perhaps you have a very small, fairly static number of TSO users. There are RACF issues if your choice is to create a new user catalog with DSNAME GEORGE when you create TSO ID GEORGE. First, a RACF admin has to permit the Storage Admin, or whoever creates the catalog to the profile for GEORGE. And by default, George will have full access to the catalog GEORGE. Is that desirable? I think not. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS QUESTION - SEMI URGENT - EXPLANATION
Here is how the user bypassed the standard CATALOG search : DEFINE CLUSTER - ( NAME(MRP01.FOCUS.APPLIC.I0001.A001) - LINEAR - REUSE - CYLINDERS(100 200) - SHAREOPTIONS(3 3) ) - DATA - ( NAME(MRP01.FOCUS.APPLIC.I0001.A001) - ) - CATALOG(T10D) By specificying the parm CATALOG(T10D) the CLUSTER was created in the CATALOG where the ALIAS T10D resides in. This floored me because I have never seen this parm with the ALIAS specified in the define cluster. On Fri, 6/13/14, retired mainframer retired-mainfra...@q.com wrote: Subject: Re: DFDSS QUESTION - SEMI URGENT To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, June 13, 2014, 10:15 PM But Willie said it was done in JCL. How? :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of Skip Robinson :: Sent: Friday, June 13, 2014 3:04 PM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: :: To specify a catalog, you have to use IDCAMS DEFINE with the CATALOG :: parameter. If SAF allows it, you can specify any catalog you choose :: regardless of normal search order. :: :: From: retired mainframer :: To: IBM-MAIN@LISTSERV.UA.EDU, :: Date: 06/13/2014 12:16 PM :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: Sent by: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU :: :: :: :: How does a user specify a specific catalog in JCL when defining a :: dataset? :: :: :: -Original Message- :: :: From: IBM Mainframe Discussion List [mailto:IBM- :: m...@listserv.ua.edu] :: On :: :: Behalf Of willie bunter :: :: Sent: Friday, June 13, 2014 9:31 AM :: :: To: IBM-MAIN@LISTSERV.UA.EDU :: :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: :: :: :: I found the cause of the problem. The user defined the dsn in a :: :: specific USER CAT. In his JCL he specified the USER CAT name. He :: broke :: :: the house rules of letting the system decide which USER CAT to has :: to :: be :: :: allocated. Hence when the LISTCATs failed because the system was :: :: looking at the default USER CAT. The REPRO MERGECAT of the ALIAS :: fixed :: :: the problem. -- 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: DFDSS QUESTION - SEMI URGENT
INCAT, COPY DUMP didn't work that is why I did the REPRO merge. Perhaps I may have been missing a parm. If you have an example I would appreciate it if you could give it to me. Thanks. On Fri, 6/13/14, retired mainframer retired-mainfra...@q.com wrote: Subject: Re: DFDSS QUESTION - SEMI URGENT To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, June 13, 2014, 10:43 AM You have already fixed the problem but you could have tried using the INCAT and ONLYINCAT operands on either a dataset DUMP or COPY operation. :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of willie bunter :: Sent: Friday, June 13, 2014 7:37 AM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: DFDSS QUESTION - SEMI URGENT :: :: I have a SMS manged VSAM (linear) dsn cataloged in the wrong USER CAT. :: Is there a way to change it to use the correct catalog? :: :: I looked at using DFDSS COPY command however since the dsn is not :: cataloged in the STANDARD ORDER OF SEARCH it did not work. :: :: Can I use IDCAMS to rectify the error? -- 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
Catalog manipulation (was RE: DFDSS QUESTION - SEMI URGENT - EXPLANATION)
This brings back memories of a small zOS shop I worked at in the late 90s. They routinely built user catalogs whose entire name was 8 characters or less, and intentionally happened to match a high level qualifier(s). Their reasoning for this practice was that they did not have to define aliases. This shop supported a number of retail businesses whose datasets were all peculiar to their business, each branch having its own user catalog. When I inquired about the why and wherefore the response was it's too much trouble to define an alias. Personally I never thought it was all that tough a task. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Monday, June 16, 2014 11:13 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFDSS QUESTION - SEMI URGENT - EXPLANATION Here is how the user bypassed the standard CATALOG search : DEFINE CLUSTER - ( NAME(MRP01.FOCUS.APPLIC.I0001.A001) - LINEAR - REUSE - CYLINDERS(100 200) - SHAREOPTIONS(3 3) ) - DATA - ( NAME(MRP01.FOCUS.APPLIC.I0001.A001) - ) - CATALOG(T10D) By specificying the parm CATALOG(T10D) the CLUSTER was created in the CATALOG where the ALIAS T10D resides in. This floored me because I have never seen this parm with the ALIAS specified in the define cluster. On Fri, 6/13/14, retired mainframer retired-mainfra...@q.com wrote: Subject: Re: DFDSS QUESTION - SEMI URGENT To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, June 13, 2014, 10:15 PM But Willie said it was done in JCL. How? :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of Skip Robinson :: Sent: Friday, June 13, 2014 3:04 PM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: :: To specify a catalog, you have to use IDCAMS DEFINE with the CATALOG :: parameter. If SAF allows it, you can specify any catalog you choose :: regardless of normal search order. :: :: From: retired mainframer :: To: IBM-MAIN@LISTSERV.UA.EDU, :: Date: 06/13/2014 12:16 PM :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: Sent by: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU :: :: :: :: How does a user specify a specific catalog in JCL when defining a :: dataset? :: :: :: -Original Message- :: :: From: IBM Mainframe Discussion List [mailto:IBM- :: m...@listserv.ua.edu] :: On :: :: Behalf Of willie bunter :: :: Sent: Friday, June 13, 2014 9:31 AM :: :: To: IBM-MAIN@LISTSERV.UA.EDU :: :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: :: :: :: I found the cause of the problem. The user defined the dsn in a :: :: specific USER CAT. In his JCL he specified the USER CAT name. He :: broke :: :: the house rules of letting the system decide which USER CAT to has :: to :: be :: :: allocated. Hence when the LISTCATs failed because the system was :: :: looking at the default USER CAT. The REPRO MERGECAT of the ALIAS :: fixed :: :: the problem. -- 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
Re: DFDSS QUESTION - SEMI URGENT - EXPLANATION
Willie: You don't seem to have the proper RCF (acf2) rules set up to not allow this. Look at some of the other replies and they gave you a hint. Ed On Jun 16, 2014, at 11:12 AM, willie bunter wrote: Here is how the user bypassed the standard CATALOG search : DEFINE CLUSTER - ( NAME(MRP01.FOCUS.APPLIC.I0001.A001) - LINEAR - REUSE - CYLINDERS(100 200) - SHAREOPTIONS(3 3) ) - DATA - ( NAME(MRP01.FOCUS.APPLIC.I0001.A001) - ) - CATALOG(T10D) By specificying the parm CATALOG(T10D) the CLUSTER was created in the CATALOG where the ALIAS T10D resides in. This floored me because I have never seen this parm with the ALIAS specified in the define cluster. On Fri, 6/13/14, retired mainframer retired-mainfra...@q.com wrote: Subject: Re: DFDSS QUESTION - SEMI URGENT To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, June 13, 2014, 10:15 PM But Willie said it was done in JCL. How? :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM- m...@listserv.ua.edu] On :: Behalf Of Skip Robinson :: Sent: Friday, June 13, 2014 3:04 PM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: :: To specify a catalog, you have to use IDCAMS DEFINE with the CATALOG :: parameter. If SAF allows it, you can specify any catalog you choose :: regardless of normal search order. :: :: From: retired mainframer :: To: IBM-MAIN@LISTSERV.UA.EDU, :: Date: 06/13/2014 12:16 PM :: Subject:Re: DFDSS QUESTION - SEMI URGENT :: Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU :: :: :: :: How does a user specify a specific catalog in JCL when defining a :: dataset? :: :: :: -Original Message- :: :: From: IBM Mainframe Discussion List [mailto:IBM- :: m...@listserv.ua.edu] :: On :: :: Behalf Of willie bunter :: :: Sent: Friday, June 13, 2014 9:31 AM :: :: To: IBM-MAIN@LISTSERV.UA.EDU :: :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: :: :: :: I found the cause of the problem. The user defined the dsn in a :: :: specific USER CAT. In his JCL he specified the USER CAT name. He :: broke :: :: the house rules of letting the system decide which USER CAT to has :: to :: be :: :: allocated. Hence when the LISTCATs failed because the system was :: :: looking at the default USER CAT. The REPRO MERGECAT of the ALIAS :: fixed :: :: the problem. -- 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
Re: Catalog manipulation (was RE: DFDSS QUESTION - SEMI URGENT - EXPLANATION)
On Mon, 16 Jun 2014 11:44:53 -0500, Tony's Basement Computer wrote: This brings back memories of a small zOS shop I worked at in the late 90s. They routinely built user catalogs whose entire name was 8 characters or less, and intentionally happened to match a high level qualifier(s). Their reasoning for this practice was that they did not have to define aliases. This shop supported a number of retail businesses whose datasets were all peculiar to their business, each branch having its own user catalog. When I inquired about the why and wherefore the response was it's too much trouble to define an alias. Personally I never thought it was all that tough a task. OTOH, what benefit results from using aliases? Aliases seem to introduce needless complexity. Is the benefit in having fewer user catalogs, but more aliases in the master catalog? Flexibility, in being able to swap catalogs simply by redefining their aliases? (Drifting somewhat:) I learned (quite recently) that one defines aliases to VSAM data sets not with the DEFINE ALIAS command, but with DEFINE PATH. (Why? Emerson?) I believe catalogs are VSAM data sets. So, then, does one use the DEFINE PATH command to define aliases of catalogs? (IANASYSPROG. Obviously.) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS QUESTION - SEMI URGENT
didn't work covers too many possibilities for a meaningful response. Do you still have any of the listings from the jobs that didn't work? :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of willie bunter :: Sent: Monday, June 16, 2014 9:24 AM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: :: INCAT, COPY DUMP didn't work that is why I did the REPRO merge. :: Perhaps I may have been missing a parm. If you have an example I would :: appreciate it if you could give it to me. :: :: Thanks. :: :: On Fri, 6/13/14, retired mainframer retired-mainfra...@q.com wrote: :: :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: To: IBM-MAIN@LISTSERV.UA.EDU :: Received: Friday, June 13, 2014, 10:43 AM :: :: You have already fixed the problem :: but you could have tried using the INCAT :: and ONLYINCAT operands on either a dataset DUMP or COPY :: operation. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS QUESTION - SEMI URGENT - EXPLANATION
For your future reference: this is not JCL. Those are utility control cards. AMS obviously allows you to bypass normal catalog search order. I was trying to determine how your user did it with JCL as claimed. The answer is he didn't. When describing problems, details are often important. :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of willie bunter :: Sent: Monday, June 16, 2014 9:13 AM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: Re: DFDSS QUESTION - SEMI URGENT - EXPLANATION :: :: Here is how the user bypassed the standard CATALOG search : :: :: DEFINE CLUSTER - ::( NAME(MRP01.FOCUS.APPLIC.I0001.A001) - :: LINEAR - :: REUSE - :: CYLINDERS(100 200) - :: SHAREOPTIONS(3 3) ) - ::DATA - ::( NAME(MRP01.FOCUS.APPLIC.I0001.A001) - :: ) - :: CATALOG(T10D) :: :: By specificying the parm CATALOG(T10D) the CLUSTER was created in the :: CATALOG where the ALIAS T10D resides in. :: :: This floored me because I have never seen this parm with the ALIAS :: specified in the define cluster. :: :: On Fri, 6/13/14, retired mainframer retired-mainfra...@q.com wrote: :: :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: To: IBM-MAIN@LISTSERV.UA.EDU :: Received: Friday, June 13, 2014, 10:15 PM :: :: But Willie said it was done in :: JCL. How? :: :: :: -Original Message- :: :: From: IBM Mainframe Discussion List [mailto:IBM- :: m...@listserv.ua.edu] :: On :: :: Behalf Of Skip Robinson :: :: Sent: Friday, June 13, 2014 3:04 PM :: :: To: IBM-MAIN@LISTSERV.UA.EDU :: :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: :: :: :: To specify a catalog, you have to use IDCAMS DEFINE :: with the CATALOG :: :: parameter. If SAF allows it, you can specify any :: catalog you choose :: :: regardless of normal search order. :: :: :: :: From: retired mainframer :: :: To: IBM-MAIN@LISTSERV.UA.EDU, :: :: Date: 06/13/2014 12:16 PM :: :: Subject: Re: DFDSS :: QUESTION - SEMI URGENT :: :: Sent by: IBM Mainframe :: Discussion List IBM-MAIN@LISTSERV.UA.EDU :: :: :: :: :: :: :: :: How does a user specify a specific catalog in JCL :: when defining a :: :: dataset? :: :: :: :: :: -Original Message- :: :: :: From: IBM Mainframe Discussion List :: [mailto:IBM- :: :: m...@listserv.ua.edu] :: :: On :: :: :: Behalf Of willie bunter :: :: :: Sent: Friday, June 13, 2014 9:31 AM :: :: :: To: IBM-MAIN@LISTSERV.UA.EDU :: :: :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: :: :: :: :: :: I found the cause of the problem. The :: user defined the dsn in a :: :: :: specific USER CAT. In his JCL he :: specified the USER CAT name. He :: :: broke :: :: :: the house rules of letting the system decide :: which USER CAT to has :: :: to :: :: be :: :: :: allocated. Hence when the LISTCATs :: failed because the system was :: :: :: looking at the default USER CAT. The :: REPRO MERGECAT of the ALIAS :: :: fixed :: :: :: the problem. :: :: -- :: 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
Re: Catalog manipulation (was RE: DFDSS QUESTION - SEMI URGENT - EXPLANATION)
On 06/16/2014 07:10 PM, Paul Gilmartin wrote: On Mon, 16 Jun 2014 11:44:53 -0500, Tony's Basement Computer wrote: This brings back memories of a small zOS shop I worked at in the late 90s. They routinely built user catalogs whose entire name was 8 characters or less, and intentionally happened to match a high level qualifier(s). Their reasoning for this practice was that they did not have to define aliases. This shop supported a number of retail businesses whose datasets were all peculiar to their business, each branch having its own user catalog. When I inquired about the why and wherefore the response was it's too much trouble to define an alias. Personally I never thought it was all that tough a task. OTOH, what benefit results from using aliases? Aliases seem to introduce needless complexity. Is the benefit in having fewer user catalogs, but more aliases in the master catalog? Flexibility, in being able to swap catalogs simply by redefining their aliases? (Drifting somewhat:) I learned (quite recently) that one defines aliases to VSAM data sets not with the DEFINE ALIAS command, but with DEFINE PATH. (Why? Emerson?) I believe catalogs are VSAM data sets. So, then, does one use the DEFINE PATH command to define aliases of catalogs? (IANASYSPROG. Obviously.) -- gil There are two types of aliases: those that map the cataloging of all data sets beginning with a specific, possibly-multi-level prefix to a specific USERCAT; and those that map one specific data set name as an alias for another specific data set name (which must be located in the same user catalog). The DEFINE PATH is only used to set up an alternate data set name for a specific VSAM data set component, some times used when the same data set needs to be referred to by different HLQ's from different systems because of prefix-alias-to-USERCAT conflicts on one of the systems. I suspect VSAM is handled differently because VSAM data sets also existed on DOS/VS which did not have a catalog structure for non-VSAM datasets, but that's just a guess. The DEFINE ALIAS is used for both VSAM and non-VSAM data sets to establish the default USERCAT for cataloging datasets based on HL prefix. The same command is also used to define a full data-set-name alias for a specific non-VSAM data set. It certainly doesn't make sense to go to the overhead of creating a new USERCAT rather than a new alias to an existing USERCAT for each new TSO user -- unless perhaps you have a very small, fairly static number of TSO users. Whether it makes sense to map multiple application HL prefixes to the same USERCAT for other non-TSO-user data sets all depends on your installation DS naming standards and the number of data sets involved. In our case the overhead and complexity of creating and maintaining unique USERCATs for each HL prefix would have been much greater than mapping multiple aliases to one USERCAT and also inappropriate for our recovery requirements. Also having the number of USERCATs being a smaller and relatively stable list made it much easier to be sure we had multiple daily backups and suitable recovery procedures in place for all USERCATs. Renaming components of a VSAM sphere in ways that change the HL prefix cannot recatalog the component into a different USERCAT, so the new prefix would also need to be an ALIAS for the same USERCAT or very confusing things happen. Depending on installation DS renaming requirements, this may also be a strong argument for having multiple ALIAS prefixes mapping to the same USERCAT. I can't conceive of a production environment where you would want USERCAT choice to be left to users or application programmers rather than having it enforced via ALIAS definitions for HLQ(s); otherwise, you inevitably end up with user errors creating lost cataloged data sets that can't be found in the expected catalog. -- Joel C. Ewing,Bentonville, AR jcew...@acm.org -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalog manipulation (was RE: DFDSS QUESTION - SEMI URGENT - EXPLANATION)
Men are from Mars. Women are from Venus. System programmers are from Earth, where a mature installation with a few decades of history under its belt has to deal with a multitude of HLQs each associated with an application and by implication a business unit, which BTW pays the bills. Our main production master catalog--the one I earlier mentioned that was created in 1983--has over a thousand aliases pointing (thankfully) to a far smaller number of user catalogs. We get by. Catalogs on Mars or Venus may represent a simpler zoo to manage. One day mankind will get there and become transformed by the vision of what life was like in Eden. Meanwhile, back on the earthly ranch, we deal with things as they are today. I'm not sure in which afterthought of Creation aliases and user catalogs emerged, but thanks to Whomever for the kindness. . . J.O.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: Joel C. Ewing jcew...@acm.org To: IBM-MAIN@LISTSERV.UA.EDU, Date: 06/16/2014 08:20 PM Subject:Re: Catalog manipulation (was RE: DFDSS QUESTION - SEMI URGENT - EXPLANATION) Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On 06/16/2014 07:10 PM, Paul Gilmartin wrote: On Mon, 16 Jun 2014 11:44:53 -0500, Tony's Basement Computer wrote: This brings back memories of a small zOS shop I worked at in the late 90s. They routinely built user catalogs whose entire name was 8 characters or less, and intentionally happened to match a high level qualifier(s). Their reasoning for this practice was that they did not have to define aliases. This shop supported a number of retail businesses whose datasets were all peculiar to their business, each branch having its own user catalog. When I inquired about the why and wherefore the response was it's too much trouble to define an alias. Personally I never thought it was all that tough a task. OTOH, what benefit results from using aliases? Aliases seem to introduce needless complexity. Is the benefit in having fewer user catalogs, but more aliases in the master catalog? Flexibility, in being able to swap catalogs simply by redefining their aliases? (Drifting somewhat:) I learned (quite recently) that one defines aliases to VSAM data sets not with the DEFINE ALIAS command, but with DEFINE PATH. (Why? Emerson?) I believe catalogs are VSAM data sets. So, then, does one use the DEFINE PATH command to define aliases of catalogs? (IANASYSPROG. Obviously.) -- gil There are two types of aliases: those that map the cataloging of all data sets beginning with a specific, possibly-multi-level prefix to a specific USERCAT; and those that map one specific data set name as an alias for another specific data set name (which must be located in the same user catalog). The DEFINE PATH is only used to set up an alternate data set name for a specific VSAM data set component, some times used when the same data set needs to be referred to by different HLQ's from different systems because of prefix-alias-to-USERCAT conflicts on one of the systems. I suspect VSAM is handled differently because VSAM data sets also existed on DOS/VS which did not have a catalog structure for non-VSAM datasets, but that's just a guess. The DEFINE ALIAS is used for both VSAM and non-VSAM data sets to establish the default USERCAT for cataloging datasets based on HL prefix. The same command is also used to define a full data-set-name alias for a specific non-VSAM data set. It certainly doesn't make sense to go to the overhead of creating a new USERCAT rather than a new alias to an existing USERCAT for each new TSO user -- unless perhaps you have a very small, fairly static number of TSO users. Whether it makes sense to map multiple application HL prefixes to the same USERCAT for other non-TSO-user data sets all depends on your installation DS naming standards and the number of data sets involved. In our case the overhead and complexity of creating and maintaining unique USERCATs for each HL prefix would have been much greater than mapping multiple aliases to one USERCAT and also inappropriate for our recovery requirements. Also having the number of USERCATs being a smaller and relatively stable list made it much easier to be sure we had multiple daily backups and suitable recovery procedures in place for all USERCATs. Renaming components of a VSAM sphere in ways that change the HL prefix cannot recatalog the component into a different USERCAT, so the new prefix would also need to be an ALIAS for the same USERCAT or very confusing things happen. Depending on installation DS renaming requirements, this may also be a strong argument for having multiple ALIAS prefixes mapping to the same USERCAT. I can't conceive of a production environment where you would want USERCAT choice to be left to users
Re: Catalog manipulation (was RE: DFDSS QUESTION - SEMI URGENT - EXPLANATION)
On Jun 16, 2014, at 10:20 PM, Joel C. Ewing wrote: --SNIP-- I can't conceive of a production environment where you would want USERCAT choice to be left to users or application programmers rather than having it enforced via ALIAS definitions for HLQ(s); otherwise, you inevitably end up with user errors creating lost cataloged data sets that can't be found in the expected catalog. Joel, I *think* in VS1 you had to have the cat (catalog) parameter . It took me 2 years of fighting to get it into the standards manual. Luckily we had Fileaid and the change was trivial. I think I did it the week after it was approved in the standards manual. The people were just hung up on having it and I could never find out why. I know back in the old MVS days sometimes stepcats were needed when messing around with the catalog but that has gone at least 99 percent with the dinosaurs. I know stepcat/jobcat are no longer honored but in the far distant passed at times they were needed(at times), I was scared when IBM announced they retirement but since IBM fixed the problems they corrected I don't have a problem anymore with their banishment. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalog manipulation (was RE: DFDSS QUESTION - SEMI URGENT - EXPLANATION)
On Jun 16, 2014, at 11:00 PM, Skip Robinson wrote: Men are from Mars. Women are from Venus. System programmers are from Earth, where a mature installation with a few decades of history under its belt has to deal with a multitude of HLQs each associated with an application and by implication a business unit, which BTW pays the bills. Our main production master catalog--the one I earlier mentioned that was created in 1983--has over a thousand aliases pointing (thankfully) to a far smaller number of user catalogs. We get by. Catalogs on Mars or Venus may represent a simpler zoo to manage. One day mankind will get there and become transformed by the vision of what life was like in Eden. Meanwhile, back on the earthly ranch, we deal with things as they are today. I'm not sure in which afterthought of Creation aliases and user catalogs emerged, but thanks to Whomever for the kindness. . . SKIP: I am with you but with one small change. We (I) always had on password (Update) on the mastercatalog (this was before RACF and ACF2) Some jerk programmer always wanted to create (and catalog) a tape with a non standard DSN (No HLQ) that put a stop to that. I was relentless with programmers, in other words I was a hard ass. Nobody knew what the password was except the sysprog group. One thing that has distressed me is that IBM *USED to* provide a CBIPO program that dealt nicely with changes to master catalogs. They dropped it and the only substitute is on the CBTTAPE. IBM has really lost it since the CBIPO. The support (of their new offering) in Germany (at least that was the last time I tried support) was useless. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS QUESTION - SEMI URGENT
Please Provide a LISTC ENT(/) ALL of the vsam dataset Also, which catalog should it be in? It is really hard (in my opinion) to catalog VSAM in the wrong Catalog unless you were not working from the target system. Did you do an ALTER NEWNAME function to do this? Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Friday, June 13, 2014 7:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DFDSS QUESTION - SEMI URGENT I have a SMS manged VSAM (linear) dsn cataloged in the wrong USER CAT. Is there a way to change it to use the correct catalog? I looked at using DFDSS COPY command however since the dsn is not cataloged in the STANDARD ORDER OF SEARCH it did not work. Can I use IDCAMS to rectify the error? Thanks for your help in advance. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS QUESTION - SEMI URGENT
Going with Lizette's comment, can you alter the dataset name so it can be found using the standard catalog search order, then use dss copy with the delete and renameu options to get it cataloged where you want it to be, and with the right DSN? Mark Jacobs On 06/13/14 10:49, Lizette Koehler wrote: Please Provide a LISTC ENT(/) ALL of the vsam dataset Also, which catalog should it be in? It is really hard (in my opinion) to catalog VSAM in the wrong Catalog unless you were not working from the target system. Did you do an ALTER NEWNAME function to do this? Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Friday, June 13, 2014 7:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DFDSS QUESTION - SEMI URGENT I have a SMS manged VSAM (linear) dsn cataloged in the wrong USER CAT. Is there a way to change it to use the correct catalog? I looked at using DFDSS COPY command however since the dsn is not cataloged in the STANDARD ORDER OF SEARCH it did not work. Can I use IDCAMS to rectify the error? Thanks for your help in advance. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mark Jacobs Time Customer Service Tampa, FL The quiet ones are the ones that change the universe... The loud ones only take the credit. Londo Mollari - Babylon 5 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS QUESTION - SEMI URGENT
When I do the LISTCAT it doesn' find the dsn. I am not sure how the dsn was cataloged in the wrong catalog. The user asked for my help. If I need to ALTER the dsn to use the right catalog is there a STEPCAT parm that needs to be used? On Fri, 6/13/14, Lizette Koehler stars...@mindspring.com wrote: Subject: Re: DFDSS QUESTION - SEMI URGENT To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, June 13, 2014, 7:49 AM Please Provide a LISTC ENT(/) ALL of the vsam dataset Also, which catalog should it be in? It is really hard (in my opinion) to catalog VSAM in the wrong Catalog unless you were not working from the target system. Did you do an ALTER NEWNAME function to do this? Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Friday, June 13, 2014 7:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DFDSS QUESTION - SEMI URGENT I have a SMS manged VSAM (linear) dsn cataloged in the wrong USER CAT. Is there a way to change it to use the correct catalog? I looked at using DFDSS COPY command however since the dsn is not cataloged in the STANDARD ORDER OF SEARCH it did not work. Can I use IDCAMS to rectify the error? Thanks for your help in advance. -- 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: DFDSS QUESTION - SEMI URGENT
DEL 'entryname' nscr cat(wrong ucat)
Def 'entryname' (other parameters) cat(correct ucat)
Other parameters will depend on the type of dataset (LVSAM, seq, .)
Another possibility is:
repro mergecat ent('entryname) ifile(wrong ucat) ofile(correct ucat)
HTH,
snip
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of willie bunter Sent: Friday, June 13, 2014 7:37 AM To:
IBM-MAIN@LISTSERV.UA.EDU Subject: DFDSS QUESTION - SEMI URGENT I
have a SMS manged VSAM (linear) dsn cataloged in the wrong USER CAT. Is
there a way to change it to use the correct catalog?
I looked at using DFDSS COPY command however since the dsn is not
cataloged in the STANDARD ORDER OF SEARCH it did not work.
Can I use IDCAMS to rectify the error?
/snip
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS QUESTION - SEMI URGENT
Lizette Koehler wrote: Please Provide a LISTC ENT(/) ALL of the vsam dataset Good request! With that command, the standard search order is used, but according to Willie it is not there. Willie, please try out the command and post the results. It is really hard (in my opinion) to catalog VSAM in the wrong Catalog unless you were not working from the target system. Indeed. This is where RACF comes in to prevent such errors. Willie Bunter wrote: I have a SMS manged VSAM (linear) dsn cataloged in the wrong USER CAT. How do you know in the first place it is cataloged in the wrong User Catalog? Is it a naming issue or result of an incorrect IDCAMS command? Or is your VSAM dataset perhaps a duplicate? VVDS/VTOC issue? Is there a way to change it to use the correct catalog? Only if you specify the right catalog while using it. I looked at using DFDSS COPY command however since the dsn is not cataloged in the STANDARD ORDER OF SEARCH it did not work. Can I use IDCAMS to rectify the error? Yes. REPRO to a temporary VSAM dataset. Get rid of the catalog entry and the actual allocated spaces. Then do a proper DEFINE using Standard Search Order and then REPRO back. HTH! Groette / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS QUESTION - SEMI URGENT - PROBLEM FIXED
I was able to rectify the problem by using the MERGECAT option since there was only 1 dsn for that specific ALIAS. I got a rude shock to find out that STEPCAT DD is no longer allowed. Ouch. Has anybody been able to use STEPCAT? On Fri, 6/13/14, willie bunter 001409bd2345-dmarc-requ...@listserv.ua.edu wrote: Subject: Re: DFDSS QUESTION - SEMI URGENT To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, June 13, 2014, 8:07 AM When I do the LISTCAT it doesn' find the dsn. I am not sure how the dsn was cataloged in the wrong catalog. The user asked for my help. If I need to ALTER the dsn to use the right catalog is there a STEPCAT parm that needs to be used? On Fri, 6/13/14, Lizette Koehler stars...@mindspring.com wrote: Subject: Re: DFDSS QUESTION - SEMI URGENT To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, June 13, 2014, 7:49 AM Please Provide a LISTC ENT(/) ALL of the vsam dataset Also, which catalog should it be in? It is really hard (in my opinion) to catalog VSAM in the wrong Catalog unless you were not working from the target system. Did you do an ALTER NEWNAME function to do this? Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Friday, June 13, 2014 7:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DFDSS QUESTION - SEMI URGENT I have a SMS manged VSAM (linear) dsn cataloged in the wrong USER CAT. Is there a way to change it to use the correct catalog? I looked at using DFDSS COPY command however since the dsn is not cataloged in the STANDARD ORDER OF SEARCH it did not work. Can I use IDCAMS to rectify the error? Thanks for your help in advance. -- 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
Re: DFDSS QUESTION - SEMI URGENT - PROBLEM FIXED
STEPCAT has been gone for (IIRC) about 7 or 8 years. ISTR. z/OS 1.9... snip I was able to rectify the problem by using the MERGECAT option since there was only 1 dsn for that specific ALIAS. I got a rude shock to find out that STEPCAT DD is no longer allowed. Ouch. Has anybody been able to use STEPCAT? /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS QUESTION - SEMI URGENT
I found the cause of the problem. The user defined the dsn in a specific USER CAT. In his JCL he specified the USER CAT name. He broke the house rules of letting the system decide which USER CAT to has to be allocated. Hence when the LISTCATs failed because the system was looking at the default USER CAT. The REPRO MERGECAT of the ALIAS fixed the problem. I thought that moving the the DSN with a DELETE RANAMEUNC would work however I couldn't run the job because of STEPCAT not being supported. Does anyone know of a way of doing what I tried to do i.e. force the system to look at a specific USER CAT (using DFDSS) so that in the future a drastic measure of MERGECAT wouldn't be necessary? I know that I was able to do this in the past when using the DFDSS COPY command. Thanks again to all who responded to my post. On Fri, 6/13/14, Elardus Engelbrecht elardus.engelbre...@sita.co.za wrote: Subject: Re: DFDSS QUESTION - SEMI URGENT To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, June 13, 2014, 8:13 AM Lizette Koehler wrote: Please Provide a LISTC ENT(/) ALL of the vsam dataset Good request! With that command, the standard search order is used, but according to Willie it is not there. Willie, please try out the command and post the results. It is really hard (in my opinion) to catalog VSAM in the wrong Catalog unless you were not working from the target system. Indeed. This is where RACF comes in to prevent such errors. Willie Bunter wrote: I have a SMS manged VSAM (linear) dsn cataloged in the wrong USER CAT. How do you know in the first place it is cataloged in the wrong User Catalog? Is it a naming issue or result of an incorrect IDCAMS command? Or is your VSAM dataset perhaps a duplicate? VVDS/VTOC issue? Is there a way to change it to use the correct catalog? Only if you specify the right catalog while using it. I looked at using DFDSS COPY command however since the dsn is not cataloged in the STANDARD ORDER OF SEARCH it did not work. Can I use IDCAMS to rectify the error? Yes. REPRO to a temporary VSAM dataset. Get rid of the catalog entry and the actual allocated spaces. Then do a proper DEFINE using Standard Search Order and then REPRO back. HTH! Groette / Greetings Elardus Engelbrecht -- 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: DFDSS QUESTION - SEMI URGENT
willie bunter wrote: I found the cause of the problem. The user defined the dsn in a specific USER CAT. In his JCL he specified the USER CAT name. He broke the house rules of letting the system decide which USER CAT to has to be allocated. Check out FACILITY Class profile STGADMIN.IGG.DIRCAT in RACF if it can prevent a re-occurance of this problem. We have also our house rules - Let the system decides on blocksizes, catalogs, Volsers and WLM classes amongst a lot of related rules+settings. And we warned the users - if we find an uncataloged dataset - it will be deleted [1] without any backups + questions at all. Groette / Greetings Elardus Engelbrecht [1] - Of course the normal checks of being cataloged in another system applies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS QUESTION - SEMI URGENT - PROBLEM FIXED
On Fri, 13 Jun 2014 16:02:49 +, Staller, Allan wrote: STEPCAT has been gone for (IIRC) about 7 or 8 years. ISTR. z/OS 1.9... You might be right about when STEPCAT/JOBCAT were removed completely, but they were never allowed with SMS managed data sets. The following is from MVS/DFP 3.3: Managing Catalogs, Document Number SC26-4555-02, dated December 1991. IIRC it wasn't new then. quote If you are running the Storage Management Subsystem (SMS), you should not use the JOBCAT and STEPCAT DD statements. If a job contains a JOBCAT or STEPCAT DD statement, the first step in the job which refers to an SMS-managed data set fails, and all following steps in that job are bypassed. The job terminates. /quote -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS QUESTION - SEMI URGENT
Agree. A desperate measure would be to beat the user abruptly about the head and shoulders On Jun 13, 2014 12:04 PM, Tom Marchant 000a2a8c2020-dmarc-requ...@listserv.ua.edu wrote: On Fri, 13 Jun 2014 09:30:46 -0700, willie bunter wrote: Does anyone know of a way of doing what I tried to do i.e. force the system to look at a specific USER CAT (using DFDSS) so that in the future a drastic measure of MERGECAT wouldn't be necessary? I wouldn't call REPRO MERGECAT a drastic measure. -- 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: DFDSS QUESTION - SEMI URGENT
You have already fixed the problem but you could have tried using the INCAT and ONLYINCAT operands on either a dataset DUMP or COPY operation. :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of willie bunter :: Sent: Friday, June 13, 2014 7:37 AM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: DFDSS QUESTION - SEMI URGENT :: :: I have a SMS manged VSAM (linear) dsn cataloged in the wrong USER CAT. :: Is there a way to change it to use the correct catalog? :: :: I looked at using DFDSS COPY command however since the dsn is not :: cataloged in the STANDARD ORDER OF SEARCH it did not work. :: :: Can I use IDCAMS to rectify the error? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS QUESTION - SEMI URGENT
Did you use the CATALOG operand to specify which catalog the dataset was in? :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of willie bunter :: Sent: Friday, June 13, 2014 8:07 AM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: :: When I do the LISTCAT it doesn' find the dsn. I am not sure how the dsn :: was cataloged in the wrong catalog. :: The user asked for my help. If I need to ALTER the dsn to use the right :: catalog is there a STEPCAT parm that needs to be used? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS QUESTION - SEMI URGENT
How does a user specify a specific catalog in JCL when defining a dataset? :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of willie bunter :: Sent: Friday, June 13, 2014 9:31 AM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: :: I found the cause of the problem. The user defined the dsn in a :: specific USER CAT. In his JCL he specified the USER CAT name. He broke :: the house rules of letting the system decide which USER CAT to has to be :: allocated. Hence when the LISTCATs failed because the system was :: looking at the default USER CAT. The REPRO MERGECAT of the ALIAS fixed :: the problem. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS QUESTION - SEMI URGENT
To specify a catalog, you have to use IDCAMS DEFINE with the CATALOG parameter. If SAF allows it, you can specify any catalog you choose regardless of normal search order. . . J.O.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: retired mainframer retired-mainfra...@q.com To: IBM-MAIN@LISTSERV.UA.EDU, Date: 06/13/2014 12:16 PM Subject:Re: DFDSS QUESTION - SEMI URGENT Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU How does a user specify a specific catalog in JCL when defining a dataset? :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of willie bunter :: Sent: Friday, June 13, 2014 9:31 AM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: :: I found the cause of the problem. The user defined the dsn in a :: specific USER CAT. In his JCL he specified the USER CAT name. He broke :: the house rules of letting the system decide which USER CAT to has to be :: allocated. Hence when the LISTCATs failed because the system was :: looking at the default USER CAT. The REPRO MERGECAT of the ALIAS fixed :: the problem. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFDSS QUESTION - SEMI URGENT
But Willie said it was done in JCL. How? :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of Skip Robinson :: Sent: Friday, June 13, 2014 3:04 PM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: :: To specify a catalog, you have to use IDCAMS DEFINE with the CATALOG :: parameter. If SAF allows it, you can specify any catalog you choose :: regardless of normal search order. :: :: From: retired mainframer :: To: IBM-MAIN@LISTSERV.UA.EDU, :: Date: 06/13/2014 12:16 PM :: Subject:Re: DFDSS QUESTION - SEMI URGENT :: Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU :: :: :: :: How does a user specify a specific catalog in JCL when defining a :: dataset? :: :: :: -Original Message- :: :: From: IBM Mainframe Discussion List [mailto:IBM- :: m...@listserv.ua.edu] :: On :: :: Behalf Of willie bunter :: :: Sent: Friday, June 13, 2014 9:31 AM :: :: To: IBM-MAIN@LISTSERV.UA.EDU :: :: Subject: Re: DFDSS QUESTION - SEMI URGENT :: :: :: :: I found the cause of the problem. The user defined the dsn in a :: :: specific USER CAT. In his JCL he specified the USER CAT name. He :: broke :: :: the house rules of letting the system decide which USER CAT to has :: to :: be :: :: allocated. Hence when the LISTCATs failed because the system was :: :: looking at the default USER CAT. The REPRO MERGECAT of the ALIAS :: fixed :: :: the problem. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
