Comment on the output of the QSYS2/SYSCOLUMNS view -- MIDRANGE-L

× 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.

Subject: Comment on the output of the QSYS2/SYSCOLUMNS view
From: x y <xy6581@xxxxxxxxx>
Date: Fri, 15 Sep 2023 16:49:52 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On V7R5, the output shows a date data type field has a length of 4 (which
is the actual size of the binary field on the persistent storage device)
and a timestamp data type column has a length of 10 (also the actual binary
size). I haven't checked a time data type yet.

AFAIK this is not consistent with DSPFD/DSPFFD and API output. Is this
variation by design or is it a miss?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Comment on the output of the QSYS2/SYSCOLUMNS view , John Yeung
Re: Comment on the output of the QSYS2/SYSCOLUMNS view , Vern Hamberg

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.