DI Studio (4.902) checkpoint does not delete all tables after processing

[Anne_A]

Hi all,

Using DI Studio 4.902, I'm experimenting with the checkpoint functionality and I notice that some of the datasets created in the checkpoint directory/library remain there even after the job has executed successfully. Does someone know:

• whether this is till the case in the latest version (4.905 I believe)
• what is the point of keeping these datasets in the file system (where they take space) even after / when the job has completed successfully?

Many TIA

Anne.

[LinusH]

I haven't used this functionality, so a bit of dry swimming here.

I think you can control this using the CHKPTCLEAN system option.

https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/lesysoptsref/n17pilbiczto7in1o4qh96lcvkv1.htm

[Anne_A]

Thank you so much @LinusH , this seems to be just what I need. My next question however is then: how can I make that option effective in DI Studio? Each time I try I get a warning: "SAS option CHKPTCLEAN is valid only at startup of the SAS System. The SAS option is ignored". Would you happen to know where I can set that option for DI Studio? (I'm working with my own image in a virtual learning environment, so I can really experiment without impacting anybody else's work)

Many grateful thanks in advance

Anne.

[LinusH]

You need to set it up in a central location - in your configuration.

For use in DI Stdio (and other interactive applications like Enterprise Guide), change the config under WorkspaceServer.

If you want this to applied in batch, change the config under SASApp.