Dropped Features

This document lists the features dropped in recent EntireX versions and indicates which features are planned to be dropped in future versions.

Features to be Dropped in Future Versions

  • Deprecation of Solaris v.11.3
    The original provider of the operating system Solaris (Oracle) strongly recommends to upgrade from version 11.3 to 11.4 as of now. In order to provide for enough time for Software AG customers to react to the upgrade policy of Oracle for Solaris versions after v.11.3, production environments based on Software AG products of this October 2020 release will in general continue to work without the immediate need to upgrade. However, Software AG customer support will only handle issues for Software AG products that can be reproduced in a Solaris v.11.4 environment. All newer versions of Software AG products AFTER the October 2020 release will no longer work with Solaris v.11.3.

    Software AG therefore strongly recommends to address necessary migration steps timely.

  • Support of AIX und Sun Solaris SPARC
    The platforms AIX and Sun Solaris SPARC will no longer be supported in the next EntireX version.

  • SVM Files at Runtime in RPC Servers
    Support for server-side mapping files (SVM) in the EntireX RPC Servers for CICS ECI, IMS Connect, CICS, Batch and IMS, together with the Deployment Wizard, will be dropped in a future version. We strongly recommend using client-side server mapping files (CVM). To migrate server-side mapping files (SVM) to client-side server mapping files (CVM), see Migrating Server Mapping Files under Server Mapping Files for COBOL in the Designer documentation for prerequisites and steps.

  • Persistent Store Version less than 5
    Persistent Stores with PSTORE-VERSION less than 5 will no longer be supported in the next EntireX version.

  • PSTORE-LOAD/UNLOAD
    The options PSTORE-LOAD and PSTORE-UNLOAD of Broker-specific attribute RUN-MODE will no longer be supported in the next EntireX version.

  • CentOS-7
    CentOS-7 will no longer be supported in the next EntireX version.

Features Dropped in Version 10.7

  • Micro Focus COBOL
    EntireX no longer supports Micro Focus COBOL.

  • EntireX Broker and RPC Servers under z/VSE
    Support for the following EntireX components will end on 31 October 2020 for all EntireX versions (including version 9.6, the last released version on z/VSE):

  • SVM Files at Design Time in Software AG Designer
    Server-side mapping files (SVM) in the Software AG Designer are no longer supported. SVM files can no longer be created by the IDL Extractor for COBOL and by the COBOL Wrapper.

    We strongly recommend using client-side server mapping files (CVM). To migrate server-side mapping files (SVM) to client-side server mapping files (CVM), see Migrating Server Mapping Files under Server Mapping Files for COBOL in the Designer documentation for prerequisites and steps.

  • Direct SSL/TLS Support for Broker under z/OS
    Direct SSL/TLS support (using GSK) inside the Broker under z/OS is no longer supported. We strongly recommend using IBM's Application Transparent Transport Layer Security (AT-TLS) instead. See the following sections in the z/OS Administration documentation:

  • AIX Support
    AIX version 7.1 is no longer supported. EntireX still supports AIX version 7.2.

Features Dropped in Version 10.5

  • Micro Focus COBOL
    Software AG is discontinuing the support of Micro Focus COBOL on the platforms Windows and Linux because Micro Focus no longer supports Micro Focus Server Express and Net Express on these platforms.

    Micro Focus COBOL is still supported on Solaris and AIX, and EntireX still supports Micro Focus COBOL on these platforms.

  • HP-UX
    Software AG no longer supports HP-UX.

Features Dropped in Version 10.3

  • The EntireX RPC Server for IBM i of EntireX version 7.1.1 running under IBM i (AS/400) is no longer supported. We strongly recommend using the new RPC Server for AS/400 or the EntireX Adapter. See also Connection Parameters for AS/400 Connections.

  • For EntireX Java ACI, the obsolete and deprecated methods getEnvironment(), setEnvironment(String), useCodePage() and useCodePage(Boolean) of the Java class BrokerService have been removed.

Features Dropped in Version 10.1

  • z/VM
    EntireX no longer supports the operating system z/VM.

  • ETBSRV
    The EntireX Broker command-line utility ETBSRV is no longer provided. You can use ETBINFO under z/OS | UNIX | Windows | BS2000 or Command Central instead (see Administering EntireX Broker using the Command Central GUI | Command Line).

  • EntireX Broker Tutorial
    The Natural-based EntireX Broker Tutorial is no longer provided.

Features Dropped in Version 9.12

  • Direct SSL/TLS Support for Broker Stubs under z/OS
    Direct SSL/TLS support (using GSK) inside the broker stubs under z/OS has been dropped. We recommend using IBM's Application Transparent Transport Layer Security (AT-TLS) instead. For an overview of broker stubs and transport, see Transport: Broker Stubs and APIs. For information on how to configure SSL/TLS with EntireX, see Using SSL/TLS with EntireX Components.

  • Administration using System Management Hub
    Administration with SMH is no longer supported. This also includes the batch interface argbatch and SNMP. The most important functionality is provided by Command Central. Minor features have been moved to the command line or were dropped.

    The following type of EntireX installation cannot be administered with Command Central:

    • EntireX installations not using SAG Installer

    • EntireX installations lower than version 9.9

    • EntireX installations on z/OS, z/VSE or BS2000

    The following alternatives are provided for these installations:

    • Use ETBINFO and/or ETBCMD

    • Use System Management Hub version 9.10 for the time being

    Authorization rules for UNIX and Windows are no longer managed with System Management Hub. Instead, rules can be stored in an LDAP repository (as in earlier versions of EntireX) or in a new section of the Broker attribute file, DEFAULTS=AUTHORIZATION-RULES. See Authorization Rules.

  • RPC Server and Listener for IBM® MQ
    Dynamic IDL/RPC parameters are no longer supported.

  • Microsoft Visual Studio
    The following EntireX components support Microsoft Visual Studio version 2015:

    • C Wrapper

    • DCOM Wrapper

    • Microsoft Visual Studio Wizard for EntireX .NET Wrapper

    Older versions of Microsoft Visual Studio (2010, 2012 or 2013) are no longer supported.

