KudoZ home » English to Dutch » IT (Information Technology)

serverity

Dutch translation: statuswaarde (van de boodschap/melding/bericht)

Advertisement

Login or register (free and only takes a few minutes) to participate in this question.

You will also have access to many other tools and opportunities designed for those who have language-related jobs
(or are passionate about them). Participation is free and the site has a strict confidentiality policy.
GLOSSARY ENTRY (DERIVED FROM QUESTION BELOW)
English term or phrase:serverity
Dutch translation:statuswaarde (van de boodschap/melding/bericht)
Entered by: Evert DELOOF-SYS
Options:
- Contribute to this entry
- Include in personal glossary

00:17 Aug 23, 2001
English to Dutch translations [PRO]
Tech/Engineering - IT (Information Technology)
English term or phrase: serverity
Log On Serverity

geen context
Linda
statuswaarde (van de boodschap/melding/bericht)
Explanation:
Bij het doorsturen van een bericht kun je via serverity aangeven wat je bepaalde status is t.o.v. het gecontacteerde bedrijf: bv. individuele gebruiker, departement, enz.

Vandaar, Inloggen op (or 'via') statuswaarde [serverity]

Dit is wat ik o.m. vond via www.google.com

FeiMsg is used by FEI API classes to report messages. You can also use it from within an application. The command line utility fei uses it for example.

You don't create an FeiMsg object in your program. Just one such object exists in program space and its created automatically for you. Instead use the global friend function to feiMsg to reference FeiMsg member functions. The general syntax is:

feiMsg().< member function >

For example:


feiMsg().record ("Hello, world!", FEI_OK);

uses the record member function to record the message Hello, world!. (The second argument is the status, or serverity, value associated with the message.)

There is a good reason for using a single object for message reporting and that's because Fei is multi-threaded. With different threads - an your application portion of a program is one thread - it's likely that more than one of them will be writting a message at the same time. The FeiMsg class controlls the activity by only allowing the existance of a single object and by serializing message reporting within that object.

By default FeiMsg writes to stderr. It can also be configured to write a log file or to send email. You open and close a log file with the member functions openLog and closeLog. To have messages mailed, setMaiTo is used. Once configured with any or all of these options, there reporting state can be turned on or off with the member functions: setPrintMessage (stderr), setLogMessge (log file) and setMailMessage (email). These functions take a boolean argument {true, false} that sets the state.

The member function record is used to report a message. The message is sent each of the report facilities (stderr, log file, email) that's configured and has a state value of true.

record takes two arguments: a formatted message and an FEI status value. FEI status values are used by all FEI classes. The values and their general meaning are:


FEI_OK: This is the value returned when things go OK.
FEI_INFO: Everything went OK. This message just reports useful information.
FEI_WARN: Something went wrong, but it was not bad enough to cause an operation to fail.
FEI_ERROR: Something went wrong causing an operation to fail.
FEI_FATAL: Something went wrong that makes it impossible to carry out further Fei operations. For example, if you can't connect to an FEI server, FEI_FATAL is returned because no transactions can be processed.

The status values are positive integers with FEI_OK having a value of 0. The precedence order is FEI_OK < FEI_INFO < FEI_WARN < FEI_ERROR < FEI_FATAL. Note: FEI_OK will always be 0 so you can check the status of an operation as shown in the following example; but don't use numeric values for the other status values; they could change in the future, although their precedence will remain the same. Here's the example:

if (status) // take action if the status is
takeAction (status); // other than FEI_OK or 0.

When reporting messages you can turn on FeiMsg's header line if you like with the member function useHeader. (By default, it's turned off.) With the header turned on, each message send starts with a line that includes string value equivalent for the status value and the current system time. Use this method if you want to time stamp you messages.

FeiMsg does not return error messages; it's simply a reporting device to be used in multi-thread environments. You can get error messages directly from Fei objects using their member functions getErrno() and getMsg(). If you want to handle reporting messages yourself, turn off all of FeiMsg's reporting states, retrieve messages when you recieve an FEI status other than FEI_OK, and report them using your own mechanism.

HTH

Selected response from:

Evert DELOOF-SYS
Belgium
Local time: 15:13
Grading comment
Super met al deze referenties! Bedankt!
4 KudoZ points were awarded for this answer

Advertisement


Summary of answers provided
na +1statuswaarde (van de boodschap/melding/bericht)
Evert DELOOF-SYS
naServerity
Sven Petersson


  

