## UDSREVI

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDSREVI COMP=UDSMF,VER=29B,DATE=180312

## UDS0200

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0200 UDS SYSTEM ERROR (&00) (&01) (&02)

### Meaning

In UDS/SQL or in the UDS/SQL-connection-module a serious error was
detected. In general, UDS/SQL or the user program will be
terminated with DUMP.

### Response

Depends on the three-digit internal message number in insert (&01).
For further information see manual 'UDS/SQL Messages'.

## UDS0201

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0201 UDS SYSTEM READY (&00) (&01) (&02)

## UDS0202

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0202 UDS ABNORMAL SYSTEM TERMINATION WITH (&00) (&01) (&02)

### Meaning

UDS/SQL is aborted due to errors or by the %TERM command.
(&00): number of the DML statement processed and date.

### Response

Take Dump.
UDS/SQL may be reloaded with restart, if required.

## UDS0203

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0203 UDS USER ERROR: LINK ERROR LINKING (&00) (&01) (&02)

### Meaning

(&00): name of module/load source
The module specified in (&00) cannot be loaded from load source (&00).
(&01): diagnostic information

### Response

1. Check software configuration inventory (SCI), LINK-FILE command
or SET-TASKLIB command.
2. Check whether the module (&00) is held in the load source (&00).
3. Check whether the LINK-FILE or SET-TASKLIB command of the master
task and PP TASKLIB match.

## UDS0204

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0204 UDS MAINTASK STARTING NOW (&00) (&01) (&02)

## UDS0205

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0205 UDS DUMP WANTED? (Y=YES/N=NO) (REASON=(&00)) (&01) (&02)

### Meaning

A memory dump is produced for the reason given in REASON.

### Response

Respond to message with
Y: Dump is generated
N: Dump is suppressed.

## UDS0206

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0206 UDS ACCEPTED COMMAND (&00) (&01) (&02)

### Meaning

The DAL command contains no errors and will be executed. Execution
may take some time.

## UDS0207

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0207 UDS USER ERROR: UDS ALREADY LOADED FOR THE CONFIGURATION (&00) (&01) (&02)

### Meaning

(&00): configuration name.

### Response

If the UDS/SQL tasks of an earlier UDS/SQL session have not yet terminated
with abnormal session end, they should be terminated using CANCEL-JOB.

## UDS0208

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0208 UDS MAINTASK READY (&00) (&01) (&02)

## UDS0209

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0209 UDS USER ERROR: COMMAND REJECTED (&00) (&01) (&02)

### Response

Depends on information in (&01). See manual 'UDS/SQL Messages'.

## UDS0210

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0210 UDS MAINTASK TERMINATION COMPLETED (&00) (&01) (&02)

### Meaning

Termination has been completed for the maintask.

## UDS0211

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0211 UDS WARNING: UDS COMMAND DELAYED, SINCE NOT POSSIBLE AT THIS MOMENT (&00) (&01) (&02)

### Meaning

The UDS/SQL command cannot be executed at the moment. Execution will be
delayed until it is possible.

### Response

Repeat command if this does not occur internally.

## UDS0212

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0212 UDS SYSTEM INITIALIZATION DELAYED. PLEASE CHECK BATCHLIMIT (&00) (&01) (&02)

### Meaning

The system is not fully initialized because all the tasks required have
not
yet been run. The batch limit may be too low.

### Response

Check if the batch limit is high enough or if the task could not be
started
for other reasons (check join task).

## UDS0213

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0213 UDS NORMAL SYSTEM TERMINATION WITH (&00) (&01) (&02)

### Meaning

UDS/SQL has terminated normally.
(&00): number of the DML statements processed and date.

## UDS0214

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0214 UDS TRANSACTION (&00) CANCEL STARTED (&01) (&02)

### Meaning

The transaction specified in (&00) is aborted.

## UDS0215

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0215 UDS STARTING (&00) (&01) (&02)

### Meaning

(&00): version number and date.

## UDS0216

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0216 UDS WARNING: LIFETIME FOR DISTRIBUTED COMMUNICATION IS TOO SMALL (&00) (&01) (&02)

### Meaning

The wait time set by UDS/SQL for responses from UDSCT or a remote
configuration is too short.

### Response

If message recurs, contact UDS/SQL support staff.

## UDS0217

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0217 UDS USER ERROR: BFORMAT RUN MISSING (&00) (&01) (&02)

## UDS0218

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0218 UDS COMPLETED EXECUTION OF DAL COMMAND (&00) (&01) (&02)

### Meaning

There will be no further messages concerning this DAL command.

## UDS0219

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0219 UDS USER ERROR: SESSION TYPE WRONG (&00) (&01) (&02)

### Meaning

The session type in a restart is different from that in the interrupted .
session.

### Response

Repeat restart with correct session type.

## UDS0220

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0220 UDS RECEIVED COMMAND: (&00) (&01) (&02)

### Meaning

UDS/SQL has received a DAL command.
There will be further messages concerning this DAL command.
(&00): received DAL command.
It is obvious from this insert what actually arrived for UDS/SQL.
In particular you will recognize whether or not parts of the
command you entered have been cut off.

## UDS0221

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0221 UDS USER ERROR: COLD START IMPOSSIBLE (&00) (&01) (&02)

### Meaning

UDS/SQL expects a warm start whilst the UDS/SQL user has attempted a
cold start.

### Response

Restart with PP START=WARM (if this is acceptable from the
administration viewpoint).

## UDS0222

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0222 UDS USER ERROR: THE GIVEN TASKLIB IS UNKNOWN. (&00) (&01) (&02)

### Meaning

The library specified in the load parameter TASKLIB is not known.

### Response

Check load parameter TASKLIB.

## UDS0223

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0223 UDS USER ERROR: PROGRAM PARAMETER WRONG (&00) (&01) (&02)

### Meaning

(&00): incorrect load parameter.

### Response

Repeat DBH session with corrected load parameter. In interactive mode, the
erroneous statement can be corrected by repeating the entry.
(Exceptions: 'PP' missing, PP DBNAME, PP PASSWORD)

## UDS0224

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0224 CONTINUE NOT ALLOWED. (&00) (&01) (&02)

### Meaning

The DAL command CONTINUE has no meaning in the current situation and is
therefore not permitted.

## UDS0225

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0225 UDS ERROR DURING (&00) STATEMENT (&01) (&02)

### Meaning

An error occurred during processing of DML statement (&00).

## UDS0226

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0226 UDS USER ERROR: SPACE ON REALM (&00) EXHAUSTED (&01) (&02)

### Meaning

The free storage which is physically available in realm (&00) is
exhausted.

### Response

Increase realm size with BREORG or activate online realm extensibility.

## UDS0227

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0227 UDS USER ERROR: NUMBER OF RECORDS EXHAUSTED FOR RECORD (&00) (&01) (&02)

### Meaning

The DBTT for record (&00) is completely full.

### Response

Increase size of DBTT with REORG or release for use DBTT entries that are
unused but occupied using BMODTT or activate online DBTT extensibility.

## UDS0228

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0228 UDS USER ERROR: REALM (&00) OFFLINE (&01) (&02)

## UDS0229

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0229 FASTPAM NOT LOADED. ACCESS WILL BE PERFORMED WITH UPAM. (&00) (&01) (&02)

### Meaning

Because FASTPAM is not loaded, UPAM will be used for file access.
This will lead to a worse performance.

### Response

For better performance FASTPAM should be loaded.

## UDS0230

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0230 UDS PROGRAM TIME RUN OUT (&00) (&01) (&02)

### Meaning

Task or program time of a UDS/SQL task has elapsed.

### Response

UDS/SQL must be reloaded with a warm start.
For UDS/SQL continuous operation, include the NTL option in the
user catalog entry if possible.

## UDS0231

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0231 UDS ERROR: I/O ERROR ON REALM (&00). NO MORE TRANSACTIONS WILL BE STARTED. (&01) (&02)

## UDS0232

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0232 UDS TASK ABNORMALLY ENDED (&00) (&01) (&02)

### Meaning

One of the UDS/SQL tasks has been ended by LOAD-EXECUTABLE-PROGRAM,
START-EXECUTABLE-PROGRAM, LOGOFF, ABEND or CANCEL-JOB.

### Response

Restart UDS/SQL.

## UDS0233

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0233 UDS ERROR: CATALOG FILE WRONG (&01) (&02) (&03)

## UDS0234

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0234 START OF SERVERTASK FAILED (&01) (&02) (&03)

### Meaning

Start of a servertask of the independent DBH failed

### Response

Check messages of mastertask and logging of the batch job
which starts the servertask

## UDS0236

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0236 UDS USER ERROR: NUMBER OF SUBSCHEMAS EXHAUSTED (&00) (&01) (&02)

### Meaning

The user transactions require more subschemas simultaneously than were
specified in PP SUBSCHEMA.

### Response

Do not start a new transaction until a subschema has been released.
Increase the value of PP SUBSCHEMA at the next opportunity
(new UDS/SQL version).

## UDS0237

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0237 UDS USER ERROR: THE GIVEN TASKLIB IS NOT SHAREABLE. (&00) (&01) (&02)

### Meaning

The library specified in the load parameter TASKLIB is not shareable.

### Response

Make library shareable.

## UDS0238

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0238 UDS USER ERROR: PASSWORD MISSING FOR REALM (&00) (&01) (&02)

## UDS0239

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0239 UDS COLD START IS EXECUTED (&00) (&01) (&02)

## UDS0240

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0240 UDS WARM START IS EXECUTED (&00) (&01) (&02)

## UDS0241

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0241 UDS TERMINATION INITIATED ON (&00) (&01) (&02)

### Meaning

Termination was introduced for the component (&00).
(&00) can assume the following values: SERVERTASK or TRANSACTION.

## UDS0242

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0242 UDS USER ERROR: UDS NOT LOADED FOR CONFIGURATION (&00) (&01) (&02)

### Meaning

a) UDS/SQL not yet been loaded.
b) A TIAM application without SECOLTP privilege is trying to connect,
but the security level of the configuration is 'F2' or 'F2-EXCEPT'.
(&00): configuration name
(&01): diagnostic information

### Response

a) Check and correct UDS/SQL loading procedure, or SET-FILE-LINK
command.
(LINK-NAME=DATABASE) of the user task if necessary.
b) Notify UDS/SQL administrator.

## UDS0243

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0243 UDS USER ERROR: NUMBER OF TRANSACTIONS EXHAUSTED (&00) (&01) (&02)

### Meaning

The maximum number of possible transactions has been reached
(PP TRANSACTION).
(&00): diagnostic information.

### Response

Do not start a new transaction until a running transaction has been
terminated (FINISH).

## UDS0244

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0244 UDS DBH ABNORMALLY DOWN (&00) (&01) (&02)

### Meaning

UDS/SQL has been terminated abnormally.
(&00): diagnostic information.

### Response

Restart UDS/SQL.

## UDS0245

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0245 UDS TRANSACTION HAS BEEN CANCELLED DUE TO DATABASE STATUS (&00) (&01) (&02)

### Meaning

The transaction has been cancelled by UDS/SQL.
(&00): data base status of DML statement which resulted in abortion.
The database status may be internal and not described in the User Guide.

## UDS0246

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0246 UDS DVS-ERROR (&00) IN UDS CONNECTION (&01) (&02)

### Meaning

Error (&00) occurred when the file with the file link name DATABASE or
UDSPLEX was opened.
(&00): diagnostic information.

### Response

Take dump.

## UDS0247

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0247 UDS USER ERROR: UDS CONNECTION CAN'T GET NAME OF (&00). SET-FILE-LINK COMMAND CORRECT? (&01) (&02)

### Meaning

The file specified in the SET-FILE-LINK command with LINK-NAME=
DATABASE/UDSPLEX could not be found.

### Response

- Check whether a SET-FILE-LINK command has been given with
LINK-NAME=DATABASE/UDSPLEX.
- Enter SET-FILE-LINK command, restart application program.

## UDS0248

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0248 UDS USER ERROR: ACTION IMPOSSIBLE DUE TO PREVIOUS ERRORS. PROGRAM TERMINATED. (&00) (&01) (&02)

### Meaning

Previous error messages and return codes have been ignored by the user
program.
(&00): diagnostic information.

### Response

Correct error(s) in program.

## UDS0249

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0249 UDS COMMANDS TO TSN (&00) PLEASE. (&01) (&02)

### Meaning

Only the master task with the TSN (&00) can process UDS/SQL commands.

### Response

Issue UDS/SQL command to master task.

## UDS0250

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0250 UDS IMMEDIATE TERMINATION WANTED? (Y=YES/N=NO) (&00) (&01) (&02)

### Meaning

Question following DAL command %TERM.

### Response

Y: the UDS/SQL session is aborted. The data base is inconsistent and
must be restarted with a warm start.
N: the %TERM command is ignored.

## UDS0251

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0251 UDS DBH DOWN (&00) (&01) (&02)

### Meaning

UDS/SQL or UDS-D has been terminated.
(&00) contains diagnostic information for UDS/SQL. Under UDS-D, (&00)
contains the module code of the module that detected that UDS-D is no
longer operational and the return code (X'0C':DBMS_DOWN).
(&01): dignostic information.

### Response

Restart UDS/SQL.

## UDS0252

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0252 UDS ERROR IN TRANSACTION (&00) (&01) (&02)

### Meaning

An error occurred in transaction (&00).
(&00): 10-digit: Global TA ID
8-digit: Program name
4-digit: TSN.

## UDS0253

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0253 UDS WARNING: REGISTERS ARE PROBABLY CHANGED BY OTHER SUBSYSTEM (&00) (&01) (&02).

### Meaning

The UDS/SQL STXIT routine has detected that the register record
of the interrupted process has been altered.

### Response

Do not necessarily use the error registers in the dump for
error diagnostics.

## UDS0254

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0254 UDS USER ERROR: IN UTILITY SESSION NO USER PROGRAM IS ALLOWED. (&00) (&01) (&02)

### Meaning

Only the UDS/SQL-internal utility routine subschemas may be addressed in
a utility session, and no user subschemas.

### Response

DIAG.

## UDS0255

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0255 UDS USER ERROR: IN USER SESSION NO UTILITY PROGRAM IS ALLOWED. (&00) (&01) (&02)

### Meaning

Only user subschemas may be addressed in a session, and no UDS/SQL-
internal utility routine subschemas.

### Response

Check subschema names in the READY statements for the application
programs.

## UDS0256

Destination: USER-TASK, CONSOLE Routing code: U Weight: 90

Warranty : NO

UDS0256 UDS SESSION CONTINUE (Y/N)? (&00) (&01) (&02)

### Meaning

Continuation after a serious error. The transaction is aborted.

