Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
What Your Subsystem Initialization Routine Can Do z/OS MVS Using the Subsystem Interface SA38-0679-00 |
|
One of the things that you must do to initialize your subsystem is to tell the SSI what function codes and function routines your subsystem supports. This is done by building an SSVT. The SSI provides the IEFSSVT macro to build your subsystem's SSVT. See Building the SSVT for more information. After building your subsystem's SSVT, your subsystem initialization routine must let MVS™ know that your subsystem is active and ready to accept SSI requests. The following are examples of other things your subsystem initialization
routine can do:
Prior to z/OS® V1R12,
the subsystem initialization routines specified in parmlib member
IEFSSNxx were invoked in the sequence they appeared and under a task
that never terminated. From z/OS V1R12,
the initialization routines are invoked in parallel after the BEGINPARALLEL
keyword in parmlib member IEFSSNxx is processed, and no longer run
under a permanent task when they are run in parallel. Because of
this, you should examine your subsystem initialization routines to
see if they allocate resources that will be freed at task termination
when previously the resources would have remain held. Resources to
consider:
For more information, see Initializing Your Subsystem. |
Copyright IBM Corporation 1990, 2014
|