[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:	DECmcc user notes file. Does not replace IPMT.
Notice:	Use IPMT for problems. Newsletter location in note 6187
Moderator:	TAEC::BEROUD

Created:	Mon Aug 21 1989
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6497
Total number of notes:	27359

811.0. "FLOAT or DECIMAL data type ? is there ?" by HLDG00::GOES () Tue Mar 19 1991 05:12

We are trying to show the easy extendibility of DECmcc by
writing an Access Module for an airconditioning (yes indeed a
network object that can be managed over DECnet).

The design of the AM did complete with minor problems.

But one has risen now.

We defined CHARACTERISTIC attributes Temperature and Humidity (both
nonsetable) with the Latin1String type.
We chose this type because the temperatures and humidities are
measured in a decimal form and we couldn't find a *DECIMAL* (or
*FLOAT*) MCC_datatype.
The problem is that we can't easily define alarm rules because the
conditions (now) depend on string-handling rather than comparing
numbers.

Is there any way around to solve this problem ?

Is there a way to pass float numbers from AM to FM (or PM) ?
   (and what datatypes do we have to define in the MSL ?)

Or is there a way to handle strings in the alarm rules ?



Thanks in advance,             Paul & Henk

T.R	Title	User	Personal Name	Date	Lines
811.1	Datatype = REAL	CHRISB::BRIENEN	DECmcc Bridge\|Station\|SNMP Management.	`Tue Mar 19 1991 07:55`	4
	The REAL datatype is what you want to use (it's what PA uses). Page 216-219, Section 9.1.2 in the DECmcc SRM, describes this datatype in detail (which looks like G_Floating to me).
811.2	Maybe our SRM is not the latest release ?	HLDG00::GOES		`Wed Mar 20 1991 03:47`	31
	Thanks for your reply, but section 9.1.2. of the DECmcc SRM (that we own) describes the boolean datatype and no REAL or FLOAT datatype. We've searched the headerfile MCC_INTERFACE_DEF.H for MCC_K_DT_????? that could possibly describe a float datatype and we found: typedef float MCC_T_FLOATF #define MCC_K_DT_FLOATF 63 typedef unsigned int MCC_T_REAL[2] #define MCC_K_DT_REAL Is one of these datatypes the one that is described in section 9.1.2 of the SRM (as mentioned in reply 1) ? Can someone supply us with the following information (for datatypes above or the datatype mentioned in reply 1) ? - User Presentation Format - MSL Name - Typedef - Length - Data Type Code - Values - Information supplied in the chapter Summary Of Datatypes - Typedef (dt_) - Symbol (MCC_K_DT_) - VMS Datatype (DSC$K_) Thanks in advance Paul Goes and Henk van Steeg
811.3	DO NOT USE MCC_K_DT_FLOATF	TOOK::GUERTIN	I want my MCC	`Wed Mar 20 1991 08:16`	7
	MCC_K_DT_FLOATF is obsolete. Using that datatype would probably cause lots of bad things to happen to your software. MCC_K_DT_REAL is real :-) and is defined in gory detail in the V1.1 SRM. There are two and a half pages of stuff. Maybe some nice soul can mail the information to you. -Matt.
811.4	Use the latest SRM. (V1.1)	CHRISB::BRIENEN	DECmcc Bridge\|Station\|SNMP Management.	`Wed Mar 20 1991 14:43`	11
	RE: 811.2 "Title: Maybe our SRM is not the latest release ?" There is no DECmcc implementation (DECmcc V1.0 EFT1 excluded) that implemented to the DECmcc SRM V1.0. The DECmcc SRM V1.1 is the System Reference Manual for the DECmcc V1.0 and DECmcc V1.1 implementations. Things as fundamental as MCC Routine Names are different between the documents (e.g., all dollar-signs were removed from routine names for portability reasons). Please use the latest version.
811.5	Alarms does handle LATIN1STRING	TOOK::ORENSTEIN		`Fri Mar 22 1991 10:43`	9
	ALARMS can handle the Latin1String datatype. So there is no problem there. The only trick is that the string in the expression must match exactly in spacing and case. aud...
811.6	Just FYI	TOOK::KOHLS	Ruth Kohls	`Mon Mar 25 1991 12:56`	4
	The floating point type defined in the V1.1 SRM is the VAX G-Float form. Ruth
811.7	question answered, thank you all	HLDG00::GOES		`Wed Mar 27 1991 10:24`	8
	Thank you all for your effort. We have used the MCC_K_DT_REAL type and it just works fine now. MCC_K_DT_REAL is indeed G-float, so you have to compile the source code using the /G_FLOAT qualifier (hint). regards, Paul Goes and Henk van Steeg
811.8	another hint	TOOK::KOHLS	Ruth Kohls	`Wed Mar 27 1991 11:07`	8
	> MCC_K_DT_REAL is indeed G-float, so you have to compile the source code > using the /G_FLOAT qualifier (hint). For more hints, like how to compile and link C modules with different float types, see the Release Notes for VAX C v3.1. Ruth