DB2 COBOL stored procedure to UDB SQL stored procedure

[PJackson]

I have been given the task of taking a 3,200 line COBOL stored
procedure and duplicating the same functionality in UDB 7.2 on the
Windows platform with a procedural SQL stored procedure. I have
fiddled with procedural SQL stored procs on UDB, but mostly
short,trivial ones. Looking for good advice, links, etc. on the best
approach to this. There doesn't seem to be the concept of subroutines
within a stored proc, so I am guessing one main stored proc that may
be calling multiple smaller stored procs? Just found out about this
need late this afternoon and wondering what the best approach is to
doing such a task.

Any and all ideas most welcome.

thanks,

fv

[Mark A]

<PJ******@txf b-ins.comwrote in message
news:11******** **************@ y80g2000hsf.goo glegroups.com.. .

>I have been given the task of taking a 3,200 line COBOL stored
procedure and duplicating the same functionality in UDB 7.2 on the
Windows platform with a procedural SQL stored procedure. I have
fiddled with procedural SQL stored procs on UDB, but mostly
short,trivial ones. Looking for good advice, links, etc. on the best
approach to this. There doesn't seem to be the concept of subroutines
within a stored proc, so I am guessing one main stored proc that may
be calling multiple smaller stored procs? Just found out about this
need late this afternoon and wondering what the best approach is to
doing such a task.

Any and all ideas most welcome.

thanks,

fv

DB2 V7.2 for LUW is no longer supported for IBM (and has not been supported
for several years). On top of that, DB2 V8 LUW has implemented some
enhancements that make it easier to write stored procedures in SQL (as
opposed to C, Java, etc). Or better yet is DB2 V9 for LUW.

[PJackson]

I have no control over what version of UDB we are on - what we have
is what I have to deal with and can only dream of V8 or V9. Just a
lowly developer given the task and need some advice as to the best
approach to the problem using procedural SQL. After looking at the
cobol stored proc for about 30 minutes I have a vague idea of what it
is doing.

Any thoughts and advice about doing this in UDB 7.2 much appreciated.

fv
On Apr 4, 10:26 pm, "Mark A" <nob...@nowhere .comwrote:

<PJack...@txf b-ins.comwrote in message

news:11******** **************@ y80g2000hsf.goo glegroups.com.. .

I have been given the task of taking a 3,200 line COBOL stored
procedure and duplicating the same functionality in UDB 7.2 on the
Windows platform with a procedural SQL stored procedure. I have
fiddled with procedural SQL stored procs on UDB, but mostly
short,trivial ones. Looking for good advice, links, etc. on the best
approach to this. There doesn't seem to be the concept of subroutines
within a stored proc, so I am guessing one main stored proc that may
be calling multiple smaller stored procs? Just found out about this
need late this afternoon and wondering what the best approach is to
doing such a task.

Any and all ideas most welcome.

thanks,

fv

DB2 V7.2 for LUW is no longer supported for IBM (and has not been supported
for several years). On top of that, DB2 V8 LUW has implemented some
enhancements that make it easier to write stored procedures in SQL (as
opposed to C, Java, etc). Or better yet is DB2 V9 for LUW.

[mike]

On Apr 5, 5:24 am, [e-mail] wrote:

I have no control over what version of UDB we are on - what we have
is what I have to deal with and can only dream of V8 or V9. Just a
lowly developer given the task and need some advice as to the best
approach to the problem using procedural SQL. After looking at the
cobol stored proc for about 30 minutes I have a vague idea of what it
is doing.

Any thoughts and advice about doing this in UDB 7.2 much appreciated.

fv

On Apr 4, 10:26 pm, "Mark A" <nob...@nowhere .comwrote:

<PJack...@txf b-ins.comwrote in message

news:11******** **************@ y80g2000hsf.goo glegroups.com.. .

>I have been given the task of taking a 3,200 line COBOL stored
procedure and duplicating the same functionality in UDB 7.2 on the
Windows platform with a procedural SQL stored procedure. I have
fiddled with procedural SQL stored procs on UDB, but mostly
short,trivial ones. Looking for good advice, links, etc. on the best
approach to this. There doesn't seem to be the concept of subroutines
within a stored proc, so I am guessing one main stored proc that may
be calling multiple smaller stored procs? Just found out about this
need late this afternoon and wondering what the best approach is to
doing such a task.

Any and all ideas most welcome.

thanks,

fv

DB2 V7.2 for LUW is no longer supported for IBM (and has not been supported
for several years). On top of that, DB2 V8 LUW has implemented some
enhancements that make it easier to write stored procedures in SQL (as
opposed to C, Java, etc). Or better yet is DB2 V9 for LUW.

"Just a lowly developer", you say, hmm..

With your target of DB2 v7.2 on Windows, you probably read that
on *that* version the SQL-PL source-code for a stored procedure
gets converted to 'C' and then you need a supported 'C' compiler
to convert that to an executable form.

I suggest you carefully read relevant sections of two books "DB2 V7.2
Application Development Guide", and "DB2 V7.2 Application Building
Guide", which came with the documentation of DB2 Version 7.

Realise that the restriction of using the out of date Version 7.2 will
hamper your ability to get support, even from this group. So it may be
worthwhile making the case of using a supported version - which does
not need any separate 'C' compiler to run SQL PL stored procedures.

[PJackson]

I stand corrected - we are on DB2 UDB version 8.1 in production. They
are looking at going to 8.2, but who knows when that might be. The C
compiler is already in place and has been for several years, and I
will be using the DB2 Development Center to write and build the stored
procedures.

thanks,

fv

>
"Just a lowly developer", you say, hmm..

With your target of DB2 v7.2 on Windows, you probably read that
on *that* version the SQL-PL source-code for a stored procedure
gets converted to 'C' and then you need a supported 'C' compiler
to convert that to an executable form.

I suggest you carefully read relevant sections of two books "DB2 V7.2
Application Development Guide", and "DB2 V7.2 Application Building
Guide", which came with the documentation of DB2 Version 7.

Realise that the restriction of using the out of date Version 7.2 will
hamper your ability to get support, even from this group. So it may be
worthwhile making the case of using a supported version - which does
not need any separate 'C' compiler to run SQL PL stored procedures.- Hide quoted text -

- Show quoted text -