IBM SC33-1683-02 Server User Manual


 
Output
Register 15
Contains the following completion codes:
0 Communication terminated successfully
Nonzero
Request failed.
Customizing the sample overseer program
The sample overseer program consists of four modules link-edited together. The
main module is DFH$AXRO; the other three modules are subroutines, described
below:
DFH$AGCB
sets up request parameter lists (RPLs), access method control blocks
(ACBs), and parameter lists.
DFH$ADSP
displays status information.
DFH$ARES
performs restart in place.
The associated DSECTs are provided in member DFH$XRDS of
CICSTS13.CICS.SDFHSAMP. There are several ways in which you can change the
supplied code to make the overseer program more suitable for your installation.
Here are some customization suggestions:
v If the supplied display of status information (DSECT DSPDS) is not suitable, you
can change the layout for your installation. You may also want to change the
content of the status display if you are using DBCTL. The supplied sample
overseer program does not read the DBCTL-related information from the CAVM
data sets, and so cannot display DBCTL information on the MVS console. If you
want this to be displayed, you have to issue a DFHWOSM FUNC=READ macro
to retrieve the global data, and you have to change the status display to
accommodate the extra information. DFHWOSM FUNC=READ is described on
page 619.
v The CSECT DFH$ADSP can be customized so that, for example, status
information is displayed automatically at regular intervals, or whenever a region is
in trouble, as well as when the console operator enters the Display command.
This would require interpretation of the status information by the overseer.
v Any of the messages to the system console, which are listed in the prolog of the
source module DFH$AXRO, can be changed.
v You can change the format or the content of the DFHOSD data set (DSECT
OSDDS) if, for example, you want it to contain more information.
v You can change the restart function so that, for example, a failed region is
restarted only during periods of heavy use, while at other times a takeover to the
alternate is initiated by the operator.
v When an active region fails and is taken over by the alternate, the old active
region must be restarted as the new alternate. In those cases where the cause of
the takeover was not an MVS failure, restart of the old active as an alternate
region could be automated in the overseer program.
DFHWOSM macros
Chapter 22. The extended recovery facility overseer program 623