yzhou2004, nice you have experience on both sides. What I am missing is experience with that including schedulers at the system programmers area. With Mainframes these are almost a pre-req to do (opc ca7 etc). The whole goal of using schedulers (job application flows) is seeing results/logs at each step so you can correct and restart easily parts without wasting too much of time. Going into testing (milo/euro) not the scheduling by triggers-time were important but running the same programs over and over again with different data to eliminate errors. That is automated testing, again flows. For fun I build an automated tool version and releasemanagement included. That was far before ISTQB did exist. Test Automation Engineering - ISTQB® International Software Testing Qualifications Board . That was a long time ago (25+trs). At the moment I am building something like but now fully focussed on SAS and build in SAS it is needed by the user groups. (They have Eguide by the way). >>> Flows are not an overkill in contrary they are one of the basic building blocks. Change your mind and use them. With Eguide flows, you can still run then individually, but also as a logical series (flow). It will stop the flow when some code is incorrect. You still have all results/log of each step. Huge dataset SPDS 100M 100+ columns look to me normal sized datasets. Time is changing and the sizing matters is just what you are seeing form day to day work. Working at a bank and installing software on your own desktop. That is a bad signal as desktop in those environments are normally closed. Only when following some release/test processes you get those updated. It looks you are in some isolated area. The guy responsible for your SAS installation should have tested and validated this all including performance and UAT testing. Never mind there are a lot of possible pitfalls at the system programming level on the Windows and Linux that are far beyond the SDW setup approach. Eg locking on files can behave different that is no real bug but a misfit of the in house desktop policies in house Linux policies and the SAS SDW ideas. That misfit of thinking by the way is a major design bug of the SDW.
... View more
