TSS9103E during IPL of Top Secret

Products

• Top Secret
• Top Secret - LDAP

Issue/Introduction

We are having TSS R16. During the start up we receive message *TSS9103E VSMPATH DD NOT SPECIFIED'.
The following is the JCL used for starting TSS:

//TSS PROC HL='TSS',
// PARM1='TSSPARM',
// PRINT=X
//TSS EXEC PGM=TSSMNGR4,DPRTY=(15,14),TIME=1440,REGION=8000K
//SECFILE DD DSN=&HL..SECFILE,DISP=SHR
//VSAMFILE DD DISP=SHR,DSN=TSS.SECFILE.VSAM
//BACKUP DD DSN=&HL..BACKUP,DISP=SHR
//VSAMBKUP DD DISP=SHR,DSN=TSS.BACKUP.VSAM
//RECFILE DD DSN=&HL..RECFILE,DISP=SHR
//AUDIT DD DSN=&HL..AUDIT,DISP=SHR
//AUDIT2 DD DSN=&HL..AUDIT2,DISP=SHR
//CPFFILE DD DSN=&HL..CPFRCVY&SYSID,DISP=SHR
//RECVCMDS DD SYSOUT=*
//PARMFILE DD DSN=&PARM1(TSS&SYSID),DISP=SHR,FREE=CLOSE
//AUTOCMDS DD DUMMY,FREE=CLOSE
//SYSUDUMP DD SYSOUT=&PRINT

Can you please explain why we are getting the TSS9103E during the startup, although we have DD VSAMFILE and VSAMBKUP in the start up procedure. 

Environment

Release:
Component: TSSMVS

Resolution

The answer depends on whether or not you share your secfile among systems.

You can check issuing a TSS MODI STATUS(BASE), look for TSS control option SHRFILE(NO).

If you have SHRFILE(NO), be sure the secfile is not shared.
If SHRFILE(YES), allocate the VSAM PATH file and update your TSS procedure accordingly.
If SHRFILE(YES) but you the secfile is NOT shared then correct your TSSPARM0 member specifying SHRFILE(NO) which will improve performance and avoid this message.