MVSFORUMS.com

[jctgf]

I am really aware of the reasons to use a cursor instead of a simple select...

But, in terms of performance, is there a difference between opening a cursor to retrieve one row (fetch 1 row only) or executing a simple select?

I ask that because I have an assistant (a program) that generates Cobol programs that retrieve data from db2 tables.

U provide a SQL query and the assistant generates a complete Cobol program that executes the query, and formats the output data area.

We use it to create Cobol subroutines that can be invoked by many callers.

It saves the effort of coding very similar programs that are meant only to recover data from a database.

The problem is that this assistant only generates programs with cursors, even when u only need to retrieve 1 row.

My doubt now is: is a simple select more efficient than a cursor that retrieves only 1 row (fetch 1 row only)?

Is my assistant generating not optimized Cobol code?

Thanks,

JC

[CICS Guy]

[jajularamesh]

Singleton select is far more efficient than using the cursor for the same requirement.

Regards,
Ramesh(Venkata Apparao Jajula)

[dbzTHEdinosauer]

Code generators use cursors so that there is no possiblility of -811's.

Sure, a singleton select is 'faster' than open/fetch/close; but is receiving a -811 efficient?

The selling point behind code generators is that people without programming experience can create code to solve business needs, without problems - that is efficient................
_________________
Dick Brenholtz
American living in Varel, Germany