The other suggestions are great for capturing running of the program(s).Further to these suggestions you can store a timestamp before running the program and then at the end find all files newer than that timestamp to display/count the output.   For the input/output files an approach I've seen used in other languages is inline comments then generated into documentation. JavaDoc and Perl's POD are examples. SASUnit does this to produce documentation and reports. I believe they used to use DoxyGen however have switched to an internal tool.  SASUnit can be found at http://sasunit.sourceforge.net/ but their report demo isn't working so download the 1.6 release and open this file for an example: example/doc/sasunit/en/rep/pgm_basedatasets.html.   Code: /** \file \ingroup SASUNIT_EXAMPLES_PGM \brief Create base datasets for a database \version \$Revision: 451 $ \author \$Author: klandwich $ \date \$Date: 2015-09-07 08:49:43 +0200 (Mo, 07 Sep 2015) $ \sa For further information please refer to https://sourceforge.net/p/sasunit/wiki/User%27s%20Guide/ Here you can find the SASUnit documentation, release notes and license information. \sa \$HeadURL: https://svn.code.sf.net/p/sasunit/code/tags/v1.6/example/saspgm/basedatasets.sas $ \copyright This file is part of SASUnit, the Unit testing framework for SAS(R) programs. For copyright information and terms of usage under the GPL license see included file readme.txt or https://sourceforge.net/p/sasunit/wiki/readme/. */ /** \cond */ Report:   ... View more

Local DI Studio logs can be found here on windows: %APPDATA%\SAS\SASDataIntegrationStudio\4.901\ To get here press WIN+R then paste the above into the open: box and press enter.   Good luck! ... View more

Here is a run through of what we've done during development. Free and without ongoing root access (we're on linux servers)   Part 1: SVN server installation   Have svn installed by root. We're on RHEL so its readily available via yum. Decide who will run the svn "service". We're using a service account. Create svn repository: mkdir ~/svn svnadmin create ~/svn/distudiodev Configure repository by editing the svnserve.conf in ~/svn/distudiodev/conf/ turn off anon-access (forces people to use credentials) turn on password-db = passwd Configure users by editing ~/svn/distudiodev/conf/passwd Run it: svnserve --daemon --root ~/svn/ Notes: This can be done on any "server" that the clients are able to connect to. Svnserve runs by default on port 3690 which doesn't require root on linux.Could also be done on windows however that exercise is left to the reader.     Part 2: Client setup Install svn client. We are using some win32 binaries with only the .exe no gui. eg https://sourceforge.net/projects/win32svn/ Remove/rename the DI Studio cvs plugin so that svn takes priority configure DI Studio for svn In the example above repository is /distudiodev on port 3690 with type SVN     ... View more

sorry to bump this as just wanted to add what I found that finally worked for me in similar circumstances:   http://support.sas.com/kb/20/784.html   data _null_; length data $1; INFILE in_filename recfm=n; file out_filenmae recfm=n mod; input data $char1. @@; put data $char1. @@; run; Although this is written for STP web process it should apply when writting to another file as the _webout is similar. The secret seems to be the recfm=n and the @@s. ... View more

The source code for the SVN and CVS plugins are availble here: http://support.sas.com/rnd/gendoc/versioncontrol/43/en/   In theory these can be used to create a plugin for any other version control system (eg git). In practice I don't think it will be something I get to on the project I'm assigned to 😞 If you do get to it, please share 😄   Another alternative could be to use a hybrid of both using DIStudio to commit to SVN then scripting a "pull" from SVN into GIT. ... View more