Re: CPYSPLF

[David & Eileen Keck <bstars@xxxxxxxxxxxxx>]

The effect is to copy the spool file entry to a database member (though
special attribute characters, overprinting, etc are probably not retained).
See other parameters to assess whether data is being added or replaced in
the file.  The CPYF command has a *PRINT option enabling you to once again
create a spool file from the database file, so yes it can be printed.  You
could also write a program to read and print the records.  If you are
looking at code in your system and wondering why it's there, consider that
database members are much easier to prorammatically manage than spool files.
Also, it's my understanding that most types of backup ignore spool files.
If the underlying data changes over time and the need to reprint arises, the
file you have will be useful.
-Dave K.
----- Original Message -----
From: "Dare" <oludare@ix.netcom.com>
To: <MIDRANGE-L@midrange.com>
Sent: Thursday, December 13, 2001 5:11 PM
Subject: CPYSPLF


> This is a multi-part message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> Guys,
>
> What is the consequence of the following command on V4R5M0.  SPLFOUTF is a
physical file (data type) and record lenght is 144.  Will I be able to print
my reports from SPLFOUTF? How?
>
>
>
> CPYSPLF FILE(QPRTSPLF) TOFILE(SPLFOUTF)
>
> --
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>