Problem Reporting - UniAccess

Contact Name

Phone Number

E-Mail Address

For problems encountered in UACS, list any PCRs applied to CMS or CPComm:

Tracking Number

Site Name

Description of the Problem

If the error is encountered using a program that accesses the UniAccess Transaction Client or the UniAccess Transaction Server, compiler (e.g., UCOB):

If the error is encountered using a program that accesses the UniAccess Transaction Client or the UniAccess Transaction Server, Compiler Level:

If you are using UniAccess Transaction Server or UniAccess ODBC Server, Operating System:

If you are using UniAccess Transaction Server or UniAccess ODBC Server, Hardware:

If you are using UniAccess Transaction Server or UniAccess ODBC Server, Client Application:

If you are using UniAccess Transaction Server or UniAccess ODBC Server, Client Application Level:

If you are using UniAccess Transaction Server or UniAccess ODBC Server, Custom Application Language:

If you are using UniAccess Transaction Server or UniAccess ODBC Server, Compiler/Interpreter Level:

If you are using UniAccess Transaction Server or UniAccess ODBC Server, UADriver Level:

Component Exhibiting the Error

UACS
UniAccess Transaction Client
UniAccess Transaction Server
UniAccess ODBC Server for RDMS 2200
UniAccess ODBC Server for DMS 2200
UADriver
UADTC
ISQL
Unknown

Which, if any, additional information you have included:

DIAG$ File
UAHS Debug Information
UADriver Trace File
Program Listing
Program Source
UACS Trace File
UniAccess Configuration File

OS 2200 Series Software level: UniAccess Level

OS 2200 Series Software level: EXEC Level

OS 2200 Series Software level: MCB Level

OS 2200 Series Software level: RDMS Level

OS 2200 Series Software level: UREP Level

OS 2200 Series Software level: URTS Level

OS 2200 Series Software level: CMS Level

OS 2200 Series Software level: CPComm Level

OS 2200 Series Software level: System Base Level

Phone

This field is for validation purposes and should be left unchanged.