Review the product documentation. There are topics that specifically deal with how you should be calling your DMP jobs if you are not running them interactively.   Regardless, check a few things: Make sure that each call by your scheduler to run the job didn't spawn a new process that is taking up system resources If your job is accessing data, make sure that your queries are running as you would expect. You can turn on more verbose levels of logging to see database interaction or you can monitor that in your database log. There are logging options you can set that will generate what are called node profile metrics. These logs will tell you how long each node is processing rather than the sum for the entire job. This is also in the documentation. Ron ... View more

@sht You might be looking for Proc HTTP. http://support.sas.com/resources/papers/proceedings16/SAS6363-2016.pdf http://documentation.sas.com/?docsetId=proc&docsetVersion=9.4&docsetTarget=n197g47i7j66x9n15xi0gaha8ov6.htm&locale=en   ... View more

This SAS note might be helpful: http://support.sas.com/kb/58/807.html     ... View more

Hi,   Thank you for your valuable feedback.   Actually I dont have any idea about DF data management studio and process jobs.   ... View more

Not sure if this is the issue but I have this problem from time to time and it is always my automated cloud backup creating the issue. I often have to put it to sleep for a few hours while working on SAS. ... View more

HI: You posted this question in a forum for SAS Studio. It is possible, but highly unlikely that people in this forum ever use DataFlux DFPowerStudio. If you want to post this question in a more appropriate forum, I suggest the SAS Data Management forum, which is specifically aimed at DI Studio and DF Studio users: https://communities.sas.com/t5/SAS-Data-Management/bd-p/data_management cynthia ... View more

Hi SHT,   Reload on restart is a feature on VA 7.3. From the VA 7.3 administrators guide:   Note:The reload is driven by the LASR table object’s association to a LASR library that supports reload-on-start. That LASR library must be associated with a data provider library that contains a backing store copy of the original source data.   How to Enable Reload-on-Start   To enable reload-on-start, use either of the following methods.   SAS Management Console 1. In SAS Management Console, right-click on a LASR library, and select Properties.   2. On the Options tab, in the Data provider library field, specify a Base SAS library. The specified library functions as the backing store for participating tables.   3. On the Extended Attributes tab, set attributes as follows: VA.ReloadOnStart.EnabledYes VA.ReloadOnStart.TableDefaultYes VA.ReloadOnStart.MethodSelective (Optional) To selectively exclude a LASR table from participation, set VA.ReloadOnStart.Enabled to No on the table’s Extended Attributes tab. --Simon   ... View more

I don't think 4GB is exceptionally large.  The dataset we were using was well over 16 GB on a non-distributed server.   Check if the LASR server has any data that can be removed so your dataset has more space to work.  Many times I see people load multiple copies of the same dataset with a few minor changes.  They don't remove the downlevel datasets - so you will see   Test_data_V1, Test_Data_v2, Test_data_v3, etc.        You might see if you can reduce the size of the dataset.   Reduce the size of the character fields.  Use PROC CONTENTS to review the length.  For instance, we had a field that had survey responses that was set to a length of 50 and the responses were "Yes" and "No".  We reset that size to 8.   Can any columns be removed?  For instance, some people have multiple date fields and the only difference is the formatting.  Here's a blog post where I talk about how to duplicate the values and use formatting inside SAS VA.   We were able to reduce the dataset size nearly in half using this techniques.   ... View more

Hi, I want size in number of bytes.   OS is windows7 ... View more