A system, method and article of manufacture to remotely configure and utilize an emulated device controller via an encrypted communication protocol

The invention relates generally to a data processing system, method and article of manufacture allowing for the dynamic reconfiguration of an input/output device controller. In particular, the present invention relates to a computer-based system, method and article of manufacture which supports and facilitates a remote configuration and utilization of an emulated input/output device controller via encrypted data communication between a plurality of users and said controller.

The present invention provides for secured, real-time, configuration and utilization of an emulated input/output device controller. The instant invention advances the art by allowing its practice to be supported via an encrypted communications protocol interfacing with, and relying upon, the teachings, practices and claims disclosed in co-pending United States Patent Applications 09/239,425 and 09/255,837 (hereinafter synonymously referred to as "Secure Agent" or "SA").

The following overview is provided to facilitate a comprehensive understanding of the teachings of the instant invention. Secure Agent utilizes a secure login sequence wherein a client connects to a Secure Agent server using a key known to both systems and a client connects and presents the server with user identification (as used herein the term "client" refers synonymously to a remote user establishing, and communicating with the instant invention through Secure Agent allocation and encryption processes as taught in the above noted applications). If recognized, the Secure Agent server initiates a protocol whereby the client's identification is verified and subsequent communication is conducted within a secured (encrypted) construct. For purposes of this overview, the term "server" should be considered a hardware configuration represented as a central processing unit wherein Secure Agent, a Host DLL and driver reside, and are executed. The term "DLL" as used herein refers to a Secure Agent host dynamically linked library (a.k.a. Host DLL). The term "DLL" or "dynamically linked library"-is used in a manner consistent with that known to those skilled in the art. Specifically, the term "DLL" refers to a library of executable functions or data that can be - used by a Windows application. As such, the instant invention provides for one or more particular functions and program access to such functions by creating a static or dynamic link to the DLL of reference, with "static links" remaining constant during program execution and "dynamic links" created by the program as needed.

The Secure Agent server presents a variable unit of data, such as the time of day, to the client as a challenge. The client must then encrypt that data and supply it back to the server. If the server is able to decrypt the data using the stored client's key so that the result matches the original unencrypted challenge data, the user is considered authenticated and the connection continue. The key is never passed between the two systems and is therefore never at risk of exposure.

The initial variable unit of data seeds the transmission of subsequent data so that the traffic for each client server session is unique. Further, each byte of data transmitted is influenced by the values of previously sent data. Therefore, the connection is secure across any communication passageway including public networks such as, but not limited to, the Internet. The distance between the client and server is not of consequence but is typically a remote connection. For accountability purposes, the actions of a client may be recorded (logged) to non-volatile storage at almost any detail level desired.

The access rights of each client (what the client is able to accomplish during a session) is governed by data stored on the Secure Agent server to which the client is associated. - As an example, such rights might encompass the ability to administer and utilize the services of the server system, which would, in turn, include capabilities such as adding new client users, changing a user's rights, transferring new code to the server, using a feature (or service) of the server and more.

Consequently, Secure Agent allows for the transmission of new code to the server and for that code to be implemented upon demand by a client. Such dynamic, real-time implementation in turn, allows for the behavior of the server to be modified. It is to this behavior modification the instant invention addresses its teachings, and thereby advances the contemporary art.

As will be readily appreciated by those skilled in the art, though the instant invention utilizes encryption/decryption and code recognition technology associated with Secure Agent, an alternative technology may be employed in support of the instant invention without departing from the disclosure, teachings and claims presented herein.

The present invention is best viewed as comprised of two server components with one or more client subcomponents or subprocesses disclosed in association thereto. It can be further conceptualized that a distinguishable client component exists for each emulated device type recognized by the invention's server, with an individual client supporting the simultaneous use of a plurality of client-side components. As used throughout the instant invention specification and claims, the term "server" is used synonymously with "emulated device controller", "server central processing unit", "server CPU", and "remotely configurable input/output device controller" and the term "client" is used synonymously with "host user", "client central processing unit", "client CPU" and "remote user".

The invention's lower-most server component layer is a device driver to communicate directly with one or more hardware components attached to one or more computer systems, such as, but not limited to, mainframe computers (a.k.a. host processors). The driver controls the hardware in a manner prescribed by its design, causing it to interact with the other computer systems to which it is connected as if it were one or more device types (emulation). The driver additionally acts as a conduit to a higher level server component that governs the overall behavior of the emulated devices. This higher level component primarily supplies the driver with new data to provide through the emulated devices to the other computers to which it is connected and accepts data arriving to the emulated devices carried up by the device driver. Both layers predominantly operate on a device by device basis. The higher level server component. in turn, serves as the interface between Secure Agent technology and remotely connected clients allowing for the encrypted transmission of all data external to the server.

