Re: Removing "BAD" characters from a file

Were they completely messed up or was there a pattern?

Did you try copying to a file with length of (actual record length + 1).
What I mean is, if, for example, your data is 80 characters, then try
copying it to a file with 81 characters.

I am sure you must have tried all this, but just checking...


On Thu, Mar 3, 2016 at 3:02 PM, Alan Shore <ashore@xxxxxxxx> wrote:

Thanks for your reply - but the records from the ifs did not line up
correctly

Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
‘If you're going through hell, keep going.’
Winston Churchill

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Vinay Gavankar
Sent: Thursday, March 03, 2016 3:01 PM
To: Midrange Systems Technical Discussion
Subject: Re: Removing "BAD" characters from a file

I haven't followed this entire conversation, but what happens if you use
ENDLINFMT(*FIXED) in the CPYFRMSTMF command?

On Thu, Mar 3, 2016 at 2:48 PM, Alan Shore <ashore@xxxxxxxx> wrote:

Well - the noise you may be hearing is me hitting my head against a
brick wall

I have tried EVERYTHING
I used the SQL translate against the file that gets created from the
CPYFRMSTMF I used a small CLLE program - tested in debug mode,
interactively - looked at the file directly after the CPYFRMSTMF and
could see the Hex(25), the sql statement runs and the HEX(25)'s are
replaced with HEXS(40) Beautiful Changed the program that needs to be
changed and started the process - in batch Does not work In debug -
when the file that gets created from the CPYFRMSTMF is DBU'ed - the
one record containing the HEX(25) has already been split into 6
individual records BEFORE the SQL statement can be run

Then I followed what was suggested below and created my own table -
with one change The hex input from the file is 0A that was converted
to HEX(25), so I changed the convert table to be HEX(40) instead

I used a small CLLE program - tested in debug mode, interactively -
looked at the file directly after the CPYFRMSTMF and could see the
Hex(25) have now been replaced with HEX(40) Beautiful Changed the
program that needs to be changed and started the process - in batch
Does not work In debug - when the file that gets created from the
CPYFRMSTMF is DBU'ed - the one record containing the HEX(25) have been
split into 6 individual records as if the Table was ignored

Does anyone think that the fact I run interactively - it works I run
in batch - it doesn’t Has any bearing on this?


Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
‘If you're going through hell, keep going.’
Winston Churchill

-----Original Message-----
From: Alan Shore
Sent: Wednesday, March 02, 2016 9:57 AM
To: Midrange Systems Technical Discussion; Tim Bronski
Subject: RE: Removing "BAD" characters from a file

It looks good
I am presently looking into this
Trying to see if a table can be created from a physical file, that way
I can try and keep the table and file in sync

Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
‘If you're going through hell, keep going.’
Winston Churchill

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
paultherrien
Sent: Wednesday, March 02, 2016 9:42 AM
To: Midrange Systems Technical Discussion; Tim Bronski
Subject: Re: Removing "BAD" characters from a file

+1
I have never used this, but this seems like an excellent option. Let
the system do what the system is already doing.

On March 2, 2016 at 9:18 AM Tim Bronski <tim.bronski@xxxxxxxxx> wrote:


Another option (if you want to keep the CPYFRMSTMF in place and not
write a pgm) is to create a translation table and specify that on
the CPY. To do this use CRTTBL TBL(yourlib/YOURTABLE)
SRCFILE(*PROMPT) BASETBL(QEBCDIC). This will give you a prompt where
you can specify which characters get mapped to what. You could make
all non printables = blank x40.
Then on the CPYFRMSTMF use CVTDTA(*TBL) and specify your new table

name.

On 3/2/2016 3:01 PM, Alan Shore wrote:

Hi Luis
Thanks for your reply

What is interesting is that I never received Robs reply - so Rob -
appreciated - NOT ignoring you

We already have a procedure in place to handle this - and that
would mean writing an RPG program for this file to use that
procedure I was just hoping that someone could see something I
could use in an SQL statement, that I could insert into my clle
program, but ity looks like I will need to bite the bullet on this

Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
‘If you're going through hell, keep going.’
Winston Churchill

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On
Behalf Of Luis Rodriguez
Sent: Wednesday, March 02, 2016 8:54 AM
To: Midrange Systems Technical Discussion
Subject: Re: Removing "BAD" characters from a file

Alan,

Besides Rob's excellent suggestion (processing stream files
directly from RPG), assuming you have a BadChar-->GoodChar table
already defined, Why not simply use RPG’s XLATE? It could be
something like

(not exact code):

//----------------------------
// Define "holders" for %Xlate
D FromChar S 064 Varying
D ToChar S 064 Varying
//
Clear FromChar;
Clear ToChar;

// Build your translation strings
DoU %Eof;
Read BADHEXCHR;
IF not %eof;
FromChar = FromChar + BHCCHAR;
ToChar = ToChar + BHCREPL;
ENDIF;
ENDDO;

DoU %Eof;
Read File-to-be-translated;
IF %not eof;
Field = %XLATE(FromChar : ToChar : Field ; ENDIF; ENDDO ;

Just an idea...

//----------------------------

Regards,

Luis


Luis Rodriguez

--
Need sFTP or PGP? Download your native sFTP or OpenPGP solutions here:
www.arpeggiosoftware.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related

questions.
Paul Therrien
Andeco Software, LLC
paultherrien@xxxxxxxxxxxxxxxxxx
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at

http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.