RE: Bug in DATAEXCACT using seperated LONGFILE-Export?

Hi Hans-Joachim,

Hans-Joachim Görke [mailto:[email protected]] wrote:

> Subject: Bug in DATAEXCACT using seperated LONGFILE-Export?
> 
> 
> I think, there is a bug in repmcli when exporting LONG BYTE-Column in
> seperated files. When you enter a command file like this
> 
> DATAEXTRACT I1,TEXTE FROM TEST1
>  OUTFIELDS  I1       1
>             TEXTE    2
>  OUTFILE 'd:\mas\server\bin\setup\sapdb\TEST1.out'
>  LONGFILE TEXTE 'd:\mas\server\bin\setup\sapdb\texte.daten.###'
> 
> you get the correct outputfile TEST1.out:
> "22","d:\mas\server\bin\setup\sapdb\texte.daten.001"
> "33","d:\mas\server\bin\setup\sapdb\texte.daten.002"
> "44","d:\mas\server\bin\setup\sapdb\texte.daten.003"
> 
> but the first filename you get is
> 	d:\mas\server\bin\setup\sapdb\texte.daten.###
> an the second is
> 	d:\mas\server\bin\setup\sapdb\texte.daten.001
> an the third ist
> 	d:\mas\server\bin\setup\sapdb\texte.daten.002
> 
> I have tryed this with version 7.3.0.34 and actual in 7.3.0.40
> 
Bug ACKed :-(
BUT: it doesn't hurt ;-) Good news, isn't it?
This file created with extension ### is empty (that's at least what
I found with tests here in the lab). So it will not be
used during DATALOAD. It's simply superfluous.

We'll of course fix the bug with one of the next versions.

Regards and thx for reporting
 Steffen
-- 
Steffen Schildberg
SAP DB Team
SAP Labs Berlin