Ladies and Gentlemen,

We have a problem involving MF COBOL (Net Express), ORACLE, XA Interface and Enterprise Server running under Windows 7.

In the following lines we describe a few details and specifics about our Development / Test environment:

>> The user interface (front-end) and connection to the MF COBOL (Net Express) application programs is through DELPHI;

>> These COBOL programs are accessed through Web Services;

>> ORACLE DB connection is through XA resource;

>> We have decided to have one single CONNECT through XA Resource instead of having the CONNECT command coded inside each and every COBOL program

but … we are experiencing the following problem:

>> moment a: COBOL programs with ORACLE SQL commands are running OK

>> moment b: we change a program (any program), according to a user request and recompile it (the changes are specific in ORACLE DML SQL commands)

>> moment c: we execute this changed program but its new image (or version) is not in effect; it seems that it is not loaded into memory and the system (Enterprise Server service) keeps accessing the old image... (very strange !!! ???) and the old SQL DML command keeps being executed instead of the new (changed) one contained in the new image of the application program.

It seems like the system (Enterprise Server service) kept using the “in memory” copy or image of the application program with the old SQL command, instead of making a refresh in order to bring the brand new image (copy) of the application program with the new SQL command to memory and use it.

As a workaround for this issue, we decided to stop and start the Enterprise Server service and could observe that with this procedure everything looks fine and the brand new image (copy) is loaded and starts to be used.

But this sort of procedure - stopping and starting the service - is not suitable and appropriate for us due to specifics of our operation and production environment.

We understand that there has to be an automatic way (through setup or a couple of configuration parameters) to have Micro Focus Enterprise Server working in a regular and consistent way in order for us to have this issue solved.

Looking forward to hearing from you soon.

Cheers, Rui Natal