Here is a condensed checklist for upgrading to a new release of CA MICS.
1. Receive the Product Service Pack (PSP) files on the mainframe from CA Support Online.
a. Run CAtoMainframe batch job to FTP directly to Unix System Services (USS) on the mainframe.
b. Use batch UNPAX job to UNPAX the file on USS.
c. Edit UNZIP file in the UNPAXed folder, BaseInstall, on USS. Add a job statement and make changes to the JCL as noted, and submit.
The result of completing step 1 will be 17 yourHLQ.CAI.MICSESD.* datasets on z/OS.
Reference: PAX Enhanced User Guide (TEC342790) on CA Support Online
2. Load the maintenance into the CA MICS PSP Libraries.
a. Use the PSP Refresh checklist to load the maintenance to the PSP libraries. You may do this via a batch job or the PSP Panel. Both methods are documented in the PSP refresh documentation.
b. Receive the new PSP tables – MWF;5;2 (Follow prompts to receive the new tables.)
The result of completing step 2 will be that the PTFs delivered with the new MICS PSP are displayed on panel MWF;5;2;1;2.
Reference: How to Use the PSP Guide section 2.2 in the MWF documentation and the topics PSP Refresh Process and Checklists (Panel and batch checklists) in CA MICS online documentation (https://docops.ca.com/ca-mics-resource-management/14-0/en/using/product-support-program-psp/psp-library-refresh-and-checklists/psp-refresh-process-and-checklists)
3. Apply the PSP Maintenance via MWF;5;2;1;2
a. Complete all steps in the product change checklists.
b. Apply multiple product changes at the same time by using the consolidated checklist option in PSP.
c. Begin with the BASE product changes as these are prerequisites for many of the analyzer changes.
d. Run operational jobs after each set of maintenance so that problems will be easier to isolate. Carefully review the output of operational jobs and reports to ensure there are no errors in the jobs or problems with the reports.
e. After the BASE product changes, select groups of PTFs by analyzer or groups of analyzers. Base the size of the PTFs selected on the number as well as time available to complete the checklist before the next operational job is scheduled to run.
f. Keep detailed notes so information that might be helpful to support is available, if problems occur.
The result of completing this step will be that all of the PTFs displayed at the end of step 2 will be applied. There will be no PTFs on MWF;5;2;1;2.
Reference: How to Use the PSP Guide chapter 3 and the topics: Selecting the Product Changes to Apply and Applying Product Changes in CA MICS online documentation (https://docops.ca.com/ca-mics-resource-management/14-0/en/using/product-support-program-psp/psp-online-panel-flow-and-dialog/option-2-apply-product-changes)
General Tips and Hints:
1. Create a test complex to apply and test the maintenance before applying to production. (Reference: Creating an Alternate CA MICS Environment). Run the test complex in parallel to production. Use notes from the test complex apply process to streamline the work when installing in production.
2. Backup all files before beginning the maintenance and backup frequently during the apply process.
3. Check the CA MICS maintenance grid on support online (https://www.ca.com/us/services-support/ca-support/ca-support-online/product-content/status/detailed-service-pack-info/ca-mics-resource-management-maintenance-grid.html) for any critical PTFs that were published after the PSP was released and apply them along with the PTFs on the PSP. See Tech doc TEC496579 on CA SUPPORT ONLINE for instructions for loading and applying individual PTFs.
4. Do not hesitate to call CA MICS Support if you have questions or errors.