Recently implemented a SMF INMEM resource dynamically by using SET SMF=.
After IPL received IFA707I SMF CANNOT CONNECT TO LOGSTREAM IFASMF.PSY1.INMEM
REASON=SAF RESOURCE WAS NOT DEFINED. This resulted in lost SMF data as IFA707I causes the SMF LOGSTREAM settings to be rejected.
Review of the syslog appears to show the SMF address space initializing and generating the IFA707I prior to Top Secret address space initialization.
Subsequently doing a SET SMF= defines the SMF logstream environment correctly with no IFA707I, and the INMEM resource is available
Release : 16.0
Component : Top Secret for z/OS
Broadcom and IBM suggests to use INMEM in different SMF PARMLIB, and activate this SMFPARMxx once Top Secret is initialized.
Can use an automated operator to look for Top Secret initialization and then activate the different SMF. Top Secret requires SMF to be up before any requests are processed so that proper auditing can be done.