DSXchange

I would like to import the job from previous project I exported; however when I imported, there are 2 message boxes as follows:

1. "File E:\First.dsx can only be imported when the client code page is 874 - it is currently 1252"

2. "File E:\First.dsx does not appear to be a valid DataStage export file or is from an incompatible release.

A valid DataStage export file is expected to be in Windows format (i.e. using CRLF line terminators)."

And I cannot import.

The following information may useful:
- Previous Project
* DataStage Release: 7.x
* Job Type: Server
* OS: Unix
- Current Project
* DataStage Release: 7.x
* OS: Window

I need to see the BASIC script inside that job.
How can I import that job, or does anyone have anyway to see the BASIC script inside that job?

Thank you very much,
Cartoon[/color]

Open the DSX file with any text editor and change the CharacterSet property (it's very near the top of the file) to the appropriate value.

Export files are always made on the client, so that the operating system of the server should be irrelevant.

Ray,

When I open the DSX file with UltraEdit-32; I see the BASIC script and non-BASIC script stay together, and that's hard to identfy which one is BASIC part.

I would like to see only BASIC script. Does it have anyway? Also, which text editor program you suggested?

The following is the sample when I open the DSX file with UltraEdit-32:

e_cartoon wrote:BEGIN HEADER
CharacterSet "CP874"
ExportingTool "Ardent DataStage Export"
ToolVersion "3"
ServerName "172.16.252.52"
ToolInstanceID "TDDEV11"
MDISVersion "1.0"
Date "2004-01-05"
Time "09.10.08"
END HEADER
BEGIN DSJOB
Identifier "CopyOfebizOdsJobControlJC"
DateModified "2003-12-02"
TimeModified "08.21.07"
BEGIN DSRECORD
Identifier "ROOT"
OLEType "CJobDefn"
Readonly "0"
Name "CopyOfebizOdsJobControlJC"
NextID "1"
Container "V0"
JobVersion "20.0.0"

Thanks,
Cartoon

e_Cartoon,

a quick look at your export header shows that this is an export from a Version 5 (or mayhaps 6) DataStage project. DSX files are upwardly compatible, so that should not cause an issue.

The 2nd line of the header specifies the CharacterSet, so just replace that value with "CP1252" as Ray suggested.

There is no text editor out there that will automatically redisplay the .dsx export file (unless someone has written an EMACS macro to do so); this file is really not meant to be edited so the format is great for machine legibility but not really for human consumption. The BASIC code itself isn't all that useful.

ArndW and Ray,

Thank you very much.

Cartoon

The BASIC code itself isn't all that useful.
... unless you've memorized every single BASIC op-code, which is a major waste of time!