Thanks for the help everyone! We are going to go ahead with this on a
limited basis, and will try to see if there is a measurable difference
running our CICS region as a started job versus an initiator-based job.
* Don *

On Wed, Jun 30, 2010 at 9:34 PM, Shmuel Metz (Seymour J.) <
shmuel+ibm-m...@patriot.net <shmuel%2bibm-m...@patriot.net>> wrote:

> In <aanlktimhtsthltssgmm_1jzzknkuhmm2odxy8cw60...@mail.gmail.com>, on
> 06/30/2010
>   at 08:34 AM, Donald Johnson <dej....@gmail.com <http://gmail.com/>>
> said:
>
> >2. We created a user file like any other proclib file to hold the
> >jobs -
> >does it need to be PDSE or is a standard PDS fine?
>
> PDS is fine; I don't know whether PDSE will work.
>
> >3. Can we move existing libraries to IEFJOBS to use this feature?
>
> Bad idea; leave your proca in a proclib and invoke then from IEFJOBS.
>
> >4. Isthere anything from a security or performance standpoint we
> >should consider - any danger in application teams updating the
> >library with CICS region changes, for example?
>
> Like any other data set used by a critical system component, the more
> people who have write access, the more at risk you'll be. From a
> security standpoint it should be as tightly controlled as, e.g.,
> PARMLIB.
>
> --
>     Shmuel (Seymour J.) Metz, SysProg and JOAT
>     ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
> We don't care. We don't have to care, we're Congress.
> (S877: The Shut up and Eat Your spam act of 2003)
>
> ----------------------------------------------------------------------
>  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

Reply via email to