Browse Prior Art Database

Intermemory Communications Facility

IP.com Disclosure Number: IPCOM000086915D
Original Publication Date: 1976-Nov-01
Included in the Prior Art Database: 2005-Mar-03
Document File: 8 page(s) / 26K

Publishing Venue

IBM

Related People

Wyman, L: AUTHOR

Abstract

A system communication manager (SCM) program component includes a program-to-program communications function that supports the transfer of messages or data between two or more programs. That is, each program that requires the ability to access data generated by one or more other programs, executing in environments in which the data is not directly addressable, will use the program-to-program communications functions to accomplish the desired data transfer from one program to another. Specifically, these functions will be used to exchange data between the: 1) Debug/Test Commands component which executes in a user memory and a Programming Support Vehicle (PSV) component which executes in a PSV memory (either of the same terminal/library processor as the user memory or on a connected test execution processor).

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 18% of the total text.

Page 1 of 8

Intermemory Communications Facility

A system communication manager (SCM) program component includes a program-to-program communications function that supports the transfer of messages or data between two or more programs. That is, each program that requires the ability to access data generated by one or more other programs, executing in environments in which the data is not directly addressable, will use the program-to-program communications functions to accomplish the desired data transfer from one program to another. Specifically, these functions will be used to exchange data between the: 1) Debug/Test Commands component which executes in a user memory and a Programming Support Vehicle (PSV) component which executes in a PSV memory (either of the same terminal/library processor as the user memory or on a connected test execution processor). 2) Library Subsystem functions which execute in the Advanced System Development Automation (ASDA) Library Manager memory and the Library Service Routine functions which execute in the ASDA user memory.

The program-to-program communications functions consist of a set of Supervisor Call Instruction (SVC) service routines that are invoked by the using program through Programming Language System (PLS) macro instructions. These service routines and their corresponding macro interfaces are defined as follows:

A. Create Message Queue - This function causes a message queue to be created and made available for the reception of messages transmitted to it by programs executing in other virtual memories on either the same or different processors. That is, each program that requires the ability to receive data from one or more other programs executing in different virtual memories will create a message queue that will be used by the creating program to receive messages transmitted to it by the sending program(s). The form of the create message queue macro (in PLS notation) is: ? label: CREATEQ QNAME (message queue name)

QID (message queue ID name)

TYPE ( FIFO )

PRIORITY

DOMAIN ( PROCESSOR )

TERMLIB

LIST, list name

RTCD (return code name)

QNAME - specifies the name of an 8 byte area that contains the user supplied name the message queue will be

known and accessed by. This area may contain any

unique bit pattern (i.e., any combination of

alpha-numeric characters and/or hit settings may be used

as a queue name as long as it is unique to the domain

the queue is being created to service). The only

exception to this rule is that qnames must not begin with the characters 'GBL' which are reserved for SCM usage. (See DOMAIN parameter.)

QID - specifies the name of an 8 byte area into which the

1

Page 2 of 8

SCM generated message queue ID will be returned upon

successful queue creation. This ID will be used to

reference the specified queue by subsequent SCM

requests.

TYPE - specifies the message enqueuing discipline to be used when messages are sent to the queue.

FIFO - specifies that messages will be enqueued using...