Sterling Connect:Direct for VM 3.2.00 Release Notes

Content

Sterling Connect:Direct for VM Version 3.2.00 allows for file migration of previous versions of Sterling Connect:Direct for VM. The Sterling Connect:Direct for VM product runs with the IBM Virtual Machine (VM) Operating System.
The Sterling Connect:Direct for VM Release Notes document is updated with each release of the product. Read the document in its entirety before installation.

Important Notes

The following notes are intended to clarify or supplement Sterling Connect:Direct for VM documentation.

Product Requirements

Sterling Connect:Direct for VM requires the following hardware and software.

• Authorized GCS User

Sterling Connect:Direct for VM must execute from a VM userid which is entered into the GCS GROUP file as an authorized user prior to generation of the GCS machine.

• DASD

Adequate space must be available for holding all Sterling Connect:Direct distribution libraries. Required direct access storage devices (DASD) are a CMS minidisk for holding Sterling Connect:Direct distribution libraries and a DOS-formatted disk for VSAM files.

Refer to Planning the DASD Requirements chapter of the Sterling Connect:Direct for VM Installation Guide for an explanation of DASD space requirements and calculations.

• HLASM

Use High-Level Assembler to assemble the sample Sterling Connect:Direct exits. The ASSEMBLE file type contains the following sample exits:

• Security Exit
• Run Task Exit
• Statistics Exit
• Submit Exit
• Allocation Exit
• Tape Drive or Cartridge Unit

The distribution tape is either a 3480 cartridge tape or a nine track, 1600-bpi reel tape. Therefore, use a cartridge unit or a 1600-bpi tape drive for unloading Sterling Connect:Direct distribution libraries.

• VMFPLC2

VMFPLC2 loads previously dumped files from tape to disk and performs various control operations on a specified tape drive. This utility is distributed with VM.

• VM Operating System

For full functionality, Sterling Connect:Direct for VM supports all currently supported releases of z/VM.

• VSAM

VSE/Virtual Storage Access Method (VSAM) 5686037 Version 2.1 or later

• SNA Network Requirements

Network support requires the following:

• VTAM for VM 5684095 Version 3.4.1 at PUT 9305 or later, or VTAM for VM/SP 5664280 Version 3.4.1 at PUT 9401 or later
• IBM Advanced Communications Function for Network Control Program (NCP) Version 4.3 or later
• ISPF Interface Requirement (Optional)

IBM's ISPF Dialog Manager must be installed to use the ISPF IUI interface

• GCS, VTAM, and VSAM

Sterling Connect:Direct for VM requires simultaneous use of segments GCS, VTAM, and VSAM. Review the storage allocation for these segments and ensure that no overlap occurs among them.

• One Group Control System (GCS) machine
• One optional Conversational Monitor Services (CMS) machine for each Sterling Connect:Direct for VM user
• TCP/IP Configuration (Optional)

Sterling Connect:Direct for VM requires IBM TCP/IP Level 540 or above.

Year 2000 Compliance
Sterling Connect:Direct for VM 3.2.00 is Year 2000 compliant. To meet Year 2000 compliance, the Connect product implements special considerations, such as:

• End-of-year transition (12/31/99 through 01/02/00)
• Leap year transition (02/28/00 through 03/02/00)
• Display/Report presentation (4-digit or a century designation)

For existing Processes and reports that have a 2-digit year format, Sterling Connect:Direct for VM 3.2.00 interprets the date as 20th century if the value is 80 or greater or 21st century if the value is less than 80.

The Year 2000 compliance of Sterling Connect:Direct for VM 3.2.00 is only valid if you are using this product with hardware and software that are also Year 2000 compliant.

Testing

The following tests ensure that all product features will run successfully before, during, and after the turn of the century:

• Connectivity validation ensures that the products function correctly in the connectivity options available.
• Function validation tests the functions supported by each product.
• Volume testing places each product under production simulations to measure throughput and execution.
• Error recovery testing validates the error recovery and logging aspects as typical network errors are randomly introduced into the tests.
• Sample and example testing examines the accuracy of Process and program examples delivered with each product.

Date Processing

The date processing for year 2000 compliance makes special considerations for Gregorian dates, date format, century designation, and displays and reports. The only change in Julian date processing is the provision for 4-digit years.

