release bulletin directconnect for db2/mvs release 10.5 for

December 9, 1996 1

Copyright © 1989–1996 by Sybase, Inc. All rights reserved. Sybase, the Sybase logo, Data Workbench, DBA Companion, Deft, GainMomentum, PowerBuilder, Powersoft, SQL Advantage, SQL Debug, Transact-SQL, ADA Workbench, AnswerBase, APT-Build, APT-Edit, APT-Execute, APT-Library, APT-Translator, APT Workbench, Backup Server, Client-Library, DB-Library, DirectCONNECT,Embedded SQL, Enterprise Builder, Enterprise Client/Server, Enterprise CONNECT, InformationCONNECT, InfoMaker,MainframeCONNECT, MAP, MDI, Net-Gateway, Net-Library, ObjectCONNECT, OmniCONNECT, OmniSQL Access Module,OmniSQL Server, Open Client, Open ClientCONNECT, Open Client/Server, Open Client/Server Interfaces, Open Gateway, OpenServer, Open ServerCONNECT, PC DB-Net, Replication Agent, Replication Driver, Replication Server, Replication Server Manager,Report Workbench, RW-Library, Secure SQL Server, SQL Server, SQL Server Manager, SQL Server Monitor, SQL Toolset, SQRWorkbench, Sybase IQ, Sybase MPP, Sybase SQL Desktop, Sybase SQL Workgroup, SyBooks, System 10, System 11, Watcom SQL,WorkGroup SQL Server, XA-Library, and XA-Server are trademarks of Sybase, Inc. Other product names used herein may betrademarks or registered trademarks of Sybase or other companies.

72237-01-1050-01

Release BulletinDirectCONNECT for DB2/MVS

Release 10.5for IBM RISC System/6000 AIX

Table of Contents

1. Product Summary 2

1.1. Migration Issues 2

1.2. Compatibility 3

2. Technical Support 3

3. Release Contents 4

3.1. Contents and Product Numbers 4

3.2. ISO Disclaimer 5

4. Special Installation and Configuration Instructions 5

4.1. DB2 Access Service Library 5

4.2. Transaction Router Service 5

5. Known Issues - DB2 Access Service Library 6

5.1. Backward Compatibility with MDI Database Gateway 7

5.2. Cursors 7

5.3. OmniCONNECT and DB2 Datatypes 8

5.4. Transfer 9

5.5. Configuration Tool 10

5.6. Stored Procedures 11

5.7. DB2 Configuration Files 11

2 Release Bulletin for IBM RISC System/6000 AIX

Product Summary DirectCONNECT for DB2/MVS Release 10.5

1. Product Summary

Enclosed is DirectCONNECT™ for DB2/MVS Release 10.5, which isa unified version of two previous products:

• MDI Database Gateway for MVS

• Net-Gateway

DirectCONNECT for DB2/MVS Release 10.5 is compatible with IBMRISC System/6000 AIX 4.1.4 platform and operating system.

For complete hardware and software requirements, see theDirectCONNECT for DB2/MVS Installation Guide for IBM RISCSystem/6000 AIX.

1.1. Migration Issues

DirectCONNECT for DB2/MVS Release 10.5 is backwardcompatible with MDI Database Gateway and Net-Gateway.

1.1.1. MDI Database Gateway

DirectCONNECT for DB2/MVS Release 10.5 Access Service Libraryis backward compatible with MDI Database Gateway for MVSVersions 2.03 and 2.05. For detailed information about backwardcompatibility with MDI Database Gateway, see the DirectCONNECTfor DB2/MVS Access Service Guide.

1.1.2. Net-Gateway

DirectCONNECT for DB2/MVS Release 10.5 Transaction RouterService is backward compatible with Net-Gateway Versions 3.0 and3.0.1.

5.8. Utility Program 12

6. Setting Up Related Products 12

6.1. SQL Server 12

6.2. OmniCONNECT 10.5 14

6.3. Replication Server 17

Table of Contents

Release Bulletin for IBM RISC System/6000 AIX 3

DirectCONNECT for DB2/MVS Release 10.5 Technical Support

1.2. Compatibility

DirectCONNECT for DB2/MVS Release 10.5 is compatible with:

• Open Client/Server™ Release 10.0.4

• Sybase SQL Server™ Release 10.0.2 or higher

• DB2 V2R3 and higher

