Re: catalog a vsam dataset in another catalog ?
In of018fe9f8.a2375a62-on852576d2.0073f0aa-852576d2.00744...@uscmail.uscourts.gov, on 02/22/2010 at 04:10 PM, John Kelly john_j_ke...@ao.uscourts.gov said: I know that I have SYS1 HLQ page DSNs, rather than PAGE, but I haven't been able to simple recatalog the page DSNs since 1.7, I also don't understand how you could use them while the other system is up, Why not, as long as the other system isn't using them? -- 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: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
In 42a1afad1002220649x5499e22vf319f85f3bec8...@mail.gmail.com, on 02/22/2010 at 09:49 AM, larry macioce mace1...@gmail.com said: Is there a way to do this? Just copy it with a new name; it doesn't have to be cataloged in the COD master catalog in order for IPL to use it. If you want the ability to update it from either system then recatalog it in the COD master catalog; that will only work if you use the SYS1 HLQ. -- 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: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
(I hate this... now there is a mixture of top posting and bottom posting, but since you went top last, I will do the same thing). So how does that support your statement - a PAGESPACE, regardless of the name, can exist in multiple catalogs at the same time? I already stated there was special code for SYS1 *and* PAGE HLQs to be cataloged in multiple catalogs at the same time. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ On Mon, 22 Feb 2010 14:39:25 -0600, McKown, John john.mck...@healthmarkets.com wrote: My page datasets all start with PAGE.SYSNAME..LOCALnn and so on. When I replace an image, I just do a DEF PAGESPACE(NAME(PAGE.LIH1.COMMON) - FILE(MVSPG3) VOL(MVSPG3) RECATALOG) - CAT(CATALOG.ICF.newmastercat) I don this while they are still in use on the currently running system. And I don't do a REPORT MERGECAT or anything else. -- John McKown Systems Engineer IV IT -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mark Zelden Sent: Monday, February 22, 2010 1:18 PM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? On Mon, 22 Feb 2010 12:43:47 -0600, McKown, John john.mck...@healthmarkets.com wrote: -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Staller, Allan Sent: Monday, February 22, 2010 12:35 PM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? snip Also SYS1 has the special attribute of DEFINE RECATALOG allowing the definition of the same dataset in 2 different catalogs (just like non-VSAMS datasdest). This only applies to datasets with the HLQ of SYS1. /snip I meant to add that with the exception of SYS1, a VSAM dataset can only exist in 1 catalog at a time. HTH, Actually a PAGESPACE, regardless of the name, can exist in multiple catalogs at the same time too. I do that all the time. Are you sure? I thought the special code in DFSMS was only for SYS1 and PAGE HLQs. Although I've never tried to define a page data set with any other HLQ than SYS1 or PAGE. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
Mark, It's not the HLQ, all page datasets can be RECATALOGed, regardless of the name. Mark Zelden mzel...@flash.net 2/23/2010 9:52 AM (I hate this... now there is a mixture of top posting and bottom posting, but since you went top last, I will do the same thing). So how does that support your statement - a PAGESPACE, regardless of the name, can exist in multiple catalogs at the same time? I already stated there was special code for SYS1 *and* PAGE HLQs to be cataloged in multiple catalogs at the same time. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ On Mon, 22 Feb 2010 14:39:25 -0600, McKown, John john.mck...@healthmarkets.com wrote: My page datasets all start with PAGE.SYSNAME..LOCALnn and so on. When I replace an image, I just do a DEF PAGESPACE(NAME(PAGE.LIH1.COMMON) - FILE(MVSPG3) VOL(MVSPG3) RECATALOG) - CAT(CATALOG.ICF.newmastercat) I don this while they are still in use on the currently running system. And I don't do a REPORT MERGECAT or anything else. -- John McKown Systems Engineer IV IT -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mark Zelden Sent: Monday, February 22, 2010 1:18 PM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? On Mon, 22 Feb 2010 12:43:47 -0600, McKown, John john.mck...@healthmarkets.com wrote: -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Staller, Allan Sent: Monday, February 22, 2010 12:35 PM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? snip Also SYS1 has the special attribute of DEFINE RECATALOG allowing the definition of the same dataset in 2 different catalogs (just like non-VSAMS datasdest). This only applies to datasets with the HLQ of SYS1. /snip I meant to add that with the exception of SYS1, a VSAM dataset can only exist in 1 catalog at a time. HTH, Actually a PAGESPACE, regardless of the name, can exist in multiple catalogs at the same time too. I do that all the time. Are you sure? I thought the special code in DFSMS was only for SYS1 and PAGE HLQs. Although I've never tried to define a page data set with any other HLQ than SYS1 or PAGE. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
Thanks. I wonder if I always had this information wrong (that only SYS1 and PAGE HLQs had special treatment) or if something change at some point. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ On Tue, 23 Feb 2010 11:36:41 -0500, Scott Rowe scott.r...@joann.com wrote: Mark, It's not the HLQ, all page datasets can be RECATALOGed, regardless of the name. Mark Zelden mzel...@flash.net 2/23/2010 9:52 AM (I hate this... now there is a mixture of top posting and bottom posting, but since you went top last, I will do the same thing). So how does that support your statement - a PAGESPACE, regardless of the name, can exist in multiple catalogs at the same time? I already stated there was special code for SYS1 *and* PAGE HLQs to be cataloged in multiple catalogs at the same time. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ On Mon, 22 Feb 2010 14:39:25 -0600, McKown, John john.mck...@healthmarkets.com wrote: My page datasets all start with PAGE.SYSNAME..LOCALnn and so on. When I replace an image, I just do a DEF PAGESPACE(NAME(PAGE.LIH1.COMMON) - FILE(MVSPG3) VOL(MVSPG3) RECATALOG) - CAT(CATALOG.ICF.newmastercat) I don this while they are still in use on the currently running system. And I don't do a REPORT MERGECAT or anything else. -- John McKown Systems Engineer IV IT -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mark Zelden Sent: Monday, February 22, 2010 1:18 PM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? On Mon, 22 Feb 2010 12:43:47 -0600, McKown, John john.mck...@healthmarkets.com wrote: -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Staller, Allan Sent: Monday, February 22, 2010 12:35 PM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? snip Also SYS1 has the special attribute of DEFINE RECATALOG allowing the definition of the same dataset in 2 different catalogs (just like non-VSAMS datasdest). This only applies to datasets with the HLQ of SYS1. /snip I meant to add that with the exception of SYS1, a VSAM dataset can only exist in 1 catalog at a time. HTH, Actually a PAGESPACE, regardless of the name, can exist in multiple catalogs at the same time too. I do that all the time. Are you sure? I thought the special code in DFSMS was only for SYS1 and PAGE HLQs. Although I've never tried to define a page data set with any other HLQ than SYS1 or PAGE. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
Things changed. The ability to control which catalog was used (via JOBCAT, STEPCAT, INCAT, etc) was sharply curtailed. The whole process of building a system had to change. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mark Zelden Sent: Tuesday, February 23, 2010 12:40 PM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? Thanks. I wonder if I always had this information wrong (that only SYS1 and PAGE HLQs had special treatment) or if something change at some point. Mark -- NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
I'm not sure how long it's been this way, but I can say for sure that it worked this way in about 1999, because I know I used it then. Mark Zelden mzel...@flash.net 2/23/2010 1:39 PM Thanks. I wonder if I always had this information wrong (that only SYS1 and PAGE HLQs had special treatment) or if something change at some point. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ On Tue, 23 Feb 2010 11:36:41 -0500, Scott Rowe scott.r...@joann.com wrote: Mark, It's not the HLQ, all page datasets can be RECATALOGed, regardless of the name. Mark Zelden mzel...@flash.net 2/23/2010 9:52 AM (I hate this... now there is a mixture of top posting and bottom posting, but since you went top last, I will do the same thing). So how does that support your statement - a PAGESPACE, regardless of the name, can exist in multiple catalogs at the same time? I already stated there was special code for SYS1 *and* PAGE HLQs to be cataloged in multiple catalogs at the same time. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ On Mon, 22 Feb 2010 14:39:25 -0600, McKown, John john.mck...@healthmarkets.com wrote: My page datasets all start with PAGE.SYSNAME..LOCALnn and so on. When I replace an image, I just do a DEF PAGESPACE(NAME(PAGE.LIH1.COMMON) - FILE(MVSPG3) VOL(MVSPG3) RECATALOG) - CAT(CATALOG.ICF.newmastercat) I don this while they are still in use on the currently running system. And I don't do a REPORT MERGECAT or anything else. -- John McKown Systems Engineer IV IT -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mark Zelden Sent: Monday, February 22, 2010 1:18 PM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? On Mon, 22 Feb 2010 12:43:47 -0600, McKown, John john.mck...@healthmarkets.com wrote: -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Staller, Allan Sent: Monday, February 22, 2010 12:35 PM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? snip Also SYS1 has the special attribute of DEFINE RECATALOG allowing the definition of the same dataset in 2 different catalogs (just like non-VSAMS datasdest). This only applies to datasets with the HLQ of SYS1. /snip I meant to add that with the exception of SYS1, a VSAM dataset can only exist in 1 catalog at a time. HTH, Actually a PAGESPACE, regardless of the name, can exist in multiple catalogs at the same time too. I do that all the time. Are you sure? I thought the special code in DFSMS was only for SYS1 and PAGE HLQs. Although I've never tried to define a page data set with any other HLQ than SYS1 or PAGE. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email
Re: catalog a vsam dataset in another catalog ?
On Tue, 23 Feb 2010 16:18:31 -0500, Scott Rowe scott.r...@joann.com wrote: I'm not sure how long it's been this way, but I can say for sure that it worked this way in about 1999, because I know I used it then. I assume based on this APAR below from 1992 that it had always been that way and I just remembered it wrong as PAGE.* instead of all pagespace. Probably a combination of that and the fact that I've never seen anything used but SYS1 and PAGE as HLQs for page data sets at every shop I've been at. APAR Identifier .. OY51398 Last Changed 95/04/03 GET MSGIDC3009I RC86 RC10 RECATALOGING NON SYS1 SMS IPL DATA SETS INTO A DIFFERENT MASTER CATALOG. OR RSN22 RC22 Symptom .. DD MSGIDC3009I Status ... CLOSED DOC Severity ... 4 Date Closed . 92/04/01 Component .. 566528418 Duplicate of Reported Release . 320 Fixed Release Component Name DFP/XA ICF CAT/ Special Notice Current Target Date .. Flags SCP ... Platform Status Detail: Not Available PE PTF List: PTF List: Parent APAR: Child APAR list: ERROR DESCRIPTION: RECATALOG OF SMS NON SYS1 IPL DATA SET INTO A DIFFERENT MASTER CATALOG FAILS WITH MSGIDC3009I RC86 RC10 IGG0CLEJ or rc22 rsn22 NON SMS NON SYS1 IPL DATA SETS ARE ABLE TO GET RECATALOGED INTO MULTIPLE CATALOGS. GC281828, SC264500 AND SC264659 MANUALS WILL BE CHANGED TO DOCUMENT THE RESTRICTIONS ON NON SYS1 SMS MANAGED IPL SYSTEM DATA SETS. LOCAL FIX: PROBLEM SUMMARY: * USERS AFFECTED: USERS OF HDP3310 AND UP * * PROBLEM DESCRIPTION: RECATALOG OF A DATASET THAT IS * * NOT A SWAPSPACE, PAGESPACE OR * * A SYS1 DATASET INTO A DIFFERENT * * MASTER CATALOG FAILS WITH * * MSGIDC3009I RC86 RC10. * * RECOMMENDATION: UPDATE MANUALS. * A DATASET MUST BE RECATALOGED INTO A CATALOG WITH THE SAME CATALOG NAME SPECIFIED IN THE VVR OR NVR UNLESS IT IS A PAGESPACE, SWAPSPACE OR SYS1 DATASET. THIS RESTRICTION IS NOT EXPLICITLY STATED IN THE DOCUMENTATION. PROBLEM CONCLUSION: RECATALOG OF NON SYS1 IPL DATASET INTO A DIFFERENT MASTER CATALOG FAILS WITH MSGIDC3009I RC86 RC10. A DATASET MUST BE RECATALOGED INTO THE CATALOG WITH THE SAME CATALOG NAME IN THE VVR OR NVR UNLESS IT IS A PAGESPACE, SWAPSPACE OR SYS1 DATASET. THIS RESTRICTION IS NOT EXPLICITLY STATED IN THE DOCUMENTATION. . THE AMS ICF REFERENCE (SC26456202) WILL BE UPDATED UNDER DEFINE CLUSTER RECATALOG PARAMETER TO STATE 'CATALOG ENTRIES CAN ONLY BE RECREATED IN THE CATALOG SPECIFIED IN THE VVR UNLESS THEY ARE A SWAPSPACE, PAGESPACE OR SYS1 DATASET. . THE AMS ICF REFERENCE (SC26456202) WILL BE UPDATED UNDER DEFINE NONVSAM RECATALOG PARAMETER TO STATE 'CATALOG ENTRIES CAN ONLY BE RECREATED IN THE CATALOG SPECIFIED IN THE NVR UNLESS THEY ARE A SWAPSPACE, PAGESPACE OR SYS1 DATASET. IN A MULTIHOST ENVIRONMENT, NON SYS1 SMS IPL DATASETS CANNOT BE RECATALOGED TO A DIFFERENT CATALOG THAN THE ONE IN THE NVR. IN A MULTIHOST ENVIRONMENT, ALL SMS IPL DATASETS THAT ARE TO BE SHARED MUST BE SYS1 DATASETS. . MVS/DFP MANAGING CATALOGS (SC26455502) WILL BE UPDATED UNDER 'RECATALOGING DATA SETS AND VSAM OBJECTS' TO STATE 'DATASETS CAN ONLY BE RECATALOGED INTO THE CATALOG SPECIFIED IN THE VVR/NVR WITH THE EXCEPTION OF PAGESPACE, SWAPSPACE OR SYS1 DATA SETS.'. . THE MVS/ESA INITIALIZATION AND TUNING REFERENCE (GC28163500) UNDER LNKLSTXX (LINK LIBRARY LIST) USE OF MEMBER UNDER LNKLSTXX (LINK LIBRARY LIST) USE OF MEMBER NOTE 2 WILL BE MODIFIED TO STATE 'NON SYS1 LINK LIBRARIES THAT ARE SMS MANAGED CANNOT BE SHARED MULTIPLE SYSTEMS.'. . THE MVS/ESA INITIALIZATION AND TUNING REFERENCE (GC28163500) UNDER LPALSTXX (LPA LIBRARY LIST) USE OF MEMBER UNDER LPALSTXX (LPA LIBRARY LIST) USE OF MEMBER NOTE 2 WILL BE MODIFIED TO STATE 'NON SYS1 LPA LIBRARIES THAT ARE SMS MANAGED CANNOT BE SHARED AMONG MULTIPLE SYSTEMS.'. . IN THE MVS/ESA STORAGE MANAGEMENT SUBSYSTEM MIGRATION PLANNING GUIDE (SC26465900) UNDER 'MULTIHOST ENVIRONMENT', A PARAGRAPH WILL BE ADDED TO STATE 'IF LPA OR LINK DATA SETS THAT ARE SMS MANAGED ARE TO BE SHARED THEY MUST BE SYS1 DATA SETS.'. . THE MVS/ESA MESSAGE LIBRARY SYSTEM MESSAGES VOLUME 1 (GC28165601) FOR MESSAGE IDC3009I RETURN CODE 86 REASON CODE 10 (RC86 RC10),THE DESCRIPTION WILL BE REPLACED TO STATE 'CATALOG ENTRIES CAN ONLY BE RECATALOGED IN THE
Re: catalog a vsam dataset in another catalog ?
I don't think I've ever seen any page datasets named other than SYS1 or PAGE either, but I remember reading the doc back in 1999. Mark Zelden mzel...@flash.net 02/23/10 4:49 PM On Tue, 23 Feb 2010 16:18:31 -0500, Scott Rowe scott.r...@joann.com wrote: I'm not sure how long it's been this way, but I can say for sure that it worked this way in about 1999, because I know I used it then. I assume based on this APAR below from 1992 that it had always been that way and I just remembered it wrong as PAGE.* instead of all pagespace. Probably a combination of that and the fact that I've never seen anything used but SYS1 and PAGE as HLQs for page data sets at every shop I've been at. APAR Identifier .. OY51398 Last Changed 95/04/03 GET MSGIDC3009I RC86 RC10 RECATALOGING NON SYS1 SMS IPL DATA SETS INTO A DIFFERENT MASTER CATALOG. OR RSN22 RC22 Symptom .. DD MSGIDC3009I Status ... CLOSED DOC Severity ... 4 Date Closed . 92/04/01 Component .. 566528418 Duplicate of Reported Release . 320 Fixed Release Component Name DFP/XA ICF CAT/ Special Notice Current Target Date .. Flags SCP ... Platform Status Detail: Not Available PE PTF List: PTF List: Parent APAR: Child APAR list: ERROR DESCRIPTION: RECATALOG OF SMS NON SYS1 IPL DATA SET INTO A DIFFERENT MASTER CATALOG FAILS WITH MSGIDC3009I RC86 RC10 IGG0CLEJ or rc22 rsn22 NON SMS NON SYS1 IPL DATA SETS ARE ABLE TO GET RECATALOGED INTO MULTIPLE CATALOGS. GC281828, SC264500 AND SC264659 MANUALS WILL BE CHANGED TO DOCUMENT THE RESTRICTIONS ON NON SYS1 SMS MANAGED IPL SYSTEM DATA SETS. LOCAL FIX: PROBLEM SUMMARY: * USERS AFFECTED: USERS OF HDP3310 AND UP * * PROBLEM DESCRIPTION: RECATALOG OF A DATASET THAT IS * * NOT A SWAPSPACE, PAGESPACE OR * * A SYS1 DATASET INTO A DIFFERENT * * MASTER CATALOG FAILS WITH * * MSGIDC3009I RC86 RC10. * * RECOMMENDATION: UPDATE MANUALS. * A DATASET MUST BE RECATALOGED INTO A CATALOG WITH THE SAME CATALOG NAME SPECIFIED IN THE VVR OR NVR UNLESS IT IS A PAGESPACE, SWAPSPACE OR SYS1 DATASET. THIS RESTRICTION IS NOT EXPLICITLY STATED IN THE DOCUMENTATION. PROBLEM CONCLUSION: RECATALOG OF NON SYS1 IPL DATASET INTO A DIFFERENT MASTER CATALOG FAILS WITH MSGIDC3009I RC86 RC10. A DATASET MUST BE RECATALOGED INTO THE CATALOG WITH THE SAME CATALOG NAME IN THE VVR OR NVR UNLESS IT IS A PAGESPACE, SWAPSPACE OR SYS1 DATASET. THIS RESTRICTION IS NOT EXPLICITLY STATED IN THE DOCUMENTATION. . THE AMS ICF REFERENCE (SC26456202) WILL BE UPDATED UNDER DEFINE CLUSTER RECATALOG PARAMETER TO STATE 'CATALOG ENTRIES CAN ONLY BE RECREATED IN THE CATALOG SPECIFIED IN THE VVR UNLESS THEY ARE A SWAPSPACE, PAGESPACE OR SYS1 DATASET. . THE AMS ICF REFERENCE (SC26456202) WILL BE UPDATED UNDER DEFINE NONVSAM RECATALOG PARAMETER TO STATE 'CATALOG ENTRIES CAN ONLY BE RECREATED IN THE CATALOG SPECIFIED IN THE NVR UNLESS THEY ARE A SWAPSPACE, PAGESPACE OR SYS1 DATASET. IN A MULTIHOST ENVIRONMENT, NON SYS1 SMS IPL DATASETS CANNOT BE RECATALOGED TO A DIFFERENT CATALOG THAN THE ONE IN THE NVR. IN A MULTIHOST ENVIRONMENT, ALL SMS IPL DATASETS THAT ARE TO BE SHARED MUST BE SYS1 DATASETS. . MVS/DFP MANAGING CATALOGS (SC26455502) WILL BE UPDATED UNDER 'RECATALOGING DATA SETS AND VSAM OBJECTS' TO STATE 'DATASETS CAN ONLY BE RECATALOGED INTO THE CATALOG SPECIFIED IN THE VVR/NVR WITH THE EXCEPTION OF PAGESPACE, SWAPSPACE OR SYS1 DATA SETS.'. . THE MVS/ESA INITIALIZATION AND TUNING REFERENCE (GC28163500) UNDER LNKLSTXX (LINK LIBRARY LIST) USE OF MEMBER UNDER LNKLSTXX (LINK LIBRARY LIST) USE OF MEMBER NOTE 2 WILL BE MODIFIED TO STATE 'NON SYS1 LINK LIBRARIES THAT ARE SMS MANAGED CANNOT BE SHARED MULTIPLE SYSTEMS.'. . THE MVS/ESA INITIALIZATION AND TUNING REFERENCE (GC28163500) UNDER LPALSTXX (LPA LIBRARY LIST) USE OF MEMBER UNDER LPALSTXX (LPA LIBRARY LIST) USE OF MEMBER NOTE 2 WILL BE MODIFIED TO STATE 'NON SYS1 LPA LIBRARIES THAT ARE SMS MANAGED CANNOT BE SHARED AMONG MULTIPLE SYSTEMS.'. . IN THE MVS/ESA STORAGE MANAGEMENT SUBSYSTEM MIGRATION PLANNING GUIDE (SC26465900) UNDER 'MULTIHOST ENVIRONMENT', A PARAGRAPH WILL BE ADDED TO STATE 'IF LPA OR LINK DATA SETS THAT ARE SMS MANAGED ARE TO BE SHARED THEY MUST BE SYS1 DATA SETS.'. . THE MVS/ESA MESSAGE LIBRARY SYSTEM MESSAGES
Re: catalog a vsam dataset in another catalog ?
Yes. Just put it on the RES volume and craft your load parameters accordingly. There is no mention of catalog requirements in the GA22-7525-12 HCD planning guide. The planning guide has a discussion on how the IPL parms, PARMLIB, and the IODF are located during IPL. Another way is to connect the COD master cat as a usercat. Define datasets using a suitable HLQ then later ALTER them to their target SYS1 names. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of larry macioce Sent: Monday, February 22, 2010 8:49 AM To: IBM-MAIN@bama.ua.edu Subject: catalog a vsam dataset in another catalog ? At first this sounds easy but let me explain: I am working on putting up a COD..not the fish as we are coming from an unsupported z/os . I'd like to use my current IODF (or even the previous one) but herein lies the problem. I DON'T want to let the COD touch my catalog as it is interwined with my production catalog...not I didn't do this someone else had the bright idea. So what i want to do is copy the IODF and place it on the COD res pack WITHOUT bringing up the COD(as it wouldn't work anyway) Is there a way to do this? thanks mace NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
You need to do an export of the system it is on and import it to the catalog that you want it to be in. Here is sample JCL: //IODF16DD DSN=SMULLER.IODF16,UNIT=SYSALLDA, // SPACE=(TRK,(14,1)),DISP=(,CATLG) //IODF DD DSN=SYS1.IODF16.CLUSTER,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSINDD * EXPORT SYS1.IODF16.CLUSTER TEMPORARY - INFILE(IODF)- OUTFILE(IODF16) Follow with an Import: //IODF16DD DSN=SMULLER.IODF16,UNIT=SYSALLDA, // SPACE=(TRK,(14,1)),DISP=(,CATLG) //IODF DD DSN=SYS1.IODF16.CLUSTER,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSINDD * EXPORT SYS1.IODF16.CLUSTER TEMPORARY - INFILE(IODF)- OUTFILE(IODF16) I hope this helps. Pat Mihalec Rush University Medical Center Senior System Programmer (312) 942-8386 pat_miha...@rush.edu P Please consider the environment before printing this email. From: larry macioce mace1...@gmail.com To: IBM-MAIN@bama.ua.edu Date: 02/22/2010 08:49 AM Subject: catalog a vsam dataset in another catalog ? Sent by: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu At first this sounds easy but let me explain: I am working on putting up a COD..not the fish as we are coming from an unsupported z/os . I'd like to use my current IODF (or even the previous one) but herein lies the problem. I DON'T want to let the COD touch my catalog as it is interwined with my production catalog...not I didn't do this someone else had the bright idea. So what i want to do is copy the IODF and place it on the COD res pack WITHOUT bringing up the COD(as it wouldn't work anyway) Is there a way to do this? thanks mace -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
Thanks to all who replied I have reread my instruction and I can ipl using an already defined iodf, but I'll have to put in the volser of the old system where the iodf resides. I am really creeped out about letting the CoD catalog and my old master cat talk to each other, that is the reason for asking. thanks mace On Mon, Feb 22, 2010 at 10:23 AM, Pat Mihalec pat_miha...@rush.edu wrote: You need to do an export of the system it is on and import it to the catalog that you want it to be in. Here is sample JCL: //IODF16DD DSN=SMULLER.IODF16,UNIT=SYSALLDA, // SPACE=(TRK,(14,1)),DISP=(,CATLG) //IODF DD DSN=SYS1.IODF16.CLUSTER,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSINDD * EXPORT SYS1.IODF16.CLUSTER TEMPORARY - INFILE(IODF)- OUTFILE(IODF16) Follow with an Import: //IODF16DD DSN=SMULLER.IODF16,UNIT=SYSALLDA, // SPACE=(TRK,(14,1)),DISP=(,CATLG) //IODF DD DSN=SYS1.IODF16.CLUSTER,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSINDD * EXPORT SYS1.IODF16.CLUSTER TEMPORARY - INFILE(IODF)- OUTFILE(IODF16) I hope this helps. Pat Mihalec Rush University Medical Center Senior System Programmer (312) 942-8386 pat_miha...@rush.edu P Please consider the environment before printing this email. From: larry macioce mace1...@gmail.com To: IBM-MAIN@bama.ua.edu Date: 02/22/2010 08:49 AM Subject: catalog a vsam dataset in another catalog ? Sent by: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu At first this sounds easy but let me explain: I am working on putting up a COD..not the fish as we are coming from an unsupported z/os . I'd like to use my current IODF (or even the previous one) but herein lies the problem. I DON'T want to let the COD touch my catalog as it is interwined with my production catalog...not I didn't do this someone else had the bright idea. So what i want to do is copy the IODF and place it on the COD res pack WITHOUT bringing up the COD(as it wouldn't work anyway) Is there a way to do this? thanks mace -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
snip So what i want to do is copy the IODF and place it on the COD res pack WITHOUT bringing up the COD(as it wouldn't work anyway) /snip Since the IODF is VSAM you'll need it catalogued. I find that the Alias HLQ to the COD catalog is the easiest way, just like you do with ServPac,etc. Then change your LOAD parms to point to the COD IODF and volume. Jack Kelly 202-502-2390 (Office) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
An IODF does not need to be cataloged in order to IPL with it. John Kelly john_j_ke...@ao.uscourts.gov 2/22/2010 11:03 AM snip So what i want to do is copy the IODF and place it on the COD res pack WITHOUT bringing up the COD(as it wouldn't work anyway) /snip Since the IODF is VSAM you'll need it catalogued. I find that the Alias HLQ to the COD catalog is the easiest way, just like you do with ServPac,etc. Then change your LOAD parms to point to the COD IODF and volume. Jack Kelly 202-502-2390 (Office) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
I believe that the IODF is one of the special cases that does not have to be cataloged. That said, I found that both the old and new IODF needs to be cataloged to perform a dynamic change. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of John Kelly Sent: Monday, February 22, 2010 10:04 AM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? snip So what i want to do is copy the IODF and place it on the COD res pack WITHOUT bringing up the COD(as it wouldn't work anyway) /snip Since the IODF is VSAM you'll need it catalogued. I find that the Alias HLQ to the COD catalog is the easiest way, just like you do with ServPac,etc. Then change your LOAD parms to point to the COD IODF and volume. Jack Kelly 202-502-2390 (Office) NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
snip-- At first this sounds easy but let me explain: I am working on putting up a COD..not the fish as we are coming from an unsupported z/os . I'd like to use my current IODF (or even the previous one) but herein lies the problem. I DON'T want to let the COD touch my catalog as it is interwined with my production catalog...not I didn't do this someone else had the bright idea. So what i want to do is copy the IODF and place it on the COD res pack WITHOUT bringing up the COD(as it wouldn't work anyway) Is there a way to do this? thanks mace --unsnip I may be wrong but ISTR we had a discussion about this several months ago. IIRC, SYS1 is a special case wherein a dataset or cluster may appear in more than one catalog. Somebody correct me if I'm wrong, please. Rick -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
IIRC, any attempt to catalog a SYS1 dataset will be forced to the current master. Locating a SYS1 dataset will always be done with the current master (unless explicit unit and vol ser is specified). SYS1 (as with any HLQ) can existing in any catalog. Getting a SYS1 entry in a usercat is a little tricky but not that hard. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Rick Fochtman Sent: Monday, February 22, 2010 10:54 AM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? snip-- --unsnip I may be wrong but ISTR we had a discussion about this several months ago. IIRC, SYS1 is a special case wherein a dataset or cluster may appear in more than one catalog. Somebody correct me if I'm wrong, please. Rick NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
-Original Message- From: IBM Mainframe Discussion List On Behalf Of Rick Fochtman snip-- At first this sounds easy but let me explain: I am working on putting up a COD..not the fish as we are coming from an unsupported z/os . I'd like to use my current IODF (or even the previous one) but herein lies the problem. I DON'T want to let the COD touch my catalog as it is interwined with my production catalog...not I didn't do this someone else had the bright idea. So what i want to do is copy the IODF and place it on the COD res pack WITHOUT bringing up the COD(as it wouldn't work anyway) Is there a way to do this? thanks mace --unsnip I may be wrong but ISTR we had a discussion about this several months ago. IIRC, SYS1 is a special case wherein a dataset or cluster may appear in more than one catalog. Somebody correct me if I'm wrong, please. It's true. We have several common SYS1.** datasets cataloged in each mastercat (yep, each LPAR still has its own mastercat). -jc- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
snip IIRC, any attempt to catalog a SYS1 dataset will be forced to the current master. /snip Not true. See the catalog operand of the IDCAMS DEFINE command snip Locating a SYS1 dataset will always be done with the current master (unless explicit unit and vol ser is specified). /snip True. Also SYS1 has the special attribute of DEFINE RECATALOG allowing the definition of the same dataset in 2 different catalogs (just like non-VSAMS datasdest). This only applies to datasets with the HLQ of SYS1. HTH, -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Hal Merritt Sent: Monday, February 22, 2010 11:29 AM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? IIRC, any attempt to catalog a SYS1 dataset will be forced to the current master. Locating a SYS1 dataset will always be done with the current master (unless explicit unit and vol ser is specified). SYS1 (as with any HLQ) can existing in any catalog. Getting a SYS1 entry in a usercat is a little tricky but not that hard. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Rick Fochtman Sent: Monday, February 22, 2010 10:54 AM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? snip-- --unsnip I may be wrong but ISTR we had a discussion about this several months ago. IIRC, SYS1 is a special case wherein a dataset or cluster may appear in more than one catalog. Somebody correct me if I'm wrong, please. Rick NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
snip Also SYS1 has the special attribute of DEFINE RECATALOG allowing the definition of the same dataset in 2 different catalogs (just like non-VSAMS datasdest). This only applies to datasets with the HLQ of SYS1. /snip I meant to add that with the exception of SYS1, a VSAM dataset can only exist in 1 catalog at a time. HTH, -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
On Mon, 22 Feb 2010 12:34:48 -0600, Staller, Allan allan.stal...@kbm1.com wrote: snip Also SYS1 has the special attribute of DEFINE RECATALOG allowing the definition of the same dataset in 2 different catalogs (just like non-VSAMS datasdest). This only applies to datasets with the HLQ of SYS1. /snip I meant to add that with the exception of SYS1, a VSAM dataset can only exist in 1 catalog at a time. And PAGE. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
Thanks for the update I did not know that ... snip I meant to add that with the exception of SYS1, a VSAM dataset can only exist in 1 catalog at a time. And PAGE. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
snip I meant to add that with the exception of SYS1, a VSAM dataset can only exist in 1 catalog at a time. /snip I must have missed this one too, when did IBM remove PAGE HLQ from this list? I thought that the original OP wanted to keep the COD separate from his running system, so I thought that the ServPac type Alias to his COD catalogue would be appropriate. I'm not sure how this thread went off into SYS1 but Jack Kelly 202-502-2390 (Office) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Staller, Allan Sent: Monday, February 22, 2010 12:35 PM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? snip Also SYS1 has the special attribute of DEFINE RECATALOG allowing the definition of the same dataset in 2 different catalogs (just like non-VSAMS datasdest). This only applies to datasets with the HLQ of SYS1. /snip I meant to add that with the exception of SYS1, a VSAM dataset can only exist in 1 catalog at a time. HTH, Actually a PAGESPACE, regardless of the name, can exist in multiple catalogs at the same time too. I do that all the time. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
-snip- snip I meant to add that with the exception of SYS1, a VSAM dataset can only exist in 1 catalog at a time. /snip I must have missed this one too, when did IBM remove PAGE HLQ from this list? I thought that the original OP wanted to keep the COD separate from his running system, so I thought that the ServPac type Alias to his COD catalogue would be appropriate. I'm not sure how this thread went off into SYS1 but unsnip One of our responders apperantly forgot that the page datasets are VSAM, by definition. :-) Rick -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
On Mon, 22 Feb 2010 12:43:47 -0600, McKown, John john.mck...@healthmarkets.com wrote: -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Staller, Allan Sent: Monday, February 22, 2010 12:35 PM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? snip Also SYS1 has the special attribute of DEFINE RECATALOG allowing the definition of the same dataset in 2 different catalogs (just like non-VSAMS datasdest). This only applies to datasets with the HLQ of SYS1. /snip I meant to add that with the exception of SYS1, a VSAM dataset can only exist in 1 catalog at a time. HTH, Actually a PAGESPACE, regardless of the name, can exist in multiple catalogs at the same time too. I do that all the time. Are you sure? I thought the special code in DFSMS was only for SYS1 and PAGE HLQs. Although I've never tried to define a page data set with any other HLQ than SYS1 or PAGE. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
My page datasets all start with PAGE.SYSNAME..LOCALnn and so on. When I replace an image, I just do a DEF PAGESPACE(NAME(PAGE.LIH1.COMMON) - FILE(MVSPG3) VOL(MVSPG3) RECATALOG) - CAT(CATALOG.ICF.newmastercat) I don this while they are still in use on the currently running system. And I don't do a REPORT MERGECAT or anything else. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mark Zelden Sent: Monday, February 22, 2010 1:18 PM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? On Mon, 22 Feb 2010 12:43:47 -0600, McKown, John john.mck...@healthmarkets.com wrote: -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Staller, Allan Sent: Monday, February 22, 2010 12:35 PM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? snip Also SYS1 has the special attribute of DEFINE RECATALOG allowing the definition of the same dataset in 2 different catalogs (just like non-VSAMS datasdest). This only applies to datasets with the HLQ of SYS1. /snip I meant to add that with the exception of SYS1, a VSAM dataset can only exist in 1 catalog at a time. HTH, Actually a PAGESPACE, regardless of the name, can exist in multiple catalogs at the same time too. I do that all the time. Are you sure? I thought the special code in DFSMS was only for SYS1 and PAGE HLQs. Although I've never tried to define a page data set with any other HLQ than SYS1 or PAGE. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
snip DEF PAGESPACE(NAME(PAGE.LIH1.COMMON) - FILE(MVSPG3) VOL(MVSPG3) RECATALOG) - CAT(CATALOG.ICF.newmastercat) /snip I know that I have SYS1 HLQ page DSNs, rather than PAGE, but I haven't been able to simple recatalog the page DSNs since 1.7, I also don't understand how you could use them while the other system is up, unless you reply to that page DSN was last used message each IPL. Jack Kelly 202-502-2390 (Office) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of John Kelly Sent: Monday, February 22, 2010 3:10 PM To: IBM-MAIN@bama.ua.edu Subject: Re: catalog a vsam dataset in another catalog ? snip DEF PAGESPACE(NAME(PAGE.LIH1.COMMON) - FILE(MVSPG3) VOL(MVSPG3) RECATALOG) - CAT(CATALOG.ICF.newmastercat) /snip I know that I have SYS1 HLQ page DSNs, rather than PAGE, but I haven't been able to simple recatalog the page DSNs since 1.7, I also don't understand how you could use them while the other system is up, unless you reply to that page DSN was last used message each IPL. Jack Kelly 202-502-2390 (Office) Hum, I don't know. This is what I did when I upgraded from 1.8 to 1.10. I had no problems. Created the 1.10 system. Brought down the 1.8. IPL'ed 1.10 in the same LPAR that 1.8 was in. Came up smooth as silk. Ref: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2c170/6.4.1 quote After a BCS recovery, some entries in the recovered BCS might not accurately reflect the current characteristics of a data set or VSAM object. The VVDS, VTOC, and tape labels should contain the accurate information for existing data sets. Data sets can only be recataloged into the catalog specified in the VVR/NVR unless they are pagespace, swapspace or SYS1 data sets. ... To recatalog a data set or VSAM object using the DEFINE RECATALOG command, the corresponding entries in the VVDS and VTOC must exist. This information is used to rebuild the BCS entries, along with information supplied in the command. Data sets can only be recataloged into the catalog specified in the VVR/NVR unless they are pagespace, swapspace or SYS1 data sets. /quote -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
Um, folks, we seems to be mixing apples and Iphones here. In this context, page files, IODF's, and master catalogs are not really VSAM. And, yes, the rules for the SYS1 HLQ are a little different. NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
On Mon, 2010-02-22 at 12:43 -0600, McKown, John wrote: I meant to add that with the exception of SYS1, a VSAM dataset can only exist in 1 catalog at a time. HTH, Actually a PAGESPACE, regardless of the name, can exist in multiple catalogs at the same time too. I do that all the time. Depends on environment. I seem to recall John John saying he runs separate MCATs - presumably not connected, and with (VSAM) volumes not shared between systems. In a single cat-plex I think you'll find SYS1 and PAGE are still the only exceptions. Shane ... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: catalog a vsam dataset in another catalog ?
On Mon, 2010-02-22 at 15:18 -0600, McKown, John wrote: -Original Message- On Behalf Of John Kelly I know that I have SYS1 HLQ page DSNs, rather than PAGE, but I haven't been able to simple recatalog the page DSNs since 1.7, I also don't understand how you could use them while the other system is up, unless you reply to that page DSN was last used message each IPL. Hum, I don't know. This is what I did when I upgraded from 1.8 to 1.10. I had no problems. Created the 1.10 system. Brought down the 1.8. IPL'ed 1.10 in the same LPAR that 1.8 was in. Came up smooth as silk. Again, I suspect you guys are talking at cross purposes. The lock-out mechanism page uses to protect the page dataset now that page datasets for multiple systems can be on the one volume is pretty simplistic. Dump the first page of a page dataset and have a look. If you bring up the same system, no problem - if another system attempts to use that datasets (currently used or not) you get the prompt. Don't know about the re-cat issue - but I may not have tried since 1.7. Shane ... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
