HP3000-L Archives

December 2005, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Bruce Collins <[log in to unmask]>
Reply To:
Bruce Collins <[log in to unmask]>
Date:
Mon, 5 Dec 2005 16:21:33 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (63 lines)
Is it possible that sed on the HP is treating the first \x at all?

Then your expression would be replacing the characters: "\" , "x" ,"7", the 
range "F-\xFE with "*".

It seems to be replacing all letters above "E" and the number "7".

Bruce

----- Original Message ----- 
From: "Dan Barnes" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, December 05, 2005 1:41 PM
Subject: [HP3000-L] SED Usage


> Hi -L Gang,
>
> I have a user who is trying to use SED to do some data manipulation and is
> not getting the desired results.
>
> The issue is incoming data from another platform that is being fed into
> MM3000.  This data occasionally has some unprintable characters, which of
> course wrecks havoc on the MM application when it is encountered.
>
> To address this, the user, using a cygwin (unix like) environment on their
> windows pc, developed a SED script that when they test in the cgywin
> environment, works just fine, but when done on the target HP3000 (7.0 pp2)
> gets an undesirable result.
>
> The script below is meant to scan and substitute based on what you see
> below:
>
> sed -e 's/[\x7F-\xFE]/*/g' < COMSHD > COMSHD1  works on cygwin
>
> Unfortunately, while meant to catch the ascii table entry for the Delete
> Character and then subsequent unprintable characters after that (hex 7F
> thru hex FE), is in fact catching more than desired.  Below is an example
> of what is being changed that was not intended:
>
> SI28772      JACT1001       3M TECHNOLOGIES (S)            PTE LTD.
> to
> **28**2      *AC*1001       3* **C********* (*)            *** **D.
>
> The user thought that because MPE/iX is POSIX compliant, that this shoudl
> work.
>
> Clearly not my forte here ;-)......
>
> Could someone steer me in the proper direction ?
>
> Thanks!
> Dan Barnes
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>
> 

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2