Frequently Asked Questions

From a command line on the AS/400, type the command WRKACTJOB. This will list running jobs and tasks that are currently running on the system. Using your page up or down to locate the Subsytem/Job named MMAKERSBSD. Once this is located, arrow key to the far Left cursor field on the same line as MMAKERSBSD. Type option 5 in this field, and hit Enter. This will bring you to a "Work with Job" menu list where you should select number 10 from the list. Once this is done, it will show the job log text which indicates when the MMAKERSBSD started, and from which library it launched. If it reads: "...subsystem MMAKERSBSD in GDE19OND." Then the process was launched from the Guide 18 library, utilizing Guide 19 data files.

The LODRUN program that runs and upgrades MileMaker from Guide 18 to Guide 19 will covert all custom points to be usable for Guide 19 calculations. All user settings will be also saved and brought over to the newer version. If there are any issues with the upgrade the installer will give you an error notification.

During the restore and install of Guide 19, the setup program will read and process all avoided and preferred records from your previous installation. Because of changes in the highway network from Guide 18 to Guide 19, not all records may be able to be converted. A message will appear on your screen notifying you if this is an issue, and will allow you to view those unconverted segments.

If you choose to retain/backup Guide 18 during installation, you will need an additional 200 Megabytes of DASD on your system. This new install will be placed into GDE19OND, and the previous library will stay GDE18OND.

From a command line, issue the command WRKACTJOB and look for a job named MMAKERSBS with a child job of MMROUTER. If you do not see this job, call program CLMI000 to run the subsystem start up menu.

The major portion of the upgrade is a comprehensive highway data update. This essentially is a complete review of all the truck usable road network which MileMaker calculates routes. Updates to road restrictions, interstate systems, and other routes which commercial travel is allowed. The effect of such changes may shorten or lengthen certain routes in some areas of the U.S., Canada and Mexico. New geographic points (such as additional cities or locations) have also been included in the update.

We have retained all interface programs commonly used in Guide 18 to be supported in Guide 19. Any parameters passed to such programs will also be the same as they were before Guide 19. It is important to remember to add the GDE19OND to your library list or Job Description in order to call the newer editions of these interfaces. If you have questions regarding how these interface routines operate, please contact Technical Support.

Normally, this message appears when the system is out of transactions or when it had reached the end of its billing cycle (expired). From the MileMaker main menu (program MI001) select the Billing/Transaction Update choice and choose Transaction Usage Report. If you are out of transactions, please contact 1-800-234-4069 and select "Billing."

No. This version of MileMaker does not allow geocoding of custom points to the system.

There is an API program routine for both HHG mileages as well as Practical Routes. For mileage request, your third party application will need to call MI110I and pass the appropriate data structure with your origin and destination cities. Practical routes will require you to call MI335I. For complete details, please refer to your On-Demand AS/400 Technical Guide. Both RPG and COBOL record layouts are available.

Yes. ICC has developed a module that will call our interface for tariff miles and payroll operations.

The whole database and mileage engine has a small footprint. We recommend approximately 460 Megabytes of DASD. Data queues and temporary files may increase this requirement depending on use.

We suggest if you have a LAN/WAN which requires mileage information that you purchase a MileMaker SP32 or IntelliRoute Deluxe suite that offers DLL, ActiveX and Java.

If the route seems inappropriate, contact our Technical Support department at 1-800-234-4069 and we will have our database department verify the answer.

The custom setup enables slower systems to allocate a 15 Meg memory pool for the router subsystem. This will ensure that the MileMaker system will always have available memory when launching and ongoing throughout operation. Most RISC-based systems do not require this custom setup - thus the majority should accept the Default setup.

The main update to the IntelliRoute program will be the highway way data that is used to determine HHG and Practical Routes. It is a comprehensive review of commercial traffic road information which makes up the mileages and routes used for rating and dispatch operations. The update also includes an update to 5 digit ZIP codes.

We will attempt to preserve most of the user preferences and settings found in the Guide 18 installation and bring them to Guide 19. We advise you review your installation after the update is complete to verify your settings comply with your organization's needs.

Once you have updated the files on your server and/or shared drive letter where IntelliRoute resides, you will need to run the setup program inside the /Client folder off of the network drive. This will ensure your workstations have been updated to Guide 19 properly. Please consult the LAN Installation Guide included on your Documentation CD-ROM.

Due to dramatic changes in Practical Route data and the redrawing of maps used in SP32, we could not ensure that Avoided or Preferred segments that were once highlighted on the Guide 18 reappear after Guide 19. We anticipate, however, that more recent restrictions applied with Guide 19 information may not require users to avoid the same segments as they did in previous Guides.

Yes. Both will be supported and executed the same way as they were prior to the update.

HHG, or Household Goods as it is known, is the standard mileage guide that Shippers and Carriers use to negotiate rates for freight. It is the shortest legal highway mileage from two points, which an 80,000 trailer may take. The calculation does not consider time as a factor, thus the route may take more driving time, but accomplish less miles. The Practical Route is the most time efficient method of driving.Practical Routes tend to be the more desirable route of travel, and also may be used for calculating Fuel Tax reporting. Both are based on a 53' trailer length and 13'6" clearances.

