Re: Best way to force jobs to a specific LPAR

2008-11-03 Thread Bond, Richard
This is not a political forum. Keep your opinions to yourself. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Anton Britz Sent: Friday, October 31, 2008 6:37 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Best way to force jobs to a specific

Re: Best way to force jobs to a specific LPAR

2008-11-01 Thread Stephen McColley
@BAMA.UA.EDU Subject: Best way to force jobs to a specific LPAR I am looking for a good (and easy) way of ensuring that certain programs only run on a specific LPAR. We are very vanilla z/OS V1.9. I was thinking of either creating a stub module that is the name of the program and then testing

Best way to force jobs to a specific LPAR

2008-10-31 Thread Lizette Koehler
I am looking for a good (and easy) way of ensuring that certain programs only run on a specific LPAR. We are very vanilla z/OS V1.9. I was thinking of either creating a stub module that is the name of the program and then testing to see if it is submitted with /*JOBPARM or creating a TSO

Re: Best way to force jobs to a specific LPAR

2008-10-31 Thread Ted MacNEIL
Try looking at WLM scheduling environments. --Original Message-- From: Lizette Koehler Sender: IBM Mainframe Discussion List To: IBM Mainframe Discussion List ReplyTo: IBM Mainframe Discussion List Sent: Oct 31, 2008 13:56 Subject: Best way to force jobs to a specific LPAR I am looking

Re: Best way to force jobs to a specific LPAR

2008-10-31 Thread Richards, Robert B.
: Best way to force jobs to a specific LPAR I am looking for a good (and easy) way of ensuring that certain programs only run on a specific LPAR. We are very vanilla z/OS V1.9. I was thinking of either creating a stub module that is the name of the program and then testing to see

Re: Best way to force jobs to a specific LPAR

2008-10-31 Thread Brian France
IF your LPARS are in the same Jes plex, ( we are a basic sysplex ), we use the sysaff ( system affinity) under the /*jobparm statement. We don't check for programs, rather we just run the entire job, how ever many steps it has to execute on that system. When we run outside of a plex, say our

Re: Best way to force jobs to a specific LPAR

2008-10-31 Thread Bob Shannon
Use Scheduling Environments. They are easy to set up and work great for this purpose. It also allows you to move the product (program) to a different system. It does require users to change their JCL. Bob Shannon Rocket Software

Re: Best way to force jobs to a specific LPAR

2008-10-31 Thread Walt Farrell
On Fri, 31 Oct 2008 13:56:52 -0400, Lizette Koehler [EMAIL PROTECTED] wrote: I am looking for a good (and easy) way of ensuring that certain programs only run on a specific LPAR. We are very vanilla z/OS V1.9. I was thinking of either creating a stub module that is the name of the program and

Re: Best way to force jobs to a specific LPAR

2008-10-31 Thread Anton Britz
What about VANILLA /*XEQ Purpose : Use the /*XEQ statement to identify the network node where the job is to execute. It performs the same function as the /*ROUTE XEQ statement. Anton On Fri, 31 Oct 2008 13:56:52 -0400, Lizette Koehler [EMAIL PROTECTED] wrote: I am looking for a good (and

Re: Best way to force jobs to a specific LPAR

2008-10-31 Thread Bob Shannon
What about VANILLA /*XEQ I believe that will only direct you to a specific node. If each system is a unique node, XEQ will work. I assumed, erroneously, that the systems were in the same Sysplex. Bob Shannon Rocket Software

Re: Best way to force jobs to a specific LPAR

2008-10-31 Thread Lizette Koehler
The intent was to do it for the users, rather than have them change their JCL. As you know, it is not always guarantee that the user will do what is needed. Lizette I am looking for a good (and easy) way of ensuring that certain programs only run on a specific LPAR. We are very vanilla

Re: Best way to force jobs to a specific LPAR

2008-10-31 Thread Shane
On Fri, 2008-10-31 at 17:23 -0400, Lizette Koehler wrote: The intent was to do it for the users, rather than have them change their JCL. As you know, it is not always guarantee that the user will do what is needed. In which case look at Walts suggestion - works a treat. ISVs will be more

Re: Best way to force jobs to a specific LPAR

2008-10-31 Thread Anton Britz
Final responds .. before we hit the weekend : a) Have you got any User exits in your shop b) have you got any Dataset naming conventions Then : a) Drop the ALIAS on the LPAR for those users that are not suppose to be on that LPAR b) User your IEFUJV to validate the users JCL c) or Jesexit6 to

Re: Best way to force jobs to a specific LPAR

2008-10-31 Thread Lizette Koehler
I would love to use this approach but we are a Top Secret Shop and not RACF. I will see if our security admins can change this to a TSS function. And yes, both processes are really required. Fail it on systems where it is not suppose to run, and make it only run on the LPAR of My choice.

Re: Best way to force jobs to a specific LPAR

2008-10-31 Thread Anton Britz
Lizette, Have to read any comparison between RACF and TSS ? TSS can do the same with half the quantity of rescources supporting it.. If you need any TSS manuals, I would send you some.. ( It actually easier to read than the IBM manuals ) Never mind... if Palin can say, what she is saying...