new feature request - identify a subfile record terminator - allsubsequent characters are ignored

[Deskin, Bob]

I was waiting to see if anyone else commented on this idea.
 
Subfiles are created by PowerHouse and, except for nodict subfiles, are
designed to be read by PowerHouse. I know that there are techniques
where the dictionary is created in PowerHouse and the data files are
created elsewhere, but I don't believe that these are very common. And
when they are used, they need to take into account the restrictions of
PH subfiles.
 
We do not currently handle variable length direct or indexed files on
UNIX or Windows. And if you're talking about a pseudo-variable length, I
expect it would require some major work to integrate into our existing
routines.
 
I don't see this as being a high demand item and is potentially high
risk and high effort. 
 
Bob


________________________________

	From: powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com
[mailto:powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com] On
Behalf Of Joe Boyle
	Sent: August 29, 2007 8:24 pm
	To: powerh-l at lists.sowder.com
	Subject: new feature request - identify a subfile record
terminator - allsubsequent characters are ignored
	
	

	I think I may have a winner here - at last :-).

	 

	New feature request - on subfile creation, identify a subfile
record length terminator - all subsequent characters are ignored for the
current record.

	 

	Currently, subfile records are of absolute length, so very
difficult to read variable length records (e.g. csv format ) with ease. 

	 

	In this scenario, a defined record terminator char can be
identified to PH, and appended to each subfile record on creation e.g.
dos example below :

	 

	`Run some process` >>  "Run_some_process.log"

	 

	For /f "tokens=*"  %i in  ("Run_some_process.log") echo %i| >>
"Run_some_process.ps"

	 

	Where the definition for portable subfile 'Run_some_process'
contains not a record/item length, but establishes a "|" char as a
record terminator.

	 

	 

	Regards, Joe.
 
     This message may contain privileged and/or confidential information.  If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so.  Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20070831/eddc484e/attachment.html