Thanks for the explaination. I never thought you were picking on my
contribution but I did wonder why the detailed audit trail interest.
Knowing what you are attempting to accomplish, I understand why the
interest in the details.
--- In turnkey-mvs <at> yahoogroups.com, "halfmeg" <opplr <at> ...> wrote:
> > cedarlakebuzzards wrote:
> > Oh No - Busted by the IT auditor.
> > I did not think any one would be interested in such detailed change
> > control/audit trail information.
> Yes, we have your code in lockup. Would you like to have the Public
Defender visit? Bail hasn't been set yet but we understand that there
are numerous bonding agencies available to release your code until final
> The primary reason I 'audited' your contribution is that I have
finally gotten some breathing room to restart the TK3 Update work. I
released a pre-Beta version to several developers and some testers back
late last year. Bug reports came back and a list of modifications
needed was saved on a disk which currently only exists as a Ghost Image
of the drive.
> I had hoped to update the Host software to XP from Win2K by having 2
partitions and just running the restored Beta environment out of the
non-Host OS partition. The initial try didn't work out so well and I am
rethinking what to do for that situation ( currently disk has been
zeroed out ).
> Finally we get to the why proper. There have been numerous
modifications to TK3 which normally occur in one of two methods, under
SMP control ( like usermods ) and outside of SMP control ( like RPF ).
> When we distributed TK3SU1, it was pretty much a rush thing and I had
set an artificial deadline to make it available. USERMOD changes
consisted of rejecting prior mods and submitting a reworked item. Some
new, never before in TK, were added and several independent installs
were performed, such as RPF and JRP.
> In the pre-BETA I elected to trim or not store the USERMODs on DASD.
An example of trimming is JRP where all the source except for the module
where password changes are made and JCL to relink after password
customization were deleted to conserve space. The SMP USERMODS were
submitted from the card reader and never uploaded to be saved on DASD.
> The net result of my attempt to reduce the size of TK3 Update was
pretty successful. By dropping the MVS and CBT source packs and doing
some extra-ordinary work, the size of TK3 Update wound up being less
than 70 MB zipped. That isn't a shadow update or non-SMP environment,
it's a standalone MVS environment with many things the original TK3 and
TK3SU1 didn't have.
> Since there are multiple versions of some USERMODS now running on
various levels of TK3, my 'audit' was intended to help me in figuring
out how to maintain a history if not the actual sources along the way
for the various modifications. Perhaps that isn't a valid concern, but
like I stated it has been awhile since I touched any of this and getting
my feet wet again has to start somewhere.
> Phil - didn't mean to pick on your contribution personally