Kbase P66378: Astra Partition Always Used in dynlaunch.i When Calling calltablett.p
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/9/2004 |
|
Status: Unverified
SYMPTOM(s):
Astra Partition Always Used in dynlaunch.i When Calling calltablett.p
The call to calltablett.p in dynlaunch.i always uses the AppServer partition, regardless of the partition name passed in the call to dynlaunch.i. Customer had defined the Astra partition as local whilst another partition was the remote appserver session. When passing a temp table to dynlaunch.i with the appserver partition defined, however, they found the performance to be very poor and debugging revealed the Astra partition was being used. When they changed the RUN statement in dynlaunch.i they found the correct partition was then used and a big performance gain.
CAUSE:
Wrong handle being used in the call to calltablett.p
FIX:
The basic code change required was to change:
RUN adm2/calltablett.p ON gshAstraAppServer
to
RUN adm2/calltablett.p ON hAppServer
as per the call to calltable.p