For security reasons, the access authorization for an Oracle database should be defined via KDCDEF generation.
Please note the following:
The Oracle user name for the connection to Oracle and the associated Oracle password must be generated in KDCDEF (KDCDEF statement DATABASE, USERID and PASSWORD operands).
The Oracle password is stored as a hashcode in the UTM system tables (masked) and is therefore not present in clear text in the UTM dump.
In the open string for the start parameter, specify the placeholder *UTMUSER in place of the Oracle user name and the placeholder *UTMPASS instead of the Oracle password. These placeholders are replaced in accordance with the following rules:
If the open string contains at least one of the placeholders *UTMUSER or *UTMPASS, then UTM replaces the placeholders with the values generated for the specific database system on an xa_open() call. I.e. in the open string, *UTMUSER is replaced by the generated Oracle user name and *UTMPASS by the generated Oracle password.
For security reasons, the Oracle password is converted into clear text only immediately prior to use on an xa_open() call and is then deleted in the process memory immediately after the xa_open() call.
If the open string of the start parameter does not contain either *UTMUSER or *UTMPASS then it is passed unchanged to the xa_open() call.
Please note that processing is case-sensitive!
Examples
You want to use the Oracle user name and the Oracle password from the UTM generation:
OS="Oracle_XA+SqlNet=O11+ACC=P/*UTMUSER/*UTMPASS+DbgFl=15"
Behavior if the Oracle access data is not generated
If the USERID and PASSWORD operands were not specified during UTM generation then you can specify the Oracle user name and the Oracle password directly in the start parameters.
If you specify *UTMUSER or *UTMPASS in the start parameter even though the USERID and PASSWORD operands were not specified during UTM generation then UTM uses an empty Oracle user name or empty Oracle password. As a result, the attempt to establish a connection to the database will generally be unsuccessful.