Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     SQL Translator - Capturing Focus Table Commands

Read-Only Read-Only Topic
Go
Search
Notify
Tools
SQL Translator - Capturing Focus Table Commands
 Login/Join
 
Gold member
posted
I know it's possible to capture the SQL generated by WebFOCUS when using a TABLE request directly against a RDBMS, but is it possible to do the reverse. In other words, see how SQL Translator translates SQL commands into WebFOCUS TABLE commands?


WF 8.1.05, Windows Server 2012 R2
 
Posts: 50 | Registered: March 26, 2004Report This Post
Expert
posted Hide Post
I don't see where SQL Translator translates SQL commands into WebFOCUS TABLE command. Aren't we bypassing WebFOCUS when using SQL?


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
Gold member
posted Hide Post
It's my understanding that WebFOCUS translates SQL entered thru the SQL Translator (hence the name) into TABLE commands because the data source is actually a FOCUS table.

SQL
SELECT *
FROM ANY_FOC_TABLE
WHERE ...
END


WF 8.1.05, Windows Server 2012 R2
 
Posts: 50 | Registered: March 26, 2004Report This Post
Expert
posted Hide Post
Yep, you're right.


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
Master
posted Hide Post
SQL
SELECT * 
FROM NEW_PROJECT 
WHERE PRJ_PROJECT_ID = 'N0110';
FILE XYZ
END
-RUN
DOS TYPE XYZ.FEX
-EXIT


Here is the table request created

SET COUNTWIDTH=ON                                                               
-SET SQLERRNUM = 0;                                                             
DEFINE FILE                                                                     
NEW_PROJECT TEMP                                                                
SQLDEF01/YYMD MISSING ON NEEDS ALL = PRJ_PLAN_START;                            
SQLDEF02/YYMD MISSING ON NEEDS ALL = PRJ_PLAN_FINISH;                           
SQLDEF03/YYMD MISSING ON NEEDS ALL = PRJ_ACTUAL_START;                          
SQLDEF04/YYMD MISSING ON NEEDS ALL = PRJ_ACTUAL_FINISH;                         
SQLDEF05/YYMD MISSING ON NEEDS ALL = PRJ_FROZEN_DATE;                           
SQLDEF06/YYMD MISSING ON NEEDS ALL = PRJ_CLOSE_DATE;                            
SQLDEF07/YYMD MISSING ON NEEDS ALL = PRJ_CANCEL_DATE;                           
SQLDEF08/YYMD MISSING ON NEEDS ALL = PRJ_APPROVED_DATE;                         
END                                                                             
TABLEF FILE NEW_PROJECT                                                         
PRINT FOCLIST PRJ_PROJECT_ID PRJ_NAME PRJ_STATE PRJ_OBJVERSION PRJ_ACCESS_ON_OFF
   PRJ_DESCRIPTION SQLDEF01 AS 'PRJ_PLAN_START' SQLDEF02 AS 'PRJ_PLAN_FINISH'   
  SQLDEF03 AS 'PRJ_ACTUAL_START' SQLDEF04 AS 'PRJ_ACTUAL_FINISH' SQLDEF05 AS    
  'PRJ_FROZEN_DATE' SQLDEF06 AS 'PRJ_CLOSE_DATE' SQLDEF07 AS 'PRJ_CANCEL_DATE'  
  SQLDEF08 AS 'PRJ_APPROVED_DATE' PRJ_MANAGER PRJ_CUSTOMER_NO                   
  PRJ_CUSTOMER_PROJECT_ID PRJ_CALENDAR_ID PRJ_PROGRAM_ID PRJ_CURRENCY_TYPE      
  PRJ_PROBABILITY_TO_WIN PRJ_CUSTOMER_ORDER_ID                                  
 WHERE ( PRJ_PROJECT_ID EQ 'N0110' ) ;                                          
ON TABLE SET CARTESIAN ON                                                       
ON TABLE SET ASNAMES ON                                                         
ON TABLE SET HOLDLIST PRINTONLY                                                 
                                                                                
END                                                                             
-RUN                                                                            
-SET SQLERRNUM = &FOCERRNUM;                                                    
DEFINE FILE                                                                     
NEW_PROJECT RESTORE                                                             
END                                                                             
-IF &SQLERRNUM GT 0 GOTO SQLEXT01;                                              
-SET SQLERRNUM = &FOCERRNUM;                                                    
-IF &RETCODE   GT 1 GOTO SQLEXT01;                                              
-IF &RETCODE   LT 0 GOTO SQLEXT01;                                              
-IF &FOCERRNUM GT 0 GOTO SQLEXT01;                                              
-SQLEXT01                                                                       
-IF &SQLERRNUM GT 0 GOTO SQLFIN;                                                
-SQLFIN                                                                         
POSTSTAT FOCERRNUM &SQLERRNUM                                                   
-* End of SQLTRANS Generated FOCEXEC                                            



Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2
Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
 
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006Report This Post
Expert
posted Hide Post
You can enable traces via WF Server Console > Diagnostics > Traces > Enable Traces.

