Re: WDSCI and EGL -- WDSCI-L

Subject: Re: WDSCI and EGL
From: "Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>
Date: Sun, 8 Apr 2007 18:55:36 -0400
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>

Sure, but did the previous target versions of COBOL support embedded SQL?

I'm asking out of ignorance, I really don't know.

Yes they did.

Generated W-code is a different issue. I can see debugging from the EGL

level, but as I point out this would require a cooperation between the EGL
and ILE teams that simply doesn't exist today.

Agreed re co-operation - that crew barely recognize a System i when they
trip over one. The W-code is a little different issue as it is a platform
neutral language with back-end support on all IBM platforms. That's why it
should be the target rather than COBOL. It should simplify their platform
issues since code-gen would be fundamentally the same for all platforms
whereas today they have to make substantial changes to optimize for each
target platform.

Jon Paris
Partner400

www.Partner400.com

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: WDSCI and EGL , Joe Pluta

This mailing list archive is Copyright 1997-2025 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.