Highlighted
Absent Member.
Absent Member.
1550 views

Call Thread on HP-UX 11.31 BOE vs MCOE

[Migrated content. Thread originally posted on 20 March 2012]

I use a CALL THREAD statement (on a main processing program) to execute another program solely to accept a Cancel button so that one can terminate the main processing program at anytime by pressing the Cancel button! The above programs run on the following environments:
Server: HP-UX 11iv3 + AcuConnect 7.2
Client: Win XP/2003/2008/Vista/7 + AcuThinClient 7.2
Test 1: Install & run the processing program on HP-UX 11.31 BOE - it took 7seconds to complete the processing!
Test 2: Install & run the same processing program on HP-UX 11.31 MCOE - it took 0.2 seconds to complete the same processing!
Test 3: Remove the Call Thread from the processing program & run it on HP-UX 11.31 BOE - it took 0.2 seconds to complete the processing
Test 4: Remove the Call Thread from the processing program & run it on HP-UX 11.31 MCOE - it took 0.2 seconds to complete the processing

From the above test results, it shows that Call Thread doesn't work well on HP-UX 11.31 BOE!
Has anyone come across this problem? Any ways to make HP-UX 11.31 BOE to achieve the same processing speed like MCOE?
Alternatively, is there a better way to achieve the process termination feature besides using Call Thread?
Thanks.
0 Likes
2 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: Call Thread on HP-UX 11.31 BOE vs MCOE

As the same Acu software is running on the HP machines, I am not sure what tips to offer. You can start AcuConnect with a trace file. You can compare the two traces to see if there is anything different.
0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

RE: Call Thread on HP-UX 11.31 BOE vs MCOE

CALL THREAD is a perfectly acceptable method to provide the user the ability to interrupt or cancel a process.

The first thing that comes to mind is that the two environments may be using different Runtime configuration settings. To determine that, execute the application with a Runtime trace. That is, include “-lxe runtime.log” in the command line in the alias. You’ll have something like:

-lxe runtime.log programname

After program execution the runtime.log will contain all of the Runtime configuration settings. Compare the settings in both environments to see if they are picking up different Runtime configuration settings.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.