See the PROD-DR files on http://zvm.sru.edu/~download
What I do is ask the operator at IPL time whether we are running on
PROD or DR. Depending on the response various service machines choose
the correct PROFILEs/EXECs on VM and also on VSE.
/Fran Hensler at Slippery Rock University of Pennsylvania USA for 46 years
mailto:f...@zvm.sru.edu http://zvm.sru.edu/~fjh +1.724.738.2153
"Yes, Virginia, there is a Slippery Rock"
--------------------------------------------------------------------------
On Thu, 28 Jan 2010 15:59:23 -0800 O'Brien, Dennis L said:
>I'm setting up a DR process for a new system. I need to use a different
>PROFILE TCPIP when the system is up in the DR site. I know that the easy and
>wrong way is to
>update TCPIP's PROFILE EXEC to copy the correct PROFILE TCPIP to the A-disk.
>I'm trying to do it the right way, by using a server exit to pass the name of
>the profile
>to
>the stack. I can't figure out what to pass to get the stack to use a
>different profile. I've tried
>
>Return ':Command.TCPIP DRTEST TCPIP *
>
>and
>
>Return ':Parms.DRTEST TCPIP *
>
>Both yield:
>DTCRUN1011I Running server command: TCPIP
>DTCRUN1011I Parameters in use:
>DTCRUN1011I DRTEST TCPIP *
>
>The problem is that the parameters don't seem to influence which file gets
>used. I don't have "userid" or "node" TCPIP files, so the stack reads PROFILE
>TCPIP. The
>userid and node name don't change during DR, so using those files wouldn't
>help. Is there a way to tell the stack what file to use, or should I just use
>the exit to
>copy
>the correct file to the A-disk as PROFILE TCPIP?
>
> Dennis O'Brien
>
>"See, I'm a man of simple tastes. I like dynamite, and gunpowder... And
>gasoline! Do you know what all of these things have in common? They're cheap!"
> -- Heath Ledger
>as
>The Joker, in The Dark Knight
