Re: Catalog move

2016-05-16 Thread Tony IBM-MAIN
Look at Catalog Recovery Plus from Rocket Software. There is a MERGECAT 
WHILEOPEN function.


Catalog entries may be moved while datasets are in use, including all 
those tricky VSAM datasets that are open by long running STC's like CICS.


Tony.

On 05/05/16 17:35, Peter wrote:

Hi

We have some product DATASET catalog to master instead of a user catalog.

So moving the DATASET entries from master to a user catalog is doable only
when the started task is down ?

Any thoughts on the above approach ?

Peter

--
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


Re: Catalog move

2016-05-05 Thread retired mainframer
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Peter
> Sent: Thursday, May 05, 2016 9:35 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Catalog move
> 
> Hi
> 
> We have some product DATASET catalog to master instead of a user catalog.
 
Do the datasets in question have high level qualifiers that are specific to 
this product and not used for any other purpose?

> So moving the DATASET entries from master to a user catalog is doable only
> when the started task is down ?

It depends.  How many tasks and address spaces are involved?  Is there a period 
of time when the task is "running" but actually idle.  Do you have any way to 
temporarily pause or quiesce the address spaces associated with the tasks?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Catalog move

2016-05-05 Thread Elardus Engelbrecht
Lucas Rosalen wrote:

>+1 for REPRO MERGECAT.
>I've done this for Netview's datasets - with all Netview's STCs down because 
>I'm a chicken :)

Let me cheep-cheep in, just as soon as I hatched from my (rotten?) egg, I did 
the same (Move, REPRO, Rename HLQ, all the works including using a new PU - LU 
settings in a new VTAM on another LPAR) for Netview Access Services VSAM 
datasets while that Netview Access Services STC was down and out ... ;-)

Uhm, no beautiful chicks were available then ...

Oh, BTW, when they complained they could not logon using the old LOGON 
APPLID(), I discovered I'm really very low in the pecking 
order...

Ok, back to the topic: 

Peter, could you be kind to describe WHAT is your STC and WHAT dsn(s) you want 
to move via recatalog?

Others gave you good solutions, but you can also rename them to something else, 
fix your aliases and rename them back. Yes, I know it is a PITA especially if 
they're really 'busy'.

But, since you mentioned DB2, if they're DB2 database datasets, then, during 
non-peak hours, stop all the subsystems, do your thing and restart them. That 
is if you can't copy/move the contents to a brand new set of datasets.

Groete / Greetings
Elardus Engelbrecht

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Catalog move

2016-05-05 Thread Rob Schramm
Chicken factor aside.  There is a document to cover such things as in ..
DFSMS Managing Catalogs, Chapter 4 Maintaining Catalogs, Splitting Catalogs
or Moving Catalog Entries.

Doing it while a data set is open has this caution...

Attention: Performing REPRO on a catalog while data sets are open in the
source catalog might result in a loss of information if any of those data
sets extend, or other catalog updates are made. The changes might not be
copied to the target catalog, resulting in a mismatch between the
information contained in the VVDS and the new target BCS. This might cause
the data sets to be inaccessible or receive errors when they are used.
Which is then followed by the 7 step procedure to move entry(s) from one
catalog to another.

I am inferring from the documentation that even if the catalog is locked
that a VVDS entry might be updated for data sets that are open.  (looking
for confirmation??)

Unless you have one of the Catalog utilities that will perform the proper
rituals to the pernicious catalog-gods and allow a wider array of options.


Rob Schramm



On Thu, May 5, 2016, 1:22 PM Lucas Rosalen  wrote:

> +1 for REPRO MERGECAT.
> I've done this for Netview's datasets - with all Netview's STCs down
> because I'm a chicken :)
>
> Lucas
> On May 5, 2016 19:05, "Peter"  wrote:
>
> What if if is a db2 datasets ? I believe to have safer move a shutdown is
> necessary ?
> On May 5, 2016 10:19 PM, "Chuck Kreiter"  >
> wrote:
>
> > I've used REPRO MERGECAT to do this in the past.  Once this is done,
> > define your alias.  The datasets should be unallocated when you do this.
> >
> > REPRO INDATASET(old catalog) -
> >  OUTDATASET(new catalog)
> >  LEVEL(hlq) MERGECAT
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> > Behalf Of Peter
> > Sent: Thursday, May 5, 2016 10:35 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Catalog move
> >
> > Hi
> >
> > We have some product DATASET catalog to master instead of a user catalog.
> >
> > So moving the DATASET entries from master to a user catalog is doable
> only
> > when the started task is down ?
> >
> > Any thoughts on the above approach ?
> >
> > Peter
> >
> > --
> > 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
>
-- 