### Response

Y: The session is continued
N: The session is aborted.

## UDS0257

Destination: USER-TASK, CONSOLE Routing code: U Weight: 90

Warranty : NO

UDS0257 UDS DUMP WANTED (Y/N)? (&00) (&01) (&02)

### Meaning

Continuation message following UDS/SQL system crash.

### Response

Y: Dump is generated
N: Dump is suppressed.

## UDS0258

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0258 CANCEL/ROLLBACK INITIATED FOR TRANSACTION (&00) (&01) (&02)

### Meaning

The DBH has discovered that updates in this transactions have been
undone. An attempt has been made to reset the updates to the stored
data using the log file(s) in an UPDATE transaction. If this is
unsuccessful or if PP LOG=NO is specified, the active data bases can
be used for retrieval. The DBH marks the data base(s) involved as
irreparably inconsistent.
Which of the two options will be used does not have to be defined when
the message is issued. Another message is issued to indicate the
marking of the data base(s) as inconsistent.
(&01) (&02): diagnostic information.

## UDS0259

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0259 PROGRAM ERROR (&00) AT LOCATION (&01) IN UDS USER PROGRAM (&02)

### Meaning

P (program) error in application program.
(&02): diagnostic information.

### Response

Correct program.

## UDS0260

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0260 PROGRAM TIME RUNOUT FOR UDS USER PROGRAM (&00) (&01) (&02)

### Meaning

The program run time (as specified in START-EXECUTABLE-PROGRAM etc.)
has expired.
(&00): diagnostic information.

### Response

Restart DBH-session with a larger value in the TIME parameter of
the START-EXECUTABLE-PROGRAM command.

## UDS0261

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0261 UDS USER PROGRAM ABNORMALLY ENDED. (&00) (&01) (&02)

### Meaning

The application program was aborted with LOGOFF, START-EXECUTABLE-PROGRAM,
LOAD-EXECUTABLE-PROGRAM, ABEND or CANCEL-JOB.
(&00): diagnostic information.

### Response

If necessary, correct program (cf. additional information for
cause of error). Restart program.

## UDS0262

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0262 UDS ERROR: CANCEL/ROLLBACK FOR TRANSACTION (&00) NOT SUCCESSFUL. (&01) (&02)

### Meaning

Rollback of transaction (&00) may have failed.
(&01): diagnostic information.

### Response

- For independent UDS/SQL with session still available:
Roll back open transaction using DAL command ABORT if possible.
- For independent UDS/SQL with session unavailable, or linked-in UDS/SQL:
Transaction can be rolled back by means of a successful warm start.
If warm start is unsuccessful, roll back to an earlier version.
If no warm start takes place, the transaction has been rolled back
successfully.

## UDS0263

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0263 UDS ACCESS VIA CALL DML NOT POSSIBLE DURING THIS SESSION (&00) (&01) (&02)

### Meaning

ERROR during linking of UDS/SQL subtasks with the SSITAB pool. It is not
possible to access UDS/SQL data bases via CALL DML or KDBS in the current
session.

### Response

If the return code of the ENAMP macro output under (&00) indicates that
the size of the virtual address space is exceeded, this space must either
be expanded or the session newly startet defining smaller values for
PP BUFFER, PP SERVERTASK, PP TRANSACTION, PP SIP-SIZE. Otherwise this is a
UDS/SQL internal error for which a dump is required, and the session can
be continued.

## UDS0264

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0264 ERROR IN STXIT ROUTINE. UDS USER PROGRAM WILL BE TERMINATED IMMEDIATELY. (&00) (&01) (&02)

### Meaning

Another interrupt has occurred in a STXIT routine.
(&00): diagnostic information.

### Response

Take dump.

## UDS0265

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0265 UDS TRANSACTION IDENTIFICATION IN USER PROGRAM INCORRECT (&00) (&01) (&02)

### Meaning

Incorrect subschema module. Incorrect transaction id.
(&00): diagnostic information.

### Response

Check subschema module (COBOL DML).
Correct transaction reference (CALL DML).

## UDS0266

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0266 UDS WARNING: ENTRY USERSTIX IS NOT SUPPORTED IN UDS VERSION (&00) (&01) (&02).

### Meaning

The option of error handling via the USERSTIX entry is no longer available
in this UDS/SQL-version.
(&00): version number.

### Response

The STXIT routines included in the application should be converted to the
new STXIT task ('STXIT parallelism').

## UDS0267

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0267 UDS USER ERROR: DML STATEMENT REJECTED, SINCE ANOTHER ONE IS ACTIVE IN UDS. (&00) (&01) (&02)

### Meaning

Deserialization (possible due to user STXIT).
(&00): diagnostic information.

### Response

Check program (possible error in user STXIT routine).

## UDS0268

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0268 UDS WARNING: UDS STXIT ROUTINE (SCSXUSER) CANNOT BE LINKED. (&00) (&01) (&02)

### Meaning

The STXIT routine cannot be linked; the program runs without
error handling routine.
(&00): diagnostic information

### Response

No immediate action. Check software configuration inventory (SCI),
LINK-FILE or SET-TASKLIB command and the module library.

## UDS0269

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0269 UDS USER ERROR: VERSION DIFFERENCE FOR (&00). (&01) (&02)

### Meaning

(&00): name of module/load source
(&01): diagnostic information
The version of the component specified in (&00) is not compatible with the
other components.

### Response

Check contents of the load source (&00), the software configuration
inventory (SCI) and the module library assigned by the LINK-FILE
command or SET-TASKLIB command.
- Create consistent module library.
- Restart program.

## UDS0270

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0270 UDS USER ERROR: THE SET-FILE-LINK COMMAND IS MISSING OR DOES NOT CONTAIN A VALID CONFIGURATION NAME (&00) (&01) (&02)

### Meaning

The command SET-FILE-LINK LINK-NAME=DATABASE has not been entered or
the specified file name contains illegal special characters or the
database is in use

### Response

Restart session using correct SET-FILE-LINK-command or make database
available

## UDS0271

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0271 UDS APPLICATION STOPPED BY COMMAND (&00) (&01) (&02)

### Meaning

The application has been stopped by the specified command.

## UDS0273

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0273 UDS WARNING: PP SERVERTASK IS GREATER THAN PP TRANSACTION. USED IS VALUE OF PP TRANSACTION. (&00) (&01) (&02)

### Meaning

A larger value was specified for PP SERVERTASK than for PP TRANSACTION.
The value for PP SERVERTASK is reduced to the value of PP TRANSACTION.
Only the number of servertasks specified in the reset value are processed.
.

### Response

At the next opportunity, enter a value for SERVERTASK that is smaller or
equal to PP TRANSACTION.

## UDS0274

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0274 UDS BKPT WANTED (Y/N)? INTERRUPT REGISTERS WILL BE LOADED. (&00) (&01) (&02)

### Meaning

If a serious error has occurred in the linked-in DBH, the contents of the
register at the time of the interruption are loaded if BKPT is selected.

### Response

Y: breakpoint is generated.
N: breakpoint is not generated.

## UDS0275

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0275 UDS DATABASE COULD STILL BE CLOSED (&00) (&01) (&02)

### Meaning

The data base could be closed successfully despite the previous errors.

## UDS0277

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0277 UDS ERROR ON PARAMFILE (&00) (&01) (&02)

### Response

See manual 'UDS/SQL Messages'.

## UDS0278

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0278 UDS STXIT ROUTINE CANNOT BE DEFINED (&00) (&01) (&02)

### Meaning

STXIT definition unsuccessful probably due to an old BS version
(V4 or older).

### Response

Check BS version.

## UDS0279

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0279 UDS USER PROGRAM TERMED WITHOUT FINISH/COMMIT;CANCEL/ROLLBACK IS GENERATED (&00) (&01) (&02)

### Meaning

A UDS/SQL application program was terminated without its transaction being
closed. The user STXIT routine therefore causes DBH to effect rollback.
Another message will indicate success.

## UDS0281

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0281 UDS USER ERROR: MAXIMUM NUMBER OF USERTASKS REACHED (&00) (&01) (&02)

### Meaning

The maximum number of user tasks permitted has been reached
(PP TRANSACTION).

### Response

Do not start any further application programs, or stop UDS/SQL session
and restart with a higher PP TRANSACTION value.

## UDS0282

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0282 UDS USER ERROR: ILLEGAL CONFIGURATION NAME (&00) (&01) (&02)

### Meaning

- The configuration name contains illegal characters.
- The connection to the configuration failed.

### Response

Check the generation of the configuration.

## UDS0283

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0283 UDS USER ERROR: USERINF PARAMETERS WRONG OR MISSING (&00) (&01) (&02)

### Meaning

The USERINF parameter area for CALL-DML is invalid or missing.

### Response

Find and correct error in application program.

## UDS0284

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0284 UDS USER ERROR: NO DSCEXT ROUTINE DEFINED (&00) (&01) (&02)

### Meaning

DSCEXT routine for CALL DML missing.

### Response

Link DSCEXT routine and restart application program.

## UDS0285

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0285 PLEASE CHECK TSN OR UTM APPLICATION (&00) (&01) (&02)

### Meaning

A task with the indicated TSN or the indicated UTM application
could be preventing UDS/SQL from being started.

### Response

Check whether a task with this TSN or with this UTM application exists.
If necessary, terminate the task with this TSN using a CANCEL-JOB
command or terminate this UTM application with BCLOSE.

## UDS0286

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0286 UDS WARNING: UDS CANNOT RUN AS TRANSACTION SYSTEM OR DEACTIVATION OPTION IS NOT ALLOWED (&00) (&01) (&02)

### Meaning

UDS/SQL does not run as a TP system or the deactivated option requested
via DBH load parameters is not contained in the JOIN entry.

### Response

Add necessary authorization to the JOIN entry if the functions are
required, otherwise ignore message.

## UDS0290

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0290 UDS SESSION RESTART WITH WRONG DB CONFIGURATION. CORRECT DB CONFIGURATION FOLLOWING: (&00) (&01) (&02)

### Meaning

A restart may only be executed on the db configuration available when the
session began.

### Response

Execute restart with the db configuration given below.

## UDS0291

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0291 UDS DBNAME = (&00) (&01) (&02)

### Meaning

Information on a db in a db configuration (see UDS0290).

### Response

(see UDS0290)

## UDS0292

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0292 UDS SESSION RESTART WITH WRONG AREA CONFIGURATION OF (&00). COMPARISON OF AREA CONFIGURATION FOLLOWING: (&01) (&02)

### Meaning

A restart may only be executed with the area configuration available
when the session began.

### Response

Execute restart with the correct area configuration for the specified db
(see list given below).

## UDS0293

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0293 UDS AREA REFERENCE (&00) (&01) (&02)

### Meaning

Reference information on an area in the db involved (see UDS0292).

### Response

(see UDS0292).

## UDS0294

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0294 UDS SESSION RESTART WITH CHANGED VALUE OF PP TRANSACTION. CORRECT VALUE IS: (&00) (&01) (&02)

### Meaning

A restart may only be executed with the PP TRANSACTION specified when the
session beegan.

### Response

Execute restart with the specified PP TRANSACTION value.

## UDS0295

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0295 UDS SESSION RESTART WITH CHANGED VALUE OF PP LOG. CORRECT VALUE IS: (&00) (&01) (&02)

### Meaning

A restart may only be executed with the PP LOG value specified when the
session began.

### Response

Execute restart with the specified PP LOG value.

## UDS0296

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0296 UDS USER ERROR: VALIDATION DATES IN SUBSCHEMA (&00) AND SCHEMA DO NOT MATCH (&01) (&02)

### Meaning

a) The validation date in the subschema differs from that in the schema
for the database.
(&00): subschema name
b) Invalid UDS/SQL version: either the DDL of the database contains
specifications concerning the Y2K-compliant processing of two-digit
year fields which cannot be processed using this UDS/SQL version,
or these YEAR specifications have not been correctly removed.
(&00): subschema name, not relevant here.
c) Invalid UDS/SQL version: the subschema contains NATIONAL data (UNICODE)
and can therefore only be processed by UDS/SQL V2.5 or a later version.
d) Invalid UDS/SQL version: the subschema contains BINARY 63 data
and can therefore only be processed by UDS/SQL V2.9 or a later version.

### Response

a) Recompile subschema. Recompile, relink and rerun application program.
b) Use the correct UDS/SQL version (>= V2.0B30).
If the YEAR specifications were not correctly removed, this can now
be done by restructuring with an unchanged schema and DDL2000 or
UDS/SQL V2.0B30 or a later version.
c) Use the correct UDS/SQL version (>= V2.5).
d) Use the correct UDS/SQL version (>= V2.9).

## UDS0297

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0297 UDS USER ERROR: VALIDATION DATES IN SUBSCHEMA (&00) AND DML STATEMENT DO NOT MATCH (&01) (&02)

### Meaning

The validation date in the DML statement, i.e. in the subschema of the
application program, differs from that in the subschema of the database.
(&00): subschema name

### Response

Recompile, relink and rerun application program.

## UDS0298

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0298 UDS AMBIGUOUS SUBSCHEMA NAMES, STARTING WITH (&00) (&01) (&02)

### Meaning

Ambigous subschema names in the current db configuration; they are
identical in their first six characters: (&00). These subschemas cannot
be referenced (via READY statement) until their names are unique.

### Response

Make subschema names unique in the first six characters (in all data bases
if possible). This might require the disconnection of the data bases
blocking a subschema due to ambiguous subschema names; a subschema name
can only be changed by deletion an recompilation.

## UDS0299

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0299 VALIDATION DATES: (&00) (&01) (&02)

### Meaning

UDS reports the non-matching validation dates (subschema/schema).
If the validation date of the schema deviates up to three seconds from
the corresponding date in the subschema, the error derives from using the
wrong UDS version (see UDS0296).
(&00): validation dates as yyyy-mm-dd hh:mm:ss;
yyyy-mm-dd hh:mm:ss

## UDS0300

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0300 UDS USER ERROR: INSUFFICENT COMMON MEMORY (&00) (&01) (&02)

### Meaning

The user address space is too small for the UDS/SQL communication pool.

### Response

Generate operating system with increased virtual storage space or
start UDS/SQL with reduced value of PP TRANSACTION or PP DBNAME.

## UDS0301

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0301 MEMORY OVERFLOW: FIND7SE MADE SEQUENTIAL (&00) (&01) (&02)

### Meaning

Normal processing of a complex FIND7 had to be abandoned due to lack of
class 6 memory for its intermediate results. A memory saving (but time
consuming) sequential search over the primary data was substituted.

### Response

Enlarge class 6 memory available for UDS/SQL.

