In <[EMAIL PROTECTED]>, on 01/04/2008
at 12:38 AM, Shai Hess <[EMAIL PROTECTED]> said:
>I decide that for now it is better, faster and more reliable (you can
>make error when you code the SMP/E) to send the XMI load library for
>installation because it is small, it can have a lot of depandency which
>make the product more sensitive to errors (my opinion).
You can make errors regardless of your CM and packaging vehicles. SMP/E
makes sense when you send individual fixes and enhancements. If all that
you ever ship is a levelset replacing the entire product then SMP/E is
overkill.
>When I put fixes in my product I check the PC and the MVS component as
>one unit and that what I send to the users for installation.
As long as you never ship a fix that has only one side, or only part of
the PC side.
>If the date is newer then the working Load library for the user then the
>user must download the installation file (one Zip file) and check file
>"FIXINFO.DOC".
What keeps the MVS and PC sides in synchronization?
>In file "FIXINFO.DOC" I put comments about each fix and the date and the
> component which have been updated.
That sounds like you're relying on a manual process, which is error prone.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
