Browse Prior Art Database

Access to Non-Office Objects from the MVS Office Environment

IP.com Disclosure Number: IPCOM000108566D
Original Publication Date: 1992-Jun-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 2 page(s) / 92K

Publishing Venue

IBM

Related People

Cox, D: AUTHOR [+4]

Abstract

This article addresses the need to provide the interchange of non-Office Objects from the user's In-Basket in OfficeVision*/MVS environments. The problem is to allow the office user to have a connection to non-office objects in the world of MVS. A non-office object is one which is created outside of the Office environment. This can be a MVS data set, such as a Partitioned Data Set (PDS) member or a sequential flat file or a CMS file from VM. The connection must provide the Office user with the ability to send and receive these objects from an Office environment. The current situation is that these non office objects flow within the control of JES for MVS or RSCS for VM and office objects only flow within the world of System Network Architecture Distribution System (SNA/DS) and DISOSS.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Access to Non-Office Objects from the MVS Office Environment

       This article addresses the need to provide the
interchange of non-Office Objects from the user's In-Basket in
OfficeVision*/MVS environments.  The problem is to allow the office
user to have a connection to non-office objects in the world of MVS.
A non-office object is one which is created outside of the Office
environment.  This can be a MVS data set, such as a Partitioned Data
Set (PDS) member or a sequential flat file or a CMS file from VM.
The connection must provide the Office user with the ability to send
and receive these objects from an Office environment. The current
situation is that these non office objects flow within the control of
JES for MVS or RSCS for VM and office objects only flow within the
world of System Network Architecture Distribution System (SNA/DS) and
DISOSS.

      The solution is to provide an Office component that will send
and receive non-office objects from MVS and provide the transport
mechanism to connect to the Office environment.  This component would
be located in APPC/MVS and provide a JES subsystem interface, in a
similar manner as the Interactive Data Transmission Facility does
today for the TSO user.  The component must provide an interface in
the Office environment which will provide the mechanism for both
sending objects from the Office environment and receiving non-office
objects into the Office environment.

      The first step is to define the non-office object into the
Office environment.  MVS non-office objects are transmitted in
Netdata format.  This format must be converted to an Office
architecture format.  The Office format should be defined as a Host
EBCDIC file, similar to the PC file structure allowed today.  The
information kept in the Netdata header would be converted into
Document Profile parameters.  These parameters would be used to build
the Netdata header when sending objects out of the Office
environment.  The limitation on the data type would be the same as
the one used between VM and MVS today, that only sequential files or
single members of a PDS be sent at one time.

      To receive non-office...