Problem Note 50475: SAS® Clinical Standards Toolkit 1.5 - Explicit macrocall variable lengths of $400 can cause generated source catalog code to exceed $255
 |  |  |  |  |
In SAS® Clinical Standards Toolkit 1.5, explicit macrocall variable lengths of $400 can cause generated source catalog code to exceed $255 and possibly truncating source code in the extract_domaindata_all.sas macro.
Consider this example:
filename incCode CATALOG "work._cstCode.domains.source" LRECL=255;
data _null_;
set srcdata.itemgroupdefs(keep=OID Name IsReferenceData SASDatasetName Domain);
file incCode;
length macrocall $400 _cstOutputName $100;
macrocall=cats('%odm_extractdomaindata(_cstSelectAttribute=OID',
', _cstSelectAttributeValue=', OID,
', _cstIsReferenceData=', IsReferenceData,
', _cstMaxLabelLength=256',
', _cstAttachFormats=Yes',
', _cstODMMinimumKeyset=No',
', _cstLang=en',
', _cstOutputDS=', _cstOutputName, ');');
put macrocall;
There are examples where the code written to the source file exceeds $255 and contains a space that can cause the code to fail when it is submitted. If the space happens in a line of code where it does not make a difference, the program runs correctly. If it inserts a space where it is not allowed, the code fails. Consider something like proc pr int instead of proc print.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Clinical Standards Toolkit | Microsoft® Windows® for x64 | 1.5 | |||
| Microsoft Windows 8 Ent | 1.5 | |||||
| Microsoft Windows 8 Pro | 1.5 | |||||
| Microsoft Windows 95/98 | 1.5 | |||||
| Microsoft Windows 2000 Advanced Server | 1.5 | |||||
| Microsoft Windows 2000 Datacenter Server | 1.5 | |||||
| Microsoft Windows 2000 Server | 1.5 | |||||
| Microsoft Windows 2000 Professional | 1.5 | |||||
| Microsoft Windows NT Workstation | 1.5 | |||||
| Microsoft Windows Server 2003 Datacenter Edition | 1.5 | |||||
| Microsoft Windows Server 2003 Enterprise Edition | 1.5 | |||||
| Microsoft Windows Server 2003 Standard Edition | 1.5 | |||||
| Microsoft Windows Server 2003 for x64 | 1.5 | |||||
| Microsoft Windows Server 2008 | 1.5 | |||||
| Microsoft Windows Server 2008 for x64 | 1.5 | |||||
| Microsoft Windows Server 2012 Datacenter | 1.5 | |||||
| Microsoft Windows Server 2012 Std | 1.5 | |||||
| Microsoft Windows XP Professional | 1.5 | |||||
| Windows 7 Enterprise 32 bit | 1.5 | |||||
| Windows 7 Enterprise x64 | 1.5 | |||||
| Windows 7 Home Premium 32 bit | 1.5 | |||||
| Windows 7 Home Premium x64 | 1.5 | |||||
| Windows 7 Professional 32 bit | 1.5 | |||||
| Windows 7 Professional x64 | 1.5 | |||||
| Windows 7 Ultimate 32 bit | 1.5 | |||||
| Windows 7 Ultimate x64 | 1.5 | |||||
| Windows Millennium Edition (Me) | 1.5 | |||||
| Windows Vista | 1.5 | |||||
| Windows Vista for x64 | 1.5 | |||||
| 64-bit Enabled Solaris | 1.5 | |||||
| Linux for x64 | 1.5 | |||||
A fix for this issue for Clinical Standards Toolkit 1.5 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/L18.html#50475| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2013-08-27 13:12:09 |
| Date Created: | 2013-07-22 14:51:54 |