Bob:
Jim's right. See below
P INIT,A=22
IEF404I INIT - ENDED - TIME=17.26.07
$HASP395 INIT ENDED
S INIT.INIT,,,JES2,SUB=JES2
$HASP250 INIT PURGED -- (JOB KEY WAS C13EA1E6)
IEA989I SLIP TRAP ID=X33E MATCHED. JOBNAME=*UNAVAIL, ASID=0022.
$HASP100 INIT ON STCINRDR
IEF196I IGD100I VIO ALLOCATED TO DDNAME SYS00003 DATACLAS ( )
IEF695I START INIT WITH JOBNAME INIT IS ASSIGNED TO USER START2
, GROUP SYS1
$HASP373 INIT STARTED
IEF403I INIT - STARTED - TIME=17.26.10
$HASP309 INIT 1 INACTIVE ******** C=AH
Adam
----- Original Message -----
From: "Bob Stark" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <IBM-MAIN@BAMA.UA.EDU>
Sent: Friday, November 02, 2007 9:43 AM
Subject: Re: How to force initiator failure
Mark,
My reason for testing is that my automation code is trapping some messages
which allegedly are issued during an initiator failure, determining the
failing
initiator number from stored data, and restarting the failed initiator
once it
leaves the planet.
I want to do it a different way, so as to not have to store and maintain
all of
that data, but I still need to determine the ASID to INIT # mapping.
Without
an actual test, I'm sure that I'll get it wrong.
I like Sam's "spectacular suicide program" with the CALLRTM. Looks fun!
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
