Open ClientConnect and Open ServerConnect Messages and Codes

Home

Transaction Router Service and Mainframe Server Gateway Messages

Open ClientConnect and Open ServerConnect Messages and Codes

Chapter 2: Messages

Mainframe ClientConnect Messages

Table 2-5 contains Mainframe Client Connect (MCC) messages. Messages in this table also contain references to the original software, Mainframe Client Gateway (MCG). All messages refer to both MCC and MCG.

Table 2-5: Mainframe ClientConnect Messages
Number
Text and Explanation - 35001 through 35061
35001
Unknown RPC. Try 'exec mcg_help'.
Explanation: An unrecognized Mainframe Client Gateway administration procedure was requested.
Action: Check that the procedure name is valid.
35002
No RPC name. Try 'exec mcg_help'.
Explanation: A remote procedure name was not received on an RPC call to Mainframe Client Gateway.
Action: Check the calling program to ensure the RPC program is being invoked correctly.
35003
Invalid parameter. Try 'exec mcg_help'.
Explanation: An invalid parameter type was provided on an Mainframe Client Gateway administration call.
Action: Check the syntax of the call. All Mainframe Client Gateway administration parameters should be in character format.
35004
Missing parameter. Try 'exec mcg_help'.
Explanation: The Mainframe Client Gateway procedure requested requires a parameter.
Action: Check the syntax of the call and try again.
35005
Client number not found.
Explanation: The specified client number is not defined to Mainframe Client Gateway.
Action: Check the client number and try again.
35006
Ready.
Explanation: Informational message that Mainframe Client Gateway started.
Action: No action is required.
35007
Could not register with Sunlink gateway. Error %x.
Explanation: Mainframe Client Gateway cannot connect to the SunLink APPC gateway.
Action: Start the SunLink APPC gateway and restart Mainframe Client Gateway.
35008
Maximum number of clients exceeded.
Explanation: Mainframe Client Gateway reached the maximum number of configured mainframe-based clients.
Action: Restart Mainframe Client Gateway and increase the maximum number of clients allowed using the -M command line parameter. For additional information, see DirectConnect Transaction Router Service User's Guide.
35009
Syntax error. Try 'exec mcg_help'.
Explanation: A syntax error occurred on an Mainframe Client Gateway administration request.
Action: Check the syntax of the request and try again.
35010
Shutdown complete.
Explanation: Mainframe Client Gateway completed shutdown and is exiting.
Action: No action is required.
35011
Listening for client requests.
Explanation: Mainframe Client Gateway is ready to accept inbound LU6.2 requests from a host.
Action: No action is required.
35012
Error accepting host based request. Sunlink error %x.
Explanation: The SunLink APPC gateway returned an error when it received an LU6.2 conversation with a remote host.
Action: Refer to the SunLink error number for more information. Either an SNA error occurred or there is a problem with the remote transaction.
35013
Error spawning client thread. Error code %d.
Explanation: MCG could not spawn an internal thread to handle the host request.
Action: Increase the maximum client connections value specified by the -M start-up parameter.
For OS/2, also increase the value for the THREAD environment variable specified in the CONFIG.SYS file. If this problem continues, notify Sybase Technical Support.
35014
Unexpected return code from Sunlink Peek(). Sunlink error %x.
Explanation: The SunLink APPC gateway returned an error.
Action: Refer to the SunLink error number for more information. The most probable cause is that the SunLink APPC gateway needs to be restarted.
35015
TRACE: Client %d: %s.
Explanation: This is an informational event tracing message.
Action: Turn off tracing if you do not want to see this message.
35016
DB-Library Error: Error %d: %s.
Explanation: An error occurred with the DB-Library connection to a server.
Action: Look up the DB-Library error message for more information.
35017
DB-Library OS Error: Error %d: %s.
Explanation: DB-Library received an operating system error.
Action: Refer to the DB-Library error number for more information.
35018
MCG could not log in to requested server.
Explanation: Mainframe Client Gateway could not log into the server requested by a host-based client.
Action: Check the following using isql at the Mainframe Client Gateway machine to connect to the desired server:
Local interfaces file for a valid entry for that server.
Userid and password the host-based client is passing.
State of the requested server.
Network connectivity between the workstation where the Mainframe Client Gateway is running and the machine where the server is located.
35019
Unexpected event. code %d: %s.
Explanation: An unexpected error occurred.
Action: Refer to the text of the message for more details.
35020
Sunlink is down, restart Sunlink.
Explanation: The connection to the SunLink APPC gateway broke.
Action: Restart the SunLink APPC gateway.
35021
Sunlink is back up.
Explanation: Mainframe Client Gateway was able to reconnect to the SunLink APPC gateway.
Action: No action is required.
35022
Connection %s already exists.
Explanation: The connection defined to Mainframe Client Gateway already exists.
Action: Check the connection name for a duplicate.
35023
Could not open connection file.
Explanation: The connection file cannot be opened.
Action: If no connections are defined, ignore this message. If connections are defined, check file permissions.
35024
Connection has been added but an error occurred trying to activate it.
Explanation: The connection that was added cannot be opened.
Action: To recover from this error:
Check that the connection is a valid connection defined to SNA Services.
Check that your vendor's SNA Services is up.
Verify the connections using the snaping utility.
35025
Starting connection %s.
Explanation: A connection is being opened.
Action: No action is required.
35026
Could not find configuration file.
Explanation: The connection file cannot be opened.
Action: If no connections are defined, ignore this message. If connections are defined, check file permissions.
35027
SNA Services error %d starting connection %s. ALLOCATE_LISTEN failed. Verify a local transaction profile named 'MCG' exists.
Explanation: Mainframe Client Gateway could not register with SNA Services. This is probably because the Mainframe Client Gateway local transaction profile is missing.
Action: Verify that a local transaction profile exists.
35028
Transaction could not be registered for connection %s. Verify a local transaction profile named 'MCG' exists.
Explanation: Mainframe Client Gateway could not register with SNA Services. This is probably because the Mainframe Client Gateway local transaction profile is missing.
Action: Verify that a local transaction profile exists.
35029
Restarting all connections.
Explanation: An error occurred with SNA Services, and the Mainframe Client Gateway is attempting to reopen all defined connections. This is an informational message.
Action: No action is required.
35030
Some connections could not be restarted.
Explanation: While attempting to recover from an SNA Services error, Mainframe Client Gateway was unable to reopen some or all of the defined connections.
Action: Check SNA Services. Run the snaping utility to verify connections.
35031
Some connections could not be restarted.
Explanation: While attempting to recover from an SNA Services error, Mainframe Client Gateway was unable to reopen some or all of the defined connections.
Action: Check SNA Services. Run the snaping utility to verify connections.
35032
Connections have been restarted.
Explanation: Mainframe Client Gateway reopened all defined connections after an SNA Services error. This is an informational message.
Action: No action is required.
35033
SNA Services error %d in %s.
Explanation: SNA Services returned an error.
Action: Check your SNA Services error log. Run the snaping utility to verify connections.
35034
SNA Services attachment or connection failure.
Explanation: SNA Services notified Mainframe Client Gateway of a connection or attachment failure.
Action: Check your SNA Services error log. Run the snaping utility to verify connections.
35035
SNA Services error %d starting connection %s.
Explanation: An SNA Services error occurred starting a connection.
Action: To recover from this error:
Check that the connection is a valid connection defined to SNA Services.
Confirm SNA Services is running.
Verify the connection, using the snaping utility.
35036
Connection %s could not be found.
Explanation: You tried to delete a connection name that is not configured.
Action: Check the connection name and try again.
35037
Connection %1! could not be dropped because it is in use.
Explanation: You tried to drop a connection used by another host-based client.
Action: Wait for the client to disconnect before dropping the connection.
35038
Communications Manager is not running. Start Communications Manager then restart MCG.
Explanation: Mainframe Client Gateway cannot start because OS/2 Communications Manager is not running.
Action: Start OS/2 Communications Manager, and then start Mainframe Client Gateway.
35039
Transaction '%s' is not defined to Communications Manager. Add a transaction program definition.
Explanation: OS/2 Communications Manager does not have a local transaction program definition for this Mainframe Client Gateway.
Action: Add a local transaction program definition for this Mainframe Client Gateway.
35040
Communications Manager error in function %s. Primary code %x, Secondary code %x.
Explanation: The OS/2 Communications Manager returned an error.
Action: See IBM OS/2 Communications Manager manuals for further description of the error message.
35041
Sunlink error in %s. Error code %x.
Explanation: SunLink returned an error.
Action: See the SunLink manuals for further description of the error message.
35042
Function has not been implemented yet.
Explanation: The specified function is not implemented.
Action: You cannot perform this function. It is not supported by your software. Check with your sales representative or system consultant to determine the availability of a version that supports this function.
35043
MSG is being shutdown.
Explanation: You tried to start a new query after Mainframe Client Gateway started a shutdown.
Action: Retry the query later when Mainframe Client Gateway restarts.
35044
HP SNAP-IX APPC Services error, %1!, primary code %2!, secondary code %3!. Refer to SNAP-IX APPC Programming Guide.
Explanation: An HP SNAP-IX function returned an error.
Action: See the HP SNAP-IX documentation for an explanation of the code.
35045
srv_alloc failed to allocate memory of size %1!
Explanation: An internal error occurred.
Action: Call Sybase Technical Support.
35046
srv_descfmt failed for column number %1!
Explanation: An internal error occurred.
Action: Call Sybase Technical Support.
35047
srv_bind failed for column number %1!
Explanation: An internal error occurred.
Action: Call Sybase Technical Support.
35048
Transaction '%1!' is not defined as an invocable TP in the SNAP-IX configuration. Add an invocable transaction program definition.
Explanation: A local transaction must be defined for each copy of the Mainframe Client Gateway running on a machine. The transaction name must match the Mainframe Client Gateway server name.
Action: Add a local transaction using the same name as your Mainframe Client Gateway -S parameter.
35049
Sunlink function mc_allocate failed with unique session name %1! and remote transaction name %2!.
Explanation: A Sunlink SNA function error occurred.
Action: This is an informational message that is accompanied by other messages stating the specific error code.
35050
HP SNAP-IX mc_allocate failed with local TP %1!, partner LU %2!, mode name %3! and transaction name %4!.
Explanation: An HP SNAP-IX SNA function error occurred.
Action: This is an informational message that is accompanied by other messages stating the specific error code.
35051
OS/2 Communications Manager error, mc_allocate with local LU %1!, partner LU %2!, modename %3! and transaction name %4!
Explanation: An error occurred on an OS/2 Communications SNA function.
Action: This is an informational message that is accompanied by another message stating the specific error code.
35052
AIX SNA Services function snalloc with mode %1! and tpn %2! failed.
Explanation: An AIX SNA Services function error occurred.
Action: This is an informational message that is accompanied by other messages stating the specific error code.
35053
NT SNA Server error, function %1!. Primary code %2!, Secondary code %3!
Explanation: This message provides additional information after a call to Windows NT SNA server failed.
Action: No action is required.
35054
NT SNA Server error, allocate with local LU %1!, partner LU %2!, modename %3! and transaction name %4!
Explanation: This message provides additional information after a call to Windows NT SNA server failed.
Action: No action is required.
35055
Novell NetWare for SAA error, function %1!. Primary code %2! secondary code %3!. Refer to Novell APPC Technical Reference.
Explanation: A Novell NetWare error occurred.
Action: Look up the primary and secondary codes in the Novell APPC Technical Reference and follow the instructions.
35056
Novell NetWare for SAA error, function %1!. Primary code %2!. Refer to Novell APPC Technical Reference.
Explanation: A Novell NetWare error occurred.
Action: Look up the function and primary code in the Novell APPC Technical Reference and follow the instructions.
35057
Novell NetWare for SAA error, mc_allocate with local LU %1!, partner LU %2!, Modename %3!, Transaction %4!
Explanation: This is an error with Novell NetWare's mc_allocate routine.
Action: Look up mc_allocate in the Novell NetWare documentation to identify the problem and take corrective action.
35058
Error: Invalid %1! %2! has been specified. Please make sure it is defined in the sybnetgw.cfg file used by the SYBCNOS nlm.
Explanation: Invalid configuration values were supplied to Mainframe Client Gateway.
Action: Check the sybnetgw.cfg file used by the SYBCNOS nlm to be sure that the configuration files are defined.
35059
NCR SNA error, function %1!. Primary code %2!, Secondary code %3!
Explanation: An NCR SNA error occurred.
Action: Look up the error in the NCR SNA reference document and follow the instructions.
35060
NCR SNA error, allocate with local LU %1!, partner LU %2!, modename %3! and transaction name %4!
Explanation: An error with the NCR SNA allocate routine occurred.
Action: No action is required.
35061
TCP system call %1! failed with error code %2!
Explanation: This message comes from TCP Mainframe Client Gateway on various TCP related calls. It generally indicates a network problem.
Action: Look up the error in the SNA reference document and follow the instructions.

