Non-printable characters in Batch Job script

[admin]

Yik,

I recently upgraded 5 to 7 without NLS enable in both versions. I had the =

same problems. the Ascential Consultant helping with the upgrade had not=20
seen this before and did not know of a way round it. I found that it was=20
the combination of the characters '\' and 's' that was converted not just=20
the 's' - mistaken for a control code i guess. I had to change them all=20
manually - luckilly it only happened in the comments part of the code.

Jon





Tony Stark
08/01/2004 14:14
Please respond to datastage-users

=20
To: datastage-users@oliver.com
cc:=20
Subject: RE: Non-printable characters in Batch Job script


Yik,
This is a guess. Is it possible that you installed DataStage 5.x with NLS=20
enabled and DataStage 7.x without NLS enabled? Or the opposite (NLS not=20
enabled in DataStage 5.x and enabled in DataStage 7.x)?
=20
Good Luck,
Tony

YikFoong=5FWong@singaporeair.com.sg wrote:

I cann't do the copy-and-paste as there are a lot if batch script. In 5.x,
there is not "=FC" character in the script, only after migrated to 7.0, this
character appears.

Regards,
Yik Foong.



|---------+--------------------------->
| | wolfgang.huerter|
| | @gerling.de |
| | |
| | 08-Jan-2004 |
| | 06:09 PM |
| | Please respond |
| | to |
| | datastage-users |
| | |
| | Sender Info: |
| | No Sender Info |
| | found in the |
| | address Book |
| | |
|---------+--------------------------->
>--------------------------------------------------------------------------=
-------------------------------------|
| |
| To: datastage-users@oliver.com |
| cc: |
| Subject: RE: Non-printable characters in Batch Job script |
>--------------------------------------------------------------------------=
-------------------------------------|




Hi Yik,

that sounds to me strange. I am not yet on 7.x, so I can't comment how=20
this
could happen. One Alternative you have is to copy the whole 5.x-code into
an
editor and save it and then to paste to code to a newly written batch job
and see what then will happen.

The "=FC" is a usual letter in non-anglo-languages like for example german
and
we print it many times in our books and papers.

In DataStage the "=FC" was used to separate fields, so we had in the passed
the opposite problem, when I wrote my Familiy-Name, which contains this
letter into a comment in a routine, the routine didn't compile.

Have a nice day

Wolfgang H=FCrter

-----Original Message-----
From: YikFoong=5FWong@singaporeair.com.sg
[mailto:YikFoong=5FWong@singaporeair.com.sg]
Sent: Thursday, January 08, 2004 5:17 AM
To: datastage-users@oliver.com
Subject: Non-printable characters in Batch Job script


Hi,

I am migrating DataStage 5.x projects directly to 7.0. However, there are
some non-printable chars found in the batch job script after the project
migrated to 7.0. For example, in 5.x,
the char 's' has become '=FC'. I tried to export & import the projects=20
again,
unfortunately the problem still exists.

Any expert has any idea how it could happen and how to avoid it? Thanks!

Regards,
Yik Foong.

>From :
Software Engineer,
APPLS SERVICES (65417378)

=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Visit us at http://www.singaporeair.com
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F

This message may contain confidential and privileged information. If you
are not the addressee (or authorized to receive for the addressee), please
notify Singapore Airlines Limited (SIA) by return email immediately, and
destroy and delete the message from your computer. Furthermore, you may
not use, copy or disclose to anyone the message or any information
contained in the message. SIA does not guarantee and is not liable for the
security of any information electronically transmitted or for the proper
and complete transmission of the information contained in this
communication, or for any delay in its receipt. The use of this email for
any illegal purpose or for any purpose other than as permitted by SIA is
strictly prohibited and such use may result in legal proceedings.








---------------------------------
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard


--=_alternative 00647A1880256E15_=--

[admin]

Thanks, Jon. The OCI stuff really helps.

Alan
>
> From: jon.hall@pharma.novartis.com
> Date: 2004/01/09 Fri AM 08:55:24 GMT
> To:
> Subject: Re: RE: Non-printable characters in Batch Job script
>
>
> There were a few things - some of these things may have been specific to 4
> of course
>
> 1) the "\s" escape code in scripts, of course and as someoneelse mentioned
> there may be problems with other escape codes eg "\v". The idea to search
> and replace in the Export file should work ok I think.
>
> 2) Oracle 8i OCI stage:
> a) Ouput\General - Array size was incorrectly filled with SQL
> statement
> b) Column Derivations were ignored in 4, so if these are incorrect in
> 4 they will now fail in 7
> c) Some problems with user defined queries being changed to column
> generated and therefor not working - just need to change back to
> user-defined
> d) had a single OCI stage with two reference outputs to 2 transformer,
> this was causing the job to hang, by splitting into 2 separate OCI
> reference stages the job worked.
>
> 3) There is a new way of handling parameter passing to Routines, but we did
> not have problems with that and I think it was only for v4, and the upgrade
> makes some checks anyway - to do with passing in variable to a function and
> then changing the value in the routine - work around is to assign the
> passed variable to a local variable.