View previous topic :: View next topic
|
Author |
Message |
sudhakar_mainframe Warnings : 1 New User
Joined: 29 Jun 2006 Posts: 25
|
|
|
|
Can any one please explain how the SQL Statements behave in STATIC and DYNAMIC calls
Thanks,
Sudhakar |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
well, since static and dynamic calls have nothing to do with SQL,
hard to answer your question (and remain civil). |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
I started putting in comments for your question but then I just stuck to know, are you asking 1. about static and dynamic SQL statements execution? 2. or the question is related to static/dynamic calls of COBOL-subroutines, which in turn, involves embedded SQL? Please explain before we (I, for one) can help you. |
|
Back to top |
|
|
sudhakar_mainframe Warnings : 1 New User
Joined: 29 Jun 2006 Posts: 25
|
|
|
|
Hi Anuj,
It is related to sql statements in static and dynamic calls.
Thanks,
Sudhakar |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
Quote: |
Can any one please explain how the SQL Statements behave in STATIC and DYNAMIC calls |
Quote: |
It is related to sql statements in static and dynamic calls. |
not much diference... the uncertainity about what You want to know is still there
You can have...
dynamic subroutine calls with static SQL statements
static subroutine calls with dynamic SQL statements
dynamic subroutine calls with dynamic SQL statements
static subroutine calls with static SQL statements
again Your question is related to ...
1) dinamic/static generic subrotine calls
2) dynamic/static SQL statements
pleser reply with 1 or 2
the call to the dsn... stub will alway be a static one ( the stub will be part permanently of the load module )
if the reply is 2 take a look at
www.redbooks.ibm.com/abstracts/sg246418.html |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Hi Sudhakar,
Though I agree with Enrico -- confusion is still there, but being from non-english origin and reading through Dick's reply, I, for one probably got what you're asking about.
Enrico I believe his choice would be 1.
But having said that, I need to go on the same lines as Dick has said earlier -- static and dynamic calls in COBOL have nothing to do with SQL. Suggest you rephrase the question and possibly, you can let us know the origin of the question as well. Some one will be around with a suggestion then. |
|
Back to top |
|
|
GuyC
Senior Member
Joined: 11 Aug 2009 Posts: 1281 Location: Belgium
|
|
|
|
Probably a question concerning the logical unit of work.
In f.e. IDMS this can be quite confusing.
if this is your question, here's an attempt of an answer :
- A rollback will rollback everything until the last commit.
- A commit anywhere (main-program, static call routine, dynamic call routine) will commit everything.
- a goback does not commit.
the end of the main-program (without abend) does an (implicit) commit.
to put it in IDMS terms : There is only one "run-unit" and everything is in it. |
|
Back to top |
|
|
|