How about these NFRs ?

I always wondered about these 2 (non-)features while using the MRE -

#1> Why is "Run Deferred" only available as a GUI right-click Context menu option and not also on the File menu while editing a fex ?

#2> How about having a Time-Completed column or an Execution-time column on the 'Deferred Report Status' window ? When trying to improve the efficiency of long-running reports, I find it distracting to keep checking this window for exact end times. Would you find it helpful to have this info for what ever purpose ?

Now, I am making these statements with what we have in 5.2. If these features have been already included in later versions, I would be glad to know.

Else, please comment on the value of having these features yourself.

Thanks so much for your input y'all.
Sandeep Mamidenna.

-------------------------------------------------------------------------------------------------
Blue Cross & Blue Shield of MS
WF.76-10 on (WS2003 + WebSphere) / EDA on z/OS + DB2 + MS-SQL
MRE, BID, Dev. Studio, Self-Service apps & a dash of fun !!

Posts: 218 | Location: Jackson, MS | Registered: October 31, 2006

Leah

Virtuoso

posted

Hide Post

quote:
I always wondered about these 2 (non-)features while using the MRE -

#1> Why is "Run Deferred" only available as a GUI right-click Context menu option and not also on the File menu while editing a fex ?

Probably because when you run deferred, it uses the 'saved' version of the fex and it doesn't always kick off right away. Run time in deferred mode is kind of hard one. If you submit it at one time, it doesn't necessarily start then. So I'd say time starts running would be good. Time completed nice to have, but the main reason I use deferred is for longer running reports.

Leah

Posts: 1317 | Location: Council Bluffs, IA | Registered: May 24, 2004

Ignored post by Leah posted

Show Post

BlueZone

Platinum Member

posted

Hide Post

Really appreciate your quick response Leah.

We use Deferred reports for long running reports too. That by definition, identifies code to be a potential candidate for improvement in efficiency. And in-turn, a need to easily be able to see the run-times, while fiddling around with the code and executing it over and over again to see the difference.

I am sure a lot us have complex routines going against vast data sources (DB2 or otherwise) on the mainframe. Hence the questions above.

Gooooooooooood day Leah !!
Sandeep Mamidenna.

Posts: 218 | Location: Jackson, MS | Registered: October 31, 2006

Ignored post by BlueZone posted

Show Post

Tony A

Expert

posted

Hide Post

quote:
#2> How about having a Time-Completed column or an Execution-time column on the 'Deferred Report Status' window ? When trying to improve the efficiency of long-running reports, I find it distracting to keep checking this window for exact end times. Would you find it helpful to have this info for what ever purpose ?

If you have a function defined in your server profile something like -

DEFINE FUNCTION ELAPSED(X/A1)
DAY/YYMD = HDATE('&YYMD','YYMD');
DATE/A6YMD = DAY;
BEGTIME/A8 = EDIT('&TOD.EVAL', '99$:99$:99');
ENDTIME/A8 = EDIT(HHMMSS('A8'), '99$:99$:99');
BEGAN/A20 = DATE | ' ' | BEGTIME;
ENDED/A20 = DATE | ' ' | ENDTIME;
-* Convert to time stamps
DATE_TIME1/HYYMDSA=HINPUT(20,BEGAN,10,'HYYMDS');
DATE_TIME2/HYYMDSA=HINPUT(20,ENDED,10,'HYYMDS');
-*Subtract the two time stamps, getting difference in seconds
ELAPSED/D12.2=HDIFF(DATE_TIME2, DATE_TIME1, 'SECOND', 'D12.2');
END

and then capture the elapsed time using something like -SET &Elapsed = ELAPSED('X'); then you can log that detail somewhere.

T

p.s. The function primarily came from the forum a while ago so acknowledgement to the Member who first produced it

In FOCUS since 1986	WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
	WebFOCUS App Studio 8.2.06 standalone on Windows 10

Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004

Ignored post by Tony A posted

Show Post

BlueZone

Platinum Member

posted

Hide Post

Thanks so much for your input too Tony.

I have actually developed a similar piece of code to capture the time of the last executed statement. I -INCLUDE it as the last step while testing such long-running programs. (Not as good as your Virtuoso-grade code here, but it still works

).

Thought it would be great to see it directly on the Deferred reports window..... right there..... without having to VIEW the report every single time. Oh well !!

Goooooooooooooood day !!
Sandeep Mamidenna

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

Posts: 218 | Location: Jackson, MS | Registered: October 31, 2006

Ignored post by BlueZone posted

Show Post

Please Wait. Your request is being processed...