02-13-2017
SusanParker
Calcite | Level 5
Member since
06-23-2011
- 37 Posts
- 2 Likes Given
- 0 Solutions
- 0 Likes Received
-
Latest posts by SusanParker
Subject Views Posted 995 12-22-2016 11:21 AM 1547 05-10-2013 12:50 PM 1547 05-08-2013 12:32 PM 2112 05-08-2013 12:15 PM 1984 05-07-2013 11:49 AM 3852 05-01-2013 04:04 PM 1817 05-01-2013 10:29 AM 1373 04-19-2013 05:31 PM 1373 04-19-2013 05:24 PM 1373 04-19-2013 05:23 PM -
Activity Feed for SusanParker
- Posted Re: Output problem in regards to page lines in SAS 9.4 on ODS and Base Reporting. 12-22-2016 11:21 AM
- Posted Re: Question regarding Installation Note 49492: SAS® Clinical Standards Toolkit 1.5 - Windows X32 operating systems are no longer supported on SAS Health and Life Sciences. 05-10-2013 12:50 PM
- Posted Re: Question regarding Installation Note 49492: SAS® Clinical Standards Toolkit 1.5 - Windows X32 operating systems are no longer supported on SAS Health and Life Sciences. 05-08-2013 12:32 PM
- Posted Question regarding Installation Note 49492: SAS® Clinical Standards Toolkit 1.5 - Windows X32 operating systems are no longer supported on SAS Health and Life Sciences. 05-08-2013 12:15 PM
- Liked Re: Issue in macro crtdds_write, clinical standards toolkit 1.4 for Lex_SAS. 05-07-2013 11:56 AM
- Posted Re: Issue in macro crtdds_write, clinical standards toolkit 1.4 on SAS Health and Life Sciences. 05-07-2013 11:49 AM
- Posted Issue in macro crtdds_write, clinical standards toolkit 1.4 on SAS Health and Life Sciences. 05-01-2013 04:04 PM
- Posted Re: Clinical Standards Toolkit v1.5? on SAS Health and Life Sciences. 05-01-2013 10:29 AM
- Posted Re: How do I quote the darned thing? on SAS Programming. 04-19-2013 05:31 PM
- Posted Re: How do I quote the darned thing? on SAS Programming. 04-19-2013 05:24 PM
- Posted Re: How do I quote the darned thing? on SAS Programming. 04-19-2013 05:23 PM
- Posted How do I quote the darned thing? on SAS Programming. 04-19-2013 04:10 PM
- Posted Re: A question regarding v1.5 on SAS Health and Life Sciences. 04-12-2013 04:05 PM
- Posted A question regarding v1.5 on SAS Health and Life Sciences. 04-11-2013 03:22 PM
- Posted Re: Clinical Standards Toolkit v1.5? on SAS Health and Life Sciences. 03-18-2013 10:35 AM
- Posted Clinical Standards Toolkit v1.5? on SAS Health and Life Sciences. 03-15-2013 02:11 PM
- Posted Re: Any ODS Graphics or GTL classes coming up soon? on Graphics Programming. 11-01-2012 04:37 PM
- Posted Re: Any ODS Graphics or GTL classes coming up soon? on Graphics Programming. 11-01-2012 02:47 PM
- Posted Any ODS Graphics or GTL classes coming up soon? on Graphics Programming. 11-01-2012 02:38 PM
- Posted Re: Should we install the Add-In? on Microsoft Integration with SAS. 09-05-2012 12:49 PM
-
Posts I Liked
12-22-2016
11:21 AM
I'm wondering if you ever got a solution for this issue. We recently upgraded to SAS 9.4M3 from 9.3 and are having the same problem.
... View more
05-10-2013
12:50 PM
So the answer from tech support, for anyone else who may have been confused, is that you must also run 64-bit SAS for CST v1.5 to be able to be installed.
... View more
05-08-2013
12:32 PM
Okay, when I get a response I'll post it here.
... View more
05-08-2013
12:15 PM
This doesn't mean that I have to be running 64-bit SAS, just 64-bit Windows, correct?
... View more
05-07-2013
11:49 AM
Turns out it was non-breaking spaces, 4 of them. Ack! The metadata spreadsheet from CDISC for 3.1.3. was the culprit for a few and probably me cutting and pasting from the 3.1.3 IG for the others. Finally I just cycled through each item I was importing from Excel and checked to see which characters were extended ASCII ones and then went back and took care of them. Thanks for the help!
... View more
05-01-2013
04:04 PM
I'm getting the following when I submit the program, create_crtdds_define to batch (non UTF-8): NOTE: Could not initialize classpath. Classpath variable is not set. ERROR: 'Invalid byte 1 of 1-byte UTF-8 sequence.' ERROR: 'com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 1 of 1-byte UTF-8 sequence.' This does not happen if I submit the program to batch with UTF-8 and it doesn't happen with another study using the same code, when I submit to batch non-UTF-8. I'm running v9.3 M2 32-bit on Windows Server 2008 R2 64-bit. The data step from crtdds_write that produces the above messages is: %* In the following, the logging level is set to info as the transform creates an empty XML doc if nothing is reported, which causes an error in the SAS libname; * Create the external XML file from intermediate xml; data _null_ %* Only use picklist for SAS V9.2 and above; %if %eval(^ (&SYSVER=9.1)) %then %do; / picklist="&_cstJavaPicklist" %end; ; dcl javaobj prefs("&_cstParamsClass"); prefs.callvoidmethod('setImportOrExport',"&_cstAction"); prefs.callvoidmethod('setStandardName',"&_cstStandard"); prefs.callvoidmethod('setStandardVersion',"&_cstStandardVersion"); prefs.callvoidmethod('setXslBasePath',tranwrd("&_cstXslReposPath",'\','/')); prefs.callvoidmethod('setSchemaBasePath',tranwrd("&_cstXsdReposPath",'\','/')); prefs.callvoidmethod('setSasXMLPath',tranwrd("&_cstCubeXMLPath",'\','/')); prefs.callvoidmethod('setStandardXMLPath',tranwrd("&_cstExternalXMLPath",'\','/')); prefs.callvoidmethod('setAvailableTransformsFilePath',tranwrd("&_cstAvailableTransformsPath",'\','/')); prefs.callvoidmethod('setLogFilePath',tranwrd("&_cstLogXMLPath",'\','/')); if ("&_cstOutputEncoding" ne '') then do; prefs.callvoidmethod('setOutputEncoding',"&_cstOutputEncoding"); end; if ("&_cstHeaderComment" ne '') then do; prefs.callvoidmethod('setHeaderCommentText',tranwrd("&_cstHeaderComment",'\','/')); end; if (&_cstCreateDisplayStyleSheet=1) then do; if ("&_cstStyleSheetPath" ne '') then do; prefs.callvoidmethod('setCustomStylesheetPath', tranwrd("&_cstStyleSheetPath",'\','/')); prefs.callvoidMethod('setOutputStylesheetName', tranwrd("&_cstOutputStyleSheetName..xsl",'\','/')); end; prefs.callvoidmethod('createDisplayStylesheet'); end; * set logging to INFO; prefs.callvoidmethod('setLogLevelString',"&loglev"); dcl javaobj transformer("&_cstTransformsClass", prefs); transformer.exceptiondescribe(1); transformer.callvoidmethod('exec'); * check the return values here and get results path; transformer.delete(); prefs.delete(); run;
... View more
05-01-2013
10:29 AM
Any news on releasing v1.5?
... View more
04-19-2013
05:31 PM
So the correct answer is to have the macro variable have the correct value to start with. I knew it had to be something staring me right in the face. Sorry for taking up people's time. %let standardsheet=%str('SDTM Terminology 2013-04-12'); and it works just fine.
... View more
04-19-2013
05:24 PM
I tried just about every combination of quotes I could think of both in and out of the macro variable. This is a situation where if you haven't run the code and verified that it works, assume I've tried it. I have not tried combinations of quoting functions together, although I'm not sure that would gain me anything.
... View more
04-19-2013
05:23 PM
It actually does matter if you nest them the other way. The error message changes, but it still doesn't work.
... View more
04-19-2013
04:10 PM
I have a spreadsheet name with spaces in it. I have placed this value into a macro variable. %let standardsheet=%str(SDTM Terminology 2013-04-13$); Now I want to use this in a proc import. PROC IMPORT OUT= WORK.newterm DATAFILE= "SDTM Terminology.xls" DBMS=EXCEL REPLACE; range="&standardsheet"; GETNAMES=YES; MIXED=NO; SCANTEXT=YES; USEDATE=YES; SCANTIME=YES; RUN; Pretty consistently, I get something along the lines of ERROR: File _IMEX_.'SDTM Terminology 2013-04-13$'n.DATA does not exist. ERROR: Import unsuccessful. See SAS Log for details. I have tried using various sets of quotes and using various macro quoting functions in my %let and I still can't get it right. The spreadsheet does exist. The wizard proc import code is PROC IMPORT OUT= WORK.test DATAFILE= "SDTM Terminology.xls" DBMS=EXCEL REPLACE; RANGE="'SDTM Terminology 2013-04-12$'"; GETNAMES=YES; MIXED=NO; SCANTEXT=YES; USEDATE=YES; SCANTIME=YES; RUN; Please save my sanity! I'm missing the very obvious.
... View more
04-12-2013
04:05 PM
Thanks Lex! Now I just have to convince others that will run the validator on my define that DD0002 is too restrictive. Looking forward to your PharmaSUG talk even though we only back-handedly use ODM through define. Definitely am using the information from last year's talk. Looking forward to v1.5 and then to define 2.0 support.
... View more
04-11-2013
03:22 PM
Will v1.5 include the Schema Instance namespace in define.xml? I keep getting this error in OpenCDISC validator. I'm also wondering if there is somewhere, besides editing my define.xml, to provide the namespace information for v1.4. I don't know java and it looks like that is what is writing the xml. I have one other question. For the SASFormatName attribute on codelists, values like $LBTESTCD are showing up as errors in the validator. Is that really the case? Was that a valid format name in v5 (assuming its some sort of transport file limitation that is the basis for the rule)? I worked on v5.18 on a VAX when I first started using SAS and I can't remember for sure. Thanks!
... View more
03-18-2013
10:35 AM
Thanks!
... View more
03-15-2013
02:11 PM
Hi! Will this have support (i.e. be able to create) for define 2.0? If not, is there an ETA on v1.5 or an ETA on supporting define 2.0? Thanks!
... View more