Answer Posted / santhosh

hi this is madhu.

main differences b/w datastage 7..52 to 8.0.1

1. in ds 7.5.2 we have manager as client. in 8.0.1 we dont
have any manager client. the manager client is embeded in
designer client.

2.in 7.5.2 quality stage has seperate designer .in 8.0.1
quality stage is integrated in designer.

3.in 7.5.2 code and metadata is stored in file based
system.in 8.0.1 code is a file based system where as
metadata is stored in database.

4.in 7.5.2 we required operating system authentications. in
8.0.1 we requiree operating system authentications and
datastage authentications.

5.in 7.5.2 we dont have range lookup. in8.0.1 we have
range lookup.

6. in 7..5.2 a single join stage can't support multiple
references. in 8.0.1 a single join stage can support
multiple references.


7.in 7.5.2 , when a developer opens a particular job, and
another developer wants to open the same job , that job
can't be opend. in 8.0. it can be possible when a developer
opens a particular job and another cdeveloper wants to open
the same job then it can be opend as read only job.

8. in 8.0.1 a compare utility is avilable to compare 2
jobs , one in development another is in production. in
7.5.2 it is not possible

9. in 8.0.1 quick find and advance find features are
avilable , in 7.5.2 not avilable

10.in 7.5.2 first time one job is run and surogate key s
generated from initial to n value. next time the same job
is compile and run again surrogate key is generated from
initial to n. automatic increment of surrogate key is not
in 7.5.2. but in 8.0.1 surrogate key is incremented
automatically.a state file is used to store the maximum
value of surrogate key.

What are the important features of datastage?

1127

---

Differentiate between datastage and informatica?

1186

---

Explain how a source file is populated?

1370

---

What are the enhancements made in datastage 7.5 compare with 7.0?

1150

---

Have you used Unstructured data?

1323

---

Can you explain how could anyone drop the index before loading the data in target in datastage?

1504

---

Define project in datastage?

1100

---

What is the difference between operational data stage (ods) and data warehouse?

1246

---

Can we use target hash file as a lookup ?

3327

---

Define oconv () and iconv () functions in datastage?

1416

---

How do you generate sequence number in datastage?

1095

---

create a job that splits the data in the Jobs.txt file into four output files. You will direct the data to the different output files using constraints. • Job name: JobLevels • Source file: Jobs.txt • Target file 1: LowLevelJobs.txt − min_lvl between 0 and 25 inclusive. − Same column types and headings as Jobs.txt. − Include column names in the first line of the output file. − Job description column should be preceded by the string “Job Title:” and embedded within square brackets. For example, if the job description is “Designer”, the derived value is: “Job Title: [Designer]”. • Target file 2: MidLevelJobs.txt − min_lvl between 26 and 100 inclusive. − Same format and derivations as Target file 1. • Target file 3: HighLevelJobs.txt − min_lvl between 101 and 500 inclusive. − Same format and derivations as Target file 1. • Rejects file: JobRejects.txt − min_lvl is out of range, i.e., below 0 or above 500. − This file has only two columns: job_id and reject_desc. − reject_desc is a variable-length text field, maximum length 100. It should contain a string of the form: “Level out of range: ”, where is the value in the min_lvl field. My Question is how do you write the stage variable for reject rows.

2723

---

Explain datastage architecture?

1404

---

What is a folder? Difference types of stages?

1178

---

In Datastage, how you can fix the truncated data error?

1161

---