UDS/SQL V2.9 (en)

UDS0200

UDS SYSTEM ERROR (&00) (&01) (&02)
(B) Routing code: U Weight: 70

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). See section "Explanation of the message text format".

(&01) may contain the following internal message numbers:

000

Meaning
Incorrect message number.

Response
Take dump.

002

Meaning
Unspecified error in SUBCONTROL. (&02) contains further information.

Response
Take dump;
if (&02)=ENTR, check entries for CPUTIME (must be > 32000 secs.) and PUBSPACE using the ACCOUNT command;
if (&02)=LOTI, check whether the master task has been down for some time. Such situations can be avoided by always running the master task in the background.

004

Meaning
Error when creating a common memory pool.
(&02) contains the POOL name.

(1)	Probably either no SET-FILE-LINK command (LINK-NAME=DATABASE) or an incorrect one was given.
(2)	The configuration name contains special characters.
(3)	The available address space is not sufficient for a pool to be created.
(4)	UDS/SQL has already been loaded for the configuration.

Response
Repeat session start using the correct SET-FILE-LINK command or a different configuration name, or generate BS2000 with increased virtual memory. Start UDS/SQL with load parameters that require a smaller pool.

005

Meaning
PASSWORD error when accessing SAM files required for internal purposes.

Response
Take dump.

006

Meaning
Error when writing to SAM files required internally. The DMS code involved is output at the end of the message.

Response
Check whether any files UDS.ENTER.... still exist, delete them and start the session again;
if unsuccessful, generate memory dump and terminate. Create space on the Public Volume Set.

008

Meaning
Error in REQM macro.

Response
Take dump.

018

Meaning
The DBH or RBAM is employing an unknown SUBCONTROL function.

Response
Take dump.

022

Meaning
SC cannot meet a storage space requirement.

Response
Take dump; generate BS2000 with increased virtual storage.

026

Meaning
Error in serialization of the subcontrol system.
(&02) contains the name of the serialization item.

Response
Take dump.

027

Meaning
Error in the event control system in the SC.
(&02) contains the name of the event item.

Response
Take dump.

029

Meaning
P error in UDS/SQL.
(&02) contains the error weight, the error address, the module code of the defective module and of the defective task.

Response
Take dump.

036

Meaning
An error occurred during generation of an event code (P1 eventing).
(&02) contains the name of the event code.

Response

Check whether tasks of an earlier UDS/SQL session with the same configuration name exist and cancel them, or delete the ENTER files UDS.ENTER... .
Restart UDS/SQL.
Check whether the dynamic subsystem for forward eventing was loaded incorrectly.

043

Meaning
An error occurred in a UDS/SQL STXIT routine.

Response
Take dump.

044

Meaning
Illegal TERM detected.

Response
Take dump.

049

Meaning
The contingency routine cannot be defined.

Response
Take dump.

060

Meaning
The DBTT of the DBDIR points to a page for the schema record which does not contain the record.
(&00): Database name

Response
DIAG; if necessary, RESET-DB.

061

Meaning
A database error or error in DBH processing was detected by means of validity check.
(&00) contains: number of validity check (CNRxx)
name of checking module (xxxxxxx).

Response
DIAG; START-UDS; if the error recurs, check the physical data with BCHECK; depending on the result of checking, RESET-DB or remove program causing error or initiate recovery measures.

087

Meaning
Incorrect CALL to LCCONTR (contents of LCBCALL are incorrect).

Response
Take dump.

110

Meaning
The act-key for the schema (SIA) in the DBTT of DBDIR is equal to zero.
(&02) contains the database name.

Response
DIAG; if necessary, RESET-DB.

115

Meaning
Connection module UDSCON cannot be linked.

Response
(1) Check SET-TASKLIB command.
(2) Check if the module is held in the corresponding library.

131

Meaning
Error on creation of a common memory pool.
(&00): Diagnostic information.

Response
Take dump.

132

Meaning
EVENTING error.
(&00): Diagnostic information.

Response
Take dump.

134

Meaning
Unspecified error.
(&00): Diagnostic information.

Response
Take dump.

136

Meaning
Communication, SSITAB or distribution pool overflow.
(&00): Diagnostic information.

Response
Take dump.

140

Meaning
The internal UDS/SQL representation of the subschema (’SSIA’) is corrupted.
(&00): Subschema name.

Response
Recompile subschema after session end or database deactivation. Recompile and relink application program.

142

Meaning
Function code in BIB incorrect.

Response
Analyze error using diagnostic information and remove its cause by means of UDS/SQL, BS2000 or administrative measures as far as possible; in particular, check if error is due to user error; DIAG and restart UDS/SQL.

150

Meaning
Serialization error in connection module.
(&00): Diagnostic information.

Response
Take dump.

152

Meaning
Error in STXIT macro.
(&00): Diagnostic information; BS2000 return code when STXIT SVC is issued.

Response
If necessary, correct program (the user may have specified a user-specific STXIT routine using the old STXIT procedure).

154

Meaning
No connection between UDS/SQL and the application program.

Response
Take dump, write error report.

167

Meaning
Error in the DBH run detected by validity check.

(&00) contains:	Number of validity check (CNRxx),
	Name of checking module (xxxxxxx).

Response

DIAG, START-UDS. If error recurs, remove program causing the error.

168

Meaning
Error during creation of event code (ENABLE).

Response
Take dump.

214

Meaning
P error in the linked-in DBH.

Response

Take dump.
Submit error report for diagnosis.
Restart linked-in application.

289

Meaning
An error occurred during access to the SSITAB pool. CALL-DML application programs cannot be processed in this session. The cause of the error may be that the UDS/SQL master task was interrupted by means of ’DUE’ and left in command mode. Thus UDS/SQL was not able to connect to the SSITAB pool.

Response
In order to be able to process CALL-DML application programs, terminate the UDS session and reload it. Note that the UDS/SQL master task must not remain in command mode after the administrator functions have been entered.

302

Meaning
A UDS/SQL programming error was detected at the address indicated.

Response
DIAG, if necessary, START-UDS.

304

Meaning
An error occurred in the UDS/SQL subsystem SUBCONTROL, compromising reliable communication with the database administrator (UDS/SQL messages, dump) or effective DBH control over the session run. UDS/SQL aborts the UDS/SQL task concerned (and thus the session) with PDUMP.

Response
DIAG, START-UDS.

759

Meaning
An overflow occurred in the internal queue of the message manager.

Response
In case of UDSADM DISPLAY command, repeat the command with limitation of the number of output lines.

UDS0201

