Re: find string ends with dump

There is a PTF recently for fixing a similar problem. Could you please
apply and see if it fixes your problem? (the problem it fixes should
occur both in RDi and green screen though)

V5R4M0 PTF 5722SS1 SI35775
V6R1M0 PTF 5761SS1 SI35776

Thanks,

Xuan Chen, Problem Determination Tools for IBM i
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx





ssc1478 <ssc1478@xxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
02/11/2009 10:54 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] find string ends with dump






Using RDi 7.5.0.3, I tried the Find String option on a source file
with approx 6000 members.

It ended with a dump. It works fine if ran from the green screen.
Has anyone else encountered this problem? Below is the error message.

Thanks!
Phil

***** error:
Receiver value too small to hold result.

Dump output directed to spooled file 1, job 304789/QUSER/QZRCSRVS
created on system SYS1 on 11/02/09 10:42:59.
Cause . . . . . : Dump output is being directed to a spooled file.
Function check. MCH1210 unmonitored by QQDAPROC at statement *N,
instruction X'01EF'.
Cause . . . . . : An escape exception message was sent to a program
which did not monitor for that message. The full name of the program
to which the unmonitored message was sent is QQDAPROC . At the time
the message was sent the program was stopped at higher level language
statement number(s) *N. If more than one statement number is shown,
the program was a bound program. Optimization does not allow a single
statement number to be determined. If *N is shown as a value, it means
the actual value was not available. Recovery . . . : See the low
level messages previously listed to locate the cause of the function
check. Correct any errors, and then try the request again.
Error while processing the FNDSTRPDM command.
Cause . . . . . : An error occurred while processing the FNDSTRPDM
command. See messages previously listed. Recovery . . . : Correct
errors and submit the command again. If the problem recurs, see the
Operator's Guide.