Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Data Stage LOG detail question

Status
Not open for further replies.

donafran

Programmer
Jul 11, 2002
71
0
0
US
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

++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
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


 
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 !
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top