IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Copying Db2 BSDS and logs to another machine via shared disk


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
jlyle

New User


Joined: 23 Jun 2020
Posts: 4
Location: USA

PostPosted: Tue Jun 23, 2020 9:56 am
Reply with quote

Hi, I'm trying to move Db2 BSDS and active log data sets from one machine to another via a shared disk. When I try to copy the data from the shared disk to the second machine I got a IEC150I 913-0C,IFG0195T message so I figured I needed to catalog the shared disk VSAM datasets. But when I tried that with DEFINE CLUSTER it failed:

DEFINE CLUSTER( -
NAME(shared-vol-dsname) -
VOLUMES(shared-volume-name) -
LINEAR -
RECATALOG -
)
IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 86 - REASON CODE IS IGG0CLEY-6
IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12

Not sure what I need to do next so I could use a nudge if anyone has any thoughts!

Thanks!
Back to top
View user's profile Send private message
Garry Carroll

Senior Member


Joined: 08 May 2006
Posts: 1205
Location: Dublin, Ireland

PostPosted: Tue Jun 23, 2020 12:50 pm
Reply with quote

AFAIK, 913 abend is security...(RACF, ACF2, ... )

Garry
Back to top
View user's profile Send private message
Willy Jensen

Active Member


Joined: 01 Sep 2015
Posts: 734
Location: Denmark

PostPosted: Tue Jun 23, 2020 1:30 pm
Reply with quote

I will suggest that you do a backup of all the datasets to a dataset on the shared disk and a restore in the other system.
Back to top
View user's profile Send private message
Joerg.Findeisen

Senior Member


Joined: 15 Aug 2015
Posts: 1337
Location: Bamberg, Germany

PostPosted: Tue Jun 23, 2020 7:39 pm
Reply with quote

IDC3009I RET=86 REAS=6 should be mismatching catalog for the RCTLG. Either you have to MERGECAT the entry to the new system or use a shared UCAT for the define. In case you have some catalog utilities they can "fix" such issues as well so the RCTLG will work as expected.

Better you do a dump/restore with DFDSS as Willy suggests. It will be the quickest way IMHO.
Back to top
View user's profile Send private message
Pete Wilson

Active Member


Joined: 31 Dec 2009
Posts: 592
Location: London

PostPosted: Tue Jun 23, 2020 9:35 pm
Reply with quote

Joerg.Findeisen wrote:
IDC3009I RET=86 REAS=6 should be mismatching catalog for the RCTLG. Either you have to MERGECAT the entry to the new system or use a shared UCAT for the define. In case you have some catalog utilities they can "fix" such issues as well so the RCTLG will work as expected.

Better you do a dump/restore with DFDSS as Willy suggests. It will be the quickest way IMHO.


DUMP/RESTORE of the BSDS via the shared volume is on the only feasible approach.

Trying to create the BSDS as a dataset on the shared volume is inviting more grief than it's worth. Mergecat on the target updates the VVDS entry for the BSDS on the shared volume to the new target usercatalog, so would create a mismatch situation on the source. You could DEL NSCR it on source but why bother. Do the DUMP/RESTORE.
Back to top
View user's profile Send private message
jlyle

New User


Joined: 23 Jun 2020
Posts: 4
Location: USA

PostPosted: Tue Jun 23, 2020 9:50 pm
Reply with quote

I'm looking at MERGECAT since BACKUP/RESTORE aren't an option for me. On the target system I just have the master ICF catalog....so do I specify that for both INBCS and OUTBCS? Just just want to catalog 5 data sets that are on this shared volume so that I can copy them into the BSDS and active logs at this target system.
Thanks!
Back to top
View user's profile Send private message
Willy Jensen

Active Member


Joined: 01 Sep 2015
Posts: 734
Location: Denmark

PostPosted: Wed Jun 24, 2020 12:46 pm
Reply with quote

When you say MERGECAT and that you want to copy the data from the shared disk, does that mean that both the actual datasets and the catalog are on the shared disk?
You can do MERGECAT into a master catalog, but you need proper authorization.
Only VSAM datasets starting with SYS1 or PAGE can be cataloged in 2 catalogs at the same time, unless something has changed since I last looked.
Back to top
View user's profile Send private message
Pete Wilson

Active Member


Joined: 31 Dec 2009
Posts: 592
Location: London

PostPosted: Wed Jun 24, 2020 2:17 pm
Reply with quote

What is the actual object of this exercise, is it a one-off copy or is this something you want to repeat? It seems a strange thing to be copying DB2 BSDS and Logs to a separate system as they're only relevant to the DB2 subsystem and DB/Tables on the source.

I can't see why a backup/restore of some form is not feasible. If you are allowed to write datasets to the shared disk then you should be able to create a DFDSS or some other utility backup of the BSDS etc on the shared volume, and then restore from that to create the datasets on the target system.

If the HLQ for the restored datasets is not defined as a Usercatalog alias they will go into the Mastercatalog by default.
Back to top
View user's profile Send private message
jlyle

New User


Joined: 23 Jun 2020
Posts: 4
Location: USA

PostPosted: Wed Jun 24, 2020 8:57 pm
Reply with quote

Simulating Tracker Site recoveries. Yes, I want to be repeating the exercise.
Back to top
View user's profile Send private message
Pete Wilson

Active Member


Joined: 31 Dec 2009
Posts: 592
Location: London

PostPosted: Thu Jun 25, 2020 5:39 pm
Reply with quote

Unless you have a common usercatalog on both plexes, on the shared volume, then I don't think it is feasible to have the BSDS and Logs defined on the shared volume because of backward pointers to the usercatalog name in the VVDS (and VVR if SMS managed) . If you try and MERGECAT the entry to a local usercatalog on target that updates the back-pointers to the new catalog name. If it's not the same as source then the datasets would become inaccessible from the source plex.

If you just define the BSDS and Logs locally on target, and create some backup files on the shared volume through which you can pipe data to be loaded into the BSDS and Logs that nay work. The backups can be say DFDSS DUMP's and on target you RESTORE with REPLACEU to overlay the target datasets, or they might be flat-file unloads from a REPRO or SORT, that you then read to copy into the existing target datasets.


I still fail to really see what benefit this would provide.
Back to top
View user's profile Send private message
jlyle

New User


Joined: 23 Jun 2020
Posts: 4
Location: USA

PostPosted: Thu Jun 25, 2020 9:35 pm
Reply with quote

I have made a little progress on this but I did run into a REPRO issue. When I REPRO from the shared disk into the BSDS and ACTIVE of the second machine it fails unless the shared disk is R/W. So REPRO is wanting to update something in the source location as it's copying to the target location? That seemed very strange to me. Anyone know why that would be? Thanks!
Back to top
View user's profile Send private message
Pete Wilson

Active Member


Joined: 31 Dec 2009
Posts: 592
Location: London

PostPosted: Fri Jun 26, 2020 3:11 pm
Reply with quote

It might help if you show the messages you get with the failure, and perhaps an example of your JCL.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts CA Disk LISTD SQL CA Products 1
No new posts Panvalet - 9 Character name - Issue c... CA Products 6
No new posts Capturing logs from spool dd JCL & VSAM 6
No new posts How to collect Job logs from $savers All Other Mainframe Topics 7
No new posts Getting an abend (I/O abend was trapp... ABENDS & Debugging 3
Search our Forums:

Back to Top