Mainframe, MVS and zOS Discussion

Hi,

In case if at some point of time DB2 is down, would that impact the pre-compilation process of a DB2-COBOL program? I ask this because when I was compiling a program the compilation went fine but when I tried to execute the job, it went down saying that DB2 is down. Later I came to know that, DB2 was down for last two hours. I was surprised to know that because if it is so then it should have allowed the compilation too. What can be the reason?

Execute the job or program?

Because the availability of DB2 has nothing to do with the pre-compiler's ability to replace SQL statements with COBOL code. Just like the lack of CICS being available does not prevent the CICS pre-compiler replacing CICS statement with COBOL code.

In agreement with nicc, the DB2 precompiler checks the SQL in the program for errors, it adds working storage areas and source code compatible statements that are used to invoke DB2 and in last all of the SQL statements are extracted from the program source and placed into a member called the DBRM. In doing all this precompiler does not refer to the DB2 catalogue tables. So the fact that DB2 is down, does not hinder the pre-compilation. But at execution time, the story is different.

It should throw error at bind time

I doubt if it will "throw" an error at any time - unless on a PC

Thanks all.

Hi Priya

Just to check did it solve your problem

It compiled well even when the DB2 was down.