Using the example of an IBM 3215 console, a client would connect to a server and request a list of the 3215 devices which shared membership to the user's security groups. The user would select a device and a logical pathway from the mainframe computer to the client's system would become established. The client would communicate through the server layers with the end result of messages transported from a mainframe through an emulated device to the client for presentation within a window on a computer screen. Conversely, commands to the mainframe may be issued at the client's workstation and are transported through to the emulated device then through it to the mainframe.

Just as a client might have the ability to administer users (i.e. add/remove), a client might be able to modify the presence and behavior of emulated devices, via Secure Agent administrative functions as taught by the afore noted pending patent applications. Allowable configuration ranges and values are verified and enforced according to rules by the server. The various data elements that may be controlled are listed at the bottom of this section. The server disallows modification of the active configuration (apart from device names and their security groups) and forces such modifications to be made to an inactive configuration. This inactive configuration may be swapped with the active configuration (thus activating it) upon demand. Thus, a new configuration may be prepared prior to a decision made to put it into effect. Additional control functionality includes but is not limited to the following:

Recycling an adaptor that is connected to an external computer system. This is commonly referred to as a Power On Reset or, more simply, a POR. <ul id="ul0001" list-style="bullet" compact="compact"><li>Viewing which users are connected to which devices.</li><li>Disconnecting a client user from a device to which he is connected.</li><li>Activating an inactive configuration.</li><li>Copying the active configuration to the inactive configuration in order to make changes based upon the active configuration.</li><li>Purging the inactive configuration in order to start fresh.</li></ul>

Consequently it is an object of the instant invention to provide for remote control, operation and use of a server Central Processing Unit (CPU).

A further object of the instant invention is to provide for a secured logon sequence utilizing encrypted data transmission in accordance with the teachings, disclosure and claims of the above noted pending patent applications.

Yet another object of the instant invention is to insure that all data transferred external of the emulated input/output device controller is encrypted in accordance with the teachings of the above noted pending patent applications.

A further object of the instant invention is to provide the ability for an administrator to alter and manage the configuration of emulated mainframe peripheral devices.

A further object of the instant invention is to allow the selective addition or restriction in the presence of devices to one or more host processors such as, but not limited to, mainframe computers.

Another object of the instant invention is to provide for a configuration specification which provides the ability to arbitrarily name each emulated device and assign it to one or more security groups of which a user must be a member in order to access that particular device.

An additional object of the present invention is to provide the capability by which an administrator may add and remove one or more users with respect to emulated input/output device allocation.

Yet another object of the instant invention is to provide a facility by which an administrator may manage the security groups to which a user belongs, thus controlling the access of devices by users at any level desired down to an individual user level.

A further object of the instant invention is to provide the ability for a user to access and operate an emulated input/output device.

Yet another object of the instant invention is to provide the facility by which an administrator may effect/implement new device emulation types.

Another object of the instant invention is to provide support for multiple device types which may be simultaneously supported and operated.

Responsive to the foregoing challenges, the Applicant has developed an innovative system, method and article of manufacture to remotely configure and utilize an emulated device controller via an encrypted validation communication protocol.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only, and are not restrictive of the invention as claimed. The accompanying drawings, which are incorporated herein by reference, and which constitute a part of this specification, illustrate certain embodiments of the invention and, together with the detailed description, serve to explain the principles of the present invention.

In this respect, before explaining at least one embodiment of the invention in detail, it is to be understood that the invention is not limited in this application to the details of construction and to the arrangement so the components set forth in the following description or illustrated in the drawings. The invention is capable of other embodiments and of being practiced and carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein are for the purpose of description and should not be regarded as limiting. As such, those skilled in the art will appreciate that the conception, upon which this disclosure is based, may readily be utilized as a basis for the designing of other structures, methods and systems for carrying out the several purposes of the present invention. It is important, therefore that the claims be regarded as including such equivalent constructions insofar as they do not depart from the spirit and scope of the present invention.

Additional objects and advantages of the invention are set forth, in part, in the description which follows and, in part, will be apparent to one of ordinary skill in the art from the description and/or from the practice of the invention.

