Deploying Enterprise Server (Known Issues)

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

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

• When running Enterprise Server applications on any RISC-based platform, you could receive an error such as "CASCD1057S JES Initiator for Server ... abended by signal 00004". In this case, set the environment value COBMAINSTACK to a value greater than 8000000 to increase the default stack size.