CALLUTM generates the following messages:
CUA0010: give attributes
This message is output after CALLUTM has been started and prompts you to enter the statement CREATE-CONFIGURATION.
CUA0015: symb-dest-name not found in UPICFILE
This message can occur after either of the statements CREATE-CONFIGURATION or MODIFY-CONFIGURATION has been issued. It is output if the name specified in the operand SYMB-DEST-NAME does not exist in the UPICFILE. The statement is aborted.
In procedures, this also causes the program to abort.
CUA0020: conversation started by service <name> has to be continued
This message indicates that a service started previously with SELECT-SERVICE needs to be continued. You can now issue the CONTINUE-SERVICE statement to continue the service, or abort it with DEALLOCATE-CONVERSATION.
<name> outputs the transaction code with which the service was started.
CUA0025: error analysing SDF statement = nnnn
An error occurred during analysis of an SDF statement. nnnn indicates the place within the program at which the error occurred.
In procedures, this causes the program to abort.
CUA0030: JV = <name> not accessible (error = nnnnnnn)
The error nnnnnnn occurred during initialization of the job variable <name>. The program attempts to rectify the error. If it cannot do so this will, in procedures, cause the program to abort.
callutm:error in <upic-call>:n
CUA0035: error in send-receive routine = nnnn
An error occurred during a call to the UPIC carrier system. Before the message CUA0035 is output, CALLUTM first issues „callutm:...“ regarding the UPIC call (<upic-call>) during which the error occurred and the UPIC return code that was generated n (for an explanation of the meaning, see the manual „openUTM-Client for the UPIC Carrier System”).
callutm:error in <upic-call>:n
In CUA0035, nnnn indicates the place within the program at which the error occurred. In procedures, this error causes the program to abort.
Example
//**- callutm: error in allocate: 1 -**//
CUA0035: error in send-receive routine = 2007
This means that it was not possible to establish a connection to the UTM application. This message is output if the UTM application is not available, if the BCMAP commands issued for the UTM application contained errors, or if no BCMAP commands have yet been issued for the UTM application.
CUA0040: not processed statement = <name>
CUA0045: program run is continued with next statement
The statement <name> could not be executed. The program run is not aborted: you can continue it by issuing further statements. In procedures, the program run is continued with the following statement:
CUA0050: configuration modified
This message can occur after a MODIFY-CONFIGURATION statement. It indicates that the statement was executed successfully and that the configuration has been modified as specified. You can now resume your work under the new configuration.
CUA0051: no value given to modify configuration
This message can occur after a MODIFY-CONFIGURATION statement. It indicates that the statement was analyzed successfully, but that the values specified did not result in a modification of the configuration.
CUA0055: conversation deallocated and abnormal end
The conversation with the UTM application has been shut down. The service in the UTM application has been aborted.
In procedures, this causes the program to abort.
Possible causes:
The service in the UTM application encountered an error (PEND ER).
An administration service was started for which the client did not possess the necessary privileges.
CUA0060: no logging file assigned, output re-assigned to sysout (stdout)
This message can occur after a SHOW-CONFIGURATION statement for which OUTPUT=*LOGGING-FILE was specified to request output to a log file.
The message indicates that no log file has yet been assigned; instead, output is redirected to SYSOUT.
CUA0065: deallocate not executed (program not in conversation), program run can be continued with next statement"
The DEALLOCATE-CONVERSATION statement has been entered but no service was open.
The output is sent to SYSOUT.
CUA0070: restart not possible, continue with new service
It was not possible to restart with KDCDISP.
CUA0080: for a list of c-strings the total c-string-length (1800) is exceeded
A list of C strings was entered in the SERVICE-DATA operand in the SELECT-SERVICE or CONTINUE-SERVICE statement. The length of the data exceeds the maximum permitted length.
CUA0085: current conversation will be terminated
CALLUTM is running in a procedure or in batch mode and the UPIC transport protocol has reported an error. CALLUTM terminates the open service and may then branch to the statement CALLUTM-ERROR-STEP or reaches the end of the statements.
CUA0090: encryption is not available in this environment
Encryption not available.
Action: Integrate encryption in the current UPIC client library.
CUA0100: CALLUTM-ERROR-STEP reached
After the occurrence of an error in a procedure or in batch mode, all statements were skipped until CALLUTM-ERROR-STEP was recognized.
CUA0105: all statements will be ignored until CALLUTM-ERROR-STEP is recognized
After the occurrence of an error in a procedure or in batch mode, all statements are skipped until CALLUTM-ERROR-STEP is detected. If no such statement is found, END terminates the program run.