These together with other objects of the invention, along with the various features of novelty which characterize the invention, are pointed out with particularity in the claims annexed to and forming a part of this disclosure. For a better understanding of the invention, its operating advantages and the specific objects attained by its uses, reference would be had to the accompanying drawings, depictions and descriptive matter in which there is illustrated preferred embodiments and results of the invention. <ul id="ul0002" list-style="none"><li>Figure 1 is a system schematic providing a conceptual overview of primary hardware and software components of the instant invention as practiced in its preferred embodiment.</li><li>Figure 2 is a logic flow diagram illustrating processing steps associated with the server initialization processing subcomponent of the instant invention when practiced in its preferred embodiment.</li><li>Figure 3 is a logic flow diagram illustrating processing steps associated with the server termination processing subcomponent of the instant invention when practiced in its preferred embodiment.</li><li>Figure 4 is a logic flow diagram illustrating processing steps associated with the adaptor configuration load processing subcomponent of the instant invention when practiced in its preferred embodiment.</li><li>Figure 5 is a logic flow diagram illustrating processing steps associated with the client connection processing subcomponent of the instant invention when practiced in its preferred embodiment.</li><li>Figure 6 is a logic flow diagram illustrating processing steps associated with the client disconnection processing subcomponent of the instant invention when practiced in its preferred embodiment.</li><li>Figure 7 is a logic flow diagram illustrating processing steps associated with administrative functions given illustrative user response/input strings.</li></ul>

While the making and using of various embodiments of the present invention are discussed in detail below, it should be appreciated that the present invention provides for inventive concepts capable of being embodied in a variety of specific contexts. The specific embodiments discussed herein are merely illustrative of specific manners in which to make and use the invention and are not-to-be interpreted as limiting the scope of the instant invention.

While the invention has been described with a certain degree of particularity, it is clear that many changes may be made in the details of construction and the arrangement of components without departing from the spirit and scope of this disclosure. It is understood that the invention is not limited to the embodiments set forth herein for purposes of exemplification, but is to be limited only by the scope of the attached claim or claims, including the full range of equivalency to which each element thereof is entitled. Turning now to Figure 1.

In Figure 1, a server CPU 103 has executing under control of its control program, Secure Agent software 106. The present invention advances the art and improves upon technology taught and claimed in the above noted pending applications, said applications and teachings incorporated by reference herein. The server 103 also has operating under control of its control program the remote configuration software 109 of the instant invention. Embodied within the server 103 is a hardware adaptor card 112. Said adaptor card 112 is in turn communicably attached to one or more host processors (121, 124, 127, 128). As used herein, the term "adaptor" refers synonymously to those hardware configurations such as, but not limited to, "adaptor cards" which allow for connectability between two or more central processing units and the transference of data associated therewith. Illustrative non-limiting examples of such adaptors as used herein would include Crossroads ESCON adaptors, Crossroads ESCON parallel adaptors, Bus-Tech adaptors and IBM ESCON adaptors.

In Figure 1, the host processors (121, 124, 127, 128) are illustrated as Host 1 128 executing as its control program a VM- system, Host 2 121 operating under as its control program a CICS system, Host 3 124 operating under the controller of its control program an IMS system and Host 4 127 operating under the dispatching control of its control program (ACP) a plurality of application specific programs. In turn, each of the host processors 128, 121, 124 and 127 illustrated in Figure 1, have connected to it one or more physical input/output devices 131. In Figure 1, said input/output devices are depicted as tape drives 141, direct access storage device 138 and smart terminals/personal computer/client computing capabilities 135. Also shown in Figure 1 is a plurality of clients referred to as Host users 145 which are communicably attached to the server 103 of the instant invention via a communications network 148 such as, but not limited to the Internet or other computer compatible network wherein computer recognized and generated signals may be communicated between one or more central processing units.

Lastly shown in Figure 1 is a Security Administrator client 151 interactively communicating with the Secure Agent software 106 operating within the server 103. As will be discussed in further detail and in association with Figures 2 through 7, the Security

Administrator 151 utilizes Secure Agent software 106 to administer and maintain user/resource profiles 157 and further communicates with information conveyed to said Secure Agent software 106 via the software processes associated with the remote configuration software 109 of the instant invention.

For purposes of clarity and to assist in comprehension of the instant invention, it is convenient to view the invention as being comprised of a number of processing subcomponents. Such processing subcomponents include, but are not limited to, Server Initialization Server Termination, Adaptor Configuration Load, Client Communication, Client Termination and Administration related subcomponents.

