User’s Guide Multi Version Switch 27 Technology Beyond Miles
ALL RIGHTS RESERVED You may print one (1) copy of this document for your personal use. Otherwise, no part of this document may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language, in any form or by any means electronic, mechanical, magnetic, optical, or otherwise, without prior written permission from ALK Technologies, Inc. Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States and other countries.
Table of Contents PC*MILER® Product Line End-User License Agreement................................................... i Notes and Updates for Version 27 – Please Read................................................................1 1.0 Introduction ...................................................................................................................6 2.0 System Requirements..................................................................................................10 2.
Appendix B: Configuring an N/S Router For Use With PC*MILER-AS/400 .................70 Appendix C: Configuring AnyNet On the AS/400 ............................................................74 Appendix D: Configuring Client Access Express For PC*MILER-AS/400 .....................75 Appendix E: The Sleep Feature For IPL Drop Outs ..........................................................80 Appendix F: Multi-Version Switch INI Settings ...............................................................
PC*MILER-AS/400 MVS User’s Guide i PC*MILER® Product Line End-User License Agreement 1. Grant of License: Subject to the terms, conditions, use limitations and payment of fees as set forth herein, ALK Technologies, Inc. (“ALK”) grants the end-user (“you”) a license to install and use the PC*MILER solution(s) (including traffic data subscriptions) you have purchased (“PC*MILER”) on a single personal computer.
PC*MILER-AS/400 MVS User’s Guide ii connectivity products), or install or use PC*MILER on a network file server, without first notifying ALK, executing a written supplemental license agreement, and paying the license fee that corresponds to the number and types of uses to which access is to be allowed. 6.
PC*MILER-AS/400 MVS User’s Guide iii ALK will replace defective media during the warranty period at no charge to you unless the defect is the result of accident, abuse, or misapplication of the product. C. THE FOREGOING WARRANTIES ARE IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITING THE GENERALITY OF THE FOREGOING ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. THE PC*MILER PROGRAM, DATA AND DOCUMENTATION IS SOLD "AS IS".
PC*MILER-AS/400 MVS User’s Guide iv 14. Obligations on Termination: Termination or expiration of this Agreement shall not be construed to release you from any obligations that existed prior to the date of such termination or expiration. 15.
PC*MILER-AS/400 MVS User’s Guide 1 Notes and Updates for Version 27 – Please Read Starting with Version 27, socket software is now automatically installed. Instead of running a self-extracting zip file like V27MVS.exe to install the socket layer for your MVS, usage will be installed automatically.
PC*MILER-AS/400 MVS User’s Guide NOTE for UPGRADE USERS: Starting with V27 you will be emailed your 25 digit product key code from alkservices@alk.com as custom MVS update disks are no longer being produced. There will be links within this email to Detailed Directions and Varsity Directions text files with instructions spefic to your company’s particular MVS installation.
PC*MILER-AS/400 MVS User’s Guide Notes and Updates for Version 21: ALK has merged what was formerly the ALK|FleetSuite Tolls product into the standard PC*MILER and PC*MILER|Streets product lines. Now known as “PC*MILER|Tolls” and “PC*MILER|Streets-Tolls”, each one is installed as an add-on data module and there is no longer a stand-alone product. The PC*MILER|Tolls component is circled below as it appears during the PC Side installation of PC*MILER-AS/400.
PC*MILER-AS/400 MVS User’s Guide Version 20 Changes – Spring 2006: On 06/10/2005 the number of Route Information segments per response packet (HR Returns) was increased from three sets to nine sets to improve performance. See section 8.2.5 for more information. ALK will provide backward compatible “Three HR Set” mileage server executables upon request. If your mileage server executable (as400.
PC*MILER-AS/400 MVS User’s Guide 1 Notes and Updates for Version 27 – Please Read Starting with Version 27, socket software is now automatically installed. Instead of running a self-extracting zip file like V27MVS.exe to install the socket layer for your MVS, usage will be installed automatically.
PC*MILER-AS/400 MVS User’s Guide NOTE for UPGRADE USERS: Starting with V27 you will be emailed your 25 digit product key code from alkservices@alk.com as custom MVS update disks are no longer being produced. There will be links within this email to Detailed Directions and Varsity Directions text files with instructions spefic to your company’s particular MVS installation.
PC*MILER-AS/400 MVS User’s Guide Notes and Updates for Version 21: ALK has merged what was formerly the ALK|FleetSuite Tolls product into the standard PC*MILER and PC*MILER|Streets product lines. Now known as “PC*MILER|Tolls” and “PC*MILER|Streets-Tolls”, each one is installed as an add-on data module and there is no longer a stand-alone product. The PC*MILER|Tolls component is circled below as it appears during the PC Side installation of PC*MILER-AS/400.
PC*MILER-AS/400 MVS User’s Guide Version 20 Changes – Spring 2006: On 06/10/2005 the number of Route Information segments per response packet (HR Returns) was increased from three sets to nine sets to improve performance. See section 8.2.5 for more information. ALK will provide backward compatible “Three HR Set” mileage server executables upon request. If your mileage server executable (as400.
PC*MILER-AS/400 MVS User’s Guide Shortest/Toll Discouraged/53’ Trailer Note that National Network and 53’ Trailer Routing cannot be combined, they are mutually exclusive. Third-Party or In-House Transportation Software Must Be Modified to Utilize PC*MILER Version 17 and Higher: If you are using PC*MILER or PC*MILER|Tolls with other transportation software, that software will have to be modified to utilize the new functionality.
PC*MILER-AS/400 MVS User’s Guide 1.0 Introduction PLEASE NOTE: In this User’s Guide, any reference to “PC*MILER” also applies to PC*MILER|Tolls unless otherwise specified. Instructions specific to Tolls products are included. A high-end function of PC*MILER®|Connect and PC*MILER®|Tolls-Connect, the Multi-Version Switch (MVS) serves as an integration tool designed to simultaneously support multiple versions of the product that are installed on one server or on several different servers.
7 PC*MILER-AS/400 MVS User’s Guide The Advantage of Using Multi-Version Switch ALK’s PC*MILER products are the de-facto industry standard software solutions for determining mileage and toll costs between locations. Thousands of over-theroad carriers as well as shippers use our products as a means to determine mileage that can be agreed upon for billing purposes.
8 PC*MILER-AS/400 MVS User’s Guide Figure 1.1 illustrates a typical PC*MILER application stack at a customer site, before installation of the MVS. There are three versions of PC*MILER which are accessed manually (through PC*MILER’s Graphical User Interface) and one version integrated via PC*MILER|Connect.
9 PC*MILER-AS/400 MVS User’s Guide The PC*MILER Multi-Version Switch currently provides connections to any version of PC*MILER|Connect, or combination of versions, listed below: PC*MILER|Connect 14.0 or 14.1 PC*MILER|Connect 15.0 or 15.1 PC*MILER|Connect 16.0 or 16.1 PC*MILER|Connect 17.0 or 17.1 PC*MILER|Connect 18.0 or 18.1 PC*MILER|Connect 19.0 or 19.1 PC*MILER|Connect 20.0 or 20.1 PC*MILER|Connect 21.0 or 21.1 PC*MILER|Connect 22.0 or 22.1 PC*MILER|Connect 23.0 or 23.
PC*MILER-AS/400 MVS User’s Guide 2.0 System Requirements Because PC*MILER-AS/400 employs a Client Server solution, the following hardware and software is required. The AS/400 server uses SNA APPC data queues to communicate. Platforms • PC/LAN Windows 2003, Vista, XP, 7 and 8 running in 32-bit compatibility mode as well as support for 64-bit native applications on Windows 7 and 8 • AS/400 NOTE: Platforms not supported include: SCO UNIX, Windows 95, 98 First/ Second Edition, Me, 2000, and NT.
PC*MILER-AS/400 MVS User’s Guide • Supports OS/400, i5/OS and IBMi operating systems; Version 4.2 (V4R2) and higher on IBM AS/400, systemi and power Systems hardware. 2.1 PC*MILER Graphics PC*MILER map graphics are not supported in PC*MILER-AS/400 MultiVersion Switch.
PC*MILER-AS/400 MVS User’s Guide 3.0 Installation PC*MILER for the AS/400* works by connecting a 32-bit Windows PC to your AS/400. The PC provides mileage lookups to the AS/400 via data queues. Generally, there is one common input or request queue that all users write to, with each user having their own output queue. The PC listens to the input queue for mileage request packets. Within each mileage request packet is the name of the user’s output queue.
PC*MILER-AS/400 MVS User’s Guide 3.1 Installation Overview On the AS/400 side you will be performing a RSTLIB on your ALKMVS or ALKMTL (for Tolls) Library CD. On the PC side there is a two-step process for each version of PC*MILER that you will be installing. Installation of the base PC*MILER product. This installation serves as the highway network “database” for your MVS server . Addition of the MVS components by unzipping self-extracting Zip files.
PC*MILER-AS/400 MVS User’s Guide 1. Create a library with the CRTLIB command. Type CRTLIB ALKMVS or ALKMTL for Tolls. 2. Add the library to the current library list. Type ADDLIBLE ALKMVS or ALKMTL for Tolls. For Innovative Computing Corporation installations, you will also need your ICC WORK and FILE libraries in your current library list. For Version R6, type ADDLIBLE I93FILE or ITSR6FILE and then ADDLIBLE I93WORK or ITSR6WORK. The ICC Version 7 libraries are IESR7WORK and IESR7FILE.
PC*MILER-AS/400 MVS User’s Guide a. b. The WRKSYSVAL command can be used by typing WRKSYSVAL, and then searching for the QUSRLIBL entry. Insert ALKMVS. If your users are using a job description in their user profiles, then use the CHGJOBD command (type CHGJOBD) and insert ALKMVS or ALKMTL. For Innovative Computing installations, a command is available to help insert a library into the library list. ALKMVS should be the first library in the library list.
PC*MILER-AS/400 MVS User’s Guide Input Data Queue Library 3.3 PC Side Installation The PC side of the PC*MILER-AS/400 Multi-Version Switch installation is a multi-faceted process. The installation varies depending on the number of versions of PC*MILER and PC*MILER|Streets involved and the number of mileage server PCs that will be used. Generally installations can be performed in less than half an hour if you strictly follow the instructions.
PC*MILER-AS/400 MVS User’s Guide A Two-Part Process Essentially the PC side of the PC*MILER-AS/400 Multi-Version Switch installation can be broken down into two parts: 1) PC*MILER-AS/400 Multi-Version Switch (as400.exe) which reads mileage requests from a request data queue on the AS/400, and 2) At least one instance of PC*MILER|TCP/IP (pcmsock.exe) which provides the mileage and routing information for as400.exe to return to a response data queue on the AS/400.
PC*MILER-AS/400 MVS User’s Guide PC Side Installation Overview Install a copy of PC*MILER for Windows (or PC*MILER|Tolls) for each version you will be accessing. On each of your MVS Install CDs you will find an MVSInst folder that will contain your install time Product Key Codes and all of the self-extracting Zip files that you will be using. Then in a separate folder you will find the installation setup.exe for each of the versions of PC*MILER that you have licenses for.
19 PC*MILER-AS/400 MVS User’s Guide The currently-supported versions of PC*MILER products are: PC*MILER 14.x PC*MILER 15.x PC*MILER 16.x PC*MILER 17.x PC*MILER 18.x PC*MILER 19.x PC*MILER 20.x PC*MILER 21.x PC*MILER 22.x PC*MILER 23.x PC*MILER 24.x PC*MILER 25.x PC*MILER 26.x PC*MILER 27.x * ALK|FleetSuite Tolls 18 ALK|FleetSuite Tolls 19 ALK|FleetSuite Tolls 20.x PC*MILER|Tolls 21.x PC*MILER|Tolls 22.x PC*MILER|Tolls 23.x PC*MILER|Tolls 24.x PC*MILER|Tolls 25.x PC*MILER|Tolls 26.x PC*MILER|Tolls 27.
PC*MILER-AS/400 MVS User’s Guide of getting the wrong version of this critical file, and unpredictable behavior may result. Note that use of the NS Router is no longer being supported by ALK. Step 2: Insert one of your Multi-Version Switch Install DVDs. Each DVD will have the same MVSInst folder and then a variety of PC*MILER installations. A typical disk would look like the following: MVSInst V140 V151 V161 V171 You can install any version you are licensed for.
PC*MILER-AS/400 MVS User’s Guide Step 2.1 Install the base PC*MILER applications by running the setup.exe that is in the version-specific subfolder on the Multi-Version Switch Install CD. Install time Serial Numbers and Product Key Codes are in: \MVSInst\Install_Codes.txt If at all possible, do not change the default installation location. Changing the default installation location increases the number of configuration steps.
PC*MILER-AS/400 MVS User’s Guide NOTE: For Version 16 and 17 there are self-extracting Zip files specific to 16.0, 16.1, 17.0, and 17.1. Take great care not to mix up the versions of the base PC*MILER (.0 or .1) and the version of the self-extracting Zip file that you use. For example, V160MVS.exe is for use with V16.0 and V161MVS.exe is for use with V16.1. NOTE: Disk sets with both .0 and .1 releases of the same version will have additional files. These files contain the letter ‘c’ in their names.
PC*MILER-AS/400 MVS User’s Guide Step 3.1 On the Multi-Version Switch Install CD: 1) For PC*MILER run: \MVSInst\alkmvs.exe, it is set to unzip to C:\Alkmvs or 2) For PC*MILER|Tolls run: \MVSInst\alktoll.exe, is set to unzip to C:\Alktoll. NOTE: The names for these files can vary depending on the products ordered. The files will always include “ALK” and be descriptively named. You can redirect the ‘Unzip to Folder’ in the Unzip window if necessary. NOTE: If you redirect ALKMVS.exe or ALKTOLL.
24 PC*MILER-AS/400 MVS User’s Guide Product9=PCMiler 20U Product10=PCMiler 21T Product11=PCMiler 22T Product12=PCMiler 23T Product 13=PCMiler 24T Product 14=PCMiler 25T Product 15=PCMiler 26T Product 16=PCMiler 27T NOTE on Version Format: These values must match those in your Pcmmv.ini file – See Version-Specific Routing and City Format Information in Chapter 8. They are case sensitive. Letters must be capitals. Use ‘W’ for Worldwide versions, ‘T’ for Tolls .0 versions and ‘U’ for Tolls .1 versions.
PC*MILER-AS/400 MVS User’s Guide Step 4.3: Edit \AlkMvs\Pcmmv.ini or \AlkToll\pcmmv.ini to point to the various instances of PC*MILER|TCP/IP. If you are going to run each instance of PC*MILER|TCP/IP on a single PC and you don’t want to adjust the port numbers, you can skip this step. Pcmmv.ini is used to locate the various instances of PC*MILER|TCP/IP (pcmsockXX.exe). By default Pcmmv.ini is pointing to local copies via the loop back address.
PC*MILER-AS/400 MVS User’s Guide NOTE: Each version of pcmsock.exe has been renamed with its version number appended so that the versions are distinguishable in the Windows Task Manager. NOTE: The second parameter passed to pcmsockxx.exe is the Port Number, if you change these values you must change the values in \alkmvs\pcmmv.ini or \alktoll\pcmmv.ini. NOTE: For non-default installation locations, you will have to edit the “Cd’ lines to change to your actual install locations. Once you have StartMvs.
PC*MILER-AS/400 MVS User’s Guide 4.0 Starting an Instance of PC*MILER|TCP/IP PC*MILER|TCP/IP can be started from a command or from a batch file. Within the PC*MILER-AS/400 Multi-Version Switch installation, each copy of PC*MILER|TCP/IP (pcmsock.exe) has been renamed to reflect the PC*MILER version it is returning mileage and routing information for. The format is pcmsockxx.exe where xx is the PC*MILER version. This enables identification of a particular version within the Windows Task Manager. Pcmsock.
PC*MILER-AS/400 MVS User’s Guide 5.0 Troubleshooting After you have started your various instances of pcmsock.exe you can test them by running the following command in DOS: C:\alkmvs\mvtestall For any failures you will have to run a second tester. In each of the ...\Pmw1xx\Tcpip subfolders created by the self-extracting Zip files in Step 2.2 of the installation, you will find a pcmstest.exe file. Pcmstest.exe tests the layer below pcmsock.exe.
PC*MILER-AS/400 MVS User’s Guide 29 You can copy delay.exe to C:\windows(winnt) and then edit StartMvs.
PC*MILER-AS/400 MVS User’s Guide 6.0 Starting and Stopping the Mileage Server At least one instance of PC*MILER|TCP/IP must be running before you can start PC*MILER-AS/400 Multi-Version Switch (as400.exe). AS400.exe while running maintains a list of available PC*MILER versions. It will find a newly started instance of PC*MILER|TCP/IP and will remove a version which has stopped responding. If you edit StartMvs.bat and create a shortcut for it in your startup folder as described in installation Step 4.
PC*MILER-AS/400 MVS User’s Guide 0 Connection Good Created Data Queue 2 Connection Good Found Data Queue Return codes of 1 or 3 are generic error codes that indicate problems with your Client Access Express connections. NOTE: Both the PC and the AS/400 must agree on the location of the Input or Request data queue. To change the location on the PC, click on the mileage server’s File menu. Choose AS/400 Control, then Change Library/Queue.
PC*MILER-AS/400 MVS User’s Guide or two to exit. Be sure to disconnect the Netsoft Router from the AS/400 before closing the router. Failure to do so may result in having to reboot the PC before you can reconnect to the AS/400. It is not necessary to manually disconnect a Client Access Express connection.
PC*MILER-AS/400 MVS User’s Guide 7.0 Using PC*MILER for the AS/400 To use PC*MILER for the AS/400, issue the command PCMVS or PCMTL for Tolls from the command line. One of the following screens will appear.
PC*MILER-AS/400 MVS User’s Guide NOTE: The PCMVS or the PCMTL command contacts the mileage server to read the data that the mileage server is using. If the PCMVS or the PCMTL command doesn’t respond or the PC*MILER screen comes up with ”PC DOWN” in the screen title, there is a problem with the connection to the mileage server PC. At the top of the main entry screen are several control settings.
PC*MILER-AS/400 MVS User’s Guide For Version 17.x and Up: Either Practical or Shortest routing can now be combined with other available PC*MILER routing options (Toll Discouraged, National Network, or 53’ Trailer). You must specify either P (Practical ) or S (Shortest) for all routes. (Refer to the main PC*MILER User’s Guide for more detailed descriptions of these routing options.
PC*MILER-AS/400 MVS User’s Guide Ovrd (Override) Restrictions: Versions 14.x and 15.x not available. Versions 16.0 and 16.1 with optional Street Level Add-on Only). All versions of 17.0 and higher. In addition to the five basic PC*MILER route types, a Heavy and Light Vehicle routing option is now offered. When Ovrd Restrictions is set to “Y”, the Light Vehicle option is activated.
PC*MILER-AS/400 MVS User’s Guide NOTE For PC*MILER|Streets Users: An address should directly follow the city/state or ZIP code entry, separated by a semicolon (e.g. “Princeton, NJ; 1000 Herrontown Road”). You can also purchase separate add-on data modules for Canadian postal codes or SPLC codes. A Canadian postal code is entered in the same manner as a ZIP code, but in the following format: L#L #L#. (e.g. “K7L 4E7”). A SPLC is a six- or nine-digit number, preceded by the letters ‘SPLC’ (e.g.
PC*MILER-AS/400 MVS User’s Guide Once you have entered stops on the main screen and initiated a mileage inquiry by pressing , the following screen will appear: PCMVS: PCMTL: This report contains leg and cumulative miles for each segment of your trip. The time and cost estimates are based on the values contained in the copy of PC*MILER (or PC*MILER|Streets) installed on your dedicated PC. (Refer to the main PC*MILER User’s Guide for instructions on how to alter these values.
PC*MILER-AS/400 MVS User’s Guide 7.
PC*MILER-AS/400 MVS User’s Guide Press for Jurisdiction-by-Jurisdiction distance breakdowns.
PC*MILER-AS/400 MVS User’s Guide 7.2 Detailed Driving Directions Report After entering stops on the main screen and pressing to initiate a Detailed Driving Directions (HS) request, press in the mileage report screen to generate driving directions. When processing is complete, the screen shown below will appear. Note that driving directions take significantly longer to process than miles or state miles because more information is requested and returned.
PC*MILER-AS/400 MVS User’s Guide 8.0 Using PC*MILER-AS/400 Multi-Version Switch with Other Transportation Software New for Version 20 - 27: New Naming Convention for PC*MILER|Tolls Codes. Up until Version 20.1, there was only a .0 release of the Tolls products and the convention for the PC*MILER version code was to end Tolls versions with a capital “T”, for example, “18T”. The new PC*MILER|Tolls code convention will be for the .0 version to end in “T” and the .1 version to end in capital “U”.
PC*MILER-AS/400 MVS User’s Guide versions are available. Passing blanks will result in the use of Product0 from your Srv32.ini file. Notes for All Users: • • • • • Changes to route types and jurisdiction codes are not uniform (see chart below). Use of comma between city and jurisdiction code is not uniform (see chart below). All HS (highway segment) turn-by-turn driving instructions are uniform at the Version 16.x level. Override Route Restrictions option not uniformly available (see chart below).
PC*MILER-AS/400 MVS User’s Guide Previously the five available codes were: P = Practical S = Shortest N = National Network T = Toll Discouraged 5 = 53 Foot Trailer New codes: P = Practical S = Shortest 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 Net
45 PC*MILER-AS/400 MVS User’s Guide Version-Specific Routing and City Format Information Version Route Types Available City Entry Jurisdiction Info PC*MILER 14.
46 PC*MILER-AS/400 MVS User’s Guide Restriction Overrides by Version PC*MILER 14.x Feature not available PC*MILER 15.x Feature not available PC*MILER 16.x Available with Street Level Add-on Only PC*MILER 17.x and Up Available all versions Codes For PC*MILER Versions (must be three characters) PC*MILER 14.0 = 140 PC*MILER 15.0 = 150 PC*MILER 16.0 = 160 PC*MILER 17.0 = 170 PC*MILER 18.0 = 180 PC*MILER 19.0 = 190 PC*MILER 20.0 = 200 PC*MILER 21.0 = 210 PC*MILER 22.0 = 220 PC*MILER 23.
PC*MILER-AS/400 MVS User’s Guide 47 8.1 Technical Overview The PC*MILER-AS/400 system uses distributed processing techniques (i.e. the processing is split into two). The user interface or interactive software is written in RPG and runs on the AS/400. The mileage calculation software is written in C++ and runs on a PC in the Windows environment. The RPG programs communicate with the PC mileage calculation software through Client Access Express.
PC*MILER-AS/400 MVS User’s Guide 48 MVRESP MVSEND2 MTSEND MTSEND2 External data structure for receiving mileage output Sample external data structure with Borders Open/Closed and Use Ferry Distance Fields External data structure for sending mileage requests 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 othe
PC*MILER-AS/400 MVS User’s Guide 8.2 Request and Response Field Parameters The following sections specify the field parameters for the request types defined in section 8.1 and the responses to each request type. IMPORTANT NOTE: When using PC*MILER|Streets, the best matching for address location lookups can be accomplished using the guidelines stated below. These rules apply to batch or interactive integration.
50 PC*MILER-AS/400 MVS User’s Guide 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.
51 PC*MILER-AS/400 MVS User’s Guide Trip” message. The VA request type can be used to produce lists of potential matches to partial spellings or ZIP codes.
52 PC*MILER-AS/400 MVS User’s Guide Y N Force Pick List Filler-1 RESP-Seq RESP-ERR 1 4 2 RESP-MVS 3 RESP-CIT 980 Filler 15 Exact match No match Pos 21) Echoed from Request P or Blank 1 blank Pos 23-26) Sequence for multiple responses 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 Pos 29-31 (3-character PC*MILER Version) Pos 32-38) Not Used Array of 14 places 70 bytes each left justified or Er
53 PC*MILER-AS/400 MVS User’s Guide REQ-MORE REQ-FMT 1 1 1 REQ-REGION (Worldwide Only) 1 REQ-CUSTOM REQ-Ovrd Restrictions 1 1 REQ-Hazmat (Data Add-on) 1 New v20 New v20 REQ-BRDR 1 REQ-FERRY 1 REQ-SEQ REQ-ERR REQ-MVS 2 2 3 (Position 29-31) MVS TOLL 1 REQ-FILL 6 REQ-CIT 700 NOTE: REQ-SEQ is not read for MI requests. REQ-BRDR and REQ-FERRY values are not back in the PC responses.
54 PC*MILER-AS/400 MVS User’s Guide 2. (Response) The following are field parameters for output miles. The City Pair response returns an output to the host application that contains city names and ZIP codes along with miles, cost and time estimates. The CP response is always returned first for all three request types (MI, SM, and HS).
55 PC*MILER-AS/400 MVS User’s Guide EA = invalid or not found server ID EB = invalid trip ID EC = error writing to queue ED = Incomplete Record/Header RESP-MVS RESP-TOLL RESP-Fill 3 1 6 PC*MILER Version (Pos 29-31) T=Tolls/Cash D=Discount or Blank (Pos 32) PC*MILER Version (Pos 33-38) RESP-CIT1 39 39 bytes All stop information including Zip and\or city\state and\or county and\or Street address or If there is error the pcmiler error code RESP-CIT2 39 39 bytes All stop information including Zip and\o
PC*MILER-AS/400 MVS User’s Guide 1 1 REQ-MORE REQ-FMT 1 1 1 REQ-REGION (Worldwide Only) 1 REQ-Custom Routing REQ-Ovrd Restrictions 1 1 REQ-Hazmat New => 1 New => REQ-BRDR 1 REQ-FERRY 1 REQ-SEQ REQ-ERR REQ-MVS 2 2 3 (Position 29-31) RESP-TOLL REQ-FILL REQ-CIT 1 6 700 56 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/Na
57 PC*MILER-AS/400 MVS User’s Guide 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 #L# NOTE: REQ-SEQ is not read for SM requests. REQ-BRDR and REQ-FERRY values are not echoed back in the PC responses. 2. (Response) The following are field parameters for the state miles output. The PC will respond with the miles (or kilometers) for the stops indicated in the "SM" request.
58 PC*MILER-AS/400 MVS User’s Guide RESP-REGION 1 RESP-Custom Routing 1 RESP-Ovrd Restrictions 1 Pos 7) A=Asia,E=Europe,F=Africa,N=North America,O=Oceania,S=South America Pos 8) C=Custom, blank=default Pos 9) Y=Override Restrictions or L=Light N=Obey Restrictions or H=Heavy Pos 10) G = General Restriction C=Caustic E = Explosive Restriction F=Flammable I = Inhalant Restriction R = Radioactive Restriction Sequence for multiple responses Error Code E1 First state not found E2 First city not found E3 Seco
59 PC*MILER-AS/400 MVS User’s Guide 8.2.5 Detailed Route Information (HS) Request and Response 1. (Request) Following are parameters for a route and state miles request. The purpose of this request is to allow the Host to retrieve detailed route information based on the city pair stop-off points.
60 PC*MILER-AS/400 MVS User’s Guide REQ-SEQ REQ-ERR REQ-MVS 2 2 3 (Position 29-31) RESP-TOLL REQ-FILL 1 6 REQ-CIT 700 Sequence for multiple responses (Not Read by PC) Error Code Requested PCMILER Version 140=PC*MILER Version 14 141=PC*MILER Version 14.1 150=PC*MILER Version 15.0 151=PCMILER Version 15.
61 PC*MILER-AS/400 MVS User’s Guide 1 1 REQ-MORE 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 Pos 2) M or K for miles or kilometers Pos 3) R = resequence stops H = hub leg miles F = resequence stops fixed destination blank = otherwise Pos 4) M = more data to follow Pos 5) Reserved by DR request Pos 6) E = Extended Format (Required, se
62 PC*MILER-AS/400 MVS User’s Guide For Tolls Only: RESP-MVS RESP-TOLL RESP-Fill RouteInfo 3 1 6 963 PC*MILER Version (Pos 29-31) T=Tolls/Cash D=Discount or Blank (Pos 32) PC*MILER Version (Pos 33-38) 9 Sets of 107 Each ROUTEINFO 9 sets { FILLER 2 indicates end of route data for stop 2 state code 1 toll indicator 6 directional (North, Turn L, etc) 35 route number 4 leg mileage 38 for intersection city or junction 6 for cumulative leg miles 6 for cumulative stop miles 7=Toll Cost 34 NOTES: The PC w
63 PC*MILER-AS/400 MVS User’s Guide 8.2.5.1 Upgrade Notice All HR returns regardless of requested PC*MILER Version return the larger V16 + format. In Version 16 and 17, the ROUTEINFO portion of the HS return was increased by 25 characters and the number of ROUTEINFO Sets per response packet was decreased from four sets to three. Route Number was increased 15 characters from 20 to 35 (Highway , Road or Street Name), and Interchange City or Junction was increased 10 characters from 28 to 38.
64 PC*MILER-AS/400 MVS User’s Guide 8.2.6 Sample Request and Response Records Sample records are shown below.
65 PC*MILER-AS/400 MVS User’s Guide 9.0 Using the Mileage Server and Map Window Maps are not available in PC*MILER-AS/400 Multi-Version Switch. 9.1 Menus All menu commands in PC*MILER for the AS/400 are described on the following pages. The File Menu Using the File menu, you can open, close, save and duplicate routes; print graphics and reports; and exit the PC*MILER program. Delete AS/400 Input Queue When a queue becomes corrupted, creates a new queue and deletes the corrupted one.
66 PC*MILER-AS/400 MVS User’s Guide on, diagnostics are written to a file called as400.log, located in the directory that the software is running from (as400.exe). Choose between Append, Overwrite, and Verbose. (Verbose adds PC to AS/400 Communications messaging.) Host Polling Timer: Use faster time slice to poll the AS/400 more often for faster interactive response time, or slower time slice for smoother graphic display. Force Pick List: Turns AS/400 pick lists off/on for duplicate city names.
PC*MILER-AS/400 MVS User’s Guide 10.0 Common Questions and Installation Problems Question: Some of the mileage returned from PC*MILER is different from the mileage returned by my other transportation software. Answer: The city spelling or ZIP being used by the other software is probably not correct. To verify what place name is being sent to PC*MILER, click on the Pick Pins icon and then on the stop-off point in the mapping window. Now correct your AS/400 cities file.
PC*MILER-AS/400 MVS User’s Guide 11.0 Technical Support Technical support is available to registered users of PC*MILER AS/400 from 9:00am to 5:00pm EST, Monday through Friday. Call (609) 683-0220, ext 2. Or e-mail us at pcmsupport@alk.com (type “MVS” in the subject line).
PC*MILER-AS/400 MVS User’s Guide Appendix A: Backward Compatibility ALK Technologies does support backward compatibility with previous versions of PC*MILER and PC*MILER for the AS/400. However, it is not advisable to develop new applications that use these short city name structures, because you lose access to county information which is necessary for resolving duplicate city name problems. Over time, this backward compatibility becomes increasingly difficult for ALK Technologies to maintain.
PC*MILER-AS/400 MVS User’s Guide Appendix B: Configuring an N/S Router For Use With PC*MILER-AS/400 Unless you have a twinax connection, configure your router using the AnyNet protocol. AnyNet needs to be enabled on the AS/400 (see Appendix D: Configuring AnyNet on the AS/400). For PC*MILER Version 14 (or higher) and any PC*MILER|Streets version, you must have the N/S Router version 3.0 or higher. Check by selecting HELP > About in the NS/Administrator or the midrange workspace.
PC*MILER-AS/400 MVS User’s Guide Then do the following: 1. In the Links Tab, highlight AnyNet, and then choose Properties. 2. In Properties, fill in the AS/400’s IP address. You can use a system name, but if your host tables are not filled in properly, you will be able to connect to the AS/400, but PC*MILER won’t be able to create a Data Queue.
PC*MILER-AS/400 MVS User’s Guide 3. The Systems tab adds the AS/400’s system name. This is where you set the password with which the router signs in. Make sure that the password has not expired, and that the account has object authority to the library where your mileage request Data Queue will reside (usually ALKMVS or an Innovative Work Library).
PC*MILER-AS/400 MVS User’s Guide 4. In the local LU tab use the second option, Use a local specific value. These are the only changes you need to make. Leave the other settings on the defaults.
PC*MILER-AS/400 MVS User’s Guide Appendix C: Configuring AnyNet On the AS/400 The following instructions are provided by NetManage. 1. Type the following command at the AS/400 command prompt: CHGNETA ALWANYNET(*YES) This value can only be changed when the AnyNet controller is varied off. Vary on the controller to make the change effective. You can check this attribute with the DSPNETA command, and page down to the bottom. 2.
PC*MILER-AS/400 MVS User’s Guide Appendix D: Configuring Client Access Express For PC*MILER-AS/400 1. Install Client Access Express on your mileage server PC by running the setup.exe that is in the Express folder on your Client Access Express CD. 2. Go to the AS/400 Operations Navigator. For new installations, the Navigator will prompt to ask if you want to add a connection.
PC*MILER-AS/400 MVS User’s Guide For existing installations of Client Access Express, go into the AS/400 Operations Navigator and right mouse click on your AS/400 connection. Choose Properties to make changes or Verify to verify a connection. The Connection Properties Window is used for changing existing connections or changing the Restart Settings for new connections. NOTE: Client Access Express has the ability to change passwords in the user profile.
PC*MILER-AS/400 MVS User’s Guide 3. Password Considerations - There are several areas to consider with a Client Access Express installation. Client Access Express offers three Password options. You can choose to have the PC logged on manually to the AS/400, have Client Access Express use the Windows User Name and Password, or you can specify a user profile and have the password typed in as needed. The default user ID is the User Profile that the mileage server PC will be signing on to.
PC*MILER-AS/400 MVS User’s Guide For auto-restart, you will also have to make the above settings in the Connection Properties dialog. (For new connections, right mouse click on your connection in the AS/400 Operation Navigator, and choose properties to get this screen.
PC*MILER-AS/400 MVS User’s Guide 4. Verify the connection. assistance.
PC*MILER-AS/400 MVS User’s Guide Appendix E: The Sleep Feature For IPL Drop Outs The Sleep Feature has been added to correct an issue in which the NS Router does not reliably reconnect to the AS/400 after an IPL or power down. This feature can also be used in the rare cases where client Access Express loses connection after an IPL. To activate the sleep feature, you need to send a message to the PC mileage server (as400.exe). Included in your ALKMVS Library is a CL program called “queue”.
PC*MILER-AS/400 MVS User’s Guide To get the AS/400 mileage server screen, you can click on SRV32 on your tool bar. You can also press and hold down the ALT key, and press and release the TAB key until the AS/400 Server – PC*MILER icon is selected, and then release both keys. To bring up the Server Log, click on the mileage server window’s pull-down menu, or press ALT-W and choose Display server Log.
PC*MILER-AS/400 MVS User’s Guide Appendix F: Multi-Version Switch INI Settings PC*MILER-AS/400 Multi-Version Switch uses multiple INI files. AS400.exe uses Srv32.INI and Pcmmv.INI. Each instance of PC*MILER|TCP/IP uses its own Pcmserve.INI. Srv32.INI is used for startup information. Pcmmv.INI is used to store the locations of your various instances of PC*MILER|TCP/IP. Srv32.INI and Pcmmv.INI have to be kept in synch at all times. Changes to the values under the [MultiVersion] Key in Srv32.
PC*MILER-AS/400 MVS User’s Guide 83 library = ALKMVS or ALKMTL qname = MIDQUE PICKLIST = FALSE Force Pick list for cities with multiple zip codes and for partial matches SLEEPTIME = 300 Used for NS Router Connects during IPL’s FrameTrip = FALSE Not used DIAG =TRUE Turn on logging Borders =FALSE ; False Cross International Borders only for International Stops Timer = Time between reads of request queue.
84 PC*MILER-AS/400 MVS User’s Guide These values will only be used if they are not specified by the calling application. Valid values for default and option settings in the pcmserve.ini that can be changed by the user are described below. Key Valid Values (Defaults) Description CalcType Practical Set In Srv32.InI Units Miles Kilometers What unit of measure should distance be shown in. ChangeDest TRUE FALSE When optimizing the route, should the trip’s destination be optimized also.
85 PC*MILER-AS/400 MVS User’s Guide UseUSPostCodes=False and UseMexPostCodes=False – Defaults to the U.S. ZIP with no routing to Mexican postal codes UseUSPostCodes=True and UseMexPostCodes=False – Same as above UseUSPostCodes=True and UseMexPostCodes=True – Defaults to the U.S. ZIP, must pass an Estados code to get Mexican location (e.g. “50510,EM”) UseUSPostCodes=False and UseMexPostCodes=True – Only Mexican postal codes are available, in the U.S. only citystate pairs will get U.S.
PC*MILER-AS/400 MVS User’s Guide Pcmmv.INI NOTE: Maintain case sensitivity, do not alter ‘PCMiler’ when editing your pcmmv.ini files. New for 25 Logging: [Logging] Enable= 1 for on, 0 or blank for off File=C:\temp\pcmmvlog.txt <=Folder must exist Append= 1 for append, 0 for overwrite [PCMiler 140] address=127.0.0.1 Ip Address of Computer Name port=8014 Port Number specified when PC*MILER|TCP/IP was started. [PCMiler 150] address=127.0.0.1 port=8015 [PCMiler 160] address=127.0.0.
87 PC*MILER-AS/400 MVS User’s Guide Appendix G: AS400.LOG Error Codes To create a log file of all mileage server input and outputs, click on the mileage server’s File menu>AS/400 Control and choose Log to file. The file created is C:\ALKMVS\as400.log or C:\ALKTOLL\AS400.log. AS400.log displays requests and responses in the exact format as they are received and sent by the mileage server. It is recommended that logging only be used for diagnostic purposes, as the log files get quite large.
88 PC*MILER-AS/400 MVS User’s Guide PC*MILER|Streets Error Codes: Error Codes Value Message PCMS_INVALIDPTR PCMS_NOINIFILE PCMS_LOADINIFILE PCMS_LOADGEOCODE PCMS_LOADNETWORK PCMS_MAXTRIPS PCMS_INVALIDTRIP PCMS_INVALIDSERVER PCMS_BADROOTDIR PCMS_BADMETANETDIR PCMS_NOLICENSE 101 102 103 104 105 106 107 108 109 110 111 PCMS_TRIPNOTREADY PCMS_INVALIDPLACE PCMS_ROUTINGERROR PCMS_OPTERROR 112 113 114 115 PCMS_OPTHUB PCMS_OPT2STOPS PCMS_OPT3STOPS 116 117 118 PCMS_NOTENOUGHSTOPS PCMS_BADNETDIR PCMS_LOADG
PC*MILER-AS/400 MVS User’s Guide Appendix H: Setting Toll Discount Program Membership Toll Discount membership is set on your PC mileage server. Changes are made within the desktop PC*MILER|Tolls program (c:\ Program Files\ALK Technologies\ pmw270\ app\ pcmwin32.exe). On your mileage server PC: 1. Click Start Programs PCMILER 27 PCMILER 27 (pcmwin32.exe). 2. Click Route Default Route Options. 3. Click the Tolls tab. 4. Check the appropriate boxes as pictured below. 5. Exit pcmwin32.exe.
PC*MILER-AS/400 MVS User’s Guide Appendix I: Renamed Program Objects Some MVS objects in PC*MILER-AS/400 and PC*MILER|Tolls-AS400 are modified versions of the ones in the standard PC*MILER|Connect-AS/400 version. The following objects have been renamed to avoid conflicts with existing PC*MILER products. NOTE: Some objects have been renamed twice to adhere to an updated naming policy.
PC*MILER-AS/400 MVS User’s Guide For PC*MILER|Tolls: Tolls: AlKWIN library => ALKMVS => ALKMTL ALKWIN/Miinqc => ALKMTL/MVTIINQ (RPG Mileage Inquiry Program) ALKWIN/Miinqc => ALKMTL/MVTIINQ (CL program that creates a response data queue and then calls ALKMTL/MTLIINQ) PCMILER Cmd => PCMTL Cmd (Calls ALKMTL/MTLiinqc) External Data Structures Used for sending and receiving trip information to/from data queues.
PC*MILER-AS/400 MVS User’s Guide Appendix J: Installing the .0 and .1 Releases of the Same PC*MILER Version You cannot have the “.0” and the “.1” release of version 14 or 15 on the same PC because they share a common Registry Key. For example, if you need access to versions 14.0 and 14.1, you will need to install 14.0 on one PC and 14.1 on a second PC. For Version 16 and higher it is possible to run both the .0 and .1 releases on the same PC. However, doing so does complicate the installation process.
PC*MILER-AS/400 MVS User’s Guide V23.x HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion \Uninstall\{BC0E8625-C6E9-4D2C-B7C9-FE615C660437} Without deleting these keys, running the Installshield setup.exe will take you into Maintenance Mode and you will not be given the option of doing a full installation. For Versions 16 and 17 this would corrupt the installation and make it unusable. For Version 18 it would convert the existing from a .0 to a .1 or vice versa.
94 PC*MILER-AS/400 MVS User’s Guide pcmserve.ini is mapped to the Pmwxx1 folder. pcmsockXX.exe file will contain a three digit version. Additionally the For versions 16 and 17, unzipping the incorrect file will corrupt the installation. Double-check that you are running the correct file for that particular release. For example, you must unzip V161Tcpip.exe and For161App.exe into a 16.1 release and not a 16.0 release.
PC*MILER-AS/400 MVS User’s Guide 95 Appendix K: Adding New Versions to Existing MVS Servers Adding new versions of PC*MILER to an existing MVS Server is a three-step process that is very similiar to an initial installation. You first install the desktop PC*MILER program via an Installshield setup.exe, then run a self-extracting Zip file that contains the MVS software, and finally you add the new version to your existing Killmvs.bat, PCMMV.ini, StartMVS.bat and Srv32.ini files.
PC*MILER-AS/400 MVS User’s Guide 1. Copy: [PCMiler 250] address=127.0.0.1 port=8250 2. Then paste to three new lines and change the version number and port number as follows: [PCMiler 260] address=127.0.0.1 port=8260 3. Save and Exit. Startmvs.bat: Copy/Paste a similiar entry for an existing version and edit the directory location and port number. For example: 1. Copy: cd \”Program Files”\”Alk Technologies”\pmw250\tcpip start pcmsock25 PC_MILER 8250 2.
PC*MILER-AS/400 MVS User’s Guide For example: [PCMiler 260] from Pcmmv.ini must match Product10=PCMiler 260 PCMiler 260 must match PCMiler 260 (case sensitive) After editing your four files, run killmvs.bat, then startmvs.bat to make the new version available to your AS/400 users.
PC*MILER-AS/400 MVS User’s Guide 98 Appendix L: New in Version 25 – Four Levels of Logging Starting with V25: Logging has been added to the pcmmv.dll and to the pcmsockxx.exe layers in addition to the existing logging at the AS400.exe (Bart) and pcmsrv32.dll/pcmserve.ini levels. AS400.exe connects to pcmmv.dll, which connects to the version-specific instances of pcmsockXX.exe, which in turn connect to their version-specific instances of pcmsrv32.dll.
PC*MILER-AS/400 MVS User’s Guide 99 to: Start Pcmsock25.exe PC_MILER 8250 LOG_BASIC .\V25log.txt or Start Pcmsock25.exe PC_MILER 8250 LOG_BASIC C:\PcmLogs\V25log.txt <=Folder must exist Other options are: Add a fourth parameter of ‘Append’ to be used to troubleshoot crashes: Start Pcmsock25.exe PC_MILER 8250 LOG_BASIC C:\PcmLogs\V25log.txt APPEND Include communications and not just routing and distance information, using LOG_ADVANCED instead of LOG_BASIC: Start Pcmsock25.
