Jon Perryman wrote: >If you omit the W (wait), then the response may not appear in the job's output.
Indeed. >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. Things can getting messy there if you're in a hurry. >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. You can resolve the waiting in a REXX program. Activate a CONSOLE, do a SYSCMD and do your getmsg function with a long enough delay value. Evaluate each message and decide what to do next. Repeat for each DB2 subsystem. Oh, remember to deactivate your CONSOLE. Alternatively use an automation product (job scheduler and Syslog scanner) to fix your timing issues. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
