In a message dated 3/13/2007 9:28:24 A.M. Central Daylight Time, [EMAIL PROTECTED] writes: >I would like to understand where the NED is set that the SCP reads. Is it something with the IOCDS? If so, where in the HCD can I look. Or is it strictly a device supplied number? >Would a vary offline,force,uncond type function clear out the NED and force a new one in? Or is this a new IOCDS and activate? Or is this an IPL type issue? The NED (Node Element Descriptor) is set by the manufacturer who built the control unit involved, and will not change unless a microcode PTF is installed or the control unit is replaced. Software can read the NED info by doing a Read Configuration Data CCW (X'FA' command code) described in the various DASD control unit reference books. If the data appears hosed when you do any display command or because of how MVS is behaving, then more than likely a software bug has overlaid the NED data. When a DASD device is varied online, the vary online command processor reads all the configuration data (inter alia) from the control unit and populates certain system control blocks with those data elements. Some data is stored in the Device Class Extension (DCE) which can be displayed by an operator command. But the configuration data (NED et al.) is stored in a control block that has not been publicly documented. I believe that it, too, can be displayed by an operator command. If an in-storage NED is hosed, a vary online or reIPL may be necessary. Also a PTF may need to be applied. Bill Fairchild
<BR><BR><BR>**************************************<BR> AOL now offers free email to everyone. Find out more about what's free from AOL at http://www.aol.com. ---------------------------------------------------------------------- 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
