× 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: Re: CPYSPLF to Database File surprise
  • From: pytel@xxxxxxxxxx
  • Date: Tue, 20 Apr 1999 16:35:33 -0500

Nothing unusual here - you can OVRDBF database file to printer file and
OVRPRTF file to database file, and it will work (with some limitations).

Best regards
    Alexey Pytel



Evan Harris <spanner@ihug.co.nz> on 04/20/99 02:44:20 PM

Please respond to MIDRANGE-L@midrange.com

To:   midrange-l@midrange.com
cc:    (bcc: Alexei Pytel/Rochester/IBM)
Subject:  CPYSPLF to Database File surprise





We have a number of programs that do this using CPYSPLF *LAST to get spool
file data into database flat files so we can send them to various users.

As a result of a job falling over (I know, it must be us, 'cause it never
happens anywhere else <g>) one of the programmers was running the tail end
of one of these copy things manually.

He rang me to ask about some CPYSPLF parameters (specifically why the
SPLFNBR(*LAST) wasn't working) and we started looking for the spool file
the program was supposed to have generated but we couldn't find it.

Eventually we found it *in* a database file with the same name as the spool
file was meant to have ! Formatting etc was exactly as the spool file would
have been.

He had created a physical file with the same name as the spool file and
RECL(132) at some stage to receive the CPYSPLF data and when he ran the
program that normally created the spool file it seems that OS/400 had "cut
out the middle man" and written the data directly to the database file.

We ran a couple of tests and the results appeared the same. I'm going to
look into it a bit further becasue it seems if the files are defined as
PRINTER in the RPG then some kind of unofficial override is taking place.
The output file created did have the same name as a printer file but it
still seems a little strange that it should do this.

We thought it was weird but useful, and I can't remember ever seeing
behaviour of this kind in the manuals, but thought I'd post the details
here in case anyone finds it handy.

I'm still mulling over the implications....

Cheers.
+---
| 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
+---



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