## UDS0304

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0304 UDS AMBIGUOUS DATABASE NAME WITHIN THIS CONFIGURATION (&00) (&01) (&02)

### Meaning

The specified PP DBNAME parameter contains a data base that is not unique
within the current configuration.

### Response

Use only data bases with different names in a configuration.

## UDS0307

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0307 UDS >>> (&00) (&01) (&02)

### Meaning

Continuation line of preceding UDS/SQL message (e.g. UDS0200, UDS0700,
UDS0723) to describe the error situation in more detail.
Explanations are given with the corresponding preceding message.

## UDS0311

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0311 UDS ERROR ON READING HASH PROCEDURES (&00) (&01) (&02)

### Meaning

An error occurred whilst user-specific hash procedures were being read in.

### Response

Check the dbname.HASHLIB and/or the user-specific hash procedures.

## UDS0312

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0312 UDS WARNING: (&00) ON STATUSFILE (&01) (&02)

### Meaning

Error in status file access. (&00) specifies whether the error is
recoverable or not.

### Response

Recoverable error: Create two new status files after the
dc applications and the DBH have terminated
normally.
Non-recoverable error: If a DMS return code is available, the measures to
taken can be found in the 'System Messages' manual.
Otherwise, end db/dc session. Reset dc application
to consistent state. Create two new status files.
Restart db/dc session.

## UDS0314

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0314 UDS USER ERROR: RESTART WITH WRONG TYPE OF DBH (&00) (&01) (&02)

### Meaning

A different DBH variant to the one used before the session interrupt was
used (LINKED-IN, INDEPENDENT).

### Response

Execute restart with the correct DBH type.

## UDS0315

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0315 UDS WARNING: PP OUT OF RANGE, HAS BEEN MODIFIED. (&00) (&01) (&02)

### Meaning

PP statement modified by UDS/SQL.
(&00): PP statement entered.

### Response

Alter PP statement, if necessary.

## UDS0316

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0316 DAL VALUE OUT OF RANGE, VALUE MODIFIED. (&00) (&01) (&02)

### Meaning

The illegal operand value has been modified in the DAL command.

## UDS0317

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0317 UDS USER ERROR: ILLEGAL NUMBER OF DATABASES. (&00) (&01) (&02)

### Meaning

More data bases have been specified than are permitted under the
current DBH variant.
(&00): PP statement concerned.

### Response

Repeat initialization with corrected PP file.

## UDS0318

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0318 UDS WARNING: PP MAXDB CHANGED TO ACTUAL NUMBER OF DATABASES. (&00) (&01) (&02)

### Meaning

The PP MAXDB specified by the user does not correspond to the number of
specified data bases. UDS/SQL makes PP MAXDB equal to the number of
DBNAMEs.

### Response

Alter PP file, if necessary.

## UDS0319

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0319 UDS USER ERROR: UNCORRECTED ERROR IN PROGRAM PARAMETERS (&00) (&01) (&02)

### Meaning

An uncorrected error was found in the PP statements after PP entry had
been
completed.

### Response

Correct PP file. Repeat initialization.

## UDS0320

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0320 UDS USER ERROR: NAME OF PLITAB MODULE (&00) IS INVALID. (&01) (&02)

### Meaning

The name of the KDBS module contains illegal characters or is too long.

### Response

- Check SET-FILE-LINK command (LINK-NAME=UDSPLEX).
- Enter correct SET-FILE-LINK command, restart application program.

## UDS0321

Destination: USER-TASK, CONSOLE Routing code: U Weight: 90

Warranty : NO

UDS0321 UDS USER DUMP WANTED (Y/N)? (&00) (&01) (&02)

### Meaning

Errored application program behavior or ABEND.

### Response

Y: Dump is generated
N: Dump is suppressed.

## UDS0322

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0322 UDSDUMP V(&00) READY (&01) (&02)

### Meaning

C.UDSDUMP is loaded and ready.

## UDS0323

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0323 UDSDUMP NOT ENOUGH CLASS 6 MEMORY AVAILABLE TO READ DUMPFILE (&00) (&01) (&02)

### Meaning

The class 6 memory is not large enough for the dump file to be read in.
Either too little virtual storage is available for class5/class 6 memory,
or the class 5 memory is larger than in the task that generated the
dump file.

### Response

Terminate task with LOGOFF then reenter LOGON to ensure that as little
class 5 memory is occupied as possible. Initiate UDSDUMP again. If error
recurs, the dump must be output in the same memory area as dump file
generation.

## UDS0324

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0324 UDSDUMP FILENAME REJECTED: (&00) (&01) (&02)

### Meaning

The specified file name contains illegal characters, is only partially
qualified or is too long.

### Response

Enter the fully qualified file name of an existing file.

## UDS0325

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0325 UDSDUMP (&00) OF FILE (&01) IN ERROR (&02) (&03)

### Meaning

An error with DMS error code (&02) occurred during execution of the DMS
SVC
(&00).

### Response

Check the file following program end; take steps depending on error code.

## UDS0326

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0326 UDSDUMP: SPECIFIED TABLE NOT PRESENT (&00) (&01) (&02)

### Meaning

The specified table has not been edited and therefore cannot be specified.

## UDS0327

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0327 UDS USER ERROR: MAXIMUM NUMBER OF SQL SESSIONS REACHED (&00) (&01) (&02).

### Meaning

The maximum number of simultaneously open SQL sessions has been reached
(PP SQL). UDS/SQL's attempt to terminate inactive SQL sessions was
unsuccessful. No SQL session was inactive for longer than the period
specified in PP SQL-LIMIT.

### Response

Do not start a new SQL session until a current SQL session has been
terminated, or abort the UDS/SQL session and restart with increased
PP-SQL or lower PP SQL-LIMIT.

## UDS0328

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0328 UDS USER ERROR: REPLY FOR SQL-DML IMPOSSIBLE (&00) (&01) (&02).

### Meaning

No response could be given to an SQL job, because the entries pertaining
to the position or length of the response area were errored.

### Response

Analyze Dump.

## UDS0329

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0329 UDSDUMP TIME RUNOUT (&00) (&01) (&02)

### Meaning

The specified program run time has elapsed.

### Response

Repeat UDSDUMP run with increased program run time.

## UDS0330

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0330 UDSDUMP FILE IS EMPTY: (&00) (&01) (&02)

### Meaning

The file contains no correctly described data blocks.
(&00): file name

### Response

Enter END command or name of a correct file.

## UDS0331

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0331 UDSDUMP FILE IS NO PRIMARY DUMPFILE: (&00) (&01) (&02)

### Meaning

The file contains no data that could be used to identify or address areas
in the dump and is probably not a primary dump file.
(&00): file name.

### Response

Enter END command or a correct file.

## UDS0332

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0332 UDSDUMP LAYOUT OF FILE (&00) HAS WRONG VERSION: (&01) (&02)

### Meaning

Different version strings in UDSDUMP and in primary dump file.
(&00): file name
(&01): version string in the file.

### Response

Use the UDSDUMP version corresponding to the file.

## UDS0333

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0333 UDSDUMP (&00) ERROR (&01) (&02)

### Meaning

General error message for SVC execution (not DMS SVC) and validity check.
(&00): SVC macro name or error identification
(&01): readable SVC return code, hexadecimal, or error specification.

### Response

None, program terminates itself.

## UDS0334

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0334 UDSDUMP DUMPFILE NOT COMPLETE, EDIT PARAMS WILL BE IGNORED (&00) (&01) (&02)

### Meaning

The file contains only part of the dump. This is output restructured;
EDIT parameters have no meaning and are ignored if entered.

### Response

Enter EDIT command without parameters, then END.

## UDS0335

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0335 UDSDUMP COMMAND '(&00)' IN ERROR (&01) (&02)

### Meaning

The command entered or at least one of the command parameters is unknown
and has been rejected.
(&00): character string entered.

### Response

Enter correct command.

## UDS0336

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0336 UDSDUMP NO EDIT CMD PRECEDING END CMD. STOP WITHOUT ANY EDITING (&00) (&01) (&02)

### Meaning

END was entered without a preceding EDIT command. No editing or output to
SYSLST occurs.

### Response

If this was not intentional, repeat UDSDUMP run and enter EDIT before END.

## UDS0337

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0337 UDSDUMP EDITING STARTED, PLEASE WAIT (&00) (&01) (&02)

### Meaning

END has been entered after at least one EDIT command. Editing and output
of
the secondary dump to SYSLST begins. The dialog user no longer has
control.

## UDS0338

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0338 UDSDUMP NORMAL END (&00) (&01) (&02)

### Meaning

The secondary dump has been output to SYSLST. UDSDUMP terminates itself.

## UDS0339

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0339 UDSDUMP PROGRAM ERROR (&00) (&01) (&02)

### Meaning

A branch has been made to the EXIT routine corresponding to the PROCHK,
error or ABEND event that occurred.
(&00): P error weight; readable decimal if PROCHK or error='ABEND'
if ABEND.

### Response

None. UDSDUMP terminates itself. The file is closed.

## UDS0340

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0340 UDS ABNORMAL END (&00) (&01) (&02)

### Meaning

UDSDUMP terminates itself due to the error indicated in the previous
message

## UDS0341

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0341 UDS DUMPFILE WRITTEN: (&00) (&01) (&02)

### Meaning

A primary dump file has been created.
(&00): file name.

## UDS0342

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0342 UDS USER ERROR: (&00) IS NOT SUPPORTED BY THE GIVEN VERSION OF UDS (&01) (&02).

### Meaning

The function selected (&00) is not supported in this version.
This message is issued in the following instances:
(1) DML statements have been sent from an XS-compatible application
program to a non-XS-compatible UDS/SQL module. All UDS versions
< UDS V5.1, UDS V5.1 with linked-in DBH and UDS/SQL V1.0 are not
commpatible.
(2) UDS V5.1 was started under a BS2000 version < 9.0 or on hardware
that is not XS-compatible.
(3) SQL statements are not permitted under UDS version =< V5.1 or with
the linked-in DBH of UDS/SQL V1.0.

### Response

(1) Ensure that the jobs are only in AMODE=24 or UDS V5.1 is available.
(2) Install BS2000 version >= V9.0 and XS hardware.
(3) Make UDS/SQL V1.0 available for SQL statements or use the
independent DBH.

## UDS0343

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0343 UDS ERROR (&00) ON WRITE OF DUMPFILE (&01) (&02)

### Meaning

An error occurred during writing in the primary dump file. A BS2000
user dump was generated instead of a UDS/SQL dump.
(&00): readable DMS or P error code or 'UNRC' for parameter error.

### Response

None; PDUMP call is executed.

## UDS0344

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0344 UDS USER ERROR: DSCEXT HAS AN INCORRECT RMODE (&00) (&01) (&02).

### Meaning

The position of the DSCEXT routine in the address space is not compatible
with the AMODE used in the DML statement.

### Response

Make the application program and the DSCEXT routine compatible.

## UDS0345

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0345 UDS USER ERROR: C.UDSSUB IS NOT SHARABLE (&00) (&01) (&02)

### Meaning

UDS/SQL administration error: If a userid other than that under which
UDS/SQL was started is specified in the SET-TASKLIB command, the
C.UDSSUB phase is loaded from this userid. C.UDSSUB must be declared
shareable.

### Response

Make C.UDSSUB shareable in the TASKLIB id.

## UDS0346

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0346 UDS USER ERROR: C.UDSSUB MISSING (&00) (&01) (&02)

### Meaning

UDS/SQL administration error: C.UDSSUB is not found in the userid under
which UDS/SQL was started or, if a SET-TASKLIB command with another
userid was specified, is not under this userid.

### Response

Either assign C.UDSSUB to the userid under which UDS/SQL was started
or, if another userid was specified for SET-TASKLIB, assign it to this
userid.

## UDS0347

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0347 UDS ADMINISTRATION: (&00) (&01) (&02)

### Meaning

Change of status or error in UDS/SQL DCAM administration.
(&00): further information see manual 'UDS/SQL Messages'.

### Response

Depends on information in (&00). See manual 'UDS/SQL Messages'.

## UDS0348

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0348 UDS CANCEL ALL TRANSACTIONS STARTED (&00) (&01) (&02)

### Meaning

Abortion of all UDS/SQL transactions has been initiated due to an
administrator command or an internal UDS/SQL error.

## UDS0349

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0349 UDS USER ERROR: (&00)-CALLS ARE ONLY POSSIBLE IN AMODE=24 (&01) (&02).

### Meaning

An attempt has been made to make calls to the linked-in DBH or KDBS calls
(indicated by (&00)) in AMODE=31.

### Response

Correct application program.

## UDS0350

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0350 UDS SC/DSA ERROR (&00) (&01) (&02)

### Meaning

Exceptional circumstance or error in one of the UDS/SQL subcontrol (SC)
subsystems or DSA. The meaning of the message depends on the specified
ERRCODE. 'DMS' (if present) means that a corresponding error code or
another secondary return code is output.

### Response

According to error code (&00).

## UDS0351

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0351 UDS NORMAL SESSION TERMINATION INITIATED (&00) (&01) (&02)

### Meaning

Due to the preceding error, the UDS/SQL DBH has initiated a premature but
normal session end. (Corresponds to '/SEND-MESSAGE CLOSE RUN-UNITS')

### Response

Start new session after error has been removed.

## UDS0352

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0352 UDS FOLLOWING REACTION AVOIDS DAMAGE TO DATABASE (&00) (&01) (&02)

### Meaning

In order to avoid compromising the integrity of the data resources due to
the preceding error, UDS/SQL enforces session abort
(corresponds to '/SEND-MESSGE %TERM').

### Response

Correct error, then START-UDS.

## UDS0353

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0353 UDS CONSISTENCY ERROR. (&00) INCONSISTENT. (&01) (&02)

### Meaning

UDS/SQL has detected an error in the consistency of data of the file
(&00).
(&00): see manual 'UDS/SQL Messages'.

### Response

Reverse any illegal user manipulation or operating errors performed on
the file; otherwise DIAG.

## UDS0354

Destination: USER-TASK, CONSOLE Routing code: U Weight: 99

Warranty : NO

UDS0354 UDS ALOG CHECKPOINT FOR (&00) (&01) (&02)

### Meaning

An ALOG checkpoint for the indicated data base is to be written. The
results and the values generated by this operation are given in a
continuation line.

### Response

Depends on the continuation line. See manual 'UDS/SQL Messages'.

## UDS0355

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0355 UDS BACKOUT CHECKPOINT FOR (&00) (&01) (&02)

### Meaning

A start or end backout checkpoint was written for the indicated
configuration. In the case of a start checkpoint, the message also
gives the timestamp ('TIMESTAMP IS...') as well as the checkpoint IDs
of the participating data bases (in subsequent message lines).

