@ChrisW75 What's the appropriate design depends of course always on the details as well as on the maturity of your client as they must in the end also be able to maintain what you leave behind. From what you describe I'd consider a design where each program is "self-contained" and can run on it's own. I'd then implement a control table where I list the programs together with possible parameters to be passed in. My master wrapper program would then process this control table and execute the "child" programs in the control table (either as %includes or via %systask). Such an approach should make it simple to add or remove additional programs and you don't need to change existing production code but you add/remove records from a control table - which in a "big" environment normally allows for a simpler change process and shorter turnaround cycle. ... View more

I know my request might sound strange in the context you presented. I am using the scheduler in an other context, which is to replicate a "batch submit" in traditional SAS. The reasoning for this utilisation is to get a date/time stamp for my logs and output that does reflect run time instead of start of EG session. Therefore, someone will be sitting at the PC when the sas project actually runs. Perhaps an option could be set-up to choose weither to prompt or not, with default set as No. I guess its not present in the current version... Thanks for helping my clarifying my question Isa ... View more