How to pass execution options to an IMS tool which will be internally invoked by another IMS tool.


Article ID: 50176


Updated On:


CA Distributed Database Management CA Database Analyzer for DB2 for Oracle CA Database Analyzer (IMS Tools) CA Mainframe Configuration Manager for IMS for z/OS IMS TOOLS - MISC CA Compress Data Compression (IMS Tools) CA Database Analyzer for IMS for z/OS CA Database Copier for IMS for z/OS CA Database Organizer for IMS for z/OS CA Mainframe Extended Terminal Manager (IMS Tools) CA High Performance Recovery for IMS for z/OS CA Database Organizer (IMS Tools) CA Mainframe Program Restart Manager for IMS for z/OS CA Secondary Index Builder for IMS for z/OS CA Secondary Index for IMS for z/OS



If an IMS tool is invoked by another IMS tool (the execution options are via the DD statement DBOCTRL) those options can only be passed to the tool which would be executed first.

How can the execution options be passed to another (subsequently) invoked IMS tool?


If execution options must be passed to an IMS tool which will be called internally by another IMS tool, the global options parameter DD statement IDIPARM needs to be used.

On the IDIPARM global options dataset, a member matching the corresponding function-related standard member name must be present and this member must have those options defined which need to be used for this execution.

For all function-related standard member names on IDIPARM: see Installation Guide, Appendix A, 'Global Parameter Members'.


DBO reload will be executed with option AUTOINDEXBUILD=YES to build all secondary indexes, which results in SIB being internally invoked by DBO.

To tell SIB to write execution progress information every 1000 records, the IDIPARM dataset must be used in the DBO reload job control, and on this dataset a member SIBIBLD (standard member name for INDEXBUILD) must be present, containing execution option PROGRESSREPORT=1000.


Component: DBO