Here is what I might do I might go ahead and in SDSF or with a JES2 command, route the job back to local on HOLD. Then route it to your node, then release the job.
Hold Jobs Route to Local Route to JES2DMVS Release Jobs That might clear up things if there is any discrepancies in JES2. Lizette > > Lizette, > Here follows the display job with the log parameter : > -$DOJ(62977),LONG > JOB62977 $HASP686 OUTPUT(RD05898) > $HASP686 OUTPUT(RD05898) > OUTGRP=2.1.1,BURST=NO,FCB=****, > $HASP686 > FLASH=****,FORMS=ODE1,HOLD=(NONE), > $HASP686 OFFS=(),OUTDISP=WRITE,PRIORITY=9, > $HASP686 PRMODE=LINE,QUEUE=W, > $HASP686 RECORDS=(26 OF > 26),ROUTECDE=JES2DMVS, > $HASP686 SECLABEL=,TSOAVAIL=NO,UCS=****, > $HASP686 > USERID=A2P01GX,WRITER=,REBUILD=NO, > $HASP686 CRTIME=(2010.004,08:11:04) > > -$D DESTID 'JES2DMVS' > $HASP822 DESTID(JES2DMVS) > DEST=N2,STATUS=NODENAME,PRIMARY=NO . > > Paul, > You are right, in fact the destid and the nodename was added > dynamically, > before the IPL. > ---------------------------------------------------------------------- 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
