1. Application Runtime for IMS User's Guide
  2. Oracle Tuxedo Application Runtime for IMS Users Configuration

4 Oracle Tuxedo Application Runtime for IMS Users Configuration

The section contains the following topics:

4.1 General Limitations

DL/I call CHKP is used to send out the messages built and commit the changes made since last check point in IMS. DL/I call ROLB is to abort all the changes made and all the messages built but not sent since last check point. In Tuxedo ART for IMS, ARTIMPP or ARTIBMP need to treat the interval between two check points as a transaction. And possibly resource managers may be added in future.

Note:

The NO_XA option cannot be configured in each domain where ARTIMPP or ARTIBMP lives.

Parent topic: Oracle Tuxedo Application Runtime for IMS Users Configuration

4.2 Environment Variables

To enable Tuxedo ART for IMS, you must set the following environment variables before starting the servers:

  • IMSDIR
  • ART_IMS_DB
  • ART_IMS_CONFIG
  • ART_IMS_FMT
  • COBPATH
  • COB_LIBRARY_PATH

You should set IMSDIR to point to the installation root of Tuxedo ART for IMS product, set ART_IMS_CONFIG to specify the location of configuration files, set ART_IMS_FMT to specify the location of control block files, set ART_IMS_DB to specify the location of GSAM files, and set COBPATH to specify the location of COBOL.gnt files.

To enable Multi-Byte Character Set (MBCS) support, you must set following environment variables for ARTICTL before starting the servers:

  • INTERCODE
  • EXTERCODE

You should set INTERCODE to encoding type used in open platform, set EXTERCODE to EBCDIC encoding type used in z/OS platform.

For more information, see Oracle Tuxedo Application Runtime for IMS Reference Guide

Parent topic: Oracle Tuxedo Application Runtime for IMS Users Configuration

4.3 Configuration Files

All the configuration files in this section are case insensitive for key and non-literal values, for example bool (yes|no) and enum. Literal values and their cases are kept. Comment line should be prefixed with “*”.

The configuration files are as follows:

  • imstrans.desc: Defines IMS transaction codes
  • imsapps.desc: Defines IMS applications
  • imsresource.desc: Define persistent transactions
  • imsdbs.desc: Defines IMS databases
  • $appname.psb: Defines PSB

The general format for configuration files is shown in the Listing below:

Listing 1 General Configuration File Format

[section name]
Field1=value1
Field2=value2
….
[section name]
….
[section name]
…

For more information, see the Oracle Tuxedo Application Runtime for IMS Reference Guide

Parent topic: Oracle Tuxedo Application Runtime for IMS Users Configuration

4.4 Security Configuration

Tuxedo ART for IMS supports three types of Tuxedo security mechanism: application password (APP_PW), user-level authentication (USER_AUTH) and ACL/Mandatory ACL.

Parent topic: Oracle Tuxedo Application Runtime for IMS Users Configuration

4.4.1 Authentication Configuration

In Oracle Tuxedo, each type of security mechanism requires that every user provide an application password as part of the process of joining the Oracle Tuxedo ATMI application, but In Tuxedo ART for IMS, it has been removed in order to keep the same behavior as IMS resides on z/OS. User should keep application password as NULL. For more information, see Using Security in ATMI Applications in the Oracle Tuxedo Users Guide.

The USER_AUTH and ACL/Mandatory ACL security mechanism requires that each user must provide a valid username and password to join the Tuxedo ART for IMS runtime. The per-user password must match the password associated with the user name stored in a file named tpusr. Client name is not used. The checking of per-user password against the password and user name in tpusr is carried out by the Oracle Tuxedo authentication service AUTHSVC, which is provided by the Oracle Tuxedo authentication server AUTHSVR.

For more information, see Using Security in ATMI Applications in the Oracle Tuxedo Users Guide.

When Oracle Tuxedo security is enabled, security profile is required by some Tuxedo ART for IMS components, which include imsadmin, ARTICTL, and DFSRRC00. The security profile securely stores Oracle Tuxedo application password, username and user password. Two types of security profile are supported: Oracle Wallet and profile created by genimsprofile. Oracle Wallet is the recommended profile type.

You can use Oracle utility orapki or mkstore to create an Oracle Wallet and add the username and passwords to it. For example:

To create an Oracle Wallet:

orapki wallet create -wallet <location of the oracle wallet> [ -auto_login_only | -auto_login | -auto_login_local ]

To add application password to an Oracle Wallet:

mkstore -wrl file:<location of the oracle wallet> -createEntry APP_PASSWORD <Application password>

To add username to an Oracle Wallet:

mkstore -wrl file:<location of the oracle wallet> -createEntry USER_NAME <user name>

To add user password to an Oracle Wallet:

mkstore -wrl file:<location of the oracle wallet> -createEntry USER_PASSWORD <user password>

Parent topic: Security Configuration

4.4.2 SSL Configuration

Tuxedo ART for IMS uses the following existing UBBCONFIG file parametersto configure information about SSL identification strings and the location of SSL certificate encryption passwords:

  • SEC_PRINCIPAL_NAME
  • SEC_PRINCIPAL_LOCATION
  • SEC_PRINCIPAL_PASSVAR

For more information, see Using Security in ATMI Applications, in the Oracle Tuxedo Users Guide

Parent topic: Security Configuration

4.4.3 SIGN Command

Tuxedo ART for IMS supports three types of SIGN Commands:

•/SIGN
    •/SIGN
    •/SIGN USER-ID PASSWORD
•/SIGN ON USER-ID PASSWORD
•/SIGN OFF

Parent topic: Security Configuration