## UDS0356

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0356 UDS EXECUTION OF ORDERS FOR (&00) (&01) (&02)

### Meaning

For the indicated configuration, execution of the orders from the user
via DAL and from UDS/SQL error handling was
a) INITIATED or
b) TERMINATED.

## UDS0357

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0357 RLOG RESERVE IS USED FOR CONFIGURATION (&00) (&01) (&02)

### Meaning

The previously indicated error causes UDS/SQL to write the original or
duplicate RLOG to the RESERVE data medium.

### Response

Remove cause of error or assign a new data medium in place of the failed
volume using MODIFY LOG (or LOG-2).

## UDS0358

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0358 UDS DROP OF (&00) (&01) (&02)

### Meaning

UDS/SQL indicates the result of a drop request for a realm.

### Response

If necessary, remove indicated error; repeat drop request.

## UDS0359

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0359 UDS (&00) BECAME UNPROCESSABLE (&01) (&02)

### Meaning

UDS/SQL has locked the entire configuration or the given data base against
access.
(&00): configuration name or data base name.

### Response

Check if the situation can be remedied by repair.

## UDS0360

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0360 UDS FATAL FILE FAILURE: (&00) (&01) (&02)

### Meaning

A fatal error occurred in the UDS/SQL file entered. The cause is indicated
in (&00).

### Response

See meaning.

## UDS0361

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0361 UDS BACKOUT FILE (&00) CLOSED (&01) (&02)

### Meaning

The indicated backout file has been closed by UDS and released.

## UDS0362

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0362 UDS BSECURE EXCLUSIVE RIGHTS ON DB: (&00) (&01) (&02)

### Meaning

A BSECURE exclusive right was dicovered for the UDS-CATALOG accessed by
the DBH. The DBH access is therefore not possible.

### Response

Wait for normal termination of the BSECURE run, then RESTART.

## UDS0363

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0363 UDS SLF INCONSISTENT. ERRCODE: (&00) (&01) (&02)

### Meaning

The indicated inconsistency was discovered during SLF processing.
(&00) may contain following error codes:
(1) SLF-BCI-ERROR Error in the block control info for the SLF page
(2) SLF-BOT-PAGE-ERROR Error in bottom page of the SLF file
(3) SLF-FORMAT-ERROR The page format of the SLF file is incompatible
with the UDS/SQL version

### Response

to (1) and
to (2) Remove illegal user changes to SLF file; after session interrupt,
a defective
SLF file must be repaired before restart or deleted. After normal
session end,
it is sufficient to delete the SLF file (/DELETE-FILE command).
RESTART; Start a new session with any data base configuration, if
required.
to (3) If the concerned SLF file was created in a configuration with an
earlier
UDS/SQL version, then a session restart with this file is impossible.
You may start the session with a different configuration name or
delete
the SLF file (paying attention to password).

## UDS0364

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0364 UDS CATALOG INCONSISTENT. ERRCODE: (&00) (&01) (&02)

### Meaning

The indicated inconsistency was detected during processing of the catalog
file. Error code:
CAT_BCI_ERROR: Error in the block control info for the CAT block.
CAT_BOT_PAGE_ERROR: Error in bottom page of the CAT block.
CAT_RLM_ENTRY_ERROR: Error during consistency checking of the current
catalog realm entry.
CAT_ACC_CONTROL_ERROR: Error in access mode for the data base concerned.
Cause: DBH programming error or user manipulation.

### Response

DIAG or reverse user manipulation.

## UDS0365

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0365 LAYOUT VERSION ERROR: (&00) (&01) (&02)

### Meaning

The specified data base file cannot be processed by the DBH in use
due to layout differences.
(&00): file name and layout version string of this file.

### Response

Use correct DBH version or migrate the data base to the
corresponding layout version.

## UDS0366

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0366 UDS SESSION RESTART WITH CHANGED VERSION. CORRECT VERSION IS: (&00) (&01) (&02)

### Meaning

The same UDS/SQL version must be used at session restart as at session
begin.

### Response

Repeat restart with correct UDS/SQL version.

## UDS0367

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0367 UDS USER ERROR: NUMBER OF REALMS FOR (&00) EXCEEDING UPPER LIMITS (&01) (&02)

### Meaning

No more than 255 realms may be used in the entire configuration.

### Response

Check the data base structure.

## UDS0368

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0368 UDS USER ERROR: DBDIR OF (&00) NOT AVAILABLE (&01) (&02)

### Meaning

DBDIR of the specified data base is not available. Possible causes:
HW error / DBDIR disconnected / BSECURE run active.

### Response

Make DBDIR available:
Either REPAIR-RLM,
or connect,
or wait for end of BSECURE run.

## UDS0369

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0369 UDS BACKOUT LOGGING (&00) (&01) (&02)

### Meaning

At a session restart, UDS/SQL has detected that a previously failed
backout
file:
a) (&00)= SWITCHED OFF: ... has not been replaced by an unimpaired new
backout file. Backout logging thus remains switched off.
b) (&00)= RESUMED: ... has been replaced by an unimpaired new backout
file. Backout logging is thus resumed.

## UDS0370

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0370 UDS USER ERROR: PP LOG MISSING WHEN BACKOUT LOGGING IS USED. (&00) (&01) (&02)

### Meaning

Backout logging is only permitted and possible in conjunction with RLOG
logging.

### Response

Repeat initialization with RLOG logging (correct PP FILE if necessary).

## UDS0371

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0371 UDS USER ERROR: NUMBER OF PASSWORDS EXCEEDING UPPER LIMIT: (&00) (&01) (&02)

### Meaning

More than 100 passwords have been specified.

### Response

Correct PP FILE, if necessary.

## UDS0372

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0372 UDS RLOG FILE (&00) MAY BE REPAIRED NOW (&01) (&02)

### Meaning

An RLOG file has been marked defective. The DBH can start repairing the
defect.

### Response

The messsag serves only as a warning.

## UDS0373

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0373 UDS ADMINISTRATION OF DISTRIBUTION IMPOSSIBLE DUE TO PREVIOUS ERRORS (&00) (&01) (&02)

### Meaning

Due to previous errors, processing of UDS-D DAL commands is not possible.
Distributed DML processing is not affected.

### Response

If DAL commands have to be transferred to UDS-D, the UDS/SQL session has
to be terminated and started again.

## UDS0374

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0374 UDSCODE STARTING (&00) (&01) (&02)

### Meaning

The C.UDSCODE utility routine has been started

## UDS0375

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0375 UDSCODE COMMON MEMORY POOL (&00) CREATED (&01) (&02)

### Meaning

A common memory pool has been created for UDS/SQL coding.
(&00): pool name

## UDS0376

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0376 UDSCODE NORMAL END (&00) (&01) (&02)

### Meaning

The C.UDSCODE utility routine has been terminated normally.

## UDS0377

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0377 UDSCODE VERSION DIFFERENCE FOR (&00) (&01) (&02)

### Meaning

C.UDSCODE has detected that the version of the component indicated in
(&00) is incompatible with the version of the other components.

### Response

Check the contents of the UDS.MODLIB and the library assigned by means
of TASKLIB.
- Create consistent module library.
- Restart program.

## UDS0378

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0378 UDSCODE MODULE (&00) NOT FOUND (&01) (&02)

### Meaning

The module indicated in (&00) has not been found.

### Response

Check contents of the UDS.MODLIB and module libraries assigned by means of
TASKLIB.
- Create consistent module library.
- Restart program.

## UDS0379

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0379 UDSCODE COMMON MEMORY POOL (&00) ALREADY EXISTS (&01) (&02)

### Meaning

A common memory pool for UDS/SQL coding already exists. The C.UDSCODE
utility routine has been linked to this pool.
(&00): name of the pool.
(&02): name of the program, which has created the pool.

## UDS0380

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0380 UDSCODE UNRECOVERABLE ERROR (&00) (&01) (&02)

### Meaning

An irrecoverable error has occurred in the C.UDSCODE utility. (&00) gives
the cause of the error, the return code and, in the case of a P error,
the address at which it occurred.
(&00): see manual 'UDS/SQL messages'.

### Response

Depends on error information in (&00). See manual 'UDS/SQL Messages'.

## UDS0381

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0381 UDSCODE ABNORMAL END (&00) (&01) (&02)

### Meaning

C.UDSCODE terminated abnormally.

### Response

This message was preceded by a message giving more details on the cause
of the error. Refer to preceding message for action.

## UDS0382

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0382 UDSCODE USER ERROR (&00) (&01) (&02)

### Meaning

The error given in (&00) was detected in C.UDSCODE.

### Response

Correct error given in (&00) (e.g. by entering correct SET-FILE-LINK
command with LINK-NAME=UDSCODE); start correct utility when (&00)=(DBH?)

## UDS0383

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0383 UDSCODE COMMAND REJECTED (&00) (&01) (&02)

### Meaning

An incorrect SEND-MESSAGE command was entered. (&00) containts the
command.

### Response

Enter correct SEND-MESSAGE command.

## UDS0384

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0384 UDS ERROR ON CODEPOOL (&00) (&01) (&02)

### Meaning

An error described in (&00) occurred at memory pool creation for the
UDS/SQL coding. UDS/SQL attempts to load the coding to class 6 memory.

### Response

If coding is required for processing in the common memory pool, the
UDS/SQL session must be terminated. Correct error indicated under (&00)
and restart session. If required, create common memory pool beforehand
using the C.UDSCODE utility routine.

## UDS0385

Destination: USER-TASK, CONSOLE Routing code: U Weight: 99

Warranty : NO

UDS0385 UDS UNRECOVERABLE ERROR ON CODEPOOL (&00) (&01) (&02)

### Meaning

The error described under (&00) has occurred at common memory pool
creation by the UDS/SQL master task. The UDS/SQL session is terminated
abnormally.

### Response

Depends on error information in (&00). See manual 'UDS/SQL messages'.

## UDS0386

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0386 UDS SESSION CONTINUES (&00) (&01) (&02)

### Meaning

The UDS/SQL session is continued regardless of the situation described in
the preceding message.

### Response

If the situation described in the preceding message is not desired by the
administrator he or she has to terminated the session, correct the error
and restart the session.

## UDS0387

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0387 UDSCODE COMMAND ACCEPTED (&00) (&01) (&02)

### Meaning

The SEND-MESSAGE command entered was accepted.
(&00) contains the file name defined with LINK-NAME=UDSCODE.

## UDS0388

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0388 FILE (&00) INDICATES WARMSTART POSSIBLE FOR FOLLOWING DB(S) (&01) (&02)

### Meaning

The indicated RLOG file still contains the entries of data bases for which
a warm start can be performed.

## UDS0389

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0389 UDS WARNING: INFORMATION IN STATUS FILE WILL POSSIBLY BE LOST (&00) (&01) (&02)

### Meaning

Information which may be required for a warm start may be lost in the
status file. The information refers to the RLOG files output under (&00)
in the format '*RLOG.<time>.*'.

### Response

If the RLOG files indicated under (&00) still exist, a warm start should
be performed for them.

## UDS0390

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0390 UDS WARNING: PP (&00) NOT SUITABLE FOR THIS SESSION; WILL BE CHANGED BY UDS (&01) (&02)

### Meaning

The load parameter indicated in (&00) contains a value which cannot be
used in the current session. In some cases continuation message U307
indicates the value substituted by UDS/SQL. Otherwise the value used
can be displayed using DISPLAY PP.

### Response

The UDS/SQL session is continued with a default value substituted by
UDS/SQL. If the administrator wishes to use a value which is closer to
the one previously entered, this can be done by trial and error or by
increasing the virtual address space or reducing PP TRANSACTION.

## UDS0391

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0391 UDS ERROR ENABLING TRANSFER POOL FOR UDS-D (&00) (&01) (&02)

### Meaning

UDS/SQL was not able to connect to the transfer pool for UDS-D. (&00)
gives the name of the transfer pool. An additional return code originates
from ENAMP-SVC. Otherwise, there is probably an internal UDS/SQL error.

### Response

If the ENAMP-SVC return code indicates that the size of the virtual
address is too small to hold the pool, the space must either be increased
or UDS/SQL restarted with smaller values defined for PP BUFFER, PP
SERVERTASK and PP TRANSACTION. If not, there is probably an internal
UDS/SQL
error in which case a dump is required.

## UDS0392

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0392 UDS-D NOT AVAILABLE DURING THIS SESSION (&00) (&01) (&02)

### Meaning

Distributed processing is not possible in this session, due either to
PP DISTRIBUTION=NO or an error during initialization of distribution or
processing, leading to termination of the distributed function.

### Response

Terminate UDS/SQL session and restart with correct PP DISTRIBUTION entry
if applicable.

## UDS0393

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0393 UDS ROLLS BACK ALL TRANSACTIONS CONCERNED (&00) (&01) (&02)

### Meaning

All transactions impeding operations required by the administrator or the
system are rolled back.

## UDS0394

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0394 UDS TABLES INCONSISTENT DUE TO ABNORMAL TERMINATION OF A USERTASK (&00) (&01) (&02)

### Meaning

The UDS/SQL tables have become inconsistent due to uncontrolled
termination of a user task. The UDS/SQL session cannot be continued.

### Response

Restart UDS/SQL. If the warm start is rejected for one (or more) data
base(s) due to open transactions which have been put in the PTC state
by UTM, warm start the corresponding UTM application first, then repeat
warm start for the rejected data base(s).

## UDS0395

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0395 UDS ERROR (&00) (&01) (&02)

### Meaning

Internal error detected by the component for communication between the
master task and UDSCT. (&00) contains diagnostic information
relevant for further processing. UDS-D can no longer be administered.

### Response

If UDS-D is to be administered, terminate and restart UDS/SQL session.

## UDS0396

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0396 FOLLOWING RLOG FILE IS RETAINED FOR POSSIBLE STATUS QUERIES FROM UDS-D (&00) (&01) (&02)

### Meaning

The RLOG file may be required for UDS-D status queries and is therefore
not
deleted.

### Response

The RLOG file can be deleted once no transactions in the entire UDS-D
network are in the PTC state.

## UDS0397

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0397 UDS USER ERROR: LOADED DBH DOES NOT PROCESS SQL-DML (&00) (&01) (&02).

### Meaning

The loaded DBH cannot process SQL DML.

### Response

Terminate the DBH and load an SQL-compatible DBH.

## UDS0398

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0398 UDS WARNING: ENTRY USERSTIX NOT SUPPORTED IN FUTURE VERSIONS OF UDS (&00) (&01) (&02)

### Meaning

