Table of Contents

Search

  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

Sample Netport Jobs

Sample Netport Jobs

PowerExchange provides sample netport jobs in the RUNLIB library. Customize the job that best fits your situation.
The following members contain sample JCL:
  • CAPXJCL, for CDC data sources
  • IMSJCL, for IMS bulk data sources
  • GDGJCL and TAPEJCL, for bulk data sources other than IMS
  • NETJCL, for examples of substitution variables
The CAPXJCL, GDGJCL, and TAPEJCL members run the PowerExchange Listener for netport jobs, DTLLST3. The IMSJCL member runs an IMS PROC, DLIBATCH. The NETJCL runs IEFBR14.
If you need other netport jobs, create them by using the JCL of one of the sample members as a template.
The sample members include REGION statements that allocate 64 MB of memory for non-IMS jobs or 128 MB of memory for IMS jobs. Verify that the JCL for netport jobs allocates sufficient memory for the PowerExchange processing in your environment. Memory usage is a particular concern if PowerExchange must perform an ICU-based code page conversion.
If IDMS access is required and the SECURITY parameter in the DBMOVER configuration file is set to 2 (each user who submits an IDMS access job must have their user ID and password checked by the relevant security package), you must use a netport job. Copy the TAPEJCL member under a new and relevant name. Make sure that the PowerExchange copies of the IDMS.LOADLIB and IDMS.DBA.LOADLIB libraries are in the STEPLIB. Code the following DD statement in the JCL that you created:
//SYSIDMS DD DSN=&HLQ..RUNLIB(DTLDMCL), // DISP=(SHR)
Ensure that the relevant SYSCTL statement is included in the JCL for Central Versions, or the following DD statements if running local:
//IDMSDCT INCLUDE MEMBER=IDMSDICT //IDMSFIL INCLUDE MEMBER=IDMSFILE
These members will need the relevant dictionary definitions and database file definitions.
The PowerExchange Listener must be restarted to detect a new netport job.