To prepare the Xmanager started ask procedure, customize the execution parameters in the default procedure (PTXMAN) in hlq.CDBASAMP. You can accept the default values for the supplied execution parameters or can edit them to execute multiple Xmanagers and to implement cross-system support. You can assign default values to JCL symbolic parameters. You can also control Xmanager execution by providing optional parameters on the EXEC statement in the Xmanager JCL procedure.
The following Xmanager execution parameters are supplied in the PTXMAN JCL procedure in hlq.CDBASAMP:
Specifies the ID for this Xmanager task. Every Xmanager task executing on the same LPAR must be assigned a unique 4-digit numeric ID.
Accept the default value unless you are executing multiple Xmanager tasks on the same LPAR.
During Xmanager execution, the default value is converted to the current Xmanager version number. This setting facilitates migration to new Xmanager versions. Xmanager-based applications are able to connect to multiple Xmanager versions without having to change the XMANID that the application uses.
To enable communication between the Xmanager and the products, the XMANID value in the JCL must match the XMANID value in the SETUPxx global parmlib member. You can connect to multiple Xmanagers by maintaining multiple suffixed SETUPxx parmlib members. The XMANID parameter of each SETUPxx member corresponds to the XMANID JCL parameter for one of the Xmanagers.
Specifies the name of a member that is used to execute the modify commands automatically when Xmanager is started. Xmanager looks for the member upon startup and if found, the commands in the member are executed.
To execute commands automatically, create a member with as many commands as you want in the hlq.CDBAPXMP library. Note the following considerations:
Default: XMANINIT in hlq.CDBAPXMP
Example: The following sample member shows how to set the sysplex interval value to 0200 and start CA Subsystem Analyzer for DB2 for z/OS data collection on DB2 subsystems DB2$ when Xmanager starts.
Implements Xmanager cross-system communications support. In this environment, each Xmanager in a sysplex complex connects to all other Xmanagers in the same complex. These connections provide transparent access to any DB2 subsystem in the sysplex complex executing on a z/OS platform that has an active Xmanager task.
Enabling this support provides a distributed communications environment to access DB2 subsystems executing on any LPAR in a sysplex complex. When XSYS=Y, the Xmanager started task must be started on a z/OS system that is a member of a sysplex complex.
To implement cross-system support, adhere to the following guidelines:
An Xmanager started task must be active on each LPAR.
When starting each Xmanager started task, set XSYS to Y in the PTXMAN member in hlq.SPFSLIB to enable the cross-system communications support feature.
The following Xmanager execution parameters are optional and can be used to customize Xmanager behavior. They are not supplied in the PTXMAN JCL procedure that is installed in hlq.CDBASAMP.
The following optional execution parameters can be specified:
Specifies a numeric pair of storage limits interpreted in MB. The high value is optional, but if present it must be greater than the low value.
If the amount of available region storage falls below the high limit, a short on storage condition is signaled to the processes in the region. CA Detector® for DB2 for z/OS and CA Subsystem Analyzer for DB2 for z/OS recognize a short on storage condition and act to reduce their storage footprint before the shortage becomes critical. This action consists of suspending current active collections until the short on storage condition is relieved.
The low limit is considered a region critical limit. If the amount of available storage falls below the low limit, a short on storage condition is signaled and Xmanager region termination begins.
If you specify CUSHION with only one value, it is interpreted as the region critical limit.
Limits: 10 to 1000
If the amount of 64-bit storage that is used to hold memory objects plus the CUSH64(high) value exceeds the memory object limit, a short on storage condition is signaled to the processes in the region. CA Detector® for DB2 for z/OS and CA Subsystem Analyzer for DB2 for z/OS recognize a short on storage condition and act to reduce their storage footprint before the shortage becomes critical. This action consists of suspending current active collections until the short on storage condition is relieved.
The CUSH64(low) limit is considered a region critical limit. If the available 64-bit storage (memory object limit minus the memory object used) falls below this limit, a short on storage condition is signaled and Xmanager region termination begins.
Limits: 0 to 2147483647
Specifies how often (in minutes) to send status information to the System State Manager (SSM) component of CA OPS/MVS® Event Management and Automation. Status updates are provided on Xmanager events at a specified interval.
Limits: 0 to 30 minutes
Default: 5 minutes
The principal applications that execute in the Xmanager region are CA Detector® for DB2 for z/OS and CA Subsystem Analyzer for DB2 for z/OS. The monitoring activities of these applications can consume considerable storage. Especially, for example, if you enable CA Detector® for DB2 for z/OS collection options like dynamic SQL text statistics or additional view by keys. In addition, multiple DB2 subsystems can be monitored from a single Xmanager address space.
Specifies a member name in the PDS on the PXMPARM DD statement of the Xmanager. This member lets you pass a list of parameters exceeding 100 characters to your Xmanager startup job. Parameters are separated by a comma, for example:
The Xmanager processes this parameter first. If the JCL contains duplicate values, the values in this parameter are overridden.
Limits: 8 characters
Sets the Xmanager sysplex interval. The sysplex interval is an Xmanager managed time interval that you can use to provide a consistent time interval across all LPARS in a sysplex complex. Products such as CA Detector® for DB2 for z/OS and CA Subsystem Analyzer for DB2 for z/OS use this time interval to coordinate time-related activities. We recommend that you set this parameter by adding a PLEXINTV(hhmm) modify command to the XMANINIT member in the hlq.CDBAPXMP library.
Supplies a value that passes into the CA Health Checker common service. This parameter enables the CA Health Checker common service to access CA Database Management Solutions for DB2 for z/OS parmlib information. This parameter helps the CA Health Checker common service perform health checks successfully when two or more Xmanagers running on a single LPAR are sharing a parmlib.
The SUFFIX parameter overrides the ENV parameter. Do not specify these parameters together.
Limits: 2 characters
Starts an Xmanager communication trace. The communication trace writes diagnostic messages to the Xmanager job log for requests that are routed between Xmanager tasks in the sysplex complex. The communication trace is intended for CA Support use only and can result in many messages being written to the Xmanager job log and system console. The XTRACE modify command can also control the Xmanager communications trace.
Example: Specify Optional Execution Parameters
The following example shows how to use the OPT= parameter to specify the optional execution parameters:
Example: Perform Health Checks for Multiple Xmanagers
After integration is completed with the IBM Health Checker and the CA Health Checker common service, several health checks are performed for licensed products automatically when Xmanager is started.
Within the Xmanager started task output, there are messages indicating that the Health Checker has started and ended:
GEN0901 CA-DB2 Tools Health Checker task attached
GEN0911 CA-DB2 Tools Health Checker interface initialization in progress
GEN0912 CA-DB2 Tools Health Checker interface initialization complete
GEN0913 CA-DB2 Tools Health Checker interface termination in progress
GEN0914 CA-DB2 Tools Health Checker interface termination complete
Under SDSF, you can display the health checks using the CK command. With CA SYSVIEW® Performance Management, you can display and update health check parameters. For example:
To display all health checks that are performed on an LPAR, specify:
To display only CA Database Management Solutions for DB2 for z/OS health checks, specify: