Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!stcns3.stc.oz.AU!uucp
From: uucp@stcns3.stc.oz.AU (UUCP Administration)
Newsgroups: comp.protocols.iso.dev-environ
Subject: (none)
Message-ID: <8907070911.22064@munnari.oz.au>
Date: 7 Jul 89 21:50:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 63

From nick Fri Jul  7 16:20 EST 1989 remote from stca77
To: stcns3!isode%sri-nic.arpa@munnari.oz
Subject: importing/exporting OPERATIONS with rosy (ISODE)
Cc: nick


Just wondering if anyone knows anything about importing/exporting OPERATIONS
and ERRORS between ASN.1 modules using ISODE 5.0.
---
Section 9.6 of X.219 says that: " If operations and errors are specified
in several ASN.1 modules and are imported to a module specifying a
specific named abstract syntax, one of the following rules apply:

1) if local values are used and exported, it is in the responsibility
of the designer importing the modules to ensure uniqueness.
2) a module may specify and export operation types and error types. The
operation values and error values are assigned in the module importing
the types. A single value shall be assigned for each operation type or
error type.
3) if global values are assigned and exported, uniqueness is ensured."

I've tried to use the methodology mentioned in the example illustrated
in ANNEX B.3 of X.219 which is (in Reader's Digest form..):

---
ExportingModule { ... } DEFINITIONS ::=
BEGIN
EXPORTS operation10, OperationTypeA;
IMPORTS OPERATION, ERROR, BIND, UNBIND
	FROM Remote-Operation-Notation { ... };

operation10 OPERATION
	ARGUMENT op10Arg INTEGER
	::= 10

OperationTypeA ::= OPERATION
	ARGUMENT opAArg INTEGER
END

ImportingModule { ... } DEFINITIONS ::=
BEGIN
IMPORTS operation10, OperationTypeA
	FROM ExportingModule { ... };

operation13 OperationTypeA ::= 13
END
---
but..., since ISODE doesn't implement the macro notation, it can't IMPORT
OPERATION from Remote-Operatin-Notation.
I have tried just importing as illustrated in the way that the
ImportingModule imports operation10 from the ExportingModule, but when
table_ImportingModule_Operations table is generated by rosy for the
ImportingModule, operation10 does not feature as an element.
Could someone in the know explain what is happening here/give me a boot
in the right direction with importing/exporting modules and their effect
in the ISODE implementation ?

many, many thanks in advance,  Nick.
---
Nick Lochrin                 nick@stca77.stc.oz
Alcatel STC Australia        ...!uunet!stca77.stc.oz!nick
41 Mandible St               nick%stca77.stc.oz@uunet.UU.NET
ALEXANDRIA  NSW  2015        "Are you the police ?.. No ma'am, we're musicians."