The option of using the UDS/SQL STXIT handling routine to call a user
STXIT routine named USERSTIX in the user task is not available in future
version of UDS/SQL. Instead, the options available under the STXIT
parallelism concept of BS2000 should be used.

## UDS0399

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0399 CHANGING OF AMODE IN A LINKEDIN-SESSION IS NOT ALLOWED (&00) (&01) (&02)

### Meaning

In a LINKEDIN-Session all the DML-orders must be sent to the DBH in the
same addressing mode.

## UDS0400

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0400 UDS ADMINISTRATION ERROR: MASTER TASK NOT BATCH TASK (&00) (&01) (&02)

### Meaning

The master task was not started as a batch task although the
security level is 'F2' or 'F2-EXCEPT'.

### Response

Start master task as batch, or change security level to 'NO'.

## UDS0402

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0402 UDS ADMINISTRATION ERROR: SECOS NOT AVAILABLE (&00) (&01) (&02)

### Meaning

The SECOS subsystem is not available in BS2000 although the
security level is 'F2' or 'F2-EXCEPT'.
(&00) missing SECOS function

### Response

Make available SECOS subsystem, or change security level to 'NO'.

## UDS0403

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0403 UDS WARNING: UDS-D NOT PERMITTED (&00) (&01) (&02)

### Meaning

PP DISTRIBUTION=STANDBY/START and UDS-D is not permitted under the
current security level.
PP DISTRIBUTION=NO is assumed.

## UDS0404

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0404 UDS ERROR: (&00) ON SAT CALL (&01) (&02)

### Meaning

(&00): SAT return code, or 'PRIV' if BS2000 user ID has no
SECOLTP privilege

### Response

If (&00)=PRIV, start master task under BS2000 user ID with SECOLTP
privilege, or change security level to 'NO'.
Otherwise, notify BS2000 security officer.

## UDS0405

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0405 UDS USER ERROR: TIAM APPLICATIONS NOT PERMITTED IN THIS CONFIGURATION (&00) (&01) (&02)

### Meaning

A TIAM application with SECOLTP privilege is trying to connect to this
configuration, although it runs under security level 'F2' or 'F2-EXCEPT'
without TIAM.

### Response

Notify UDS/SQL administrator.

## UDS0407

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0407 UDS WARNING: LOCAL ADMINISTRATION NOT PERMITTED (&00) (&01) (&02)

### Meaning

PP ADM=LOCAL and security level 'F2' or 'F2-EXCEPT' are not
compatible.
PP ADM=REMOTE is assumed.

### Response

Administration via UDSADM.

## UDS0408

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0408 UDS ADMINISTRATION ERROR: DAL COMMAND (&00) VIA /SEND-MSG NOT PERMITTED (&01) (&02)

### Meaning

The current security level is 'F2' or 'F2-EXCEPT'. The DAL command
entered via /SEND-MSG failed to terminate the session or UDS-D.

### Response

Enter DAL command via administration program, or terminate session.

## UDS0409

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0409 UDS SYSTEM ERROR: TRANSFER CONTAINER MANAGEMENT ERROR (&00) (&01) (&02)

### Meaning

The session is terminated.

### Response

Take Dump.
Restart UDS/SQL.

## UDS0410

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0410 UDS APPLICATION TERMINATED WITH (&00) DMLS (&01) (&02)

### Meaning

The application program ended.
(&00): Number of executed DMLs in the application program

## UDS0500

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0500 UDSMON COMMAND ACCEPTED (&00) (&01) (&02)

## UDS0501

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0501 UDSMON ENTER START PARAMETER OR 'HELP' (&00) (&01) (&02)

## UDS0502

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0502 UDSMON NORMAL TERMINATION (&00) (&01) (&02)

## UDS0503

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0503 UDSMON INVALID CONFIGURATION NAME OR UDS NOT LOADED (&00) (&01) (&02)

### Meaning

An incorrect configuration name has been entered or no UDS/SQL has been
loaded with this configuration.
In batch mode, the monitor terminates with dump.

### Response

Enter configuration name again; wait for UDS/SQL loading, if necessary.

## UDS0504

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0504 UDSMON SYSTEM ERROR: CONNECTING TO DISTRIBUTION POOL UNSUCCESSFUL (&00) (&01) (&02)

### Meaning

An error occurred during connection to the distribution pool. The monitor
terminates.

### Response

Take dump.

## UDS0505

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0505 UDSMON NO LONGER WAITS FOR UDS INITIALIZATION (&00) (&01) (&02)

### Meaning

The monitor has been waiting for the end of UDS/SQL initialization for
five minutes. The monitor terminates with dump.

### Response

Wait for SYSTEM READY then restart UDS/SQL monitor.

## UDS0506

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0506 UDSMON UDS-D NOT LOADED. NO UDS-D MASKS WILL BE DISPLAYED (&00) (&01) (&02)

## UDS0507

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0507 UDSMON ENTER ANY CHARACTER TO CONTINUE PROGRAM (&00) (&01) (&02)

### Meaning

Enter any character and DUE to continue monitor processing.

## UDS0508

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0508 UDSMON OUTPUT MEDIUM INCORRECT. OUTPUT MEDIUM CHANGED TO LIST (L) (&00) (&01) (&02)

### Meaning

An illegal output medium was selected in batch mode. The output medium has
been changed to LIST (output to printer).

## UDS0509

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0509 UDSMON CONFNAME COMMAND MISSING (&00) (&01) (&02)

### Meaning

The CONFNAME=<conf-name> command must be entered before the START command.
In batch mode, the monitor terminates.

### Response

Enter CONFNAM and repeat START.

## UDS0510

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0510 UDSMON SEND-MSG COMMAND NOT POSSIBLE AT PRESENT. RETRY COMMAND LATER (&00) (&01) (&02)

### Meaning

An SEND-MSG command is already awaiting processing.

## UDS0511

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0511 UDSMON COMMAND NOT ALLOWED IN PREDIALOG (&00) (&01) (&02)

### Meaning

If monitor terminates if the command is entered in batch mode.

## UDS0512

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0512 UDSMON COMMAND ONLY ALLOWED IN PREDIALOG (&00) (&01) (&02)

## UDS0513

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0513 UDSMON COMMAND NOT ALLOWED FROM CONSOLE (&00) (&01) (&02)

## UDS0514

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0514 UDSMON OPEN ERROR ON MONITOR FILE (&00) (&01) (&02).

### Meaning

The indicated error occurred during opening of the monitor file.
Output to the file has been terminated.
(&00): file name
(&01):
(&02): DMS error code.

### Response

Check file and restart output to the file.

## UDS0515

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0515 UDSMON CLOSE ERROR ON MONITOR FILE (&00) (&01) (&02).

### Meaning

An error occurred during closing of the monitor file.
(&00): file name
(&01):
(&02): DMS error code.

### Response

Check file and repair if necessary with the BS2000 /VERIFY command or the
SDF command /REPAIR-DISK-FILES.

## UDS0516

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0516 UDSMON WRITE ERROR ON MONITOR FILE (&00) (&01) (&02)

### Meaning

The indicated error occurred during writing to the monitor file. Output to
the file has been terminated.
(&00): file name
(&01):
(&02): DMS error code.

### Response

Check file; restart output to the file.

## UDS0517

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0517 UDSMON ERROR WHEN CREATING MONITOR FILE (&00) (&01) (&02)

### Meaning

The indicated error occurred during cataloging of the monitor file.
No output is made to the file.
(&00): file name
(&01):
(&02): DMS error code.

### Response

Check file and correct, if necessary; restart output of file.

## UDS0518

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0518 UDSMON USER ERROR: UNKNOWN COMMAND. (&00) (&01) (&02)

### Meaning

The character string entered is not a monitor command. If the error
occurred in the predialog in batch mode, the monitor terminates.

### Response

Correct and repeat command.

## UDS0519

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0519 UDSMON USER ERROR: INTERVAL FOR OUTPUT MEDIUM NOT CORRECT (&00) (&01) (&02)

### Meaning

Illegal monitor time interval. If the error occurs in the predialog in
batch mode, the monitor terminates.

### Response

Repeat entry with corrected parameters.

## UDS0520

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0520 UDSMON USER ERROR: ILLEGAL MONITOR OUTPUT MEDIUM (&00) (&01) (&02)

### Meaning

If the error occurs in the predialog in batch mode, the monitor
terminates.

### Response

Repeat entry with corrected parameters.

## UDS0521

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0521 UDSMON USER ERROR: MASK TYPE NOT CORRECT (&00) (&01) (&02)

### Meaning

If the error occurs in the predialog in batch mode, the monitor
terminates.

### Response

Repeat entry with corrected parameters.

## UDS0522

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0522 UDSMON MACRO ERROR (&00) (&01) (&02)

### Meaning

An error occurred during macro call (&00). The monitor terminates.
(&00): macro name
(&01):
(&02): DMS error code.

## UDS0523

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0523 UDSMON SYSTEM ERROR: STCK NOT SUCCESSFUL, NO TIMER INTERVAL POSSIBLE (&00) (&01) (&02)

### Meaning

No interval could be formed because the timer is not available. The
monitor
terminates.

## UDS0524

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0524 UDSMON SYSTEM ERROR: PROGRAM ERROR (&00) (&01) (&02)

### Meaning

Program error in the monitor. The monitor terminates.
(&00): error weight
(&01):
(&02): error address.

### Response

Take dump.

## UDS0525

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0525 UDSMON ABNORMALLY TERMINATED (&00) (&01) (&02)

### Meaning

The monitor has terminated due to an error.

### Response

Restart monitor.

## UDS0526

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0526 UDS NORMALLY TERMINATED. UDSMON TERMINATION INITIATED (&00) (&01) (&02)

## UDS0527

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0527 UDS ABNORMALLY TERMINATED. UDSMON TERMINATION INITIATED (&00) (&01) (&02)

### Meaning

UDS/SQL has been terminated due to an error - monitor termination has been
initiated.

## UDS0528

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0528 UDSMON NO TRACE ACTIVE, COMMAND IGNORED (&00) (&01) (&02)

### Meaning

No UDS/SQL trace is active. The command used to terminate the trace has
been ignored.

## UDS0529

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0529 UDSMON CLOSE OF TRACE FILES STILL ACTIVE. COMMAND REJECTED (&00) (&01) (&02)

### Meaning

The trace files are already being closed.

## UDS0530

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0530 UDSMON SAMPLING STARTED (&00) (&01) (&02)

## UDS0531

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0531 UDSMON NOT PERMITTED UNDER CURRENT SECURITY LEVEL (&00) (&01) (&02)

### Meaning

The UDS/SQL monitor cannot run under the current security level.
UDSMON terminates.

## UDS0532

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0532 UDSMON VERSION DOES NOT MATCH UDS VERSION (&00) (&01) (&02)

### Meaning

The UDS/SQL version differs from the UDS/SQL monitor version.
UDSMON terminates.

## UDS0533

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0533 UDSMON USER ERROR: RUNTIME PARAMETER OUTSIDE PERMITTED RANGE (&00) (&01) (&02)

### Meaning

An invalid value was specified for the RUNTIME paramater.
In batch mode, UDSMON terminates.

### Response

Correct and repeat RUNTIME command.

## UDS0534

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0534 UDSMON INTERNAL OVERFLOW IN COUNTER (&00) (&01) (&02)

### Meaning

An internal overflow occurred in counter (&00).
The value given by the counter does not correspond to the actual value.

## UDS0535

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0535 UDSMON THE BS2000 VERSION USED DOESN'T SUPPORT THE TRANSFER OF MONITOR DATA TO OPENSM2 (&00) (&01) (&02)

### Meaning

The BS2000 version used doesn't support the transfer of monitor data to
openSM2. As of BS2000/OSD V8,
this transfer is supported.

## UDS0536

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0536 UDSMON UDS-SQL MEASUREMENT PROGRAM IN SM2 NOT YET STARTED (&00) (&01) (&02)

### Meaning

The UDS-SQL measurement program in SM2 is not yet started.

### Response

Start measurement program with SM2 command START-MEASUREMENT-PROGRAM
TYPE=*UDS-SQL.

## UDS0537

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0537 UDSMON SM2 GATHERER TASK NOT ACTIVE (&00) (&01) (&02)

### Meaning

The SM2 gatherer task is not active.

### Response

Activate gatherer task in SM2; execute
ADD MEDIUM S,... in UDS/SQL monitor

## UDS0538

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0538 UDSMON SUBSYSTEM SM2 NOT ACTIVE (&00) (&01) (&02)

### Meaning

The subsystem SM2 is not active.

### Response

Start subsystem SM2 and start measurement program UDS/SQL;
execute ADD MEDIUM S,... in UDS/SQL monitor

## UDS0600

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0600 FASTPAM NON RESIDENT MEMORY (&00) (&01) (&02)

### Meaning

A resident memory could not be used.
The user system can continue to operate. However,
FASTPAM performance is affected adversely.
A more detailed specification is contained in (&00).
(&00): see manual 'UDS/SQL Messages'.

### Response

Depends on (&00). See manual 'UDS/SQL Messages'.

## UDS0700

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0700 UDS RESOURCE ERROR (&00) (&01) (&02)

### Meaning

An error occurred in one of the UDS/SQL resources (e.g. UDS/SQL file,
main memory). (&00) (&01) (&02) identifies the error.
A more detailed specification may be contained in
- a symbolic error code
- a DMS return code or a secondary return code
- the name of the file involved
- the PAM block number of the file block concerned.
The possible reactions of UDS/SQL to this error which are relevant
for the user are described below.
(&00): see manual 'UDS/SQL Messages'.

### Response

Depends on error code (&00). See manual 'UDS/SQL Messages'.

## UDS0701

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0701 UDS SUBSYSTEM ERROR (&00) (&01) (&02)

### Meaning

A programming error has occurred at the interface of the UDS/SQL DBH with
the subsystem SUBCONTROL or DSA. In addition to a dump, short diagnostic
information is output containing the address and the first 12 bytes of the
parameter list.

### Response

DIAG.

## UDS0702

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0702 UDS PARTIAL FAILURE OF FILE (&00) (&01) (&02)

### Meaning

UDS/SQL cannot access the indicated file due to the previously reported
error. No more updates are performed on this file. UDS/SQL, however,
continues working with the existing unimpaired duplicate. The file
failure is not (yet) critical because no data has been lost.

### Response

Take repair measures according to file type. See manual
'UDS/SQL Messages'.

## UDS0703

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0703 UDS TOTAL FAILURE OF FILE (&00) (&01) (&02)

### Meaning

UDS/SQL cannot access the indicated file due to the recently reported
error. An unimpaired duplicate of this file does not exist (any longer).
The file failure must therefore be considered critical.
(&00): file name (see manual 'UDS/SQL Messages').

