This chapter lists the messages issued by the Oracle Procedural Gateway for APPC server and provides a possible cause and recommended action for each message. In addition to these messages, there are gateway messages, prefixed with GTW, that are documented in Oracle Open Gateways Guide for SQL-Based and Procedural Gateways.
This chapter contains the following sections:
func
. This message is preceded by additional messages that provide more information about the error.Locate Error Message PGA-20910 for Your Platform From This List
func
). The CPI-C function return code (rc
) and system error number (errno
) are provided in the message text. CPI-C function return codes and system error numbers are described in the vendor documentation. Also, the CPI-C return codes are available in the /usr/include/cmc.h
header file, and the AIX SNA system error numbers can be found in the /usr/include/luxsna.h
header file.
Table 2-1 lists some commonly received rc
and errno
combinations on AIX and their possible causes.
Table 2-1 Error Message PGA-20910 for AIX Systems
rc | errno | Possible Causes |
---|---|---|
1 |
22 |
The partner |
1 |
25 |
The |
6 |
133 |
A security violation occurred on the target system. Either the user ID or password is not valid on that system, or the user ID is not authorized to execute the requested transaction. |
9 |
127 |
The transaction program requested is not defined to the target |
10 |
147 |
The transaction program requested is defined to the target |
17 |
121 |
The transaction program terminated abnormally on the target |
19 |
9 |
Either the target |
20 |
125 |
The |
20 |
160 |
|
func
). The CPI-C function return code (rc
) and system error number (errno
) are provided in the message text. The CPI-C function return codes and system error numbers are described in the vendor documentation.
Commonly received return codes and their possible causes on hp-ux are listed in Table 2-2.
Table 2-2 Error Message PGA-20910 for HP-UX
rc | errno | Possible Cause(s) |
---|---|---|
2 |
N/A |
The target |
6 |
N/A |
A security violation occurred on the target system. Either the user ID or password is not valid on that system, or the user ID is not authorized to execute the requested transaction on the target |
9 |
N/A |
The transaction program requested is not defined to the target |
10 |
N/A |
The transaction program requested is defined to the target |
17 |
N/A |
The transaction program terminated abnormally on the target |
19 |
N/A |
The mode name specified was not defined in the mode table for the target |
26 |
N/A |
The |
CPI-C
function (func). The CPI-C
function return code (rc) and system error number (errno) are provided in the message text. For the SNA communication package
, CPI-C
function return codes are described in the Solaris vendor documentation.
Table 2-3 lists commonly received rc
and errno combinations, and their possible causes on Solaris.
Table 2-3 Error Message PGA-20910 for Solaris
rc | errno | Possible Cause(s) |
---|---|---|
6 |
5 |
A security violation occurred on the target system. Either the user ID or password is not valid on that system, or the user ID is not authorized to execute the requested transaction on the target |
9 |
0 |
The transaction program requested is not defined to the target |
17 |
0 |
The transaction program terminated abnormally on the target |
CPI-C
function (func). The CPI-C
function return code (rc
) and system error number (errno
) are provided in the message's text. The CPI-C
function return codes are described in the vendor documentation. Also, the CPI-C
return codes are contained in the C:\bkoffice\include\wincpic.h
header file. The system error number is meaningless for the Host Integration Server on Microsoft Windows and is usually 0
.
Table 2-4 lists some commonly received rc
or errno messages, and their possible causes.
Table 2-4 Error Message PGA-20910 for Microsoft Windows
rc | errno | Possible Cause(s) |
---|---|---|
2 |
0 |
Either the target |
6 |
0 |
A security violation occurred on the target system. Either the user ID or password is not valid on that system, or the user ID is not authorized to execute the requested transaction. |
9 |
0 |
The transaction program requested is not defined to the target |
10 |
0 |
The transaction program requested is defined to the target |
17 |
0 |
The transaction program terminated abnormally on the target |
19 |
0 |
The target |
20 |
0 |
Either the target |
If you use the IBM Communication Server, then the error message numbers and return codes that you get are different from those listed. Refer to the wincpic.h
file for more information about error message numbers.
tpname
has already been started at LU luname
by a PGAINIT
call with synclevel
set to 1
or 2
. Only one transaction at synclevel
1
or 2
is allowed at any given time.PGAXFER
were zero. This is invalid.PGDL
and COBOL
record descriptions that are used to define the transaction to PGAU
are syncronized with the transaction program and that the PL/SQL TIP
was generated by PGAU
using the correct definitions. If modifications have been made to the generated PL/SQL
code, then check that they are correct.len
) passed to PGAXFER
was larger than the actual size (size
) of the send buffer passed to PGAXFER
.PGDL
and COBOL
record descriptions that are used to define the transaction to PGAU
are syncronized with the transaction program and that the PL/SQL TIP
was generated by PGAU
by using the correct definitions. If modifications have been made to the generated PL/SQL
code, then check that they are correct.(len
) passed to PGAXFER
was larger than the maximum allowed length (max
).PGDL
and COBOL
record descriptions that are used to define the transaction to PGAU
are syncronized with the transaction program and that the PL/SQL TIP
is generated by PGAU
by using the correct definitions. If modifications have been made to the generated PL/SQL
code, then check that they are correct.(count
) in the send lengths array passed to PGAXFER
specified more elements than the send lengths array contained. Only (num
) elements were found in the array.PGDL
and COBOL
record descriptions that are used to define the transaction to PGAU
are syncronized with the transaction program and that the PL/SQL TIP
is generated by PGAU
by using the correct definitions. If you have modified the generated PL/SQL
code, then check that the modifications are correct.count
) in the receive lengths array passed to PGAXFER
specified more elements than the receive lengths array contained. Only (num
) elements were found in the array.PGDL
and COBOL
record descriptions that are used to define the transaction to PGAU
are syncronized with the transaction program and that the PL/SQL TIP
is generated by PGAU
by using the correct definitions. If you have modified the generated PL/SQL
code, then check that the modifications are correct.len
) specified in send lengths array element number (num
) exceeded the number of bytes (bytes
) of data remaining in the send buffer.PGDL
and COBOL
record descriptions that are used to define the transaction to PGAU
are syncronized with the transaction program and that the PL/SQL TIP
is generated by PGAU
by using the correct definitions. If modifications have been made to the generated PL/SQL
code, then check that they are correct.len
) specified in receive lengths array element number (num
) exceeded the number of bytes (bytes
) of space remaining in the receive buffer.PGDL
and COBOL
record descriptions that are used to define the transaction to PGAU
are syncronized with the transaction program and that the PL/SQL TIP
is generated by PGAU
by using the correct definitions. If modifications have been made to the generated PL/SQL
code, then check that they are correct.PGDL
and COBOL
record descriptions that are used to define the transaction to PGAU
are syncronized with the transaction program and that the PL/SQL TIP
is generated by PGAU
by using the correct definitions. If modifications have been made to the generated PL/SQL
code, then check that they are correct.(len
) bytes of data when the gateway was expecting to receive only (num)
bytes.PGDL
and COBOL
record descriptions that are used to define the transaction to PGAU
are syncronized with the transaction program and that the PL/SQL TIP
is generated by PGAU
by using the correct definitions. If modifications have been made to the generated PL/SQL
code, then check that they are correct.PGDL
and COBOL
record descriptions that are used to define the transaction to PGAU
are syncronized with the transaction program and that the PL/SQL TIP
is generated by PGAU
by using the correct definitions. If modifications have been made to the generated PL/SQL
code, then check that they are correct.stat
) was received from the remote transaction program following the CPI-C
(func
) call. The descriptive name of the status code is (desc)
. CPI-C
func function receives the status.CPI-C
function call are documented in the platform-specific SNA software documentation for your system. documentation.
See Also:
Refer to the System Requirements chapter of the Oracle Procedural Gateway for APPC Installation and Configuration Guide for your operating system for titles of SNA softwarestate
), and its descriptive name is (desc)
.PGAINIT
was called with no Side Information profile name specified, but the LU
name, TP
name, and Mode name parameters were not all filled in with non blank values.PGDL
used to define the transaction program to PGAU.
Ensure either a valid Side Information profile name is specified (SIDEPROFILE
keyword), or that the LU name, TP name, and Mode name (LUNAME
, TPNAME
, LOGMODE
keywords) are all specified with valid values. If no Side Information profile is specified, then the LU name, TP name, and Mode name parameters are all required.uid
) was too long (len
) to be used with APPC conversation security. The maximum allowable length for the user ID is max
characters. This can occur only when the gateway initialization parameter PGA_SECURITY_TYPE
is set to either SAME
or PROGRAM
.len
) was too long to be used with APPC conversation security. The maximum allowable length for the password is max
characters. This can occur only when the PGA_SECURITY_TYPE
gateway initialization parameter is set to PROGRAM
.sync
, passed to PGAINIT was not a valid value. This value is specified by the SYNCLEVEL
keyword in the DEFINE TRANSACTION
statement that is used to define the transaction to PGAU.SYNCLEVEL
must fall within the range, min:max
. Correct the value specified in the DEFINE TRANSACTION
statement for the SYNCLEVEL
keyword and regenerate the PL/SQL TIP using PGAU.len)
, passed to PGAXFER
was larger than the maximum allowed, max
.PGDL
and COBOL
record descriptions used to define the transaction to PGAU
do not define any data items larger than the maximum size allowed by APPC
. Correct the data items in error and regenerate the PL/SQL TIP
using PGAU
.keyword=value
, specifies an invalid value.profile
) was not defined to the SNA software. Either the profile name was misspelled, or no profile has been defined.SNA
software if it was not already defined.sync)
passed to PGAINIT
was incompatible with the setting of the PGA_CAPABILITY
gateway initialization parameter (cap)
.PGAINIT
is correct, then the PGA_CAPABILITY
gateway initialization parameter must be changed to allow the desired sync level to be supported. If the sync level is not correct, then the TIP
should be changed to specify the correct sync level in the call to PGAINIT
.
If the TIP was generated by PGAU, then the SYNCLEVEL
keyword of the DEFINE TRANSACTION
statement should be changed to specify the correct sync level and the TIP should be regenerated. In the following list, each PGA_CAPABILITY
value setting is followed by the number of the sync levels that are valid for that setting:
READ_ONLY
or RO
: 0
sync levels allowed
SINGLE_SITE
or SS
: 0
, 1
sync levels allowed
COMMIT_CONFIRM
or CC
: 0
,1
sync levels allowed
PGAXFER
was (len
), but the send lengths array was either null or contained a send count of zero.PGDL
or COBOL
record descriptions that are used to define the transaction to PGAU
are synchronized with the transaction program and that the PL/SQL TIP
is generated by PGAU
by using the correct definitions.PGAXFER
was (len)
, but the receive lengths array was either null or contained a receive count of zero.PGDL
or COBOL
record descriptions that are used to define the transaction to PGAU
are synchronized with the transaction program and that the PL/SQL TIP
is generated by PGAU
by using the correct definitions.PGAXFER
was too small to contain a valid send item count. The actual length of the send lengths array was (len)
. The minimum length of the send lengths array is 4 bytes.TIP
was generated by PGAU
, then ensure that it was modified correctly. If the TIP
was not modified, then supported customers should contact Oracle Support Services for assistance. If the TIP
was modified or was not generated by PGAU
, then correct the send lengths array passed to PGAXFER
.PGAXFER
was too small to contain a valid receive item count. The actual length of the receive lengths array was (len)
. The minimum length of the receive lengths array is 4 bytes.TIP
was generated by PGAU
, then ensure that it was modified correctly. If the TIP
was not modified, then supported customers should contact Oracle Support Services for assistance. If the TIP
was modified or was not generated by PGAU
, then correct the receive lengths array passed to PGAXFER
.PGA_LOG_DB, PGA_LOG_USER
, and PGA_LOG_PASS
parameters in the gateway initialization file and ensure that they specify the correct database string, user ID, and password, respectively.var
) for use in performing transaction logging functions. An Oracle server message follows this message.GA_LOG_DB, PGA_LOG_USER,
and PGA_LOG_PASS
parameters in the gateway initialization file, and ensure that they specify the correct database string, user ID, and password, respectively.PL/SQL
stored procedure. An Oracle server message follows this message.PGA_LOG_DB, PGA_LOG_USER,
and PGA_LOG_PASS
parameters in the gateway initialization file, and ensure that they specify the correct database string, user ID, and password, respectively. Verify that the transaction logging PL/SQL procedure is properly installed on the Oracle server under the user ID and password specified by PGA_LOG_USER
and PGA_LOG_PASS
and that it is executable.var
) to be used for accessing the transaction log table during recovery processing. An Oracle server message will follow this message.PGA_LOG_DB, PGA_LOG_USER
, and PGA_LOG_PASS
parameters in the gateway initialization file, and ensure that they specify the correct database string, user ID, and password, respectively.PGA_LOG_DB
, PGA_LOG_USER
and PGA_LOG_PASS
parameters in the gateway initialization file, and ensure that they specify the correct database string, user ID, and password, respectively. Verify that the transaction logging PL/SQL
stored procedure and the transaction log table are properly installed into the Oracle server under the user ID and password specified by PGA_LOG_USER
and PGA_LOG_PASS
.func
). The function return code is rc
and the system error number is errno
. The AIX SNA Server LU6.2 API function return codes and system error numbers are described in the vendor documentation. The SNA system error numbers can also be found in the /usr/include/luxsna.h
header file on AIX systems.
Table 2-5 lists commonly received rc
and errno
combinations and their possible causes.
Table 2-5 Error Message PGA-20995 on AIX Systems
rc | errno | Possible Cause(s) |
---|---|---|
-1 |
112 |
When received at conversation startup time, either the target When received during an active conversation, the |
-1 |
113 |
A conversation was requested at synclevel 2, but the required |
-1 |
121 |
The transaction program terminated abnormally on the target |
-1 |
123 |
The mode name specified is either not locally defined to |
-1 |
127 |
The transaction program requested is not defined to the target |
-1 |
133 |
A security violation occurred on the target system. Either the user ID or password is not valid on that system, or the user ID is not authorized to execute the requested transaction. |
-1 |
146 |
The target |
-1 |
147 |
The transaction program requested is defined to the target |
-1 |
160 |
The SNA communication package is not active. |
SIGDANGER
signal to the server indicating that there is a shortage of paging space. All currently active conversations are deallocated normally.See Also:
Refer to the Oracle Database Server Messages for information about this Oracle server messageTCP/IP
function (func
). The TCP/IP
function return code (rc
) and the function (func
) parameter is (parm
).uid
) is too long (len
) to be used with TCP/IP RACF
conversation security. This can occur only when the PGA_SECURITY_TYPE
gateway initialization parameter is set to either SAME
or PROGRAM
.max
characters. This restriction is imposed by RACF
, and not by the gateway.len
) to be used with TCP/IP RACF
conversation security. This can occur only when the PGA_SECURITY_TYPE
gateway initialization parameter is set to PROGRAM
.max
characters. This restriction is imposed by RACF
, and not by the gateway.IMS
Connect error occurred while executing the recv
function. The return code (rc
) and reason code (rsc
) are provided in the message text.
For more information, refer to the OLTP SDSF
log and the IMS
Connect error message that starts with HWS
. The messages are documented in the IBM IMS Connect Guide and Reference Manual
len
) passed to PGAINIT
or PGAINIT_SEC
was larger than the maximum allowed length (max
).PGDL
and COBO
L record descriptions used to define the transaction to PGAU
are syncronized with the transaction program and that the PL/SQL TIP
was generated by PGAU
using the correct definitions. If modifications have been made to the generated PL/SQL
code, then ensure that they are correct.
See Also:
For more information, refer to the Oracle Procedural Gateway Installation and Configuration Guide for the required gateway initialization parameters for gateways using TCP/IP