-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mark H. Young Sent: Wednesday, August 29, 2007 7:35 AM To: [email protected] Subject: Re: JES2 converter via /*JOBPARM SYSAFF=xxxx
<SNIP> But the suggestion to use /*XMIT would work, so that JES2 converts the JCL on the EXECUTION system, right? Just as SYSAFF=xxxx would, right?! <SNIP> Mark: JCL REF at 1.7 says: Note: Use the SYSAFF parameter to ensure the conversion and execution of the job will be done on a specific system. If you code SYSAFF, both processes are done on the specified system. For TSO-submitted jobs that specify NOTIFY in the JOB statement: after a job has completed execution, JES2 may change the SYSAFF specification for the job if the job executed on a processor other than the processor that the user is logged on. This is done by JES2 during output processing to allow NOTIFY processing to take place on the user's processor. [Chapter 27. JES2 Control Statements 27-7] If this is insufficient, then perhaps a small experiment using both methods is in order to determine which gives you the best results? I have used both methods, because I needed to verify when C/I took place for a certain problem I was trouble-shooting some years ago (back when z/OS 1.1 was in use, and before 1.2 was GA). I have also used TSO XMIT to send a JOB where I needed/wanted it to be processed -- believe it or not, I sent the JOB to VSE! Regards, Steve Thompson -- ---------------------------------------------------------------------- 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
