Executing executable file created under AIX in OMVS

Midhun Mohandas · New User Joined: 03 Mar 2014 Posts: 24 Location: India

Hi,

I have a sample program TEST1.cbl

IDENTIFICATION DIVISION.
PROGRAM-ID. TEST1.
DATA DIVISION.
WORKING-STORAGE SECTION.
01 VATR PIC X(1).
PROCEDURE DIVISION.
DISPLAY 'TEXT ENTERED'
STOP RUN.

I have created an executable file under AIX using command

"cob2 -testq test1.cbl" , so an executable file 'testq' will be created.

Next I moved testq to OMVS region, as binary file and tried to execute it in OMVS region, but it was not executing.

The error shown is " -ÿØ -: testq 3: FSUM7351 not found "

Please help me to solve this issue.

enrico-sorichetti · Posted: Tue Apr 08, 2014 2:33 pm

Midhun Mohandas · New User Joined: 03 Mar 2014 Posts: 24 Location: India

Yes I am trying to run a executable file created in AIX under OMVS.

In AIX and OMVS we are using same compiler and in both environment the compiler command used is "cob2", so I am expecting it to work under OMVS.

I have created an executable file under AIX using command cob2 -testq test1.cbl

This command will compile test1.cbl and produce an executable file testq.

Then I moved this testq to OMVS region and tried to execute it there, but it is not working and throwing the error " -ÿØ -: testq 3: FSUM7351 not found "

Nic Clouston · Posted: Tue Apr 08, 2014 3:20 pm

Well, being COBOL it did not 'throw' an error but abended with error message ....

What happened ehn you compiled and linked the program on OMVS? You do know that AIX and OMVS are completely different beasts with different I/O routines?

Midhun Mohandas · New User Joined: 03 Mar 2014 Posts: 24 Location: India

Thanks everyone,

But I want to create a dll for cobol db2 program. In AIX I am able to create a dll for cobol-db2 program.

But in OMVS I am unable to create a dll for cobol-db2 program. When I used cob2 option to compile a cobol-db2 program and create a dll, the following error was shown

"An exec sql statement was found but the sql compiler option was not in effect. the statement was discarded".

enrico-sorichetti · Posted: Tue Apr 08, 2014 3:56 pm

even a beginner should realize that there is a difference between

SOURCE compatibility
and
OBJECT/EXECUTABLE compatibility

zOS and AIX are different operating systems,
AIX hardware and Zxxx machines have different architectures

and ...
please do not PM for answers

steve-myers · Posted: Tue Apr 08, 2014 4:48 pm

Just to add to Mr. Sorrichetti's post.

AIX uses the ASCII character set, OMVS uses the EBCDIC character set.
I can't say this with 100% certainty, but the machine operation codes in AIX hardware are almost certainly different than the machine operation codes in z/Architecture hardware.
I can't say this with 100% certainty, but the contents of AIX binary executable files (beyond the binary program text) are almost certainly different than OMVS binary executable files.

I'm not a Cobol programmer, and you will have to research this on your own, but does the version of MVS Cobol you are using even have the capability of creating and using DLLs? Your use of "COB2" suggests to me you are using a very old Cobol compiler.

Nic Clouston · Posted: Tue Apr 08, 2014 6:47 pm

I believe COB2 is a script for doing the compile. Not having seen it I do not know if it takes switches to alert it to the fact that DB2 precompile is required or if a different script should be used. However, the system programmer(s) should know or the DB2 DBA.

dick scherrer · Posted: Tue Apr 08, 2014 7:00 pm

Hello,

Is there another similar process that is working in your environment?

How does this process do what is needed?

The mechanics should be done as a "standard" and not as a personal experiment. System support, database support, etc should be involved in the implementation of a new method.

How are you trying to "move" between environments?

Robert Sample · Posted: Tue Apr 08, 2014 7:41 pm

Many people have successfully compiled DB2 COBOL programs under OMVS on z/OS without any issues. You need to add to your source code, as the first line, *PROCESS SQL (or *CBL SQL) to indicate to COBOL that you are using the DB2 coprocessor.

