We recently upgraded from z/OS 1.4 to z/OS 1.7 and are now seeing
"phantom" active jobs that look like the following in response to a
JES2 $ DA command:
MAB 00000290 $ DA
JOB00000 00000090 $HASP890 JOB(**TEMP**) 109
109 00000090 $HASP890 JOB(**TEMP**) STATUS=(ON L99.JR1/MVS5),CLASS=A,
109
00000090 $HASP890 PRIORITY=15,SYSAFF=(ANY),HOLD=(NONE)
JOB00000 00000090 $HASP890 JOB(**TEMP**) 110
110 00000090 $HASP890 JOB(**TEMP**) STATUS=(ON L99.JR4/MVS5),CLASS=A,
110
00000090 $HASP890 PRIORITY=15,SYSAFF=(ANY),HOLD=(NONE)
(I sent the previous lines in a fixed width font and hope they get to
the list that way. If not, my apologies.)
L99 is the NJE line that connects to our z/VM 5.3 system.
Once these phantom jobs show up they don't go away. (Though a JES2
cold start does the trick.)
Does anyone know what these may be and what we need to do to stop
them from happening?
Thanks,
Mark Bodenstein ([EMAIL PROTECTED])
Cornell University
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
