Switch to standard view 
  Sybase logo
 
 
 



DocID: 36382-01-0401-01

Topic

Page

1. Accessing current release bulletin information

2. Component summary

4. Special installation instructions

4.1 Installing Adobe Acrobat Reader 5.0

4.2 Inserting the Key Code

5. Changed functionality in this version

5.1 ECRTP map cache

5.2 The ODBC connection cache

5.3 Using ECRTP in threads

5.4 Redesign of MQSeries-related commands

5.5 RemoveMessage and RestoreMessage commands

5.6 RunThread command

5.7 Additional information on EC Gateway MQSeries-related commands

5.8 Other functions

6. Fixed CRs in 4.0.1

6.1 ECRTP CRs

6.2 EC Gateway CRs

7. Fixed CRs in 4.0

7.1 ECRTP CRs

7.2 ECMap CRs

7.3 EC Gateway CRs

8. Known problems

8.1 Component/Module

9. Documentation updates and clarifications

9.1 PutMessage parameter definitions

9.2 SYS_SECU and PWD_GEN

10. Technical support

11. Other sources of information

1. Accessing current release bulletin information

A more recent version of this release bulletin may be available on the World Wide 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

  1. Go to Product Manuals.

  2. Follow the links to the appropriate New Era of Networks product.

  3. Select the “Release Bulletin” collection for the product version you are interested in.

  4. You can either download the PDF version or browse the document online.


2. Component summary

For details on system requirements and platform information, see the installation guide for your platform.

This release bulletin provides the latest information and known software problems or documentation updates and clarifications.

3. Creation of the EDI and HIPAA newsgroup

An EDI and HIPAA newsgroup has been created. It is called sybase.private.EDIandHIPPA, and can be accessed via a newsreader. This newsgroup should be used as a forum for dialog with other EDI and HIPAA customers, and to discuss and prioritize enhancements that you would like to see in future EDI and HIPAA products.

We cannot guarantee all enhancement requests will be addressed, but we do appreciate your valuable input into our product development process. Remember that all product related issues still need to be reported through support so that engineering can address them in a timely manner.

Product releases and product update notices will be announced to this newsgroup. If you would like to receive email notification for new releases and fixes, you can also join the Sybase Developer Network (SDN) by setting up a MySybase account. This can be done via the Sybase Web site, where it is the first option in the options list on the left.

The newsgroup is open to all EDI and HIPAA customers. There is no limitation to the number of participants from an organization on the newsgroup. The logon is EDI, and the password is EDIProducts. For information on how to set up a newsreader, see Configuring your Newsreader for the Sybase News Service.

This newsgroup service is being offered outside of the normal Sybase maintenance agreements, in response to requests by a number of customers. We hope it will benefit the entire community of customers. The newsgroup will initially be offered on a trial basis, but will be offered permanently based on usage and value.

4. Special installation instructions

This section provides information for installation that is not included in the installation guide.

4.1 Installing Adobe Acrobat Reader 5.0

The documentation is supplied in pdf files. To view the documentation, you must install Adobe Acrobat Reader, version 5.0. You must upgrade to this version if you currently have Reader 4.0.

Installing on Windows

  1. Double-click the ar50eng.exe file.


Installing on AIX, HP-UX, or Solaris

  1. Follow the instructions in the INSTGUID.TXT file.


4.2 Inserting the Key Code

The New Era of Networks EDI Server is a product bundle containing the following components:

The key code is on the hard copy format of this Release Bulletin.

The key code for each component is listed below:

5. Changed functionality in this version

See the Feature Guide for descriptions of new and changed functionality.

5.1 ECRTP map cache

The map cache provides an in-memory cache of maps. For all maps in the cache, the RTP loads the map from memory instead of from disk, which is considerably faster. The scope of the map cache is a single process. All threads running ECRTP within that single process share the same map cache. Only the first parameter that specifies the maximum number of maps in the cache has an effect. Subsequent calls specifying a different maximum number of maps are ignored.

The map cache benefits interactive EDI processing primarily because certain batch processing scenarios also benefit. Batch files generally contain thousands of transactions, while interactive files contain one or a few transactions. To process either type of file, there is a start-up time, a map processing time, and a shutdown time, regardless of the number of transactions. For a batch file, the start-up time, the map loading time, and the shutdown time happen only once during an ECRTP run. For example, if a batch file has 1,000 transactions, the overhead time is spread across all 1,000 transactions. The total time per transaction is the processing time per transaction plus the overhead time divided by 1000. The overhead time per transaction is relatively insignificant.

However, with an interactive file with one transaction, for example, the total time per transaction is the processing time per transaction plus the overhead time divided by 1. In this case, the overhead time is spread over one transaction only. It is therefore more significant.

