Hi,
It seems to me that it would be better to change/patch 9.1 if the problems
started there. There is a lot of legacy from all previous versions that it
might be harder to fix than just having BMC change their most recent code.
Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.
> Well folks,
>
>
>
> I'm afraid it just got a lot worse!!!
>
>
>
> 9.1.0 identifies itself as 9.0.0 but has a different set of AR_SERVER_INFO
> values:
>
>
>
>>From 9.0.0
>
> #define AR_CURRENT_API_VERSION 21 /* current api version */
>
> #define AR_MAX_SERVER_INFO_USED 426 /* set "highest" server info */
>
>
>
>>From 9.1.0
>
> #define AR_CURRENT_API_VERSION 21 /* current api version */
>
> #define AR_MAX_SERVER_INFO_USED 443 /* set "highest" server info */
>
>
>
> I suppose it is too late for BMC to fix this absolute mess. How is one's
> source code to differentiate between 9.0.0 and 9.1.0 - given that they both
> identify themselves as the same release and given that they have different
> symbols defined? I suppose it means that AR_CURRENT_API_VERSION is NOT to
> be used to identify the API release but rather AR_MAX_SERVER_INFO_USED (as
> long as you don't go back far enough that that symbol is not defined) or
> possibly a combination of the two symbols.
>
>
>
> I have yet to look at the actual INFO values themselves and shudder to think
> what I may find.
>
>
>
> Cheers
>
> Ben
>
>
>
> From: Ben Chernys [mailto:ben.cher...@softwaretoolhouse.com]
> Sent: March-01-16 10:24
> To: 'arslist@ARSLIST.ORG'
> Subject: Confusion over AR_SERVER_INFO values as changed in the Rel 9 API
>
>
>
> Hi Folks,
>
>
>
> I am just trying to get my head around the AR_SERVER_INFO changes introduced
> in release 9.
>
>
>
> ARS 9 does something not done previously with these values:
>
> It changes the integer in some Info values and deletes some Info values
>
>
>
> Image this scenario: You have a release 9 API accessing a Release 8 server.
>
> Which symbol do you use for a release 8 value? There are no symbols for
> deleted values which are still legitimate on the 8 server. The symbol
> defined in the 9 API will request the wrong value on an 8 server.
>
>
>
> Similarly, you have a release 8 API accessing a release 9 server: When you
> ask for an Info that has had a number change, what do you get?
>
>
>
> For now, I will have to get around the problem by not asking for contentious
> info values. Heaven forbid that someone wants these values J
>
>
>
> I question how something this basic and simple could have been turned into
> something this obtuse and convoluted. I also question what the API itself
> does when "maintaining compatibility" across server releases.
>
>
>
> Kudos to BMC, they have maintained excellent compatibility across server
> releases when it comes to the data portion of the API.
>
> This is the first release which does not. Any comments from BMC would be
> welcome.
>
>
>
> Details:
>
>
>
> Release 8.1 API
>
> - These are all dropped in 9:
>
> #define AR_SERVER_INFO_MESSAGE_BROKER_URL 374 /* char - Message
> Broker URL */
>
> #define AR_SERVER_INFO_NUMBER_OF_SELECTOR_THREADS 375 /* int - Number of
> selector threads. */
>
> #define AR_SERVER_INFO_MESSAGE_BROKER_PORT 376 /* int -
> Messsaging(JMS) broker port. */
>
> #define AR_SERVER_INFO_JMX_PORT 377 /* int - JMX Port */
>
> #define AR_SERVER_INFO_PEER_LISTENER_PORT 378 /* int - (Cache)
> Peer-listener-port */
>
> - These are renumbered in 9:
>
> #define AR_SERVER_INFO_API_MONITORING_UPDATE_INTERVAL 379 /* int - Update
> Interval for API Monitoring */
>
> #define AR_SERVER_INFO_API_RECORDING_CLIENT_TYPE 380 /* char - API
> Recording on for specific Client Type */
>
> #define AR_SERVER_INFO_API_RECORDING_ENABLE 381 /* int - Enable Flag
> would be set to T or F */
>
> #define AR_SERVER_INFO_API_RECORDING_CLIENT_TYPE 380 /* char - API
> Recording on for specific Client Type */
>
> #define AR_SERVER_INFO_API_RECORDING_ENABLE 381 /* int - Enable Flag
> would be set to T or F */
>
> #define AR_SERVER_INFO_OBJ_RESERVATION_REPOSITORY_TYPE 382 /* int - Object
> reservation repository type - 0 ARS; 10 External */
>
> - This value has a different meaning in 9:
>
> #define AR_SERVER_INFO_SERVICE_RECORDING_ENABLE 383 /* int - flag to
> enable the Service Monitoring */
>
> - Now they align with 9
>
> #define AR_SERVER_INFO_STATS_APISQL_CONTROL 384 /* Bitmask for controlling
> API/SQL display to console, exception logging option, etc. */
>
>
>
> Release 9 API Release 9 has no 379 J
>
> #define AR_SERVER_INFO_API_MONITORING_UPDATE_INTERVAL 380 /* int -
> Update Interval for API Monitoring */
>
> #define AR_SERVER_INFO_API_RECORDING_CLIENT_TYPE 381 /* String
> - API Recording on for specific Client Type */
>
> #define AR_SERVER_INFO_API_RECORDING_ENABLE 382 /* int -
> Enable Flag would be set to T or F */
>
> #define AR_SERVER_INFO_OBJ_RESERVATION_REPOSITORY_TYPE 383 /* int Object
> reservation repository type - 0 ARS */
>
> /*
> - 10 External */
>
> #define AR_SERVER_INFO_STATS_APISQL_CONTROL 384 /* bitmask Controls
> API and SQL recording */
>
>
>
>
>
>
> Cheers,
>
> Ben Chernys
> Senior Software Architect
> logoSthInc-sm
>
> Canada / Deutschland
> Mobile: +49 171 380 2329 GMT + 7 + [ DST ]
>
> Land: +1 403 240 4377
> Email: <mailto:ben.cher...@softwaretoolhouse.com>
> ben.cher...@softwaretoolhouse.com
> Web: <http://www.softwaretoolhouse.com/> www.softwaretoolhouse.com
>
> We are a BMC Technology Alliance Partner
>
>
>
>
>
> Check out Software Tool House's free Diary Editor and our Freebies Section
> for ITSM Forms and Fields spreadsheet.
>
> Meta-Update, our premium ARS Data tool, lets you automate your data changes,
> imports, migrations, in no time at all, without programming, without staging
> forms, without merge workflow.
>
>
>
> Meta-Archive does ITSM Archiving your way: with your forms and your
> multi-tenant rules, treating each root request as the tree of data and forms
> that it is it is. Output to Archive forms, an archive server, CSV and HTML
> with all attachments extracted and linked.
>
>
>
> Pre ITSM 7.6.04? Clarify? Roll your own? No problem!
>
> You can keep your valuable data!
>
>
> <http://www.softwaretoolhouse.com/> http://www.softwaretoolhouse.com/
>
>
>
>
>
>
>
>
>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
