I'm testing SASUnit 2.0 (SASUnit - Browse Files at SourceForge.net) with SAS Studio.
I've an error when running for the first time %reportsasunit :
MPRINT(REPORTSASUNIT._REPORTLOGHTML._CHECKLOG): RUN;
ERROR: Physical file does not exist, \\xxxx\xxxx\sasunit\sasunit_example\output\log\000.log.
NOTE: The SAS System stopped processing this step because of errors.
MPRINT(REPORTSASUNIT._REPORTLOGHTML): ;
I've no error when running %reportsasunit another time due to "IF tsu_lastinit > tsu_lastrep OR &o_force. THEN DO;" condition in %reportsasunit macro (000.log is not used when running %reportsasunit a second time).
I noticed that this behaviour could be linked to %initsasunit macro update compared to SASUnit 1.7 version. This Code below is now related to this condition "%IF (&g_runMode. = SASUNIT_BATCH) %THEN %DO;"
%_runProgramSpawned(i_program =&l_work./check_spawning.sas
,i_scnid =000
,i_generateMcoverage=0
,r_sysrc=l_sysrc
,i_pgmIsScenario =0
);
--> There's no "000.log" file created when "_runMode" is different than "SASUNIT_BATCH" with SASUnit 2.0.
Did someone else have this same problem ?
Thanks in advance for your answers.
