DEC/EDI Version 3.2 Release Notes This document provides supplemental infor- mation about DEC/EDI Version 3.2. This in- cludes DEC/EDI Application Client and Server for OpenVMS AXP, OpenVMS VAX and Digital UNIX, DEC/EDI Application Client for Sun Solaris and HP-UX, and DEC/EDI Cockpit and CommandCenter for use with OpenVMS and Digital UNIX Servers. It includes notes on restrictions, and known problems. Digital Equipment Corporation Maynard, Massachusetts ________________________ December 1997 Possession, use or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital[TM] or an authorized sublicensor. While Digital believes the information included in this publication is correct as of the date of publication, it is subject to change without notice. Digital Equipment Corporation makes no repre- sentations that the use of its products in the manner described in this document will not in- fringe on existing or future patent rights, nor do the descriptions contained in this document imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. © Digital Equipment Corporation 1990,1997. All rights reserved. The following are trademarks of Digital Equipment Corporation: AXP, DEC, Digital, DEC/EDI, DECforms, DECnet, DECwindows, MAILbus, OpenVMS, VAX, VAX 9000, VAXcluster, VAXstation, VMS, VMSmail and the DIGITAL logo. AT&T is a trademark of American Telephone & Telegraph Company. TYMNET is a registered trademark of TYMNET, Inc. UNIX is a registered trademark licensed exclu- sively by X/Open Company Ltd. OSF/1 is a registered trademark of Open Software Foundation, Inc. IBM, AIX and RS/6000 are registered trademarks of International Business Machines Corporation. HP and HP-UX are registered trademarks of Hewlett-Packard Company. Microsoft is a registered trademark, and Windows is a trademark, of Microsoft Corporation. CLEO, 3780Plus and SYNCcable+ are registered trademarks of CLEO Communications. Oracle is a registered trademark of the Oracle Corporation. CORBA is a registered trademark of the Object Management Group. Adobe and Acrobat are registered trademarks of Adobe Systems Incorporated. Sun and Solaris are registered trademarks of Sun Microsystems, Inc. HP and HP-UX are registered trademark of Hewlett Packard Company. BEA ObjectBroker is a registered trademark of BEA Systems Inc. This document was prepared using VAX DOCUMENT, Version 2.1. Contents __________________________________________________________ __________________________________________________________ CHAPTER 1 INTRODUCTION 1-1 1.1 DOCUMENT CONTENT 1-1 1.2 NEW USERS 1-2 1.3 EXISTING USERS 1-2 __________________________________________________________ CHAPTER 2 MAJOR NEW FEATURES 2-1 2.1 BEA OBJECTBROKER IS OPTIONAL FOR TCP/IP USERS 2-1 2.2 SUPPORT FOR COMMANDCENTER MAPPING TABLE EDITOR ON OPENVMS 2-2 2.2.1 Additional Features provided by the Mapping Table Editor 2-2 2.3 SUPPORT FOR EDIFACT CONTRL MESSAGE 2-3 2.4 SUPPORT FOR ACCESS CONTROLS 2-4 2.5 SUPPORT FOR BUSINESS REFERENCES 2-4 2.6 COCKPIT SUPPORTS ALL SERVER PLATFORMS 2-4 2.7 UNIFIED DOCUMENTATION SET 2-5 iii __________________________________________________________ CHAPTER 3 KNOWN PROBLEMS 3-1 3.1 KNOWN PROBLEMS IN THE MAPPER 3-1 3.1.1 EDIFACT Segment SCC can have Repeat Count of 0 3-1 3.1.2 $DATE() function to be used only for intermediate conversions on DIGITAL UNIX 3-2 3.1.3 Extended Division and Extended Multiplication not supported on UNIX 3-2 3.2 KNOWN PROBLEMS IN THE TRANSLATION SERVICES 3-2 3.2.1 TFBs may not map to new profile caches 3-3 3.2.2 UCS Rn data type is not supported by DEC/EDI 3-4 3.3 KNOWN PROBLEMS IN THE COCKPIT 3-4 3.3.1 Problems when resetting large numbers of documents or transmission files 3-5 3.3.2 GUI Server error when viewing files that don't exist 3-5 3.3.3 'You do not have privilege' message when fail to login to Server 3-6 3.3.4 BEA ObjectBroker error connecting to V3 Server then a V2 Server 3-6 3.3.5 Cockpit can crash viewing an OpenVMS error log with short nodename 3-7 3.3.6 Viewing the bottom of the error log does not go quite to the bottom 3-7 3.4 KNOWN PROBLEMS IN THE COMMANDCENTER 3-7 3.4.1 User Access Control Editor may be displayed with scroll bars 3-7 iv 3.4.2 Network Tester can crash with OracleRDB on Windows 95 3-8 __________________________________________________________ CHAPTER 4 PROBLEMS WITH SOLUTIONS 4-1 4.0.1 OpenVMS Servers which do not have DECnet Plus installed and running 4-1 4.0.2 'Unlink' Error when Post/Fetch Server (TCP) Processes Timeout 4-2 4.0.3 VAX Systems May be too Slow to Start a Child Process 4-2 4.0.4 Error During Upgrade From FileBridge or DEC/EDI V2.0 4-3 4.0.5 Problems with Microsoft Office 97 and Oracle 7 ODBC drivers 4-4 4.1 BEA OBJECTBROKER MULTIPLE OBJECT PROBLEMS 4-5 __________________________________________________________ CHAPTER 5 APPLICATION CLIENT RELEASE NOTES 5-1 5.1 MAJOR NEW FEATURES 5-1 5.1.1 ObjectBroker is optional for TCP/IP users 5-1 5.2 COMPARISON WITH PREVIOUS RELEASES 5-2 5.2.1 UNIX Track Selection List is Comma Separated 5-2 5.3 KNOWN PROBLEMS 5-2 5.3.1 Extra ObjectBroker Server processes on heavily loaded systems 5-2 5.3.2 Server Error when using ObjectBroker on Digital UNIX 5-3 5.3.3 Configuration of ObjectBroker V2.7 on Sun Solaris fails 5-5 v Chapter 1 Introduction __________________________________________________________ __________________________________________________________ 1.1 Document Content This document forms the release notes for the following products: o DEC/EDI for OpenVMS[TM] VAX[TM], V3.2. This product contains both application client and server components for the OpenVMS VAX platform. o DEC/EDI for OpenVMS Alpha[TM], V3.2. This product contains both application client and server components for the OpenVMS Alpha platform. o DEC/EDI for Digital UNIX[TM], V3.2. This product contains both application client and server components for the Digital UNIX platform. o DEC/EDI Cockpit, V3.2. This product contains the DEC/EDI Cockpit and Access Control Editor for use with DEC/EDI for Digital UNIX and DEC/EDI for OpenVMS VAX and Alpha servers. o DEC/EDI CommandCenter, V3.2. This prod- uct contains the DEC/EDI Cockpit and CommandCenter applications for use with DEC/EDI for Digital UNIX and DEC/EDI for OpenVMS VAX and Alpha servers, and online Introduction 1-1 documentation in Adobe[TM] Acrobat [TM] for- mat. All information in this document applies equally to all of the above products unless specifically stated otherwise. The information in Chapter 5 is common to all Application Clients. In addition to the OpenVMS and Digital UNIX Application Clients this also includes the following: o DEC/EDI for Sun[TM] Solaris[TM], V3.2. This product contains the DEC/EDI application client for the Sun Solaris platform. o DEC/EDI for HP-UX[TM], V3.2. This product contains the DEC/EDI application client for the HP-UX platform. __________________________________________________________ 1.2 New Users If you are a new user of DEC/EDI, you should follow the installation instructions for the product contained in DEC/EDI: Installation. You are also recommended to read DEC/EDI: Introduction which gives an overview of DEC/EDI describing the main components of the system and explaining how the system processes business data. __________________________________________________________ 1.3 Existing Users If you are an existing user of DEC/EDI, you should follow the installation instructions for the product contained in DEC/EDI: Installation. DEC/EDI for OpenVMS VAX, V3.2 supports installa- tion over previous OpenVMS VAX versions of the product. Specifically it may be installed over: o DEC/EDI V2.1D 1-2 Introduction o DEC/EDI V2.1C o DEC/EDI V2.1B o DEC/EDI V2.1A o DEC/EDI V2.1 o DEC/EDI V1.3 o DEC/EDI FileBridge V1.1 Note that it may not be installed over any other versions. DEC/EDI for OpenVMS Alpha V3.2 supports instal- lation over previous OpenVMS Alpha versions of the product. Specifically it may be installed over: o DEC/EDI V2.1D o DEC/EDI V2.1C o DEC/EDI V2.1B o DEC/EDI V2.1A o DEC/EDI V2.1 DEC/EDI for Digital UNIX V3.2 supports installa- tion over previous Digital UNIX versions of the product. Specifically it may be installed over: o DEC/EDI V3.1A o DEC/EDI V3.1 o DEC/EDI V3.0 Introduction 1-3 Chapter 2 Major New Features __________________________________________________________ This chapter outlines the major new features introduced in DEC/EDI V3.2 since the previous release. __________________________________________________________ 2.1 BEA ObjectBroker is optional for TCP/IP users DEC/EDI now provides a choice of using either the BEA ObjectBroker network interface that was available in previous versions, or a TCP/IP only network interface. For more information and details on configuring the network interface, refer to DEC/EDI: Installation. OpenVMS On OpenVMS, use the following command procedure to configure the network interface: $ @DECEDI$TOOLS:DECEDI$CONFIGURE_CLIENT_SERVER Digital UNIX On Digital UNIX, use the following command to configure the network interface: # /usr/sbin/decedi_config Major New Features 2-1 __________________________________________________________ 2.2 Support for CommandCenter Mapping Table Editor on OpenVMS The Mapping Table Editor component of the DEC/EDI CommandCenter may be used to develop Mapping Tables for integrating business applica- tions for both OpenVMS and Digital UNIX Server platforms. The DEC/EDI Server for OpenVMS now supports the Mapping Table Editor as a feature-rich alternative to using the FileBridge development interface. Use of the Mapping Table Editor requires the DEC/EDI CommandCenter license to be installed on the Server, using the License Management Facility (LMF). __________________________________________________________ 2.2.1 Additional Features provided by the Mapping Table Editor The Mapping Table Editor provides the following additional features, which are not available through the FileBridge development interface: o Shared Lookups Lookup tables may be shared between Mapping Tables, by use of a server-resident table. o Enhanced Audit Trail Access In the inbound direction, the Mapping Service may access many of the fields in the transla- tion services audit record for the document currently being processed, by the use of global variables. o Support for Business References 2-2 Major New Features Business references may be used and assigned in mapping statements, by the use of global variables. __________________________________________________________ 2.3 Support for EDIFACT CONTRL Message The EDIFACT Syntax and Service Report Message (CONTRL), Version D, Release 3, is now supported by the translation services on both OpenVMS and Digital UNIX Server platforms. The CONTRL message is a message that syntacti- cally acknowledges or rejects with error indica- tion, a received interchange, functional group or document. DEC/EDI implements a syntactical check of the received interchange and any functional groups and documents it contains. DEC/EDI returns a CONTRL message that acknowl- edges receipt of the interchange itself and details of any failing functional groups or doc- uments within the interchange. Any documents or functional groups not explicitly referenced in the CONTRL message are assumed to be syntacti- cally correct. The user may optionally specify that the CONTRL message should contain an indication of the suc- cess or failure of all documents and functional groups within the interchange, by setting the functional acknowledgement flag to DOC. The EDIFACT CONTRL message is provided as a separate message dictionary as part of the DEC/EDI Message Updates service. Major New Features 2-3 __________________________________________________________ 2.4 Support for Access Controls The DEC/EDI Cockpit and CommandCenter products include a new application, the Access Control Editor, which enables an authorized user to manage access to particular aspects of the DEC/EDI system. Access controls may be used to restrict the set of applications or trading partners that a par- ticular Cockpit user may view, and whether they may perform reset operations or modify data. These act as a filter, so the user may only ac- cess the audit data that they are authorized to access. Access control may also be used to identify whether a particular user may use the Cockpit only, or may use the other CommandCenter appli- cations. __________________________________________________________ 2.5 Support for Business References The user may assign up to five business ref- erence values, using the Client/Server API or Command Line Interface (TRADE command), or within the Mapping Service, in both the inbound or outbound directions. Documents may subsequently be tracked via the API or Command Line Interface, or via the INTERCHANGE command (OpenVMS Server) or Cockpit (OpenVMS and Digital UNIX Servers). __________________________________________________________ 2.6 Cockpit supports all Server platforms The DEC/EDI Cockpit supports simultaneous access to both OpenVMS and Digital UNIX servers. 2-4 Major New Features __________________________________________________________ 2.7 Unified Documentation Set Much of the user documentation has been uni- fied across all platforms. In particular, the following books cover all platforms: o Release Notes This document, which provides information that should be read prior to installing or upgrading to DEC/EDI V3.2. o Introduction This book provides an introduction to DEC/EDI, its components and architecture. o Installation This book covers installation and basic con- figuration of a DEC/EDI system, and covers all supported platforms, including setting up the database and network interface for use by DEC/EDI. A configuration example is used to assist with verification that the system is config- ured correctly, and to provide an introduc- tion to using some of the DEC/EDI components. o Application Development This book covers the DEC/EDI Client/Server Application Programming Interface (API) and Command Line Interface (CLI), and setting up and using the Mapping Service in detail. The following books are specific to the Server platform you are using. o Digital UNIX User Support Manual This book covers all aspects of configur- ing, maintaining and setting up the DEC/EDI server, and troubleshooting the DEC/EDI Server. Major New Features 2-5 o OpenVMS User Support Manual Volume 1 This book covers all aspects of configur- ing, maintaining and setting up the DEC/EDI Server. It includes reference material on the DEC/EDI commands, and a tutorial style section on using the Mapping Service. o OpenVMS User Support Manual Volume 2 This book covers troubleshooting and solving problems on the DEC/EDI Server, and informa- tion on the error messages that may be logged by the DEC/EDI system. The full user documentation suite, is provided online in Adobe[TM] Acrobat[TM] format on the DEC/EDI CommandCenter CD-ROM. 2-6 Major New Features Chapter 3 Known Problems __________________________________________________________ __________________________________________________________ 3.1 Known Problems in the Mapper __________________________________________________________ 3.1.1 EDIFACT Segment SCC can have Repeat Count of 0 In EDIFACT Versions 1 and 901, Document ORDERS, the second segment SCC has an invalid repeat count of 0. To correct this, load the ORDERS document into the Tables Editor. Edit the invalid SCC segemnt. Set the repeat count to 1, and save to the server. Replace the EDIFACT Tables cache. When using the invalid segment in the Mapper, the Mapper will give the following error at runtime: SEG: SCC#2 DECEDI__OUTGOING_SEG_MISSING (e), required segment not generated in document FILE=1, DOC=1 DECEDI__OPERATION_ABORTED (e), operation Aborted To correct this error edit the SCC segment as described above, load the map into the Mapping Table Editor, reimport the document definition, and recompile the mapping table. Known Problems 3-1 __________________________________________________________ 3.1.2 $DATE() function to be used only for intermediate conversions on DIGITAL UNIX In DEC/EDI V3.2 the $DATE() function is used for conversion to/from the VMS Binary date format. This function is fully supported in DEC/EDI V3.2 for OpenVMS. However, in DEC/EDI V3.2 for DIGITAL UNIX, $DATE() should be used only for arriving at intermediate values, not for values to be read and/or written to an application file. The alternative function $DATE_CONVERT() should be used in place of $DATE(). See the online help for the Mapping Table Editor for informa- tion regarding the use of $DATE_CONVERT __________________________________________________________ 3.1.3 Extended Division and Extended Multiplication not supported on UNIX In DEC/EDI V3.2 on UNIX the mapper functions that perform extended division and extended multiplication are not supported. If an attempt to perform extended arithmatic is made then one of the following messages will be written to the output log file: LIB_EDIV - nyi LIB_EMUL - nyi __________________________________________________________ 3.2 Known Problems in the Translation services 3-2 Known Problems __________________________________________________________ 3.2.1 TFBs may not map to new profile caches This problem affects the TFBs for both X12 and Edifact translation services on all server platforms. As each converted outbound document reaches a TFB it is immediately processed and queued internally within the TFB, with a status of building, until the conditions are right to build the document into a transmission file. Each building document queued at the TFB has profile cache data associated with it, hence the TFBs will only map to a new profile cache if they do not have any documents queued with a status of building. The result of this is that it is possible for documents to fail to build, apparently because there is no matching trading partner profile in the profile cache, even though you are sure that the profile is in the cache. This is most likely to occur on systems that have long TFB build intervals, or where outbound batching is being used. If the problem does occur then you can take either of the following steps: o Shutdown and Restart the DEC/EDI server. ( Only partial shutdown and restart are re- quired ). o Force the TFB to empty its queues: o Set all build intervals down to a short time interval. ( Once the queues have been flushed, you can reset the build interval ). o Ensure that any batches are either com- pleted or cancelled. Known Problems 3-3 If you suspect that you have this problem and need to confirm the contents of the profile cache you should use the DEC/EDI Profile Cache Viewer: o See "man decedi_pcv" on UNIX servers. o See DECEDI$TOOLS:DECEDI$PCV.TXT on VMS servers. __________________________________________________________ 3.2.2 UCS Rn data type is not supported by DEC/EDI The UCC/UCS ( DEC/EDI TDCC ) standard defi- nitions contain some elements with data type Rn. UCC/UCS data type Rn is a decimal number with a specified level of precision. An example of this data type is as follows. In an R3 element the number 12.3456 would be truncated to 12.345 . The same number represented as an R1 data type would be 12.3. DEC/EDI does not support this data type. UCC/UCS element definitions that have a data type of Rn will be represented in DEC/EDI as having a data type of Nn. The DEC/EDI translation services will treat this data type as "N". The DEC/EDI tables editors will not allow users to enter a data type on Nn. DEC/EDI will not apply precision to data types represented as Nn. For example: Whereas the number 12.3456 represented as a UCS R1 data type should be 12.3, when represented as a DEC/EDI N1 data type it is 12.3456 __________________________________________________________ 3.3 Known problems in the Cockpit 3-4 Known Problems __________________________________________________________ 3.3.1 Problems when resetting large numbers of documents or transmission files From Cockpit, when resetting a large number of documents of transmission files (e.g. several hundred or more) in one operation you may en- counter problems. These can exhibit themselves in various ways after a number of the items have been reset, e.g.: Cockpit slows down and gradually comes to a halt A message saying Cockpit has run out of mem- ory A message saying Cockpit could not allocate any more memory When this happens it is necessary to kill the Cockpit (and DDE Server if using BEA ObjectBroker) and possibly reboot your PC. It may also be necessary, on the server, to stop the BEA ObjectBroker GUI deamon (if using BEA ObjectBroker). The workaround is to reset a smaller number of items at a time. __________________________________________________________ 3.3.2 GUI Server error when viewing files that don't exist When viewing certain files from Cockpit, e.g. detailed listings, error lists and external files you may get the error 'The DEC/EDI GUI Server failed to open a file, Please refer to the Error Log for details'. The error log will contain a DECEDI__GUIERRSRC error saying there was an error opening the file and it may not exist. It will also list the filename. Known Problems 3-5 These files may not exists for perfectly valid reasons, e.g. you have configured the Server so they are not created. However, the error implies something more serious has happened. You can safely ignore these errors for files that you know shouldn't exist. __________________________________________________________ 3.3.3 'You do not have privilege' message when fail to login to Server If you fail to login to a Server (e.g. wrong password) when User Access Controls are in force, then when you try again you are told e.g. 'You do not have privilege to view documents' even though you do. The workaround is to exit the Cockpit and re- start it. __________________________________________________________ 3.3.4 BEA ObjectBroker error connecting to V3 Server then a V2 Server If you login to a V2 Server and use BEA ObjectBroker to say read the Error Log; then login to a V3 Server you will get the message: An BEA ObjectBroker System Exception occured. This can arise due to incorrect configuration on your PC,or a problem with the DEC/EDI GUI Server: CORBA_BAD_PARAM OBB_DB_MTHMAPNOTFND (e), Method Map Not Found For Interface `6c38779ff54b.02.10.24.50.3e.00.00.00'. -OBB_DB_INTNOTFND (e), Interface 6c38779ff54b.02.10.24.50.3e.00.00.00 not found. -OBB_DB_OBJNOTFND (e), Object `6c38779ff54b.02.10.24.50.3e.00.00.00' not found. The work around is to shutdown the DDE Server and try again. 3-6 Known Problems __________________________________________________________ 3.3.5 Cockpit can crash viewing an OpenVMS error log with short nodename When viewing an OpenVMS error log with Cockpit with the TCP/IP Interface, it can crash when scrolling up and down or going to the top or bottom. This may occur if you have defined the Server with the Server Nodename in the short form (e.g. edipc) rather than the long form (e.g. edipc.domain.com). The workaround is to define the Server with the long form of the nodename. __________________________________________________________ 3.3.6 Viewing the bottom of the error log does not go quite to the bottom When viewing the error log with Cockpit and you select to go to the bottom, and also when the error log is initially displayed, the entries displayed may not actually be the last entries. Use the down arrow key to bring the last errors into view. __________________________________________________________ 3.4 Known problems in the CommandCenter __________________________________________________________ 3.4.1 User Access Control Editor may be displayed with scroll bars On displays where the User Access Control Editor completely fills up the screen, or is too large for the screen, the editor may be displayed with vertical scrollbars. In this circumstance it is necessary to use the scrollbars to make the buttons at the bottom and fields at the top visible. Known Problems 3-7 __________________________________________________________ 3.4.2 Network Tester can crash with OracleRDB on Windows 95 If your VMS DEC/EDI Server is configured with the short form of the node name, e.g. 'decedipc' instead of 'decedipc.domain.com', then doing the 'ODBC Test' multiple times may cause it to crash, typically after three to six times. You need not worry about this as the rest of Cockpit and CommandCenter work OK. You can work around it by using the full node name in the Server definition. 3-8 Known Problems Chapter 4 Problems with Solutions __________________________________________________________ __________________________________________________________ 4.0.1 OpenVMS Servers which do not have DECnet Plus installed and running As of OpenVMS 7.0, it is no longer necessary for an OpenVMS machine to have DECnet Plus installed and configured, the machine relying on TCP/IP connectivity alone to communicate with the outside world. A by-product of DECnet Plus not being installed is that the logical SYS$NODE is left undefined. The DEC/EDI Server relies on the existance of the logical SYS$NODE, both during installation, and during the operation of the server. To allow the DEC/EDI Server to be installed and to allow it to run in a TCP/IP only environment, then the logical SYS$NODE should be defined. For example, the DEC/EDI server, mynode.company.com, could have a line added to SYS$MANAGER:SYSTARTUP_ VMS.COM prior to starting DEC/EDI of DEFINE/SYSTEM SYS$NODE "MYNODE::" Problems with Solutions 4-1 It should be noted that some of the optional components of DEC/EDI rely on DECnet Plus being installed and configured and therefore will not work in this environment. These being: V1.3 Support Services. Client access (either local or remote) via DECnet. OFTP Communications. X.400, X.435 Communications. INS TRADANET Communications. __________________________________________________________ 4.0.2 'Unlink' Error when Post/Fetch Server (TCP) Processes Timeout On a Digital UNIX server, when Post/Fetch or Track server processes timeout, there may be this error message in the DEC/EDI error log file: Tue Jan 18 17:04:37 2000 PID = 9892 NAME = Post/Fetch Server (TCP) DECEDI__STOPPING (i), shutdown started DECEDI__CHILDTIMEOUT (i), Child server exiting as inactive for too long. Tue Jan 18 17:04:37 2000 PID = 9892 NAME = Post/Fetch Server (TCP) DECEDI__STOPPED (i), shutdown completed Tue Jan 18 17:29:40 2000 PID = 10511 NAME = Post/Fetch Server (TCP) DECEDI__SYSSRVERR (e), error calling the system service routine No such file or directory unlink This message can be safely ignored. __________________________________________________________ 4.0.3 VAX Systems May be too Slow to Start a Child Process If you have a particularly slow VAX system, it is possible that when you issue a POST, FETCH or TRACK request you will see the following error in the error log file: 4-2 Problems with Solutions %DECEDI-E-CHILDSICK, Child server process, type: decedi$csf, id: 002, unable to respond to requests. -DECEDI-I-CONDLOGGED, condition logged by DECEDI$PS on node EDINOD:: at 6-OCT-1 997 10:20:46.62 The request will be rejected, but in the meantime the decedi$csf will have most likely started up. This can be verified by checking the state of the POST, FETCH or TRACK child server processes: @DECEDI$TOOLS:DECEDI$PS_CONTROL SHOW At least one of the child servers should be at the IDLE state-i.e. ready to accept a request. Issue the request again and it will be accepted. __________________________________________________________ 4.0.4 Error During Upgrade From FileBridge or DEC/EDI V2.0 A problem has been found when upgrading a system that has currently got FileBridge or DEC/EDI V2.0 installed. The problem occurs during execution of FBR$ARCHIVE.COM The following error can be given: %DCL-E-INVIFNEST, invalid IF-THEN-ELSE nesting structure or data inconsistency %DCL-E-INVIFNEST, invalid IF-THEN-ELSE nesting structure or data inconsistency The file SYS$COMMON:[SYSEXE]FBR$ARCHIVE.COM needs to be modified before performing an up- grade to DEC/EDI V3.2 in order to correct an error in an IF-THEN-ELSE structure. The following section of code shows the error: Problems with Solutions 4-3 803 $ 804 $ ! Add checking for out of sync cases where one of fbr$library and 805 $ ! fbr$audit_root is not defined and the other is 806 $! 807 $ if (library .eqs. "" .and. root .nes. "") .or. - 808 (library .nes. "" .and. root .eqs. "")) 809 $ then 810 $ err "%FBR-F-NOLIB - FBR$LIBRARY, FBR$AUDIT_ROOT definition mismatch" 811 $ goto FBR_ARCHIVE_END 812 $ endif Line 808 contains one extra close parentheses. The line should be updated to read as follows: 808 (library .nes. "" .and. root .eqs. "") A new version of this file is shipped with the DEC/EDI V3.2 kit. However, it is necessary, during an upgrade, to execute the old command file before the new file can be installed. __________________________________________________________ 4.0.5 Problems with Microsoft Office 97 and Oracle 7 ODBC drivers If you use the 32bit CommandCenter on Windows 95 with an Oracle 7 ODBC driver, and you have Microsoft Office 97 installed on the same PC; then you may find there are errors when connect- ing to your Oracle 7 Server. You may get a 'Function Sequence Error' or an Oracle 7 ODBC error something like: SQLSTATE: 08003, Native Code Error: 0 Driver Message [Oracle][ODBC Oracle Driver] Connection Not Open SQLSTATE: 01000, Native Code Error: 0 Driver Message [Microsoft][ODB Driver Manager] The driver returned invalid (or failed to return) SQL_DRIVER_ODBC_VER: %s 4-4 Problems with Solutions Or some of the CommandCenter Editors may crash when loading from or saving to the Server database. This is due to a problem with the Office 97 ODBC drivers and the Oracle 7 ODBC drivers interfer- ing with each other. Note, it only occurs if you install ODBC drivers when installing Office 97. Oracle have provided a fix for this problem by upgrading your ODBC driver to V2.0.3.1.4 (requires SQL*NET V2.3) and then applying a patch Oracle can supply. __________________________________________________________ 4.1 BEA ObjectBroker Multiple Object Problems The DEC/EDI Server supports multiple cur- rent clients posting and fetching from the server. To do this with the latest versions of BEA ObjectBroker, this means that a new BEA ObjectBroker implementation was introduced, DECEDI_IMO_IMPL, to hand out unique object iden- tifiers for each concurrent request up to a maximum of 20. The first client request to post or fetch an ob- ject starts the DECEDI_IMO_IMPL implementation, which then readies its list of 20 concurrent object identifiers and hands the first one out, which in turn is used to auto-start the first post/fetch implementation, DECEDI_IMF_IMPL. However, if another post/fetch request enters the DEC/EDI Server before BEA ObjectBroker has completed starting the first DECEDI_IMO_IMPL implementation then BEA ObjectBroker will start another DECEDI_IMO_IMPL implementation and they will clash over handing out the unique object identifiers. Problems with Solutions 4-5 To avoid this happening, the DECEDI_IMO_IMPL implementation, should be allowed to start before any real post/fetch requests are ready to be made. Once the DECEDI_IMO_IMPL implementation has been completely started by BEA ObjectBroker then all subsequent post and fetch requests will be routed to the already running DECEDI_IMO_ IMPL to get a free object identifier first and if it is busy will wait for it to service the next request (which should not take long). Once they have this free object identifier then can then talk to the DECEDI_IMF_IMPL which has been allocated to them. To ensure the DECEDI_IMO_ IMPL is started we recommend issuing a TRADE FETCH command as soon as DEC/EDI is completed starting. This can use an application id not registered to avoid fetching any real data. For example: trade fetch INTRUDER temp.tmp /type=document 4-6 Problems with Solutions Chapter 5 Application Client Release Notes __________________________________________________________ __________________________________________________________ 5.1 Major New Features This chapter outlines the major new features introduced in DEC/EDI V3.2 since the previous release. __________________________________________________________ 5.1.1 ObjectBroker is optional for TCP/IP users DEC/EDI now provides a choice of using either the ObjectBroker network interface that was available in previous versions, or a TCP/IP only network interface. For more information and details on configuring the network interface, refer to DEC/EDI: Installation. Sun Solaris On Sun Solaris, use the following command to configure the network interface: # /usr/bin/decedi_config.sh HP-UX On HP-UX, use the following command to configure the network interface: # /usr/bin/decedi_config.sh Application Client Release Notes 5-1 __________________________________________________________ 5.2 Comparison with Previous Releases This section describes features in the Application Client that have changed in this release. __________________________________________________________ 5.2.1 UNIX Track Selection List is Comma Separated In previous releases the tracking selection list in the UNIX Application Client was space separated. This did not reflect what was docu- mented, and was inconsistent with the OpenVMS Client implementation. The tracking selection list on UNIX client has been modified to be a comma separated list. __________________________________________________________ 5.3 Known Problems This section describes known problems with the TCP/IP or ObjectBroker network interface between the DEC/EDI Server and remote PC or Application Client installations. __________________________________________________________ 5.3.1 Extra ObjectBroker Server processes on heavily loaded systems Due to a problem with BEA ObjectBroker, it is possible that on heavily loaded OpenVMS systems, where many processes are swapped out, all Application Client activity may stop after a time with a surplus of Post/Fetch (DECEDI_IMF) and Track (DECEDI_IMT) servers executing. The APPLICATION/BROKER command incorrectly shows the processes in a "Process Died" state. However, the processes are still executing on the system and taking up system resources. 5-2 Application Client Release Notes Until a patch from BEA Systems for ObjectBroker becomes available, the only courses of action are: 1. Switch to using direct TCP/IP for the client- server communications. Note that on OpenVMS systems, this may require the installation of DIGITAL TCP/IP Services. To do this: a. Shut Down ObjectBroker b. Shut Down DEC/EDI c. Run the Client Configuration Utility and select the "Configure TCP/IP" option: $ @DECEDI$TOOLS:DECEDI$CONFIGURE_CLIENT_SERVER.COM d. Run the Client Configuration Utility on each of the Application Client systems, as described in DEC/EDI: Installation. e. Re-start DEC/EDI 2. Increase your system resources (memory, page- file and/or swapfile space). __________________________________________________________ 5.3.2 Server Error when using ObjectBroker on Digital UNIX When a client gets a 'Server Error' when issuing a trade post, fetch, or track command, it is possible that nothing is written into the error log file. When this happens, check that the ObjectBroker server process has come up under a username that has enough access rights. Issue the 'obbmsho' command. For example: Application Client Release Notes 5-3 > obbmsho Implementation Name Username Status ------------------------------------------ ------------ ------ DECEDI_GUI_IMPL decedi Executing Inst UUID: 7eb3cf3fe099.02.10.48.60.82.00.00.00 Pid: 926 Impl UUID: 6c38779ff54b.02.10.24.50.3e.00.00.00 Registered at: Thu Aug 28 08:43:41 1997 Server has no attributes DECEDI_IMO_IMPL decedi Executing Inst UUID: 7ed227925a61.02.10.49.90.3a.00.00.00 Pid: 4005 Impl UUID: 77b71d8d9182.0c.d0.a8.00.00.00.00.00 Registered at: Wed Sep 3 04:45:08 1997 Server has no attributes DECEDI_IMF_IMPL jones Executing Inst UUID: 7ed227925a62.02.10.49.90.3a.00.00.00 Pid: 4008 Impl UUID: 68eb4b476f3b.0c.70.a9.00.00.00.00.00 Registered at: Wed Sep 3 04:45:10 1997 Server has no attributes OBB_CMD_NUMMSRVSFND (i), 3 servers found. Note that the DECEDI_IMF_IMPL server is running under the username of 'jones'. Jones may not have enough access rights. The workaround is to stop the unprivileged server and start a new one while logged into a more privileged account such as root. That is: > obbmstp 7ed227925a62.02.10.49.90.3a.00.00.00 > su # trade post my-application .... ! this starts a new server. # logout > 5-4 Application Client Release Notes __________________________________________________________ 5.3.3 Configuration of ObjectBroker V2.7 on Sun Solaris fails When running decedi_config on a Sun Solaris system with OBB V2.7 installed and you select ObjectBroker, you get the following error: # /usr/bin/decedi_config.sh 1. Configure TCP/IP Client-Server Link 2. Configure ObjectBroker 3. Exit Configuration Select option [3] : 2 Configuring ObjectBroker Enter the name of the DEC/EDI Server [server.company.com] : ...creating repository ...registering servers ...creating client object ld.so.1: /usr/bin/decedi_make_imc_obj: fatal: /usr/lib/libobb.so.2.6: can't open file: e2 Killed ...creating context object The workaround is to copy the 2.7 library file into a 2.6 (or 2.5) file so the configuration process can find it. For example: # cp /opt/DECOBBDEV/lib/libobb.so.2.7 /usr/lib/libobb.so.2.6 Application Client Release Notes 5-5