Attached below are BAT file back ups for our road net server. These files transport the data needed for our current (3/14/2022) routing server.

If the router believes he has bad files, then you can run the following commands to generate a new file for him.  jrun: routlist Final Route = N Re-Route = Y Route Day = (Day value of the week, Sunday is 1.) Release all routes e to exit jrun: rnetord Enter tomorrows date (Format MMDDYY) Enter same route day as entered above jrun: purscan Enter AES in all caps Enter 4 e to exit After this final step has ran, you can inform the router that he is able to retrieve the file using the icon on the roadnet server.

Router - The individual responsible for directing what trucks go where SSIT - The second shift IT individual who helps process files SSIT - Generating the file for the router To Generate the files for the router to begin his process, enter these commands in our Unix System. jrun: routlist Final Route = N Re-Route = Y Route Day = (Day value of the week, Sunday is 1.) Release all routes e to exit jrun: rnetord Enter tomorrows date (Format MMDDYY) Enter same route day as entered above jrun: purscan Enter AES in all caps Enter 4 e to exit Router  - Consumes the file After the final step has ran, the router can run his BAT file on the Roadnet server. The bat file consumes two files /users/data/roadnet/orders.r /users/data/roadnet/rnetcust.txt Router then does his work, adjusting routes and exports his routing file.   Router - Exporting file After the router has finished making his adjustments, he will export the following files  from the Roadnet server into the Unix Server: /users/data/roadnet/ORDERS.S /users/data/roadnet/EXTENDATA.TXT SSIT - Consumes new files, generates new files and sends to pallet builder To consume the files the router has sent back, run the following programs: jrun: routlist Final Route = N Re-Route = Y Route Day = (Day value of the week, Sunday is 1.) Release all routes e to exit This program will consume the changes made to the file by the router. The next program is used to push these changes to the dock office to print the labels used for picking product.  jrun: runlab2 enter truck number for specified route enter route number enter route number Repeat these steps for all routes finished (the router will let you know which routes are good to process with the runlab2 program. Generally, these are given in three groups (Columbus, Detroit, Locals) Once all routes are completed, you must run the following program trun:wms-orders3 This will push all generated files from the runlab2 file over to pallet builder. Pallet builder is the website used to print labels for our third shift crew to pick orders off of. 

This is a document that contains all known reasons as to why a customers order would be "below the line" on the final route list. A customer could be in status 85 - this means they are an inactive account. I don't know how to check this. I will update this after I speak with Joel Watters. Their order was below the minimum dollar amount If no dollar minimum was set when their account was set up, it will be on hold by default. They are an off day routing  The router will know how to check this. They were originally on the back order report This report can be found here on the Unix server: /users/data/curtze1/backflist It can also be found here on the network drive: T:\Information Technology Drive\Automation\BackOrderList\Daily Report The Second shift unix operator did not consume the file that was sent from the Roadnet server into Unix. This can be fixed by rerunning the routlist program and hitting option J before exiting the program. A possible issue could be the router not sending the file to Unix, this would look identical to the step above. To confirm the router sent the file to the Unix server, check the time stamp on this file: /users/data/roadnet/ORDERS.S

If you receive an error when trying to load the file from Unix. Check this file in the Unix server: /users/data/roadnet/orders.r This is the file that is moved with the BAT file on the roadnet server's desktop. If the file listed above looks similar to the image listed below, follow these steps. Run - jrun, rnetlod rerun programs to generate files for routing If normal week day, run these steps: jrun, routlist jrun, rnetord jrun, purscan if it is for saturday delivery: lmrun, dalbydte jrun, routsat jrun, satrnetord if further instructions are required, they can be found in Unix Procedure files, located here:  T:\Information Technology Drive\Documentation\NHB Procedures