SV: DB2 Connect cmallc rc=20

Sven Heidorn

SV: DB2 Connect cmallc rc=20
Franco,
I can't really help you with the problem, but this is what the manual says.

20 CM_PRODUCT_SPECIFIC_ERROR
The local program made a CPI-C call that failed because of a
platform-related
condition.
Explanation
An operational problem has been detected which relates to the CPI-C
product that the local program is using. A description of the error has
been written to the local CPI-C product's system error log. See the
product documentation for an indication of conditions and state
changes caused by this return code.

The state of the conversation remains unchanged.

Likely Causes
This return code generally indicates a problem with the underlying
CPI-C software and the environment in which it is running, not the
local program. For example:

* The underlying CPI-C or APPC software is stopped, has not been
started or is not yet fully active, or is abended.

* CPI-C is unable to allocate needed memory for its internal control
blocks. For example, no more conversation IDs are available.

* If the return code is from a call to Accept_Conversation()
(CMACCP), it is likely that the program was started locally (for
example, from the command line), but the program should have
been started by the attach manager because of an incoming Attach.

* There is a CPI-C implementation bug.

Here are some other platform-specific examples of this return code.

On the OS/2 Communications Manager:
If the local platform is OS/2 Communications Manager, the
local TP may have been deactivated using Subsystem
Management.
If the local platform is OS/2 Communications Manager, the
APPCTPN environment variable was not set before calling
Accept_Conversation().

On CICS/ESA:
If the local platform is CICS/ESA, this return code results in
one of the following informational error messages:
* DFHCP0742 - the session is not available for CPI-C, as it is
already in use by another process.
* DFHCP0743 - CPI-C can not be used, as the transaction was
initiated by ATI.
* DFHCP0750 - an unrecognized profile name was supplied
in the partner resource sym_dest_name.

On MVS/ESA:
If the local platform is MVS/ESA, the system writes a
symptom record to SYS1.LOGREC to identify the error.

On VM/ESA:
If the local platform is VM/ESA, the system writes a
symptom record to CPICOMM LOGDATA to identify the
error.

However, depending on the platform, there are some types of
problems that are caused by an application program. For example:
* There is a multi-tasking interference problem. One way this can
occur is for a multi-threaded program to issue more than one CPI-C
call for a given conversation at the same time.

Programmer Action
This return code generally indicates a problem that the local program
cannot recover from without intervention. Since the state of the
conversation generally is not changed by this call, the local program
should issue a Deallocate() call (with deallocate_type set to
CM_DEALLOCATE_ABEND, if possible) to end the conversation.

Operator Action
First, make sure the local CPI-C software is active. If the CPI-C
software was active when this return code occurred, check the local
CPI-C product's system error log (and related message logs) for
additional details about this problem.
CPI-C may be making calls to underlying APPC software. The details
of these calls, including their control blocks and internal return codes,
provide lots of diagnostic information. If possible, get a trace of these
internal calls, to see the return codes returned by APPC.

Hope this helps
Sven Heidorn

