Return Code 39 - CANNOT PROCESS OLD REQUEST

CA Datacom/DB Return Codes › Return Codes › Return Code 39 - CANNOT PROCESS OLD REQUEST

Return Code 39 - CANNOT PROCESS OLD REQUEST

Reason:

Request Area and index changes have prevented the processing of a request.

Action:

See the following internal return code for details.

Return Code 39 Internal Return Codes

Dec	Hex	M	B	Explanation	User Response
089	59	N	N	Using the DATACOM or CBLDBMS entry point, the application program issued either a Locate Next command (LOCNE, LOCNK, or LOCNX) or a Read Next command (RDUNE, RDUNX, REDNE, or REDNX), but the request cannot be processed because the Request Area and the index have been changed.	Correct the application program so that the Request Area and the related index are available for the next-type command. Note: Although a Request Area can be saved during an entire job for use by next-type commands, it cannot be saved beyond job boundaries.
090	5A	N	N	You attempted to run a request through an old entry point (not DBNTRY) against a DBID whose Index Area (IXX) has been INITed with OLDEP=NO.	Either INIT the IXX with OLDEP=YES and RETIX the DBID, or use the current and preferred entry point.

Dec

Hex

Explanation

User Response

089

Using the DATACOM or CBLDBMS entry point, the application program issued either a Locate Next
command (LOCNE, LOCNK, or
LOCNX) or a Read Next command (RDUNE, RDUNX, REDNE, or
REDNX), but the request cannot be processed because the Request
Area and the index have been changed.

Correct the application program so that the Request Area and the related index are available for the next-type command.

Note: Although a Request Area can be saved during an entire job for use by next-type commands, it cannot be saved beyond job boundaries.

090

You attempted to run a request through an old entry point (not DBNTRY) against a DBID whose
Index Area (IXX) has been INITed
with OLDEP=NO.

Either INIT the IXX with OLDEP=YES and RETIX the DBID, or use the current and preferred entry point.