The DDM TCP/IP server does not use transaction program names (TPNs) as the Advanced Program-to-Program Communication (APPC) server does. However, the use of prestart jobs by the TCP/IP server provides a way to start a service job in that environment.
Note, however, that with the introduction of the function associated with the QRWOPTIONS data area usage, you might not need to start a service job in many cases. That feature allows one to start traces and do other diagnostic functions. You might still need to start a service job if you need a trace of the connection phase of the job.
You can use the Display Log (DSPLOG) command to find the CPI3E34 message reporting the name of the server job being used for a given connection if the following statements are true:
You can then use the Start Service Job (STRSRVJOB) command.
If you do need to trace the connect statement, or do not have time to do manual setup on the server after the connection, you will need to anticipate what prestart job will be used for the connection before it happens. One way to do that is to prevent other users from connecting during the time of your test, if possible, and end all of the prestart jobs except one.
You can force the number of prestart jobs to be 1 by setting the following parameters on the Change Prestart Job Entry (CHGPJE) command for QRWTSRVR running in QSYSWRK to the values specified here:
If you use this technique, be sure to change the parameters back to values that are reasonable for your environment; otherwise, users will get the message that 'A connection with a remote socket was reset by that socket' when trying to connect when the one prestart job is busy.