An easy way to select SMB is to go to the ROUTES menu. Then select HHG Full Route with SMB or Practical Route with SMB. This will then display the city entry dialogue box where the "with SMB" radial button can be selected. Once the route is calculated, State Mileage for each state traveled will be at the lower left of the itinerary screen.

Be sure and check the format of your city. Points need to be entered as City Name-comma-two letter state abbreviation. There is no space between the comma and the state code. (Example: ST LOUIS,MO)

You may also enter a 5 digit ZIP code, SPLC, Latitude and Longitude, and junction as a location entry.

When entering Mexican points, you must also enter a state code for the respective state that the city you are using resides. All Mexican points are to be entered in the same manner that U.S. and Canadian locations are used. For a complete description of state abbreviations, choose the REFERENCE menu, and select Abbreviations.

For example: Mexico City must be entered as "Mexico City,DF" This indicates it is in the state of Distrito Federal.

Some ZIP codes have multiple postal regions. The error value indicates that multiple cities share this ZIP code address. To ensure that you always receive a mileage from this area, you may want to use Default ZIP Code processing. Within the MileMaker program, go to the FEATURES menu, select Route Processing Options, and turn on Default ZIP Code processing. This will enable the system to select the default city where the post office is located. For Practical Routes, this may be a junction or suburb nearest the actual ZIP Code district.

MileMaker SP32 is not an Address to Address application. We do offer a Streets Module within our IntelliRoute suite of products. Please contact your Rand McNally account Manager for details.

Within MileMaker, go to the VIEW menu, and select Show Toolbar. This will toggle the visibility of the large icon shortcut keys.

MileMaker SP32 has a DLL library which may be opened and passed origin and destination pairs. This library, MILES32.DLL, is located in the C:\Program Files\Rand McNally\MMAKER32\bin folder. Examples in Visual Basic and C++ on how to call the DLL from an outside program are available within the MMAKER32\Examples\ folder.

When you installed, you had the opportunity to install the DLL and Example files components. If you need these resources and API, please contact our Technical Support Department at (800) 234-4069 and we can arrange sending you the appropriate software.

You will need to contact our Customer Service department or your Account Manager to authorize another installation or re-load of the MileMaker software. Both are available at 1-800-234-4069.

This problem is usually attributed to inadequate permissions for the user running the application. Please ensure that the folder that SP32 was installed has Full Control access granted to users.

Also, the Registry Key HKEY_LOCAL_MACHINE\SOFTWARE\Rand McNally on the workstation needs to grant "Full Control" to users who execute the program at the desktop level.

To turn off the printing of these sheets, go to the FILE menu, select Print, and then uncheck Route Summary Page and Overview Map page. You may also click the drop down menu to the left of these checkboxes to specify what would want to appear on the printer.

Optimization will only work once you have 3 or more points in a route. The purpose is to generate a stopover order that is the most time efficient regardless of how the points are entered. You may also specify a particular destination that will ensure that the trip ends at a certain city.

Since HHG is a rating mileage, drivers generally do not actually drive the itinerary generated. The Practical Route, however, is a more driver accepted path to a destination that is why maps are provided.

The * denotes the default city choice for an HHG mileage calculation. The city with this note is typically the city where the post office is located. The # denotes the default city or location for Practical Route inquiries. The Default ZIP code processing feature will utilize these selections when it is enabled.

MileMaker runs on the mainstream flavors of UNIX. This includes SCO, AIX, Solaris, Linux, and HP-UX. The minimum requirements are supported as per manufacturer recommendation:

HP-UX: 11.1 (both PA/RISC and Itanium Releases)
Solaris: 10
SCO Open Server 5.0.7
SCO UnixWare 7.1
IBM AIX 5.2
RedHat Linux Enterprise Server 4
Suse Unix Enterprise Server 9

If you upgrade to the new Guide, it would be advised that you contact your software vendor that installed MileMaker or your traffic software. Because we are replacing files, operations may have to be temporarily shut down. If you have such a third party software or a special operating system configuration that automatically regulates Rand McNally programs such as routproc or our aca, please consult your interface software vendor or system administrator.

The updated ACA is completely backward compatible. It still supports the named-pipe (to_server and from_server request files), non-named pipes, as well as the TCP/IP function flag. The directory structure will remain the same as before. The only actual change is that you can pass Latitude and Longitude coordinates in place of city names. This obviously does not require a state or ZIP to be passed with the two decimal values. They are to be used only in practical routes.

The CD-ROM has been saved with relative pathnames, therefore you can load the updated to any directory structure. Historically, Guide 18 files have been installed to /usr/micro/g18 by default. To install the product into another directory, please see later FAQ for instructions.

The update program, /g18/exe/update19 will bring over user accounts, user conversion records, avoid/preferred segments, and other preferences and previously existing parameters set in the Guide 18 base install.

