This page will help you setting up a proper RSCS machine with TCPNJE capabilities in the VM SixPack extended operating system. The standard Sixpack system does not have a proper RSCS installed. Rene Ferland (kudo’s Rene) did install RSCS to be able to connect to remote Job Entry clients. After that he added Pete Coghlan’s patch for Network Job Entry (NJE).
So the current situation is that there are two RSCS nuclei on Rene’s personal Sixpack system, one standard that has been built by Rene and another one that has been built following Pete Coghlan’s instructions.
To be able to work with either, the CP nucleus parameter files had to be modified and the nucleus had to be rebuilt. These modifications are on the four DASDs Rene made available to us.
This is a rather long script, it will address:
- SDL Hyperion NJE
- modify startup script(s)
- Get VM Sixpack Extended
- Acquiring four new DASD files for VM Sixpack
- Install the DASD’s on your system
- IPL new VM
- Change MAINT files
- Configure your RSCS machine
- Rebuild the RSCS nucleus
- Re-configure Hercules
- Re-IPL and start RSCS and your lines
If not already installed on your system, you need the following:
SDL hyperion with NJE enabled
You will need to have the SDL Hyperion NJE enabled emulator. See this page to get and install it.
Modified startup scripts
Do not forget to modify your startup script(s) as described at the end of the page about the SDL hyperion NJE enabled version of hercules above.
VM 6pack extended
On top of that, you need to have installed Rene Ferland’s VM/370 R6 PLC29 “SixPack/Ext” ver 1.2+. Download it here.
Get the new DASD files
Okay, so now you have the prerequisites met, now let’s get those DASD’s and a sample text file. Download them here, (about 74 MB).
Unzip the files and upload them to your Linux system.
I put them in my ~/Upload directory. The names are:
As I told you, there are 4 disks and a text file.
- DASD 141 contains the modified directory and CP nucleus
- DASD 241 contains the minidisk of RSCS
- DASD 34f contains Pete Coghlan’s minidisk
- DASD 440 contains the modified stuff for the CP nucleus
Install DASDs in our system
Now let’s make these DASDs part of our system. (you did install the standard Sixpack/Extended mentioned above, right?).
Backup the old ones?
You can choose to overwrite the current DASDs, but should you want to save the original minidisks, use these commmands from your VM base directory (for me that’s ~/VM6PExt/6PExt):
cd ~/VM6PExt/6PExt/disks mv vm3350-1.141.cckd vm3350-1.141.cckd.old mv vm3350-2.241.cckd vm3350-2.241.cckd.old mv vm3350-3.34f.cckd vm3350-3.34f.cckd.old mv vm3350-4.440.cckd vm3350-4.440.cckd.old
Copy the new ones in
Now copy the downloaded DASD files in there:
cp ~/Upload/vm3350* .
IPL your new VM
You can now IPL your VM Sixpack system with your modified startup script including the new DASD’s and start with the configuration of the RSCS and NJE stuff.
Check files on MAINT
Now logon to your MAINT user on a 3270 terminal and check the SIXPCKE DIRECT A file. There you will find that these physical lines have been dedicated to the RSCS virtual machine as virtual lines 070, 071 and 072. Make sure they are! What we need is those line to look like the bold/italic ones below:
USER RSCS RSCS 2M 14M G IPL CMS OPTION ECMODE CONSOLE 009 3215 DEDICATE 070 040 DEDICATE 071 041 DEDICATE 072 042
When you have these verified, issue this command to make the direct file active:
DIRECT SIXPCKE DIRECT A
There’s another file you have to change in MAINT, this one is a little bit more involved because it is on the Read Only system disk. The file is SYSTEM NETID S2. First make it available to us in RW mode:
ACC 190 T
CMS will warn you that it’s also the S disk. Never mind, we knew that…
We will need the system’s CPU ID, do a:
This will give you a long string like:
CPUID = FF09805243810000
Strip the first ‘FF’ , then take six characters as your CPU ID and discard the rest. So mine is ‘098052’. Now go edit the file, make sure to specify the ‘2’ at the end:
EE SYSTEM NETID T2
Now make this file look like:
*CPUID NODEID NETID 098052 LNODEVM RSCS
Replace LNODEVM with your local node name and save the file.
(NOTE: in the following, press ENTER ONLY ONCE after the IPL 190 otherwise you will mess up your system)
IPL 190 <enter> SAVESYS CMS <enter>
Give one ENTER to get the CMS Ready; prompt. Then check the contents of your file:
type system netid s
Done that and everything okay? Then you can logoff MAINT for now.
Check RSCS config
Now logon to your RSCS machine (in a 3270 terminal):
LOGON RSCS RSCS
Now, when you do a
you can see the DASDs we just added. Especially 091, 191 and 192, these belong to RSCS. Rene’s nucleus (REL 6, LEV 0, 11/20/19) is on 191, and Pete Coghlan’s nucleus on 091 (REL 7, LEV 0, 12/12/19).
#CP IPL 091
you will get that RSCS nucleus up and when you issue a:
you can see that there are two lines, TCPNJE0 and TCPNJE1, both inactive.
Configure RSCS parameter files
We want to change the names of those lines. To do that we have to go back into CMS:
#CP IPL CMS
When CMS is up, we need to prepare it for rebuilding the RSCS nucleus by giving these commands:
REL A REL D ACC 091 A ACC 094 B/B ACC 194 D/D ACC 192 F/F
Now press clear and issue a:
This will show you the minidisks you have attached to your CMS. When all went well, you are at the point that you can build Pete Coghlan’s nucleus, but first we have to edit a line definition file:
EE AXSLINKS COPY
and change the first three lines with ‘ID=’ in them. You want to change the names of these in the ID= fields to the names you choose or that were assigned to you. The first entry is for your local node name. The second and third are the lines with which you connect to others; typically these get the name of the remote node your are connecting to. Here’s what my lines look like:
GENLINK ID=NLGERVM,TYPE=LOCAL GENLINK ID=MOSHIX4,TYPE=DMTYJB,KEEP=5,LINE=070,TASK=YJE0 GENLINK ID=NLGERL0,TYPE=DMTYJB,KEEP=5,LINE=071,TASK=YJE1 GENLINK ID=NLGERL1,TYPE=DMTYJB,KEEP=5,LINE=072,TASK=YJE2
NLGERVM is the local node name of my VM system. MOSHIX4 is a system that I connect to. NLGERL0 and NLGERL1 are spare lines.
(NOTE: there is more to be configured to be able to connect, I will describe that later on in this process, and you will need to contact the owner of that system to get the specifics).
Also note that there are line numbers here, they point to VIRTUAL line numbers of the RSCS machine. In this system the PHYSICAL line numbers have been defined as 040, 041 and 042.
Another parameter file
We need to check one more file:
EE LAXLINES COPY
This file contains parameters to define the lines we have; they should look like the following:
GENLINE LINE=070 GENLINE LINE=071 GENLINE LINE=072 GENLINE LINE=0B0 GENLINE LINE=0B1 GENLINE LINE=0B2
Once you verified that they do, or changed to so they are now correct, we are ready to:
Rebuild the RSCS nucleus
There will sometimes be warnings, you can discard them. This process punches a new nucleus to your virtual reader. Check it with:
This should show you:
FILES: 1 RDR, NO PRT, NO PUN
We can use that file to IPL our newly built nucleus:
IPL 00C CLEAR
This will lead to a question/answer sequence as follows:
DMTINI407R REWRITE THE NUCLEUS ? yes DMTINI408R IPL DEVICE ADDRESS = 091 DMTINI409R NUCLEUS CYL ADDRESS = 9 DMTINI410R ALSO IPL CYLINDER 0 ? yes DMTINI4101 NUCLEUS WRITE COMPLETE CP ENTERED; DISABLED WAIT PSW '00060000 00000012'
In this state we can logoff. The new nucleus has been written to disk 091.
Shutdown the VM system for now, we still need to:
Reconfigure the hercules.cnf file
With VM shut down we go to our hercules.cnf file and add the following definition lines, defining the PHYSICAL lines:
#--------------------------------------------------------- # RSCS connections #--------------------------------------------------------- 0040 TCPNJE 2703 LHOST=your_ip LPORT=your_port LNODE=NLGERVM RHOST=remote_url RPORT=remote_port RNODE=MOSHIX4 # 0041 TCPNJE 2703 LHOST=your_ip LPORT=your_port LNODE=NLGERVM RHOST=remote_url RPORT=remote_port RNODE=remote_node # 0042 TCPNJE 2703 LHOST=your_ip LPORT=your_port LNODE=NLGERVM RHOST=remote_url RPORT=remote_port RNODE=remote_node
As I said earlier, you will have to contact the owner of the machine you want to connect to for the specifics of each node.
Re-IPL and re-login to RSCS
When this has all been done, we can re-IPL our VM/370 and login to RSCS again. Now we can do:
And our new nucleus has been started. When that’s happened, we can start the lines we need, by (in my example) specifying:
This will bring up the line(s) when the other side is ready as well.