RE: CPYSPLF

OK, So why do you go from COBOL to a spooled file and then to a PF
instead of writing the proper PF from the COBOL and never making the
spooled file?

Brad 

-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Kelly Cookson
Sent: Thursday, June 23, 2005 8:57 AM
To: COBOL Programming on the iSeries/AS400
Subject: RE: [COBOL400-L] CPYSPLF

I assume the PF to which you are copying them is a flat file. Would it
be possible to put a marker in the blank lines of the spooled file so
they aren't really blank (e.g., put an asterisk at the beginning or end
of each blank line, or a period at the beginning or end of each line).
It's not a great solution, but if you can't find anything better...

Also, why not just write output to the PF directly? Do you really need
the spooled file?

Thanks,
Kelly

> -----Original Message-----
> From: cobol400-l-bounces@xxxxxxxxxxxx
[SMTP:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Good, Brad
> Sent: Thursday, June 23, 2005 7:53 AM
> To:   COBOL Programming on the iSeries/AS400
> Subject:      RE: [COBOL400-L] CPYSPLF
> 
> So to clarify, you need the blank lines to stay, but CPYSPLF is 
> dropping them out.  Right?
> 
> Brad
> 
>  
> 
> -----Original Message-----
> From: cobol400-l-bounces@xxxxxxxxxxxx
> [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of 
> Santhamurthy_Veeraraghavan
> Sent: Thursday, June 23, 2005 4:41 AM
> To: cobol400-l@xxxxxxxxxxxx
> Subject: [COBOL400-L] CPYSPLF
> 
> Hi,
> 
> Request you to kindly help me with the following query.
> 
> I have a program which generates a spool file with some data. The data

> in the spool file is in a way that there are blank lines between data.
> In this scenario, the spool file has to be copied to a PF, since the 
> PF has to be FTPed.  Question is when CPYSPLF command is used to copy 
> spool file data to PF, the blank lines are omitted and are not seen in
the PF.
> Please let me know if there is any solution as this is an automated 
> process.
> 
> Regards,
> Santha
> 
> 
> DISCLAIMER:
> This email (including any attachments) is intended for the sole use of

> the intended recipient/s and may contain material that is CONFIDENTIAL

> AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or 
> copying or distribution or forwarding of any or all of the contents in

> this message is STRICTLY PROHIBITED. If you are not the intended 
> recipient, please contact the sender by email and delete all copies; 
> your cooperation in this regard is appreciated.
> 
> _______________________________________________
> This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) 
> mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To 
> subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
> or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take 
> a moment to review the archives at
http://archive.midrange.com/cobol400-l.
> 
> 
> 
> 
> _______________________________________________
> This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) 
> mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To 
> subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
> or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take 
> a moment to review the archives at 
> http://archive.midrange.com/cobol400-l.
> 
_______________________________________________
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing
list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/cobol400-l.