PGA-20916
send count is number but only number 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 modifications have been made to the generated PL/SQL code, check that they are correct.
PGA-20916
send count is number but only number 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 modifications have been made to the generated PL/SQL code, check that they are correct.
PGA-20916
send count is number but only number 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 modifications have been made to the generated PL/SQL code, check that they are correct.
