Re: SMS Dataset Alloc Issue
Hello, Thanks for help. But I still have once confusion is, When I am trying to delete the Data component of these datset, for which cluster part is not visible , system is not allowing me to delete. I get error DATASET not Found. I think, I am getting this error because that particular datset is not part of current master catalog. But if Still I want to delete the data component I created, Can you please help to perform this task. Regards Saurabh On Sat, May 26, 2012 at 10:23 AM, retired mainframer retired-mainfra...@q.com wrote: You misinterpreted. If the dataset is not catalogued in the normal search order, you have to tell DSLIST to search all the catalogs. The way to do this is to specify a wild card as the HLQ, include any additional qualifiers to limit the output, and NOT specify a volume. In the example you posted, try **.SMS.SCDS. If you specify the Display Catalog Name option, it will be easy to see which cluster came from MCATB and which components belong to that cluster. (This assumes SOZ1D.MASTER.CATALOG is connected to your current master catalog. Reasonable since otherwise your define would have failed.) :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On :: Behalf Of saurabh khandelwal :: Sent: Friday, May 25, 2012 5:24 AM :: To: IBM-MAIN@bama.ua.edu :: Subject: Re: SMS Dataset Alloc Issue :: :: Hello Group, :: Walter has clarified my doubt that I am trying :: to :: see a cluster cataloged under MCATB from a system whose master catalog :: is :: MCATA. Then, it is perfectly normal to see only the data part of the :: cluster. So I will be able to see cluster+data only when I logon on :: thesystem whose master catalog is MCATB. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- Thanks Regards Saurabh Khandelwal -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: SMS Dataset Alloc Issue
Hello, Thanks for help. But I still have once confusion is, When I am trying to delete the Data component of these datset, for which cluster part is not visible , system is not allowing me to delete. I get error DATASET not Found. I think, I am getting this error because that particular datset is not part of current master catalog. But if Still I want to delete the data component I created, Can you please help to perform this task. Regards Saurabh Some questions 1) Is the catalog where this SYS1.SMS.SCDS is cataloged a USER CAT on the system you are trying to do the display? 2) Is the system where the SYS1.SMS.SCDS is cataloged - up or able to be IPL'D? If you have system up with MCATA and MCATB is a usercat in MCATA then you may be able to delete the dataset with the CATALOG parm in IDCAMS DEL. If you can bring up the system where MCATB is the Master Cat then you can do the changes from the running system IIRC SETSMS command can point SMS to different SCDS or ACDS datasets. So if you have a running system that you can logon, then you can fix from that system. Or could you create a new SYS1.SMS2.SCDS dataset to the correct MCAT and then update the SYS1.PARMLIB member to point to the new SCDS dataset and IPL? You may have several options to correct this issue. Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: SMS Dataset Alloc Issue
And since no one else seems to have mentioned it yet, this whole thread is an excellent argument for NOT using a SYS1. high level for naming installation datasets you want system-specific, like the this SCDS dataset -- instead using some unique high-level qualifier associated with the master catalog of each system, say MCTA and MCTB. Then you can simply create and maintain your installation System-B datasets from System-A by temporarily connecting the System-B MCAT as a User Catalog to System-A and defining MCTB (in System-A MCAT) as an ALIAS pointing to the System-B MCAT. With those conventions and working with datasets with an MCTB high-level from System-A, everything gets correctly pointed to the System-B MCAT without having to play any bizarre games, and utilities like ISPF 3.4 will behave more predictably as well. When System-B is up and running on its Master Catalog, there will be no ALIAS for MCTB defined in the System-B MCAT, so a search for MCTB.anything from System-B would default to the System-B Master Catalog. J C Ewing On 05/26/2012 12:12 PM, Lizette Koehler wrote: Hello, Thanks for help. But I still have once confusion is, When I am trying to delete the Data component of these datset, for which cluster part is not visible , system is not allowing me to delete. I get error DATASET not Found. I think, I am getting this error because that particular datset is not part of current master catalog. But if Still I want to delete the data component I created, Can you please help to perform this task. Regards Saurabh Some questions 1) Is the catalog where this SYS1.SMS.SCDS is cataloged a USER CAT on the system you are trying to do the display? 2) Is the system where the SYS1.SMS.SCDS is cataloged - up or able to be IPL'D? If you have system up with MCATA and MCATB is a usercat in MCATA then you may be able to delete the dataset with the CATALOG parm in IDCAMS DEL. If you can bring up the system where MCATB is the Master Cat then you can do the changes from the running system IIRC SETSMS command can point SMS to different SCDS or ACDS datasets. So if you have a running system that you can logon, then you can fix from that system. Or could you create a new SYS1.SMS2.SCDS dataset to the correct MCAT and then update the SYS1.PARMLIB member to point to the new SCDS dataset and IPL? You may have several options to correct this issue. Lizette ... -- Joel C. Ewing,Bentonville, AR jcew...@acm.org -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: SMS Dataset Alloc Issue
You do not delete the data component. You delete the cluster. You do so using Access Methods Services (aka IDCAMS) by specifying both the fully qualified DSN and the catalog where that DSN can be found. If you have problems show us the job and the IDCAMS output. :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On :: Behalf Of saurabh khandelwal :: Sent: Saturday, May 26, 2012 8:48 AM :: To: IBM-MAIN@bama.ua.edu :: Subject: Re: SMS Dataset Alloc Issue :: :: Hello, ::Thanks for help. But I still have once confusion is, When I :: am :: trying to delete the Data component of these datset, for which cluster :: part :: is not visible , system is not allowing me to delete. I get error :: DATASET :: not Found. :: :: I think, I am getting this error because that particular datset is not :: part :: of current master catalog. But if Still I want to delete the data :: component :: I created, :: Can you please help to perform this task. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
SMS Dataset Alloc Issue
Hello Group, I have used below JCL to allocate SMS dataset. But when I checked, JCL has created only data part not cluster part of the dataset. not sure why it has happened. I tried ISPF 3.4 against volume. Only Data part is visible. //SMSALOC JOB (660),SAURABH, // CLASS=A,NOTIFY=SYSUID, // MSGCLASS=A //* //ALLOC EXEC PGM=IDCAMS,REGION=512K //DDSOZ1D1 DD DISP=OLD,UNIT=SYSALLDA,VOL=SER=SOZ1D1 //SYSPRINT DD SYSOUT=* //SYSINDD * /* ALLOCATE SCDS */ DEFINE CLUSTER( - NAME(SYS1.SMS.SCDS)- LINEAR - VOLUMES(SOZ1D1)- TRK(6 6) - SHAREOPTIONS(2,3) - ) - DATA( - NAME(SYS1.SMS.SCDS.DATA) - ) - CATALOG(SOZ1D.MASTER.CATALOG) /* ALLOCATE ACDS */ DEFINE CLUSTER( - NAME(SYS1.SMS.ACDS)- LINEAR - VOLUMES(SOZ1D1)- TRK(6 6) - SHAREOPTIONS(3,3) - ) - DATA( - NAME(SYS1.SMS.ACDS.DATA) - ) - CATALOG(SOZ1D.MASTER.CATALOG) /* ALLOCATE COMMDS */ DEFINE CLUSTER( - NAME(SYS1.SMS.COMMDS) - LINEAR - VOLUMES(SOZ1D1)- TRK(1 1) - SHAREOPTIONS(3,3) - ) - DATA( - NAME(SYS1.SMS.COMMDS.DATA) - ) - CATALOG(SOZ1D.MASTER.CATALOG) /* // -- Thanks Regards Saurabh -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN 1 J E S 2 J O B L O G -- S Y S T E M M V S 9 -- N O D E J E S S U P 0 00.09.35 JOB00712 THURSDAY, 24 MAY 2012 00.09.35 JOB00712 IRR010I USERID SKHAND9 IS ASSIGNED TO THIS JOB. 00.09.35 JOB00712 ICH70001I SKHAND9 LAST ACCESS AT 23:54:22 ON WEDNESDAY, MAY 23, 2012 00.09.35 JOB00712 $HASP373 SMSALOC STARTED - INIT BASE - CLASS A - SYS MVS9 00.09.35 JOB00712 IEF403I SMSALOC - STARTED - TIME=00.09.35 00.09.35 JOB00712 - -TIMINGS (MINS.)-- -PAGING COUNTS 00.09.35 JOB00712 -STEPNAME PROCSTEPRC EXCP CONN TCB SRB CLOCK SERV WORKLOAD PAGE SWAP VIO SWAPS 00.09.35 JOB00712 -ALLOC00105 52 .00 .00 .0 7006 SYSTEM 0 0 0 0 00.09.35 JOB00712 IEF404I SMSALOC - ENDED - TIME=00.09.35 00.09.35 JOB00712 -SMSALOC ENDED. NAME-SAURABH TOTAL TCB CPU TIME= .00 TOTAL ELAPSED TIME=.0 00.09.35 JOB00712 $HASP395 SMSALOC ENDED 0-- JES2 JOB STATISTICS -- - 24 MAY 2012 JOB EXECUTION DATE - 51 CARDS READ - 110 SYSOUT PRINT RECORDS -0 SYSOUT PUNCH RECORDS -5 SYSOUT SPOOL KBYTES - 0.00 MINUTES EXECUTION TIME 1 //SMSALOC JOB (660),SAURABH, JOB00712 // CLASS=A,NOTIFY=SYSUID, // MSGCLASS=A //* IEFC653I SUBSTITUTION JCL - (660),SAURABH,CLASS=A,NOTIFY=SKHAND9,MSGCLASS=A 2 //ALLOC EXEC PGM=IDCAMS,REGION=512K 3 //DDSOZ1D1 DD DISP=OLD,UNIT=SYSALLDA,VOL=SER=SOZ1D1 4 //SYSPRINT DD SYSOUT=* 5 //SYSINDD * ICH70001I SKHAND9 LAST ACCESS AT 23:54:22 ON WEDNESDAY, MAY 23, 2012 IEF236I ALLOC. FOR SMSALOC ALLOC IEF237I 6137 ALLOCATED TO DDSOZ1D1 IEF237I JES2 ALLOCATED TO SYSPRINT IEF237I JES2 ALLOCATED TO SYSIN IEF237I 6137 ALLOCATED TO SYS1 IEF285I SYS12145.T000935.RA000.SMSALOC.R0138041 KEPT IEF285I VOL SER NOS= SOZ1D1. IEF237I 6137 ALLOCATED TO SYS2 IEF285I SYS12145.T000935.RA000.SMSALOC.R0138042 KEPT IEF285I VOL SER NOS= SOZ1D1. IEF237I 6137 ALLOCATED TO SYS3 IEF285I SYS12145.T000935.RA000.SMSALOC.R0138043 KEPT IEF285I VOL SER NOS= SOZ1D1. IEF142I SMSALOC ALLOC - STEP WAS EXECUTED - COND CODE IEF285I SYS12145.T000935.RA000.SMSALOC.R0138040 KEPT IEF285I VOL SER NOS= SOZ1D1. IEF285I SKHAND9.SMSALOC.JOB00712.D102.? SYSOUT IEF285I SKHAND9.SMSALOC.JOB00712.D101.? SYSIN IEF373I STEP/ALLOC /START 2012145.0009 IEF032I STEP/ALLOC /STOP 2012145.0009 CPU:
Re: SMS Dataset Alloc Issue
From: saurabh khandelwal sourabhkhandelwal...@gmail.com I tried ISPF 3.4 against volume. Only Data part is visible. Saurabh, are you sure you cataloged the VSAM under the correct master catalog ? Walter Marguccio z/OS Systems Programmer BELENUS LOB Informatic GmbH Munich - Germany -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: SMS Dataset Alloc Issue
Were you looking at a catalog search or did you specify the volume serial on the 3.4 screen? Thank You, Dave O'Brien From: Walter Marguccio [walter_marguc...@yahoo.com] Sent: Friday, May 25, 2012 7:06 AM To: IBM-MAIN@bama.ua.edu Subject: Re: SMS Dataset Alloc Issue From: saurabh khandelwal sourabhkhandelwal...@gmail.com I tried ISPF 3.4 against volume. Only Data part is visible. Saurabh, are you sure you cataloged the VSAM under the correct master catalog ? Walter Marguccio z/OS Systems Programmer BELENUS LOB Informatic GmbH Munich - Germany -- 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: SMS Dataset Alloc Issue
Saurabh, By specifying the volume, you will only see the DATA. The CLUSTER part is just a catalog entry, not a physical dataset. (Yeah, guys, I know, but let's keep it simple, OK?) Leave off the VOLUME on ISPF 3.4, and you will see both the Cluster and Data portions. Cheers,,,Steve Steven F. Conway, CISSP LA Systems z/OS Systems Support Phone: 703.295.1926 steve_con...@ao.uscourts.gov From: saurabh khandelwal sourabhkhandelwal...@gmail.com To: IBM-MAIN@bama.ua.edu Date: 05/25/2012 06:49 AM Subject:SMS Dataset Alloc Issue Sent by:IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Hello Group, I have used below JCL to allocate SMS dataset. But when I checked, JCL has created only data part not cluster part of the dataset. not sure why it has happened. I tried ISPF 3.4 against volume. Only Data part is visible. //SMSALOC JOB (660),SAURABH, // CLASS=A,NOTIFY=SYSUID, // MSGCLASS=A //* //ALLOC EXEC PGM=IDCAMS,REGION=512K //DDSOZ1D1 DD DISP=OLD,UNIT=SYSALLDA,VOL=SER=SOZ1D1 //SYSPRINT DD SYSOUT=* //SYSINDD * /* ALLOCATE SCDS */ DEFINE CLUSTER( - NAME(SYS1.SMS.SCDS)- LINEAR - VOLUMES(SOZ1D1)- TRK(6 6) - SHAREOPTIONS(2,3) - ) - DATA( - NAME(SYS1.SMS.SCDS.DATA) - ) - CATALOG(SOZ1D.MASTER.CATALOG) /* ALLOCATE ACDS */ DEFINE CLUSTER( - NAME(SYS1.SMS.ACDS)- LINEAR - VOLUMES(SOZ1D1)- TRK(6 6) - SHAREOPTIONS(3,3) - ) - DATA( - NAME(SYS1.SMS.ACDS.DATA) - ) - CATALOG(SOZ1D.MASTER.CATALOG) /* ALLOCATE COMMDS */ DEFINE CLUSTER( - NAME(SYS1.SMS.COMMDS) - LINEAR - VOLUMES(SOZ1D1)- TRK(1 1) - SHAREOPTIONS(3,3) - ) - DATA( - NAME(SYS1.SMS.COMMDS.DATA) - ) - CATALOG(SOZ1D.MASTER.CATALOG) /* // -- Thanks Regards Saurabh -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN [attachment SMS.txt deleted by Steve Conway/DCA/AO/USCOURTS] -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: SMS Dataset Alloc Issue
I see you are specifying a catalog too. Why? Are you sure you are using the correct catalog? If not, you wont see it either. _ Dave Jousma Assistant Vice President, Mainframe Services david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Steve Conway Sent: Friday, May 25, 2012 8:16 AM To: IBM-MAIN@bama.ua.edu Subject: Re: SMS Dataset Alloc Issue Saurabh, By specifying the volume, you will only see the DATA. The CLUSTER part is just a catalog entry, not a physical dataset. (Yeah, guys, I know, but let's keep it simple, OK?) Leave off the VOLUME on ISPF 3.4, and you will see both the Cluster and Data portions. Cheers,,,Steve Steven F. Conway, CISSP LA Systems z/OS Systems Support Phone: 703.295.1926 steve_con...@ao.uscourts.gov From: saurabh khandelwal sourabhkhandelwal...@gmail.com To: IBM-MAIN@bama.ua.edu Date: 05/25/2012 06:49 AM Subject:SMS Dataset Alloc Issue Sent by:IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Hello Group, I have used below JCL to allocate SMS dataset. But when I checked, JCL has created only data part not cluster part of the dataset. not sure why it has happened. I tried ISPF 3.4 against volume. Only Data part is visible. //SMSALOC JOB (660),SAURABH, // CLASS=A,NOTIFY=SYSUID, // MSGCLASS=A //* //ALLOC EXEC PGM=IDCAMS,REGION=512K //DDSOZ1D1 DD DISP=OLD,UNIT=SYSALLDA,VOL=SER=SOZ1D1 //SYSPRINT DD SYSOUT=* //SYSINDD * /* ALLOCATE SCDS */ DEFINE CLUSTER( - NAME(SYS1.SMS.SCDS)- LINEAR - VOLUMES(SOZ1D1)- TRK(6 6) - SHAREOPTIONS(2,3) - ) - DATA( - NAME(SYS1.SMS.SCDS.DATA) - ) - CATALOG(SOZ1D.MASTER.CATALOG) /* ALLOCATE ACDS */ DEFINE CLUSTER( - NAME(SYS1.SMS.ACDS)- LINEAR - VOLUMES(SOZ1D1)- TRK(6 6) - SHAREOPTIONS(3,3) - ) - DATA( - NAME(SYS1.SMS.ACDS.DATA) - ) - CATALOG(SOZ1D.MASTER.CATALOG) /* ALLOCATE COMMDS */ DEFINE CLUSTER( - NAME(SYS1.SMS.COMMDS) - LINEAR - VOLUMES(SOZ1D1)- TRK(1 1) - SHAREOPTIONS(3,3) - ) - DATA( - NAME(SYS1.SMS.COMMDS.DATA) - ) - CATALOG(SOZ1D.MASTER.CATALOG) /* // -- Thanks Regards Saurabh -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN [attachment SMS.txt deleted by Steve Conway/DCA/AO/USCOURTS] -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: SMS Dataset Alloc Issue
The original define only explicitly named the data component. The index got a system generated name. LISTCAT the cluster and you should see the data component you named and the name that was generated for the index. Doug -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of O'Brien, David W. (NIH/CIT) [C] Sent: Friday, May 25, 2012 7:14 AM To: IBM-MAIN@bama.ua.edu Subject: Re: SMS Dataset Alloc Issue Were you looking at a catalog search or did you specify the volume serial on the 3.4 screen? Thank You, Dave O'Brien From: Walter Marguccio [walter_marguc...@yahoo.com] Sent: Friday, May 25, 2012 7:06 AM To: IBM-MAIN@bama.ua.edu Subject: Re: SMS Dataset Alloc Issue From: saurabh khandelwal sourabhkhandelwal...@gmail.com I tried ISPF 3.4 against volume. Only Data part is visible. Saurabh, are you sure you cataloged the VSAM under the correct master catalog ? Walter Marguccio z/OS Systems Programmer BELENUS LOB Informatic GmbH Munich - Germany -- 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: SMS Dataset Alloc Issue
Hello Group, Walter has clarified my doubt that I am trying to see a cluster cataloged under MCATB from a system whose master catalog is MCATA. Then, it is perfectly normal to see only the data part of the cluster. So I will be able to see cluster+data only when I logon on thesystem whose master catalog is MCATB. Thanks for helping me . Regards Saurabh On Fri, May 25, 2012 at 5:48 PM, Jousma, David david.jou...@53.com wrote: I see you are specifying a catalog too. Why? Are you sure you are using the correct catalog? If not, you wont see it either. _ Dave Jousma Assistant Vice President, Mainframe Services david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Steve Conway Sent: Friday, May 25, 2012 8:16 AM To: IBM-MAIN@bama.ua.edu Subject: Re: SMS Dataset Alloc Issue Saurabh, By specifying the volume, you will only see the DATA. The CLUSTER part is just a catalog entry, not a physical dataset. (Yeah, guys, I know, but let's keep it simple, OK?) Leave off the VOLUME on ISPF 3.4, and you will see both the Cluster and Data portions. Cheers,,,Steve Steven F. Conway, CISSP LA Systems z/OS Systems Support Phone: 703.295.1926 steve_con...@ao.uscourts.gov From: saurabh khandelwal sourabhkhandelwal...@gmail.com To: IBM-MAIN@bama.ua.edu Date: 05/25/2012 06:49 AM Subject:SMS Dataset Alloc Issue Sent by:IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Hello Group, I have used below JCL to allocate SMS dataset. But when I checked, JCL has created only data part not cluster part of the dataset. not sure why it has happened. I tried ISPF 3.4 against volume. Only Data part is visible. //SMSALOC JOB (660),SAURABH, // CLASS=A,NOTIFY=SYSUID, // MSGCLASS=A //* //ALLOC EXEC PGM=IDCAMS,REGION=512K //DDSOZ1D1 DD DISP=OLD,UNIT=SYSALLDA,VOL=SER=SOZ1D1 //SYSPRINT DD SYSOUT=* //SYSINDD * /* ALLOCATE SCDS */ DEFINE CLUSTER( - NAME(SYS1.SMS.SCDS)- LINEAR - VOLUMES(SOZ1D1)- TRK(6 6) - SHAREOPTIONS(2,3) - ) - DATA( - NAME(SYS1.SMS.SCDS.DATA) - ) - CATALOG(SOZ1D.MASTER.CATALOG) /* ALLOCATE ACDS */ DEFINE CLUSTER( - NAME(SYS1.SMS.ACDS)- LINEAR - VOLUMES(SOZ1D1)- TRK(6 6) - SHAREOPTIONS(3,3) - ) - DATA( - NAME(SYS1.SMS.ACDS.DATA) - ) - CATALOG(SOZ1D.MASTER.CATALOG) /* ALLOCATE COMMDS */ DEFINE CLUSTER( - NAME(SYS1.SMS.COMMDS) - LINEAR - VOLUMES(SOZ1D1)- TRK(1 1) - SHAREOPTIONS(3,3) - ) - DATA( - NAME(SYS1.SMS.COMMDS.DATA) - ) - CATALOG(SOZ1D.MASTER.CATALOG) /* // -- Thanks Regards Saurabh -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN [attachment SMS.txt deleted by Steve Conway/DCA/AO/USCOURTS] -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu
Re: SMS Dataset Alloc Issue
You misinterpreted. If the dataset is not catalogued in the normal search order, you have to tell DSLIST to search all the catalogs. The way to do this is to specify a wild card as the HLQ, include any additional qualifiers to limit the output, and NOT specify a volume. In the example you posted, try **.SMS.SCDS. If you specify the Display Catalog Name option, it will be easy to see which cluster came from MCATB and which components belong to that cluster. (This assumes SOZ1D.MASTER.CATALOG is connected to your current master catalog. Reasonable since otherwise your define would have failed.) :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On :: Behalf Of saurabh khandelwal :: Sent: Friday, May 25, 2012 5:24 AM :: To: IBM-MAIN@bama.ua.edu :: Subject: Re: SMS Dataset Alloc Issue :: :: Hello Group, :: Walter has clarified my doubt that I am trying :: to :: see a cluster cataloged under MCATB from a system whose master catalog :: is :: MCATA. Then, it is perfectly normal to see only the data part of the :: cluster. So I will be able to see cluster+data only when I logon on :: thesystem whose master catalog is MCATB. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
