Test ability for PAGENT updates prior to installing them

This item is unlikely to be given high enough priority to be placed into product plan.

Thanks very much for the additional info - very helpful. One more question - did you open a case for the situation that caused NCA to generate a policy file that pagent rejected? If so, please pass it along. If not, we would be interested in the X500 name you used that led to the error..

I am looking for a test ability to confirm that a updated pagent config will be successfully parsed without error prior to the pagent file being used. For example is a FQDN is coded with a X.500 name, z/OS configuration assistant allows that kind of setup and generates a file that is coded as such, however if such a file is loaded into pagent ( it generates a error) NOW if such a file was installed while a LPAR is down (via a filesystem update) then on system IPL PAGENT totally ignores said file and then depending on the level of inter system encryption setup it becomes much more difficult to correct that mistake


Thus a function to test if the file will be loaded successfully by pagent as if you were doing so for real would be a great way to give confidence a pagent update can be done during a ipl of system

Thanks for submitting this requirement. Can you expand a bit on what you mean by "logic errors?" Are you just looking for a pagent function to prove that the policy file can be successfully parsed and installed into the TCP/IP stack, or are you also looking for something to test the behavior of the policy rules themselves? Also, which policy types are most important to you regarding this capability?