Markus,

Thank you for the reply. First, I have patched the R3load, R3trans, libdbsl, DW, r3ldctl, Rtvenvvar, among other things. I am not quite sure how to apply the patch for dipgntab as it is not listed and I am unsure as to what patch it would be included in.

While I did not run RADCUCNT directly from SE38, I did execute Create Unicode nametabs from within SPUMG and there were not any errors after that had ran that I noticed.

I also did find the same note 937983 and ran the DIPGNTAB '-rwr40 -srctt DDNTT -srctf DDNTF -dsttt DDNTT -dsttf DDNTF -ttonly TT' on the operating system level before I executed the unicode preconversion routine in the SID I am attempting to convert. I just tried to process this very same command on the newly created unicode SID and received the very same error the sapinst gave me.

I also have a message out to SAP on this issue.

Thank you again for the assistance.

Doug

Also check note 937983 which describes a problem with field sequence selections caused by a wrong libdbsl.

--

Markus

Hello Doug,

reading these messages, 2 things came into my mind:

1. SAP note 918335

There is a known issue with the R3LDCTL program in the ASCII (!!!) kernel since the necessary control files for export/import are written from programs in the ASCII kernel. Unfortunately the bug occurs first after the reload of the database. Please check if your SAPSDIC.STR contains the entries for the dictionary tables.

2. The issue with "$SAPSYSTEM format error"

Please check if you have the latest version of R3INLPGM in both kernels ASCII and Unicode and corresponding in library R3400. The version in the 3rd library has to be identically with the one from the SAP kernel that is currently applied to the system.

Just a hint right at the end, please follow the guides as close as possible. Especially report RADCUCNT can have some impact and running it again (with the right variant name) might be possible. For details please have a look at SAP note 837173.

Best regards,

René Lang

SAP NetWeaver on IBM System i Development

Hi Goug,

your customer message has been updated. Please have a look.

Regards, René

... and please tell me if it would be okay for you running DIPGNTAB manually. I want to see the content of the joblog. Make a notice into the customer message about this.

Regards, René

Hi Doug,

do we see here the DIPGNTAB.log as well or is this one missing ?

(something similar seems to be there in the middle)

Because I would hope on more information there ...

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

Hello Volker,

Thank you for responding. Here is everything that is in the dipgntab.log:

/usr/sap/BWD/SYS/exe/run/dipgntab=>sapparam(9): environment variable $SAPSYSTEM format error.

-

Begin: NAMETAB OPERATION rewrite of active nametabs ("20070521133520")

-

PARAMETERS FOR NAMETAB OPERATION "read/write of active NT (for NT switch)" :

SOURCE NAMETAB (HEADER TABLE) = DDNTT

SOURCE NAMETAB (FIELDS TABLE) = DDNTF

DEST. NAMETAB (HEADER TABLE) = DDNTT

DEST. NAMETAB (FIELDS TABLE) = DDNTF

OPTION = TT

LIST-TABLE OF TABLENAMES = <NOT SET>

TABLENAME FIELD IN LIST-TABLE = <NOT SET>

START RELEASE (in cp/cmp NT) = <NOT SET>

DEST. RELEASE (in cp/cmp NT) = <NOT SET>

EXTENSION (in cp/cmp NT only) = <NOT SET>

WCONTENT (in cp/cmp NT) = <NOT SET>

FLAGS (in cp/cmp NT) = <NOT SET>

-

-

Didb-lib Version : 1.3

OPTIONS:

PRINT ONLY = no

iNT-TIMESTAMP RESET = no

DELETE iNT = yes

DELETE iNT FIELDS = yes

ACTIVATE iNT = yes

TOLERATE UNCRITICAL STMTs = no

COMPARE TIMESTAMPs IN MV40-Op. = yes

SUPPRESS COMMITs = no

CALL EXTERNAL NT_SYNC = no

DONT TOUCH dep. LOADS = no

RESET FLAG DBTABPOS = no

protocol output to file = no (NULL)

-

rewrite nt "/BI0/ABP_ID00":

Thank you,

Doug

Rene,

Thank you very much for the reply. I will double check for updates for the non unicode kernel and update if need be, The unicode kernel is very up to date and the R3INLPGM is indeed in the kernel library as well as the R3<SID>400 library and the files match each other for creation date.

One thing I did not do is run RADCUCNT from SE38 with those variants. I ran this from SPUMG with the create unicode nametabs menu selection and the report displayed no errors that I am aware of.

Lastly, I am not quite sure where to locate the SAPSDIC.STR file. If you could enlighten me where it is located I would sincerely appreciate it.

Thank you again for your assistance.

Regards,

Doug Slupski

Hi Doug,

report RADCUCNT needs to run again if something has been changed in between (e.g. if the system was running after the first run and Unicode nametab elements have changed). If you are sure that no Unicode nametab relevant changes happened in between the run using SPUMG should be sufficient.

For the file SAPSDIC.STR, I cannot provide a complete path since it depends on the SAPinst version and the involved SAP product. But it is quite easy to find it starting in directory /usr/sap/SAPinst. Just open a Windows share on your iSeries box, go to this directory and let the Windows explorer search for it. The file itself appears first when the export was started and the step with R3LDCTL has been passed.

If unsure if you have the right version of R3LDCTL you can test it easily in front of an export.

1. Signon as user

5. R3ldctl <-- here the ASCII version is required !

Afterwards, you can find all *.STR and *.TPL files needed for the export in this temporary directory, and SAPSDIC.STR as well.

Best Regards,

René