DSXchange

Go back to Ascential and ask why. Then tell us. The project cleanup performs two tasks; finding and removing orphan files (that do not belong to any job), and rebuilding the respository indexing. Rebuilding the indexes can be performed using DS_REINDEX command; it prompts for the name of a file (unl...

It even has the potential to get people in trouble who have never been employees of Ascential. [B)] Dennis and the folks at DCS (who bring you this site) are currently negotiating with Ascential about the framework (legal and otherwise) within which white papers and the like can be published. There ...

Some technical info... There is some inconsistency with how DataStage routines are cataloged (more historical accident than anything else). There are five main prefixes: "DSD." routines used primarily at design/compile time (for example DSD.Browse) "DSP." routines associated with stored procedures (...

Sure does look like bad data, in at least one row. It's this kind of thing that tools like Quality Manager or MetaRecon are particularly geared to identifying. The really important thing to feed back to the owner of the data is that this problem exists, and they'd better do something about determini...

... but no cigar! [}:)]

This message can be caused by a number of things, including the inactivity timeout having been exceeded. If it occurs while importing from a DSX file, chances are that the repository indexing is not quite right. To fix this you will need to get exclusive access to the project, then use the Administr...

The period is vital! SETFILE creates an "F" pointer, referring to the hashed file by its pathname. SET.FILE creates a "Q" pointer to a hashed file in another account, referring to the hashed file by its account name and local name within that account. (Spooky UV stuff!) [;)] Ray Wurlod Education and...

@USER0 through @USER4 are system variables that can be used anywhere in a single process. That is, for example, they can be used in the before-stage subroutine of a Transformer stage, any transform functions called by that stage, and in the after-stage subroutine called from that stage. Being variab...

It's a sequential file, so I trust that you are processing it with READSEQ rather than READ. Either is possible, but READSEQ is more efficient. OpenSeq pathname To filevariable Then Loop While ReadSeq RecordString From filevariable * code to process this line * in RecordString variable Repeat CloseS...

If there is a known and finite number of distinct values of the grouping column, a really efficient mechanism would be a Transformer stage that splits the input stream into multiple outputs using constraint expressions based on the grouping column. For example: GroupingColumn = "a" GroupingColumn = ...

It is definitely an error message generated by Oracle, as Ken pointed out. Was any other information logged either in the Oracle error logs or in the DataStage job log? In particular, is the offending value reported anywhere? What happens if you change the data type to VarChar in DataStage, and modi...

The Oracle error message informed you that your date picture ended before converting the entire input string. Your input string ended at microseconds. Your date picture ended at seconds. Either you need a different date picture that includes microseconds, or you need an expression to strip the micro...

"telnet" licensing (my term) limits the number of concurrent telnet (that is, tty or pts) connections to the DataStage server. This was the licensing model used prior to release 6.0. Developer licensing (ostensibly) limits the number of connected DataStage clients, which connect via a different mech...

I'm with Ken, based on many years of experience (his and mine). Always prefer discrete parameters, as it makes the job design easier to understand and therefore to maintain. Further, the effort involved in composing the mother of all parameters and subsequently decomposing it means that CPU cycles a...

(I don't have access to a UNIX machine this week, so this is from memory.) Take a look at the installation script. It waits, displaying "*" characters, while background tasks do some of the heavy duty copying. There is a command line option you can use to force everything to be done in the foregroun...