PI67614: WHEN NEW SECURITY RULES ARE LOADED BY ASE, THE ENGINE DIDN'T USETHE NEW RULES

APAR status

• Closed as fixed if next.

Error description

• Expected behavior:
  New security rules loaded by ASE should be used by
  the engine
  
  Observed behavior:
              When new rules are loaded by ASE, the sdk loaded by
  the agenthost process does load the new rules, however it spawns
  another engine process which loads the rules on it's own and
  looks in the default location, not the location that the sdk was
  told
  
  Workarounds (if applicable):
               copy the security rules dll back to the default
  folder, or run the sdk as one process
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * user who perform a security rules update                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * the new security rules dll location passed to the sdk was    *
  * not forwarded to the appscanengineagent, fixed by the enging *
  * team                                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * upgrade to 9.0.3.4                                           *
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R903 PSY

     UP