Hi all
I have a fex which uses DSTRUN to kick off a schedule. The schedule in turn saves a file in Report Library.
The problem is that DSTRUN should be executed only after the file has been created (creation of file is a part of the same fex).
Here's what my fex looks like:

FILEDEF EXCELOUT DISK &TEMP_PATH
TABLE FILE ABC
PRINT *
ON TABLE HOLD AS EXCELOUT FORMAT EXL2K
END

********This is where I want DSTRUN to hold on till the above file is created

-SET &SUBERR=DSTRUN(
- 'usr', 7,
- 'pwd', 7,
- 'srverort', 16,
- &SCH_JOB_ID,12,
- ' ', 0,
- 3,
- 'ownr', 7,
- ' ', 0,
- ' ', 0,
- 'I4') ;

-RUN

----------
When the excel is small, the above code works fine and the excel gets saved to Report Library. Whereas, if the excel takes a lot of time to get created, DSTRUN triggers off the schedule and the excel doesn't get saved to Library.

I have tried using STATE/UNIX ls/SLEEP etc. But DSTRUN always gets executed before the excel creation is complete.

Any suggestions on how to deal with this situation?

Thanks
Syed

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

Try:

FILEDEF EXCELOUT DISK &TEMP_PATH
TABLE FILE ABC
PRINT *
ON TABLE HOLD AS EXCELOUT FORMAT EXL2K
END
-RUN   <-- Add this *before* DSTRUN is executed

-SET &SUBERR=DSTRUN( ...

Adding -RUN makes the stacked commands to execute before moving forward to the next step. Hopefully it'll work as you need.

-RUN is the way to go nsjden !
I just tried it and it seems to be working fine.

Thanks much for the suggestion.

Syed

You're welcome Syed. I'm glad it helped.

quote:

-RUN is the way to go nsjden !
I just tried it and it seems to be working fine.

It is great that folks get a solution to their question, but I sometimes wonder if they realise why the suggestion works?

Syed, Do you comprehend why the addition of -RUN works or are you just happy that you have a solution? I ask only because if you don't understand the reason, and you hit the underlying problem again, you may ask the same basic question again.

T

Hey Toni
As much as I understand, -RUN forces execution of all WebFOCUS commands/code before continuing with the rest of the procedure. In a way it acts like a checkpoint, ensuring execution before the next command is executed. And that's exactly what I was looking for - something that would complete the creation of excel file (ON TABLE HOLD AS EXCELOUT FORMAT EXL2K) before DSTRUN was fired.
Since FOCUS is a procedural language, execution of a code in WebFOCUS does not require the execution of its previous stack of commands.

Let me know if there's more to it.

Thanks
Syed

Hi Syid,

Just wanted to make sure that you understood why the -RUN was required. It looks like you did some digging but it's not always obvious that the answer is understood.

T

Sure. I should have mentioned this explanation in my previous post - I got so excited with the solution, that I quickly wanted to get the ball rolling

But thanks - I'll keep this in mind...

Cheers
Syed

quote:

Adding -RUN makes the stacked commands to execute before moving forward to the next step

I had provided Syed with some explanation as to why -RUN was most likely the solution he needed. It may not have been the most technical description of what it does but that's what the product manuals are for, is it not?.

Anyway, Tony has raised a valid point which is always good to keep in mind. It's more important to understand the conceptual logic behind any solution before worrying too much about specific syntax which can always be looked up in a manual.