Re: The Forte Stopwatch

We had a similar problem. We reported the problem to Forte technical
support and they determined that it is a bug. I don't know if this has been
fixed in the 3.0.F release.
The Stopwatch seems to be accurate for long (several second) intervals, but
it can't be trusted for measuring short intervals.
Kevin Klein
Millennium Partners, Inc.
-----Original Message-----
From: [email protected] <[email protected]>
To: [email protected] <[email protected]>
Date: Tuesday, December 30, 1997 1:40 PM
Subject: The Forte Stopwatch
>
All,
At our site we are using Windows NT 4.0 clients and a Windows NT
Server with Forte 3.0.E.0.
Periodically, we use the Forte StopWatch class to measure durations for
access to data. We've noticed
a strange phenomenon, and we're not sure if it's simply circumstance or if
there's a problem. All of the
measured durations that we receive through the Split method appear to
contain either a 0 or a 9 in the
tenth-of-a-second position. For example, values of 1011 and 1912. Has
anybody noticed this?
Thank you,
Keith

Hello Kevin,
Normally, it has been corrected from the last public release 2.
Hope this helps.
Daniel Nguyen
Kevin Klein wrote:
>
We had a similar problem. We reported the problem to Forte technical
support and they determined that it is a bug. I don't know if this has been
fixed in the 3.0.F release.
The Stopwatch seems to be accurate for long (several second) intervals, but
it can't be trusted for measuring short intervals.
Kevin Klein
Millennium Partners, Inc.
-----Original Message-----
From: [email protected] <[email protected]>
To: [email protected] <[email protected]>
Date: Tuesday, December 30, 1997 1:40 PM
Subject: The Forte Stopwatch
All,
At our site we are using Windows NT 4.0 clients and a Windows NT
Server with Forte 3.0.E.0.
Periodically, we use the Forte StopWatch class to measure durations for
access to data. We've noticed
a strange phenomenon, and we're not sure if it's simply circumstance or if
there's a problem. All of the
measured durations that we receive through the Split method appear to
contain either a 0 or a 9 in the
tenth-of-a-second position. For example, values of 1011 and 1912. Has
anybody noticed this?
Thank you,
Keith
Name: Kevin Klein.vcf
Part 1.2 Type: text/x-vcard
Encoding: 7bit

Similar Messages

Bus error in the Forte executable