Order Designation for Gregorian Dates

Sterling Connect:Direct for VM allows you to select the format for your Gregorian dates. The DATEFORM initialization parameter provides the option of entering and presenting your Gregorian dates in any one of the following orders:

• MDY for month, day, and year order
• DMY for day, month, and year order
• YMD for year, month, and day order
• YDM for year, day, and month order

If you do not specify the DATEFORM parameter, Sterling Connect:Direct for VM defaults to the MDY format for Gregorian dates.

Formats Available

The following table presents the valid formats for each order format listed previously. You specify these formats in the STARTT and STOPT parameters of the PROCESS and SUBMIT statements.

Julian Date Processing

Sterling Connect:Direct processes Julian dates the same as previous releases. The following formats are valid:

• yyddd or yyyyddd
• yy/ddd or yyyy/ddd
• yy.ddd or yyyy.ddd

The only change in Julian date processing is the change for 4-digit years.

Distribution Media

The Sterling Connect:Direct for VM package consists of the distribution media, a product key, and product publications.

Distribution media for Sterling Connect:Direct for VM is either a 1600 bpi magnetic tape or a 3480 cartridge tape. It is identified with an external label showing the product name and release level.

Installation Notes

Refer to the following notes before beginning your installation:

• The module DMGRATX that uniquely identifies your Sterling Connect:Direct system is not included in the upgrade libraries. Refer to the How to Install a Sterling Connect:Direct for VM Upgrade Tape section for complete instructions.
• Review the Sterling Connect:Direct for VM Installation Guide before installing Sterling Connect:Direct.
• Complete the installation worksheets in the Sterling Connect:Direct for VM Installation Guide before you begin your installation.
• Verify your security configuration to ensure compatibility with Sterling Connect:Direct before your installation.
• Review the storage allocation for GCS, VTAM, VSAM, and SFS (Shared File System) to ensure that no overlap occurs among these segments. Sterling Connect:Direct for VM requires simultaneous use of these segments.
• Verify that you have downloaded the current maintenance for Sterling Connect:Direct for VM from the Technical Support Knowledge Bases section of the Sterling Commerce web site before you install. After you install Sterling Connect:Direct for VM, follow the procedures documented in the Instructions for Installing Fixes section of the Sterling Commerce Technical Support Knowledge Bases web site to install the updated maintenance containing the product fixes. (Refer to the Registering for Access to Technical Support Knowledge Bases section for specific instructions about how to access the Technical Support Knowledge Bases section of the Sterling Commerce web site.)

How to Install a Sterling Connect:Direct for VM Upgrade Tape

This section supplements the description of the installation process described in the Sterling Connect:Direct for VM Installation Guide. Refer to both sources for a complete description of the Sterling Connect:Direct for VM installation.

The module DMGRATX that uniquely identifies your Sterling Connect:Direct system is not included in the upgrade libraries. You must copy the DMGRATX from your existing LOADLIB into the CDV3200 LOADLIB during your installation.

After you complete the CDSETUP procedures described in Step 3 Download Tape and Configure VSAM Disk of the Sterling Connect:Direct for VM Installation Guide, use the following command to copy your existing DMGRATX module into the new CDV3200 LOADLIB.

At the first system prompt (ENTER:), type the following command:

At the second system prompt, type the following command:

At the third system prompt, press Enter on your keyboard.

After you have verified the installation of Sterling Connect:Direct, you can archive or delete the previous LOADLIB.

IBM Support

For more information about fixes, log in to the Sterling Legacy Software Request web site at https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=swg-SterlngLegacyreq, select Sterling Connect:Direct for VM Version 3.2.00, and then select the individual files you want to download.

Summary of Updates

Enhancements in Sterling Connect:Direct for VM Version 3.2.00 are described in this section.

Enhancements

The enhancements in Version 3.2.00 are as follows:

Enhanced TCP/IP and LU6.2 Connectivity

This enhancement provides TCP/IP and LU6.2 support for VM, MVS, and OS/400, NT, UNIX, and OS/2 Warp operating systems. NT, UNIX, and OS/2 Warp connectivity was not available with previous versions of Sterling Connect:Direct for VM.

VM Shared File System Support (SFS)