Features Dropped in Version 9.10

  • Windows 32-bit Operating Systems
    Software AG no longer supports Windows 32-bit operating systems. However, the following EntireX components are supported for 32-bit applications on Windows 64-bit operating systems:

  • Encryption
    The encryption/decryption mechanism provided by EntireX Security is deprecated. We strongly recommend using the Secure Sockets Layer/Transport Layer Security protocol. See SSL/TLS, HTTP(S), and Certificates with EntireX.

    Documentation and other appearances of EntireX Encryption (for example interfaces, configuration file) have been removed. Existing applications using EntireX Encryption are still be supported at runtime for compatibility reasons.

  • Java Message Service
    EntireX Broker support for Java Message Service (JMS) has been dropped.

  • Publish and Subscribe
    The EntireX Broker communication model Publish and Subscribe is no longer supported. You therefore need to remove the broker attribute PUBLISH-AND-SUBSCRIBE from your broker attribute file, otherwise error ETBE0023 Unknown attribute PUBLISH-AND-SUBSCRIBE is returned.

  • Swapping out New Units of Work
    The ability to swap out new units of work that was provided in earlier EntireX versions is now no longer required. The corresponding broker attributes SWAP-OUT-NEW-UOWS and MIN-UOW-CONVERSATIONS-IN-MEMORY are no longer supported and will be ignored.

  • Library broker.so
    Under UNIX, library broker.so has been replaced by library libbroker.so. Library libbroker.so was already delivered in earlier EntireX versions and is identical. Make sure you applications use only libbroker.so.

  • SMH Technical Information
    The System Management Hub Technical Information Agent is no longer delivered.

  • SNMP
    The SNMP (Simple Network Management Protocol) interface of the System Management Hub is no longer supported. SMH itself will no longer be supported in the next version.

Features Dropped in Version 9.9

  • EntireX Mini Runtime
    The EntireX Mini Runtime is no longer delivered. The functionality is provided instead with EntireX libraries, which are installed using the Software AG Installer.

  • IAF
    EntireX support for Software AG's Integrated Authentication Framework (IAF) has been dropped from all interfaces.

  • EntireX Wrapper for Enterprise JavaBeans
    As announced in the EntireX 9.7 Release Notes, the Wrapper for EJB is no longer provided. It is no longer possible to enable Java-based components to access an EntireX RPC server using Enterprise JavaBeans.

  • Adapter Services Wrapper for Natural
    As announced in earlier Release Notes, the Adapter Services Wrapper for Natural is no longer provided. The functionality is already covered by using the IDL Extractor for Natural and the Integration Server Wrapper.

  • Partner Broker ID
    Partner Broker ID is no longer supported.

  • IBM Compiler PL/I for MVS & VM
    Support for IBM compiler PL/I for MVS & VM has been dropped. Support for Enterprise PL/I for z/OS compiler will continue. This affects PL/I Wrapper, RPC Server for Batch and RPC Server for IMS.

  • Microsoft Visual Studio Wizard for EntireX DCOM Wrapper
    The Microsoft Visual Studio Wizard for EntireX DCOM Wrapper as a Software AG plug-in is no longer provided. The functionality is provided by the Designer.

  • Broker Control Block Definitions NATDEF12 and NATDEF21 of ACI for Natural
    The LDAs NATDEF12 and NATDEF21, which define API version 2 only, are consolidated into the LDA NATDEF. NATDEF12 and NATDEF21 are no longer provided. Use NATDEF in your application for Broker control block definition.

Features Dropped in Version 9.7

  • Broker Services
    Broker Services were partially retired with EntireX version 8.0; they are now fully retired. This affects in particular the following components:

    • Broker Services WebSphere MQ Support
      Retired since version 8.0. There was no direct replacement for the Broker Services WebSphere MQ support. However, WebSphere MQ is supported with the RPC Server for IBM MQ and the Listener for IBM MQ. For scenarios using the Broker Services WebSphere MQ support, both of these might be a more modern and easier-to-use alternative.

    • Broker Services APPC Adapter
      Retired since version 8.0. There was no replacement for the Broker Services APPC Adapter. We recommend using the standard EntireX functionality in the future. Possible migration paths can vary and should be determined based on your projects.

    • Broker Services Attach Service
      There is no replacement for the Broker Services Attach Service. Most of the RPC server implementations support multiple worker models for load balancing purposes. See for example Scenario Worker Models under CICS | Batch. For Natural RPC servers, the Natural RPC Server front-end provides similar functionality.

  • Location Transparency
    Support for Location Transparency was dropped in EntireX version 9.5. Location Transparency has now been removed from all major interfaces.

    Java sources generated with older versions of the EntireX Wrapper for Enterprise JavaBeans do not compile with this version and newer versions of EntireX. Re-generate these source files. It is possible to run classes based on older versions of EntireX with this version and newer versions of EntireX, as long as Location Transparency is not used.

Features Dropped in Version 9.6

  • Operating System Support
    The following platforms are no longer supported: z/OS 1.12, z/VSE 4.3.

  • BKIMBTSO
    Broker stub BKIMBTSO is no longer provided. The functionality is covered by stub BROKER. The default transport method for BKIMBTSO was TCP; default for BROKER is NET. However, this can be changed to TCP if required. See Setting the Default Transport Method under Administering Broker Stubs in the z/OS Administration documentation.

  • IAF
    No new version of IAF is delivered with this release of the webMethods suite.