Ansicht
Dokumentation

SQL0752 - Connection cannot be changed. Reason code is &1. ( OS/400 )

SQL0752 - Connection cannot be changed. Reason code is &1. ( OS/400 )

Addresses (Business Address Services)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by IBM.
SAP E-Book


Message : SQL0752
Connection cannot be changed. Reason code is &1.

Message Long Text :

Cause . . . . . : Connection cannot be made because the application process is not in a connectable state. The reason code is &1. Reason codes and their meanings are:
1 -- SQL is not in a connectable state. SQL enters the connectable state after a COMMIT or ROLLBACK. SQL leaves the connectable state when any SQL statement except a COMMIT, ROLLBACK, or CONNECT statement is run.
2 -- There are pending changes or open files under commitment control at the current server and the relational database (RDB) specified on the CONNECT request is not the current server.
3 -- A create SQL package request is being processed when not on a commit boundary.
4 -- The connection is locked by another invocation of Interactive SQL, or there is a level mismatch between the Interactive SQL product and IBM i.
5 -- The connection cannot be changed due to restrictions with remote connections and the job level commitment definition.
6 -- The connection cannot be changed to a remote system due to a SET TRANSACTION statement.
7 -- The connection cannot be changed using *RUW connection management because a previous connection is protected.
8 -- CONNECT RESET cannot start a local connection to RDB &2 because the RDB for the auxiliary storage pool (ASP) group of the thread is &3.
9 -- There is a mismatch between the active connection and the current ASP group of the thread.
Recovery . . . : Do one of the following based on the reason code:
1 -- Issue a COMMIT or ROLLBACK statement to enter the connectable state.
2 -- Close all files open under commitment control and issue a COMMIT or ROLLBACK statement.
3 -- Issue a COMMIT or ROLLBACK statement.
4 -- Exit Interactive SQL and try the request again. If Interactive SQL is active, the current server can only be changed using Interactive SQL.
5 -- All activation groups associated with the job level commitment definition must be local; or only one remote connection and no local connections can be associated with the job level commitment definition.
6 -- Issue a COMMIT or ROLLBACK statement.
7 -- Release the protected conversation followed by a COMMIT.
8 -- Change the ASP group of the thread to the ASP group for relational database &2.
9 -- Either change the ASP group of the thread to the ASP group for relational database &2 or use a CONNECT or SET CONNECTION statement to change the active connection.

Message File : QSQLMSG
Library Message File : QSYS2924


Fill RESBD Structure from EBP Component Structure   CPI1466 during Backup  
This documentation is copyright by IBM.

Length: 3266 Date: 20240426 Time: 053753     sap01-206 ( 2 ms )