|
|
|
The product change status report assists you in planning PSP
upgrades by providing a complex-wide view of unapplied and
current CA MICS upgrade levels. Use this report to see which
units are impacted by unapplied product changes. You can
also track the status, date, and job name of product change
apply jobs.
The report has the following five sections:
o Apply Product Change Status Exceptions
Lists product change exceptions.
o Pending Product Change not Associated with a Unit
Lists unapplied product changes not associated with a
CA MICS database unit (for example, CA MICS Capacity
Planner Option or CA MICS Performance Manager Option).
o Pending Product Change Grouped by Product and Database
Lists unapplied product changes based on CA MICS
product with affected database units.
o Applied Product Change Status Grouped by Product
Lists applied product changes listed according to CA
MICS product.
o Applied Product Change Status Grouped by Date
Lists applied product changes by date.
Figure 4-1 illustrates a sample CA MICS PSP product change
status report.
+-------------------------------------------------------------------------------------------+ | CA MICS PSP PRODUCT CHANGE STATUS REPORT | | Reporting on CA MICS Complex: complex.prefix 05AUGyyyy 10:12:28 | | ------------------------- | | Section 1 -- Apply Product Change Status Exceptions | | Section 2 -- Pending Product Change not Associated with a Unit | | Section 3 -- Pending Product Change Grouped by Product and Database | | Section 4 -- Applied Product Change Status Grouped by Product | | Section 5 -- Applied Product Change Status Grouped by Date | | | | Product Change Status Exceptions | | No apply Product Change status exceptions were found | | | | Pending Product Changes | | Grouped by Installed Product and Database Unit | | SNT | | --- | | Units: (P:FORALL, 9:R2AXI) | | SNT6570 -- UNAPPLIED -- Product Change Date: 20JULyy -- NPM VTAM Buffer Pool Statist... | | SNT6560 -- UNAPPLIED -- Product Change Date: 15OCTyy -- ORGSYSID ???? Support and Co... | | | | Applied Product Change Status | | Grouped by Product | | ACT | | --- | | ACT7130 was applied 01JUNyy by mntjob0. | | ... | | | | BAS | | --- | | BAS7325 was applied 02AUGyy by mntjob5. | | ... | +-------------------------------------------------------------------------------------------+
Figure 4-1. Sample Product Change Status Report (Part 1 of 2)
+-------------------------------------------------------------------------------------------+ | | | Applied Product Change Status | | Grouped by Date | | CAP6410 was applied 05AUGyy by mntjob0. | | BAS7325 was applied 02AUGyy by mntjob5. | | ACT7140 was applied 28JULyy by mntjob1. | | CIC6550 was applied 16JULyy by mntjob1. | | MQR7140 was applied 13JULyy by mntjob3. | | STG6080 was applied 13JULyy by mntjob0. | | RMF6710 was applied 09JULyy by mntjob1. | | MQS6410 was applied 07JULyy by mntjob1. | | AUM6380 was applied 02JULyy by mntjob2. | | ACT7130 was applied 01JUNyy by mntjob0. | | | +-------------------------------------------------------------------------------------------+
Figure 4-1. Sample Product Change Status Report (Part 2 of 2)
To generate the CA MICS PSP Product Change Status Report, do
one of the following:
o Submit the PSPSTAT job in sharedprefix.MICS.CNTL. You
can run this job in batch mode.
o Select Option 4 (Submit the PSP Status Report) on the
Status panel (MWF;5;2;1;4). See Appendix E for a
description of the Status panel.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |