Desktop productivity for business analysts and programmers

Things to check as a programmer- when moved from SAS EG 6.1/7.1

Reply
Occasional Contributor
Posts: 12

Things to check as a programmer- when moved from SAS EG 6.1/7.1

Hey there,

Can anybody let me know, what are the things to be checked on the programs, when we update SAS EG from 6.1 to 7.1 in order to see if the programs are working the same as they used to in the older EG version. I know few things, like comparing the run time, output, and the log for any additional warnings/errors. Are there any other things to be added to the list. Please provide your inputs.

Thank you

Respected Advisor
Posts: 3,062

Re: Things to check as a programmer- when moved from SAS EG 6.1/7.1

Are you changing SAS versions too? Do you use EG projects or just you own written code?

If you are not changing SAS versions and run only code then only functional testing is required - do your programs run without error or not.

We've just changed EG versions but not SAS version and have only user-written code. Everything ran fine with minimal functional testing.

If you are changing SAS versions say 9.3 to 9.4, then full regression testing is required including checking data. I found some significant issues when doing this.

Occasional Contributor
Posts: 12

Re: Things to check as a programmer- when moved from SAS EG 6.1/7.1

We use written codes and we'll be switching from 9.3 to 9.4 as well. Can you share the issues you found in 9.4 please.

Thank you very much

Respected Advisor
Posts: 3,062

Re: Things to check as a programmer- when moved from SAS EG 6.1/7.1

The issues we found in moving from SAS 9.3 to 9.4 were:

  • The data order of SQL queries was sometimes different to 9.3. We had to add ORDER BY clauses to correct this
  • SQL sub-queries with GROUP BY's sometimes gave wrong results. These could be fixed by adding AS ColumnName to column selected
  • PROC IMPORT of Excel spreadsheets now only allows MIXED = YES statement if DBMS = EXCEL. Code change required.
  • Struck a bug with the EXCELXP ODS tagset documented in SAS Note 53344 - fortunately there is a workaround.

The SQL problems were tracked with Tech Support. They were acknowledged as a problem and forwarded to SAS R & D.

The lesson from this exercise is that changing SAS versions requires comprehensive testing.

We used PROC COMPARE extensively to ensure important datasets were indeed identical. It is a fantastic utility for this type of work and should be an essential part of every SAS developers toolkit. 

Ask a Question
Discussion stats
  • 3 replies
  • 289 views
  • 2 likes
  • 2 in conversation