|
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
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Mark Murphy/STAR BASE Consulting Inc." <mmurphy@xxxxxxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 05/18/2010 03:44 PM
Subject: OCL Documentation
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Does anyone know of any on-line OCL documentation? I can deduce some of
it, but some things are totally foreign.
For example I have a line that goes like this:
// IF ?4R?/Y IF ?7R?/Y GOTO TMCD
I believe that first ?4R? is retrieving input from the screen, and if it
is a Y then it does the second IF. No prompts or anything, it just waits
for more input from the screen? or uses the previous input? What are the
4 and 7 for? Are these just variable placeholders? ?7? is not set
directly in the procedure, other than the R there. If ?7? is a Y it
should go to the label, but what would cause that? Just user input
without any prompt?
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.