RE: Generate SQL to source member has hex codes -- why?

["Wilt, Charles" <CWilt@xxxxxxxxxxxx>]

Ok,

I seem to have found the answer.  On the options tab of the "Generate SQL" 
dialog box, unselect the "Format statements for readability" option.


HTH,

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Wilt, Charles
> Sent: Monday, February 07, 2005 9:24 AM
> To: Midrange Systems Technical Discussion (E-mail)
> Subject: Generate SQL to source member has hex codes -- why?
> 
> 
> I used the Generate SQL option of iSeries Navigator to 
> generate SQL for a physical file that had originally been 
> created with DDS.
> 
> In the "Generate SQL" dialog box, I choose the option to save 
> the generate SQL to a source member on the system.
> 
> When I look at the source in SEU, a solid bar is shown from 
> the end of the text to the end of the source for every line.
> 
> Looking at it in hex, I see a 0D25 followed by blanks to the 
> end of the source.  Also, I see some 05 every once and a while.
> 
> Anybody understand what is going on and how to stop it?
> 
> Thanks,
> 
> 
> Charles Wilt
> iSeries Systems Administrator / Developer
> Mitsubishi Electric Automotive America
> ph: 513-573-4343
> fax: 513-398-1121
>  
> 
> -- 
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
>