Re: QSECOFR expired, cannot compile -- WDSCI-L

× 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.

Subject: Re: QSECOFR expired, cannot compile
From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
Date: Tue, 22 Jul 2008 10:10:54 -0500
List-archive: <http://archive.midrange.com/wdsci-l>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Websphere Development Studio Client for iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

Justin Taylor wrote:

I proofed the Wiki entry.

The problem happened again this morning, so I contacted IBM.

Which problem happened exactly? An EVFEVENT file was created with MAXMBRS of one? How did that happen? Did you delete an existing one, or did you do a compile in a new library?

Because if neither of those happened, and you had changed the MAXMBRS of al files to *NOMAX, then somehow the MAXMBRS attribute of an existing file got changed, and that's very unusual.

Joe

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.