RE: CPYSPLF to Database File surprise -- MIDRANGE-L

I just tried a test program using a print file that didn't exist and a flat
file by the same name.

The program compiled, (I wondered about that), and then wrote its output
(using O specs) to the flat file.  There's got to be a use for this.  I
haven't had time to try overprinting yet.

Don't pick on me for using O specs.   

-----Original Message-----
From: Evan Harris [mailto:spanner@ihug.co.nz]
Sent: Tuesday, April 20, 1999 12:44 PM
To: midrange-l@midrange.com
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
+---