Resending CDN Order
 		Previous Topic  Next Topic 

Resending CDN Order


From TCL on the customers machine we can look to see what orders may be stuck out there we do that with the command;


CT TABLE OC.SENDLIST


An order may appear with the format;


1-0153013 37327*14145*4*e560


After the order number the 37327 is the time (TME in TCL) the 14145 is the date (DTE in TCL) the 4 in this example is the times the order has tried to be sent and the e560 is the error code, in this case this is an invalid username/password issue.


The times the order has been sent works as follows;


<5 Every Minute


<10 Every 15 Minutes


<20 Every 60 Minutes


<25 Every 24 Hours. It will give up doing this after 25 days.


By editing the times the order has been sent we can force it to be resent, this is done by;


U TABLE OC.SENDLIST


The times sent can be edited to say ‘1’. Then by typing;


WATCH CT TABLE OC.SENDLIST


We can see the order get resent, it will say no items present when these are sent through.


The background process SEND.OC.SLEEP has to be running on the customer’s machine for an order to be sent (back to us).

To start the Perfection process on the customer’s machine, the SEND.OC.SLEEP, type CHECK.SEND.OC.ACTIVE.


If you see the SEND.OC.SLEEP running you also need to tandem to it to ensure there is not additional problem with it. If it appears to be locked or inoperative still then you can stop and start the process in the same way we do for PDA’s. (In cust on line start/stop order import process)


The SEND.OC.SLEEP process deals with order confirmations coming back to perfection and on to PPG, the col.transfer process deals with retrieving the orders from us. Thus if the customer is not receiving orders from us then it is the col.transfer process you will have to tandem too to make sure it is working and again if it is not it can be restarted from the customer online menu. It has been seen to require more than one restart at times so after you restart it tandem back to ensure its actually running.


On the 10.1.1.11 machine also check to make sure the PerfUtilService is started from services.