1 INFO-VAX	Fri, 08 Dec 2006	Volume 2006 : Issue 674       Contents:! RE: Alpha sales extended 6 months ! Re: Alpha sales extended 6 months ! Re: Alpha sales extended 6 months ! Re: Alpha sales extended 6 months ! RE: Alpha sales extended 6 months  dcldialogue.com  Re: dcldialogue.com  Re: DEC Educational Stuff ) Re: OT: Outsourcing to offshore locations ) Re: OT: Outsourcing to offshore locations P Shadowing shared disks (was Re: Current Alpha SCSI controllers for shared storagP Re: Shadowing shared disks (was Re: Current Alpha SCSI controllers for shared st Standalone vs a regular backup" Re: Standalone vs a regular backup Re: Who called me?  F ----------------------------------------------------------------------  $ Date: Thu, 7 Dec 2006 15:59:37 -0500' From: "Main, Kerry" <Kerry.Main@hp.com> * Subject: RE: Alpha sales extended 6 monthsT Message-ID: <FA60F2C4B72A584DBFC6091F6A2B868401E834AB@tayexc19.americas.cpqcorp.net>   > -----Original Message-----3 > From: Neil Rieck [mailto:n.rieck@sympatico.ca]=20   > Sent: December 7, 2006 9:30 AM > To: Info-VAX@Mvb.Saic.Com , > Subject: Re: Alpha sales extended 6 months >=20 >=20  
 [snip ...]   > > F > > migrations are a real pain?  we have been thru two of them without > > nothing H > > more than a recompile for dibol ... rms is rms ... on vms migrations > > with; > > with properly written software a re a piece of cake ...  > >  >=20@ > I couldn't agree more but I think you've missed my main point: >=20B > In today's corporate culture people wanting to bring in their=20 > own favourite=20@ > technology will take the opportunity to blow everything out=20 > of proportion.=20 I > These people tend to have the ear of upper management and one of the=20 + > negative phrases they use is "code port".  >=20= > (if we're going to go through all the trouble of a "code=20  > port" then we might=20; > as well take this opportunity to consolidate all those=20  > "legacy" OpenVMS apps=20; > onto one of our currently "supported" platforms - Like=20  > Windows 2003 Server=20
 > Edition)  B So, to go from Alpha to Integrity, simply position it as simply anG OpenVMS upgrade on par with something like an VMS V7 to V8 upgrade i.e. 3 some App's have to be re-compiled and re-tested.=20    :-)     D Re: Windows .. Well, if your App is critical, and you test your AppsH before any patches are rolled out (like all self respecting SysAdmins inB critial environments do), then the answer might be "given the 5-20D monthly security patches per month on Windows (Linux) and the impact> that would have on our App QA/Testing, we can not afford those platforms".    Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  4 OpenVMS - the secure, multi-site OS that just works.   ------------------------------  $ Date: Thu, 7 Dec 2006 16:17:51 -0500) From: "Neil Rieck" <n.rieck@sympatico.ca> * Subject: Re: Alpha sales extended 6 months; Message-ID: <457883ee$0$1645$9a6e19ea@news.newshosting.com>   3 "Main, Kerry" <Kerry.Main@hp.com> wrote in message  N news:FA60F2C4B72A584DBFC6091F6A2B868401E834AB@tayexc19.americas.cpqcorp.net...   [...snip...]  D > So, to go from Alpha to Integrity, simply position it as simply anI > OpenVMS upgrade on par with something like an VMS V7 to V8 upgrade i.e. 2 > some App's have to be re-compiled and re-tested. >  > :-)   E >Re: Windows .. Well, if your App is critical, and you test your Apps I >before any patches are rolled out (like all self respecting SysAdmins in C >critial environments do), then the answer might be "given the 5-20 E >monthly security patches per month on Windows (Linux) and the impact ? >that would have on our App QA/Testing, we can not afford those  >platforms". >  >Regards > Kerry Main  L I can't argue with your logic. I only wish the computer people inside large M corporations were logical but they are not. Sometimes I get the feeling that  M the majority of them get their information from the free industry newspapers    while sitting on the toilet. :-)  
 Neil Rieck Kitchener/Waterloo/Cambridge,  Ontario, Canada.8 http://www3.sympatico.ca/n.rieck/links/cool_openvms.html: http://www3.sympatico.ca/n.rieck/links/openvms_demos.html    ------------------------------  % Date: Thu, 07 Dec 2006 17:31:18 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> * Subject: Re: Alpha sales extended 6 months8 Message-ID: <8747a$45789643$cef8887a$16487@TEKSAVVY.COM>   Neil Rieck wrote: O > I've never considered myself to be the best programmer in the world but I do  K > employ some self discipline and must say that "all my own" programs went  , > from VAX to Alpha with a single recompile.    L You obviously never developped programmes in the original K&R C with VAX-C. J You can't just recompile them with the ANSI-C DEC-C compiler.  (Ok, there K are options to allow the modern compiler to accept the old K&R constructs).   H In terms of downgrading to that iA64 thing, you need to look at any/all L #ifdefs because your program may have some if (alpha) then do this, else do L that , which means that on IA64, the code will be compiled as if it were on  a vax.  J Now, is this worse than windows upgrades where due to the change to .NET, J many things in programs need to be rewritten ? No.  But it is still not a 
 small change.   L Consider this:  when/if IA64 is declared matured in a year or two, VMS will L either be ported to the 8086 or also declared mature.  It isn't worth it to H go through a porting exercise that will last only a few years. Might as L well extend Alpha by a couple of years and migrate once (either to VMS-8086  or to Linux or AIX or Solaris).    ------------------------------  $ Date: Thu, 7 Dec 2006 18:28:42 -0500) From: "Neil Rieck" <n.rieck@sympatico.ca> * Subject: Re: Alpha sales extended 6 months; Message-ID: <4578a299$0$1609$9a6e19ea@news.newshosting.com>   ; "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message  2 news:8747a$45789643$cef8887a$16487@TEKSAVVY.COM... > Neil Rieck wrote:  [...snip...]   > G > You obviously never developped programmes in the original K&R C with  M > VAX-C. You can't just recompile them with the ANSI-C DEC-C compiler.  (Ok,  G > there are options to allow the modern compiler to accept the old K&R   > constructs). >   K Yes I have but VAX-C to DEC-C is not the real problem (although the points  J you mention are correct). The real problem is that "C" has evolved into a " popular replacement for assembler.  K (if my cousin David is reading this, he will remember a conversation a few  J Christmas's back when I said that "C is not a high level language" and he 0 replied "it is after you pull in the includes".)  J > In terms of downgrading to that iA64 thing, you need to look at any/all K > #ifdefs because your program may have some if (alpha) then do this, else  I > do that , which means that on IA64, the code will be compiled as if it   > were on a vax. > M True. One of the problems with VAX-C was that the complier existed while the  L language was still evolving. Some people wrote good code in VAX-C requiring H almost no modifications when moved to DEC-C while many other people cut  every corner possible.   > L > Now, is this worse than windows upgrades where due to the change to .NET, L > many things in programs need to be rewritten ? No.  But it is still not a  > small change.  > I > Consider this:  when/if IA64 is declared matured in a year or two, VMS  M > will either be ported to the 8086 or also declared mature.  It isn't worth  M > it to go through a porting exercise that will last only a few years. Might  H > as well extend Alpha by a couple of years and migrate once (either to * > VMS-8086 or to Linux or AIX or Solaris).  F I never regretted doing the port to Alpha because trying to get stuff M through the new compiler revealed problems caused by a junior programmer who  J should have been supervised more closely. On top of that, porting several I hundred applications was much easier than rewriting everything (which is  : what certain people in other departments were suggesting).  
 Neil Rieck Kitchener/Waterloo/Cambridge,  Ontario, Canada.8 http://www3.sympatico.ca/n.rieck/links/cool_openvms.html9 http://www3.sympatico.ca/n.rieck/links/openvms_demos.html    ------------------------------  $ Date: Thu, 7 Dec 2006 21:57:26 -0500' From: "Main, Kerry" <Kerry.Main@hp.com> * Subject: RE: Alpha sales extended 6 monthsT Message-ID: <FA60F2C4B72A584DBFC6091F6A2B868401E83577@tayexc19.americas.cpqcorp.net>   > -----Original Message-----9 > From: JF Mezei [mailto:jfmezei.spamnot@teksavvy.com]=20   > Sent: December 7, 2006 5:31 PM > To: Info-VAX@Mvb.Saic.Com , > Subject: Re: Alpha sales extended 6 months >=20   .snip .. =B8 B > Consider this:  when/if IA64 is declared matured in a year or=20H > two, VMS will either be ported to the 8086 or also declared mature.  = It=20 I > isn't worth it to go through a porting exercise that will last only a =  few=20F > years. Might as well extend Alpha by a couple of years and migrate = once=20 5 > (either to VMS-8086 or to Linux or AIX or Solaris).  >=20  ; Well, you might just be forgetting a few small items like =  costs-risks-testing-time.   G Yes, this is also required for Alpha to Integrity, but as many Cust`s = J have found out, the relative costs-risk-testing of Alpha to Integrity is =H about a 2 or 3 on a scale of 10. Doing what you suggest has a relative == cost-risk-testing-time effort of about 8 or 9 on scale of 10.   I Course, with Windows or Linux, you also have to add the efforts and $`s = E associated with App  QA-Testing against all of the monthly security =  patches.  B For some Cust`s, risks, costs and security are big considerations.   Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  4 OpenVMS - the secure, multi-site OS that just works.   ------------------------------  $ Date: Thu, 7 Dec 2006 16:04:44 -0500, From: "Kevin G. Barkes" <kgbarkes@gmail.com> Subject: dcldialogue.comI Message-ID: <eddcc1330612071304l41cca794ma2a9f8f8370379fc@mail.gmail.com>    Hi all,   D I recently sold the kgb.com domain name and made some other changes,C specifically locating the archive of my DCL Dialogue columns in DEC  Professional/Digital Age at:   http://www.dcldialogue.com  @ http://www.dcldialog.com will also work, for you phonetic phans.  B Other affected addresses are in my sig... kgb.com changes hands atD 12:01 am this Saturday. I have no idea who's actually buying it; theC transaction was handled by a very nice, extremely competent broker.   : As someone once said, so long and thanks for all the fish.   --   Regards,   KGB    -----  Kevin G. Barkes  Email: kgbarkes@gmail.com  KGB Report:  http://www.kgbreport.com Commentwear by KGB:  http://www.commentwear.com National Temperature Index: # http://nationaltemperatureindex.com  DCL Dialogue on line:  http://www.dcldialogue.com Random Quotations Generator: http://www.goodquotations.com " Over 12,000 searchable quotations.   ------------------------------   Date: 7 Dec 2006 13:27:53 -0800 ) From: "WWWebb" <William.W.Webb@gmail.com>  Subject: Re: dcldialogue.comB Message-ID: <1165526873.407376.289290@73g2000cwn.googlegroups.com>   Kevin G. Barkes wrote:	 > Hi all,  > F > I recently sold the kgb.com domain name and made some other changes,E > specifically locating the archive of my DCL Dialogue columns in DEC  > Professional/Digital Age at: >  > http://www.dcldialogue.com > B > http://www.dcldialog.com will also work, for you phonetic phans. > D > Other affected addresses are in my sig... kgb.com changes hands atF > 12:01 am this Saturday. I have no idea who's actually buying it; theE > transaction was handled by a very nice, extremely competent broker.  > < > As someone once said, so long and thanks for all the fish. >  > --
 > Regards, >  > KGB  >  > -----  > Kevin G. Barkes  > Email: kgbarkes@gmail.com 
 > KGB Report:  > http://www.kgbreport.com > Commentwear by KGB:  > http://www.commentwear.com > National Temperature Index: % > http://nationaltemperatureindex.com  > DCL Dialogue on line:  > http://www.dcldialogue.com > Random Quotations Generator: > http://www.goodquotations.com $ > Over 12,000 searchable quotations.  G Thank you, Kevin.  DCL Dialogue provided me (and many others, I'm sure) / with a good deal of levity in the days of yore.   C I probably learned a few things from it, too, but it's been so long @ that I've probably forgotten and re-learned them in the interim.  D I hope you didn't throw your towel in as part of the deal- you never know when you might need it.   WWWebb,   G who used to have a kgb.com email address in the days when I got my mail  by dialing your BULLETIN BOARD.    ------------------------------   Date: 7 Dec 2006 20:56:11 -0800  From: tomarsin2015@comcast.net" Subject: Re: DEC Educational StuffB Message-ID: <1165553771.594541.229630@16g2000cwy.googlegroups.com>   Hello G Myabe its listd as RPGII. I can recall loading RPGII when I was working 8 at DEC. This was around 1990 or so. This is from the pak Product Name: RPGII  Release Date 13-Mar-1991 Availability F phillip  Ian Miller wrote:  > for information VAX RPG see  > 2 > http://www.migrationspecialties.com/VAX-RPG.html   ------------------------------  % Date: Thu, 07 Dec 2006 19:25:50 -0500 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net> 2 Subject: Re: OT: Outsourcing to offshore locations: Message-ID: <xZGdnXwGooqRLOXYnZ2dnUVZ_rydnZ2d@comcast.com>   JF Mezei wrote: , > I had a most unfortunate experience today. > J > Netgear has a switch JFS523 and one FS524. Figured I would call Netgear J > and ask them what the difference is between the two. In the past, I had 5 > had good experience with Netgear telephone support.  > F > So I call the number on their web site. Press the key for pre-sales D > support. Someone with the accent of the world's largest democracy I > answers. After needing to use aviation speeling to spell out the model  K > numbers, the guys asks me to wait. He comes back and tells me he doesn't  0 > know and that I should call some other number. > M > I call that other number. That number just tells me to call another number. J > I call another number. It is an american who answers the call, but then I > proceeds to tell me that I need a contract or a case number to proceed.  >   D Avoid buying any Netgear products!  These are the geniuses who hard E coded the address of the University of Wisconsin's NTP server into a  I router with a broken implementation of SNTP that queried the server once  A per second.  Then they sold a few million of these things.  U of  ' Wisconsin's network crashed big-time!!!   , http://www.cs.wisc.edu/~plonka/netgear-sntp/4 http://kbserver.netgear.com/kb_web_files/n101176.asp   ------------------------------  % Date: Thu, 07 Dec 2006 20:20:39 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 2 Subject: Re: OT: Outsourcing to offshore locations8 Message-ID: <5d905$4578bdf4$cef8887a$13892@TEKSAVVY.COM>   Richard B. Gilbert wrote: % > Avoid buying any Netgear products!  . > http://www.cs.wisc.edu/~plonka/netgear-sntp/6 > http://kbserver.netgear.com/kb_web_files/n101176.asp     OUCH !  K I've had 2 netgerar products for years (a Netgear branded Zyxel router and  F a netgear hub and had in the past been impressed with their technical 1 support. And I like the colour of their boxes :-)   I But today's experience has been dismal. And your story sure puts Netgear  - down to the low end such as dlink or linksys.     J Ahhh, the days when you could confidently order from Digital even network $ products and knew you'd get quality.   ------------------------------   Date: 7 Dec 2006 15:58:00 -0800 ( From: "Rich Jordan" <jordan@ccs4vms.com>Y Subject: Shadowing shared disks (was Re: Current Alpha SCSI controllers for shared storag B Message-ID: <1165535880.718763.298360@f1g2000cwa.googlegroups.com>   Richard B. Gilbert wrote:  > Rich Jordan wrote: > J > > Are there any controllers more current (read faster) than the KZPBA-CB/ > > that are supported in DS10 systems for VMS?  > > F > I don't think so.  Is "speed" of the controller really a bottleneck?) > Usually, access time tends to dominate!  >  > <snip>  ? Maybe, maybe not.  In this case the KZPBA may actually be quite F acceptable.  It will be faster than the KZPSA controllers in any case.  D Since using a single shared bus (mandatory with DS10-L systems) withD shadowing is unknown territory for me, has anyone done that?  I knowE you can shadow drives that are on a single ended channel (I've played C with host-based shadowing two drives on a single KZPCA-AA channel).   C Does it work on a shared bus also?  Can two clustered systems which G both have access to both of the physical devices making up a shadow set @ 'cooperate' in the creation and management of that set?  Does itD require making each system handle one of the drives and treating theG other (physical) drive as /noavailable, so it only sees the MSCP served  face of the drive?  = Assume a single bus shelf with 2 + 1 disks (the extra being a B non-shadowed quorum disk), shared between two DS10-Ls via KZPBA-CBG controllers via the 3X-DWZCV-BA HVD to LVD adapter.  Both nodes see all E three disks on the shelf.  Can drive 0 and 1 be shadowed in a fashion 5 that allows either/both systems to run the shadowset?   ? Perhaps we mark drive 0 as /noavailable on Alpha 1, and drive 1 F /noavailable on Alpha 2, then run the shadowset across both nodes?  Or> is it smart enough to do the right thing just using the normal4 allocation class naming when creating the shadowset?   Thanks.    Rich   ------------------------------  * Date: Fri, 8 Dec 2006 01:58:54 +0000 (UTC)7 From: moroney@world.std.spaamtrap.com (Michael Moroney) Y Subject: Re: Shadowing shared disks (was Re: Current Alpha SCSI controllers for shared st ( Message-ID: <elagsu$l3o$1@pcls4.std.com>  * "Rich Jordan" <jordan@ccs4vms.com> writes:  M >Does [shadowing] work on a shared bus also?  Can two clustered systems which H >both have access to both of the physical devices making up a shadow setA >'cooperate' in the creation and management of that set?  Does it E >require making each system handle one of the drives and treating the H >other (physical) drive as /noavailable, so it only sees the MSCP served >face of the drive?   E Shadowing on a shared bus works just fine, as long as the drives and  G controllers are ones that understand multiple initiators, that is, more K than one host accessing a given drive.  That's just about all the supported  ones nowadays.  E You have to make sure the controllers are set to different SCSI id's  E (normally they're ID 7, set one to 6), and make damn sure the cluster F configuration is such that the two nodes can _never_ access the drivesG at the same time when not in the same cluster.  (that is, be sure VOTES  and EXPECTED_VOTES are correct)    ------------------------------   Date: 7 Dec 2006 21:04:17 -0800  From: tomarsin2015@comcast.net' Subject: Standalone vs a regular backup A Message-ID: <1165554257.386748.38040@80g2000cwy.googlegroups.com>    Hello E I have a 3100-90 that was running 7.3. The disk went south and I dont E have a standalone backup, but I do have a weekly backup of the system D disk. I would like to restore the system. I am wondering if I reloadF 7.3 and then do a normal restore of the weekly backup would that work. What problems would I face?? thanks phillip  p.s. HAPPY HOLIDAYS TO ALL    ------------------------------  * Date: Thu, 7 Dec 2006 23:09:43 -0600 (CST)* From: sms@antinode.org (Steven M. Schweda)+ Subject: Re: Standalone vs a regular backup 2 Message-ID: <06120723094329_2020028F@antinode.org>   From: tomarsin2015@comcast.net  G > I have a 3100-90 that was running 7.3. The disk went south and I dont G > have a standalone backup, but I do have a weekly backup of the system F > disk. I would like to restore the system. I am wondering if I reloadH > 7.3 and then do a normal restore of the weekly backup would that work.  G    It's hard to say, as "weekly backup" is not a well-defined concept.  F If you have an image backup, why would you want to "reload 7.3"?  JustI resore the image backup using Standalone BACKUP (and hope for the best).  F If you don't have an image backup, you're probably looking at a lot of% work to get things back as they were.    > What problems would I face??      It depends.  H ------------------------------------------------------------------------  3    Steven M. Schweda               sms@antinode-org 4    382 South Warwick Street        (+1) 651-699-9818    Saint Paul  MN  55105-2547    ------------------------------   Date: 7 Dec 2006 16:36:57 -0800 $ From: "roger" <rogerntucker@msn.com> Subject: Re: Who called me? B Message-ID: <1165538217.712628.136480@16g2000cwy.googlegroups.com>  ? OK.  I finally got it working...  Here is an example of calling - TBK$SHOW_TRACEBACK() for everyone to enjoy... F It produces three tracebacks.  The first one callable from anywhere in	 the code. ( the second one from a condition handler.( The last one is from VMS for comparison:  1 %MYTRACE-F-TRACEBACK, symbolic stack dump follows ?   image  module  routine      line      rel PC           abs PC E  T  T  c                      23369 00000000000003B0 00000000000303B0 E  T  T  b                      23370 00000000000003E0 00000000000303E0 E  T  T  a                      23371 0000000000000410 0000000000030410 C  T  T  main                 23386 00000000000004F4 00000000000304F4 F  T  T  __main                      0 0000000000000094 0000000000030094B                                0 FFFFFFFF8026BED4 FFFFFFFF8026BED4) %MYTRACE-I-END, end of MYTRACE stack dump     ; %SYSTEM-E-ACCVIO, access violation, reason mask=01, virtual : address=0000000000000002, PC=0000000000030454, PS=0000001B1 %MYTRACE-F-TRACEBACK, symbolic stack dump follows F   image  module  routine             line      rel PC           abs PC  E  T  T  z                      23380 0000000000000454 0000000000030454 E  T  T  y                      23382 0000000000000484 0000000000030484 E  T  T  x                      23383 00000000000004B4 00000000000304B4 C  T  T  main                 23388 0000000000000528 0000000000030528 G  T  T  __main                       0 0000000000000094 0000000000030094 E                                   0 FFFFFFFF8026BED4 FFFFFFFF8026BED4 ) %MYTRACE-I-END, end of MYTRACE stack dump     ; %SYSTEM-E-ACCVIO, access violation, reason mask=01, virtual : address=0000000000000002, PC=0000000000030454, PS=0000001B/ %TRACE-E-TRACEBACK, symbolic stack dump follows F   image  module  routine             line      rel PC           abs PC  E  T  T  z                      23381 0000000000000454 0000000000030454 E  T  T  y                      23382 0000000000000484 0000000000030484 E  T  T  x                      23383 00000000000004B4 00000000000304B4 C  T  T  main                 23388 0000000000000528 0000000000030528 G  T  T  __main                       0 0000000000000094 0000000000030094 E                                   0 FFFFFFFF8026BED4 FFFFFFFF8026BED4        /*> ** This example program shows how to call TBK$SHOW_TRACEBACK()8 ** One shows the current stack from the point of calling stack_dump_here().F ** The other shows how to output a stack dump from a condition handler% ** This example works on alpha 7.3-2.  **E ** TBK$SHOW_TRACEBACK() handles several cases that are hard to handle > **	yourself.  Like VAX translated frames and exception frames. **@ ** Be sure to compile /NOOPT or most of the stack frames will be **	optimized away. ** **  Written by: Roger Tucker */   #define __NEW_STARLET    #include <starlet.h> #include <stsdef.h>  #include <lib$routines.h>  #include <descrip.h> #include <libicb.h>  #include <ssdef.h>   #include <stdio.h> #include <string.h>   9 static unsigned long find_image_symbol(const char *image,   	const char *name, void **addr);A static void stack_dump(unsigned __int64 fp, unsigned __int64 pc);    static void stack_dump_here()      {       /* Get my callers FP & PC */%     struct _invo_context_blk context; (     lib$get_curr_invo_context(&context);?     unsigned long status = lib$get_prev_invo_context(&context); 9     if (!$VMS_STATUS_SUCCESS(status)) lib$signal(status); 4     unsigned __int64 fp = context.libicb$q_ireg[29];;     unsigned __int64 pc = context.libicb$q_program_counter;      stack_dump(fp,pc);     }    /*3 ** my_handler() - output the message and stack dump  */   #include <chfdef.h> 4 unsigned int my_handler(void *sigarr, void *mecharr)     { .     struct chf$mech_array *mech_arr = mecharr; #ifdef __INITIAL_POINTER_SIZE & #pragma __required_pointer_size __save& #pragma __required_pointer_size __long #endifE     unsigned __int64 *signal_array = mech_arr->chf$ph_mch_sig64_addr; >     unsigned short *arg_cnt = mech_arr->chf$ph_mch_sig64_addr; #ifdef __INITIAL_POINTER_SIZE ) #pragma __required_pointer_size __restore  #endif2     *arg_cnt -= 2;			/* Subtract the PC and PSL */=     unsigned long status = sys$putmsg(signal_array, 0, 0, 0);  					/* output the message */ &     *arg_cnt += 2;			/* Put it back */  ,     /* Skip the condition handling frames */  %     struct _invo_context_blk context; (     lib$get_curr_invo_context(&context);1     status = lib$get_prev_invo_context(&context); 9     if (!$VMS_STATUS_SUCCESS(status)) lib$signal(status); 1     status = lib$get_prev_invo_context(&context); 9     if (!$VMS_STATUS_SUCCESS(status)) lib$signal(status); 1     status = lib$get_prev_invo_context(&context); 9     if (!$VMS_STATUS_SUCCESS(status)) lib$signal(status); 4     unsigned __int64 fp = context.libicb$q_ireg[29];  					/* Get the frame pointer */  ,     stack_dump(fp,signal_array[*arg_cnt-1]); 					/* Produce a stack dump */ <     return SS$_RESIGNAL;		/* give other handlers a chance */     }   & static void c() { stack_dump_here(); } static void b() { c(); } static void a() { b(); }   /*, ** Note 10 is an Accvio with error severity.A **  Accvio needs 4 args, 2 by me, 2 added by lib$signal (PS, PSL)  */   static void z()      { /     lib$signal(10,1,2);			/* Compare the two */      }  static void y() { z(); } static void x() { y(); }
 int main()     {      a();6     VAXC$ESTABLISH(my_handler);		/* Test my handler */     x();     }    /*0 ** stack_dump() - this prints out the stack-dump+ **	If first dynamically activates TRACE.EXE / **	and finds the address of TBK$SHOW_TRACEBACK. 7 **	Note: TBK$SHOW_TRACEBACK says it needs the SP but by 4 **	looking at the 7.1 source listings it's not used. */  @ static void stack_dump(unsigned __int64 fp, unsigned __int64 pc)     {      unsigned long status; 5     static unsigned long (*tbk$show_traceback)() = 0;      if (!tbk$show_traceback) 	{9 	status = find_image_symbol("TRACE","TBK$SHOW_TRACEBACK",   		(void **)&tbk$show_traceback);6 	if (!$VMS_STATUS_SUCCESS(status)) lib$signal(status); 	}     if (tbk$show_traceback)  	{@ 	printf("%%MYTRACE-F-TRACEBACK, symbolic stack dump follows\n");/ 	status = tbk$show_traceback(fp,	/* FAULT FP */ $ 		0,			/* FAULT SP - NOT USED!!!! */ 		pc,			/* PC */ 		0,			/* detail flag */  		0,			/* User action routine */ 		0); 6 	if (!$VMS_STATUS_SUCCESS(status)) lib$signal(status);< 	printf("%%MYTRACE-I-END, end of MYTRACE stack dump\n\n\n"); 	}     }   9 static unsigned long find_image_symbol(const char *image,  	const char *name, void **addr)      { G     struct dsc$descriptor image_dsc = { 0, DSC$K_DTYPE_T, DSC$K_CLASS_S  };+     image_dsc.dsc$w_length = strlen(image); ,     image_dsc.dsc$a_pointer = (char *)image;F     struct dsc$descriptor name_dsc = { 0, DSC$K_DTYPE_T, DSC$K_CLASS_S };)     name_dsc.dsc$w_length = strlen(name); *     name_dsc.dsc$a_pointer = (char *)name;F     return lib$find_image_symbol(&image_dsc, &name_dsc, (void *)addr);     }    Enjoy, Roger    ------------------------------   End of INFO-VAX 2006.674 ************************