Customize Xnet

Execution Manager Networking (Xnet) provides a communications subsystem that the CA Database Management Solutions for DB2 for z/OS share. Xnet executes as a started task in its own address space and works with the Execution Manager (Xmanager) address space for the CA Database Management Solutions for DB2 for z/OS.
Execution Manager Networking (Xnet) provides a communications subsystem that the CA Database Management Solutions for DB2 for z/OS share. Xnet executes as a started task in its own address space and works with the Execution Manager (Xmanager) address space for the CA Database Management Solutions for DB2 for z/OS.
Xnet, like Xmanager, must be running at all times. Xnet uses minimal system resources (CPU and memory) when the agents for the CA Database Management Solutions for DB2 for z/OS are not actively communicating. Xnet also requires an external security manager (ESM) product like CA ACF2, CA Top Secret, or IBM RACF with the System Authorization Facility (SAF) interface.
The basic Xnet customization enables Xnet to be started so that correct operation of the major Xnet components can be verified. For example, the Xmanager connection and TCP/IP services. This customization must be done only once. Additional customization is required to enable Xnet use with the CA Database Management Solutions for DB2 for z/OS and other products.
Follow these steps:
  1. Gather the following information:
    • The XMANID that is assigned to the Xmanager component. This value is defined during Xmanager customization.
    • The STC name of the IBM TCP/IP address space.
    • The TCP/IP port number for use by the Xnet TCP/IP listener.
    • The fully-qualified data set name of the APF-authorized IBM Db2 load module data set for the most recent version of IBM Db2 for z/OS that is installed on the system where Xnet will be executing.
    To obtain the STC name and TCP/IP port number, coordinate as needed with other personnel that are responsible for the communications components of your z/OS system.
  2. Complete Xnet customization:
    1. Select option
      2 (Customize)
      from the Post-Install Tailoring menu and press Enter.
      The Select PTISYS Parmlib Members panel appears.
    2. Select a PTISYS parmlib member and press Enter.
      The Product Customization panel appears.
    3. Type
      S
      next to
      PXN (Xnet)
      and press Enter.
      The PXN Xnet Customization menu appears.
    4. Select the following options to prepare the JCL procedures for Xnet started tasks and allocate the Xnet runtime log file data sets:
Review the Xnet Customization Member
Review the Xnet customization member before you begin the actual Xnet customization. This member summarizes the required customization tasks and provides installation processing instructions.
Allocate Xnet Log File Data Sets
Two twenty cylinder permanent log file data sets are allocated for Xnet use. These data sets are standard sequential data sets that will contain informational, warning, error, and trace messages that are logged during Xnet execution. Xnet logging switches between the data sets as each one fills up while Xnet is running. A third smaller data set is also allocated and used in the Xnet JCL procedure (PXNPROC) to prevent the accidental startup of more than one instance of the primary Xnet address space. PXNPROC is set to use the data sets as allocated by PXNALLOC.
After selecting this option (2 – Allocate the Xnet log file data sets) on the Xnet Customization menu, the PXNALLOC sample job is displayed in an edit session. Follow the instructions in the JCL comments to prepare the JOB and then submit it to perform the data set allocations. Return code zero (0) is expected. The sample JOB is saved in the CDBASAMP data set.
These data sets can be deleted and reallocated any time Xnet is down to change the size or location of the data sets.
You must allocate the log files before you try to start Xnet.
Prepare the Xnet JCL (PXNPROC)
PXNPROC is provided in the CDBASAMP data set. To prepare the JCL, follow the instructions in the JCL comments and specify the following values:
  • The XMANID that you selected for your Xmanager.
  • The STC name of your IBM TCP/IP address space.
  • The TCP/IP port number for use by Xnet. Xnet establishes a TCP/IP listener on the port that you specify.
  • The IBM DB2 load module data set name.
Save your changes and then copy this procedure to a z/OS system PROCLIB that is used for started task JCL procedures that are started using the z/OS START command.
Xnet security definitions must be created before attempting to start Xnet.
Prepare the Xnet Execution Space JCL (PXNPROCE)
The Xnet execution space (XES) JCL member (PXNPROCE) is provided in the CDBASAMP data set. The XES component gives Xnet the ability to start, stop, and manage auxiliary z/OS address spaces. These address spaces are used to execute units of work on behalf of the products that are part of the
CA Database Management Solutions for DB2 for z/OS
. Prepare the JCL as described (specify the IBM DB2 load module data set name). Save your changes and then copy this procedure to a z/OS system PROCLIB where you copied the previously created PXNPROC JCL.
In the initial release of XES features, auxiliary address spaces are used to increase the availability of the agents that work with
CA Chorus™
.
Edit the Xnet Startup Parameters (PXNPARM)
Sample startup parameters for Xnet are distributed in member PXNPARM in the CDBAPARM data set. Review and edit the comments in this member directly or from the Xnet Customization panel by selecting option 5 - Edit the Xnet initialization parms (PXNPARM).
The Xnet startup parameters establish operational settings that are processed each time Xnet is started. All parameters have default values that are established during Xnet initialization. Most default values are appropriate for all users.