CA SYSVIEW Performance Management

Expand all | Collapse all

Why did the hold-data for R15.0 Feature 5 flip the sequence of  INST0050 (Security) and INST0051 (profiles)

Jump to Best Answer
  • 1.  Why did the hold-data for R15.0 Feature 5 flip the sequence of  INST0050 (Security) and INST0051 (profiles)

    Posted 01-31-2018 11:11 AM

    We noticed in the Hold data for R15.0, Feature 5, that the sequence was flipped, this running 51 BEFORE 50.

     

    The base install of R15.0 had it INST0050, then INST0051.  Is there a new dependency we need to be aware of?

     

    We also noticed this for a converted system, already on Feature 3 or 4, where to go to 5, you execute the profile convert, then the security job:

     

    4. Stop the SYSVIEW STC's, GSSA, and any user sessions.             
    5. Run Profile Conversion JCL contained in CNM4BSAM member GSVUCPRF.
    6. Run Security Conversion JCL contained in CNM4BSAM member GSVUCSEC.

    This was easy to miss after many installs, so we're trying to understand what changed.



  • 2.  Re: Why did the hold-data for R15.0 Feature 5 flip the sequence of  INST0050 (Security) and INST0051 (profiles)
    Best Answer

    Posted 02-01-2018 05:54 PM

    Hi Pete,

    It was caused by the number and the content of the list of modules that were being updated which necessitated that the order be switched for this implementation of the feature 5 PTF.