For batch scenarios that involve a lot of automatic map switching, the map cache is also a significant benefit.

With the RunMapIn command and the RunMapOut command, users can specify the maximum number of maps in the cache. The scope of these parameters is one process only. The parent thread and all child threads share the same map cache because they all coexist in one process. When the map cache parameter is set in a process, that number remains unchanged for the remainder of the process, regardless of whether other calls to ECRTP specify different parameter values.

5.2 The ODBC connection cache

The ODBC connection cache provides an in-memory pool of ODBC connections. When ECRTP needs another ODBC connection, it can often get it from the cache instead of opening a new one.

The scope of the ODBC connection cache is a single process. All threads running ECRTP within that single process share the same connection cache. Only the first parameter that specifies the maximum number of maps in the cache has an effect. Subsequent calls specifying a different maximum number of ODBC connections are ignored.

5.3 Using ECRTP in threads

One architecture for supporting real time processing of EDI transactions is running ECRTP in separate threads for each message received. ECRTP, because it is threadsafe, can be run in this way. Two new features, the map cache and the ODBC connection cache, are intended primarily to benefit multi-threading by reducing the time required for each call to ECRTP in the separate threads. EC Gateway supports this multithreading model via the new RunThread command. Alternatively, users can write their own programs to spawn threads and call ECRTP by using the same API that EC Gateway uses to call ECRTP.

Using this model, you may run into system limits on certain resources including the maximum number of open files per process and the maximum number of database connections across all users of the database. Users can address these problems by increasing these parameters or by limiting the maximum number of threads to be run simultaneously. EC Gateway provides an input parameter to set the maximum number of simultaneous open threads.

In particular, you may see the following:

5.4 Redesign of MQSeries-related commands

EC Gateway’s interface with MQSeries has been redesigned. Two commands, GetMessagePutReply and PutMessageGetReply, have been dropped. Two other commands, GetMessage and PutMessage, have been changed to not only provide the functions available in EDI 2.9, but also to provide the functions of the dropped commands. Customers with scripts from 2.9 that use MQSeries-related commands must rewrite those scripts to run on EDI 4.0.

5.5 RemoveMessage and RestoreMessage commands

The GetMessage command does not actually remove a message from the queue. Instead, the message is marked by MQSeries as having been read. The user has control over the actual deletion of the message from the queue via the RemoveMessage and RestoreMessage commands in their script. This feature is designed to improve the robustness of message processing.

To actually remove a message from the queue, use the RemoveMessage command. To change a message that has already been marked as read to one that is marked as unread, and subject to being read again, use the RestoreMessage command. If the script does not explicitly execute one of these two commands, then the message is removed when the script terminates.

5.6 RunThread command

The scope of the RunThread command is a single process. When an EC Gateway listener script gets a message and initiates a child thread to run EC Gateway, which in turn calls ECRTP, these are all part of the same process. This is because an ECRTP DLL is called instead of an ECRTP executable, which is a separate process.

Additionally, the EC Gateway parameter that specifies the maximum number of threads to run affects only that one process. If different values are used to specify the maximum number of threads in one process, the first value is used and subsequent values are ignored.

5.7 Additional information on EC Gateway MQSeries-related commands

Topic

Description

MQSeries Administration

All MQSeries administration such as creating, modifying, and deleting queue managers, queues and their characteristics must be done using MQSeries Administration Tools. EC Gateway definitions only reference and use existing MQSeries objects.

Handling Multiple Queues and Queue Managers (continued)

Example 2 - Using Two Q’s on Two QM’s on the Same System (specifically using QA1 on QMA and QB1 on QMB)

First Method:

Create a ‘Remote Q’ definition in MQSeries for QB1 on QMA which serves as an alias for QB1 on QMB (the real Q). Also required in MQSeries are ‘transmission Q’s’, ‘Channels’ and ‘Listeners’ between the two QM’s.

  1. Define two channels in EC Gateway:

    • QMA + QA1; and

    • QMA + QB1

  2. Reference either channel in your script. Note however MQSeries supports MQPUT’s to local or remote Q’s while MQGET’s are supported from local Q’s only. In particular the script can do a PutMessage to QMA + QB1 but cannot do a GetMessage from QMA + QB1. Of course one could have defined both queues based on QMB:

    • QMB + QB1; and

    • QMB + QA1

Second Method:

  1. Define two channels in EC Gateway:

    • QMA + QA1; and

    • QMB + QB1

  2. Reference either channel in your script. EC Gateway will automatically disconnect from one QM and connect to the other QM as necessary because MQSeries supports connections to only one QM at a time. Note this method will take more time than the first method because MQSeries connects and disconnects are time consuming relative to addressing a remote Q.

