I open the EG project on my laptop and access the SAS Instance and the SASUNIT installation on a Red Hat Server. SASUNIT_ROOT and SASUNIT_PROJECT_ROOT are on the Server.
On starting initSASUnit with the following parameter, I get the error mentioned below.
The error occurs only if I specify a value DEBUG, INFO or ERROR. If the parameter are empty, it works and I am able to execute my testcases.
.
ERROR: Level can not be changed for the logger "App.Program.SASUnit".
ERROR: An error occurred while executing function LOG4SAS_LOGGER referenced by the %SYSFUNC or %QSYSFUNC macro function.
Using a local Windows installation works with this parameter.
Running SASUNIT in batch on Linux works as well.
What is the normal behaviour?
Thank you very much.
Kind regards
Albert Meyn
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.
This email may contain confidential and/or privileged information. If you are not the intended recipient (or have received this email in error) please notify the sender immediately and destroy this email. Any unauthorized copying, disclosure or distribution of the material in this email is strictly forbidden.
My expectation would be that it should run in any of these combinations.
The configurations is obviously correct.
I had a short look into SAS Notes and SAS documentation.
First guess is that SAS start under Linux is differently configured within SAS.
Immutabilityof the logger is explicitly set to FALSEto be able to change the logging level.
Perhaps it is not possible to change the logging level under Linux.
My next step is to recreate this error in our environments and then come back to you.
This may take some time.
Kind regards
Klaus Landwich
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think I found an explanation. In Batch the logger are created in the logconfig.xml.
In interactive mode this is not present. So SASUnit tries to change the log level of an non existing logger.
Here windows seems to act differently.
Perhaps we should get rid of the logconfig.xml-files and generate all loggers in the programs.
Thanks for aour post.
Kind regards
Klaus Landwich
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear All,
I open the EG project on my laptop and access the SAS Instance and the SASUNIT installation on a Red Hat Server. SASUNIT_ROOT and SASUNIT_PROJECT_ROOT are on the Server.
On starting initSASUnit with the following parameter, I get the error mentioned below.
%initSASUnit(
i_root =&SASUNIT_PROJECT_ROOT.
,io_target =&SASUNIT_PROJECT_ROOT./doc/sasunit/en
,i_overwrite =1
,i_project =SASUnit Example project
,i_sasunit =&SASUNIT_ROOT./saspgm/sasunit
,i_sasautos =saspgm
,i_testdata =dat
,i_refdata =dat
,i_doc =doc
,i_testcoverage =0
,i_verbose =0
,i_crossref =0
,i_crossrefsasunit =0
,i_language =en
,i_log4sassuiteloglevel =INFO
,i_log4sasscenariologlevel =INFO
,i_SASUnitRoot =&SASUNIT_ROOT.
,i_resourceFolder =&SASUNIT_ROOT./resources
,i_OSEncoding =wlatin1
);
The error occurs only if I specify a value DEBUG, INFO or ERROR. If the parameter are empty, it works and I am able to execute my testcases.
.
ERROR: Level can not be changed for the logger "App.Program.SASUnit".
ERROR: An error occurred while executing function LOG4SAS_LOGGER referenced by the %SYSFUNC or %QSYSFUNC macro function.
Using a local Windows installation works with this parameter.
Running SASUNIT in batch on Linux works as well.
What is the normal behaviour?
Thank you very much.
Kind regards
Albert Meyn
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.
This email may contain confidential and/or privileged information. If you are not the intended recipient (or have received this email in error) please notify the sender immediately and destroy this email. Any unauthorized copying, disclosure or distribution of the material in this email is strictly forbidden.
Dear Albert Meyn,
first of all thanks for giving SASUnit a try.
My expectation would be that it should run in any of these combinations.
The configurations is obviously correct.
I had a short look into SAS Notes and SAS documentation.
First guess is that SAS start under Linux is differently configured within SAS.
Immutabilityof the logger is explicitly set to FALSEto be able to change the logging level.
Perhaps it is not possible to change the logging level under Linux.
My next step is to recreate this error in our environments and then come back to you.
This may take some time.
Kind regards
Klaus Landwich
Dear Albert Meyn,
I think I found an explanation. In Batch the logger are created in the logconfig.xml.
In interactive mode this is not present. So SASUnit tries to change the log level of an non existing logger.
Here windows seems to act differently.
Perhaps we should get rid of the logconfig.xml-files and generate all loggers in the programs.
Thanks for aour post.
Kind regards
Klaus Landwich