Re: Who the bloody eff still codes CABEQ in this century?!?!?!?

On 20 July 2017 at 00:03, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:

Buck, thanks for spelling out the stages. I do remember when the
"/free plus free H, F, D, and P specs" was being introduced and
discussed on these lists, but where I work, we were so hopelessly
behind at the time that it kind of just whizzed by. Then the **free
thing happened. Also a blur. And as you say, no really good
terminology to differentiate them, so I quickly lost track of the
specifics.

That's the issue: when one is back level, one doesn't really keep
track of the things one can't do :-( Then one reads about it again
and wonders 'Wait; could I have been doing that all along?' Tough to
say sometimes.

And now we're still on 7.1, which feels extremely new to us. We don't
keep up with PTFs, so we don't have anything past the original /free,
as far as I can tell. (And that's why I'm hoping all the latest comes
with 7.3, right out of the box.)

It's baked in to 7.3, but for all those reading; there are two PTFs
that bring this functionality to the system:
One for the RPG compiler
One for the SQL pre-compiler

The PTF for the RPG compiler can be ordered and installed without an
IPL. SNDPTFORD during the day and off you go. Very nice.

The SQL pre-compiler PTF... may need an IPL. Or it may not. Much
depends on the state of your system at the moment you apply the PTF.
The issue isn't the one 'free RPG' PTF; it's the co-reqs and pre-reqs
that (may) come along with it. The good news, such as it is, is that
if the machine will need an IPL, the PTF simply won't apply until the
IPL happens. You won't break anything.

The reason the SQL pre-compiler situation is so different is that the
pre-compiler is maintained by the database group rather than the
compiler group. They have a whole different problem set they face, so
their PTFs tend to be more involved.

--buck