Re: Problem with Search->iSeries

Hey Adam,

Do you have any other messages?
I think I may have seen this before, and it seems to be related to the
events file reaching a limit.
Try  DLTF *CULIB/EVFEVENT and see if that helps, otherwise try changing the
events file so that it has a larger size limit.

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab



wdsci-l-bounces@xxxxxxxxxxxx wrote on 01/04/2007 11:22:13 AM:

Hi all,

I was looking for the code that used a specific message ID this morning.

I

did a couple of iSeries searches, some of which I cancelled when I
realized I had an incorrect library or member name.  The only other
unusual searching thing I've done recently is to run FNDSTRPDM from the
command line (troubleshooting from home last night). Now, I am getting

the

following in the iSeries Commands Log:

------------------------------------------------------------
FNDSTRPDM STRING(MSGID) FILE(LTL38/QRPGLESRC) MBR(RS*) OPTION(*NONE)

COL(1

*RCDLEN) CASE(*IGNORE) PRTRCDS(*ALL *CHAR) PARM(*EVENTF)
 Searching member . MEMBER
<list of members searched>

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.
Function check. MCH3601 unmonitored by QQDAPROC at statement *N,
instruction X'0199'.
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.
------------------------------------------------------------

FNDSTRPDM still works just fine from the command line.  I've never seen
this error before, and I can't find anything similar in the archives.  I
did find a report of EVFEVENT getting too full, and tried deleting
EVFEVENT in my CURLIB to see if recreating the event file would make a
difference, but no luck there.  I'm at WDSC v6 with all updates, and V5R4

on the i.

Any ideas would be appreciated,
Adam