Browse Prior Art Database

Access to a MVS Command Processor from the Office Environment

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

Publishing Venue

IBM

Related People

Cox, D: AUTHOR [+4]

Abstract

This article addresses the need to provide the ability for an Office user to access an MVS Command Processor and route the reply to the user's In-Basket. The problem is to be able to offer the Office user an MVS executable environment. The Office user would like to be able to execute CLIST or REXX programs within the MVS environment, without the currently required TSO address space. The request for execution would flow from the user to this environment. The output or results from this program execution would flow back to the user.

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

Access to a MVS Command Processor from the Office Environment

       This article addresses the need to provide the ability
for an Office user to access an MVS Command Processor and route the
reply to the user's In-Basket.  The problem is to be able to offer
the Office user an MVS executable environment. The Office user would
like to be able to execute CLIST or REXX programs within the MVS
environment, without the currently required TSO address space.  The
request for execution would flow from the user to this environment.
The output or results from this program execution would flow back to
the user.

      The solution is to provide a general function that will create
a MVS executable environment and interface to the Office Mail
facility.  This function would be located in APPC/MVS and would be
available to the entire Office environment.  The function is able to
accept command language, either CLIST or REXX, execute it, and return
the results. The results can be returned either synchronously through
a LU 6.2 request or asynchronously with an Office Object.

      The user must create a Host EBCDIC Office Object containing a
command language program.  This Object is then sent to the function,
which creates the environment for execution.  The function has access
to MVS datasets and databases.  The output or results are placed into
another Host EBCDIC Object.  The results are either errors from the
execution or messages normally displayed on the terminal....