From: SeaSideSam on
Ref: http://primacomputing.co.nz/cobdata

sss here. i've been going thru the change and am making changes on an
hourly basis: replacing opera with chrome and grabit with thunderbird.
i have been informed that both steps were necessary. i am not convinced.

in "robert's original code" some pic clauses have periods following and
others don't. the compiler must handle this okay.
-snip-
. 10 layout-type pic x(01)
. 88 type-binary value 'b'
. 88 type-packed value 'p'
. 10 layout-redefines-name pic x(31).
. 10 layout-redefines-stack.
. 15 layout-redefines-depth binary pic s9(02).
. 15 layout-redefines-entry occurs 10 binary pic s9(04).

. procedure division.
-end snip-

"view license"... you guessed it; chrome displays a blue box.

"Process diagram"...

when you complete this process how much 'cobol' remains? i'm trying to
visualize the most complex program i've worked with (payroll; exempt,
nonexempt, 5 unions, nonunion) after completing steps 1 and 3. my
oldtymers keeps interfering. we had relocatables back in the day, and
made use of them; so step 3 would not gain much. i never had the guts
or the time to implement step 1.

you two seemed to get this done in a very short time. would this be
typical?

not to nitpick; but... ever since i've had a tp monitor on my desk (at
work or at home) with the capability of running a compile and having the
listing available at my desk within moments i have had a dummy program
available where i 'copy' the data structure i'm working with, compile,
and get offset and displacement info directly from the compiler listing.
worked for me.

happy spring time.

sss


---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 080926-0, 09/26/2008
Tested on: 9/27/2008 2:28:56 AM
avast! - copyright (c) 1988-2008 ALWIL Software.
http://www.avast.com



From: Robert on
On Sat, 27 Sep 2008 02:28:53 -0500, SeaSideSam <Sam(a)Sea.Side> wrote:

>Ref: http://primacomputing.co.nz/cobdata
>
>in "robert's original code" some pic clauses have periods following and
>others don't. the compiler must handle this okay.
>-snip-
> . 10 layout-type pic x(01)
> . 88 type-binary value 'b'
> . 88 type-packed value 'p'
> . 10 layout-redefines-name pic x(31).
> . 10 layout-redefines-stack.
> . 15 layout-redefines-depth binary pic s9(02).
> . 15 layout-redefines-entry occurs 10 binary pic s9(04).
>
> . procedure division.

I'm embarrassed. It's fixed now.

>you two seemed to get this done in a very short time. would this be
>typical?

It would have been faster if our longitudes/time zones were closer. Also, if we had used
collabortion tools better than email.

>not to nitpick; but... ever since i've had a tp monitor on my desk (at
>work or at home) with the capability of running a compile and having the
>listing available at my desk within moments i have had a dummy program
>available where i 'copy' the data structure i'm working with, compile,
>and get offset and displacement info directly from the compiler listing.
> worked for me.

Why do you need offsets? I've needed them only once, when creating a record description
for ODBC access to flat files.
 | 
Pages: 1
Prev: Microsoft Outlook Web Access
Next: Pete Dashwood