Information about Proc CDISC can be found here: http://support.sas.com/rnd/base/xmlengine/proccdisc/index.html SAS is planning to provide additional CDISC capabilities via the SAS Clinical Data Standards toolkit and the SAS Clinical Data Integration product in 2009. The toolkit is initially focused on SDTM validation and define.xml creation, and, like Proc CDISC, will be available at no additional cost over a SAS/Base license. Dave Business Solutions Manager for Life Sciences R&D, SAS ... View more

The errors indicate that the domain dataset is improperly constructed, and these errors must be corrected before additional checks are made. You will need to add the required fields to your data set before Proc CDISC can get to the next level of data checking. ... View more

We're working through this documentation right now, specifically as it relates to registry settings associated with the Process Editor. These may also carry over to the other applications. There are various business rules that can be defined in the registry (for example, all macro variables that begin with inds_ will default to input data sets, etc.). Documenting this detailed information is taking a bit longer than I had anticipated. Dave ... View more

François There is documentation about the registry, but it's a bit scattered among several different documents. I'm pulling the relevant content together and will post it soon. Dave ... View more

The default behavior can be changed to 'Unassigned' by modifying the system registry. Specifically, the property DataTransforms/PPV/defaults/domain/INITANALYSISTYPES should be set to 'N'. Changing this setting will typically involve having the system administrator perform the task -- most likely by requesting it through a change request form if the system is hosted at SAS. Dave ... View more

Any SAS data set can be exported in a CDISC format, but it tends to be more complex than that. CDISC has a variety of different data models -- often, users want to convert data to the Submission Data Tabulation Model (SDTM) which requires restructuring the data to match the model (that is, call the dataset 'this', and the columns 'that'). Additonally, users sometimes need to use the Operational Data Model (ODM) as the transport mechanism or container. The ODM file can contain SDTM data, but doesn't have to. Similarly, the SDTM can be transported via ODM, but can be a SAS data set or transport file. This can be certainly be confusing, but without more information it's difficult to answer the question more directly. Dave ... View more

The context here is very important. It's difficult to tell from the originial question if this is a 'listing, as normally used in clinical trials', or a more generalized 'listing'. A clinical trials listing is most often a 'dump' of the data, as would most easily been generated when applying a 'proc print' to a clinical data table. (Of course, the dump could be made prettier with ODS, proc report and other tools). Regardless of how it looks, it is a num-summarized display. A more generalized listing is much more difficult to describe. Dave ... View more

I think it's safe to say that all companies have different expectations of their biostatistics and SAS programming teams. I've worked with SAS programmers that didn't know anything about biostatistics. I've worked with SAS programmers with PhD's in biostatistics that preferred SAS programming. I've worked with biostatisticians that knew little about how to program in SAS. Regardless of their formal training, both roles work together collaboratively to manipulate and analyze the clinical trials data. Dave ... View more

The 'light' version of SAS is SAS Learning Edition. More information can be found at: http://support.sas.com/training/le/ ... View more

In SAS 9, there is a new environment variable for the Enhanced Editor named SAS_EXECFILENAME, then you can retrieve the name of the current program by issuing this statement: %put The current program is %sysget(SAS_EXECFILENAME); There is also an environment variable for the Enhanced Editor called SAS_EXECFILEPATH that contains the full path of the submitted program or catalog entry. The full path includes the folder and the filename. %put The current path is %sysget(SAS_EXECFILEPATH); ... View more

There are SAS tools that support define.xml, but they generally require some additional work beyond using just 'proc cdisc'. There's a wealth of information available on the web regarding where to start -- www.cdisc.org lists training classes and the like. In the end, the answer to the question comes back to 'what do you want to do with CDISC?'. Are you just interested in creating the define.xml? Do you need to deliver SDTM data to your sponsors? Do you need to load ODM data from an EDC system? Dave ... View more

Based on user and market feedback, providing SDTM 3.1.1 support has been prioritized at SAS over support for define. The SDTM work is progressing and scheduled for availability within a few months. After the SDTM work is completed, support for ODM 1.3 will be addressed, followed by activities on define. [The CDISC define team is currently discussing a new version that supports data submission via XML, and the work at SAS on define is being deferred until the CDISC define team progresses further in their discussion.] ... View more

Jason: Thanks for the request. I'll pass it along to the folks that are responsible for creating new forums. Since you posted your request to the clnical trials forum, are there specific topics you'd like to see discussed -- CDISC, for example? ... View more

Thanks for the suggestion. I've passed it along to the technical team responsible for maintaining these forums. Dave ... View more

You can modify the code so that within the iterate macro, you divide the incoming parameters by 10. The following sample code may help you -- no guarantees expressed or implied. I've changed the upper bounds of the do loop to 20 instead of 2 as well. %macro iterate(i,j); data _null_; temp_i= &i/10; temp_j= &j/10; call symput ("new_i",temp_i); call symput ("new_j", temp_j); run; %put "&new_i &new_j"; /* proc nlmixed data=dataset1; parms beta1=&new_i, beta2=&new_j, s2e=1, s2beta=1; model Y ~ normal(beta1+beta2+betavar,s2e); random betavar ~ normal(0,s2beta) subject=sid; run; */ %mend iterate; %macro looped; %do i=1 %to 20 %by 1; %do j=1 %to 20 %by 1; %iterate(&i,&j); %end; %end; %mend looped; %looped; ... View more