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.



Read-Only Read-Only Topic
Go
Search
Notify
Tools
SEGNAME=SQLOUT
 Login/Join
 
<Shyam L>
posted
Hi,
We are running a procedure through a scheduler and it dumps the output in Excel format in Report Library. When we try to open the Excel from the Library, the contents of the excel is displayed as "SEGNAME=SQLOUT" instead of the report output.

What can be the reason? The scheduler showed the job as success. We are using SQL Passthru in the procedure for data retrievel.
Can it be a failure in retrieveing the records from Database (DB is DB2)? In that case will the job get through as success?
 
Report This Post
TexasStingray
Master
posted Hide Post
If it runs correctly thru a browser and not caster it could be a securty issue. I would look at the id that the job is running with thru the browser and thru caster. make sure they are the same make sure that the last table request the the formated output not SQL.

Hope this helps or points you in the right direction




Scott

 
Posts: 865 | Registered: May 24, 2004Report This Post
<Shyam L>
posted
Hi TexasStingray,
thanks for the post.
I forgot to mention that the same job ran successfully from RC many times but one time it gave this message. ID is the same from both browser and RC.

Thanks,
Shyam L
 
Report This Post
<Shyam L>
posted
Further, the Report Caster log for this particular report has:
User: userid
Procedure: id
Schedule ID: id
Start Time: start time
End Time: end time
Starting worker thread
Starting task: Report Name
Task type: MR Standard Report
Retrieving MR report: report name
Connecting to server EDASERVE with execution id
Executing focexec.
SYSPRINT.SCR
SYSPRINT.SCR
SYSPRINT.SCR
SYSPRINT.SCR
SYSPRINT.SCR
SYSPRINT.SCR
SYSPRINT.SCR
Task finished.
DISTRIBUTED TO report library

Whereas a normal log which went into success will not have SYSPRINT.SCR.
 
Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic


Copyright © 1996-2020 Information Builders