DSXchange

Thanks Ray for the Reply. As mentioned, the Table is Hash Partitioned by Different Column (Col: 1) and the Updates in this Job are done by different Columns (Column 12: Column 18 and). And we have Index on Column_12 and Column_18 still the updates are taking longer time (we are updating around 200+ ...

Need Experts advise. We are updating a Db2 Table (Around 200 Columns) based on Where clause which are indexed. Input: Sequential File Output: Db2 Connector Stage Operation: update Input_File --> Transformer --> Db2 Connector Stage. Update Statement: Update Table_name set col_1 = ORCHESTRATE.Col_1, C...

lzm004- I guess this is the User, Please check the Posts and delete them as well

Check with the system whoever is creating the excel if they are correctly populating the NULL Values (or Add Constraint <> '<NULL>' and see if the data is getting Filtered out by the constraint. I tried sample ds job to create unstructured data with 1 Column as NULLABLE Yes and set to SETNULL() and ...

Thanks, looks like the Stage variable defined as VARCHAR(255) in this case.

Tried running simple DS Job with below 2 Columns Hospital_ProductTypeID,Ancillary_ProductTypeID 3,2 1,8 3,6 7,2 7,7 And it worked as expected. "Hospital_ProductTypeID","Ancillary_ProductTypeID","svCoverTypeCode","indicator" "1","8","HA...

Please provide your Output File Format

Spaces between columns: This field is only active when you select the Fixed-width columns check box. Contains a number to represent the number of spaces used between columns.

Check below link and see if this is of any use for Custom Routine creation:

https://blogs.perficient.com/delivery/b ... datastage/

Similar post on Date Validation, Please take a look and try

viewtopic.php?p=256967

As mentioned, DataStage doesn't a feature called "Batch ID." In my previous project, we used to generate Job_Id whenever the Job Sequence starts and use log that id to Job Table to track the Job start and end and which job has inserted/updated/deleted along with the creation date and last ...

If you are looking for Id generation, there are several ways, You can generate taking the Max_Id + 1. What's the purpose of this Id in your Table?

Any Idea why Datastage is treating as DECIMAL(31,0) when casing as DECIMAL(31,5) and defined as Decimal (31,5)? Also, Can you make sure that the order of the columns are correct and Just View Data for the 1 Row (Sample you mentioned) in both DS Versions and make sure that you are getting 0.45 in old...

looks like you have successfully imported the layouts and trying to read a Mainframe File with Multiple layouts. If Yes, please check with mainframe team whoever is creating how to Identify the records for multiple formats and define those in the RECORD_ID Tab and try to read it.

Try running with Double quotes

db2 -x "select colum1 from schema.table where colum2='abc'"

Ask your mainframe support person to do num off std and then download again so that numbers on left side will go off and make sure that 01 level record starts at 8 position. I have removed the line numbers and removed the comments from your Cobol Copybook and could able to successfully import 01 RDK...