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

IMSID Statement

IMSID Statement

The IMSID statement defines characteristics of the IMS source subsystem for PowerExchange IMS bulk data movement operations and IMS log-based CDC.
z/OS
IMS
Yes, for IMS bulk data movement operations and IMS log-based CDC
IMSID=(
ims_ssid
,
dbdlib
,RECON=(
recon1
[,
recon2
][,
recon3
]) ) or IMSID=(
ims_ssid
,DD:
XXXXXXXX
,RECON=(
recon1
[,
recon2
][,
recon3
]) )
ims_ssid
The IMS subsystem ID (SSID).
If you import source DBD information from the IMS catalog, this
ims_ssid
value is required and must match the
ims_ssid
value in an IMSBSDS statement.
For IMS log-based CDC, this
ims_ssid
value must match the
Recon Identifier
value specified in the registration group.
If you create data maps that use the
IMS ODBA
access method, this value is required for PowerExchange to connect to the IMS subsystem to access data.
dbdlib
or DD:
XXXXXXXX
Provides PowerExchange access to the IMS DBD which is required for activities such as reading IMS unload files, registering IMS sources for CDC, and running utilities, including DTLURDMO and DTLUCBRG. In this parameter, you can either specify the IMS DBD library dataset name in line or specify a DD name for PowerExchange to search. By specifying DD:
XXXXXXXX
, where
XXXXXXXX
is the DD name coded in the JCL for the component requiring access, you can have one or more DBD libraries for a system allocated to the specified DD name.
If you use the DD:
XXXXXXXX
, PowerExchange uses the first DBDLIB it finds in the concatenated list and continues processing. Ensure that you place this DD with the one or more DBD libraries in the appropriate JCL or started task.
RECON=(
recon1
,[
recon2
],[
recon3
])
Optional. The RECON data sets for IMS log-based CDC. If you include the RECON parameter, you must specify at least one data set name. You can enter each data set name on a separate line in the DBMOVER member.
  • You can specify up to 10 IMSID statements in a DBMOVER member.
  • PowerExchange does not require the IMSID statement to create data maps if you import DBD information for source objects from the DBDLIB library. However, when you perform IMS bulk data movement operations, PowerExchange matches the
    ims_ssid
    in the IMSID statement against the
    IMS SSID
    value in the data map to determine the DBDLIB data set to use. Also, for IMS log-based CDC, PowerExchange matches the
    ims_ssid
    value in the IMSID statement against the
    ims_ssid
    value in the
    Recon Identifier
    field in the registration group.
  • If you create data maps by importing DBD information for source objects from IMS catalog, the
    ims_ssid
    in the IMSID statement is required to find a matching IMSBSDS statement. If you create a registration group for IMS log-based CDC, the
    ims_ssid
    value in the
    Recon Identifier
    field matches against the
    ims_ssid
    value in an IMSBSDS statement.