DSXchange

I need to write data in 2 columns of a Hfile in 2 steps 1st step : write results of an sql query (obtained with BCI SQlExecDirect, SQLFetch, ...) in a first column 2nd step : after subsequent processes, add a column with results of another sql query in a 2nd column. The key are the same for the 2 qu...

Hi Kasia, make one Hashfile and two Jobs. Job 1 writes as you describe and fills ID (which is key) and column: count1 Job 2: reads in a lookup the file and write the read column 1 and the new got column count 2. By this the file is updated so that you have finaly the result you want. Wolfgang > ----...

Job parameters for an XE/390 job can be specified in the "Parameters" panel of the "Job Properties". To get there select Edit --> Job Properties from the menu. The DataStage COBOL program reads the parameters from the dataset named in the DD statement specified on the "Parameters" panel. Mike. -----...

Hi Adam, as far as I have expiericend, I just started to install 5.2, you cannot use parameters for field and column-names. One question: Why do you want to change target-columnnames at all? If it is columns like: "Earning_May_2002"; "Income_May_2002" and so on you should better think about putting ...

All I am creating a generic job to update a table via and ODBC stage. However whilst the format of the source data is constant, the destination table name and columns change. I am trying to use parameters to identify the destination table and its columns. However whilst it seems this is possible whe...

Hi Rachna, Assuming this is the CA-IDMS product, its not supported directly in DS/390 but can be accessed using the External Source/target Stages. The external stages allow you to create your own program to access external products and link these into DataStage by creating an external routine in the...

One question
how i get the use of parameters
in the mainframe job v 5.2

thanks
--
_______________________________________________
Get your free email from http://e-mail.peru.com

Powered by Outblaze

Doris, Have a look in the &PH& directory in the relevant project. If you view the most recent file immediately after running the job it may provide more useful information. Regu -----Original Message----- From: Doris Zammit [mailto:Doris.Zammit@oit.state.nj.us] Sent: 15 August 2002 19:51 To: datasta...

Hi, I would like to know if DataStage can be used to extract from mainframe IDMS. The XE/390 speaks about integration with the mainframe environment. If anyone has used this feature, please let me know if this is possible and/or issues if any. The target datawarehouse database is Oracle. Thanks, Rac...

Hello group, We have been unsuccessful at loading an Oracle table. Here is the scenario..We have one large 50 million Oracle table. Our first OCI stage reads this table with a selection criteria of year 2002. Then we go through a transform stage that matches field for field and should write out roug...

Spot on. Thanks Regu -----Original Message----- From: Simon Fryett [mailto:sfryett@hotmail.com] Sent: 13 August 2002 14:07 To: datastage-users@oliver.com Subject: RE: add_to_heap() - Unable to allocate memory This does sound like a file creation problem, however you should check the max data segment...

When the DataStage Manager compiles a user-written routine, it creates a Catalog entry with a "DSU." prefix (DataStage User-written). You must call the other Routine using the prefixed name. In your case, in your VerificaExistencia routine you need a CALL statement using the prefixed name, for examp...

This is a topic for an orphaned message.

...And making sure your shared library path is correctly defined, etc. See the admin doco. Chris. Quoting Chris Kearns : > My understanding is that when you import ODBC metadata, DataStage uses > the information in the .odbc.ini file to determine how to connect to > your ODBC > source. When you impo...

My understanding is that when you import ODBC metadata, DataStage uses the information in the .odbc.ini file to determine how to connect to your ODBC source. When you import metadata via a native connection such as CLI, .odbc.ini is NOT used. Thats my guess as to why it works via ODBC for you. There...