DSXchange

Fair enough. In hindsight while I didn't generally have issues with 'complex' sequence jobs, I did have an issue with one and oddly enough it also involved a loop. It had been working fine and then went sideways after I tweaked some innocuous thing. Now that I think about it, it started looping once...

Somehow in all those shenanigans you corrupted or removed part (or all) of the log's dynamic hashed file. The reimport recreated that for you.

First (for me at least) you'd need to clarify what exactly it is you are trying to accomplish. For whatever reason, neither your original post nor your fifo solution make much sense to me as I'm not really sure what you mean by 'assigned this value dynamically to the dsadmin commands'. Can you expan...

As they say - TNSTAAFL. This decision may very well have saved 'lots of efforts' now but will hurt you in the long run as it really is not a Best Practice especially when painted on with such a liberal brush. As noted you should allocate time later in the project to do this the right way before it b...

From a TCL prompt or using dssh:

Sainath.Srinivasan wrote:If ^M is at the end of the record, it may be due to DOS type record termination. Setting this property will handle it properly.

This, typically. But as Arnd noted there are various ways so it really depends on the where and the what of it.

So is this actually a Server job? Yours are usually PX ones and we are in the PX forum after all, hence the question.

That's... odd. I have no idea what would cause something like that or why you'd have to take such drastic action to get it to loop properly. One suggestion would be to look at the Job Properties tab with all of that loverly generated code and step through that, see if anything there lets you know wh...

So 'promote' the message handler from the job along with it. They're stored locally in the one of the job specific folders (SC?) with 'msh' in the filename from what I recall.

It's actually $APT_STRING_PADCHAR and the default is the null you are seeing. If it doesn't exist, add it as noted set to a space. Seems like you could do as you said - extract, trim, reload - or you could probably just do this via sql in your target database without all that.

Disable? No. Prune? Yes. Easy enough to create a cron script to run in off hours and delete all files over X days old.

Durga, please start your own post so we can have all of the particulars of your version of this problem since I doubt it is exactly the same version, hardware, O/S, etc as this three year old post.

The words you are looking for are "positive" and "negative", not "+ve" or "-ve".