I have a focexec that I would like to incorporate into a Dashboard. The idea is that the user brings up an html page in Dashboard, specifies values for a few parameters, and then clicks on the Submit button and the job gets submitted as a batch run. The user comes by later to get the file of results.

So, I have an html page built in MRE that performs a IBIF_ex run for the process, and all runs well. The page waits, and upon completion I get the text from the run and the output file appears where it's supposed to.

My concern is that some of these runs will take an hour or more, so I'd like to have it submitted to the queue and just give the user a page indicating that the process got started. Sounds easy, but I can't find a parameter setting to submit it batch instead of on-demand. What I have so far:

[INPUT TYPE='hidden' name='IBIF_ex' value="00_complete_cdc_extraction_flow.fex">
[INPUT TYPE='hidden' name='servername' value="spec">
[INPUT TYPE='hidden' name='IBIC_server' value="I-WAY">
[INPUT TYPE='hidden' name='appbx' value="1">
[INPUT TYPE='hidden' name='IBIAPP_app' value="cdc_extracts">
[input type='hidden' name='IBIMR_random' value=''>
[script>
document.form.IBIMR_random.value = Math.random();
[/script>
[INPUT TYPE='submit' NAME='Submit' VALUE='Submit'>

Can anyone clue me in about what I need to add to turn this into a send-and-forget submission?

J.

Can you not right click on your report option from MRE and select "Run only as deferred report". That will run your report in defer mode only.

Thanks
Sayed

Thank you for your response.
This is not an MRE report. It is a self-serve focexec and needs to remain that way. I need to present it through MRE for security but run it outside of MRE.

You should be able to add an additional input value to get this to run deferred:

<INPUT TYPE='hidden' name='IBIMR_defer' value="defer">

In that case it cannot be done out of the box. you have to figure out and create the enitre process your self. WebFOCUS Deferred reports are for MRE/CUS Reports Only.

How about creating a focexec in MRE that says
-MRNOEDIT -INCLUDE 00_complete_cdc_extraction_flow

Then it grabs the code from the server (as long as it's in the server's apppath), but it still appears to be an MRE fex and can be run using the deferred option.

This is also a technique that I have used to allow for drilldown from an MRE procedure to a server procedure. Extra fex required, but it's so simple and solves the whole problem. You are, in essence, converting a server fex to an MRE fex, but you only have to maintain code in one place. The MRE fex is merely a spot reference to the server fex.

This message has been edited. Last edited by: Darin Lee,

I like it. I can put all of my Data Migrator flows right onto the dashboard for end users to run as they please that way.

Thanks!

Umm, isn't that kind of scary? I know I wouldn't want my users running most of our DM flows at their leisure. On table contains data as of yesterday and other contain current data?

Anyway, glad you found something you could use.

In order to run flows thru the DataMigrator server (so that output is written to the DataMigrator log and if specified an email is sent on completion and/or failure) instead of executing the flow directly using EX it should be run using EX CMASAP specifying the flow name and other paramaters. The syntax is documented in the DataMigrator Users Guide.

John_Edwards,

The Dialogue Manager DSTRUN function, inoked as "-SET &SUBERR=DSTRUN(,,,,,,,,,,,,,,,,,)" [yes, it has 17 parametrers] works very well in any *.fex (MRE or SelfServ) to submit for execution any ReportCaster schedule.

DSTRUN is documented with an execution example in "WebFOCUS-7, ReportCaster API Developer's Reference" (DN4500694.0206), Appendix A. ReportCaster API Subroutines, Page A-30.

Just make a simple MRE procedure that uses this function for each dashboard option to submit the appropriate job with any needed parameter values. After the submission, give user feedback with a

TABLE FILE ... END 

that queries any available table with

 WHERE READLIMIT=1   

and contains only a HEADING section to display the desired message (the report body has to exist so include

 PRINT <anyfield> NOPRINT  

).

The RCaster job you initiate has it's 'Enabled' property unset so it never gets run except by the use of DSTRUN. When run, it sends the report to wherever you want the user to find it.

Chris

This message has been edited. Last edited by: cburtt,