DSXchange

I believe it's that the password is encrypted, and not being converted back to text by the runtime engine. I defer to others who use the SP stage to comment further, because I've hit the extent of my experience with this.

Good luck.

It could be as simple as a syntax error. How are you typing in the Data source and user name? Do you just name the parameter -- parmDataSource -- or are you using the escape # -- #parmDataSource#? I know that in other stages, you must use #, and in other stages you must not. Usually the difference i...

I recently posted a FAQ about CFF. The link to the post is at the bottom of this post. Read about editing the copybook before loading it with the Import Wizard. Occurs depending and groups are definitely problem areas needing attention before loading the table definition. One thing about ODO: you mi...

Disciplined, or punished? :P I tell my infrastructure support people that they have two choices: do some planning and announce any "outage" in advance, or watch me do a verbal scorched earth routine. It should be very simple. The system is in use, or it is the private playground of the mai...

If you must abort the job sequence, and you must also complete the after-job routine, try putting an Execute command activity next. I use a row count in a similar way, and the command output value determines the triggered link. For example, if my output file is empty, but always has a header row, if...

sed -e 's/&PLID/#ec_Get_PLID_Value.$CommandOutput#/g' Sorry, I missed this one, and UCDI has the right idea. Command output is only available in the subsequent stages in "raw" format, meaning it could contain spaces or control characters that can't be read by DataStage. Put the comman...

Sandhya, I'm just an adequate Unix guy. You have a sed issue that others here can better address. My only advice is to use a script with input parameters instead of a command line, because you can better control the processing, particularly how you pass the results back to the stage. Two best practi...

I have a job that generically sets a loop to run individual FTP sessions from a text file with a list of file names to get. It goes like this: Exec Command -- script to determine the number of files (sets end value of loop). User Variable -- set variable values from script. Loop: Exec Command -- get...

Craig, I'm a designated access person in the financial industry. My fingerprints are on file at the SEC. I work in the most regulated industry in human history (well, arguable by some, but they are pikers, really), and I will happily stipulate that my shop is as closed-down as it is possible to be a...

Ray,

That would never fly here, having passwords (even encrypted) in a permanent file. Much too hackable.

Have you considered "dirty" logic branches in a job sequence? It means having redundant stages, their only difference being the environment variables used. You are aiming for an efficient solution. I'd do the same, but sometimes it's better to surrender to the obstacle and change it to som...

In my first Cobol job, I was faced with a long If statement -- 4 pages worth when printed -- which was failing, and no clue where. I took the printout to a conference room table, used multi-colored pens to carefully chart the various Ifs, Elses and Thens, and after 3 hours was ready to break somethi...

You're not following me because I'm likely not understanding your situation. :oops: First likely bad assumption: you're storing the variables in the project repository as User defined environment variables. If that's not true, my suggestion is not appropriate. I thought that was true when you mentio...

As a second-level thinking, if you really need to set these values at runtime, a routine that builds a proc for you seems best. You would call that proc each cycle, and how you build it is up to you. I would still avoid using DataStage, but if your architects believe it to be the best choice, have a...

I strongly caution that since this is JCL -- job code that will be executed by the operating system, not data to be processed (at this level) -- that DataStage is a bad choice for accomplishing your task. In JCL -- with a strong parallel in the job sequence -- it is best practice to break up distinc...