RE: variable length field used in DSPF -- MIDRANGE-L

Subject: RE: variable length field used in DSPF
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Fri, 19 May 2017 15:27:03 +0000
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

"no one has a twinax terminal anymore"

I wish that were true.

-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Friday, May 19, 2017 10:10 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: variable length field used in DSPF

Back when we had OV/400 we handled really long fields by not even storing them in the database but storing them instead into "documents" and executing EDTDOC to maintain them. Document name was based off of the key.

Since no one has a twinax terminal anymore perhaps you could pop up an alternative interface, like hotspotting a url or some such thing?

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: variable length field used in DSPF , Douglas Dunn

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.