Idea Details

Enhance NetMaster to better indicate what maintenace level it is at - D-42111

Last activity 06-13-2019 09:38 AM
Bob Davidson's profile image
09-01-2015 12:06 PM

There is current no easy way to tell that all required maintenance is applied and that all necessary hold actions for MODS, PANELS and OSCNTL have been completed insync with the SMPE code changes.

 

Even when level S1507 is installed the product still show 1212 on the ST display

 

N11414 SYSTEM CONFIGURED WITH SNAAUTO (LMP=XY) - R12.1 LEVEL 1212

N11414 SYSTEM CONFIGURED WITH TCPIP (LMP=Y7) - R12.1 LEVEL 1212

 

or the /LEVELS display!


Comments

01-16-2019 12:56 PM

NMS12.2 INC02 PTFs: R092903, RO92904, and R092905. 

Added....

  • product release number to the product region Primary menu 
  • release number to the start messages for SSI and for the product region

 

Also PTF SO04199 adds PROVIDE VSAM UPDATE TRACKING 

 

Idea updated as delivered.

01-07-2016 09:45 AM

Ok, this is disappointing.

 

Shouldn't the messages N11414 and BAVL02 have been updated to reflect level S1507 some how? MODS is clearly not at level INSTALL and had been updated many times by the VIP utility as a result of fixes.

 

Also could we have a utility that scanned MODS / PANELS / OSCNTL and RAMDB and reported the highest level of fix found?

01-06-2016 10:36 AM

We have completed our research for every avenue.   The Service Update is not meant to be a ServicePack and provide a new gen level. The Service Update is meant to include base and all fixes up to a point in time to help customers who are upgrading to a new release so that they don't have to install many PTFs after the install upgrade installation.    Once you have the Service Update installed you would still need to use your release level and high apar or the recommended CA RS level to know your installation's maintenance level.  This item can't be completed and will be marked as not delivered. 

10-27-2015 03:57 PM

Hey Bob,

 

Due to the nature of the Service update, our research shows that we need to take a different approach so we are looking to enhance the $$SYSPRO routine to determine if we can specify this data.


Just wanted to give you an update and to let you know our plan of action.


Thanks,

Jennifer

09-01-2015 04:55 PM

Hi Kevin,

 

Yes, I get that also

BAVL02 System VSAM base is: MODS INSTALL PANELS 1311 OSCNTL INSTALL RAMDB MSR7.6

 

But on level S1507 I would expect MODS to show higher than INSTALL for example.

09-01-2015 01:08 PM

Our internal database record -D-42111

09-01-2015 12:59 PM

Ok .. we got a defect, Bob!   The levels will need to be corrected.  Marking this as Currently Planned and will deliver via PTF.  You're the customer listed.

 

In regards to the VSAM files, we are looking at them overall for the future and this includes better VSAM maintenance information. 

09-01-2015 12:37 PM

Bob,

In the $$SYSPRO there is a line output for the VSAM levels.

 

The line is

BAVL02 System VSAM base is: MODS INSTALL  PANELS 1311  OSCNTL INSTALL  RAMDB MSR7.6

 

Kevin

 

 

from the help -

Message ID ...+ BAVL02                                                   

Message Text                                                            

      System VSAM base is: MODS ~P1  PANELS ~P2  OSCNTL ~P3 ~P4 ~P5      

                                                                         

Message Explanation                                                     

      The system maintenance level for distributed VSAM data is shown as 

      follows:                                                           

                                                                         

       P1 is the MODS level - menus, messages, web records, and so on.   

       P2 is the panels level.                                           

       P3 is the OSCNTL level - ASN1 maps.                               

       P4 is RAMDB if Automation Services is licensed.                   

       P5 is the RAMDB level.                                            

                                                                         

      Maintenance levels are in yymm , the year and month of service pack

      creation.                                                          

09-01-2015 12:15 PM

Hmm ... To me this sounds like a bug.... let me get Steve to look at it.