The following discussion in association with Figure 1 provides a brief non-limiting synopsis of the teachings of the instant invention and generally discusses the interrelationships of hardware and software processing components of the instant invention. In Figure 1, a Security Administrator 151 defines via Secure Agent software 106, user and resource profiles 157. Such profiles are stored in a non-volatile storage medium, such as but not limited to, a disk drive 158. User resource records are those records which typically define security group or groups, and access control variables associated with the user. Stated succinctly, the user resource record/profile defines those resources that the user may utilize and the bounds of such utilization. The Security Administrator 151 may also define resource profiles, such resource profiles define the device type and grouping of emulated input/output devices as well as central processing unit designations associated with each emulated device type and/or grouping. When attempting to establish a session between a host user 145 and any one of the operating systems and/or application programs operating under the dispatching control of the operating systems of host processors 128, 121, 124 or 127, a user via a communications network 148 communicates first with Secure Agent software 106 operating within the server 103 of the instant invention 109. Assuming the user 145 is recognized as an authenticated and authorized user of the system as governed by Secure Agent software 106, the user 145 next requests a device or a device grouping of emulated input/output devices he or she anticipates utilizing in the requested session. The Secure Agent so software 106 verifies the user 145 as authority to allocate such emulated input/output devices and correspondingly associates such devices with the user and user session between one or more of the host processors 128, 121, 124 and 127. Once established, the session continues as normal with input/output requests of the user serviced via emulated input/output device as opposed to the real input/output devices 131 associated with one or more of the host processors. Upon completion of the session or a specific deallocation request initiated by the user, the client termination subprocess of the instant invention deallocates the emulated input/output device or devices. As indicated, the processing subcomponents of the instant invention further include Adaptor Configuration Load, Client Communication, Client Termination, Administration, Server Initialization and Server Termination subprocesses. It is to such subprocesses Figures 2 through 7 address themselves. A more detailed disclosure of each subprocess follows.

Figure 2 discloses in further detail the process steps in which the server of the instant invention is initialized. While discussion of the individual subprocesses is provided in an illustrative logic sequence, it is to be noted that process steps defined therein need not occur in a serial manner. Rather it is expressly recognized that many of the subprocesses execution steps may be executed in a concurrent manner, or have their execution sequence factored upon the statusing of a previously executed process step.

With respect to server initialization, the driver of the instant invention first initializes all driver module-wide variables, such as clearing out how many adaptors are being supported, 201. Once these variables have been initialized, adaptors are located by enumerating all peripheral component interconnect computer Bus-type (PCI) devices present in the system using data and techniques published by the PCI Special Interest Group and. by Microsoft's Window's NT Device Driver Kit (DDK). Specifically, the adaptor vendor and device IDs 202 are referenced to identify the presence of such supported adaptors. For each adaptor located, adaptor specific variables are initialized by the driver 203, with the resources used by the adaptor, such as buffer areas and IRQ (interrupt request lines) being next allocated and reserved 204 using functions provided by DDK. The adaptor is then reset 205 by the driver using a technique made known by the adaptor's manufacturer. Since these adaptors are generally intelligent it is necessary to transfer (download) to them microcode (a manufacturer-supplied program specific to such a device) that controls internal instruction sequencing. Therefore, microcode is downloaded into the adaptor 206 in a manner prescribed by the adaptor manufacturer with the adaptor then considered initialized 207. The driver next requests a connection to each unique IRQ so that any interrupts generated by any of the recognized adaptors may be serviced by the driver 208 and next initiates timer support 209 so that approximately once every second, general operations may be performed on behalf of each adaptor. This support typically, though not limitedly, includes ensuring an adaptor does not generate a non-detected interrupt. Having once initiated its timer 209, the driver next exposes standard module-wide support to all applications 210, which allows for communications with the driver as to be established by the Host DLL.

Subsequent to the driver initialization, the Host DLL initializes variables it utilizes 211 and clears a user connection block to allow information for each user to be represented 212. The Host DLL further exposes and makes available to Secure Agent a block of data, representing an emulated device specific administrative instruction set 213, for each user. In addition to such normal data elements as a user ID and password, this instruction set advises Secure Agent to maintain device type and security group strings on behalf of each user specifically for the support of this Host DLL. The device types limits those types of emulated devices to which a user might claim access whereas the device security groups name the emulated device security groups to which a user is subscribed. In addition, at this stage linkage to configuration support routines within the Host DLL is also established. As practiced in one embodiment of the invention, the root name of the administrative tree structure is exposed to Secure Agent indicating that the Host DLL supports the configuration of information and will respond in a positive manner to requests for information and management of branches under this particular root. The I-lost DLL next creates a mutex serialization mechanism to be used by configuration support routines during access of adaptor configuration data to insure data integrity 214. This serialization mechanism is used to prevent for example potential simultaneous updates by multiple administrators as well as to prevent a client from enumerating emulated devices while it is being manipulated.

The Host DLL continues to open or otherwise establishes communication with the driver 215 and requests from it a number of recognized adaptors 216 to which the driver responds 217, whereupon the Host DLL requests from the driver its version number 218 to which the driver also responds 219. The Host DLL then records into a Secure Agent log the driver version and the number of adaptors it controls 220, and proceeds to indicate that each adaptor is not yet in a condition to support client connectivity 221. Data representing the adaptor configuration to be utilized (the active configuration) is next loaded 223. This data specifies device types and number of devices to be emulated, in conjunction with user-friendly (readable) names and security groups for each such emulated device. A second unique set of this data is loaded (the inactive configuration) 224 on behalf of this same adaptor to be used as a work area for administrators. This allows administrators to accumulate a series of configuration changes prior to effecting the activation of those changes as a whole. During said initialization, the Host DLL lastly ensures that the loaded adaptor configurations are within operationally permissible parameters 225.

