Communications Access Methods for SAS/CONNECT and SAS/SHARE Software

OS/2: APPC Access Method

SAS/CONNECT

Until the configuration is properly specified, it can be difficult to establish communications within an SNA network, especially for a host subarea peripheral node. To simplify troubleshooting, SAS/CONNECT uses a convention for error handling that passes information to you to help you debug your configuration. This information includes operation codes, return codes, and sense data, which is framed within the context of the function the software is trying to perform. SAS/CONNECT does not attempt to interpret this information. Use this information to work with network systems and SAS support personnel at your site to resolve the problem.

Each message has the following format:

ERROR: APPC communication failure: 
transaction program = program-name 
opcode = operation-code
 prc = primary-rc src = secondary-rc

where

opcode: is the failing verb operation code.
prc: is the primary return code.
src: is the secondary return code. When an allocation error occurs ( prc=0003), the src field contains the necessary SNA sense data.

For more information about these fields, see References.

Note: Most failures are caused by configuration or network setup errors, or they occur because the application that you are attempting to communicate with is not currently running, or it has rejected your connection request. [cautionend]

The following messages document some common failures:

ERROR: APPC communication failure:
transaction program = SASRMT (or SASVQEL) 
opcode = 1A00   prc = F012  src = 00000000.

A CONVERT request ( opcode = 1A00) has failed for the reason COMMUNICATION_SUBSYTEM_ NOT_LOADED ( prc = F012). Communications Manager must be started on the local workstation before any services can be utilized.

ERROR: APPC communication failure: 
transaction program = SASRMT (or SASVQEL)
opcode = 0100   prc = 0001  src = 00000018.

An ALLOCATE request ( opcode = 0100) has failed with a PARAMETER_CHECK ( prc = 0001) because of an UNKNOWN PARTNER LU condition ( src = 00000018). The user-supplied partner LU alias (the value for the REMOTE= option) is not defined to the local node or to the designated network node directory server. Verify the DEFINE_PARTNER_LU definition in the NDF file.

ERROR: APPC communication failure: 
transaction program = SASRMT (or SASVQEL) 
opcode = 0100   prc = 0003  src = 08570003.

An ALLOCATE request ( opcode = 0100) has failed with an ALLOCATION_ERROR ( prc = 0003). The src in this case has been overridden by sense data 08570003, which indicates that the SSCP-SLU session is inactive. An attempt to communicate with a VTAM-owned logical unit has failed because the application does not have an active control session with VTAM (the host APPL/ACB is not OPEN). Ask your systems administrator why the partner LU (the value for the REMOTE= option) is not active.

ERROR: APPC communication failure: 
transaction program = SASRMT (or SASVQEL) 
opcode= 0100   prc = 0003  src = 081C0103.

An ALLOCATE request ( opcode = 0100) has failed with an ALLOCATION_ERROR ( prc = 0003). The src in this case has been overridden by sense data 081C0103, which indicates that the function cannot be executed because the receiver has an error condition. The last four digits, 0103, indicate that the remote node is not responding to polling requests, perhaps because it is turned off or because the hardware is not functioning correctly.

ERROR: APPC communication failure: 
transaction program =SASRMT (or SASVQEL) 
opcode = 0D00   prc = 0003  src = 080F6051.

A RECEIVE_AND_POST ( opcode = 0D00) request has failed with an ALLOCATION_ERROR ( prc = 0003). The src in this case has been overridden by sense data 080F6051, which indicates that the receiver does not accept the Access Security Information field. For example, the supplied userid and password combination may be invalid or one or both of the fields may have been omitted and the remote partner requires them. Find out if your system is case sensitive; if so, use the appropriate case and enclose both the userid and password in quotation marks.

ERROR: APPC communication failure: 
transaction program = SASRMT 
opcode = 0D00 prc = 0003  src = 10086021.

A RECEIVE_AND_POST ( opcode = 0D00) request has failed with an ALLOCATION_ERROR ( prc = 0003). The src in this case has been overridden by sense data 10086021, which indicates that the transaction program name specified by the FMH-5 Attach command was not recognized by the receiver. This may occur if the SASRMT transaction program is not properly defined at the remote system, or there was a failure in the initialization of the environment within which the transaction program was to run. It might aid="OS2APPCREFS">.

