ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » WORK FLOW ON AIX

Post new topic  Reply to topic Goto page Previous  1, 2
 WORK FLOW ON AIX « View previous topic :: View next topic » 
Author Message
mahek
PostPosted: Thu Jan 06, 2005 1:40 pm    Post subject: Reply with quote

Voyager

Joined: 10 Sep 2004
Posts: 87

Hi jamac,
According to the doc we have
4)Add a Data Default Connector to the Empty Activity and i am using that and it is working for XP AND 2003

Modeling with Buildtime
To implement an Empty Activity, perform the following modeling steps:
1. Model a dummy UPES for an Empty Activity
2. Model an Empty Activity program
3. Create an Empty Activity as Program Activity within your process model
4. Add a Data Default Connector to the Empty Activity
5. Define Transition Conditions on the outgoing Control Connectors
Back to top
View user's profile Send private message
jmac
PostPosted: Thu Jan 06, 2005 1:48 pm    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

I dont know what document you are looking at... but have a look at this one:

http://www-1.ibm.com/support/docview.wss?rs=795&context=SW920&uid=swg21078709

See slide 23... YOU MUST HAVE a default control connector.

That's what I am talking about.
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
mahek
PostPosted: Thu Jan 06, 2005 2:22 pm    Post subject: Reply with quote

Voyager

Joined: 10 Sep 2004
Posts: 87

Hi jamac,
I was not abel to my posting so i posted 3 times .
yes we need this default control connector if any of the conditions are not meet but here i am giving yes yes for both the b and c .
YOU are right but the case which you are telling when both b and c are no then it uses the default control connector then if there is no default connector then there will be a problem
Back to top
View user's profile Send private message
hos
PostPosted: Mon Jan 10, 2005 2:18 am    Post subject: Reply with quote

Chevalier

Joined: 03 Feb 2002
Posts: 470

Hi,

the documentation says that you should select asynchronous synchronization for NOOP program activity. However your setting is
Quote:
SYNCHRONIZATION CHAINED
. This most probably results in the unexpected behaviour you are seeing.
Back to top
View user's profile Send private message
Andy
PostPosted: Mon Jan 10, 2005 3:49 am    Post subject: Reply with quote

Centurion

Joined: 14 May 2003
Posts: 122

I remember there is a bug in buildtime and sychronous/asynchronous setting changes while doing certain steps.

Dont remember exact steps.
_________________
Andy
Back to top
View user's profile Send private message
sac
PostPosted: Mon Jan 10, 2005 8:16 am    Post subject: Reply with quote

Apprentice

Joined: 10 Feb 2003
Posts: 44

Yea, there is this problem with NoOp activity. The observation that i had for this was that whenever you change any property of NoOp activity,say you change the data container of the activity, then this Asynch property changes to Synch. So need to careful about this.
Back to top
View user's profile Send private message
seamonsterboy
PostPosted: Fri Jan 14, 2005 12:28 am    Post subject: Reply with quote

Newbie

Joined: 06 Jan 2004
Posts: 5
Location: Los Angeles

We see the same behaviour described in the original post (although we are using 3.4.6 on AIX). Our NOOP activities also never go into error state but do hang. We do have default data connectors on all of them.

According to the IBM doc included a couple of posts ago (page 21) "SYNCHRONIZATION CHAINED /* mode asynchronous */".

Does anyone have an update on this? Thanks.
Back to top
View user's profile Send private message Visit poster's website
francoisvdm
PostPosted: Fri Jan 28, 2005 1:22 am    Post subject: PDF corrupted? Reply with quote

Partisan

Joined: 09 Aug 2001
Posts: 332

The download file from
http://www-1.ibm.com/support/docview.wss?rs=795&context=SW920&uid=swg21078709

is arriving on my side corrupted! Anybody that can forward me a verified copy? Thanks.
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.

Francois van der Merwe
Back to top
View user's profile Send private message Send e-mail
jmac
PostPosted: Fri Jan 28, 2005 5:35 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

Done
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
seamonsterboy
PostPosted: Fri Jan 28, 2005 8:47 am    Post subject: IBM Sent us a Patch Reply with quote

Newbie

Joined: 06 Jan 2004
Posts: 5
Location: Los Angeles

To follow up on the original problem in this thread - IBM sent us a patch for MQWF that fixed this problem on AIX.
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » WORK FLOW ON AIX
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.