• CICS 3.3 and PTF UN90057 for full functionality with thepassword expiration manager (PEM) feature

• OmniCONNECT™ Release 10.5

• Sybase Replication Server™ Release 11.0

DirectCONNECT for DB2/MVS Release 10.5 supports the followingapplications (listed by company, product name, and version):

• Andyne GQL 3.2.1

• Business Objects BusinessObjects 3.1.1

• Cognos Impromptu 3.0.4

• Microsoft Access 7.0

• Microsoft Visual Basic 3.0

• Powersoft Powerbuilder 4.0

If you are currently using one of these applications, we recommendthat you download DirectCONNECT certification reports for yourapplication by accessing the Sybase Partners world wide web page.

Please note that the following Sybase Partners web address is case-sensitive:

www.sybase.com/Partners/certification

➤ NoteDirectCONNECT for DB2/MVS Release 10.5 does not currently support

the PeopleSoft application.

2. Technical Support

If you have any questions about this installation or need assistanceduring the installation process, please contact SybaseInformationCONNECT Division (ICD) Technical Support or theSybase subsidiary in your area.


Release Contents DirectCONNECT for DB2/MVS Release 10.5

If you do not know how to contact Sybase Technical Support, pleasecontact the distributor from which your software was purchased.

3. Release Contents

DirectCONNECT for DB2/MVS Release 10.5 includes the following:

• Program tape, diskettes or CD

• Product documentation

• This release bulletin

➤ NoteFor directory and file information, see the README file on the program

tape, diskette or CD.

3.1. Contents and Product Numbers

The following table shows the contents and product ID numbers ofDirectCONNECT for DB2/MVS Release 10.5.

Table 1: DirectCONNECT for DB2/MVS Release 10.5 product set

Product Product Type Product ID

DirectCONNECT for DB2/MVS for IBM RISCSystem/6000 AIX

Program tapeor CD

26770-10-1050-4126770-55-1050-41

DirectCONNECT for DB2/MVS InstallationGuide for IBM RISC System/6000 AIX

Document 34203-01-1050-01

DirectCONNECT for DB2/MVS ConnectivityGuide for IBM RISC System/6000 AIX

Document 36459-01-1050-01

DirectCONNECT Server Administration Guide Document 35365-01-1050-01

DirectCONNECT Error Message Guide Document 38580-01-1050-01

DirectCONNECT for DB2/MVS Access ServiceGuide

Document 36455-01-1050-01

DirectCONNECT Transaction Router ServiceGuide

Document 38581-01-1050-01


DirectCONNECT for DB2/MVS Release 10.5 Special Installation and Configuration Instructions

3.2. ISO Disclaimer

Some DirectCONNECT products incorporate software that islicensed for distribution by Sybase from third parties. Sybase makesno express or implied representation, warranty, or promiseregarding the ISO 9001 certification status of such third-partysoftware. This disclosure is intended to notify customers that third-party software incorporated into the product is not covered by anySybase ISO 9001 certification. However, it does not imply any lack ofquality, reliability, or certifiability of such third-party products.

4. Special Installation and Configuration Instructions

4.1. DB2 Access Service Library

If you install DirectCONNECT for DB2/MVS Release 10.5 on thesame machine on which other Sybase products (such asOmniCONNECT) are already installed, we recommend that youinstall DirectCONNECT in a separate directory structure to avoidpossible shared library conflicts. For detailed installationinstructions, see the DirectCONNECT for DB2/MVS Installation Guidefor IBM RISC System/6000 AIX.

4.2. Transaction Router Service

4.2.1. Requirements for each Transaction Router Service configuration

Transaction Router Service requires a separate DirectCONNECTserver installation per unique Transaction Router Serviceconfiguration set. For detailed configuration instructions, see theDirectCONNECT Transaction Router Service Guide.

4.2.2. Using the Transaction Router Service DateTime Property

The MainframeCONNECT DateTime configuration propertyspecifies the format that MainframeCONNECT uses to return DB2timestamps. The default specification is DB2.

To return timestamps in a format that allows OmniCONNECT tocommunicate with the DirectCONNECT Transaction Router Service,specify the format TRO.


Known Issues - DB2 Access Service Library DirectCONNECT for DB2/MVS Release 10.5

If you use service name redirection, set up services using theexamples shown in the following table.

trs_db2_service Example

