×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I can confirm that if the EVFEVENT file does not exist in my current
library (as set by the RSE connection properties) the Find Text option
will create it with MAXMBRS(1). A compile will create the EVFEVENT file
with MAXMBRS(*NOMAX). If the EVFEVENT file already exists then neither
the find text or compile options will create it, and if it exists with
MAXMBRS(1) the compile will silently fail.
I can not think of any fix other than to ensure that the EVFEVENT file
already exists with MAXMBRS(*NOMAX) in the connection's current library.
I think that if you select *CRTDFT as your current library, then the
EVFEVENT file will be located in QGPL, but I am not certain.
Best regards,
Paul
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Justin Taylor
Sent: 29 July 2008 22:32
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] QSECOFR expired, cannot compile
We had the problem again today of an EVFEVENT file being created with
MAXMBRS(1).
I did a little trial-and-error and think that I found the cause. If I
run an iSeries Search and no EVFEVENT file exists in my current library,
it creates one with MAXMBRS(1). If I run a compile and no EVFEVENT
exists, it creates one with MAXMBRS(*NOMAX). If an EVFEVENT exists with
MAXMBRS(1), the compile fails. I had another developer try this and it
does the same thing for him.
Can anyone confirm this?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.