Figure 3 is a logic flow diagram illustrating processing steps associated with the server termination processing subcomponents of the instant invention as practiced in its preferred embodiment. Turning now to Figure 3.

In Figure 3 with respect to server termination, the Host DLL first disconnects each currently connected user 301. Such disconnection is facilitated via processing accommodated in the Client Disconnection Processing subcomponent as will be discussed in association with Figure 6. Recognized adaptors are then set offline to their channels through the Adaptor Configuration Load processing subcomponent 302. The [lost DLL next ceases communication, or closes the driver 303, and frees all allocated storage and resources 304. The one second timer is then closed by the driver 305 and module-wide exposure of support to application through NT is eliminated 306. The driver then ensures / verifies each adaptor is offline to the channel and the adaptor is reset 307, disconnects all previously connected IRQ's 308, and destroys each object instance 309. Such destruction further includes but is not limited to elimination of exposure of the emulated devices support to applications through NT 310 and the freeing of all allocated storage and resources 311.

Figure 4 is a logic flow diagram illustrating- the processing steps associated with the Adaptor Configuration Load processing subcomponent of the instant invention as practiced in its preferred embodiment.

In Figure 4 the Host DLL first indicates the adaptor's unavailability 401 and for each client currently connected to a logical unit on this adaptor, issues a message to the client indicating that the client is being disconnected due to administrative device management 402. The Host DLL then performs the client disconnection services in association with the invention's Client disconnection subprocess as will be discussed in further detail in association with Figure 6. The Host DLL continues by next recording into Secure Agent log the configuration for this adaptor is being loaded 403 and if the adaptor is to) be forced offline to the mainframe to which it is connected 404, prepare and uses an empty configuration indicating that Emulated devices are not to be emulated during this session. If the adaptor is not to be forced offline, an active configuration for the adaptor is provided and a request that the adaptor using the active configuration data is initiated 405. The driver as instructed causes the adaptor to be offline to the channel at this stage in the adaptor configuration load 406, destroys each of the adaptor emulated devices driver object instances 407 causing or eliminating the exposure of emulated devices support to applications through NT 408 and frees all allocated storage and resources 409. The driver next determines if Emulated devices are to be emulated 410 and then request that the adaptor be brought online to the channel 411, lastly indicating that the adaptor is available for client use 412.

Figure 5 is a logic flow diagram illustrating the processing steps associated with the Client Connection processing subcomponent of the instant invention as practiced in its preferred embodiment.

In Figure 5, a client connection first initializes variables that it utilizes 501 then employs Secure Agent client code in order to establish a connection to the Host DLL 502, whereupon the Host DLL retains the client's name 503 and loads the client's device type and security groups 504. A new client object instance is then created to represent this new client connection with the variables it will use becoming initialized 505. The Host DLL then stores the location of the client object in a user connection block 506. At this point the client sends to the Host DLL the command version level that represents the client feature set as a means to facilitate backward compatibility by future Host DLLs 507 which the Host DLL stores for possible reference 508. By knowing the version of the client, the Host DLL can and will prevent communicating with older clients in a manner supported only by newer clients, whereas newer clients will be able to take advantage of a fuller set of features that the Host DLL offers. The client next provides to the Host DLL the emulated device type in which it is interested 509 whereupon the Host DLL stores it for later reference 510. The client then requests of the Host DLL its command version level 511 that the client stores for possible reference 513. Just as with the Host DLL being able to restrict its behavior for older clients, since the client knows the version level of the Host DLL it can restrict itself from attempting to take advantage of features available only on newer servers whereas newer servers might be more fully exploited. The client then requests from the Host DLL a list of the currently available emulated devices to which the client may connect 514. The Host DLL returns the response back 515 whereupon the client selects one of the emulated devices and requests that the Host DLL establish a connection to it on its behalf 516.

Figure 6 is a logic flow diagram illustrating the processing steps associated with Client Disconnection processing subcomponent of the instant invention as practiced in its preferred embodiment.

As can be seen in Figure 6, the Host DLL destroys the client object instance which requires the following activity. If connected to a logical unit, the logical unit is closed 601 and the threads that were created to perform input/output device of the logical unit, if any, are terminated 602. If connected to a logical unit, the logical unit-in-use flag is set to not in use 603 and if connected to a logical unit, the logical unit client value is set to none 604. The Host DLL lastly frees all allocated storage and resources for the client object 605.