The trs_db2_service has a default language handler defined to runagainst transaction AMD2. In this example, AMD2 has defined theDateTime configuration property on the host to be DB2.

You also need to set up the Transaction Router Service defaultlanguage handler with the sgw_addrpc local procedure, when you arerunning TRS with the security off, as follows:

exec sgw_addrpc SYRT, AMD2, region, security

For detailed configuration instructions, see the DirectCONNECTTransaction Router Service Guide.

trs_tro_service Example

The trs_tro_service has a default language handler defined to runagainst transaction AMD3. In this example, AMD3 has defined theDateTime configuration property on the host to be TRO.

Here, too, you need to set up the Transaction Router Service defaultlanguage handler with the sgw_addrpc local procedure as follows:

exec sgw_addrpc SYRT, AMD3, region, security

5. Known Issues - DB2 Access Service Library

This section contains known issues pertaining to DirectCONNECTfor DB2/MVS Release 10.5 for DB2 Access Service Library.

Table 2: Service Setup for Alternative DateTime Configuration

requested_service user_id application_name assigned_service

DB2 * isql trs_db2_service

DB2 * Omni trs_tro_service


DirectCONNECT for DB2/MVS Release 10.5 Known Issues - DB2 Access Service Library

5.1. Backward Compatibility with MDI Database Gateway

5.1.1. Destination-Template Transfer

Destination-template transfers using ?D, ?d, ?T or ?t datatypequalifiers for non-datetime character source data do not behave inthe same way as in the MDI Database Gateway. These qualifiers dowork the same for DATE, SMALLDATETIME (DATETIME4),DATETIME, TIME, and TIMESTAMP data.

When you use destination-template to transfer CHAR data that isalready in a DB2 DATE format from a CHAR or VARCHAR columnto a DB2 DATE column, the ?d datatype qualifier fails. Using the ? or?C datatype qualifier correctly transfers the data.

Similarly, the ?t datatype qualifier fails to transfer char data in a DB2TIME format to a DB2 TIME column. Using either the ? or ?C qualifierpermits the data to transfer correctly.

5.1.2. Error Messages

DirectCONNECT for DB2/MVS Release 10.5 does not providebackward-compatible messages for MDI Database Gateway.

5.2. Cursors

5.2.1. Inconsistencies Related to Cursors in Open Client

The following are Open Client inconsistencies related to cursors witholder (pre 10.0.4) versions.(These problems do not exist with OpenClient version 10.0.4 or newer.)

• Modifying a Read-Only Cursor

When you attempt to update or delete a row from a table using aread-only cursor, the operation fails.This is expected behavior.Any attempt to fetch additional rows after this operation willalso fail. This occurs because when ct_results() fails, as is the casewhen a delete is requested of a read-only cursor, ct_cancel() shouldbe called. Once a ct_cancel is issued, the cursor is no longer valid(no more rows can be fetched). Because deleting rows using aread-only cursor is impossible, the best workaround is to avoidthis behavior in the first place.



• Passing Parameters to a Cursor Declared with No Parameters

When a cursor is declared with no parameters, but one or moreparameter values is supplied when the cursor is opened, theadditional values are ignored and the cursor still runssuccessfully. The access service ignores this behavior and fails towarn of the mismatch between the number of parametersexpected and the number supplied.

5.2.2. Fetch Count for Cursors

Normally, the select @@rowcount command returns the number ofrows actually returned to the client as a result of the most recentrequest. However, on DB2, when a cursor is open and results arefetched, select @@rowcount returns the number of rows in the fetchcount for that cursor. This may differ from the number of rowsactually returned, depending upon how the cursor is used.

5.2.3. Long Cursor Names

Cursor names longer than 32 characters generate an error, and theconnection to the database is dropped. Cursor names of 32 charactersand less are valid and work fine. This also applies to cursors usedthrough Transaction Router Service.

5.2.4. Cursor deletes using three-part tablename

Attempting to pass a three-part tablename for the name parameter ofct_cursor on a cursor delete function will fail with an error message.

5.3. OmniCONNECT and DB2 Datatypes

5.3.1. DB2 TIMESTAMP Datatype

When creating a DB2 table using OmniCONNECT, do not specify thedatatype timestamp. Doing so creates a column that cannot be writtento. Instead, specify the OmniCONNECT datetime datatype, whichcreates a DB2 TIMESTAMP column on the host. Due to thelimitations of datetime on OmniCONNECT, it is impossible to insertdates earlier than Jan. 01, 1753 into this column.



