Table of Contents


  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. PowerExchange Globalization
  12. Using the PowerExchange ODBC Drivers
  13. PowerExchange Datatypes and Conversion Matrix
  14. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  15. Appendix B: PowerExchange Glossary

Setting Up Netport Jobs for GDGs

Setting Up Netport Jobs for GDGs

To set up a netport job for a GDG, complete the following steps.
  1. Determine an available z/OS port number to use with the netport job.
    In the example syntax in the following steps, this port number is “7777.”
  2. Add a NODE statement to your source and target DBMOVER configuration files. For example:
    If you use ODBC drivers to point from partner software, you need to add a driver for this new location.
  3. Update the DBMOVER configuration file in the RUNLIB library on z/OS:
    Add a LISTENER statement:
    LISTENER=(node1,TCPIP,2480) LISTENER=(node1,TCPIP,7777)
    To indicate to the z/OS PowerExchange Listener that the second port is associated with a netport, add a NETPORT statement with the same port number. For example:
  4. Create the GDGJCL member in the RUNLIB library.
    You can use the TAPEJCL member as a template. Add a job card with "%N5" appended to it, and any other DDs that you might need for your PowerExchange Listener job.
    When the z/OS PowerExchange Listener detects activity on the netport, instead of directly trying to service it, the Listener tries to submit the JCL file that is specified in the fifth positional parameter of the NETPORT statement to the JES internal reader. As the JES reader reads and submits the JCL, it scans every JCL line for %
    tokens, where
    is a numeric value from 1 through 8. The JES reader substitutes these tokens with the appropriate values from parameters 6 through 13 in the NETPORT statement.
    Do not confuse the %
    tokens with the %N
    tokens. The %N
    tokens are used to generate incremented numeric values of
    You can then submit the GDGJCL job whenever a request is received through the assigned port for the netport job. This action enables a job to end and another job to begin and process the GDGs on z/OS appropriately.
  5. Stop and restart the PowerExchange Listener on z/OS.
    Whenever you access a GDG, point to the z/OS GDG location instead of to the z/OS location.


We’d like to hear from you!