next up previous 211
Next: Calculating Globally Unique Error Codes
Up: Portability
Previous: Coding and porting prerequisites


Operating system specific routines

The following routines have system-specific features and may produce differing results on different platforms. System-specific code (apart from minor format differences on WRITE statements) is all in the equivalent EMS routines.
ERR_FACER
Assign a Starlink facility error message to a token.

Calls its EMS counterpart which is system-specific - for more details see SSN/4.

ERR_FIOER
Assign a Fortran I/O error message to a token.

Calls its EMS counterpart which will generally need to be rewritten for each new target platform. Current versions have the appropriate messages hardwired into the code. For more details see SSN/4.

ERR_SYSER
Assign an operating system error message to a token.

Calls its EMS counterpart which is platform specific. For more details see SSN/4.

ERR_FMTx
Assign a value to a message token (formatted).

These routines call their EMS counterpart and behave differently on different systems in the event of an error. Sometimes the errors are reported by Fortran and can be trapped but sometimes they are not. If they are reported, the token remains unset but if they are not reported, the character string generated can differ.



next up previous 211
Next: Calculating Globally Unique Error Codes
Up: Portability
Previous: Coding and porting prerequisites

MERS (MSG and ERR) Message and Error Reporting Systems
Starlink User Note 104
P C T Rees
A J Chipperfield
22 October 2001
E-mail:ussc@star.rl.ac.uk

Copyright © 2001 Council for the Central Laboratory of the Research Councils