Customizing TDPUAX
When customizing a TDPUAX module, the following points must be considered:
TDPUAX can include a user word in its parameter list to maintain context across calls. The parameter list is associated with the jobstep task under which the application is executing. Thus, the contents of the user word are passed to TDPUAX with each call under that jobstep task.
If another application is executing under a different jobstep task in the same address space and initiates a logon to the Teradata Database, a different parameter list (and thus another unique user word) is passed.
If TDPUAX invokes services that require a save area, TDPUAX must provide one for the use of that service.
Control is passed to TDPUAX with general register 1 pointing to the TDPUAXP control block (parameter list), which contains the following:
Note: The TDP identifier and separating slash that CLI allows as a prefix to the Logon String, and the ending semicolon character, are removed by CLI, so are not present within the exit.
If the logon string is parsed, the userid, password, and account name each consists of characters from the session character set. When supported by the session character set, each contiguous group of double byte characters is preceded by the Shift-out control character, X’0E’, and followed by the Shift-in control character, X’0F’. Neither commas nor blanks can be specified as double byte characters.
On return, TDPUAX passes one of the following return codes to TDP in general register 15:
Return Code |
Meaning |
0 |
Allow the logon request to continue. |
Nonzero |
Do not allow the logon request to continue. |
The parameter list is described by the TDPUAXP macro, which is distributed with the product.