Re: Overriding default end-of-line character for UNIX or WinNT

["Hins, Thomas D." <Thomas-Hins@OUHSC.EDU>]

Rod,
   I believe I was experiencing the same problem you are talking about.
What I did was assign a value to a variable such as

let $CarraigeReturn = chr(13) || chr(10)

then that is the last in my write data.  It seems to do the same no
matter if I run the sqr in SQRW in Windows or if I run the SQR on the
Unix server.  I am pretty sure something of this nature will work for
you at least it does for me.
Tom Hins
Information Technology - Application Solutions
University of Oklahoma Health Sciences Center
P.O. Box 26901
Oklahoma City, OK  73190
Phone:(405) 271-2262 Ext. 50213
Fax: (405) 271-2352


-----Original Message-----
From: Rob Talbert [mailto:rtalbert@KNOASIS.COM]
Sent: Monday, January 07, 2002 2:50 PM
To: SQR-USERS@list.iex.net
Subject: Overriding default end-of-line character for UNIX or WinNT


SQR Version: 3.0.18 (moving to 4.3.4)
DB: Oracle 8i
OS: UNIX Solaris 8 and Windows NT
App: PeopleTools 6.1

Situation:  I create an extract file from PeopleSoft (using SQR "Open
$File as 1 For-Writing" and "Write 1 from") running on an Oracle DB.
The SQR program can be run from a UNIX server or on a Windows client
(and the resulting files are deposited in a UNIX or Windows directory,
respectively).  When run on the UNIX server, the resulting extract file
has a one-byte end-of-file marker which is HEX '0A' (line feed) and when
run on Windows, each line is terminated with two bytes, HEX '0A' and
'0D' (line feed/carriage return).   I believe this is all normal.

I would like my extract file to always have the same line termination
character, no matter if I run it from UNIX or Windows.  Is there a way
over-ride either OS file I/O default from SQR to force either '0A' or
'0A 0D' from either UNIX or Windows?

Thanks,
Rob Talbert
Washington, DC