Profile parameter where DEFAULT value takes precedence over INSTANCE value

[Former Member]

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?

[former_member644293]

Dear Rick Bates,

Instance profile is the one which will be read last and will override the settings of the default profile. as the names says value set in instance profile will affect only the particular instance while default for all.

Example - default client while users login to the system. assume for 3 app servers, if default has 100 while first instance has 200 as the value updated. Then first app server will have 200 and rest two app servers will have 100 as default client.

PSTATE - stands for profile parameter status Modified standard value.

So in your case it might be that admin would have modified the profile file in OS level which is not reflecting in RZ10 or value might be deleted in instance profile at OS level. so default profile takes precedence.

Please check the value in both instance, default profile and then you will be able to identify the issue.

Regards,

[dasistdochscheisse]

Check the parameter in RZ11 on both application servers. There you can see, where the actual value comes from. If the parameter is dynamically changeable, you can change it there too and will not see the value in any profile.