This is in response to the "Commands to Avoid Running in QINTER" article in the November 1990 issue.
I agree that the commands listed should never be run interactively. But no matter how often people hear this, someone always thinks "one time won't hurt anything." To prevent people from executing commands interactively, the following command should be executed from each command to restrict:
CHGCMD CMD(xxx) ALLOW(*BATCH *BPGM)
This will issue an error message, CPD0031 - Command xxx not allowed in this setting, when someone attempts to run the command interactively.
Just a few notes on using this technique. The CHGCMD should be coded in a CL program so that the same commands can be issued when a new release of the operating system is installed. Also, you should *EXCLUDE the public from using the CHGCMD, because they could change it right back!
Louise Best Milwaukee, Wisconsin
Editor's Note:
The technique shown above will work provided that there are no interactive programs that legitimately run the commands being blocked. In order for this technique to work better, each command should be changed by issuing:
CHGCMD CMD(xxx) ALLOW(*BATCH *BPGM *IPGM *EXEC)
If you are on Release 3.0, you may wish to consider adding *BREXX and *IREXX if you are considering using REXX.
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online