DSXchange

chulett wrote:contact your official support provider, something I think you'll need to do regardless now that you've manually deleted

even more of the project.

This sounds... familiar. Perhaps a carefully chosen search would turn something up.

I guess that is indeed what I'm proposing, assuming you're still going the way you asserted earlier and using job parameters that are set to $ENV as their default value. There's no reason to pass them in on the command line in that case and if the script can set them in the job's environment painles...

Can't be much help with your query but more confusing were the responses, where does date conversion come in to it? No clue, I only added my date comment after the first response specifically complained about not having IConv/OConv to do dates in PX. :? And yes, should have mentioned the same thoug...

You still shouldn't have to "resolve these in each controlling sequence" if by "resolve" you mean "set". Still unclear what you have in place in the way of job control, meaning I'm still wondering what is actually running your sequence jobs across your enterprise. If it...

I would think that they are but honestly I can't say for sure. You'd probably need to confirm or deny that with your official support provider.

Saw all those other ".H" files there and forgot they stuck the ones you're looking for off in each project directory for some reason:

./dsinclude/JOBCONTROL.H

Sure, it's in the $DSHOME/INCLUDE directory.

Oddly enough, my code is G09HULETT if anyone would like to use it to save 100 smackers US.

Looking at the routine code, you'll see you've gotten past the "open" step to the actual writing step, which to me would typically mean a permissions or space issue there. Any chance that filename already exists there? (probably not seeing as now it is timestamped) Can you try putting Exec...

Go to Search, make sure Exact Search is selected and search for "This Jobtype is not currently runnable on this platform" - you'll get 19 matches.

Simple enough to manually add the 'phone_type' columns (x3) to the data before the pivot and then drop any pivoted rows where the number was null post-pivot.

Your best bet is to optimize the source query and presize the hashed file (Minimum Modulus) properly.

I don't believe so, AFAIK you'd need to create a job to copy the dataset and drop the records you no longer needed during the process.

That's your problem, then, the old projects are gone and I would assume you'll need to reinstall the 7.5 version. Best to check with your official support provider and I hope you have a backup.