To check the presence of routproc's activity on your system you can use the ps command. Please note the use of the character "pipe," the | above the backslash key.

Example: the command ps -ef |grep routproc will return a screen as below:

root 323 1 0 Nov-09 ? 00:00:09 routed
micro 4441 4429 0 10:44:09 ttyp0 00:00:00 ./routproc
micro 4444 4429 0 10:44:23 ttyp0 00:00:00 grep rout

Notice above that on the right, routproc is listed. It was started by user micro, with a process ID of 4441 on today's date at 10:44AM, on tty number ttyp0. If no listing of "routproc" comes up on the far right, routproc is not running. The above example is based on SVR4 compliant UNIX flavors. Please consult your system administrator to re-launch the router process or contact technical support at (800) 234-4069.

Same as the method of checking for routproc's operation in the previous FAQ, you can use the ps command at the UNIX prompt.

See below:

Command line: ps -ef |grep aca Provides the following:

micro 4455 4429 0 10:49:45 ttyp0 00:00:00 ./aca

Notice above that on the right, aca is listed. It was started by user micro, with a process id of 4455 on today's date at 10:49AM, on tty number ttyp0. If no listing of "aca" comes up on the far right, the aca is not running. You may see it listed as: aca tcp & The "tcp" flag is to denote when the aca is using TCP/IP for communicating. (Sometimes with or without the "&" listed or tagged as a background process.)

The fully installed product is roughly 80 megabytes. Some flavors of UNIX will use larger amounts of disk space than others.

Be sure and consult your system administrator of your system if MileMaker appears not to operating properly. Some transportation software packages and databases will have automated scripts to manage routproc and aca. For instructions on manually resetting these programs, please contact Technical Support at (800) 234-4069.

The ACA application provided with the product has multiple levels of communication. MileMaker can utilize named-pipe (to_server and from_server request files), non-named pipes integration, as well as TCP/IP listening facilities.

Yes, we have binary compatible distribution that will run in either a 32 or 64-bit kernel configurations of AIX 5.x operating system. If you have questions about your copy of MileMaker, please call technical support.

We have a number of business partners who provide transportation software solutions in conjunction with MileMaker. Please visit our Interface Partners page, or contact us at (800) 234-4069.

Since the distribution tapes are created with full pathnames, you will need to extract the contents to either the default directory first, or create a symbolic link to point to another filesystem other than /usr/micro. You must also modify the file profile.19 which loads the appropriate environment variables the for application to operate.

Below is an except of the profile.19 file:

NETWORK_PATH=/usr/micro/g18/data/network.19 DATA_FILE_PATH=/usr/micro/g18/data/geo.19 STATE_IND_PATH=/usr/micro/g18/data/stateidx.19

These environments must be changed to point to the new location of MileMaker's files. A change from /usr/micro to /apps within profile.19 may look like this:

NETWORK_PATH=/apps/g18/data/network.19 DATA_FILE_PATH=/apps/g18/data/geo.19 STATE_IND_PATH=/apps/g18/data/stateidx.19

This is probably caused by an incomplete load of the environment variables. Be sure and executing the profile.18 prior to launching any and all copies of our executables. Be sure you are in the /usr/micro/g18 directory and type:

. ./profile.19This is a space between the two periods.

There are a few output log files that both debugging as well as standard errors are reported when running MileMaker executables. The following are brief identifiers of such files. Please note all are in the /usr/micro/g19/data default directory.

FILE REPORTING
error.log General errors, logs routproc, main, milemaker & demon.
reader.log ACA log file. Usually interface issues
server.log ACA log file. Integration flag
taskrout.dat The routproc log file

If you experience unusual errors or program behavior, please contact Technical Support.

Generally, the /usr/micro/g18/data folder needs Read and Write permission to all users or groups of users that need access to MileMaker. The /usr/micro/g18/exe folder needs Read, Write, and Execute permissions on its files so that whoever needs to run the program will have success.

Please consult your system administrator for changing such permission in your organization. -rwxr-xr-x 1 micro staff 186208 Apr 16 1999 routproc
-rwxr-xr-x 1 micro staff 19680 Apr 16 1999 start_urmm
-rwxr-xr-x 1 micro staff 29084 Apr 16 1999 tcp_client /usr/micro/g18/exe #

We can reset your password so that you can regain access to MileMaker. Please contact our technical support department if someone is not available in your organization to locate your MileMaker login information.

An easy way to check transactions is to do the following steps:

1. 
   
2. Login as root or the appropriate user.
3. Type: cd /usr/micro/g19
4. At your prompt type: . ./profile.19
5. At the next prompt: cd exe
6. 
   This will bring you into the prompt.
   
7. Type: ./main
8. 
   This will bring up the MileMaker screen.
   
9. Hit then continue.
10. Login to the master menu with your defined ID and Password.
11. Select option "M" for Maintenance Menu
12. On the Maintenance Menu, enter the password
13. Select "Transaction Usage Report"

Canadian Postal codes contain 6 characters. However, you can submit all 6 together; for example: N5P 4B1. Or, you can enter the field with a space in between: N5P4B1.