It's on every system that i have now covering many mv's. Not all, but many.
----- Original Message -----
From: "Anthony Youngman" <[EMAIL PROTECTED]>
To: "U2 Users Discussion List" <[EMAIL PROTECTED]>
Sent: Thursday, February 05, 2004 3:06 AM
Subject: RE: Proc or Para


Old history now, but as a Pr1mate (as in used, not worked for), I never
learnt (or even MET!) procs until extremely late in the day. Official
support for procs appeared with INFORMATION 8.1, released probably about
1991 just before they went bust :-(

It just WASN'T THERE on any system I ever worked with ...

Cheers,
Wol

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Mark Johnson
Sent: 05 February 2004 04:41
To: U2 Users Discussion List
Subject: Re: Proc or Para

Here, Here!! I agree with Chuck on the value of procs. Being a 25 year
proctologist myself allows me to support a wide variety of platforms.
Many
of my UD/UV/D3 clients, while having paragraphs and other newer
additions
available, still function with a lot of code that was inherited from
earlier
conversions. Oftentimes management many not be able to justify a
re-write of
code just because the language isn't today's flavor.

Coming from Microdata since the 70's, you only had procs with
procread/procwrite as a way to get fancy with PQ procs. PQN in 1979
offered
more read/write and direct variable features but the other licenses were
developing EXECUTE which, looking back, was the better tact. Still, i
keep
my proc skills sharpened as I still have to support it. Proc does have
some
pretty nifty features for such a simple command set.

Earlier PQ proc didn't have read/write so they developed a sideline
language
called BATCH which did these tasks. BATCH is officially removed from the
direct decendancy of R80/83 as D3 doesn't recognize it and i haven't
seen it
on any U2 systems. RPL, which predates this further never made it past
the
mid 1970's.

Isn't it great to have choices.
my 1 cent.
----- Original Message -----
From: "Results" <[EMAIL PROTECTED]>
To: "U2 Users Discussion List" <[EMAIL PROTECTED]>
Sent: Wednesday, February 04, 2004 1:18 PM
Subject: Re: Proc or Para


> L,
>     Proc predates Pick BASIC as a programming language. The short
answer
> (to my mind) is that Paragraph is an add-on to
> Access/English/AQL/Retrieve, but Proc is really a scripting language.
If
> you need to automate procedures, tie complex programs into a batch, or
> do other heavy lifting, Proc is great. The problem that gets all these
> Proc haters on their soapbox isn't Proc, its when people use Proc for
> the wrong tasks (like Proc menus instead of parametric menus). Proc
> really is incredibily powerful and well worth knowing, but it
shouldn't
> be used for 9-% of the tasks it is normally associated with in the
Pick
> world.
>     Personally, I rtarely use Paragraph because I need to port
software.
>
>     - Charles 'Proc is JCL on Steroids' Barouch
>
>
> --
> u2-users mailing list
> [EMAIL PROTECTED]
> http://www.oliver.com/mailman/listinfo/u2-users

--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users




****************************************************************************
*******

This transmission is intended for the named recipient only. It may contain
private and confidential information. If this has come to you in error you
must not act on anything disclosed in it, nor must you copy it, modify it,
disseminate it in any way, or show it to anyone. Please e-mail the sender to
inform us of the transmission error or telephone ECA International
immediately and delete the e-mail from your information system.

Telephone numbers for ECA International offices are: Sydney +61 (0)2 9911
7799, Hong Kong + 852 2121 2388, London +44 (0)20 7351 5000 and New York +1
212 582 2333.

****************************************************************************
*******

--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users

-- 
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users

Reply via email to