Already, any user that can run WinSQL* from their PC can change any data they access with SQL commands (update, delete, insert). I would like to prevent this to avoid any disaster.
The WINSQL package is not limited by our green screen application, so it can directly access the database and change data which can be a disaster.
There are two possible options to prevent problems:
- Implement true security architecture and define correct authorities to the files in the data base. This is the "correct" solution but it is difficult and sometime not practical to implement.
- Install a security software package to monitor and control remote access to your data base (or write your own exit program). Example products are firewall++ from Raz-Lee or network security by Powertech.
Dig Deeper on iSeries system and application security
Related Q&A from Shahar Mor
Use work station customize object or printer type in iSeries Access to print the output of an RPG file from the AS/400 to an HP printer. Continue Reading
On the AS/400 library, source files are multi-member. View source files using GET QCLSRC.membername or MGET QRPGSRC.* Continue Reading
Connecting the iSeries in AS/400, issue STRHOSTSVR *ALL. Make sure the as-signon port is in listen state and check the firewall settings. Continue Reading