Can’t Start OMVS/JES Because Of Top Secret TSS7250E PROGRAM Violation

Products

• Top Secret
• Top Secret - LDAP

Issue/Introduction

Receiving:

TSS7250E 136 J=OMVS A=aaaaaaaa TYPE=PROGRAM RESOURCE=pgmname
TSS7250E 136 J=JES2 A=aaaa TYPE=PROGRAM RESOURCE=pgmname

for the OMVS/JES started task. 

Since OMVS/JES won't start, no one can signon to TSO to PERMIT the ACID to the program.

The MSCA previous password is lost so it is not possible to issue TSS commands from the console.

Environment

Release:
Component: TSSMVS

Resolution

There are 2 options:

1) Add MODE=WARN to the start command for Top Secret during IPL. For example:

S TSS,,,(MODE=WARN)

NOTE: There are 3 commas between TSS and the ‘(‘. All 3 are required.

2) Set MODE(WARN) in the Top Secret Parameter File and IPL.

This will allow the OMVS/JES started task to come up even though it will receiving security violations. Sign on to TSO session and permit thhe OMVS/JES started task ACID to PROGRAM. 

Once this is done:
- If you started Top Secret with MODE=WARN, you can issue TSS MODIFY MODE(FAIL). This will put all facilities in FAIL mode. A restart of Top Secret is not required. Be sure to remove the ‘,,,MODE(FAIL)’ from the start command for Top Secret during IPL. 

- If you updated the parameter file, you can also issue TSS MODIFY MODE(FAIL). Be sure to remove MODE(WARN) from the TSS parameter file so the next time TSS is started, it won't be in WARN mode.