Doc ID: DC75005-01-1260-01
1. Accessing current release bulletin information
A more recent version of this release bulletin may be available on the Web. To check for critical product or document information added after the release of the product CD, use the Sybase® Technical Library Product Manuals Web site.
Accessing release bulletins at the Technical Library Product Manuals Web site
2. Product summary
Enclosed is the Mainframe Connect Client Option for IMS and MVS 12.6, which is a programming environment that enables you to develop mainframe client applications that access LAN (UNIX and Windows) applications and data.
The Client Option for IMS and MVS runs on an IBM z/Series or plug-compatible mainframe computer. It uses the TCP/IP communications protocol and an IMS TM or native MVS host transaction processor.
2.1 Product name changes
The following table describes new names for products in the 12.6 release of the Mainframe Connect IPS.
The new product names are used throughout this document.
2.2 Hardware and software requirements
For planning, installation, and configuration information, see the Mainframe Connect Client Option for IMS and MVS Installation and Administration Guide.
2.3 Product media
The following table lists the Client Option for IMS and MVS 12.6 distribution media.
For directory and file information, see the CONTENTS member of the JCL data set for your Server Option 12.6 installation.
2.4 Product documentation
The following table lists all documentation for the Client Option for IMS and MVS 12.6. Although not all documents are shipped as paper copy, all documents are available on the Web and on the Technical Library CD or the SyBooks™ CD.
3. Changed functionality in this version
For information on new features and functionality in the Client Option for IMS and MVS 12.6, see Mainframe Connect IPS New Features (DC00182-01-1260-01).
3.1 Compiler upgrade
The Client Option and Server Option are now built with the IBM LE/370 C compiler. These products are now compatible with the IBM Language Environment. The compiler used in the previous release, the IBM V2.1 C compiler, is no longer supported.
3.2 Unicode support
The current version of the Client Option for IMS and MVS contains support for Unicode based on the Unicode support provided by IBM z/OS, including the conversion environment and conversion services. With the conversion environment and services installed and set up, the Client Option can convert character streams from one Coded Character Set Identifier (CCSID) to another. This support is provided in addition to the support for language and character sets offered in previous versions.
For details on Unicode, refer to IBM documentation.
3.2.1 Using the IBM z/OS conversion environment and services
Installing Unicode support
Use the following procedure to establish the necessary IBM z/OS conversion environment.
To enable Client Option Unicode support, set the USEIBMUNICODE configuration parameter to Y. The USEIBMUNICODE is specified in the SYGWMCST macro in the SYGWXCPH customization module. The Client Option uses the newly defined unichar, univarchar, and unitext internal datatypes and performs conversions between UTF-8, UTF-16, and other CCSIDs.
For information on installing Unicode support for IBM z/OS, see “Support for Unicode Using Conversion Services” (SA22-7649-01).
3.2.2 SYGWXCPH customization module changes
The character set translation routines in the Client Option use tables in the SYGWXCPH customization module for the conversion of character sets. IBM Unicode support requires the CCSIDs of the character sets involved in conversion, so the translation tables in the SYGWXCPH customization module and the SYGWMCXL macro have been modified to contain CCSIDs.
The USEIBMUNICODE parameter has been added to the SYGWMCST customization macro. The following are valid values for the USEIBMUNICODE parameter:
The SYGWMCXL macro has been modified to include the following parameters, which are used for character conversion:
3.2.3 New datatypes for Unicode support
Components of the Mainframe Connect IPS have two new datatypes using the UTF-16 encoding of the Unicode character. The new unichar and univarchar datatypes are independent of the existing char and varchar datatypes but behave similarly. Like the char datatype, unichar is a fixed-width, non-nullable datatype. Like the varchar datatype, univarchar is a variable-width, nullable datatype. Each unichar or univarchar character requires 2 bytes of storage, so a unichar or univarchar column consists of 16-bit Unicode values.
Components of the Mainframe Connect IPS also have a unitext datatype defined, but there is no special support for it.
3.2.4 Unicode support in the Client Option for IMS and MVS
The unichar, univarchar, and unitext datatypes have been added for Unicode support in the Client Option. These three datatypes are mapped to TDS_LONGBINARY with a user type of 34, 35, or 36, as shown in Table 3.
The Client Option has the following three datatypes to support unichar, univarchar, and unitext:
Currently, there is no special support for CS_UNITEXT_TYPE.
COBOL API names are used here to illustrate use. The C API names are different but behave the same as those for COBOL.
The CHARSETCNV property of the CTBCONPROPS API call is used to change the default character set sent to the server at login. The CHARSETCNV is a login property and must be specified before a connection is established for its value to be effective. If the value of the CHARSETCNV property is not specified before the CTBCONNECT API call, the connection is established with the default communication character set, iso_1.
The following properties are new for the CTBCONPROPS API call:
CTBCONPROPS may specify values for these properties any time after a connection has been established. The default values for these properties depend on the character set established for the connection at login.
For a connection established with the UTF-8 character set, the default values for the CS_CLIENT_CCSID, CS_SERVER_CCSID, CS_PROG_CCSID, and CS_DATA_CCSID parameters are 1208, 1208, 500, and 500, respectively.
The following COBOL example changes the login character set from the default iso_1 to UTF-8:
Thereafter, the Client Option automatically converts all character datatypes to and from UTF-8, unless otherwise specified.
The following COBOL example illustrates how the value of CS_PROG_CCSID can be changed from 500 to 1208:
Thereafter, all program data is presented to the application in UTF-8 as it is received by the Client Option.
The Client Option does not reset any CCSID property values set by an application program. Once an application changes a CCSID property value, the setting remains for all API calls until it is reset by the application.
The CTBDESCR API call now returns CS_UNICHAR_TYPE, CS_UNIVARCHAR_TYPE, and CS_UNITEXT_TYPE instead of CS_LONGBINARY_TYPE when the user type is 34, 35, or 36, respectively.
The CTBBIND API call allows the implicit conversion between the CS_UNICHAR, CS_UNIVARCHAR, and CS_UNITEXT datatypes and the CS_CHAR, CS_VARCHAR, and CS_TEXT datatypes. The CCSIDs used in this conversion are 1200 (UTF-16) and CS_PROG_CCSID (the CCSID used by the client application).
The CTBFETCH API call automatically converts incoming CS_UNICHAR, CS_UNIVARCHAR, and CS_UNITEXT data to the datatype specified by CTBBIND.
3.3 Updated sample programs
Sample programs, source code, and JCL compile and link modules provided with the Client Option and Server Option for IMS and MVS have been changed to accommodate compiler changes. Sybase provides these updated SOURCE and JCL libraries.
4. Known issues
The following section describes known issues in the Client Option for IMS and MVS 12.6.
4.1 InstallShield license-key strings
License keys containing sequences of multiple consecutive dollar signs ($$$) entered in the InstallShield installation wizard are rendered in the resulting install job, IxLIC, with only one dollar sign instead of a sequence.
For example, a license-key string entered in the InstallShield installation wizard as A$$$B$$C is rendered in the install job as A$B$C.
To correct your license key, edit the license string in the IxLIC install job after you have run the InstallShield installation wizard.
4.2 InstallShield wizard temporary space requirement
The InstallShield wizard, which runs only on Windows, requires a maximum of 800KB of free disk space for temporary files.
5. Product compatibilities
For full functionality with the current release, use these Sybase components, as available at your site:
6. Technical support
Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you have any questions about this installation or if you need assistance during the installation process, ask the designated person to contact Sybase Technical Support or the Sybase subsidiary in your area.
7. Other sources of information
7.1 Sybase certifications on the Web
Technical documentation at the Sybase Web site is updated frequently.
Finding the latest information on product certifications
Creating a personalized view of the Sybase Web site (including support pages)
Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.
7.2 Sybase EBFs and software maintenance
Finding the latest information on EBFs and software maintenance