> halfmeg wrote:
>> Simon Williams wrote:
>> 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?
No, my setup was still very much an experimental one and I so I replaced the DASD images I had created with those in the update. I had created the system by following both the MVS Sysgen and MVS Customization sections of the New User Cookbook. I ran all scripts (having to fix makeadisk as it appeared to assume an earlier version of dasdload, which used different parameters) and all the sg* and mvs* jobs. The only ones I didn't run were those that removed accepted PTFs and, predicatably for am IT professional, the ones that took snapshots of the system!
>> 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.
It was under JES2 on the initial turnkey system that startrek couldn't be found!
>> 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.
I can't see why it should, given that entire DASD images would be overwritten, except in the case of changes in shadow files where the base image was overwritten and the shadow file contain updates to the original. I don't think I had shadow files on the images replaced by the update, but I can't be sure. I will try using the update as a standalone system and then add the other stuff back in and see what happens!
You didn't. I saw that the zip file did not contain all the DASD images that the CD created and assumed that that meant the update only replaced certain images. My mistake.
>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.
The messages weren't the ones in the Cookbook, very different, but a cold start sorted them out with no problem. It could have been to do with confusion resulting from me updating an existing system rather than IPL'ing the update standalone.
>> 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.
Same result under both JES3 and JES2, but I'll let you know once I've attempted a standalone IPL of the update.
>> 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 ?
As above, I did the full build.
>Which Hercules versions have you used and did one in particular permit using 2 CPUs without many problems?
Exactly the same build 3.07 rarely gave me a problem under standard Turnkey 3, but got it consistently under the update. I will report back after I try the update stand alone.
>> 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.
0C6 is defined as the JES3 console!!!!
>> 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.
I tried loading RPF 153 onto the system from the distribution tape last night and it didn't cure the problem, although I'm not sure that it would if the problems I am having are down to replacing existing DASD images with those I on the update and mixing those in with images from the existing system. As I said earlier, my system is very much an experimental one at present (although I am intending it to become more of a hobby). It currently has no value so I think I will starrt again using TK3UPD as the base. I still have all the control files I set up to create my extra DASD and the rest is just configuration editting. I'll report back in a couple of days.