TSS9103E during IPL

Document ID : KB000115773
Last Modified Date : 25/09/2018
Show Technical Document Details
Question:
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. 
Answer:

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

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

If you don't have SHRFILE(NO), you must be sure your are sharing your secfile.
If yes, you have to allocate the VSAM PATH file and update you TSS procedure accordingly.
If not, you must correct your TSSPARM0 member specifying SHRFILE(NO), it will improve performance and avoid this message.