Consider using a"PIPES" like concept to multi thread, i.e., if J1 creates a dataset read by J2, send the data to a pipe so that J2 can run concurrently.
Or if these are DB updates, split the inut into multiples jobs and run concurrently. It depends on you work flow. n Fri, 9 Nov 2018 10:09:40 +0100 Kevin Neuhaus/KBS <[email protected]> wrote: :>Hello everyone, :> :>we have a LPAR with 2-3 CPs and currently 330 MSU. :>Unfortunately large portions of a migration batch are single-threaded and :>therefore only run with ~178 MSU on CP. :> :>Is there a way to combine >2 CP's to make them work together on a :>single-threaded task? :> :>Best regards :>Kevin Neuhaus -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