Example 3 - Using Two Q’s Attached to Two QM’s on Two Different Systems (specifically using QA1 on QMA and QC1 on QMC and EC Gateway running on System A)

  1. a) Define two channels on EC Gateway on System A.

    • QMA + QA1

    • QMA + QC1

    Create a ‘Remote Q’ definition in MQSeries for QC1 on QMA which serves as an alias for QC1 on QMC. Also required in MQSeries are ‘transmission Q’s’, and ‘Channels’ and ‘Listeners’ between the two QM’s.

  2. Reference either channel in your script. As above, due to MQSeries not supporting GET’s from remote Q’s, an EC Gateway script on System A can do a PutMessage to QMA + QC1 but not a GetMessage from QMA + QC1.

In this case, the second method given above for Example 2 will not work because MQSeries does not support connections to QM’s on other systems.

Message Type Parameter

Two of the MQSeries related commands in EC Gateway, GetMessage and PutMessage, contain a parameter field fields called Message Type, documented as user-definable fields. This field should be left blank unless these commands interact with the New Era of Networks Rules and Formatter found in MQSI, e-Biz Integrator, and e-Biz 2000. In that case the Message Type field contains the name of the relevant ‘format’ or ‘schema’ defining the message.

Further, if you want to propagate the schema name between incoming and outgoing messages, you need to explicitly transfer the value by using parameter variables in the EC Gateway script.

5.8 Other functions

Topic

Page

Using DB2

When using DB2, the default page size for the default table space needs to be increased from 4k to 8k, before creating the system tables required by EC Gateway.

Also, the system environment variable, auto_inc_fix, needs to be set in order for auto-increment fields to work:

auto_inc_fix = NOT NULL GENERATED ALWAYS AS IDENTITY

6. Fixed CRs in 4.0.1

6.1 ECRTP CRs

6.2 EC Gateway CRs

7. Fixed CRs in 4.0

7.1 ECRTP CRs

7.2 ECMap CRs

7.3 EC Gateway CRs

8. Known problems

The following sections describe known problems and workarounds.

8.1 Component/Module

This section discusses known problems with EC Gateway.

8.1.1 RunMap

Problem: ‘Error message: Operation is not supported for this type of object.’

Workaround: Download and install the updated version of Microsoft Jet 4.0 Service Pack 5 (SP5) for Windows 2000. The download is available at the Windows Download Center.

8.1.2 Microsoft Access

Problem: Microsoft Access is listed as a supported database in the Installation Guide.

Workaround: Sybase does not recommend using Microsoft’s Access database in a production environment. Customers using our EDI products in complex operating environments have experienced lockup problems due to simultaneous access and corruption and maximum size problems when the database is large. Instead of Microsoft Access, use the other databases listed in the Installation Guide.

9. Documentation updates and clarifications

9.1 PutMessage parameter definitions

These parameter definitions were omitted from the PutMessage documentation in Table 3-3, “Parameters and values for the PutMessage command,” Chapter 3, “Enhancements to EC Gateway,” in the New Feature Guide for EDI Products version 4.0:

9.2 SYS_SECU and PWD_GEN

The following two tables should have been included in the New Functionality Guide.

Table 1: SYS_SECU

Field

Type

Length

Description

GW_VERSION

Text

50

Gateway version number

ONE_USERID

Text

1

Unique user ID

ONE_LOGIN

Text

1

Unique login

ONE_ALPHA

Text

1

At least one alpha character

ONE_DIGIT

Text

1

At least one numeric character

PWD_MINLEN

Number

Integer

Minimum length of password

BAD_ATTEMP

Number

Integer

Bad attempt of logins

PWD_EXPIRE

Number

Integer

Number of days in which password will expire

PWD_GEN

Number

Integer

Password history

Table 2: PWD_GEN

Field

Type

Length

Description

USER_ID

Text

50

User ID

USER_TYPE

Text

50

User type

PWD_GEN

Number

Integer

Password generation

USER_PWD

Text

50

Password

10. Technical support

If you have a Technical Support contract and are located in the United States or Canada, call 1.800.8SYBASE.

Outside North America, contact your local Sybase office.

For a listing of local support center numbers, refer to online resources from the Sybase Support Web site

For more information on Support Services, education, and consulting services, refer to the Customer Services Reference Guide.

11. Other sources of information

Use the documentation that is provided with this product and the Technical Library Product Manuals Web site to learn more about your product, access the Sybase Product Manuals Web site.



Back to Top
© Copyright 2010, Sybase Inc.