× 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: OV/400 to PF
  • From: rob@xxxxxxxxx
  • Date: Thu, 8 Mar 2001 17:12:21 -0500


We have an application which basically used OV/400 as an early version of
variable length fields for entering comments.  There would be a field in
the main PF which would contain the document name in OV/400.  To print the
main doc was a masterpiece of merging.  Now I have just under 2,000
documents I need to convert into data into a PF.  I've looked at CPYFRMPCD
and CPYFRMIMPF and I am meeting with abysmal failure.

Then I tried PRTDOC into an output file.  This looks nothing like the
printout.  You get scads of stuff where I have no idea where it came from.

My next technique will be to PRTDOC into a spool file.  Copy the spool file
to a disk file.  Take the disk file and append that onto another DB2 file
and construct a key back to the original file.  Now if I can only get that
dang cheshire cat to stop disappearing and reappearing...

Any better suggestions?

Rob Berendt

==================
Remember the Cole!

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.