DSXchange

Work around was to use the sql server TRY..CATCH structure so that the stored procedure sql action could fail but the stored procedure did not fail

In our new DataStage environment, there have been a number of Message handler (.msh) files that were created independently and with files name structured like abc def.msh I now wish to create a consolidated project level file with a name like project.msh Would the steps be 1. In Unix (Dev environmen...

I have now developed a number different jobs calling SQL server stored procedures, all the jobs have run successfully with returning ProcCode 0 I now want to design my job to handle when the sql server stored procedure fails. I believe sql server returns ProcCode and ProcMess My example job Simple s...

It was not my intention to use the stored proedure stage in place of a function.

The intention of the exercise was to simply to test using the stored prodedure stage, for the exercise I created a working sql server stored procedure which in this case returned a known value ie Day of week

Job is now working Stored Procedure CREATE proc [dbo].[uspGetCurrentDayOfWeek] @Result varchar(200) OUTPUT as select @Result = ( DATENAME(dw, CAST(DATEPART(m, GETDATE()) AS VARCHAR) + '/' + CAST(DATEPART(d, GETDATE()) AS VARCHAR) + '/' + CAST(DATEPART(yyyy, GETDATE()) AS VARCHAR)) ) GO SQL Server St...

Yes - I created and tested the stored procedure and it works as desired, before I started on the DataStage solution.

Once On have my SQL Server/DataStage solution working I be expanding the solution

Thank you Andy - I have made some good progress Latest solution version ran without warnings - but no result value SQL server stored procedure changed to CREATE proc [dbo].[uspGetCurrentDayOfWeek] @Result varchar(200) OUTPUT as select ( DATENAME(dw, CAST(DATEPART(m, GETDATE()) AS VARCHAR) + '/' + CA...

I have already searched the DSX forums relating to executing SQL server stored procedures - yet I am still unable to create a working example. Simple Example. SQL Server stored procedure return current Day of week CREATE proc [dbo].[uspGetCurrentDayOfWeek] @Dummy varchar(200) = null, @Result varchar...

Separate tests confirm that the Format is correct.

Given that the input data is in the correct format, to completely test the TimeStamp value, I needed to test that the value was a valid TimeStamp value

Thank you for your reply Ray. The Format can be validated. The additional Data Rules Stage test I am aimming for is that the Time component is valid For Example expected TimeStamp tests "2014-11-03 06:42:00" -- Valid "2014-11-33 06:42:00" -- Invalid "2014-11-03 26:42:00"...

Have just started using the Data Rules stage, with only a couple of jobs done so far.

I now have to validate a TimeStamp value (read as a string)

Has anyone validated a TimeStamp with the Data Rules Stage

Thanking you all in advance

The ExeSH Before job subroutine is basically ..../dsjob -run ... -mode RESET -warn 0 -wait JOB_A; .../dsjob -run ... -mode NORMAL JOB_A It appears that I have not -wait on the second instance I will add the required wait So the expectation is that only when JOB_A has finish that the main job will th...

A team member has the following issue with expectation of a Before-job Subroutine completing before the main job is run The team member job is slightly different to my original job - I do not seem to have the same issue. The ExeSH Before job subroutine runs two dsjob commands. The first occurrence i...

I have not yet rasied a support PMR - I will now

I have been away from the office for a while

I have attempted to schedule a repeating job (Every Thursday at 12:06 PM). The job never ran at the secheduled time