IKJEFF10 runs in the TSO user address space, under the TCB of the submit command. This means that it can display a message to the user terminal. In addition it has access to TSO/E control blocks that exist in the submittor address space. IEFUJV runs in the Converter or Interpreter, not in the submitting address space. It has more limited means of communicating to the submittor.
=============================================== Wayne Driscoll OMEGAMON DB2 L3 Support/Development wdrisco(AT)us.ibm.com =============================================== From: Paul Gilmartin <paulgboul...@aim.com> To: IBM-MAIN@bama.ua.edu Date: 08/10/2011 10:46 AM Subject: Re: Enforcing job name conventions - which exit? Sent by: IBM Mainframe Discussion List <IBM-MAIN@bama.ua.edu> On Wed, 10 Aug 2011 10:25:37 -0400, Scott Rowe wrote: >Two what? > >There is one TSO submit exit (IKJEFF10), and one job verification exit >(IEFUJV). These two exit points were created for different purposes and >functions. > What can be done in IKJEFF10 that couldn't equally well be done in IEFUJV? Can IEFUJV detect that the job is being submitted from a TSO session (whether by SUBMIT or writing directly to INTRDR) and take any special action needed for TSO? Does IEFUJV get control too late to perform actions required for TSO? Or does IEFUJV get control too early, before some control blocks required for TSO operations are set up? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
