Re: State of Turnkey
2010-11-09 13:51:26 GMT
>> I have finally got round to giving the Turnkey 3 Update Beta a go
>> and have achieved some success, particularly in that I now have a
>> viable JES3 installation. I fed back my experiences to Carlos and
>> he has asked me to share them with the group.
>> I was a standard Turnkey 3 system, built from the starter system
>> using the sysgen instructions on the CD.
>So as to be clear about your setup, you have 2 separate environments. One that you built from starter system up and the other TK3UPD BETA?
>> The machine I am running on is a Toshiba i686 laptop with Nvidia
>> graphics running Debian Squeeze (all packages up to date as of
>> Saturday). My Hercules is 3.07 as packaged for Debian. I had added
>> extra printers, readers, terminals, tapes drives and lots of DASD to
>> the Turnkey 3 system and had the number of CPUs set to 2, but the
>> sysgen was standard (as I have not yet managed to find instructions
>> for rerunning the sysgen for an existing system).
>Am not sure if the jobstreams for IOGEN or MINIGEN were ever posted.
>> Everything worked reasonably well, although I had not got startrek
>> to work under TSO, it just told me it didn't exist!
>Possible that JES3 parml ib entries don't have all that is needed yet. JES3 is very new addition to TK3 so there may be many issues to be resolved.
>> Once I had loaded the updates (just unzip the downloaded archive
>> into the directory containing conf, dasd, etc.),
> Hmmm, not correct. TK3UPD is a self contained environment. Unzipping it into already populated directories may give unpredictable results.
>It does not have the CBT or MVS source DASD, but every thing else should be there. See post:
>Don't have the README.TXT handy right now, but don't believe I mentioned overlaying anything already existing.
>To regain use of CBT and MVS source DASD you can copy them into the DASD directory. At least I believe I left the entries in the tk3upd.conf >file.
>> I IPL'd the emulator and (after some very scary messages during the
>> initial JES2 startup and subsequent failure!) managed to do a cold
>> start of JES2 and all looked reasonably good.
>Sounds like normal initial JES2 start, thought that was mentioned in the Turnkey Cookbook but don't see it currently.
>> One point I did note was that CMD1 abends S106 on every startup.
>Under JES2 or JES3 ? Either way possible side effect of mixing system built previously with TK3UPD. If JES3 only, then possible parmlib or >memory size issue.
>> I then tried amending the config to include NUMCPU=2 and
>> consistently had a problem with a processor spin being detected on
>> the second CPU. This happened occasionally with the original
>> Turnkey 3 installation, but now happens consistently. I have fallen
>> back to a single CPU and that seems to be fine.
>This has been a intermittent issue for a while which I would like to resolve. Did your initial build of TK3 from scratch add all the PTFs or did you >build as Jay Moseley's build with minimum PTFs ?
>> When I originally tried to start JES3 (IPL and then r 00, sysp=j3),
>> I had a problem as it was complaining that it didn't have a console
>> on device 0009 (it has been moved to 001F).
>And it may have been moved back to 009. I can't remember right now what the issue was but a post mentioned 01F which is no longer correct if it >was moved back to 009. Believe the address is in the JES3INISH deck.
>> It was also complaining about a missing printer at 030F and a
>> missing console on 00C6.
>30F is known issue, 0C6 is something which I don't recall at all.
>> I added these by duplicating the telnet definition on 001F for
>> 0009, duplicating the printer on 030E (with a different file name)
>> for 030F and adding a 3270 device on 00C6. All terminals are
>> connected before IPL, that is telnet x 2 for devices 0009 and 001F
>> and X3270 x 6 for devices 0010, 0011, 00C0, 00C1, 00C2 and 00C6.
>> Once I had done this, JES3 started with no problems.
>> Once I had this up and running, I tried logging in to TSO, which
>> worked, but I got a couple of abend messages during statup and my
>> brief testing (the other half was nagging me to stop playing with my
>> toys as we had important stuff to do!) showed that although TSO was
>> functional, t here are problems with it.
>> Startrek couldn't find a couple of files (although it didn't run at
>> all in the original, so it was a step in the right direction), but
>> more worryingly RPF would not run.
>STARTREK has issues due to the load modules which were part of the CBT file 35, quick add of modules, are depending upon Fortran runtime >libraries TK3 doesn't have. We only have G & H. The source for STARTREK on CBT is for a later version of Fortran. The fix is minor in that a >format statement needs to be added for input variables. The fix is major in that it needs over 100 of these to be 'fixed'.>
>RPF and other things may be due to PARMLIB entries missing for JES3.