The APPLICATION-CONTEXT control statement is required only for communication based on the OSI TP protocol. You only have to specify the APPLICATION-CONTEXT statement if you want to define an additional application context.
It allows you to define the application context used for communication via OSI TP. The application context determines the rules governing data transfer between the
communication partners. It defines how the user data is encoded for transfer, and the format in which data is transferred. The application context must be coordinated with the partner.
The APPLICATION-CONTEXT statement enables you to define a local name for an application context, and to assign an object identifier and the abstract syntaxes belonging to this application context.
openUTM generates the standard application contexts UDTAC, UDTDISAC, XATMIAC, UDTCCR, UDTSEC and XATMICCR.
|
|
application_context_name | |
A local name for an application context up to eight characters in length. application_context_name must be unique within the UTM application. | |
OBJECT-IDENTIFIER=object_identifier | |
Object identifier of the application context specified as follows: object_identifier=(number1,number2, ... ,number10) number is a positive integer in the range 0 to 67108863. For object_identifier, you can specify two to ten integers enclosed in parentheses, each of which is separated by a comma. The number of integers entered and their positions are relevant. object_identifier must be unique within the UTM application, i.e. another application context must not be generated with the same object identifier. | |
ABSTRACT-SYNTAX= Abstract syntax assigned to the application context for the transfer of user data. | |
abstract_syntax_name | |
Name of an abstract syntax defined using the ABSTRACT-SYNTAX control statement. | |
(abstract_syntax_name, ..., abstract_syntax_name) | |
List of up to nine abstract syntaxes separated by commas. Each abstract syntax specified in abstract_syntax_name must be defined beforehand using the ABSTRACT-SYNTAX statement. The default UTM syntaxes CCR, UDT, XATMI, and UTMSEC need not be explicitly generated. |
To work with transaction processing, a application context must be selected that contains the abstract syntax CCR.
If sign-on data is to be passed in a APRO call, then a application context must be selected that contains the abstract syntax UTMSEC.
If both partners use the XATMI interface, then a application context must be selected that contains the abstract syntax XATMI.
openUTM automatically generates the application contexts UDTAC, UDTDISAC, XATMIAC, UDTCCR, UDTSEC and XATMICCR, which are defined as follows:
Generation of “UDTAC”:
APPLICATION-CONTEXT UDTAC, -
OBJECT-IDENTIFIER=(1, 0, 10026, 6, 2), -
ABSTRACT-SYNTAX=UDT
Symbolic representation of the object identifier:
(iso, standard, tp, udt, application-context)
Generation of “UDTDISAC”:
APPLICATION-CONTEXT UDTDISAC, -
OBJECT-IDENTIFIER=(1, 0, 10026, 6, 2, 1), -
ABSTRACT-SYNTAX=UDT
Symbolic representation of the object identifier:
(iso, standard, tp, udt, application-context, with-tp)
Generation of “XATMIAC”:
APPLICATION-CONTEXT XATMIAC, -
OBJECT-IDENTIFIER=(1, 2, 826, 0, 1050, 4, 2, 1), -
ABSTRACT-SYNTAX=(XATMI)
Symbolic representation of the object identifier:
(iso, national-member-body, bsi, disc, xopen, xatmi, application-context,
atpll-21-31)
Generation of “UDTCCR”:
APPLICATION-CONTEXT UDTCCR, -
OBJECT-IDENTIFIER=(1, 0, 10026, 6, 2), -
ABSTRACT-SYNTAX=(UDT, CCR)
Symbolic representation of the object identifier:
(iso, standard, tp, udt, application-context)
Generation of “UDTSEC”:
APPLICATION-CONTEXT UDTSEC, -
OBJECT-IDENTIFIER=(1, 3, 0012, 2, 1107, 1, 6, 1, 3, 0), -
ABSTRACT-SYNTAX=(UDT, UTMSEC, CCR)
Symbolic representation of the object identifier:
(iso, identified-organisation, icd-ecma, member-company, siemens-units,
sni, transaction-processing, utm-security, application-context, version)
Generation of “XATMICCR”:
APPLICATION-CONTEXT XATMICCR, -
OBJECT-IDENTIFIER=(1, 2, 826, 0, 1050, 4, 2, 1), -
ABSTRACT-SYNTAX=(XATMI, CCR)
Symbolic representation of the object identifier:
(iso, national-member-body, bsi, disc, xopen, xatmi, application-context,
atpll-21-31)