UNICODE upgrade - missing R3lsctl

[Former Member]

We are on an as/400 v7r1 system running an upgrade from ASCII to UNICODE on a 4.7 SAP system.

When we start the sapinst.exe we get thru a few steps then the upgrade stops because R3ldctl is missing.

We loaded patch R3ldctl_9-20000359.SAR with APYR3FIX but this looks like it loads R3ldctlDB4.

We copied over a version of R3ldctl from another direcory and the job failed.

Error message from sapinst.exe is below

An error occurred while processing service DB2/iSeries ASCII/Unicode Conversion Kit > ASCII ABAP Database Content Export

( Last error reported by the step :TMKSVR Exception translating call parameters: changeCallForO4Spawn: "\usr\sap\T03\SYS\exe\run\R3ldctl" could not be resolved..). You may now

press Retry to repeat the current step.

press the View Log button to get more information about the error.

stop the task and continue with it later.

Log files are written to Z:\usr\sap/SAPinst/NW04S/EXP.

Where can we get R3ldctl ?

Thanks

[former_member195641 · Accepted solution]

Hello Matt,

from your first posting I asume you hav an R/3 4.7 system which may run with 620 kernel or 640 downward compatible kernel. I think you are running a 640 kernel, isn't it? In this case you have to download the patch R3ldctl (last shipped patch was version 28 from 2010). Be careful, unfortunately, there is another patch with patch level 7 written in uppercase letters. This is the wrong one. You have to use file

R3ldctl_28-20000357.SAR in case of ASCII (means during the export procedure) and/or

R3ldctl_28-20000565.SAR in case of UNICODE (means during the import procedure)

To implement the patch you have to use command APYR3FIX as usual. In addition, even usual for kernel 640 and higher, you have run the command APYR3KRN after the last run of APXR3FIX to sync correctly the ILE and PASE parts of your kernel. The APYR3KRN command also creates the link R3LDCTLDB4 (without the DB4 extension) in your kernel directory.

The most strange thin in your posting is the given path to the logfiles:

Z:\usr\sap/SAPinst/NW04S/EXP
                       ^

The letter S in NW04S points to a 700 base toolkit. One of the differences between 640 and 700 on OS400 is the way how R3ldctl works. In 640 it is an ILE program called R3LDCTLDB4 and in 700 it is a PASE program called R3ldctl. Both are not compatible to each other. Please make sure to use the right toolkit. You wil need:

Toolkit 640 SR1 Patch Collection

It includes a 640 SAPinst which expects a R3LDCTLDB4 program. If you are still in doubt please open a customer ticket and provide a telnet connection.

Best regards,

Renu00E9 Lang

SAP on IBM i Development

[Former Member · Accepted solution]

Thanks

I am looking for the patches you mentioned.

Which unicode intsall kit do we need to upgrade a r/3 4.7 ascii system to unicode?

Thanks

[Former Member · Accepted solution]

Hi Matt,

as you are using 4.7, you should use the CPC InPlace Kit based on 6.40, that you are obviously using already )

Regards

Volker Gueldenpfennig, consolut international ag

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

[Former Member · Accepted solution]

Thanks Volker, we cant seem to find the control.xml that uses R3ldctldb4 - the 3 versions we have a seem to point to R3ldctl the later version.

[former_member195641 · Accepted solution]

Hello Matt,

it seems the whole thing gets a little complicated. The CPC InPlace Kit for 640 is disappeared on the SMP. This one would be the right one for you which should run without any manual workarounds. But as we know now, it's no longer an option.

The currently available CPC Kit is based on the installation kit for NW 7.0, but has this bug you found with the XML. Finally, the CPC InPlace Kit for NW 7.0 will be able to run the CPC for 640 systems too. I informed the developer.

The 3rd option at the moment is the common 640 Patch Collection which contains a recent setup of installation tools. The biggest disadvantage is the missing support for the inplace codepage conversion. Only the R3load version is available.

Finally, the most pragmatic solution (if you want to use the inplace conversion) is to create a symbolic link in the kernel directory to fulfill the need of a programm called R3ldctl. run following command before you start the SAPinst:

ADDLNK OBJ('/usr/sap/SID/SYS/exe/run/R3LDCTLDB4')
NEWLNK('/usr/sap/SID/SYS/exe/run/R3ldctl') LNKTYPE(*SYMBOLIC)

Please keep in mind, even this is a workaround and just a hint. If unsure about this, please open a customer message and require a patch for the CPC InPlace Kit.

Regards, René

[Former Member · Accepted solution]

Thanks Rene!

The addlnk worked OK - We had to do the same thing with

ADDLNK OBJ('/usr/sap/T03/SYS/exe/run/R3SZCHKDB4') NEWLNK('/usr/sap/T03/SYS/exe/run/R3szchk') LNKTYPE(*SYMBOLIC)

