RE: OCL Documentation

Me too Paul!

Best wishes,

Richard

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: 20 May 2010 14:00
To: 'Midrange Systems Technical Discussion'
Subject: RE: OCL Documentation

And pretty soon, that'll be gone, too. :-))

I'm at the point where I'm thinking about getting out of IT altogether.

Paul Nelson
Office 512-392-2577
Cell 708-670-6978
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Thursday, May 20, 2010 7:44 AM
To: Midrange Systems Technical Discussion
Subject: RE: OCL Documentation

Oh, I still have my debugging templates. About the only thing they're good
for is as a quick reference for the Output edit codes (after 35 years I
still can't recall any from memory except 'J').

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx

Age is a question of mind over matter. If you don't mind, it doesn't
matter. -Satche Paige


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Tuesday, May 18, 2010 4:25 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: OCL Documentation

Heh. I just uncovered a folder containing RPG II debugging templates.

Paul Nelson
Office 512-392-2577
Cell 708-670-6978
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Tuesday, May 18, 2010 3:54 PM
To: Midrange Systems Technical Discussion
Subject: RE: OCL Documentation

Ironic, but I tossed all of my /36 manuals about a month before I applied
for my current job. Ironic because we live in the 36 environment here. The
only thing I still have (must have overlooked it when I was cleaning up) is
the Procedures and Commands summary. I could swear (and often do) that I
had a link to an OCL manual. But the closest I can come right now is a S/32
manual at www.bitsavers.org. It doesn't even cover ?R? (that I could find).
Maybe the /32 didn't have prompting.

The worst case of substitution and parameter passing I ever saw was an IBM
package on the /34. Proc-A might have // INCLUDE PROCB ?1?,?2?,?3? and
Proc-B might then have // INCLUDE PROCC ?2?,?1?,?4R? so that by the time you
got to PROCC what was parameter 2 is parameter 1 to that procedure, etc.
Really ugly and a pain in the arse to debug.

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx

Well, God is getting an earful today. -Jim Murray on the death of Casey
Stengel


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, May 18, 2010 3:01 PM
To: Midrange Systems Technical Discussion
Subject: Re: OCL Documentation

It retrieves it from the screen IF it wasn't passed in. For example, if
your procedure name is DUDE then you could type in
DUDE A,B,D,E
?1? = A, ?2?=B and so on.


Rob Berendt