This enhancement creates a new communications method that supports read/write access to Shared File System. SFS does not require a one-to-one correspondence between DTF service machines and file server virtual machines. The activation of SFS support occurs during the DTF initialization process.

Increased Logical Record Length

This enhancement allows customers to transfer files with a logical record length up to 64K.

Improved Statistics Facility

This enhancement includes support for:

• New Statistics File Structure
• Improved SELECT STAtistics Performance
• Archiving for Long-term Storage
• Enhanced Selection Criteria for the SELECT STAtistics Command
• Statistics Log Record Exclusion

Event Services Support

The Sterling Connect:Direct Event Services Support (ESS) implements an asynchronous event generation facility in Sterling Connect:Direct. The ESS is designed for use by external management and automated operations applications that require real-time notification of Sterling Connect:Direct activities. Refer to the Sterling Connect:Direct Event Services Support System Guide for complete information about this enhancement.

Improved I/O Exit Support

This enhancement provides Sterling Connect:Direct users with an interface to user written programs, allowing them to read and write data to and from a file whose organization Sterling Connect:Direct does not support or would improperly access.

Enhanced Memory Management

This enhancement allows Sterling Connect:Direct to improve performance by eliminating the GETMAIN/FREEMAIN for DSECT storage on entry to and exit from each program. Sterling Connect:Direct maintains the memory for DSECT storage in a table unique to each Task Control Area (TCA). By controlling storage at the step level, Sterling Connect:Direct minimizes storage allocation levels and experiences memory management benefits. This feature is transparent to the user.

Double Byte Character Support

Double Byte Character Set (DBCS) support provides a mechanism to translate languages with several thousand characters into coded character sets. DBCS translates Single Byte Character Sets (SBCS) and DBCS data in the form supported on the requested platform. The DBCS support creates a translation table for ASCII and EBCDIC DBCS data.

Synchronized Submit

This enhancement synchronizes batch or interactive applications with the execution of Sterling Connect:Direct Processes.

Variable Extended Compression

Sterling Connect:Direct for VM Version 3.2.00 implements a variable compression routine. This compression routine will be used when extended compression is specified and both sides support the variable compression routine.

Year 2000 Compliance

This enhancement provides support for a 4-digit year and any changes for the new century, including century roll-over certification and leap year processing.

Maintenance Updates

Sterling Connect:Direct for VM addresses some maintenance issues from previous releases of Sterling Connect:Direct for VM. This table lists the maintenance updates from prior versions of Sterling Connect:Direct for VM.

Documentation Updates

The following updates apply to the Sterling Connect:Direct for VM documentation:

Using SYSOPTS for DBCS Examples

The information in this section should be included at the end of the Sterling Connect:Direct for VM COPY Statement chapter of the Sterling Connect:Direct Process Guide.

Notification that a Process is transferring a DBCS file is done by means of the SYSOPTS statement. This statement must be included on the host node definition of the COPY statement.

By requiring the Process to notify Sterling Connect:Direct of its DBCS capability through the SYSOPTS statement, support for multiple transfers with multiple translation tables is possible. Furthermore, all Processes support compression and check pointing.

The following example has a table name of EBCXKSC and the default values x'0E', for so, and x'0F' for si.

The following example has a table name of KSCXEBC and the default values x'0E', for so, and x'0F' for si.

The following example has a table name of EBCXKSC and the NOSO value x'00' for so and si.

The following example has a table name of EBCXKSC and takes the defaults for so and si.

The following example has a table name of USERTAB and takes the defaults for so and si. USERTAB is a user-defined, customized translation table.

Defining a DBCS Capable Process

The information in this section should be included in the Sterling Connect:Direct for VM COPY Statement chapter of the Sterling Connect:Direct Process Guide.

The following PC-to-host DBCS translation uses the supplied translation table KSCXEBC. Required parameters for this translation are in bold.

The previous sample COPY statement copies a data set from a PC to a host Sterling Connect:Direct for VM node; its description follows:

• The copy step is named STEP01.
• The input data set is cataloged after successful completion of the Process.
• The DCB attributes specified in the TO clause of the COPY statement are used for file allocation.
• The SYSOPTS attribute specified in the TO clause of the COPY statement is used to define the supplied translation table KSCXEBC.
• UNIT has been specified on the PNODE only.
• The TYPE parameter on the FROM clause of the COPY statement must be set to ASC2ASC.

