The place I last worked at we kept several INITs as JES managed. We did convert the main job classes over to WLM INITs. First as was stated we did have one class as JES managed for emergency situations. Second, we used a few to single thread some jobs. I would guess the second point could have been done with WLM INITs but old dogs new tricks. Third was high priority very short running jobs that just had to get run no matter how busy the system was used JES managed INITs. These jobs used very little CPU and ran for a very short time.
The other thing was getting the programmers and end users use to the idea that even though it looked like there was available INITs that WLM was not going to let jobs start if it determined the system couldn't handle any more work. Paul -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Allan Staller Sent: Wednesday, April 16, 2025 8:01 AM To: [email protected] Subject: Re: WLM Managed Batch Initiators & JES Commands? Classification: Confidential 1) Assign a different WLM service class to WLM managed job classes than JES Managed classes. The WLM managed classes include queue delay when determining whether to start or stop initiators and velocity calculations. WLM job queueing is FIFO. JES queueing is priority within job lass (pending initiator availability). 2) Until you get to a "happy place" with WLM managed inits, keep a couple of JES managed classes around for "emergency" use. There is alspo a specific operator JES command to "start this job new" that can also be used. 3) Your existing JES managed icommands will most likely be honored. There are logical equivalents for WLM managed commands. GIYF. There should be a bunch of stuff at SHARE.ORG, and other related places around the timeframe of z/OS 1.4 about all of the (then) new stuff. I think I hit the high points above. HTH, -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Steve Estle Sent: Wednesday, April 16, 2025 7:44 AM To: [email protected] Subject: WLM Managed Batch Initiators & JES Commands? [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] Hello All, We are embarking on an effort where we will be implementing WLM managed batch Initiators across multiple ZOS 2.5 LPAR's. The implementation seems relatively straight forward with JES Init parm updates to activate fully. My basic question is what happens from an automation perspective to the various automation scripts / JES commands that are embedded in the system that are trying to manipulate the batch initiator configuration dynamically (start inits, stop inits, reassign classes, etc.). Does JES just ignore / reject all those commands or ??? Any lessons learned from implementing anyone would like to share - gotchas, etc? Thanks, Steve Estle CDW ZSeries Services ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ::DISCLAIMER:: ________________________________ The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
