So, I just drafted sample JCL for SMF dataset recatalog.
//DDSMF001 DD DISP=OLD,UNIT=SYSALLDA,VOL=SER=SMF001
//SYSIN DD *
DEFINE CLUSTER( -
NAME(SYS1.SYS9.MAN1) -
VOLUMES(SMF001) -
FILE(DDSMF001) -
CONTROLINTERVALSIZE(4096) -
NONINDEXED -
RECORDSIZE(4086 32767) -
REUSE -
SHAREOPTIONS(2) -
SPANNED -
SPEED -
RECATALOG -
) -
DATA( -
CYLINDERS(60 0) -
) -
CATALOG(ZZ.MASTER.CATALOG)
Out of all these parameter, what are all we can remove and keep minimum to
define these SMF dataset under z/OS 2.1 as well.
On Wed, Jun 11, 2014 at 6:27 PM, Mainframe Mainframe <
[email protected]> wrote:
> Thanks .. Can we do same for SMS , STGINDEX, SMF MAN dataset all having
> HLQ as SYS1 with RECATALOG parameter.
>
>
>
>
> On Wed, Jun 11, 2014 at 6:17 PM, Pommier, Rex <[email protected]>
> wrote:
>
>> No, this JCL is recataloging a currently-existing page dataset into your
>> new master catalog. You would use SPACE if you were creating a new page
>> dataset.
>>
>> Rex
>>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List [mailto:[email protected]] On
>> Behalf Of Mainframe Mainframe
>> Sent: Wednesday, June 11, 2014 7:38 AM
>> To: [email protected]
>> Subject: Re: Dataset in Two master catalog
>>
>> Thanks for reply . By seeing this sample JCL you provided,
>>
>> //PAGESPCE EXEC PGM=IDCAMS
>> //SYSPRINT DD SYSOUT=*
>> //SYSIN DD *
>> DEFINE PAGESPACE( -
>> NAME(PAGE.BUBBA.COMMON) -
>> FILE(VOLSER) -
>> VOL(volser) -
>> RECATALOG) -
>> CAT(new.master.catalog)
>>
>> /*
>> //VOLSER DD DISP=OLD,UNIT=SYSDA,VOL=SER=volser
>>
>>
>> Don't I have to use space parameter while defining common dataset. Please
>> suggest.
>>
>>
>> On Wed, Jun 11, 2014 at 5:32 PM, John McKown <
>> [email protected]>
>> wrote:
>>
>> > This might help:
>> >
>> http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2c180/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.
>> > </quote>
>> >
>> > Now, this is not really all that clear, but basically it means that a
>> > PAGESPACE or any type of VSAM file whose DSN starts with SYS1. can be
>> > simultaneously cataloged in multiple z/OS ICF (normal) catalogs. So all
>> you
>> > need to do for something like a PAGESPACE data set in your z/OS 2.1
>> master
>> > catalog, run a job like
>> >
>> > //PAGESPCE EXEC PGM=IDCAMS
>> > //SYSPRINT DD SYSOUT=*
>> > //SYSIN DD *
>> > DEFINE PAGESPACE( -
>> > NAME(PAGE.BUBBA.COMMON) -
>> > FILE(VOLSER) -
>> > VOL(volser) -
>> > RECATALOG) -
>> > CAT(new.master.catalog)
>> > /*
>> > //VOLSER DD DISP=OLD,UNIT=SYSDA,VOL=SER=volser
>> >
>> > The above works for _any_ page space, regardless of the DSN. And it
>> works
>> > for any VSAM file whose name starts with SYS1. Such as SYS1.BUBBA.MAN1
>> >
>> >
>> > On Wed, Jun 11, 2014 at 5:36 AM, Mainframe Mainframe <
>> > [email protected]> wrote:
>> >
>> > > Hello,
>> > > We want some of the system dataset like
>> page,SMF,STGINDEX,SMS
>> > > need to be reused with my newly installed Z/OS(z/OS 2.1) .
>> > >
>> > > This means that we want to use page,SMF,STGINDEX,SMS dataset used by
>> > z/OS
>> > > 1.13 system currently and cataloged under master catalog of z/OS 1.13
>> > will
>> > > be used by z/OS 2.1 and z/OS 1.13 will be shutdown.
>> > >
>> > > I tried checking on some of the manual and found that we can use
>> > recatalog
>> > > option for doing this, but I am still not 100% sure. Also I am not
>> sure,
>> > > why do we have to use DEFINE PAGESPAE again on z/OS 2.1 system as
>> these
>> > > dataset already exist in z/OS 1.13 system in master catalog.
>> > >
>> > > FYI. We have used z/OS 1.13 MASTER CATALOG as USERCATALOG while
>> defining
>> > > z/OS 2.1 master catalog.
>> > >
>> > >
>> > > Any suggestions are highly appreciated.
>> > >
>> > > //DEFPAGE JOB 5640,TEST,
>> > > // CLASS=A,
>> > > // MSGCLASS=A
>> > > //S1 EXEC PGM=IDCAMS
>> > > //PAG001 DD VOL=SER=PAG001,UNIT=3390,DISP=OLD
>> > > //SYSPRINT DD SYSOUT=*
>> > > DEFINE PAGESPACE -
>> > > (NAME(PAGE.SYS9T.COMMON) -
>> > > FILE(PAG001) -
>> > > VOLUMES(PAG001) -
>> > > RECATALOG -
>> > > CYLINDERS(200)) -
>> > > CAT(ZS.MASTER.CATALOG) ----------------------z/OS 2.1 MASTER
>> > > CATALOG
>> > > DEFINE PAGESPACE -
>> > > (NAME(PAGE.SYS9T.PLPA) -
>> > > FILE(PAG001) -
>> > > VOLUMES(PAG001) -
>> > > RECATALOG -
>> > > CYLINDERS(180)) -
>> > > CAT(ZS.MASTER.CATALOG)
>> > > DEFINE PAGESPACE -
>> > > (NAME(PAGE.SYS9T.LOCAL1) -
>> > > FILE(PAG001) -
>> > > VOLUMES(PAG001) -
>> > > RECATALOG -
>> > > CYLINDERS(200)) -
>> > > CAT(ZS.MASTER.CATALOG)
>> > >
>> > > ----------------------------------------------------------------------
>> > > For IBM-MAIN subscribe / signoff / archive access instructions,
>> > > send email to [email protected] with the message: INFO
>> IBM-MAIN
>> > >
>> >
>> >
>> >
>> > --
>> > There is nothing more pleasant than traveling and meeting new people!
>> > Genghis Khan
>> >
>> > Maranatha! <><
>> > John McKown
>> >
>> > ----------------------------------------------------------------------
>> > For IBM-MAIN subscribe / signoff / archive access instructions,
>> > send email to [email protected] with the message: INFO IBM-MAIN
>> >
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
>>
>> The information contained in this message is confidential, protected from
>> disclosure and may be legally privileged. If the reader of this message is
>> not the intended recipient or an employee or agent responsible for
>> delivering this message to the intended recipient, you are hereby notified
>> that any disclosure, distribution, copying, or any action taken or action
>> omitted in reliance on it, is strictly prohibited and may be unlawful. If
>> you have received this communication in error, please notify us immediately
>> by replying to this message and destroy the material in its entirety,
>> whether in electronic or hard copy format. Thank you.
>>
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
>>
>
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
