Parallel sysplex connectivity

anka · New User Joined: 10 Aug 2011 Posts: 5 Location: Russia

Hello mainframers,

I'm deploying parallel sysplex, which consists of 2 z/OS systems and runs under z/VM, using special z/VM guest machine with CFCC (tricky, I know).

However, what I can't understand despite all IBM sysplex manuals, is connectivity between systems. I have read that the best way to establish connectivity is via CF list structures. I need to define such structures in CFRM policy and in PATHIN/PATHOUT statements in COUPLExx member. This is logical side of the case, which sounds rather clear.

However, what I don't understand is physical side - like, what exactly devices are used for communication, channels etc. How they are related with these CF list structures?

I'd appreciate advices/tips/howtos.

PeterHolland · Posted: Wed Aug 10, 2011 1:20 pm

Maybe you can find some info here :

Introduction to the New Mainframe: z/OS Basics SG24-6366

anka · New User Joined: 10 Aug 2011 Posts: 5 Location: Russia

Hi Peter,

I know this book pretty well and honestly don't see how it can help, since my question is rather specific and I guess is beyond this book's scope.

PeterHolland · Posted: Wed Aug 10, 2011 1:42 pm

Well if you want to know about the hardware try a search on ESCON or FICON.

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

Have you tried looking at Chapter 5 Planning signaling services in a sysplex in the manual z/OS V1R12.0 MVS Setting Up a Sysplex

anka · New User Joined: 10 Aug 2011 Posts: 5 Location: Russia

Nevilh,

Of course I did - from that chapter I learnt about definitions of CF link structures in CFRM and COUPLExx.

My question regards implementation of additional steps, like relating CF structures with virtual/physical devices...if that is needed.

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

Everything you need is described in the book. Firstly you have to decide how you are going to communicate between systems. On a nonVM system this is easy we are told what hardware is available, you may be more flexible as you are running under VM. However you will still have to decide whether you want to use stuctures defined in the coupling facility or (f)ctc's or a mixture of the two. If (as it sounds) you have decided to use the coupling facility , you will just have to update the couple member and make the relevent policy definitions

anka · New User Joined: 10 Aug 2011 Posts: 5 Location: Russia

Ok, thanks. I'll try it that way...Though I'm wondering how Cf will establish communication knowing only list structures - what virtual devices will be used exactly? Who will decide that - CF, z/VM or z/os?

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

Now I have a problem I have not worked with VM for along time. On a non-VM system LPAR's are defined for the CF and for z/OS. These can then be activated (modified) using HMC. Using HCD the partitions are defined, here the channels that connect to the CF are defined.

Robert Sample · Posted: Wed Aug 10, 2011 5:10 pm

Have you read chapter 2 (IBM System z) and chapter 4 (System z connectivity) of the Redbook ABC's of z/OS System Programming, Volume 10 (SG24-6990) which covers z/Architecture?

anka · New User Joined: 10 Aug 2011 Posts: 5 Location: Russia

Hi Robert,

Nope, have not, but will. Thanks.