Original Publication Date: 1995-May-01
Included in the Prior Art Database: 2005-Mar-30
Duffield, DM: AUTHOR [+7]
Disclosed is a distributed graphical interface to selected OS/400* functions without requiring an emulation session.
a distributed graphical interface to selected
OS/400* functions without requiring an emulation session.
Graphical Operations (GraphicOps) provides a distributed
graphical interface on an OS/2* or Windows** client to selected
OS/400 server functions. With GraphicOps, users can manage their
AS/400* printer output, jobs, messages, and objects. This
simplified, easy-to-learn and easy-to-understand graphical user
interface reduces the need for users to understand and use
traditional OS/400 user interfaces.
application user's perspective, GraphicOps coexists in
the client environment as a Windows or OS/2 application. The user
has the ability to move between GraphicOps and other applications
without closing either. For example, when the user wants to work
with their AS/400 printing they can move directly into the GraphicOps
view of that function, perform their task, and return directly to the
previous application. It will not be necessary to exit the
application or switch to an emulation session where the user would
have to navigate OS/400's hierarchical menu structure to find the
desired printing functions.
In GraphicOps, there are two major types of objects
available to the
o Workstation objects
o AS/400 resources
objects are objects that exist on the personal
computer and are used to group, summarize, and work with AS/400
resources. They do not exist on the AS/400 system. For example, the
Batch Job List is a workstation object that lists jobs on the AS/400
system and allows the GraphicOps user to work with them. Workstation
objects primarily consist of:
o Work Areas - Work areas group together related objects to assist
the user in performing tasks.
o Templates - Templates are used to create new workstation objects
or AS/400 objects. For example, the Job List Template is used
create another job list with the same settings as the template.
You can think of a template as a cookie cutter. You create a
mold or shape that you use to create more cookies that look
o Instances - Instances are basically the cookies that come from
the cookie cutters. The instances of workstation objects that
come shipped with GraphicOps are what we cut out. For example,
the Batch Job List is an instance of the Job List Template. A
user can create their own instances from templates and refine
them once created.
resources include AS/400 objects and other resources
that reside on the AS/400 system which can be represented by
GraphicOps. OS/400 Graphical Operations supports management and use
of the followi...