#68 Provide testing environment for SAS 9.3 under Windows

[Andreas Mangold]

Provide testing environment on a virtual machine: Windows 7 64 bit english, SAS 9.3 64 bit english.

Currently there is a testing environement on a virtual machine. It's as stated below german Windows and german SAS9.3 (TS1M0). It's only a temporary solution until we have an english Windows machine running.

The VM is considered as a test environment. Developing is done on your local machine. When everything is fixed and tested on the local machine then the programs are copied to the virtual machine and executed. Preferrebly this will be done via Enterprise Guide. I will provide a store process on the VM to do that.
Ideally there is no need to connect via remote desktop. SASUnit can be started vie SEG and the result can be access via a share on the VM.

For each SASUnit developer there is a local user SASUnit_\<HMS-ShortName> (like SASUnit_KL). This user can also access via remote desktop.

There is a special folder that holds all official SASUnit releases:

• C:\AA_projekte\SASUnit\SASUnit_vxx.xxx.

To simplify testing each SASUnit developer has a seperate testing folder:

• C:\AA_Projekte\SASUnit\SASUnit_Test\SASUnit_\<family name>.
  There you are free to copy your local SASUnit version for testing.

Testing is currently done on HD1PCMS0070. For any further informtion like shared folders, PWDs, etc. consult the HMS wiki.

If there are any questions or inconveniences on HD1PCMS0070 feel free to contact me (Klaus Landwich)

The English Windows machine (HD1PCMS0091) is running as a VM. It's setup is identical to the setup of HD1PCMS0070 (see above). It has installations of several SAS versions.

For any further detail consult the HMS Wiki, there you can find a page with all VM for SASUnit (Search for "SASUnit VM").

[Klaus Landwich]

Because there is no Englisch windows available, we dicided to first test the combination Windows/German and SAS/German.
In particular it's Windows 7 64-Bit and SAS 9.3 TS1M0 64-Bit

[Klaus Landwich]

DoxyGen is installed in version 1.8.2 the latest I could get.

[Klaus Landwich]

The combination Windows 7 64 bit English, SAS 9.3 64 bit English will be tested in a later phase

[Andreas Mangold]

When reports are generated in german or in english, they should go into doc/de or doc/en

The "_I" should be deleted from the names of the environment variables, it should be used only for macro parameter names.

[Klaus Landwich]

Curretnly there is still a doxygen folder underneath doc. I got three possibilites for the foldernames:

First:

• doc/doxy
• doc/sasunit/de
• doc/sasunti/en

Second:

• doc/de/sasunit
• doc/doxy
• doc/en/ssunit

Third:

• doc/de
• doc/doxy
• doc/en

As long as we still need the DoxyGen-tool I would suggest the first one. When we integrate the DoxyGen functionality we can switch to the third one.

What's your opinion?

[Andreas Mangold]

First one is OK.

[Klaus Landwich]

Obviously we also need an OS-Variable for the SAS version, because this is also part of the name of the config files.

To test this new parameter I added skripts for starting SASUnit under SAS 9.2 that's still on my development machine. They are tested under WIN7 64-bit and SAS 9.2 32-bit. The scripts work fine. SASUnit results I haven't checked in detail yet.

In addition I provided skripts for LINUX. They are tested under UBUNTU 12.04 LTS an should be valuable as templates. I still got problems with the sub-processes started by SASUnit, they can't find the config file. SASUnit does! But that must be solved by someone that knows LINUX/UBUNTU better than I.

All these changes will be checked in today.

[Klaus Landwich]

• Description has changed:

Diff:

--- old
+++ new
@@ -1 +1,18 @@
 Provide testing environment on a virtual machine: Windows 7 64 bit english, SAS 9.3 64 bit english