Number	Text and Explanation - 35001 through 35061
35001	Unknown RPC. Try 'exec mcg_help'. Explanation: An unrecognized Mainframe Client Gateway administration procedure was requested. Action: Check that the procedure name is valid.
35002	No RPC name. Try 'exec mcg_help'. Explanation: A remote procedure name was not received on an RPC call to Mainframe Client Gateway. Action: Check the calling program to ensure the RPC program is being invoked correctly.
35003	Invalid parameter. Try 'exec mcg_help'. Explanation: An invalid parameter type was provided on an Mainframe Client Gateway administration call. Action: Check the syntax of the call. All Mainframe Client Gateway administration parameters should be in character format.
35004	Missing parameter. Try 'exec mcg_help'. Explanation: The Mainframe Client Gateway procedure requested requires a parameter. Action: Check the syntax of the call and try again.
35005	Client number not found. Explanation: The specified client number is not defined to Mainframe Client Gateway. Action: Check the client number and try again.
35006	Ready. Explanation: Informational message that Mainframe Client Gateway started. Action: No action is required.
35007	Could not register with Sunlink gateway. Error %x. Explanation: Mainframe Client Gateway cannot connect to the SunLink APPC gateway. Action: Start the SunLink APPC gateway and restart Mainframe Client Gateway.
35008	Maximum number of clients exceeded. Explanation: Mainframe Client Gateway reached the maximum number of configured mainframe-based clients. Action: Restart Mainframe Client Gateway and increase the maximum number of clients allowed using the -M command line parameter. For additional information, see DirectConnect Transaction Router Service User's Guide.
35009	Syntax error. Try 'exec mcg_help'. Explanation: A syntax error occurred on an Mainframe Client Gateway administration request. Action: Check the syntax of the request and try again.
35010	Shutdown complete. Explanation: Mainframe Client Gateway completed shutdown and is exiting. Action: No action is required.
35011	Listening for client requests. Explanation: Mainframe Client Gateway is ready to accept inbound LU6.2 requests from a host. Action: No action is required.
35012	Error accepting host based request. Sunlink error %x. Explanation: The SunLink APPC gateway returned an error when it received an LU6.2 conversation with a remote host. Action: Refer to the SunLink error number for more information. Either an SNA error occurred or there is a problem with the remote transaction.
35013	Error spawning client thread. Error code %d. Explanation: MCG could not spawn an internal thread to handle the host request. Action: Increase the maximum client connections value specified by the -M start-up parameter. For OS/2, also increase the value for the THREAD environment variable specified in the CONFIG.SYS file. If this problem continues, notify Sybase Technical Support.
35014	Unexpected return code from Sunlink Peek(). Sunlink error %x. Explanation: The SunLink APPC gateway returned an error. Action: Refer to the SunLink error number for more information. The most probable cause is that the SunLink APPC gateway needs to be restarted.
35015	TRACE: Client %d: %s. Explanation: This is an informational event tracing message. Action: Turn off tracing if you do not want to see this message.
35016	DB-Library Error: Error %d: %s. Explanation: An error occurred with the DB-Library connection to a server. Action: Look up the DB-Library error message for more information.
35017	DB-Library OS Error: Error %d: %s. Explanation: DB-Library received an operating system error. Action: Refer to the DB-Library error number for more information.
35018	MCG could not log in to requested server. Explanation: Mainframe Client Gateway could not log into the server requested by a host-based client. Action: Check the following using isql at the Mainframe Client Gateway machine to connect to the desired server: Local interfaces file for a valid entry for that server. Userid and password the host-based client is passing. State of the requested server. Network connectivity between the workstation where the Mainframe Client Gateway is running and the machine where the server is located.
35019	Unexpected event. code %d: %s. Explanation: An unexpected error occurred. Action: Refer to the text of the message for more details.
35020	Sunlink is down, restart Sunlink. Explanation: The connection to the SunLink APPC gateway broke. Action: Restart the SunLink APPC gateway.
35021	Sunlink is back up. Explanation: Mainframe Client Gateway was able to reconnect to the SunLink APPC gateway. Action: No action is required.
35022	Connection %s already exists. Explanation: The connection defined to Mainframe Client Gateway already exists. Action: Check the connection name for a duplicate.
35023	Could not open connection file. Explanation: The connection file cannot be opened. Action: If no connections are defined, ignore this message. If connections are defined, check file permissions.
35024	Connection has been added but an error occurred trying to activate it. Explanation: The connection that was added cannot be opened. Action: To recover from this error: Check that the connection is a valid connection defined to SNA Services. Check that your vendor's SNA Services is up. Verify the connections using the snaping utility.
35025	Starting connection %s. Explanation: A connection is being opened. Action: No action is required.
35026	Could not find configuration file. Explanation: The connection file cannot be opened. Action: If no connections are defined, ignore this message. If connections are defined, check file permissions.
35027	SNA Services error %d starting connection %s. ALLOCATE_LISTEN failed. Verify a local transaction profile named 'MCG' exists. Explanation: Mainframe Client Gateway could not register with SNA Services. This is probably because the Mainframe Client Gateway local transaction profile is missing. Action: Verify that a local transaction profile exists.
35028	Transaction could not be registered for connection %s. Verify a local transaction profile named 'MCG' exists. Explanation: Mainframe Client Gateway could not register with SNA Services. This is probably because the Mainframe Client Gateway local transaction profile is missing. Action: Verify that a local transaction profile exists.
35029	Restarting all connections. Explanation: An error occurred with SNA Services, and the Mainframe Client Gateway is attempting to reopen all defined connections. This is an informational message. Action: No action is required.
35030	Some connections could not be restarted. Explanation: While attempting to recover from an SNA Services error, Mainframe Client Gateway was unable to reopen some or all of the defined connections. Action: Check SNA Services. Run the snaping utility to verify connections.
35031	Some connections could not be restarted. Explanation: While attempting to recover from an SNA Services error, Mainframe Client Gateway was unable to reopen some or all of the defined connections. Action: Check SNA Services. Run the snaping utility to verify connections.
35032	Connections have been restarted. Explanation: Mainframe Client Gateway reopened all defined connections after an SNA Services error. This is an informational message. Action: No action is required.
35033	SNA Services error %d in %s. Explanation: SNA Services returned an error. Action: Check your SNA Services error log. Run the snaping utility to verify connections.
35034	SNA Services attachment or connection failure. Explanation: SNA Services notified Mainframe Client Gateway of a connection or attachment failure. Action: Check your SNA Services error log. Run the snaping utility to verify connections.
35035	SNA Services error %d starting connection %s. Explanation: An SNA Services error occurred starting a connection. Action: To recover from this error: Check that the connection is a valid connection defined to SNA Services. Confirm SNA Services is running. Verify the connection, using the snaping utility.
35036	Connection %s could not be found. Explanation: You tried to delete a connection name that is not configured. Action: Check the connection name and try again.
35037	Connection %1! could not be dropped because it is in use. Explanation: You tried to drop a connection used by another host-based client. Action: Wait for the client to disconnect before dropping the connection.
35038	Communications Manager is not running. Start Communications Manager then restart MCG. Explanation: Mainframe Client Gateway cannot start because OS/2 Communications Manager is not running. Action: Start OS/2 Communications Manager, and then start Mainframe Client Gateway.
35039	Transaction '%s' is not defined to Communications Manager. Add a transaction program definition. Explanation: OS/2 Communications Manager does not have a local transaction program definition for this Mainframe Client Gateway. Action: Add a local transaction program definition for this Mainframe Client Gateway.
35040	Communications Manager error in function %s. Primary code %x, Secondary code %x. Explanation: The OS/2 Communications Manager returned an error. Action: See IBM OS/2 Communications Manager manuals for further description of the error message.
35041	Sunlink error in %s. Error code %x. Explanation: SunLink returned an error. Action: See the SunLink manuals for further description of the error message.
35042	Function has not been implemented yet. Explanation: The specified function is not implemented. Action: You cannot perform this function. It is not supported by your software. Check with your sales representative or system consultant to determine the availability of a version that supports this function.
35043	MSG is being shutdown. Explanation: You tried to start a new query after Mainframe Client Gateway started a shutdown. Action: Retry the query later when Mainframe Client Gateway restarts.
35044	HP SNAP-IX APPC Services error, %1!, primary code %2!, secondary code %3!. Refer to SNAP-IX APPC Programming Guide. Explanation: An HP SNAP-IX function returned an error. Action: See the HP SNAP-IX documentation for an explanation of the code.
35045	srv_alloc failed to allocate memory of size %1! Explanation: An internal error occurred. Action: Call Sybase Technical Support.
35046	srv_descfmt failed for column number %1! Explanation: An internal error occurred. Action: Call Sybase Technical Support.
35047	srv_bind failed for column number %1! Explanation: An internal error occurred. Action: Call Sybase Technical Support.
35048	Transaction '%1!' is not defined as an invocable TP in the SNAP-IX configuration. Add an invocable transaction program definition. Explanation: A local transaction must be defined for each copy of the Mainframe Client Gateway running on a machine. The transaction name must match the Mainframe Client Gateway server name. Action: Add a local transaction using the same name as your Mainframe Client Gateway -S parameter.
35049	Sunlink function mc_allocate failed with unique session name %1! and remote transaction name %2!. Explanation: A Sunlink SNA function error occurred. Action: This is an informational message that is accompanied by other messages stating the specific error code.
35050	HP SNAP-IX mc_allocate failed with local TP %1!, partner LU %2!, mode name %3! and transaction name %4!. Explanation: An HP SNAP-IX SNA function error occurred. Action: This is an informational message that is accompanied by other messages stating the specific error code.
35051	OS/2 Communications Manager error, mc_allocate with local LU %1!, partner LU %2!, modename %3! and transaction name %4! Explanation: An error occurred on an OS/2 Communications SNA function. Action: This is an informational message that is accompanied by another message stating the specific error code.
35052	AIX SNA Services function snalloc with mode %1! and tpn %2! failed. Explanation: An AIX SNA Services function error occurred. Action: This is an informational message that is accompanied by other messages stating the specific error code.
35053	NT SNA Server error, function %1!. Primary code %2!, Secondary code %3! Explanation: This message provides additional information after a call to Windows NT SNA server failed. Action: No action is required.
35054	NT SNA Server error, allocate with local LU %1!, partner LU %2!, modename %3! and transaction name %4! Explanation: This message provides additional information after a call to Windows NT SNA server failed. Action: No action is required.
35055	Novell NetWare for SAA error, function %1!. Primary code %2! secondary code %3!. Refer to Novell APPC Technical Reference. Explanation: A Novell NetWare error occurred. Action: Look up the primary and secondary codes in the Novell APPC Technical Reference and follow the instructions.
35056	Novell NetWare for SAA error, function %1!. Primary code %2!. Refer to Novell APPC Technical Reference. Explanation: A Novell NetWare error occurred. Action: Look up the function and primary code in the Novell APPC Technical Reference and follow the instructions.
35057	Novell NetWare for SAA error, mc_allocate with local LU %1!, partner LU %2!, Modename %3!, Transaction %4! Explanation: This is an error with Novell NetWare's mc_allocate routine. Action: Look up mc_allocate in the Novell NetWare documentation to identify the problem and take corrective action.
35058	Error: Invalid %1! %2! has been specified. Please make sure it is defined in the sybnetgw.cfg file used by the SYBCNOS nlm. Explanation: Invalid configuration values were supplied to Mainframe Client Gateway. Action: Check the sybnetgw.cfg file used by the SYBCNOS nlm to be sure that the configuration files are defined.
35059	NCR SNA error, function %1!. Primary code %2!, Secondary code %3! Explanation: An NCR SNA error occurred. Action: Look up the error in the NCR SNA reference document and follow the instructions.
35060	NCR SNA error, allocate with local LU %1!, partner LU %2!, modename %3! and transaction name %4! Explanation: An error with the NCR SNA allocate routine occurred. Action: No action is required.
35061	TCP system call %1! failed with error code %2! Explanation: This message comes from TCP Mainframe Client Gateway on various TCP related calls. It generally indicates a network problem. Action: Look up the error in the SNA reference document and follow the instructions.


	Expand Search