Browse Prior Art Database

Spooling in the MVS Office Environment

IP.com Disclosure Number: IPCOM000106983D
Original Publication Date: 1992-Jan-01
Included in the Prior Art Database: 2005-Mar-21
Document File: 1 page(s) / 47K

Publishing Venue

IBM

Related People

Cox, DR: AUTHOR [+3]

Abstract

This article describes the problem for OfficeVision*/MVS (OV/MVS) that Office Components need to spool data out to disk for safekeeping during execution. Rather than risking loss in case of a system failure or abnormal termination of a task, data can be placed on a spool. To be able to complete complex or distributed transactions outside the confines of a management system, such as CICS/MVS*, the spool function is essential.

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

Spooling in the MVS Office Environment

       This article describes the problem for OfficeVision*/MVS
(OV/MVS) that Office Components need to spool data out to disk for
safekeeping during execution. Rather than risking loss in case of a
system failure or abnormal termination of a task, data can be placed
on a spool. To be able to complete complex or distributed
transactions outside the confines of a management system, such as
CICS/MVS*, the spool function is essential.

      The solution is to provide a general spool function that will
allow access for all components in OV/MVS.  This function would be
located in APPC/MVS and provide an interface in CICS and other
requestor environments. The function would maintain one or more
spools or disk queues. The function would accept the data and then
carry out asynchronous I/O. The function would perform like a queue
manager. It would prevent the spool from being a system bottleneck,
yet provide a guaranteed safestore of transaction information. The
interface would accept the request and place it on the spool queue
and return to the caller. It would capture the information needed to
restore the transaction, in case of abnormal termination or a backout
request. It would provide the ability to place data on the spool,
delete items from the queue, and retrieve items from the queue at
initialization or transaction request. The task would accept items
from both a local or remote LU 6.2 conversation and from Cross Memory
Servi...