Skip to main content

We are using Micro focus visual cobol development hub 7.0 version for business logic. Getting error while starting the application only ECS orchestration and same cobol container is working fine in EKS orchestration.

Need help to understand why we are getting this error only in ECS. 

Execution error : file 'exptnmgr'
error code: 191, pc=0, call=1, seg=0
191 Terminal type not defined


#container
#MicroFocus
#VisualCOBOL

We are using Micro focus visual cobol development hub 7.0 version for business logic. Getting error while starting the application only ECS orchestration and same cobol container is working fine in EKS orchestration.

Need help to understand why we are getting this error only in ECS. 

Execution error : file 'exptnmgr'
error code: 191, pc=0, call=1, seg=0
191 Terminal type not defined


#container
#MicroFocus
#VisualCOBOL

Hello Priya Nambi,

 

The most common cause for this error is that the terminal type defined by the TERM setting is not available or configured correctly in the failing environment. You might try determining how the $TERM environment variable is set when the application runs, and check for whether that terminal type is available when you are running under ECS.

 

Also, running containers inherit some functionality from their container host system, so you might want to investigate which host platform and O/S versions are in use on the ECS and EKS implementations.

Beyond that, investigating this type of problem is likely beyond the scope of a Community Post. You might want to open a Support Case if the above does not help you resolve the issue.


Hello Priya Nambi,

 

The most common cause for this error is that the terminal type defined by the TERM setting is not available or configured correctly in the failing environment. You might try determining how the $TERM environment variable is set when the application runs, and check for whether that terminal type is available when you are running under ECS.

 

Also, running containers inherit some functionality from their container host system, so you might want to investigate which host platform and O/S versions are in use on the ECS and EKS implementations.

Beyond that, investigating this type of problem is likely beyond the scope of a Community Post. You might want to open a Support Case if the above does not help you resolve the issue.

I suspect the terminal is required because a object COBOL runtime exception is being generated (it clears the screen, displays a error message and waits for "Hit T to terminate" style message) and exptnmgr is the program that does it.


Hello Priya Nambi,

 

The most common cause for this error is that the terminal type defined by the TERM setting is not available or configured correctly in the failing environment. You might try determining how the $TERM environment variable is set when the application runs, and check for whether that terminal type is available when you are running under ECS.

 

Also, running containers inherit some functionality from their container host system, so you might want to investigate which host platform and O/S versions are in use on the ECS and EKS implementations.

Beyond that, investigating this type of problem is likely beyond the scope of a Community Post. You might want to open a Support Case if the above does not help you resolve the issue.

Thank you Blair, Stephen for the response. Variable TERM was not set in ECS orchestration and now we have set it and it worked. Thanks again!