Sybase.com

Topic	Page
1. Accessing current release bulletin information
2. Component summary
3. Creation of the EDI and HIPAA newsgroup
4. Special installation instructions
4.1 Installing Adobe Acrobat Reader 5.0
4.2 Insert 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 for 4.0.1
6.1 ECRTP CRs
6.2 EC Gateway CRs
7. Fixed CRs for 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

Go to Product Manuals.

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

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

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:

Double-click the ar50eng.exe file.

Installing on AIX, HP-UX, or Solaris

Follow the instructions in the INSTGUID.TXT file.

4.2 Insert the Key Code

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

ECMap(AV) (unlimited copies)
ECRTP (1production copy)
EC Gateway (1 production copy)
EC Gateway Operations Viewer (unlimited copies)

The key code is on the hard copy format of this release bulletin.

5. Changed functionality in this version

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

EDI products now support Windows XP.
Distinct FTP software has been upgraded to v5.1.

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:

Trace messages from wsproces (if you have TRACE ON) or other messages from the ECRTP may display to the console. The reason for this is that the maximum number of FileDescriptors, that is, the maximum number of files that can be opened, is set too low on your system. Speak to your UNIX system administrator to have this limit increased.
All databases have a maximum number of concurrent connections allowable. If you find that some of your maps are failing and you have TRACE ON, you maysee an error message telling you that the maximum number of connections has been exceeded.

Either ask your DBA to increase the maximum number of concurrent connections, or set the maximum number of concurrent threads to run. Do this by either using the -td switch if you are running your scripts from the command line/scheduler, or, if you are running them through the EC Gateway GUI, you can set this option on the Run Process screen.

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. Define two channels in EC Gateway: QMA + QA1; and QMA + QB1 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: Define two channels in EC Gateway: QMA + QA1; and QMB + QB1 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) 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. 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.

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.

Define two channels in EC Gateway:
- QMA + QA1; and
- QMA + QB1
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:

Define two channels in EC Gateway:
- QMA + QA1; and
- QMB + QB1
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)

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.
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

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 for 4.0.1

6.1 ECRTP CRs

