|
What is populating the user space to begin with? Is that one of your
processes? If so, keep track of the number of bytes written to the user
space and then use that same int value for writing to stdout.
Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/
On Tue, Dec 8, 2009 at 8:44 AM, Mike <koldark@xxxxxxxxx> wrote:
I have CR defined asin
D CR C const(X'25')
I have something coming out now, but it is cutting off most of the data
my user space.xsi:noNamespaceSchemaLocation="
This document was in one of the articles I found. I forgot the original
author.
Here is the beginning of the document:
<?xml version="1.0" encoding="UTF-8" ?>
<RequestforUICGroup SchemaVersionMajor="2008-2009" SchemaVersionMinor="1"
CollectionId="1" CollectionName="RequestforUIC"
SubmittingSystemVendor="Computer Management Technologies"
SubmittingSystemName="CIMS Student Management System"
SubmittingSystemVersion="SMS 0806" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
https://XXXX.state.XX.us/srsd/xmlschema/UICRequest/RequestforUIC2008-2009.xsd
">--
<RequestforUIC>
<SubmittingEntity>
Here is what gets delivered from the user space:
<?xml version="1
My Content-Length is 16 and I removed that line of code that sends that
number so this is what Apache is sending. The problem is determining the
length of the string in the user space. How do you determine that length?
Google is not being my friend here.
D p_UsrSpcData s *
--
Mike Wills
http://mikewills.info
P: (507) 933-0880 | Skype: koldark
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.
As an Amazon Associate we earn from qualifying purchases.
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.