[Openroad-users] FW: Old OpenROAD User group emails

Wed Jan 31 04:10:40 EST 2007

Hi Kristine,

On the Google search page, you can click on the [Cached] button to see
the text of the original posting.
The list archives - and interactive web pages - are off line at the
moment.  We have some serious configuration work to finish as soon as I
get clear of this project.

Regards

Paul
OpenROAD List Admin -  having fun on a remote tropical island somewhere
in the barrier reef
ps. I wish
pps. Thanks Pete.

________________________________

	From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of Pete
Rabjohns
	Sent: Tuesday, 30 January 2007 8:01 PM
	To: International OpenROAD Users
	Subject: Re: [Openroad-users] FW: Old OpenROAD User group emails

   RE: [Openroad-users] Call System. 

From: Duplenne, Brigitte <Brigitte.Duplenne at ca.com
<mailto:Brigitte.Duplenne at ca.com> > 
To: <rob.mckenzie at rogers.com <mailto:rob.mckenzie at rogers.com> > 
CC: openroad-users at peerlessit.com <mailto:openroad-users at peerlessit.com>

Date: Feb 17 2004 - 6:15pm 

	Hi,

	There was indeed a problem with SP2 on UNIX only. 
	A fix has been made and a SFP for Solaris has been created and
we are waiting for the client to confirm the fix.
	Please open an issue so we can build a patch for the platform
you are using.

	For Windows the problem has indeed been reported but we have not
reproduced it.

	Regards,

	Brigitte

	Brigitte Duplenne
	Computer Associates
	Manager, L2 Support 
	Alameda, California
	+1 510 748 2684
	brigitte.duplenne at ca.com <mailto:brigitte.duplenne at ca.com> 

	-----Original Message-----
	From: openroad-users-bounces at peerlessit.com
<mailto:openroad-users-bounces at peerlessit.com> 
	[mailto:openroad-users-bounces at peerlessit.com
<mailto:openroad-users-bounces at peerlessit.com> ]On Behalf Of
	rob.mckenzie at rogers.com <mailto:rob.mckenzie at rogers.com> 
	Sent: Tuesday, February 17, 2004 6:10 AM
	To: Tondreau Jr., David L
	Cc: openroad-users at peerlessit.com
<mailto:openroad-users at peerlessit.com> 
	Subject: [Openroad-users] 

	David,

	The ProcessWait attribute was already suggested to me, and I
added code to explicitly set it to TRUE. However, I have no joy!!! The
call system still hands back control immediately. Another member of this
group has informed me that this is indeed a known problem, and that the
call system also does not handle certain special characters - in
particular the ">". Apparently there may be a level 2 patch available to
address this problem - are you aware of any such patch. I will open a
call with tech support to see what they can do.

	Rob

	Hello All,

	To be sure, is it possible that have you set the value of
	CurSession.ProcessWait to FALSE somewhere else in your
application? 
	The
	ProcessWait and ProcessWindow attributes were introduced in
OpenROAD 
	4.1
	and control whether or not a CALL SYSTEM command will wait for
the
	called program (ProcessWait) and whether or not it will show the

	command
	window (ProcessWindow).

	Recognize that because these attributes are on the CurSession
global,
	they apply to the entire application at runtime. Once it is set,
it
	applies everywhere in the runtime environment. This could change
the
	behavior of your application if a developer inserts the
statement 

	CurSession.ProcessWait = FALSE;

	somewhere in the application code that may or may not be
executed
	depending on user actions. Processes elsewhere in the
application that
	used to wait may or may not depending on the value of this
attribute at
	the time that the command is issued. I would recommend putting a
trace
	message before the offending code to determine the value of this
	attribute (its default value is TRUE). Better yet still is to
write a
	wrapper for these commands that allow the ProcessWait and
