Logistics system for automating transportation of goods5631827Abstract The various transportation logistics tasks, such as order processing, order fulfillment, transportation of goods and tracking, are assigned to individual client/server objects which make up the building blocks of the computerized logistics management system. A tokenized message handling scheme allows client and server objects to share information, even where the respective data types do not match. An external processing manager provides script handling services to other client applications, allowing those applications to modify the performance of other program objects and to communicate with the outside world. Claims What is claimed is: Description BACKGROUND OF THE INVENTION
TABLE I
______________________________________
Program Object Function
______________________________________
Supervisory Server:
Acts as a repository for system wide
information.
Document Server:
Manages the client requests for
non-carrier document formats and the
printing of those documents.
FedEx Rate Server:
Manages the Federal Express rates,
carrier rules and documentation
requirements.
UPS Rater Server:
Manages the UPS rates, carrier rules
and documentation requirements.
RPS Rate Server:
Manages the RPS rates, carrier rules
and documentation requirements.
LTL Rate Server:
Manages the LTL rates, carrier rules
and documentation requirements.
Supervisory Manager:
Acts as a repository for
machine-specific informaton.
Ext. Process Manager:
Manages the client requests for
access to outside services such as
remote databases and remote
computers.
Device Manager:
Manages the client requests for
access to outside devices such as
printers, scanners, and scales.
Reset Database:
Resets the sample database to its
default values to facilitate training
exercises.
Introduction to the
A tutorial for the new user.
system:
Reports: Double-clicking this icon will run a
third party report generator program.
Supervisory Allows the user to edit system
Administration:
settings, manage shipper information
and allows users to send messages to
other computers.
Script Administration:
Allows the user to create and edit
scripts used by the External
Processing Manager.
FedEx Administration:
Allows the user to configure the
Federal Express Server settings such
as account numbers, EDI settings and
to close out the manifests.
UPS Rate Allows the user to configure the UPS
Administration:
Server settings such as account
numbers, rates, discounts and to close
out the manifests.
RPS Administration:
Allows the user to configure the RPS
Server settings such as account
numbers, rates, discounts and to close
out the manifests.
LTL Administration:
Allows the user to configure the LTL
Server settings such as account
numbers, and rates, discounts and to
close out.
Search and Trace:
A client application which allows the
user to search and trace specific
packages, shipments and orders.
Shipments: A client application which allows the
user to process shipments comprised
of multiple packages per order.
Packages: A client application which allows the
user to process shipments comprised
typically of one package per order.
Bills of Lading:
Allows the user to create bills of
lading for LTL Motor Freight
Shipments.
LTL Shipments:
Allows the user to create and rate bills
of lading for LTL Motor Freight
Shipments.
Document Allows the user to configure the
Administration:
Document Server with UCC-128
serial number information and
document attributes.
______________________________________
In an actual implementation of the system, one supervisory server and at least one supervisory manager would be provided. Specifically, one (and only one) supervisory server is provided for the entire network. In addition, one supervisory manager is provided for each CPU that will be running client or server applications on the network. This is illustrated in FIG. 3A, which depicts a distributed architecture employing three networked CPUs 102, 104 and 106. As illustrated, the supervisory server and one supervisory manager are running on CPU 104. Supervisory managers are also running on CPUs 102 and 106. For illustration purposes a UPS rate server object and a UPS rate administration object are also running on CPU 102; whereas a shipments client and a device manager are running on CPU 106. Thus, FIG. 3A represents one possible configuration assembled from the collection of presently preferred program objects. Although multiple CPU, distributed architecture installations represent a powerful configuration, it is possible to implement the invention on a single, standalone, CPU. This is illustrated in FIG. 3B, in which a standalone CPU is indicated at 108. As illustrated, this simple configuration includes a supervisory server and supervisory manager, along with any other program objects which may be required for the task being performed. Thus, in the example illustrated in FIG. 3B several rate servers and a packages client have been illustrated. Application User Interface Referring to FIGS. 4A-4L, the presently preferred user interface will now be described. In general, the client/server program objects, illustrated as icons in FIG. 2, may each have a user interface in the form of a screen or window through which the user can enter information, make command selections, and look up information. In practice, the user interface may vary in appearance and function, as dictated by the particular task to be performed. Thus the user interface screens illustrated in FIGS. 4A-4L are intended merely as examples in accordance with the presently preferred embodiment. Overall Icon View--System Folder The presently preferred embodiment places icons for all user-selectable program objects in the Logistics Management System folder or window, shown in FIG. 2. In this regard, the window shows a sample set of icons for the presently preferred system. Each icon is a pointer to a seperate client, manager or server object. By double-clicking on the appropriate icon, its object is started. For example, double-clicking on the Shipments Client starts that program object running. Typically, once an object is started, it continues to run and is able to communicate with other program objects via the interprocess communications (IPC) mechanism. Shipments Client Shown in FIG. 4A, the Shipments client accepts user input for the routing, rating and documentation of a group of packages comprising a shipment. Multiple shipper accounts are allowed and the desired account may by selected from the Shipper "drop-box." Similarly, the service is selected from the Service box. Alternatively, the service may be set to Best Way and the system will choose the least cost carrier which meets the transit time requirements indicated in the commitment field. The operator types or scans the Reference # (such as order #, pick ticket #, . . . ) and the system may be set to look up the associated information from one or more local and remote sources such as databases and mainframe or minicomputer terminal sessions. The upper left quadrant of the screen is to record information for the shipment as a whole. The lower left quadrant is used to record specific information for each package in the shipment. In all client data entry screens there are several special data entry provisions. Any field which has an ellipsis (. . . ) at its right edge has additional related fields of data available to be "examined" or edited by touching the F10 key or clicking the Examine icon. A popup window with the associated fields is displayed for the user. In addition, most fields may be set up to "browse" available valid entries. They may browse from database records or from "hard-coded" values in scripts. The Shipments client and most other clients are capable of processing shipments of mixed modes; e.g. small parcel ground, small parcel air, LTL motor freight, air freight, and TL motor freight. Packages Client Shown in FIG. 4B, the Packages client is designed to facilitate the entry and processing of shipments which typically consist of single small packages. Although, like most other clients, it will handle multiple modes of shipment, it is best suited for single piece shipments. If a multi-piece shipment is encountered, the user may touch CTRL-M or click the Multi button and the shipment is accomodated. Script Administration The Script Administration object, shown in FIG. 4C, allows the creation and editing of scripts for the modification of default behavior of the clients. A script may be triggered in various ways, such as upon the changing of the contents of virtually any field, upon the pressing or clicking of the function buttons on the client screen, upon the opening or closing of the client, and so on. In the illustration of FIG. 4C, the Shipments client is being operated upon to modify the Commitment terms based on the type of Service being used by the shipper. UPS Rate Adjustments Referring to FIG. 4D, the UPS Rate Adjustments program object and substantially similar objects for each of the carrier rate servers installed on the system, allow the user to adjust the discounts and incentive programs extended to the shipper by the carrier. Existing discounts may be edited, or new incentive programs not yet envisioned by the carrier may typically be created by the user within the flexible structure of this client type. Adjustments may be qualified by destination (either zone, postal code or destination country) and by weight range. Adjustments may be calculated as percentages or fixed amounts and include or exclude special service fees. If desired multiple adjustments may be created and put into effect. Serial Port 2 Configuration The Serial Port 2 Configuaration screen, shown in FIG. 4E, is a part of the Device Manager object. It allows the adjustment of basic serial port setup values. By clicking on the "Defaults" button, the default settings appropriate to the specific attached device are automatically entered. The "Test" button provides a facility for sending data to and receiving data from the attached device. Additional aspects of the Device Manager object are discussed in connection with FIGS. 4G-4L, below. Document Administration The Document Administration object, shown in FIG. 4F, allows the user to adjust settings for the UCC-128 standards of serialized container marking and Electronic Data Interchange. It allows the user to load and store consignee names and addresses and UCC-128 specific values. It also allows the user to edit the database and settings as changes may occur. Document Server The document server, illustrated as one of the icons in FIG. 2, allows any client to print almost any type of document, including shipping labels, waybills and manifests. The information needed to print a document is processed through a script. This allows the data to be brought in from any number of sources such as databases, mainframes, files or user-entered information from a client application. Also, one document format can serve several client applications and any particular processing needs a user might have. This is quite readily accomplished due to the fact that all data is passed through scripts. Thus, for example, one user might look up the export information for a FedEx international document from a database, while another user might wish to hand enter this data. Both of these tasks can be accomplished by a single document format and without the need for custom programming. Device Manager Object The Device Manager provides a device-independent means of interfacing with peripheral devices. Device drivers can be added or removed without modifying the software. The Device Manager also provides integrated testing tools. The Device Manager of the presently preferred embodiment has the ability to monitor power, through an uninterruptible power supply connected to the system. If power fails, the other applications are notified, and an orderly shutdown of the system will take place. This prevents loss or corruption of data by sudden power outage or by subsequent failure of battery power, once the reserves of the uninterruptible power supply have been depleted. The monitoring service provided by the Device Manager can shut down multiple machines on a network connected through one uninterruptible power supply. Referring to FIGS. 4G-4L, additional capabilities of the Device Manager object are illustrated. In FIG. 4G the communications port COM2 is shown as assigned or connected to an electronic scale, in this case a scale designated Toledo 8213 Scale. The parallel port LPT1 is shown as being assigned or connected to a printer, in this case a printer designated IBM 2380 Printer. Beneath the printer designation there appears a notation "No stock" which indicates that no particular paper stock has yet been designated. Double-clicking on the COM2 icon brings up the configuration screen shown in FIG. 4E. Selecting the purl-down menu designated "Device" brings up the device selection menu shown in FIG. 4H. Using the device selection menu the Toledo 8213 Scale may be selected, as illustrated. Thereafter, by returning to the device manager menu of FIG. 4G, the Toledo 8213 Scale icon may be double-clicked to bring up the device settings menu illustrated in FIG. 4I. Alternately, from the device manager menu of FIG. 4G, the parallel port LPT1 may be selected (by single-clicking) and configured by again accessing the "Device" menu option. In this case, referring to FIG. 4J, the IBM 2380 printer may be selected, as illustrated. Thereafter, the user may click "OK" to return to the device manager screen, FIG. 4G. From the device manager screen the user can double-click on the printer icon to bring up the appropriate device settings menu (FIG. 4K) for that device. Referring to FIG. 4K, note the Current Stock states "No stock loaded." If desired, the user can change the current stock by clicking on the change button. This action brings up the stock selection menu of FIG. 4L. DETAILED DESCRIPTION OF CLIENT/SERVER OBJECTS The client/server architecture utilized by the logistics management system affords a great deal of flexibility. The client and server program objects are designed to work independently of one another, communicating with one another through a tokenized message handling mechanism discussed below. In this way, rate server data and user data are separated from one another. The advantage of this is that when a given carrier changes the way rates are handled, the affected rate server can be modified (to change the type or amount of data stored in that rate server, for example) without affecting the user's data in any way. This separation is important since carrier requirements and carrier service options may change at any time. The presently preferred embodiment implements an internal version numbering scheme which provides a mechanism to allow client applications to determine what version of a server they are communicating with. In so doing, the client applications are able to make any necessary adjustments or to disconnect from that server if incompatibilities are found. This provides greater reliability, since server applications are given the ability to handle communications with servers intelligently. Separation between client and server objects also makes possible an automatic updating capability whereby a user's existing setup information is automatically merged into a new installation when an application is updated or reinstalled. This reduces the amount of setup time due to reinstallation. Each server of the presently preferred embodiment has built-in debugging capabilities which allow server transactions to be displayed on the screen or logged to a file for later analysis. The presently preferred rate servers optimize shipments to minimize cost through the use of shipment pricing rules supplied by the carrier. Optimization occurs "live" as a shipment is being processed, or, alternatively, at the end of the day when all packages shipped are then optimized. The rate servers can directly access carrier-supplied data, such as Federal Express routing and rate file data. This allows the user to load in new rate information as soon as such information is provided by the carriers. In addition, the rate servers of the presently preferred embodiment have the ability to rate and process a package, but to withhold it from the manifest until notified to do so. This allows "pack and hold" or future shipping. This is important in an automated system where a package may be processed upstream, but not placed on the manifest until it reaches the shipping dock. In the presently preferred embodiment client applications have editable bar code templates, to allow data to be entered via a barcode scanner. Because the templates are editable, they can be added to, deleted from or modified by the user without the need for additional programming. Clients can also process in "batch" mode, reading data from a source and sending that data to the appropriate rate servers for processing. The sources for data can include databases, files or direct connection to a host computer via serial or network connection. As stated above, the presently preferred embodiment uses a multitasking operating system which supports the processing of multiple processes or multiple threads effectively simultaneously. This allows client applications and server applications to operate effectively concurrently. To illustrate how multiple threads operate in the presently preferred embodiment refer to FIG. 5. In FIG. 5, the left-most box designated main thread 120 represents the starting point. Main thread 120 is launched by the operating system. One of the functions of main thread 120 is to perform or control the performance of the operating system routines illustrated in FIG. 5 by loop 122. When a server is started under the operating system the main thread launches a server thread, as represented by launch thread arrow 124. The server thread is represented by box 126. In the preferred embodiment the server thread performs the necessary initialization routines 128 and then enters a loop or state 130 where it waits for a client to initiate a connection request. When such a request is received the server thread launches a client thread, depicted in FIG. 5 by launch thread arrow 132. The client thread is depicted by block 134 in FIG. 5. It is responsible for handling the client's request. Once the client thread is launched by the server thread, the server thread returns to its wait for client loop or state 130, whereby the server thread is then able to launch additional client threads upon demand. Thus in the preferred embodiment, each server that is running will include a main thread and a server thread. Client threads are generated on an as needed basis. There is one client thread for each currently connected client. Communication between client and server, whereby requests are passed to the server and responses passed back to the clients, may be accomplished in a variety of different ways. In general, the methods of communicating between multiple processes running on the same CPU include shared memory, semaphores, pipes, queues and signals. The methods of communicating between multiple processes running on different CPUs (distributed architecture) include mechanisms such as NETBIOS, named pipes, sockets and mail slots. Collectively all of these methods of communicating between multiple processes form part of the interprocess communication (IPC) mechanism. Not all multitasking operating systems provide each of these IPC mechanisms. The presently preferred embodiment runs under the OS/2 operating system and uses LAN Server to provide operating system support for a distributed application architecture over a network. The presently preferred embodiment uses named pipes as the IPC mechanism. Named pipes allow one process to communicate with another process as follows. The client process first requests a named pipe connection to a server process. Once this connection is made, there is little distinction between the client process and the server process, since either can communicate with the other. One advantage of using the named pipe IPC mechanism is that the client process machine does not have to be running under the same operating system as the server process. All that is required is that the operating system platform on which the client process is running will support named pipes. Thus, a client process running under MS-DOS, or under MS-DOS with windows, for example, could establish communication with a server process running under the presently preferred OS/2 system, provided named pipe communication is supported. Essentially, under a named pipe communications scheme, the server process is known by a pipe name. Programs wishing to connect to that server will use the pipe name, in a fashion similar to using a file name. For example, pipe names may take the form:
______________________________________
.backslash.PIPE.backslash.pipename; or
.backslash..backslash.server.backslash.PIPE.backslash.pipename.
______________________________________
Although the named pipe IPC mechanism permits communication between any server and any client, the presently preferred configuration constrains communication to a tree-structured communications scheme illustrated in FIG. 6. Referring to FIG. 6, the single supervisory server communicates directly with only supervisory managers. In FIG. 6 the lines of communication are designated by the letter "C" at one end and the letter "S" at the other end. These indicate, for a given line of communication, which object is the client and which object is the server. Thus each of the supervisory managers communicates as the client with the supervisory server. In a similar fashion, the rate server, label server, external processing manager and device manager all communicate as clients with the supervisory managers, as servers. Likewise, the rate server administration object, the shipping client and the device manager administration object all communicate as clients with one or more of the objects appearing above them in FIG. 6 (namely rate server, label server, external processing manager and device manager). Thus it will be seen that certain objects function in a dual capacity, serving as client objects in some instances and serving as server objects in other instances. The presently preferred communications scheme permits objects to communicate with devices, external databases and other computer systems which are not part of the client/server logistics management system. To accommodate this certain objects are given the ability to communicate with the outside world. These objects include the device manager, which communicates with hardware devices, such as printers, bar code scanners, modems, postal scales and the like. Communication with external databases and other programs which do not form a part of the client/server logistics management system (e.g., accounting software packages, spreadsheet programs, operating system utilities and the like) are communicated with through the external processing manager. Because the presently preferred embodiment can be implemented in multiple CPU environments (distributed architecture), an announcement mechanism is provided in order to extend the communications scheme to multiple CPUs across a network. The supervisory managers are preprogrammed with the ability to send "announcements" across the network operating system according to the named pipe protocol which has been implemented. Thus, as illustrated in FIG. 6, each of the supervisory managers includes a communications pathway designated "announcements" through which communications with parts of the system operated by different CPUs are sent and received. The supervisory managers are not, themselves, responsible for coordinating this message passing between objects controlled by different CPUs. That function is reserved for the supervisory server, since the supervisory server occupies the unique position of controlling the registration process whereby client and server applications are made aware of each other in order to communicate. However, in order to distribute the announcement function, the supervisory managers are responsible for providing the actual announcement communications. In this regard, the supervisory managers act as servers, with the supervisory server in this instance, acting as the client. To illustrate this in FIG. 6, each of the supervisory managers is connected to the supervisory server by a second line of communication designed "receiver." It will be understood that these "receiver" connections represent a "reverse" client/server connection, in which the supervisory server acts as a client in order to request announcement services from the supervisory managers, acting as announcement servers. In summary, FIG. 6 illustrates the preferred IPC connections over which client/server communications take place. The presently preferred embodiment uses a tokenized message passing scheme in which all data is passed back and forth between client and server as ordered pairs of tokens and associated data values. The purpose of the token is to uniquely identify the data associated with it. Referring to Table II in the accompanying Appendix, a sample listing of tokens is presented. Reading the columns of Table II from left to right, the left-most column lists the token name; the column to its immediate right gives a brief description of the nature of the value associated with the token; the next right-most column lists the type declaration of the value; and the right-most column gives the maximum length of the value, where applicable. The tokenized message handling scheme is very flexible, in that new tokens can be added at any time to accommodate new features, without the need to rewrite all client and server data structures. This is in contrast to the conventional fixed field data structure used in conventional data communication schemes. In the conventional, fixed field data structure scheme adding a new data value often requires all program modules to be rewritten to accommodate the added data field. The tokenized message passing scheme of the present invention avoids this problem. If a new data field is required, to support a new feature, for example, a new token is created and only those objects which make use of the new value will need to be reprogrammed to scan for the newly added token. All remaining objects simply ignore tokens which are undefined for them. The presently preferred tokenized message passing scheme implements automatic data type conversion. As set forth in Table II, the type definitions of all values associated with tokens are predefined, thus the tokenized message passing scheme has advance knowledge of the data types of all values. This allows the tokenized message handling scheme to perform all data type conversions, removing the need for client and server objects to perform type conversions. In other words, a server can pass a long word value to a client which is expecting a string value. The tokenized message handling scheme performs the data conversion automatically so that the server does not need to be aware of the client's data type requirements and the client does not need to be aware of the server's data type requirements. External Processing Manager In order to allow the client server logistics management system to communicate with the outside world, e.g. with external data bases or other application programs, the external processing manager is provided. The external processing manager is, itself, a client of a supervisory manager, as illustrated in FIG. 6. The external processing manager, in turn, operates as a server to provide external processing functions to other clients. In FIG. 6 the shipping client uses the external processing manager for this purpose. In the preferred embodiment, the external processing manager interfaces with the REXX command interpreter supplied with the OS/2 operating system. The external processing manager is designed to receive its instructions from an ASCII file called a script file. If desired the script file can be encrypted to prevent unauthorized access. The script file comprises a list of program commands or instructions written in the REXX language. If desired, the REXX language command set can be extended to add additional commands. This may be done by embedding the additional commands in the external processing manager. The external processing manager would envoke the REXX interpreter and register itself as the source of the additional commands. In this way, the REXX interpreter would automatically pass control to the external processing manager to handle the additional commands. The external processing manager is designed to communicate directly with the REXX interpreter, passing the script file commands to the REXX interpreter and requesting the output of the REXX interpreter to be directed back to the external processing manager, where appropriate. In this way, the external processing manager is given access to the operating system and to all other application programs running on the operating system. This is a very powerful command which allows the logistics management system to interface with other applications which may not necessarily be designed to integrate directly with the logistics management system. For example, the external processing manager could use the REXX interpreter to send SQL queries to a database, in order to upload information about a customer's account from the accounting system software. The external processing manager's ability to handle scripts provides another powerful feature. Scripts may be written for the purpose of modifying the performance of other program objects comprising the logistics management system. Scripts can be used, for example, change the shipments client to provide a reminder message to the user in the event the user attempts to ship a package without first entering the weight of the package. Similarly, a script could be written to change the shipments client to supply a convenient list of package dimension sizes, allowing the operator to quickly fill in the size of a package in the appropriate field by simply selecting it from a list. In general, the scripting language can be used to provide virtually any custom tailoring that a shipper might want to implement. The REXX language is straightforward and easy to use, thus most customizing to meet the user's requirements can be done in the field, without the need to access or modify the underlying program source code. In running a script to modify the performance of a program object, the external processing manager uses the existing IPC mechanism. Through this mechanism the external processing manager can request a data item stored by the object or it may supply a data value as an input to the data object. In addition, the external processing manager can request that one or more operations defined for that object to be performed. Thus the external processing manager serves as an alternate to the normal user interface as a means for manipulating data or performing operations. From the foregoing it will be seen that the present invention provides a logistics management system comprising a plurality of building blocks or client/server objects. These objects can be configured to communicate in a variety of different ways to accommodate virtually any transportation-related logistics application. Thanks to the client/server architecture and the support for distributed architectures, the overall logistics management task is readily subdivided into highly self contained functional units. When changes in a given function are required, only the object providing the function normally needs to be changed. The client/server objects provide further flexibility through the external processing manager and scripting language, whereby individual objects can be modified to provide special features quite readily on an as needed basis. While the invention has been described in its presently preferred form, it will be understood that the principles of the invention may be extended to a wide variety of different forms. Accordingly, the preferred embodiment described herein should be considered as exemplary of the principles of the invention and not as a limitation of the scope of the claims.
TABLE II
__________________________________________________________________________
APPENDIX
TYPE MAXIMUM
I/O TOKEN VALUE DESCRIPTION DESCRIPTION
LENGTH
__________________________________________________________________________
Registry
To register a program:
REGISTER PROG.sub.-- ID.sub.-- . . . id from
string
PROGRAM PROGISTI.H machine on
ID which program is running
MACHINE blank if no network use
getmachinename( ) function
To unregister a program:
UNREGISTER
PROG.sub.-- ID.sub.-- . . . id from
string
PROGRAM PROGISTI.H machine on
ID which program is running
MACHINE blank if no network use
getmachinename( ) function
Use this to get a list of ALL programs running in the environment. If
FILENAME is blank, then either the program is not a server or it is a
server
you cannot use. For historical purposes, you may use ENUM SERVER as
well as ENUM PROGRAM.
ENUM your current/local machine
string
PROGRAM blank if no network use
MACHINE getmachinename( ) function
[ PROG.sub.-- ID.sub.-- . . . id from
string 150
ID PROGISTI.H user-friendly
NAME name of the program FOR
DISPLAY PURPOSES ONLY!!
TYPE "server type" mask from
ushort
MACHINE PROGISTI.H machine on
string
which program is running FOR
DISPLAY PURPOSES ONLY!!
ZONE where is the program running?
short
1 = on your local machine
2 = somewhere else
FILENAME pipe name you may use to
string
access server - BLANK IF
YOU CANNOT ACCESS
SERVER
. . . ]
Announcements
Use this to send an announcement. Only include the DATA token if you
need
it (it uses a queue slot on the receiving machines). You may include one
or
more specific machine names if you want the announcement sent to
specific
machines. If you don't specify MACHINE or if it is blank, the
announcement
will be sent to all machines currently in the environment.
ANNOUNCE ANN.sub.-- . . . from ANNOUNCE.H
long string
ANNOUN
ID optional string CE.sub.-- DATA
[DATA LEN]
[MACHINE destination machine name
string]
. . . ]
Miscellaneous
Use this to close the environment. This is harmless and will not close
anything that is not ready to be closed. It will never shut down a
machine.
SHUTDOWN
System Numbers
If QUERY/ENUM/MODIFY SYSNBR is used with an SYSNBR ID that does
not yet exist, an entry is automatically added to the number list with
these
defaults:
Last value
(VALUE) 0
used
First in (START) I
sequence
Limit/last in
(STOP) 2147483646
(maximum
sequence long)
In all cases, the value passed for TOK-SYSNBR must be non-zero (except
for ENUM) and unique within all programs that might ever be running in
the
system. The recommendation is to use the appropiate TOK.sub.-- . . .
define for
your SYSNBR value.
To got the next number in sequence:
QUERY see rules above short
SYSNBR
VALUE next number in sequence
long
To get the status of an entry in the number list:
ENUM see rules above short
SYSNBR
ID short
VALUE see doc above long
START see doc above long
STOP see doc above long
INCREMENT see doc above long
To get the status of all entries in the number list:
ENUM
SYSNBR (no value specified)
[
ID short
VALUE see doc above long
START see doc above long
STOP see doc above long
INCREMENT see doc above long
. . . ]
To change the status of an entry in the number list:
MODIFY
SYSNBR see rules above short
VALUE see doc above - optional
long
START see doc above - optional
long
STOP see doc above - opflonal
long
INCREMENT see doc above - optonal
long
If any optional token is not specified, the previous value is not
changed. This
can be used to change certain numbers without being required to change
others. For example, if you add to entry and want to use the defaults
for
START, STOP and INCREMENT but want to specify you own VALUE, you
can do it.
Shipper Maintenance
All of these commands deal with the master list of shippers. Clients can
access the master list via ENUM. An announcement is sent when any
shipper
information of any kind changes. This allows other programs to know when
they need to do another ENUM - especially if they are storing additional
shipper information in parallel with this master list. Other programs can
use
LOCK and UNLOCK to prevent a shipper from being deleted "out from under,
them."
To get full information on all current shippers:
ENUM
SHIPPER
[ Unique ID for this shipper
string SHPAB-
ID unique shipper short name BRLEN
SYMBOL
follows C rules for a variable
NAME user-friendly shipper name
string undefined
FOR DISPLAY PURPOSES
ONLY!!
ERRCODE validity/status of shipper
string SHPAB-
SHPNA name/address boolean BRLEN
SHPABBR shipper abbreviation
LOCK is shipper locked by some
. . . ] program?
To get full information on a shipper:
ENUM
SHIPPER shipper ID (from ENUM
SHIPPER)
ID unique ID for this shipper
string SHPAB-
SYMBOL unique shipper short name BRLEN
follows C rules for a variable
NAME user-friendly shipper name
string undefined
FOR DISPLAY PURPOSES
ONLY!!
ERRCODE validity/status of shipper
string SHPAB-
SHPNA name/address boolean BRLEN
SHPABBR shipper abbreviation
LOCK is shipper locked by some
program?
To change a shipper's lnformation:
MODIFY shipper ID (from ENU
string SHPAB-
SHIPPER SHIPPER) BRLEN
SHPNA name/address - optional
SHPABBR shipper abbreviation - optional string
To add a shipper:
ADD
SHIPPER
To delete a shipper:
DELETE shipper ID (from ENUM
SHIPPER SHIPPER)
To check-out a shipper to a program to prevent deleting:
LOCK shipper ID (from ENUM
SHIPPER SHIPPER)
PROGRAM PROG.sub.-- ID.sub.-- . . . ID from
PROGISTI.H
MACHINE machine on which program is
running string blank if no
network use
getmachinename( ) function
To check-in a shipper (UNLOCK):
UNLOCK shipper ID (from ENUM
SHIPPER SHIPPER)
PROGRAM PROG.sub.-- ID.sub.-- . . . ID from
PROGISTI.H
MACHINE machine on which program is
running string blank if no
network use
getmachinename( ) function
Commitment Code
To get the master list of available commitments:
ENUM
COMMIT-
MENT
[ COMMIT.sub.-- . . . ID from RATER.H
string undefined
ID Commitment short name
SYMBOL follows C rules for a variable
NAME user-friendly commitment
string undefined
name FOR DISPLAY
. . . ] PURPOSES ONLY!!
START use manifest mode? boolean]
[MANIFEST /* default package info */
[
SHIPDATE date (TDC) long 0
SHIPPER ID short 0
DONTBAND don't band yet boolean
SERVICE ID (see FDXRATER.H) short 0
PKGTYPE ID (see RATER.H) short 0
PAYTYPE payment type (see RATER.H)
|
Same subclass Same class Consider this |
||||||||||