VSE/POWER networking (PNET)
Ingolf24 120000DRN3 Comment (1) Visits (11559)
In my test environment I just defined a VSE/POWER network between two z/VSE systems. I wanted to verify that a specific configuration still works.
With this blog entry I want share how I defined PNET. May be that is also of interest for you and you may want to try it in your test environment.
My small network communicates via TCP/IP. That is you have to configure and start one of the TCP/IP solutions first (TCP/IP for VSE/ESA, IPV6/VSE or Linux Fast Path). I used the IUI Program Development to define/edit the VSE/POWER members, but you may use any editor and catalog the members into the z/VSE Library afterwards. I describe a very simple configuration, without security definitions. Please consult the VSE/POWER books and job skeletons in ICCF library 59 for more details. The VSE/POWER Networking book would be a good start. The z/VSE Administration book describes the use of the PNET skeletons, if you want to use the IUI setup. The books are here.
You have to install the z/VSE Generation Feature. It's on the z/VSE base tape. You may use the IUI dialog for installation (Installation -> Install Generation Feature).
I have two z/VSE systems - VSE1 and VSE2 - both connected to a TCP/IP network. All skeletons that I mention are in ICCF library 59. First I started with the Network definition table (NDT). You may use the skeleton SKPWRNDT.
In my example it looks like this:
NDT1 PNODE NODE=VSE1, - (own node)
NDT2 PNODE NODE=VSE2, - (own node)
You need to compile that with High Level Assembler (HLASM) and link / catalog the VSE1 NDT into VSE1's PRD2.CONFIG sublibrary and VSE2 NDT into VSE2's PRD2 CONFIG sublibrary. Save a prior NDT into PRD2.SAVE.
Next you need to generate to VSE/POWER startup phase. You may use skeleton SKPWRGEN.
Now we go to the most critical part: We need to change the VSE/POWER startup procedure. It's in skeleton SKPWSTRT.
If you don't use our skeletons you may punch your procedure and edit that one.
Please save your existing procedure into PRD2.SAVE before you replace it.
In the VSE/POWER startup procedure on VSE1 and VSE2 you need to change the EXEC phase name for VSE1 to
>>>> If you use skeleton SKPWSTRT and you want to try out my PNET configuration, please remove the "SET SYSID=Y" card and change the "SET PNET=YYYYYYYY". Just locate the labels marked with "/. WARM" and change or change all startup phase/parameters.
The VSE/POWER startup procedure is located in z/VSE sublibrary IJSYSRS.SYSLIB. Please save it in PRD2.SAVE before any changes. After that you have to catalog the changed procedure into z/VSE sublibrary IJSYSRS.SYSLIB.
Now you can shutdown your z/VSE systems and re-IPL. After your TCP/IP stack is active VSE/POWER will connect to the other z/VSE system. You will see some PNET messages that show the connection status.
To verify if VSE/POWER networking works you may submit a small VSE/POWER job like this from VSE1:
It will be executed on VSE2. After you answered the PAUSE statement on VSE2, the output will be transferred back into the LST queue of VSE1.
If your VSE/POWER startup fails, you can use the following method:
You may use such a PNET environment e.g. to separate your online workload from batch, which may require to share data. Consider the performance implications of data sharing.
Please let me know, if this blog entry was useful.