UniAccess ODBC Server for RDMS 2200 Issues

Knowledge Base: UniAccess ODBC Server for RDMS 2200 Issues

The following are solutions to commonly reported UniAccess errors specific to the UniAccess ODBC Server for RDMS 2200 environment. See the proceeding sectionUniAccess Server Issues for other reported errors.

Problem:
ODBC UARS Transactions consume a lot of CPU time.
Solution:
Review this document to see if your site needs to apply this Unisys PLE.
Problem:
UniAccess Relational Service Transaction (UARS) Does Not Receive RDMS Table Information when used with RDMS 12R2, 13R1, 13R1A, or 14R1.
Solution:
Review this document to see if your site needs to apply this Unisys PLE.
Problem:
The UARS transaction may appear to stall until the RELSRV WAITTIME expires.

The apparent stall of the UARS transaction may cause the client application to indicate that the server has timed out.

This has been determined to be caused by modifications to memory handling introduced by the EXEC change 00006-61620-PCR.

Solution:
The suggested resolution is dependent upon the hardware platform.

  • M Series Systems(2200/300, 2200/500, 2200/700, 2200/900, 2200/3800)

    The resolution for the apparent transaction stall is to change the VALTAB to indicate that the transaction should run in “TIP-memory-compatible mode”. This is specified by the O option in the VALTAB indicator field.

    For additional information please see the OS 2200 Transaction Processing Administration and Operations Reference Manual that corresponds to the System Base installed on your system.

    The resolution for C Series Systems, described below, will also work on M Series systems.

    For better performance, the VALTAB program type for UARS should be reentrant (PRG,3), and the FLAGBOX bit for STICKING should be set (FB ON STICKING). Additional performance gains can be made by making the transaction a  resident transactions. Resident online programs (RTPS feature) are loaded either via TP keyin or RPINIT utility request.

  • C Series Systems (1100/90, 2200/400, 2200/600, 2200/600ES)

    If TIP memory is being used on the system, the VALTAB should be updated to indicate that the transaction should run in TIP memory. This is specified by the O option in the VALTAB indicator field.

    If TIP memory is not being used on the system, the value of the WAITTIME parameter on the RELSRV configuration statement should be set to 0 (zero). UniAccess Server-Library transactions should set the TDWAITTIME to 0 (zero).For better performance, the VALTAB program type for UARS should be reentrant (PRG,3), and the FLAGBOX bit for STICKING should be set (FB ON STICKING). Additional performance gains can be made by making the transaction a resident transaction. Resident online programs (RTPS feature) are loaded either via TP keyin or RPINIT utility request.

Problem:
UARS transaction receives an out-of-memory error (RDM error 50000).

The VALTAB O indicator option causes the UARS transaction to run in TIP-compatible-memory.  The EXEC prevents the attempts to expand or contract application level backs for transactions in “TIP memory”. 

Solution:
Any of the following will resolve the problem.<br

  • Apply the changes associated with EXEC PLE 17074075.
  • Move to EXEC level 45R2A, or later.  EXEC level 45R2A is supplied with SB7.1 and HMP-IX3.1.
  • Remove the O indicator option from the UARS VALTAB and set the RELSRV WAITTIME to zero (0).
Problem:
When tables are dropped that were created using the implicit storage area feature of RDMS 2200, the underlying storage area that is automatically created by the create table command is not dropped. This creates a problem if an attempt is made to recreate the table.
Solution:
The storage area must be manually deleted before attempting to recreate the table. Implicit storage area creation can be overridden by specifying a Storage Area when a UniAccess data source is configured. This storage area must be created by the OS 2200 system administrator before any table creation commands can be issued. All tables that are created using the UniAccess data source will be placed in the storage area specified in the Storage Area field. See the Unisys Relational Data Management System (RDMS 2200) Administration Guide, section 2.3.2: Creating a Table with an Implicit Storage Area for more details.
Problem:
UARS receives the following message: “APP x DCS EX 20120 This run is not configured in UDS to pass a caller certified user-id. The BEGIN THREAD command is ignored.

This error will occur when TIP session control is not active and MASTER-RUN-USERID is not=@@@@@@@@@@@@

Solution:
Use @DD to update the UREP Configuration MASTER-RUN-USERID attribute in APP x to ‘@@@@@@@@@@@@’.
Problem:
Table or column information is not being returned to the ODBC client.
Solution:
When UREP is installed, it defaults to partial options set for RDMS. If this is the case, table and column names will not be maintained. The runstream SYS$LIB$*UAUTIL(T).UNIACCESS/CREATE, when added, changes this to RDMS-LEVEL COMPLETE, capturing all future table and column names to the repository. However, any tables created prior to adding this runstream are not automatically updated in the repository. Note: If there are foreign key relationships between tables, you must ATTACH the parent table first. To update the repository with the complete table information, perform the following:

@DD,E,appname
PROCESS TABLE tablename FOR SCHEMA schemaname ATTACH

Knowledge Base: UniAccess ODBC Server for RDMS 2200 Issues