Hi, Is this still the current approach for testing LE maintenance? I am applying UM31620 to MODULEs CEEBINIT, CEEBOICI, & CEEPIPI. Or is there a better way?
BTW, the VMSES/E service guide seems to stay far, far away from hints/tips on how to test various components other than CMS (Appendix D). Seems sort of strange. Thanks -- Craig Dudley Manager, Mainframe Technical Support Group Office of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-1506 Fax 603-271-1516 >Mats, > >The simplest method of testing the LE code on the 49E disk is not the most >elegant. First, ACCESS 49E earlier than the 19E Y-disk (I usually use >filemode T). After the ACCESS, NUCXLOAD the CEExxxxx MODULEs on the 49E >disk. If you are trying to test just serviced parts on the 49E disk, you >only need to NUCXLOAD the newly built MODULEs, as the rest of the parts >will be unchanged. >When LE decides it needs to load a new routine, it first checks the NUCEXT >chain to see if the code is already loaded. If it is loaded, that code is >used. If it is not loaded, then LE tries a SEGMENT LOAD, followed by a >LOADMOD of the part, followed by a LOAD from the GLOBAL LOADLIB list. > >Thanks! > Mike > > > > > "Westlund, Mats" > <[EMAIL PROTECTED] > .COM> To > Sent by: VM/ESA [email protected] > and z/VM cc > Discussions > <[EMAIL PROTECTED] Subject > .UARK.EDU> LE Testing > > > 03/29/2004 03:09 > AM > > > Please respond to > VM/ESA and z/VM > Discussions > > > > > > >How can I test Language Environment fixes from the 49E disk to see if they >work before saving new segments. >I only want to use the files on the 49E disk and not pick up things from >the "old" segments. > > >Regards Mats Westlund
