That depends on how you cataloged them. But I suspect that the the OP is not using SYMBOLICRELATE.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 LinkedIn as sme...@gmu.edu ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of retired mainframer <retired-mainfra...@q.com> Sent: Wednesday, November 29, 2017 11:42 AM To: IBM-MAIN@listserv.ua.edu Subject: Re: How to use master catalog as user catalog in another system If you copied the product datasets from a SYSA volume to a SYSB volume and then attempt to use the SYSA catalog to access them from SYSB, you will end up accessing the datasets on the SYSA volume. Since you went through the effort to copy them, I assume this is not desirable. Without specifying a vol-ser on all your DD statements, the only way to access the datasets on the SYSB volume is to have catalog entries that point to the SYSB volume. You can use ISPF 3.4 to list the datasets on the SYSB volume and issue the appropriate ISPF or IDCAMS commands to create those catalog entries in the SYSB catalog. As others have pointed out, it is a good idea to restrict the master catalog to system datasets and place product and user datasets in one or more user catalogs. However, unless you want SYSB to access the datasets on the SYSA volume, this would have no effect on your current effort. It does not matter if the catalog entry for a dataset is in the master or a user catalog. If the entry points to a SYSA volume, any allocation that uses that catalog entry will find the dataset on the SYSA volume. There are way for a catalog entry to point to different volumes based on which system is performing the allocation (for example, using a system symbol for the volume) but that is a whole new discussion. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of johnnydeep san > Sent: Wednesday, November 29, 2017 6:27 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: How to use master catalog as user catalog in another system > > Thanks, Tom and Lizette for your quick response . > > Lizette, I'm trying this in sanbox where i will going to run my product > which was installed already in SYSA , i would like to use all the product > dataset's in SYSB for testing .I alredy > transferred VOLUME(contain all product dataset) to sysB . though i have > volume i'm not able to fetch the dataset since they are not cataloged. So > i thought of going alternate master catalog . > > > + JD + > > > > > On Wed, Nov 29, 2017 at 8:41 AM, Lizette Koehler > <stars...@mindspring.com> > wrote: > > > What problem are you trying to solve? > > > > Creating an alt master cat and importing it to a new system may only fix > > some of your issues. > > > > Consider the master catalog like the ROOT in Unix. It controls where > > things can be found in z/OS. It is the key to the IPL Process. If > > anything is not correct in the MCAT then an IPL may not work. > > > > > > There is a manual on working with catalogs. And if this is not a sandbox > > - that is - if this system cannot take outages if there are issues you > > should take care there could be challenges by doing this. > > > > It helps if you have a system programmer sandbox when working with > > catalogs. This is an environment where if things get broken, there is not > > impact to other work going on in the shop. > > > > > > If there are issues with your catalog, you may need to IPL or other > > activities to fix it. For example - catalog recovery processes > > > > If you are not the system programmer, you should contact the one at your > > shop. They can help you with your activities and reduce potential > > problems. This list does not know your shop or your configuration. It can > > only provide guidance based on information provided. You system > programmer > > can be better at helping you with these types of questions. > > > > When you import the master cat from another system, you cannot not see > all > > of the datasets. Anything currently cataloged on the new system in the > > MasterCat may not be seen. > > > > If you want datasets that are in the MCAT on SYSA on SYSB and you want > are > > SYS1.** datasets, then you may not see them on SYSB. > > > > A catalog is a tree structure. MCAT entries over ride UCAT (user catalog) > > entries. > > > > IMPORT CONNECT does - > > > > https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1. > > 0/com.ibm.zos.v2r1.idai200/toc.htm > > > > The IMPORT command moves or restores a cluster or alternate index, or > > restores a catalog. Import a Catalog: Example 2 > > > > https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1. > > 0/com.ibm.zos.v2r1.idai200/imicf.htm > > > > In this example, a catalog, USERCAT4, that was previously exported, is > > imported. (See the EXPORT example, Export a Catalog: Example 1.) The > > original copy of USERCAT4 is replaced with the imported copy, from the > > portable file copy in CATBACK. Access method services finds and deletes > the > > duplicate name, USERCAT4. Any aliases in the master catalog for USERCAT4 > > are preserved. (A duplicate name exists because the catalog was exported > > with the TEMPORARY attribute.) Access method services then redefines > > USERCAT4, using the catalog information from the portable file, CATBACK. > > USERCAT4 is locked to prevent access to anyone except authorized > recovery > > personnel. > > > > Another search for CONNECT MASTER CATALOG in www.ibm.com > produces many > > hits > > > > https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1. > > 0/com.ibm.zos.v2r1.e0zb100/migrtas.htm > > > > Migrating to another system section in z/OS Planning manual. This section > > only lists actions you need to take to move a copy of software from one > > system to another. It does not list the actions needed to install and > > migrate new levels of software. For that information, see other > > documentation such as z/OS Migration. > > > > > > > > > > I went to www.ibm.com and searched on CATALOG MASTERCAT > > > > http://www- > 01.ibm.com/support/docview.wss?crawler=1&uid=isg3T1019473 > > > > http://www-01.ibm.com/support/docview.wss?uid=isg1II13354 > > > > And many other hits. > > > > I went to > http://www.redbooks.ibm.com/redbooks.nsf/searchsite?SearchView > > > > And searched on CATALOG in the REDBOOK site on IBM. > > > > Many hits that will be helpful > > > > http://www.redbooks.ibm.com/abstracts/sg248262.html?Open > > > > http://www.redbooks.ibm.com/abstracts/redp4212.html?Open > > > > http://www.redbooks.ibm.com/abstracts/sg246983.html?Open ** > There > > are a series of Redbooks called ABC and ABCs and they explain a lot of the > > functions in z/OS and how to work with them > > > > http://www.redbooks.ibm.com/abstracts/sg246105.html?Open > > > > > > > > There are many more. > > > > Lizette > > > > > > > > > > > -----Original Message----- > > > From: IBM Mainframe Discussion List [mailto:IBM- > m...@listserv.ua.edu] On > > > Behalf Of johnnydeep san > > > Sent: Wednesday, November 29, 2017 5:16 AM > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > Subject: How to use master catalog as user catalog in another system > > > > > > Hi Team, > > > > > > As a newbie for mainframe, i may ask simple question but i couldn't track > > > right answer in google :) . > > > > > > > > > I have create alternate master catalog on volume ALTVOL1 on SYSA. > Please > > > guide me , how to use this alternate master catalog of SYSA as a > > usercatalog > > > in another system SYSB? . since both are different system , Will import > > > catalog works ?. > > > > > > > > > + JD + > > > > > > > ---------------------------------------------------------------------- > > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
