DataStage Basic Complier Problems

kduke · Post by **kduke** » Tue Feb 20, 2007 7:50 am

Try this viewtopic.php?t=94304&highlight=KDBP

ArndW · Post by **ArndW** » Tue Feb 20, 2007 8:13 am

The compiler is called using the "BASIC" command. It is better to create the folder as type 19 so it doesn't do funky things with your filename. BASIC commands do not need to be terminated with a semicolon.

chulett · Post by **chulett** » Tue Feb 20, 2007 8:18 am

I'm just curious why you are taking this path rather than creating Routines in the Manager or coding in the Job Control tab of a Server job?

SteffenRdk · Post by **SteffenRdk** » Tue Feb 20, 2007 8:56 am

I analyse DataStage and consequently I need to analyse also BASIC.

chulett · Post by **chulett** » Tue Feb 20, 2007 9:00 am

Doesn't really answer the question, but... ok. Whatever.

Why not just 'analyse BASIC' by studying the supplied Routines? There are a plethora, documentation is decent and all you have to do is double-click on one to reveal the BASIC source code.

ray.wurlod · Post by **ray.wurlod** » Tue Feb 20, 2007 1:24 pm

The file you opened is the dictionary. It is (was) a hashed file. By overwriting it with text you have irretrievably damaged the hashed file structure, and therefore the file dictionary. What you needed to do was to open a file in the BASICCODE1 directory, not in D_BASICCODE1.

You need to undo your work, and begin again. Use the command DELETE.FILE BASICCODE1 so that the VOC entry is also deleted.

The next point is that "basic.exe" is not the BASIC compiler. The BASIC compiler MUST be invoked using the BASIC command from within the DataStage environment.

You need to read the early chapters of the DataStage BASIC manual thoroughly.