Error response code 53

, ,
1

Product/components used and version/fix level:

A D A B A S N A T I V E S Q L VERSION 2.4.1

Detailed explanation of the problem:

When reading an adabas database by ISN from a native Cobol program, I’m intermittently getting error response code 53.
I’ve been advised to use the DYNAMCID parameter, but I don’t know how to code it in the program or if it should be specified in the compiler. I also don’t know if that’s the solution to the problem.
If anyone in this forum has encountered this problem, please help me resolve it. Thanks in advance.
I’ve attached the code for the read by ISN statement:
EXEC ADABAS
READ ISN
DECLARE UBO1 CURSOR
SELECT STATUS-OPER
FROM BOC-TRANS-DIV-SOLIC BOC-UPDATE1
WHERE ISN = :WS-ISN-BUSC
OPTIONS DBID=BD024
HOLD
END-EXEC

Error messages / full error message screenshot / log file:

1 A D A B A S S Q L T R A C E

PRTRCICS TRANS : ZS07 TASK : 016514 DATE : 25/09/2025 TIME : 02:42:28 TRACE : SI

SOURCE COMMAND :

COMMAND-CODE= L4,COMMAND-ID=CTRL,FILE-NUMBER=194,RESPONSE-CODE= 53

  RESPINT - ADABAS RESPONSE INTERPRETATION PROGRAM FOR ADABAS SQL

RESPONSE CODE: 53

RESPCICS

SHORT TEXT:

Wrong record buffer size. DB/FNR/Subcode …/…/…

EXPLANATION:

The record buffer is too small to contain all required Adabas values

in compressed form; or the record buffer size does not correspond

to the record-buffer size of the global format ID (GFID) already

established in Adabas. Or the ISN buffer is too small.

Question related to a free trial, or to a production (customer) instance?

2

It’s been a day or two since I used SQL with Adabas but here are some thoughts that might help.

If I recall correctly, response code 53 occurs when you try to update or release a record that is not currently held by your session. This could be due to a logic error somewhere else in the process or a not found condition but you’re still hitting the update, or maybe a concurrent access issue with another user.

3

Brian,

I just realized that this was reported from the SAG community forums. It seems to just be a coincidence that somebody else is reporting the code 53 error, but in this case it is with SQL reads instead of updates. This is the response from a SAG community forum member.