User guide

22
DLOG Commands
(NTP 297-YYYY-545 or NTP 297-YYYY-350 — PCL NTPs)
Note: DLOG (Disk LOG) utility can be used to retrieve logs.
>DLOG enters DLOG utility >QUIT exits DLOG utility.
>EXCLUDEALL removes all logs, except PROTOLOGS from the set of
logs to be formatted. %% start out by excluding all
logs or it will dump out too many logs in the out file.
See the EXCLUDEPROTO subcommand.
>INCLUDEALL resets the set of logs to format to all logs except
PROTOLOGS. See INCLUDEPROTO subcommand.
>EXCLUDE accepts logs, except PROTOLOGS, to EXCLUDE
from format executed by FORMAT subcommand. See
the EXCLUDEPROTO subcommand.
>INCLUDE <logs> accepts logs, except PROTOLOGS, to INCLUDE in
format executed by FORMAT subcommand.
(i.e, >INCLUDE ISDN PM or >INCLUDE PM 189)
See INCLUDEPROTO subcommand.
>INCLUDEPROTO & EXCLUDEPROTO commands removes or
excludes all PROTOLOGS (TRAP, SWER, INIT, etc.)
from the FORMAT subcommand execution.
>STATUS displays the logs and PROTOLOGS
INCLUDED/EXCLUDED, earliest valid start time
and previous use information.
>
FORMAT
accepts parameters for date/time range and “tofile”
such as SFDEV, or “to terminal” to appear on screen.
>
FORMATFILE
accepts filename of unformatted DLOG file to format.
>LISTFILES displays the raw DLOG files recorded in the internal
table with their start times and end times.
>
PRINT <formatted filename>
print a copy of “tofile” in FORMAT.
Post-Release Software Manager (PRSM)
Quick References
(NTP 297-8991-540, Post-Release Software Manager (PRSM) Ref. Guide)
(NTP 297-8991-541, PRSM Basic Commands, Syntax, and Examples (with
PATCHER Command Comparison))
(NTP 297-8991-542, PRSM Quick Reference Guide)
Post-Release Software Updates
(PRSU) Statuses
Note:
Patches are called PRSUs.
PRSM assigns a status to each PRSU on every DEST (destination). There
are five different PRSU statuses.
NV - Needs Validating
—indicates a PRSU needs validating in the DEST.
VA - Validated for Application
—indicates PRSU can apply in the
DEST.
A - Applied
—indicates the PRSU is currently applied in the DEST.
R - Removed
—indicates the PRSU has been removed from the DEST.
NN - Not Needed
—indicates the PRSU is not needed in a DEST.
Note: A valid SPM non-permanent PRSU will have an NN status against
an SPMLOAD destination with the same loadname.
PRSU EXTENSIONS Using the Format 'AAANNTaa'
AAANN = baseid, AAA=alpha, NN=numeric
T = Processor Type: B - BRISC C - SUPERNODE
P - POWERPC I - ISN
X - XPM S - SPM
aa = Patch Release aa = alphanumeric)
Which PRSU files to keep/erase
CM, XACM and ISN (Intelligent Service Node) PRSU files, once applied,
are not required in order to remove the PRSU from the device. All of these
device types are capable of being imaged manually or automatically with
all the patches applied so re-applying PRSUs after reloading is not
required. Therefore, these files can be erased after being imaged to clean
up disk space and also reduce the time taken by the nightly file audit. The
one exception to this is ISN PRSUs during an office upgrade. The ISN
DESTs are loaded with the new release load and patched before the XACM
or CM is upgraded. It is recommended to keep these ISN PRSU files on
disk until after the XACM or CM has been upgraded to the new load and
the new PRSM has validated the PRSU files. The files can then be
removed since the new PRSM will now have captured the information
needed from the PRSU files. If retaining the ISN PRSU files is desired, it
is recommended that the files be placed in a volume not datafilled in table
PADNDEV.
Continues on the next page.