Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

KSDS sharing between two systems

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
Grant Goodale

New User


Joined: 13 Nov 2010
Posts: 55
Location: Brampton, Ontario, Canada

PostPosted: Tue Jan 14, 2014 8:07 am    Post subject: KSDS sharing between two systems
Reply with quote

I want to define a KSDS that will be shared between two or more LPARs, provided that it resides in shared DASD, of course. I am currently using SHR(3 3). Is this possible if the two systems do not share catalogs? I cannot see any way to define it on the second system using IDCAMS.

I have done a search and I did not notice anything that addresses this issue but I might have missed something.

TIA
Back to top
View user's profile Send private message

sureshpathi10

Active User


Joined: 03 May 2010
Posts: 154
Location: Kuala Lumpur

PostPosted: Wed Jan 15, 2014 10:26 am    Post subject:
Reply with quote

Hi,

I'm guessing that, you want to create a KSDS that can be accessible in multiple LPARs.

Here are my thoughts:
When you DEFINE a KSDS it will be cataloged in that LPAR. Only the VOLUME is shared across the systems not the catalogs. So, You need to catalog the same KSDS file in the second LPAR by specifying the VOL Serial.

Note: I've faced this problem with the normal PDS and fixed like above mentioned. I'm not sure how this will work with VSAM.
Back to top
View user's profile Send private message
Grant Goodale

New User


Joined: 13 Nov 2010
Posts: 55
Location: Brampton, Ontario, Canada

PostPosted: Wed Jan 15, 2014 7:02 pm    Post subject: VSAM access
Reply with quote

Suresh -

I have tried to do that DEFINE with the VOL parameter but IDCAMS complains that there are no space specifications. I know that I can do it with a non-VSAM. It looks like a shared catalog is the only way of getting access.

Thanks.
Back to top
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10203
Location: italy

PostPosted: Wed Jan 15, 2014 7:20 pm    Post subject: Reply to: KSDS sharing between two systems
Reply with quote

I strongly suggest to read

http://www.redbooks.ibm.com/redbooks/pdfs/sg246105.pdf
Back to top
View user's profile Send private message
Grant Goodale

New User


Joined: 13 Nov 2010
Posts: 55
Location: Brampton, Ontario, Canada

PostPosted: Wed Jan 15, 2014 10:33 pm    Post subject:
Reply with quote

Enrico -

Interesting document. I think that I will just use a shared user catalog. It seems like the simplest solution.

Thanks
Back to top
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10203
Location: italy

PostPosted: Wed Jan 15, 2014 11:05 pm    Post subject: Reply to: KSDS sharing between two systems
Reply with quote

do You have already a plan to provide INTEGRITY
Back to top
View user's profile Send private message
Grant Goodale

New User


Joined: 13 Nov 2010
Posts: 55
Location: Brampton, Ontario, Canada

PostPosted: Wed Jan 15, 2014 11:27 pm    Post subject:
Reply with quote

Yes - cross system ENQs
Back to top
View user's profile Send private message
Bill O'Boyle

CICS Moderator


Joined: 14 Jan 2008
Posts: 2502
Location: Atlanta, Georgia, USA

PostPosted: Thu Jan 16, 2014 1:41 am    Post subject: Reply to: KSDS sharing between two systems
Reply with quote

Grant,

Have you researched the MVS Coupling Facility and MVS Logger?
Back to top
View user's profile Send private message
Grant Goodale

New User


Joined: 13 Nov 2010
Posts: 55
Location: Brampton, Ontario, Canada

PostPosted: Thu Jan 16, 2014 6:39 am    Post subject:
Reply with quote

Personally, no but I believe that one of my co-workers is conversant in these items. I will check them out myself.

Thanks for the suggestion.
Back to top
View user's profile Send private message
PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2422
Location: Netherlands, Amstelveen

PostPosted: Thu Jan 16, 2014 11:00 am    Post subject:
Reply with quote

You will find some interesting info here (pdf alert) :

https://www.google.nl/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&cad=rja&ved=0CDcQFjAB&url=https%3A%2F%2Fshare.confex.com%2Fshare%2F116%2Fwebprogram%2FHandout%2FSession8978%2FSHARE%2520Best%2520Practices%2520for%2520ICF%2520Catalog%2520and%2520VSAM%2520Anaheim%2520S8978.pdf&ei=j23XUs-IKMjI0wWx24CgCQ&usg=AFQjCNHgOPD-XZDl0wr1WSiAZ3BSVzKF5Q&bvm=bv.59568121,d.bGQ
Back to top
View user's profile Send private message
Grant Goodale

New User


Joined: 13 Nov 2010
Posts: 55
Location: Brampton, Ontario, Canada

PostPosted: Sun Jan 19, 2014 6:13 am    Post subject:
Reply with quote

Peter -

Interesting reading. Thanks

- Grant
Back to top
View user's profile Send private message
Pete Wilson

Active User


Joined: 31 Dec 2009
Posts: 437
Location: London

PostPosted: Wed Feb 26, 2014 10:25 pm    Post subject:
Reply with quote

This is a messy and ill advised route to go down, trust me. If it can't be in a proper shared catalog then don't do it, unless perhaps it is a completely static unchanging file.

For one, the catalog stat's are always going to be wrong once any updates are done because the 'other side' wouldn't be aware of it. So any process opening the file is going to be invoking implicit verifies every time I suspect which could be a large overhead. Not sure if the Catalog Address Space (CAS) is going to be too happy either. Also may require special treatment in GRS.

You can try doing a DEFINE with the VOLUMES and RECATALOG parameters, but not sure it will work. It uses the VVDS information to build the catalog information and it knows what catalog the file was originally defined to as that's stored in the VVR record. You may have to define a usercatalog on the 'other' system with the same name to do the RECATALOG, but that may not be feasible if the ALIAS points somewhere else.
Back to top
View user's profile Send private message
Grant Goodale

New User


Joined: 13 Nov 2010
Posts: 55
Location: Brampton, Ontario, Canada

PostPosted: Thu Feb 27, 2014 1:08 am    Post subject:
Reply with quote

Pete -

I have opted to go the shared catalog route. Anything else looks like a horror story.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Several errors during building altern... Andi1982 JCL & VSAM 11 Wed Jul 06, 2016 7:39 pm
This topic is locked: you cannot edit posts or make replies. BAE Systems - Recruitment Open Days -... Express Mainframe Jobs 0 Fri Apr 22, 2016 8:19 pm
This topic is locked: you cannot edit posts or make replies. Job Offer: Information systems consu... Express Mainframe Jobs 0 Thu Mar 10, 2016 7:18 pm
This topic is locked: you cannot edit posts or make replies. Canada mainframe systems programming ... Gary Jacek Mainframe Jobs 0 Sat Jan 30, 2016 4:26 am
No new posts Empty KSDS Files Jeenu Bajaj JCL & VSAM 6 Fri Aug 21, 2015 2:44 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us