When an administrator desires to modify the configuration of adaptors managed by the Host DLL it issues requests for enumeration of the "/Adaptors" root and its branches to which the Host DLL will respond. This provides the administrator with the means necessary to discover what information exists to be changed. The data exposed through these branches correlates to the data within the active and inactive configurations for each adaptor.

Once supplied with the name and value of a piece of adaptor configuration data an administrator can decide whether or not to make changes to it and, if so, supply that name with a new value back to the Host DLL which will then make that change on the administrator's behalf.

Additionally, an administrator may enumerate a series of controls that can be employed for special actions by the Host DLL against an adaptor. Specifically, an administrator might decide to activate the inactive configuration, whereupon the Host DLL will exchange the data of the active configuration with that of the inactive configuration then perform the actions detailed with Adaptor Configuration Load, Figure 4. If, on the other hand, an administrator opted to copy the contents of the active configuration into that of the inactive configuration then the Host DLL would perform that action. An administrator also has the option to simply clear out the inactive configuration whereupon the Host DLL would reinitialize it to reflect the absence of configured emulated devices. If an administrator decided it was necessary to reinitialize the adaptor then he could specify that the Host DLL do so whereupon it would perform the actions detailed with Adaptor Configuration Load, Figure 4. Finally, if an administrator decided that an adaptor should either be kept offline or could come back online then he could request that of the Host DLL and it would toggle that state for the adaptor then perform the actions detailed with Adaptor Configuration Load, Figure 4.

Non-limiting examples of dialog and processing as provided for in the invention's administrative configuration subcomponent follow immediately for purposes of facilitating full and enabling disclosure.

When the adaptor interrupts with a message relating to Connected Client Traffic from the Logical Unit: Mainframe Message (3215 Example) from the mainframe then that message is first caught by the driver emulated devices object and carried up into the Host DLL by a thread created on behalf of the client that performs I/O against the Logical unit. This message is then transmitted through SA to the client.

When the adaptor is found to go online or offline to the channel relating to Connected Client Traffic from Logical Unit: Online or Offline Event (3215 Example) then that event is first caught by the driver emulated devices object and carried up into the Host DLL by a thread created on behalf of the client that performs I/O against the Logical unit. This event is then transmitted through SA to the client.

The Connected Client Traffic from Client Mainframe Command (3215 example), the client may send a mainframe command to the Host DLL which is immediately transported to the driver emulated devices object by a thread created on behalf of the client that performs I/O against the Logical unit. The driver emulated devices object then requests that the adaptor send the command to the mainframe.

Figure 7 is a logic flow diagram illustrating processing steps associated with administrative functions given non-limiting examples of user input command strings. Turning now to Figure 7.

Administration of Adaptor Configuration Data: Input Request = Enumerate Branch/Adaptors

Administrator requests an enumeration of "/ESCON Adaptors" 701.

Host DLL builds and returns a string consisting of a concatenation of all the adaptors, in the form of Adaptor # where # is the 1-based number of the adaptor, along with a flag for each indicating that each element has, in turn, more branches 702.

Administration of Adaptor Configuration Data: Input Request = Enumerate Branch /Adaptors/Adaptor #

Administrator requests an enumeration of, for example, "/Adaptors/Adaptor 1" 703.

Host DLL builds and returns a string consisting of a concatenation of "Active Configuration" and "Inactive Configuration", each with a flag for each indicating that they have, in turn, more branches, along with a string of "Configuration Control" with a flag indicating that it has values 702.

Administration of Adaptor Configuration Data: Input Request = Enumerate Branch Adaptors/Adaptor #/(In)Active Configuration

Administrator requests an enumeration of, for example, "/Adaptors/Adaptor I/Active Configuration" 704.

Host DLL builds and returns a string consisting of a concatenation of 16 CUs, in the form of Control Unit x## where ## is hexadecimal from 00 through 0F, along with a flag for each indicating that each element has, in turn, more branches 702.

Administration of Adaptor Configuration Data: Input Request = Enumerate Branch/Adaptors/Adaptor#/(In)Active Configuration/Control Unit x##

Administrator requests an enumeration of, for example, "/Adaptors/Adaptor 1/Active Configuration/Control Unit x00" 705.

Host DLL builds and returns a string consisting of a concatenation of "Assignments" and "Logical Units", each with a flag indicating that they have values 702.

Administration of Adaptor Configuration Data: Input Request = Enumerate Branch/Adaptors/Adaptor#/(In)Active Configuration/Control Unit x##/Assignments

Administrator requests an enumeration of, for example, "/Adaptors/Adaptor I/Inactive Configuration/Control Unit x00/Assignments" 706.

