User guide

23
XPM and SPM PRSU files need to be kept on disk for as long as the PRSU
is at applied status. This is because the PRSU file is always required in
order to remove the PRSU from a DEST, and to automatically re-apply the
PRSU following a reload or RTS of the device. Any applied XPM or SPM
PRSU will have a file alarm raised if PRSM is unable to locate the PRSU
file. If the applied XPM or SPM PRSU file is moved, it is recommended
that the PRSU be validated following it being moved so the alarm will not
be raised.
Missing PRSU Files
For situations where the current PRSM discovers PRSUs that have been
applied by another instance of PRSM (for example an LIU7 patched image
from another switch loaded into the LIU7), it is important that PRSM vali-
date the PRSU files. PRSUs in this situation can display “???” for the cat-
egory field. If this situation is encountered, retrieve a copy of the PRSU
file and validate the PRSU in one of the DESTs that shows a category of
“???”. PRSM will then take the information from the PRSU file and place
it in the PRSM database and the category will change to what it is supposed
to be.
Note: The above procedure can be avoided if all of the PRSU files are
located, placed in the users search patch, and a dbaudit is performed fol-
lowing loading of the DEST with the patched image. The dbaudit will find
the PRSU files and immediately populate the PRSM database with the
missing information. Dbaudit is only capable of doing this on the first
attempt. If there are category “???” present in the PRSM database, then it
is too late for the DBAUDIT command to correct the situation. Validating
with the PRSU file is the only way to get the category to the correct value.
OBSolete/OBsolete Emergency (OBS/OBE) PRSUs at VA status
An OBS or OBE PRSU can be found at VA status. This is normal and not
a cause for concern. When a PRSU changes category to OBS or OBE,
PRSM needs to be informed. This occurs when a file with a file name of
<PRSUID>$DF is downloaded and validated. This file is just the adminis-
tration section of the patch and is erased after validation automatically. If
the PRSU has already been removed when this occurs, the patch transitions
from R to VA, the category goes from what it was (GENeral (GEN) for
example) to OBS or OBE, and AUTO APPly (AUTOAPP) goes to N. The
only way to get the OBS/OBE PRSU back to R at this point is to apply it
and then remove it — which is NOT RECOMMENDED. The process
requires that the OBS/OBE PRSU file be removed from the site after
removal from all DESTs in the office so an accidental apply cannot occur.
Note: For XPM PRSUs the category will not change to OBS or OBE since
the only two categories allowed for XPM PRSUs are SouRCe (SRC) and
MANual (MAN). However, the AUTOAPP field will be N following
validation of the obsolete $DF for XPM PRSUs.
SPM loadfile destinations
When an SPM loadfile is datafilled in table PMLOADS, a destination is
added to the PRSM database with the type of SPMLOAD. The SPM per-
manent PRSUs associated with the SPMLOAD are placed in the PRSM
database during a dbaudit of the SPMLOAD. These PRSUs are contained
within the load file and cannot be removed from the SPMLOAD DEST
(hence the designation permanent).
The DBAUDIT command can be issued manually following adding of the
loadfile to PMLOADS, but this is not required since the nightly status audit
will perform a dbaudit on all SPMLOAD DESTs in the office.
An SPM loadfile which contains non-permanent (and thus removable)
PRSUs is called a Pre-Patched Spectrum Load (PPSL). The filename of a
PPSL has 2 characters (a letter followed by a number) appended to the 14
character milestone file name. The DESTID in PRSM will only refer to the
14 character loadfilename for both milestone and PPSL files.
To determine what non-permanent PRSUs are resident in a PPSL, the
SPMLFINFO command can be used. For a PPSL there is an additional
permanent PRSU which contains a list of the resident non-permanent
PRSUs in its description text. The naming convention of this permanent
PRSU starts with “SPPSL” followed by the 7 character loadname of the
given SPM load. A space separated list of removable PRSUs contained
within the load will be displayed in the description section of this PRSU.
An example command line would look like:
>spmlfinfo cem16cm_010064a2 qprsu SPPSLCEM16CM
It is recommended that the PRSU files associated with the contained
removable PRSUs be located and validated before the PPSL is datafilled in
table PMLOADS, but validation can be done after. Note that a validation
of the given SPM PRSU file must be performed and the file must be avail-
able in order to remove the PRSU.
Note:
A PPSL is the same as the milestone load with the patches already
applied. It behaves the same as the milestone load with the patches applied
via PRSM. Therefore, there is no reason (under normal circumstances) to
upgrade from a milestone load to the PPSL version. Simply datafill the
PPSL in PMLOADS to be prepared for any future reload from disk (man-
ual or system).
PRSM Quick References continue on the next page.