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

Windows 32s: CPIC Access Method

CAUTION:: Version 6 Only Beginning with Version 7, the Windows 32s platform is not supported. However, information about Windows 32s is included here for Version 6 users.

SAS/CONNECT and SAS/SHARE

Until the configuration is properly specified, it can be difficult to establish communications within an SNA network. The CPIC communication access method reflects failures as they are reported by the operating system components with which they interface. Often, this information is in the form of operation codes, return codes, and sense data. No attempt is made to interpret these failures. Because of the numerous possibilities for failure that are a function of your particular environment, it is expected that you will work with network systems and SAS support personnel at your site to determine the problem and find the solution.

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

The following is a list of possible CPIC return codes and their values:

CPIC Return Codes
Return Code Value

CM_OK 0

CM_ALLOCATE_FAILURE_NO_RETRY 1

CM_ALLOCATE_FAILURE_RETRY 2

CM_CONVERSATION_TYPE_MISMATCH 3

CM_PIP_NOT_SPECIFIED_CORRECTLY 5

CM_SECURITY_NOT_VALID 6

CM_SYNC_LEVEL_NOT_SUPPORTED_LU 7

CM_SYNC_LEVEL_NOT_SUPPORTED_PGM 8

CM_TPN_NOT_RECOGNISED 9

CM_TP_NOT_AVAILABLE_NO_RETRY 10

CM_TP_NOT_AVAILABLE_RETRY 11

CM_DEALLOCATED_ABEND 17

CM_DEALLOCATED_NORMAL 18

CM_PARAMETER_ERROR 19

CM_PRODUCT_SPECIFIC_ERROR 20

CM_PROGRAM_ERROR_NO_TRUNC 21

CM_PROGRAM_ERROR_PURGING 22

CM_PROGRAM_ERROR_TRUNC 23

CM_PROGRAM_PARAMETER_CHECK 24

CM_PROGRAM_STATE_CHECK 25

CM_RESOURCE_FAILURE_NO_RETRY 26

CM_RESOURCE_FAILURE_RETRY 27

CM_UNSUCCESSFUL 28

CM_DEALLOCATED_ABEND_SVC 30

CM_DEALLOCATED_ABEND_TIMER 31

CM_SVC_ERROR_NO_TRUNC 32

CM_SVC_ERROR_PURGING 33

CM_SVC_ERROR_TRUNC 34

CM_OPERATION_INCOMPLETE 35

CM_SYSTEM_EVENT 36

CM_OPERATION_NOT_ACCEPTED 37

***CPIC Return Codes***
Return Code	Value
CM_OK	0
CM_ALLOCATE_FAILURE_NO_RETRY	1
CM_ALLOCATE_FAILURE_RETRY	2
CM_CONVERSATION_TYPE_MISMATCH	3
CM_PIP_NOT_SPECIFIED_CORRECTLY	5
CM_SECURITY_NOT_VALID	6
CM_SYNC_LEVEL_NOT_SUPPORTED_LU	7
CM_SYNC_LEVEL_NOT_SUPPORTED_PGM	8
CM_TPN_NOT_RECOGNISED	9
CM_TP_NOT_AVAILABLE_NO_RETRY	10
CM_TP_NOT_AVAILABLE_RETRY	11
CM_DEALLOCATED_ABEND	17
CM_DEALLOCATED_NORMAL	18
CM_PARAMETER_ERROR	19
CM_PRODUCT_SPECIFIC_ERROR	20
CM_PROGRAM_ERROR_NO_TRUNC	21
CM_PROGRAM_ERROR_PURGING	22
CM_PROGRAM_ERROR_TRUNC	23
CM_PROGRAM_PARAMETER_CHECK	24
CM_PROGRAM_STATE_CHECK	25
CM_RESOURCE_FAILURE_NO_RETRY	26
CM_RESOURCE_FAILURE_RETRY	27
CM_UNSUCCESSFUL	28
CM_DEALLOCATED_ABEND_SVC	30
CM_DEALLOCATED_ABEND_TIMER	31
CM_SVC_ERROR_NO_TRUNC	32
CM_SVC_ERROR_PURGING	33
CM_SVC_ERROR_TRUNC	34
CM_OPERATION_INCOMPLETE	35
CM_SYSTEM_EVENT	36
CM_OPERATION_NOT_ACCEPTED	37

Each message follows this format:

ERROR: CPIC communication failure: 
transaction program = program-name
opcode = operation-code oprc = CPIC rc

where

opcode: is the failing verb operation code.
oprc: is the CPIC return code.

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]

ERROR: CPIC communication failure: 
transaction program = SASRMT (or SASVQEL) 
opcode = cminit oprc = 00000014.

This message signifies that an INITIALIZE_ CONVERSATION verb has failed due to a PRODUCT_ SPECIFIC_ERROR. An operational problem has been detected by the underlying CPIC subsystem. A description of the error has been written to the CPIC product's error log. For example, with the Microsoft SNA Server, you should make sure that the Windows NT SNA Server is running and that WNAP is able to connect to it across the LAN.

ERROR: CPIC communication failure: 
transaction program = SASRMT (or SASVQEL) 
opcode = cmallc oprc = 00000014.

This message signifies that an ALLOCATE verb has failed due to a PRODUCT_SPECIFIC_ERROR. An operational problem has been detected by the underlying CPIC subsystem. A description of the error has been written to the CPIC product's error log. For example you should make sure that you have specified a valid partner LU_alias and that a default local LU has been defined.

ERROR: CPIC communication failure:
transaction program = SASRMT (or SASVQEL) 
opcode = cmallc oprc = 00000001.

This message signifies that an ALLOCATE verb has failed due to an ALLOCATION_FAILURE. There are hundreds of reasons for this return code. For example, the partner LU is not in the network or cannot be reached, the partner LU is in the network but is not active (VTAM APPL/ACB not active), the mode name that was requested for this session is not configured at both the local and remote sides, or there is no route through the network with the requested COS (class of service).

ERROR: CPIC communication failure: 
transaction program = SASRMT (or SASVQEL) 
opcode = cmrcv oprc = 00000009.

This message signifies that a RECEIVE verb has failed due to the partner rejecting the incoming Attach because it did not recognize the specified TP name that was supplied to it. This error would commonly occur as a result of the partner not being properly configured.

ERROR: CPIC communication failure:
transaction program = SASRMT (or SASVQEL) 
opcode = cmrcv oprc = 0000000A.

This message signifies that a RECEIVE verb has failed due to the partner rejecting the incoming Attach because it could not start the remote partner's transaction program. This error would commonly occur if the partner had a partially correct configuration, for example, if the TP name is configured but the intended executable program (SAS) does not exist.

ERROR: CPIC communication failure: 
transaction program = SASRMT (or SASVQEL)
opcode = cmrcv oprcs = 00000006.

This message signifies that a RECEIVE verb has failed due to the partner rejecting the conversation because of invalid userid or password security that was specified in the allocation request. Make sure that you have specified the correct userid and password in

the CPIC_SECURE environment variable or that the proper security is specified in CPIC side information.

If you cannot resolve your connectivity problem, call SAS Technical Support for assistance. You will likely be requested to generate traces to assist in documenting the problem, so ensure that you or your site support personnel are familiar with the tracing services available through the SNA component used and VTAM.

Chapter Contents
Previous
Next
Top of Page