Re: User datasets wrongly catalogued under Master Catalogue
Somewhere stuck in the back of mymemory is a restriction that the source catalog for a REPRO MERGECAT cannot be the active master catalog. However, I am not able to find something in the documentation to back up this memory. Maybe this is an old restriction that has since been removed; maybe I cannot find the doc to prove this; maybe I am just getting old. If this is a restriction, you can always bring up the system with another master catalog and connect this master catalog to it and treat it as a user catalog. Jeff Holst -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: User datasets wrongly catalogued under Master Catalogue
On z/OS 1.11 and probably as far back as OS/390 2.10, I have had no problem using the MERGECAT operand specifying the active master catalog in either direction (source or destination). - Original Message - From: Jeff Holst jeff.ho...@fiserv.com To: IBM-MAIN@bama.ua.edu Sent: Thursday, March 1, 2012 10:31:56 AM Subject: Re: User datasets wrongly catalogued under Master Catalogue Somewhere stuck in the back of mymemory is a restriction that the source catalog for a REPRO MERGECAT cannot be the active master catalog. However, I am not able to find something in the documentation to back up this memory. Maybe this is an old restriction that has since been removed; maybe I cannot find the doc to prove this; maybe I am just getting old. If this is a restriction, you can always bring up the system with another master catalog and connect this master catalog to it and treat it as a user catalog. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: User datasets wrongly catalogued under Master Catalogue
The sample below will do the job. As others have mentioned, products like T-REX can perform this task exponentially faster. It would also offer you a SIMULATE feature to verify what entries would be moved. If you have any questions on the process, or would like to bounce ideas off me, feel free to call anytime. Larry Crilley Dino-Software Corporation 800.480.DINO 412.366.3566 www.dino-software.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Richard L Peurifoy Sent: Wednesday, February 29, 2012 12:06 PM To: IBM-MAIN@bama.ua.edu Subject: Re: User datasets wrongly catalogued under Master Catalogue On 2/29/2012 6:43 AM, Martin, Larry D wrote: You can also use IDCAMS MERGECAT to move the catalog entries and then define the ALIAS(s). Here is a sample to do it. //MOVCAT JOB //* //PRINT EXEC PGM=IDCAMS //* //SYSPRINT DD SYSOUT=A //SYSIN DD * REPRO - LEVEL(@ ) - INDATASET(CATALOG.MSTCAT) - OUTDATASET(CATALOG.USRCAT) - MERGECAT DEFINE ALIAS(NAME(@ ) - RELATE(CATALOG.USRCAT)) - CAT(CATALOG.MSTCAT) -- Richard -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Fwd: User datasets wrongly catalogued under Master Catalogue
In 5467422117818390.wa.paulgboulderaim@bama.ua.edu, on 02/29/2012 at 01:28 AM, Paul Gilmartin paulgboul...@aim.com said: I have a question on terminology: someone stated here lately that user catalogs are ancient history; no longer used. Are you sure? Perhaps they stated that VSAM catalogs or STEPCAT were anceint history. Is this so? No. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: User datasets wrongly catalogued under Master Catalogue
You use IDCAMS to to a REPRO LEVEL(userid) MERGECAT from the master to the correct user catalog and then DEFINE the ALIAS. There are Catalog enhancing utilities (Catalog Recovery Plus and the other one) that do this faster than IDCAMS if you have a large number of entries to move. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Jake anderson Sent: Tuesday, February 28, 2012 7:45 PM To: IBM-MAIN@bama.ua.edu Subject: Fwd: User datasets wrongly catalogued under Master Catalogue I agree that this happens when a userid is defined with alias relating to user catalog. typo - it happens when a userid is *not* defined with alias relating to user catalog. -- Forwarded message -- From: Jake anderson justmainfra...@gmail.com Date: Wed, Feb 29, 2012 at 9:11 AM Subject: User datasets wrongly catalogued under Master Catalogue To: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Hi, Recently We have installed a new system Z/OS 1.13. During migration the Users datasets were restored and unfortunately all the user datasets are catalogued under Master catalogue. I agree that this happens when a userid is defined with alias relating to user catalog. I am just trying to understand if it is possible to move all the users dataset catalogued under master catalogue to a user catalogue since the Number of datasets are in big number. Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Fwd: User datasets wrongly catalogued under Master Catalogue
I think the reference is to REPRO MERGECAT... doubt that will help here. Might be easiest to use DF/DSS to dump/delete datasets, then establish the proper catalogue alias, then RESTORE/catalogue the files. I imagine FDR can do the same thing. I was looking at a piece of software here called T-Rex (by Dino-soft), but all it would help with is an INTEGRITYCHECK command to compare catalogues and verify the alias' are all correct and accounted for. Ant. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Jake anderson Sent: Wednesday, 29 February 2012 5:25 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Fwd: User datasets wrongly catalogued under Master Catalogue Robert, I am unable to find any Information on MIGRATECAT on google search.. Is there someone who can point me to some Fine manuals relating to MIGRATCAT? Jake On Wed, Feb 29, 2012 at 1:04 PM, Vernooij, CP - SPLXM kees.verno...@klm.com wrote: Paul Gilmartin paulgboul...@aim.com wrote in message news:5467422117818390.wa.paulgboulderaim@bama.ua.edu... On Wed, 29 Feb 2012 09:14:36 +0530, Jake anderson wrote: typo - it happens when a userid is *not* defined with alias relating to user catalog. To my understanding, that's half right. It happens when a userid is *not* defined with alias relating to user catalog _and_ the master catalog is *not* suitably protected. I have a question on terminology: someone stated here lately that user catalogs are ancient history; no longer used. Is this so? If so, how are user data sets catalogued? -- gil This was probably about CVOL catalogs, I remember this remark. Kees. For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Fwd: User datasets wrongly catalogued under Master Catalogue
Just uncat them (with nscr) define the alias, recat. No need to mess with the data itself. See RCNVTCAT on the cbt. And yes, it works on SMS datasets as well. You'll need to massage the file RCNVTCAT generates so as not to hit innocent bystanders, but its just a mindless edit. Feed the file into IDCAMS. Worked fine last time I had to do it - a while ago admittedly. Shane ... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Fwd: User datasets wrongly catalogued under Master Catalogue
REPRO MERGECAT will certainly work, but Shane's also correct if the datasets aren't SMS. Even if they are SMS, with proper authority, you could DELETE dsn NOSCRATCH and DEFINE RECATALOG If it was me, I'd use MERGECAT (I have that job already in my library) unless it was a really large number of datasets, then since I have CR+, I'd use it. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Anthony Thompson Sent: Wednesday, February 29, 2012 12:11 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Fwd: User datasets wrongly catalogued under Master Catalogue I think the reference is to REPRO MERGECAT... doubt that will help here. Might be easiest to use DF/DSS to dump/delete datasets, then establish the proper catalogue alias, then RESTORE/catalogue the files. I imagine FDR can do the same thing. I was looking at a piece of software here called T-Rex (by Dino-soft), but all it would help with is an INTEGRITYCHECK command to compare catalogues and verify the alias' are all correct and accounted for. Ant. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Jake anderson Sent: Wednesday, 29 February 2012 5:25 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Fwd: User datasets wrongly catalogued under Master Catalogue Robert, I am unable to find any Information on MIGRATECAT on google search.. Is there someone who can point me to some Fine manuals relating to MIGRATCAT? Jake On Wed, Feb 29, 2012 at 1:04 PM, Vernooij, CP - SPLXM kees.verno...@klm.com wrote: Paul Gilmartin paulgboul...@aim.com wrote in message news:5467422117818390.wa.paulgboulderaim@bama.ua.edu... On Wed, 29 Feb 2012 09:14:36 +0530, Jake anderson wrote: typo - it happens when a userid is *not* defined with alias relating to user catalog. To my understanding, that's half right. It happens when a userid is *not* defined with alias relating to user catalog _and_ the master catalog is *not* suitably protected. I have a question on terminology: someone stated here lately that user catalogs are ancient history; no longer used. Is this so? If so, how are user data sets catalogued? -- gil This was probably about CVOL catalogs, I remember this remark. Kees. For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 - - For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: User datasets wrongly catalogued under Master Catalogue
Hi, Recently We have installed a new system Z/OS 1.13. During migration the Users datasets were restored and unfortunately all the user datasets are catalogued under Master catalogue. I agree that this happens when a userid is defined with alias relating to user catalog. I am just trying to understand if it is possible to move all the users dataset catalogued under master catalogue to a user catalogue since the Number of datasets are in big number. Jake If the datasets are not migrated, then you can use DFDSS to dump/delete, create the alias, restore the files with CATALOG. If they are migrated, then recall them, DFDSS dump/delete, create the alias, restore with CATALOG option. If they are migrated and you cannot recall them, then keep the list of migrated files, and recover them with DFHSM after you correct the alias. I do not think you can do a repromergcat if the alias does not already exist. This should work. I have used this technique in the past. Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: User datasets wrongly catalogued under Master Catalogue
You can also use IDCAMS MERGECAT to move the catalog entries and then define the ALIAS(s). -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Lizette Koehler Sent: Wednesday, February 29, 2012 7:34 AM To: IBM-MAIN@bama.ua.edu Subject: Re: User datasets wrongly catalogued under Master Catalogue Hi, Recently We have installed a new system Z/OS 1.13. During migration the Users datasets were restored and unfortunately all the user datasets are catalogued under Master catalogue. I agree that this happens when a userid is defined with alias relating to user catalog. I am just trying to understand if it is possible to move all the users dataset catalogued under master catalogue to a user catalogue since the Number of datasets are in big number. Jake If the datasets are not migrated, then you can use DFDSS to dump/delete, create the alias, restore the files with CATALOG. If they are migrated, then recall them, DFDSS dump/delete, create the alias, restore with CATALOG option. If they are migrated and you cannot recall them, then keep the list of migrated files, and recover them with DFHSM after you correct the alias. I do not think you can do a repromergcat if the alias does not already exist. This should work. I have used this technique in the past. Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: User datasets wrongly catalogued under Master Catalogue
Yes, it is possible to move files cataloged to the master onto an alias under a user catalog. It's been a while since I've done this but you probably have to define an alias different from the first level of your files. For example, if you have files, aaa.bbb that are defined to the master; then, the new alias can't be aaa; it has to be something different like aa1. Once the new alias has been defined, then the catalog pointers need to be merged onto the new user cat. If you have a utility such as TREX or Catalog Solutions, these utilities make this work much easier but IDCAMS can also do the merge of these records. Being user files, you may be able to just rename the files to your new alias provided these are not in use and there are no VSAM files involved; you can't rename a VSAM to an alias that's in a different catalog than the original vsam. Thanks, Hervey -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Jake anderson Sent: Tuesday, February 28, 2012 10:45 PM To: IBM-MAIN@bama.ua.edu Subject: Fwd: User datasets wrongly catalogued under Master Catalogue I agree that this happens when a userid is defined with alias relating to user catalog. typo - it happens when a userid is *not* defined with alias relating to user catalog. -- Forwarded message -- From: Jake anderson justmainfra...@gmail.com Date: Wed, Feb 29, 2012 at 9:11 AM Subject: User datasets wrongly catalogued under Master Catalogue To: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Hi, Recently We have installed a new system Z/OS 1.13. During migration the Users datasets were restored and unfortunately all the user datasets are catalogued under Master catalogue. I agree that this happens when a userid is defined with alias relating to user catalog. I am just trying to understand if it is possible to move all the users dataset catalogued under master catalogue to a user catalogue since the Number of datasets are in big number. Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: User datasets wrongly catalogued under Master Catalogue
Responses to a question with different opinions about the best way to solve a problem are nothing new to this list. But the amount of misinformation you received for a relatively simple question probably sets a high water mark I hope we don't challenge ever again. Fortunately you did recieve some workable solutions. The REPRO MERGECAT command reference is in the Access Methods Services manual. If you need further explanatory material, see the Managing Catalogs manual. The DSS commands are described in the DFSMSdss Storage Administration manual. - Original Message - From: Jake anderson justmainfra...@gmail.com To: IBM-MAIN@bama.ua.edu Sent: Tuesday, February 28, 2012 9:44:36 PM Subject: Fwd: User datasets wrongly catalogued under Master Catalogue I agree that this happens when a userid is defined with alias relating to user catalog. typo - it happens when a userid is *not* defined with alias relating to user catalog. -- Forwarded message -- From: Jake anderson justmainfra...@gmail.com Date: Wed, Feb 29, 2012 at 9:11 AM Subject: User datasets wrongly catalogued under Master Catalogue To: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Hi, Recently We have installed a new system Z/OS 1.13. During migration the Users datasets were restored and unfortunately all the user datasets are catalogued under Master catalogue. I agree that this happens when a userid is defined with alias relating to user catalog. I am just trying to understand if it is possible to move all the users dataset catalogued under master catalogue to a user catalogue since the Number of datasets are in big number. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: User datasets wrongly catalogued under Master Catalogue
On 2/29/2012 6:43 AM, Martin, Larry D wrote: You can also use IDCAMS MERGECAT to move the catalog entries and then define the ALIAS(s). Here is a sample to do it. //MOVCAT JOB //* //PRINT EXEC PGM=IDCAMS //* //SYSPRINT DD SYSOUT=A //SYSIN DD * REPRO - LEVEL(@ ) - INDATASET(CATALOG.MSTCAT) - OUTDATASET(CATALOG.USRCAT) - MERGECAT DEFINE ALIAS(NAME(@ ) - RELATE(CATALOG.USRCAT)) - CAT(CATALOG.MSTCAT) -- Richard -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Fwd: User datasets wrongly catalogued under Master Catalogue
At 13:24 +0530 on 02/29/2012, Jake anderson wrote about Re: Fwd: User datasets wrongly catalogued under Master Cata: Robert, I am unable to find any Information on MIGRATECAT on google search.. Is there someone who can point me to some Fine manuals relating to MIGRATCAT? Jake OOPS - As Dave Gibney responded the command I was thinking of is MERGECAT. I mistyped/misremembered the command name but had the right idea. I did however add the or something like that caveat to cover the wrong name case. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
User datasets wrongly catalogued under Master Catalogue
Hi, Recently We have installed a new system Z/OS 1.13. During migration the Users datasets were restored and unfortunately all the user datasets are catalogued under Master catalogue. I agree that this happens when a userid is defined with alias relating to user catalog. I am just trying to understand if it is possible to move all the users dataset catalogued under master catalogue to a user catalogue since the Number of datasets are in big number. Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Fwd: User datasets wrongly catalogued under Master Catalogue
I agree that this happens when a userid is defined with alias relating to user catalog. typo - it happens when a userid is *not* defined with alias relating to user catalog. -- Forwarded message -- From: Jake anderson justmainfra...@gmail.com Date: Wed, Feb 29, 2012 at 9:11 AM Subject: User datasets wrongly catalogued under Master Catalogue To: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Hi, Recently We have installed a new system Z/OS 1.13. During migration the Users datasets were restored and unfortunately all the user datasets are catalogued under Master catalogue. I agree that this happens when a userid is defined with alias relating to user catalog. I am just trying to understand if it is possible to move all the users dataset catalogued under master catalogue to a user catalogue since the Number of datasets are in big number. Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: User datasets wrongly catalogued under Master Catalogue
At 09:11 +0530 on 02/29/2012, Jake anderson wrote about User datasets wrongly catalogued under Master Catalogue: Hi, Recently We have installed a new system Z/OS 1.13. During migration the Users datasets were restored and unfortunately all the user datasets are catalogued under Master catalogue. I agree that this happens when a userid is defined with alias relating to user catalog. I am just trying to understand if it is possible to move all the users dataset catalogued under master catalogue to a user catalogue since the Number of datasets are in big number. Jake I seem to have an impression that there is a command called MIGRATECAT (or something like that) which will move the catalog entries from one catalog to another. If you follow that by a define of the alias you should get your desired result). Assuming that I am correct the only Gotcha is if the command will accept a From Here On wild card (ie: HLQ.* means ALL Datasets and Clusters under HLQ no matter how many levels). -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Fwd: User datasets wrongly catalogued under Master Catalogue
On Wed, 29 Feb 2012 09:14:36 +0530, Jake anderson wrote: typo - it happens when a userid is *not* defined with alias relating to user catalog. To my understanding, that's half right. It happens when a userid is *not* defined with alias relating to user catalog _and_ the master catalog is *not* suitably protected. I have a question on terminology: someone stated here lately that user catalogs are ancient history; no longer used. Is this so? If so, how are user data sets catalogued? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: User datasets wrongly catalogued under Master Catalogue
Still: we do not allow a restore/recall to update the Master catalog, we rather let it fail to clearly indicate the problem. Kees. Jake anderson justmainfra...@gmail.com wrote in message news:cahtvvruffawfixnbt4uch3a4xuzftwxoop82sqzzqhzhjzc...@mail.gmail.com ... I agree that this happens when a userid is defined with alias relating to user catalog. typo - it happens when a userid is *not* defined with alias relating to user catalog. -- Forwarded message -- From: Jake anderson justmainfra...@gmail.com Date: Wed, Feb 29, 2012 at 9:11 AM Subject: User datasets wrongly catalogued under Master Catalogue To: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Hi, Recently We have installed a new system Z/OS 1.13. During migration the Users datasets were restored and unfortunately all the user datasets are catalogued under Master catalogue. I agree that this happens when a userid is defined with alias relating to user catalog. I am just trying to understand if it is possible to move all the users dataset catalogued under master catalogue to a user catalogue since the Number of datasets are in big number. Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Fwd: User datasets wrongly catalogued under Master Catalogue
Paul Gilmartin paulgboul...@aim.com wrote in message news:5467422117818390.wa.paulgboulderaim@bama.ua.edu... On Wed, 29 Feb 2012 09:14:36 +0530, Jake anderson wrote: typo - it happens when a userid is *not* defined with alias relating to user catalog. To my understanding, that's half right. It happens when a userid is *not* defined with alias relating to user catalog _and_ the master catalog is *not* suitably protected. I have a question on terminology: someone stated here lately that user catalogs are ancient history; no longer used. Is this so? If so, how are user data sets catalogued? -- gil This was probably about CVOL catalogs, I remember this remark. Kees. For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Fwd: User datasets wrongly catalogued under Master Catalogue
Robert, I am unable to find any Information on MIGRATECAT on google search.. Is there someone who can point me to some Fine manuals relating to MIGRATCAT? Jake On Wed, Feb 29, 2012 at 1:04 PM, Vernooij, CP - SPLXM kees.verno...@klm.com wrote: Paul Gilmartin paulgboul...@aim.com wrote in message news:5467422117818390.wa.paulgboulderaim@bama.ua.edu... On Wed, 29 Feb 2012 09:14:36 +0530, Jake anderson wrote: typo - it happens when a userid is *not* defined with alias relating to user catalog. To my understanding, that's half right. It happens when a userid is *not* defined with alias relating to user catalog _and_ the master catalog is *not* suitably protected. I have a question on terminology: someone stated here lately that user catalogs are ancient history; no longer used. Is this so? If so, how are user data sets catalogued? -- gil This was probably about CVOL catalogs, I remember this remark. Kees. For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
