DSXchange

My experience with this, using environment variables for passwords, involves how the variables are listed and used in the job. My implementation: Define the environment variable in the job properties parameter tab, and set the default value to $PROJDEF. Name the variable in the stage for the passwor...

I saw that one. 143 Boomi reviews to 14 for DS. Not up to even the minimal statistical standards. Humph.

Note: I searched DSXchange already, and found no posts that reference Boomi. Basically, I'm looking for a side-by-side comparison, but not at any great level of detail. I've looked at the Dell material and found little in the way of comparisons elsewhere. Your thoughts and opinions are most grateful...

Vicky, all I can say is that you have Mainframitis, and it might be incurable. First, manual updates to production being rather, ahem, unusual, they should at least apply some discipline and do the update around the same time every day. That doesn't make your job easier, but it does give you somethi...

Vicky, A hypothetical job flow: Job1 -- Query for update to system date in db table. Loop conditions: if not found, wait five minutes and try again. If found, end and release next job to run. Job2 -- Extract system date for further processing. It looks simple, because the complexity is under the cov...

Craig has good suggestions. I wonder about whether your jobs run in isolation, or if you have a scheduling application like Control-M to manage the jobs. If, for example, there was a scheduled job which updates the system date, your DataStage job would just wait for it to run and complete the update...

Single quote is a valid character in the file name, but it has a meaning and usage in DataStage. You can't work around that, so you have to change the file name. I suggest a script which lists the names of the files you intend to read, parses the names for characters that cause you problems, copy th...

Craig, the server is not happy. My post took a couple of minutes to be saved and displayed. Indeed, I expect this post to be visible sometime in the year 2022.

Many issues you'll face with Cobol data is covered in the FAQ linked at the bottom of my post. I believe you are looking at a signed numeric field. The data is alphanumeric, but the digit with the "odd" character has been changed to contain the sign. "0" = xF0 and in many numeric...

I just completed a total restructuring of the folders in a project with more than 600 design objects -- sequence and parallel. I did it manually, knowing that any other method had some risks for the project integrity. I started with documenting the old structure, and linking old folders with new fol...

Prepare for possible embarrassment I've felt many times.

What is the Default Value of $APT_LASTDATEPROCESSED in the job you run?

If it's not $PROJDEF, there's your problem.

Ah. Looks like a timing issue. The difference between us appears to be that updating the env variable(s) happens before any jobs that use them are invoked. The gap in timing for us is often hours, depending on how we are constrained from scheduling configuration changes. Experiment: make sure no job...

it seems the value does not update until the project is reloaded. This is a bit mysterious to me. When we run env updates -- always in batch mode, I should point out -- we don't go through a "reload" process. The value is reflected in the repository, and any jobs that run after the update...

Unfortunately, you will need to add the variable to every job that needs it. However, if you already have a variable or parameter in place (in a User Variable stage, perhaps) you can value it with the environment variable. An alternative is exporting your Design code to a dsx file and editing it, bu...

I'm not clear on how you want to implement it. Do you want the variable value updated for every cycle, or as a one-time task? Either way, invoking this dsadmin command for environment variables should be doable from a script or command line: ${DSHOME}/bin/dsadmin ${CLI_ARGS} -envset ${VARNAME} -valu...