DSXchange

Did you notice if the machine was slower than usual when this happened? The timeout is often seen on heavily overloaded boxes, so the message isn't surprising. But if you have never seen this before and haven't changed anything significant on the machine it needs to be investigated.

Unfortunately the DSGet... routines won't work with job sequences.

Do you want the job name in a sequence, or in another job? One way would be to get the list of running jobs and, for each one, find out it's controller - which will be the sequence name.

Transformer stages are always active stages. The basic transform stage is part of the Server product, but the PX engine allows this stage to be called (the opposite, using a PX stage in Server is not possible)

The latest version is 8, but the latest version for 7.5 is 7.5.2

If only your ID is affected then I would look at the differences between your user and others at the UNIX level. Hanging up is odd; can you do a "view data" on the datasets from your designer window? You can also use the "truss -p {pid}" on one of your job's runtime processes to see which system cal...

I prefer the "view data" of a dataset over a peek, but will use a peek stage when I want to view interim data, i.e. when the peek stage needs to be put into the processing stream and has both an input and an output.

DataStage server is written based on a database which is very much like IBM UniVerse. They used to be the same system but have now been developed indendantly. The database is a Pick postrelational one and you can use your favorite web search tool to find thousands of pages discussing this.

Hari - posting a question two times will not double the speed you get answers. Posting a PX/EE question like this in a server forum will not get you any answers at all. Stick with the question you asked here

Which column number is "Student"? Can you post both your column definitions and a sample row of data to help analyze the problem?

The solution is to change the datatype to accept the bigger value or change the value to fit into the datatype.

Put a reject link in your output stage and point it at a peek stage. Run the job and examine the data in error to determine which column is causing you grief.

DataStage Server - yes
DataStage PX/EE - no

You cannot convert COMP-3 columns in that manner within the editor. Do you have ANY columns in your COBOL that are "COMP" or "COMP-3" or "COMP-2"?

I was thinking of the Switch on the first letter, but as Ray has pointed out, you would need a transform/modify stage in the job, so you might as well use the transform to split the streams.

Using Search shows 320 posts discussing link collector. I haven't looked through them for a case where the link collect doesn't work and doesn't give an error. Have you? If you have a specific case where this happens on your machine and can write your job so that you don't need a link collector then...

You can split the stream using a switch or transform or filter stage (I'm sure that there are others I've overlooked)