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.
There is a new SLEEP command. It was available in 764 which you have:
Suspending Execution How to: Suspend Execution for a Specified Number of Seconds You can suspend execution of your WebFOCUS application for a specified number of seconds using the SLEEP function. This is most useful in Dialogue Manager when one process cannot begin until another process has started. For example, you can start a FOCUS Database Server and wait until the server is started before initiating a client application. Syntax: How to Suspend Execution for a Specified Number of Seconds SLEEP(delay, outfld); where: delay Numeric Is the number of seconds to delay execution. The number can be specified down to the millisecond. 46
It goes in a focexec. You could put it in the report and then see if you can't figure out using operating system commands or whatever to figure out if your load is done.
I do this. I make first one KILL_RPC = 'Y' when date not equal so next one not run. Next job is make file "up to the minute". Last job run report. This help you no?
Kofi
Client Server 8.1.05: Apache; Tomcat;Windows Server 2012 Reporting Server 8.1.05; Oracle; MS SQL; Windows Server 2012
In actual fact SLEEP has been around for about as long as Dialog Manager, just not documented.
The difference between the original SLEEP and the newer SLEEP function is SLEEP is used only in DM and so is great if you want to loop to wait for another process to finish or you are waiting for availability of a resource.
The advantage is that if you repeatedly loop while waiting you will very quickly be running 100% cpu using SLEEP means you do not.
When used in DM it only requires the number of seconds as a parameter
-REPEAT ENDREPEAT
-* Whatever your test or check
! STATE C:\TEMP\mydata.ftm
-IF &RETCODE EQ 0 GOTO WakyWaky;
-* sleep for 10 seconds and recheck
SLEEP 10
-ENDREPEAT
-WakyWaky