2 Procedural Gateway Server Messages

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, documented in the Oracle Open Gateways Guide for SQL-Based and Procedural Gateways.

This chapter contains the following sections:

Messages PGA-20900 to PGA-20927
Messages PGA-20930 to PGA-21451
Message PGA-22001 to 22012 (for Gateway using TCP/IP)

2.1 Messages PGA-20900 to PGA-20927

PGA-20900 unable to obtain n bytes of storage for description: Cause: Memory shortage in the gateway server process.; Action: Ensure that your system has enough available memory to support the number of concurrent users you are running.

PGA-20901 internal gateway error: [arg1] [,arg2] [,arg3] [,arg4] [,arg5]: Cause: Internal error in the gateway server process.; Action: Reproduce the error with debugging enabled in order to produce a log file. Supported customers should contact Oracle Support Services for assistance.

PGA-20905 invalid conversation id: no active conversations were found: Cause: There were no APPC conversations active for the user.; Action: Check that the application is not calling the PL/SQL TIP routines out of sequence.

PGA-20906 invalid conversation id: no matching conversation was found: Cause: The conversation id received from the caller is not a valid active conversation id.; Action: Check that the application is not calling the PL/SQL TIP routines out of sequence.

PGA-20907 preceding error occurred during gateway func processing: Cause: An error occurred processing the specified Oracle function func. This message is preceded by additional messages providing more information about the error.; Action: Refer to the messages preceding this one to determine the course of action.

Locate Error Message PGA-20910 for Your Platform From This List

