Hi all, Last night we had a weird situation that prompted the operations people to contact one of our standby teams.
A DB2 job started running and requested a PRIVAT tape: 05.34.24 J1234567 IEF403I DB2PRJ1O - STARTED - TIME=05.34.24 05.34.30 J1234567 IEF233D M 7070,PRIVAT,SL,DB2PRJ1O,PRDB2PRC, 934 934 DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01, 934 OR RESPOND TO IEF455D MESSAGE The "TAPE ON" message for this PRIVAT tape was not issued until more than four hours later: 09.44.53 J1234567 IEC705I TAPE ON 7070,CTX817,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2 and another forty minutes went by until that tape was unmounted and a new one was requested: 10.32.11 J1234567 IEC502E K 7070,CTX817,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01 10.32.11 J1234567 IEC501A M 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01 However, this time, the "TAPE ON" message was immediate, as expected under normal conditions: 10.32.13 J1234567 IEC705I TAPE ON 7070,CTX929,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2 This run was the one that was executed without glitches as the first time around the operations people contacted a standby team, the job was cancelled and then resubmitted again (a few times). I am not sure about what DB2 was doing but SORT was being used. So, my question here is, why the first "TAPE ON" message was not issued right after the MOUNT message? Any help will be greatly appreciated Thank you jack ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
