Using CDISC Validation Tools in a Validated Hosted Environment   Below is the paper link http://www.phusewiki.org/docs/Conference%202014%20CD%20%20Papers/CD11%20%20%20.pdf   if you need copy of SAS Macro, please contact me.   Thanks, Sandeep ... View more

This post contains attachment for the Poster presented at FDA/PhUSE Annual Computational Science Symposium 2013 ... View more

SAS Drug Development (SDD) is a content repository which provides the capability to store and analyze versioned data and documents. This paper describes how to extend SDD’s capabilities to retrieve various kind of information from the content repository using various tools and technologies and how to present them in different formats like Executable Jar Files, Executable (exe) files, SAS Macros or even in graphical format using Microsoft Excel, which can be used in making key Business decisions. This paper assumes the reader has basic Java, SAS, and VBA programming knowledge. ... View more

Yes SDD 4.1 does have API support. To start using the SAS Drug Development Java API, you must first establish a session with your instance of the application. From the session, you can obtain the services that are currently delivered which provide a number of methods for resource manipulation. For example:   import com.sas.hls.client.*;   import com.sas.hls.resource.repository.RepositoryResourceService;   ...     Session session = SessionFactory.newSession(new URL(http://yourSDDMachine.domain.com), "mySDDuid", "mySDDpwd");   DrugServiceManager serviceManager =  ((DrugServiceManager) session.getServiceManager());                                              RepositoryResourceService repoService = serviceManager.getRepositoryResourceService(); repoService.checkoutToWorkspace("/YOURORG/Files/Folder/someProgram.sas"); ... See RepositoryResourceService and WorkspaceResourceService for a list of methods currently available in the API.   There is also a samples directory which includes instructions on how you can set up an environment to use the API as well as providing several full example programs that illustrate the use of the API. ... View more

Repository – Repository is content sharing location which is accessible by all the members of the SDD instance provided they are granted appropriate permissions. The files stored in Repository are in Read-Only mode. Any action performed in Repository is recorded and metadata associated with the action is stored in the Audit Trail. It is divided into two parts 1. Organization level Repository – This area of the repository is accessible by all members of SDD instance provided they are granted appropriate permissions. Any content which needs to be shared among team members should be uploaded to Organization level Repository. Special objects like Project and Analysis can be created and the content can be controlled by various permission definitions. 2. User level Repository – User Repository is accessible ONLY by the User. Any content uploaded to this area of the repository is not seen by any other member of the SDD instance. You cannot create special kind of nodes like Project or Analysis underneath User Repository. Also since this area is ONLY accessible by the user himself/herself there are no permission definitions available. One should not use this area for day to day activities or should not store lot of content in this level of repository because you are not sharing this content with anyone. This is your PERSONAL content. . Workspace – Workspace is the location in which you manipulate the objects that you need to perform your job. it’s your work area. Any document or file or data which you want to update needs to be checked out from the Organization level Repository (mostly), get copy of that file into your workspace,  update in workspace and once the work is done check it back to Organization level Repository. It lets you create, modify and update the files and data. Most of the content will be developed by users in their workspace and when they feel content is ready to be shared with other team members it will be uploaded into the Repository. ... View more

odUsers would like to know if they can run SDD API code from Windows SAS without displaying user password in the log. In order to run the SDD code from Windows SAS follow the below steps Go to site ftp://ftp.sas.com/techsup/download/hotfix/35drugdev.html and download the latest Remote API release Refer to the ftp://ftp.sas.com/techsup/download/hotfix/drugdev/35drgrmtapi03/RemoteAPI.pdf and chapter 2 for installation instruction. Once the API is installed properly to execute SDD API code from Windows SAS, the major challenge is that first step is call to %sasdrugdev_login macro which requires userid and password values as parameters. In order to make sure user password is not displayed in the log use the below code.   options mprint symbolgen mlogic; %macro sddlogin;     *******************************************************;   * Make sure no macro resolution take place            *;   *******************************************************;   %let _mprint =%sysfunc(getoption(mprint));   %let _symbolgen = %sysfunc(getoption(symbolgen));   %let _mlogic=%sysfunc(getoption(mlogic));   options nomprint nosymbolgen nomlogic;     *******************************************************;   * Specify the SDD instance URL and capture userid,    *;   * password using the window screen                    *;   *******************************************************;    %let sddurl=%str(https://XXXXXX.sas.com/sddremote); * --> UPDATE THIS LINE TO YOUR SDD INSTANCE URL;    * Initialize macro variables as local and clear them;   %local username password;   %let username=;   %let password=;    %window pw    columns=55 rows=15 icolumn=5 irow=25    #4 @15 'SDD Authentication' attr=highlight    #6 @15 'Username:'    #6 @25 username 15 required=yes attr=underline    #8 @15 'Password:'    #8 @25 password 15 display=no required=yes attr=underline    ; %display pw;   %sasdrugdev_login(url=&sddurl, sdduserid=%superq(username), sddpassword=%superq(password));       %mend sddlogin; %sddlogin; ********************************************************; * Reset the macro resolution options to original value *; ********************************************************; options &_mprint &_symbolgen &_mlogic; %sasdrugdev_getobjects(sddpath=/SDD,dsname=work.getobjects,recursiveLevel=1); proc print data=work.getobjects width=min; run; %sasdrugdev_logout; Above code encapsulates the %sasdrugdev_login into another macro %sddlogin which uses the concept of %window and %display. Combination of these two statements provide user interface where user can enter authentication information and suppressing mlogic mprint and symbolgen options make sure that the value of these macro variables are not resolved during execution. Using above technique generic and dynamic code can be developed which can be run without every worrying about displaying user authentication information in the log. This is how we recommend.  Do you use this same approach or a different one? ... View more

SDD One of the biggest challenges in SAS Programming is that there is no standard way to generate Traceability Matrix for SAS programs with their inputs and outputs. As time progresses programs are updated and there is no way to do impact analysis for these updates on existing programs. This paper talks about how to generate Traceability Matrix for any SAS program along with their inputs / outputs and their version numbers in SAS Drug Development Environment (SDD). It decodes the JobLog XML files (.jlgxml) and generates report which can help to carry out impact analysis for any updates to existing source code. ... View more