Run the SQL SELECT statement and then take a look at the trace file from the same window as above.

Among the hundreds of lines generated by the trace are these juicy tidbits:

SQL SELECT * FROM CAR

generates this:

sqtrn2: SQL from manipulated parse tree
sqtrn2: SELECT * FROM CAR  ;
...
sqtrn2: SQL from J-Tree
sqtrn2: SELECT * FROM CAR  ;
...
sqtrn2: SQL After View Substitution
sqtrn2: SELECT CAR.COUNTRY , CAR.CAR , CAR.MODEL , CAR.BODYTYPE , CAR.SEATS ,
sqtrn2:  CAR.DEALER_COST , CAR.RETAIL_COST , CAR.SALES , CAR.LENGTH , CAR
sqtrn2: .WIDTH , CAR.HEIGHT , CAR.WEIGHT , CAR.WHEELBASE , CAR.FUEL_CAP , CAR
sqtrn2: .BHP , CAR.RPM , CAR.MPG , CAR.ACCEL , CAR.WARRANTY , CAR.STANDARD
sqtrn2:  FROM CAR ;
...
sqtrn2: Fully qualified SQL
sqtrn2: SELECT SQLCOR01.COUNTRY , SQLCOR01.CAR , SQLCOR01.MODEL , SQLCOR01
sqtrn2: .BODYTYPE , SQLCOR01.SEATS , SQLCOR01.DEALER_COST , SQLCOR01.RETAIL
sqtrn2: _COST , SQLCOR01.SALES , SQLCOR01.LENGTH , SQLCOR01.WIDTH , SQLCOR01
sqtrn2: .HEIGHT , SQLCOR01.WEIGHT , SQLCOR01.WHEELBASE , SQLCOR01.FUEL_CAP ,
sqtrn2:  SQLCOR01.BHP , SQLCOR01.RPM , SQLCOR01.MPG , SQLCOR01.ACCEL ,
sqtrn2:  SQLCOR01.WARRANTY , SQLCOR01.STANDARD  FROM CAR SQLCOR01 ;
...
prput: line is 80 bytes, line:
TABLE FILE CAR

message length = 80
prput: line is 80 bytes, line:
PRINT COUNTRY CAR MODEL BODYTYPE SEATS DEALER_COST RETAIL_COST SALES LENGTH

message length = 80
prput: line is 80 bytes, line:
WIDTH HEIGHT WEIGHT WHEELBASE FUEL_CAP BHP RPM MPG ACCEL WARRANTY STANDARD
...
prput: line is 80 bytes, line:
ON TABLE SET CARTESIAN ON

message length = 80
prput: line is 80 bytes, line:
ON TABLE SET ASNAMES ON

message length = 80
prput: line is 80 bytes, line:
ON TABLE SET HOLDLIST PRINTONLY

message length = 80
prput: line is 80 bytes, line:
END


Note that turning traces on with the method above turns it on for all requests. There's probably a method of turning on traces from within the fex so that only that fex is traced.


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
Expert
posted Hide Post
John's method is nice and clean.


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
Gold member
posted Hide Post
Use the following to get the table file syntax that was generated. Keep in mind that this is taking the SQL and converting it to focus and will do this regardless of data type.

SET TRACEOFF=ALL
SET TRACEON=SQLTRANS/1/CLIENT
SET TRACEUSER=ON


SQL passthru will not translate to focus since you are telling it to ignore the sql. SQL passthru only happens if you specifically state the engine such as

SQL SQLMSS
select * from Northwind.dbo.orders;
END

The following would be translated as it would need to read the master file description and would then be retranslated back to SQL to pass on to the RDBS.
SQL
select * from ORDERS;
END

You can use the following to get the FOCUS to SQL translation.

SET TRACEOFF=ALL
SET TRACEON=STMTRACE//CLIENT
SET TRACEUSER=ON



Windows: WF 7.6.2: SQL Server 2008 R2
 
Posts: 86 | Location: Chicago | Registered: August 03, 2007Report This Post
Gold member
posted Hide Post
Thanks everyone, that will come in very handy.


WF 8.1.05, Windows Server 2012 R2
 
Posts: 50 | Registered: March 26, 2004Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     SQL Translator - Capturing Focus Table Commands

Copyright © 1996-2020 Information Builders