After upgrading Top Secret from 15.0 to 16.0, the following message is received at startup:
*TSS9103E VSMPATH DD NOT SPECIFIED
The description for TSS9103E says:
VSAMFILE DD NOT SPECIFIED
Reason: The VSAM file feature was specified on the security file but no VSAMFILE DD statement was found in the startup JCL for CA Top Secret.
Action: Specify a VSAMFILE DD statement that references the VSAM dataset associated with the SECFILE DD security file dataset.
Isn't this message issued because a VSAMPATH file was not specified in the Top Secret startup proc, which is not supposed to be specified because the security and audit files are not shared among LPARs?
Check what is set for the SHRFILE Control Option.
In a SHRFILE(YES) environment without the VSMPATH or VSAMAIX files, without these files allocated, when a certificate change occurs on a sharing LPAR, Top Secret will need to read the entire list of VSAM file CERTIFICATE entries in order to process the update.
One or more of the following messages is now issued depending upon which file is missing from the Top Secret startup proc.
TSS9103E VSMPATH DD NOT SPECIFIED
TSS9103E VSAMAIX DD NOT SPECIFIED
If the security and audit files are not shared across systems, SHRFILE(NO) should be set on all systems that are not sharing. (With SHRFILE(NO), the LOCK records on the Security and Audit Files are obtained at startup and never released, totally eliminating all I/O required for lock record processing in a single CPU environment.) With multiple systems not sharing, changing SHRFILE(YES) to SHRFILE(NO) can be done 1 system at a time. It does not have to be done on all non sharing systems at the same time.