DSXchange

Field Marks in the dynamic array output. Try either:


or

Google would answer your questions, however...

ENU is the official abbreviation for "English" just like JPN is used for Japanese, etc.

Xalan and Xerces support XSLT and XML parsing / manipulation.

veera24 wrote:can any one explain me how to go to Administrator command window

Okay... Administrator / Projects / <select project> / Command.

veera24 wrote:I got the fatal error as "Abnormal Termination error cos of NLS".

I doubt any error message uses "cos". You'd need to post the complete / unedited log message for anyone to provide proper help.

Use DSJ.ME if the routine is querying the current job. Or use DSAttachJob (and DSDetachJob) to establish a handle to another job, then use that handle in your DSGetJobInfo call.

The online help lists all valid InfoType values for DSGetJobInfo regardless of the handle. Job Name is retrieved using DSJ.JOBNAME for example. No clue where you got J_PRGM_STATUS from.

[Thumbs][/Up]

How are you setting this? The 'not appropriate' problem usually comes from @FM characters in captured command output.

Read the help for Sequence jobs and Checkpoint Restarting. Sequence jobs need to Abort and show 'Aborted/Restartable' in order to do what you want. Master and failed Sub both.

/rul?

Your words: "I have to parametrize this". Get rid of UtilityRunJob, you don't need it and it unnecessarily complicates what you need to do. Use Job Activity stages and all of the 'restart' features the tool offers, it will then all happen automatically for you and you can reset the segments you need...

Why do you 'have' to parameterize this? Seems to me there's as much (or more) effort involved in creating and setting up the use of the parameter as there is in simply resetting the 'Master JS' from the Director manually once in a blue moon. [shrug]

Or perhaps you could do the same thing dsenv does:

Who cares if it generates 'duplicate' values within your data? All you care about is, if any aspect of the data changes, does the new CRC value differ from the old CRC value. In my mind, Ray's 'false positive' is the chance that the values in a single record would change and still manage to generate...

Not sure, but for some reason they wanted to drop the seconds from the timestamp as well so you can't just put the two pieces together, even without the microseconds. However, thinking about it, it can be made even simpler: Convert(":- ","",Arg1[1,16]:Arg2) Do one substri...