If you omit the W (wait), then the response may not appear in the job's output. 1. Route command may have receiving an end of message before the actual command response is received. 2. Routing commands can take time for the other system to respond. 3. Starting DB2 has multiple single line messages. By waiting, you ignore the end of message and will receive multiple messages up to the timeout. You hope that the response is in the job's output.
There may also be another side effect. By using W, you are providing a delay between each of the start DB2 commands. Maybe the delay solved a problem where starting multiple DB2's at the same time causes a problem. I doubt this is the case for DB2 but other commands may have have a timing problem. Jon Perryman On Tuesday, July 1, 2014 7:12 PM, Shmuel Metz (Seymour J.) <shmuel+ibm-m...@patriot.net> wrote: ITYM 'why is there a "W" in front of the "/"' As others have told you, >it stands for "wait". > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
