On Tue, 19 Dec 2006 10:17:47 -0600, Mark Zelden <[EMAIL PROTECTED]>
wrote:
<snip>
>But the syntax can get tricky. For example (not including
>SDATA differences):
>
>DUMP COMM=(TCPIP)
>R XX,JOBNAME=(TCPIP1),CONT
>R XX,REMOTE=(SYSLIST=(sysid('TCPIP2')))
>
>See the MVS Commands manual for more details.
>
>If you have a system specific parmlib (which you probably don't have)
>you could just issue RO *ALL,DUMP PARMLIB=xx (the IEADMCxx member would
>be different in each system specific parmlib). If you do this often
>enough it might be worth setting up the different parmlibs.
<snip>
On Tue, 19 Dec 2006 11:42:08 -0500, Robert Wright <[EMAIL PROTECTED]> wrote:
>The option with REMOTE has the advantage that you'll acquire one incident
>ID to tie both of the dumps together. Broadcasting DUMP commands may allow
>you to associate the results via time stamps that are very close to each
>other and the title that you supply, but the system will consider them the
>results of separate incidents.
>
I made this more complicated than it needed to be. There is no
reason you couldn't set up a single IEADMCxx with all the REMOTE
and SDATA options you want and issue the DUMP PARMLIB=xx command
once from a single system. Then you get the one incident ID also.
Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - GITO
mailto:[EMAIL PROTECTED]
z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/
Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
