Kees Vernooij wrote:
>Our DB2 experts confirm this, but think that you need a
>DB2/CONNECT license to make it working.
Good news: that's not correct. DB2 Connect licensing is not required when
the JDBC client is running on z/OS, when connecting to Db2 for z/OS. I'll
quote from IBM's Db2 Version
nframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Frank Swarbrick
> Sent: 25 September, 2017 20:46
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: LPAR to LPAR access
>
> My understanding is the JDBC "Type 4" (pure Java) client for DB2 has the
&g
__
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of
Peter Hunkeler <p...@gmx.ch>
Sent: Monday, September 25, 2017 8:17 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AW: Re: LPAR to LPAR access
>You need DDF access to the DB2 that has the data and from Lunix/
>You need DDF access to the DB2 that has the data and from Lunix/Unix/Windows
>this can be achieved by installing IBM Data Server Client and on z/OS you must
>install DB2 to facilitate this. This DB2 does not need databases, datasharing
>or Sysplex, only IP connectivity to the DB2 with data,
tember, 2017 18:51
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: LPAR to LPAR access
>
> I'm confused. If both the "one and only" DB2 (the database server) and
> the "remote" system are z/OS systems, then as far as I know "DB2 for
> z/OS" has to be se
Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of
Vernooij, Kees (ITOPT1) - KLM <kees.verno...@klm.com>
Sent: Friday, September 22, 2017 12:17 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LPAR to LPAR access
Not on the remote system, if that is what you mean. The remote sys
35
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: LPAR to LPAR access
>
> Still requires the entire DB2 for z/OS setup, and associated started
> tasks.
>
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf
> of
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LPAR to LPAR access
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Peter Hunkeler
> Sent: 20 September, 2017 19:56
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: AW: Re: LPAR
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of
Timothy Sipples <sipp...@sg.ibm.com>
Sent: Wednesday, September 20, 2017 11:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LPAR to LPAR access
Frank Swarbrick wrote:
>Does anyone have
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Peter Hunkeler
> Sent: 20 September, 2017 19:56
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: AW: Re: LPAR to LPAR access
>
>
> >Db2 Data sharing i
Frank Swarbrick wrote:
>Does anyone have any insight into the possibility that an RFE to
>have 'client only' code on z/OS would be accepted?
Or a Db2 for z/OS client only license? No idea, but it probably doesn't
hurt to ask.
"Best guess" is that such a construction wouldn't be relevant to
y' code on z/OS would be accepted?
Frank
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of
Peter Hunkeler <p...@gmx.ch>
Sent: Wednesday, September 20, 2017 11:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AW: Re: LPAR to LPAR access
>Db2 Data sharing isn't the only way to get 2 Db2 subsystems on different
>LPAR's to talk to each other. As long as the 2 LPAR's have some connectivity,
>TCP/IP etc. in common, it is possible to use Db2 distributed data facility to
>allow the 2 subsystems to communicate.
But they do *not*
Software
Note - All opinions are strictly my own.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Nelson, Judith
Sent: Wednesday, September 20, 2017 9:27 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LPAR to LPAR access
Thank you Kees
@LISTSERV.UA.EDU
Subject: Re: LPAR to LPAR access
Judith,
If you are referring to Timothy's "DB2 data Sharing", this requires a Parallel
Sysplex.
Kees.
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Nelson, Judith
> Se
7 16:15
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: LPAR to LPAR access
>
> Hi Timothy,
> Adding DB2 to the other LPAR sounds more and more the way to go.
>
> Thanks for your response.
>
> Judith Nelson
>
>
> -Original Message-
> From: IBM Mainframe
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LPAR to LPAR access
You can configure your CICS "File Owning Region" (FOR) in CICS TS in the LPAR
with DB2, then access that FOR from any interconnected CICS regions -- and from
interconnected TXSeries, for that matter. The folks in the CICS-L ma
t;Sent: Tuesday, September 19, 2017 5:43 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: LPAR to LPAR access
>
>Hi Jerry,
>I have looked into the link to the remote database. As far as I
>understand this is that requires a db2 instance on both LPAR's. :(
>
>Thank you,
>
:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LPAR to LPAR access
Yes, Judith. That is correct. I missed that in your email. However, I believe
the BMC tool allows you to connect CICS and maybe batch on one LPAR to DB2 on
another LPAR.
-Original Message-
From: IBM Mainframe Discussion
You can configure your CICS "File Owning Region" (FOR) in CICS TS in the
LPAR with DB2, then access that FOR from any interconnected CICS regions --
and from interconnected TXSeries, for that matter. The folks in the CICS-L
mailing list likely can provide more details if you need them. Basically,
ent: Tuesday, September 19, 2017 5:43 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: LPAR to LPAR access
>
>Hi Jerry,
>I have looked into the link to the remote database. As far as I understand
>this is that requires a db2 instance on both LPAR's. :(
>
>Thank you,
>
, Judith
Sent: Tuesday, September 19, 2017 5:43 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LPAR to LPAR access
Hi Jerry,
I have looked into the link to the remote database. As far as I understand this
is that requires a db2 instance on both LPAR's. :(
Thank you,
Judith Nelson
-Original Message
nframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Nelson, Judith
> Sent: Tuesday, September 19, 2017 10:00 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: LPAR to LPAR access
>
> Thank you Jerry!
>
> Judith Nelson
>
>
> -Original Messag
, Judith
Sent: Tuesday, September 19, 2017 12:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LPAR to LPAR access
Thank you Jerry!
Judith Nelson
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Edgington, Jerry
Sent: Tuesday, September 19
Thank you Jerry!
Judith Nelson
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Edgington, Jerry
Sent: Tuesday, September 19, 2017 11:25 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LPAR to LPAR access
Sorry Judith,
Our email
-optimizer.html
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Edgington, Jerry
Sent: Tuesday, September 19, 2017 12:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LPAR to LPAR access
Judith,
I think this link should help with the setup
Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Nelson, Judith
Sent: Tuesday, September 19, 2017 11:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LPAR to LPAR access
Hi Jerry,
You are correct with your assumption. :)
If I set up the database
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Edgington, Jerry
Sent: Tuesday, September 19, 2017 9:17 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LPAR to LPAR access
Judith,
I know of a couple of ways to get batch and CICS to access a remote DB2, which
is what you are asking, I believe
Judith,
I know of a couple of ways to get batch and CICS to access a remote DB2, which
is what you are asking, I believe, because you don't want to setup a DB2 data
sharing.
1) Within DB2, you can setup a database as a remote. DB2 admin should know how
to do this.
2) BMC has a product that
29 matches
Mail list logo
