×
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.
Ok, I found this link
(
http://archive.midrange.com/midrange-l/200008/msg00324.html) in the
archives; of specific note, it mentions to APIs: QSPGETF and QSPPUTF. Are
these APIs still valid and, if so, are they carried over into v61?
Thanks
Tom
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tom
Sent: Friday, October 23, 2009 3:46 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: CPYSPLF and AFPDS
OK, a bit more detail:
We have a report generated by 3rd-party software, from a big vendor with
lots of customers. We want to extract some of the text from the report and
generate a new report (using an overlay). To get the 3rd party vendor to
make a change is a big deal, costing lots of cash and taking at least a
month. As an 'independent' contractor, I can do it way faster and for a
whole lot less.
With *SCS files, I might CPYSPLF to copy it to a 133 record length file
(called 'SPOOLFILE'), write up a quickie program to build a new spoolfile,
printing what I need from the original and apply the overlay.
So... now I need to do this same process on an *AFPDS type of spoolfile.
Tom
midrange.com
