Microfocus Cobol/Vertex in Progress

[mcunningham]

We are running Vertex Sales Tax programs compiled in Microfocus Cobol on our Solaris UNIX system. The programs are being called using the UNIX command within a Progress program. This has been working fine until just now. Here are the differences:

- When previously run on the system it is now crashing on, it was running in Progress V8.
- When running on Progress V9.1D, it was running just fine on a different Solaris box running on p-code (this system is running 4GL Development and Enterprise DB licenses of Progress)
- We have now moved our production to a Sun box running only the Enterprise DB License of Progress. It does not work on this system. We can go to a UNIX prompt and it works just fine, but from within the program we are getting the following error message (related to the Microfocus Cobol):

id.so.l: /usr/local/cobol/rts32: fatal: liboops.so.2.0: open failed: No such file or directory

Here is what we have done already:

- Checked all environment variables - they all match
- Checked all UNIX system kernel variables - they are either the same or better on the box we are having a problem with
- Checked file existance, sizes, dates/times and rights and they all match
- Checked Microfocus Cobol's knowledgebase with no luck

FYI - the databases are sitting on a remote database server. The scripts to bring them up are identical as they reside on the remote server.

The only difference is that it works when run through Progress when running p or r code using a 4GL Development License in addition to the Enterprise DB license. Running strictly r-code is when it fails.

We are running Progress v9.1D, Vertex L v3.503 and Microfocus Cobol v4.1.

Has anyone else run into anything such as this?

While we can run the processes directly from UNIX, it is preferrable to have the Progress process for this.

Thanks in advance for your help!!

Mary

 

[cecsno]

Are you sure you weren't running p-code and not r-code on your development box? Can you take the snippet of code that performs the UNIX command on your production box and run it from the Progress editor successfully? If so try to compile that snippet and see if it will run.

How about a look at it?

 

[mcunningham]

We are definitely running the r-code. We renamed the p-code just to be sure.

The Progress statement that calls the UNIX script is:

UNIX /data2/v2/MonthlyUpdate.

The UNIX script that is crashing:

echo " VTS100 in progress .............."
echo "VTS100 Started at: " >> MonthlyUpdate.log
date >> MonthlyUpdate.log
/usr/local/cobol/bin/cobrun ./VTS100.int

It is as soon as this runs that we get the error message. The code before this are simple UNIX cp commands and they are working fine.

Thanks!
Mary

 

[cecsno]

Is one of the copies (cp) a file need for the UNIX /data2/v2/MonthlyUpdate script. If so try putting a pause 1 after the last cp.