Re: CPYSPLF to Database File surprise

At 22:04 20/04/99 +0100, you wrote:
>Evan Harris <spanner@ihug.co.nz> wrote:
>He was working manually and "at some stage" had created the physical file.
>My guess would be that that was the first time he ran the CPYSPLF. He then
>deleted the spooled file, got confused and started over. Do you have a
>joblog or audit trace to show precisely what manual commands he entered? If
>not you should suspect human error every time rather than believe that the
>operating system has somehow rewritten itself. When someone tells me what
>they did I never, never, never take it at face value. Doesn't mean they're
>lying necessarily, just that humans are not very reliable.
>

Dave,

this was precisely my reaction. However when we did it again, it behaved
the same way, hence my post. Buck and a few others have clarified the
behaviour for me, I was just surprised, because "traditionally" I have
always expected to have to do a CPYSPLF to get printed output into a flat
file.

I've since checked the source and sure enough a PRINTER defined file; but
you were right - if the programmer hadn;t created the flat file manually we
would never have noticed it.

It just goes to show you learn something every day 

BTW thanks for the other responses.... I just thought it was a neat thing
for the 400 to do.. kinda smart <g>

Cheers
Evan Harris
+---
| 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
+---