cloverleaf 6.0 – concern about site name length limit

The reason I made this post was to hopefully get an answer to our question.

How long can a site name be in Cloverleaf 6.0 and are there conditions that could also limit the site name length?

Since the documentation contradicts itself, I’m not able to use the doucmentation to get the answer to our question.

This question is still up in the air for me and I’m unable to add any more information at this time.

We did move forward with Cloverelaaf 6.0 and have all test sites live and 70% of our prod sites live with a couple of months left to get them all live.

In my case what I really need is longer site names.

Still a clarification would be helpful to know just how short a site name needs to be confined to.

My observation and experience is that we can use longer site names to be make our work easier to develop and maintain.

I did not consider 15-19 character sitenames all that long, they seem rather restrictive to me.

I must not be the only one because I’m always having to remind other team members they exceeded my max comfort level of more than 19 characters.

We even changed hciconnstatus and hicprocstatus to display 25 characters because the team could not make due with 15 characters for thread names or process names.

In fact, it recently came to my attention while upgrading from Cloverleaf 5.6 to 6.0, that so many process names greater than 25 characters exist I can’t even take on remediating them.

All of us still have been hard pressed to stay within those 25 characters and with site names there is no difference except they are even shorter that 25 characters.

We have hundereds of sites so having enough lenght to employee human digestible site name standards is preferred over having a decoder ring for very abbreviated site names.

For our batch sites we did resort to ID #’s that require decoding like

test_batch_001

.

.

test_batch_065

You may have seen my posts about change control today, so when adding things to the site name like sitename_new or sitename_old that right there is an extra 4 characters before I even get started with a base site name.

Jim Kosloskey feel free to chime in because I recall how hard it was to fit sitenames into 19 characters for the Sorian project with all the proposed environments and various granulaity.

Having an environment as part of the site name like p_ or prod_ or t_ or test_ makes the unique part of the site name even shorter, too.

Thanks Bob for posting.

We also try to put the unique part of thread names at the front within the first 15 characters as we learned this the hard way.

Having smaller sites with fewer threads helps to keep us out of trouble with the first 15 characters of 2 threads in a site matching.

It is a bit of a concern to hear about a 48 total character restriction, because our process name + thread name consumes those 48 characters in a great majority of cases before adding the site name length.

We have been tyring to work with (19 for site name) + (25 for process name) + (25 for thread name) which exceeds 48 characters.

We have a good many cases that go some beyond these bariers but we aren’t aware of issues.

Perhaps our smaller sites are helping with problems we might see if we had fewer larger sites.

I still prefer to know just what it takes to stay out of trouble, thanks again for you post.