backerman | JES2's funny ideas about "stop" (Reply)

$BACKUP_SOFTWARE has been giving me far too much grief at work. You'd think I'd read a book at home or something. Maybe even unpack. Instead, I'm installing MVS.

0000 05.41.35           $P
0000 05.41.35           $HASP000 SYSTEM DRAINING
0000 05.41.55           $PJES2
0000 05.41.55           $HASP000 JES2 NOT DORMANT -- SYSTEM NOW DRAINING
0000 05.42.28           $DU
0000 05.42.28           $HASP000 READER1   00C INACTIVE
0000 05.42.28           $HASP000 PRINTER1  00E INACTIVE
0000 05.42.28           $HASP000 PRINTER2  00F HALTED
0000 05.42.28           $HASP000 PRINTER3  30E DRAINED
0000 05.42.28           $HASP000 PUNCH1    00D INACTIVE
0000 05.42.28           $HASP000 LINE1     *** DRAINED  (RMT1)

You don't say... do you not understand the meaning of the $P command? I gorram want my printers drained. Be good or I'll replace you with JES3.

0000 05.42.37           $P RDR1
0300 05.42.37           $HASP097 READER1  IS DRAINED
0000 05.42.37           $HASP000 OK
0000 05.42.41           $P PRT1
0300 05.42.41           $HASP097 PRINTER1 IS DRAINED
0000 05.42.41           $HASP000 OK
0000 05.42.44           $P PRT2
0000 05.42.44           $HASP000 OK

Okay, here's the problem. Stopping any device should drain it and reply with $HASP097. Yet JES2 stares at me with a glazed look in its eyes that says "hold my head to your ear, you will hear the sea."

0000 05.42.58           $DU
0000 05.42.58           $HASP000 READER1   00C DRAINED
0000 05.42.58           $HASP000 PRINTER1  00E DRAINED
0000 05.42.58           $HASP000 PRINTER2  00F DRAINING
0000 05.42.58           $HASP000 PRINTER3  30E DRAINED
0000 05.42.58           $HASP000 PUNCH1    00D INACTIVE
0000 05.42.58           $HASP000 LINE1     *** DRAINED  (RMT1)

Nope. After some flailing around and consulting the manuals, I decided to try reverse psychology:

0000 05.49.09           $S PRT2
0200 05.49.09           $HASP160 PRINTER2 INACTIVE - CLASS=Z
FF40 05.49.09           $HASP099 ALL AVAILABLE FUNCTIONS COMPLETE
0000 05.49.09           $HASP000 OK

Yeah. In this parallel world, starting a printer drains it.

0000 05.49.17           $DU
0000 05.49.17           $HASP000 READER1   00C DRAINED
0000 05.49.17           $HASP000 PRINTER1  00E DRAINED
0000 05.49.17           $HASP000 PRINTER2  00F INACTIVE
0000 05.49.17           $HASP000 PRINTER3  30E DRAINED
0000 05.49.17           $HASP000 PUNCH1    00D DRAINED
0000 05.49.17           $HASP000 LINE1     *** DRAINED  (RMT1)
0000 05.49.40           $PJES2
4000 05.49.40 STC    2  $HASP395 INIT     ENDED
4000 05.49.40 STC    3  $HASP395 INIT     ENDED
4000 05.49.40 STC    7  $HASP395 INIT     ENDED
4000 05.49.40 STC    4  $HASP395 INIT     ENDED
4000 05.49.40 STC    5  $HASP395 INIT     ENDED
4000 05.49.40 STC    6  $HASP395 INIT     ENDED
4000 05.49.40           IEE043I A SYSTEM LOG DATA SET HAS BEEN QUEUED TO SYSOUT CLASS A
4000 05.49.40           IEE037I LOG NOT ACTIVE
4000 05.49.40 STC    2  IEF404I INIT - ENDED - TIME=05.49.40
4000 05.49.40 STC    3  IEF404I INIT - ENDED - TIME=05.49.40
4000 05.49.40 STC    7  IEF404I INIT - ENDED - TIME=05.49.40
4000 05.49.40 STC    4  IEF404I INIT - ENDED - TIME=05.49.40
4000 05.49.40 STC    5  IEF404I INIT - ENDED - TIME=05.49.40
4000 05.49.40 STC    6  IEF404I INIT - ENDED - TIME=05.49.40
FFFF 05.50.45           $HASP085 JES2 TERMINATION COMPLETE

And that's all she wrote. I'm hoping fixing this is in the sysgen checklist somewhere, or it's a weird emulator artifact thingy.