We allow test jobs to READ some production (non HIPAA) data. And it is known 
that they will be CANCELed if they need to be or get in production's way. If a 
test job causes a production job to go down, it is written up and the 
programmer gets a talking to.

--
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * (817)-961-6183 cell
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

 

> -----Original Message-----
> From: IBM Mainframe Discussion List 
> [mailto:ibm-m...@bama.ua.edu] On Behalf Of John Hooper
> Sent: Tuesday, July 06, 2010 8:55 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: ENQ trap for dynamic allocation
> 
> This thread has had some interesting comments.  I agree that 
> in todays world 
> it is a terrible idea to develop your own screening or 
> front-end code to provide 
> functionality.  The ENQ front-end was done 15 years ago and 
> has served us 
> well.  It has allowed us to sort-of "have our cake and eat it 
> too".  Our 
> requirement was to prevent "test" jobs from adversely 
> affecting "production" 
> jobs.  This was in the days of a single LPAR and using the 
> security system to 
> prevent all access was not deemed to be a good idea.  I 
> accept the fact that 
> this facility will be retired.  I do have a question.  What 
> do most shops do to 
> prevent this condition?  I see three options.  I hope there 
> are more.  One - I 
> think CA-MIM can address this problem.  Is that true?  Two - Totally 
> physically isolate development from production and do not 
> allow them to even 
> see production files.  Three - Use the security system to not 
> even allow READ 
> access.  Again - how do you address this issue?
> 
> ----------------------------------------------------------------------
> 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