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



> Martin Rowe
>There was a HISTORY
>command written in '97 from MC (?) that can pull out commands for a job,
>but it's limited to the selected job. F9 retrieval is okay, but very
>limited (no search, and only backwards scrolling - miss the one you want;
>start again :-( ).

> James Rich
>Now maybe I won't *have* to
>press that *@#$ F4 key all the time just to get some work done.  I don't
>have fingers to waste on typing those stupid keywords.

If you work from QCMD you can scroll back through your old commands, point
your cursor to the one you want to repeat, and press <F9>.

My first job was with a System 38 shop working on overutilized remote
systems over incredibly slow lines/modems.  We learned pretty quickly that
while prompting was neat, every interaction with the processor was a waste
of time.  Now I work with a lot of AS/400 doubters who confuse me by
referring to the AS/400 as a prompt-driven, menu-driven system.  To me, the
AS/400 had a logical, intuitive command set facilitating memorization and
direct command input.  The prompts, field-sensitive help, and menus were a
nice layer on top of that command set.

I've always worked from the QCMD (or QCL) Command Entry command line instead
of the MAIN menu command line.  I rarely prompt a command, and usually don't
type keywords unless I'm forced.  Back when SBMJOB required Request Data
instead of a Command (and back when you had to submit Copy Files to batch :)
) I used to be able to type fairly complex copies as batch submits and press
<enter> with the confidence that they would run successfully.  When I used
to program I'd fill the SEU screen with blank lines with an RPG C spec
format at the top and fill in a page before pressing <enter> for syntax
checking.  I'm sure many of you work the same way.

One of the things I've admired about Unix admins has been their desire to
work the way I work -- straight off the command line from memory, and taking
advantage of creative command sequences and scripts.  What I love about the
AS/400 command set is field-sensitive help and the ability to construct a
difficult command through prompting.  What I'd love to steal from Unix is
the ability to pipe commands to commands.

Also, the user defined options in PDM are kick-ass.  If they'd carry that
into the IFS Kenneth Graap would have a great answer to his original
question.

At two jobs I've been shot down on this, but I believe that any AS/400
developer, admin, or operator with command line access should have an
initial prompt from QCMD Command Entry -- not from a menu.  Go into PDM or
the menus as needed, but exit back to Command Entry as your primary
environment.  This, I think, is the best way to really learn the system.

-Jim

James P. Damato
Manager - Technical Administration
Dollar General Corporation
<mailto:jdamato@dollargeneral.com>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.