Re: Writing Commands, how-to manual where?

I like that option also.  And not that we shouldn't be doing it that way, 
but most people have started the other way around and I thought that idea 
I recently read would be a good start.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Douglas Handy <dhandy1@xxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/23/2004 02:21 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
Re: Writing Commands, how-to manual where?






Rob,

>A simple CMD object, without any of the great bells and whistles capable 
>of within a CMD object can be created quite easily from a CL program. 

I actually do it the other way around.  By keeping a copybook of commonly 
used
keywords, I can whip out a CMD object very, very fast.  Then I wrote a 
simple
utility which accepts a command object name as input and bunch of option
settings, and it generates the CL program for me from a variety of 
templates
generating all the DCL's, handling list processing, setting up any 
overrides
needed, and optionally does stuff like setting up OPNQRYF processing, 
submitting
itself to batch, yada, yada.

The command processing capabilities of OS/400 has always seemed woefully
under-utilized by application programmers, IMHO.

Doug
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.