Text preview for : B232 Software Subsystems in MVS; Antognini.pdf part of IBM B232 Software Subsystems in MVS; Antognini IBM share SHARE_61_Proceedings_Volume_1_Summer_1983 B232 Software Subsystems in MVS; Antognini.pdf
Back to : B232 Software Subsystems | Home
:SSHARE:
- = SHARE SESSION REPORT
B232 Software Subsystems in MVS 225
SHARE NO. SESSION NO. SESSION TITLE ATTENDANCE
MVSE MVS Project Mary Jane Akin NNL
PROJECT SESSION CHAIRMAN INST. CODE
Northwestern Nat'l Life, Route 3235, 20 Washington Ave. S., Minneapolis,
MN 55440, 612-372-5695
SESSION CHAIRMAN'S COMPANY, ADDRESS, AND PHONE NUMBER SOFTWARE SUBSYSTEMS IN MVS
Session B232, SHARE 61
24 August 1983
James Antognini (IBM) described the elements of subsystems: Identification to
New York NY
MVS, initialization, subsystem interface, subsystem function support,
authoirzation, restrictions, command broadcast, notification of other events,
and uses and advantages.
A copy of the foils from this presentation and a paper are attached.
James Antognini
IBN Santa Teresa Laboratory
555 Bailey Avenue
San Jose CA 95150
....
o.-J
17 August 1983, 11:16:01
~
Abstract
Subsystems in the classical MVS sense are often spoken of but
seldom understood even though they are integral to MVS (the
master and job entry subsystems). Subsystems are programs
started through the master subsystem; they are able to accept
broadcast of commands, to be notified of other events and to
communicate through the subsystem interface. This paper deals
with the elements of subsystems: Identification to MVS,
initialization, subsystem interface, subsystem function
support, authorization, restrictions, command broadcast,
notification of other events, and uses and advantages.
Examples are taken from a user-written subsystem and from JES2.
Permission is granted to SHARE to publish this presentation paper in the
SHARE Proceedings. IBM retains its right to distribute copies of this
presentation to whomever it chooses.
3/J/ear/l
Antognini MVS Software Subsystems page 2 Antognini MVS Software Subsystems page 3
character-may be placed in the SCHEDULR macro and become part of the
SYSGEN process; the name may be ins