I'm going to patent the big toe. Everybody who walks must pay me a royality. 
UPTSO is full of fools and failed engineers.

John McKown 

Systems Engineer IV

IT

 

Administrative Services Group

 

HealthMarkets(r)

 

9151 Boulevard 26 * N. Richland Hills * TX 76010

(817) 255-3225 phone * 

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-MAIN@bama.ua.edu] On Behalf Of Jim Thomas
> Sent: Tuesday, July 19, 2011 11:12 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: Making Z/OS easier - Effectively replacing JCL 
> with Unix like commands
> 
> Ummm say doc (switching to Bugs Bunny accent) ... would that be 
> why Microsoft got a patent for PDSs ?? .. a concept that's been
> around even before Microsoft.
> 
> From the 'Summary Of The Invention' for U.S. patent no. 
> 6,594,674, 'System
> and
> method for creating multiple files from a single source 
> file', which was
> issued
> today to Microsoft: 
> 
> Kind Regards
> 
> Jim Thomas
> 617-233-4130             (mobile)
> 636-294-1014                (res)
> j...@thethomasresidence.us (Email)
> 
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List 
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf
> Of John McKown
> Sent: Monday, July 18, 2011 9:10 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: Making Z/OS easier - Effectively replacing JCL 
> with Unix like
> commands
> 
> On Mon, 2011-07-18 at 14:45 -0700, Sam Siegel wrote:
> > On Mon, Jul 18, 2011 at 2:10 PM, Wayne Driscoll <wdri...@us.ibm.com>
> wrote:
> > > In my 20 plus year career I have seen a lot more people 
> with mainframe
> > > backgrounds expressing a willingness to learn and 
> integrate usage of
> > > non-mainframe technology than I have seen people from an 
> "open-systems"
> > > background show a willingness to learn anything about the 
> mainframe.
> > 
> > I completely agree with this statement.  It is typically a 
> requirement
> > of mainframe types to understand open system terminology and then
> > speak of mainframe using open systems language.  sysplex vs. cluster
> > is a typical rough and ready analogy.
> > 
> > I've yet to see an open system person have even a vague 
> understanding
> > of record oriented I/O or PDS processing.
> > 
> > The list goes on and on.
> 
> PDS is a weird beastie. IMO, the closest analogy would be a directory
> with very restricted file names. Record I/O might be possible if they
> use a "looping" language like C or Perl to process each row in an SQL
> result set.
> 
> -- 
> John McKown
> Maranatha! <><
> 
> ----------------------------------------------------------------------
> 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
> 
> 
> 
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 10.0.1390 / Virus Database: 1516/3772 - Release 
> Date: 07/18/11
> 
> ----------------------------------------------------------------------
> 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