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.
If you're using WebFOCUS, you can turn SQL traces on to see the SQL generated by WebFOCUS, along with any relevant messages from the SQL translator.
(Always add this at the top of your code if you're accessing DBMS tables:
-*-- Set up SQL tracing - as provided by Francis Mariani on FocalPoint ---------
-*-- Deactivate SQL tracing --------------------------------
SET TRACEOFF = ALL
-*-- Show Commands and data exchange between the -----------
-*-- physical and the logical layers of the data adapter
-*SET TRACEON = SQLCALL
-*-- Enable Trace for the SQL Translator -------------------
SET TRACEON = SQLTRANS
-*-- Show SQL statements -----------------------------------
SET TRACEON = STMTRACE//CLIENT
-*-- Show Optimization information -------------------------
SET TRACEON = SQLAGGR//CLIENT
-*-- Show SQL generated statement trace --------------------
-*SET TRACEON = STMTRACE/1/CLIENT
-*-- Show SQL generated sub-statement trace ----------------
-*SET TRACEON = STMTRACE/2/CLIENT
-*-- Disable the trace stamp (Date/Time etc) ---------------
SET TRACESTAMP = OFF
-*-- Set trace line wrapping - # of characters -------------
SET TRACEWRAP = 78
-*-- Activate SQL tracing ----------------------------------
SET TRACEUSER = ON
-RUN
(Leave the commented lines in comments as these trace statements generate a lot on unnecessary lines)
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
just before your TABLE FILE and leave it there until you have made the code efficient. This command "previews the format of a report without actually accessing any data".
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
And remember, IMS is not an SQL-based data base. Is there a way to turn a trace on the backend (how are you getting to IMS or are you running a reporting server on the mainframe?). You really need to see what IMS is getting. Maybe your IMS DBA, also, could help you out.
That's the result of the XRETRIEVAL=OFF - the request does not retrieve and data. If that's all you got, then it's because, as Ginny pointed out, IMS is not a SQL-based database.
You can issue any SQL request through the Adapter for IMS
Take a look at the above mentioned manual. There is some discussion of traces in IMS, but it does not seem to be SQL tracing. There are some optimization suggestions that might be interesting to look at.
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
Yes, you can issue SQL for IMS, but it wont be passthru!
Enigma,
Can you get output from each IMS table (they were called segments)?
If you can, then does your JOIN command take into account:
quote:
when you join TO an IMS database, you must join to one of the following: · A key field or secondary index in the root segment (ALIAS= IMSname.KEY, IMSname.HKY, or IMSname.SKY). · The high-order portion of a key field or secondary index in the root segment
Look at the IMS interace pdf.
Daniel In Focus since 1982 wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006
JOIN COL1 AND COL2 AND COL3 AND COL4 AND COL5 AND COL6 AND COL7 IN TBL1
TO COL1 AND COL2 AND COL3 AND COL4 AND COL5 AND COL6 AND COL7 IN TBL2 AS J1
END
I think this should work.
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
You also have to pay attention to what Danny said. Working with IMS is very tricky so it is imperative that you read the IMS Interface or adapter manual or the chapter in the Data Administration manual related to IMS. You need to be able to look at the setup for each file to make sure that the join can be done.
Or you can extract the data separately then do the join in WebFOCUS with your hold files.
it seems a bit strange to me that you have to join on 7 fields. As far as I can recall, IMS did not deal with multiple field joins. I think you should take a hard look at the masters of these 2 segments or maybe post them here. If you still are stumped, could you go the way Ginny suggested: extract, hold and then join?
Daniel In Focus since 1982 wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006