I just upgraded TSS on one of our systems from 15.0 to 16.0. and received the following message:
*TSS9103E VSMPATH DD NOT SPECIFIED
The description I see for TSS9103E is:
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.
However, I think this message is being generated because I didn't specify a VSAMPATH, which I'm not supposed to specify because I'm not sharing this database among LPARs.
Check what is set for the SHRFILE Control Option.
SHRFILE(YES) environment without the VSMPATH or VSAMAIX files.
Without these files allocated, when a certificate change occurs on a sharing LPAR, TSS 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 will now be issued depending upon which file is missing:
TSS9103E VSMPATH DD NOT SPECIFIED
TSS9103E VSAMAIX DD NOT SPECIFIED
Check what is specified for the SHRFILE Control Option.
IF SHRFILE(YES) is in effect and you are not sharing the secfile then you will receive one the messages