What could be cause of this error message?

kkocheganov

Member
Hi everyone.

This night brought the following error message when of of R49500 for a shipment of 337 lines was executing for a long time and was killed by CNC. The shipment was for a ST-OT from main b/p to other coutry b/p (so there must be invoice printed (called through a document set).

MCH3601 Escape 40 12/06/15 01:44:11,870286 < gHighUse4K 000110 JDELIB B7334SYS *STMT
From Program . . . . . . . : stringHighUse4K
To module . . . . . . . . . : JDE400U
To procedure . . . . . . . : BlankFillStr
Statement . . . . . . . . . : 3
Message . . . . : Pointer not set for location referenced.
Cause . . . . . : A pointer was used, either directly or as a basing pointer, that has not been set to an address.

JDE version is B7334, running at AS/400.

What do I expected to see in submitted jobs is the following UBEs completed - R49500 (calling batch), R47500, R4981, R5942565(customisation of R42565).

What do I see - R47500 (thanks God) completed successfully and I didn't lost integrity for F41021/F4111, R4981 is also done, but R49500 was still running, no invoce for a customer printed...

So, any idea/similar experience with printing big invoices in a foreign country (repricing is switched on in invoice print)?

Thanks everyone in advance
 
When you state for a foreign country - is that a doublebyte country ? ie, Japan or China ? It sounds like the PDF creation is where the issue lay - and the error seems to have something to do with abusing the size of a string...
 
You need to provide some more info about your installation for a start.
The error you have found may just be because the job was cancelled.

http://www-01.ibm.com/support/docview.wss?uid=nas8N1019244
MCH3601 is normally useless in finding the cause of this type of problem. Message MCH3601 happens as a result of storage corruption that might have happened in a previous program CALL.

I would suggest you have a problem with your customisation in R5942565, seeing as that is the only bit that didn't complete normally.

Can you reproduce the problem using R42565?
Can you reproduce the problem on a fat client running locally?
Can you reproduce the problem somewhere with logging turned on, so you can find the last actions before the MCH3601?
 
Hi everyone.

This night brought the following error message when of of R49500 for a shipment of 337 lines was executing for a long time and was killed by CNC. The shipment was for a ST-OT from main b/p to other coutry b/p (so there must be invoice printed (called through a document set).

MCH3601 Escape 40 12/06/15 01:44:11,870286 < gHighUse4K 000110 JDELIB B7334SYS *STMT
From Program . . . . . . . : stringHighUse4K
To module . . . . . . . . . : JDE400U
To procedure . . . . . . . : BlankFillStr
Statement . . . . . . . . . : 3
Message . . . . : Pointer not set for location referenced.
Cause . . . . . : A pointer was used, either directly or as a basing pointer, that has not been set to an address.

JDE version is B7334, running at AS/400.

What do I expected to see in submitted jobs is the following UBEs completed - R49500 (calling batch), R47500, R4981, R5942565(customisation of R42565).

What do I see - R47500 (thanks God) completed successfully and I didn't lost integrity for F41021/F4111, R4981 is also done, but R49500 was still running, no invoce for a customer printed...

So, any idea/similar experience with printing big invoices in a foreign country (repricing is switched on in invoice print)?

Thanks everyone in advance

Hi everyone.

Finally got some time to look further into the problem and it seems I've a problem with R42950 called from invoice print.
Just made a test with a shipment with more than 500 lines (and switched off the call of repricing from R5942565 version) -> no issue at all.

Another test shipment with same number of lines but with a call of R42950 failed with the same symptoms.

Thanks everyone for the comments/advises.

@Altquark, I'll proceed with debugging of R42950, it's not a doublebyte country but it might be related to a pdf creation (if shipment not exceeding 210-215 lines - everything works fine

@David Robertson, thanks for the idea of eliminating possible causes (just by the advise to use R42565).
 
Back
Top