z/OS Communications Server: CMIP Services and Topology Agent Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


ASN.1 value format

z/OS Communications Server: CMIP Services and Topology Agent Guide
SC27-3646-00

The value format is based on an ASN.1 module, as shown in the following example.
    A ::= INTEGER
 
    a INTEGER ::= 1
    b INTEGER ::= 2
    c INTEGER ::= 3
    d A       ::= 4
 
    B ::= SET {
       f   [1] INTEGER,
       g   [2] INTEGER,
       h   [3] INTEGER
       }
    C ::= SEQUENCE {
       f   [1] INTEGER,
       g   [2] INTEGER,
       h   [3] INTEGER
       }
 
Values for A may be specified as:
        a
        b
        d
        12
Values for B may be specified as:
        (f a, h d, g 34)
        (h 138, f d, g 34)
Values for C may be specified as:
        (c, 12, 19)
        (f c, 12, h 19)
        (f c, g 12, h 19)
 

The application program can specify a, b, c, or d as the <value> portion of a <label> <value> pair. If the value appears in a context that might be ambiguous, such as for the value of the g field in the SET B, the appropriate <label> must accompany the <value>. The labels can be omitted when specifying values for C, because there is no ambiguity. The labels can never be omitted when specifying values for B, because A is optional and without a label for B, it is not possible to determine whether the value is for A or B.

CMIP services, using information from the compiled ASN.1 modules, verifies that the value and type are compatible.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014