Answers


20 mins
Serverity


Explanation:
Serverity is proper name (Serverity Corp. server, Singapore).


    Reference: http://web.singnet.com.sg/~eugenteo/democode.html
Sven Petersson
Sweden
Local time: 15:13
Works in field
Native speaker of: Native in SwedishSwedish, Native in EnglishEnglish
Login to enter a peer comment (or grade)

38 mins peer agreement (net): +1
statuswaarde (van de boodschap/melding/bericht)


Explanation:
Bij het doorsturen van een bericht kun je via serverity aangeven wat je bepaalde status is t.o.v. het gecontacteerde bedrijf: bv. individuele gebruiker, departement, enz.

Vandaar, Inloggen op (or 'via') statuswaarde [serverity]

Dit is wat ik o.m. vond via www.google.com

FeiMsg is used by FEI API classes to report messages. You can also use it from within an application. The command line utility fei uses it for example.

You don't create an FeiMsg object in your program. Just one such object exists in program space and its created automatically for you. Instead use the global friend function to feiMsg to reference FeiMsg member functions. The general syntax is:

feiMsg().< member function >

For example:


feiMsg().record ("Hello, world!", FEI_OK);

uses the record member function to record the message Hello, world!. (The second argument is the status, or serverity, value associated with the message.)

There is a good reason for using a single object for message reporting and that's because Fei is multi-threaded. With different threads - an your application portion of a program is one thread - it's likely that more than one of them will be writting a message at the same time. The FeiMsg class controlls the activity by only allowing the existance of a single object and by serializing message reporting within that object.

By default FeiMsg writes to stderr. It can also be configured to write a log file or to send email. You open and close a log file with the member functions openLog and closeLog. To have messages mailed, setMaiTo is used. Once configured with any or all of these options, there reporting state can be turned on or off with the member functions: setPrintMessage (stderr), setLogMessge (log file) and setMailMessage (email). These functions take a boolean argument {true, false} that sets the state.

The member function record is used to report a message. The message is sent each of the report facilities (stderr, log file, email) that's configured and has a state value of true.

record takes two arguments: a formatted message and an FEI status value. FEI status values are used by all FEI classes. The values and their general meaning are:


FEI_OK: This is the value returned when things go OK.
FEI_INFO: Everything went OK. This message just reports useful information.
FEI_WARN: Something went wrong, but it was not bad enough to cause an operation to fail.
FEI_ERROR: Something went wrong causing an operation to fail.
FEI_FATAL: Something went wrong that makes it impossible to carry out further Fei operations. For example, if you can't connect to an FEI server, FEI_FATAL is returned because no transactions can be processed.

The status values are positive integers with FEI_OK having a value of 0. The precedence order is FEI_OK < FEI_INFO < FEI_WARN < FEI_ERROR < FEI_FATAL. Note: FEI_OK will always be 0 so you can check the status of an operation as shown in the following example; but don't use numeric values for the other status values; they could change in the future, although their precedence will remain the same. Here's the example:

if (status) // take action if the status is
takeAction (status); // other than FEI_OK or 0.

When reporting messages you can turn on FeiMsg's header line if you like with the member function useHeader. (By default, it's turned off.) With the header turned on, each message send starts with a line that includes string value equivalent for the status value and the current system time. Use this method if you want to time stamp you messages.

FeiMsg does not return error messages; it's simply a reporting device to be used in multi-thread environments. You can get error messages directly from Fei objects using their member functions getErrno() and getMsg(). If you want to handle reporting messages yourself, turn off all of FeiMsg's reporting states, retrieve messages when you recieve an FEI status other than FEI_OK, and report them using your own mechanism.

HTH



Evert DELOOF-SYS
Belgium
Local time: 15:13
Works in field
Native speaker of: Native in DutchDutch, Native in FlemishFlemish
PRO pts in category: 81
Grading comment
Super met al deze referenties! Bedankt!

Peer comments on this answer (and responses from the answerer)
agree  Boudewijn van Milligen
6 mins
Login to enter a peer comment (or grade)




Return to KudoZ list


Changes made by editors
Apr 14, 2005 - Changes made by Evert DELOOF-SYS:


KudoZ™ translation help
The KudoZ network provides a framework for translators and others to assist each other with translations or explanations of terms and short phrases.



See also:



Term search
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search