User`s guide
PC*MILER-AS/400 MVS User’s Guide 52
Y Exact match
N No match
Force Pick List Pos 21) Echoed from Request P or Blank
Filler-1 1 1 blank
RESP-Seq 4 Pos 23-26) Sequence for multiple responses
RESP-ERR 2 Pos 27-28 Error Code
E2 Place not found
EA = invalid or not found server ID
EB = invalid trip ID
EC = error writing to queue
ED = Incomplete Record/Header
RESP-MVS 3 Pos 29-31 (3-character PC*MILER Version)
Pos 32-38) Not Used
RESP-CIT 980 Array of 14 places 70 bytes each left justified
or
Error message if there is a problem
Filler 15
8.2.3 Point-to-point Miles (MI) Request and Response
1. (Request) The following are field parameters for requesting miles. The purpose
of the Mileage request is to allow the host application to retrieve point-to-point
miles. This type of request could be used for a quick mile lookup from a host
inquire program or for running several stop-off points in a batch environment.
The host dispatching software could generate this request when a new trip is
established.
Var Name Len Value Description Extended Format
REQ-TYPE 2 MI Miles request
REQ-REF 10 Output Queue Name
(ALK uses ‘Q’ + the job number)
Trip Options Positions 13-22 Request Position
REQ-OPTION 1 Pos 1) S=Shortest
P=Practical
N=National/Practical
T=Toll Discouraged/Practical
5=53’ Trailer/Practical
B=Toll Discouraged/Practical
C=National Network/Practical
D=53 Foot Trailer/Practical
E=Toll Discouraged/National Network/Practical
F=Toll Discouraged/53 Foot Trailer/Practical
G=Toll Discouraged/Shortest
H=National Network/Shortest
I=53 Foot Trailer/Shortest
J=Toll Discouraged/National Network/Shortest
K=Toll Discouraged/53 Foot Trailer/ Shortest
1 Pos 2) M or K for miles or kilometers
1 Pos 3) R=resequence stops
H=hub leg miles
F=resequence stops fixed destination