Anonymous_User Absent Member.
Absent Member.
1286 views

GWTMSMP - getTimestamp

Does anyone know why the function "getTimestamp()" returns the "old" retention
timestamp value after resetting (switch '/clear' on NW) the retention timestamp via
GWTMSMP utility?

I'd like to reset the timestamps, but always get the "old" values, which have been
set via SOAP.
When resetting the timestamp via GWTMSTMP this utility return s success and shows the
"unknown" value on the console log; but verifying via SOAP, the function
getTimestamp() returns the "old" timestamp again...


Markus


Labels (1)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: GWTMSMP - getTimestamp

Markus Colorado wrote:
> Does anyone know why the function "getTimestamp()" returns the "old" retention
> timestamp value after resetting (switch '/clear' on NW) the retention timestamp via
> GWTMSMP utility?
>
> I'd like to reset the timestamps, but always get the "old" values, which have been
> set via SOAP.
> When resetting the timestamp via GWTMSTMP this utility return s success and shows the
> "unknown" value on the console log; but verifying via SOAP, the function
> getTimestamp() returns the "old" timestamp again...
>
>
> Markus
>
>

Can be cached in memory. Try bouncing the POA, and I'll bet you'll get
the new value.

You will also get the new value if you SET via soap.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: GWTMSMP - getTimestamp

Hi Michael,

Caching might be the reason, but what do you mean with "..try bouncing the POA.."? -
Restart?
Setting via soap does definitely work, but not really an option for testing purposes
at the customer side ;-))


Thanks,
Markus



"Michael Bell" <mikebell90@no-mx.forums.novell.com> schrieb im Newsbeitrag
news:YalHl.3518$s8.525@kovat.provo.novell.com...
> Markus Colorado wrote:
>> Does anyone know why the function "getTimestamp()" returns the "old" retention
>> timestamp value after resetting (switch '/clear' on NW) the retention timestamp
>> via GWTMSMP utility?
>>
>> I'd like to reset the timestamps, but always get the "old" values, which have been
>> set via SOAP.
>> When resetting the timestamp via GWTMSTMP this utility return s success and shows
>> the "unknown" value on the console log; but verifying via SOAP, the function
>> getTimestamp() returns the "old" timestamp again...
>>
>>
>> Markus
>>
>>

> Can be cached in memory. Try bouncing the POA, and I'll bet you'll get the new
> value.
>
> You will also get the new value if you SET via soap.
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: GWTMSMP - getTimestamp

Markus Colorado wrote:
> Hi Michael,
>
> Caching might be the reason, but what do you mean with "..try bouncing the POA.."? -
> Restart?
> Setting via soap does definitely work, but not really an option for testing purposes
> at the customer side ;-))
>
>
> Thanks,
> Markus
>
>
>
> "Michael Bell" <mikebell90@no-mx.forums.novell.com> schrieb im Newsbeitrag
> news:YalHl.3518$s8.525@kovat.provo.novell.com...
>> Markus Colorado wrote:
>>> Does anyone know why the function "getTimestamp()" returns the "old" retention
>>> timestamp value after resetting (switch '/clear' on NW) the retention timestamp
>>> via GWTMSMP utility?
>>>
>>> I'd like to reset the timestamps, but always get the "old" values, which have been
>>> set via SOAP.
>>> When resetting the timestamp via GWTMSTMP this utility return s success and shows
>>> the "unknown" value on the console log; but verifying via SOAP, the function
>>> getTimestamp() returns the "old" timestamp again...
>>>
>>>
>>> Markus
>>>
>>>

>> Can be cached in memory. Try bouncing the POA, and I'll bet you'll get the new
>> value.
>>
>> You will also get the new value if you SET via soap.
>>

>
>

Just for testing Markus. Jeez

If it is the case, you write your own gwtmstmp utility using SOAP - not
a difficult thing.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: GWTMSMP - getTimestamp


"Michael Bell" <mikebell90@no-mx.forums.novell.com> schrieb im Newsbeitrag
news:l_mHl.3560$s8.2487@kovat.provo.novell.com...
> Markus Colorado wrote:
>> Hi Michael,
>>
>> Caching might be the reason, but what do you mean with "..try bouncing the
>> POA.."? - Restart?
>> Setting via soap does definitely work, but not really an option for testing
>> purposes at the customer side ;-))
>>
>>
>> Thanks,
>> Markus
>>
>>
>>
>> "Michael Bell" <mikebell90@no-mx.forums.novell.com> schrieb im Newsbeitrag
>> news:YalHl.3518$s8.525@kovat.provo.novell.com...
>>> Markus Colorado wrote:
>>>> Does anyone know why the function "getTimestamp()" returns the "old" retention
>>>> timestamp value after resetting (switch '/clear' on NW) the retention timestamp
>>>> via GWTMSMP utility?
>>>>
>>>> I'd like to reset the timestamps, but always get the "old" values, which have
>>>> been set via SOAP.
>>>> When resetting the timestamp via GWTMSTMP this utility return s success and
>>>> shows the "unknown" value on the console log; but verifying via SOAP, the
>>>> function getTimestamp() returns the "old" timestamp again...
>>>>
>>>>
>>>> Markus
>>>>
>>>>
>>> Can be cached in memory. Try bouncing the POA, and I'll bet you'll get the new
>>> value.
>>>
>>> You will also get the new value if you SET via soap.
>>>

>>
>>

> Just for testing Markus. Jeez
>
> If it is the case, you write your own gwtmstmp utility using SOAP - not a difficult
> thing.


This own written soap gwtmstmp utility wouldn't be the prob, but do we really have to
"reinvent the wheel"? I thought there might me a straight way forcing the po to
update the timestamp (as after a soap "set").

Thanks for yr help!
Markus


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.