Installing MVS 3.8
Normal Startup of Customized MVS 3.8
This is the process you should follow to IPL the customized MVS 3.8 to the state that batch jobs may be submitted and TSO users may log on and utilize the system.
1. Start Hercules
Open a console window (Linux) or a Command Prompt window (Windows) and start hercules from the mvs directory:
I have this automated under Windows 7 by creating an application shortcut that executes a batch script to set paths and execute the above command.
2. Start a TN3270 client session for the console
In another window, start a tn3270 client and connect to localhost at port 3270. Remember that the 3270 console specification in the Hercules' configuration file has specified a group name of CONSOLE for the console connection, so you must set your TN3270 client settings (LU, GROUP, or something similar, depending upon the client) to localhost, port 3270, and LU=console.
Your tn3270 client screen for the MVS master console should display an identification screen indicating it has connected to Hercules:
Notice that the Device number field shows a value of 0010, which indicates that this tn3270 client session is correctly connected to address x'010', the 3277 designated as the master console.
So far, this is exactly the same procedure used to IPL the newly generated system. But TSO has now been configurated, so you also need to add a TN3270 client session for TSO.
3. Start a TN3270 client session for one or more TSO users
In another window, start a tn3270 client and connect to localhost at port 3270. Remember that the tso 3270 specifications in the Hercules' configuration file have specified a group name of TSO for the tso connections, so you must set your TN3270 client settings (LU, GROUP, or something similar, depending upon the client) to localhost, port 3270, and LU=tso.
Your tn3270 client screen for the TSO session should display an identification screen indicating it has connected to Hercules:
Notice that the Device number field for this single TSO session shows a value of 0400, which indicates that this tn3270 client session is correctly connected to address x'0400', the 3277 designated as the first 3270 available for use by TSO.
If you need to start additional TSO user sessions after the system is running, simply start another TN3270 client and connect it as you did this one. Then press the CLEAR key in the TN3270 client window. This will establish the connection to MVS and the TSO logon screen will appear.
4. IPL from the System Residence DASD volume
IPL from the device at address x'150' (the 3350 DASD containing the MVS System Residence volume - dasd/mvsres.3350). In the Hercules command window, type the command ipl 0150 and press ENTER. On the MVS console (the tn3270 client window), you should see:
The next three messages are the same as they were when you IPL the newly created MVS for the first time.
5. Respond to the IEA101A message
Normally you simply press ENTER, but you can also enter parameters here to control how the IPL proceeds. The most common entry here if you have made an update to the system and are directed to rebuild the Link Pack Area would be R 0,clpa to rebuild the Link Pack Area.
6. Respond to the IFB010D message
Type R 0,U.
7. Respond to the $HASP426 message
Normally you should reply to this message with R 1,noreq to simply bring up JES2 with no further requests for input (that is what the noreq specifies). This is referred to as a WARM start; all JES2 queues will be in the same state they were in when the system was last shut down. If you don't want to retain job data on the queues, you may respond R1,cold,noreq. There are some times when you may need to clear everything that is stored on the JES2 queue, and to do that the response is R1,format,noreq. If you request the spool queue to be formatted, you will also have to respond to the two checkpoint reset messages that occur the first time the system is IPLed.
What if JES2 will not start?
This is a good place to address a situation that I know some people have had, because they have contacted me about it. If you see these messages at this point:
you did not edit the Hercules' configuration file (conf/mvs.cnf) to remove the comment lines from the DASD device specifications at addresses 180, 190, 220, 221, 222, 223, 224, 225, and 253. Close everything (no need to try to shut down properly), edit the configuration file, and start the IPL process from the top of this page.
8. Set console mode to Roll/Delete
When you see the message IEE159E MESSAGE WAITING at the lower right of the console TN3270 client window, press Program Function Key 12. This will issue the long command that has been set up for PFK12 to set the console into Roll/Delete mode. You will then see IEE163I MODE= RD on the left, directly beneath the input area on the console.
9. Start VTAM and TSO
On the MVS console (the tn3270 client window), type the command s net and press Enter. VTAM will start and as soon as it is initialized, TSO will start. If you are like me, this will become a nuisance after a while, and you can put this command in SYS1.PARMLIB(COMMND00) to have VTAM/TSO started automatically.
Log on to the TSO session with one of the TSO user IDs, and you are ready to use the system.
Shutting Down TSO and VTAM
Shutting down the system is the same as it was when we finished customizing MVS.
First you should log off all TSO sessions you have running with the TSO LOGOFF command. When you log off of TSO the tn3270 client window will again display the Network Solicitor screen.
To shut down TSO, on the MVS console, type P TSO and press Enter. If you have properly logged off all TSO user sessions, the shutdown will be quick and without fuss:
To shut down VTAM, on the MVS console, type Z NET,QUICK and press Enter:
You should be familiar by now how to shut down JES2 and MVS in an orderly fashion - $pjes2/z eod/quiesce - so I will not repeat those details here.
I hope that you have found my instructions useful. If you have questions that I can answer to help expand upon my explanations and examples shown here, please don't hesitate to send them to me:
This page was last updated on November 09, 2015 .