Skip to Content
0
May 12, 2020 at 09:09 AM

Profile parameter where DEFAULT value takes precedence over INSTANCE value

1190 Views Last edit May 13, 2020 at 09:05 AM 2 rev

Hi

We have a situation where we have a RSPARAM in RZ11 that shows value x for a specific app server. And x is active and it works.

But when we look in table TPFET there is a DEFAULT PFNAME with value x and version 50. But there is also an entry in there for the specific app server with version 100 and value y. I would expect that the value of y of the INSTANCE parameter will take precedence over the x of DEFAULT, but it seems to not be happening.

I can also mention that the DEFAULT entry in TPFET has a PSTATE of 'M' where the Instance values all have a blank PSTATE. Not sure if that makes a difference?

Why would the DEFAULT value take precedence over the Instance value?