> I found a thread from 2012 discussing BLSR and whether or not it > supports dynamic changes via the SETSSI command. That thread > indicated that BLSR had been updated to support SETSSI, and that > upon a SETSSI ACT, the subsystem would be added and activated. That > part appears to work, but now I can't deactivate it! How's this for bizarre? > > SETSSI ADD,S=BLSR,I=CSRBISUB > CSR002I BATCH LSR SUBSYSTEM BLSR INITIALIZATION COMPLETE. > IEFJ022I SETSSI ADD COMMAND FOR SUBSYSTEM BLSR COMPLETED > SUCCESSFULLY > > > SETSSI DEACT,S=BLSR > IEFJ023I SETSSI DEACTIVATE COMMAND FOR SUBSYSTEM BLSR COMPLETED WITH > ERRORS > IEFJ036I SUBSYSTEM BLSR IS NOT ENABLED FOR THE SETSSI COMMAND > > > D SSI,SUB=BLSR > IEFJ100I 10.56.35 SSI DISPLAY 588 > SUBSYS=BLSR > DYNAMIC=YES STATUS=ACTIVE COMMANDS=REJECT > > > I'm hoping this won't cause any conflicts with the VSAMTune product > e are running here. It shouldn't since it requires JCL changes to > actually use it.
BLSR was implemented as a PTF on top of MVS/ESA SP3.1.3 in 1989. That was years before SETSSI was implemented on SP5.2.0. SETSSI ADD works for BLSR because BLSR didn't need to do anything to make it work. BLSR knows nothing about SETSSI. SETSSI DEACTIVATE requires the subsystem to provide support, and we have no intention of doing any BLSR enhancements. As you hoped, there is no need or reason to deactivate BLSR. It is invoked only when requested via SUBSYS=(BLSR,etc.) in JCL or SVC 99. It does not use SSI functions to monitor messages, commands, task terminations, memory terminations, or any other SSI stuff. Jim Mulder Former BLSR Developer IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
