🚀 go-pugleaf

I thought I sent the following yesterday, but our system
is messed up lately, and I dont know if it made it there,
as it didnt really send it back to me(something that it
did for the test I send a few min ago), so here I am
resending it. Feel free to delete it if you've already
read it.

-----------------



I have been busy lately(havent we all) and didnt have
the time to answer right away, but I'd like to explain
a couple of things about the zaps or fixes naming convention.

Its probably better if I do it using an example or base,
so let that be vmsecure.

Currently there are 2 releases of vmsecure supported
the 4.4A release and the 4.4B release. I know a hand full
of people have 4.40 out there, but that was the LA or
Limited Availability release(post Beta if you wish) and
noone should really have that running production, but
anyway.

Well, suppose SCI makes a zap while 4.4A is in production.
It will be named X44Annn. Now, if this zap applies to the
4.4B release as well, it will not be copied to a X44Bnnn,
but will instead keep its old regular name. The 4.4B
summary file will include it, so that folks know to
apply that as well to the 4.4b release.

Another example. Suppose sci made a fix when 4.4 was in
production(it never really was, but for the sake of the
argument lets assume so). It was named X440nnn. Now if this
fix applies to 4.4A and even further to 4.4B, then it will
keep its X440nnn name, and that name will be included in
the summary file of both releases.

This is how things have always been here, and this stands
for all products.

As a result, the recommended way of applying maintenance
would be to obtain the product summary file, check and
find which zaps/fixes apply to your system(some are
for HPO only, some for XA etc, some might have an APAR
as a prereq etc) and then apply these zaps/fixes
REGARDLESS of the first 4 characters of their name.

The reason this convention is used is of course
maintenability. Its a lot easier to maintain one file
than 2 or 3 or even more. Careful here, I am not saying
this is my preferable way of doing things(I am not
saying its not either) so dont hit me :-) if you dont
agree with it, I am just saying how things are done
and what the naming convention is so that it might
help you apply maintenance easier and with fewer
headaches.

I hope that helps, have a nice day.

Nick Gavrielatos
ucnick@socrates.umd.edu