If DCAM is used for administration, the messages are also sent to the console (UCON). The user may use the PP UCON load parameter to specify the logging destination. Refer to PP UCON in the “Database Operation” manual if necessary.
The default value is PP UCON=C’<U’. The first messages issued when UDS/SQL is started are sent to this destination.
The user may also use PP UCON to specify whether a message header is also to be output. The first messages issued when UDS/SQL is started always include the message header. Messages output to the terminal (SYSOUT) do not include the message header.
The messages are output in their full length, i.e. up to a maximum of 230 bytes. Only the first 230 bytes of messages longer than 230 bytes are output. Messages which exceed this maximum length can occur when the message file is not compatible with the UDS/SQL version.
A UDS/SQL central system message that is sent to a DCAM application has the following format:
|
: : :
0 ... P ... < 230 bytes
message-header
Information section for the support of automatic administration, which consists of printable characters and which has the following structure:
Bytes | ||
0-8 | Character constant ’UDS/SQL: (’ | |
9-12 | UDS/SQL version | |
13-14 | Double-digit version identifier of the message format; the version of this message format is ’01’. | |
15-22 | DCAM processor name at the time the message was generated; | |
23-30 | Configuration name at the time the message was generated; | |
31-34 | Four-digit sequence number for all the messages of the configuration, | |
35 | Single-character identifier ’S’ The messages contains message-text, i.e. it is a message from themessage file. The additional information provided within the message is independent of the national language being used. ’N’ The message contains output-text, i.e. it is a message generated by the UDS/SQL central system; national language-independent output starting with tttt: alphanumeric task sequence number | |
36-39 | Four-character message identifier for this message. All messages generated by one and the same DAL command have the same message identifier. | |
40 | Single-character identifier ’+’ Indicates other messages with the same message identifier exist | |
’'BLANK'’ | indicates the last message with this message identifier in a contiguous block. | |
41-43 | Three-digit number indicating the length of message-text or output-text | |
44-46 | Three-digit number indicating the position P of message-text or output-text within the message. | |
from 47 | This is where the part of the message that is to be interpreted in conjunction with the message identifier (byte 35) starts. If the identifier is ’N’, the contents of bytes 47-71 are not defined. If the identifier is ’S’, the contents of bytes 47-71 are defined as follows: | |
47-53 | Seven-character alphanumeric message key for the UDS/SQL message. | |
54-56 | Three-digit number indicating the length of the additional information (&00), or ’000’ if (&00) does not exist. | |
57-59 | Three-digit number indicating the position of the additional information (&00) within the message-text , i.e. relative to P, or ’000’ if (&00) does not exist. | |
60-62 | Three-digit number indicating the length of the additional information (&01), or ’000’ if (&01) does not exist. | |
63-65 | Three-digit number indicating the position of the additional information (&01) within the message-text , i.e. relative to P, or ’000’ if (&01) does not exist. | |
66-68 | Three-digit number indicating the length of the additional information (&02), or ’000’ if (&02) does not exist. | |
69-71 | Three-digit number indicating the position of the additional information (&02) within the message-text , i.e. relative to P, or ’000’ if (&02) does not exist. | |
72 - < 230 | Reserved area including the character ’)’ and message-text or output-text. The starting position P of message-text or output-text can only be defined by means of the position in bytes 44-46. | |
message-text
Message from the UDS/SQL central system with the following format (see "Explanation of the message text format"):
mpref mkey t1 (&00) t2 (&01) t3 (&02) t4
mpref | Message prefix; characters which the operating system adds to the message as a prefix. |
mkey | Seven-character alphanumeric message key of the UDS/SQL message (like bytes 47-53). |
t1-t4 | National language parts of the message. |
(&00) | Variable national-language-independent parts of the message. |
(&01) | Additional diagnostic information. |
(&02) | Variable national-language-independent parts of the message. |
output-text
Output from the UDS/SQL central system with the following format:
tttt: 'BLANK'
text
tttt | Four-digit task sequence number of the task which caused the message to be output |
text | Output text; national-language-independent |
Example
The example below describes the UDS/SQL message UDS0201, including the message header.
UDS/SQL:(029B01D016ZE01SALESDPT0007SA001 052080UDS0201000000023029000000) % UDS0201 UDS SYSTE
0 1 2 3 4 5 6 7 8 9
0.........0.........0.........0.........0.........0.........0.........0.........0.........0.........
M READY (OPCF001,14:41:11/4284)
1 1 1 1 1
0 1 2 3 4
0.........0.........0.........0.........0......
029B | UDS/SQL Version 2.9B |
01 | Interface version |
D016ZE01 | DCAM processor name |
SALESDPT | Configuration name |
0007 | Sequence number of the message |
S | The message is from the message file. |
A001 | Message identifier |
’ ’ | It is the last message of a message block. |
052 | message-text is 52 bytes long. |
080 | message-text starts at byte 80. |
UDS0201 | The message key of the UDS/SQL message is UDS0201. |
000 | (&00) does not exist. |
000 | (&00) does not exist |
023 | (&01) is 23 bytes long. |
029 | (&01) starts at byte 80 + 29 = 109. |
000 | (&02) does not exist. |
000 | (&02) does not exist. |
Messages resulting from DAL commands
If DCAM is used for administration, messages relating to DAL commands are logged.
Once a DAL command has been entered, the following is the first message issued as a result of the command:
UDS0220 UDS RECEIVED COMMAND: dal-echo
dal-echo Repetition of the DAL command entered.
The associated message header contains a message identifier which is then used for all subsequent messages issued as a result of this DAL command. Only the message identifier allows the user to clearly identify any subsequent messages generated by this DAL command.
The same applies to the DAL command PERFORM, i.e. the message identifier of messages generated by PERFORM is associated with the DAL command PERFORM. The messages are not linked to messages generated by previous DAL commands like ADD DB, DROP DB, etc..
If the DAL command was entered correctly and no errors occurred during the processing of this DAL command, the following message is the last message issued as a result of this DAL command:
UDS0218 UDS COMPLETED EXECUTION OF DAL COMMAND
or, in the case of UDS-D DAL commands
UDS0832 UDS-D COMMAND EXECUTED
This does not apply to all DAL commands. The DAL command ABORT ALL, for example, generates further internal actions that result in all currently open transactions being rolled back.
The final message issued as the result of a DAL command only signals the end of the primary action in the system. The end of any secondary actions is not logged. With the help of an appropriate DISPLAY DAL command, the administrator can also monitor the secondary actions of a DAL command.
If an incorrect DAL command is entered or the processing of a DAL command is aborted, one of the following messages is issued as the final message, depending on the cause of the error:
UDS0209 UDS USER ERROR: COMMAND REJECTED UDS0392 UDS-D NOT AVAILABLE DURING THIS SESSION UDS0803 UDS-D NOT YET STARTED UDS0804 UDS-D ALREADY STARTED UDS0808 UDS-D TERMINATING
The message UDS0209 may appear more than once with differing levels of detail concerning the cause.
The message
UDS0206 UDS ACCEPTED COMMAND
is issued after
UDS0220 UDS RECEIVED COMMAND:
for some DAL commands and signals the fact that the command has been entered correctly and can be executed, even if execution cannot be effected immediately.