ProcessWindow
	attributes to be explicitly set for each command. For instance:

	Procedure CallSystem
	(
	Command = VARCHAR(2000) NOT NULL;
	ProcessWait = INTEGER WITH DEFAULT NULL;
	ProcessWindow = INTEGER WITH DEFAULT NULL;
	) =
	Declare
	CurProcessWait = INTEGER NOT NULL;
	CurProcessWindow = INTEGER NOT NULL;
	EndDeclare
	{
	CurProcessWait = CurSession.ProcessWait;
	CurProcessWindow = CurSession.ProcessWindow;

	CurSession.ProcessWait = 
	IFNULL(ProcessWait,CurSession.ProcessWait);

	CurSession.ProcessWindow =
	IFNULL(ProcessWindow,CurSession.ProcessWindow); 

	CurProcedure.Trace(Text=Command);
	CALL SYSTEM :Command;

	CurSession.ProcessWait = CurProcessWait;
	CurSession.ProcessWindow = CurProcessWindow; 
	}

	If you still continue to have problems, a reproducable test case
is
	almost a requirement.

	Regards,

	David

	David Tondreau
	Computer Associates
	david.tondreau at ca.com <mailto:david.tondreau at ca.com> 

	-----Original Message-----
	From: openroad-users-bounces at peerlessit.com
<mailto:openroad-users-bounces at peerlessit.com> 
	[mailto:openroad-users-bounces at peerlessit.com
<mailto:openroad-users-bounces at peerlessit.com> ] On Behalf Of Stephen 
	Ward
	Sent: Tuesday, February 17, 2004 5:29 AM
	To: rob.mckenzie at rogers.com <mailto:rob.mckenzie at rogers.com> 
	Cc: openroad-users at peerlessit.com
<mailto:openroad-users at peerlessit.com> 
	Subject: RE: [Openroad-users] Call System Problems

	We have experienced similar problems running OR4.1 patch 9471
(and
	above) on Windows 2000. It seems as if there is something about
the
	operating system that causes this sort of behaviour as certain
	installations of Windows 2000 do not cause the problem and
others do.
	The problem we have had is that it has not been possible to pin
this
	down to any single thing although I think we have come up with
an
	installation that works for us, which is fine in theory until we
	consider the number of machines that require a re-installation
of the
	operating system.

	I have taken this up with CA in the past who tell me that they
cannot
	re-create the problem. I wonder if they've done some
'optimization' the
	way threading works that ends up causing problems if everything
is not
	how it should be.

	One of my colleagues has discovered that if the command line is
first
	written to a batch file, which is then executed instead of
executing 
	the
	command line directly, the code waits for the batch file to
finish
	executing
	(?!?!)

	Steve Ward

	-----Original Message-----
	From: openroad-users-bounces at peerlessit.com
<mailto:openroad-users-bounces at peerlessit.com> 
	[mailto:openroad-users-bounces at peerlessit.com
<mailto:openroad-users-bounces at peerlessit.com> ] On Behalf Of
	rob.mckenzie at rogers.com <mailto:rob.mckenzie at rogers.com> 
	Sent: 16 February 2004 18:42
	To: openroad-users at peerlessit.com
<mailto:openroad-users at peerlessit.com> 
	Subject: [Openroad-users] 

	We are in the process of testing OpenRoad 4.1 on HP/UX 11.

	An application that runs fine under 3.5/02 is not working under 
	4.1/0302

	The problem is with the call system command.

	It appears that under 4.1 the "call system" command forks the
command,
	contrary to what the documentation says. Under 3.5 the following
works
	fine:

	system_buffer = 'copy_database_tables -dtaxi_d::wtis_tst1
	-uwtis_dba -scopy_tables -l';
	system_buffer = 'echo "' + system_buffer + '" >' + log_file_name
	+
	'; ' + system_buffer + ' >' + log_file_name;
	call system :system_buffer;

	Under 3.5 system_buffer is echoed into the log file, and then
the
	copy_database_tables program is executed, completes, and control
is
	returned to OpenRoad. Under 4.1, if I leave the echo statement
