RE: Making command parameters off-limits

Dan - I have e-mailed you privately, (at least that was my intention).
I would just like to take this time to thank everyone for their help. 
If more replies are made, please dont take umbrage with me if there is no 
reply. I start my vacation tomorrow. My parents are flying in from England, and 
my daughter graduates, so I will be celebrating a little. 
If I get chance I will try to sign in from home, otherwise a huge thank you to 
all.
Happy 4th of July (why I as an Englishman am celbrating this I dont know. Oh 
yeah - beer).

>>> "Bale, Dan" <D.Bale@handleman.com> 06/19/01 12:54PM >>>
I neglected to mention in my first reply that, if you are thinking about
rolling your own WRKSPLF, I have such an animal that I'd be willing to
share (actually compliments of Mike Cravitz from eons ago).  It utilizes
UIM - pretty cool.  I use it to substitute my own options like CPYSPLF
and the recently talked about CVTSPLSTMF (convert spool files into PDF &
HTML!), supplying the job and spool data for the appropriate prompts.

If anyone is interested, please contact me PRIVATELY!  It's too large to
post on the list.  The WRKSPLF-like utility can run on V3R2 and higher.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952
D.Bale@Handleman.com 
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)

-------------------------- Original Message --------------------------

> -----Original Message-----
> From: Phil [SMTP:sublime78ska@yahoo.com] 
> Sent: Tuesday, June 19, 2001 9:50 AM
> To:   MIDRANGE-L@midrange.com 
> Subject:      RE: Making command parameters off-limits
> 
> There's another resoure = "Desktop Guide to Creating CL Commands" by
> Lynn
> Nelson".  It's a News/400 book.  ISBN 1-882419-56-1.  This book
> explains
> pretty good how to create validity checking programs and commands.
> The most
> difficult part is understanding how the parameters are passed.  This
> book
> covers that pretty good.  For something like your own wrksplf command,
> I
> think (I could be wrong) that you need to use UIM and the list api's.
> This
> will be more work than the validity checking program.  (Someone on the
> list
> was talking about writing a book on UIM, and maybe releasing it a
> chapter at
> a time.  I'm looking forward to that.)  There is a UIM book (very old)
> by
> either News/400 or Midrange Computing.  It's basic, though.  For V3
> (maybe
> V2) there was a display programming manual which had a few chapters on
> UIM.
> If I come across either of these I'll post the titles.
> 
> Phil
> 
> 
> 
> -----Original Message-----
> From: owner-midrange-l@midrange.com 
> [mailto:owner-midrange-l@midrange.com]On 
> Behalf Of alan shore
> Sent: Tuesday, June 19, 2001 9:04 AM
> To: MIDRANGE-L@midrange.com 
> Subject: RE: Making command parameters off-limits
> 
> Well - FYI - I attempted to look at this book (V4r3) online, and it is
> no
> longer available. The same for V3r7.
> Interesting
> 
> >>> "MCPARTLAND, Stan" <stanley.mcpartland@bently.com> 06/18/01
> 04:57PM >>>
> Alan,
> 
> A validity checking program will allow you to provide additional
> validity
> checking for a command.  You control who can specify what values for a
> command parameter, whether the user can execute this command in this
> environment, etc.  See 9.11 Writing a Validity Checking Program in the
> CL
> Programming manual (SC41-5721).  Be sure to have good testing and
> change
> management on any validity checking programs you write.
> 
> Regards,
> Stan

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---