Running QTP from Axiant on HP

[Peter Bateman]

Hi J.M:

I assume you are running MPE/iX and not HP-UX as you server OS.

The key to successfully running QTP from PHSVRN ( thin client server ) is to 
control QTP's standard input and output files so
that any that are required are accessing a permanent disc file
instead of the terminal. Any that are not required should be equated
with $NULL. i.e. FILE STDIN=myparm,old;acc=in
                 FILE QTPLIST=listqtp,old;acc=append
                 FILE QTPIN=$NULL
                 etc
Your permanent file names must be unique.
So if two people are concurrently using AXIANT and they both
want run QTP you could have a naming conflict.
It is possible to use the PHDVRN process id to tag filenames.
The SHOWPROC command yield the current PHSVRN process id.

I would also use the run time parameter NOBREAKSET.
This tells QTP not to disable and enable break around a lock.
You are not likely to be breaking a process that is running as a son
of PHSVRN!
                QTP INFO="NOBREAKSET AUTO=MYPROG"

Regards,
Peter Bateman

>From: "Bruin, J.M. de" <Bruin@WT.TNO.NL>
>To: "'Powerhouse listserver'" <powerh-l@lists.sowder.com>
>Subject: Running QTP from Axiant on HP
>Date: Fri, 20 Feb 2004 16:41:32 +0100
>
>Hi there,
>
>first of all I must emphasize that I am really glad this list is up and 
>running
>again. Thx to David for all the effort he has put into it.
>Now hope that you folks re-discover this wonderfull expert exchange.
>
>My question has to do ith running QTP from within Axiant on a HP in a thin
>client environment, thus.
>Last week I was stationed with a client in Switserland in order to help 
>them
>migrate to Axiant (and later on away from the HP to NT) and off-course the
>'problem' of running QTP was there as well.
>I have followed the guidelines and tips from Cognos (the Knowlegde base 
>t.i.)
>but no luck.
>
>We have tried everything and as I am not a HP wizard (I'm more into VMS) we 
>had
>to quit the effort for the time being.
>
>We made a scipt on the HP that run well interactively but as sooon as we 
>tried
>running it from within Axiant (using run command) it failed to even start 
>QTP. I
>do not recall the exact message but it had something to do with an 
>Exception
>error.
>We logged some environment settings from with the script and that worked 
>well,
>although a 'listeq' did not produce any output (in a log file) at all.
>
>Anyone out there recall the same problems?
>
>Any help, hint and / or tip would be appreciated.
>
>Regards,
>
>Mark
>
>
>= = = = = = = = = = = = = = = = = = = = = = = = = = = =
>Mailing list: powerh-l@lists.sowder.com
>Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
>Unsubscribe: "unsubscribe <password>" in message body to 
>powerh-l-request@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.

_________________________________________________________________
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.  
http://join.msn.com/?page=features/virus&pgmarket=en-ca&RU=http%3a%2f%2fjoin.msn.com%2f%3fpage%3dmisc%2fspecialoffers%26pgmarket%3den-ca