Each TDP must be defined as a subsystem.
- Create or modify the IEFSSNxx member of SYS1.PARMLIB to include TDP subsystem names.
The IEFSSNxx member is described in the IBM publication z/OS MVS Initialization and Tuning Reference available at http://www-01.ibm.com/support/knowledgecenter/. The IEFSSNxx member is only used by MVS, never directly by TDP.
The following is an example using keyword parameter notation:
SUBSYS SUBNAME(TDP0) INITRTN(TDPISSI) /*Production system*/ SUBSYS SUBNAME(TDP1) INITRTN(TDPISSI) /*Test system*/
The following is an example using positional parameter notation:
TDP0,TDPISSI PRODUCTION SYSTEM TDP1,TDPISSI TEST SYSTEM
The TDP0 and TDP1 subsystems are defined when you perform the next IPL.
- Execute TDPISSI (TDP Initialize SubSystem Interface) to establish the TDP subsystem.TDPISSI is the initialization program for the TDP subsystem. It allows TDP to use primary subsystem services.
When executed, TDPISSI can only fail if the TDPid is not TDPa, where a is any character valid for a subsystem name. Otherwise, execution is successful, as indicated by a return code of zero - no messages are issued.
You only need the most recent version of TDPISSI to support all your existing releases of Teradata software. The highest level of TDPISSI is downward compatible with other releases of the Teradata software.TDPISSI must always execute successfully before TDP starts. If TDP starts before TDPISSI completes executing, TDP will end abnormally.If either of the following conditions is true, TDPISSI must be manually executed:
- You do not specify TDPISSI in the appropriate IEFSSNxx member of SYS1.PARMLIB
- TDP subsystem definitions are not dynamically added after IPL, but before you start TDP
Specifying TDPISSI for each TDP subsystem minimizes the possibility of TDP starting before TDPISSI completes its execution as a batch job.