Harold Grovesteen firstname.lastname@example.org [hercules-390]
2015-12-05 16:19:06 UTC
thread is the foundation, I would like to take the topic in a different
I have participated in more than one email conversation on the topic of
MTS assembler(s) and the TABLES module.
As Mike Stramba articulated, from the standpoint of making MTS useful,
the ability to modify the TABLES module seems to be advantageous,
assembler considerations aside. Only the most knowledgeable MTS
aficionado will be rewriting or wanting to assemble internal modules.
I also got the impression that there are no detailed descriptions of the
structure of the "module" once assembled. That, in fact, the macros
themselves are the documentation. I hope I am wrong on that count.
Documenting what this module looks like and what values are used in what
fields for what purposes seems to me to be a prerequisite to any
At present, MTS has a very small community of MTS professionals.
Certainly that is needed. But, a broader community is needed to make it
survive. More than once, I have seen individuals start exploring MTS
and the first issue that arises is adding a new disk or some other
device for the person's exploration. I see some emails on the MTS list.
And then they die.
I have seen other efforts die for lack of community. Open Solaris on z
I believe is a recent example. The project was kept under wraps by the
implementers. When trouble developed, there was no place to go for help
and it died. There were those willing to help.
The inability to adjust the configuration seems to me to be a usability
hurdle limiting the MTS community's size. Once the module is
documented, others could conceivably work on getting a new
implementation with varying approaches possible, both from within MTS
and external to MTS. And, it may not require an MTS professional to do
that. Just someone who understands assembler macros.
MTS I believe is following in the same path as Open Solaris on z. The
MTS professionals seem to keep everything to themselves. Without
getting individuals outside of the current core group, it will have
difficulties moving forward. Overcoming the current usability issues I
believe is needed as a start to that. This is not meant as criticism,
but an observation based upon other lessons learned. I don't know what
priorities exist, if any. But making MTS easier for more people to
become involved I believe is critical. More involvement by the MTS core
group with the Hercules community from which the MTS community needs to
draw users would be encouraged. Out of sight, out of mind. For the
most part, MTS is out of sight.