Hi,
We have an environment with forte' (ver. 3.0.G.2) running
on AIX 4.1 (The name of central server is cld_app1 and the nodemgr start
with the name cld_TDR). In our environment we are using two differnet
repository. In rep1 we have a very simple project (called 'aaa') that
use one small class with two methods. One method print the date & time.
The second method communicate with a serviceobject that use MQSeries to
put/get some messages in the queues.
The project work correctly in test run and in distribuite mode.
If we export the same project (aaa) and we import in other repository
(rep2 in the same environment) the project doesn't work. Infact,
during test run forte' return the following:
Begin Stack Backtrace
=========================================================
=
Trace caused by a bus error in the Forte executable:
ftexec Version 3.0.G.2
IBM RS6000/Aix 4.1
Forte Application Environment (tm), Forte Runtime Environment (tm),
Forte Conductor (tm):
Copyright (c) 1994-1998, Forte Software, Inc. and its licensors.
US Patent No. 5,457,797
Forte Express (tm), Forte WebEnterprise (tm):
Copyright (c) 1995-1998, Forte Software, Inc.
All Rights Reserved.
Unpublished rights reserved under the copyright laws of the United
States.
Fri Mar 13 16:07:45 1998
Fault at 25-Mar-1999 10:42:53, pid '2292', node 'cld_app1':
0xd0b8886c = d0b8886c()
0xd0b88ae4 = d0b88ae4()
qqos_StkTrc: Cannot print stack trace.
Recursive stack trace detected. Exiting.
If we try to run in partitioning mode, the same error appears when
forte' "loading partition into server" with the following adding
message:
Unable to start the partition aaa_cl0_Part1 on any of nodes to wich
been assigned. See the remainder of the error stack for more
information.
In the "more" informations we have the following:
SYSTEM ERROR: Unable to start the partition aaa_cl0_Part1 on any of the
nodes to which it has been assigned. See the remainder of the error
stack for more
information.
Class: qqsp_ResourceException
Error #: [1602, 593]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
Last TOOL statement: method overview.StartApplication
Error Time: Thu Mar 25 09:22:21
Exception occurred (locally) on partition "Forte_cl0_Client",
(partitionId
= 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
[546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
application
"Forte_cl0", pid 20236 on node cld_app1 in environment
Collaudo_TDR.
SYSTEM ERROR: Unable to start partition aaa_cl0_Part1 on node cld_TDR.
Class: qqsp_ErrorDescriptor
Error #: [1602, 592]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
Error Time: Thu Mar 25 09:22:21
Exception occurred (locally) on partition "Forte_cl0_Client",
(partitionId
= 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
[546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
application
"Forte_cl0", pid 20236 on node cld_app1 in environment
Collaudo_TDR.
SYSTEM ERROR: Lost contact with remote server while trying to load
partition
aaa_cl0_Part1. Check server log file for more information about the
specific
problem.
Class: qqsp_ResourceException
Error #: [1301, 102]
Detected at: qqem_IPartitionAgent::Startup at 5
Error Time: Thu Mar 25 09:22:21
Exception occurred (locally) on partition "Forte_cl0_Client",
(partitionId
= 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
[546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
application
"Forte_cl0", pid 20236 on node cld_app1 in environment
Collaudo_TDR.
INFORMATION: The connection to the partner was terminated by the
Communication
Manager for the reasons below.
Class: qqsp_DistAccessException
Detected at: qqdo_PartitionMgr::StopLocation at 1
Error Time: Thu Mar 25 09:22:20
Distributed method called: qqrt_ForteExecAgentProxy.LoadPartition!6
(object name Unnamed) from partition "Forte_Executor",
(partitionId =
546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158, taskId =
[546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158.19]) in application
"Forte_cl0", pid 20236 on node cld_app1 in environment
Collaudo_TDR
Exception occurred (locally) on partition "Forte_cl0_Client",
(partitionId
= 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
[546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
application
"Forte_cl0", pid 20236 on node cld_app1 in environment
Collaudo_TDR.
INFORMATION: Network partner closed connection. This usually means the
process at the other end of the wire failed. Please go look there and
find
out why.
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Thu Mar 25 09:22:20
Exception occurred (locally) on partition "Forte_cl0_Client",
(partitionId
= 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
[546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
application
"Forte_cl0", pid 20236 on node cld_app1 in environment
Collaudo_TDR.
INFORMATION: Error parameters for Set:0 Msg:0:
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Thu Mar 25 09:22:20
Exception occurred (locally) on partition "Forte_cl0_Client",
(partitionId
= 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
[546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
application
"Forte_cl0", pid 20236 on node cld_app1 in environment
Collaudo_TDR.
Thanks in advance
Luz Marina e Massimiliano
Get Your Private, Free Email at http://www.hotmail.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Hi,
We have an environment with forte' (ver. 3.0.G.2) running
on AIX 4.1 (The name of central server is cld_app1 and the nodemgr start
with the name cld_TDR). In our environment we are using two differnet
repository. In rep1 we have a very simple project (called 'aaa') that
use one small class with two methods. One method print the date & time.
The second method communicate with a serviceobject that use MQSeries to
put/get some messages in the queues.
The project work correctly in test run and in distribuite mode.
If we export the same project (aaa) and we import in other repository
(rep2 in the same environment) the project doesn't work. Infact,
during test run forte' return the following:
Begin Stack Backtrace
=========================================================
=
Trace caused by a bus error in the Forte executable:
ftexec Version 3.0.G.2
IBM RS6000/Aix 4.1
Forte Application Environment (tm), Forte Runtime Environment (tm),
Forte Conductor (tm):
Copyright (c) 1994-1998, Forte Software, Inc. and its licensors.
US Patent No. 5,457,797
Forte Express (tm), Forte WebEnterprise (tm):
Copyright (c) 1995-1998, Forte Software, Inc.
All Rights Reserved.
Unpublished rights reserved under the copyright laws of the United
States.
Fri Mar 13 16:07:45 1998
Fault at 25-Mar-1999 10:42:53, pid '2292', node 'cld_app1':
0xd0b8886c = d0b8886c()
0xd0b88ae4 = d0b88ae4()
qqos_StkTrc: Cannot print stack trace.
Recursive stack trace detected. Exiting.
If we try to run in partitioning mode, the same error appears when
forte' "loading partition into server" with the following adding
message:
Unable to start the partition aaa_cl0_Part1 on any of nodes to wich
been assigned. See the remainder of the error stack for more
information.
In the "more" informations we have the following:
SYSTEM ERROR: Unable to start the partition aaa_cl0_Part1 on any of the
nodes to which it has been assigned. See the remainder of the error
stack for more
information.
Class: qqsp_ResourceException
Error #: [1602, 593]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
Last TOOL statement: method overview.StartApplication
Error Time: Thu Mar 25 09:22:21
Exception occurred (locally) on partition "Forte_cl0_Client",
(partitionId
= 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
[546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
application
"Forte_cl0", pid 20236 on node cld_app1 in environment
Collaudo_TDR.
SYSTEM ERROR: Unable to start partition aaa_cl0_Part1 on node cld_TDR.
Class: qqsp_ErrorDescriptor
Error #: [1602, 592]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
Error Time: Thu Mar 25 09:22:21
Exception occurred (locally) on partition "Forte_cl0_Client",
(partitionId
= 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
[546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
application
"Forte_cl0", pid 20236 on node cld_app1 in environment
Collaudo_TDR.
SYSTEM ERROR: Lost contact with remote server while trying to load
partition
aaa_cl0_Part1. Check server log file for more information about the
specific
problem.
Class: qqsp_ResourceException
Error #: [1301, 102]
Detected at: qqem_IPartitionAgent::Startup at 5
Error Time: Thu Mar 25 09:22:21
Exception occurred (locally) on partition "Forte_cl0_Client",
(partitionId
= 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
[546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
application
"Forte_cl0", pid 20236 on node cld_app1 in environment
Collaudo_TDR.
INFORMATION: The connection to the partner was terminated by the
Communication
Manager for the reasons below.
Class: qqsp_DistAccessException
Detected at: qqdo_PartitionMgr::StopLocation at 1
Error Time: Thu Mar 25 09:22:20
Distributed method called: qqrt_ForteExecAgentProxy.LoadPartition!6
(object name Unnamed) from partition "Forte_Executor",
(partitionId =
546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158, taskId =
[546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158.19]) in application
"Forte_cl0", pid 20236 on node cld_app1 in environment
Collaudo_TDR
Exception occurred (locally) on partition "Forte_cl0_Client",
(partitionId
= 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
[546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
application
"Forte_cl0", pid 20236 on node cld_app1 in environment
Collaudo_TDR.
INFORMATION: Network partner closed connection. This usually means the
process at the other end of the wire failed. Please go look there and
find
out why.
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Thu Mar 25 09:22:20
Exception occurred (locally) on partition "Forte_cl0_Client",
(partitionId
= 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
[546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
application
"Forte_cl0", pid 20236 on node cld_app1 in environment
Collaudo_TDR.
INFORMATION: Error parameters for Set:0 Msg:0:
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Thu Mar 25 09:22:20
Exception occurred (locally) on partition "Forte_cl0_Client",
(partitionId
= 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
[546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
application
"Forte_cl0", pid 20236 on node cld_app1 in environment
Collaudo_TDR.
Thanks in advance
Luz Marina e Massimiliano
Get Your Private, Free Email at http://www.hotmail.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

How to use the Forte C++ (SunWorkshop)

Hello!
I want to compile the Wine (Windows Emulator) for Solaris 9 (x86). One way is that I install gcc 3.2, and the other is to use the FORTE C++ compiler provided by Sun Microsystems. Now, I have downloaded the gcc-3.2 source code from the sunfreeware.com. But I am unable to install the gcc compiler.
Please guide me (or any reference) to some easy installation methods for gcc, or else, tell me the way, I could use the Forte C++ compilers, provided by SUN. I am unable to find a way to use the Forte.

Geeze, a second request on how to make gcc. Guess it's time for me to brush up. :)
First off, make sure you have the prerequisites installed:
http://gcc.gnu.org/install/prerequisites.html
A full install of Sol 9 should have everything on that list above.
Unpack the gcc source code into a directory, go into that directory and do the following:
% mkdir objdir
% cd objdir
% ../configure
assuming the configure goes ok do this:
% make CFLAGS='-O' LIBCFLAGS='-g -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
then assuming the compiling went ok:
% make install
I've compiled gcc before, and it can take several hours. Of course the last time I did it was on really slow machines for gcc 2.7.2, so maybe gcc 3.3.2 is quicker to compile :)
I'll take this opportunity to say that I've used the gcc package (from http://www.sunfreeware.com/ ) without any problems for quite some time...
As for Forte C++ compiler, (that's "cc" isn't it?), you should make sure it's in your path before everything else, then try to use it. Or optionally you can set the environment variable CC=<path to your cc compiler>, some applications will use that environment variable (while others do not, but it's worth a try).
Daryl

Classpath in the FORTE

Hello,
knows where I configures classpath of the FORTE?
I am trying to compile a program in the FORTE and receive the following message:
java.lang.ClassNotFoundException: to org.postgresql.Driver
When I compel using javac this error does not appear.
I thank any suggestion.
Darcy

If you add the JAR file containing the required packages & classes to the project, the Forte compiler should see the classes, IIRC.
Bhav

Specifying Repository Name in the Forte Shortcut

I have been looking for information on how to specify the Repository Name
with the Forte shortcut. I have a couple of repositories and I would
like to create a Forte shortcut for each repository. I am running Forte
3.0.E.0 on an NT 4.0 box. I have been trying the following command:
c:\forte\install\bin\ftcmd.exe run "forte -fr bt:central -fnd
<nodename>"
Where central is the name of the physical repository on <nodename>. I've
tried several variations without success and cannot connect with the
CentralRepository. Any suggestions? I know that I can startup the Forte
Control Panel and specify the name on that dialog, but that is tedious
when trying to switch between multiple repositories. Thanks.
Bradley K Wells
Strong Capital Management, Inc
http://www.strong-funds.com

It looks like you are not using the proper syntax for ftcmd. Refer to "A Guide to the Forte Workshops" p51,54 for the complete list of flags for ftcmd.
I believe the following is what you should use. If you are accessing a repos through a rpserver, then the repos flag needs the repos name and does not need the repos type (bt). The repos name is the value for the -n flag for the rpserver.
c:\forte\install\bin\ftcmd.exe -fnd nodename -fr central run forte
Hope this helps,
Andrew Zwerin
[email protected]
To: [email protected]
From: [email protected]@internetmime on Mon, Dec 22, 1997 7:59 PM
Subject: Specifying Repository Name in the Forte Shortcut
I have been looking for information on how to specify the Repository Name
with the Forte shortcut. I have a couple of repositories and I would
like to create a Forte shortcut for each repository. I am running Forte
3.0.E.0 on an NT 4.0 box. I have been trying the following command:
c:\forte\install\bin\ftcmd.exe run "forte -fr bt:central -fnd
<nodename>"
Where central is the name of the physical repository on <nodename>. I've
tried several variations without success and cannot connect with the
CentralRepository. Any suggestions? I know that I can startup the Forte
Control Panel and specify the name on that dialog, but that is tedious
when trying to switch between multiple repositories. Thanks.
Bradley K Wells
Strong Capital Management, Inc
http://www.strong-funds.com
------------------ Mail Header Follows ------------------
Date: 22 Dec 97 17:41:48 -0800
Sender: "[email protected]" <owner-forte-users@SageIT#d#com>
From: "[email protected]@internetmime" <brwells@strong-funds#d#com@internetmime>
Reply-To: "[email protected]@internetmime" <brwells@strong-funds#d#com@internetmime>
To: "[email protected]" <forte-users@Sagesoln#d#com> (Reply not requested)
Subject: Specifying Repository Name in the Forte Shortcut
UA-Content-Id: Specifying Repos
Delivery-Time-Stamp: Mon Dec 22 19:53:05 1997
P1-Recipient: "Zwerin_Andrew" <Zwerin#u#Andrew>,
"Murphy_Bill" <Murphy#u#Bill>, "Rahmey_Ness" <Rahmey#u#Ness>
Priority: normal
Importance: normal
P1-Message-Id: us*mailserver.stron*TWI;971222195242
Original-Encoded-Information-Types: IA5-Text
X400-Trace: us*mailserver.stron*TWI; arrival 971222174148-0800 deferred 971222174148-0800 action Relayed
X400-Trace: us*thud*TWI; arrival 971222174026-0600 deferred 971222174026-0600 action Relayed
X400-Trace: us*pebble.sagesoln.*TWI; arrival 971222154008-0800 deferred 971222154008-0800 action Relayed
X400-Trace: us*pebble.SageIT.co*TWI; arrival 971222154034-0800 deferred 971222154034-0800 action Relayed
X400-Trace: us*pebble.SageIT.co*TWI; arrival 971222154036-0800 deferred 971222154036-0800 action Relayed
X400-Trace: us*ec-fw2.twi.com*TWI; arrival 971223005248Z deferred 971223005248Z action Relayed
X400-Trace: us*ecsmtp.twi.com*TWI; arrival 971222195125-0500 deferred 971222195125-0500 action Relayed
X400-Trace: us*twwtny1.twi.com*TWI; arrival 971222195240-0500 deferred 971222195240-0500 action Relayed
X400-Trace: US*MCI*TWI; arrival 971222174000-0800 deferred 971222174000-0800 action Relayed
Message-Id: <349F16DC#064#mailserver#d#strong-funds#d#com*/>
P1-Content-Type: P2

Drop me from the forte-users list

Please drop me from the forte-users list. [email protected]
Thanks

I think you may need to contact customer service regarding your request. Just click the link below to see the instructions on how you can get in touch with the Support team ;
http://community.skype.com/t5/The-Skype-Lounge/How-to-Contact-Skype-Customer-Service/td-p/2056783
IF YOU FOUND OUR POST USEFUL THEN PLEASE GIVE "KUDOS". IF IT HELPED TO FIX YOUR ISSUE PLEASE MARK IT AS A "SOLUTION" TO HELP OTHERS. THANKS!
ALTERNATIVE SKYPE DOWNLOAD LINKS | HOW TO RECORD SKYPE VIDEO CALLS | HOW TO HANDLE SUSPICIOS CALLS AND MESSAGES
SEE MORE TIPS, TRICKS, TUTORIALS AND UPDATES in
| skypefordummies.blogspot.com |

Is there any way to copy the numbers from the iPad stopwatch?

I am doing some timestudies using the stopwatch in the clock app on an iPad mini. Is there anyway to get the time out of the stopwatch and into notes or an e-mail? I would like the text not just a screenshot of the stopwatch.

No, you can't. There are stopwatch apps out there that have that feature, but the default iOS app can not. I agree, it should have that feature.

RE: Native Forte Clients with Express Services

I would be very interested in hearing from anyone using Express who may
have attempted using Native Forte Clients with Express Services, especially
what problems/issues (if any) you encountered and whether you found it to
be a successful way to develop complex screens where the 'look and feel'
can't be achieved with Express alone.I wrote a general-purpose windows framework which uses Express Services for its
database access. Had I known what I was letting myself in for, I probably
wouldn't have attempted it! I started it when Express V1 was fairly new, and
Express Windows did not support the types and complexity of relationships
required by the application we were developing. I soon discovered how
difficult it is to implement a completely general framework which handles every
possible permutation. Obviously I ended up making compromises, but what we
have now meets our needs very well. We are about to upgrade to Express V2, so
the real test will be whether the framework migrates smoothly to the new
release.
If I were starting a new project now with Express V2, I don't know if I would
go down the same path. If you do, be aware of the following (based on my
experience of Express V1):
* Your design MUST obey the fundamental rules of Express Services. Your
BusinessQueries must be fired off by the correct BusinessClient subclass,
your BusinessClass attributes must be logged at the right time (depending
on which concurrency scheme you are using), and you must start and end
Express transactions (different to Forte transactions) appropriately.
* Your design needs to take into account the difference in the way Express
Services handles aggregate and non-aggregate associations.
* If you manage parent-child class relationships from your windows, you must
make sure you set and log foreign key attributes at the right time. If
the relationship is not aggregation, you must also manage the order in
which the records are saved to the database (if you use referential
integrity constraints).
* If you call Express Services directly from the windows, it is hard to
reconcile the asynchronous nature of a windows interface with the
database's requirement for things to happen in a certain order. (From
memory, there was a very good discussion in this user group last year of
what should constitute a unit of work in the windows paradigm.) If I
were doing it again, I would move all the Express-related objects and
method calls from the windows to a separate layer, which would manage
putting together the data from multiple windows, assigning foreign keys
and firing things off in the right order.
Fiona Symon
Babylon Software Pty Ltd

Hello Kevin,
Normally, it has been corrected from the last public release 2.
Hope this helps.
Daniel Nguyen
Kevin Klein wrote:
>
We had a similar problem. We reported the problem to Forte technical
support and they determined that it is a bug. I don't know if this has been
fixed in the 3.0.F release.
The Stopwatch seems to be accurate for long (several second) intervals, but
it can't be trusted for measuring short intervals.
Kevin Klein
Millennium Partners, Inc.
-----Original Message-----
From: [email protected] <[email protected]>
To: [email protected] <[email protected]>
Date: Tuesday, December 30, 1997 1:40 PM
Subject: The Forte Stopwatch
All,
At our site we are using Windows NT 4.0 clients and a Windows NT
Server with Forte 3.0.E.0.
Periodically, we use the Forte StopWatch class to measure durations for
access to data. We've noticed
a strange phenomenon, and we're not sure if it's simply circumstance or if
there's a problem. All of the
measured durations that we receive through the Split method appear to
contain either a 0 or a 9 in the
tenth-of-a-second position. For example, values of 1011 and 1912. Has
anybody noticed this?
Thank you,
Keith
Name: Kevin Klein.vcf
Part 1.2 Type: text/x-vcard
Encoding: 7bit

Re: Running the same (Forte) application multiple times -for different

Hi
We had the same problem - how to deploy a number of identical applications, using each their own db.
(for training).
The solution we used is to wrap the entire application into different applications by using a very small
module called KURSUS01, KURSUS02 etc, that did nothing but call the start procedure of the main app.
Then in the dbsession connect, we made a call appname to get the application name, and appended the
first 8 chars to the dbname. Thus our dbnames now points to logicals name: rdbdataKURSUS01, rdbdataKURSUS02 etc.
All this allows us to deploy the identical apps in the same env, or change one version, and run both the old
and new program on the same pc and server at the same time (eg. KURSUS01 and KURSUS02).
I also think this is a kludge - but it works nicely!
Jens Chr
KAD/Denmark
-----Original Message-----
From: Haben, Dirk <[email protected]>
To: 'Soapbox Forte Users' <[email protected]>
Date: 15. januar 1999 09:41
Subject: Running the same (Forte) application multiple times - for different business clients.
Hi All
We have a number of different business clients all willing to use our
application.
The (forte) application is to run on our machines etc for these (business)
clients.
All (business) clients will have their data kept in separate Oracle DBs
(instance).
The problem now is that the entire (forte) application is written using
DBSessions.
Now, depending on what business client needs to be serviced (so to speak) we
need to attach to the right DB - or use the "right" SO.
The two options we can think of are:
Option1:
Programatic change to somehow "know" what (business) client (DB) I'm talking
about and then use the right DB.
Pro:
Only one forte environment to maintain
Can run multiple (business) clients on same PC at the same time
Con:
Requires many program changes
bending O-O rules(?)
can't dynamically name SOs so can it be done at all? (ResourceMGRs maybe?)
Option2:
Use separate environments! One for each business client.
Pro:
More defined separation of app and data,
SLA-easy
Con:
Maintain "n" number of environments
Can only run the application for one environment (business client) at a time
on one PC - Big Negative here!
Not knowing any feasible solution to option 1 (without much code changes and
developer moaning) I would go for option two; as I have already worked on
multi-environment setups on VMS back at the Hydro (hi guys).
I would appreciate any comments from anyone who has solved this problem.
How, Why Pro Con etc.
TIA,
Dirk Haben
Perth, WA
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Hi
We had the same problem - how to deploy a number of identical applications, using each their own db.
(for training).
The solution we used is to wrap the entire application into different applications by using a very small
module called KURSUS01, KURSUS02 etc, that did nothing but call the start procedure of the main app.
Then in the dbsession connect, we made a call appname to get the application name, and appended the
first 8 chars to the dbname. Thus our dbnames now points to logicals name: rdbdataKURSUS01, rdbdataKURSUS02 etc.
All this allows us to deploy the identical apps in the same env, or change one version, and run both the old
and new program on the same pc and server at the same time (eg. KURSUS01 and KURSUS02).
I also think this is a kludge - but it works nicely!
Jens Chr
KAD/Denmark
-----Original Message-----
From: Haben, Dirk <[email protected]>
To: 'Soapbox Forte Users' <[email protected]>
Date: 15. januar 1999 09:41
Subject: Running the same (Forte) application multiple times - for different business clients.
Hi All
We have a number of different business clients all willing to use our
application.
The (forte) application is to run on our machines etc for these (business)
clients.
All (business) clients will have their data kept in separate Oracle DBs
(instance).
The problem now is that the entire (forte) application is written using
DBSessions.
Now, depending on what business client needs to be serviced (so to speak) we
need to attach to the right DB - or use the "right" SO.
The two options we can think of are:
Option1:
Programatic change to somehow "know" what (business) client (DB) I'm talking
about and then use the right DB.
Pro:
Only one forte environment to maintain
Can run multiple (business) clients on same PC at the same time
Con:
Requires many program changes
bending O-O rules(?)
can't dynamically name SOs so can it be done at all? (ResourceMGRs maybe?)
Option2:
Use separate environments! One for each business client.
Pro:
More defined separation of app and data,
SLA-easy
Con:
Maintain "n" number of environments
Can only run the application for one environment (business client) at a time
on one PC - Big Negative here!
Not knowing any feasible solution to option 1 (without much code changes and
developer moaning) I would go for option two; as I have already worked on
multi-environment setups on VMS back at the Hydro (hi guys).
I would appreciate any comments from anyone who has solved this problem.
How, Why Pro Con etc.
TIA,
Dirk Haben
Perth, WA
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

RE: (forte-users) Sv: (forte-users) The Death ofForte

This is what I got today:
Statement of Direction
Sun Microsystems, Inc.
Forté 4GL(tm) Product (formerly the Forté Application Environment)
Product Context
· Forté 4GL is an award-winning, proven product with many unique
advantages for building enterprise business systems that are distributed,
that involve the integration of existing business systems as well as new
functionality, and that target heterogeneous runtime environments.
· Forté 4GL is recognized by Gartner Group as the most successful
Enterprise Application Development Tool.
· The Sun Microsystems, Inc. (SMI) development tools group (formerly
Forté Software, Inc.) has a strong internal commitment to Forté 4GL. Forté
Fusion is written with, and is currently being enhanced with Forté 4GL.
· The SMI development tools group intends to actively enhance and
promote Forté 4GL for the indefinite future. The best opportunity for
attracting new customers is to leverage the ability of Forté 4GL to easily
build powerful shared business services (server components) that can be
accessed by non-Forté clients (e.g., browsers, Java clients) and that can
easily integrate with new and existing business systems.
· The product enhancement plan calls for continuing to issue
incremental releases approximately twice a year. To speed the release of new
functionality, new features will be included with "preview status." This
means that the overall release can support production deployments, but that
the features marked "preview" are certified for development and demos.
· The planned contents of the next two releases are indicated below.
Users should not expect any features other than those on the list. The
contents of subsequent releases will be determined approximately a year in
advance.
· SMI has retained the Forté field sales organization as an
independent unit whose primary product offerings are Forté 4GL and Forté
Fusion. Continued volume sales of Forté 4GL remain the foundation of our
business plan.
Mid-Year Release
· Tentatively labeled "release 3.5" to be distributed as a free
product enhancement for customers under maintenance
· Scheduled for Summer 2000
· Defining features
· Introspection (reflection) - the ability for an object to describe
itself at runtime
· Improved integration with applications developed using
Forté-for-Java Community Edition(tm) (formerly NetBeans)
· Platform support improvements to track important operating system
and database vendor activity
· Target features
· Display system enhancements (e.g., Motif 2 support, line arrowheads,
window refresh control, editable outline fields)
· Dynamic library loading
· Improved CORBA/IIOP support
· Improved XML and XSLT class support
· JMQ support
End-Year Release
· Tentatively labeled "release 3.6" to be distributed as a free
product enhancement for customers under maintenance
· Scheduled for year end 2000
· Defining features
· Any Release 3.5 target features that were not included in 3.5
· Generation of EJB interfaces for R3 service objects
· Platform support improvements to track important operating system
and database vendor activity
· Target features
· COBOL record handling as part of the OS390 transaction adapter
· Improved runtime security
· Interface classes for access to Netscape Server 4.0 and possibly
other web servers
Longer Term Product Directions
1. TOOL code to Java code migration. Neither release 3.5 nor 3.6 will
contain an automated solution in this area. Technical differences between
TOOL and Java make a 100% automated conversion all but impossible. A
workable solution is likely to involve a combination of tools and services.
2. Common repository between the 4GL and Java products. The recently
devised Java Tools Strategy has necessitated a change in the technology base
for our Java products to make them compatible with both the iPlanet
Application Server and the Forté for Java Community Edition. This, in turn,
has complicated our original vision of a common repository to the point that
we will not embark on this project. Instead, we have elevated
interoperability a short-term priority. In addition, we plan to migrate the
Fusion process definition tools to Java, thereby enabling Fusion definitions
to be stored in a common repository with Java code and components.
3. Other long-term enhancements will be determined by additional
customer and market feedback. A major criterion for new functionality will
be enhancing the revenue generating ability of the product, thereby
fostering its long-term health in the marketplace.
As our products continue to evolve, the features and specifications
described in this document are subject to change without notice. Sun
Microsystems cannot guarantee the completion of any future products or
product features mentioned in this Statement of Direction. By signing
below, the receiving Company agrees that it has not relied on, is not
relying on and will not rely on the potential availability of any future Sun
product, functionality or feature in making any purchases from Sun.
Executed by the Receiving Company Executed by Sun
Microsystems, Inc.
Signature:________________________
Signature:________________________
Name:___________________________
Name:___________________________
(Please Print) (Please
Print)
Title:____________________________
Title:____________________________
Date:____________________________
Date:____________________________

This is what I got today:
Statement of Direction
Sun Microsystems, Inc.
Forté 4GL(tm) Product (formerly the Forté Application Environment)
Product Context
· Forté 4GL is an award-winning, proven product with many unique
advantages for building enterprise business systems that are distributed,
that involve the integration of existing business systems as well as new
functionality, and that target heterogeneous runtime environments.
· Forté 4GL is recognized by Gartner Group as the most successful
Enterprise Application Development Tool.
· The Sun Microsystems, Inc. (SMI) development tools group (formerly
Forté Software, Inc.) has a strong internal commitment to Forté 4GL. Forté
Fusion is written with, and is currently being enhanced with Forté 4GL.
· The SMI development tools group intends to actively enhance and
promote Forté 4GL for the indefinite future. The best opportunity for
attracting new customers is to leverage the ability of Forté 4GL to easily
build powerful shared business services (server components) that can be
accessed by non-Forté clients (e.g., browsers, Java clients) and that can
easily integrate with new and existing business systems.
· The product enhancement plan calls for continuing to issue
incremental releases approximately twice a year. To speed the release of new
functionality, new features will be included with "preview status." This
means that the overall release can support production deployments, but that
the features marked "preview" are certified for development and demos.
· The planned contents of the next two releases are indicated below.
Users should not expect any features other than those on the list. The
contents of subsequent releases will be determined approximately a year in
advance.
· SMI has retained the Forté field sales organization as an
independent unit whose primary product offerings are Forté 4GL and Forté
Fusion. Continued volume sales of Forté 4GL remain the foundation of our
business plan.
Mid-Year Release
· Tentatively labeled "release 3.5" to be distributed as a free
product enhancement for customers under maintenance
· Scheduled for Summer 2000
· Defining features
· Introspection (reflection) - the ability for an object to describe
itself at runtime
· Improved integration with applications developed using
Forté-for-Java Community Edition(tm) (formerly NetBeans)
· Platform support improvements to track important operating system
and database vendor activity
· Target features
· Display system enhancements (e.g., Motif 2 support, line arrowheads,
window refresh control, editable outline fields)
· Dynamic library loading
· Improved CORBA/IIOP support
· Improved XML and XSLT class support
· JMQ support
End-Year Release
· Tentatively labeled "release 3.6" to be distributed as a free
product enhancement for customers under maintenance
· Scheduled for year end 2000
· Defining features
· Any Release 3.5 target features that were not included in 3.5
· Generation of EJB interfaces for R3 service objects
· Platform support improvements to track important operating system
and database vendor activity
· Target features
· COBOL record handling as part of the OS390 transaction adapter
· Improved runtime security
· Interface classes for access to Netscape Server 4.0 and possibly
other web servers
Longer Term Product Directions
1. TOOL code to Java code migration. Neither release 3.5 nor 3.6 will
contain an automated solution in this area. Technical differences between
TOOL and Java make a 100% automated conversion all but impossible. A
workable solution is likely to involve a combination of tools and services.
2. Common repository between the 4GL and Java products. The recently
devised Java Tools Strategy has necessitated a change in the technology base
for our Java products to make them compatible with both the iPlanet
Application Server and the Forté for Java Community Edition. This, in turn,
has complicated our original vision of a common repository to the point that
we will not embark on this project. Instead, we have elevated
interoperability a short-term priority. In addition, we plan to migrate the
Fusion process definition tools to Java, thereby enabling Fusion definitions
to be stored in a common repository with Java code and components.
3. Other long-term enhancements will be determined by additional
customer and market feedback. A major criterion for new functionality will
be enhancing the revenue generating ability of the product, thereby
fostering its long-term health in the marketplace.
As our products continue to evolve, the features and specifications
described in this document are subject to change without notice. Sun
Microsystems cannot guarantee the completion of any future products or
product features mentioned in this Statement of Direction. By signing
below, the receiving Company agrees that it has not relied on, is not
relying on and will not rely on the potential availability of any future Sun
product, functionality or feature in making any purchases from Sun.
Executed by the Receiving Company Executed by Sun
Microsystems, Inc.
Signature:________________________
Signature:________________________
Name:___________________________
Name:___________________________
(Please Print) (Please
Print)
Title:____________________________
Title:____________________________
Date:____________________________
Date:____________________________

Re: (forte-users) Ok, what's the "secret" for setting serverside envi

Dear Robinson,
It seems to be that you have 2 ways of solving the problem:
1) restart forte after setting the environment variables
2) write a little application which sets the required variables, using
the task.part.OperatingSystem.SetEnv(name,value) method.
If you have to chage the variables rarely, then it`s easier to restart forte,
otherwise I would suggest to use the SetEnv function...
Best Regards,
Tamas Deak
"Robinson, Richard" wrote:
Subject says it all.
We have a bunch of environment variables that are used by the server side
objects. What I want to do is change the value of some of the variables
prior to running my application in Forte Development IDE (3.0.G.2). I've
tried to set the environment variables via NT's registry, but it appears
that at execution time the variables take on the value of whatever they are
for the node manager.
Most IDE's I've worked with before have a way to specify environment
variables right in the tool. Forte doesn't appear to have that capability -
say it ain't so!
Any clues?
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]
Tamas Deak
Lufthansa Systems Hungary
(forte developer)
2-6 Mazsa ter, Budapest, 1107, HUNGARY
(36-1) 4312 973
[email protected]
[email protected][email protected]-

Richard,
There is no way of changing the environment variable once the Node
Manager is up. You will have to shutdown the node manager and then restart
it to have the new environment variables take effect. Sorry, there is no
secret way of doing this that I know of.
But you can set the variables on you development machine and run you
application without distributing. This way the partition will be running in
your client machine and not the server.
Another way we have also got around this is by having a special
environment variable on the client side that opens a admin screen when you
run you application. This admin screen will allow you to change the
environment variables and then set them on the server partition. You will
have to do come coding on the server to make this happen but if you are
using a framework then it should be easy. We call this developer reconnect
facility. It only can be activated by the special client side environment
variable. I comes in very handy when we are development and want to change
the database on the server partition.
Hope this help.
ka
Kamran Amin
Framework, Inc.
303 South Broadway
Tarrytown, NY 10591
(914) 631-2322x121
[email protected]
http://www.frameworkinc.com/
-----Original Message-----
From: Robinson, Richard [mailto:[email protected]]
Sent: Thursday, November 04, 1999 7:23 AM
To: [email protected]
Subject: (forte-users) Ok, what's the "secret" for setting server side
environment varia bles when running in the Forte Development
Environment?
Subject says it all.
We have a bunch of environment variables that are used by the server side
objects. What I want to do is change the value of some of the variables
prior to running my application in Forte Development IDE (3.0.G.2). I've
tried to set the environment variables via NT's registry, but it appears
that at execution time the variables take on the value of whatever they are
for the node manager.
Most IDE's I've worked with before have a way to specify environment
variables right in the tool. Forte doesn't appear to have that capability -
say it ain't so!
Any clues?
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]

RE: (forte-users) Killing the Nones - solved

Thanks to all of you who helped ... this pex file works great.
Allan
-----Original Message-----
From: kelsey.petrychynsasktel.sk.ca [SMTP:kelsey.petrychynsasktel.sk.ca]
Sent: Thursday, August 24, 2000 9:51 AM
To: Pomeroy, Allan
Cc: kamranaminyahoo.com
Subject: Re: (forte-users) Killing the Nones
Try the code contained in this pex file.
We got it from someone in Forte quite a while ago and found that it worked
pretty good. I haven't used it for a long time since, and it was probably
written using an old version of Forte. However, it should still work, or
at
least you may find some salvageable code that can be "modernized" to what
ever
version you are using.
(See attached file: FtExecShutDown.pex)
PS
You would almost think that by version 3+ of a product Forte would have
nailed
down their empty and orphaned (defunct in UNIX) processes bugs. The
environment
manager should be able to auto-magically shut them down or at least keep
them
down to an acceptable number. But alas, we still find ourselves
occasionally
exceeding our finite server resources due to rouge processes doing
nothing.
Kelsey PetrychynSaskTel Technical Analyst
ITM - Technology Solutions - Distributed Computing
Tel (306) 777 - 4906, Fax (306) 359 - 0857
Internet:kelsey.petrychynSasktel.sk.ca
Quality is not job 1. It is the only job!
"Pomeroy, Allan" <Allan.PomeroyLibertyMutual.com> on 08/24/2000 07:09:16
AM
To: kamranaminyahoo.com
cc: (bcc: Kelsey Petrychyn/SaskTel/CA)
Subject: (forte-users) Killing the Nones
Venerable Forte Gurus,
Aside from using the Econsole, is there a way to kill the "None" ftexecs
that sometimes hang around after forte partitions are shut down?
In Econsole, if you view->node outline, then select the Forte Executor,
you
may see some running ftexecs with no application assigned -- they show up
as
"None". When I subsequently launch applications, I want them to start in
new ftexecs, not in the old "none"s, which have old command-line parms,
memory settings, etc.
Thanks!
Allan
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com
<< File: FtExecShutDown.pex >>

Try the code contained in this pex file.
We got it from someone in Forte quite a while ago and found that it worked
pretty good. I haven't used it for a long time since, and it was probably
written using an old version of Forte. However, it should still work, or at
least you may find some salvageable code that can be "modernized" to what ever
version you are using.
(See attached file: FtExecShutDown.pex)
PS
You would almost think that by version 3+ of a product Forte would have nailed
down their empty and orphaned (defunct in UNIX) processes bugs. The environment
manager should be able to auto-magically shut them down or at least keep them
down to an acceptable number. But alas, we still find ourselves occasionally
exceeding our finite server resources due to rouge processes doing nothing.
Kelsey PetrychynSaskTel Technical Analyst
ITM - Technology Solutions - Distributed Computing
Tel (306) 777 - 4906, Fax (306) 359 - 0857
Internet:kelsey.petrychynSasktel.sk.ca
Quality is not job 1. It is the only job!
"Pomeroy, Allan" <Allan.PomeroyLibertyMutual.com> on 08/24/2000 07:09:16 AM
To: kamranaminyahoo.com
cc: (bcc: Kelsey Petrychyn/SaskTel/CA)
Subject: (forte-users) Killing the Nones
Venerable Forte Gurus,
Aside from using the Econsole, is there a way to kill the "None" ftexecs
that sometimes hang around after forte partitions are shut down?
In Econsole, if you view->node outline, then select the Forte Executor, you
may see some running ftexecs with no application assigned -- they show up as
"None". When I subsequently launch applications, I want them to start in
new ftexecs, not in the old "none"s, which have old command-line parms,
memory settings, etc.
Thanks!
Allan
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

Forté Icon in the Window Title Bar.

Hi,
I would like to know if it is possible to change the Forté little
Icon in all windows of our application for our company logo.
Example:
<<...OLE_Obj...>> <<Forte.zip>>
Thank.
Allen Vachon
INFLUATEC Inc.
Programmer Analyst
(819)/(888) 595-1794
avachoninfluatec.com

No. The image will remain in memory until either the VI is closed or IMAQ Dispose.vi is called.
- If IMAQ WindClose is called, the display window will disappear, but the image in memory will be available in memory for further processing.
If you use IMAQ WindShow, you have the ability to get the status of the display window (showing or hidden).
- It also allow you to set if the display window is to show or hide.

Web for Forte - what is the right product?

We are using Web Enterprise on a new application and on another existing
Forte application.
Concerning our experiences on the new application:
1) Watch what version of Forte and WE you use. Earlier that 3.M.2 and WE
E.1, we experienced a page truncation bug (that Forte admitted was their
bug).
2) Upgrades between Forte versions have been difficult as each upgrade means
an upgrade to the WE pieces. The only way we have been successful in these
upgrades is by recreating the repository, creating the new HTTP/HTML
libraries/projects, and importing (in order) our projects. This is time
consuming. It would be nice if Forte did not force the WE upgrade when the
Forte version changes.
3) As of yet, we have not been able to get a load balanced Web Access SO to
work. The help desk has suggested using a higher port number range (from
1780 up to 6000) but we haven't tried this yet.
Concerning our experiences with the existing application conversion:
1) The GUI interface of a windows application and a browser application are
basically different. There are things that are easy in a std GUI that are
much more difficult with a browser. So, if using std HTML, typically the
application will behave somewhat differently.
2) We used JavaScript within our HTML to do some basic editing within the
browser. This was much easier than doing std HTML to Forte for every type
of edit. In fact, we even used Forte to dynamically generate JavaScript in
certain circumstances.
3) We did NOT use Java at all.
4) The Forte application we are converting is old (4+ yrs) and was not
designed in the ideal way. Much of the processing logic and sql is embedded
inside windows. My point is that if the architecture of the existing
application is 'good' (good separation of pure GUI functions from business
rules from db access), then moving to WE can be fairly easy. If every Forte
window operation calls some method rather than invoking inline code, then
that is a good step. If every window operation calls some external
(non-window) method, then that is even better. That makes the replacement
of the Forte GUI with a browser based GUI much easier.
5) We tested, very briefly, the Window Converter operations of WE. It did
seem to work but we really could not utilize this facility because of the
poor design of the Forte GUI. We would have been forced to re-write our
existing GUI to take advantage of this.
6) We are attempting to reuse what we can from the existing application but
we are also taking advantage of this rewrite to implement a cleaner
architecture within a newly developed framework.
Jerry Fatcheric
Verizon Wireless
Hi Forte Experts
We are developing an application in 'pure' Forte 4GL, but have now reachedthe point >where some 20 windows must also be used from a WWW interface,
both for dataentry and >lookup of info.
So what is the right product(s) to look for / buy? Forte for Java ,WebEnterprise, >WebEnterprise Designer or is the functionality already in
30M2 and all we need to do >is to open the documentation-kit...?
Suggestions or War-stories are welcomed...
thanks
jens chr /KAD Denmark

Adobe makes three products that could work here: Photoshop Elements, Lightroom and Photoshop. Other companies also make programs that will do these tasks.
You make it sound like this is a one-time need. If that's true, I would think that the Adobe products are overkill. In fact, to edit the photos you might want to look at freeware products like RawTherapee, and there are plenty of freeware slideshow applications.

(forte-users) Ok, what's the "secret" for setting serversideenvironmen

You can use EConsole, (or EScript I suppose) to change Server Environemt variables. The Forte documentation lead me to believe I could set them at the environment level. However, I've discovered I can only set/alter them for existing online partitions.
Just drill down to at least the 'Partition' level (this would cover any replicates under it), and chose the menu option Component -> SetEnvRemote. An Execute Command Dialog box comes up with a place to enter the Variable Name and the Value you want it to be.
This works great for installed apps that aren't going anywhere, but it's a bit harder for "running man" processes. You never know which Forte_Executor Active Partition you're gonna get. So sometimes you have to wait to see which one you grab, then change the variable there.
What I wish Forte would provide (at the Econsole level) is the ability to also query an environment variable to see it's current value! I've needed that before many times.

You can use EConsole, (or EScript I suppose) to change Server Environemt variables. The Forte documentation lead me to believe I could set them at the environment level. However, I've discovered I can only set/alter them for existing online partitions.
Just drill down to at least the 'Partition' level (this would cover any replicates under it), and chose the menu option Component -> SetEnvRemote. An Execute Command Dialog box comes up with a place to enter the Variable Name and the Value you want it to be.
This works great for installed apps that aren't going anywhere, but it's a bit harder for "running man" processes. You never know which Forte_Executor Active Partition you're gonna get. So sometimes you have to wait to see which one you grab, then change the variable there.
What I wish Forte would provide (at the Econsole level) is the ability to also query an environment variable to see it's current value! I've needed that before many times.

Re: The Forte Stopwatch

Similar Messages

Maybe you are looking for