Creating dynamic ENVIRONMENT VARIABLES
Glenn
Glenn at Baxterit.com.au
Tue Oct 4 10:06:45 CDT 2005
And catching up on the Environment Variables issue.
I found it a little bewildering coming from a hp3000 environment; where we
enjoyed system; account; user and group catalogues for such variables.
Enough of that though!
Syed is using a thin client deployment; My understanding is that all
referenced environment variables must be true at the server; at the time of
executiion; if they are used for naming/ locating etc.
The server variable PH_SBF_LOC is a good example. Powerhouse is executing at
the server; so looks for it. We set it from the server. An Axiant thin
client does not need it AND cannot over-ride it.
To reference an environment variable; such as Syed's quiz naming convention;
implies that that value is true at the server at the time of creation;
because that's where the file is being created.
To me that implied that it must be within the command file being executed;
if you are using command files that is.
We do use SETX at the client; via a common logon script; called by the NT
logon procedure. This sets environment variables at the Client once at
logon.
We have non powerhouse app which handles parms and prompts and printer
choice and copies; which is called from Axiant. It is based on a database of
batfile names; components; where each component may be qtp;quiz etc and may
also require parms for prompts etc.
Quiz can have output; thus requiring a printer choice and copy selection!
The app picks the variables and builds a "bat" file to the server;
containing the many set strings. These are valid for the batch process. Our
batch process' may contain multiple quiz; qtp or OS commands and resulting
"print /d" commands etc.
The resulting "bat" file is "given" by the axiant client to the server;
containing references to the client/local env variables; in short comprising
some of:
%ph_server%\%ph_root%\%ph_application%\%ph_user%\%ph_submit_location%\batfil
e_date_time.bat eg
\\my_server\phapps\sales\glenn\batfiles\dothis_20051004_090909.bat
Report output is named by
%ph_server%\%ph_root%\%ph_application%\%ph_user%\%ph_report_location%\progra
m_date_time.txt
Logging is "piped" to
%ph_server%\%ph_root%\%ph_application%\%ph_user%\%ph_log_location%\batfile_d
ate_time.log
Parms are piped into each component at the command line from
%ph_server%\%ph_root%\%ph_application%\%ph_user%\%ph_parms_location%\program
_date_time.parms
The command files can be built to a local drive I guess. We preferred to see
all components at the server.
We use the command /c contstruct to "call" the resulting command file from
the Axiant Client; it passes it to the user NETD session.
We use WinCron to schedule tasks. It happily monitors a folder for "start"
commands; not unlike AT; offering start time; repeat processing features. It
runs as an NT Service.
Remember;
- Set - will set a value for a session only.
- SetX - will set a value at the machine; until updated or removed; client
or server. SetX is valid for Win2000 or Xp.
- Any env variable if used for Thin Client execution; must be visible to the
server; so a Client SetX variable will essentially be invisible to the
server, unless the value is "passed" to the server; say via a "bat" file.
Regards
Glenn Baxter
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: Tuesday, 4 October 2005 8:56 PM
To: shulbert at clblf.com; powerh-l at lists.sowder.com
Subject: RE: Creating dynamic ENVIRONMENT VARIABLES
I have always assumed that the administrator is required only to actually
execute the AT command. Once the file is AT'ed, to run every five minutes
for example, presumably any file that is referenced by it for execution can
be written to from the Axiant user's process - simulating the AT command.
To give a very basic example, if a .cmd file, AT'ed ( by an administrator)
to run every 10 minutes, contained syntax
'call c:\cmds\do_userx_10min_commands.cmd'
the commands for this file could be written to it from the axiant client at
any point, and then be executed within the next ten minutes.
There could be a file AT'ed to run once every hour, once a day ...etc... The
developer would only have to add additional file calls.
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
shulbert at clblf.com
Sent: 04 October 2005 11:33
To: powerh-l at lists.sowder.com
Subject: RE: Creating dynamic ENVIRONMENT VARIABLES
you need to belong to the administrator group to use the AT command to
stream background jobs on the server.
utility vs security: utility wins.
and, besides, you don't HAVE to tell the users they've got admin rights on
the server.
regards,
stephen.
-----Original Message-----
From: atla38 at dsl.pipex.com [mailto:atla38 at dsl.pipex.com] Sent:
Tuesday, October 04, 2005 11:24 AM
To: sshahulgm at gmail.com
Cc: powerh-l at lists.sowder.com
Subject: RE: Creating dynamic ENVIRONMENT VARIABLES
a chap named Chad said that you can use command 'setx' to create a system
env, but I believe this depends on the version of DOS you have ( V6
probably).
I'm still not sure why you want to be an administrator to run Axiant -
wouldn't this be risky at an unattended desktop - these are the usual
arguments against.
I'm pretty sure that sestsystemval on Windows platforms creates a variable
that is available to child processes only.
Regards, Joe. _____ From: Syed Shahul Hameed Mustaffa
[mailto:sshahulgm at gmail.com] Sent: 04 October 2005 11:07
To: Joe Boyle
Cc: powerh-l at lists.sowder.com
Subject: Re: Creating dynamic ENVIRONMENT VARIABLES
Thanks joe.
The login dialog appears when I start the application.
Glenn in one of his mails says (if I am remembering correctly) it appears
and there is no way to suppress it. I tried logging into to the server
using the application's network userid. I tried to create environment
variables. But the system doesn't let me create system environment
variables. However it permits me to create user environment variables. but
SETSSTEMVAL function creates a system env.
variable and not a user environment variable. Regards,
SYED.
On 10/4/05, Joe Boyle <atla38 at dsl.pipex.com> wrote: it might be worth
typing the string below ( or a variation ) in the google search window
http://www.google.co.uk/ , I hav'nt tried the security options in the netd
config window personally, so am not sure if this is what you are looking
for,
site:lists.sowder.com <http://lists.sowder.com/> powerh-l axiant security
netd
Regards, Joe. _____ From: Joe Boyle [mailto: atla38 at dsl.pipex.com] Sent:
03 October 2005 22:00
To: 'Syed Shahul Hameed Mustaffa'; 'powerh-l at lists.sowder.com'
Subject: RE: Creating dynamic ENVIRONMENT VARIABLES
personally I would use syntax 'set report device disc NOLIMIT name
$UEVD_REPNAME ; but that aside, why do you feel that the network user you
are using to connect to server has to be a member of the ADMINISTRATORS
group ?
Incidentally, I am always happy for the users to log in when they run the
Ax app, so I wonder if this is happening at other times, when exactly are
your
users being prompted for login details ? 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
<mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com> ] On Behalf
Of Syed Shahul Hameed Mustaffa
Sent: 03 October 2005 21:17 To: powerh-l at lists.sowder.com
Cc: Joe Boyle; Glenn
Subject: Creating dynamic ENVIRONMENT VARIABLES
Dear Gurus,
I'm using AXIANT 4GL/PH/WINDOWS (Thin Client).
To set the report path dynamically, I am storing the path in the database.
I'm creating a dynamic Windows environment variable to pass this path to the
report using the following command.
SETSYSTEMVAL("UEVD_REPNAME", TRUNCATE(REPORTFILE))
I'm using the following command in the quiz file.
set report device disc LIMIT 10000 name $UEVD_REPNAME
My issue is security.
The network user I'm using to connect to server has to be a member of the
ADMINISTRATORS group.
And I could not suppress the network user logon dialog box. How can I
resolve this issue?
Can anyone helpme out of this issue? 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 <password>" 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.
<< File: ALTERNATIVE.HTM >>
CLB Littlejohn Frazer
Chartered Accountants
1 Park Place
Canary Wharf
London
E14 4HJ
Tel 020 7987 5030
Fax 020 7987 9707
www.clblf.com
The information contained in this communication is confidential and may be
legally privileged. It is intended solely for the use of the individual or
entity to whom it is addressed and others authorised to receive it. If you
are not the intended recipient you are hereby notified that any disclosure,
copying, distribution or taking of any action in reliance on the contents of
this information is strictly prohibited and may be unlawful.
CLB Littlejohn Frazer reserves the right to monitor the content of any
message sent to or from clblf.com.
A list of partners may be inspected at the above address which is also the
address for serving documents.
CLB Littlejohn Frazer is registered to carry on audit work by the Institute
of Chartered Accountants in England & Wales, and authorised and regulated by
the Financial Services Authority for investment business.
CLB Corporate Finance LLP is authorised and regulated by the Financial
Services Authority.
--
= = = = = = = = = = = = = = = = = = = = = = = = = = = = Mailing list:
powerh-l at lists.sowder.com
Subscribe: "subscribe" in message body to powerh-l-request at lists.sowder.com
Unsubscribe: "unsubscribe <password>" 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 <password>" 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.
More information about the powerh-l
mailing list