Buildexternal phenomenon(a)

Fri Sep 11 12:29:21 CDT 2009

Lorry:

My admittedly (and evident continuing) confusion is that the .PHEXE works like a charm when I equate the qkdriver to it, yet when I equate qkdriver to the new qdriver.exe I create with the buildexternal /share, it ignores the do eternal, or it calls the subroutine and nothing happens. 

Thanks! 

I think we are close to a solution if only one more person would read their email!

It has to be a simple thing, this ain't brain surgery (if I can do it!)...

John M Penney
1532 Fern Street SW
Olympia, WA  98502

(360)789-8159

--- On Fri, 9/11/09, Lorry Litman <LLitman at manitoba-ehealth.ca> wrote:

From: Lorry Litman <LLitman at manitoba-ehealth.ca>
Subject: RE: Buildexternal phenomenon(a)
To: "Penney, John" <resolutebay at yahoo.com>
Date: Friday, September 11, 2009, 12:09 PM

For some reason I thought that if you did the build/noshare  and thus create the .phexe you just need to point the logical qkdriver to that image, however, if you do the build/share you create the .exe and the problem would be that when you fire up quick it is using the .exe in memory which is why you would need to do the install/replace. I’ve never tried what Erik had suggested, but, it may allow you to test without affecting all users accessing that image, which would happen if you did the install/replace. Hope some other vms types provide you more help.

Thanx
        Lorry

From: Penney, John [mailto:resolutebay at yahoo.com] 
Sent: Friday, September 11, 2009 11:55 AM
To: Lorry Litman
Subject: RE: Buildexternal phenomenon(a)

Thanks, Lorry:

Don't think it has anything to do with the Image, but who knows?

Cheers!

JP

John M Penney

1532 Fern Street SW

Olympia, WA   98502

(360)789-8159

--- On Fri, 9/11/09, Lorry Litman <LLitman at manitoba-ehealth.ca> wrote:

From: Lorry Litman <LLitman at manitoba-ehealth.ca>
Subject: RE: Buildexternal phenomenon(a)
To: "Penney, John" <resolutebay at yahoo.com>
Cc: "power-l" <powerh-l at lists.sowder.com>
Date: Friday, September 11, 2009, 10:58 AM

Hi John, after you did the build did you replace the image? Checkout the vms Install command and then you may just need to do replace/header/share qkdriver. Haven’t done this in a while so not 100% sure. Thanx Lorry

From: powerh-l-bounces+llitman=manitoba-ehealth.ca at lists.sowder.com [mailto:powerh-l-bounces+llitman=manitoba-ehealth.ca at lists.sowder.com] On Behalf Of Penney, John
Sent: Friday, September 11, 2009 10:17 AM
To: power-l
Subject: Fw: Buildexternal phenomenon(a)

Dear Listers:

Does anybody have experience with or can anyone out there give me some idea as to what kind of parameters / combination of same I need to do a buildexternal correctly in OpenVMS? To construct a SHAREAble subroutine from Quick?

I have successfully created, compiled, BUILDEXTERNAL /NOSHARE and executed a Quick screen calling a C subroutine. Whopee! Haven't done that in a dog's age. C is 10 years ago....

However, (HOWEVER), when I attempt to build a /SHARE-able copy of the 
subroutine (for performance - no spawn) using buildexternal and its myriad 
of combinations, permutations and etrc. parameters per the Qdesign manual, 
it patently doesn't work. 

The PHEXE works like the proverbial charm, but the .EXE does not. Quick just skips over the "do external" statement (put debug into the C routine - and it's not called)...I have 
tried 25 different ways from Sunday but the resulting .EXE just seems to 
be ignored by the Quick program and merrily (demonstrably) does the square 
root of zero in the "do external" construct.

Anybody have ideas?

Thanks!

John M Penney

1532 Fern Street SW

Olympia, WA   98502

(360)789-8159

-----Inline Attachment Follows-----

This email and/or any documents in this transmission is intended for the
addressee(s) only and may contain legally privileged or confidential information.  Any unauthorized use, disclosure, distribution, copying or dissemination is strictly prohibited.  If you receive this transmission in error, please notify the sender immediately and return the original.

Ce courriel et tout document dans cette transmission est destiné à la personne ou aux personnes à qui il est adressé. Il peut contenir des informations privilégiées ou confidentielles. Toute utilisation, divulgation, distribution, copie, ou diffusion non autorisée est strictement défendue. Si vous n'êtes pas le destinataire de ce message, veuillez en informer l'expéditeur immédiatement et lui remettre l'original.

-----Inline Attachment Follows-----

-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l at lists.sowder.com
Subscribe: 'subscribe' in message body to powerh-l-request at lists.sowder.com
Unsubscribe: 'unsubscribe &lt;password&gt;' in message body to powerh-l-request at lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
Add 'site:lists.sowder.com powerh-l' to your search terms to search the list archive at Google.
 This email and/or any documents in this transmission is intended for the
addressee(s) only and may contain legally privileged or confidential information.  Any unauthorized use, disclosure, distribution, copying or dissemination is strictly prohibited.  If you receive this transmission in error, please notify the sender immediately and return the original.

Ce courriel et tout document dans cette transmission est destiné à la personne ou aux personnes à qui il est adressé. Il peut contenir des informations privilégiées ou confidentielles. Toute utilisation, divulgation, distribution, copie, ou diffusion non autorisée est strictement défendue. Si vous n'êtes pas le destinataire de ce message, veuillez en informer l'expéditeur immédiatement et lui remettre l'original.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20090911/7ed7a128/attachment.htm 