While the structure of TSO is quite a bit different in MVT from what it became in later OSes, the function is definitely the same. The main difference is that, unlike in MVS, TSO users have a small piece of the address space which they share among themselves via a swapping mechanism managed by the TSO main task.
VTAM hadn't been invented yet, so all TSO use is through TCAM. TCAM is capable of controlling local 3270, remote 3270, and remote line-mode terminal devices; Hercules currently emulatesonly the first, so that's what we will set up. The procedure here will generate a TCAM with exactly one local 3270 device defined to it. Extending that definition to define multiple 3270s is straightforward.
The first step is to add JCL procs for TSO and TCAM to the
SYS1.PROCLIB dataset. This job does that. It can be found in
This job does two things:
SYS1.BRODCAST, as it does in later versions, contains all messages sent to a user by the SEND command and saved for later reading because the user was not logged on.
SYS1.SWAP0is the swap dataset managed by TSO to swap users in and out of memory.
TCAM is generated by a stage 1/stage 2 process similar to the OS itself.
Fortunately, both steps are quite a bit simpler than those. Stage 1 is
done by feeding a source deck to the assembler, which produces assembler
output that builds the actual TCAM message control program (MCP). Stage 1
jcl/tcamstg1.jcl. Before starting it, if HASP is not
running, you need to start a writer for the punch output in SYSOUT class B.
Do this by entering the command
s wtr,00d,,bon the MVT console. If HASP is running, this is unnecessary, as it automatically runs the writer for you.
jcl/tcamstg2.txt. Edit this file, insert the contents of
pch00d.txtwhere the comment (surrounded by rows of !!!!! - delete those) indicates it should go, save the modified JCL as
jcl/tcamstg2.jcl, then run that. The supplied
jcl/tcamstg2.jclfile is the result of running the supplied stage 1 gen, and may be used unmodified if the stage 1 deck has not been changed.
TCAM may be started, once the stage 2 is complete, by entering the command
s tcamon the MVT console. Aside from the message that says TCAM has been started, nooutput will be produced. Start TSO by entering
s tsoThis will be more verbose:
IEF403I TSO STARTED TIME=13.20.22 IKJ017I SMF NOT ACTIVE - SMF PARAMETER IGNORED IKJ016I REGNMAX=1 - REGIONS STARTING=1 IKJ030I SYSWAP00,000300,000300 SWAP DATA SET FORMAT IKJ090I TSO DUMP FUNCTION INOPERATIVE IKJ052I TIME SHARING REGION 01 HAS STARTED IKJ019I TSO HAS BEEN INITIALIZEDThe
IKJ030Imessage will only be produced the first time TSO is started. At this point, it's all running.
Logging on under TCAM is finicky, at least on MVT. To log on, you must follow these steps:
IKJ54012A ENTER LOGON -This message is issued by TCAM.
IBMUSER LOGON IN PROGRESS AT 13:42:21 ON FEBRUARY 14, 1975 NO BROADCAST MESSAGES READYThe first time, you'll get a complaint about the broadcast dataset being unusable. This will be corrected when you define another user ID. To do so, logon as IBMUSER, then do:
accountYou'll be greeted with:
ACCOUNTThis tells you you're in ACCOUNT mode. This is the program that is used to define TSO users. Enter
add (userid * * ikjaccnt) oper acct jcl size(44)This will define a new user with the id userid. TSO user IDs must be no longer than 7 characters. The new user ID will have all of the same capabilities as IBMUSER, which is everything. As a side effect, the broadcast dataset will be formatted. Exit ACCOUNT by entering
endThis will return you to the READY prompt.
To shut down TSO, enter
p tsoon the MVT console. This will produce:
IKJ078I TSO TSO TSO IS STOPPING 05 IKJ024D TSO STOP IN PROGRESS, REPLY 'U' OR 'FSTOP' IKJ051I TIME SHARING REGION 01 HAS TERMINATED IEE400I THESE MESSAGES CANCELLED - 05. IKJ085I TSO MODIFY/STOP SUBTASK TERMINATED IEF404I TSO ENDED TIME=13.53.24The message IKJ024D will automatically be replied to, so you don't have to reply yourself.
To shut down TCAM, enter
z tpon the MVT console. This will produce:
IED097I TCAM IS CLOSED DOWN - IEF404I TCAM ENDED TIME=13.55.58At this point, TCAM and TSO are down. The system may be shut down if desired.
Up to table of contents Previous: Building and installing HASP Next: What's next?
Last updated 14 February 2003