This Q&A forum allows users to post and respond to "How Do I Do ....." questions. Please do not use to report (suspected) errors - you must use your regional help desk for this. The information contained in this forum has not been validated by LANSA and, as such, LANSA cannot guarantee the accuracy of the information.
When using a Slave install to the iSeries, does being a QSECOFR automatically make you the Partition Security Officer (PSO)?
Working with support on an issue and changed my iSeries group to be QSECOFR. Just did a System Init in Visual LANSA to get some task updates and all of a sudden I am getting the PSO warning when using my credentials.
I don't want to change my profile back (have to get the boss involved) as the support ticket has not yet been closed and we may still need that level.
Will this have a negative impact on other components in other tasks? I know working as the PSO (DCXPMGLIB) causes all kinds of permission issues later on. I experienced them first hand.
Regardless, is it normal to get the PSO warning when you are in the QSECOFR group?
Yes that's how it works for us too. I don't have security issues later when QSECOFR group checks things in though. Normally we are part of the QPGMR group.