[CR #292571] The EDI engine failed to catch the error in the compliance map when the maximum of number of sub-elements was exceeded.

Resolution: When the maximum number of sub-elements is exceeded, an error is now written to the trace file and to the log during a compliance map run.
[CR #295822] ECRTP was not catching missing mandatory elements in certain scenarios. For instance, if you had the following segment: REF*1*2~, and the 3rd element was mandatory, nothing was reported.

Resolution: ECRTP can now handle the above scenario.
[CR #296257]: Record types were not handled correctly for EBCDIC.

Resolution: Record types (found as an attribute on the field/edit or field/new screens) can now have an ASCII value entered and converted to the EBCIDIC equivalent, if the record is used in an EBCIDIC file.
[CR #296341] Packed decimal value with leading 00 (null value in EBCDIC and ASCII character sets) made EDI engine (RTP) fail since “null” was the terminating character.

Resloution: ECRTP has been updated to decode this value into a normal number.
[CR #297239] The RTP was not catching a missing mandatory NM1 in the 835 compliance map. At the start of a loop repetiton, a segment in the loop with a mandatory conditional was not being reported as missing if the last segment in the loop had a higher ordinal number than the segment with the mandatory conditional segment.

Resolution: Problem corrected.
[CR #299479] When the value in the AMT02 was greater than 14 digits, an application error was generated.

Resolution: This has been corrected.

6.2 EC Gateway CRs

[CR #301588] RunMap command FileAlias tab was not working if you selected the Parameter variables to store the alias.

Resolution: The problem was caused by increasing the number of parameter variables from 20 to 40 and now is fixed.
[CR #301285] When assigning the value of FileSize to one of the ten count variables, a core dump error was produced on the Sun Solaris platform.

Resolution: This problem has been fixed.
[CR #300789] In an Oracle database the transaction log report failed with an error message "error detected by database DLL". Reports other than management reports displayed blank.

Resolution: The problem has been fixed by changing the SQL syntax behind reports.
[CR #295116] Many GoTo commands caused scripts to fail with a memory addressing error.

Resolution: The maximum number of labels has been increased to 800 to allow 800 labels defined in a single script.
[CR #293924] Large amounts of Do Process commands caused memory errors. The limit is 46 Do Process commands.

Resolution: The maximum number of lines in a script file has been increased to 20,008.
[CR #292032] The assign to parameter was appending data instead of replacing it.

Reolution: The problem has been fixed.
[CR #292026] A memory exception displayed when closing the PFS-Async host window on a Windows 2000 server.

Resolution: Install Windows 2000 SP 3.
[CR #291024] Value 150 was invalid for the retry indicator.

Resolution: This problem has been fixed and wsproces no longer rejects the constant retry number.
[CR #291020] Could not run any processes via scheduler on the UNIX Sun platform, version 2.9.

Resolution: User script file has errors.
[CR #289262] The default scheduler resolution time was 1 second, which started process every second regardless of whether or not there was a file. This caused performance issues.

Resolution: User script file has errors.
[CR #287915] Run command did not work with parameters as arguments.

Resolution: The parameter parsing function in wsproces was corrected. Arguments as provided in parameters will now be passed to the program started.
[CR #287544] Need a way to close the windows after setup and run FTP server.

Resolution: A menu item was added to the File menu to close the window and run the FTP server.

7. Fixed CRs for 4.0

7.1 ECRTP CRs

[CR #293871] RTP is not zero-filling right-justified fields in EBCDIC files.

Resolution: Zero-filled fields, to be written into EBCDIC files, now uses the hex value 0x40 (space in EBCDIC character set) instead of 0x20 (space in ASCII character set) to replace leading spaces.
[CR #291615] The RTP is not correctly converting integer input values into unsigned packed decimal values.

Resolution: The problem with handling packed decimal has been fixed.
[CR #291372] Cannot run two ECRTP executables at the same time that use the same DBC3 trade partner tables.

Resolution: The DBC3 tables now use shared mode.
[CR #290713] The FGETC command is running slowly in certain situations when reading the file.

Resolution: The FGETC command has been changed to FREAD; the program now runs approximately four times faster.
[CR #290710] The final time reported at the end of inbound and outbound map left out the time required to write the log records to the database, once ECRTP changed its logic to cache the log records and do a bulk write at the end of the run.

Resolution: Repositioned the final time calculation for the trace output (-tm switch output) to after ODBC logging and freeing of memory completes.
[CR #287921] An enhancement request to use the Run_ID in the select criteria for the 997 maps.

Resolution: The 997 map has been enhanced to accept a Run_ID as an optional input parameter. When this enhanced 997 map is run and the new input parameter is specified, the map selects only records that match the Run_ID criterion in addition to all the other criteria for a 997 message.
[CR #287035] Mapping an alphanumeric to an unsigned integer for EDI with ECRTP 2.9.0.21, sometimes causes incorrect results. For example, mapping the system variable GP FUNC NUM (AN-35) to an XML element (UI-9) does not work, even though it worked in earlier versions of ECRTP.

Resolution: The RTP now removes all leading and trailing spaces and retrieves the actual number from the alphanumeric field. That value can be mapped to an unsigned integer field or other datatype field. If the length of the actual number is still larger than the length of the destination field, the data is truncated and an error message is written to the trace file.
[CR #279369] When the last transaction in a run of an inbound map aborts, information written to files is lost.

Resolution: The RTP has been fixed so that writes that occur outside the transaction are not affected in the above scenario.
[CR #279056] In an inbound map, an element is shown as mapped in the trace file even if no data has been passed in that element. The error causes a problem downstream because a prior assignment to the record field mapped to the element is overwritten.

Resolution: ECRTP no longer maps to an element that is not present in the input EDI file.
[CR #278516] When multiple Gateway scripts are run simultaneously, 997 files contain information from both runs.

Resolution: The 997 map has been enhanced to accept a Run_ID as an optional input parameter. When this enhanced 997 map is run and the new input parameter is specified, the map selects only records that match the Run_ID criterion in addition to all the other criteria for a 997 message.
[CR #276715] When the entire incoming EDI file has not EDI data in it, a BAD file is not being produced by the compliance map.

Resolution: A BAD file is now produced even when an input file contains no EDI data.
[CR #274151] When the -m mapname switch passed to ECRTP to run a map with no trade partner lookups, no EDI OUT GOOD file is produced.

Resolution: TheGOOD file produced will be in the same directory as the BAD file if there is no trading partner database or if the “all” trade partner mailbox is empty. If there is a trade partner database and the “all” trade partner mailbox is not empty, then the EDI OUT file will be placed in the normal routing mailbox subdirectory.
[CR #273578] An inbound map placed the zeros to the left of the sign when the zero-fill option was turned on. For example, “+12345” was converted to “0000+12345”.

Resolution: The code has been modified to handle the leading “+” sign correctly when the zero-fill option is on.
[CR #272984] ECMap rounds numeric data values. This appears to occur only at the maximum data element size.

Resolution: Explicit decimal, implicit decimal, or signed decimal number with over maximum precision is now handled correctly by EDI Server.You can map a large number from one datatype to another datatype without losing precision. Normally, long double datatypes on a PC can handle 19 digits (precision) and on UNIX can handle 16 digits (precision). EDI Server can handle any size by treating these large numbers as normal strings.
[CR #271750] Users cannot create a new ISA/IEA envelope during an outbound map run.

Resolution: A new system variable, NEW_COMPANY_ID, has been added. When this is set, a new interchange is created.
[CR #271433] Users cannot map ISA and GS elements to the output in the master level.

Resolution: Additional system variables have been added to enable this functionality.
[CR #270965] This is a parent QTS ticket for the following CRs: 266682, 266683, 266684, 266724, 267683, 267686, 267689, 268528, 268549, 268550, 268551, 268552 and 269934.

Resolution: New error messages were added relating to those problems.
[CR #270237] A clear record command, used in a map with a write NDO command, is not clearing all information when new EDI data is processed.

Resolution: The record field buffer is now cleared after each NDO building process.
[CR #268553] Customers cannot create and accept TA1s.

Resolution: The capability to create and accept TA1s has been added as a new feature in version 4.0.
[CR #268552] The RTP does not reject a transaction in which the GS05 was missing or misformed.

Resolution: The RTP has been corrected to address the issue.
[CR #268551] The GS07 is not being rejected when an invalid code is used.

Resolution: New edits have been added to the RTP for compliance maps only.
1. The value must be 1 to 2 chars.
2. The first character must be T or X and second character, if any, must be a space. If either of these edits fail, the following error message is written:
```
"(2188) ERROR: Invalid GS Responsible Agency Code"
```
[CR #268550] See CR #268551, a duplicate.
[CR #268549] The GS08 – version/release/industry identifier code – has a length of 1/12. When the code length is invalid, it is rejected with a misleading error message.

Resolution: A new GS08 edit has been added. For compliance maps, the length must be between 6 and 12, and if the first 6 characterss are not numeric, the version is invalid. If not a compliance map, the RTP checks that the field length >= 1 and len <= 12. If any of these edits fail, the following error message is written:
```
"(2189) ERROR: Invalid GS Version Number"
```
[CR #267689] See CR #268552, a duplicate.
[CR #267686] For transformation maps, the RTP is not validating the GS01 element. Also for compliance maps, the RTP is not validating the GS01 and ST01 against each other. For example, an 850 Purchase Order (ST01 = 850) should have a GS01 of PO.

Resolution: Although users can validate the GS01 by comparing it via a system variable where the GS01 value is stored, the generate.exe has been enhanced to add a validation check of the GS01/ST01 in compliance maps. This is the same problem addressed in QTS #267683.
[CR #267646] The -pf switch that passes a file containing run parameters to WRMI32.exe for executing a map does not work correctly.

Resolution: This problem has been fixed.
[CR #266684] The RTP is not correctly rejecting an invalid ISA14.

Resolution: The ISA14 (acknowledgment requested) is mandatory and must have a length of 1. A new edit has been added to the RTP for compliance maps to check that value is 0 or 1. If this check fails, the following error message is written:
```
"(2183) ERROR: Invalid Acknowledgement Requested value"
```
[CR #266683] The RTP is not correctly rejecting an invalid ISA12. The ISA11 is mandatory and must have a length of 1. The ISA12 is also mandatory and must have a length of 5. Depending on the value in the ISA12, the ISA11 may have different valid values. Additionally, the ISA11 and ISA12 can have different valid values depending upon the version of X12 being used.

Resolution: For compliance maps, new edit checks have been added to RTP to validate the ISA11 and ISA12. The edits on the ISA11 are performed when the ISA12 is read. The new checks include:
- ISA12 length is exactly 5 and is completely numeric. If this check fails, this message is written:
```
"(2180) ERROR: Invalid Interchange Control Version Number"
```
- If the value of Interchange Control Version Number is less than 00402, and if the Interchange Control Standards Identifier is not a ‘U’, this error message is written:
```
"(2181) ERROR: Invalid Interchange Control Standards Identifier
```
- The condition that the value of the repeat delimiter in ISA11 cannot match an existing delimiter value was added to the logic shown below which was already being used for both compliance and normal maps. If version ISA12 < 00402 then there is no repeat delimiter and REPEAT_DELIM is set to space. If version ISA12 >= 00402, if ISA11 is not space and is not between 0-9, a-z, A-Z, and not equal to another delimiter value, then REPEAT_DELIM is set to the ISA11 value. If ISA11 fails these conditions when ISA12 >= 00402, then, for compliance only, this error message is written:
```
"(2181) ERROR: Invalid Interchange Control Standards Identifier.
```
If these edits fail for a normal noncompliance run, then the REPEAT_DELIM is set to space and the run is continued. This relates to QTS #266682.
[CR #266682] See CR #266683, a duplicate.
[CR #266557] Users cannot overwrite the values in both the ISA and GS.

Resolution: This capability has been added to version 4.0.
[CR #266351] The RTP is incorrectly detecting and reporting that an ISA subelement separator is missing and no error is reported.

Resolution: ECRTP now detects this condition and reports it as an error.
[CR #266287] Users cannot overwrite the GS time and date values.

Resolution: This capability has been added to version 4.0.
[CR #265746] The RTP is incorrectly formatting the output of the conversion from a DI field to a DE field when the value is less than 1, because it leaves a leading zero to the left of the decimal.

Resolution: For output from the RTP, the leading zero to the left of the decimal has been removed.
[CR #257892] When a TM time value with a leading zero, such as 0830, is assigned to an AN field, the RTP incorrectly dropps the leading zero.

Resolution: This issue has been addressed.
[CR #256942] Compliance maps in the RTP are not catching all invalid dates. When a user assigns an invalid date from a memory variable to a date field, the system variable Err_Occurred is not set to Y.

Resolution: The RTP has been changed to check for additional invalid dates such as 20000000 or 19990000.

7.2 ECMap CRs

[CR #291429] Adding too many segments to ECMap causes errors when building a map.

Resolution: The ECMap code now uses a long integer instead of an integer.
[CR #291374] Updating the TP and TRADSTAT tables for updating control numbers takes excessive time.

Resolution: An index on the TP field in TPKEY and an index on the TRADSTAT field in TRADKEY has been added.
[CR #290106] When generating a compliance map, flow entries that take ECRTP from the current level to a new level are sometimes entered as mandatory. This caused ECRTP to occasionally report incorrectly that segments are missing.

Resolution: Generating a compliance map now optionally creates each flow entry that takes the ECRTP from the current level to a new level. This allows ECRTP to correctly report missing mandatory segments. This change has no impact on noncompliance maps.
[CR #287921] An enhancement request to use the Run_ID in the select criteria for the 997 maps.

Resolution: The 997 map has been enhanced to accept a Run_ID as an optional input parameter. When this enhanced 997 map is run and the new input parameter is specified, the map selects only records that match the Run_ID criterion in addition to all the other criteria for a 997 message.
[CR #287143] The Map Quick Reference report is not displaying the segments and elements in the correct order.

Resolution: The report has been fixed to display segments and elements in the correct order.
[CR #280264] The 270 compliance map is occasionally generating a 997 that rejects a transaction, but does not contain an AK502.

Resolution: A command within one of the processing rules (rule 18) now executes earlier in the sequence, and writes the correct value to the AK502.
[CR #278683] Invalid log entries are made when ECRTP was running an any-to-any map.

Resolution: The No EDI File switch, which should have been used, was missing for any-to-any maps. This has been fixed.
[CR #278516] When multiple Gateway scripts are run simultaneously, 997 files contain information from both runs.

Resolution: The 997 map has been enhanced to accept a Run_ID as an optional input parameter. When this enhanced 997 map is run and the new input parameter is specified, the map selects only records that match the Run_ID criterion in addition to all the other criteria for a 997 message.
[CR #277187] ECMap accepts duplicate flow entries in inbound flow, which causes problems in the GUI.

Resolution: ECMap now traps duplicate flow entries correctly when developing an inbound flow. A message is generated when a duplicate entry is attempted; the duplicate entry is not saved.
[CR #276516] The output is incorrect when a field is mapped to the PID1110 element in the PID segment.

Resolution: The HL7 standard has been updated to correct this problem.
[CR #275926] ECMap does not include sufficient length for the Nx datatype to account for a sign (+/-) in the data.

Resolution: An extra byte has been added to the Nx datatypes to include sufficient length to account for a sign appearing in the data. This change has been made for the following automatically generated maps: XML, compliance, NDO, and print.
[CR #275767] The ECMap map generate program has an error when a memory variable has a CRLF hard-coded in a fixed string.

Resolution: The problem has been fixed.
[CR #275206] The code that automatically generates maps for compliance, XML, print or auto-mapping is not long enough to account for the sign and decimal that might appear in the real number datatype field.

Resolution: The size of an EDI real number datatype field has been increased by two bytes, which allow for the sign and decimal in a real number datatype field.
[CR #273570] In ECMap, when a user adds a SQL rule command and chooses the SQL command 'Stored Procedure Call', her or she must complete the SQL Procedure Call Form. On this window, there is a Compile Statement button which populates the stored procedure call field using information from the rest of the form. If the user compiles the statement, clicks OK and exits the window, the correct rule command displays on the rules window. However, if the user later selects that rule command, chooses Properties, reenters the SQL Procedure Call Form, and clicks the Compile Statement button again, then an additional “?” is added to the statement. The extra “?” is carried forward to the rules window if the user uses OK to exit the subwindows.

Resolution: This problem has been fixed.
[CR #273376] If prompted to reindex the segments during mapping, an error occurs if there are more than 327 segments in the map. The segments do not display correctly in the mapping window.

Resolution: This problem has been fixed.
[CR #272491] The select statement returned by the Generate Print Map program does not obtain a column used later in the program.

Resolution: The select statement has been changed to return the column.
[CR #271800] The copy map utility does not give correct errors when the copy map failed.

Resolution: The copy map has been updated to give correct errors when the copy map fails.
[CR #271750] Users cannot create a new ISA/IEA envelope during an outbound map run.

Resolution: A new system variable, NEW_COMPANY_ID, has been added. When this is set, a new interchange is created.
[CR #271638] The Rules Cross-Reference report is not reporting rules used in the before rule for inbound maps.

Resolution: The problem has been fixed; these rules are now reported.
[CR #271434] Customers cannot make entries in the segment, element, or sub-element delimiter.

Resolution: This function has been implemented by adding system variables for the ISA and GS. See the 4.0 documentation for details.
[CR #271433] Users cannot map ISA and GS elements to the output in the master level.

Resolution: Additional system variables have been added to enable this functionality.
[CR #271432] When adding segments and doing a copy with data, reindexing corrupts the map.

Resolution: This problem was fixed.
[CR #271070] Commands on the any-to-any mapping window are not displayed in the correct order.

Resolution: Commands now display in the correct order.
[CR #270965] This is a parent QTS ticket for the following CRs: 266682, 266683, 266684, 266724, 267683, 267686, 267689, 268528, 268549, 268550, 268551, 268552 and 269934.

Resolution: New error messages were added relating to those problems.
[CR #270073] The string find and string replace commands are not working properly when multiple constants are used in the find commands.

Resolution: The string find and string replace commands now work correctly.
[CR #270070] The string replace command does not replace correctly.

Resolution: The window has been changed to clarify the command.
[CR #268553] Customers cannot create and accept TA1s.

Resolution: The capability to create and accept TA1s has been added as a new feature in version 4.0.
[CR #266557] Users cannot overwrite the values in both the ISA and GS.

Resolution: This capability has been added to version 4.0.
[CR #266556] When creating a template record, the hourglass never goes away.

Resolution: The code has been modified to ensure the hourglass changes back to a pointer when the template process was completed.
[CR #266287] Users cannot overwrite the GS time and date values.

Resolution: This capability has been added to version 4.0.
[CR #258909] A runtime error occurs under certain conditions in ECMap, when clicking the Browse button to select a company ID.

Resolution: The ECMap window, which displayed company IDs, has been modified so the list of available company IDs can be displayed and selected from the RunMap window.
[CR #255255] See CR #277187, a duplicate.

7.3 EC Gateway CRs

[CR #286687] Sometimes when using EFTP, the "Ready" message does not appear.

Resolution: This problem has been fixed by detecting an empty directory and displaying this message:
```
"Ready, directory can not be listed"
```
[CR #279367] The inactivity timeout is not working as expected. You are disconnected if you choose to list the files, and that file listing takes more than the timeout period.

Resolution: pfs/Async has been modified to not allow a timeout during listing of files.
[CR #279256] ODBC aliasing is not working properly.

Resolution: This problem has been fixed.
[CR #276968] Log queries are not saved.

Resolution: The log query function in 4.0 has been enhanced to support creating, editing, and deleting log queries. See the New Features Guide for detailed information.
[CR #276967] If a file exists when a new file with the same name is sent to the same directory via FTP, the existing file is overwritten.

Resolution: This problem has been fixed by appending a timestamp to the existing file.
[CR #276960] Users need more than 20 parameters.

Resolution: In Gateway 4.0, the number of parameters has been increased from 20 to 40. File Name variables and Count variables remain at 10 each.
[CR #275487] The file movement and file archive commands in EC Gateway are slow, especially for large files. These tasks are not calling the appropriate system functions that work faster.

Resolution: The file movement and file archive commands in wsproces were modified to use these system commands. These functions are now much faster when the move is within a file system.
[CR #275474] The EC Gateway GUI allows a value greater than the maximim 9,223,372,036,854,775,807 to be entered as a value for the count variables.

Resolution: EC Gateway GUI no longer allows numbers greater than 9,223,372,036,854,775,805.
[CR #273766] When copying or renaming a file, the original modified date and time is lost.

Resolution: This problem has been fixed.
[CR #273629] DOS FTP can connect to a site but not EFTP.

Resolution: If a user does not have rights to view the contents under a directory, when the user connects to that site by using EFTP, the message is:
```
"Ready, directory can not be listed" 
```
[CR #271926] Two reports in EC Gateway, the “Monthly summary report by trading partner” and the “Daily summary by transaction” incorrectly state that a transaction being run through a compliance map is an outbound transaction.

Resolution: This problem has been fixed.
[CR #271924] If a user with an EC Gateway user ID and password changes their password by using the Change Password utility, system privileges are lost.

Resolution: Users no longer lose system privileges when changing their password.
[CR #271874] Some commands permit users to enter parameter boxes in any order while others do not.

Resolution: Parameter boxes for all commands can now be entered in any order.
[CR #271764] mput and mget do not work identically. mget gets either all or some of the files (based on a wildcard) in a directory. mput only sends all of the files.

Resolution: mput has been enhanced to work the same as mget.
[CR #271752] Gateway’s copy table utility was creating duplicate entries in the trade agreement table.

Resolution: The copy table utility now checks for each record whether a source trade agreement record exists in the destination trade agreement record. If the source record exists, the record is not copied; otherwise it is copied.
[CR #271751] When copying a trade partner, the file name in the trade agreement window displays the folder name instead of the file name.

Resolution: This problem has been fixed.
[CR #271566] Access to the trade partner database via ODBC is failing for both inbound and outbound maps when using ECRTP with EC Gateway.

Resolution: This problem has been fixed.
[CR #271214} The Help button for the comm channel | properties | host tab should display a context sensitive help topic but it is not.

Resolution: This problem has been fixed.
[CR #270092] The string replace command fails with a Dr. Watson error when the value to be replaced is either a space or a null character.

Resolution: The string replace command now handles replacing a string with a space or no character.
[CR #269930] The FileSize command returns accurate values when the file size is 2,097,152 Kb (2GB+) or smaller. When files are larger than this, the command returns a -1.

Resolution: The FileSize command has been enhanced to handle file sizes larger than the limit above (2GB).
[CR #269621] The GetNextFile command was aborting when retrieving a file and assigning it to a FileName-n field.

Resolution: This has been fixed by ensuring that GetNextFile has a valid file name to copy before assignment.
[CR #269494] In version 2.8.3 of Gateway, an Microsoft ODBC error, "duplicate values in the index", is received when trying to paste a process in Gateway.

Resolution: This problem has been fixed.
[CR #269370] In Gateway, when editing a script longer than one window, if you scroll to the bottom of the script, select a line near the top of the window and edit it, the edited line drops to the bottom of the window when you click OK or Apply.

Resolution: This problem has been fixed.
[CR #269219] Some fields in the process tables are expected as NULL string, but in some old version 2.8.3 databases, these fields are empty.

Resolution: This problem has been fixed.
[CR #268796] Gateway’s string replace command appends instead of replacing.

Resolution: The string replace command no longer appends.
[CR #266709] pfs/Async permits a single ID to log in multiple times concurrently, allowing the user to have an undetermined number of active sessions.

Resolution: User now has a option that only one connection for one user.
[CR #257616] Enhancement requestto keep track of messages and responses through their lifecycle. .

Resolution: The MQSeries interface command interface has been redesigned using only a PUT and GET interface command. This new interface allows the customer to control reading, saving, and modifying the Message ID and Correlation ID fields in the MQ Message header.

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:

Message ID – specifies whether or not the message ID from the message being sent is to be saved in a parameter variable.

If a parameter value is not assigned, the message ID value is not saved as an individual parameter variable. This is the default. If a parameter value is assigned, the program saves the message ID value in the specified parameter.
Correlation ID – specifies whether or not the correlation ID from the message being sent is to be saved in a parameter variable.

If a parameter value is not assigned, the message ID value is not saved as an individual parameter variable. This is the default. If a parameter value is assigned, the program saves the message ID value in the specified parameter.

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.