LPEX Line number or sequence number -- 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: LPEX Line number or sequence number
From: David FOXWELL <David.FOXWELL@xxxxxxxxx>
Date: Wed, 14 Nov 2007 12:54:22 +0100
Accept-language: fr-FR, en-US
Acceptlanguage: fr-FR, en-US
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>

Summin's changed between V5 and V6.

I used to look at my compile listing on the greenscreen to get the sequence number of the error message and then type that number with ctrl l. Now it's taking me to the line number instead, so I can't find the line that caused the error.

Have to it this way cos still can't get the errors back to WDSc with /*EVENTF in the compile command.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: LPEX Line number or sequence number , adrian

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.