×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




The quick dirty way would be to create your own SIGNOFF command and rename
the IBM one to something that only you know.

Thanks,

Mark

Mark D. Walter
Senior Programmer/Analyst
CCX, Inc.
mwalter@xxxxxxxxxx
http://www.ccxinc.com


|---------+------------------------------->
|         |           Loyd Goodbar        |
|         |           <loyd@xxxxxxxxxxxxxx|
|         |           >                   |
|         |           Sent by:            |
|         |           midrange-l-bounces@m|
|         |           idrange.com         |
|         |                               |
|         |                               |
|         |           11/01/2003 04:02 PM |
|         |           Please respond to   |
|         |           Midrange Systems    |
|         |           Technical Discussion|
|         |                               |
|---------+------------------------------->
  
>------------------------------------------------------------------------------------------------------------------------------|
  |                                                                             
                                                 |
  |       To:       Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>                                              |
  |       cc:                                                                   
                                                 |
  |       Subject:  Re: Method to Remove *NOLIST Capability from IBM Signoff 
Command                                             |
  
>------------------------------------------------------------------------------------------------------------------------------|




If the SIGNOFF command doesn't have a validity checking program (I'm not at
a
400 to find out), you could write your own VCP that disallows the *NOLIST
value.

This is playing with fire since you'd be modifying an IBM command object.

HTH,
Loyd

On Sat, 1 Nov 2003 12:38:26 -0500, "William N. Harrell, Jr."
<wharrell@xxxxxxxxx> wrote:

>We would like to remove the *NOLIST capability on the Signoff Command on
our
>system to prevent users up to those having ALLOBJ from signing off their
>interactive job without creating a job log.
>
>What is everyone's suggestion for cleanly handling this ?

--
Mediocrity: It takes a lot less time and most people won't notice
the difference until it's too late. <http://www.despair.com/>
loyd@xxxxxxxxxxxxxx  ICQ#504581  http://www.blackrobes.net/


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







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