How will we know when all userids in Dsn-System-PROFILE sysview.CNM4BPRF have been converted [upgraded]?
search cancel

How will we know when all userids in Dsn-System-PROFILE sysview.CNM4BPRF have been converted [upgraded]?

book

Article ID: 195397

calendar_today

Updated On:

Products

SYSVIEW Performance Management NXBRIDGE - SYSVIEW/ENDEVOR

Issue/Introduction

Q1) How will we know when all userids in Dsn-System-PROFILE sysview.CNM4BPRF have been converted [upgraded]?

Q2) When can Dsn-System-PROFILE sysview.CNM4BPRF be removed from  System Configuration Options member GSVXGSVX ?

Q3) Do we retain dataset Dsn-System-PROFILE sysview.CNM4BPRF indefinitely? 

Environment

Release : 16.0

Component : SYSVIEW

Resolution

A1)  

  1. user profiles that have been upgraded from Dsn-System-PROFILE to Dsn-System-PROFLIB - upgraded
    Cmd      Member   Source   ....
    ________ userid1  PROFILE  
    ________ .        PROFLIB
  2. user profiles that never had an entry in the old profile library Dsn-System-PROFILE - no upgrade needed
    Cmd      Member   Source   
    ________ userid2  PROFLIB

  3. user profiles that never been upgraded to the new profile data library Dsn-System-PROFLIB - action may been needed
    Cmd      Member   Source  
    ________ userid3  PROFILE


    Since SYSVIEW automatically upgrades profiles when a user logs on (aka upgrade on-demand), item#3 indicates that the user has not logged on in a long time for whatever reason (no longer with the company, moved to a different division, or etc) and this is a good time to clean up such profiles.  

    You can 
    1. Upgrade such profiles by asking the user to log on or manually upgrade them or
    2. Ignore those profiles 

 A2) Whenever you no longer wish for SYSVIEW to upgrade user profiles, update your System Configuration Options member to 

Dsn-System-PROFILE               NONE  

 A3) This is completely up to you. Once you make the configuration update mentioned in the bullet above, SYSVIEW is no longer aware of the data set.