I understand.
But, that's why there are standards.
You backed down when you shouldn't have.

My complaint is the dictatorial SYSPROG.
-
Ted MacNEIL
eamacn...@yahoo.ca
Twitter: @TedMacNEIL

-----Original Message-----
From:         Paul Gilmartin <paulgboul...@aim.com>
Sender:       IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
Date:         Thu, 15 Aug 2013 00:16:14 
To: <IBM-MAIN@LISTSERV.UA.EDU>
Reply-To:     IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
Subject: Re: C issue - 'struct stat'

On Thu, 15 Aug 2013 03:04:35 +0000, Ted MacNEIL wrote:

>>are limited by their sysprogs in whatever they can or cannot do (up to the 
>>point of not having any say in what compiler option they could or could not 
>>use in their COBOL applications.)
>
>Their SYSPROGs have too much power!
>Applications Programmers are there to facilitate the business.
>So are SYSPROGs!
>Which means they facilitate apps.
>NOT set arbitrary rules!
>  
I've been on the other side of that one, doing development tools
support.  For our project, we agreed that our code should be
reusable, reentrant, refreshable, running in its own address
space, loaded from an authorized library into a nonmodifiable
subpool.  Each developer could do his own coding and unit
testing, but I was charged with the tools for integration.  So
I made RENT the uniform PARM for assembler, and
REUS/RENT/REFR for link editing.

Then _one_ developer writing a stand-alone utility chose to make
it non-renterable.  Not for any functional reason, but only because
he chose not to obtain RSA and working storage because "It wasn't
necessary."  I seethed and added the flexibility to our development
tools to support one developer's one load module.  He cost me more
in the support effort than he saved by not coding a GETMAIN.

-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to