In a memorable scene from Lethal Weapon 3, Mel Gibson and Rene Russo compare battle scars. Many of us could easily step into that scene and compete. RSU* might represent some of our scars. OTOH RSU* might have prevented some of those scars. Maintenance is an art, not a science. There's no magic algorithm. But you still need to know exactly how the SOURCEID syntax works.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John Eells Sent: Monday, November 16, 2015 6:31 AM To: [email protected] Subject: (External):Re: RSU APPLY It depends on your objective. If the objective is to "bring the system 'up to RSU1509,'" then: SELECT(RSU*) with EXSRCID(all available RSUs later than RSU1509) ...is what you want. And, I'd hope that is the objective, rather than the alternative of installing "only what's in RSU1509 that is eligible for selection." As Kurt points out, RSU* is a better objective from our point of view. Mainframe Mainframe wrote: > Hi, > While apply RSU into SMPE, do we need to specify only that > particular RSU number in SOURCEID parm or we can use RSU* . For > example > > > Currently in our z/OS system we RSU1403 and now we planning to apply > RSU1509 then in this case, in SOURCEID parameter what we should be > specifying > > SOURCEID(RSU1509) or SOURCEID(RSU*) . -- John Eells IBM Poughkeepsie [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
