|
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/
As an Amazon Associate we earn from qualifying purchases.
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.