Conference azur::mcc

2172.0. "Exception definition in MSL" by BALZAC::COULON (Even if it works, ask why) Thu Jan 23 1992 04:40

 My OST global entity has 2 levels of child entity, FEP and LINE. Thus my MSL
is structured as:

	GLOBAL ENTITY OST
		CHILD ENTITY FEP
			CHILD ENTITY LINE

 All the levels support the SHOW IDENTIFIER directive with different exceptions
but for FEP and LINE levels, the dispatch table specifies only one entry point:

	mcc_dispatch_entry -
                SHOW,-
		<mcc_entity <OST,*> <OST_FEP,*> <...>>,-
                IDENTIFIER, OST_SHOW_IDENTIFIERS

 The question is : How do we specify the exceptions in the MSL? It seems that
we have to DUPLICATE all the FEP exceptions at the LINE level because if the AM
returns a FEP exception for a command like:

	SHOW OST <instance> FEP <instance> LINE <instance>

 this exception will not be displayed by the FCL, because it is unknown at the
LINE level... 

 Do we really have to re-declare all the exceptions like below or is there a
way to declare "global" exceptions?

	GLOBAL ENTITY level_0
	 DIRECTIVE SHOW
         EXCEPTION level_0_exceptions
		CHILD ENTITY level_1
		 DIRECTIVE SHOW
		 EXCEPTION level_0_exceptions
		 EXCEPTION level_1_exceptions
			CHILD ENTITY level_2
		 	 DIRECTIVE SHOW
		 	 EXCEPTION level_0_exceptions
			 EXCEPTION level_1_exceptions
			 EXCEPTION level_2_exceptions

 Regards,

 Serge

For now, the only thing you can use (to reduce the MS file size) is to
use an INCLUDE statement to read in a new file of some segment of code
like an exception

The syntax is:

	INCLUDE file-name.ms;

The functionality is the same as the C #include statement which inlines
the contents from the specified file.

I am   sure   EMA  doesn't  allow  entity-specific  exceptions  on  database
directives  (like  Show).   Has  this changed? In fact, I can't think of any
sort of error you might want to return on a Show which isn't already covered
in the common exceptions anyway.

Graham