Ansicht
Dokumentation

04952 - LRAW data still in EBCDIC in file D010S after migration

04952 - LRAW data still in EBCDIC in file D010S after migration

ROGBILLS - Synchronize billing plans   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

LRAW data still in EBCDIC in file D010S after migration

Hi Volker,

The integrity of SAP software is still intact. The older version
R3LOAD (14) gave us the exact same result.

It seems to me that there is either a problem with R3LOAD or there is
some configuration or a flag in one of the command files or something
we need to do different. What tells R3LOAD to do an EBCDIC to ASCII
conversion? All the regular data files we've looked at are converted
correctly.

Thanks for your time,

Phillip Pugh
Webco Industries, Inc.

--- In SAP on System iZy..., "Gueldenpfennig, Volker"
<volker.gueldenpfennigZs...> wrote:
> Hi Phil,
>
> then I'm interested, what happens at your next try!
> And I don't know what I should wish to you, because I'm not too
happy, if we
> can't predict what happens in our software!
>
> Regards
>
> Volker
>
> > -----Original Message-----
> > From: welchraider [mailto:ppughZw...]
> > Sent: Montag, 4. Februar 2002 18:45
> > To: SAP on System iZy...
> > Subject: Re: LRAW data still in EBCDIC in file
D010S
> > after migration
> >
> >
> > Hi,
> >
> > Thanks for your reply.
> >
> > I had updated table TCPDB. First we just cleared it. Then we
tried it
> > with the 1100 & 1100 values.
> >
> > I had also tried adding the abap/import_char_conversion = 1 to
the
> > instance profile.
> >
> > I suspect its a translation problem, since the program
> > name "âÁ×Ôââèò" (hex: E2C1D7D4E2E2E8F2) in the error message
> > is "SAPMSSY2" (hex: E2C1D7D4E2E2E8F2) in EBCDIC displayed in
ASCII.
> >
> > When I look at table D010S, PROG = SAPMSSY2 and compare the data
in
> > field BLOCK (type LRAW) in the migrated data base it is identical
> > (unconverted) to the data in the original table on the AS/400.
The
> > other fields in the table (PROG etc.) have been converted.
> >
> > However if I look at the same record in a clean install on NT,
the
> > BLOCK field has different data.
> >
> > I then picked another table with the LRAW type of data. I used
D021S,
> > (D020S was a typo on my original message) and compared the data
> > between the original table on the AS/400 and the clean install on
NT.
> > The field (BLOCK) in D021S in the migrated data base does not
match
> > the original AS/400 table, but does match the same record in the
> > clean install. (I have no idea what table D021S is, I just
picked it
> > because of the similar fields)
> >
> > We have now tried just copying D010S from the clean install into
the
> > migrated data base, replacing what was migrated. We still get
the
> > same errors on startup and are still unable to log on. This tells
me
> > there are obviously other tables involved.
> >
> > So, falling back to the BASIS first line of defense, we are going
to
> > just "TRY AGAIN" and reload the migration from the start. I'll
let
> > you know how it turns out.
> >
> > Thanks for your help,
> >
> > Phillip Pugh
> > Webco Industries, Inc.
> >


Durban Tours - Südafrika Safari

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 3904 Date: 20240621 Time: 043155     sap01-206 ( 2 ms )