I have a somewhat customized VK4- based MVS system which fills all my
needs and wishes, but there is something (not yet fully analyzed)
wrong with the 3375/80/90 DASD support. Making these devices PRIVATE
or taken offline (as many as possible) causes the shstem to run fine.
I have assumed that I somehow lost some updates when performing
an IOGEN, but now I am in doubt.
I have no particular interest in starting all over again with TK5
or updates to TK5 but J90010.het is of course interesting.
My question now is:
Is there a suggested path/method to UPDATE an existing system with
the updated usermod rather than update the DLIB and then rebuild
the complete system?
After realizing that the 3375/80/90 additions were actually SMP
ACCEPTed before generation and not part of the usermods that the
doc tells me to RESTORE before an IOGEN and APPLY again, it seems
less likely that I made some mistake when performing the IOGEN
via removing all LKED includes from the DLIB datasets which are
already in the present system rater than the RESTORE/APPLY method.
The DASD support in question would be on the DLIB!
While working with this, I happened to note the presence of a few
sysgen related macros in SMPMTS. They are UNITNAME, IODEVICE and
GENERATE from a set of changes named M026. When listing the CDS I
also find related changes named M023 and M024 (which prereqs M023)
but all is dated within a few days in 1984.
Thw modifications in the J90010 file uses the same M023 names
as are already ACCEPTed. I am not sure if SMP can sort out
how to perform such an update.
I can of course take each individual change from the J90010 file
and match my system and ZAP/Assemble-Linkedit any deltas found,
but I must also assume that in the future there will appear a
J90011 file with more corrections. Probably the changed macros in
SMPMTS are already SUPerceeded, but there presence could have
effect on other updates via SMP. The SMPMTS has no role in the
Stage1 - Stage2 processing.?
?
??
