RE: Default for command without default value?

No, it seems like you understand my point.  We just differ.  I feel that
the command should be consistent, qualified or not.  You feel that there
should be some 'back door' to override the efforts to standardize a shop.

That is good news about those library special values though.  Not 100% but
it is a least a piece of kibble to munch on.

Rob Berendt

==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.


                                                                                
                                         
                    "Ed Fishel"                                                 
                                         
                    <edfishel@us.ibm.co        To:     MIDRANGE-L@midrange.com  
                                         
                    m>                         cc:                              
                                         
                    Sent by:                   Subject:     RE: Default for 
command without default value?               
                    owner-midrange-l@mi                                         
                                         
                    drange.com                                                  
                                         
                                                                                
                                         
                                                                                
                                         
                    08/06/2001 09:07 AM                                         
                                         
                    Please respond to                                           
                                         
                    MIDRANGE-L                                                  
                                         
                                                                                
                                         
                                                                                
                                         





Rob,

>>Why do they give a rats a$$ if the command was qualified?  On second
thought, I don't care.  I want it to work anyways.  When I add the exit
point I specify the library containing the command anyways.<<

I am not sure that I understand your point. Command that are qualified with
a specific library name, such as QSYS/command, cannot be changed by the
change command exit program while those that are qualified with *NLVLIBL,
*SYSTEM, *LIBL, or not qualified at all, can be changed. The reason we
designed it this way was to allow applications (and the system) to indicate
that they did not want the commands they use changed. It works very much
the way it did with commands placed in a library ahead of QSYS. Before
these exit points existed, applications could library qualify their
commands to prevent their programs from using an unknown command from a
library ahead of QSYS.

Ed Fishel,
edfishel@US.IBM.COM


+---
| 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
+---




+---
| 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
+---