> -----Ursprungligt meddelande-----
> Från: Masone, Franco [SMTP:[login to unmask email]
> Skickat: den 12 oktober 1999 16:09
> Till: [login to unmask email]
> Ämne: DB2 Connect cmallc rc=20
>
> Hi to all,
> Db2connect again......
> I am trying to do a connection with the OS390 DB2 V4.1, I try to use APPC
> thru SNA SERVER (Independent LU 6.2).
> I followed all the directions from the manual, at time of connection I
> receive a message reporting a return code 20 (product specific error)
> from cmallc.
> Any suggest ? The 6.2 lu is defined in Sysibm.lunames.
> How can I debug this (perhaps communication (CPI) problem ?)
> Thanks in advance
> Franco
>
>
> visit
>
>



[login to unmask email]

Re: SV: DB2 Connect cmallc rc=20
(in response to Sven Heidorn)

Sven,

I am currently about to set up a link from QMF for Windows to DB2 v4 using
CPI-C. Please supply the title of the manual you were referring to
concerning CPI-C error messages.

Thank you,
Jim Leask.

______________________________ Reply Separator _________________________________
Subject: SV: DB2 Connect cmallc rc=20
Author: Sven.Heidorn ([login to unmask email]) at Internet
Date: 12/10/99 15:59


Franco,
I can't really help you with the problem, but this is what the manual says.

20 CM_PRODUCT_SPECIFIC_ERROR
The local program made a CPI-C call that failed because of a
platform-related
condition.
Explanation
An operational problem has been detected which relates to the CPI-C
product that the local program is using. A description of the error has
been written to the local CPI-C product's system error log. See the
product documentation for an indication of conditions and state
changes caused by this return code.

The state of the conversation remains unchanged.

Likely Causes
This return code generally indicates a problem with the underlying
CPI-C software and the environment in which it is running, not the
local program. For example:

* The underlying CPI-C or APPC software is stopped, has not been
started or is not yet fully active, or is abended.

* CPI-C is unable to allocate needed memory for its internal control
blocks. For example, no more conversation IDs are available.

* If the return code is from a call to Accept_Conversation()
(CMACCP), it is likely that the program was started locally (for
example, from the command line), but the program should have
been started by the attach manager because of an incoming Attach.

* There is a CPI-C implementation bug.

Here are some other platform-specific examples of this return code.

On the OS/2 Communications Manager:
If the local platform is OS/2 Communications Manager, the
local TP may have been deactivated using Subsystem
Management.
If the local platform is OS/2 Communications Manager, the
APPCTPN environment variable was not set before calling
Accept_Conversation().

On CICS/ESA:
If the local platform is CICS/ESA, this return code results in
one of the following informational error messages:
* DFHCP0742 - the session is not available for CPI-C, as it is
already in use by another process.
* DFHCP0743 - CPI-C can not be used, as the transaction was
initiated by ATI.
* DFHCP0750 - an unrecognized profile name was supplied
in the partner resource sym_dest_name.

On MVS/ESA:
If the local platform is MVS/ESA, the system writes a
symptom record to SYS1.LOGREC to identify the error.

On VM/ESA:
If the local platform is VM/ESA, the system writes a
symptom record to CPICOMM LOGDATA to identify the
error.

However, depending on the platform, there are some types of
problems that are caused by an application program. For example:
* There is a multi-tasking interference problem. One way this can
occur is for a multi-threaded program to issue more than one CPI-C
call for a given conversation at the same time.

Programmer Action
This return code generally indicates a problem that the local program
cannot recover from without intervention. Since the state of the
conversation generally is not changed by this call, the local program
should issue a Deallocate() call (with deallocate_type set to
CM_DEALLOCATE_ABEND, if possible) to end the conversation.

Operator Action
First, make sure the local CPI-C software is active. If the CPI-C
software was active when this return code occurred, check the local
CPI-C product's system error log (and related message logs) for
additional details about this problem.
CPI-C may be making calls to underlying APPC software. The details
of these calls, including their control blocks and internal return codes,
provide lots of diagnostic information. If possible, get a trace of these
internal calls, to see the return codes returned by APPC.

Hope this helps
Sven Heidorn

> -----Ursprungligt meddelande-----
> Från: Masone, Franco [SMTP:[login to unmask email]
> Skickat: den 12 oktober 1999 16:09
> Till: [login to unmask email]
> Ämne: DB2 Connect cmallc rc=20
>
> Hi to all,
> Db2connect again......
> I am trying to do a connection with the OS390 DB2 V4.1, I try to use APPC
> thru SNA SERVER (Independent LU 6.2).
> I followed all the directions from the manual, at time of connection I
> receive a message reporting a return code 20 (product specific error)
> from cmallc.
> Any suggest ? The 6.2 lu is defined in Sysibm.lunames.
> How can I debug this (perhaps communication (CPI) problem ?)
> Thanks in advance
> Franco
>
>
> visit
>
>


com/db2-To change your subscription option
s or to cancel your subscription visit the DB2-L webpage at http://www.ryci.com/
db2-l. The owners of the list can