in the
	command, everything is echoed to the window I started OpenRoad
from, 
	and
	the program is not executed.
	If I take out the echo, and the quoted string after it, and
simply pass
	the program and params to call system, the program is executed,
but it
	is executed as a new process and control is immediately returned
to OR
	before the program completes.

	Has anyone else experienced this sort of behaviour in 4.1? Is
there
	something in HP/UX that could be set that could cause this to
happen.

	Any thoughts???

	Thanks for any help,
	Rob McKenzie
	Toronto Transit Commission

________________________________

	From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of Sidney Glenn
	Sent: 30 January 2007 08:28
	To: International OpenROAD Users
	Subject: [Openroad-users] FW: Old OpenROAD User group emails

	Hi Folks

	A colleague of mine is looking for any emails dealing with
ProcessWindow (attribute of SessionObject)

	Nothing turned up in my archives and Paul must still be on his
honeymoon [allegedly]. So if someone has them in their archive or could
point Kris in the right direction it would be appreciated

	Thanks in advance

	Cheers 

	Sidney Glenn 

	Premium Services 
	Ingres Australia 
	sidney.glenn at ingres.com <mailto:sidney.glenn at ingres.com>  
	http://www.ingres.com 

	+61 7 3289 6061 
	+61 401 101 916 

________________________________

	From: Seeto, Kristine [mailto:KRISTINE.SEETO at ca.com] 
	Sent: Tuesday, 30 January 2007 9:40 AM
	To: Sidney Glenn; Paul White
	Subject: RE: Old OpenROAD User group emails

	Hey Paul,

	Did a Google search and this is what came back...however, it's a
dead link.  

	[Openroad-users] Call System Problems
<http://www.peerlessit.com/pipermail/openroad-users/2004-February/000425
.html> 

The ProcessWait and ProcessWindow attributes were introduced in OpenROAD
4.1 and control whether or not a CALL SYSTEM command will wait for the
called ...
www.peerlessit.com/pipermail/openroad-users/2004-February/000425.html
<http://www.peerlessit.com/pipermail/openroad-users/2004-February/000425
.html>  

	If you could point me in the right direction to get the above
article, that'd be great.

	Thanks,

	Kristine

________________________________

	From: Sidney Glenn [mailto:Sidney.Glenn at ingres.com] 
	Sent: Tuesday, 30 January 2007 9:29 AM
	To: Paul White
	Cc: Seeto, Kristine
	Subject: Old OpenROAD User group emails

	Hi Paul

	I hope the new year finds you well

	Kristine has asked how best to access old OpenROAD emails. Kris
is looking for emails relating to

	ProcessWindow (attribute of SessionObject)

	I have looked through my archives and can't find anything

	Cheers 

	Sidney Glenn 

	Premium Services 
	Ingres Australia 
	sidney.glenn at ingres.com <mailto:sidney.glenn at ingres.com>  
	http://www.ingres.com 

	+61 7 3289 6061 
	+61 401 101 916 

________________________________

	From: Seeto, Kristine [mailto:KRISTINE.SEETO at ca.com] 
	Sent: Tuesday, 30 January 2007 9:18 AM
	To: Sidney Glenn
	Subject: 

	Hey Sid, 

	Do you know how I can access the 'old' openROAD user group
emails?  Or maybe if you could access it for me...can you do a search
for issues with ProcessWindow (attribute of SessionObject).

	Thanks, 

	Kris 

	Kristine Seeto
	CA
	Senior Consultant
	tel: +61 7 3367 7107
	fax: +61 7 3367 7010
	mobile: +61 411 028 245
	email: kristine.seeto at ca.com <mailto:kristine.seeto at ca.com>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://peerlessit.com/pipermail/openroad-users/attachments/20070131/b8941f12/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 116 bytes
Desc: image001.gif
Url : http://peerlessit.com/pipermail/openroad-users/attachments/20070131/b8941f12/attachment.gif 