DSXchange

or pre-stored commands LISTF, LISTFL or LISTFR.

Job parameter references are not supported in the Command field; they must be in the Parameters field.

Not particularly creative, but these (or their DSMacro equivalents) are very useful in error processing streams to enrich the error data with "location" information - job name, start date, project, etc. I tend to encapsulate that processing in a shared container for re-use.

An alternative is to strip the line terminator in the command itself.

Yes. And that's how database engines do it too.

Not really - more

UNIX should have recorded when the user ID was created, since this is a security event and these typically are logged. Ask your UNIX administrator.

PXSequentialFile is a class identifier. This is the parallel Sequential File stage. The CSequentialFileStage class is for the server Sequential File stage.

Is this really a QualityStage question?

You have the choice:

• name the Parameter Set and give the values file name as its "value" e.g. -param Database=database_par
  
  name individual parameters using "dot notation" e.g. -param Database.SRC_USR=zaphod

Edit the file of names to build SELECT statements around them. Or: Execute Command activity: cat #filepath# User Variables activity: Ereplace((Cats(Reuse("SELECT * FROM "), Command.$Output),@FM," UNION ALL ",-1,0) That will get you close. You may have to trim the trailing @FM fro...

DS.TOOLS is only available in projects. Once you're in dssh in the admin account (which you have described) you need to remembering that project names are case sensitive.

Once you get version 8.7 you can go one step further than what Stuart indicated and include a Data Rules stage in a DataStage/QualityStage job. This stage can use data rule definitions published from Information Analyzer or you can develop data rule definitions within the stage (and, optionally, pub...

Yes, I was being simplistic. For example are your VarChar data types bounded (have a maximum length) or unbounded? There are also other overheads associated with storage in a Data Set - approximately 80 bits per row last time I looked (version 7.x).

I can't see where you specified the project in your command.

I am therefore mystified that the command itself identified a project name.

Read any of the IEEE monographs on storage of floating point numbers. All of them tell you that it can't be done - what's possible in a digital computer is at best a compromise. DataStage chooses to alert you to that fact whenever you use float or dfloat data types.