×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
While the fact that in list displays, option 4 (delete or end job) and
option 5 (display, work with, &c.) are right next to each other on your
keyboard, can occasionally lead to a sudden feeling of tightness in the
chest, they at least usually have confirmation screens that can stop you
from destroying things.
Likewise, shutting down a system usually doesn't do any permanent
damage. And with most delete commands, you know what you're deleting.
Not so with DLTUSRPRF OWNOBJOPT(*DLT). You might think you're only
deleting some miscellaneous QSYS objects the user created, but remember,
the IFS doesn't respect OWNER(*GRPPRF) on a user profile, even if it's
set and the user HAS a group profile, and depending on the application,
a user who has no reason or ability to create so much as a single QSYS
object could own THOUSANDS of programmatically-created IFS objects that
nobody is likely to notice until it's too late to recover them.
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: My nomination for the single most dangerous command on an IBM Midrange box, (continued)
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.
midrange.com
