User`s guide

PC*MILER-AS/400 MVS User’s Guide 50
8.2.1 PC*MILER Versions Available (MV) Request and Response
It is recommended that you maintain a list of available versions via the MV
request type. Within the MV return is a space-delimited list of available versions.
For example: 190 200 21T 21W 22T 23T 24T 25T 26T 27T
NOTE: The PC*MILER-AS/400 Multi-Version Switch PC mileage server is
designed such that if the mileage server (as400.exe) loses connection to a
particular version of PC*MILER, the affected version will be removed from the
list.
Version Request:
Var Name Len Value Description
REQ-TYPE 2 MV PC*MILER Versions Available
REQ-REF 10 Output Queue Name
(ALK uses “Q” plus job number)
REQ-PARMS 10 Optional
REQ-SEQUENCE 4 Optional
REQ-ERROR 2
REQ-MVS 3 Optional
REQ-FILL 237 Blank Fill
Total 268
Version Response:
Var Name Len Value Description
RESP-TYPE 2 NV Stop pick list
RESP-REF 10 Output Queue Name
RESP-PARMS 10 Trip Parms
RESP-SEQUENCE 4 Always 0001
RESP-ERR 2 Pos 27-28 Error Code
RESP-MVS 3 Pos 29-31) PC*MILER Version
RESP-FILL 7 Pos 32-38) Not Used
RESP-VERSIONS 228 Array of space delimited, left justified, 3 character
versions; e.g. 140<space>150<space>161
8.2.2 Stop Validation (VA) Request and Response
The following are field parameters for stop and (for PC*MILER|Streets users)
street address validation. A stop can be a city/state pair separated by a comma, a
ZIP code, a latitude/longitude point or (with optional add-on modules) a Canadian
Postal code or SPLC (Standard Position Location Codes). PC*MILER|Streets
users may include street addresses.
Validation requests are important because error reporting in mileage requests is
limited to the first two stops of a trip. If your bad stop is lower in the list of stops,
you will not be told which is the nonvalid stop, you will get a generic “Can’t Run