Architecting, installing and maintaining your SAS environment

Kannand your are asking how some tool should be used but not mentioning the goal your are needing it

Reply
Trusted Advisor
Posts: 3,212

Kannand your are asking how some tool should be used but not mentioning the goal your are needing it

Kannand you are asking a question for a tool usage but not mentioning the goal.
The old adigm: When you know a hammer everything becomes a nail (also scerws).

There is release management.  That is going through the development / test / uat / production stages
There is version segregation between the developers, creating braches of code as everybode has has own. 
These are twe different moves like a vertical and horizontal direction.  This is all about like a COBOL language environment. The SAS code program as separate file looks like a COBOL source altough it is a interpreter.

The midtier SAS metadata is not a source like system like COBOL.  The midtier java container is not  a source like system like COBOL . These are just two of the many component in a SAS eco-system where a classic Verion/release system will cause a lot of headaches. They must be extracted first and handling using alls SAS specifics in that step and than later getting exported with SAS specifics.  

 

---->-- ja karman --<-----
Regular Contributor
Posts: 161

Re: Kannand your are asking how some tool should be used but not mentioning the goal your are needin

Thanks for following up @jakarman Sorry if I was unclear.   

 

I am trying to find out if there is a tool that can be used for deploying SAS code in a Unix environment, an equivalent of "Changeman" or "Endevor" that exists on a Mainframe environment.  

 

Hope this helps...!!!

Kannan Deivasigamani
Trusted Advisor
Posts: 3,212

Re: Kannand your are asking how some tool should be used but not mentioning the goal your are needin

I understood your question. The release mangèrent also indicated dtap is a very problematic topic.

The developing of code you make is possible that way but it is not commonly accepted by SAS institute.
Whatever you do with a tool it is about the goal the dtap segregation as with scrum itil being in the working set. It is bad not what you wanted to hear.
You would have liked an answer like use svn (possible with Sas di) or Jenkins or git. Sorry it is not that way.
---->-- ja karman --<-----
Ask a Question
Discussion stats
  • 2 replies
  • 365 views
  • 1 like
  • 2 in conversation