Host DLL builds and returns a string consisting of a concatenation of the following: 702 <ul id="ul0003" list-style="none"><li>A. "Controller Type" with a flag indicating the data presentation to be a drop-down box. This includes a list of all of the valid CUTypes (i.e. 7412, 3174) along with the currently assigned value. This value is taken from the specified Adaptor configuration data for this adaptor, indexed to the specified control unit.</li><li>B. "Base Address" with a flag indicating the data presentation to be a text box. This includes the currently assigned value. This value is taken from the specified Adaptor configuration data for this adaptor, indexed to the specified control unit.</li><li>C. "Device Count" with a flag indicating the data presentation to be a text box. This includes the currently assigned value. This value is taken from the specified Adaptor configuration data for this adaptor, indexed to the specified control unit.</li><li>D. If the specified Adaptor configuration is the active configuration then a flag is added to all fields marking them as non-modifiable meaning that this data cannot be changed. For these particular datas only that within the inactive configuration may be worked upon.</li></ul>

Administration of Adaptor Configuration Data: Input Request = Enumerate Branch/Adaptors/Adaptor#/(In)Active Configuration/Control Unit x##/Logical Units

Administrator requests an enumeration of, for example, "/Adaptors/Adaptor I/Inactive Configuration/Control Unit x00/Logical Units" 707.

