OpenSwitch log messages thrd__secession_cb to thrd_connect

Message text	Explanation and action
`thrd__secession_cb: Unable to bind client response`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__secession_cb: Unable to bind negotiation data`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__secession_cb: Unable to fetch negotiation description`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__secession_cb: Unable to get client response description`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__secession_cb: Unable to xfer client response`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__secession_cb: Unable to xfer negotiation data`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__secsession_cb: Unable to get control structure`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__sendinfo: Invalid thread type!`	This error is usually raised when a client disconnects abruptly due to time-out or some other reason. If OpenSwitch behavior is not affected, you can safely ignore this error. Otherwise, call Sybase Technical Support for assistance.
`thrd__sendinfo: Not a client thread!`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__sendinfo: srv_sendinfo() failed!`	This error is usually raised when a client disconnects abruptly due to time-out or some other reason. If OpenSwitch behavior is not affected, you can safely ignore this error. Otherwise, call Sybase Technical Support for assistance.
`thrd__sendinfo: srv_thread_props(SRV_T_IODEAD) failed!`	This error is usually raised when a client disconnects abruptly due to time-out or some other reason. If OpenSwitch behavior is not affected, you can safely ignore this error. Otherwise, call Sybase Technical Support for assistance.
`thrd__sendmsg: Unable to send message`	This error is usually raised when a client disconnects abruptly due to time-out or some other reason. If OpenSwitch behavior is not affected, you can safely ignore this error. Otherwise, call Sybase Technical Support for assistance.
`thrd__sendseclabels: CS_USERDATA NULL.`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__sendseclabels: srv_bind(CS_GET, SRV_NEGDATA) failed!`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__sendseclabels: srv_descfmt(CS_GET, SRV_NEGDATA) failed!`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__sendseclabels: srv_negotiate(CS_SET,SRV_NEG_SECLABEL) failed`	The client may have disconnected due to time-out or other errors. Call Sybase Technical Support if needed.
`thrd__sendseclabels: srv_negotiate(SRV_NEG_SECLABEL) failed!`	The client may have disconnected due to time-out or other errors. Call Sybase Technical Support if needed.
`thrd__sendseclabels: srv_numparams() failed!`	This is an internal OpenSwitch error. Call Sybase Technical Support if needed.
`thrd__sendseclabels: srv_senddone(SRV_DONE_FINAL) failed!`	The client may have disconnected due to time-out or other errors. Call Sybase Technical Support if needed.
`thrd__sendseclabels: srv_xferdata(CS_GET, SRV_NEGDATA) failed!`	The client may have disconnected due to time-out or other errors. Call Sybase Technical Support if needed.
`thrd__sendseclabels: Unable to fetch user data`	This is an internal OpenSwitch error. Call Sybase Technical Support if needed.
`thrd__spid: Error retrieving results`	This is an internal OpenSwitch error. Call Sybase Technical Support if needed.
`thrd__spid: Unable to allocate command`	OpenSwitch may have temporarily run out of memory. Check previous errors in the OpenSwitch error log. Call Sybase Technical Support if needed.
`thrd__spid: Unable to bind results`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__spid: Unable to build command`	OpenSwitch may have temporarily run out of memory. Check previous errors in the OpenSwitch error log. Call Sybase Technical Support if needed.
`thrd__spid: Unable to fetch results`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__srvparams: ct_bind() failed`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__srvparams: ct_describe() failed`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__srvparams: ct_fetch() != CS_END_DATA`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__srvparams: ct_res_info(CS_NUMDATA) failed`	OpenSwitch is unable to retrieve information from Adaptive Server. Check the Adaptive Server error log for additional error messages.
`thrd__srvparams: Output parameter not found`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__srvparams: srv_bind() failed`	OpenSwitch is unable to bind the output parameters to the client. The client may have disconnected due to time-out or other errors, or the output parameters are invalid. If the problem persists, call Sybase Technical Support.
`thrd__srvparams: srv_descfmt(CS_GET) failed`	OpenSwitch is unable to get the description of the output parameters from the client. The client may have disconnected due to time-out or other errors, or the output parameters are invalid. If the problem persists, call Sybase Technical Support.
`thrd__srvparams: srv_descfmt(CS_SET) failed`	OpenSwitch is unable to set the output parameters in the client. The client may have disconnected due to time-out or other errors, or the output parameters are invalid. If the problem persists, call Sybase Technical Support.
`thrd__srvparams: srv_numparams() failed`	OpenSwitch is unable to get the input parameters from the client. The client may have disconnected due to time-out or other errors, or the output parameters are invalid. If the problem persists, call Sybase Technical Support.
`thrd__srvparams: srv_thread_props(SRV_T_EVENT) failed`	OpenSwitch is unable to retrieve information from the client. The client may have disconnected due to time-out or other errors, or the output parameters are invalid. If the problem persists, call Sybase Technical Support.
`thrd__srvparams: srv_xferdata(CS_SET) failed`	OpenSwitch is unable to transfer the output parameters to the client. The client may have disconnected due to time-out or other errors, or the output parameters are invalid. If the problem persists, call Sybase Technical Support.
`thrd__transtate: ct_res_info(CS_TRANS_STATE) failed.`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd__use: Unable to allocate command`	OpenSwitch may have temporarily run out of memory. Check previous errors in the OpenSwitch error log. You may need to allocate more memory to the OpenSwitch process, or reevaluate the load on the OpenSwitch server given the current resources. If the problem persists, call Sybase Technical Support.
`thrd__use: Unable to build command`	OpenSwitch may have temporarily run out of memory. Check previous errors in the OpenSwitch error log. You may need to allocate more memory to the OpenSwitch process, or reevaluate the load on the OpenSwitch server given the current resources. If the problem persists, call Sybase Technical Support.
`thrd_bulk_passthru: ct_cmd_alloc() failed`	OpenSwitch may have temporarily run out of memory. Check previous errors in the OpenSwitch error log. You may need to allocate more memory to the OpenSwitch process, or reevaluate the load on the OpenSwitch server given the current resources. If the problem persists, call Sybase Technical Support.
`thrd_bulk_passthru: ct_cmd_drop() failed`	This is an internal OpenSwitch error. Call Sybase Technical Support for assistance.
`thrd_bulk_passthru: srv_thread_props(CS_GET,BULKTYPE) failed`	This is an internal OpenSwitch error. Call to srv_thread_props (CS_GET, SRV_T_BULKTYPE) failed. Verify that the client language command sent a valid bulk type (image or text type).
`thrd_bulk_passthru: Unrecognized BULK I/O type`	OpenSwitch does not recognize the bulk datatype sent by the client application. See the Open Server Server-Library/C Reference Manual under the SRV_T_BULKTYPE property for the valid types of bulk data acceptable in a bulk request.
`thrd_connect: failed to get a servername to connect to.`	OpenSwitch was unable to get a server name for the client to connect to. See the OpenSwitch error log for messages prior to this failure.
`thrd_connect: Login attempt failed because the target pool or server is locked.`	The client's login attempt was rejected because its designated server or pool has a LOCKED status. This message is only seen if the NOWAIT_ON_LOCKED configuration parameter is set to 1. Check this client’s server and pool in your OpenSwitch configuration, and reset the LOCKED status to UP or DOWN using the appropriate rp_server_status or rp_pool_status command: UP if you determine that the server or pool is ready to use again, DOWN if you want the clients to fail over to the next available server or pool.
`thrd_connect: Login retry failed because no eligible server can be found.`	After an initial login attempt failed, the client tried logging in again but was rejected because its designated server or pool has a LOCKED status. This message is only seen if the NOWAIT_ON_LOCKED configuration parameter is set to 1. Check this client’s server and pool in your OpenSwitch configuration, and reset the LOCKED status to UP or DOWN using the appropriate rp_server_status or rp_pool_status command: UP if you determine that the server or pool is ready to use again, DOWN if you want the clients to fail over to the next available server or pool.
`thrd_connect: Login retry failed because the target pool or server is locked.`	After an initial login attempt failed, the client tried logging in again but was rejected because its designated server or pool has a LOCKED status. This message is only seen if the NOWAIT_ON_LOCKED configuration parameter is set to 1. Check this client’s server and pool in your OpenSwitch configuration, and reset the LOCKED status to UP or DOWN using the appropriate rp_server_status or rp_pool_status command: UP if you determine that the server or pool is ready to use again, DOWN if you want the clients to fail over to the next available server or pool.
`thrd_connect: The thread's I/O channel is no longer valid. Please check that the client is still active and that it has connectivity to OpenSwitch.`	The thread’s I/O channel is dead. The client application may have terminated abruptly, or the connection may have terminated unexpectedly (due to hardware or network problems). Check the OpenSwitch error log for messages prior to this failure. The user needs to reconnect.
`thrd_connect: thrd__connect failed.`	OpenSwitch was unable to connect the client to the designated Adaptive Server. Check the OpenSwitch error log for messages prior to this failure.
`thrd_connect: Unable to allocate structure`	OpenSwitch may have temporarily run out of memory. Check previous errors in the OpenSwitch error log. You may need to allocate more memory to the OpenSwitch process, or reevaluate the load on the OpenSwitch server given the current resources. If the problem persists, call Sybase Technical Support.
`thrd_connect: Unable to determine password`	OpenSwitch was unable to look up the password of the incoming connection. Check that the password is valid.
`thrd_connect: Unable to determine username`	OpenSwitch was unable to look up the user name of the incoming connection. Check that the user name is valid.