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



Kelly,

Rather than using the Hierarchical File System APIs (which Write to Stream
File (QHFWRTSF) is part of), you should look to use the Integrated File
System APIs (like Write to Descriptor (write)).  The Integrated File System
APIs will provide a much stronger/wider base for your application to work
on.

I see that someone else has posted some sample code using the write API,
which hopefully will help you along.

Bruce




                      Kelly Cookson
                      <kc62301@yahoo.com        To:       
cobol400-l@midrange.com
                      >                         cc:
                      Sent by:                  Subject:  Re: COBOL output to 
XML file
                      cobol400-l-admin@m
                      idrange.com


                      07/12/2002 01:51
                      PM
                      Please respond to
                      cobol400-l





I just found the Write to Stream File API.
Thanks for the tip.

Kelly



--- Rick Klopfer <rklopfer@daytonprogress.com> wrote:
> --
> My initial suggestion is to use API's to do this.  I
> have read stream files on the IFS with API's so I am
> sure that they exist to write them as well.  The IBM
> Info Center would be the place to check.
>
>
> >>> kc62301@yahoo.com 07/11/02 02:00PM >>>
> I'm trying code a COBOL program that generates an
> XML
> file.
>
> The COBOL program WRITEs to a physical file or
> source
> file member, then I transfer the file to a PC text
> file.  I've used the Client Access Express transfer
> function, the copy to stream file (CPYTOSTMF)
> command
> and the copy to PC document (CPYTOPCD) command.  In
> each case, an end-of-file label is added to the text
> file. The end-of-file label makes the XML file
> ill-formed. (Deleting the end-of-file label with a
> text editor makes the XML file well-formed.)
>
> Can I WRITE directly to a PC text file from
> COBOL400?
> Or can I set up a translation table that does not
> add
> an end-of-file label to the PC text file?
>
> Thanks for any insights.
>
> Kelly
>
> __________________________________________________
> Do You Yahoo!?
> Sign up for SBC Yahoo! Dial - First Month Free
> http://sbc.yahoo.com
> _______________________________________________
> This is the COBOL Programming on the iSeries/AS400
> (COBOL400-L) mailing list
> To post a message email: COBOL400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit:
>
http://lists.midrange.com/cgi-bin/listinfo/cobol400-l
> or email: COBOL400-L-request@midrange.com
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/cobol400-l.
> --
> [ Converted text/html to text/plain ]
> My initial suggestion is to use API's to do this.  I
> have read stream files on
> the IFS with API's so I am sure that they exist to
> write them as well.  The
> IBM Info Center would be the place to check.
>
> >>> kc62301@yahoo.com 07/11/02 02:00PM >>>
> I'm trying code a COBOL program that generates an
> XML
> file.
> The COBOL program WRITEs to a physical file or
> source
> file member, then I transfer the file to a PC text
> file.  I've used the Client Access Express transfer
> function, the copy to stream file (CPYTOSTMF)
> command
> and the copy to PC document (CPYTOPCD) command.  In
> each case, an end-of-file label is added to the text
> file. The end-of-file label makes the XML file
> ill-formed. (Deleting the end-of-file label with a
> text editor makes the XML file well-formed.)
> Can I WRITE directly to a PC text file from
> COBOL400?
> Or can I set up a translation table that does not
> add
> an end-of-file label to the PC text file?
> Thanks for any insights.
> Kelly
> __________________________________________________
> Do You Yahoo!?
> Sign up for SBC Yahoo! Dial - First Month Free
> http://sbc.yahoo.com[1]
> _______________________________________________
> This is the COBOL Programming on the iSeries/AS400
> (COBOL400-L) mailing list
> To post a message email: COBOL400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit:
>
http://lists.midrange.com/cgi-bin/listinfo/cobol400-l[2]
> or email: COBOL400-L-request@midrange.com
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/cobol400-l.[3]
>
> ===References:===
>   1. http://sbc.yahoo.com
>   2.
>
http://lists.midrange.com/cgi-bin/listinfo/cobol400-l
>   3. 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@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit:
>
http://lists.midrange.com/cgi-bin/listinfo/cobol400-l
> or email: COBOL400-L-request@midrange.com
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/cobol400-l.
>


__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com
_______________________________________________
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing
list
To post a message email: COBOL400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/cobol400-l
or email: COBOL400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.








As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.