The following messages document some common failures:

ERROR: APPC communication failure: 
transaction program = SASRMT (or SASVQEL) 
opcode = 1A00   prc = F012  src = 00000000.

ERROR: APPC communication failure: 
transaction program = SASRMT (or SASVQEL)
opcode = 0100   prc = 0001  src = 00000018.

ERROR: APPC communication failure: 
transaction program =SASRMT (or SASVQEL) 
opcode = 0100   prc = 0003  src = 08570003.

ERROR:APPC communication failure: 
transaction program = SASRMT (or SASVQEL) 
opcode= 0100   prc = 0003  src = 081C0103.

ERROR: APPC communication failure: 
transaction program =SASRMT (or SASVQEL) 
opcode = 0D00   prc = 0003  src = 080F6051.

ERROR: APPC communication failure: 
transaction program = SASRMT 
opcode = 0D00 prc = 0003  src = 10086021.

ERROR: APPC communication failure: 
transaction program = SASRMT 
opcode = 0100 prc = 0003  src = 08970015.

An ALLOCATE request ( opcode = 0100) has failed with an ALLOCATION_ERROR ( prc = 0003). The src in this case has been overridden by sense data 08970015, which indicates that a session initiation request has been received for an independent LU that has not been defined to the destination VTAM. If appc.luname is not specified, SAS/CONNECT uses CP_ALIAS by default. To avoid this problem, use the APPC_LUNAME environment variable to specify a local LU alias that is also defined to the destination VTAM.

ERROR: APPC communication failure: 
transaction program = SASRMT 
opcode = 0100   prc = 0003  src = 00821002.

An ALLOCATE request ( opcode = 0100) has failed with an ALLOCATION_ERROR ( prc = 0003). The src in this case has been overridden by sense data 00821002, which indicates that the mode name that was specified to present session parameters to the remote LU is not defined to the remote LU. The OS/2 to remote-host-connection communications mode defaults to SASAPPC. To circumvent the problem, use the APPC_LU62MODE environment variable to specify a correctly defined mode name that is known to both the local and remote LUs.

ERROR: APPC communication failure:
 transaction program = SASRMT 
opcode = 0100   prc = 0003  src = 08970015.
ERROR: Remote SIGNON cancelled.

This error occurs when OS/2 is the local host. Use the APPC_LUNAME environment variable to specify the local LU alias.

ERROR: APPC communication failure: 
transaction program = SASVQEL 
opcode = 0D00   prc = 0003  src = 084C0000 
ERROR: Remote SIGNON cancelled.

This error occurs when SIGNON is attempted between two OS/2 hosts. To circumvent the problem, verify that the SASRMT and SASTP62 transaction programs have been configured on the remote host.

ERROR: APPC communication failure:
transaction program = SASRMT (or SASVQEL) 
opcode = 1A00   prc = 0001  src = 00000406

A CONVERT request ( opcode=1A00) has failed with a PARAMETER_CHECK ( prc=0001) because a conversion error occurred ( src=00000406). This failure typically occurs when an invalid character is present in a user-supplied string, such as APPC_USER or APPC_SECURE. Verify that the values that you have specified contain only uppercase letters A through Z, lowercase letters a through z, numerics 0 through 9, and special characters $, #, and @.

If you cannot resolve a problem from the explanations given here and by using the cited resources, call SAS Technical Support for assistance. You will probably be asked to generate traces that document the problem, so be sure that you or your site support personnel are familiar with the tracing services available through OS/2 Extended Services and VTAM.

SAS/SHARE

Until the configuration is properly specified, it can be difficult to establish communications within the SNA network, especially for a host subarea peripheral node. SAS/SHARE passes error handling information to you to help you debug your configuration. This information includes operation codes, return codes, and sense data that relate to the function that the software is performing. Although SAS/SHARE does not interpret the information, you can use the information to work with network systems and SAS support personnel at your site to resolve any problems.

The following error messages are produced by the OS/2 APPC access method. Error reports for the APPC access method include the failing verb operation code ( opcode), the primary return code ( prc), secondary return code ( src), and, in some cases, the sense data.

For more information that will help you with troubleshooting, see References.

APPC communication failure: transaction program = SASVQEL opcode = 1A00 prc = F012 src = 00000000