5.3.2. OmniCONNECT nchar and nvarchar Datatypes

An error is returned when using OmniCONNECT to create an ncharor nvarchar column on DB2. However, if it is necessary to use eitherof these datatypes, do the following:

1. Create the tables manually on DB2 with columns of typeGRAPHIC in place of OmniCONNECT nchar columns, andcolumns of type VARGRAPHIC in place of OmniCONNECTnvarchar columns.

2. Use OmniCONNECT with the nchar and nvarchar columns in thecorresponding locations to create existing table on OmniCONNECTto correspond to the DB2 table.

5.3.3. OmniCONNECT Numeric Datatype Translation

If you attempt to insert data into a NUMERIC field usingOmniCONNECT Release 10.5, and the backend database is theTransaction Router Service, the insert fails with an invalid OpenServer datatype error. As a workaround, create the table onOmniCONNECT using a DECIMAL (18,0) value instead of aNUMERIC value.

5.4. Transfer

5.4.1. Bulk copy transfer from a source DECIMAL to a target DECIMAL

Bulk copy transfer does not transfer data from a source DECIMALcolumn to a target DECIMAL column if the precision and scale of thetarget column is less than that of the source column. This transferfails even if the precision and scale of the value in the source columnis not greater than the precision and scale of the value in the targetcolumn.

5.4.2. Bulk copy transfer of SQL Server DECIMAL types

When an attempt is made to transfer from an SQL Server DECIMALtable where the precision = scale to DB2 tables that do not supportvalues from 0 and 1, or between 0 and -1, then the values aretruncated and a value of “0” is inserted into the target. For example,a bulk copy transfer from SQL server DECIMAL (15,15) to a DB2 intcolumn table will result in a value of “0” being inserted into the intcolumn.



5.4.3. Bulk copy transfer into SQL server bit column

Bulk copy transfer of DECIMAL value “0” into a SQL server willresult in the insertion of the value “1” rather than “0”.

5.4.4. Destination template transfer to DB2 timestamp columns

Destination template transfer using ?T qualifier to DB2 timestampcolumns from DB2 timestamp columns using the sameDirectCONNECT server and service as the primary service, returnsunexpected error messages to the client and fails the transfer

5.4.5. Destination template issue with ?t, ?d or ?T qualifiers

• Destination template transfer TO secondary connection FROMDB2 time, date, or timestamp datatypes using the qualifier ?t, ?d,or ?T respectively, fails. The workaround is to either use theFROM destination template transfer syntax or use bulk transferTO or FROM the secondary connection.

• A second issue involves failures in transferring a TIMESTAMP-formatted string value into a DB2 date or time datatype using the?d, or ?t qualifiers, respectively. One workaround is to use bulkcopy transfer which will handle this situation.

5.5. Configuration Tool

5.5.1. Starting the DirectCONNECT server

For the “Retrieve Log” functionality provided in the ConfigurationTool to work correctly, you must start the DirectCONNECT serverusing one of the following methods:

• start the DirectCONNECT server from the econnect/bin directory,

or

• create a directory named “work”, sibling to the directory wherethe user starts the DirectCONNECT server. For example, if theuser starts DirectCONNECT from the /software/sybasedirectory, then the user will need to create a /software/workdirectory. This “work” directory should have a minimumpermission set to 755.



If neither of these methods are used to start the DirectCONNECTserver, then the “Retrieve Log” function within the ConfigurationTool will always return an empty log file.

5.6. Stored Procedures

5.6.1. sp_password

sp_password is not supported when TCP/IP is used to connect to themainframe. There is no workaround for this issue.

5.6.2. sp_fkeys procedure and wildcards

The sp_fkeys catalog stored procedure currently allows a wildcard(%) to be passed in for the pk_table and fk_table parameters.Wildcards for these parameters should not be accepted and althoughan error message is NOT generated, wildcards within theseparameters will not work properly.

5.7. DB2 Configuration Files

5.7.1. Duplicate Client Interaction sections

If two “Client Interaction” sections are mistakenly placed within thedb2.cfg file, the DirectCONNECT server will start, but no clients willbe able to connect to the DirectCONNECT server.

5.7.2. Incorrect Protocol Specifier when using TCP/IP ConnectionSpecifications

