DSXchange

Hi Iin our environment the production jobs are managed by a totally different group who do so for the entire firm for all production jobs. The only reason we want to do this is because we could end up changing datastage jobs due to failures and currently, the production support staff ( who are the o...

Also check out the Ascential web site, Education section. They offer, among other things, a MetaStage Best Practices class. ----- Original Message ----- From: Kenneth Bland Date: Tue, 1 Apr 2003 12:24:41 -0800 (PST) To: datastage-users@oliver.com Subject: Re: DataStage best practice to capture ETL m...

Could I counsel your revisiting the reasons why you want to do this? Is there an alternative approach, whereby a job in the current project could operate on files, tables, etc., associated with the other project? ----- Original Message ----- From: gxganes@regence.com Date: Tue, 1 Apr 2003 11:51:23 -...

Thanks, Andrew. Scott >>> 03/31/2003 3:14:30 PM >>> Scott, The java stage is an optional stage for the new release of datastage, so you wont have it as yet. It allows a java class to become a source (to fetch data and return it to the datastage stream), a transform (to allow a row of data to be pass...

Check www.DataStagExchange.com, they have a MetaStage forum and Barbara Nichols moderates that discussion. She is the foremost expert on MetaStage. -Ken --- Malathi_Vellanki@mckinsey.com wrote: > Hi, > > Any of you have document outlining DataStage job > development best practices > to capture ETL m...

Thanks everyone for the replies. I gather that it is not possible to do it from a datastage job to call a datastage job from in another project. We are well parameterised for Hash File and other paths. Ofcourse, these questions have opened up some issues which we never thought about. Looks like we n...

Hi, Any of you have document outlining DataStage job development best practices to capture ETL metadata in MetaStage? I appreciate if you could share this document with me. Thanks. Malathi. +---------------------------------------------------------+ This message may contain confidential and/or privi...

Anyone know what this error means ? "CreateOrderedMasterDataHashFilesJob.: RT_STATUS Record for wave 1 not found." The job is running, but when i click on it in the director it gives me this error, and also when i open it in the designer. In the director i cant stop it - only the run and reset butto...

Ive got to agree, if your issue is with how components are delivered to production you really should be using the version control tool. The developer or a release coordinator can build the required emergency fix release by importing it into the Version Control tool, they pass the batch number onto S...

You can see how the error handler is used by looking at the job control code for a compiled sequence job: h$1 = DSAttachJob(jb$1, DSJ.ERRNONE) If (Not(h$1)) Then msg$ = DSMakeMsg("DSTAGE_JSG_M_0001Error calling DSAttachJob(%1) %2", jb$1:@FM:DSGetLastErrorMsg()) msg$id = "@GetCustomers"; GoTo L$ERROR...

certainly you can do this by shelling out to uv, then doing logto, then exceuting run cmd john Craig Hulett wrote: >I dont believe so, at least not directly. Now perhaps someone like Ray or >Ken can give you some way to accomplish that down in the underlying engine, >but typically your jobs only kno...

we also recd this info mess when upgrading and permissions were not set correctly for read of DS_JOBS etc Surendranath Gujjala wrote: >Hi , >I have a datastage job that is giving following when I try to open in >designer. > > " Item has no design time information " > >But Im able to run the job. > >...

The answer will be different depending on whether youre talking about server jobs, mainframe jobs or parallel jobs. It will also depend on how thorough you have been in parameterizing all those factors that vary between projects and, as Ken mentioned, how you have set up any hashed files you may be ...

This is a topic for an orphaned message.

Theres 2 issues to deal with for what youre trying: (1) If you used hash files local to a project, ie you did not specify a path (recommended practice) or you left the "account" (really the project) blank, then running a job in another project means that the hash files are not "visible" to other job...