User`s guide

PC*MILER-AS/400 MVS User’s Guide 48
MVRESP External data structure for receiving mileage output
MVSEND2 Sample external data structure with Borders Open/Closed and Use Ferry Distance Fields
MTSEND External data structure for sending mileage requests
MTSEND2 Sample external data structure with Borders Open/Closed and Use Ferry Distance Fields
MTRESP External data structure for receiving mileage output
The programs MVSIINQ and MTLIINQ contain two subroutines that can be used to
integrate miles with other transportation software. The subroutine SNDREQ sends
mileage requests to PC*MILER and the subroutine RSLT receives mileage results
from PC*MILER.
The PC mileage server can respond to a total of five types of Mileage Requests:
Mileage:
VN = Version of PC*MILER-AS/400 Multi-Version Switch being used by the server
MV = Versions of PC*MILER Highway Data available.
VA = Validation that a stop (City, ZIP code, etc.) is recognized by
PC*MILER or a list of possible matches to a partial city or ZIP code
MI = Total mileage for up to 30 stops
SM = Total mileage for up to 30 stops broken down by state or province
HS = Turn-by-turn driving instructions for up to 30 stops
The PC mileage server responds with the following types of returns:
VR – Version of PC*MILER or PC*MILER|Streets running on the PC
NS – Version(s) of PC*MILER running available.
PL – Good/Bad Stop or a ‘pick list’ of potential matches
CP – Total Miles for a trip
SR – Total Miles for a trip broken down by state or province
HR – Turn-by-turn driving instructions or “highway segments”
VN returns a VR
MV returns a NS
VA returns a PL
MI returns a CP
SM returns a CP and an SR.
HS returns a CP, an SR and an HR