Within a service configuration, setting the connection protocol toLU62 while having connection specifications set for TCP/IP causesthe server to hang when any client connections are made to thatservice.


Setting Up Related Products DirectCONNECT for DB2/MVS Release 10.5

5.8. Utility Program

5.8.1. Snrfchk utility program

The -? argument to the snrfchk utility program does not work asdescribed in the snrfck help screen. There are 2 workarounds: typesnrfck and hit enter, or type snrfck -h.

6. Setting Up Related Products

This section provides instructions for setting up SQL Server,OmniCONNECT, and Replication Server to use with aDirectCONNECT service.

6.1. SQL Server

To set up SQL Server for remote procedure calls (RPCs) against theDirectCONNECT service, perform the following steps:

1. Create a SQL Server user ID and password that matches aDirectCONNECT service host user ID and password.

For instructions on creating the ID and password, see your SQLServer documentation.

2. Configure SQL Server for remote access.

3. Define each DirectCONNECT service as a remote server.

4. Define connectivity between SQL Server and theDirectCONNECT service:

- For a Sybase SQL Server, use sqledit to add the Net-Library™connection and the DirectCONNECT service connectioninformation to the sql.ini file. For a Sybase SQL server runningon AIX, add entries to the interfaces file.

- For a Microsoft SQL Server, use the Microsoft ClientInstallation utility to add the Net-Library connection andDirectCONNECT service information to the Windows NTRegistry.


DirectCONNECT for DB2/MVS Release 10.5 Setting Up Related Products

6.1.1. Configure SQL Server for Remote Access

To configure SQL Server for remote access, log in to SQL Server as anadministrator and check the current sp_configure setting using thefollowing command:

sp_configure 'remote access'

• If the returned value is 1, SQL Server is configured for remoteaccess.

• If the returned value is 0, perform the following steps:

1. Enter:sp_configure 'remote access',1

2. Restart SQL Server.

6.1.2. Define the DirectCONNECT Service as a Remote Server

To define the DirectCONNECT service as a remote server, enter eachDirectCONNECT service name in the SQL Server SYSSERVERStable using the following command:

sp_addserver service_name

where service_name is the name of the DirectCONNECT service youwant to set up as a remote server. The name is case-sensitive andmust match the name you used to define the connectivity betweenSQL Server and the DirectCONNECT service.

To verify that the DirectCONNECT service is successfully defined asa remote server, enter:

select service_name from sysservers

If data rows return, you successfully defined the DirectCONNECTservice as a remote server.

When SQL Server issues an RPC to a DirectCONNECT AccessService, it attempts to connect using a service name identical to theSQL Server identifier in the sql.ini file. To support SQL Server RPCevents, perform either of the following procedures:

• Define a service within the access service library using the samename as SQL Server,or

• Set up service name redirection to redirect the SQL Server to theappropriate service.



6.2. OmniCONNECT 10.5

You can configure OmniCONNECT to access data on a remote serversuch as a DirectCONNECT service by performing the followingsteps:

➤ NoteContact Sybase ICD Technical Support to be sure you are running the

latest OmniCONNECT emergency bug fix (EBF) versions for your platform.

1. Configure the DirectCONNECT Access ServiceSQLTransformation property for sybase mode.

2. Add the DirectCONNECT service.

- Use the omnicfg utility to add the DirectCONNECT service tothe interfaces file.

- Use the sp_addserver system procedure to add the name, serverclass, and DirectCONNECT service network name toOmniCONNECT system tables. Define the DirectCONNECTservice to OmniCONNECT as server class “access_server”.

3. Verify OmniCONNECT connectivity using the OmniCONNECTextension to Transaction-SQL connect to server_name. Thiscommand establishes a Passthrough mode connection to theDirectCONNECT service. The Passthrough mode remains ineffect until you issue a disconnect command.

4. Enable location transparency of remote data through remoteobject mapping.

- Use sp_addobjectdef to define the storage locations of remoteobjects.

- Use either create table or create existing table (as applicable) to mapremote table schema to OmniCONNECT.

5. Perform joins across the DirectCONNECT service.

- Use sp_addserver stored procedure to define eachDirectCONNECT service.

- Use sp_addobjectdef to define each remote object.

- Use create existing table to map the remote tables toOmniCONNECT.

- Use select to perform the join.



For more information about the process, plus detailed instructionsfor configuring and tuning OmniCONNECT, see theOmniCONNECT User’s Guide.

