Skip to main content

9.3 how to have an in-component storage of a $collhandle

Author: ulrichmerkel@web.de (ulrich-merkel)

I'm using 9.3 and have to load huge volumes of data from the outside world into multitudes of entities.

To speed up processing, I want to wrap a lot of methods (fill_in_field) in Collection Operations so I have to work out the $collhandle only once and the code is identical.

Expl in PSEUDOCODE, thats why I use "-" in names.

if (whatsoever-most-complicated-action)

$my-coll-handle$ = $collhandle(ABC)

endif

And now looping through all kind of information (like CALLBACKs from UXMLREADER)

$my-coll-handle$->fill_in_field()

compare/next (A_PK_SURROGATE) from "INPUTA"

if ($result <= 0)

$my-coll-handle$->finalise_record()

endif

 

For this, I need a place to store this handle, either as a field in HEADER.USYS or as a component variable.

 

Doing this in 9.3, I am pushed to specify some "Classification" which browses through the component signatures.

Confusing, isn't it?

 

Has someone (perhaps from CPWR) the experience how to define collhandle field?

9.3 how to have an in-component storage of a $collhandle

Author: ulrichmerkel@web.de (ulrich-merkel)

I'm using 9.3 and have to load huge volumes of data from the outside world into multitudes of entities.

To speed up processing, I want to wrap a lot of methods (fill_in_field) in Collection Operations so I have to work out the $collhandle only once and the code is identical.

Expl in PSEUDOCODE, thats why I use "-" in names.

if (whatsoever-most-complicated-action)

$my-coll-handle$ = $collhandle(ABC)

endif

And now looping through all kind of information (like CALLBACKs from UXMLREADER)

$my-coll-handle$->fill_in_field()

compare/next (A_PK_SURROGATE) from "INPUTA"

if ($result <= 0)

$my-coll-handle$->finalise_record()

endif

 

For this, I need a place to store this handle, either as a field in HEADER.USYS or as a component variable.

 

Doing this in 9.3, I am pushed to specify some "Classification" which browses through the component signatures.

Confusing, isn't it?

 

Has someone (perhaps from CPWR) the experience how to define collhandle field?

Hi Uli,

I don't believe that the clasification field is mandatory, you should be able to leave this field blank and assign any handle to the variable of field.

Regards,

Mike


Author: Mike Taylor (michael.taylor@uniface.com)

9.3 how to have an in-component storage of a $collhandle

Author: ulrichmerkel@web.de (ulrich-merkel)

I'm using 9.3 and have to load huge volumes of data from the outside world into multitudes of entities.

To speed up processing, I want to wrap a lot of methods (fill_in_field) in Collection Operations so I have to work out the $collhandle only once and the code is identical.

Expl in PSEUDOCODE, thats why I use "-" in names.

if (whatsoever-most-complicated-action)

$my-coll-handle$ = $collhandle(ABC)

endif

And now looping through all kind of information (like CALLBACKs from UXMLREADER)

$my-coll-handle$->fill_in_field()

compare/next (A_PK_SURROGATE) from "INPUTA"

if ($result <= 0)

$my-coll-handle$->finalise_record()

endif

 

For this, I need a place to store this handle, either as a field in HEADER.USYS or as a component variable.

 

Doing this in 9.3, I am pushed to specify some "Classification" which browses through the component signatures.

Confusing, isn't it?

 

Has someone (perhaps from CPWR) the experience how to define collhandle field?

Hi Mike,

thank you very much for your input.

Because it is for a client, I don't want to risk a trial-and-error-experience for his developers.

Uli

 


Author: ulrich-merkel (ulrichmerkel@web.de)
Terms & ConditionsAccessibility statement