Universe 14.1 and SB+5

Hey Barry,

The setting in UV 14.1 is USE_LEGACY_OPENSSL_ALGORITHM.  This needs to be set to 1 in order for the older encryption algorithms in SB version 5 to work. 

It is also important to note that if you are coming from a version of UniVerse prior to 11.3 we made changes User number assignments.  Your applications could be impacted if you capture the user number. 

See the following notice on UniVerse 11.3.1:

https://rbc.rocketsoftware.com/notice.asp?passedSolutionId=000019466

Also see the release notes for that version, specifically UNV-17658:

https://rbc.rocketsoftware.com/downloads/readme/UV-11.3.1.pdf?11:22

Other than the above we expect the same functionality in SB 5 on UniVerse 14 as we do on any other version of UniVerse.

-Andrew Clay

Thanks for the clarification Andrew.

We have many user on 11.2.5 but we have been working in 11.3.5 for the current release of our software, so I am aware of the port assignment change and we have handled that where we need to.

To your knowledge (or if anyone else reading this knows) how many companies are running SB+5 on UV14.1 in production?

I do not doubt what you are saying is true, but it always helps to back it up with a number of successful implementations.

Kind Regards

Barry

Hi running sb on 400+sites, we start to deploy with Uv14 (we skip the r12). 

If you set like Andrew Clay explain, sb run without problems.

Nevertheless, I suggest you check carefully the flollowing uvconfig param 

MFILES, T30FILE, NUSERS, USE_LEGACY_OPENSSL_ALGORITHM 

activeFileTable

SESSION_NFILES, SESSION_AFT_BUCKET

info : slot/buket

N_AFT, N_AFT_SECTION, N_AFT_SECTION_BUCKET

info : slot/section

info : slot/bucket

locks management

GLM_MEM_SEGSZ

N_GLM_GLOBAL_BUCKET

info : nb lock slots

info : nb lock slots /bucket : GLM_MEM_ALLOCN, GLM_SELF_BUCKET

standard

ALLOWNFSU, VTEMPS, ELBUFC, ENTURYPIVOT, MAXERRLOGENT, EXACTNUMERIC, OPTMEM 

Regarding sb filevar cache (FILEVARS(30) + SBFILE( 750), you have 780 + uv sys + open by basic filevar in memory times indexes, data level, datapart, data/ovf... It manage a lot of files handle.

I'm used to set MFILES to 3000.

And now, it impact system wide  N_AFT... Etc. 

If you try to open one more file than N_AFT, you go to ELSE clause not ON ERROR then sb report 'file not open'.

I can share a Excel sheet used to define all uvconfig regarding (license +phantom+uvnet)->NUSERS, size of account, number of users per account,...

Hi Manu,

Thanks for your reply, very informative.

Can I just confirm that some of the SB sites you have are SB+5.x.

If you could share your spreadsheet, that would be very helpful and greatly appreciated.

Kind Regards

Barry

Hi Barry, Yes, most of our sites runs Sb r5.x (cui/gui), we also run sbr6 (cui/gui) and sbr6 (cui/gui/xui), the upgrade to r6 is engage but it takes time to complete 400 sites. 

Manu

Thanks again Manu.

That is very helpful and good to know.

We are faced with a similar challenge but not on that scale.

Kind Regards

Barry

Barry,

Another thing I forgot to mention in my last comment.  There is a setting introduced in UniVerse 12 and later that can be set to use the older style user number assignment. 

We have a tech article on the setting:

https://my.rocketsoftware.com/RocketCommunity/s/article/Support-for-SB-5-x-x-releases-on-UniVerse-12-1-and-later

It involves adding a uvconfig parameter 'USERNO_COMPATIBLE_STYLE' which reverts the changes made in UV 11.3.

I need to check if this setting is still applicable in UV 14 however.

-Andrew