DSXchange

I agree with you, Craig. The -lparams command SHOULD work irrespective of whether the job is aborted/restartable or otherwise. And yes, the Status is shown as '0'. Let me brief you on the nature of my 'wrapper script'. 1. The script will take two parameters: proj name and job name. 2. The dsjob -lpa...

Chulett,
I checked with another job that had finished status... this one also shows a different list of parameters... really do not know what's wrong, 'cause all I am trying to do is execute the -lparams command

Chulett,
I checked with another job that had finished status... this one also shows a different list of parameters... really do not know what's wrong, 'cause all I am trying to do is execute the -lparams command

I executed the command in the usual manner, ie. dsjob -lparams projname job1 But the result of this command yields a set of parameters which are not used in the job 'job1'. Rather it yields a set of parameters from some other job 'job2'. And yes Chulett, the job 'job1' was in an 'Aborted/Restartable...

Hi, I am trying to list the job parameters and use it in a shell script. The -lparams worked perfectly. But after testing it for several jobs and sequences, we found some strange behaviour. The dsjob -lparams was executed for a sequence as before. But it returned a different set of parameters. We co...

If I use it as you say I get the following warning for each record of the input,
When checking operator: When validating export schema: At field "DATE_COLUMN": Exporting nullable field without null handling properties

If I use it as you say I get the following warning for each record of the input,
When checking operator: When validating export schema: At field "DATE_COLUMN": Exporting nullable field without null handling properties

I have a similar kind of requirement so I thought I'd ask here itself. Which stage variable should we give in the derivation for the Output Columns? That is, should the stage variable prefixed 'prev' be used or the one with 'curr' be used? When I use 'prev' the first row is displayed with empty rows...

Hi, I am trying to redesign a Cosort program into PX. Right now I am checking out the metadata details. The input file has a date column which can have null values. As reported in different topics in this forum, I set the metadata as Date(10) with Nullable property to 'Yes' and the Null Field Value ...

We are using a two node configuration. And like I had mentioned earlier, the sort stage uses hash partitioning and the remove dups stage uses 'same' partitioning.

Stefan, by 'inserted sort' do you mean the 'perform sort' option within the sort stage and the remove dups stage? If that is so, yes I have disabled them. And yes I have used the keys in the order that you have shown. I guess the warnings are not an issue. The problem is that the sorted data is jumb...

I have to replicate the following scenario in DataStage. There is a sequential file which has been sorted using five different keys in descending order using a SyncSort program. The output of this file is given to another SyncSort program which uses three keys (these three are part of the five used ...

I have to replicate the following scenario in DataStage. There is a sequential file which has been sorted using five different keys in descending order using a SyncSort program. The output of this file is given to another SyncSort program which uses three keys (these three are part of the five used ...

According to the DataStage PX documentation, the size for Double is 8 bytes, Float is 4 bytes. What is the storage szie for Decimal and Numeric types? And what is the range for these types?

so what exactly is the difference between a NULL field and an EMPTY field? For example, my record looks like this in a sequential file: 10.00||20.00 where all the fields are decimal values. But when I use the View Data option in Datastage, the record is displayed as 10.00 NULL 20.00 So how does one ...