I think the main issue at least with z/XDC Is that Dave operates whitin z/OS
RTM so he has to abide by z/OS rules In each environment thus making his Job complicated Sent from my iPhone On Apr 9, 2013, at 11:46 AM, DASDBILL2 <[email protected]> wrote: > You're right. #DIE is what I was describing. I confuse and conflate things > myself. > > > > I think there is a HOOK macro in z/OS that assembles into a Monitor Call > instruction for a User event to be traced by GTF, but I could be conflating > some more . > > Bill Fairchild > Franklin, TN > > > ----- Original Message ----- > From: "Frank" <[email protected]> > To: [email protected] > Sent: Tuesday, April 9, 2013 10:43:27 AM > Subject: Re: New Software Tool for z/OS Developers Announced by Arney > Computer Systems > > Bill, > > You are thinking of the #DIE macro. That assembles into a x'00' instruction > with a special identifier for zXDC. If zXDC is established as the newest > ESTAE, the #DIE would cause a debugging session to start. Otherwise a S0C1 > is generated. > > A HOOK, either a dynamic HOOK or the #XDCHOOK macro, is indeed a SVC call. > This can be problematic in certain environments such as SRBs, FRR protected > environments, etc. For this reason, we distribute a "HOOK script" that can > be used to establish XDC into environments where a SVC is not allowed. The > script can be found in the *.XDCCMDS library. > > Hope this helps, > Frank > > > > On Tue, 9 Apr 2013 14:55:43 +0000, DASDBILL2 <[email protected]> wrote: ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
