×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Data Stage LOG detail question

Data Stage LOG detail question

Data Stage LOG detail question

(OP)
On my Transaction Download from the As/400 ODBC connection, I am getting 200 or so extra records than I am expecting – using job parameters as variables in my SQL where clause on the ODBC step.

If I HARDCODE the values into the WHERE clause, I get the correct number of transaction records. So I’m thinking it has to do with quotes or lack of for the character strings - -But I can’t see what is being rendered.

Is there a way to view the ACTUAL SQL that is being generated at Run Time ??

For instance –
In Data Manager, I can code WITH THE VARIABLES:

Select … … …
FROM "{$JDEDATALIB}"."F57011BZ5M"
WHERE FBTYPF='CF' AND FBDRQJ >= {$FRM_DATE}
AND FBCO='{$CAN_CODE}'

But the RUN TIME Log actually shows me the reconciliation of the values of the variables:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++
… … …
FROM "PD900DTA"."F57011BZ5M"
WHERE FBTYPF='CF' AND FBDRQJ >= 106001
AND FBCO='00101'

[PROGRESS - 03:28:44] Checking Fact Data existence
[DETAIL - 03:28:45] Fact Data found
[PROGRESS - 03:28:45] Processing Reference Data
[PROGRESS - 03:28:45] Processing Dimension Domains
[PROGRESS - 03:28:45] Processing Fact Data
[SQL - 03:28:45] truncating table

++++++++++++++++++++++++++++++++++++++++++++++++++++++++

RE: Data Stage LOG detail question

Thinking outside the box, can your DBA team capture the SQL that runs? Also, I seem to remember that there was a way to view the actual SQL in earlier versions of Data Stage. Let me look around. We have both v8 and v9 here - what version are you running?

==================================
The trouble with doing something right the first time is that nobody appreciates how difficult it was - Steven Wright


RE: Data Stage LOG detail question

(OP)
HEY !!
Just found it --
Add Environmental Variable $OSH_ECHO and set it to TRUE.
Then in your view of the Job log, look for a Statement similar to
main_program: Echo: (...)
Then DOUBLE CLICK on it for more details --
It shows you the SQL statement with the variables replaced by the actual values !

I knew that had to be a way to do this !

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close