You have installed to MVS Tur(n)key system from CD-Rom, and are ready to try it out. Where do you start?
First start the Hercules emulator.
This can be done by using the script startmvs
in the Tur(n)key installation directory. There will be many messages
flying by, and then you will see something like this:
190 3380 e:/mvs38j_test/dasd/work03.190 [1113 cyls] open + 0191 3390 e:/mvs38j_test/dasd/mvscat.191 [1113 cyls] open 0240 3350 e:/mvs38j_test/dasd/pub000.240 [555 cyls] open 0248 3350 e:/mvs38j_test/dasd/mvsdlb.248 [560 cyls] open 0280 3380 e:/mvs38j_test/dasd/pub002.280 [1770 cyls] open 0150 3330 e:/mvs38j_test/dasd/start1.150 [808 cyls] open 0151 3330 e:/mvs38j_test/dasd/spool0.151 [808 cyls] open 0340 3350 e:/mvs38j_test/dasd/cbt000.340 [555 cyls] open 0341 3350 e:/mvs38j_test/dasd/cbt001.341 [555 cyls] open 0342 3350 e:/mvs38j_test/dasd/cbt002.342 [555 cyls] open 0343 3350 e:/mvs38j_test/dasd/cbtcat.343 [555 cyls] open 0348 3350 e:/mvs38j_test/dasd/src000.348 [555 cyls] open 0349 3350 e:/mvs38j_test/dasd/src001.349 [555 cyls] open 034A 3350 e:/mvs38j_test/dasd/src002.34a [555 cyls] open 034B 3350 e:/mvs38j_test/dasd/src003.34b [555 cyls] open 0149 3350 e:/mvs38j_test/dasd/smp001.149 [560 cyls] open 014A 3350 e:/mvs38j_test/dasd/smp002.14a [560 cyls] open 014B 3350 e:/mvs38j_test/dasd/smp003.14b [560 cyls] open 014C 3350 e:/mvs38j_test/dasd/smp004.14c [560 cyls] open > panrate 1000 Panel refresh rate = 1000 millisecond(s) HHC429I EOF reached on .RC file. Command ==> CPU0000 PSW=00000000 00000000 0000000000000000 M....... instcount=0
You should now attach at least three 3270 session to the Hercules engine,
and one standard telnet session. You can either do this manually, or
edit the script startterm
in the Tur(n)key directory.
You will see the following messages
HHC604I Client 192.168.1.196 connected to 3270 device 0010 HHC604I Client 192.168.1.197 connected to 3270 device 0011 HHC604I Client 192.168.1.196 connected to 3270 device 00C0 HHC604I Client 192.168.1.197 connected to 3270 device 00C1 HHC604I Client 192.168.1.197 connected to 3270 device 00C2 HHC604I Client 192.168.1.196 connected to 3215 device 0009
You can now initiate the MVS bootstrap process (IPL, for Initial Program Load) by entering
Command ==>ipl 148 CPU0000 PSW=00000000 00000000 0000000000000000 M....... instcou
Which tells the system to read the IPL program from Track 0, Record 0 of device 148, which is our MVS system residence device. On the hercules console you will see the messages
CPU0000: SIGP CPU0001 Initial program reset PARM 00000000 000C:CCW=03000000 20000001=>040E0000 00041572 00000000 00000000 ................ 000C:Stat=0E00 Count=0001 000C:Sense=40000000 00000000 00000000 00000000 00000000 00000000 000C:Sense=INTREQThese are no error messages, just an info that something needs to be done eventually on device 00C. (That is our reader for jobstreams that we want to send to MVS. No need to worry now).
Switch to the TN3270 session on address 010, which is our MVS master console. After a very short time you should see
| IEA101A SPECIFY SYSTEM PARAMETERS FOR RELEASE 03.8 .VS2See the cursor in the lower left area of the screen? Don't try to place it anywhere else, it is in the correct position. If this is the first time we start MVS, or after some changes to
SYS1.LPALIB
, we now
enter
r 00,clpaand the system will react with
| IEA101A SPECIFY SYSTEM PARAMETERS FOR RELEASE 03.8 .VS2 | r 00,clpa | IEA940I THE FOLLOWING PAGE DATA SETS ARE IN USE | PLPA ... SYS1.PAGELPA | COMMON . SYS1.PAGECSA | DUPLEX . SYS1.DUPLEX | LOCAL .. SYS1.PAGEL01 | LOCAL .. SYS1.PAGEL02
And what happens, when this the very first time the system is IPLed, and you just press enter, without the CLPA option? The system will complain:
| IEA101A SPECIFY SYSTEM PARAMETERS FOR RELEASE 03.8 .VS2 | | IEA939D QUICK AND WARM START DATA IS INVALID, | RE-IPL OR REPLY 'GO' FOR COLD START
Now you can either start from square one, or answer
r 00,go
to continue with the IPL and CLPA (Create Link Pack Area). Shortly afterwards, the screen clears, and new messages are displayed: If this is the very first start after Spool/Checkpoint have been built, the system will show the following
IEE360I SMF NOW RECORDING ON SYS1.MANX ON MVSRES TIME=22.01.38 IGF992I MIH INIT COMPLETE, PRI=000300, SEC=000015 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED *00 $HASP479 UNABLE TO OBTAIN CKPT DATA SET LOCK - IO ERROR - * REPLY Y OR N TO CONTINUE
to which you reply with
r 00,y
and what happens now? JES2 refuses to start nevertheless:
- r 00 SUPPRESSED IEE600I REPLY TO 00 IS;SUPPRESSED - $HASP434 WARM START DENIED -- INVALID CHECKPOINT RECORD - $HASP428 CORRECT THE ABOVE PROBLEMS AND RESTART JES2 - $HASP489 INITIALIZATION MAY NOT HAVE RELEASED CKPT DATA SET LOCK - $HASP085 JES2 TERMINATION COMPLETE
The Tur(n)key system is built in such a way that JES2 automatically gets started with the warm start option. This is the appropiate choice in nearly all cases. Not now, though, when spool and/or checkpoint have just been built. Okay, then we start JES2 like this
s jes2
and we now see the message
- s jes2 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED *01 $HASP426 SPECIFY OPTIONS - HASP-II, VERSION JES2 4.1
to which you reply
r 01,format,noreq
You could have provided the statrtup option in the start command as well, like this
s jes2,,,parm='FORMAT,NOREQ'
JES start up now continues (hopefully), and the next message might get thrown your way
*02 $HASP479 UNABLE TO OBTAIN CKPT DATA SET LOCK - IO ERROR - * REPLY Y OR N TO CONTINUE
The correct reply now of course is
r 02,yfollowed by
IEE600I REPLY TO 02 IS;SUPPRESSED *03 $HASP436 REPLY Y OR N TO CONFIRM CHECKPOINT RECORD CHANGE
and
r 03,y
Startup of JES now continues, and you might see more messages
IGF992I MIH INIT COMPLETE, PRI=000300, SEC=000015 IEE360I SMF NOW RECORDING ON SYS1.MANX ON MVSRES TIME=14.29.46 IEF677I WARNING MESSAGE(S) FOR JOB JES2 ISSUED - $HASP493 JES2 QUICK-START IS IN PROGRESS - $HASP412 MAXIMUM OF 1 READER(S) EXCEEDED * *IEA000A 00C,INT REQ,42,0E40,4000,,,JES2 IEE041I THE SYSTEM LOG IS NOW ACTIVE $HASP000 OK $HASP000 OK $HASP000 OK $HASP000 OK $HASP000 OK $HASP000 OK $HASP000 OK $HASP000 OK $HASP000 OK $HASP000 OK $HASP160 PRINTER1 INACTIVE - CLASS=A $HASP160 PRINTER2 INACTIVE - CLASS=Z IEE152I ENTER CANCEL D C,K IEE159E MESSAGE WAITING
Note: The message $HASP412
can be safely ignored. There
is only one reader defined to JES2, but we have provided more than
one reader device in the Hercules Configuration.
And now? The system seems to stop. Nothing is happening any more. See the message at the bottom right corner of the screen. This message tells you, that there are more messages for you to look at. How can you see those? You need to set the Console into RD (=Roll Delete) mode, which makes messages scroll off the top of the screen. This command is rather long, and thus the Turnkey system has a predefined function key to issue that command for you. Press F11 to invoke the command. You should issue F11 on the other console screen as well.
The automatic startup of MVS will continue, and many more messages will pass by,
scrolling off the top of the screen. There is no way to scroll
backwards!. If you want to see the messages of the past,
you need to revert to the hardcopy log. You find it in the
log
directory under the name hardcopy.log
When the dust settles, and no more messages appear, IPL is complete. You could now enter the command
IEE152I ENTER CANCEL D C,K D A,Land let MVS display the active Address spaces:
00- d a,l IEE102I 14.43.03 74.172 ACTIVITY 335 C 00005 JOBS 00006 INITIATORS CMD1 CMD1 CMD1 V=V JES2 JES2 IEFPROC V=V BSPPILOT BSPPILOT IEFPROC V=V S NET NET IEFPROC V=V TSO TSO STEP1 V=V S 00000 TIME SHARING USERS 00000 ACTIVE 00008 MAX VTAM TSO USERS IEE152I ENTER CANCEL D C,K IEE163I MODE= RD
As you can see, VTAM (NET) is active, and so is TSO. JES2 has been autostarted, and the MVS autopilot BSPPILOT as well. If you want to logon to TSO, take a look at How To Logon To TSO
The # command subsystem
is active (it has the name CMD1
). Enter the command
IEE152I ENTER CANCEL D C,K K E,Dto erase the data in the display area (see Controlling the Console Terminal elsewhere in this document). Then you could try
IEE152I ENTER CANCEL D C,K #ato show the active address spaces, or
IEE152I ENTER CANCEL D C,K #hto get help on the command subsystem, as well. You should read the Documentation though before using the powerful package
This 3270 MVS console is a tricky beast, but you learn to tame it soon enough. Let use first look at the console screen layout:
- d a,l - i smf | *IEE362A SMF ENTER DUMP FOR SYS1.MANX ON MVSRES IEE360I SMF NOW RECORDING ON SYS1.MANY ON MVSRES TIME=14.37.38 STC 568 $HASP100 SMFDAILY ON STCINRDR - STC 568 $HASP373 SMFDAILY STARTED - STC 568 IEF403I SMFDAILY - STARTED - TIME=14.37.38 - STC 568 IEF404I SMFDAILY - ENDED - TIME=14.37.39 - STC 568 $HASP395 SMFDAILY ENDED STC 568 $HASP150 SMFDAILY ON PRINTER2 36 LINES $HASP160 PRINTER2 INACTIVE - CLASS=Z STC 568 $HASP250 SMFDAILY IS PURGED IEE152I ENTER CANCEL D C,K IEE163I MODE= RDMessage IEE163I indicates that the console is in RD (=Roll Delete) mode: New messages are added to the screen at the lower end, and old messages scroll off the screen t the upper end of the screen.
The lines between IEE152I and IEE163I are the command area, It is here that you enter MVS operator commands.
The area above IEE152 is used by MVS to display messages etc. This area can be one single area, or
can be divided into separate display areas. This is done with the K A
operator commands
K A,10tells MVS that you want to split off a display area of 10 lines at the bottom of the message area. Messages in this display area do not automatically scroll off the screen, but stay there until you scroll them via the command, you can direct the output of certain commands to go into this display area. Other commands automatically route their output into the display area if it is defined. The system replies with
IEE928I DISPLAY AREA ID'S FOR CONSOLE 01 ARE Atelling you that it has created a display area with the name A at the bottom of the available screen. Why the need for a name? You could have requested more than one display area via
K A,5,8which would have defined display area A for 5 rows off the bottom of the message area, and display area B for 8 rows on top of area A. The command
K A,NONEremoves all display areas again. Just try
K A,10followed by
d a,lYou will see that the Display Active command output goes into the display area A, while the rest of the system messages continue to scroll in the upper part of the screen. You can scroll the display area by entering
K D,FIn the tur(n)key distribution you can use
PFK 8
to issue this command.
with
K E,D(or
PFK 7
you can erase the display area contents. Finally, just entering
Kwill erase (part of) the message area and scroll the messages upwards. You might want to look at the output from
D C,Kfor an overvire of console relaed commands:
d c,k 15.44.56 IEE162I 15.44.56 K COMMAND 551 K A,REF DISPLAY ALL DISPLAY AREA DEFINITIONS ,NONE DELETE ALL DISPLAY AREA DEFINITIONS ,LL DEFINE DISPLAY AREA OF LENGTH LL K C,D,ID CANCEL IN-LINE DISPLAY NUMBERED ID K D,N NUMBER MESSAGE LINES UNTIL DELETION REQUESTED ,N,HOLD NUMBER MESSAGE LINES ALL THE TIME ,F MOVE STATUS DISPLAY FORWARD ONE FRAME ,H HOLD DYNAMIC DISPLAY - DO NOT UPDATE ,U UPDATE DYNAMIC DISPLAY K E,SEG ERASE MESSAGE LINE SPECIFIED IN SEG=NN OPTION ,NN,NN ERASE MESSAGE LINE NN THROUGH NN ,F ERASE FLAGGED MESSAGES ,D ERASE OUT-OF-LINE STATUS DISPLAY ,N ERASE MESSAGE LINE NUMBERS K N,PFK=(NN,CMD='TEXT') DEFINE PFK NN AS COMMAND ,PFK=(NN,KEY=NN,NN,...) DEFINE PFK NN AS LIST OF KEYS ,CON=Y DEFINE PFK AS CONVERSATIONAL ,CON=N DEFINE PFK AS NON-CONVERSATIONAL K Q,R=HC RE-ROUTE THE MESSAGE QUEUE FOR THIS CONSOLE TO HARDCOPY ,R=CC RE-ROUTE THE MESSAGE QUEUE FOR THIS CONSOLE TO CONSOLE CC K S,REF DISPLAY ALL SPECIFICATION VALUES ,DEL=Y DELETE MESSAGES AUTOMATICALLY ,DEL=N DO NOT DELETE MESSAGES AUTOMATICALLY ,DEL=R ROLL ALL MESSAGES ,DEL=RD ROLL ONLY DELETABLE MESSAGES ,CON=Y DELETE MESSAGES WITH VERIFICATION ,CON=N DELETE MESSAGES WITHOUT VERIFICATION ,SEG=NN DELETE NN LINES WHEN K E,SEG IS ENTERED ,RNUM=NN ROLL NN MESSAGES (DEL=R OR RD) ,RTME=NNN ROLL MESSAGES EVERY NNN SECONDS (DEL=R OR RD) K T,REF DISPLAY TIME INTERVAL FOR DYNAMIC DISPLAY UPDATE ,UTME=NNN UPDATE DYNAMIC DISPLAY EVERY NNN SECONDS K V,USE=FC VARY USE OF DEVICE TO FULL CAPABILITY ,USE=SD VARY USE OF DEVICE TO STATUS DISPLAY ,USE=MS VARY USE OF DEVICE TO MESSAGE STREAM THE ROUTING OPERAND L=CCA IS ADDED TO A K COMMAND TO DEFINE AREAS ON ANOTHER CONSOLE, TO CONTROL A DISPLAY IN A PARTICULAR AREA, TO RE-ROUTE CONSOLE MESSAGES, OR TO VARY THE USE OF A CONSOLE.