Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
Same SQL Statement Number in Omegamon Trace (DB2 Zos)

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2
View previous topic :: :: View next topic  
Author Message
Manshadi

New User


Joined: 31 Aug 2005
Posts: 82

PostPosted: Sat Sep 03, 2011 2:24 pm    Post subject: Same SQL Statement Number in Omegamon Trace (DB2 Zos)
Reply with quote

Hi,

I have been looking at the BCAS trace inputs.

In some cases, the statement number listed is conflicting.

Statement 4518 of DBIOCASV is referred as Insert, Select, Update. But the real statement is INSERT.
+ INSERT 4518 DBIOCASV 1 00:00.01361 0 0 0
+ SELECT 4518 DBIOCASV 1 00:00.20540
+ UPDATE 4518 DBIOCASV 1 00:00.60928

Similarly statement 5732 of DBIOINCT, which is an INSERT, appears as Close Cursor, Select, Insert.
+ CLOSE CURSOR 5732 DBIOINCT..done 1 00:00.17315
+ SELECT 5732 DBIOINCT 1 00:00.19338
+ INSERT 5732 DBIOINCT 1 00:00.01296...done

Is there any reason why this would occur?

Regards
Manshadi
Back to top
View user's profile Send private message

Bill Woodger

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7315

PostPosted: Sat Sep 03, 2011 2:38 pm    Post subject: Reply to: Same SQL Statement Number in Omegamon Trace (DB2 Z
Reply with quote

Is this the first time you have looked at these? Or have you done so before and are saying these particular ones are unusual?

What do your colleagues have to say about this? Anything in manual or online help of any sort?
Back to top
View user's profile Send private message
Manshadi

New User


Joined: 31 Aug 2005
Posts: 82

PostPosted: Sat Sep 03, 2011 2:47 pm    Post subject:
Reply with quote

No this is not first time which I found that and it's not happen always for example during (1 hour ) trace 2 times.

I could not find anything related to this issue on online help or document.

Please note that the sql statement on DBRMLIB is unique for each statement.

regards
Manshadi
Back to top
View user's profile Send private message
Bill Woodger

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7315

PostPosted: Sat Sep 03, 2011 3:10 pm    Post subject: Reply to: Same SQL Statement Number in Omegamon Trace (DB2 Z
Reply with quote

Do you know the data that caused the multiple references?
Back to top
View user's profile Send private message
Manshadi

New User


Joined: 31 Aug 2005
Posts: 82

PostPosted: Sat Sep 03, 2011 3:13 pm    Post subject:
Reply with quote

Yes the data referenced with multiple transactions.(with DEP GEN CAS transactions)
Back to top
View user's profile Send private message
Bill Woodger

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7315

PostPosted: Sat Sep 03, 2011 3:20 pm    Post subject: Reply to: Same SQL Statement Number in Omegamon Trace (DB2 Z
Reply with quote

OK. I'm being Plastic-Blow-Up-Programmer here, in that I'm keeping time until someone who knows something about this comes by. You talk to me in the hope that you realise something in explaining.

Assume I know nothing, so explain as though to a simpleton.

Quote:
Yes the data referenced with multiple transactions.(with DEP GEN CAS transactions)


So, the above is meaningless to me. Explain as fully as you can, and how (if it is) it is different from other data that has caused expected use in the trace.
Back to top
View user's profile Send private message
Manshadi

New User


Joined: 31 Aug 2005
Posts: 82

PostPosted: Sat Sep 03, 2011 3:59 pm    Post subject:
Reply with quote

Sorry about poor explanation.

I mean same DBIO and same SQL statement will call by different transactions.

For example 5732 sql statement of DBIOINCT could be call by DEP or CAS transaction in same time.

Regards
Manshadi
Back to top
View user's profile Send private message
Bill Woodger

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7315

PostPosted: Sat Sep 03, 2011 5:11 pm    Post subject: Reply to: Same SQL Statement Number in Omegamon Trace (DB2 Z
Reply with quote

OK. Now I'm walking on air waiting to do a "Wile E Coyote".

Obviously the SQL that is at that original statement does not change, and then change back again for the next process, unless everything has gone to pot.

So, is there a way that one SQL statement presented to DB2 will cause others to be generated to satisfy the requirement that you are aware of? That matches the statements you have seen in the trace?

If not

Code:
_____...
    !   .
    !    .
    !    .
    !   \¦/
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2 All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts WER268A OUTREC STATEMENT : SYNTAX E... frozenblood87 SYNCSORT 12 Sat Aug 26, 2017 9:45 pm
No new posts Suppress value reported by BREAK in D... Learncoholic DFSORT/ICETOOL 3 Wed Aug 16, 2017 6:03 pm
No new posts Profile changed to NUMBER ON STD (fro... Martylin TSO/ISPF 1 Thu Aug 03, 2017 9:14 am
No new posts ON 2 AND EVERY 1 - Statement ??? UmeySan COBOL Programming 2 Tue Jul 25, 2017 1:20 pm
No new posts Trace in CLIST PANEL cvnlynn CLIST & REXX 1 Thu Jun 22, 2017 11:06 pm

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us