| Author |
Message
|
| praveenchhangani |
 Posted: Mon Jul 21, 2003 11:53 am Post subject: [SOLVED]Workflow confused about NOP.sh vs. NOP.dll |
 |
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
Folks,
I have a strange problem at hand. For some reason, my process model which happens to be running on my aix server keeps trying to load the windows NT nop.dll eventhough, under the definition of the program NOP, I have both the NOP.dll and the NOP.sh defined.
| Code: |
| The error it displays is "FMC32001E The Dynamic Link Library d:\upes\nop.dll could not be loaded ." |
I have verified that the NOP.sh is in the directory on the aix server where it is supposed to be. So why is workflow getting confused with the NT stuff?
any help is appreciated.
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
 |
| praveenchhangani |
| Posted: Mon Jul 21, 2003 11:56 am Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
Correction to my subject:
NOP.sh vs. NOP.dll
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Jul 21, 2003 12:41 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I just tested what you were doing and I dont have any problem. Can you post your FDL?
_________________
-Ratan |
|
| Back to top |
|
|
| praveenchhangani |
| Posted: Mon Jul 21, 2003 12:47 pm Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
Here is the NOP that is being referenced:
| Code: |
PROGRAM 'NOP'
STRUCTURES_FROM_ACTIVITY
UNATTENDED
AIX EXE PATH_AND_FILENAME "/workflow/programs/nop.sh"
WORKING_DIRECTORY "/workflow/programs"
INHERIT ENVIRONMENT
DO NOT RUN_IN_XTERM
WINNT DLL PATH_AND_FILENAME "d:\upes\nop.dll"
ENTRY_POINT "NOP"
KEEP_LOADED
FENCED_MODE
END 'NOP' |
And here is the program activity that is choking due to the NOP perhaps?
| Code: |
PROGRAM_ACTIVITY 'CollectActivity' ( 'Input', 'Output' )
DESCRIPTION "Loan Number %LoanNumber%"
START AUTOMATIC WHEN AT_LEAST_ONE CONNECTOR TRUE
EXIT AUTOMATIC WHEN "CLReceived = ""True""" XPOS -645 YPOS 1095
LAYOUT XPOS -620 YPOS 1220
NAME_POSITION XPOS -642 YPOS 1132
PRIORITY DEFINED_IN INPUT_CONTAINER
DONE_BY PERSON 'ADMIN'
CHECKOUT_POSSIBLE
PROGRAM 'NOP'
SYNCHRONIZATION NESTED
END 'CollectActivity' |
I am not sure why workflow is trying to invoke the windows dll instead of the AIX nop.sh. Could someone perhaps explain how this works.
I understand the fact that in buildtime, under the NT tab, one specifies the .dll file whereas on the AIX tab, he/she would specify the .sh file. Where I would like more detail is on how workflow is able to understand which is which and which one to invoke thereafter.
Getting a deeper understanding on that might lead to the solution of the above.
Thanks
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Jul 21, 2003 1:05 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
This is why I believe it is not working for you.
you are probably trying to run the activity on a windows machine. If you are starting the process from a RTC which is on a Windows machine, the program will try to execute on a Windows machine.
You can get around this by assigning the Activity to a user XYZ and starting a PEA on the server under his ID.
_________________
-Ratan |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Jul 21, 2003 1:55 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
| praveenchhangani wrote: |
I am not sure why workflow is trying to invoke the windows dll instead of the AIX nop.sh. Could someone perhaps explain how this works.
I understand the fact that in buildtime, under the NT tab, one specifies the .dll file whereas on the AIX tab, he/she would specify the .sh file. Where I would like more detail is on how workflow is able to understand which is which and which one to invoke thereafter. |
Praveen:
As Ratan is indicating, MQWF decides which of the Platforms to use based on where the request is originating. Thus if you invoke from a client running on AIX it uses the AIX executable, and from a client on NT it uses the NT executable etc. Realize here that of I am speaking of a FAT client.
If you are not trying to run this from an NT box as Ratan is thinking, please post more information, as what you are indicating would be pretty strange.
Regards
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| praveenchhangani |
| Posted: Tue Jul 22, 2003 6:56 am Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
You were both correct about this. It was indeed being invoked from a windows application which was causing the use of the NOP.dll vs. the NOP.sh. Thanks a bunch folks!
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
|
|
|
