Deploying Enterprise Server (Known Issues)

• On Windows 10, if you are using Microsoft's EDGE browser to access the Enterprise Server Administration GUI, issues with EDGE can cause the automatic refresh feature to display a dialog asking whether you want to resubmit a form. To work around this issue, cancel the resubmit request and then refresh the server list page or the Home page of Enterprise Server Administration. You can also turn off the automatic refresh by setting the Auto-refresh interval setting on the Home page of Enterprise Server Administration to 0.

• User ID and password constraints:

  Enterprise Server emulates the mainframe operating system on Microsoft Windows, UNIX and Linux operating system platforms. Mainframe user authentication constraints and technical limitations are therefore emulated through the Enterprise Server External Security Facility (ESF) Manager to ensure mainframe compatibility.

  These constraints and technical limitations apply to many components of Enterprise Server including:

  • CICS
  • Job Entry Subsystem (JES)
  • Micro Focus Directory Server (MFDS)
  • IMS

  To avoid issues with user signon and similar functions, avoid attempting to create user IDs or passwords that do not meet these requirements.

For more information, see Long Usernames and Passwords.

• You can start and stop enterprise servers from Server Explorer only if they are running on a local MFDS instance through a loopback adapter (such as "localhost" or 127.0.0.1). You cannot control remote servers, including the case when you access the local machine using its network name, in this manner. Instead, you must use Enterprise Server Common Web Administration to configure these.

• The Historical Statistics Facility may generate incorrect records for SSTM-enabled enterprise servers.
• In Enterprise Developer 2.3, some job scheduling tools from third-party vendors might stop communicating with Enterprise Server. This might have an impact on our external partners who integrate with Enterprise Server such as job schedulers which do not use MFBSI. The issue might occur with job schedulers such as Zena, CA, ASG or UC4, if these are run outside of a COBOL environment with the path set. Click here for more information about the issue and how to work around it.

• There is currently no template for a PL/I-configured enterprise server.