Rob Schramm
The Art of Mainframe, Inc

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Catalog move

2016-05-05 Thread Lucas Rosalen
+1 for REPRO MERGECAT.
I've done this for Netview's datasets - with all Netview's STCs down
because I'm a chicken :)

Lucas
On May 5, 2016 19:05, "Peter"  wrote:

What if if is a db2 datasets ? I believe to have safer move a shutdown is
necessary ?
On May 5, 2016 10:19 PM, "Chuck Kreiter" 
wrote:

> I've used REPRO MERGECAT to do this in the past.  Once this is done,
> define your alias.  The datasets should be unallocated when you do this.
>
> REPRO INDATASET(old catalog) -
>  OUTDATASET(new catalog)
>  LEVEL(hlq) MERGECAT
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Peter
> Sent: Thursday, May 5, 2016 10:35 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Catalog move
>
> Hi
>
> We have some product DATASET catalog to master instead of a user catalog.
>
> So moving the DATASET entries from master to a user catalog is doable only
> when the started task is down ?
>
> Any thoughts on the above approach ?
>
> Peter
>
> --
> 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


Re: Catalog move

2016-05-05 Thread Peter
What if if is a db2 datasets ? I believe to have safer move a shutdown is
necessary ?
On May 5, 2016 10:19 PM, "Chuck Kreiter" 
wrote:

> I've used REPRO MERGECAT to do this in the past.  Once this is done,
> define your alias.  The datasets should be unallocated when you do this.
>
> REPRO INDATASET(old catalog) -
>  OUTDATASET(new catalog)
>  LEVEL(hlq) MERGECAT
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Peter
> Sent: Thursday, May 5, 2016 10:35 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Catalog move
>
> Hi
>
> We have some product DATASET catalog to master instead of a user catalog.
>
> So moving the DATASET entries from master to a user catalog is doable only
> when the started task is down ?
>
> Any thoughts on the above approach ?
>
> Peter
>
> --
> 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


Re: Catalog move

2016-05-05 Thread Chuck Kreiter
I've used REPRO MERGECAT to do this in the past.  Once this is done, define 
your alias.  The datasets should be unallocated when you do this.  

REPRO INDATASET(old catalog) -
 OUTDATASET(new catalog)
 LEVEL(hlq) MERGECAT

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Peter
Sent: Thursday, May 5, 2016 10:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Catalog move

Hi

We have some product DATASET catalog to master instead of a user catalog.

So moving the DATASET entries from master to a user catalog is doable only when 
the started task is down ?

Any thoughts on the above approach ?

Peter

--
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


Re: Catalog move

2016-05-05 Thread John McKown
On Thu, May 5, 2016 at 11:35 AM, Peter  wrote:

> Hi
>
> We have some product DATASET catalog to master instead of a user catalog.
>
> So moving the DATASET entries from master to a user catalog is doable only
> when the started task is down ?
>

​Why? What are you planning to use do to the move? I've used REPRO MERGECAT
as below to move my CICS41 data set entries to a separate catalog. I assume
you that I did not take down all the CICS regions!

e.g.

//STEP002   EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSINDD *
 REPRO -
  OUTDATASET(CATALOG.ICF.VLIHTS2) -
  INDATASET(CATALOG.ICF.CICS41) -
  MERGECAT -
  LEVEL(CICS41)
/*


>
> Any thoughts on the above approach ?
>
> Peter
>
>

-- 
The unfacts, did we have them, are too imprecisely few to warrant our
certitude.

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Catalog move

2016-05-05 Thread Lizette Koehler
It depends on if there are Active open dataset.

Are these files only non vsam or vsam or a mix of both?

If only non vsam then a simple uncatalog, delete noscratch, define alias, 
catalog - process will work

If VSAM is involved, I think you have to use a process like DFDSS to MOVE the 
vsam (DELETE and CATALOG) for them.

If you can close the files to the STC, then you do not need to stop the STC.  
If not, then you will need to stop the STC

I typically use DFDSS to DUMP with DELETE, define the new ALIAS, and the 
RESTORE from DFDSS DUMP.

Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Peter
> Sent: Thursday, May 05, 2016 9:35 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Catalog move
> 
> Hi
> 
> We have some product DATASET catalog to master instead of a user catalog.
> 
> So moving the DATASET entries from master to a user catalog is doable only
> when the started task is down ?
> 
> Any thoughts on the above approach ?
> 
> Peter
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN