View previous topic :: View next topic
|
Author |
Message |
babuprashad Warnings : 1 New User
Joined: 09 Aug 2007 Posts: 15 Location: mysore
|
|
|
|
Hi,
Do we have any rexx or any code to convert SAS report code to PLI copy book. I searched on the internet and found that we have a program to convert COBOL copybook to SAS code. But, did not find any thing which converts from SAS to PLI/COBOL......thanks |
|
Back to top |
|
|
vasanthz
Global Moderator
Joined: 28 Aug 2007 Posts: 1742 Location: Tirupur, India
|
|
|
|
Hi,
Are you trying to convert SAS input statements to PLI? |
|
Back to top |
|
|
babuprashad Warnings : 1 New User
Joined: 09 Aug 2007 Posts: 15 Location: mysore
|
|
|
|
Yes....have u done this before....??? |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
As long as you;re just talking DATA step statements, I can't imagine the conversion would be very complex. If there are PROC step statements to be converted, that's an elephant of a different color.
I haven't seen -- or heard -- of any products to do this of conversion. I suspect you're going to have to do the conversion by hand. |
|
Back to top |
|
|
vasanthz
Global Moderator
Joined: 28 Aug 2007 Posts: 1742 Location: Tirupur, India
|
|
|
|
Hi,
I have not done this. But automating convertion of an input statement could be a daunting task, as SAS has list, column, position input, and not to mention the position inputs with +'s and :'s and @'s and you have to take into account of length statements, format statements. |
|
Back to top |
|
|
Phrzby Phil
Senior Member
Joined: 31 Oct 2006 Posts: 1042 Location: Richmond, Virginia
|
|
|
|
Quote: |
But automating convertion of an input statement could be a daunting task |
One might also consider this a very interesting challenge.
As pointed out, many statements other than the INPUT must be processed: length and format have been mentioned.
There might also be macros preceding the INPUT that provide this code, so they must be expanded. Also, any macro variables must be resolved. These would necessarily have been defined prior to the data step containing the INPUT, so recognizing this boundary is required; a macro variable set in this step must be ignored.
It would be reasonable to put restrictions on version 1 of the conversion program that match code at your installation. You must still check for code that "breaks" these rules and report the offending code. |
|
Back to top |
|
|
|