PGA-20910 communication error: CPI-C func failed, rc = rc, errno = errno: Cause: (on AIX systems) An unexpected communication error occurred while executing the specified CPI-C function (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. Also, the CPI-C return codes can be found 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.; Action: Determine the cause of the communications error, correct it, and rerun the transaction.

Table 2-1 Error Message PGA-20910 for AIX Systems

rc	errno	Possible Cause(s)
1	22	The partner LU location profile for the target LU is either missing or incorrect, or the target LU is not active or has not enabled SNA communications.
1	25	The LU name is not defined on the target system. This name is the fully-qualified LU name specified in either the Side Information Profile or the Partner LU Location Profile.
6	133	A security violation occurred on the target system. Either the user ID/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 LU.
10	147	The transaction program requested is defined to the target LU, but could not be found.
17	121	The transaction program terminated abnormally on the target LU, or issued a DEALLOCATE_ABEND.
19	9	Either the target LU name or alias is not defined locally to SNA Server, the mode name is not defined locally to SNA Server, or the mode name is not defined to the target LU.
20	125	The SNA session on which the conversation was running has been terminated, or SNA communication package is shutting down.
20	160	SNA Server is not currently running.

PGA-20910 communication error: CPI-C func failed, rc = rc, errno = errno: Cause: (on HP-UX) An unexpected communication error occurred while executing the specified CPI-C function (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.
Some commonly received return codes and their possible causes on HP-UX are listed in Table 2-2 below.; Action: Determine the cause of the communications error, correct it, and rerun the transaction.

Table 2-2 Error Message PGA-20910 for HP-UX

rc	errno	Possible Cause(s)
2	n/a	The target LU is not active or has not established communications with the SNA communications package.
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 OLTP.
9	n/a	The transaction program requested is not defined to the target OLTP.
10	n/a	The transaction program requested is defined to the target OLTP, but could not be found.
17	n/a	The transaction program terminated abnormally on the target OLTP, or issued a DEALLOCATE_ABEND.
19	n/a	The mode name specified was not defined in the mode table for the target LU, or the LU name specified does not exist, or the LU name specified is not defined to the SNA communication packages.
26	n/a	The SNA communication package is not active, or the local node or link station is not active.

PGA-20910 communication error: CPI-C func failed, rc = rc, errno = errno: Cause: (on Solaris) An unexpected communication error occurred while executing the specified 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 some commonly received rc and errno combinations, and their possible causes on Solaris.; Action: Determine the cause of the communications error, correct it, and rerun the transaction.

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 OLTP.
9	0	The transaction program requested is not defined to the target OLTP.
17	0	The transaction program terminated abnormally on the target OLTP, or issued a DEALLOCATE_ABEND.

PGA-20910 communication error: CPI-C func failed, rc = rc, errno = errno: Cause: (on Microsoft Windows) An unexpected communication error occurred while executing the specified 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/errno messages, and their possible causes.; Action: Determine the cause of the communication error, correct it and rerun the transaction.

Table 2-4 Error Message PGA-20910 for Microsoft Windows

rc	errno	Possible Cause(s)
2	0	Either the target LU name is not defined on the target system or the mode name is not defined on the target system.
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 LU.
10	0	The transaction program requested is defined to the target LU, but could not be found.
17	0	The transaction program terminated abnormally on the target LU, or issued a DEALLOCATE _ABEND.
19	0	The target LU is not active or has not established communication with the Microsoft Host Integration Server.
20	0	Either the target LU name or alias is not defined locally to the Microsoft Host Integration Server, or the mode name is not defined locally to the Microsoft Host Integration Server.

If you are using the IBM Communication Server, the error message numbers and return codes you get are different from those listed above. Refer to the wincpic.h file for more information about error message numbers.

PGA-20911 update transaction is already active with TP tpname at LU luname: Cause: Transaction 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.; Action: The new transaction is not started. Change your application to start the second update transaction after the first one has completed.

PGA-20912 send and receive buffer lengths cannot both be zero: Cause: Both the send and receive buffer lengths passed to PGAXFER were zero. This is invalid.; Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync 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.

PGA-20914 send buffer length of len exceeds actual send buffer size of size: Cause: The send buffer length (len) passed to PGAXFER was larger than the actual size (size) of the send buffer passed to PGAXFER.; Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync 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.

PGA-20915 receive buffer length of len exceeds the maximum of max: Cause: The receive buffer length len passed to PGAXFER was larger than the maximum allowed length max.; Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync 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.

PGA-20916 send count is count but only num send lengths were specified: Cause: The first value 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.; Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions. If you have modified the generated PL/SQL code, check that the modifications are correct.

PGA-20917 receive count is count but only num receive lengths were specified: Cause: The first value 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.; Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions. If you have modified the generated PL/SQL code, check that the modifications are correct.

PGA-20918 send length number num is len but only bytes bytes are left in the buffer: Cause: The length (len) specified in send lengths array element number num exceeded the number of bytes (bytes) of data remaining in the send buffer.; Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync 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.

PGA-20919 receive length number num is len but only bytes bytes are left in the buffer: Cause: The length len specified in receive lengths array element number num exceeded the number of bytes (bytes) of space remaining in the receive buffer.; Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync 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.

PGA-20920 unexpected request-to-send received: Cause: The remote transaction program requested to send data when the gateway was still sending data.; Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync 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.

PGA-20921 buffer overflow on receive: requested num bytes, received len bytes: Cause: The remote transaction program sent len bytes of data when the gateway was expecting to receive only num bytes.; Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync 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.

PGA-20922 no data available to receive: num bytes were requested: Cause: The remote transaction program has either requested to receive or deallocated the conversation, but the gateway is still expecting to receive more data.; Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync 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.

PGA-20923 unexpected status, stat, received after func: Cause: An unexpected status code stat was received from the remote transaction program following the CPI-C func call. The descriptive name of the status code is desc. func is the CPI-C function receiving the status.; Action: This is usually a problem with the remote transaction program or a network problem. The status codes for each CPI-C function call are documented in the platform-specific SNA software documentation for your system. Refer to the "System Requirements" chapter of the Oracle Procedural Gateway for APPC Installation and Configuration Guide for your platform for titles of SNA software documentation.

PGA-20924 unable to enter send state for normal deallocate, state = state (desc): Cause: The gateway was unable to enter send state to perform a normal deallocation. The conversation state is state, and its descriptive name is desc.; Action: This is usually a problem with the remote transaction program or a problem with the network. Check the remote system for diagnostic information. The gateway performs an abnormal deallocation after this error has been encountered.

PGA-20925 missing LU/TP/Mode name parameter and no side info profile specified: Cause: 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.; Action: Check the PGDL used to define the transaction program to PGAU to 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.

PGA-20926 userid uid length of len is invalid; maximum length is max: Cause: The user ID (uid) is 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.; Action: The user ID must be changed to a shorter value on both the client system and the system where the remote transaction program is being executed. This restriction is imposed by SNA and APPC, not by the gateway.

PGA-20927 password length of len is invalid; maximum length is max: Cause: The password length is too long (len) to be used with APPC conversation security. The maximum allowable length for the password is (max) characters. This can occur only when the gateway initialization parameter PGA_SECURITY_TYPE is set to PROGRAM.; Action: The password must be changed to a shorter value on both the client system and the system where the remote transaction program is being executed. This restriction is imposed by SNA and APPC, not by the gateway.

2.2 Messages PGA-20930 to PGA-21451

PGA-20930 invalid SYNCLEVEL, sync, specified; valid range is min:max: Cause: The synclevel, sync, passed to PGAINIT is not a valid value. This value is specified by the SYNCLEVEL keyword in the DEFINE TRANSACTION statement used to define the transaction to PGAU.; Action: The value for the 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.

PGA-20931 send buffer length of len exceeds the maximum of max: Cause: The send buffer length, len, passed to PGAXFER was larger than the maximum allowed, max.; Action: Check that the 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 item(s) in error and regenerate the PL/SQL TIP using PGAU.

PGA-20932 invalid function code, func, passed to pgatctl: Cause: The function code, func, passed to the PGATCTL function was invalid.; Action: Correct the function code in the PL/SQL procedure, recompile it and retry the operation.

PGA-20933 invalid value specified by initialization parameter keyword=value: Cause: The keyword parameter keyword=value specifies an invalid value.; Action: Refer to the Oracle Procedural Gateway for APPC Installation and Configuration Guide documenting gateway initialization parameters for the keyword and correct the error.

PGA-20934 side information profile profile not defined; cannot establish conversation: Cause: The Side Information profile (profile) is not defined to the SNA software. Either the profile name was misspelled, or no profile has been defined.; Action: Correct the profile name if it was misspelled, or have the profile defined to the SNA software if it was not already defined.

PGA-20935 sync level sync is not allowed when PGA_CAPABILITY=cap

Cause: The sync level parameter that was requested (sync) passed to PGAINIT was incompatible with the setting of the PGA_CAPABILITY gateway initialization parameter, (cap).

Action: If the sync level passed to PGAINIT is correct, then the gateway initialization parameter PGA_CAPABILITY 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 level(s) 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

PGA-20936 send buffer length is len but no send lengths were specified: Cause: The send buffer length passed to PGAXFER was len, but the send lengths array was either null or contained a send count of zero.; Action: Check that the PGDL or COBOL record descriptions used to define the transaction to PGAU are synchronized with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions.

PGA-20937 receive buffer length len but no receive lengths were specified: Cause: The receive buffer length passed to PGAXFER was len, but the receive lengths array was either null or contained a receive count of zero.; Action: Check that the PGDL or COBOL record descriptions used to define the transaction to PGAU are synchronized with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions.

PGA-20938 send lengths array too small (len) to contain a valid send count: Cause: The send lengths array passed to 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.; Action: If the TIP was generated by PGAU, then ensure that it was not modified incorrectly. 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.

PGA-20939 receive lengths array too small (len) to contain a valid receive count: Cause: The receive lengths array passed to 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.; Action: If the TIP was generated by PGAU, then ensure that it was not modified incorrectly. 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-20945 unable to log on to Oracle for transaction logging: Cause: The gateway server was unable to connect to the Oracle server where the transaction log table is stored. An Oracle server message will follow this message.; Action: Ensure that the Oracle server and its TNS listener are both operational. Also check the 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. Refer to the Oracle Database Server Messages for information on this Oracle server message.

PGA-20947 unable to bind variable var for transaction logging: Cause: The gateway server was unable to bind variable (var) for use in performing transaction logging functions. An Oracle server message follows this message.; Action: Ensure that the Oracle server and its TNS listener are both operational. Also check the 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. Refer to the Oracle Database Server Messages for information on this Oracle server message.

PGA-20948 unable to prepare the statement for transaction logging: Cause: The gateway server was unable to prepare the statement to be used to call the transaction logging PL/SQL stored procedure. An Oracle server message will follow this message.; Action: Ensure that the Oracle server and its TNS listener are both operational. Also check the 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 has been properly installed into the Oracle server under the user ID and password specified by PGA_LOG_USER and PGA_LOG_PASS and that it is executable. Refer to the Oracle Database Server Messages for information on this Oracle server message.

PGA-20949 unable to define variable var for transaction recovery: Cause: The gateway server was unable to define the variable (var) to be used in accessing the transaction log table during recovery processing. An Oracle server message will follow this message.; Action: Ensure that the Oracle server and its TNS listener are both operational. Also check the 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. Refer to the Oracle Database Server Messages for information on this Oracle server message.

PGA-20950 unable to perform oper on transaction log: Cause: The gateway server was unable to insert, update, or delete a pending transaction row in the transaction log table. An Oracle server message will follow this message.; Action: Ensure that the Oracle server and its TNS listener are both operational. Also check the 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 have been properly installed into the Oracle server under the user ID and password specified by PGA_LOG_USER and PGA_LOG_PASS. Refer to the Oracle Database Server Messages for information on this Oracle server message.

PGA-20995 communication error: func failed, rc =rc, errno = errno: Cause: An unexpected communications error occurred while executing the AIX SNA Server API func function. 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 some commonly received rc and errno combinations, and their possible causes.; Action: Determine the cause of the communications error, correct it, and rerun the transaction. If you need assistance, then contact your system administrator.

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 LU is not active or has not enabled SNA communications, or the target LU name is not defined on the target system. The target LU name is the fully-qualified LU name specified in either the side information profile or the Partner LU Location Profile. When received during an active conversation, the SNA session on which the conversation was running has been terminated.
-1	113	A conversation was requested at synclevel 2, but the required LU6.2 Resource Recovery Manager, PG4ARRM, is not active on the Local LU.
-1	121	The transaction program terminated abnormally on the target LU, or issued a DEALLOCATE_ABEND.
-1	123	The mode name specified is either not defined locally to SNA Server, or it is not defined to the target LU.
-1	127	The transaction program requested is not defined to the target LU.
-1	133	A security violation occurred on the target system. Either the user ID/password is not valid on that system, or the user ID is not authorized to execute the requested transaction.
-1	146	The target LU name or alias is not defined locally to SNA Server.
-1	147	The transaction program requested is defined to the target LU, but could not be found.
-1	160	SNA communication package is not active.

PGA-20999 SIGDANGER received from system - all conversations deallocated: Cause: The system sent a SIGDANGER signal to the server indicating that there is a shortage of paging space. All currently active conversations are de-allocated normally.; Action: Contact your system administrator.

2.3 Message PGA-22001 to 22012 (for Gateway using TCP/IP)

PGA-22001 remote host name is null.: Cause: TCP/IP protocol has returned " null" for the remote host name.; Action: Verify the remote host name via the pg4tcpmap tool and re-execute your PL/SQL statement. If the problem cannot be resolved, supported customers should contact Oracle Support Services.

PGA-22002 communication error: TCP/IP func failed, rc = rc: Cause: The TCP/IP function (func) has failed with the return code of rc.; Action: If the problem cannot be resolved, supported customers should contact Oracle Support Services.

PGA-22003 communication error: TCP/IP func failed, rc = rc, for parm: Cause: An unexpected communications error occurred while executing the specified TCP/IP function (func). The TCP/IP function return code (rc) and the function (func) parameter is (parm).; Action: If the problem cannot be resolved, supported customers should contact Oracle Support Services.

PGA-22004 length of the total message value len not within valid range (min:max): Cause: The length (len) for the value is not within the valid range (min):(max).; Action: If the problem cannot be resolved, supported customers should contact Oracle Support Services.

PGA-22005 invalid socket file descriptor: no active conversations were found: Cause: There were no TCP/IP conversations active for the user.; Action: Check that the application is not calling the PL/SQL TIP routines out of sequences.

PGA-22006 parameter parm is not specified: Cause: Parameter (parm) is missing from the gateway initialization file.; Action: Add the missing parameter to the gateway initialization file. Refer to the Oracle Procedural Gateway Installation and Configuration Guide for the required initialization parameters for gateways using TCP/IP.

PGA-22007 user ID uid length of len is invalid; maximum length is max: Cause: The user ID (uid) is too long (len) to be used. The maximum allowable length for the user ID is max characters.; Action: The user ID must be changed to a shorter value for OCI logon to the table PGA_TCP_IMSC. Refer to the Oracle Procedural Gateway Installation and Configuration Guide for the required gateway initialization parameters for gateways using TCP/IP.

PGA-22008 password length of len is invalid; maximum length is max: Cause: The password is too long (len) to be used. The maximum allowable length for the password is max.; Action: The password must be changed to a shorter value for OCI logon to the PGA_TCP_IMSC table. Refer to the Oracle Procedural Gateway Installation and Configuration Guide for the required gateway initialization parameters for gateways using TCP/IP.

PGA-22009 database name db name length of len is invalid; maximum length is max: Cause: The database name (db name) is too long (len) to be used. The maximum allowable length for the database name is (max).; Action: The database name must be changed to a shorter value for OCI logon to the PGA_TCP_IMSC table. Refer to the Oracle Procedural Gateway Installation and Configuration Guide for the required gateway initialization parameters for gateways using TCP/IP.

PGA-22010 userid uid length of len is invalid; maximum length is max: Cause: The user ID (uid) is too long (len) to be used with TCP/IP RACF conversation security. This can occur only when the gateway initialization parameter PGA_SECURITY_TYPE is set to either "SAME" or "PROGRAM".; Action: The user ID must be change to a shorter value on both the client system and the system where the remote transaction program is being executed. The maximum allowable length for the user ID is max characters. This restriction is imposed by RACF, not by the gateway.

PGA-22011 password length of len is invalid; maximum length is max: Cause: The password is too long (len) to be used with TCP/IP RACF conversation security. This can occur only when the gateway initialization parameter PGA_SECURITY_TYPE is set to "PROGRAM".; Action: The password must be changed to a shorter value on both the client system and the system where the remote transaction program is being executed. The maximum allowable length for the password is max characters. This restriction is imposed by RACF, not by the gateway.

PGA-22012 IMS Connect error: return code = rc, reason code =rsc: Cause: An unexpected 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 IMS Connect error message which starts with HWS. The messages are documented in the IBM IMS Connect Guide and Reference Manual; Action: Determine the cause of the error, correct it, and rerun the transaction.

PGA-22014 transaction code length of len exceeds the maximum of max: Cause: The transaction code length (len) passed to PGAINIT or PGAINIT_SEC was larger than the maximum allowed length (max).; Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync 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, check that they are correct.