<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: alternative to proc format in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/alternative-to-proc-format/m-p/65582#M18706</link>
    <description>Why don't you create a permanent format library.  It "sounds" like you are running the PROC FORMAT code in each job possibly, via %INC.  but the point is you don't need to do it that way.  A library would be more efficient.</description>
    <pubDate>Wed, 19 Aug 2009 21:22:18 GMT</pubDate>
    <dc:creator>data_null__</dc:creator>
    <dc:date>2009-08-19T21:22:18Z</dc:date>
    <item>
      <title>alternative to proc format</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/alternative-to-proc-format/m-p/65579#M18703</link>
      <description>We use a huge set ( about 3000) of formats using proc format.  This is done with proc format; value; syntax.  I some how feel this is increasing the run time of the program. Is there an alternative way to do this?</description>
      <pubDate>Wed, 19 Aug 2009 19:03:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/alternative-to-proc-format/m-p/65579#M18703</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-08-19T19:03:48Z</dc:date>
    </item>
    <item>
      <title>Re: alternative to proc format</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/alternative-to-proc-format/m-p/65580#M18704</link>
      <description>Rather than trying to explain it here is a paper showing how to use a dataset to create formats.&lt;BR /&gt;
&lt;A href="http://www2.sas.com/proceedings/forum2007/068-2007.pdf" target="_blank"&gt;http://www2.sas.com/proceedings/forum2007/068-2007.pdf&lt;/A&gt;</description>
      <pubDate>Wed, 19 Aug 2009 19:24:33 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/alternative-to-proc-format/m-p/65580#M18704</guid>
      <dc:creator>Flip</dc:creator>
      <dc:date>2009-08-19T19:24:33Z</dc:date>
    </item>
    <item>
      <title>Re: alternative to proc format</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/alternative-to-proc-format/m-p/65581#M18705</link>
      <description>It's unclear whether the PROC FORMAT execution is what you feel is "increasing the run time" or whether using the SAS formats in your DATA step code is where you have concern for run time.&lt;BR /&gt;
&lt;BR /&gt;
I don't expect you will see significant run time improvements with using the CNTLIN= approach, however that approach will make it much easier to maintain your input/output data values used with these formats.&lt;BR /&gt;
&lt;BR /&gt;
You can analyze your SAS execution time easily by not executing the PROC FORMAT code, and setting the NOFMTERR option to experiment.  Review the SAS log information for DATA and PROC step execution times.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.</description>
      <pubDate>Wed, 19 Aug 2009 19:33:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/alternative-to-proc-format/m-p/65581#M18705</guid>
      <dc:creator>sbb</dc:creator>
      <dc:date>2009-08-19T19:33:34Z</dc:date>
    </item>
    <item>
      <title>Re: alternative to proc format</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/alternative-to-proc-format/m-p/65582#M18706</link>
      <description>Why don't you create a permanent format library.  It "sounds" like you are running the PROC FORMAT code in each job possibly, via %INC.  but the point is you don't need to do it that way.  A library would be more efficient.</description>
      <pubDate>Wed, 19 Aug 2009 21:22:18 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/alternative-to-proc-format/m-p/65582#M18706</guid>
      <dc:creator>data_null__</dc:creator>
      <dc:date>2009-08-19T21:22:18Z</dc:date>
    </item>
  </channel>
</rss>

