Martin Thanks for your help. Unfortunately this is not the observation I was after.
DYNAMICXCF is a parameter of the IPCONFIG statement in the CS *IP* PROFILE data set. It does *not* appear in major nodes members in the VTAMLST partitioned data set. What you are seeing is the IUTSAMEH TRLE which is defined "under-the- covers" whenever, for whatever reason, CS IP decides it should create an IUTSAMEH internal interface - or - just possibly, the system programmer defines an IUTSAMEH pair of DEVICE and LINK statements in the CS IP PROFILE data set as follows - assuming IPv4: DEVICE IUTSAMEH MPCPTP AUTORESTART LINK linkname MPCPTP IUTSAMEH where linkname is EZASAMEMVS if defined because DYNAMICXCF was specified. Go and have a look in your CS IP PROFILE data set for DYNAMICXCF. Chris Mason On Fri, 20 Feb 2009 11:11:04 -0600, Martin Kline <[email protected]> wrote: >>If there is someone still reading this who has experience with CS IP >> *without* DYNAMICXCF specified who can state whether or not IUTSAMEH >>is defined automatically, I for one would like to hear about it - perhaps >>Stuart himself. > >DYNAMICXCF does not appear anywhere in our VTAMLST, but a display of >ID=IUTSAMEH shows: > >IST075I NAME = IUTSAMEH, TYPE = TRLE >IST486I STATUS= ACTIV, DESIRED STATE= ACTIV >IST087I TYPE = LEASED , CONTROL = MPC , HPDT = YES >IST1954I TRL MAJOR NODE = ISTTRL >IST1715I MPCLEVEL = HPDT MPCUSAGE = SHARE >IST1717I ULPID = TCPIP >IST1500I STATE TRACE = OFF >IST314I END > >This is under z/os 1.9. ---------------------------------------------------------------------- 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
