IFS command question -- 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: [WDSCI-L] IFS command question
From: "David Gibbs" <david@xxxxxxxxxxxx>
Date: Wed, 28 Aug 2002 09:40:15 -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/cgi-bin/listinfo/wdsci-l>,<mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/wdsci-l>,<mailto:wdsci-l-request@midrange.com?subject=unsubscribe>
Newsgroups: gmane.editors.websphere.iseries
Organization: midrange dot com

I just noticed something odd ... in the RSE command window, there are fields
at the bottom to allow the user to enter iSeries and IFS commands.

What good is this function if I can't see the results of the command after
it's done processing?  Since RSE's host component is (more or less) batch,
it seems like a trivial task to pull the last spool generated and display it
in the window.

For the IFS commands, which are executed using QSH, it should be easy to
capture stdout & stderr and display those to the user.

Pardon me for saying so, but it seems like there are a lot of reasonably
good ideas in WDSC ... but they are only half implemented.

david

--
David Gibbs
Sr. Software Engineer / R&D / MKS Inc., www.mks.com
Lombard, IL, USA; tel: 630-495-2108; fax: 630-495-3591
Build Better Software

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.