<?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: DB2UTIL proc , table name too long in ODS and Base Reporting</title>
    <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/DB2UTIL-proc-table-name-too-long/m-p/40877#M5581</link>
    <description>Hi:&lt;BR /&gt;
  The ODS forum mostly focusses on PROC PRINT, PROC REPORT, PROC TABULATE for Base SAS reporting, with ODS. If a DATA step program were used for producing reports with Base SAS, that question might fit here, also.&lt;BR /&gt;
 &lt;BR /&gt;
  However, the DATA step and PROC DB2UTIL do not fit in this category -- especially since you are performing file maintenance and not reporting, per se. You might be better off posting your question in the SAS Procedure or the Data Step and Macro forum. If you have persistent or urgent problems with your DB2UTIL program, you might wish to open a track with Tech Support for more help.&lt;BR /&gt;
 &lt;BR /&gt;
cynthia</description>
    <pubDate>Fri, 15 Jan 2010 04:25:48 GMT</pubDate>
    <dc:creator>Cynthia_sas</dc:creator>
    <dc:date>2010-01-15T04:25:48Z</dc:date>
    <item>
      <title>DB2UTIL proc , table name too long</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/DB2UTIL-proc-table-name-too-long/m-p/40876#M5580</link>
      <description>I am trying to delete records from a db2 table using proc DB2UTIL  as shown below on os/390.  As table name is too long I am getting following error &lt;BR /&gt;
&lt;BR /&gt;
data indate;           &lt;BR /&gt;
  deldate = '30NOV08' ;&lt;BR /&gt;
&lt;BR /&gt;
options db2ssid=dbXX ;              &lt;BR /&gt;
proc db2util                        &lt;BR /&gt;
     data = indate                  &lt;BR /&gt;
     table = aaaaaaa.mmmmm_eee_xxxx_yyyy    &lt;BR /&gt;
     function=delete update;        &lt;BR /&gt;
     where  calendar_dt = %deldate; &lt;BR /&gt;
     sqlout = sqlfile;              &lt;BR /&gt;
     update;                        &lt;BR /&gt;
     run;                           &lt;BR /&gt;
&lt;BR /&gt;
As existing table name is too long, I am getting the following error. &lt;BR /&gt;
DSNT408I SQLCODE = -204, ERROR:  aaaaaaa.mmmmm_eee_xxxx_yy . If you observe the last two bytes are truncated. The table has 5million rows, so I am not able to create view also. Can anyone suggest how to handle this?</description>
      <pubDate>Fri, 15 Jan 2010 03:03:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/DB2UTIL-proc-table-name-too-long/m-p/40876#M5580</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2010-01-15T03:03:04Z</dc:date>
    </item>
    <item>
      <title>Re: DB2UTIL proc , table name too long</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/DB2UTIL-proc-table-name-too-long/m-p/40877#M5581</link>
      <description>Hi:&lt;BR /&gt;
  The ODS forum mostly focusses on PROC PRINT, PROC REPORT, PROC TABULATE for Base SAS reporting, with ODS. If a DATA step program were used for producing reports with Base SAS, that question might fit here, also.&lt;BR /&gt;
 &lt;BR /&gt;
  However, the DATA step and PROC DB2UTIL do not fit in this category -- especially since you are performing file maintenance and not reporting, per se. You might be better off posting your question in the SAS Procedure or the Data Step and Macro forum. If you have persistent or urgent problems with your DB2UTIL program, you might wish to open a track with Tech Support for more help.&lt;BR /&gt;
 &lt;BR /&gt;
cynthia</description>
      <pubDate>Fri, 15 Jan 2010 04:25:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/DB2UTIL-proc-table-name-too-long/m-p/40877#M5581</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2010-01-15T04:25:48Z</dc:date>
    </item>
  </channel>
</rss>

