(JMS only) to help with debugging, monitoring, and so forth, predefined properties specific to Adaptive Server are included in the properties portion of the JMS message. These properties typically handle messages that either originate from another Adaptive Server, or that may be useful in debugging.
Many of these message properties are included only if you are running diagserver, or when certain trace flags are turned on. All properties beginning with “ASE_” are reserved; you cannot set them using msgsend or msgpublish. Table 3-3 describes these message properties.
Property |
Description |
When to use |
|---|---|---|
ASE_RTMS_CHARSET |
Character set encoding of sent data. |
Always |
ASE_MSGBODY_SCHEMA |
The schema describing the message body or a null value. This schema is non-null only if the user sends the message schema as part of msgsend. If ASE_MSGBODY_FORMAT is xml, this property contains the XML schema describing the payload. This schema is not truncated, even if its value exceeds 16K. |
Always |
ASE_MSGBODY_FORMAT |
The format of the message body: xml, string (in server character set), binary, and unicode (unichar in network order). |
Always |
ASE_ORIGIN |
Name of the originating Adaptive Server. |
Present with diagserver |
ASE_RTMS_VERSION |
Version of Adaptive Server using Active Messaging. |
Always |
ASE_SPID |
SPID that sent the message. |
Present with diagserver |
ASE_TIMESTAMP |
The timestamp of Adaptive Server showing the time the message was sent. |
Present with diagserver |
ASE_VERSION |
Version of Adaptive Server that published the message. |
Always |
ASE_VERSIONSTRING |
Version string of the Adaptive Server. Provides information about platform, build type, and so on. Useful for debugging. |
Present with diagserver |
These properties are shown for informational purposes
only. They may change in the future.
