Skip to main content

Server/Region does not start; console.log shows error 173 "file not found" on "MVSOPTLM"

  • January 26, 2015
  • 0 replies
  • 0 views

Problem:

A server/region cannot be started, neither using "casstart" from the command line, nor from the ES Administration web page.  The console.log shows an error 173 "file not found" on file "MVSOPTLM".

Resolution:

The problem is caused by installing the product named Visual COBOL, as opposed to an appropriate product such as Enterprise Developer or Studio Enterprise Edition.

"MVSOPTLM" is an entry point into Micro Focus MSS (Mainframe SubSystems) functionality.  The Visual COBOL (VC) product does not include MSS functionality, thus "MVSOPTLM" is not found under VC.  VC includes Enterprise Server (ES) to support web services, but does not support MSS features such as CICS, JCL, or IMS.

The customer in this case had, on a separate machine, populated an Enterprise Server with MSS servers/regions, then had Exported the repository of that ES, then transferred the repository onto a machine on which Visual COBOL had been installed, then Imported the repository.  Thus ES showed the existence of MSS servers/regions, but could not start them, because MSS is not included under Visual COBOL.

The solution is to un-install Visual COBOL and install the product that was originally used to create the ES repository, either Enterprise Developer or Studio Enterprise Edition.


#EnterpriseDeveloper
#MFDS

0 replies

Be the first to reply!