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



On Mon, 15 Oct 2001, Scott Klement wrote:

> I always prefer a command line.   However, the syntax to type the equiv
> command is _not_ overly cumbersome, IMHO.
>
> just type:
>
>         STRSEU LIB/FILE MEMBER

Hmm... If I choose option 5, then exit, then press F9 I get:

STRSEU SRCFILE(BMERAWO/QRPGLESRC) SRCMBR(WO5100IR) OPTION( 5)

I guess this is the cumbersome command I was referring to.  But as it has
been pointed out already all those keywords are not necessarily required.

> It's certainly no more work than:
>
>          vi /usr/local/etc/myfile.conf
>
> Granted, the command name is longer, but the lack of complexity in the
> pathname still makes it shorter.

Unless you are using tcsh or bash in which case you type in:

vi /u[tab]lo[tab]e[tab]myf[tab]

and let the shell fill in the rest for you.

An equally interesting topic is why the *$#% IBM decided to go with such a
flat filesystem.  I honestly don't understand or know of any reason to do
so.  It seems to me that a deep filesystem (one with many levels of
directories) is an advantage.

> Also, you can type STRSEU by itself to bring up the last member that you
> changed, which isn't as simple in Unix.

Well SEU is a program that runs, not a command syntax.  You could
certainly create a program that opened the file you modified and run it on
a unix system.  The underlying OS has nothing to do with that.

James Rich
james@eaerich.com



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.