+Currently there is a testing environement on a virtual machine. It's as stated below german Windows and german SAS9.3 (TS1M0). It's only a temporary solution until we have an english Windows machine running.
+
+The VM is considered as a test environment. Developing is done on your local machine. When everything is fixed and tested on the local machine then the programs are copied to the virtual machine and executed. Preferrebly this will be done via Enterprise Guide. I will provide a store process on the VM to do that.
+Ideally there is no need to connect via remote desktop. SASUnit can be started vie SEG and the result can be access via a share on the VM.
+
+For each SASUnit developer there is a local user SASUnit_\<HMS-ShortName\> (like SASUnit_KL). This user can also access via remote desktop.
+
+There is a special folder that holds all official SASUnit releases: 
+-  C:\\AA_projekte\\SASUnit\\SASUnit_vxx.xxx.
+
+To simplify testing each SASUnit developer has a seperate testing folder: 
+-  C:\\AA_Projekte\\SASUnit\\SASUnit_Test\\SASUnit_\<HMS-Shortname\>.
+There you are free to copy your local SASUnit version for testing.
+
+Testing is currently done on HD1PCMS0070. For any further informtion like shared folders, PWDs, etc. consult the HMS wiki.
+
+If there are any questions or inconveniences on HD1PCMS0070 feel free to contact me (Klaus Landwich)

[Klaus Landwich]

• Description has changed:

Diff:

--- old
+++ new
@@ -10,7 +10,7 @@

 -  C:\\AA_projekte\\SASUnit\\SASUnit_vxx.xxx.

 To simplify testing each SASUnit developer has a seperate testing folder: 
--  C:\\AA_Projekte\\SASUnit\\SASUnit_Test\\SASUnit_\<HMS-Shortname\>.
+-  C:\\AA_Projekte\\SASUnit\\SASUnit_Test\\SASUnit_\<family name\>.
 There you are free to copy your local SASUnit version for testing.

 Testing is currently done on HD1PCMS0070. For any further informtion like shared folders, PWDs, etc. consult the HMS wiki.

[Andreas Mangold]

Please write documentation of the testing environment as an email and close the ticket.

[Klaus Landwich]

E-mail is written

• status: accepted --> closed

[Andreas Mangold]

Windows on Machine hd1pcms0091 must be registered.

[Klaus Landwich]

• Description has changed:

Diff:

--- old
+++ new
@@ -1,4 +1,5 @@
-Provide testing environment on a virtual machine: Windows 7 64 bit english, SAS 9.3 64 bit english
+Provide testing environment on a virtual machine: Windows 7 64 bit english, SAS 9.3 64 bit english.
+
 Currently there is a testing environement on a virtual machine. It's as stated below german Windows and german SAS9.3 (TS1M0). It's only a temporary solution until we have an english Windows machine running.

 The VM is considered as a test environment. Developing is done on your local machine. When everything is fixed and tested on the local machine then the programs are copied to the virtual machine and executed. Preferrebly this will be done via Enterprise Guide. I will provide a store process on the VM to do that.
@@ -16,3 +17,7 @@
 Testing is currently done on HD1PCMS0070. For any further informtion like shared folders, PWDs, etc. consult the HMS wiki.

 If there are any questions or inconveniences on HD1PCMS0070 feel free to contact me (Klaus Landwich)
+
+The English Windows machine (HD1PCMS0091) is running as a VW. It's setup is identical to the setup of HD1PCMS0070 (see above).
+
+For any further detail consult the HMS Wiki, there you can find a page with all VM for SASUnit (Search for "SASUnit VM").

• status: assigned --> accepted

[Klaus Landwich]

• Description has changed:

Diff:

--- old
+++ new
@@ -18,6 +18,6 @@

 If there are any questions or inconveniences on HD1PCMS0070 feel free to contact me (Klaus Landwich)

-The English Windows machine (HD1PCMS0091) is running as a VW. It's setup is identical to the setup of HD1PCMS0070 (see above).
+The English Windows machine (HD1PCMS0091) is running as a VM. It's setup is identical to the setup of HD1PCMS0070 (see above). It has installations of several SAS versions. 

 For any further detail consult the HMS Wiki, there you can find a page with all VM for SASUnit (Search for "SASUnit VM").

[Andreas Mangold]

Command scripts exit with a rc of 1 or 2 even when SASUnit runs without problems, command scripts pause showing rc. What does that mean and is it useful to have it like that?

[Klaus Landwich]

In my opinion it is useful to have it like that. The exit code of the SAS session has a meaning towards program quality.

Here is a short list with the exit codes:

• 0 Everything is OK
• 1 SAS ended with a warning
• 2 SAS ended with an error
• 3+ An ABORT-Statement was issued

This information is in my eyes valuable for programmers to enhance their programs. I would like to keep it in.

[Klaus Landwich]

All changes completed. All related subtickets are closed.