Home > Archive > Cobol > June 2007 > Re: Getting SQLCODE -302 after migrating DB2 V7 to V8 IN ibm z/os
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Getting SQLCODE -302 after migrating DB2 V7 to V8 IN ibm z/os
|
|
|
| Sri wrote:
> All
>
> Recenetly our shop migrated to DB2 V8 from V7. We are in IBM System Level:
> z/OS 1.6.1 @ RSU 0702.
> <SNIP> . . . There is no code modification made for many
> years. It is working fine in DB2 V7 enviornments. The module is using
> <SNIP>
> Any idea we need to change the code for v8 or is the probelm with DB2 v8
> migration.
>
> Thanks
> Ravi
At the risk of raising the wrath of some on this list, ...
The first question I have is which compiler was used to compile the
program? Depending on the 'mode' you are running DB2 V8, you may be
running into the minimum level of the compiled code required for DB2 V8.
Specifically, to run in New Function Mode [NFM], your COBOL program
must have been compiled by Enterprise COBOL V3.2 or later.
There are actually three modes for running DB2 V8:
1) Compatibility Mode (CM) is acceptable provided the code was
successfully running with DB2 V7. In this case, as long as you meet the
compiler level for V7, you're OK.
2) Before you can move to NFM, you must pass through the Enabling New
Function Mode [ENFM]. This is basically the stage where you meet the
prerequisites for NFM, you have started some of the migration steps, but
you have not attempted to exploit the new functions in V8.
3) Then finally, NFM.
Ref: DB2 UDB for z/OS V8 Release Planning Guide (SC18-7425-02)
Chapter 3. Planning for migration, conversion, and fallback
So, if you really have the situation "...There is no code modification
made for many years...," then I would suspect that you might have a
problem with the compiler level of your program.
Carl
| |
|
| In article <58811$466217da$d06620ed$22614@FUSE.NET>,
CG <Carl.Gehr.ButNoSPAMStuff@MCGCG.Com> wrote:
[snip]
>So, if you really have the situation "...There is no code modification
>made for many years...," then I would suspect that you might have a
>problem with the compiler level of your program.
'What's wrong with Your Program? It's throwing garbage results!'
'Hmmmmm... according to the load module it hasn't been touched in thirteen
years or so... what do the data look like?'
'We're getting the same data as always, from SmallCo... there's something
wrong with Your Program!'
'SmallCo... didn't I read that they were acquired and are now a subsidiary
of BigCo?'
'So what... there's something wrong with Your Program!'
'Let me take a look at the data... how interesting... you know, it looks
like you're receiving comma-delimited ASCII input now, the program was
designed for EBCDIC files.'
'Look, everyone knows I'm Not Technical... but Your Program's throwing
garbage, do something about it!'
DD
| |
|
| Iam pretty sure the DB2 V8 is in CM mode. System DBAs informred this one.
The compiler version is PP 5655-G53 IBM Enterprise COBOL for z/OS 3.3.1.
**DISPLAY 'PREPARE GET DUPL USAGE'.
EXEC SQL
PREPARE SQL_STM6 FROM :WS06-GET-DUPLICATE-CURSOR
END-EXEC.
**DISPLAY 'DECLARE GET DUPL USAGE'.
EXEC SQL
DECLARE GET_DUPLICATE CURSOR FOR SQL_STM6
END-EXEC.
"CG" <Carl.Gehr.ButNoSPAMStuff@MCGCG.Com> wrote in message
news:58811$466217da$d06620ed$22614@FUSE.NET...
> Sri wrote:
>
> At the risk of raising the wrath of some on this list, ...
>
> The first question I have is which compiler was used to compile the
> program? Depending on the 'mode' you are running DB2 V8, you may be
> running into the minimum level of the compiled code required for DB2 V8.
> Specifically, to run in New Function Mode [NFM], your COBOL program must
> have been compiled by Enterprise COBOL V3.2 or later.
>
> There are actually three modes for running DB2 V8:
> 1) Compatibility Mode (CM) is acceptable provided the code was
> successfully running with DB2 V7. In this case, as long as you meet the
> compiler level for V7, you're OK.
> 2) Before you can move to NFM, you must pass through the Enabling New
> Function Mode [ENFM]. This is basically the stage where you meet the
> prerequisites for NFM, you have started some of the migration steps, but
> you have not attempted to exploit the new functions in V8.
> 3) Then finally, NFM.
>
> Ref: DB2 UDB for z/OS V8 Release Planning Guide (SC18-7425-02)
> Chapter 3. Planning for migration, conversion, and fallback
>
> So, if you really have the situation "...There is no code modification
> made for many years...," then I would suspect that you might have a
> problem with the compiler level of your program.
>
> Carl
| |
|
|
|
|
|