DSXchange

You can also create three files - header, detail, trailer - and then cat them together in the proper order after job. Record counts for the trailer can be built using the Aggregator.

To do what? Run a script before/after job? No, you set the routine to ExecSH and then give it the complete path to the script, plus whatever arguments it may need.

As noted, Vista is not supported. That being said, have you tried running the Designer in any of the compatibility modes? Right-click on the executable, Properties, Compatibility.

I dont't understand why i'm not receive the whole posted message. You don't? You're not aware of the Premium Membership available here? There are five (six?) Premium Posters and their complete answers can only be seen by those whom (in essence) subscribe to DSXchange, helping to keep the site alive...

Never had to run that before for all the installs I've done... I'll check it out.

Not sure how that wasn't helpful as it explained your compiler error, which was all I was trying to do. Obviously, you need to go back to "Y"/"N" or "NULL" in your variable, making sure your derivations are correct.

No problem, glad you managed to find it.

They are still present and owned by root - and so I am. No can do. It's been a year since this server has been rebooted and I totally forgot the shenanigans we have to play when that happens. Had to drive into the office on Turkey Day and dig through my email archives for the confirmation of the pro...

We "lost an nPar" on our HP-UX Superdome so had no access to any of the production DataStage servers. They "reset" things and everything came back fine except for one server. I can't connect from the client in spite of the fact that everything seems to be running, including the dsrpc daemon. I can c...

Error when checking composite operator: Setting null to this non-nullable field:StageVar0_svCODEGRPGEP

Stage variables are non-nullable so cannot be set to null.

Does your target field in the table allow nulls?

You have it. You need to determine what is different between the two environments, obviously something is if it works in one and not the other (something you should have mentioned from the start).

Your export is just the executables or source and executables? Regardless, you should be able to open it as it is just a text file and check for the pattern you would need to search for to pull the job names from it. Off the top of my head, there should be a 'BEGIN DSJOB' record and the immediately ...

No, that's not true.