LO56145: STUSERINFO PROCESS CAUSES DAOS TO PANIC IN IT'S TERMINATION CODE.

APAR status

• Closed as program error.

Error description

• STUserInfo process causes DAOS to Panic in it's termination
  code.
  
  The STUserInfo process connects to Domino and then fully
  disconnects which
  causes all the shared memory to be detached.
  The DAOS initialization sets up and then uses a global pointer
  to the static
  memory. The termination code also uses this local pointer to the
  static area.
  This works the first time this occurs and the coder assumed that
  the process
  would exit. However STUserInfo does not exit and call OSInit
  again. The DAOS
  code finds it's local variable, it's not null, so it assumes
  that the shared
  memory was attached to and exits. When OSTerm is call the local
  variable is
  still there and doesn't point to the right stuff. For the NSD I
  looked at, it
  had a storage pointer to the refcnt which was decremented to
  zero. The causes
  it to think this was the last reference to the DAOS control
  block and it tried
  to clean up. It fails accessing the other values that are not
  valid.
  

Local fix

• Don't start DAOS or STUserInfo.
  

Problem summary

• A programming error was found and will be corrected in a future
   release.
  

Problem conclusion

• A programming error was found and will be corrected in a future
   release.
  

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

• Fixed component name

  DOMINO SERVER

• Fixed component ID

  5724E6200

Applicable component levels

• R852 PSN

     UP