This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

pcli list export to xml

No problem with the command as such, but what are the date formats? Cannot find an explanation in PCLI users guide, i.e. the long ugly numbers in red below? 

<VersionedFile EntityPath="/Proj/somecode.cbl" Name="somecode.cbl" ArchivePath="D:\Somepath\Proj\archives\Proj\somecode.cbl-arc" ArchiveOwner="johndoe" CreateTime="1179299264000" LockCount="0" RevisionCount="15" WorkPath="." WorkPathNamespace="0">
<WorkfileDescription>init
</WorkfileDescription>
<Revision EntityPath="/Proj/somecode.cbl/1.14" Name="1.14" Author="janedoe" LockCount="0" ModificationDate="1602767058000" CheckedInDate="1603107676000">
<ChangeDescription>Maskinell &#x00e4;ndring av CALL_DML, Task 154811
</ChangeDescription>
</Revision>

Probably makes sense to someone, but an explanation in the documentation would have been nice.

 

/Robert

  • Verified Answer

    +1
    So this is probably epoch with milliseconds tucked on at the end. Really useful since it's always zero. But running the list command without xml-format seem to back this up, eg ModificationDate is 1602767058000 divided by 1000 and converted gives 2020-10-15 15:04 which match "ArchiveRevision:ModificationDate=Thu Oct 15 15:04:18 CEST 2020" from list without -fx.

    so I answered my own question - nice.
  • 0   in reply to 

    Hi Robert,

    I tried replying last week, but the old community site went offline just at that time :-)

    Your observations are correct. The time is expressed in milliseconds because that is the standard for the Time object Java uses, which is the architecture PCLI is based on.

    Let me know if you have any follow-up questions.

    Kind regards,

    - Richard.

  • 0 in reply to   

    Hi Richard,

    This seems to have been sent to me in error.

    Thanks,

    Phil