6.2.1. Using OmniCONNECT with the SQL Server Transaction Model

OmniCONNECT 10.5 requires a DirectCONNECT service tosupport particular aspects of the SQL Server transaction model. If theDirectCONNECT service is configured correctly forOmniCONNECT, and if it recognizes the OmniCONNECT clientapplication, it supports the transaction model. The model includesthe following statements:

• begin tran

• prepare tran

• commit or rollback

➤ NoteThis is a limited implementation of the SQL Server transaction model and is

available only for OmniCONNECT 10.5. Other applications cannot use

these features.

To process OmniCONNECT transactions, you must set thetransaction mode and transform level parameters. For instructions,see the OmniCONNECT User’s Guide.

If all conditions are met, the transaction statements are handled asfollows:

begin tran statement

The DirectCONNECT service does the following:

• Sets a flag so that it knows it is in an OmniCONNECTtransaction.

• Sets the transaction mode to long.

• Returns a successful status, just as if a set command wereexecuted.

Other considerations are as follows:

• Nested transactions are not required, nor are such transactionssupported.

• OmniCONNECT does not issue this statement if outstandingchanges were not committed or rolled back.



• The DirectCONNECT service issues a commit prior to handlingthe statement.

prepare tran statement

If the DirectCONNECT service is in an OmniCONNECT transaction,it does the following:

• Ignores this statement.

• Returns a successful status, just as if a set command wereexecuted.

This statement is issued in preparation for a commit statement.

commit or rollback statement

If the DirectCONNECT service is in an OmniCONNECT transaction,it performs the following:

• Resets the flag that indicates it is in an OmniCONNECTtransaction.

• Resets the mode to short.

• Returns a success or failure status of the commit or rollbackstatement to OmniCONNECT

OmniCONNECT expects the DirectCONNECT service to be in shorttransaction mode unless:

• OmniCONNECT opened one or more read-only cursors.

• OmniCONNECT issued a begin tran but did not issue a commit orrollback.

Because the DirectCONNECT service automatically switches to longtransaction mode when a cursor is declared or when a dynamicevent prepare occurs, it backs out of this mode when the last cursorand prepared statement are deallocated and not in a begin tran block.

➤ NoteOmniCONNECT always issues dynamic events within its own transaction,

so it is not necessary to consider backing out when the last dynamic

statement is freed.

In the event of a back-out, the DirectCONNECT service issues acommit and sets the transaction mode to short.



6.3. Replication Server

The following example is a recommended procedure for creating aconnection from DB2 to Replication Server using a DirectCONNECTfor DB2/MVS access service.

create function string class db2_function_class

create function string rs_begin fordb2_function_classoutput language ‘set current sqlid = USER’

create function string rs_commit fordb2_function_classoutput language ‘delete from LTMLASTCOMMIT whereorigin = ?rs_origin!sys?;

insert into LTMLASTCOMMIT values (?rs_origin!sys?,x?rs_origin_qid!sys?, x?rs_secondary_qid!sys?);commit’

create function string rs_rollack fordb2_function_classoutput language ‘rollback’

create function string rs_usedb fordb2_function_classoutput language ‘set current sqlid = USER’

create function string rs_get_lastcommit fordb2_function_classoutput language ‘select origin, origin_qid,secondary_qid from LTMLASTCOMMIT’

create function string rs_get_sortorder fordb2_function_classoutput language ‘select “binary” fromsysibm.sysdatabase where name in (select min(name)from sysibm.sysdatabase)’

create function string rs_get_charset fordb2_function_classoutput language ‘select “iso_1” fromsysibm.sysdatabase where name in (select min(name)from sysibm.sysdatabase)’

create function string rs_marker fordb2_function_classoutput language “

create error class db2_error_class



create connection to db2omni.dwmdbas6set error class db2_error_classset function string class db2_function_classset username dwmq11set password kyle05 with dsi_suspendedconfigure connection to db2omni.dwmdbas6set dsi_cmd_separator to ‘;’configure connection to db2omni.dwmdbas6set dsi_sql_data_style to ‘db2’

release bulletin directconnect for db2/mvs release 10.5 for

Documents

ibm riscsystem 6000 aix

exec sgw addrpc syrt

sgw addrpc local procedure

bulk copy transfer

snrfchk utility program

mdi database gateway

configure sql server

set command wereexecuted