|
And we had an application that used a link to OV/400 for a wordy text field. After the demise of OV/400 we added another field to the database that was variable length to process it. 5250 sucks for processing a 32,000 byte variable length field, but we got it done. Rob Berendt -- "All creatures will make merry... under pain of death." -Ming the Merciless (Flash Gordon) Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 12/18/2003 05:17 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Fax to Subject Re: Al Barsa on OV/400 and ptf's This is a relatively old story, and at some point or other, IBM slipped us V5R2 PTFs that would allow OV to run. Previously, RSTLICPGM would not restore it. This allowed a lot of customers to go to V5R2 and use newer hardware. You know, IBM went to a lot of pain in the late eighties to push OV/400, and when they were moderately successful. I had one customers with 600 pages of help text in OV. We moved them from OV to TextManagement/38! Some of the software vendors that were tied to OV, developed proprietary packages to move them to M$Word. I know that HTE has one. Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com Pat Barber <mboceanside@worl dnet.att.net> To Sent by: Midrange Systems Technical midrange-l-bounce Discussion s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> cc 12/18/2003 07:41 Subject PM Re: Al Barsa on OV/400 and ptf's Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> Could you expand on that a little bit about PTF's and allowing OV/400 to go to V5R2 ???? Is this an old story ??? I belive this is the first I have seen this mentioned... Al Barsa wrote: > Hi, > > First of all, PTFs were issued to allow you to load the last release of OV > onto V5R2. You need to change some system values to accomplish this, and > it will get deleted for every new release hereafter, and it's not > supported, but it is what it is. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.