UDS SYSTEM READY (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0202

UDS ABNORMAL SYSTEM TERMINATION WITH (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: LINK ERROR LINKING (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
(&00): name of module / load source
(&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 corresponding module library.
(3)	Check whether the SET-TASKLIB command of the master task and PP TASKLIB match.

UDS0204

UDS MAINTASK STARTING NOW (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0205

UDS DUMP WANTED? (Y=YES/N=NO) (REASON=(&00)) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS ACCEPTED COMMAND (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0207

UDS USER ERROR: UDS ALREADY LOADED FOR THE CONFIGURATION (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS MAINTASK READY (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0209

UDS USER ERROR: COMMAND REJECTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

Response
Depends on information in (&01).

(&01) may contain the following internal message numbers (see "Explanation of themessage text format"):

021

Meaning
The specified character string cannot be interpreted as a command.
(&00) contains the incorrect character string.

Response
Correct command and repeat.

023

Meaning
The specified character string cannot be interpreted as an SC command.
(&00) contains the incorrect character string.

Response
Correct command and repeat.

072

Meaning
This command cannot be currently executed for one of the following reasons:

A dump is being generated.
There are already too many unprocessed commands in the input queue.

Response
Repeat the command later. Note that only commands that begin with ’%’ are permitted during the execution of a warm start or when a job is being processed (following the PERFORM command).

192

Meaning
The SEND-MSG command was rejected by the UDS/SQL connection module. (It starts with ’%’ and is not recognized by the UDS/SQL connection module!)

Response
The user’s own SEND-MSG commands may not begin with ’%’.

305

Meaning
The DAL command issued is incorrect.

(&00) may contain the following:

CATID NOT WITHIN SCOPE OF CURRENT AND PENDING UDS PUBSET DECLARATIONS.

Meaning
A new definition for the RLOG logging entries using DAL MODIFY LOG, MODIFY LOG-2, or MODIFY RESERVE is rejected because the new specification is outside the pubset space of the current UDS/SQL pubset declaration and also outside the pubset space of a new UDS/SQL pubset declaration which has already been determined using DAL NEW PUBSETS but has not been enabled by means of PERFORM.

CATID NOT WITHIN SCOPE OF CURRENT UDS PUBSET DECLARATION.

Meaning
A new definition for the RLOG logging entries using DAL MODIFY LOG, MODIFY LOG-2, or MODIFY RESERVE is rejected because the new specification is outside the pubset space of the current UDS/SQL pubset declaration.

CATID NOT WITHIN SCOPE OF PENDING UDS PUBSET DECLARATION.

Meaning
A new definition for the RLOG logging entries using DAL MODIFY LOG, MODIFY LOG-2, or MODIFY RESERVE is rejected because the new specification is outside the pubset space of a new UDS/SQL pubset declaration which has already been determined using DAL NEW PUBSETS but has not been enabled by means of PERFORM.

COMMAND TEMPORARY FORBIDDEN

Meaning
The DAL command is currently not permitted, but can be repeated later.

COMMAND UNKNOWN

Meaning
The DAL command is unknown.

COMMIT IS WITHOUT PTC

Meaning
The specified transaction is not in the PTC, COMMIT is therefore superfluous.

DB DESTROYED

Meaning
The database has been destroyed.

DB IS ALREADY ONLINE

Meaning
The given database is already configured.

DB IS UNKNOWN TO DBH

Meaning
The given database is not configured.

DB WITHOUT ALOG-LOGGING

Meaning
The database is processed without ALOG logging.

DB-NAME IS AMBIGUOUS WITHIN CONFIGURATION

Meaning
The DB name entered is not unique within the configuration.

DBTT CONCURRENTLY EXTENDED

Meaning
A DBTT extension is already in progress for the specified record type. Consequently no further extension can be initiated for the record type at present.

DBTT HAS MAXIMUM SIZE

Meaning
The specified record type’s DBTT cannot be extended because it has already reached its maximum size.

DBTT IS NOT ONLINE

Meaning
The specified record type’s DBTT realm is not attached.

DBTT REALM EXTENSION NOT ACTIVATED

Meaning
Online extensibility is not activated for the specified record type’s DBTT realm.

DBTT REALM EXTENSION SUSPENDED

Meaning
Online extensibility is suspended for the specified record type’s DBTT realm.

DIFFERENT VOLSETS FOR SAME LOGFILE ARE FORBIDDEN.

Meaning
Volumes from different volume sets of an SM pubset were specified for creating an RLOG file.

ERROR IN SYNTAX OF COMMAND

Meaning
There is a syntax error in the DAL command (see the manual “UDS/SQL Database Operation”, chapter “Administration”, section “The Database Administrator Language DAL”).

ERROR IN SYNTAX OF DB-NAME

Meaning
There is a syntax error in the DB name.

ERROR IN SYNTAX OF PASSWORD

Meaning
There is a syntax error in the password entered.

ERROR IN SYNTAX OF REALM-NAME

Meaning
There is a syntax error in the realm name.

ERROR IN UDS PUBSET DECLARATION.

Meaning
The change to the current UDS/SQL pubset declaration using DAL NEW PUBSETS is rejected.
More precise details on the cause were provided in a previous message, for example with UDS0748, UDS0749, UDS0752, UDS0755.

ILLEGAL COMBINATION OF OPERANDS

Meaning
The entered combination of operands is not permitted for this DAL command.

ILLEGAL VALUE OF DAL-COMMAND

Meaning
An index term has been assigned an illegal value in a DAL command.

LOC FOR LOG AND LOC FOR LOG-2 ARE NOT DIFFERENT

Meaning
The same data medium has been specified for both copies of the RLOG file.

MORE DB’S THAN SPECIFIED

Meaning
The maximum number of databases permitted have already been entered.

MORE PASSWORDS THAN ALLOWED

Meaning
More passwords have been specified than are permitted.

NO ACTION POSSIBLE

Meaning
The DAL command had no effect. The reason for this has already been reported in an earlier message.

NO ORDERS EXISTING

Meaning
No orders requiring processing exist.

NO RESTART-LOGGING

Meaning
The session is run without RESTART-LOGGING.

OPERAND UNKNOWN

Meaning
At least one of the operands entered is unknown.

OWN-BUFFER-SIZE CONFLICT

Meaning
The specified shared user buffer pool already exists and has a size that is different from the one specified in this command.

OWN-BUFFER-SIZE MISSING

Meaning
The specified shared user buffer pool is not yet defined for another database, and no buffer pool size (or OWN-BUFFER-SIZE = 0) is specified.

PASSWORD IS STILL EXISTING

Meaning
The password is already known to the DBH.

PASSWORD IS UNKNOWN TO DBH

Meaning
The specified password is unknown to the DBH.

REALM IS ALREADY ONLINE

Meaning
The specified realm has been added.

REALM IS NOT EXISTING

Meaning
The specified realm no longer exists (the DB has been reconstructed).

REALM IS NOT ONLINE

Meaning
The specified realm has been dropped (DAL).

REALM IS PART OF SHARED-RETRIEVAL-DB

Meaning
The specified realm is part of a SHARED-RETRIEVAL-DB.

REALM IS TEMPORARY

Meaning
The specified realm is temporary.

REALM IS UNKNOWN TO DBH

Meaning
The specified realm is unknown to the DBH.

REALM NOT DROPABLE

Meaning
The specified realm cannot be dropped.

REALM NOT PRESENT IN THIS DB-VERSION

Meaning
The specified realm is not present in this version of the database. (Dropped with BSECURE).
(Can only occur in versions < UDS/SQL V1.2)

REALM WITH ACTIVATED DBTT EXT

Meaning
The online extensibility of the specified realm cannot be deactivated as at least one online DBTT extension is activated in the realm.

REALM-NAME IS AMBIGUOUS WITHIN CONFIGURATION

Meaning
The specified realm name is not unique within the configuration.

RECORD NOT EXISTING

Meaning
The specified record type does not exist.

RUNID IS UNKNOWN TO DBH

Meaning
The specified RUNID is unknown to the DBH.

SECOND ADD-DB-ORDER

Meaning
The task of adding this database has already been initiated with another DAL command.

SESSION WITHOUT LOG-2

Meaning
No duplicate of the RLOG file is being maintained in the current session.

VORGANG NOT EXISTING

Meaning
The specified SQL conversation does not exist.

VSNS IN LOC FOR LOG/LOG-2/RESERVE ARE NOT DIFFERENT

Meaning
The same data medium has been specified for both copies of the RLOG file or for one copy and the reserve assignment.

UDS0210

UDS MAINTASK TERMINATION COMPLETED (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Termination has been completed for the maintask.

UDS0211

UDS WARNING: UDS COMMAND DELAYED, SINCE NOT POSSIBLE AT THIS MOMENT (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS SYSTEM INITIALIZATION DELAYED. PLEASE CHECK BATCHLIMIT (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS NORMAL SYSTEM TERMINATION WITH (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0214

UDS TRANSACTION (&00) CANCEL STARTED (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The transaction specified in (&00) is aborted.

UDS0215

UDS STARTING (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
(&00): version number and date.

UDS0216

UDS WARNING: LIFETIME FOR DISTRIBUTED COMMUNICATION IS TOO SMALL (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: BFORMAT RUN MISSING (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0218

UDS COMPLETED EXECUTION OF DAL COMMAND (&00) (&01) (&02)(B) Routing code: U Weight: 50

Meaning
There will be no further messages concerning this DAL command.

UDS0219

UDS USER ERROR: SESSION TYPE WRONG (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Repeat restart with correct session type.

UDS0220

UDS RECEIVED COMMAND: (&00) (&01) (&02)(B) Routing code: U Weight: 50

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

UDS USER ERROR: COLD START IMPOSSIBLE (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: THE GIVEN TASKLIB IS UNKNOWN. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Check load parameter TASKLIB.

UDS0223

UDS USER ERROR: PROGRAM PARAMETER WRONG (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

CONTINUE NOT ALLOWED. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0225

UDS ERROR DURING (&00) STATEMENT (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0226

UDS USER ERROR: SPACE ON REALM (&00) EXHAUSTED (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: NUMBER OF RECORDS EXHAUSTED FOR RECORD (&00) (&01) (&02)(B) Routing code: U Weight: 70

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 reserved using BMODTT or activate online DBTT extensibility.

UDS0228

UDS USER ERROR: REALM (&00) OFFLINE (&01) (&02)(B) Routing code: U Weight: 70

UDS0229

FASTPAM NOT LOADED. ACCESS WILL BE PERFORMED WITH UPAM. (&00) (&01) (&02)(B) Routing code: U Weight: 50

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

Response
FASTPAM should be loaded for better performance.

UDS0230

UDS PROGRAM TIME RUN OUT (&00) (&01) (&02)(B) Routing code: U Weight: 70

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 NO-CPU-LIMIT option in the user catalog entry if possible.

UDS0231

UDS ERROR: I/O ERROR ON REALM (&00). NO MORE TRANSACTIONS WILL BE STARTED. (&01) (&02)(B) Routing code: U Weight: 70

UDS0232

UDS TASK ABNORMALLY ENDED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS ERROR: CATALOG FILE WRONG (&01) (&02) (&03)(B) Routing code: U Weight: 70

UDS0234

START OF SERVERTASK FAILED (&01) (&02) (&03)(B) Routing code: U Weight: 70

Meaning
Start of a server task of the independent DBH failed.

Response
Check messages of mastertask and logging of the batch job which starts the server task

UDS0236

UDS USER ERROR: NUMBER OF SUBSCHEMAS EXHAUSTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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.

UDS0237

UDS USER ERROR: THE GIVEN TASKLIB IS NOT SHAREABLE. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Make library shareable.

UDS0238

UDS USER ERROR: PASSWORD MISSING FOR REALM (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0239

UDS COLD START IS EXECUTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0240

UDS WARM START IS EXECUTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0241

UDS TERMINATION INITIATED ON (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0242

UDS USER ERROR: UDS NOT LOADED FOR CONFIGURATION (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: NUMBER OF TRANSACTIONS EXHAUSTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS DBH ABNORMALLY DOWN (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Restart UDS/SQL.

UDS0245

UDS TRANSACTION HAS BEEN CANCELLED DUE TO DATABASE STATUS (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The transaction has been cancelled by UDS/SQL.
(&00): most recent database status of the DML statement that caused the cancellation. The database status may be internal and not described in the manual.

UDS0246

UDS DVS-ERROR (&00) IN UDS CONNECTION (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Take dump.

UDS0247

UDS USER ERROR: UDS CONNECTION CAN’T GET NAME OF (&00). SET-FILE-LINK COMMAND CORRECT? (&01) (&02) (B) Routing code: U Weight: 70

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

UDS USER ERROR: ACTION IMPOSSIBLE DUE TO PREVIOUS ERRORS. PROGRAM TERMINATED. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Correct error(s) in program.

UDS0249

UDS COMMANDS TO TSN (&00) PLEASE. (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Issue UDS/SQL command to master task.

UDS0250

UDS IMMEDIATE TERMINATION WANTED? (Y=YES/N=NO) (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Question following DAL command %TERM.

Response
Y: the UDS/SQL session is aborted. The database is inconsistent and must be restarted with a warm start.

N: the %TERM command is ignored.

UDS0251

UDS DBH DOWN (&00) (&01) (&02)(B) Routing code: U Weight: 70

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): diagnostic information.

Response
Restart UDS/SQL.

UDS0252

UDS ERROR IN TRANSACTION (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning

(&00):	10-digit:	Global TA ID
	8-digit:	Program name
	4-digit:	TSN.

UDS0253

UDS WARNING: REGISTERS ARE PROBABLY CHANGED BY OTHER SUBSYSTEM (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: IN UTILITY SESSION NO USER PROGRAM IS ALLOWED. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
DIAG.

UDS0255

UDS USER ERROR: IN USER SESSION NO UTILITY PROGRAM IS ALLOWED. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS SESSION CONTINUE (Y/N)? (&00) (&01) (&02)(B) Routing code: U Weight: 90

Meaning
Continuation after a serious error. The transaction is aborted.

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

UDS0257

UDS DUMP WANTED (Y/N)? (&00) (&01) (&02)(B) Routing code: U Weight: 90

Meaning
Continuation message following UDS/SQL system crash.

Response
Y: Dump is generated
N: Dump is suppressed.

UDS0258

CANCEL/ROLLBACK INITIATED FOR TRANSACTION (&00) (&01) (&02)(B) Routing code: U Weight: 70

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 databases can be used for retrieval. The DBH marks the database(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 database(s) as inconsistent.
(&01) (&02): diagnostic information.

UDS0259

PROGRAM ERROR (&00) AT LOCATION (&01) IN UDS USER PROGRAM (&02)(B) Routing code: U Weight: 70

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

Response
Correct program.

UDS0260

PROGRAM TIME RUNOUT FOR UDS USER PROGRAM (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

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

UDS0261

UDS USER PROGRAM ABNORMALLY ENDED. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS ERROR: CANCEL/ROLLBACK FOR TRANSACTION (&00) NOT SUCCESSFUL. (&01) (&02)(B) Routing code: U Weight: 70

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

UDS ACCESS VIA CALL DML NOT POSSIBLE DURING THIS SESSION (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Error on linking UDS/SQL server tasks with the SSITAB pool. It is not possible to access
UDS/SQL databases 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 too small, this space must be expanded, or the session must be restarted with smaller values for PP BUFFER-SIZE, PP SERVERTASK, PP TRANSACTION, and PP SIP-SIZE. Otherwise, this is a UDS/SQL internal error for which a dump is required, and the session can be continued.

UDS0264

ERROR IN STXIT ROUTINE. UDS USER PROGRAM WILL BE TERMINATED IMMEDIATELY. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Take dump.

UDS0265

UDS TRANSACTION IDENTIFICATION IN USER PROGRAM INCORRECT (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

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

UDS0266

UDS WARNING: ENTRY USERSTIX IS NOT SUPPORTED IN UDS VERSION (&00) (&01) (&02).(B) Routing code: U Weight: 70

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

UDS USER ERROR: DML STATEMENT REJECTED, SINCE ANOTHER ONE IS ACTIVE IN UDS. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Check program (possible error in user STXIT routine).

UDS0268

UDS WARNING: UDS STXIT ROUTINE (SCSXUSER) CANNOT BE LINKED. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: VERSION DIFFERENCE FOR (&00). (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: THE SET-FILE-LINK COMMAND IS MISSING OR DOES NOT CONTAIN A VALID CONFIGURATION NAME (&00) (&01) (&02) (B) Routing code: U Weight: 70

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

Response
Restart the session using the correct SET-FILE-LINK-command or an available database.

UDS0271

UDS APPLICATION STOPPED BY COMMAND (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The application has been stopped by the specified command.

UDS0273

UDS WARNING: PP SERVERTASK IS GREATER THAN PP TRANSACTION. USED IS VALUE OF PP TRANSACTION. (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
A larger value was specified for PP SERVERTASK than for PP TRANSACTION.
The value for PP SERVERTASKS is reduced to the value of PP TRANSACTIONS.
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 the number of TRANSACTIONS.

UDS0274

UDS BKPT WANTED (Y/N)? INTERRUPT REGISTERS WILL BE LOADED. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS DATABASE COULD STILL BE CLOSED (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The database could be closed successfully despite the previous errors.

UDS0277

UDS ERROR ON PARAMFILE (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
(&01) may contain the following internal message numbers (see "Explanation of the message text format"):

045

Meaning
OPEN of load parameter file unsuccessful.

Response
Check load parameter file.

046

Meaning
Load parameter file locked.

Response
Check the load parameter file.

048

Meaning
SYSFL macro on load parameter unsuccessful.

Response
Check the load parameter file.

UDS0278

UDS STXIT ROUTINE CANNOT BE DEFINED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Check BS version.

UDS0279

UDS USER PROGRAM TERMED WITHOUT FINISH/COMMIT;CANCEL/ROLLBACK IS GENERATED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: MAXIMUM NUMBER OF USERTASKS REACHED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: ILLEGAL CONFIGURATION NAME (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning

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

Response
Check the generation of the configuration.

UDS0283

UDS USER ERROR: USERINF PARAMETERS WRONG OR MISSING (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Find and correct error in application program.

UDS0284

UDS USER ERROR: NO DSCEXT ROUTINE DEFINED (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
DSCEXT routine for CALL DML missing.

Response
Link DSCEXT routine and restart application program.

UDS0285

PLEASE CHECK TSN OR UTM APPLICATION (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS WARNING: UDS CANNOT RUN AS TRANSACTION SYSTEM OR DEACTIVATION OPTION IS NOT ALLOWED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS SESSION RESTART WITH WRONG DB CONFIGURATION. CORRECT DB CONFIGURATION FOLLOWING: (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS DBNAME = (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
(see UDS0290)

UDS0292

UDS SESSION RESTART WITH WRONG AREA CONFIGURATION OF (&00). COMPARISON OF AREA CONFIGURATION FOLLOWING: (&01) (&02)(B) Routing code: U Weight: 70

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

UDS AREA REFERENCE (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
(see UDS0292).

UDS0294

UDS SESSION RESTART WITH CHANGED VALUE OF PP TRANSACTION. CORRECT VALUE IS: (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Execute restart with the specified PP TRANSACTION value.

UDS0295

UDS SESSION RESTART WITH CHANGED VALUE OF PP LOG. CORRECT VALUE IS: (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: VALIDATION DATES IN SUBSCHEMA (&00) AND SCHEMA DO NOT MATCH (&01) (&02)(B) Routing code: U Weight: 70

Meaning

The validation date in the subschema differs from that in the schema for the database.
(&00): subschema name.
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.
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.
(&00): subschema name.
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.
(&00): subschema name.

Response

Recompile subschema. Recompile, relink and rerun application program.
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.
Use the correct UDS/SQL version (>= V2.5).
Use the correct UDS/SQL version (>= V2.9).

UDS0297

UDS USER ERROR: VALIDATION DATES IN SUBSCHEMA (&00) AND DML STATEMENT DO NOT MATCH (&01) (&02)(B) Routing code: U Weight: 70

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

UDS AMBIGUOUS SUBSCHEMA NAMES, STARTING WITH (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Ambiguous 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 databases if possible). This might require the disconnection of the databases blocking a subschema due to ambiguous subschema names; a subschema name can only be changed by deletion an recompilation.

UDS0299

VALIDATION DATES: (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0300

UDS USER ERROR: INSUFFICENT COMMON MEMORY (&00) (&01) (&02)(B) Routing code: U Weight: 70

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 values for the TRANSACTION load parameters or DBNAME.

UDS0301

MEMORY OVERFLOW: FIND7SE MADE SEQUENTIAL (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS AMBIGUOUS DATABASE NAME WITHIN THIS CONFIGURATION (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Use only databases with different names in a configuration.

UDS0307

UDS >>> (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS ERROR ON READING HASH PROCEDURES (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS WARNING: (&00) ON STATUSFILE (&01) (&02)(B) Routing code: U Weight: 70

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 be taken can be found in the
’System Messages’ brochure. Otherwise, end the DB-DC session. Reset the DC application to a consistent state. Create two new status files.

Restart the DB-DC session.

UDS0314

UDS USER ERROR: RESTART WITH WRONG TYPE OF DBH (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS WARNING: PP OUT OF RANGE, HAS BEEN MODIFIED. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Alter PP statement, if necessary.

UDS0316

DAL VALUE OUT OF RANGE, VALUE MODIFIED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0317

UDS USER ERROR: ILLEGAL NUMBER OF DATABASES. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Repeat initialization with corrected PP file.

UDS0318

UDS WARNING: PP MAXDB CHANGED TO ACTUAL NUMBER OF DATABASES. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Alter PP file, if necessary.

UDS0319

UDS USER ERROR: UNCORRECTED ERROR IN PROGRAM PARAMETERS (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Correct PP file. Repeat initialization.

UDS0320

UDS USER ERROR: NAME OF PLITAB MODULE (&00) IS INVALID. (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The name of the KDBS-PLITAB 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

UDS USER DUMP WANTED (Y/N)? (&00) (&01) (&02)(B) Routing code: U Weight: 90

Meaning
Errored application program behavior or ABEND.

Response
Y: Dump is generated
N: Dump is suppressed.

UDS0322

UDSDUMP V(&00) READY (&01) (&02)(B) Routing code: U Weight: 70

Meaning
C.UDSDUMP is loaded and ready.

UDS0323

UDSDUMP NOT ENOUGH CLASS 6 MEMORY AVAILABLE TO READ DUMPFILE (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSDUMP FILENAME REJECTED: (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSDUMP (&00) OF FILE (&01) IN ERROR (&02) (&03)(B) Routing code: U Weight: 70

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

UDSDUMP: SPECIFIED TABLE NOT PRESENT (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0327

UDS USER ERROR: MAXIMUM NUMBER OF SQL SESSIONS REACHED (&00) (&01) (&02).(B) Routing code: U Weight: 70

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

UDS USER ERROR: REPLY FOR SQL-DML IMPOSSIBLE (&00) (&01) (&02).(B) Routing code: U Weight: 70

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

UDSDUMP TIME RUNOUT (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The specified program run time has elapsed.

Response
Repeat UDSDUMP run with increased program run time.

UDS0330

UDSDUMP FILE IS EMPTY: (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Enter END command or name of a correct file.

UDS0331

UDSDUMP FILE IS NO PRIMARY DUMPFILE: (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSDUMP LAYOUT OF FILE (&00) HAS WRONG VERSION: (&01) (&02)(B) Routing code: U Weight: 70

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

UDSDUMP (&00) ERROR (&01) (&02)(B) Routing code: U Weight: 70

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

UDSDUMP DUMPFILE NOT COMPLETE, EDIT PARAMS WILL BE IGNORED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSDUMP COMMAND ’(&00)’ IN ERROR (&01) (&02)(B) Routing code: U Weight: 70

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

UDSDUMP NO EDIT CMD PRECEDING END CMD. STOP WITHOUT ANY EDITING (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSDUMP EDITING STARTED, PLEASE WAIT (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSDUMP NORMAL END (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0339

UDSDUMP PROGRAM ERROR (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS ABNORMAL END (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0341

UDS DUMPFILE WRITTEN: (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0342

UDS USER ERROR: (&00) IS NOT SUPPORTED BY THE GIVEN VERSION OF UDS (&01) (&02).(B) Routing code: U Weight: 70

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 compatible.
(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

UDS ERROR (&00) ON WRITE OF DUMPFILE (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: DSCEXT HAS AN INCORRECT RMODE (&00) (&01) (&02). (B) Routing code: U Weight: 70

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

UDS USER ERROR: C.UDSSUB IS NOT SHARABLE (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: C.UDSSUB MISSING (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS ADMINISTRATION: (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Change of status or error in UDS/SQL DCAM administration.

(&00) may contain the following internal values:

APP.NAME=name

Meaning
DCAM application name opened.
Connection to DCAM administration possible.

COMMEND=code

Meaning
Forced end of DCAM application; for cause, see COMMEND contingency
(DCAM manual “Program Interfaces“); code=x’FFFFFFFF’: internal cause;
UDS/SQL attempts to reopen the connection independently.

LOGON=name

Meaning
Application/terminal has set up DCAM connection to UDS/SQL administration.

LOSCON=code

Meaning
Loss of connection; for cause, see LOSCON contingency (DCAM manual “Program Interfaces“)

LOSCON=name or DISCONN.=name

Meaning
Application/terminal name has broken the connection to DCAM administration.

macro=code

Meaning
Error in DCAM or SOLSIG
macro: SOLSIG/Y....... (DCAM macro name)
code : Return code of the macro

Response
According to the return code (see DCAM manual “Macros“).

NEG.TACK=code

Meaning
Negative transport acknowledgment from the DCAM connection, possibly due to a temporary malfunction in the link to the administration task.

REJ.LOGON=name

Meaning
Connection request from application/terminal name was rejected (only one connection
permitted/password invalid).

Response
Enter correct password.

UDS0348

UDS CANCEL ALL TRANSACTIONS STARTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0349

UDS USER ERROR: (&00)-CALLS ARE ONLY POSSIBLE IN AMODE=24 (&01) (&02).(B) Routing code: U Weight: 70

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

UDS SC/DSA ERROR (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS NORMAL SESSION TERMINATION INITIATED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Start new session after error has been removed.

UDS0352

UDS FOLLOWING REACTION AVOIDS DAMAGE TO DATABASE (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Correct error, then START-UDS.

UDS0353

UDS CONSISTENCY ERROR. (&00) INCONSISTENT. (&01) (&02)(B) Routing code: U Weight: 70

Meaning
UDS/SQL has detected an error in the consistency of data of the file (&00).

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

The time stamps in continuation lines must be interpreted as UTC time. (&00) may contain the following values:

log-filename

Meaning
alog-filename: Name of the ALOG file, taken from the tables.

realm-filename

Meaning
realm-filename: File name of the realm from the associated database.

CONS-MSG: ACT-CPKT-ERROR: (DDDDDDD/AAAAAAA)

Meaning

`DDDDDDD:`	Expected 7-digit value of the CKPT-ID of the AFIM file, taken from the tables.
`AAAAAAA:`	Actual 7-digit value of the CKPT-ID of the AFIM file, taken from the AFIM bottom page.

The indicated values of the CKPT-ID of the AFIM file differ.
(Only relevant for versions < UDS/SQL V1.2)

CONS-MSG: AFIM-BPG-NAME: ABPG-name

Meaning
ABPG-name: Name of the AFIM file, taken from the AFIM bottom page. The name of the AFIM file provided differs from the expected name.
(Only relevant for versions < UDS/SQL V1.2)

CONS-MSG: AK0-AKN-DIFFERENCE

Meaning
Act-Key-0 and Act-Key-N of the realm differ.

CONS-MSG: AK0-REALM-NAME: AK0-realmname

Meaning
AK0-realmname: Realm name from the Act-Key-0 of the realm. The realm names in DBDIR and in the Act-Key-0 differ.

CONS-MSG: ALOG-BACK-UP-DATA-ERROR: (AAAAAAAAAAAAAA/DDDDDDDDDDDDDD)

Meaning

`AAAAAAAAAAAAAA:`	Actual value of the BACK-UP-DATA in the ALOG file.
`DDDDDDDDDDDDDD:`	Expected value of the BACK-UP-DATA for the ALOG file, taken from the DBDIR

The indicated BACK-UP-DATA values differ.

CONS-MSG: ALOG-CKPT-TIME-ERROR: (AAAAAAAAAAAAAA/DDDDDDDDDDDDDD)

Meaning

`AAAAAAAAAAAAAA:`	Time stamp upon leaving the last checkpoint, taken from the ALOG file.
`DDDDDDDDDDDDDD:`	Time stamp upon leaving the last checkpoint, taken from the DBDIR

The indicated time stamp values differ.

CONS-MSG: ALOG-SEQU-NR-ERROR: (AAAAAAAAA/DDDDDDDDD)

Meaning

`AAAAAAAAA:`	ALOG file sequence number, taken from the ALOG file.
`DDDDDDDDD:`	ALOG file sequence number, taken from the DBDIR

The indicated values of the ALOG file sequence numbers differ.

CONS-MSG: BACK UP DATA ERROR: (DDDDDDDDDDDDDD/RRRRRRRRRRRRRR)

Meaning

`DDDDDDDDDDDDDD:`	Expected value of BACK-UP-DATA for the realm, taken from the CONSISTENCY record of the database.
`RRRRRRRRRRRRRR:`	Actual value of BACK-UP-DATA in the Act-Key-0 of the realm.

The indicated values of BACK-UP-DATA for the realm differ.

CONS-MSG: BLOCK_FORMAT_ERROR

Meaning
The page size of the realm is incompatible with the database.

CONS-MSG: CREATE-DATA-ERROR: (DDDDDDDDDDDDDD/RRRRRRRRRRRRRR)

Meaning

`DDDDDDDDDDDDDD:`	DBDIR creation date.
`RRRRRRRRRRRRRR:`	Realm creation date.

The creation date of the realm and the creation date of the DBDIR differ.

CONS-MSG: DBTT-EXT-PENDING-ERROR

Meaning
The indication of a running online DBTT extension in the realm’s AK0 is inconsistent.

CONS-MSG: EXTENSIBILITY-ERROR

Meaning
The specifications relating to online extensibility in the realm’s AK0 are inconsistent.

CONS-MSG: GLOBAL-EXTENT-ERROR

Meaning
The specifications relating to the DB-LAYOUT-VERSION and extension status in the DBDIR’s AK0 are inconsistent.

CONS-MSG: INCOMPLETELY-UPDATED-ONLINE-COPY

Meaning
An online copy was not updated as far as the last required ALOG file.

Response
Update using all required ALOG files (these can be identified using the BMEND function SHOW-LOG-INFORMATION).

CONS-MSG: LAST-ALOG-FILE-ERROR

Meaning
The current ALOG file has not been identified as the last ALOG file.

Response
If necessary, reverse any illegal user manipulation/operating errors involving the indicated file; otherwise DIAG.

CONS-MSG: LOCAL-EXTENT-ERROR

Meaning
The specifications relating to the DB-LAYOUT-VERSION and extension status in the realm’s AK0 are inconsistent.

CONS-MSG: REALM-CONFLICT BEFORE UPDATE

Meaning
The database was found to be in an inconsistent state before an update, possibly due to an unauthorized update by a second entity at the same time. An inconsistent read access operation was performed on the database since the last checkpoint.

CONS-MSG: REALM-CONFLICT DURING UPDATE

Meaning
The database was rendered inconsistent during an update, possibly due to an unauthorized update by a second entity at the same time. An inconsistent access operation was performed on the database since the last checkpoint.

CONS-MSG: REALM-EXT-PENDING-ERROR

Meaning
The indication of a running online realm extension in the realm’s AK0 is inconsistent.

CONS-MSG: SYSTEM-BREAK-ERROR ALOG

Meaning
The ALOG file has been marked inconsistent in the ALOG bottom page although the database is consistent.

CONS-MSG: SYSTEM-BREAK-ERROR REALM

Meaning
The realm has been marked inconsistent in the Act-Key-0 of the realm, although no inconsistent database has been connected.

UDS0354

UDS ALOG CHECKPOINT FOR (&00) (&01) (&02)(B) Routing code: U Weight: 99

Meaning
An ALOG checkpoint for the indicated database is to be written. The results and the values generated by this operation are given in a continuation line.
The time stamps in continuation lines must be interpreted as UTC time.

The continuation lines may contain the following values:

AFIM-CKPT ccccccc: AFIM-NR: nnnnn AVAILABLE NOW. ACC-SYS: UPD.

Meaning
The AFIM checkpoint ccccccc for the indicated database has now been completed with the connection of the new AFIM file nnnnn. UDS/SQL now allows updating accesses to the database. (Only relevant for versions < UDS/SQL V1.2)

`ccccccc:`	Current checkpoint ID of the database = End checkpoint ID of old AFIM file. = Start checkpoint ID of new AFIM file.
`nnnnn:`	Sequence number of AFIM file.

AFIM-CKPT ccccccc: BOOKED.

Meaning
AFIM checkpoint ccccccc for the indicated database has been booked only as its AFIM log pool is not online at the moment (due to retrieval option). The AFIM checkpoint is effected with the next connection of the database without retrieval option.
(Only relevant for versions < UDS/SQL V1.2)

ALOG-CKPT cccccccccccccc: ALOG-NR nnnnnnnnn N O T AVAILABLE. ACC-SYS: RTR.

Meaning
Connection of the new ALOG file nnnnnnnnn, as part of generating ALOG checkpoint cccccccccccccc for the database concerned, has failed. In order to prevent the loss of afterimages, UDS/SQL limits access to the database to retrieval.

Response
Remove cause of rejection of ALOG file connection (e.g. by creating new ALOG files) and initiate completion of the ALOG checkpoint using /SEND-MSG TO=PROGRAM,
MSG=C’CHECKPOINT DB=xxx’ and /SEND-MSG TO=PROGRAM, MSG=C’PERFORM’

ALOG-CKPT cccccccccccccc: CKPT ALREADY EXISTING.

Meaning
The ALOG checkpoint cccccccccccccc for the indicated database has already been written.

ALOG-CKPT cccccccccccccc: FIXED (ALOG-NR: nnnnnnnnn,START-CKPT: ssssssssssssss)

Meaning
The ALOG checkpoint was written with disconnection of the old ALOG file nnnnnnnnn whose start checkpoint is ssssssssssssss.

Response
Realm copies of the database can be updated using the disconnected ALOG file if required.

ALOG-CKPT cccccccccccccc: FIXED (ALOG-NR: nnnnnnnnn D E F E C T I V E).

Meaning
A changeover to a new ALOG file with start checkpoint cccccccccccccc has been effected for the database concerned. The old ALOG file nnnnnnnnn is defective and cannot be used.

Response
Counteract gap in ALOG logging for the database concerned by generating new realm copies.

ALOG-CKPT OMITTED: DB WITHOUT ALOG-LOGGING.

Meaning
The ALOG checkpoint for the indicated database is suppressed as it is processed without ALOG logging.

UDS0355

UDS BACKOUT CHECKPOINT FOR (&00) (&01) (&02)(B) Routing code: U Weight: 70

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 time stamp (’TIMESTAMP IS...’) as well as the checkpoint IDs of the participating databases (in subsequent message lines).

UDS0356

UDS EXECUTION OF ORDERS FOR (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

RLOG RESERVE IS USED FOR CONFIGURATION (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS DROP OF (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
If necessary, remove indicated error; repeat drop request.

UDS0359

UDS (&00) BECAME UNPROCESSABLE (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Check if the situation can be remedied by repair.

UDS0360

UDS FATAL FILE FAILURE: (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
See meaning.

UDS0361

UDS BACKOUT FILE (&00) CLOSED (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0362

UDS BSECURE EXCLUSIVE RIGHTS ON DB: (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
A BSECURE exclusive right was discovered 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

UDS SLF INCONSISTENT. ERRCODE: (&00) (&01) (&02)(B) Routing code: U Weight: 70

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 database 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 the password).

UDS0364

UDS CATALOG INCONSISTENT. ERRCODE: (&00) (&01) (&02)(B) Routing code: U Weight: 70

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 database concerned. Cause: DBH programming error or user manipulation.

Response
DIAG or reverse user manipulation.

UDS0365

LAYOUT VERSION ERROR: (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The specified database 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

UDS SESSION RESTART WITH CHANGED VERSION. CORRECT VERSION IS: (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: NUMBER OF REALMS FOR (&00) EXCEEDING UPPER LIMITS (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Check the database structure.

UDS0368

UDS USER ERROR: DBDIR OF (&00) NOT AVAILABLE (&01) (&02)(B) Routing code: U Weight: 70

Meaning
DBDIR of the specified database 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

UDS BACKOUT LOGGING (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
At a session restart, UDS/SQL has detected that a previously failed backout file:

(&00)= SWITCHED OFF: ... has not been replaced by an unimpaired new backout file.
Backout logging thus remains switched off.
(&00)= RESUMED: ... has been replaced by an unimpaired new backout file. Backout logging is thus resumed.

UDS0370

UDS USER ERROR: PP LOG MISSING WHEN BACKOUT LOGGING IS USED. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: NUMBER OF PASSWORDS EXCEEDING UPPER LIMIT: (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
More than 100 passwords have been specified.

Response
Correct PP FILE, if necessary.

UDS0372

UDS RLOG FILE (&00) MAY BE REPAIRED NOW (&01) (&02)(B) Routing code: U Weight: 70

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

Response
The message serves only as a warning.

UDS0373

UDS ADMINISTRATION OF DISTRIBUTION IMPOSSIBLE DUE TO PREVIOUS ERRORS (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSCODE STARTING (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The C.UDSCODE utility routine has been started

UDS0375

UDSCODE COMMON MEMORY POOL (&00) CREATED (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0376

UDSCODE NORMAL END (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The C.UDSCODE utility routine has been terminated normally.

UDS0377

UDSCODE VERSION DIFFERENCE FOR (&00) (&01) (&02)(B) Routing code: U Weight: 70

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 the TASKLIB command.

Create consistent module library.
Restart program.

UDS0378

UDSCODE MODULE (&00) NOT FOUND (&01) (&02)(B) Routing code: U Weight: 70

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

UDSCODE COMMON MEMORY POOL (&00) ALREADY EXISTS (&01) (&02)(B) Routing code: U Weight: 70

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

UDSCODE UNRECOVERABLE ERROR (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
An unrecoverable 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) may contain the following values:

ABEND RC = iw

Meaning
C.UDSCODE has been terminated abnormally by means of LOGOFF, START-EXECUTABLE-PROGRAM, LOAD-EXECUTABLE-PROGRAM, ABEND or CANCEL-JOB.

Response
Take dump.

ENAMP RC

Meaning
The attempt to create the code pool or to link with an existing code pool was rejected.

Response

Check file names for illegal special characters.
Link with existing pool; check if the specified file name is identical with that specified at code pool creation (suffix!); enter correct SET-FILE-LINK command with LINK-NAME=UDSCODE and start again.
Check if code pool already exists with another DBH type.
Check if a code pool created by another version already exists.
Otherwise dump.

GTMAP RC

Meaning
The request for user memory map was not honored.

Response
Take dump.

MEMO RC = 00

Meaning
User address space too small to accept code pool.

Response
Inform system administrator; dump.

MEMO RC = 01

MEMO RC = 03

Meaning
A different task attempted to create the code pool; the loading of modules exceeded the time limit.

Response
Terminate the other task and restart C.UDSCODE; dump.

MEMO RC = 02

Meaning
A different task attempted to create the code pool, but was terminated prematurely.

Response
Restart C.UDSCODE; dump.

MSG RC

Meaning
Message output failed.

Response
Take dump.

P-ERR RC = iw AT LOCATION addr

Meaning
P error occurred at indicated address during the run of the C.UDSCODE utility routine.

Response
Take dump.

STXIT RC

Meaning
Error at STXIT routine creation.

Response
Take dump.

UNLOD RC

Meaning
Module unload failed.

Response
Take dump.

UDS0381

UDSCODE ABNORMAL END (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSCODE USER ERROR (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSCODE COMMAND REJECTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Enter correct SEND-MESSAGE command.

UDS0384

UDS ERROR ON CODEPOOL (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS UNRECOVERABLE ERROR ON CODEPOOL (&00) (&01) (&02)(B) Routing code: U Weight: 99

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.

(&00) may contain the following values:

DBH ?

Meaning
A code pool with a different DBH type already exists.

Response
Start UDS/SQL or UDSCODE with the correct DBH.

ENAMP RC

Meaning
The attempt to create the code pool or to link to an existing pool was rejected.

Response

Check file names for illegal special characters.
Link with existing pool; check if the specified file name is identical to that specified at log pool creation (suffix!); enter correct SET-FILE-LINK command with LINK-NAME=UDSCODE and restart.
Check if code pool already exists with another DBH type.
Check if a code pool created by another version already exists.
Otherwise dump.

GTMAP RC

Meaning
The request for user memory map has not been honored.

Response
Take dump.

MEMO RC = 00

Meaning
User address space too small to accept code pool.

Response
Inform system administrator; dump.

MEMO RC = 01

Meaning
A different task attempted to create the code pool; loading of the modules exceeded the time limit.

Response
Terminate the other task and restart UDS/SQL; dump.

MEMO RC = 02

Meaning
A different task attempted to create the code pool, however it was terminated prematurely.

Response
Restart C.UDSCODE; dump.

MEMO RC = 03

Meaning
A different task attempted to create the code pool. The UDS/SQL modules have been loaded, but installation time has exceeded the limit.

Response
Terminate the other task and restart UDS/SQL; dump.

UNLOD RC

Meaning
Module unload failed.

Response
Take dump.

UDS0386

UDS SESSION CONTINUES (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSCODE COMMAND ACCEPTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0388

FILE (&00) INDICATES WARMSTART POSSIBLE FOR FOLLOWING DB(S) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0389

UDS WARNING: INFORMATION IN STATUS FILE WILL POSSIBLY BE LOST (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS WARNING: PP (&00) NOT SUITABLE FOR THIS SESSION; WILL BE CHANGED BY UDS (&01) (&02) (B) Routing code: U Weight: 70

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

UDS ERROR ENABLING TRANSFER POOL FOR UDS-D (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS-D NOT AVAILABLE DURING THIS SESSION (&00) (&01) (&02)(B) Routing code: U Weight: 70

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.

(&00) contains the following value:

ENTR, cpu-limit, job-class

Meaning
CPU limit is too small for the job class. The enter job for the UDSCT cannot be started.

NDIP

Meaning
A UDS-D-specific DAL command cannot be processed, since UDS-D is not available.

UDS0393

UDS ROLLS BACK ALL TRANSACTIONS CONCERNED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0394

UDS TABLES INCONSISTENT DUE TO ABNORMAL TERMINATION OF A USERTASK (&00) (&01) (&02) (B) Routing code: U Weight: 70

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) database(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 database(s).

UDS0395

UDS ERROR (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

FOLLOWING RLOG FILE IS RETAINED FOR POSSIBLE STATUS QUERIES FROM UDS-D (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: LOADED DBH DOES NOT PROCESS SQL-DML (&00) (&01) (&02).(B) Routing code: U Weight: 70

Meaning
The loaded DBH cannot process SQL DML.

Response
Terminate the DBH and load an SQL-compatible DBH.

UDS0398

UDS WARNING: ENTRY USERSTIX NOT SUPPORTED IN FUTURE VERSIONS OF UDS (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

CHANGING OF AMODE IN A LINKEDIN-SESSION IS NOT ALLOWED (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
All DML orders within a LINKEDIN session must be sent to the DBH in the same addressing mode.

UDS0400

UDS ADMINISTRATION ERROR: MASTER TASK NOT BATCH TASK (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS ADMINISTRATION ERROR: SECOS NOT AVAILABLE (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS WARNING: UDS-D NOT PERMITTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0404

UDS ERROR: (&00) ON SAT CALL (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: TIAM APPLICATIONS NOT PERMITTED IN THIS CONFIGURATION (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS WARNING: LOCAL ADMINISTRATION NOT PERMITTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Administration via UDSADM.

UDS0408

UDS ADMINISTRATION ERROR: DAL COMMAND (&00) VIA /SEND-MSG NOT PERMITTED (&01) (&02)(B) Routing code: U Weight: 70

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

UDS SYSTEM ERROR: TRANSFER CONTAINER MANAGEMENT ERROR (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The session is terminated.

Response
Take Dump. Restart UDS/SQL.

UDS0410

UDS-APPLICATION TERMINATED WITH (&00) DMLS (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0500

UDSMON COMMAND ACCEPTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0501

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

UDS0502

UDSMON NORMAL TERMINATION (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0503

UDSMON INVALID CONFIGURATION NAME OR UDS NOT LOADED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSMON SYSTEM ERROR: CONNECTING TO DISTRIBUTION POOL UNSUCCESSFUL (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Take dump.

UDS0505

UDSMON NO LONGER WAITS FOR UDS INITIALIZATION (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSMON UDS-D NOT LOADED. NO UDS-D MASKS WILL BE DISPLAYED (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0507

UDSMON ENTER ANY CHARACTER TO CONTINUE PROGRAM (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Enter any character and DUE to continue monitor processing.

UDS0508

UDSMON OUTPUT MEDIUM INCORRECT. OUTPUT MEDIUM CHANGED TO LIST (L) (&00) (&01) (&02) (B) Routing code: U Weight: 70

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

UDS0509

UDSMON CONFNAME COMMAND MISSING (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSMON SEND-MSG COMMAND NOT POSSIBLE AT PRESENT. RETRY COMMAND LATER (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
An SEND-MSG command is already awaiting processing.

UDS0511

UDSMON COMMAND NOT ALLOWED IN PREDIALOG (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0512

UDSMON COMMAND ONLY ALLOWED IN PREDIALOG (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0513

UDSMON COMMAND NOT ALLOWED FROM CONSOLE (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0514

UDSMON OPEN ERROR ON MONITOR FILE (&00) (&01) (&02).(B) Routing code: U Weight: 70

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

Response
Check file and restart output to the file.

UDS0515

UDSMON CLOSE ERROR ON MONITOR FILE (&00) (&01) (&02).(B) Routing code: U Weight: 70

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

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

UDS0516

UDSMON WRITE ERROR ON MONITOR FILE (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Check file; restart output to the file.

UDS0517

UDSMON ERROR WHEN CREATING MONITOR FILE (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

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

UDS0518

UDSMON USER ERROR: UNKNOWN COMMAND. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSMON USER ERROR: INTERVAL FOR OUTPUT MEDIUM NOT CORRECT (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSMON USER ERROR: ILLEGAL MONITOR OUTPUT MEDIUM (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Repeat entry with corrected parameters.

UDS0521

UDSMON USER ERROR: MASK TYPE NOT CORRECT (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Repeat entry with corrected parameters.

UDS0522

UDSMON MACRO ERROR (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0523

UDSMON SYSTEM ERROR: STCK NOT SUCCESSFUL, NO TIMER INTERVAL POSSIBLE (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0524

UDSMON SYSTEM ERROR: PROGRAM ERROR (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Take dump.

UDS0525

UDSMON ABNORMALLY TERMINATED (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The monitor has terminated due to an error.

Response
Restart monitor.

UDS0526

UDS NORMALLY TERMINATED. UDSMON TERMINATION INITIATED (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0527

UDS ABNORMALLY TERMINATED. UDSMON TERMINATION INITIATED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0528

UDSMON NO TRACE ACTIVE, COMMAND IGNORED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0529

UDSMON CLOSE OF TRACE FILES STILL ACTIVE. COMMAND REJECTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The trace files are already being closed.

UDS0530

UDSMON SAMPLING STARTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0531

UDSMON NOT PERMITTED UNDER CURRENT SECURITY LEVEL (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0532

UDSMON VERSION DOES NOT MATCH UDS VERSION (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0533

UDSMON USER ERROR: RUNTIME PARAMETER OUTSIDE PERMITTED RANGE (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

Response
Correct and repeat RUNTIME command.

UDS0534

UDSMON INTERNAL OVERFLOW IN COUNTER (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0535

UDSMON THE BS2000 VERSION USED DOESN’T SUPPORT THE TRANSFER OF MONITOR DATA TO OPENSM2 (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0536

UDSMON UDS-SQL MEASUREMENT PROGRAM IN SM2 NOT YET STARTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSMON SM2 GATHERER TASK NOT ACTIVE (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The SM2 gatherer task is not active.

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

UDS0538

UDSMON SUBSYSTEM SM2 NOT ACTIVE (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

FASTPAM NON RESIDENT MEMORY (&00) (&01) (&02)(B) Routing code: U Weight: 50

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).

Response
Depends on (&00).

(&00) may contain the following values:

FASTPAM-PRIVILEGE-MISSING

Meaning
The user ID under which UDS/SQL was started does not have FASTPAM privileges.

Response
Ensure that the corresponding user ID is granted FASTPAM privileges.
See the manual “Database Operation“ for details.

REAL-MEMORY-SHORTAGE

Meaning
The main memory of the system is insufficient to make the memory resident.

Response
Expand the main memory of the system.

USER LIMIT EXCEEDED

Meaning
The amount of resident main memory allocated at program startup is exhausted.

Response
Increase the allocation for resident main memory. See the manual “Database Operation“ for details.

UDS0700

UDS RESOURCE ERROR (&00) (&01) (&02)(B) Routing code: U Weight: 70

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.

Response
Depends on error code (&00).

(&00) may contain the following values:

ACS_ERROR

Meaning
When the indicated file was opened, the file name in the FCB was changed. The file name has probably been defined as an alias by means of the ACS (Alias Catalog Service).

Response
Cancel ACS definition.

ALOG_OVERFLOW

Meaning
DMS could not extend the indicated ALOG file due to a “hard” overflow which prevents further action involving the ALOG file. The space in the ALOG file was insufficient for reaching a consistency point for the database concerned. The DBH deactivates the database concerned in an inconsistent state.

Response
Ensure that the ALOG file can be extended. Then perform a warm start.

BLOCK_FORMAT_ERROR

Meaning

(1)	The block size of the DBDIR is not 2 KB, 4 KB or 8 KB or
(2)	The block size of a realm is not the same as of the DBDIR (in these two cases the cause is usually an operator error while converting the database or the user has changed something) or
(3)	a shared user buffer pool that already exists was specified for a database and it has a different page size than the converted database.

Response

(1) and (2):	Correct the database conversion, possibly using DIAG.
(3):	Specify an appropriate user buffer pool when activating the DB or assign the system buffer pool to the database.

BLOCK_NOT_EXISTING

Meaning
Accessing the indicated page (PAMBNR) on the indicated file was not possible as the page does not exist. It is either outside the file limits or does not logically belong to the file (see “coded file-id”). This is due to a programming error or illegal user manipulation in the file.

Response
Reverse user manipulation or DIAG.

BOT_PAGE_ERROR

Meaning
The contents of the bottom page (see PAMBNR) of the indicated file are invalid. The file can thus not be processed.
Exception: DBSTAT file:The DBSTAT file has previously been

incompletely initialized or
marked as defective and not repaired yet.

Response
Reverse illegal user manipulation, otherwise DIAG.
Exception: DBSTAT file:
Replace indicated DBSTAT file with copy of the duplicate DBSTAT file.

BUFFER_NOT_AVAILABLE

Meaning
The database to be connected requires a system buffer pool with an 8-Kbyte page format, but no such pool has been created.

Response
Repeat the attempt to connect the database, this time specifying an exclusive buffer pool for it, or set up a system buffer pool with an 8-Kbyte page format at session startup.

CMS_ERROR

Meaning
An error is reported for the indicated file by the CMS (Catalog Management System). This error can only occur when ascertaining the availability unit for and RLOG file pair.

Response
Analyse the cause of the error using CMS error code; DIAG if required.

COMMAND_ERROR

Meaning
Above error occurred when the PASSWORD command for BS2000 was entered.

Response
Analyze and remove error using indicated DMS error code. DIAG if required.

DB_FORMAT_ERROR

Meaning
The physical file format of a database file is incompatible with the length of the database pages.
This is usually due to a handling error during database conversion or user manipulation.

Response
Correct the database conversion; DIAG if required.

DMS_ERROR

Meaning
DMS or FASTPAM has reported an error for the indicated file that is probably dependent on time and/or environment and has thus not (yet) caused an irrecoverable corruption of the file contents. In general, the UDS/SQL reaction to this type of error differs from that to HW_ERROR.

Response
Analyze cause of error using DMS or FASTPAM error code; DIAG if required.
If the first four digits of the error code (dddd) are not 0000, then a DMS error is the cause. Analyze the cause of DMS errors using HELP-MSG MSG-ID=DMSdddd, e.g. for error code 054D 00000000 enter HELP-MSG MSG-ID=DMS054D.
If the first four digits of the error code are 0000, then a FASTPAM error is the cause. Analyze the cause of FASTPAM errors based on the last 4 digits (ffff) using
HELP-MSG MSG-ID=DFPffff, e.g. for error code 0000 01400142 enter
HELP-MSG MSG-ID=DFP0142.

A UDS/SQL pubset declaration which does not specify all required pubsets may also cause this message.

FILE_DID_NOT_EXIST

Meaning
From the point of view of the DBH, the indicated file (including its duplicate) does not exist (or is empty).
The following situations are possible:

(1)	The file should exist but does not, and the DBH is not able to create it (e.g. permanent realm).
(2)	The non-existent file does not need to exist because the DBH would normally be able to create it. In reality, this is not possible because the file would have to be created under a user ID other than the configuration user ID, which is not allowed in BS2000 (e.g. a new ALOG file or a DB that is not located under the configuration user ID).
(3)	The file exists, but under a user ID other than the configuration user ID, and is affected by a DMS lock due to a previous session abort. When this file is opened again UDS/SQL can only use the VERIFY function to cancel such locks in its own (i.e. theconfiguration) ID, not in any other ID (e.g. current ALOG file for a database which is notlocated under the configuration user ID).
(4)	The file exists but is not located under the configuration user ID and is not shareable.
(5)	The file exists on a pubset which was not specified in the UDS/SQL pubset declaration.

Response

(1)	Make file (and duplicate) with appropriate contents available again.
(2)	Create file (and duplicate) beforehand in the appropriate user ID.
(3)	Remove lock on file (and duplicate) under the appropriate user ID using the /VERIFY command with specification REPAIR=ABS.
(4)	Use the BS2000 command /MODIFY-FILE-ATTRIBUTES to make the file under the user ID involved shareable.
(5)	Add the pubset concerned to the UDS/SQL pubset declaration, or create the file on a pubset specified in the UDS/SQL pubset declaration.

FILE_ERROR

Meaning
The contents of the indicated file have been corrupted either due to programming error or illegal user manipulation.

Response
Reverse user manipulation or DIAG.

FILE_INCONSISTENT

Meaning
As far as the DBH is concerned, the file pair is inconsistent because the files differ. The following cases are possible:
(1) One file of the indicated file pair exists and the other does not.
(2) One file is not empty while the other file is.
This is either due to illegal user manipulation or a session interrupt during the creation of a file pair.

Response
Reverse user manipulation or replace the missing/empty file with a copy of the non-empty file or make the non-accessible copy shareable, as appropriate.

FILE_INOP

Meaning
An INOP state has been reported for the indicated file (following unsuccessful DMS/operator interaction). The file can thus be assumed to (still) be recoverable but not available at the moment. In general, the UDS/SQL reaction to this type of error differs from that to HW_ERROR.

Response
Remove INOP state with the aid of operating functions.

FILE_LOCKED

Meaning
The indicated file cannot be opened by the DBH because

(1)

it has been opened by other BS2000 tasks and is therefore locked for UDS/SQL.

(2)

it is still affected by a DMS lock (from previous abortion) which cannot be removed by the DBH using the VERIFY command.

(3)

the disk containing the file cannot be accessed at the moment.

Possible causes:

device error
the file is on a private disk which is processed exclusively by another task (BS2000 SETUP SYSTEM or SET DISC command missing).

Response

(1)	Either terminate locking tasks or wait for their normal termination.
(2)	Remove DMS lock with the aid of BS2000 commands.
(3)	Remedy device error or enter missing BS2000 command.

FILE_NOT_SHARED

Meaning
The indicated file has not been made shareable although it is not under the configuration user identification. It can thus not be opened by the DBH.

Response
Make file shareable using BS2000 command /MODIFY-FILE-ATTRIBUTES.

FILE_OVERFLOW

Meaning
The DMS was unable to extend the indicated file, possibly due to insufficient free space in the volume.
Note on the file type ALOG file:
When this return code occurs, the DBH attempts to write a consistency point for the database concerned and to change the ALOG file. In most cases, there is sufficient space in the ALOG file for writing the log record required to reach a consistency point. If it is not possible to reach a consistency point, the return code ALOG_OVERFLOW is subsequently issued.

Response
Take sufficient secondary allocation into account when creating files.

FILENAME_AMBIGUOUS

Meaning

(1)	The name of the indicated file is not unique within the current MPVS environment, i.e. (at least) two files of this name exist in the online public volume sets.
(2)	Too many RLOG files with the indicated time stamp exist for the current warm start (due to illegal user manipulation). In both cases UDS/SQL is unable to determine which othese files is to be used.

Response

(1)	Rename excessive files or disconnect excessive public volume sets.
(2)	Reverse user manipulation.

HW_ERROR

Meaning
An irrecoverable hardware error (e.g. parity error) has been detected in the indicated file, i.e. the file is probably technically defective.

Response
Try to locate the defective part on volume and avoid using it.

INCONSISTENT_ACTKEY

Meaning
The indicated page (see PAMBNR) of the indicated file contains an inconsistent act-key, i.e. the act-key of the page does not match the position of the page in the file. This may be due to a programming error or user manipulation.

Response
DIAG.
RESET-DB if required.

INCONSISTENT_ONLINE-COPY-BIT

Meaning
The online copy bit that is set internally by UDS/SQL for a file (for online recovery) does not match the actual attribute of the file.

Response
The desired online recovery capability for database files may only be changed with the BMEND utility routine. Reverse the bypassing of BMEND.

JOBV_NO_SHARED_JV

Meaning
All 10 job variables have already been created for a shared retrieval DB and have been assigned configuration names which are not suitable for the current DBH. The database variable is not supplied by the current DBH.

JOBV_PERMANENT_ERROR

Meaning
A permanent error in the job variable subsystem was detected.
The session is continued.

JOBV_SYSTEM_ERROR

Meaning
A recoverable error occurred when an attempt was made to assign values to a job variable.Return information (SEC-RC) is also output in the insert.
The first four characters identify the job variable function (e.g. CATJV (X'0004'), SETJV (X'0001'), GETJV (X'0000')). The next four characters contain the return code of the relevant JV SVC. The cause can then be determined and possibly corrected using HELP-MSG MSG-ID=JVSxxxx (xxxx=5th through 8th characters of SEC-RC).
In the case of database and session job variables the session is continued. After the problem has been solved, the session job variable is assigned a value again the next time an event occurs which results in the content of the job variable being changed. After an error has occurred, database job variables are supplied with values again only if the database is attached again.
If a corresponding error occurs during initialization while the pubset declaration variable is being read, the session is terminated as the usage of the job variable which is clearly intended is not possible.

LAST_MAINREF_BLOCKED

Meaning
The last main reference of the DBH has become invalid due to the last error reported. The number of transactions which can be open at the same time (PP TRANSACTION) has been reduced to 0, and continuation of the session is not feasible.

Response
Remove cause of error and restart session.

LM_BS_ERROR

Meaning
The operating system reported an error for the database involved on requesting/releasing the file lock that is used for coordinating database access throughout the configuration. Note that this does not refer to the usual “file locked“ state (cause: The BS2000 function ENQAR or DEQAR responded with an unexpected return code).

Response
Reconnect the database if required, possibly in a new session. If read-only access on the database is sufficient, connect the database with the option SHARED-RETRIEVAL.
If these measures are unsuccessful: DIAG; contact the system administrator, since a BS2000 error is probably involved.

LM_LACK_OF_BS_RESOURCE

Meaning
The operating system reported an internal resource bottleneck for the database involved on requesting/releasing the file lock that is used for coordinating database access throughout the configuration (BS2000 function ENQAR and DEQAR). Note that this does not refer to the usual “file locked“ state.

Response
Reconnect the database if required, possibly in a new session. If read-only access on the database is sufficient, connect the database with the option SHARED-RETRIEVAL.
If these measures are unsuccessful: DIAG; contact the system administrator, since a BS2000 error is probably involved.

LOCK_TIMEOUT

Meaning
The DBH attempted to make the DMS lock the indicated CATALOG file for ten seconds in order to have exclusive access. Another UDS/SQL access system must be locking the CATALOG for an excessively long period.

Response
Find and remove cause of excessively long locking.

MEMORY_OVERFLOW

Meaning
The main memory available for the DBH is not sufficient.
Independent DBH: no further common memory pool can be generated.
Linked-in DBH: class 6 memory exhausted.

Response
Find and remove cause of the lack of memory (e.g. high load parameter values).

NO_BUFFER_FREE

Meaning
The number of buffers required by the DBH exceeds that available in the buffer pool (PP BUFFER-SIZE).

Response
No action is required if the error occurs only sporadically. UDS/SQL counteracts the lack of buffer by terminating the transaction concerned. If the error occurs frequently, the value of load parameter PP BUFFER-SIZE should be increased at the next opportunity.

PASSWORD_ERROR

Meaning
The indicated file is protected by a password which is not known to the DBH. It can thus not be opened.

Response
Submit password to the DBH via load parameter or DAL. Exception: An SLF password other than C’UDS_’ is not transferred to the DBH (for technical reasons) but to BS2000 via
ADD-PASSWORD command.

PP_DMS_ERROR

Meaning
A DMS error occurred when reading DBH load parameters.

Response
Analyze and remove error using DMS error codes.

REALM_OCCUPIED_BY_UTILITY

Meaning
The BMEND utility routine is currently performing recovery measures on the realm.

Response
Wait for the recovery measures to end and then connect the realm, possibly via DAL.

RESTART_CONFLICT

Meaning
The contents of the indicated backout file do not match the current session restart. Continuation would render the file inconsistent.

Response
Either assign correct backout file (processed prior to session abort) and repeat restart, or do without the restart by beginning a new session. Starting a new session would, however, result in a gap in the backout logging.

SAME_AVAILABILITY_UNIT

Meaning
When an RLOG file pair was opened, it was discovered that both the original and the duplicate are to be buffered using the same availability unit of the GS (Global Store).

Response
Modify the GS buffering for one of the public volume sets on which the RLOG original and duplicate are to be stored so that a different availability unit of the GS is used.

UNALLOWED_ROLLBACK

Meaning
The rollback of a user transaction was unsuccessful because not all logging data required was still available. This is due to total failure of the RLOG file or to omission of logging
(PP LOG=NO). The databases rendered inconsistent by this error are indicated in a continuation message.

Response
Consider PP LOG=RLOG-2 as preventative measure and place RLOG files on separate disks.

UDS0701

UDS SUBSYSTEM ERROR (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS PARTIAL FAILURE OF FILE (&00) (&01) (&02)(B) Routing code: U Weight: 70

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.

(&00) contains a file name. The file may be one of the following types:

CATALOG file

Meaning
UDS/SQL immediately disconnects the database involved in order to give the user an opportunity to repair the failed CATALOG file.

Response
Replace the failed CATALOG version with an intact copy of the CATALOG before(!) reconnecting this database to a UDS/SQL access system (including a session restart!).

DBSTAT file

Meaning
The following two scenarios are possible:

(1)	The message refers to the current DBSTAT file of the running session: UDS/SQL continues the session using non-failed file of the DBSTAT file pair.
(2)	The message refers to a DBSTAT file other than the current one: UDS/SQL continues the current operation (warm start or updating of the DBSTAT file) using the non-failed file of the DBSTAT file pair.

Response

(1)	Repair the failed file by replacing it with a copy of the non-failed file before starting or restarting a session under the current configuration name.
(2)	The failed file has to be repaired as under (1) as soon as the DBH has completed the current operation.

RLOG file

Meaning
The following two scenarios are possible:

(1)

The message refers to the current RLOG file of the running session:

As soon as all the update transactions have been completed, UDS/SQL has the databases of the configuration marked consistent and switches to another RLOG file inorder to give the user the opportunity to raise the value for the restart logging to thedesired number (PP LOG).

(2)

The message refers to an RLOG file that is not the current one:

UDS/SQL continues the current operation (warm start or updating of a DBSTAT file)using the non-failed RLOG file.

Response

(1)

If UDS/SQL succeeds in disconnecting the old (obsolete) RLOG file, it is not necessary to repair the failed file. In any case, the user should erase it with ERASE-RLOG. If,however, a session is aborted or a database disconnected in an inconsistent state (an the RLG file may possibly still be required), the failed RLOG file has to be repaired priorto continuing the session or warm starting the database involved. This is accomplishedby replacing the failed file with a copy of the non-failed file. (Original file: without suffix“.SAVE”; duplicate: with suffix “.SAVE”)

(2)

If the RLOG file still exists after this operation, i.e. it has not been invalidated by
UDS/SQL (i.e. deleted or returned to the RLOG pool), the failed RLOG file has to berepaired as under (1).

UDS0703

UDS TOTAL FAILURE OF FILE (&00) (&01) (&02)(B) Routing code: U Weight: 70

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.

Response
Take recovery measures (depending on the file type).

(&00) contains a file name. The file may be one of the following types:

ALOG file

Meaning
UDS/SQL tries to keep the damage resulting from the failure of the ALOG file to a minimum (depending on the conditions under which the error occurred).

Response
The appropriate user action can be obtained from the continuation messages which give details on the UDS/SQL reaction.

Backout file

Meaning
UDS/SQL ceases backout logging and closes the backout file, but continues the session.

Response
Take into account the gap resulting in the backout logging of all databases involved.

CATALOG file

Meaning
UDS/SQL can no longer update the CATALOG of the database from this point on.

Response
A failed CATALOG pair can be reverted to a defined state only by using RESET-DB.

DBSTAT file

Meaning
(Cannot refer to the current DBSTAT file of the running session.) UDS/SQL aborts the current operation (DB warm start or updating of a DBSTAT file).

Response
Try to remove cause of failure and repeat operation. This may require communication with the openUTM and/or UDS-D partner system.
Failing this, erase both DBSTAT files and repeat creation.
Warning:
This total loss of status information can result in the output of incorrect status information to the partner systems (openUTM/UDS-D) and thus impair the integrity of data resources.

Permanent realm

Meaning
UDS/SQL disconnects the realm to give the user the opportunity to take repair measures, at the same time trying to keep damages resulting from the realm failure to a minimum (depending on the conditions under which the error occurred).

Response
The appropriate user action can be obtained from the continuation messages which give details on the UDS/SQL reaction.

RLOG file

Meaning
The following two scenarios are possible:

(1)

The message refers to the current RLOG file of the running session:

As soon as all update transactions are completed, UDS/SQL has all databases of theconfiguration marked consistent and switches to another RLOG file to give the user theopportunity to raise the value for the restart logging to the desired number (PP LOG).

(2)

The message refers to an RLOG file that is not the current one: UDS/SQL aborts the current operation (warm start or updating of a DBSTAT file).

Response

(1)	If UDS/SQL succeeds in disconnecting the old (obsolete) RLOG file without any rollbacks, the data resources are not impaired and the failure of the RLOG file has noeffect. In the case of session abort, rollback or disconnection of databases in an inconsistent state, however, damage to the databases concerned cannot be prevented.
(2)	Try to remove cause of failure and repeat operation. This may require communication with the openUTM and/or UDS-D partner system. Failing this, RESET-DB for alldatabases for which warm start is not possible, and ERASE-RLOG.

SLF

Meaning
Following this message, UDS/SQL will cease SLF logging of any changes of database configuration and/or in the load parameters for the restart. The session is continued if DBH initialization has already been completed.

Response
The SLF concerned has to be invalidated before starting or restarting a session under the current configuration name; its contents are obsolete.

Temporary realm

Meaning
UDS/SQL ceases working with the indicated realm until session end or until session abort, resuming it at the next session start or restart under the same configuration name. For this period, the number of transactions that can be processed in parallel (PP TRANSACTION) is reduced by one.

Response
Remove error causing file failure after session end or during next session interrupt.

UDS0704

UDS DATABASE (&00) IS MARKED DEFECTIVE (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The indicated database has become irrecoverably due to the preceding error.

Response
RESET-DB.

UDS0705

UDS USER ERROR: RESTART WITH UDS VERSION (&00) ONLY. (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: RESTART IN (&00)-SESSION ONLY. (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: RESTART WITH (&00)-UDS ONLY. (&01) (&02)(B) Routing code: U Weight: 70

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

UDS USER ERROR: RESTART WITH UDS/SQL-(&00) ONLY. (&01) (&02)(B) Routing code: U Weight: 70

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

UDS SESSION RESTART: PROGRAM PARAMETERS WILL BE SKIPPED. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS PROGRAM PARAMETER ’(&00)’ (&01) (&02)(B) Routing code: U Weight: 70

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

UDS PROGRAM PARAMETER REJECTED: (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The load parameter indicated is invalid.

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

(&00) may contain the following values:

CATID NOT WITHIN SCOPE OF CURRENT UDS PUBSET DECLARATION.

Meaning
The DBH cannot be started because one of the RLOG logging entries PP LOG, PP LOG-2, or PP RESERVE is outside the pubset space of the current UDS/SQL pubset declaration.The program parameter involved is displayed in a previous message.

DB-NAME IS AMBIGUOUS WITHIN CONFIGURATION

Meaning
The specified DB name is not unique in the configuration.

DIFFERENT VOLSETS FOR SAME LOGFILE ARE FORBIDDEN.

Meaning
Volumes from different volume sets of an SM pubset were specified to create one of the RLOG files.

ERROR IN SYNTAX OF DB-NAME

Meaning
The specified DB name contains a syntax error.

ERROR IN SYNTAX OF PASSWORD

Meaning
The specified password contains a syntax error.

ERROR IN SYNTAX OF PROGRAM-PARAMETER

Meaning
The load parameter contains a syntax error.

ILLEGAL PROGRAM-PARAMETER

Meaning
The specified load parameter is not permitted.

ILLEGAL VALUE OF PROGRAM-PARAMETER

Meaning
An invalid value was specified for this load parameter.

LOC FOR LOG AND LOC FOR LOG-2 ARE NOT DIFFERENT.

Meaning
The same volume was specified for both examples of the RLOG file.

MORE DB’S THAN SPECIFIED

Meaning
The highest possible number of databases has already been specified.

MORE PASSWORDS THAN ALLOWED

Meaning
More passwords were specified than allowed.

OWN-BUFFER-SIZE CONFLICT

Meaning
The specified shared user buffer pool already exists and has a size different from the size specified in this load parameter.

OWN-BUFFER-SIZE MISSING

Meaning
The specified shared user buffer pool is not yet defined for another database, and no buffer pool size (or n = 0) was specified.

PASSWORD IS STILL EXISTING

Meaning
This password was already specified for an earlier load parameter.

PROGRAM-PARAMETER UNKNOWN

Meaning
The load parameter is unknown.

PROGRAM-PARAMETER WAS ALREADY PROCESSED

Meaning
The specified load parameter has already been specified.

PROGRAM-PARAMETER WAS TRUNCATED

Meaning
The specified load parameter is too long and has therefore been truncated.

SECOND ADD-DB-ORDER

Meaning
This database was already specified for an earlier load parameter.

VSNS IN LOC FOR LOG/LOG-2/RESERVE ARE NOT DIFFERENT

Meaning
The same volume was specified for both versions of the RLOG file or the same volume was specified for one version and the reserve assignment.

UDS0712

UDS WARMSTART WITH RLOG FILE (&00) SUCCESSFUL FOR FOLLOWING DATABASE(S): (&01) (&02)(B) Routing code: U Weight: 70

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

UDS0713

UDS WARMSTART WITH RLOG FILE (&00) LEAVES FOLLOWING PTC TRANSACTIONS (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The listed (distributed) transactions could not be released (for reasons of consistency) from the PTC state by means of a database 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 messages.
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 application involved.

The two scenarios are not mutually exclusive. In fact, several UDS/SQL configurations and UTM applications may be involved. The database can be reconnected using the DAL command once all the required configurations and applications have been made accessible.

UDS0714

UDS: UTM (&00) PTC FOR FOLLOWING TA (&01) (&02)(B) Routing code: U Weight: 70

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

UDS TA (&00) IN STATE PTC (&01) (&02)(B) Routing code: U Weight: 70

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

UDS THIS TRANSACTION IS STILL IN PTC DUE TO (&00) (&01) (&02)(B) Routing code: U Weight: 70

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).

(&00) may contain the following values:

DISTRIBUTION_DISARRANGED

Meaning
Although UDS-D has been loaded, the state of the transaction cannot be determined due to preceding errors.

Response
Terminate the local UDS/SQL session and repeat with PP DISTRIBUTION=START.

DISTRIBUTION_MISSING

Meaning
The state of the transaction cannot be determined because UDS/SQL has been started without distribution option, i.e. PP DISTRIBUTION=NO.

Response
Connect the database to a UDS/SQL which has been started with distribution option.

DISTRIBUTION_VIA_UTM

Meaning
UTM is part of the distribution of this transaction; it is thus responsible for the resolution of the present state.

Response
Start appropriate openUTM-D application.
If the transaction remains in the PTC state due to the UDS/SQL reaction indicated in the subsequent message (and the databases concerned are disconnected again), connection of the database can be retried after removing the cause of the error. Interconfiguration consistency remains unaffected.
If the cause of the error cannot be removed, the user can effect a forced termination of the transaction with the next database addition and warm start attempt by changing the warm start PTCSYNCH value (see DAL command MODIFY). This may, however, impair interconfiguration consistency of the data resources.

LIFETIME_OVERFLOW

Meaning
The state of the transaction could not be resolved within the time limit with UDS/SQL unable to determine the reason.
Possible causes:

The connection to the remote UDS/SQL is down and cannot be reestablished.
The remote UDS/SQL configuration has terminated.
The remote UDSCT task has terminated.
The line speed is lower than assumed by UDS/SQL.

Response
Determine and remove cause of error.

LOCAL_UDSCT_ABSENT

Meaning
The UDSCT task of the home UDS/SQL configuration is missing, i.e. it has not been started or it has already been terminated.

Response
Start UDSCT task of home UDS/SQL configuration.

LOCAL_UDSCT_DOWN

Meaning
The UDSCT task of the home UDS/SQL configuration has been terminated abnormally during the attempt to resolve the state of the transaction.

Response
Restart UDSCT task of home UDS/SQL configuration.

PTC_IN_PROCESS

Meaning
The transaction concerned is in the end phase, i.e. its state will be resolved without further action.

Response
Retry database addition and warm start after a short pause.

REMOTE_DMS_ERROR

Meaning
DMS error in partner UDS/SQL configuration prevents resolution of the state of the transaction. The DMS error code is output as secondary return code (SEC-RC).

Response
Remove DMS error in the partner UDS/SQL configuration.

REMOTE_FATAL_ERROR

Meaning
Irrecoverable error in the partner UDS/SQL configuration during the attempt to resolve the state of the transaction.

Response
DIAG.

REMOTE_STATUS_DEADLOCK

Meaning
A deadlock in the partner UDS/SQL configuration has (temporarily) prevented resolution of the state of the transaction.

Response
Retry database addition and warm start.

REMOTE_UDS_DOWN

Meaning
The partner UDS/SQL configuration terminated abnormally during the attempt to resolve the state of the transaction.

Response
START-UDS for the partner UDS/SQL configuration.

REMOTE_UDSCT_ABSENT

Meaning
The UDSCT task of the partner UDS/SQL configuration is missing, i.e. it has not been started, has already been terminated or the entire partner UDS/SQL configuration is missing.

Response
Start UDSCT task of the partner UDS/SQL configuration or start entire partner UDS/SQL configuration.

STATUS_MEMORY_OVERFLOW

Meaning
Memory overflow during the attempt to resolve the state of the transaction. The output secondary return code (SEC-RC) specifies the location:
X’0003’: in the partner UDS/SQL configuration
X’0004’: in the UDSCT task of the home configuration
X’0005’: in the master task of the UDS/SQL configuration.

Response
Retry database addition and warm start after a short pause. Determine cause of memory bottleneck.

UDS0717

UDS REACTION FOR THIS PTC TRANSACTION: (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
This message describes (via symbolic code) the UDS/SQL reaction to the previously indicated PTC transaction.

Response
Depends on information in (&00).

(&00) may contain the following values:

PTCSYNCH-ABORT or PTCSYNCH-COMMIT

Meaning
UDS/SQL terminates the indicated transaction of the current UDS/SQL configuration with (ABORT) or without (COMMIT) CANCEL (according to the current PTCSYNCH value). The consistency of the data resources is only retained for the home UDS/SQL configuration while it may be impaired within the partner’s configuration. The potential effects of this inconsistency are described in the subsequent messages.

Response
Ensure that analogous action is taken in the partner UDS/SQL configurations for the subtransactions involved. Remove any inconsistencies arising between the UDS/SQL configurations involved by means of a correct transaction.

PTCSYNCH-WAIT

Meaning
Addition of any database on which updating accesses are to be performed by the indicated transaction is rejected by UDS/SQL (according to the current PTCSYNCH value).
UDS/SQL thus prevents new transactions from working with (temporarily) inconsistent data resources.

Response
Remove cause of PTC (see preceding message) or change PTCSYNCH value, and repeat database addition.

UDS-FORCED-WAIT

Meaning
Regardless of the current PTCSUNCH value, UDS/SQL reacts as under PTCSYNCH-WAIT. Reason: UDS/SQL expects the status of the PTC transaction to be resolved shortly without intervention (timer-controlled).

Response
Retry database addition after short pause.

UDS0718

UDS: TA (&00) CONCERNED (&01) (&02)(B) Routing code: U Weight: 70

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

UDS ENFORCES (&00) FOR ERROR HANDLING (&01) (&02)(B) Routing code: U Weight: 70

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.

Response
If a database or realm is disconnected: Reconnect, if desired, via DAL once the cause of the disconnection has been removed.

(&00) may contain the following values:

CHECKPOINT DB=dbname

Meaning
AFIM checkpoint for database dbname written.

DROP DB=dbname

Meaning
Database dbname disconnected.

DROP RN=realmname, DB=dbname

Meaning
Realm realmname or database dbname disconnected.

NEW RLOG

Meaning
Changeover to new RLOG file.

UDS0720

UDS ADD ORDER REJECTED: (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The addition of a database or file to the current session was unsuccessful. The cause of the rejection is given in the symbolic code.

Response
Remove cause of the rejection and retry addition.

(&00) may contain the following values:

ALOG-SUPPORT NOT WITHIN SCOPE OF UDS PUBSET DECLARATION

Meaning
A DB cannot be added because one of the ALOG logging entries made with the DEFAULT-SUPPORT or RESERVE-SUPPORT parameter of the BMEND statement START-LOG is outside the pubset space of the current UDS/SQL pubset declaration.
More precise details on the cause were provided in a previous message, for example with UDS0755.

BACKOUT_CONFIGURATION_CHANGED

Meaning
During restart of an aborted (linked-in) session, UDS/SQL was not able to reconnect the complete database configuration required. It therefore aborts the restart to prevent a gap in the backout logging for the databases involved.

Response
Remove cause of restart prevention in the corresponding databases.

BACKOUT_REALM_LIMIT

Meaning
If backout logging is used, the current database configuration must not exceed 254 realms.
UDS/SQL aborts session start as this limit has been exceeded.

Response
Reduce number of realms in the database configuration.

BUFFER_NOT_AVAILABLE

Meaning
The database to be connected requires a system buffer pool with an 8-Kbyte page format. No such buffer pool was created.

Response
Repeat the connection attempt by specifying an exclusive buffer pool for the database or create a system buffer pool with an 8-Kbyte page format when starting the session.

BUFFER_TOO_LARGE

Meaning
No buffer pool of the requested size can be created for the database to be connected.

Response
Repeat the connection attempt by specifying a much smaller exclusive buffer pool for the database or leave out the exclusive buffer pool entirely. It is not advisable to use up all the address space for buffer pools.

DB_ACCESS_CONFLICT

Meaning
Other UDS/SQL DBHs/utility routines have been given access right to the indicated database, thus preventing access rights from being granted which are required for the current addition.

Response
Wait for interfering access rights to be withdrawn.

DB_BFORMAT_MISSING

Meaning
The indicated file has not yet been formatted by means of the BFORMAT utility routine or a restructuring or renaming cycle has not yet been terminated properly.

Response
Initiate BFORMAT run or terminate restructuring or renaming cycle.

DB_DBDIR_MISSING

Meaning
The DBDIR of the indicated database has been disconnected. Without the DBDIR, no database can be added.

Response
REPAIR-RLM for DBDIR.

DB_DEFECTIVE

Meaning
The indicated database has been marked defective due to irrecoverable errors and thus cannot be processed by UDS/SQL.

Response
RESET DB.

DB_FORMAT_ERROR

Meaning
The physical file format of a database file is incompatible with the length of the database pages.
This is usually due to a handling error during database conversion or user manipulation.

Response
Correct the database conversion; DIAG if required.

DB_OCCUPIED_BY_UTILITY

Meaning
The indicated database is exclusively accessed by a utility routine and cannot be processed by the DBH while this access right is in force.

Response
Either normal termination of the utility routine (after restart as the case may be) or RESET DB.

DB_REALM_LIMIT

Meaning
The indicated database has more realms than allowed (125 for 2-Kbyte databases and 245 for 4 or 8-Kbyte databases).

Response
Reduce the number of realms for this database.

DB_SCHEMA_DEFECTIVE

Meaning
The schema of the indicated database is defective or a restructuring or renaming cycle has not yet been terminated properly.

Response
DIAG or terminate restructuring or renaming cycle; RESET-DB, if necessary.

DB_SCHEMA_MISSING

Meaning
The schema of the indicated database is missing.

Response
DIAG; RESET-DB, if necessary.

REALM_OCCUPIED_BY_UTILITY

Meaning
The utility routine BMEND is currently performing recovery measures on the realm.

Response
Wait for the recovery measures to terminate.

REALM_RECOVER_BUSY

Meaning
The BSECURE utility routine is performing recovery measures on the added realm.
(Only relevant for versions < UDS/SQL V1.2)

Response
Wait until realm recovery measures have been completed.

REALM_RECOVER_OUTSTANDING

Meaning
The added realm has been marked defective and thus cannot be processed. (Only relevant for versions < UDS/SQL V1.2)

Response
Initiate recovery measures for this realm (BSECURE).

RLOG_FILE_MISSING

Meaning
Due to previously indicated errors, UDS/SQL is not able to provide a new RLOG file. It therefore rejects all updates on databases of the current configuration as well as the opening of any distributed transactions to prevent the loss of any restart logging data.

Response
Remove cause preventing provision of the RLOG file and repeat RLOG file addition using
/SEND-MSG TO=PROGRAM,MSG=C’NEW RLOG’ and
/SEND-MSG TO=PROGRAM,MSG=C’PERFORM’.

UDS0721

FILE (&00) IS MARKED DEFECTIVE (&01) (&02)(B) Routing code: U Weight: 99

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.

Response
Repair defective realm/DBSTAT file or take into account the possible effects of a gap in
RLOG/AFIM or backout logging.

The following data types may be involved:

ALOG file

Meaning
The defect marker remains in effect during the entire life of the ALOG file. This results in a gap in AFIM logging for the database concerned, i.e. all “previous” realm copies can no longer be used for REPAIR-RLM measures.

Response
Produce new realm copies for the database concerned as soon as possible (even in parallel to the running session); they are indispensable for any RLM-REPAIR measures based in the ALOG log pool.

Backout file

Meaning
Normally, the defect marker remains in effect until session end. If the user provides a new backout file as part of a session restart, backout logging is resumed and the defect marker removed.

Response
In the case of a session abortion, provide a new backout file for restart. This allows backout logging to be resumed in the current session.

DBSTAT file

Meaning
The defect marker remains in effect until the DBSTAT file has been repaired.

Permanent realm

Meaning
The defect marker remains in effect until the user has repaired the realm.

Response
REPAIR-RLM.

RLOG file

Meaning
(Can only refer to the current RLOG file of the running session.) The defect marker for the failed RLOG file remains in effect in the databases involved until they have become independent from this file (without rollback), i.e. they have been marked consistent.

Response
ERASE-RLOG, if necessary.

UDS0722

UDS ORDER (&00) IN EXECUTION (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Execution of the indicated request has been completed or in case of an ADD request has been commenced.

(&00) may contain the following values:

ACT INCR,RR=realmref,DB=dbname

Meaning
Online extensibility has been successfully activated for the realm.

ACT DBTT-INCR,RECR=recordref,DB=dbname

Meaning
Online DBTT extensibility has been successfully activated for the record type.

ACT DBTT-INCR,DB=dbname

Meaning
The request for the activation of online DBTT extensibility for all the record types in the DB has been executed. The current state of DBTT extensibility can be displayed using
DIS DBTT-INCR,DB=dbname.

ADD DB=dbname

Meaning
The ADD DB request (including warm start, if required) has commenced.

ADD RN=realmname, DB=dbname

Meaning
The ADD realm request has commenced.

ADD RLOG rlog-timestamp

Meaning
The ADD RLOG request has commenced.

DEACT INCR,RR=realmref,DB=dbname

Meaning
Online extensibility has been successfully deactivated for the realm.

DEACT DBTT-INCR,RECR=recordref,DB=dbname

Meaning
Online DBTT extensibility has been successfully deactivated for the record type.

DEACT DBTT-INCR,DB=dbname

Meaning
The request for the deactivation of online DBTT extensibility for all the record types in the DB has been executed. The current state of DBTT extensibility can be displayed using DIS DBTT-INCR,DB=dbname.

DROP DB=dbname

Meaning
The DROP DB request has been completed successfully. The database is consistent, i.e. it does not require a warm start.

DROP DB=dbname (ABNORMAL)

Meaning
The DROP DB request has been completed successfully. The database was disconnected in the state it had when the DROP request was given. It may thus be inconsistent (require a warm start) or even irrecoverably defective.

DROP RN=realmname, DB=dbname

Meaning
The DROP realm request has been completed successfully. The realm has been dropped permanently, i.e. it can be reconnected by UDS/SQL if its disconnection is revoked specifically by means of DAL command or BMEND operation.

DROP RN=realmname, DB=dbname (TEMPORARY)

Meaning
The DROP realm request has been completed successfully. The realm has been dropped temporarily, i.e. it is reconnected without user intervention as soon as its database is reconnected.

DROP RLOG rlog-timestamp

Meaning
The DROP RLOG request has been completed.

UDS0723

UDS WARMSTART REJECTED FOR DATABASE (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
A warm start for the indicated database 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.

The continuation line may contain the following values:

CODED FILE ID INCONSISTENT

Meaning
The coded file id of some of the DB files differs from the entry in the database. Therefore, an attempt is made to perform an online backup or to warm start an inconsistent database, which is not permitted.

Response
Apply BMEND to the current database (UPDATE-DATABASE,DEADLINE=BREAK-POINT). Then repeat warm start.

NO RLOG-FILE

Meaning
The indicated database has become inconsistent in a session without restart logging
(PP LOG=NO or utility session). The logging data required for warm start is missing.

Response
RESET-DB.

RETRIEVAL-OPTION

Meaning
The retrieval option was specified for the addition of the indicated database although it is not consistent. The retrieval option prevents any type of update, including warm start.

Response
Add database without retrieval option, thus allowing warm start to be performed. Then disconnect database and reconnect with retrieval option, if required.

UDS-VERSION Vx.y

Meaning
The indicated database has become inconsistent under UDS/SQL Vx.y, warm start was attempted under another UDS/SQL version however.

Response
Repeat database warm start under UDS/SQL Vx.y. Change of version is only possible with consistent databases.

USER-SESSION

Meaning
The indicated database has become inconsistent in a user session; however, a warm start was attempted in a utility session.

Response
Make the database consistent by means of a warm start in a user session, then repeat the utility routine.

UTILITY-SESSION

Meaning
The indicated database has become inconsistent in a utility session; however, a warm start was attempted in a user session.

Response
Make the database consistent by means of a warm start in a utility session, then connect to the user session.

UTILITY utility

Meaning

The indicated database has been rendered inconsistent by utility routine utility. The required warm start cannot be performed by the DBH, but by the indicated utility only.

Response
Check if restart is possible for utility utility. If this is the case: Make database consistent again by means of utility restart and normal utility termination. Otherwise: RESET DB.

UDS0724

UDS INTERRUPTED ERROR HANDLING IS RESUMED (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Error handling for a failed realm or AFIM file was interrupted due to a session abort (or an abnormal database disconnection). It is now resumed as part of the connection procedure for this database and completed.
See following UDS/SQL messages.

UDS0725

UDS USER HASH ERROR (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
An error occurred at loading (LINK) or unloading (UNLOAD) of the indicated hash module for the indicated database.

LINK error: Database is disconnected.
UNLOAD-UDSHASH error: Session is aborted.
UNLOAD user hash module error: Error is ignored.

Response

LINK error: Remove cause, reconnect database.
UNLOAD-UDSHASH error: DIAG, START-UDS.
UNLOAD user hash module error: Avoid addition of a database whose user hash module has the same name but different contents until session end or abort.

UDS0726

UDS OPPOSITE ORDER IS CANCELLED. (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Self-explanatory.

UDS0727

UDS: PRIMARY TA CONCERNED :(&00) (&01) (&02)(B) Routing code: U Weight: 70

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

LOAD PARAMETER PP LOG NOT CORRECTLY SPECIFIED. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

PP LOG AND PP LOG-2 IN CONFLICT. (&00) (&01) (&02)

(B) Routing code: U Weight: 70

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

PP LOG AND PP LOG-2 MUST BE DIFFERENT. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

RESTART MUST USE (&00). (&01) (&02)(B) Routing code: U Weight: 70

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

END OF TA (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS ADMINISTRATION ERROR: DB (&00) CANNOT BE ATTACHED DUE TO HASH MODULE (&01) (&02)(B) Routing code: U Weight: 70

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

ALOG RESERVE BEING USED FOR DB (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Due to the previous error, UDS/SQL changes the ALOG file for database
(&00) to the reserve medium.

Response
Remove error.

UDS0735

GAP IN LOGGING FOR DB (&00) CAN BE PREVENTED BY WARM START (&01) (&02) (B) Routing code: U Weight: 70

Meaning
The previous ALOG overflow caused a gap in the logging for database
(&00); the gap can be remedied using a warm start.

Response
Accommodate ALOG file expansion. If DMS code 0946 has been returned, reorganize ALOG file (by copying). Then initiate DB warm start.

UDS0736

UDS USER ERROR: RESTART ONLY POSSIBLE WITH UNCHANGED SECOLTP PRIVILEGE (&01) (&02)(B) Routing code: U Weight: 99

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

REALM HAS BEEN EXTENDED: (&00) DATABASE-PAGES (&01) (&02)(B) Routing code: U Weight: 50

Meaning
(&00): dbname.realmname +nr-pages. The realm realmname in the database dbname has been extended by nr-pages database-pages.

UDS0738

ONLINE EXTENSIBILITY FOR REALM (&00) CANNOT BE DEACTIVATED AS FOR SOME DBTTS EXTENSIBILITY IS ACTIVATED (&01) (&02)(B) Routing code: U Weight: 50

Meaning
The deactivation of online extensibility of realm dbname.realname 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

REALM (&00) CANNOT BE EXTENDED. MAXIMUM SIZE ALREADY REACHED (&01) (&02) (B) Routing code: U Weight: 70

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 pagesize to reclaim free space in all realms of the database), or erase records no longer required.

UDS0740

ONLINE EXTENSIBILITY FOR REALM (&00) SUSPENDED (&01) (&02)(B) Routing code: U Weight: 70

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 diskspace 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

DBTT HAS BEEN EXTENDED: (&00) DBTT ENTRIES (&01) (&02)(B) Routing code: U Weight: 50

Meaning
(&00): dbname.recordname + nr-entries.
The DBTT of record recordname in the database dbname has been extended by nr-entries entries.

Response
None

UDS0742

DBTT OF RECORD (&00) CANNOT BE EXTENDED. MAXIMUM SIZE ALREADY REACHED (&01) (&02)(B) Routing code: U Weight: 50

Meaning
The DBTT of record dbname.recordname shown in (&00) cannot be extended as it has already reached its maximum size.

Response
None

UDS0743

DBTT OF RECORD (&00) CANNOT BE EXTENDED (&01) (&02)(B) Routing code: U Weight: 50

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

ONLINE DBTT EXTENSIBILITY IN REALM (&00) IMPOSSIBLE AS REALM IS NOT EXTENDIBLE. (&01) (&02)(B) Routing code: U Weight: 50

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

ONLINE DBTT EXTENSIBILITY IN REALM (&00) CANNOT BE PROCESSED AS REALM IS NOT AVAILABLE. (&01) (&02) (B) Routing code: U Weight: 50

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

UDS PUBSET DECLARATION (&00) FOLLOWS (&01) (&02) (B) Routing code: BOTH Weight: 50

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

UDS PUBSET DECLARATION NOT PRESENT, DEFAULT IS CATID * (&00) (&01) (&02)(B) Routing code: BOTH Weight: 50

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

UDS USER ERROR IN UDS PUBSET DECLARATION (SYNTAX): (&00) (&01) (&02)(B) Routing code: BOTH Weight: 50

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

UDS USER ERROR IN UDS PUBSET DECLARATION (SYNTAX) (&00) (&01) (&02)(B) Routing code: BOTH Weight: 50

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

UDS WARNING: PHYSICAL ALLOCATION RIGHT MISSING FOR (&00) (&01) (&02)(B) Routing code: BOTH Weight: 50

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

UDS WARNING: PUBSET/VOLUMESET (&00) NOT ACCESSIBLE (&01) (&02) (B) Routing code: BOTH Weight: 50

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

UDS USER ERROR: ACCESS TO UDS-PUBSET-JV VIA JV-LINKNAME (&00) FAILED (&01) (&02)(B) Routing code: BOTH Weight: 50

Meaning
The analysis of the UDS 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

UDS SUPPRESSES FURTHER ERROR MESSAGES FOR DB JV (&00) (&01) (&02)(B) Routing code: BOTH Weight: 50

Meaning
The limit for the number of similar error messages concerning DB JV was reached. Further error messages are suppressed.

UDS0754

UDS SWITCHES TO NEW PUBSET DECLARATION NOW (&00) (&01) (&02)(B) Routing code: BOTH Weight: 50

Meaning
The UDS/SQL Pubset Declaration announced with DAL NEW PUBSETS is now effective as a result of a possibly internal PERFORM.

UDS0755

UDS USER ERROR: CATID MISSING IN UDS PUBSET DECLARATION (&00) (&01) (&02)(B) Routing code: BOTH Weight: 50

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

UDS WARMSTART WITH RLOG FILE (&00) STARTED (&01) (&02)(B) Routing code: BOTH Weight: 70

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

EXTEND REALM FOR REALM (&00) DATABASE PAGES FAILED (&01) (&02)(B) Routing code: BOTH Weight: 70

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

NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE(B) Routing code: BOTH Weight: 70

Meaning
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

UDS-D SYSTEM ERROR (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
A serious error occurred in UDS-D. UDS-D is terminated with a dump.

Response
Forward dump file to diagnostics department. Restart UDSCT with
&START DISTRIBUTION. If the error recurs, terminate UDS/SQL session and restart.

(&01) may contain the following internal message numbers (see "Explanation of themessage text format"):

358

Meaning
STXIT event “P error” or “program monitoring” in UDSCT.
(&00) contains the interrupt weight and address.

Response
Forward dump file to diagnostics department.
Restart UDSCT using &START DISTRIBUTION.

359

Meaning
TERM in UDSCT causes emergency halt initialization.
(&00) contains the interrupt weight and address.

Response
Forward dump file to diagnostics department.
Restart UDSCT using &START DISTRIBUTION. If the error recurs, terminate UDS/SQL session and restart.

360

Meaning
Second STXIT activation in UDSCT (error in error handling).
(&00) contains the interrupt weight and address.

Response
Forward dump file to diagnostics department.
Restart UDSCT using &START DISTRIBUTION.

361

Meaning
System error in the UDSCT storage management.
(&00) contains the identification of the originator and the pool.

Response
Forward dump file to diagnostics department.
Restart UDSCT using &START DISTRIBUTION. If the error recurs, terminate UDS/SQL session and restart.

363

Meaning
An error occurred in the storage management of the UDS-D component in the master task. UDS-D administration is locked. The UDSCT task has to be terminated using operating system command /CANCEL-JOB tsn in order to deactivate distribution.

Response
If UDS-D commands are to be used, terminate UDS/SQL session and restart.

365

Meaning
Module with invalid parameters has been activated in UDSCT.
(&00) contains the module identification.

Response
Forward dump file to diagnostics department.
Restart UDSCT using &START DISTRIBUTION.

366

Meaning
An error has been detected in a service routine of the UDS-D component in the master task.
(&00) contains the module identification, operation code, return code.

Response
Output dump.
Restart UDSCT using &START DISTRIBUTION.
If error recurs, terminate UDS/SQL session and restart.

367

Meaning
Error in message of the UDS-D component in the master task to UDSCT.
(&00) contains the module identification and the return code.

Response
Forward dump file to diagnostics department.
If distribution functions are required, terminate UDS/SQL session and restart.

369

Meaning
Error during SVC execution.
(&00) contains the module identification and the SVC.

Response
Forward dump file to diagnostics department.
Restart UDSCT using &START DISTRIBUTION.

370

Meaning
Inconsistency in message from DCS partner to UDS-D task.
UDSCT continues following dump.

Response
Forward dump file to diagnostics department.

371

Meaning
Error at close of STXIT handling in UDSCT.
(&00) contains the module identification and the return code.

Response
Forward dump file to diagnostics department.

373

Meaning
An error occurred during calling of the UDS/SQL connection module UDSCONCT.
(&00) contains the module identification, operation code and return code.

Response
Forward dump file to diagnostics department.
Restart UDSCT using &START DISTRIBUTION.
If the error recurs, terminate UDS/SQL session and restart.

374

Meaning
An error occurred in the table generation during UDSCT initialization.
(&00) contains the module and table identification.

Response
Forward dump file to diagnostics department.
Terminate UDS/SQL session and restart.

375

Meaning
Error in the UDSCT/master task communication.
(&00) contains the module identification and the return code.

Response
Forward dump file to diagnostics department.
Restart UDSCT using &START DISTRIBUTION.
If the error recurs, terminate UDS/SQL session and restart.

376

Meaning
System error in the UDSCT connection management.
(&00) contains module identification and the return code of the logical connection control block (CHATX,CONN_RC).

Response
Forward dump file to diagnostics department.
Restart UDSCT using &START DISTRIBUTION.

390

Meaning
Error in event control.
(&00) contains module and event identification, and return code.

Response
Forward dump file to diagnostics department.
Restart UDSCT using &START DISTRIBUTION. If the error recurs, terminate UDS/SQL session and restart.

391

Meaning
A control error occurred during processing of a secondary subtransaction. (&00) contains the module identification and the internal number of the transaction concerned. The transaction is rolled back.

Response
Forward dump file to diagnostics department.
Restart UDSCT using &START DISTRIBUTION. If the error recurs, terminate UDS/SQL session and restart.

UDS0801

UDS-D STARTING (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
UDS-D task UDSCT has been initialized.
(&00): (version,date).

UDS0802

UDS-D INITIALIZATION DELAYED. PLEASE CHECK BATCHLIMIT. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS-D NOT YET STARTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS-D ALREADY STARTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
UDS-D has already been started. The DAL command &START DISTRIBUTION is rejected.

UDS0805

UDS-D READY (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Distributed transactions can be started.

UDS0806

UDS-D: ADMINISTRATION CLOSED DUE TO ERROR (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS-D: TERMINATION INITIATED (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Self-explanatory.

UDS0808

UDS-D TERMINATING (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
UDS-D is being terminated; the DAL command indicated is rejected.

Response
Start UDS-D using &START DISTRIBUTION. Repeat DAL command.

UDS0809

UDS-D NORMAL TERMINATION (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Message indicated normal end.

UDS0810

UDS-D ABNORMAL TERMINATION (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Abnormal termination of UDSCT.
(&00): number of rolled back secondary transactions that are still open.

Response
Forward dump file to diagnostics department. Restart UDSCT using &START DISTRIBUTION.

(&01) may contain the following internal message numbers (see "Explanation of themessage text format"):

354

Meaning
Abnormal termination during UDSCT initialization.

Response
Forward dump file to diagnostics department.
Restart UDSCT using &START DISTRIBUTION.

355

Meaning
Abnormal termination of UDSCT during the session.
(&00) gives the number of rolled back secondary transactions that are still open.

Response
Forward dump file to diagnostics department.
Restart UDSCT using &START DISTRIBUTION.

UDS0811

UDS-D: TASK PROGRAM TIME RUN OUT (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS-D: TASK ABNORMALLY ENDED (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS-D WARNING: MEMORY OVERFLOW (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
UDS-D memory request could not be honored.

Response
If the error recurs regularly, terminate UDS/SQL session and restart with increased value for PP TRANSACTION.

(&01) may contain the following internal message numbers (see "Explanation of themessage text format"):

362

Meaning
UDSCT memory request could temporarily not be honored.
(&00) contains the module and pool identification.

Response
If this message is issued during the processing of a DAL command, repeat entry. If the error recurs or occurs independent of DAL commands, terminate UDS/SQL session and restart with increased values for PP TRANSACTION.

364

Meaning
Memory request of the UDS-D component in the master task could temporarily not be honored.
Distributed transaction processing is not affected.

Response
If this message is issued during processing of a DAL command, repeat command entry. If the error recurs or occurs independent of DAL commands, terminate UDS/SQL session and restart with increased values for PP TRANSACTION.

UDS0814

UDS-D: INVALID PARAMETERS IN UDSCT ENTER FILE. (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS-D ERROR READING INPUT FILE FOR DISTRIBUTION TABLE (&00) (&01) (&02) (&01) (&02)(B) Routing code: U Weight: 99

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= returncode.

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

UDS-D ERROR WRITING OUTPUT FILE FOR DISTRIBUTION TABLE (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Error during saving of distribution table (using DAL ’&SAVE DISTRIBUTION’).
(&00) contains

a)	DMS return code:	DMSCODE= dmscode
b)	SVC-WRLST return code:	WRLST= returncode.

Response
Check existence, type and access right of output file.

UDS0817

UDS-D USER ERROR: INPUT FILE FOR DISTRIBUTION TABLE CONTAINS TOO MANY INVALID RECORDS (&00) (&01) (&02) (B) Routing code: U Weight: 70

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

UDS-D ERROR: WRONG DCAM VERSION (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The DCAM version is not allowed for UDS-D.

Response
Make appropriate DCAM available.

UDS0819

UDS-D DISTRIBUTION TABLE CANNOT BE CHANGED AT THE MOMENT (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The distribution table cannot be updated at the moment because other tasks have read access.

Response
Repeat DAL command later.

UDS0820

UDS-D WARNING: THE DISTRIBUTION TABLE FILE CONTAINS DATABASE ENTRIES WITHOUT REFERENCES TO A CONFIGURATION (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The input file for the distribution task contains database entries without any reference to a configuration or processor. These entries are taken up into the distribution table, but the associated databases cannot take part in the distribution.

Response
Effect assignment to configuration or processor using DAL command
&ADD DISTRIBUTION.

UDS0821

UDS-D WARNING: RECORD FROM DISTRIBUTION TABLE FILE REJECTED AS NAMES ALREADY EXISTING (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS-D WARNING: INPUT FILE FOR DISTRIBUTION TABLE CONTAINS (&00) INVALID RECORDS (&01) (&02)(B) Routing code: U Weight: 70

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 invalid records. Repeat reading of distribution table using &ADD DISTRIBUTION, if necessary.

UDS0823

UDS-D: INPUT FILE FOR DISTRIBUTION TABLE (&00) READ (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The input file (&00) for the distribution table has been read.

UDS0824

UDS-D: ONLY PASSIVE PARTICIPATION POSSIBLE AS NO DISTRIBUTION TABLE FILE DEFINED (&00) (&01) (&02) (B) Routing code: U Weight: 70

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

UDS-D USER ERROR: NAME (&00) UNKNOWN IN DISTRIBUTION TABLE (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The name indicated under (&00) does not exist in the distribution table.

Response
Correct and repeat DAL command.

UDS0826

UDS-D USER ERROR: SPECIFIED DISTRIBUTION DEFINITION UNKNOWN (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The assignment indicated under (&00) does not exist in the distribution table.

Response
Correct distribution table using a DAL command.

UDS0827

UDS-D DCS ERROR (&00) (&01) (&02)(B) Routing code: U Weight: 70

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 means 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 apply:
Forward dump file to diagnostics department.
Restart UDSCT if necessary using &START DISTRIBUTION .

UDS0828

UDS-D: DCS CLOSED, RECONNECTION TRIED PERIODICALLY (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Connection of UDSCT to the DCS component has been terminated. UDSCT periodically attempts reconnection.

Response
Check DCS generation.

UDS0829

UDS-D: STATUS OF PRIMARY SUBTRANSACTION IS UNKNOWN, BECAUSE PARTNER CONFIGURATION (&00) COULD NOT BE REACHED (&01) (&02)(B) Routing code: U Weight: 70

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

UDS-D: PARTNER CONFIGURATION (&00) COULD NOT BE REACHED (&01) (&02)(B) Routing code: U Weight: 70

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

UDS-D: (&00) SECONDARY SUBTRANSACTIONS REMAIN IN PTC STATE (&01) (&02)(B) Routing code: U Weight: 70

Meaning
UDS-D terminates although secondary subtransactions are still in the PTC state.
(&00): number of remaining secondary transactions.

Response

Leave secondary transactions in the PTC state:
- The databases 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.
Determine the transaction ID using DAL command DISPLAY and terminate the secondary subtransaction using COMMIT or ABORT OPTION=PTC.
(Warning: Affects interconfiguration consistency)
Restart UDSCT using &START DISTRIBUTION. UDS-D makes another attempt to terminate the secondary subtransactions in a consistent state. This operation is successful only if the configurations of the associated primary subtransactions can be reached.

UDS0832

UDS-D: COMMAND EXECUTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
An UDS-D DAL command has been executed.

UDS0833

UDS-D ERROR FOR ENTER-JOB UDSCT (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS-D WARNING: THE DISTRIBUTION TABLE FILE CONTAINS ONLY COMMENTS (&00) (&01) (&02) (B) Routing code: U Weight: 70

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

UDS-D: MORE MESSAGES IN SYSOUT PROTOCOL OF UDS-D TASK UDSCT (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDS-D WARNING: SHORTAGE OF BCAM RESOURCES (&00) (&01) (&02).(B) Routing code: U Weight: 70

Meaning
There are frequent BCAM buffer bottlenecks during communication with the partner. This leads to relatively long UDS/SQL response times.
(&00): processor and application concerned.

Response
Check DCS generation. Ensure that the number/length of the BCAM buffers correspond to the size of the subschemas.

UDS0837

UDS-D WARNING: DCAM-APPLICATION (&00) CAN TEMPORARILY NOT BE OPENED. OPENING WILL BE TRIED PERIODICALLY (&01) (&02).(B) Routing code: U Weight: 70

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.

UDS0839

UDS-D ERROR: DCAM-APPLICATIONS CANNOT BE OPENED (&00) (&01) (&02).(B) Routing code: U Weight: 70

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

UDS-D: CONNECTION REQUEST REJECTED(B) Routing code: U Weight: 70

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

UDS-D: PREVIOUS OUTPUT OF DISPLAY DISTRIBUTION INCOMPLETE (&00) (&01) (&02).(B) Routing code: U Weight: 70

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

UDSADM STARTS (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0902

UDSADM READY (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
UDSADM initialization has completed.

UDS0904

WRONG SDF COMMAND (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
Wrong usage of SDF command.

UDS0905

UDSADM TERMINATED NORMALLY (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0906

UDSADM TERMINATED ABNORMALLY (&00) (&01) (&02)(B) Routing code: U Weight: 70

Response
Take Dump.
Restart UDSADM, if required.

UDS0907

UDSADM GENERATES DUMP (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
An error situation results in a UDSADM dump call.

UDS0908

UDSADM: SDF SUBSYSTEM NOT AVAILABLE (&00) (&01) (&02)(B) Routing code: U Weight: 70

Response
Make SDF available.

UDS0909

UDSADM: INVALID SDF SYNTAX FILE (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The currently assigned syntax file is invalid.

Response
Assign SDF syntax file for UDSADM.

UDS0910

UDSADM: DCAM SUBSYSTEM NOT AVAILABLE (&00) (&01) (&02)(B) Routing code: U Weight: 70

Response
Make DCAM available.

UDS0917

UDSADM: DCAM APPLICATION ALREADY OPEN (&00) (&01) (&02)(B) Routing code: U Weight: 70

Response
Terminate task and start UDSADM with another task.

UDS0920

UDSADM: UDS CONFIGURATION (&00) CONNECTED (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The UDS/SQL configuration has been connected.
(&00): name of UDS/SQL configuration

UDS0921

UDSADM: CONFIGURATION ALREADY CONNECTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The UDS/SQL configuration has already been connected to UDSADM.

UDS0922

UDSADM: UNKNOWN CONFIGURATION (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The UDS/SQL configuration has not been opened or DCAM administration is forbidden
(PP ADM=LOCAL).

UDS0923

UDSADM: CONNECTION REJECTED BY UDS (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The connection to the UDS/SQL configuration has been rejected
Possible reasons:

incorrect connection password (ADMPASS).
UDS/SQL is connected to another administration program.
security privilege of the administrator is not sufficient

Response
Remove the reason of rejection.

UDS0924

UDSADM: VIOLATION OF SECURITY REQUIREMENTS (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSADM: UDS CONFIGURATION (&00) DISCONNECTED (&01) (&02)(B) Routing code: U Weight: 70

UDS0940

UDSADM: RECEIVE MODE STARTED (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
UDSADM has been switched to receive mode. It waits for messages from the connected
UDS/SQL configuration.

UDS0942

UDSADM: RECEIVE MODE INTERRUPTED BY ADMINISTRATOR (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0943

UDSADM: RECEIVE MODE INTERRUPTED BY LOSCON (&00) (&01) (&02)(B) Routing code: U Weight: 70

UDS0950

UDSADM: NO OUTSTANDING MESSAGES (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
There are no messages from the connected UDS/SQL configuration.

UDS0971

UDSADM: CONNECTION TO UDS CONFIGURATION STILL EXISTS (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
A DCAM connection between UDSADM and the UDS/SQL configuration still exists.

UDS0980

UDSADM: UNKNOWN CONFIGURATION (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
The connection to the UDS/SQL configuration has failed.

Response
Check security aspects of the UDS/SQL configuration.

UDS0981

UDSADM: NO CONNECTION TO UDS CONFIGURATION (&00) (&01) (&02)(B) Routing code: U Weight: 70

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

UDSADM: CONNECTION TO UDS CONFIGURATION LOST (&00) (&01) (&02)(B) Routing code: U Weight: 70

Response
Repeat CONNECT-CONFIGURATION.

UDS0990

UDSADM: INVALID BS2000 VERSION (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
UDSADM was started under a BS2000 version which has not yet been released.

UDS0999

UDSADM: FATAL ERROR (&00) (&01) (&02)(B) Routing code: U Weight: 70

Meaning
A fatal error occurred in UDSADM.
(&02): additional diagnostic information.

Response
Take dump.

Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly

Central system messages