sqlcode=-923

rsshanmugam · New User Joined: 08 Mar 2005 Posts: 62 Location: Basildon

how to solve sqlcode -923.

i know that it is for db2 connection failure.

in our company we use package-plan structure and my bind is succesful and db2 also is up,i found db2 is up by quering via SPUFI.

my program is db2-cics program,it is one of visionplus component.

kindly help in this regard.

jagadeshdvn · Posted: Wed Aug 10, 2005 3:34 am

Hi,

Please see if this helps:

-923 CONNECTION NOT ESTABLISHED: DB2 condition REASON reason-code, TYPE
resource-type, NAME resource-name

Explanation: The connection to DB2 failed for the reason indicated by
condition, which can be any of the following:

o DB2 not up
o DB2 not operational
o DB2 shutdown in progress
o DB2 restricted access mode
o Allocation error
o DB2 - CICS attachment not up
o DB2 - CICS ENTRY disabled
o The object is dependent on facilities of a release of DB2 that is
newer than the release that you are currently running (fall back).
o DB2 restarted in LIGHT(YES) mode
Possible causes of an allocation error are:

o The application plan does not exist.

o The application plan is inoperative. An explicit REBIND or BIND is
required.

o The application plan is invalid. Underlying resources have changed.

o A required database, table space, table, or index is unavailable.

o Data set allocation failed for a required data set.

o There is insufficient virtual storage.

o The application is trying to execute the plan from a system
(environment) that was restricted when the plan was bound or rebound.
Check the SYSPLSYSTEM table to determine from which systems (for
example, IMS or CICS) the plan can be executed.

If the condition is "CICS attachment not up", then NAME indicates the DB2
subsystem that is not available. The reason code indicates the reason the
attachment is not available.

If the condition is "CICS entry disabled", then NAME indicates the entry
that is disabled.

System Action: The statement cannot be executed. The connection to DB2 is
not established.

Programmer Response: If the connection failed because either DB2 or a
required database, table space, table, or index was unavailable, wait
until it is available before invoking the application again.

If allocation failed for an application plan, REBIND the plan to determine

the problem. Error messages are produced explaining why the plan could not
be allocated.

For other types of allocation errors, installation action might be
required to correct the problem.

For CICS attachment failures, resolve the primary cause as noted by the
reason code. Then restart the attachment.

Problem Determination: The reason-code, resource-type, and resource-name
might not be available. If they are not available, nothing appears. If
they are available, refer to Section 4. DB2 Codes for an explanation of
the reason-code, resource-type, and resource-name.

Refer to message DSNT500I under DSNT... Messages for an explanation of
resource type and resource name. Refer to Table 3 in Appendix B, "Problem
determination" in item PROBLEM_DETERMIN for an explanation of resource type
codes. Any attempts to issue SQL statements after receiving SQLCODE -923
will cause unpredictable results.
SQLSTATE: 57015

rsshanmugam · New User Joined: 08 Mar 2005 Posts: 62 Location: Basildon

hai thank you yar how can you get this much detail can you tell me where you learnt.

thanks once again

prashanthkumarhs · New User Joined: 12 Aug 2009 Posts: 1 Location: Bangalore

Hi,

Those information will available in mainframe itself.

Bill Woodger · Posted: Mon Sep 05, 2011 5:20 pm

I'm sure the TS has been waiting six years for that...

dick scherrer · Posted: Mon Sep 05, 2011 11:52 pm

Hello and welcome to the fourm,

It is better to reply to currently active topics rather than those that have been inactive for years. . .

And when you do post a reply, you need to post something informative - telling people that something is "available in mainframe itself" is basically just clutter. . . And is not really correct. The information is in the documentation and is not part of the "mainframe itself".