Host DLL builds and returns a string consisting of a concatenation of the following: 702 <ul id="ul0004" list-style="none" compact="compact"><li>A. For each emulated devices per Logical Unit Count for the specified Adaptor configuration data for this adaptor, indexed to the specified control unit (the following uses of ## is the current Logical Unit Count entry + the Logical Unit Base, providing the emulated devices address as it appears to the mainframe.): <ul id="ul0005" list-style="none"><li>1. "Device x## Name(s)" with a flag indicating this is a text box. This includes the currently assigned value per the specified Adaptor configuration data for this adaptor, indexed to the specified CU and emulated devices per the current Logical Unit Count entry.</li><li>2. "Device x## Group(s)" with a flag indicating this is a text box. This includes the currently assigned value per the specified Adaptor configuration data for this adaptor, indexed to the specified CU and emulated devices per the current Logical Unit Count entry.</li><li>3. If the specified Adaptor configuration is the active configuration: <ul id="ul0006" list-style="none" compact="compact"><li>a. "Device x## Status" with a flag indicating this is a text box. This includes either the currently assigned emulated devices Client value (client user id) if the emulated devices In-Use flag indicates "in use", otherwise "this device is not in use". The emulated devices values involved are per the specified Adaptor configuration data for this adaptor, indexed to the specified CU and emulated devices per the current Logical Unit Count entry. This field is marked as non-modifiable meaning that this data cannot be changed (informational only).</li></ul></li></ul></li></ul>

Administration of Adaptor Configuration Data: Input Request = Enumerate Branch /Adaptors/Adaptor #/Configuration Control

Administrator requests an enumeration of, for example, "/Adaptors/Adaptor 1/Configuration Control" 708.

Host DLL builds and returns a string consisting of a concatenation of the following: 702 <ul id="ul0007" list-style="none" compact="compact"><li>A. "Check this then click save to activate the inactive configuration" with a flag indicating this is a check box and a value of unchecked.</li><li>B. "Check this then click save to copy the inactive configuration to the inactive" with a flag indicating this is a check box and a value of unchecked.</li><li>C. "Check then click save to purge the inactive configuration" with a flag indicating this is a check box and a value of unchecked.</li><li>D. "Check this then click save to POR the adaptor" with a flag indicating this is a check box and a value of unchecked.</li><li>E. "Force adaptor offline" with a flag indicating this is a check box. This includes the currently assigned value per the specified Adaptor configuration data for this adaptor.</li></ul>

Continuing with non-illustrated, non-limiting examples of Administrative processing functionality: <ul id="ul0008" list-style="none"><li>Administration of Adaptor Configuration Data: Data Assignment of a /Adaptors/Adaptor ##/(In)Active Configuration/Control Unit x## Logical Units value: Administrator <ul id="ul0009" list-style="none" compact="compact"><li>1. Requests an assignment of any modifiable value under "/Adaptors/Adaptor #/(In)Active Configuration/Control Unit x##/Logical Units" providing the new value along with the path to the data name. Host DLL.</li><li>2. Assigns the specified data of the adaptor, indexed to the specified CU and Logical Unit, to the provided value.</li><li>3. Saves the data to non-volatile storage through SA.</li><li>4. If the change was to an emulated devices Name then, if that emulated devices is currently in use by a user per the emulated devices In-Use flag, use the emulated devices Client value to locate the client object then issue that client a message indicating the new emulated devices name.</li><li>5. If the change was to an emulated devices Groups then, if that emulated devices is currently in use by a user per the emulated devices In-Use flag, use the emulated devices Client value to locate the client object and revalidate the client's authority exactly as is in accordance with Client Connection discussion. If the client no longer has the authority to access the device then send him a message to that effect and perform Client Disconnection processing.</li></ul></li><li>Administration of Adaptor Configuration Data: Data Assignment of a /Adaptors/Adaptor #/(In)Active Configuration/Control Unit x##/Assignments value: <ul id="ul0010" list-style="none" compact="compact"><li>1. Administrator requests an assignment of any modifiable value under "Adaptors/Adaptor#/(In)Active Configuration/Control Unit x##/Assignments", providing the new value along with the path to the data name. Host DLL.</li><li>2. Ensures that every Logical Unit Base and Logical Unit Count is within the ranges established (and published) as acceptable to the adaptors and IBM mainframe computers. If not then reject the change.</li><li>3. Assigns the specified data of the adaptor, indexed to the specified CU, to the provided value.</li><li>4. Saves the data to non-volatile storage through SA.</li></ul></li><li>Administration of Adaptor Configuration Data: Admin checked /Adaptors/Adaptor #/Configuration Control/Check this then click save to activate the inactive configuration <ul id="ul0011" list-style="none" compact="compact"><li>1. Administrator requests to activate the inactive configuration of the specified adaptor. Host DLL</li><li>2. Uses the configuration datas for the specified adaptor.</li><li>3. Indicates that the adaptor is unavailable for use by clients.</li><li>4. For each client currently connected to an emulated devices on this adaptor: <ul id="ul0012" list-style="none" compact="compact"><li>A. Issue a message to the client indicating that they are being disconnected due to administrator device management.</li><li>B. Perform <b>Client Disconnection.</b></li></ul></li><li>5. Exchanges the contents of the active configuration with that of the inactive configuration.</li><li>6. Saves the configurations to non-volatile storage through SA.</li><li>7. Performs Adaptor Configuration Load.</li></ul></li><li>Administration of Adaptor Configuration Data: Admin checked /Adaptors/Adaptor #/Configuration Control/Check this then click save to copy the inactive configuration to the inactive <ul id="ul0013" list-style="none" compact="compact"><li>1. Administrator requests to copy the active configuration to the inactive configuration of the specified adaptor. Host DLL</li><li>2. Uses the configuration datas for the specified adaptor.</li><li>3. Copies the contents of the active configuration into the inactive configuration.</li><li>4. Saves the inactive configuration to non-volatile storage through SA.</li></ul></li><li>Administration of Adaptor Configuration Data: Admin checked /Adaptors/Adaptor #/Configuration Control/Check then click save to purge the inactive configuration <ul id="ul0014" list-style="none" compact="compact"><li>1. Administrator requests to purge the inactive configuration of the specified adaptor. Host DLL</li><li>2. Uses the inactive configuration data for the specified adaptor.</li><li>3. Clear it out to default values as does Start Server when a configuration doesn't exist. In summary, all of the CUTypes are assigned to 7412 and everything else is assigned to 0.</li><li>4. Saves the inactive configuration to non-volatile storage through SA.</li></ul></li><li>Administration of Adaptor Configuration Data: Admin checked /Adaptors/Adaptor #/Configuration Control/Check this then click save to POR the adaptor</li><li>Administrator requests to perform a Power On Reset (POR, or an offline/online recycle) of the specified adaptor.</li><li>Host DLL performs Adaptor Configuration Load for the specified adaptor.</li><li>Administration of Adaptor Configuration Data: Admin checked /Adaptors/Adaptor #/Configuration Control/Force adaptor offline</li><li>Administrator <ul id="ul0015" list-style="none" compact="compact"><li>1. Requests a change to the flag that controls whether or not the adaptor is to be forced offline to the mainframe to which it is connected.</li><li /></ul></li><li>Host DLL <ul id="ul0016" list-style="none" compact="compact"><li>2. Assigns the supplied setting to the data for the specified adaptor.</li><li>3. Saves the value to non-volatile stored through SA.</li><li>4. Performs Adaptor Configuration Load.</li></ul></li></ul>

While this invention has been described to illustrative embodiments, this description is not to be construed in a limiting sense. Various modifications and combinations of the illustrative embodiments as well as other embodiments will be apparent to those skilled in the art upon referencing this disclosure. It is therefore intended that this disclosure encompass any such modifications or embodiments.

It will be apparent to those skilled in the art that various modifications and variations can be made in the construction, configuration, and/or operation of the present invention without departing from the scope or spirit of the invention. For example, in the embodiments mentioned above, variations in the materials used to make each element of the invention may vary without departing from the scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of the invention provided they come within the scope of the appended claims and their equivalents.