PC*MILER|AS/400 MVS User’s Guide 35
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.IE:140<space>150<space>161
7.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 Trip” message. The VA request type can be
used to produce lists of potential matches to partial spellings or ZIP
codes.
Validation Request:
Var Name Len Value Description
Extended Format
REQ-TYPE 2 VA Validate Stop or Address
REQ-REF 10 Output Queue Name
(ALK uses “Q” plus job number)
Filler-8 8
Force Pick List 1 P=Force Pick List or Blank (Position 20)
Filler-7 7
NewÆ
ÆÆ
Æ MVS Parms 10 (positions 29-31) 3 bytes PC*MILER Version
7 bytes not used
REQ-CIT 70 70 bytes each left justified
38 byte maximum ci ty name
1 byte comma (optional)
2 byte state abbrev
1 byte comma (optional)
13 byte county name (optional)
or for Streets
1 byte semicolon ; followed by street address
Examples
Warminster,PA,BUCKS
Warminster,PA;1174 NASSAU ROAD
18974
Lat/long format should be 1234567N,1234567W
5 digit zips only
Canadian Postal Codes use the format L#L<space>
#L# (add-on data module)
For Standard Position Location Codes SPLC plus
the number (add-on data module)
Filler-CIT 630 blank