Product Install, UNDO and recovery data (again!) - VMS

This is a discussion on Product Install, UNDO and recovery data (again!) - VMS ; At the end of 2005 and early in 2006, there were about 3 threads asking about PCSI and deletion of recovery data. In particular, doing a PRODUCT INSTALL leads to a message similar to this: --------------------------------------------------------------------- * If you continue, ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: Product Install, UNDO and recovery data (again!)

  1. Product Install, UNDO and recovery data (again!)

    At the end of 2005 and early in 2006, there were about 3 threads
    asking about PCSI and deletion of recovery data. In particular,
    doing a PRODUCT INSTALL leads to a message similar
    to this:

    ---------------------------------------------------------------------
    * If you continue, recovery data for the patches listed above will be
    deleted.
    * The deletion of recovery data does not affect the installation status of
    * patches applied to products that are not participating in this operation.
    * However, continuing with this operation prevents you from uninstalling
    * these patches at a future time by use of the PRODUCT UNDO PATCH command.

    Do you want to continue? [NO] y
    ---------------------------------------------------------------------

    I *think* the conclusion from those discussions, particularly John
    Santos' post(s), was that (1) when doing PROCICT INSTALL of
    ECOs/patches, the recovery data is, or can be, saved and the patch
    backed out with a PRODUCT UNDO command; and (2) that a PRODUCT INSTALL
    of some product (not a patch) will delete the recovery data.

    My questions are:

    a) Is this summary pretty much correct?
    b) It doesn't matter if the patches are VMS patches and
    the product is something unrelated (Fortran for example),
    the VMS recovery data will *still* be deleted?

    I've run into this trying to install DFU 3.2 on VMS/Alpha 7.3-2 and
    find I cannot avoid the warning no matter what combination of
    /SAVE, /NOSAVE, etc., qualifiers I use. Just a sanity check.

    Thanks, Ken
    --
    Ken & Ann Fairfield
    What: Ken dot And dot Ann
    Where: Gmail dot Com

  2. Re: Product Install, UNDO and recovery data (again!)

    In article <5kp4e3F4snqaU1@mid.individual.net>, Ken Fairfield writes:
    >I *think* the conclusion from those discussions, particularly John
    >Santos' post(s), was that (1) when doing PROCICT INSTALL of
    >ECOs/patches, the recovery data is, or can be, saved and the patch
    >backed out with a PRODUCT UNDO command; and (2) that a PRODUCT INSTALL
    >of some product (not a patch) will delete the recovery data.
    >
    >My questions are:
    >
    > a) Is this summary pretty much correct?
    > b) It doesn't matter if the patches are VMS patches and
    > the product is something unrelated (Fortran for example),
    > the VMS recovery data will *still* be deleted?


    Yes and yes.

    Recovery data are saved in the PCSI$UNDO directories regardless whether
    it is an ECO for VMS or for a layered product.

    "Full kit" (you know, the kits with "*-1.PCSI*") installations delete
    the recovery data (saved by this "*-4.PCSI*") before their installation.

    Therefore my install recommendations are still:

    1) Install one kit after the other (and not more than one on the same time)
    2) Group them so that you have
    a) VMSINSTAL kits
    b) full PCSI kits
    c) ECO PCSI kits
    3) Always use an installation log file
    a) always use /SAVE_RECOVERY_DATA (or DEFINE PCSI$$SAVE_RECOVERY_DATA YES)
    b) always use /LOG (or define PCSI$LOG TRUE)
    c) always use /TRACE (or define PCSI$TRACE TRUE)
    4) Always delete all recovery data before the installation session begins

    ad1) this way you have only one product per logfile and you may remove
    this one product later by hand (if PRODUCT REMOVE doesn't work/exist)
    It also helps identifying where a file on the system disks belongs to.

    ad2) VMSINSTAL kits _MAY_ render your saved recovery data useless/corrupt
    and you/PCSI won't notice.

    ad3) this is for sanity of course (and gets as much info there as possible)

    ad4) or you end up having the deletion of umpteen PCSI$UNDO directories
    listed in the installation log of one (the first, and unrelated) full PCSI kit

    btw: TCPIP V5.5/V5.6 ECO1 is not an ECO, but a full PCSI kit instead!!

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

  3. Re: Product Install, UNDO and recovery data (again!)

    In article <5kp4e3F4snqaU1@mid.individual.net>, Ken Fairfield
    writes:

    > At the end of 2005 and early in 2006, there were about 3 threads
    > asking about PCSI and deletion of recovery data. In particular,
    > doing a PRODUCT INSTALL leads to a message similar
    > to this:


    > I've run into this trying to install DFU 3.2 on VMS/Alpha 7.3-2 and
    > find I cannot avoid the warning no matter what combination of
    > /SAVE, /NOSAVE, etc., qualifiers I use. Just a sanity check.


    I used to worry about this until I started using /SAVE on the PRODUCT
    INSTALL command. I think Peter Langstoeger finally cleared up my
    confusion.


  4. Re: Product Install, UNDO and recovery data (again!)

    In article <46e7a69e@news.langstoeger.at>, peter@langstoeger.at (Peter
    'EPLAN' LANGSTOeGER) writes:

    > 3) Always use an installation log file
    > a) always use /SAVE_RECOVERY_DATA (or DEFINE PCSI$$SAVE_RECOVERY_DATA YES)
    > b) always use /LOG (or define PCSI$LOG TRUE)
    > c) always use /TRACE (or define PCSI$TRACE TRUE)


    Good advice. In addition, before starting I do SET HOST/LAT/LOG to have
    a log of the entire session.


  5. Re: Product Install, UNDO and recovery data (again!)

    Peter 'EPLAN' LANGSTOeGER wrote:
    > In article <5kp4e3F4snqaU1@mid.individual.net>, Ken Fairfield writes:
    >> I *think* the conclusion from those discussions, particularly John
    >> Santos' post(s), was that (1) when doing PROCICT INSTALL of
    >> ECOs/patches, the recovery data is, or can be, saved and the patch
    >> backed out with a PRODUCT UNDO command; and (2) that a PRODUCT INSTALL
    >> of some product (not a patch) will delete the recovery data.
    >>
    >> My questions are:
    >>
    >> a) Is this summary pretty much correct?
    >> b) It doesn't matter if the patches are VMS patches and
    >> the product is something unrelated (Fortran for example),
    >> the VMS recovery data will *still* be deleted?

    >
    > Yes and yes.


    OK, thanks for the confirmation.

    > Recovery data are saved in the PCSI$UNDO directories regardless whether
    > it is an ECO for VMS or for a layered product.
    >
    > "Full kit" (you know, the kits with "*-1.PCSI*") installations delete
    > the recovery data (saved by this "*-4.PCSI*") before their installation.
    >
    > Therefore my install recommendations are still:
    >
    > 1) Install one kit after the other (and not more than one on the same time)
    > 2) Group them so that you have
    > a) VMSINSTAL kits
    > b) full PCSI kits
    > c) ECO PCSI kits
    > 3) Always use an installation log file
    > a) always use /SAVE_RECOVERY_DATA (or DEFINE PCSI$$SAVE_RECOVERY_DATA YES)
    > b) always use /LOG (or define PCSI$LOG TRUE)
    > c) always use /TRACE (or define PCSI$TRACE TRUE)
    > 4) Always delete all recovery data before the installation session begins

    [...]

    That process is all fine and well (3a,b,c), but in a case like mine,
    DFU wasn't installed when the other full kits were, and indeed,
    subsequent ECO kits were installed, thus the various PSCI$UNDO
    directories are present. But now I'm installing a "full kit" for
    DFU. Just seems counter-intuitive to me that DFU installation
    deletes recovery data for VMS732* ECO's. But such is life... :-}

    Thanks again, Ken
    --
    Ken & Ann Fairfield
    What: Ken dot And dot Ann
    Where: Gmail dot Com

  6. Re: Product Install, UNDO and recovery data (again!)

    In article <5krph7F54itfU1@mid.individual.net>, Ken Fairfield writes:
    >That process is all fine and well (3a,b,c), but in a case like mine,
    >DFU wasn't installed when the other full kits were, and indeed,
    >subsequent ECO kits were installed, thus the various PSCI$UNDO
    >directories are present. But now I'm installing a "full kit" for
    >DFU. Just seems counter-intuitive to me that DFU installation
    >deletes recovery data for VMS732* ECO's. But such is life... :-}


    Yes, it is hard to find out, that you forgot to install a full kit
    at "full kit time" and you would therefore loose recovery data.
    But in my case, the full kit will have to wait till the next installation
    session a few weeks later (as I want to find out which of the ECOs - if any -
    brought troubles with it).

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

+ Reply to Thread