DSXchange

Print out the value when you get the error - that might give you a clue as to what is happening. It won't print if it is a proper file pointer, but the error message you are getting already tells us that it isn't correct.

Use TRIM(Your.ColumnName,'"','B')

What a great idea! "Job Interview Questions & Answers Forum" (subtitled "creative fiction essays for the uninitiated"). I love it; I can finally explain, in detail, my "DataSet unified field theory for data coloration"

Aakash - In your environment you can also do a 'SELECT JOBLOGMASTER WHERE PARENT = "{ParentJobName}"' in your environment If a sequence calls another sequence which calls jobs you can also find the ultimate parent. n.b. This only works for Aakash, I happen to recall that the JobLogMaster table exist...

What does your function do for the ELSE part of the OPENPATH?

Welcome to DSXchange!

Please post your actual compile time error message.

Killing a job is something that, under normal circumstances, should never be done. Jobs should be stopped from the graphical front end.
Unlocking a job is only necessary when it has failed in an unexpected manner or someone has killed it.

The file names for pathed hashed files can be extracted by doing a full project export to a .dsx file and parsing the export file. This isn't too difficult to do in a simple DS job using one transform and a stage variable to keep track of the job name being processed. This will let you find out whic...

I am so used to using the OPEN '','FILENAME' syntax that I didn't check to make sure that the first parameter is actually optional until I went to check after reading Craig's statement. I stand corrected, the syntax of both statements is identical.

No, you can change the job that runs multi-instance to just write to the hashed files. Run that with as many parallel instances as your heart desires. Once all instances are finished, start one job to read the hashed files and write to the sequential file.

...I get an Improper Data Type error message, no matter what!!... This error message occurs when the file unit ("FileHandlers(POS)") is invalid - this occurs when your OPEN or OPENPATH has failed. Can you post that statement? You cannot just add the "path" to the the statement, as the syntax of bot...

...The DS Jobs are actually run by a program call PHANTOM that runs another programs called DSD.RUN... I hate to be too picky, but in this case I need to clarify that PHANTOM is a verb which just forks a background process - in this case to execute the DSD.RUN compiled basic program inside the UV s...

I think he's trying to login to the DataStage server, so that userid/pwd combination is the one to use.

I just got to a DS account, and it does look like the hostname returned from the DSGetProjectInfo() routine is retrieved from the entry in the UV.ACCOUNT hashed file; so deleting/re-creating the project should work. Peter - can you create a new account and test a job with this call to see which name...

You need to use a userid/password combination valid on the DS server, not the client.

If you try the same account/port/userid/password combination from a PC without MCM does it work?