13 replies to this topic

[Rob Fantini]

Hello,
I've looked thru most of the docs and can't find howto
use Wide Communication Variables. [@!COM1 thru @!COM10] .

Could someone refer me to the documentation and or give
and example of howto use wide comm variables?

Rob F.

[Larry Siemer]

Hi Rob,

My experience with Wide Comm Variables is limited but this
has worked for me!

@!COM9 = WIDEVAL($_TMP)
$_TMP = ALPHA(@!COM9)

Larry

[Rob Fantini]

Larry,
That works! Thanks!

Once again the value of this forum is proved.


Rob

[George Macken]

Hi

I'm familiar with how the @$COM & @#COM SYSTEM VARIABLES are used (mis-used) in developinig PRO-IV application.

I'm now requeted to implement a modification - a Switch/Mode - per operator running the system - as the system already makes extensive usage of @$COM[1-10] & @#COM[1-10] - I'm thinking of using one of the @!COM VARIABLES for this - In Prototype sofar it seems to work OK for string/toggling an Alpha Value -

Anyone out there had any bad experience of using Wide Comm Variables ?

Thanks

George

[Joseph Bove]

George,

I don't know if this is still an issue or if it has been resolved. When we first started using @!COM's, if you had logic like this:

@!COM1 = WIDEVAL('')
$STRING = ALPHAVAL(@!COM1)

The results were completely random.

We got around this by changing our codes as follows:

@!COM1 = WIDEVAL(' ')
$STRING = ALPHAVAL(@!COM1)

Other than that, @!COM's have been a helpful addition. Of course, in a perfect world, nearly everything would be developed with global functions and the COMs would have little to no use...

Regards,

Joseph

[George Macken]

Thanks Joseph

I had noticed that when/where the @SYSLOOK shows no values in the Wide Variables that when I did UMSG of the ALPHA(@!COM[9-8]) that spurious values were echo'd back.

I therefore am no checking for '' (null)

I'm using the Value as follows:

$user_value = ALPHA(@!COM[n])
IF $user_value # $expected_value1, $expected_value2 THEN
$user_value # $expected_value_default
ENDIF

I then allow toggle of $user_value based on a Button

then set up COMM variable for future usage thru system

@!COM[n] = WIDEVAL($user_value)

seems to be working OK

tnks

George

[Phil]

Of course another way of by-passing comm variables is to have a system wide, terminal driven file that could hold as much or as little as you want.

[Joseph Bove]

Phil,

That's a good approach as well.

Although COM variables have a purpose, I was always chagrined that they couldn't be given dynamic names and thus by global variables.

Having to read code that references @$COM7 make maintenance more challenging. It would have been great to have been to able dynamically set and use variables like:

@$CLIENT
@#START_DATE
@#END_DATE

etc.

Although a variety of solutions exist for this, they all include a degree overhead for implementing.

My two cents anyway.

Regards,

Joseph

[George Macken]

Tnks all

I had a typo in posting above

$user_value = ALPHA(@!COM[n])
IF $user_value # $expected_value1, $expected_value2 THEN
$user_value = $expected_value_default
ENDIF

I then allow toggle of $user_value between $expected_value1, $expected_value2 based on a Button

then set up COMM variable for future usage thru system

@!COM[n] = WIDEVAL($user_value)

=====
I agree with using terminal/operator keyed file and this is


The value I'm using/storing is of even length


I've done further testing and usage and its seems to 100% meet the requirements


tnks

George

[Chris Mackenzie]

=====
I agree with using terminal/operator keyed file and this is

What for? No need to waste those bytes.

MKY files are unique to the process.

[George Macken]

my mind and keyboard are not always on the same wavelenght

I agree with using terminal/operator keyed file and .... it is HOW I'd normally pass variables - however what
I'm looking todo here is have a simple value present per operator and COMM variables are ideal for this. Sometimes when working remote form the client site making file changes, new fields etc., is not always the easiest solution to implement on an ORACLE DB


MKY is TLA for ?


tnks

George

[Chris Mackenzie]

MKY is an ABBREVIATION for Memory keyed file, the terminfo
and operator are not required.

You can have a global_function/logic
to return indivual fields from your parameter record as required.

e.g. :

#SESSIONID = GETSESSPARM('SESSIONID')

[Tony Waszkiewicz]

Don't forget that there is an ovehead in calling a global function.
If you are doing this in a heavy batch update the performance may become unacceptable

regards