### Response

Take recovery measures (dependent of file type). See manual
'UDS/SQL Messages'.

## UDS0704

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0704 UDS DATABASE (&00) IS MARKED DEFECTIVE (&01) (&02)

### Meaning

The indicated data base has become irrecoverably due to the preceding
error.

### Response

RESET-DB.

## UDS0705

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0705 UDS USER ERROR: RESTART WITH UDS VERSION (&00) ONLY. (&01) (&02)

### Meaning

The UDS/SQL version used for restart must be identical to that used for
session start.

### Response

Repeat restart with UDS/SQL version indicated.

## UDS0706

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0706 UDS USER ERROR: RESTART IN (&00)-SESSION ONLY. (&01) (&02)

### Meaning

The session type specified for restart (user/utility session) must be
identical to that specified for session start.

### Response

Repeat restart with session type indicated.

## UDS0707

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0707 UDS USER ERROR: RESTART WITH (&00)-UDS ONLY. (&01) (&02)

### Meaning

The DBH type (independent/linked-in) specified for restart must be
identical to that specified for session start.

### Response

Repeat restart with DBH type indicated.

## UDS0708

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0708 UDS USER ERROR: RESTART WITH UDS/SQL-(&00) ONLY. (&01) (&02)

### Meaning

The UDS/SQL variant (Master/Entry) specified for restart must be
identical to that specified for session start.

### Response

Repeat restart with UDS/SQL variant indicated.

## UDS0709

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0709 UDS SESSION RESTART: PROGRAM PARAMETERS WILL BE SKIPPED. (&00) (&01) (&02)

### Meaning

The indicated load parameters are ignored as they are not required for
restart.

### Response

Only PP END must be specified as the PPs saved in the SLF file are used.

## UDS0710

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0710 UDS PROGRAM PARAMETER '(&00)' (&01) (&02)

### Meaning

The load parameter indicated is invalid. (Passwords are given as 'S'). The
cause of the error is given in the continuation message.

### Response

See continuation message.

## UDS0711

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0711 UDS PROGRAM PARAMETER REJECTED: (&00) (&01) (&02)

### Meaning

The load parameter indicated is invalid.
(&00): see manual 'UDS/SQL Messages'.

### Response

Repeat entry with correct parameters.
Exceptions: The insert PROGRAM-PARAMETER UNKNOWN is used as a hint for
such load parameters that were valid in earlier UDS/SQL
versions,
but have been withdrawn in the current version. In this cases
correction is not nessecary.
If PP is missing or PP DBNAME is incorrect, the entire
initialization must be repeated using correct load parameters.

## UDS0712

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0712 UDS WARMSTART WITH RLOG FILE (&00) SUCCESSFUL FOR FOLLOWING DATABASE(S): (&01) (&02)

### Meaning

A successful warm start has been performed using the indicated RLOG file
on data bases listed. This means that any open transactions (including any
distributed transactions) have been completed and the data bases concerned
have been marked consistent (in keeping with the consistency aspect).

## UDS0713

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0713 UDS WARMSTART WITH RLOG FILE (&00) LEAVES FOLLOWING PTC TRANSACTIONS (&01) (&02)

### Meaning

The listed (distributed) transactions could not be released (for reasons
of
consistency) from the PTC state by means of a data base warm start using
the indicated RLOG file because information required from the partner
configurations was not available.
(&00): name of the RLOG file.

### Response

See continuation message.
UDS/SQL indicates which part is in control of the distribution.
1. If control is at another UDS/SQL configuration:
make this configuration accessible for consistency purposes.
2. If control is at UTM:
warm start the UTM applicaton involved.
The two scenarios are not mutually exclusive. In fact, several UDS/SQL
configurations and UTM applications may be involved. The data base can be
reconnected using the DAL command once all the required configurations and
applications have been made accessible.

## UDS0714

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0714 UDS: UTM (&00) PTC FOR FOLLOWING TA (&01) (&02)

### Meaning

A transaction distributed by UTM (also) is in the PTC state. The UTM
identification comprising DC application name, UTM user name and terminal
name is output.

### Response

Wait for UTM to resolve the PTC or take action to this effect.

## UDS0715

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0715 UDS TA (&00) IN STATE PTC (&01) (&02)

### Meaning

The (sub-)transaction with the local TA-ID (processor name, configuration
name, RLOG-ID, TA-ID) is in the PTC state.

### Response

Try to terminate the subtransactions involved in the same way. To this
end, UDS/SQL indicates its reaction and the subtransactions involved in
subsequent messages; or the state can be influenced by the administrator
via a primary subtransaction, in which case, the TA-ID of the primary
subtransaction is indicated in the following message.

## UDS0716

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0716 UDS THIS TRANSACTION IS STILL IN PTC DUE TO (&00) (&01) (&02)

### Meaning

This message gives the reason (using a short code) why the indicated
distributed transaction could not be released from the PTC state.

### Response

Depends on information in (&00). See manual 'UDS/SQL Messages'.

## UDS0717

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0717 UDS REACTION FOR THIS PTC TRANSACTION: (&00) (&01) (&02)

### Meaning

This message describes (via symbolic code) the UDS/SQL reaction to the
previously indicated PTC transaction.

### Response

Depends on information in (&00). See manual 'UDS/SQL Messages'.

## UDS0718

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0718 UDS: TA (&00) CONCERNED (&01) (&02)

### Meaning

The subtransaction with the indicated global TA-ID (processor name,
configuration name, RLOG-ID, TA-ID) is affected by the preceding reaction.

### Response

Try to terminate the affected transaction in the same way using DAL.
Inform the transaction user.

## UDS0719

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0719 UDS ENFORCES (&00) FOR ERROR HANDLING (&01) (&02)

### Meaning

The preceding error forces UDS/SQL error handling to initiate
disconnection or reassignment of files. (&00) give additional information
on the UDS/SQL reaction in DAL syntax. All transactions which would
delay the disconnection or reassignment are aborted.
(&00): see manual 'UDS/SQL Messages'.

### Response

If a data base or realm is disconnected: Reconnect, if desired, via DAL
once the cause of the disconnection has been removed.

## UDS0720

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0720 UDS ADD ORDER REJECTED: (&00) (&01) (&02)

### Meaning

The addition of a data base or file to the current session was
unsuccessful. The cause of the rejection is given in the symbolic code.
(&00): see manual 'UDS/SQL Messages'.

### Response

Remove cause of the rejection and retry addition.
Further information see manual 'UDS/SQL Messages'.

## UDS0721

Destination: USER-TASK, CONSOLE Routing code: U Weight: 99

Warranty : NO

UDS0721 FILE (&00) IS MARKED DEFECTIVE (&01) (&02)

### Meaning

Due to a previously indicated failure that has resulted in a loss of data,
UDS/SQL has marked the indicated file defective. As long as the defect
marker is in effect, UDS/SQL cannot use this file.
(&00): see manual 'UDS/SQL Messages'.

### Response

Repair defective realm/DBSTAT file or take into account the possible
effects of a gap in RLOG/AFIM or backout logging.
Further information see manual 'UDS/SQL Messages'.

## UDS0722

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0722 UDS ORDER (&00) IN EXECUTION (&01) (&02)

### Meaning

Execution of the indicated request has been completed or in case of
an ADD request has been commenced.
(&00): see manual 'UDS/SQL Messages'.

## UDS0723

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0723 UDS WARMSTART REJECTED FOR DATABASE (&00) (&01) (&02)

### Meaning

A warm start for the indicated data base was rejected. The cause of the
rejection is given in the symbolic code in the continuation line of this
message.

### Response

Remove indicated cause of warm start rejection. Meaning of symbolic code
see manual 'UDS/SQL Messages'.

## UDS0724

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0724 UDS INTERRUPTED ERROR HANDLING IS RESUMED (&00) (&01) (&02)

### Meaning

Error handling for a failed realm or AFIM file was interrupted due to a
session abort (or an abnormal data base disconnection). It is now resumed
as part of the connection procedure for this data base and completed.
See following UDS/SQL messages.

## UDS0725

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0725 UDS USER HASH ERROR (&00) (&01) (&02)

### Meaning

An error occurred at loading (LINK) or unloading (UNLOAD) of the
indicated hash module for the indicated data base.
- LINK error: Data base is disconnected.
- UNLOAD-UDSHASH error: Session is aborted.
- UNLOAD user hash module error: Error is ignored.

### Response

- LINK error: Remove cause, reconnect data base.
- UNLOAD-UDSHASH error: DIAG, START-UDS.
- UNLOAD user hash module error: Avoid addition of a data base whose user
hash module has the same name but different contents until session end
or
abort.

## UDS0726

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0726 UDS OPPOSITE ORDER IS CANCELLED. (&00) (&01) (&02)

### Meaning

Self-explanatory.

## UDS0727

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0727 UDS: PRIMARY TA CONCERNED :(&00) (&01) (&02)

### Meaning

This message refers to a previous message; it gives the global TA-ID of
the corresponding primary subtransaction for a subtransaction in the
PTC state.

### Response

Remove the cause indicated previously or change PP PTCSYNCH.

## UDS0728

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0728 LOAD PARAMETER PP LOG NOT CORRECTLY SPECIFIED. (&00) (&01) (&02)

### Meaning

The PP LOG load parameter has not been specified or has been
incorrectly specified. UDS/SQL aborts the DBH run.

### Response

Enter the PP LOG load parameter correctly in the load parameter file;
repeat UDS/SQL start.

## UDS0729

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0729 PP LOG AND PP LOG-2 IN CONFLICT. (&00) (&01) (&02)

### Meaning

There is no point entering the load parameter PP LOG-2 if PP LOG=NO
has been set. UDS/SQL aborts the DBH run.

### Response

Change PP LOG load parameter or PP LOG-2. Restart UDS/SQL start.

## UDS0730

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0730 PP LOG AND PP LOG-2 MUST BE DIFFERENT. (&00) (&01) (&02)

### Meaning

The data volumes specified for the RLOG file (PP LOG) and the duplicate
RLOG file (PP LOG-2) are not different.
If an error occurs with the RLOG file or the duplicate RLOG file and
the reserve volume (PP RESERVE) has to be used the volume specifications
for PP RESERVE and the RLOG file not affected by the error must differ.

### Response

Change load parameter PP LOG, PP LOG-2 or PP RESERVE. Restart UDS/SQL if
necessary or select new RLOG files (DAL command NEW RLOG).

## UDS0731

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0731 RESTART MUST USE (&00). (&01) (&02)

### Meaning

(&00): DBH WITH SQL or DBH WITHOUT SQL.
The same DBH variant (with SQL/without SQL) must be used at restart as at
session start.

### Response

Repeat restart with the indicated DBH variant.

## UDS0732

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0732 END OF TA (&00) (&01) (&02)

### Meaning

The indicated transaction in PTC state has been forcibly terminated.
Interconfiguration consistency in distributed processing may now be
compromised.
(&00): global TA-ID (processor name, configuration name, RLOG-ID, TA-ID)
as well as type of termination (COMMIT or ABORT).

## UDS0733

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0733 UDS ADMINISTRATION ERROR: DB (&00) CANNOT BE ATTACHED DUE TO HASH MODULE (&01) (&02)

### Meaning

A database with a user-defined hash module is to be attached to
this configuration although it runs under the security level of
'F2' or 'F2-EXCEPT' without hash.
(&00): DB name

### Response

If necessary, restart UDS/SQL session and change security level to
'F2-EXCEPT' with hash.

## UDS0734

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0734 ALOG RESERVE BEING USED FOR DB (&00) (&01) (&02)

### Meaning

Due to the previous error, UDS/SQL changes the ALOG file for database
(&00) to the reserve medium.

### Response

Remove error.

## UDS0735

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0735 GAP IN LOGGING FOR DB (&00) CAN BE PREVENTED BY WARM START (&01) (&02)

### Meaning

The previous ALOG overflow caused a gap in the logging for database
(&00); the gap can be remedied using a warm start.

### Response

Accomodate ALOG file expansion. If DMS code 0946 has been returned,
reorganize ALOG file (by copying). Then initiate DB warm start.

## UDS0736

Destination: USER-TASK, CONSOLE Routing code: U Weight: 99

Warranty : NO

UDS0736 UDS USER ERROR: RESTART ONLY POSSIBLE WITH UNCHANGED SECOLTP PRIVILEGE (&01) (&02)

### Meaning

The setting of the SECOLTP privileges (assigned /not assigned) must
be the same for the restart of UDS/SQL tasks as for session start.

### Response

Correct setting of SECOLTP privileges and repeat restart.

## UDS0737

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0737 REALM HAS BEEN EXTENDED: (&00) DATABASE-PAGES (&01) (&02)

### Meaning

(&00): <dbname>.<realmname> +<nr-pages>.
The realm <realmname> in the database <dbname> has been extended by
<nr-pages> database-pages.

## UDS0738

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0738 ONLINE EXTENSIBILITY FOR REALM (&00) CANNOT BE DEACTIVATED AS FOR SOME DBTTS EXTENSIBILITY IS ACTIVATED (&01) (&02)

### Meaning

The deactivation of online extensibility of realm <dbname>.<realmname>
is not possible because DBTTs in this realm are still online extendible.

### Response

Deactivate online extensibility for all DBTTs in this realm which are
still extendible and repeat deactivation of online realm
extensibility.

## UDS0739

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0739 REALM (&00) CANNOT BE EXTENDED. MAXIMUM SIZE ALREADY REACHED (&01) (&02)

### Meaning

The realm <dbname>.<realmname> shown in (&00) cannot be extended
as it has already reached its maximum size.

### Response

Release unused space within the realm (e.g. using BPGSIZE offline with
unchanged page-size to reclaim free space in all realms of the database),
or erase records no longer required.

## UDS0740

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0740 ONLINE EXTENSIBILITY FOR REALM (&00) SUSPENDED (&01) (&02)

### Meaning

The realm <dbname>.<realmname> shown in (&00) cannot be extended.
In the present situation no further attempts to extend the realm will be
made.
The cause is indicated by a previous message, e.g.
UDS0700...DMS ERROR...0922 xxxxxxxx or
UDS0700...DMS ERROR...0000 xxxx0140 if Secondary-Allocation = 0.
UDS0700...DMS ERROR...054D xxxxxxxx or
UDS0700...DMS ERROR...0000 xxxx0142 if User Id exhausted.
UDS0700...DMS ERROR...0541 xxxxxxxx or
UDS0700...DMS ERROR...0000 xxxx0141 if no disc space available.

### Response

