TK3 Shadow Update Available - Again
2007-10-03 08:39:43 GMT
I have uploaded the TK3SU1.zip file again. It should stay online this
time around until I get another update out the door.
You can download it currently from:
Softlib is moving and classiccmp has graciously allowed us to be
hosted there. The softlib link will be redirected after I finish
uploading the rest of the old site to the new location.
Phil - original post replied to as I have forgotten everything we did
in the shadow update
There is a fixpack1.zip file as well which should be run after the
TK3SU1.zip is applied to correct a few minor/major glitches. It is
also found at the above link.
Good Luck all:
> halfmeg wrote:
> We have been working a little recently to bring you a fairly large
> update to the MVS TK3 system. The list of things included are
> All of the items 1 - 32 at:
> with updates of RPF and IND$FILE to even more recent versions and a
> bug fix for the XMIT/RECV package.
> I believe that 2, 5*, 6, & 7 on the still to-do list are also done.
> ( * JES3 is a very recent addition and currently is on the same
> sysres as JES2 ).
> As with a lot of things, some small things slip through the cracks.
> I forgot to include a README in the update zip file itself. One of
> the testers reported a need to specify a REGION statement on jobs
> submitted under JES3 as I didn't increase the default from 52K or
> So without further ramblings, you can obtain the update zip file at:
> www.box.net/public/at0xixe608#main < no longer valid <<<<----<<<<<
> It is slightly less than 63 Mb.
> It should be applied to a fresh or clean install of the TK3 base
> system. You don't have to have all the packs installed. If you
> selected to leave the CBT, SRC, SMP and starter system packs
> uninstalled, this update should still work with your MVS
> So the procedure would be.
> 1. Clean install of TK3.
> 2. Unzip of TK3SU1.zip into the directory where TK3 was installed
> ie c:\mvs38j or similiar
> At this point a new config file ( TK3SU.conf ) will be placed in
> your config directory which will need to be used for hercules
> startup. If you start Hercules with the line commands it would be
> something like:
> hercules -f conf\tk3su.conf
> New DASD base files for the added packs like DLIxxx and JSxxxx will
> be added to the DASD directory and the bulk of the data will be
> added to the SHADOW directory as shadow disk files.
> For routine operation of JES2, the startup is identical to 1st time
> TK3 startup I believe.
> 3. Start hercules
> 4. Connect your 3270 client and telnet client as you would normally
> 5. IPL 148
> 6. to IEA101 message reply R 0,CLPA
> 7. JES2 will terminate due to unformatted spool and checkpoint
> 8. S JES2, reply 'r x,cold,format'
> 9. $S when it asks you to enter requests
> 10. The system should be up and running at this point with all the
> new stuff ready to use.
> Now for those who want to experiment a little. You can run the
> updated system with a security package. You have a choice of 2
> different ones, RAKF or PIES. This is currently only available with
> the JES2 environment and has to be selected at IPL time. When the
> IEA101 message appears, reply, 'r 0,sysp=PI' for PIES or
> 'r 0,sysp=RA' for RAKF.
> For the even more adventurous, you can experiment with JES3. At IPL
> time when presented with the IEA101 message, reply r 0,sysp=j3 and
> you will soon see some different messages and required responses to
> bring JES3 up and running.
> IAT3011 SPECIFY JES3 START TYPE
> *00 IAT3011 (L H HA W WA OR C)
> give this a r 0,C
> *01 IAT3033 CONFIRM JES3 COLDSTART REQUEST (U)
> and a r 1,U
> *02 IAT3012 SELECT JES3 INISH ORIGIN (N M= OR U=), AND OPTIONAL EXIT
> PARM (,P=)
> and a r 2,N
> then this shows up
> 0142007 IAT3100 JES3 3.0.0 SYSTEM COLDSTART ON 6.337 AS SY1
> enter *s jss
> An important note here, we haven't configured any JES3 consoles in
> the system ( remember very recent addition ) so the telnet console (
> formerly 009 now moved to 01F ) is your main console for JES3 as
> delivered currently.
> You can start the card reader and output printer.
> *x cr,in=00c,k
> *x wtr,out=00e
> 8s 00e
> * & 8 are interchangable in the JES3 command systax for 1st
> You are now ready to run a job, but not to logon on TSO. Why you
> may ask. Because of that other twist of fate. I didn't add all
> the start up commands that the JES2 side already has in place. If
> you want to run under JES3 and log on to TSO , just enter 's net' &
> 's tso'. Your 3270 client tso terminal should be ready for you to
> logon. This should also help to remind you that the JES3 stuff is
> a work in progress.
> How do I shut this beast down. Ok, if you have started up TSO,
> enter 'p tso' followed by a 'U' to the reply that appears. Then
> enter 'z net,quick' to shutdown VTAM. Enter 'P CMD1' to stop CMD1
> and finally you enter '8return' to shutdown JES3. You can now
> 'power off' Hercules.
> If it all works, it's the effort of many people, if it's broken,
> blame me.
> Phil - a space blanket, that's what I need - they'll never find me
> in space