DSXchange

Ernie, a bit of both. Using .dsx's with compiled code will work only if the two environments are absolutely identical, i.e. all relevant paths to executables, projects, libraries, system components, DB components, etc. Since this is not always the case, I tend to prefer non-executable deployments wi...

That means somebody deleted the project from UNIX and not from the Administrator. Create a new dummy project from the Administrator, then copy the complete contents in Windows from the new project into the MyProject directory and then proceed to immediately delete both projects.

Has this suddenly started happening on your workstation and things were working before? If so, perhaps your PC has been automatically updated by system software and libraries have been overwritten. Try re-installing the clients - assuming you've already re-booted and seen if the problem still occurs.

Create a simple job that writes to a sequential file, then make a copy of it changing only the append mode. Export both into .dsx files and compare the two. Now you know which setting to look for. Export your whole project into a .dsx and search.

With Version 8 there now 2 places where this metadata is stored, once inside the "old" DS Engine and the other is in the "new" repository. I haven't yet played around with the new repository side in order to be able to state what you need to do in order to clean up, though. You can try to use the DS...

That means something has changed. Either on the server, or perhaps an automatic update on your workstation. Have you checked the Information Server status with your administrator - either locks on your user or perhaps even a redefintion of your user's access rights might be causing this.

I'm afraid I don't understand - you created test jobs but couldn't create a new job? How does that work?

That is a repository error message. Does everyone have similar problems, or just your user or even your particular workplace? Is this a new error (i.e. have you saved jobs before as this user on this install)? Have the administrator go and check in the information server for sessions that might stil...

Approach the problem step-by-step, as Wolfgang has suggested. What is your source character set? What character set would you like as your target?

right-mouse-click on the column, then "edit row" and check to see if all attributes listed are identical in both columns. Basically DataStage is seeing a difference in formatting or datatype between CREATED and LAST_UPD which is causing *s to be displayed. What if you were to delete "CREATED" in the...

The record delimiter field in the sequential file window only allows the input of the 2 default values, nothing or 1-character so in this particular instance you cannot use the 0x1E type of representation. This should be noted as a bug, in my opinion. Wasn't there a Windows keyboard shortcut to crea...

It sounds like you know more than I do; I haven't heard of the "X Migrator" and don't know what it will do. Perhaps someone else will chime in here and explain that to both of us.

Add a reject link and examine the SQL codes that are added to the output stream on rejects in order to determine why these records are being rejected.

Yes, you can migrate directly. Many such migrations will go without a hitch, but sometimes you might encounter issues. Is it a complex implementation and are there a lot of "special" programs or code? I can't recall if one was still allowed to change parameter values inside jobs at V5, but if yes an...

You need to convert it into internal format first, using ICONV(In.Column,"D4YMD") and then you convert it back into display format using something like OCONV(InternalDate,"D2DMY[2,3,2]")