Depending on the cause of the problem (see previous message) the
Administrator can proceed as follows:
If the cause can be eliminated without dropping the realm (e.g.
if there was not enough disk-space available to the user ID) the
DAL-Command
"REACT INCR" can be used to enable further extension attempts.
If it is necessary to drop the realm, (e.g. because the primary space
allocation for the realm-file is too small and the secondary allocation is
zero), to drop the database, or to terminate the session the next
attachment
of the realm to a session will enable further extension attempts.

## UDS0741

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0741 DBTT HAS BEEN EXTENDED: (&00) DBTT ENTRIES (&01) (&02)

### Meaning

(&00): <dbname>.<recordname> +<nr-entries>.
The DBTT of record <recordname> in the database <dbname> has been
extended by <nr-entries> entries.

## UDS0742

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0742 DBTT OF RECORD (&00) CANNOT BE EXTENDED. MAXIMUM SIZE ALREADY REACHED (&01) (&02)

### Meaning

The DBTT of record <dbname>.<recordname> shown in (&00) cannot be extended
as it has already reached its maximum size.

## UDS0743

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0743 DBTT OF RECORD (&00) CANNOT BE EXTENDED (&01) (&02)

### Meaning

The DBTT of record <dbname>.<recordname> shown in (&00) cannot
be extended. For the reason see preceding or following messages.

### Response

Remove cause of error and repeat order to extend DBTT.

## UDS0744

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0744 ONLINE DBTT EXTENSIBILITY IN REALM (&00) IMPOSSIBLE AS REALM IS NOT EXTENDIBLE (&01) (&02)

### Meaning

The online DBTT extensibility of the DBTTs in Realm (&00)
cannot be activated or executed because the realm is not
online extendible.

### Response

Activate online realm extensibility and repeat the order for
the DBTTs concerned.

## UDS0745

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0745 ONLINE DBTT EXTENSIBILITY IN REALM (&00) CANNOT BE PROCESSED AS REALM IS NOT AVAILABLE (&01) (&02)

### Meaning

The online DBTT extensibility of DBTTs in realm (&00) cannot
be activated, deactivated or executed because the realm is
not available.

### Response

Repeat the order for the DBTTs concerned when the realm has
been added.

## UDS0746

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0746 UDS PUBSET DECLARATION (&00) FOLLOWS (&01) (&02)

### Meaning

The contents of the current or new UDS/SQL Pubset Declaration are shown
in the following message lines.
Insert (&00) distinguishes between the two cases:
(CURRENT): The contents of the currently effective UDS/SQL Pubset
Declaration are shown.
(PENDING): The contents of the new UDS/SQL Pubset Declaration which
will become effective at the next DAL PERFORM are shown.

## UDS0747

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0747 UDS PUBSET DECLARATION NOT PRESENT, DEFAULT IS CATID * (&00) (&01) (&02)

### Meaning

As no UDS/SQL Pubset Declaration is present Catid * is used.
Insert (&00) distinguishes between the two cases:
(CURRENT): The message concerns the currently effective UDS/SQL Pubset
Declaration.
(PENDING): The message concerns the UDS/SQL Pubset Declaration which
will become effective at the next DAL PERFORM.

## UDS0748

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0748 UDS USER ERROR IN UDS PUBSET DECLARATION (SYNTAX): (&00) (&01) (&02)

### Meaning

The analysis of the UDS/SQL Pubset Declaration (identification of
Catid Groups) detected the error specified in (&00):
CATID GROUP TOO LONG: A Catid Group exceeds the maximum Length
of 26 Characters.
TOO MANY CATID GROUPS: More than 100 Catid Groups have been defined.
EXCLUDE CATID GROUP NOT ALONE: The definition of a Catid Group to be
excluded is combined with the definition of Catid Groups to be
included.
The contents of the UDS/SQL Pubset Declaration are shown in
following message lines.

### Response

Correct the UDS/SQL Pubset Declaration.
If the error was detected when starting the DBH restart the DBH.
If the error was detected when executing DAL NEW PUBSETS repeat
the DAL.

## UDS0749

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0749 UDS USER ERROR IN UDS PUBSET DECLARATION (SYNTAX) (&00) (&01) (&02)

### Meaning

The syntax check of each Catid Group of the UDS/SQL Pubset Declaration
detected the error specified in (&00):
CATID GROUP REJECTED BY FSTAT: Syntax error reported by FSTAT using Catid
Group.
CATID GROUP REJECTED BY CMDWCC: Syntax error reported by SDF-macro CMDWCC
for Catid Group.
Following message lines show with
UDS-PUBSET-JV: the name of the JV concerned,
PUBSETS: the Catid Group concerned, and
FSTAT-DMS-RC: the FSTAT Returncode (only for CATID GROUP REJECTED BY
FSTAT).
No more than 10 Errors are shown.
The test file name used for FSTAT is UDS-PUBSET-DECLARATION-TEST-NAME.

### Response

Correct the UDS/SQL Pubset Declaration.
If the error was detected when starting the DBH restart the DBH.
If the error was detected when executing DAL NEW PUBSETS repeat
the DAL.

## UDS0750

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0750 UDS WARNING: PHYSICAL ALLOCATION RIGHT MISSING FOR (&00) (&01) (&02)

### Meaning

(&00): <catid>, DB: <dbname>
The physical allocation right, which would be necessary for the the
allocation of new ALOG files of the database <dbname>, is missing on
the pubset <catid> for the current userid.

### Response

Allocate the ALOG files by yourself, before they are needed by the
database handler
or get the required right granted by the bs2000 administrator.

## UDS0751

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0751 UDS WARNING: PUBSET/VOLUMESET (&00) NOT ACCESSIBLE (&01) (&02)

### Meaning

(&00): <catid>
The pubset or volumeset, which is specified for the allocation of
new RLOG files, is not accessible.

### Response

Make the pubset or volumeset accessible or specify another
location for the RLOG files.

## UDS0752

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0752 UDS USER ERROR: ACCESS TO UDS-PUBSET-JV VIA JV-LINKNAME (&00) FAILED (&01) (&02)

### Meaning

The analysis of the UDS/SQL Pubset Declaration found an allocation
for the JV-Linkname specified in (&00), but access to the JV
was not possible, perhaps due to non existence of the JV (or
length 0) or to access restrictions.

### Response

Correct the allocation for the JV-Linkname or modify the
attributes of the JV.
If the error was detected when starting the DBH restart the DBH.
If the error was detected when executing DAL NEW PUBSETS repeat
the DAL.

## UDS0753

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0753 UDS SUPPRESSES FURTHER ERROR MESSAGES FOR DB JV (&00) (&01) (&02)

### Meaning

The limit for the number of similar error messages concerning DB JV was
reached. Further error messages are suppressed.

## UDS0754

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0754 UDS SWITCHES TO NEW PUBSET DECLARATION NOW (&00) (&01) (&02)

### Meaning

The UDS/SQL Pubset Declaration announced with DAL NEW PUBSETS is now
effective as a result of a possibly internal PERFORM.

## UDS0755

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

UDS0755 UDS USER ERROR: CATID MISSING IN UDS PUBSET DECLARATION (&00) (&01) (&02)

### Meaning

A Catid previously specified in connection with ALOG- or
RLOG-Logging is missing from the UDS/SQL Pubset Declaration.
(&00) gives information about Catid and the logging object concerned.

## UDS0756

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0756 UDS WARMSTART WITH RLOG FILE (&00) STARTED (&01) (&02)

### Meaning

UDS has started to perform a warmstart for one or more databases
with the RLOG file (&00).
The end of this action will be noted by further messages.

## UDS0757

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0757 EXTEND REALM FOR REALM (&00) DATABASE PAGES) FAILED (&01) (&02)

### Meaning

(&00) contains: <dbname>.<realmname> (<nr-pages>.
The realm <dbname>.<realmname> specified in (&00) cannot be extended
by <nr-pages> database pages.
The cause is indicated by a previous message, e.g.
UDS0700...DMS ERROR...0922 xxxxxxxx or
UDS0700...DMS ERROR...0000 xxxx0140 if Secondary-Allocation = 0.
UDS0700...DMS ERROR...054D xxxxxxxx or
UDS0700...DMS ERROR...0000 xxxx0142 if User Id exhausted.
UDS0700...DMS ERROR...0541 xxxxxxxx or
UDS0700...DMS ERROR...0000 xxxx0141 if no disc space available.

### Response

After fixing the problem (indicated by the previous message)
try again DAL EXTEND REALM.

## UDS0758

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0758 NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE (&00) (&01) (&02)

### Meaning

Number of DML-statements and I/O counters per database are shown.
After the message UDS0758, the number of DML statements
and logical and physical read and write orders is shown
in a table, including internal I/O orders that occur
when opening and closing the database.

## UDS0800

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0800 UDS-D SYSTEM ERROR (&00) (&01) (&02)

### Meaning

A serious error occurred in UDS-D. UDS-D is terminated with a dump.
(&01): see manual 'UDS/SQL Messages'.

### Response

Forward dump file to diagnostics department.
Restart UDSCT with &START DISTRIBUTION. If the error recurs, terminate
UDS/SQL session and restart.
Further information see manual 'UDS/SQL Messages'.

## UDS0801

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0801 UDS-D STARTING (&00) (&01) (&02)

### Meaning

UDS-D task UDSCT has been initialized.
(&00): (version,date).

## UDS0802

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0802 UDS-D INITIALIZATION DELAYED. PLEASE CHECK BATCHLIMIT. (&00) (&01) (&02)

### Meaning

UDS-D initialization has not yet been completed because the UDSCT task
cannot start (due to low batch limit) or cannot complete initialization
due to errors. This message also applies of relinking with UDSCT.

### Response

Check if batch limit is high enough or if the C.UDSCT phase exists. If the
UDSCT task does not exist any more, analyze error messages on SYSLST log.
Restart UDSCT using &START DISTRIBUTION.

## UDS0803

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0803 UDS-D NOT YET STARTED (&00) (&01) (&02)

### Meaning

The DAL command entered has been rejected because UDS-D has not been
started yet.

### Response

Start UDS-D using &START DISTRIBUTION. Repeat rejected DAL command.

## UDS0804

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0804 UDS-D ALREADY STARTED (&00) (&01) (&02)

### Meaning

UDS-D has already been started. The DAL command &START DISTRIBUTION is
rejected.

## UDS0805

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0805 UDS-D READY (&00) (&01) (&02)

### Meaning

Distributed transactions can be started.

## UDS0806

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0806 UDS-D: ADMINISTRATION CLOSED DUE TO ERROR (&00) (&01) (&02)

### Meaning

UDS-D administration is no longer possible. Distributed transactions are
not affected.

### Response

For subsequent deactivation of the distribution, terminate the UDSCT task
using the operating system command /CANCEL-JOB <tsn>. If administration is
required, terminate UDS/SQL session and restart.

## UDS0807

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0807 UDS-D: TERMINATION INITIATED (&00) (&01) (&02)

### Meaning

Self-explanatory.

## UDS0808

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0808 UDS-D TERMINATING (&00) (&01) (&02)

### Meaning

UDS-D is being terminated; the DAL command indicated is rejected.

### Response

Start UDS-D using &START DISTRIBUTION. Repeat DAL command.

## UDS0809

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0809 UDS-D NORMAL TERMINATION (&00) (&01) (&02)

### Meaning

Message indicated normal end.

## UDS0810

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0810 UDS-D ABNORMAL TERMINATION (&00) (&01) (&02)

### Meaning

Abnormal termination of UDSCT.
(&00): number of rolled back secondary transactions that are still open.
(&01): see manual 'UDS/SQL Messages'.

### Response

Forward dump file to diagnostics department.
Restart UDSCT using &START DISTRIBUTION.
Further information see manual 'UDS/SQL Messages'.

## UDS0811

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0811 UDS-D: TASK PROGRAM TIME RUN OUT (&00) (&01) (&02)

### Meaning

STXIT event: The maximum runtime for the UDSCT task has elapsed.

### Response

1) check join entry for CPU time
2) activate UDS-D using DAL command &START DISTRIBUTION.

## UDS0812

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0812 UDS-D: TASK ABNORMALLY ENDED (&00) (&01) (&02)

### Meaning

STXIT event ABEND for UDSCT:
UDSCT has been terminated with LOGOFF, START-EXECUTABLE-PROGRAM,
LOAD-EXECUTABLE-PROGRAM, ABEND or CANCEL-JOB.

### Response

Restart UDS-D with DAL command &START DISTRIBUTION.

## UDS0813

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0813 UDS-D WARNING: MEMORY OVERFLOW (&00) (&01) (&02)

### Meaning

UDS-D memory request could not be honored.
(&01): see manual 'UDS/SQL Messages'.

### Response

If the error recurs regularly, terminate UDS/SQL session and restart with
increased value for PP TRANSACTION.
Further information see manual 'UDS/SQL Messages'.

## UDS0814

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0814 UDS-D: INVALID PARAMETERS IN UDSCT ENTER FILE. (&00) (&01) (&02)

### Meaning

Invalid parameters were detected during reading of the UDSCT enter file
UDS.ENTER.<master task tsn>.CT000.

### Response

Check the enter file. Terminate and restart UDS/SQL session in order to
create a new enter file.

## UDS0815

Destination: USER-TASK, CONSOLE Routing code: U Weight: 99

Warranty : NO

UDS0815 UDS-D ERROR READING INPUT FILE FOR DISTRIBUTION TABLE (&00) (&01) (&02)

### Meaning

The input file for the distribution table could not be read.
(&00) contains
a) SSM return code: SSMCODE=>SSMCODE<
b) RDATA return code: RDATA=>return-code<.

### Response

Check existence, contents, type and access right of input file for
distribution table. Fetch the DMS code by using the BS2000 command
/ASSIGN-SYSDTA for the input file.

## UDS0816

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0816 UDS-D ERROR WRITING OUTPUT FILE FOR DISTRIBUTION TABLE (&00) (&01) (&02)

### Meaning

Error during saving of distribution table (using DAL '&SAVE
DISTRIBUTION').
(&00) contains
a) DMS return code: DMSCODE=>DMS-CODE<
b) SVC-WRLST return code: WRLST=>return-code<.

### Response

Check existence, type and access right of output file.

## UDS0817

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0817 UDS-D USER ERROR: INPUT FILE FOR DISTRIBUTION TABLE CONTAINS TOO MANY INVALID RECORDS (&00) (&01) (&02)

### Response

Check contents of the input file for the distribution table. Check
specification for PP DISTABLE or file name entered with
&ADD DISTRIBUTION. Reread input file using DAL command &ADD DISTRIBUTION.

## UDS0818

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0818 UDS-D ERROR: WRONG DCAM VERSION (&00) (&01) (&02)

### Meaning

The DCAM version is not allowed for UDS-D.

### Response

Make appropriate DCAM available.