The export is running now.

[Former Member]

The export ran for about 3.5 hrs and 3 jobs of 16 failed. The failing jobs are

ERROR: 2011-10-11 11:07:08 com.sap.inst.migmon.LoadTask run

Unloading of 'SAPPOOL' export package is interrupted with R3load error.

Process '/usr/sap/T03/SYS/exe/run/R3load -e SAPPOOL.cmd -datacodepage 4102 -l SAPPOOL.log -stop_on_error' exited with return code 2.

For mode details see 'SAPPOOL.log' file.

Standard error output:

¢u2014u2014u2122u201Dz@¢u2014u2122u2021¥M@u2122u2021u0192k@u2122u2021¥]@u02C6¢@u2022u2013£@u201Au2026u2026u2022@u0192u201Cu201Cu2026u201EK%¢u2014u2014u2122u201DMñu0192]z@Õu2013@×u2122u2013u2020u2030u201Cu2026@¤¢u2026u201EK%¢u2014u2014u2122u201Dz@âÁ×âèâãÅÔÕÁÔÅ@u2022u2026u2030£u02C6u2026u2122@u2030u2022@×u2122u2013u2020u2030u201Cu2026@u2022u2013u2122@u2030u2022@Ãu2013u201Du201Du2022u201Eu201Cu2030u2022u2026%

ERROR: 2011-10-11 11:10:26 com.sap.inst.migmon.LoadTask run

Unloading of 'SAPSDIC' export package is interrupted with R3load error.

Process '/usr/sap/T03/SYS/exe/run/R3load -e SAPSDIC.cmd -datacodepage 4102 -l SAPSDIC.log -stop_on_error' exited with return code 2.

For mode details see 'SAPSDIC.log' file.

Standard error output:

¢u2014u2014u2122u201Dz@¢u2014u2122u2021¥M@u2122u2021u0192k@u2122u2021¥]@u02C6¢@u2022u2013£@u201Au2026u2026u2022@u0192u201Cu201Cu2026u201EK%¢u2014u2014u2122u201DMñu0192]z@Õu2013@×u2122u2013u2020u2030u201Cu2026@¤¢u2026u201EK%¢u2014u2014u2122u201Dz@âÁ×âèâãÅÔÕÁÔÅ@u2022u2026u2030£u02C6u2026u2122@u2030u2022@×u2122u2013u2020u2030u201Cu2026@u2022u2013u2122@u2030u2022@Ãu2013u201Du201Du2022u201Eu201Cu2030u2022u2026%

ERROR: 2011-10-11 14:48:42 com.sap.inst.migmon.LoadTask run

Unloading of 'SAPCLUST' export package is interrupted with R3load error.

Process '/usr/sap/T03/SYS/exe/run/R3load -e SAPCLUST.cmd -datacodepage 4102 -l SAPCLUST.log -stop_on_error' exited with return code 2.

For mode details see 'SAPCLUST.log' file.

Standard error output:

¢u2014u2014u2122u201Dz@¢u2014u2122u2021¥M@u2122u2021u0192k@u2122u2021¥]@u02C6¢@u2022u2013£@u201Au2026u2026u2022@u0192u201Cu201Cu2026u201EK%¢u2014u2014u2122u201DMñu0192]z@Õu2013@×u2122u2013u2020u2030u201Cu2026@¤¢u2026u201EK%¢u2014u2014u2122u201Dz@âÁ×âèâãÅÔÕÁÔÅ@u2022u2026u2030£u02C6u2026u2122@u2030u2022@×u2122u2013u2020u2030u201Cu2026@u2022u2013u2122@u2030u2022@Ãu2013u201Du201Du2022u201Eu201Cu2030u2022u2026%

Unfortunatley the log files for sappool.log, sapsdic.log and sapclust.log are not readable.....

[former_member195641]

Hi Matt,

I think it doesn't make sense to track this any longer in the SDN. Please open a ticket on component BC-OP-AS4 and provide Telnet access and credentials for the SIDOFR user.

BTW, the logs are readable but are in EBCDIC. For SAPPOOL.log, the standard error simply says:

sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

Go to the IBM i machine and navigate to the given files with WRKLNK and use option 5 to try to read it. I'm pretty sure you will find a "real" reason for the errors.

Regards, René

[Former Member]

Hi Matt,

are you sure, that you checked for the correct release of r3ldctl ?

Because, r3ldctldb4 is the ILE version of r3ldctl and I would guess ( I didn't check ), that this was ok for 6.40, but would be not ok for 7.0x.

You need to patch r3ldctl of that release, that you are using right now and the use APYR3FIX up to 7.01 ...

Regards

Volker Gueldenpfennig, consolut international ag

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

[Former Member]

Not sure what the correct version of R3dlctl is as the install program said it was was missing.