Would you expect to be able to compile a programs on a Windows machine and run that executable on z/OS? Of course not -- so WHY would you expect the executable from AIX to run on z/OS?

Rohit Umarjikar · Posted: Wed Apr 09, 2014 4:32 am

Robert, it seems to me the TS has the same issue before and he is not getting any support from the DBA or support person from his shop,

www.ibmmainframes.com/viewtopic.php?t=62474&highlight=

Midhun,

As Dick mentioned, have you talked once with your site person on this and if so then what had them to say?

Midhun Mohandas · New User Joined: 03 Mar 2014 Posts: 24 Location: India

Hi,

Thanks for all who have replied my question

.

I have contacted my support team but they are not that good at OMVS, so if you can help me, I will be able to do it.

Now I understood that an executable created in AIX cannot be executed in OMVS.

Now my only option is to create a executable file in OMVS region itself.

The command I give is cob2 -o <outputfilename> <inputfilename.cbl>

Below is my source file

PROCESS SQL, DLL,LIB,RENT,THREAD,OUTDD(WCGILOUT),SIZE(4000K)
IDENTIFICATION DIVISION.
PROGRAM-ID. REASIN RECURSIVE.
DATA DIVISION.
WORKING-STORAGE SECTION.
EXEC SQL DECLARE U756470.LIBRARY TABLE
( T_BNUM CHAR(5) NOT NULL,
T_BNAME CHAR(20) NOT NULL,
T_AUTHOR CHAR(15) NOT NULL,
T_STATUS CHAR(2) NOT NULL
) END-EXEC.
*************************************************************
* COBOL DECLARATION FOR TABLE U756470.LIBRARY
*************************************************************
01 DCLLIBRARY.
10 T-BNUM PIC X(5).
10 T-BNAME PIC X(20).
10 T-AUTHOR PIC X(15).
10 T-STATUS PIC X(2).
PROCEDURE DIVISION.
EXEC SQL
SELECT T_AUTHOR INTO :T-AUTHOR FROM LIBRARY WHERE
T_BNUM = 'A1234'
END-EXEC
DISPLAY T-AUTHOR.

When I compiled it without using 'CBL' compiler option the error I am getting is 'IGYDS0225-S, An "EXEC SQL" statement was found, but the "SQL" compiler option was not in effect. The statement was discarded.'

Later I added 'sql' compiler option, then the error I am getting is 'IGYOS4081-U, DSNH006I DSNHPSRV FILE "DBRMLIB " COULD NOT BE OPENED'

Please go through restrictions of Cob2 compiler( page number 283) at pic.dhe.ibm.com/infocenter/pdthelp/v1r1/topic/com.ibm.entcobol.doc_4.2/PGandLR/igy3pg50.pdf

Please help me in solving this issue..

Rohit Umarjikar · Posted: Wed Apr 09, 2014 12:57 pm

Did you check ibmmainframes.com/about62574.html ?

As well as www-01.ibm.com/support/docview.wss?uid=swg1PK89652

Midhun Mohandas · New User Joined: 03 Mar 2014 Posts: 24 Location: India

Hi Rohit,
I have gone through both of the links.

The first link, in the forum, is posted by me but none of the replies helped me to find a solution for what I am looking for though every replies helped me to learn more..

In the second link, it is about editing JCL. But in OMVS there is no option to add DBRMLIB(as there is no JCL) as of my knowledge.

Could you please find a solution for me ?

Nic Clouston · Posted: Wed Apr 09, 2014 2:16 pm

Have you checked the documentation for cob2 to see if the DBRMLIB can be added via a command line switch or any other way?

Robert Sample · Posted: Wed Apr 09, 2014 6:14 pm

Which version of Enterprise COBOL are you using? I was researching the issue and found out that my earlier statement was wrong. The version 4.2 Programming Guide manual says in Chapter 15 (Compiling under z/OS UNIX):