Thanks for your input Jeff.

I opted for the two separate integer variables. Not exactly the way I
wanted to do it but it works.

I'm (too) easy to please, I guess :-)

Problem solved (until next time).

Thanks,
Brian.

On Mon, 21 Feb 2005 21:50:59 -0800, Vance, Jeff H (Cupertino)
<[log in to unmask]> wrote:

>Unfortunately all CI integer variables are signed 32 bit entities.  You
>might be able to represent your number in a string variable.
>
>Jeff Vance, vCSY
>
>> The intrinsic HPCIPUTVAR will put an integer to the variable
>> table when you specify item number = 1.
>>
>> However, moving a PIC S9(18) COMP field (the longint field)
>> into an integer field (PIC S9(09) COMP) is causing the value
>> in the variable stored in the CI variable table to "look"
>> suspiciously incorrect.
>>
>> It certainly doesn't look correct because it contains the
>> same value every time I run the program.
>>
>> These double integers are supposed to represent "microseconds
>> since January 1, 1970" and so I think their value should be
>> changing every time I run the program.
>>
>> Do I need to split my PIC S9(18) COMP value up into two
>> separate PIC S9(09) COMP fields and then do two separate
>> calls to HPCIPUTVAR?
>>
>> I certainly don't like that idea at all. I would prefer to
>> store the entire longint_type into the variable table.
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *