User guide

25
PRSM Quick References continue.
Patching After Loading (PAL)
Following a reload of an XPM device, PAL is invoked. The patches to be
applied are chosen by the status of the Apply On Reload (AOR) flag. If the
AOR flag is set to Y for any XPM DEST with the given loadname in the
office, then the PRSU will be reapplied following the reload. If the AOR
flag is set to N for all XPM DESTs with the given loadname, then the
PRSU will not be re-applied. Anytime a PRSU is applied to an XPM
device, PRSM automatically sets the AOR flag to Y for that PRSU on that
DEST. Conversely, anytime a PRSU is removed from an XPM device,
PRSM automatically sets the AOR flag to N for that PRSU on that DEST.
The AOR flag can also be set manually using the ASSIGN command. For
example, if one wanted to soak a PRSU in one DEST and did not want it to
be re-applied following a reload, just set AOR to N for the entire office:
>assign aor n in prsuset abc04x17 on xpm
PRSU abc04x17 will not be re-applied to any device following a reload.
SPM Patching After Return To Service (SPARTS)
Whenever an SPM destination is brought into service, the SPM mainte-
nance software sends a request to PRSM to execute SPARTS. SPARTS
will compare the patch content in the running device with the patch content
associated with the given loadname and remove/apply patches to bring the
device up to date patch-wise if required. What PRSUs are removed/applied
is based upon the AOR flag just like PAL in XPMs. If the AOR flag is set
to Y for any SPM DEST with the given loadname in the office, then the
PRSU will be re-applied following the RTS if required. If the AOR flag is
set to N for all SPM DESTs with the given loadname, then the PRSU will
not be re-applied and in fact will be removed if found applied. PRSM sim-
ilarly automatically sets the AOR flag to Y/N for a given PRSU on a given
device upon application/removal just like in the XPM case.
The steps SPARTS performs are the same as the steps performed by the
ISTBAUDIT command on an SPM device:
1. Query the SPM device whether or not a reload has occurred. If a reload
has occurred, then continue on to the next step. If not, then inform SPM
OAMP software that the patchfail is cleared and exit.
2. Run a dbaudit on the specified destinations to sync the destinations
with the PRSM database.
3. Remove any extra PRSUs applied to the specified destinations as
determined by the AOR flag (see above). This situation may occur with
a Pre-patched SPM load (PPSL) that contained an unwanted PRSU or
a device reloading from a stale flash image.
Note: There is a time delay following removal (or application) of a
patch to an SPM device before the patched image is copied from RAM
memory to flash memory. If an SPM device reloads from flash
memory during this time delay, then a patch that was recently removed
could show up as applied. This is an example of a stale flash image.
4. Apply any missing PRSUs to the specified destinations as determined
by the AOR flag (see above).
5. Inform SPM OAMP software about the status of the patchfail alarm
and exit. If the above 2 steps completed successfully, then patchfail is
cleared, and if not, then patchfail is failed for the given SPM device.
An SPM301 log is output to show the status of the patchfail alarm.
Note: Following any SPARTS failure (patches unable to be applied,
PRSM busy etc.) SPARTS will reattempt multiple times after the
failure at approximately 30 minute intervals.
The technique used in PAL for XPMs can be applied to SPMs to control
re-applying or removing a PRSU following an RTS, namely setting the
AOR flag to N for all SPM devices via the ASSIGN command:
>assign aor n in prsuset def09s0p on spm
PRSU def09s0p will now not be re-applied on any device following an
RTS and removed on any DEST that it is found applied to.
Other ways to control SPARTS (these do not work for PAL) is to place a
PRSU onhold or hold an SPM DEST:
>assign onhold y in prsuset def09s0p
The status of PRSU def09s0p will now be frozen and SPARTS will not be
able to re-apply it or remove it from any device.
>assign hold y in destset spm 3 cem 1
The patch content of spm 3 cem 1 will now be frozen and SPARTS will not
be able to apply or remove any PRSUs from the DEST.
AUTOPROC command
Use the AUTOPROC command to query the status of any or all of the
PRSM automated processes discussed on the following page. It can also be
used to START, STOP or DELAY any of the automated processes. Type
“prsm;help commands autoproc” for more information.
PRSM Quick References continue on the next page.