Yes. However, we use a /*JOBPARM S=xxx instead. I think that construct was easier to implement under our job scheduler.
One task for the scheduler is to 'wind down' for an IPL. That is, to insure long running jobs that will not complete are not submitted until after the IPL. Interestingly, the job scheduler still runs on z/os. One reason is that the primary user interface is TSO. We don't have much incentive to move it because it uses very few MSUs. There is an agent that runs on z/os.e that tracks job execution. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Walter Marguccio Sent: Monday, January 16, 2006 7:38 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: limited Numbers of TSO users on z/OS.e Hal, does a basic sysplex (which is the minimum requirement for a MAS) allow you to run a job on a specific LPAR depending on the jobclass ? Walter Marguccio ---------------------------------------------------------------------- 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
