|
Henrik, There are too many menus and programs with SIGNOFF embedded. As far as OFF, we too came from a S/36 environment. As part of each OS upgrade we do a DLTCMD OFF CRTDUPOBJ of SIGNOFF to OFF Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Henrik Krebs" <hkrebs@xxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 11/01/2003 03:02 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To <midrange-l@xxxxxxxxxxxx> cc Subject Re: Method to Remove *NOLIST Capability from IBM Signoff Command "William N. Harrell, Jr." 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. "Joe Pluta" wrote: > Once you've gotten that straightened out, my guess would be to try to > write my own SIGNOFF command that didn't have a *NOLIST option and put > it higher on the system library list. Higher in the system library list than QSYS? This involves a special library for this purpose. Why not give it its own name (say 'OFF') and revoke the authority to SIGNOFF. You know that you can change the commands used for the Sys Rq menu (They are defined in a text in a message). Henrik http://hkrebs.dk _______________________________________________ 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 mailing list archive is Copyright 1997-2025 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.