Search found 15 matches
- Fri Jul 15, 2005 7:00 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Ouput from an ExecSh-run script as input to a job
- Replies: 9
- Views: 8096
- Fri Jul 15, 2005 6:07 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Ouput from an ExecSh-run script as input to a job
- Replies: 9
- Views: 8096
Hi Arnd and Ray, I tried both methods, but the same error occurs for both. Arnd - I added in the trim statement, and I get the same error. Ray - I was in fact running using a sequence already, but I was using a Routine Activity linked to a Job Activity. However I took your advice and changed the rou...
- Fri Jul 15, 2005 3:26 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Ouput from an ExecSh-run script as input to a job
- Replies: 9
- Views: 8096
Hi Arnd, My parameter type is string. I think it is probably like you say about stripping off the unwanted characters. Can you give me an example how to do that? Currently I am just using Ans= Trim(Output) Also, I am finding it difficult to output any additional log information so I can see what the...
- Fri Jul 15, 2005 3:08 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Ouput from an ExecSh-run script as input to a job
- Replies: 9
- Views: 8096
Thanks for that. I created a custom routine of type transform function, and in the code I set Ans = Output It seems this solved the initial problem, i.e. now I can pass a value, but I have hit another error, which may be to do with datatypes of syntax. The job parameter I am setting is of type Strin...
- Fri Jul 15, 2005 2:19 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Ouput from an ExecSh-run script as input to a job
- Replies: 9
- Views: 8096
Ouput from an ExecSh-run script as input to a job
Hi, First time posting, I had a search around but couldn't find the answer to this one, hope someone can help! I am using the ExecSh routine to run a shell script (which it turns executes sql). The script and routine work correctly, and in the DS Log I see: STGLoadADCQuality..JobControl (ExecSH): Ex...
- Thu Nov 25, 2004 6:09 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Problems with Oracle OCI Load Stage
- Replies: 7
- Views: 3352
- Thu Nov 25, 2004 12:50 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Problems with Oracle OCI Load Stage
- Replies: 7
- Views: 3352
Hi there I reset the job and only get the very explanatory information (NOT) Job DevFDMxStoreProcessedRecords aborted. Resetting Job DevFDMxStoreProcessedRecords. Resetting stage DevFDMxStoreProcessedRecords..xfmRecords. Finished Resetting stage DevFDMxStoreProcessedRecords..xfmRecords. Job DevFDMxS...
- Thu Nov 25, 2004 12:22 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Problems with Oracle OCI Load Stage
- Replies: 7
- Views: 3352
- Wed Nov 24, 2004 11:24 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Problems with Oracle OCI Load Stage
- Replies: 7
- Views: 3352
Problems with Oracle OCI Load Stage
Hi I am experimenting with the Oracle OCI Load Stage using direct path loading and I dont seem to get a simple job to run. It is a simple job with one Oracle Source, Transformer and the OCI Load Stage. I am using the AUTOMATIC load option and hence do not specify any Directory Path Control File Name...
- Wed Sep 29, 2004 7:06 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: NOFILES and MAXUPROC Kernel Parameters in DS 7.5
- Replies: 8
- Views: 7096
NOFILES and MAXUPROC Kernel Parameters in DS 7.5
In the latest DataStage Installation Guide there are 2 new kernel parameter configuration recommended, the MAXUPROC and NOFILES. For Solaris the following values are reccommended MAXUPROC - Minimum Value of 100 per CPU NOFILES - Minimum Value 1000 The upgrade/install guide does not state the purpose...
- Thu Sep 09, 2004 7:25 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DataStage Upgrade from 5.1 to 7.5
- Replies: 3
- Views: 2061
DataStage Upgrade from 5.1 to 7.5
Hi
I am planning an upgrade from DS 5.1 to 7.5 in a Solaris Environment. I wanted to hear if somebody out there had done a similar upgrade and if there were any issues/pitfalls with doing such an upgrade (that is not covered in the upgrade guidlines from Ascential)
Best Regards
Oli, 3 Sweden
I am planning an upgrade from DS 5.1 to 7.5 in a Solaris Environment. I wanted to hear if somebody out there had done a similar upgrade and if there were any issues/pitfalls with doing such an upgrade (that is not covered in the upgrade guidlines from Ascential)
Best Regards
Oli, 3 Sweden
- Tue May 18, 2004 9:47 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Migration to XML Pack 2.0
- Replies: 0
- Views: 855
Migration to XML Pack 2.0
Hi there I have one rather simple question (not for me tough). In one of my jobs that had XML pack 1.1 then I stated the output path for the XML files in the XML writer on the format #PROJ##OUTPUT_DIR#/Tre%@.xml The first column was the datestamp so I got the outputfiles Tre20040518.xml, Tre20040518...
- Tue Apr 13, 2004 5:15 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: ERROR during Installation of DS SERVER 7.1 on SOLARIS 2.8
- Replies: 5
- Views: 2723
- Tue Apr 06, 2004 9:11 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DataStage 5.1 to 7.1: Compilation error after migration
- Replies: 2
- Views: 2527
Minor change
This is a server job, not paralell
//OLI
//OLI
- Tue Apr 06, 2004 9:09 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DataStage 5.1 to 7.1: Compilation error after migration
- Replies: 2
- Views: 2527
DataStage 5.1 to 7.1: Compilation error after migration
Hi there I am currently upgrading DataStage from 5.1 to 7.1. I just migrated one of my projects to 7.1 and get several compilation errors that I did not get with version 5.1. Within Job Sequences I have I have several routines where I declare variables within the routine, an example is an Error Code...