This table contains Transaction Router Service (TRS) and Mainframe
Server Gateway (MSG) messages. All messages begin with the name “Msg.”
Table 2-4: TRS and MSG messages - 34150 through
34334
Message number
|
Text and explanation -
34150 through 34334
|
34150
|
MSG: Request rejected. No password was given, a password is required.
Explanation: The password is missing.
Action: Enter the correct password.
|
34152
|
MSG: Request rejected: Missing parameter.
Explanation: A Net Gateway TRS control parameter is missing.
Action: Check the syntax of the command and reenter it.
|
34153
|
MSG: Request rejected: Invalid action code.
Explanation: You entered an invalid parameter on a gateway control request.
Action: Check the syntax of the command and reenter it.
|
34154
|
MSG: Request rejected: Remote procedure '%1!' not found. Retry the request with a valid remote procedure name or contact the Gateway Administrator.
Explanation: The referred RPC is unknown.
Action: Use the sgw_status rpc command
to determine the status of the erroneous RPC. Reenter the command
with the correct RPC name.
|
34155
|
MSG: Request rejected: Remote procedure '%1!' is already defined.
Explanation: You tried to add a procedure that already exists.
Action: Use the sgw_status rpc command
to determine the status of the erroneous RPC. Check the RPC name
and try again.
|
34156
|
MSG: Request rejected: Connection '%1!'to ‘%2!’ is already defined.
Explanation: You tried to add a connection that already exists.
Action: Use the sgw_status connections command
to determine the status of all connections.
|
34157
|
MSG: Request rejected: Could not find that client. Retry the request with an active client ID.
Explanation: You tried to disconnect a client using an invalid client
ID.
Action: Use the sgw_status clients command
to determine the status of clients. Verify the client ID and try
again.
|
34158
|
MSG: Request rejected: Could not find that connection. Retry the request with a valid connection ID.
Explanation: You tried to deactivate or activate a connection using an
invalid connection ID.
Action: Use the sgw_status connection command
to determine the status of the connection ID. Verify the connection
ID and try again.
|
34201
|
MSG: Request rejected: Language transaction is set inactive. Contact the Gateway administrator.
Explanation: The procedure used to process language requests is inactive.
Action: Use the sgw_status rpcs command
to determine the status of the language translation. Usually it
is SYRT or AMD2 depending on your implementation of OCC and OSC.
|
34202
|
MSG: Request rejected. No host connections are available. Wait for an available connection, or contact the Gateway Administrator.
Explanation: There are no gateway-mainframe connections available.
Action: Use the sgw_status connections and
the sgw_status clients commands to add
additional connections to alleviate the problem.
|
34203
|
MSG report: Could not start conversation with remote transaction %1!. Contact Gateway administrator or host network operator. Transaction %2!
Explanation: An LU 6.2 conversation cannot be started with the requested
host transaction.
Action: Check the appropriate SNA server error log to determine why
the transaction could not be started.
|
34204
|
MSG report: Unexpected end of results from host transaction. Contact Gateway administrator or host network operator. Transaction %1!
Explanation: The host conversation terminated abnormally while a result
set was being received.
Action: This is usually due to a CICS application abend; however,
it can also occur if the session with the host is unbound. Contact
your CICS systems programmer.
|
34206
|
MSG: File error: Cannot open or create the RPC file. Check the SYBASE directory read/write permissions.
Explanation: The file containing RPC definitions cannot be opened. This
file does not exist if RPCs are not defined.
Action: If RPC definitions are not defined, ignore this error. This
message always appears when a newly installed MSG starts. If an
RPC is defined, check the permissions on the RPC file and verify
that your SYBASE environment variable is set correctly.
|
34207
|
MSG: File error: Cannot open or create the connection file. Check the SYBASE directory read/write permissions.
Explanation: The file containing connection definitions cannot be opened.
This file does not exist if connections are not defined.
Action: If connection definitions are not defined, ignore this error.
This message always appears when a newly installed MSG starts.
If connections are defined, check the permissions on the connection
file and verify that your SYBASE environment variable is set correctly.
|
34208
|
MSG warning: Client disconnected while receiving results.
Explanation: The LAN connection between MSG and a client was disconnected
while a result set was being forwarded to the client.
Action: No action required.
|
34209
|
MSG: Request rejected: Cannot perform delete, remote procedure '%1!' is in use. Deactivate the remote procedure then try again.
Explanation: An RPC that is in use cannot be deleted.
Action: Retry the command when the RPC is not in use. If the RPC
is used constantly, first deactivate the RPC using sgw_deactrpc so
that new clients cannot use it to start a query.
When all current users finish using the connection, delete
it.
|
34210
|
MSG: Request rejected: Cannot perform delete, connection is in use. Retry the request after the connection is free or inactive.
Explanation: A connection that is in use cannot be deleted.
Action: Retry the command when the connection is not in use. If the
connection is used constantly, first deactivate the connection using sgw_deactcon so
new clients cannot use it to start a query.
When all current users finish using the connection, delete
it.
|
34211
|
MSG: Sunlink is back up.
Explanation: The Sunlink APPC Gateway was down. Mainframe Server Gateway
detected that the Sunlink APPC Gateway restarted.
Action: No action is required.
|
34213
|
MSG: Security violation: Connection must be through a SQL Server. Change your DSQUERY value, or contact the administrator.
Explanation: The request was rejected because Mainframe Server Gateway
is running with the -D start-up parameter to
prohibit direct requests.
Action: Execute the desired procedure as an RPC through SQL Server,
or restart MSG without the -D parameter.
|
34214
|
MSG: Connection file not found.
Explanation: Mainframe Server Gateway cannot open the file containing connection definitions.
If connections are not defined, this is an error, which is the case
when you start MSG for the first time.
Action: If connections are defined, ignore this error. This message
always appears when a newly installed MSG is started.
If connections are defined, check the permissions on the connection
file and verify that your SYBASE environment variable is set correctly.
|
34215
|
MSG: Request rejected: Login rejected, Gateway is being shutdown. Contact the Gateway administrator.
Explanation: Mainframe Server Gateway is shutting down and is not accepting
any new requests.
Action: Retry when MSG is started again.
|
34216
|
MSG: Request rejected: Login failed, maximum number of clients exceeded. Wait for an available slot, or contact the Gateway administrator.
Explanation: The maximum number of concurrent users was exceeded.
Action: Restart MSG using a larger value for the -M parameter.
|
34217
|
MSG: RPC file not found.
Explanation: The Mainframe Server Gateway file containing RPC definitions
cannot open. This file does not exist if RPCs are not defined.
Action: If RPCs are not defined, ignore this error. This message
always appears when a newly installed Mainframe Server Gateway starts.
If RPCs are defined, check the permissions on the RPC file
and verify that your SYBASE environment variable is set correctly.
|
34218
|
MSG: Could not start Connection %1! Modename %2!. Connection set inactive. Contact host network operator or Gateway administrator.
Explanation: The connection could not be made due to an SNA problem or
a configuration error.
Action: Contact your VTAM operator to verify the state of your connection.
Use sgw_actcon all to restart connections
once the problem is resolved.
|
34219
|
SNA services stopped or the network crashed. Some connections may have to be reactivated.
Explanation: SNA services notified Mainframe Server Gateway of an attachment
or connection failure.
Action: Check SNA services error log to determine error. Coordinate
with VTAM operator to ensure connectivity problems are corrected.
|
34220
|
Connection %1! started.
Explanation: A connection started.
Action: No action is required.
|
34221
|
MSG starting. Version (%1!)
Explanation: The Transaction Router Service started.
Action: No action is required.
|
34222
|
MSG: startup completed. Ready.
Explanation: Mainframe Server Gateway is ready to accept client requests.
Action: No action is required.
|
34223
|
MSG: Security violation: Login denied (no login entry or incorrect password) Contact the Gateway administrator.
Explanation: An incorrect password was specified, or the user ID is not
defined to Mainframe Server Gateway.
Action: Use the correct password or add the user ID to Mainframe
Server Gateway.
|
34224
|
MSG: Security group file not found.
Explanation: Mainframe Server Gateway could not find the security group
file.
Action: This is not an error if no logins, transaction groups, or
connection groups are defined. Mainframe Server Gateway file creates
the file the first time one of these is added.
|
34225
|
MSG: File error: Cannot open or create the security group file. Check SYBASE directory read/write permissions.
Explanation: You cannot open or create the security group file.
Action: Check the read/write permissions in the $SYBASE directory.
|
34226
|
MSG: Request rejected. Could not find that login entry. Retry the request with a valid login name.
Explanation: A gateway control operation was requested on a login that
is not defined.
Action: Check the syntax of the gateway control operation or confirm
that the user ID is valid.
|
34227
|
MSG: Request rejected. Cannot perform delete, login '%1!' is in use. Retry the request after the login is free or inactive.
Explanation: A login cannot be dropped if a user is currently connected
using that ID.
Action: Either disconnect that client using sgw_disclient or
wait for that user to log off.
|
34228
|
MSG: Request rejected. Login '%1!' is already defined.
Explanation: You tried to define a login that is already defined.
Action: Use another name or delete the login before redefining it.
For additional information, see the Mainframe Connect DirectConnect
for z/OS Option User's Guide for Transaction Router
Services.
|
34229
|
MSG: Security violation: Your login '%1!' does not have authorization to run Gateway control functions. Contact Gateway administrator.
Explanation: Your user ID does not have permission to execute gateway control
procedures.
Action: Have the Gateway administrator grant this authority to your
account. For additional instructions, see the Mainframe Connect
DirectConnect for z/OS Option User's Guide for Transaction
Router Services.
|
34230
|
MSG: Request rejected. Transaction group '%1!' is already defined.
Explanation: You tried to add a transaction group that already exists.
Action: Either use a different name or delete the existing group.
For further information, see the Mainframe Connect DirectConnect
for z/OS Option User's Guide for Transaction Router
Services.
|
34231
|
MSG: Request rejected. Transaction group is not defined. Retry the request with a valid transaction group name.
Explanation: You tried a gateway control operation on a transaction group
that does not exist.
Action: Check the syntax of the command and the group name. For additional
information, see the Mainframe Connect DirectConnect for z/OS
Option User's Guide for Transaction Router Services.
|
34232
|
MSG: Request rejected. Remote procedure '%1!' is already in transaction group.
Explanation: You tried to add an RPC to a group when that RPC was already
defined to that group.
Action: Use another name or delete the RPC before redefining it.
For additional information, see the Mainframe Connect DirectConnect
for z/OS Option User's Guide for Transaction Router
Services.
|
34233
|
MSG: Request rejected. Remote procedure '%1!' is not in transaction group.
Explanation: You tried to delete an RPC from a transaction group to which
the RPC does not belong.
Action: Check the RPC name. For additional information, see the Mainframe
Connect DirectConnect for z/OS Option User's
Guide for Transaction Router Services.
|
34234
|
MSG: Request rejected. Connection group '%1!' is already defined.
Explanation: You tried to add a connection group that already exists.
Action: Use a different name or delete the existing group. For additional
information, see the Mainframe Connect DirectConnect for z/OS
Option User's Guide for Transaction Router Services.
|
34235
|
MSG: Request rejected. Connection group is not defined. Retry the request with a valid connection group name.
Explanation: You tried a gateway control operation on a connection group
that does not exist.
Action: Check the syntax of the command and the group name. For additional
information, see the Mainframe Connect DirectConnect for z/OS
Option User's Guide for Transaction Router Services.
|
34236
|
MSG: Request rejected. Connection '%1!' is already in connection group.
Explanation: You tried to add a connection to a group that was already
defined to the group.
Action: Check the connection name. For additional information, see
the Mainframe Connect DirectConnect for z/OS Option User's
Guide for Transaction Router Services.
|
34237
|
MSG: Request rejected. Connection '%1!' is not in connection group. Retry the request with a connection name that is part of that group.
Explanation: You tried to add a connection to a group that was already
defined to the group.
Action: Check the connection name. For additional information, see
the Mainframe Connect DirectConnect for z/OS Option .User's
Guide for Transaction Router Services
|
34238
|
MSG: Security violation: Access to remote procedure '%1!' is denied. You are not authorized to access that remote procedure. Contact the Gateway administrator.
Explanation: You tried to execute an RPC that is not defined to your transaction
group.
Action: Ask the Gateway administrator to define the RPC to your transaction
group.
|
34239
|
MSG: Request rejected: Remote procedure '%1!' is set inactive. Contact the Gateway administrator.
Explanation: The requested procedure is inactive.
Action: Use sgw_actrpc to reactivate
the procedure.
|
34240
|
Msg: SNA servers are not responding. Make sure attachment and connections are active through SNA services.
Explanation: A system call to SNA Services did not return within the period
of time allowed. This can occur due to one of the following:
On slow SDLC lines, the default time of 15 seconds may not
be sufficient to allow the attachment to start. You can increase
this value using the -Qseconds start-up parameter.
Action: When a timeout occurs, the default behavior of Mainframe
Server Gateway is to mark the connection inactive so that the error
is avoided on a subsequent request. If you want the connection to
remain “active,” use the -d start-up
parameter to prohibit connections from being marked “inactive” on
no-recoverable allocate failures and SNA Services timeouts.
|
34241
|
MSG: Some connections could not be started.
Explanation: When connections were activated, an error was detected on
one or more of them.
Action: Correct the error and use the sgw_actcon procedure
to reactivate the connection(s).
|
34242
|
MSG shutdown completed.
Explanation: The gateway is disabled.
Action: No action is required.
|
34243
|
MSG: Request rejected. Invalid RPC request. Check that all RPC parameters used are valid datatypes and that the RPC name is correct.
Explanation: An RPC call was made using a parameter datatype that is not
supported by Mainframe Server Gateway.
Action: Verify that all parameters sent to Mainframe Server Gateway
are of the correct datatype.
|
34244
|
MSG: Request rejected. Conversation level security is not supported on this platform. The security option must be set to 'None'.
Explanation: You requested conversational-level security, which is not
supported on the current DirectConnect for z/OS Option
platform.
Action: Set up conversation level security on your DirectConnect for
z/OS Option platform with your security administrator.
|
34245
|
MSG: Sunlink function %1!, Sunlink error code %2!. Refer to Sunlink API Guide.
Explanation: An error was returned by the Sunlink APPC gateway.
Action: See the Sunlink documentation for an explanation of the error.
|
34246
|
MSG: OS/2 Communications Manager is down. Restart Communications Manager.
Explanation: OS/2 Communications Manager stopped.
Action: Restart OS/2 Communications Manager. You may need
to restart Mainframe Server Gateway.
|
34247
|
MSG: Sunlink is down. Restart the Sunlink peer to peer gateway.
Explanation: The Sunlink APPC gateway is down.
Action: Restart the Sunlink APPC gateway.
|
34248
|
MSG: Cannot connect to the Sunlink peer to peer gateway.
Explanation: The Sunlink APPC gateway is down.
Action: Restart the Sunlink APPC gateway.
|
34249
|
MSG: The Sunlink peer to peer gateway name was not specified on the command line. It must be specified with the -A parameter.
Explanation: A Sunlink gateway name was not specified in the start-up
command.
Action: Add the -A parameter and the name of the
Sunlink Gateway to the start-up command.
|
34250
|
MSG: NT SNA Server error, %1!, primary code %2!, secondary code %3!. Refer to NT SNA Server manuals.
Explanation: Microsoft SNA Server for Windows NT returned an error.
Action: See the SNA Server documentation for an explanation.
|
34251
|
MSG: Accounting log file not found.
Explanation: The accounting log file was not found in the $SYBASE directory.
Action: The accounting log is created the first time it is needed.
If this is a new installation, this is not an error and action is
not required.
|
34252
|
MSG: File error: Cannot open the accounting log file. Check the SYBASE directory read/write permissions.
Explanation: The accounting file in the $SYBASEdirectory
cannot be opened.
Action: Check the $SYBASE directory
permissions.
|
34255
|
MSG: OS/2 Communications Manager error, %1!, primary code %2!, secondary code %3!. Refer to APPC Programming Reference.
Explanation: OS/2 Communications Manager returned an error.
Action: See the OS/2 documentation for an explanation.
|
34256
|
MSG: Request rejected: No host connections are defined to the requested subsystem. Contact the Gateway Administrator.
Explanation: None of the existing configuration connections go to the host
region where the requested procedure is defined.
Action: Add connections to the required region or make sure that
your connections and RPCs are defined correctly.
|
34257
|
MSG: Request rejected: A connection group is not defined for this login. Contact the Gateway Administrator.
Explanation: This client is not assigned to a connection group.
Action: When running without the -O parameter,
each client must be assigned to a transaction group and a connection
group. Redefine the client login to be part of a connection group.
For additional information, see the Mainframe Connect DirectConnect
for z/OS Option User's Guide for Transaction
Router Services.
|
34258
|
MSG: Request rejected: A timeout occurred while waiting for a host connection to become available. Retry the request or contact the Gateway Administrator.
Explanation: All connections to the requested region are in use.
Action: Either define more connections to Mainframe Server Gateway
or increase the connection queue timeout period using the -Q start-up
parameter.
|
34259
|
%1!
Explanation: Initialization status message.
Action: Information only; no action required.
|
34260
|
MSG: Syntax error.
Explanation: The syntax of the gateway control procedure is incorrect.
Action: Check the syntax of your command or use sgw_help to
display the proper syntax.
|
34261
|
MSG: Request rejected: Invalid parameter
Explanation: You entered an invalid parameter on a gateway control request.
Action: Check the syntax of the command and reenter it.
|
34262
|
MSG: Syntax error. All gateway control parameters are expected to be in character format. Put quotes around numeric values.
Explanation: All gateway control parameters must be in character format.
Action: Put quotes around numeric values.
|
34263
|
MSG: Request rejected: No host connections are active to the requested subsystem. Contact the Gateway Administrator.
Explanation: Every connection to the required region is in an inactive
state, probably due to previous network errors.
Action: Use the sgw_actcon procedure
to reactivate connections once the network problem is resolved.
|
34264
|
MSG: AIX SNA Services function %1!, AIX error code %2!.
Explanation: An AIX SNA Services function returned an error.
Action: See the SNA Services documentation for an explanation of the
code.
|
34265
|
MSG: 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.
|
34266
|
MSG: srv_desfmt failed for column number %1!.
Explanation: An internal error occurred.
Action: Call Sybase Technical Support.
|
34267
|
MSG: srv_bind failed for column number %1!.
Explanation: An internal error occurred.
Action: Call Sybase Technical Support.
|
34268
|
MSG: srv_alloc failed and cannot allocate memory.
Explanation: An internal error occurred.
Action: Call Sybase Technical Support.
|
34269
|
MSG: AT&T SNA LU 6.2 error, %1!, primary code %2!, secondary code %3!. Refer to AT&T Networks - SNA LU 6.2 Administrator and Programmer Guide.
Explanation: An SNA function call failed.
Action: The error code printed is the code returned from the SNA package.
See the documentation supplied with your SNA package for a more
detailed error description.
|
34270
|
MSG: Region file not found.
Explanation: The region file cannot be opened.
Action: If you never ran sgw_addreg,
this file does not exist and this message is not an error. Otherwise,
check the permissions on the files in the $SYBASE directory.
|
34271
|
MSG: File error: Cannot open or create the region file. Check the SYBASE directory read/write permissions.
Explanation: The region file cannot be opened.
Action: If you never ran sgw_addreg, this
file does not exist. In this case, this message is not an error.
Otherwise, check the permissions on the files in the $SYBASE directory.
|
34272
|
MSG: Request rejected. Region '%1!' is already defined.
Explanation: You tried to add a region that is already defined.
Action: Drop the region using sgw_dropregion before
adding it again.
|
34273
|
MSG: Request rejected. Could not find that region. Retry the request with a valid region name.
Explanation: You tried to drop or deactivate a region that is not defined.
Action: Check the region name.
|
34274
|
MSG: Network call failed: %1!. Function %2! error %3!
Explanation: A network OS call failed.
Action: Refer to the OS error number displayed.
|
34275
|
MSG: A new remote procedure cannot be started until the currently running transaction has been completed. End the current transaction and try again.
Explanation: You started a long-running transaction on a host where a transaction
is still processing. You cannot start a new transaction on this
client connection until the current transaction completes processing.
Action: The host transaction is expecting another follow-up RPC call.
Disconnecting from Mainframe Server Gateway causes the host transaction
to be terminated. You can terminate DB2 transactions by issuing
either commit or rollback.
|
34276
|
MSG: A gateway control procedure cannot be started until the currently running transaction has been completed. End the current transaction and try again.
Explanation: You started a long-running transaction on the host where
a transaction is still running. You cannot start a new transaction
on this client connection until the current transaction is completed.
Action: The host transaction is expecting another follow-up RPC call.
Disconnecting from Mainframe Server Gateway terminates the host
transaction. You can terminate DB2 transactions by issuing either commit or rollback.
|
34277
|
MSG: A new remote procedure cannot be started until the currently running transaction ‘%1!’ has been completed. End the current transaction and try again.
Explanation: You started a long-running transaction on the host where a
transaction is still running. You cannot start a new transaction
on this client connection until the current transaction completes
processing.
Action: The host transaction is expecting another follow-up RPC call.
Disconnecting from Mainframe Server Gateway causes the host transaction
to be terminated. You can terminate DB2 transactions by issuing
either commit or rollback.
|
34278
|
MSG: A new query cannot be started until the currently running transaction ‘%1!’ has been completed. End the current transaction and try again.
Explanation: You started a long-running transaction on the host where
a transaction is still running. You cannot start a new transaction
on this client connection until the current transaction is completed.
Action: The host transaction is expecting another follow-up RPC call.
Disconnecting from Mainframe Server Gateway terminates the host
transaction. You can terminate DB2 transactions by issuing either commit or rollback.
|
34279
|
MSG: Tried to delete nonexistent client in the disconnect event.
Explanation: An internal error occurred.
Action: Call Sybase Technical Support.
|
34280
|
MSG: Host transaction could not be started. transaction %1!, host name %2!, port %3!.
Explanation: A network error occurred.
Action: This message is accompanied by other messages with detailed
error codes. Check your appropriate SNA error logs for additional
information.
|
34281
|
MSG: The requested host transaction could not be started because it is not recognized by the host. Check the RPC definition and contact the host system programmer.
Explanation: The host rejected the start transaction request because the
host region did not recognize the transaction name.
Action: Verify that the host transaction name associated with this
RPC is correct using exec sgw_status rpc.
If it appears to be correct, contact the host region administrator.
|
34282
|
MSG: The requested host transaction could not be started because of a host security violation.
Explanation: The security system on the host rejected the start
transaction request.
Action: Verify the following:
Correct user ID
and password being sent to the host.
RPC you want to run was defined to use security
when it was defined using sgw_addrpc.
CICS region configuration is correctly set up for
security.
Host mode table entry is appropriate for your security
settings.
|
34283
|
MSG: Could not start transaction because an error occurred allocating the host conversation. See error log.
Explanation: Mainframe Server Gateway received an error when it tried
to allocate a conversation to the host.
Action: Refer to your vendor’s SNA error log file for a
more detailed description of the problem.
|
34284
|
MSG: The requested host transaction could not be started by host.
Explanation: The host rejected the transaction start request.
Action: Verify that the host transaction program is installed and
available.
|
34285
|
MSG: The conversation with the host transaction ended abnormally. This may have been due to a host transaction program abend.
Explanation: The conversation with the host disconnected unexpectedly.
Action: The disconnect is most likely due to an abnormal termination
of the host transaction program. A network error can also terminate
the conversation.
|
34286
|
MSG: Could not start conversation with the host due to an SNA resource failure. This is usually due to an SNA configuration error or network outage. Contact gateway administrator.
Explanation: Mainframe Server Gateway received an SNA resource failure
notification from the SNA package when it tried to allocate a conversation
to the host.
Action: This is usually due to a configuration error. Verify that
the connection to the host is established, using the snaping utility.
For additional information, see the Mainframe Connect DirectConnect
for z/OS Option User's Guide for Transaction
Router Services.
|
34287
|
MSG: Connection has been stopped. The host session associated with this connection has been brought down since it was last accessed.
Explanation: Since this connection was last accessed, an SNA error occurred
that caused the connection to become invalid.
Action: This error usually occurs when the attachment associated
with the connection disconnected since its last use. Mainframe Server
Gateway closes the connection and attempts to reopen it automatically.
If the attachment is established, the connection can be reopened;
no action is required.
If Mainframe Server Gateway is unable to reopen the connection,
the state of SNA Services should be checked using the snaping utility.
The host operator might be required to vary active the
associated line, PU, or LU.
|
34288
|
MSG: SNA protocol violation.
Explanation: An internal error in a gateway or SNA package.
Action: Call Sybase Technical Support.
|
34289
|
MSG: The requested host transaction could not be started because of an unknown LU 6.2 mode table entry. This is probably due to a configuration error locally or at the host. Contact the Gateway Administrator
Explanation: The LU 6.2 Mode name specified in sgw_addcon is
incorrect.
Action: Check the mode name in CICS, VTAM, and local SNA services.
|
34290
|
MSG: Host transaction could not be started. Transaction name %1! Connection name %2!
Explanation: The requested transaction did not start.
Action: Refer to the gateway log file for the detailed SNA error
code.
|
34291
|
MSG: SNA Services is not running. Contact the Gateway Administrator
Explanation: The SNA Services software is not running.
Action: Start SNA Services.
|
34292
|
MSG: OS/2 Communications Manager is not running. Contact the Gateway Administrator.
Explanation: The OS/2 Communications Manager software for this
platform is not running.
Action: Start SNA Services.
|
34293
|
MSG: Sunlink is down. Restart the Sunlink Peer to Peer Gateway.
Explanation: The Sunlink Peer to Peer Gateway is not running.
Action: Start the Sunlink Peer to Peer Gateway.
|
34294
|
MSG: HP SNAP-IX is not running. Restart HP SNAP-IX.
Explanation: The SNA package used by this platform is not running.
Action: Start the HP-UX SNA plus daemons. See your HP-UX
SNA plus Administration Guide for details.
|
34295
|
MSG: AT&T SNA is not running. Restart SNA.
Explanation: The AT&T SNA software is not running.
Action: Start the AT&T SNA software.
|
34296
|
MSG: Microsoft NT SNA Server is not running. Restart the SNA Server.
Explanation: The Microsoft SNA Server for Windows NT is not running.
Action: Start the SNA Server.
|
34297
|
MSG: Novell SNA is not running. Restart SNA.
Explanation: The Novell SNA software is not running.
Action: Start the Novell SNA software.
|
34298
|
MSG: A timeout occurred waiting for an SNA function to complete. SNA Services is not responding. Check state of connection and attachment.
Explanation: Mainframe Server Gateway made a system call to AIX SNA Services
and did not receive a response.
Action: This is usually due to the inability of SNA Services to start
an attachment or connection. Verify that the VTAM operator activated
the host attachment, PU, and LU. If the problem persists, stop SNA
Services and restart it.
|
34299
|
MSG: Host transaction could not be started due to a network or host problem. See the error log.
Explanation: A problem occurred with the SNA software or the host when
starting the transaction.
Action: Refer to your vendor’s SNA error log for a more
detailed description of the problem.
|
34300
|
MSG: An invalid datastream was received from the host. The host conversation may have been terminated abnormally due to a host transaction program abend.
Explanation: Mainframe Server Gateway received an invalid datastream or
the host conversation ended unexpectedly.
Action: This is usually due to an abend of the host application.
Check the CICS error log. Also check the local SNA software log
file.
|
34301
|
MSG: Sunlink function mc_allocate failed. Unique session name %1! Host transaction name %2!.
Explanation: A Sunlink allocation error occurred.
Action: These messages accompany several other network failure messages
that can provide additional information about the parameters involved
in the error.
|
34302
|
MSG: HP SNAP-IX mc_allocate failed. Local LU %1!, Partner LU %2!, Mode name %3! Transaction name %4!.
Explanation: An HP SNAP-IX allocation error occurred.
Action: This message accompanies several other network failure messages
that can provide additional information about the parameters involved
in the error.
|
34303
|
MSG: OS/2 Communications Manager error in allocate. Local LU %1!, Partner LU %2!, Modename %3!, Transaction name %4!.
Explanation: An OS/2 SNA error occurred.
Action: This message accompanies several other network failure messages
that can provide additional information about the parameters involved
in the error.
|
34304
|
MSG: AIX SNA Services snalloc failed. Mode %1!, Transaction %2!
Explanation: An AIX SNA Services allocation error occurred.
Action: This message accompanies several other network failure messages
that can provide additional information about the parameters involved
in the error.
|
34305
|
MSG: NCR SNA LU 6.2 error, m_allocate. Remote LU %1!, Mode %2!, Transaction name %3!
Explanation: An NCR SNA allocation error occurred.
Action: This message accompanies several other network failure messages
that can provide additional information about the parameters involved
in the error.
|
34306
|
MSG: Cannot get %1!. srv_thread_props (%2!) failed.
Explanation: An internal error occurred.
Action: Call Sybase Technical Support.
|
34307
|
MSG: Cannot get %1! from the locale structure in the connect handler.
Explanation: An internal error occurred.
Action: Call Sybase Technical Support.
|
34308
|
MSG: Can't set the capability information. srv_capability_info (%1!) failed.
Explanation: An internal error occurred.
Action: Call Sybase Technical Support.
|
34309
|
MSG: Invalid TDS version returned by srv_thread_props(SRV_T_TDSVERSION).
Explanation: An internal error occurred.
Action: Call Sybase Technical Support.
|
34310
|
MSG: The transaction could not be started because an error occurred connecting to the remote CICS listener program. See error log.
Explanation: A socket to the CSKL transaction cannot be opened.
Action: Verify that CSKL is running. Use the cicsping utility
to check connectivity to CICS.
|
34311
|
MSG: The transaction could not be started due to an error from the remote CICS listener program. See error log.
Explanation: An error occurred starting the requested transaction.
Action: Check the log for the associated system error.
|
34312
|
MSG: An invalid datastream was received from the host. The socket may have been terminated abnormally due to a host transaction program abend.
Explanation: Mainframe Server Gateway received an invalid datastream or
the socket with the host disconnected unexpectedly.
Action: This is usually due to an abnormal ending of the host application.
Check the CICS error log.
|
34313
|
MSG: An error occurred on the socket between the gateway and the CICS transaction program. See error log.
Explanation: The socket with the host transaction program disconnected
unexpectedly.
Action: This is usually due to an abnormal ending of the host application.
Check the CICS error log.
|
34314
|
MSG: NT SNA Server error in allocate. Local LU %1!, Partner LU %2!, Modename %3!, Transaction name %4!.
Explanation: A Microsoft SNA Server for Windows NT allocation error occurred.
Action: This message accompanies several other network failure messages
that can provide additional information about the parameters involved
in the error.
|
34315
|
There are two possible
messages:
1) MSG: An error occurred starting
a transaction. returned from CICS Listener transaction ‘%1!’.
Explanation: The CSKL socket listener program rejected a start transaction
request.
Action: Refer to the returned message for the specific reason.
2) MSG: Cannot set the %1! field
of the locale structure to ‘%2!’ in rpc_sgwchlng.
Explanation: Failed to change the client’s locale structure.
Action: Contact Sybase Technical Support.
|
34316
|
MSG: Cannot open the tds log file ‘%1!’. Check the SYBASE directory read/write permissions.
Explanation: An error occurred reading or creating this file.
Action: Verify that the Mainframe Server Gateway process has write
permission to the $SYBASEdirectory.
|
34317
|
MSG: Novell NetWare for SAA error 407 in mc_allocate. Local LU %1!, Partner LU %2!, Modename %3!, Transaction 408 name %4!.
Explanation: The Novell SNA APPC function call mc_allocate failed.
Action: Refer to the Novell NetWare for SAA APPC API Guide for
an explanation of the error.
|
34318
|
MSG: Novell NetWare for SAA 411 error from verb %1! primary code %2!, secondary code %3!. Refer to Novell 412 APPC Technical Reference.
Explanation: A Novell Network APPC function call failed.
Action: Refer to the Novell NetWare for SAA APPC API Guide for
an explanation of the error.
|
34319
|
MSG: Novell NetWare for SNA error from verb %1!, primary code %2!. Refer to Novell APPC Technical Reference.
Explanation: A Novell Network APPC function call failed.
Action: Refer to the Novell NetWare for SAA APPC API Guide for
an explanation of the error.
|
34320
|
MSG: Invalid %1! %2! has been specified. Please make sure it is defined in the sybnetgw.cfg file used by the SYBCNOS nlm.
Explanation: An invalid configuration value was supplied to Mainframe
Server Gateway.
Action: Check the sybnetgw.cfg file and make
sure the configuration is properly defined.
|
34321
|
MSG: Unknown User: User '%1!' is unknown to the APPC Password Expiration Management PEM Server and the sign on is rejected.
Explanation: The user ID is invalid or unknown to the Password Expiration
Manager (PEM) Server.
Action: Make sure the user ID is properly set up and defined.
|
34322
|
MSG: Password Incorrect: The sign on to the APPC Password Expiration Management PEM Server is rejected. Contact Gateway administrator.
Explanation: The password specified is incorrect.
Action: Make sure the password is properly set up and defined.
|
34323
|
MSG: Password Expired: The APPC Password Expiration Management PEM Server indicates that the password has expired. Please execute sgw_pemchpwd or sgw_pemchgrppwd to change the password.
Explanation: The user’s password expired.
Action: Change the password by using sgw_pemchpwd or sgw_pemchgrppwd.
|
34324
|
MSG: Invalid New Password: The new password specified is not acceptable to the APPC Password Expiration Management PEM Server.
Explanation: The new password specified is invalid.
Action: Use an acceptable password.
|
34325
|
MSG: The APPC Password Expiration Manager PEM Server rejects the security function. Contact Gateway administrator.
Explanation: The PEM server rejected the security request by the Gateway
administrator.
Action: The Gateway administrator must correct the setup error.
|
34326
|
MSG: The APPC Password Expiration Manager returns a status code of '%1!'. Contact Gateway administrator.
Explanation: An internal error occurred.
Action: Contact the Gateway administrator.
|
34327
|
MSG: The host login and password cannot be zero length or longer than 8 characters.
Explanation: An invalid user ID or password was specified.
Action: Specify a valid password and be sure the length does not
exceed eight characters.
|
34328
|
MSG: The two instances of new password specified must match each other.
Explanation: The passwords do not match.
Action: Determine the correct password and use the correct password
in both instances.
|
34329
|
MSG: The password for host userid '%1!' has been successfully changed.
Explanation: The password for the indicated host user ID was changed.
Action: No action is required.
|
34330
|
MSG: The requested action cannot be executed because the APPC Password Expiration Manager PEM Server support flag ‘-P’ is not enabled. Contact Gateway administrator.
Explanation: The -P start-up parameter is not specified.
Action: Contact your Gateway administrator. The administrator must
specify the -P start-up parameter.
|
34331
|
MSG: The requested host transaction could not be started because of a host security violation. Please execute sgw_peminfopwd for more information.
Explanation: The password for the indicated host user ID was changed.
Action: No action is required.
|
34332
|
MSG: The requested host transaction could not be started because of a host security violation with the group login of transaction group '%1!'. Execute sgw_peminfogrppwd %2! for more info or contact Gateway administrator.
Explanation: The password for the indicated host user ID was changed.
Action: No action is required.
|
34333
|
MSG: Invalid ‘%1!’ value ‘%2!’ received from %3!.’
Explanation: Mainframe Server Gateway received invalid information from
Open Server.
Action: Contact Sybase Technical Support.
|
34334
|
‘%1’
The message varies depending on the conditions.
Explanation: Depending on the situation, this message displays information
about the current condition or an error message.
Action: If you encounter an error, contact Sybase Technical Support
or your system administrator.
|