Add entries for new SQLCODEs

DB2 UDB versions later than 4.1 return SQLCODEs without corresponding entries in the translate table. In this circumstance, AMD2 assigns a generic error message (“Error 33231”) and sends the associated text from the text table for that message number. To provide clients with more than the generic message, add new entries to the AMD2 message table for each new DB2 SQLCODE.

There are two options for translating new SQLCODEs to client messages. New SQLCODEs can be:

Mapped to existing DB2 UDB Option for CICS messages (“Error 30000”, “Error 30001”, and “Error 30002”).
Mapped to messages that correspond to ASE messages. These ASE messages may exist in the AMD2 message table, or you may need to create new entries for these messages.

The changes to the AMD2 message table for the preceding two options are shown in Table 5-3.

**Table 5-3: Adding entries for new SQLCODEs**
Option	Message number (MSGNO=)	Translate table changes	Text table changes	For coding the changes, see
Map to existing DB2 UDB Option messages.	Assign number by severity level: 30000–Error 30001–Warning 30002–Confirmation	Add an SYRTMAMX entry for each new message.	No change.	“Adding a translate table entry”.
Map to ASE messages.	Use corresponding ASE message number.	Add an SYRTMAMX entry for each new message.	If message is already in text table, no change is needed. If message is not in text table, add the message number and the text of ASE message to SYRTMAMT entry for each language in use.	“Adding a translate table entry”. “Adding a message to the text table”.