Environment Variable question. QTP doesn't recognize env-variables

Syed Shahul Hameed Mustaffa sshahulgm at gmail.com
Fri Dec 23 05:49:21 CST 2005 

Very Sorry Joe!

I was out of office and was busy with some important work.
As I told you, I have this problem only with data load qtps.
Others are working well as before.
So I don't have many such scripts and in fact I might do it only for a very
few number of times.
So , for the time being, I'm ignoring the problem.

However I'd like to find a workaround for the problem. If you need me to
send you my scripts in SQL, I'll do so.

Best Regards,
SYED.


On 12/18/05, Joe Boyle <atla38 at dsl.pipex.com> wrote:
>
> I am assuming that the directory/folder pointed to by the environment
> variable does actually exist ?
>
> Regards, Joe.
>
> -----Original Message-----
> From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
> [mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On Behalf
> Of
> Joe Boyle
> Sent: 18 December 2005 11:41
> To: 'Syed Shahul Hameed Mustaffa'
> Cc: 'PowerHouse List'
> Subject: RE: Environment Variable question. QTP doesn't recognize
> env-variables
>
> Hi Syed,
>
> your earlier email says you are running qtp as below, I can't see how
> licenses would be an issue with this, you must have at least runtime
> access
> which is all you need to execute a .qtc file,
>
>      cmd /c qtp.exe dict=D:\HERDSPRD\Dictionary\hms.pdc
> auto=D:\HERDSPRD\RemoteBuild\test.qtc
>
> the .qtc file must be running in order to give the error : no such file or
> directory (ERRNO 2)File: $PSLOC2\alupdd
>
> As for scheduling, I found the AT command to work ok.
>
> I would need a more detailed example of what you are doing to be of any
> help
> on this.
>
>
> Regards, Joe.
> ________________________________________
> From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
> [mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On Behalf
> Of
> Syed Shahul Hameed Mustaffa
> Sent: 18 December 2005 08:03
> To: Glenn Baxter; Ken at langendock.com; Joe Boyle
> Cc: PowerHouse List
> Subject: Re: Environment Variable question. QTP doesn't recognize
> env-variables
>
> Thank you so much for all you tips and detailed explanations.
>
> To see if PH is picking up the variable, I followed the way of Joe (which
> he
> states one of his earliers mails).I connected to QTP from the cmd prompt
> and issued $set <env-var name> command. PH picks up the variable from
> here.
>
> The issue actually seems to be what Ken is saying in his last mail. The
> problem happens only with data load scripts. Logically it doesn't make any
> sense to me (probably because of my lack of indepth knowledge of PH
> internals). With other qtps that are creating subfiles and quizs using
> these
> subfiles, it doesn't give me any problem. I lately understood that I
> cannot
> use QTP or QUIZ interactively in the PRODUCTION machine, because I don't
> have a development license.
>
> Glenn! Are u asking me to call the set batch file just before I call the
> qtp
> from a quick screen. In my case I'm streaming all these statements to SQL
> Server job manager (ie SQL SERVER AGENT) as a replacement solution for
> powerfuljob scheduling functionality of MPEIX .
>
> Regards,
> SYED.
>
> On 12/18/05, Glenn <Glenn at baxterit.com.au> wrote:
> Hi Syed, Joe and others,
>
> Like Syed {I think} I had set my environment variables at the server. I
> did
> this from Control Panel etc. They are permanent.
> I had only set PH_SUBF_LOC and not pathed any Qtp for the reload.
> I did not compile my reloads.
> These reloads worked as PH_SBF_LOC is always "known" to PH if set.
> The command files were executed AT the server, by double clicking from
> explorer.
>
> If I wasn't sure is a variable was/was not set I would simpley insert a
> "set" statement into by "bat" file and pipe it to a txt file eg
>
> Set > true_variables.txt
>
> Insertthe command ahead of your Qtp reload statement. The file will be
> created in the current directory - from where you are running the command.
> In this way you will at least be able to see if the variable does exist.
>
> Remember: each server set variable is ONLY true at the server; so the
> command file must be executed from the server; in the same way that NETD
> executes commands for you at the server {Thin Client}.
>
> Let us know if you do see the variable.
> What PH8 version are you running at the server?
> Glenn Baxter
> =======================
> Baxter IT Solutions Pty Ltd
> e: glenn at baxterit.com.au
> =======================
>
>
> -----Original Message-----
> From: powerh-l-bounces+glenn=baxterit.com.au at lists.sowder.com
> [mailto: powerh-l-bounces+glenn=baxterit.com.au at lists.sowder.com] On
> Behalf
> Of Joe Boyle
> Sent: Sunday, 18 December 2005 5:34 AM
> To: 'Syed Shahul Hameed Mustaffa'
> Cc: 'PowerHouse List'
> Subject: RE: Environment Variable question. QTP doesn't recognize
> env-variables
>
> I recall one other possibility, which is that Axiant has an option to
> associate a command file with a given run profile; I would imagine that
> any
> environment settings created in it would be available to all processes
> executed below it. Could it be that you have such a command file but it
> has
> been changed by someone ?
>
> Other than that I can't think of anything else, unless there is a bug in
> your qtp version which might be saving the envar translation at compile
> time, rather than a pointer to it.
>
> Could it be that you had a system level envar set at the time this code
> worked, but don't have it set now ?
>
> A new cmd window will not see a user level envar so this must be the
> explanation.Why is it they you cannot simply create a new system level
> envvar ?
>
> Regards, Joe.
>
> ________________________________________
> From: powerh-l-bounces+atla38= dsl.pipex.com at lists.sowder.com
> [mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On Behalf
> Of
> Syed Shahul Hameed Mustaffa
> Sent: 17 December 2005 15:27
> To: Joe Boyle
> Cc: PowerHouse List
> Subject: Re: Environment Variable question. QTP doesn't recognize
> env-variables
>
> Thanks Joe for all your tips.
>
> The same code was working well before.
> Why should it suddenly stop?
> I don't have the option to change the code now.
>
> Is there any PH configuration that might have affected the server?
> Could any windows update cause this problem?
>
> Regards,
> SYED.
>
>
>
>
> On 12/17/05, Joe Boyle <atla38 at dsl.pipex.com> wrote:
> please ignore the %%1 part, that is true of the 'for' command only;
> parameters in command files are %1 to %8 and not %%1 to %%8.
>
> Regards, Joe.
>
>
> -----Original Message-----
> From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
> [mailto: powerh-l-bounces+atla38= dsl.pipex.com at lists.sowder.com] On
> Behalf
> Of Joe Boyle
> Sent: 17 December 2005 10:03
> To: 'Syed Shahul Hameed Mustaffa'
> Cc: 'PowerHouse List'
> Subject: RE: Environment Variable question. QTP doesn't recognize
> env-variables
>
> Another alternative approach is to use a command file as follows, this way
> you can set the value locally before executing the qtp,
>
> Doqtp.cmd
> Set PSLOC2=%%1
> qtp dict=D:\HERDSPRD\Dictionary\hms.pdc
> auto=D:\HERDSPRD\RemoteBuild\test.qtc
> exit
>
> the powerhouse/axiant syntax would go like that below,
>
> let t_path = "string"
> let t_run_command = "cmd /c d:\loc_path\ Doqtp.cmd " + t_path run command
> t_run_command
>
> The value in t_path will be passed to the script as parameter i.e. %1 of
> possible %1 to %8 parameters. If you run the script locally you have to
> use
> %1 only, if in batch use %%1 i.e. two percent signs.
>
>
> Regards, Joe.
> ________________________________________
> From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
> [mailto: powerh-l-bounces+atla38= dsl.pipex.com at lists.sowder.com] On
> Behalf
> Of Syed Shahul Hameed Mustaffa
> Sent: 17 December 2005 05:26
> To: Joe Boyle; Ken at langendock.com
> Cc: PowerHouse List
> Subject: Re: Environment Variable question. QTP doesn't recognize
> env-variables
>
> Thanks Joe, Ken.
>
> Joe! I checked #set.. from QTP. It is picking up the correct value.
> However
> when I attempt to run the qtp (cmd /c qtp.exe
> dict=D:\HERDSPRD\Dictionary\hms.pdc auto=D:\HERDSPRD\RemoteBuild\test.qtc)
> it fails with the following error message. But in development it is
> working
> without any problem.
>
> ============ ERROR MESSAGE ====================== Data access error.
> File: $PSLOC2\alupdd
> Action Taken: Run terminated.
> -------------------------------------
> No such file or directory (ERRNO 2)
> File: $PSLOC2\alupdd
> -------------------------------------
> Finished.
> =================================================
>
> Ken! This system environment variable is a permanant one (Created from
> Windows MyComputer). The same code was working well before.
>
>
> Regards,
> SYED.
>
> On 12/16/05, Joe Boyle <atla38 at dsl.pipex.com> wrote:
> Do you have embedded spaces in the path specified in your variable
> settings
> ?
>
> If you go into qtp, and type '$set spsloc2' do you see the correct path
> displayed ?
>
> do
>
> Regards, Joe.
> ________________________________________
> From: Syed Shahul Hameed Mustaffa [mailto: sshahulgm at gmail.com]
> Sent: 16 December 2005 18:06
> To: PowerHouse List
> Cc: Joe Boyle
> Subject: Environment Variable question. QTP doesn't recongize
> env-variables
>
> Dear Gurus,
>
> Quick Intro: I've migrated a PH/MPEIX application to
> AXIANT4GL/PH4GL/WINDOWS
>
>
> (Thin Client).
>
> I have qtps to load the MPEIX/PH data into the WINDOWS/PH.
> I used environment variable to identify the location of the data files.
>
> eg
> set process
> nolimit
> request ONE
> acc *$PSLOC2\alupdd alias PS_ALPRO_UPDATE_D
>
> BUILD SMALL_TABLES_1
> ;-------------------------------------
> It was working well before. Last time I used these qtps to load my data.
> Suddenly these qtps arenot working. Because PH doesn't recognize the
> environment variable.
> I checked the environment variable. It is there and ok.
> I recreated it and restarted the server too.
> Still PH doesn't recognize the environment variable.
> I tried changing the environment variable to another env-variable I'm
> using
> in other qtps. PH not recognizing this variable too.
> I had to hardcode a path in all my data load qtps to make it work. (That
> proves, there is nothing wrong with the data files).
>
> What could have gone wrong?
> I'm using environment variables widely in my application.
> If PH stops recognizing variables like this, it will be disaster.
>
> Can anyone please help me in this? I'll appreciate.
>
> Regards,
> SYED
>
>
>
>
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = 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.
>
>
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = 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.
>
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> 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.
>
>
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> 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.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20051223/64b46277/attachment-0001.htm

More information about the powerh-l mailing list