V5R2 value setting criteria has changed. I have always had this set at a low number (0-). Now, to auto configure...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
virtual devices, this setting must be set to a high (calculated, I believe) number. I currently have 3000 plus configured virtual devices. Can you provide more detail on the new value requirements and any potential security risks by having this continuously set to a high number? The real danger with this system value is leaving it at *NOMAX. *NOMAX allows someone to create a denial of service attack by filling your system with virtual devices. You should be able to set this value to be something less that your currently configured setting or set it to 0 and not have an issue.
MORE INFORMATION ON THIS TOPIC
The Best Web Links: tips, tutorials and more.
Search400's targeted search engine: Get relevant information on security.
Ask your systems management questions--or help out your peers by answering them--in our live discussion forums.
Check out this Search400.com Featured Topic: Top ten security tips
Dig Deeper on iSeries system and application security
Related Q&A from Carol Woodbury
Before changing password levels and upgrading operating systems on the AS/400, ensure the clients connecting to the NetServer do not need the old ...continue reading
Look in the audit journal (QAUDJRN) on the AS/400 for an authority failure message with the name of the library as the object name. Use the ...continue reading
The UPPWEI field corresponds to the password expiration interval field, and its values "0" and "-1" represent the *SYSVAL and *NOXMAX commands.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.