## UDS0819

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0819 UDS-D DISTRIBUTION TABLE CANNOT BE CHANGED AT THE MOMENT (&00) (&01) (&02)

### Meaning

The distribution table cannot be updated at the moment because other tasks
have read access.

### Response

Repeat DAL command later.

## UDS0820

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0820 UDS-D WARNING: THE DISTRIBUTION TABLE FILE CONTAINS DATABASE ENTRIES WITHOUT REFERENCES TO A CONFIGURATION (&00) (&01) ( &02)

### Meaning

The input file for the distribution task contains data base entries
without
any reference to a configuration or processor. These entries are taken up
into the distribution table, but the associated data bases cannot take
part
in the distribution.

### Response

Effect assignment to configuration or processor using DAL command
&ADD DISTRIBUTION.

## UDS0821

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0821 UDS-D WARNING: RECORD FROM DISTRIBUTION TABLE FILE REJECTED AS NAMES ALREADY EXISTING (&00) (&01) (&02)

### Meaning

Identical names in the distribution table are not allowed. Names have to
be
unique in the entire network.
Example: existing record: SS A to DB B
new record: SS A to DB C
The new record is rejected.
(&00): name of the rejected record.

### Response

Check network-wide uniqueness of specifications in distribution table.
Remove duplicates.

## UDS0822

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0822 UDS-D WARNING: INPUT FILE FOR DISTRIBUTION TABLE CONTAINS (&00) INVALID RECORDS (&01) (&02)

### Meaning

Invalid records in the input file for the distribution table.
(&00): number of invalid records.

### Response

Check input file for distribution table and correct error. Repeat reading
of distribution table using &ADD DISTRIBUTION, if necessary.

## UDS0823

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0823 UDS-D: INPUT FILE FOR DISTRIBUTION TABLE (&00) READ (&01) (&02)

### Meaning

The input file (&00) for the distribution table has been read.

## UDS0824

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0824 UDS-D: ONLY PASSIVE PARTICIPATION POSSIBLE AS NO DISTRIBUTION TABLE FILE DEFINED (&00) (&01) (&02)

### Meaning

No distribution table exists because no specifications were entered in
PP DISTABLE at UDS/SQL start. The configuration is thus restricted
to passive participation in the distribution, i.e. it can process
DML statements from remote configurations, but cannot have its own DML
statements processed in remote configurations.

### Response

If active participation in the distribution is desired, set up
distribution
table using DAL command &ADD DISTRIBUTION.

## UDS0825

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0825 UDS-D USER ERROR: NAME (&00) UNKNOWN IN DISTRIBUTION TABLE (&01) (&02)

### Meaning

The name indicated under (&00) does not exist in the distribution table.

### Response

Correct and repeat DAL command.

## UDS0826

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0826 UDS-D USER ERROR: SPECIFIED DISTRIBUTION DEFINITION UNKNOWN (&00) (&01) (&02)

### Meaning

The assignment indicated under (&00) does not exist in the distribution
table.

### Response

Correct distribution table using a DAL command.

## UDS0827

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0827 UDS-D DCS ERROR (&00) (&01) (&02)

### Meaning

Error in the UDS-D/DCAM interoperation.
(&00) contains module identification and DCAM return codes (FDBK):
- if output is in master task or UDSCT:
UDSCT module identification and DCAM return codes (FDBK)
- if output is in the user task:
4 bytes hex. diagnostic info from UDSNET and DCAM return codes (FDBK).
FDBK=0C5C can mean that the partner rejected the connection request.
Possible causes for this rejection are: wrong password, incompatibility
of versions. If the partner UDSCT rejected the connection request because
of a wrong password or because of incompatibility of versions,
the partner UDSCT outputs the message UDS0840.

### Response

If none of the above mentioned causes:
forward dump file to diagnostics department.
Restart UDSCT if necessary using &START DISTRIBUTION.

## UDS0828

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0828 UDS-D: DCS CLOSED, RECONNECTION TRIED PERIODICALLY (&00) (&01) (&02)

### Meaning

Connection of UDSCT to the DCS component has been terminated. UDSCT
periodically attempts reconnection.

### Response

Check DCS generation.

## UDS0829

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0829 UDS-D: STATUS OF PRIMARY SUBTRANSACTION IS UNKNOWN, BECAUSE PARTNER CONFIGURATION (&00) COULD NOT BE REACHED (&01) (&02)

### Meaning

Secondary subtransactions in PTC state cannot be terminated as the state
of
associated primary transactions cannot be determined. The required partner
configuration cannot be reached.
(&00): partner processor and configuration name.

### Response

Check state of the connection and the partner configuration.

## UDS0830

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0830 UDS-D: PARTNER CONFIGURATION (&00) COULD NOT BE REACHED (&01) (&02)

### Meaning

The secondary subtransaction in the indicated partner configuration cannot
be informed of the transaction end effected for the associated primary
transaction due to a warm start because it cannot be reached.
(&00): partner processor and configuration name.

### Response

Check state of the connection and the partner configuration.

## UDS0831

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0831 UDS-D: (&00) SECONDARY SUBTRANSACTIONS REMAIN IN PTC STATE (&01) (&02)

### Meaning

UDS-D terminates although secondary subtransactions are still in the
PTC state.
(&00): number of remaining secondary transactions.

### Response

a) Leave secondary transactions in the PTC state:
- The data bases concerned cannot be disconnected from the UDS/SQL
configuration.
- The UDS/SQL session can no longer be terminated using CLOSE CALLS CLOSE
RUN-UNITS, but only using %TERM.
- The secondary subtransactions in the PTC state occupy entries in the
UDS/SQL tables and thus reduce the
number of transactions that can be serviced in parallel. Furthermore,
they impede UDS/SQL operation by
means of locks and block the RLOG file.
b) Determine the transaction ID using DAL command DISPLAY and terminate
the secondary subtransaction
using COMMIT or ABORT OPTION=PTC. (Warning: Affects interconfiguration
consistency)
c) Restart UDSCT using &START DISTRIBUTION. UDS-D makes another attempt to
terminate the seconary subtranactions in a
consistent state. This operation is successful only if the
configurations of the associated primary subtransactions can be reached.

## UDS0832

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0832 UDS-D: COMMAND EXECUTED (&00) (&01) (&02)

### Meaning

An UDS-D DAL command has been executed.

## UDS0833

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0833 UDS-D ERROR FOR ENTER-JOB UDSCT (&00) (&01) (&02)

### Meaning

Execution of the ENTER macro for the start of UDSCT was not successful.
(&00): return code.

### Response

Check if the enter file UDS.ENTER <mastertask tsn>.CT000 exists and if
at least 32000 CPU seconds are available for the userid under which
UDS/SQL is running. Then restart UDSCT using &START DISTRIBUTION.

## UDS0834

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0834 UDS-D WARNING: THE DISTRIBUTION TABLE FILE CONTAINS ONLY COMMENTS (&00) (&01) (&02)

### Meaning

The input file for the distribution table contains only commands.

### Response

Check contents of input file for distribution table. Check entry for
PP DISTABLE or file name for &ADD DISTRIBUTION. Reread file using
&ADD DISTRIBUTION.

## UDS0835

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0835 UDS-D: MORE MESSAGES IN SYSOUT PROTOCOL OF UDS-D TASK UDSCT (&00) (&01) (&02)

### Meaning

Not all the messages on the administration task could be output during
reading of the distribution table file.

### Response

Check distribution table file.

## UDS0836

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

## UDS0837

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0837 UDS-D WARNING: DCAM-APPLICATION (&00) CAN TEMPORARILY NOT BE OPENED. OPENING WILL BE TRIED PERIODICALLY (&01) (&02).

### Meaning

The DCAM-application could not be opened.
If this situation occurs except during initialization of UDSCT
UDSCT will try periodically to open this application.
(&00): module code/application concerned/DCAM feedback.

### Response

Check state of DCS.

## UDS0838

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0838 UDS-D WARNING: DCAM-APPLICATION (&00) CANNOT BE OPENED (&01) (&02).

### Meaning

The DCAM-application could not be opened.
The problem is not temporary.
(&00): module code/application concerned/DCAM feedback.

### Response

Check state of DCS.

## UDS0839

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0839 UDS-D ERROR: DCAM-APPLICATIONS CANNOT BE OPENED (&00) (&01) (&02).

### Meaning

The DCAM-application could not be opened due to
DCS-problems or some control blocks could not be
created in the necessary size.
The problems occurred during the initialization of UDSCT
or the problems are not temporary DCS-problems.
UDSCT is terminated.

### Response

Check state of DCS or reduce number server tasks.

## UDS0840

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0840 UDS-D: CONNECTION REQUEST REJECTED (&00) (&01) (&02).

### Meaning

A partner's connection request was rejected.
(&00): module code/application concerned/processor concerned/reason
If "VERSION" is given as reason, the partner's
UDS/SQL version is not supported.
If "PASSWORD" is given as reason, the local configuration is
protected by a password which the partner did not communicate
when requesting a connection.

### Response

If "VERSION" is given as reason, the partner has to use a higher
UDS/SQL version.
If "PASSWORD" is given as reason and a connection to the
partner should be allowed, the partner's distribution table
or the local distribution table has to be changed as far as
the password protection for the local configuration
is concerned.

## UDS0841

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0841 UDS-D: PREVIOUS OUTPUT OF DISPLAY DISTRIBUTION INCOMPLETE (&00) (&01) (&02).

### Meaning

The output of the distribution table is incomplete because
it is too large.

### Response

Repeat DAL with restricting conditions or produce output
of the whole distribution table in a file with SAVE
DISTRIBUTION.

## UDS0901

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0901 UDSADM STARTS (&00) (&01) (&02)

## UDS0902

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0902 UDSADM READY (&00) (&01) (&02)

### Meaning

UDSADM initialization has completed.

## UDS0904

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0904 WRONG SDF COMMAND (&00) (&01) (&02)

### Meaning

Wrong usage of SDF command.

## UDS0905

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0905 UDSADM TERMINATED NORMALLY (&00) (&01) (&02)

## UDS0906

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0906 UDSADM TERMINATED ABNORMALLY (&00) (&01) (&02)

### Response

Take Dump.
Restart UDSADM, if required.

## UDS0907

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0907 UDSADM GENERATES DUMP (&00) (&01) (&02)

### Meaning

An error situation results in a UDSADM dump call.

## UDS0908

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0908 UDSADM: SDF SUBSYSTEM NOT AVAILABLE (&00) (&01) (&02)

### Response

Make SDF available.

## UDS0909

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0909 UDSADM: INVALID SDF SYNTAX FILE (&00) (&01) (&02)

### Meaning

The currently assigned syntax file is invalid.

### Response

Assign SDF syntax file for UDSADM.

## UDS0910

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0910 UDSADM: DCAM SUBSYSTEM NOT AVAILABLE (&00) (&01) (&02)

### Response

Make DCAM available.

## UDS0917

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0917 UDSADM: DCAM APPLICATION ALREADY OPEN (&00) (&01) (&02)

### Response

Terminate task and start UDSADM with another task.

## UDS0920

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0920 UDSADM: UDS CONFIGURATION (&00) CONNECTED (&01) (&02)

### Meaning

The UDS/SQL configuration has been connected.
(&00): name of UDS/SQL configuration

## UDS0921

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0921 UDSADM: CONFIGURATION ALREADY CONNECTED (&00) (&01) (&02)

### Meaning

The UDS/SQL configuration has already been connected to
UDSADM.

## UDS0922

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0922 UDSADM: UNKNOWN CONFIGURATION (&00) (&01) (&02)

### Meaning

The UDS/SQL configuration has not been opened or DCAM administration
is forbidden (PP ADM=LOCAL).

## UDS0923

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0923 UDSADM: CONNECTION REJECTED BY UDS (&00) (&01) (&02)

### Meaning

The connection to the UDS/SQL configuration has been rejected
Possible reasons:
-incorrect connectionpassword (ADMPASS).
-UDS/SQL is connected to another administrationprogram.
-security privilege of the administrator is not sufficent

### Response

Remove the reason of rejection.

## UDS0924

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0924 UDSADM: VIOLATION OF SECURITY REQUIREMENTS (&00) (&01) (&02)

### Meaning

UDSADM has been started under a user ID with SECOLTP privilege.
The security specifications for the UDS/SQL configuration do not match.

### Response

Check the security parameters defined for the UDS/SQL configuration.

## UDS0930

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0930 UDSADM: UDS CONFIGURATION (&00) DISCONNECTED (&01) (&02)

## UDS0940

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0940 UDSADM: RECEIVE MODE STARTED (&00) (&01) (&02)

### Meaning

UDSADM has been switched to receive mode.
It waits for messages from the connected UDS/SQL configuration.

## UDS0942

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0942 UDSADM: RECEIVE MODE INTERRUPTED BY ADMINISTRATOR (&00) (&01) (&02)

## UDS0943

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0943 UDSADM: RECEIVE MODE INTERRUPTED BY LOSCON (&00) (&01) (&02)

## UDS0950

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0950 UDSADM: NO OUTSTANDING MESSAGES (&00) (&01) (&02)

### Meaning

There are no messages from the connected UDS/SQL configuration.

## UDS0971

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0971 UDSADM: CONNECTION TO UDS CONFIGURATION STILL EXISTS (&00) (&01) (&02)

### Meaning

A DCAM connection between UDSADM and the UDS/SQL configuration still
exists.

## UDS0980

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0980 UDSADM: UNKNOWN CONFIGURATION (&00) (&01) (&02)

### Meaning

The connection to the UDS/SQL configuration has failed.

### Response

Check security aspects of the UDS/SQL configuration.

## UDS0981

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0981 UDSADM: NO CONNECTION TO UDS CONFIGURATION (&00) (&01) (&02)

### Meaning

The UDSADM statement has been rejected because there is no
connection to a UDS/SQL configuration.

### Response

Set up connection and repeat statement.

## UDS0985

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0985 UDSADM: CONNECTION TO UDS CONFIGURATION LOST (&00) (&01) (&02)

### Response

Repeat CONNECT-CONFIGURATION.

## UDS0990

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0990 UDSADM: INVALID BS2000 VERSION (&00) (&01) (&02)

### Meaning

UDSADM was started under a BS2000 version which has not yet been
released.

## UDS0999

Destination: USER-TASK, CONSOLE Routing code: U Weight: 70

Warranty : NO

UDS0999 UDSADM: FATAL ERROR (&00) (&01) (&02)

### Meaning

A fatal error occurred in UDSADM.
(&02): additional diagnostic information.

### Response

Take Dump.

©2020 Fujitsu Technology Solutions GmbH | BS2000 OSD/BC System Messages