Error message MCH3602 running 'CALL PGM(SAPDV6UPG/R3UPCHGJRN)

[steven_glennie]

Hello Group,

We are in phase MAIN_UPTRANS/STARTSAP_PUPG after downtime from an ECC EHP4 upgrade to EHP7 on SAP on iseries.

However, the upgrade has stopped when trying to start the SAP system for the final time. We are receiving the following error so seems to be an issue with journals ahead of starting the SAP system.

Last error code set: SAPupdbdb4.c:1014: Error message MCH3602 running 'CALL PGM(SAPDV6UPG/R3UPCHGJRN) PARM('R3DV6DATA' 'QSQJRN' 'R3DV6JRN' 'QSQJRN0004' '*NO')'.

I can see from searches MCH3602 means "Pointer not valid for requested operation" but this is not helping resolve.

Has anyone come across this before ? Any help would be much appreciated. We have raised SAP message 329643 for those with access, but I thought

I would try this group as well.

Best regards,

Steven

[steven_glennie · Accepted solution]

Hello Group,

Just to follow up that SAP helped move past the upgrade issue with journals, but we do not have an explanation why this did not work. Below is the response from SAP

I could not catch the reason for the MCH3602 error since it simply did not occurred when the debug version was used. I will try to recreate it with an SAP in house system by using the SUM SP17 you currently have with the same upgrade path. It's not the first time I found that debug program versions hide pointer issues somehow... Fixing such issues is time consuming but possible.

Best regards,

Steven

[volker_gldenpfennig · Accepted solution]

Hi Steven,

first of all, very good, that your issue got solved really quick ;-))

But, this sounds like a translator bug ;-((

... really ugly thing ...

good luck,

Regards,

Volker Gueldenpfennig, consolut international ag

[jpuigserver]

Hi,

Do you have the last PTF applied? We performed the same upgrade and experienced some similar errors that were solved applying them.

It looks like a typical support response but we have had to open a message with IBM in order to solve it

Rgds,

Jaume

[Former Member]

SF99776                   4  Installed

SF99775                  17  Installed

SF99769                   1  Installed

SF99767                   2  Installed

SF99766                   3  Installed

SF99759                   7  Related g

SF99747                  14  Installed

SF99721                   5  Installed

SF99720               16127  Installed

SF99719                  67  Installed

SF99719                  65  Installed

SF99718                  33  Installed

SF99717                   4  Installed

SF99716                   9  Installed

SF99715                  24  Installed

SF99714                   4  Installed

SF99713                  15  Installed

SF99711                   3  Installed

SF99711                   2  Installed

SF99709                 156  Related g

SF99709                 126  Related g

SF99708                  50  Related g

SF99708                  35  Related g

SF99707                  11  Related g

SF99707                   9  Related g

SF99706                   9  Related g

SF99706                   7  Related g

SF99705                  24  Related g

SF99705                  12  Related g

SF99702                  12  Installed

SF99701                  38  Related g

SF99701                  32  Related g

SF99658                   3  Installed

SF99657                   2  Related g

SF99647                  13  Related g

SF99647                   9  Related g

SF99637                   9  Related g

SF99637                   8  Related g

SF99627                  11  Related g

SF99627                  10  Related g

SF99617                   6  Related g

SF99572                  23  Related g

SF99572                  18  Related g

SF99481                   8  Installed

SF99480                   6  Installed

SF99381                  14  Related g

SF99381                   9  Related g

SF99380                  14  Related g

SF99380                  11  Related g

SF99369                  16  Related g

SF99369                  15  Related g

SF99368                  37  Related g

SF99367                   9  Related g

SF99367                   8  Related g

SF99366                  12  Related g

SF99366                  11  Related g

SF99364                   9  Related g

SF99363                  18  Related g

SF99363                  16  Related g

SF99362                  53  Related g

SF99362                  40  Related g

SF99359                  23  Related g

SF99359                  17  Related g

SF99145                   9  Installed

[volker_gldenpfennig]

Hi Steven,

obviously, you are using the option of turning off archiving during downtime. I would recommend for further upgrades, to not use this option, as it doesn't make any sense ... the biggest part of the JRNRCVs is created during uptime anyway ...

I would try the following:

Change the journals to delete no manually and try again ... If you did this already, delete all receivers except the last one and turn back to autodelete and try to repeat with this ...

for your futire upgrades, this should never hurt you, as this coding wil be skipped because of the different settings in the beginning.

good luck,

Regards,

Volker Gueldenpfennig, consolut international ag

[Former Member]

Hi Volker,

I am working with Steven on this issue.  We did try your above recommendation, but are still receiving the error. 

Any other ideas?

Thanks,

Brady

[volker_gldenpfennig]

Hi Brady & Steven,

I'm sorry, then I would have no further idea as well ...

... already looking forward to your solution later on 😉

good luck,

Regards,

Volker Gueldenpfennig, consolut international ag