i'm currently using a Job within SAS DI Studio that basically consists of a User Written Code with a SAS Macro Call that transforms input data and pushes them to another system via a sequence of Webservice Calls.
Now what i experienced is that for larger input data sets the SAS DI Job seems to be stuck im limbo when executed via DI Studio itself, i.e. the Job does not terminate and also doesn't do any more Webservice Calls. If i generate a log file, the log is also seems to be cut off in the middle of processing - without any technical issues indicating a technical problem.
This behaviour is replicable with large enough input data that cause the job to run for more than about three hours. Interesting enough, if i just execute the SAS Macro Call within SAS EG (without running the UWC within DI Studio), it runs perfectly without any issues. Hence my assumption is that DI Studio itself contains some kind of configuration/limilation that creates issues for longer running Jobs.
Does anyone ever experienced something similar or know if there are any configurations my admin team can do to prevent the SAS DI Jobs from getting stuck?
Cheers and i'm also happy to provide any background info on this issue,
Maybe this isn't really helpin, but DI Studio is not really designed to execute prodcution (which could be lon running). My suggestoin is to deploy the job for scheduling, and then execute from a script or SAS Managamnt Console. This will make the job run under the Batch server, rather than the Worksspace Server.
Registration is open! SAS is returning to Vegas for an AI and analytics experience like no other! Whether you're an executive, manager, end user or SAS partner, SAS Innovate is designed for everyone on your team. Register for just $495 by 12/31/2023.
If you are interested in speaking, there is still time to submit a session idea. More details are posted on the website.