A CONVERT request ( opcode = 1A00) has failed for the reason COMMUNICATION_SUBSYTEM_NOT_LOADED (prc = F012). Communications Manager must be started on the local workstation before any services can be utilized.

APPC communication failure: 
transaction program = SASVQEL
opcode = 0100   prc = 0003  src = 08210002

An ALLOCATE request ( opcode = 0100) has failed with an ALLOCATION_ERROR ( prc = 0003). The src in this case has been overridden by sense data 08210002, which means "Invalid Mode Name at CP: The specified mode name was not recognized by the CP." The mode name presented by the local workstation must be defined at the destination control point.

APPC communication failure: 
transaction program = SASVQEL 
opcode = 1A00 prc = F012  src = 00000000

A CONVERT request ( opcode = 1A00) has failed for the reason COMMUNICATION_SUBSYTEM_NOT_LOADED ( prc = F012). Communications Manager must be started on the local workstation before any services can be utilized.

APPC communication failure: 
transaction program = SASVQEL 
opcode = 0100   prc = 0003  src = 08210002

APPC communication failure: 
transaction program = SASVQEL 
opcode = 0100   prc = 0001  src = 00000018

An ALLOCATE request ( opcode = 0100) has failed with a PARAMETER_CHECK ( prc = 0001) because of an UNKNOWN PARTNER LU condition ( src = 00000018). The server-id that is specified by SERVER= is not defined to the local node or to the designated network node directory server as a partner LU alias.

APPC communication failure: 
transaction program = SASVQEL
opcode = 0100   prc = 0003  src = 80040000

An ALLOCATE request ( opcode = 0100) has failed with an ALLOCATION_ERROR ( prc = 0003). The src in this case has been overridden by sense data 80040000, which means "Unrecognized Destination: A node in the path has no routing information for the destination that is specified by the SLU name in the BIND request". The server-id that is specified by SERVER= is defined to the local node as a partner LU alias but the partner LU cannot be located.

APPC communication failure: 
transaction program = SASVQEL
opcode = 0100   prc = 0003  src = 081C0103

An ALLOCATE request ( opcode = 0100) has failed with an ALLOCATION_ERROR ( prc = 0003). The src in this case has been overridden by sense data 081C0103, which means "The requested function cannot be executed, because of a permanent error condition in the receiver. X'0103' indicates that the remote node is not responding to polling requests. The remote node may be powered off or the hardware may be functioning incorrectly."

APPC communication failure: 
transaction program = SASVQEL 
opcode = 0F00 prc = 0003  src = 084B6031

A SEND_DATA request ( opcode = 0F00) has failed with an ALLOCATION_ERROR ( prc = 0003). The src in this case has been overridden by sense data 084B6031, which means "Transaction Program Not Available - Retry Allowed: The FMH-5 ATTACH command specifies a transaction program that the receiver is unable to start". The (internal) transaction program SASVQEL (encapsulated in SASTP62), which is configured as QUEUED_OPERATOR_PRELOADED, is unavailable because a process has not issued a RECEIVE_ALLOCATE to signify the transaction program's availability to the Attach Manager component. That is, the specified server is not running.

APPC communication failure: 
transaction program = SASVQEL 
opcode = 0D00 prc = 0003  src = 080F6051

A RECEIVE_AND_POST request ( opcode = 0D00) has failed with an ALLOCATION_ERROR ( prc = 0003). The src in this case has been overridden by sense data 080F6051 indicating "The request specifies an Access Security Information field that is unacceptable to the receiver. The partner rejected the userid or the password received on an incoming ATTACH." That is, the server is running secured but the userid and password combination was missing or invalid (possibly because of case-sensitivity).

APPC communication failure: 
transaction program = SASVQEL
opcode = 1A00   prc = 0001  src = 00000406

A CONVERT request ( opcode=1A00) has failed with a PARAMETER_CHECK ( prc = 0001) because of a conversion error ( src = 00000406). This is probably attributable to an invalid character being present in a user-supplied string, such as APPC_USER or APPC_SECURE. Verify that the values that you have specified contain only uppercase letters A through Z, lowercase letters a through z, numerics 0 through 9, and special characters $, #, and @.

Chapter Contents
Previous
Next
Top of Page