The following host-to-PC DBCS translation uses the supplied translation table EBCXKSC. Required parameters for this translation are in bold.

The previous sample COPY statement copies a data set from a host Sterling Connect:Direct for VM to a PC node; its description follows:

• The copy step is named STEP01.
• The SYSOPTS attribute is specified in the FROM clause of the COPY statement is used to define the default translation table EBCXKSC.
• The TYPE parameter on the TO clause of the COPY statement must be set to ASC2ASC.

The following UNIX-to-host DBCS translation uses the default translation table EBCXKSC. Required parameters for this translation are in bold.

The previous sample COPY statement copies a data set from a UNIX to a host Sterling Connect:Direct for VM node; its description follows:

• The copy step is named STEP01.
• The SYSOPTS attribute is specified in the TO clause of the COPY statement is used to define the default translation table EBCXKSC.
• The SYSOPTS parameter on the FROM clause of the COPY statement is required.

The following host-to-UNIX DBCS translation uses the default translation table KSCXEBC. Required parameters for this translation are in bold.

The previous sample COPY statement copies a data set from a host Sterling Connect:Direct for VM to a UNIX node; its description follows:

• The copy step is named STEP02.
• The SYSOPTS attribute specified in the TO clause of the COPY statement is used to define the default translation table KSCXEBC.
• The DCB attributes specified on the TO clause of the COPY statement are used for file allocation.
• Unit is specified on the PNODE.
• The SYSOPTS parameter on the FROM clause of the COPY statement is required.

Interfacing Through the Event Services Exit

You can execute event services commands through any existing Sterling Connect:Direct Application Program Interface (API) such as CICS (MVS and VSE only), ISPF (MVS only), and DMBATCH. However, no Sterling Connect:Direct APIs can process event data received from an EVENT SERVICES START command.

System Architecture

The event services exit acts as an extension to the Sterling Connect:Direct server. Upon encountering an event, Sterling Connect:Direct calls the event services exit. An event exit control block is passed for each event. The control block contains the following information:

• Address of the event record
• Flags indicating first or last call
• Fields for the user to indicate return code and message

DMEVEXCB, found in the sample library, maps the event exit control block. A sample exit, NDMEVX01, is also provided in the sample library. For VM, DMEVEXCB is in CDV3200's MACLIB.

The event services exit is called as a subtask from Sterling Connect:Direct so that user code waiting for system services will not directly effect Sterling Connect:Direct processing. The sample exit (NDMEVX01) writes each event record to a predefined data set. Other than VM, NDMEVX01 must be modified to specify the name of your event exit data set. The data set must be defined to accommodate records up to 2048 bytes in length.

VM requires a Filedef stat using the keyword OUTFILE as in the following example.

Using the ESS Exit

Each record passed to the exit consists of a record header and an event record. DMMNHDR, which is in the Sterling Connect:Direct for MVS sample library, maps the record header. Members in the sample library also map the event records. Use the ESS Reference Material appendix to determine which member maps a particular event record.

The exit must reside in a load library accessible to the Sterling Connect:Direct server (DTF). Sterling Connect:Direct moves event data to storage below the 16M line before calling the event services exit. This step accommodates systems where I/O calls must be done below the 16M line. The VM NDMEVX01 exit must be AMODE/RMODE 24 and NORENT.

Known Restrictions

Sterling Connect:Direct for VM has the following known restriction:

• The COMMAND LINE ACCESS and the ISPF/IUI interface cannot be used when the user's CMS A minidisk is an SFS directory.

Sterling Connect:Direct for VM Documentation

The Sterling Connect:Direct for VM documentation can be downloaded from http://www.ibm.com/support/docview.wss?uid=swg27023721. The Sterling Connect:Direct for VM documentation consists of:

• Sterling Connect:Direct for VM Administration Guide
• Sterling Connect:Direct for VM Installation Guide
• Sterling Connect:Direct for VM User's Guide
• Sterling Connect:Direct Overview
• Sterling Connect:Direct Console Operator's Guide
• Sterling Connect:Direct Event Services Support System Guide
• Sterling Connect:Direct Problem Isolation Guide

Information on Sterling Connect:Direct Processes is available at http://pic.dhe.ibm.com/infocenter/cdproc/v1r0/index.jsp.