× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks Nadir for response. We can not pass the timestamp in input field .
So I am passing the parameters as part of the input datastructure. So I
have same datastructure as defined in rpg program.

.

<struct name="t_Headquarters_Service">
<data length="9" name="headquarterNumber" precision="0"
type="packed" usage="inherit"/>
<data length="52" name="headquarterName" type="char"
usage="inherit"/>
<data length="52" name="headquarterAddressLine1" type="char"
usage="inherit"/>
<data length="52" name="headquarterAddressLine2" type="char"
usage="inherit"/>
<data length="52" name="headquarterAddressLine3" type="char"
usage="inherit"/>
<data length="30" name="headquarterCity" type="varchar"
usage="inherit"/>
<data length="2" name="headquarterState" type="char"
usage="inherit"/>
<data length="13" name="headquarterZipcode" type="char"
usage="inherit"/>
<data length="3" name="headquarterCountry" type="char"
usage="inherit"/>
<data length="5" name="headquarterTimeZone" type="char"
usage="inherit"/>
<data length="3" name="headquarterTelephoneCountryCode" type="char"
usage="inherit"/>
<data length="10" name="headquarterPhoneNumber" type="char"
usage="inherit"/>
<data length="10" name="headquarterFaxNumber" type="char"
usage="inherit"/>
<data length="102" name="headquarterEmail" type="char"
usage="inherit"/>
<data length="1" name="headquarterStatus" type="char"
usage="inherit"/>
<data dateformat="ISO" dateseparator="hyphen"
name="headquarterOpenDate" type="date" usage="inherit"/>
<data length="9" name="headquarterCreditLimit" precision="0"
type="packed" usage="inherit"/>
<data name="headquarterLastChangedDate" type="timestamp"
usage="inherit"/>
<data length="9" name="billToHeadquartersNumber" precision="0"
type="packed" usage="inherit"/>
<data length="9" name="contactCustomerHeadquartersNumber"
precision="0" type="packed" usage="inherit"/>
<data length="30" name="userIdLastUpdated" type="varchar"
usage="inherit"/>
<data length="4" name="idPk" precision="31" type="int"
usage="inherit"/>
*<data name="changedTimeStamp" type="timestamp" usage="inherit"/>*
</struct>

Thanks
Anshul


On Tue, Jun 25, 2019 at 5:24 PM Nadir Amra <amra@xxxxxxxxxx> wrote:

I am not sure why you are getting 2011-11-23-07.34.12. But it as far as
the fractional part IWS currently only supports millisecond precision.

Can you post how you are defining the timestamp field in the RPG code?




"WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx> wrote on 06/25/2019 03:11:17
PM:

From: anshul narang <narang.anshul@xxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)"
<web400@xxxxxxxxxxxxxxxxxx>
Date: 06/25/2019 03:11 PM
Subject: [EXTERNAL] [WEB400] IWS: Input Timestamp Precision issues
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>

HI All

I am having issues with timestamps in IWS. I am passing timestamp like
'2019-06-21T14:54:22.677325' and I am getting the
timestamp
in the Rpgle programs as
2011-11-23-07.34.12.123000.

I tried doing precisions as well in PCML.
I tried setting timezone in Server Properties file as well.
It didnt help . Any ideas?




--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.