How to handle string data > 32767 bytes, keyed data queue access, how to store login credentials

String data > 32767 bytes:
I'm working a web service that returns an XML document. What would be
the preferred way to return a document that is larger than 32767 bytes?
Is there a magical way to plug a stream writer into a clob or something
similar? I think I can work around it this time, but I'm sure it will
become an issue at some point. I'm interfacing with an IIS web site, so
I need something that's not totally hostile to Windows.

Keyed data queue:
I uncovered another secret (I guess) today. In order to use a keyed
data queue with the "EQ" comparand, it seems it's necessary to fill the
key completely. If it has trailing blanks, even if you very carefully
pass them in the call to getNextElement(), nothing is ever retrieved. I
was using the IIS session ID as the key. The fix was to right adjust the
key value and replace any blanks with zeros in both the EGL module and
the back end server.

Login credentials:
What's the best way to store login credentials for accessing the i? I
know I don't want to hard code the user ID and password every place it's
needed. Is there a better way than just storing it in a text file? Is
there a way to use environment strings in EGL? No great security risks
here, just mainly housekeeping. I also need to be able to to somehow
dynamically change the name of the i host partition for promotion to
production, so an environment string would be ideal.