|
|
|
This section provides several examples of the utility SASLIST report output. The report is divided into two sections. o The first report section shows product change updates and user modifications in detail. It is followed by a summary of the various types of modifications and product change updates encountered. This first section is repeated for each cccGENIN updated by the product. Most product changes update a single cccGENIN, but a product change for the CA MICS Tape Analyzer Option, for example, is likely to update both TLMGENIN and VTSGENIN. o The second report section provides recommendations for how to proceed based on the utility analysis.
EXAMPLE 1: Product Change Where cccGENIN has no User Modifications ------------------------------------------------------------------ o First Report Section
CA MICS PWR7777 GENLIB Analysis Report 18:50 Wednesday, June 23, yyyy 1 MEMBER=PWRGENIN */* (C) 1994,1999 COMPUTER ASSOCIATES INTERNATIONAL, INC. */ 00002000 AS DISTRIBUTED */* Copyright (C) 2010 CA. All rights reserved. */ 00002000 PWR7777 UPDATE */* PWR7777| |mmyy|Simple Product Change */ 00002477 PWR7777 ADDITION FILE PJB 00 1 Y N N Y Y Y N Y VSE/POWER Job Activity File 00025000 AS DISTRIBUTED FILE PJB 00 1 Y N N Y Y Y Y Y VSE/POWER Job Activity File 00025000 PWR7777 UPDATE NAME PJBNEWWW 00 0 N N N N New Element 00062900 PWR7777 ADDITION CA MICS PWR7777 GENLIB Analysis Report 18:50 Wednesday, June 23, yyyy 2 +-------------------------------------------------------------------------------------------------+ | PWRGENIN User Modification Analysis Summary | | -------------------------------------------- | | No USER modifications found | | | | | | Product Change PWR7777 - Update Analysis Summary for PWRGENIN | | -------------------------------------------------------------- | | Additions 2 | | Updates 2 | | User Modification Replications 0 | | User Modification CONFLICTS 0 | | | +-------------------------------------------------------------------------------------------------+
This example shows a very simple product change that updates two existing lines and adds two lines to PWRGENIN. Note that where an existing line is updated, the report shows how the line looked prior to the product change update. It is a best practice to closely examine each product change addition and update. You may decide to make some modifications if you do not want to accept how the product change is updating existing lines. In the example above, you may decide that you want the new data element on in all timespans, instead of just in DETAIL as PWR7777 is delivering it. If so, you could change the '0 N N N N' to '0 0 0 0 0' after the product change apply, and before executing sharedprefix.MICS.CNTL(PWRCGEN).
EXAMPLE 1: Product Change Where cccGENIN has no User Modifications (Continued) ------------------------------------------------------------------------------ o Second Report Section
+-------------------------------------------------------------------------------------------------+ |----------------- UTILITY ANALYSIS RECOMMENDATIONS FOR PRODUCT CHANGE PWR7777 -----------------| +-------------------------------------------------------------------------------------------------+ | | | o - No problems detected | | o - Examine the report output to review product change updates | | | | o - No user modifications--empty member will be created in sharedprefix.MICS.GENLIB(UPWR7777) | | Check MICSLOG for member creation confirmation. | | | | Reference: CA MICS How to Use the PSP guide, Section 4.2 | | | +-------------------------------------------------------------------------------------------------+
The second, final section of the report provides recommendations based on the analysis of the product change and any user modifications. This example shows the simplest possible result. There were no user modifications and the only task required is to take a look at how the product change has updated cccGENIN. If you decide that you do not want any of the additions, or updates, as delivered, you can update sharedprefix.MICS.GENLIB(cccGENIN) after the product change apply step, and before you execute sharedprefix.MICS.CNTL(cccCGEN). The note regarding the utility created member, shareprefix.MICS.GENLIB(UPWR7777) tells you that the member will be empty because GENLIB(PWRGENIN) had no user modifications.
EXAMPLE 2: Product Change Where cccGENIN has User Modifications --------------------------------------------------------------- o First Report Section
CA MICS PWR7777 GENLIB Analysis Report 18:50 Wednesday, June 23, yyyy 1 MEMBER=PWRGENIN */* (C) 1994,1999 COMPUTER ASSOCIATES INTERNATIONAL, INC. */ 00002000 AS DISTRIBUTED */* Copyright (C) 2010 CA. All rights reserved. */ 00002000 PWR7777 UPDATE */* PWR7777| |mmyy|Simple Product Change */ 00002477 PWR7777 ADDITION FILE PJB 00 1 Y N N Y Y Y N Y VSE/POWER Job Activity File 00025000 AS DISTRIBUTED FILE PJB 00 1 Y N N Y Y Y Y Y VSE/POWER Job Activity File 00025000 PWR7777 UPDATE NAME PJBGRPRC 00 0 N N N N Job Group Received 00061000 AS DISTRIBUTED >>---> NAME PJBGRPRC 00 0 n n N N Job Group Received 00061000 USER MODIFICATION: Insignificant <---<< NAME PJBNEWWW 00 0 N N N N New Element 00062900 PWR7777 ADDITION NAME PJBMASK 00 0 N N N N Record Construction Audit Mask 00065000 AS DISTRIBUTED >>---> NAME PJBMASK 00 0 N N N N Record Construction Audit Mask 00065000 USER MODIFICATION: Insignificant <---<< NAMX PJBORGJN 00 0 N N N N Origin Job Number 00070000 AS DISTRIBUTED >>---> NAMX PJBORGJN 00 0 N N N N Origin JOB NUMBER 00070000 USER MODIFICATION <---<< NAMX PJBORGNN 00 0 N N N N Origin Node Name 00087000 AS DISTRIBUTED >>---> NAMX PJBORGNN 00 0 0 0 0 0 Origin Node Name 00087000 USER MODIFICATION <---<< NAME PRAERROR 00 0 0 0 0 0 Errors Count 00678000 AS DISTRIBUTED >>---> USER DELETION: Should FIX this!!! <---<< CA MICS PWR7777 GENLIB Analysis Report 18:50 Wednesday, June 23, yyyy 1 +-------------------------------------------------------------------------------------------------+ | PWRGENIN User Modification Analysis Summary | | -------------------------------------------- | | Modifications 2 | | Modifications-Insignificant 2 <-- FIX AND RE-RUN UTILITY | | Additions 0 | | Deletions 1 <-- FIX AND RE-RUN UTILITY | | | | | | Product Change PWR7777 - Update Analysis Summary for PWRGENIN | | -------------------------------------------------------------- | | Additions 2 | | Updates 2 | | User Modification Replications 0 | | User Modification CONFLICTS 0 | | | +-------------------------------------------------------------------------------------------------+
This second example shows the same product change, but there are a number of user modifications to PWRGENIN. Notice that user modifications are bracketed with arrows (>>---> and <---<<). Legitimate modifications are simply labeled USER MODIFICATION. If a user modification is labeled as USER MODIFICATION: Insignificant, or USER DELETION, you should take the time to correct them.
USER MODIFICATION: Insignificant are a nuisance--they are operationally equivalent to the corresponding line in sharedprefix.MICS.HOLD.PARMS(cccGENIN), but show up as different in comparisons between HOLD.PARMS and GENLIB. To fix insignificant modifications, replace the line in GENLIB(cccGENIN) with the corresponding line (same sequence number) from HOLD.PARMS. When you re-run the PSP GENLIB Compare Utility program they will no longer show up as user modifications.
USER DELETIONS are bad. Lines should never be deleted from sharedprefix.MICS.GENLIB(cccGENIN). If you have any user deleted lines, copy the corresponding line from HOLD.PARMS(cccGENIN) and use statement parameters to inactivate the statement. Notice that the analysis summary quantifies the types of user modifications encountered, and encourages you to fix any insignificant modifications or deletions, and then re-run the utility.
EXAMPLE 2: Product Change Where cccGENIN has User Modifications (Continued) --------------------------------------------------------------------------- o Second Report Section
+-------------------------------------------------------------------------------------------------+ |----------------- UTILITY ANALYSIS RECOMMENDATIONS FOR PRODUCT CHANGE PWR7777 -----------------| +-------------------------------------------------------------------------------------------------+ | | | o - No problems detected | | o - Product change does not appear to conflict with user modifications | | o - Examine the report output to review product change updates | | | | o - BEST PRACTICE: Resolve the 2 insignificant user mods then re-execute utility | | o - BEST PRACTICE: Resolve the 1 user deletions then re-execute utility | | | | o - User modifications will be saved in sharedprefix.MICS.GENLIB(UPWR7777) | | Check MICSLOG for member creation confirmation. | | | | Reference: CA MICS How to Use the PSP guide, Section 4.2 | | | +-------------------------------------------------------------------------------------------------+
The second, final section of the report is different when user modifications are found. The recommendations acknowledge that user modifications were found, and that it appears as though the product change updates do not interfere with the user mods. You are still encouraged to examine the report to see how the product change has updated cccGENIN. If you decide that you do not want any of the additions, or updates, as delivered, you can update sharedprefix.MICS.GENLIB(cccGENIN) after the product change apply step and before you execute sharedprefix.MICS.CNTL(cccCGEN).
You are also encouraged to take care of any insignificant user modifications or user deletions. Notice that the note regarding the utility created member, shareprefix.MICS.GENLIB(UPWR7777), is different because GENLIB(PWRGENIN) did have user modifications. This report is generated just before the creation of the Ucccnnnn member--so to confirm that it was indeed created, you can check MICSLOG.
EXAMPLE 3: Product Change with CONFLICTS and Replications --------------------------------------------------------- o First Report Section
CA MICS PWR7777 GENLIB Analysis Report 18:50 Wednesday, June 23, yyyy 1 MEMBER=PWRGENIN */* Copyright (C) 2010 CA. All rights reserved. */ 00002000 PWR7777 UPDATE */* PWR7777| |mmyy|Simple Product Change */ 00002477 PWR7777 ADDITION FILE PJB 00 1 Y N N Y Y Y N Y VSE/POWER Job Activity File 00025000 AS DISTRIBUTED >>---> FILE PJB 00 1 Y N N Y Y Y Y Y VSE/POWER Job Activity File 00025000 USER MODIFICATION: Replicated <---<< FILE PJB 00 1 Y N N Y Y Y Y Y VSE/POWER Job Activity File 00025000 PWR7777 UPDATE NAME PJBNEWWW 00 0 N N N N New Element 00062900 PWR7777 ADDITION NAMX PJBORGJN 00 0 N N N N Origin Job Number 00070000 AS DISTRIBUTED >>---> NAMX PJBORGJN 00 0 N N N N Origin JOB NUMBER 00070000 USER MODIFICATION <---<< NAMX PJBORGJN 00 0 0 0 0 0 Origin Job Number 00070000 PWR7777 UPDATE: CONFLICT <---<< NAMX PJBORGNN 00 0 N N N N Origin Node Name 00087000 AS DISTRIBUTED >>---> NAMX PJBORGNN 00 0 0 0 0 0 Origin Node Name 00087000 USER MODIFICATION <---<< CA MICS PWR7777 GENLIB Analysis Report 16:15 Thursday, June 24, 2010 2 +-------------------------------------------------------------------------------------------------+ | PWRGENIN User Modification Analysis Summary | | -------------------------------------------- | | Modifications 2 | | Modifications-Insignificant 0 | | Additions 0 | | Deletions 0 | | | | | | Product Change PWR7777 - Update Analysis Summary for PWRGENIN | | -------------------------------------------------------------- | | Additions 2 | | Updates 2 | | User Modification Replications 1 | | User Modification CONFLICTS 1 <-- WARNING--ANALYZE AND REACT | | | +-------------------------------------------------------------------------------------------------+
This final example shows a similar product change where there is a conflict with a user modification as well as a replication of a user modification. USER MODIFICATION: Replicated - This means that the user had modified a line in GENLIB(cccGENIN) and the product change is delivering the line exactly as the user had modified it. Notice that the count of user modifications is 2, even though three are noted in the report. The replicated line is no longer a user modification. It will no longer appear in the GENLIB(Ucccnnnn) member that contains user modified lines.
PWR7777 UPDATE: CONFLICT - This requires your careful examination. Whenever a CONFLICT is noted, it means that a modification you have made is being overlayed by the product change. In the example above, the user has modified the data element label from "Origin Job Number" to "Origin JOB NUMBER." The product change is updating the timespan activation switches for the element. If you do nothing, the data element will now be on in all timespans, and the label will revert to the original value. You may decide that you want to go ahead and accept the timespan activation changes, but you also want to preserve your data element label modification.
To accomplish this, you would need to apply the product change. After the apply step, you must update sharedprefix.MICS.GENLIB(PWRGENIN) to update the data element label before you execute sharedprefix.MICS.CNTL(PWRCGEN). It is very important to review the PSP GENLIB Compare Utility SASLIST output to see if any conflicts occur. If the lines impacted are OPTION or FILE statements, you can seriously impact operational behavior and database content if you neglect to examine cases where your database modifications are overlayed by product change updates.
EXAMPLE 3: Product Change with CONFLICTS and Replications (Continued) ---------------------------------------------------------------------
+-------------------------------------------------------------------------------------------------+ |----------------- UTILITY ANALYSIS RECOMMENDATIONS FOR PRODUCT CHANGE PWR7777 -----------------| +-------------------------------------------------------------------------------------------------+ | | | o - WARNING: CONFLICTS FOUND!!! | | Review the 1 product change update(s) that conflict with user modifications | | If you want to preserve your modifications, update the CONFLICT lines | | AFTER executing the PSP apply job and BEFORE executing the cccCGEN job. | | | | | | o - User modifications will be saved in sharedprefix.MICS.GENLIB(UPWR7777) | | Check MICSLOG for member creation confirmation. | | | | Reference: CA MICS How to Use the PSP guide, Section 4.2 | | | +-------------------------------------------------------------------------------------------------+
When conflicts are found, the final section of the report provides a WARNING, encourages you to review the user modifications impacted, and explains the actions necessary to preserve your user modifications.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |