After upgrading CA Top Secret to r15, message"$HASP100 TSS ON STCINRDR" is no longer issued during IPL. (It was issued in previous releases of CA Top
Also, message TSS2069I is now issued after the TSS2000I/TSS2001I messages;
TSS2000I CA TOP SECRET MSTR INITIALIZATION IN PROGRESS
TSS2001I CA TOP SECRET MSTR INITIALIZATION COMPLETE
TSS2069I Subsystem TSS is Active
Even though CA Top Secret is not started with SUB=MSTR, it seems now CA Top Secret is running as subsystem automatically at r15. How can CA Top Secret be
setup to not run as a subsystem at r15?
CA Top Secret r15 uses a subsystem at startup time, and the default name of the subsystem is TSS. With MVS, if a started task proc name is the same as the
name of a subsystem, then the started task will run under SUB=MSTR.
So, the easiest way to not run CA Top Secret as a subsystem is to change the name of the proc to something other than TSS, such as TSS150.
It is also possible to change the name of the subsystem to anything of the form TSx or TSxx, but that is somewhat more complicated than just changing the
name of the proc. To do this, 2 members are needed in SYS1.PARMLIB.
Member CAISEC00 will contain the line:
Member CAITSS01 will contain:
where TSxx is the changed subsystem name. As long as there is a START TSS command, either in COMMNDxx or elsewhere in the IPL procedure,
you can ignore the following 'Important!' warning from chapter 6 of the CA Top Secret r15 Installation Guide, section
'CA Top Secret as a Subsystem', subsection 'Specifying Startup Options in CAITSS' about needing a proc with the same name as the subsystem.
Important! The CA TSS procedure has to match the subsystem name and must be in the system procedure library (SYS1.PROCLIB).
This is only needed if you are depending on the subsystem starting TSS (which is optional).