Conference acadmy::tpas_notes

61.0. "Separate_Open or no Separate_Open?" by TROOA::BCAMERON (Bob Cameron, dtn 631-7431, Tea?) Thu Jan 26 1995 15:07

Hi Lois,

We have begun our testing of the interface to the TPAS_CALC_TRNSFR_PRC
module. Our intension is to use the TPAS$SEPARATE_OPEN logical, set
as "Y", as we plan to perform transfer price calculations on groups of
parts.


I have tried the TPAS_DEMOSITE.COB in a number of ways.

  1) With the logical TPAS$SEPARATE_OPEN defined as "N" and
     the TPAS_DEMOSITE.COB not performing the separate open.

  2) With the logical TPAS$SEPARATE_OPEN defined as "Y" and
     the TPAS_DEMOSITE.COB not performing the separate open.

  3) With the logical TPAS$SEPARATE_OPEN defined as "N" and
     a version of the TPAS_DEMOSITE.COB that performs the
     separate open.

  4) With the logical TPAS$SEPARATE_OPEN defined as "Y" and
     a version of the TPAS_DEMOSITE.COB that performs the
     separate open.


From these tests, it appears that ....

    A) I include the TPAS_OPEN_DB_SQL in the TPAS_DEMOSITE program, the
       time to open DB is encurred on the separate open.

    B) If I run the TPAS_DEMOSITE without the TPAS_OPEN_DB_SQL call, the
       open DB time is encurred when performing the first part # transaction.

However, in both cases, it appears that all subsequent transactions are
fast, and hence do not repeat the open DB. Also, In both cases, it does not
seem to matter how the logical TPAS$SEPARATE_OPEN is set.

From what I have learned, we likely do not need to worry about using
the separate open for groups of parts, as the TPAS_CALC_TRNSFR_PRC module
appears to have the smarts built in to only perform the DB open once. Is
this in-line with the lOGIC module code?

thanks, Bob C
    Canadian IM&T/Finance
    
    

Bob,

>> From what I have learned, we likely do not need to worry about using
>> the separate open for groups of parts, as the TPAS_CALC_TRNSFR_PRC module
>> appears to have the smarts built in to only perform the DB open once. Is
>> this in-line with the lOGIC module code?


You are correct in saying that TPAS_CALC_TRNSFR_PRC.COB open the database 
only once as long as the process is active. So the overhead of opening
the databasesonly occurs once no matter if you let TPAS open then or
your code open them.

The reason for allowing the separate open code is that applications which
interface with TPAS and use RDB as their databases, can open all the databases
at once. RDB has a problem with opening databases here and there, it wants
all the databases open at once.

Performance was not the reason for the separate open. So if your application
doesn't use RDB then let TPAS do the work - less coding for you.
    
Lois