I need to tell a customer how to map, assuming this is even possible, a
global section into which I write data for them. They only do COBOL. :(
Is this possibe? How does one reference the data once mapped in the
expanded region? I've tried to make heads or tails of COBOL but I get
totally lost in the PICs.

If only somebody would do what Jim Duff did for calling system services
with C but using COBOL. So very few examples exist.

— VAXman (still on the outside trying to look into VMS x86)

On Thursday, September 7, 2023 at 10:36:35 AM UTC-4, Brian Schenkenberger wrote:
> I need to tell a customer how to map, assuming this is even possible, a
> global section into which I write data for them. They only do COBOL. :(
> Is this possibe? How does one reference the data once mapped in the
> expanded region? I've tried to make heads or tails of COBOL but I get
> totally lost in the PICs.
>
> If only somebody would do what Jim Duff did for calling system services
> with C but using COBOL. So very few examples exist.
>
> — VAXman (still on the outside trying to look into VMS x86)
There was a programming VMS using Cobol class many years ago that had examples of these routines and how to use them. I should have a hardcopy around. Check the net for PDFs, they may exist.

Dan

On 2023-09-07 14:36:31 +0000, Brian Schenkenberger said:

> I need to tell a customer how to map, assuming this is even possible, a
> global section into which I write data for them. They only do COBOL. :(
> Is this possibe? How does one reference the data once mapped in the
> expanded region? I've tried to make heads or tails of COBOL but I get
> totally lost in the PICs.
>
> If only somebody would do what Jim Duff did for calling system services
> with C but using COBOL. So very few examples exist.
>
> — VAXman (still on the outside trying to look into VMS x86)

OK. I've gotten this far but now I have no idea how to access the data
in the mapped region.

IDENTIFICATION DIVISION.
PROGRAM-ID. SYSMGBLS.
ENVIRONMENT DIVISION.
DATA DIVISION.
WORKING-STORAGE SECTION.

*** EXTERNAL VALUE from SEC.MAR ($SECDEF GLOBAL)
*** $ MACRO SEC.MAR
*** $ LINK SYSMGBLSC,SEC

01 SEC$M_EXPREG PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_EXPREG.
01 SEC$M_PERM PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_PERM.
01 SEC$M_SYSGBL PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_SYSGBL.

01 FLAGS PIC S9(09) COMP VALUE IS 0.

01 RETSTS PIC S9(09) COMP VALUE IS 0.
01 GBLSECNAM PIC X(21) VALUE IS "A-GLOBAL-SECTION-NAME".

01 INADR.
02 ADDRESS-1 PIC S9(09) COMP VALUE IS 512.
02 ADDRESS-2 PIC S9(09) COMP VALUE IS 512.

01 RETADR.
02 ADDRESS-1 PIC S9(09) COMP VALUE IS 0.
02 ADDRESS-2 PIC S9(09) COMP VALUE IS 0.

PROCEDURE DIVISION.
0-BEGIN.

ADD SEC$M_EXPREG TO FLAGS.
ADD SEC$M_PERM TO FLAGS.
ADD SEC$M_SYSGBL TO FLAGS.

CALL "SYS$MGBLSC" USING BY REFERENCE INADR,
BY REFERENCE RETADR,
OMITTED,
BY VALUE FLAGS,
BY DESCRIPTOR GBLSECNAM,
OMITTED,
OMITTED
GIVING RETSTS.

IF RETSTS IS FAILURE CALL "LIB$SIGNAL" USING BY VALUE RETSTS.

IF RETSTS IS SUCCESS DISPLAY "GLOBAL SECTION MAPPED".

*** NOW WHAT???

0-END.
STOP RUN.

On 9/7/2023 1:44 PM, Brian Schenkenberger wrote:
> On 2023-09-07 14:36:31 +0000, Brian Schenkenberger said:
>> I need to tell a customer how to map, assuming this is even possible,
>> a global section into which I write data for them. They only do COBOL.
>> :( Is this possibe? How does one reference the data once mapped in the
>> expanded region? I've tried to make heads or tails of COBOL but I get
>> totally lost in the PICs.
>>
>> If only somebody would do what Jim Duff did for calling system
>> services with C but using COBOL. So very few examples exist.
>
> OK.  I've gotten this far but now I have no idea how to access the data
> in the mapped region.
>
> IDENTIFICATION DIVISION.
> PROGRAM-ID. SYSMGBLS.
> ENVIRONMENT DIVISION.
> DATA DIVISION.
> WORKING-STORAGE SECTION.
>
> ***  EXTERNAL VALUE from SEC.MAR ($SECDEF GLOBAL)
> ***  $ MACRO SEC.MAR
> ***  $ LINK SYSMGBLSC,SEC
>
> 01 SEC$M_EXPREG    PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_EXPREG.
> 01 SEC$M_PERM    PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_PERM.
> 01 SEC$M_SYSGBL    PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_SYSGBL.
>
> 01 FLAGS  PIC S9(09) COMP VALUE IS 0.
>
> 01 RETSTS PIC S9(09) COMP VALUE IS 0.
> 01 GBLSECNAM PIC X(21) VALUE IS "A-GLOBAL-SECTION-NAME".
>
> 01 INADR.
>  02 ADDRESS-1 PIC S9(09) COMP VALUE IS 512.
>  02 ADDRESS-2 PIC S9(09) COMP VALUE IS 512.
>
> 01 RETADR.
>  02 ADDRESS-1 PIC S9(09) COMP VALUE IS 0.
>  02 ADDRESS-2 PIC S9(09) COMP VALUE IS 0.
>
> PROCEDURE DIVISION.
> 0-BEGIN.
>
>    ADD SEC$M_EXPREG TO FLAGS.
>    ADD SEC$M_PERM TO FLAGS.
>    ADD SEC$M_SYSGBL TO FLAGS.
>
>    CALL "SYS$MGBLSC"    USING    BY REFERENCE INADR,
>                 BY REFERENCE RETADR,
>                 OMITTED,
>                 BY VALUE FLAGS,
>                 BY DESCRIPTOR GBLSECNAM,
>                 OMITTED,
>                 OMITTED
>             GIVING    RETSTS.
>
>    IF RETSTS IS FAILURE CALL "LIB$SIGNAL" USING BY VALUE RETSTS.
>
>    IF RETSTS IS SUCCESS DISPLAY "GLOBAL SECTION MAPPED".
>
> *** NOW WHAT???
>
> 0-END.
>    STOP RUN.

I think you will need a hack.

:-)

For inspiration:

$ type main.cob
IDENTIFICATION DIVISION.
PROGRAM-ID. SYSMGBLS.
ENVIRONMENT DIVISION.
DATA DIVISION.
WORKING-STORAGE SECTION.

*** EXTERNAL VALUE from SEC.MAR ($SECDEF GLOBAL)
*** $ MACRO SEC.MAR
*** $ LINK SYSMGBLSC,SEC

01 SEC$M_EXPREG PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_EXPREG.
01 SEC$M_PERM PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_PERM.
01 SEC$M_SYSGBL PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_SYSGBL.

01 FLAGS PIC S9(09) COMP VALUE IS 0.

01 RETSTS PIC S9(09) COMP VALUE IS 0.
01 GBLSECNAM PIC X(21) VALUE IS "A-GLOBAL-SECTION-NAME".

01 INADR.
02 IN-ADDRESS-1 PIC S9(09) COMP VALUE IS 512.
02 IN-ADDRESS-2 PIC S9(09) COMP VALUE IS 512.

01 RETADR.
02 RET-ADDRESS-1 PIC S9(09) COMP VALUE IS 0.
02 RET-ADDRESS-2 PIC S9(09) COMP VALUE IS 0.

01 DATA-LEN PIC S9(09) COMP VALUE IS 81920.

PROCEDURE DIVISION.
0-BEGIN.

ADD SEC$M_EXPREG TO FLAGS.

CALL "SYS$MGBLSC" USING BY REFERENCE INADR,
BY REFERENCE RETADR,
OMITTED,
BY VALUE FLAGS,
BY DESCRIPTOR GBLSECNAM,
OMITTED,
OMITTED
GIVING RETSTS.

IF RETSTS IS FAILURE CALL "LIB$SIGNAL" USING BY VALUE RETSTS.

IF RETSTS IS SUCCESS DISPLAY "GLOBAL SECTION MAPPED".

CALL "BRIAN" USING BY REFERENCE DATA-LEN, BY VALUE RET-ADDRESS-1.

0-END.
STOP RUN.
$ type brian.cob
IDENTIFICATION DIVISION.
PROGRAM-ID.BRIAN.
* DATA DIVISION.
WORKING-STORAGE SECTION.
01 NBYT2 PIC S9(9) DISPLAY.
01 CVAL PIC S9(9) DISPLAY.
LINKAGE SECTION.
01 NBYT PIC 9(9) COMP.
01 BLOB.
03 BYT PIC X OCCURS 1000000 TIMES.
* PROCEDURE DIVISION USING NBYT BLOB.
ACK-PARAGRAPH.
MOVE NBYT TO NBYT2
DISPLAY NBYT2
MOVE FUNCTION ORD(BYT(1)) TO CVAL
DISPLAY CVAL.
END PROGRAM BRIAN.
$ @cob
$ cob main
$ cob brian
$ link main + brian
$ run main
GLOBAL SECTION MAPPED
00008192{
00000017H

And yes - the first byte of that global section I setup for the test
has value of 177.

Arne

On 2023-09-07 20:51:20 +0000, Arne Vajhj said:

On 2023-09-07 20:51:20 +0000, Arne Vajhj said:

> On 9/7/2023 1:44 PM, Brian Schenkenberger wrote:
>> On 2023-09-07 14:36:31 +0000, Brian Schenkenberger said:
>>> I need to tell a customer how to map, assuming this is even possible, a
>>> global section into which I write data for them. They only do COBOL. :(
>>> Is this possibe? How does one reference the data once mapped in the
>>> expanded region? I've tried to make heads or tails of COBOL but I get
>>> totally lost in the PICs.
>>>
>>> If only somebody would do what Jim Duff did for calling system services
>>> with C but using COBOL. So very few examples exist.
>>
>> OK.  I've gotten this far but now I have no idea how to access the data
>> in the mapped region.
>>
>> IDENTIFICATION DIVISION.
>> PROGRAM-ID. SYSMGBLS.
>> ENVIRONMENT DIVISION.
>> DATA DIVISION.
>> WORKING-STORAGE SECTION.
>>
>> ***  EXTERNAL VALUE from SEC.MAR ($SECDEF GLOBAL)
>> ***  $ MACRO SEC.MAR
>> ***  $ LINK SYSMGBLSC,SEC
>>
>> 01 SEC$M_EXPREG    PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_EXPREG.
>> 01 SEC$M_PERM    PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_PERM.
>> 01 SEC$M_SYSGBL    PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_SYSGBL.
>>
>> 01 FLAGS  PIC S9(09) COMP VALUE IS 0.
>>
>> 01 RETSTS PIC S9(09) COMP VALUE IS 0.
>> 01 GBLSECNAM PIC X(21) VALUE IS "A-GLOBAL-SECTION-NAME".
>>
>> 01 INADR.
>>  02 ADDRESS-1 PIC S9(09) COMP VALUE IS 512.
>>  02 ADDRESS-2 PIC S9(09) COMP VALUE IS 512.
>>
>> 01 RETADR.
>>  02 ADDRESS-1 PIC S9(09) COMP VALUE IS 0.
>>  02 ADDRESS-2 PIC S9(09) COMP VALUE IS 0.
>>
>> PROCEDURE DIVISION.
>> 0-BEGIN.
>>
>>    ADD SEC$M_EXPREG TO FLAGS.
>>    ADD SEC$M_PERM TO FLAGS.
>>    ADD SEC$M_SYSGBL TO FLAGS.
>>
>>    CALL "SYS$MGBLSC"    USING    BY REFERENCE INADR,
>>                 BY REFERENCE RETADR,
>>                 OMITTED,
>>                 BY VALUE FLAGS,
>>                 BY DESCRIPTOR GBLSECNAM,
>>                 OMITTED,
>>                 OMITTED
>>             GIVING    RETSTS.
>>
>>    IF RETSTS IS FAILURE CALL "LIB$SIGNAL" USING BY VALUE RETSTS.
>>
>>    IF RETSTS IS SUCCESS DISPLAY "GLOBAL SECTION MAPPED".
>>
>> *** NOW WHAT???
>>
>> 0-END.
>>    STOP RUN.
>
> I think you will need a hack.
>
> :-)
>
> For inspiration:
>
> $ type main.cob
> IDENTIFICATION DIVISION.
> PROGRAM-ID. SYSMGBLS.
> ENVIRONMENT DIVISION.
> DATA DIVISION.
> WORKING-STORAGE SECTION.
>
> *** EXTERNAL VALUE from SEC.MAR ($SECDEF GLOBAL)
> *** $ MACRO SEC.MAR
> *** $ LINK SYSMGBLSC,SEC
>
> 01 SEC$M_EXPREG PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_EXPREG.
> 01 SEC$M_PERM PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_PERM.
> 01 SEC$M_SYSGBL PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_SYSGBL.
>
> 01 FLAGS PIC S9(09) COMP VALUE IS 0.
>
> 01 RETSTS PIC S9(09) COMP VALUE IS 0.
> 01 GBLSECNAM PIC X(21) VALUE IS "A-GLOBAL-SECTION-NAME".
>
> 01 INADR.
> 02 IN-ADDRESS-1 PIC S9(09) COMP VALUE IS 512.
> 02 IN-ADDRESS-2 PIC S9(09) COMP VALUE IS 512.
>
> 01 RETADR.
> 02 RET-ADDRESS-1 PIC S9(09) COMP VALUE IS 0.
> 02 RET-ADDRESS-2 PIC S9(09) COMP VALUE IS 0.
>
> 01 DATA-LEN PIC S9(09) COMP VALUE IS 81920.
>
> PROCEDURE DIVISION.
> 0-BEGIN.
>
> ADD SEC$M_EXPREG TO FLAGS.
>
> CALL "SYS$MGBLSC" USING BY REFERENCE INADR,
> BY REFERENCE RETADR,
> OMITTED,
> BY VALUE FLAGS,
> BY DESCRIPTOR GBLSECNAM,
> OMITTED,
> OMITTED
> GIVING RETSTS.
>
> IF RETSTS IS FAILURE CALL "LIB$SIGNAL" USING BY VALUE RETSTS.
>
> IF RETSTS IS SUCCESS DISPLAY "GLOBAL SECTION MAPPED".
>
> CALL "BRIAN" USING BY REFERENCE DATA-LEN, BY VALUE RET-ADDRESS-1.
>
> 0-END.
> STOP RUN.
> $ type brian.cob
> IDENTIFICATION DIVISION.
> PROGRAM-ID.BRIAN.
> *
> DATA DIVISION.
> WORKING-STORAGE SECTION.
> 01 NBYT2 PIC S9(9) DISPLAY.
> 01 CVAL PIC S9(9) DISPLAY.
> LINKAGE SECTION.
> 01 NBYT PIC 9(9) COMP.
> 01 BLOB.
> 03 BYT PIC X OCCURS 1000000 TIMES.
> *
> PROCEDURE DIVISION USING NBYT BLOB.
> ACK-PARAGRAPH.
> MOVE NBYT TO NBYT2
> DISPLAY NBYT2
> MOVE FUNCTION ORD(BYT(1)) TO CVAL
> DISPLAY CVAL.
> END PROGRAM BRIAN.
> $ @cob
> $ cob main
> $ cob brian
> $ link main + brian
> $ run main
> GLOBAL SECTION MAPPED
> 00008192{
> 00000017H
>
> And yes - the first byte of that global section I setup for the test
> has value of 177.
>
> Arne

Thanks for trying. I'm totally lost. Why are you DISPLAYing in the
data segment? FUNCTION ORD?

This "language" has a POINTER feature but I can't figure out how to use
it. Isn't there an example ANYWHERE on the net where $EXPREG or
LIB$GET_VM is used in COBOL?

On 9/7/2023 6:26 PM, Brian Schenkenberger wrote:
> On 2023-09-07 20:51:20 +0000, Arne Vajhj said:
>> For inspiration:
>>
>> $ type main.cob
>> IDENTIFICATION DIVISION.
>> PROGRAM-ID. SYSMGBLS.
>> ENVIRONMENT DIVISION.
>> DATA DIVISION.
>> WORKING-STORAGE SECTION.
>>
>> ***  EXTERNAL VALUE from SEC.MAR ($SECDEF GLOBAL)
>> ***  $ MACRO SEC.MAR
>> ***  $ LINK SYSMGBLSC,SEC
>>
>> 01 SEC$M_EXPREG    PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_EXPREG.
>> 01 SEC$M_PERM    PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_PERM.
>> 01 SEC$M_SYSGBL    PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_SYSGBL.
>>
>> 01 FLAGS  PIC S9(09) COMP VALUE IS 0.
>>
>> 01 RETSTS PIC S9(09) COMP VALUE IS 0.
>> 01 GBLSECNAM PIC X(21) VALUE IS "A-GLOBAL-SECTION-NAME".
>>
>> 01 INADR.
>>   02 IN-ADDRESS-1 PIC S9(09) COMP VALUE IS 512.
>>   02 IN-ADDRESS-2 PIC S9(09) COMP VALUE IS 512.
>>
>> 01 RETADR.
>>   02 RET-ADDRESS-1 PIC S9(09) COMP VALUE IS 0.
>>   02 RET-ADDRESS-2 PIC S9(09) COMP VALUE IS 0.
>>
>> 01 DATA-LEN PIC S9(09) COMP VALUE IS 81920.
>>
>> PROCEDURE DIVISION.
>> 0-BEGIN.
>>
>>        ADD SEC$M_EXPREG TO FLAGS.
>>
>>        CALL "SYS$MGBLSC"    USING    BY REFERENCE INADR,
>>                  BY REFERENCE RETADR,
>>                  OMITTED,
>>                  BY VALUE FLAGS,
>>                  BY DESCRIPTOR GBLSECNAM,
>>                  OMITTED,
>>                  OMITTED
>>              GIVING    RETSTS.
>>
>>        IF RETSTS IS FAILURE CALL "LIB$SIGNAL" USING BY VALUE RETSTS.
>>
>>        IF RETSTS IS SUCCESS DISPLAY "GLOBAL SECTION MAPPED".
>>
>>        CALL "BRIAN" USING BY REFERENCE DATA-LEN, BY VALUE RET-ADDRESS-1.
>>
>> 0-END.
>>        STOP RUN.
>> $ type brian.cob
>> IDENTIFICATION DIVISION.
>> PROGRAM-ID.BRIAN.
>> *
>> DATA DIVISION.
>> WORKING-STORAGE SECTION.
>> 01 NBYT2 PIC S9(9) DISPLAY.
>> 01 CVAL PIC S9(9) DISPLAY.
>> LINKAGE SECTION.
>> 01 NBYT PIC 9(9) COMP.
>> 01 BLOB.
>>    03 BYT PIC X OCCURS 1000000 TIMES.
>> *
>> PROCEDURE DIVISION USING NBYT BLOB.
>> ACK-PARAGRAPH.
>>      MOVE NBYT TO NBYT2
>>      DISPLAY NBYT2
>>      MOVE FUNCTION ORD(BYT(1)) TO CVAL
>>      DISPLAY CVAL.
>>      END PROGRAM BRIAN.
>> $ @cob
>> $ cob main
>> $ cob brian
>> $ link main + brian
>> $ run main
>> GLOBAL SECTION MAPPED
>> 00008192{
>> 00000017H
>>
>> And yes - the first byte of that global section I setup for the test
>> has value of 177.
>
> Thanks for trying.  I'm totally lost. Why are you DISPLAYing in the data
> segment? FUNCTION ORD?

The routine BRIAN just displays the length passed and
the first byte of the data passed.

It is to verify that the call is working.

The hack is this:

>> 01 RETADR.
>> 02 RET-ADDRESS-1 PIC S9(09) COMP VALUE IS 0.
>> 02 RET-ADDRESS-2 PIC S9(09) COMP VALUE IS 0.

>> CALL "SYS$MGBLSC" USING BY REFERENCE INADR,
>> BY REFERENCE RETADR,

RET-ADDRESS-1 and RET_ADDRESS-2 are lonmgwords
that after the call to MGBLSC contains start
and end address of the mapped area.

>> CALL "BRIAN" USING BY REFERENCE DATA-LEN, BY VALUE RET-ADDRESS-1.

Now we call BRIAN with second argument being a longword passed
by value.

But a longword that contains an address.

>> LINKAGE SECTION.
>> 01 NBYT PIC 9(9) COMP.
>> 01 BLOB.
>> 03 BYT PIC X OCCURS 1000000 TIMES.
>> *
>> PROCEDURE DIVISION USING NBYT BLOB.

BRIAN expect a structure BLOB (containing a byte array here,
but it could be anything) passed by reference.

SO the trick is to pass a longword by value containing the
address to a routine expecting a structure by reference.

> This "language" has a POINTER feature but I can't figure out how to use
> it. Isn't there an example ANYWHERE on the net where $EXPREG or
> LIB$GET_VM is used in COBOL?

I believe POINTER is just a container.

Arne

On Thursday, September 7, 2023 at 7:21:22 PM UTC-4, Arne Vajhøj wrote:
> On 9/7/2023 6:26 PM, Brian Schenkenberger wrote:
> > On 2023-09-07 20:51:20 +0000, Arne Vajh j said:
> >> For inspiration:
> >>
> >> $ type main.cob
> >> IDENTIFICATION DIVISION.
> >> PROGRAM-ID. SYSMGBLS.
> >> ENVIRONMENT DIVISION.
> >> DATA DIVISION.
> >> WORKING-STORAGE SECTION.
> >>
> >> *** EXTERNAL VALUE from SEC.MAR ($SECDEF GLOBAL)
> >> *** $ MACRO SEC.MAR
> >> *** $ LINK SYSMGBLSC,SEC
> >>
> >> 01 SEC$M_EXPREG PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_EXPREG.
> >> 01 SEC$M_PERM PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_PERM.
> >> 01 SEC$M_SYSGBL PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_SYSGBL.
> >>
> >> 01 FLAGS PIC S9(09) COMP VALUE IS 0.
> >>
> >> 01 RETSTS PIC S9(09) COMP VALUE IS 0.
> >> 01 GBLSECNAM PIC X(21) VALUE IS "A-GLOBAL-SECTION-NAME".
> >>
> >> 01 INADR.
> >> 02 IN-ADDRESS-1 PIC S9(09) COMP VALUE IS 512.
> >> 02 IN-ADDRESS-2 PIC S9(09) COMP VALUE IS 512.
> >>
> >> 01 RETADR.
> >> 02 RET-ADDRESS-1 PIC S9(09) COMP VALUE IS 0.
> >> 02 RET-ADDRESS-2 PIC S9(09) COMP VALUE IS 0.
> >>
> >> 01 DATA-LEN PIC S9(09) COMP VALUE IS 81920.
> >>
> >> PROCEDURE DIVISION.
> >> 0-BEGIN.
> >>
> >> ADD SEC$M_EXPREG TO FLAGS.
> >>
> >> CALL "SYS$MGBLSC" USING BY REFERENCE INADR,
> >> BY REFERENCE RETADR,
> >> OMITTED,
> >> BY VALUE FLAGS,
> >> BY DESCRIPTOR GBLSECNAM,
> >> OMITTED,
> >> OMITTED
> >> GIVING RETSTS.
> >>
> >> IF RETSTS IS FAILURE CALL "LIB$SIGNAL" USING BY VALUE RETSTS.
> >>
> >> IF RETSTS IS SUCCESS DISPLAY "GLOBAL SECTION MAPPED".
> >>
> >> CALL "BRIAN" USING BY REFERENCE DATA-LEN, BY VALUE RET-ADDRESS-1.
> >>
> >> 0-END.
> >> STOP RUN.
> >> $ type brian.cob
> >> IDENTIFICATION DIVISION.
> >> PROGRAM-ID.BRIAN.
> >> *
> >> DATA DIVISION.
> >> WORKING-STORAGE SECTION.
> >> 01 NBYT2 PIC S9(9) DISPLAY.
> >> 01 CVAL PIC S9(9) DISPLAY.
> >> LINKAGE SECTION.
> >> 01 NBYT PIC 9(9) COMP.
> >> 01 BLOB.
> >> 03 BYT PIC X OCCURS 1000000 TIMES.
> >> *
> >> PROCEDURE DIVISION USING NBYT BLOB.
> >> ACK-PARAGRAPH.
> >> MOVE NBYT TO NBYT2
> >> DISPLAY NBYT2
> >> MOVE FUNCTION ORD(BYT(1)) TO CVAL
> >> DISPLAY CVAL.
> >> END PROGRAM BRIAN.
> >> $ @cob
> >> $ cob main
> >> $ cob brian
> >> $ link main + brian
> >> $ run main
> >> GLOBAL SECTION MAPPED
> >> 00008192{
> >> 00000017H
> >>
> >> And yes - the first byte of that global section I setup for the test
> >> has value of 177.
> >
> > Thanks for trying. I'm totally lost. Why are you DISPLAYing in the data
> > segment? FUNCTION ORD?
> The routine BRIAN just displays the length passed and
> the first byte of the data passed.
>
> It is to verify that the call is working.
>
> The hack is this:
> >> 01 RETADR.
> >> 02 RET-ADDRESS-1 PIC S9(09) COMP VALUE IS 0.
> >> 02 RET-ADDRESS-2 PIC S9(09) COMP VALUE IS 0.
> >> CALL "SYS$MGBLSC" USING BY REFERENCE INADR,
> >> BY REFERENCE RETADR,
> RET-ADDRESS-1 and RET_ADDRESS-2 are lonmgwords
> that after the call to MGBLSC contains start
> and end address of the mapped area.
> >> CALL "BRIAN" USING BY REFERENCE DATA-LEN, BY VALUE RET-ADDRESS-1.
> Now we call BRIAN with second argument being a longword passed
> by value.
>
> But a longword that contains an address.
> >> LINKAGE SECTION.
> >> 01 NBYT PIC 9(9) COMP.
> >> 01 BLOB.
> >> 03 BYT PIC X OCCURS 1000000 TIMES.
> >> *
> >> PROCEDURE DIVISION USING NBYT BLOB.
> BRIAN expect a structure BLOB (containing a byte array here,
> but it could be anything) passed by reference.
>
> SO the trick is to pass a longword by value containing the
> address to a routine expecting a structure by reference.
> > This "language" has a POINTER feature but I can't figure out how to use
> > it. Isn't there an example ANYWHERE on the net where $EXPREG or
> > LIB$GET_VM is used in COBOL?
> I believe POINTER is just a container.
>
> Arne
Yep, POINTER is one of the few COBOL 2002 keywords in the compiler.
Just a container of the correct size (64-bits) but you can't really operate on
it. You can just pass it to some other routine (in another language that CAN
operate on such things)

On 2023-09-08 01:50:30 +0000, John Reagan said:

> Yep, POINTER is one of the few COBOL 2002 keywords in the compiler.
> Just a container of the correct size (64-bits) but you can't really
> operate onit. You can just pass it to some other routine (in another
> language that CAN
> operate on such things)

So, it's useless. I've been trying COBOL examples I've found on the net
and they fail. That explains why.

So there's no way to $MGBLSC, $EXPREG, LIB$GET_VM and use the region
created directly in COBOL.

Grrrr.

Thanks John. At least I won't be banging my head against the wall
trying to figure out this COBOL.

— Brian

On Friday, September 8, 2023 at 8:09:01 AM UTC-4, Brian Schenkenberger wrote:
> On 2023-09-08 01:50:30 +0000, John Reagan said:
>
> > Yep, POINTER is one of the few COBOL 2002 keywords in the compiler.
> > Just a container of the correct size (64-bits) but you can't really
> > operate onit. You can just pass it to some other routine (in another
> > language that CAN
> > operate on such things)
> So, it's useless. I've been trying COBOL examples I've found on the net
> and they fail. That explains why.
>
> So there's no way to $MGBLSC, $EXPREG, LIB$GET_VM and use the region
> created directly in COBOL.
>
> Grrrr.
>
> Thanks John. At least I won't be banging my head against the wall
> trying to figure out this COBOL.
>
> — Brian
I wasn't in the meetings with the COBOL team to hear if they were planning
to add additional COBOL 2002 support that would include the ability to
operate. I don't remember hearing about it at the lunch table (which is where
I got most of my information at that time). Regardless, you are correct, I
don't think you can write an all-COBOL solution

John

On 9/8/2023 8:08 AM, Brian Schenkenberger wrote:
> On 2023-09-08 01:50:30 +0000, John Reagan said:
>> Yep, POINTER is one of the few COBOL 2002 keywords in the compiler.
>> Just a container of the correct size (64-bits) but you can't really
>> operate onit.  You can just pass it to some other routine (in another
>> language that CAN
>> operate on such things)
>
> So, it's useless. I've been trying COBOL examples I've found on the net
> and they fail.  That explains why.
>
> So there's no way to $MGBLSC, $EXPREG, LIB$GET_VM and use the region
> created directly in COBOL.

POINTER may be "useless".

But as I showed you just pass an integer with the address by value
to a routine expecting something by reference.

Arne

On 2023-09-07, Brian Schenkenberger <mail@SendSpamHere.ORG> wrote:
>
> ? VAXman (still on the outside trying to look into VMS x86)
>

Where exactly are you being blocked from registering for the x86-64
VMS community program and how ?

If it's a browser issue, what browser and OS are you using, and what
have you tried ?

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.

On 2023-09-08 12:25:38 +0000, Simon Clubley said:

> On 2023-09-07, Brian Schenkenberger <mail@SendSpamHere.ORG> wrote:
>>
>> ? VAXman (still on the outside trying to look into VMS x86)
>>
>
> Where exactly are you being blocked from registering for the x86-64
> VMS community program and how ?
>
> If it's a browser issue, what browser and OS are you using, and what
> have you tried ?
>
> Simon.

I got a reply from VSI over a week ago but I'm still in the dark.

I've had several request to port RMS-CDC but that may never ever
happen. C'est la vie.

On 2023-09-07 23:21:18 +0000, Arne Vajhj said:

> On 9/7/2023 6:26 PM, Brian Schenkenberger wrote:
>> On 2023-09-07 20:51:20 +0000, Arne Vajhj said:
>>> For inspiration:
>>>
>>> $ type main.cob
>>> IDENTIFICATION DIVISION.
>>> PROGRAM-ID. SYSMGBLS.
>>> ENVIRONMENT DIVISION.
>>> DATA DIVISION.
>>> WORKING-STORAGE SECTION.
>>>
>>> ***  EXTERNAL VALUE from SEC.MAR ($SECDEF GLOBAL)
>>> ***  $ MACRO SEC.MAR
>>> ***  $ LINK SYSMGBLSC,SEC
>>>
>>> 01 SEC$M_EXPREG    PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_EXPREG.
>>> 01 SEC$M_PERM    PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_PERM.
>>> 01 SEC$M_SYSGBL    PIC S9(09) COMP VALUE IS EXTERNAL SEC$M_SYSGBL.
>>>
>>> 01 FLAGS  PIC S9(09) COMP VALUE IS 0.
>>>
>>> 01 RETSTS PIC S9(09) COMP VALUE IS 0.
>>> 01 GBLSECNAM PIC X(21) VALUE IS "A-GLOBAL-SECTION-NAME".
>>>
>>> 01 INADR.
>>>   02 IN-ADDRESS-1 PIC S9(09) COMP VALUE IS 512.
>>>   02 IN-ADDRESS-2 PIC S9(09) COMP VALUE IS 512.
>>>
>>> 01 RETADR.
>>>   02 RET-ADDRESS-1 PIC S9(09) COMP VALUE IS 0.
>>>   02 RET-ADDRESS-2 PIC S9(09) COMP VALUE IS 0.
>>>
>>> 01 DATA-LEN PIC S9(09) COMP VALUE IS 81920.
>>>
>>> PROCEDURE DIVISION.
>>> 0-BEGIN.
>>>
>>>        ADD SEC$M_EXPREG TO FLAGS.
>>>
>>>        CALL "SYS$MGBLSC"    USING    BY REFERENCE INADR,
>>>                  BY REFERENCE RETADR,
>>>                  OMITTED,
>>>                  BY VALUE FLAGS,
>>>                  BY DESCRIPTOR GBLSECNAM,
>>>                  OMITTED,
>>>                  OMITTED
>>>              GIVING    RETSTS.
>>>
>>>        IF RETSTS IS FAILURE CALL "LIB$SIGNAL" USING BY VALUE RETSTS.
>>>
>>>        IF RETSTS IS SUCCESS DISPLAY "GLOBAL SECTION MAPPED".
>>>
>>>        CALL "BRIAN" USING BY REFERENCE DATA-LEN, BY VALUE RET-ADDRESS-1.
>>>
>>> 0-END.
>>>        STOP RUN.
>>> $ type brian.cob
>>> IDENTIFICATION DIVISION.
>>> PROGRAM-ID.BRIAN.
>>> *
>>> DATA DIVISION.
>>> WORKING-STORAGE SECTION.
>>> 01 NBYT2 PIC S9(9) DISPLAY.
>>> 01 CVAL PIC S9(9) DISPLAY.
>>> LINKAGE SECTION.
>>> 01 NBYT PIC 9(9) COMP.
>>> 01 BLOB.
>>>    03 BYT PIC X OCCURS 1000000 TIMES.
>>> *
>>> PROCEDURE DIVISION USING NBYT BLOB.
>>> ACK-PARAGRAPH.
>>>      MOVE NBYT TO NBYT2
>>>      DISPLAY NBYT2
>>>      MOVE FUNCTION ORD(BYT(1)) TO CVAL
>>>      DISPLAY CVAL.
>>>      END PROGRAM BRIAN.
>>> $ @cob
>>> $ cob main
>>> $ cob brian
>>> $ link main + brian
>>> $ run main
>>> GLOBAL SECTION MAPPED
>>> 00008192{
>>> 00000017H
>>>
>>> And yes - the first byte of that global section I setup for the test
>>> has value of 177.
>>
>> Thanks for trying.  I'm totally lost. Why are you DISPLAYing in the
>> data segment? FUNCTION ORD?
>
> The routine BRIAN just displays the length passed and
> the first byte of the data passed.
>
> It is to verify that the call is working.
>
> The hack is this:
>
> >> 01 RETADR.
> >> 02 RET-ADDRESS-1 PIC S9(09) COMP VALUE IS 0.
> >> 02 RET-ADDRESS-2 PIC S9(09) COMP VALUE IS 0.
>
> >> CALL "SYS$MGBLSC" USING BY REFERENCE INADR,
> >> BY REFERENCE RETADR,
>
> RET-ADDRESS-1 and RET_ADDRESS-2 are lonmgwords
> that after the call to MGBLSC contains start
> and end address of the mapped area.
>
> >> CALL "BRIAN" USING BY REFERENCE DATA-LEN, BY VALUE RET-ADDRESS-1.
>
> Now we call BRIAN with second argument being a longword passed
> by value.
>
> But a longword that contains an address.
>
> >> LINKAGE SECTION.
> >> 01 NBYT PIC 9(9) COMP.
> >> 01 BLOB.
> >> 03 BYT PIC X OCCURS 1000000 TIMES.
> >> *
> >> PROCEDURE DIVISION USING NBYT BLOB.
>
> BRIAN expect a structure BLOB (containing a byte array here,
> but it could be anything) passed by reference.
>
> SO the trick is to pass a longword by value containing the
> address to a routine expecting a structure by reference.
>
>> This "language" has a POINTER feature but I can't figure out how to use
>> it. Isn't there an example ANYWHERE on the net where $EXPREG or
>> LIB$GET_VM is used in COBOL?
>
> I believe POINTER is just a container.
>
> Arne

I have the SYS$MGBLSC working... at least, in the debugger. I defined
a test global section with two longwords.

1,-1
2,-2
3,-3
etc.,-etc.
0,0

I have the following for the global section's element definition:

LINKAGE SECTION.

01 GLOBAL-SECTION.
02 ELEMENT OCCURS 2000 TIMES.
03 A PIC S9(9) COMP.
03 B PIC S9(9) COMP.

and the procedure...

PROCEDURE DIVISION USING GLOBAL_SECTION.
PARAGRAPH-MAIN.
PERFORM PARAGRAPH-ENTER THRU PARAGRAPH-EXIT
VARYING I FROM 1 BY 1 UNTIL A(I) = 0 AND B(I) = 0.
PARAGRAPH-ENTER.
DISPLAY "First[" I "]: " A(I) " Second[" I "]: " B(I).
PARAGRAPH-EXIT.
EXIT.
END PROGRAM GBLSEC.

In the debugger, A(I) and B(I) show me the values but DISPLAY pukes on
them. It'd be great too if there was a way to DISPLAY them in HEX but
just getting it to DISPLAY without regurgitaing garbage would be great.

I also can't figure out how to define GLOBA:L-SECTION ELEMENT OCCURS *
TIMES. The number of the elements in the global section could be quite
variable.

On 9/8/2023 12:45 PM, Brian Schenkenberger wrote:
> I have the SYS$MGBLSC working... at least, in the debugger.  I defined a
> test global section with two longwords.
>
> 1,-1
> 2,-2
> 3,-3
> etc.,-etc.
> 0,0
>
> I have the following for the global section's element definition:
>
> LINKAGE SECTION.
>
> 01 GLOBAL-SECTION.
>  02 ELEMENT OCCURS 2000 TIMES.
>    03 A        PIC S9(9) COMP.
>    03 B        PIC S9(9) COMP.
>
> and the procedure...
>
> PROCEDURE DIVISION USING GLOBAL_SECTION.
> PARAGRAPH-MAIN.
>    PERFORM PARAGRAPH-ENTER THRU PARAGRAPH-EXIT
>            VARYING I FROM 1 BY 1 UNTIL A(I) = 0 AND B(I) = 0.
> PARAGRAPH-ENTER.
>    DISPLAY "First[" I "]: " A(I) "  Second[" I "]: " B(I).
> PARAGRAPH-EXIT.
>    EXIT.
> END PROGRAM GBLSEC.
>
> In the debugger, A(I) and B(I) show me the values but DISPLAY pukes on
> them. It'd be great too if there was a way to DISPLAY them in HEX but
> just getting it to DISPLAY without regurgitaing garbage would be great.

Add a couple of temporary variables:

WORKING-STORAGE SECTION.
01 AI PIC 9(4) DISPLAY.
01 BI PIC 9(4) DISPLAY.

and do:

MOVE A(I) TO AI
MOVE B(I) TO BI
DISPLAY "First[" I "]: " AI " Second[" I "]: " BI.

If anyone that actually knows Cobol has a better solution then
I am also interested!

> I also can't figure out how to define GLOBA:L-SECTION ELEMENT OCCURS *
> TIMES. The number of the elements in the global section could be quite
> variable.

I don't think it is possible.

Just declare it big enough and only access what actually exist.

It is just an address that is being passed.

Arne

On 9/8/2023 1:13 PM, Arne Vajhøj wrote:
> On 9/8/2023 12:45 PM, Brian Schenkenberger wrote:
>> I have the SYS$MGBLSC working... at least, in the debugger.  I defined
>> a test global section with two longwords.
>>
>> 1,-1
>> 2,-2
>> 3,-3
>> etc.,-etc.
>> 0,0
>>
>> I have the following for the global section's element definition:
>>
>> LINKAGE SECTION.
>>
>> 01 GLOBAL-SECTION.
>>   02 ELEMENT OCCURS 2000 TIMES.
>>     03 A        PIC S9(9) COMP.
>>     03 B        PIC S9(9) COMP.
>>
>> and the procedure...
>>
>> PROCEDURE DIVISION USING GLOBAL_SECTION.
>> PARAGRAPH-MAIN.
>>     PERFORM PARAGRAPH-ENTER THRU PARAGRAPH-EXIT
>>             VARYING I FROM 1 BY 1 UNTIL A(I) = 0 AND B(I) = 0.
>> PARAGRAPH-ENTER.
>>     DISPLAY "First[" I "]: " A(I) "  Second[" I "]: " B(I).
>> PARAGRAPH-EXIT.
>>     EXIT.
>> END PROGRAM GBLSEC.
>>
>> In the debugger, A(I) and B(I) show me the values but DISPLAY pukes on
>> them. It'd be great too if there was a way to DISPLAY them in HEX but
>> just getting it to DISPLAY without regurgitaing garbage would be great.
>
> Add a couple of temporary variables:
>
> WORKING-STORAGE SECTION.
> 01 AI PIC 9(4) DISPLAY.
> 01 BI PIC 9(4) DISPLAY.
>
> and do:
>
> MOVE A(I) TO AI
> MOVE B(I) TO BI
> DISPLAY "First[" I "]: " AI "  Second[" I "]: " BI.
>
> If anyone that actually knows Cobol has a better solution then
> I am also interested!

I really don't have that much experience with VMS COBOL and have no idea
what $MGBLSC means, but, if it is merely a display problem how about a
REDEFINES from COMP to DISPLAY instead of another variable and the MOVE?

Is this unique to x86-64 or could I play with the examples on EISNER?

bill

On 9/8/2023 1:55 PM, bill wrote:

> I really don't have that much experience with VMS COBOL and have no idea
> what $MGBLSC means,

Brian is attempting to access a global section from a Cobol program. (Must be a
glutton for punishment.) That is a system service to map to an existing (I
think) global section.

--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: davef@tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486

On 9/8/2023 1:55 PM, bill wrote:
> On 9/8/2023 1:13 PM, Arne Vajhøj wrote:
>> On 9/8/2023 12:45 PM, Brian Schenkenberger wrote:
>>> I have the SYS$MGBLSC working... at least, in the debugger.  I
>>> defined a test global section with two longwords.
>>>
>>> 1,-1
>>> 2,-2
>>> 3,-3
>>> etc.,-etc.
>>> 0,0
>>>
>>> I have the following for the global section's element definition:
>>>
>>> LINKAGE SECTION.
>>>
>>> 01 GLOBAL-SECTION.
>>>   02 ELEMENT OCCURS 2000 TIMES.
>>>     03 A        PIC S9(9) COMP.
>>>     03 B        PIC S9(9) COMP.
>>>
>>> and the procedure...
>>>
>>> PROCEDURE DIVISION USING GLOBAL_SECTION.
>>> PARAGRAPH-MAIN.
>>>     PERFORM PARAGRAPH-ENTER THRU PARAGRAPH-EXIT
>>>             VARYING I FROM 1 BY 1 UNTIL A(I) = 0 AND B(I) = 0.
>>> PARAGRAPH-ENTER.
>>>     DISPLAY "First[" I "]: " A(I) "  Second[" I "]: " B(I).
>>> PARAGRAPH-EXIT.
>>>     EXIT.
>>> END PROGRAM GBLSEC.
>>>
>>> In the debugger, A(I) and B(I) show me the values but DISPLAY pukes
>>> on them. It'd be great too if there was a way to DISPLAY them in HEX
>>> but just getting it to DISPLAY without regurgitaing garbage would be
>>> great.
>>
>> Add a couple of temporary variables:
>>
>> WORKING-STORAGE SECTION.
>> 01 AI PIC 9(4) DISPLAY.
>> 01 BI PIC 9(4) DISPLAY.
>>
>> and do:
>>
>> MOVE A(I) TO AI
>> MOVE B(I) TO BI
>> DISPLAY "First[" I "]: " AI "  Second[" I "]: " BI.
>>
>> If anyone that actually knows Cobol has a better solution then
>> I am also interested!
>
> I really don't have that much experience with VMS COBOL and have no idea
> what $MGBLSC means,

SYS$MGLBSC is the VMS system service to map a global section.

> but, if it is merely a display problem how about a
> REDEFINES from COMP to DISPLAY instead of another variable and the MOVE?

How would that look like?

> Is this unique to x86-64 or could I play with the examples on EISNER?

Not x86-64 specific. In fact I am pretty sure that Brian is not
running it on x86-64. You could run it on VAX!

Arne

On 9/8/2023 4:40 PM, Arne Vajhøj wrote:
> On 9/8/2023 1:55 PM, bill wrote:
>> On 9/8/2023 1:13 PM, Arne Vajhøj wrote:
>>> On 9/8/2023 12:45 PM, Brian Schenkenberger wrote:
>>>> I have the SYS$MGBLSC working... at least, in the debugger.  I
>>>> defined a test global section with two longwords.
>>>>
>>>> 1,-1
>>>> 2,-2
>>>> 3,-3
>>>> etc.,-etc.
>>>> 0,0
>>>>
>>>> I have the following for the global section's element definition:
>>>>
>>>> LINKAGE SECTION.
>>>>
>>>> 01 GLOBAL-SECTION.
>>>>   02 ELEMENT OCCURS 2000 TIMES.
>>>>     03 A        PIC S9(9) COMP.
>>>>     03 B        PIC S9(9) COMP.
>>>>
>>>> and the procedure...
>>>>
>>>> PROCEDURE DIVISION USING GLOBAL_SECTION.
>>>> PARAGRAPH-MAIN.
>>>>     PERFORM PARAGRAPH-ENTER THRU PARAGRAPH-EXIT
>>>>             VARYING I FROM 1 BY 1 UNTIL A(I) = 0 AND B(I) = 0.
>>>> PARAGRAPH-ENTER.
>>>>     DISPLAY "First[" I "]: " A(I) "  Second[" I "]: " B(I).
>>>> PARAGRAPH-EXIT.
>>>>     EXIT.
>>>> END PROGRAM GBLSEC.
>>>>
>>>> In the debugger, A(I) and B(I) show me the values but DISPLAY pukes
>>>> on them. It'd be great too if there was a way to DISPLAY them in HEX
>>>> but just getting it to DISPLAY without regurgitaing garbage would be
>>>> great.
>>>
>>> Add a couple of temporary variables:
>>>
>>> WORKING-STORAGE SECTION.
>>> 01 AI PIC 9(4) DISPLAY.
>>> 01 BI PIC 9(4) DISPLAY.
>>>
>>> and do:
>>>
>>> MOVE A(I) TO AI
>>> MOVE B(I) TO BI
>>> DISPLAY "First[" I "]: " AI "  Second[" I "]: " BI.
>>>
>>> If anyone that actually knows Cobol has a better solution then
>>> I am also interested!
>>
>> I really don't have that much experience with VMS COBOL and have no idea
>> what $MGBLSC means,
>
> SYS$MGLBSC is the VMS system service to map a global section.
>
>>                      but, if it is merely a display problem how about a
>> REDEFINES from COMP to DISPLAY instead of another variable and the MOVE?
>
> How would that look like?

Can you point me at a copy of the VMS COBOL Reference Manual?
This is something VMS specific. I tried a couple sites. One
of them returned XML errors and sector7 pointed me at localhost.
If I can grab a quick look at the manual I can probably provide
a fairly clean way to do it. I may even try to figure out how
to get to EISNER after the port change and then I will actually
test what I write.

>
>> Is this unique to x86-64 or could I play with the examples on EISNER?
>
> Not x86-64 specific. In fact I am pretty sure that Brian is not
> running it on x86-64. You could run it on VAX!
>
> Arne
>
>

bill

On 08/09/2023 23:50, bill wrote:
> On 9/8/2023 4:40 PM, Arne Vajhøj wrote:
>> On 9/8/2023 1:55 PM, bill wrote:
>>> On 9/8/2023 1:13 PM, Arne Vajhøj wrote:
>>>> On 9/8/2023 12:45 PM, Brian Schenkenberger wrote:
>>>>> I have the SYS$MGBLSC working... at least, in the debugger.  I
>>>>> defined a test global section with two longwords.
>>>>>
>>>>> 1,-1
>>>>> 2,-2
>>>>> 3,-3
>>>>> etc.,-etc.
>>>>> 0,0
>>>>>
>>>>> I have the following for the global section's element definition:
>>>>>
>>>>> LINKAGE SECTION.
>>>>>
>>>>> 01 GLOBAL-SECTION.
>>>>>   02 ELEMENT OCCURS 2000 TIMES.
>>>>>     03 A        PIC S9(9) COMP.
>>>>>     03 B        PIC S9(9) COMP.
>>>>>
>>>>> and the procedure...
>>>>>
>>>>> PROCEDURE DIVISION USING GLOBAL_SECTION.
>>>>> PARAGRAPH-MAIN.
>>>>>     PERFORM PARAGRAPH-ENTER THRU PARAGRAPH-EXIT
>>>>>             VARYING I FROM 1 BY 1 UNTIL A(I) = 0 AND B(I) = 0.
>>>>> PARAGRAPH-ENTER.
>>>>>     DISPLAY "First[" I "]: " A(I) "  Second[" I "]: " B(I).
>>>>> PARAGRAPH-EXIT.
>>>>>     EXIT.
>>>>> END PROGRAM GBLSEC.
>>>>>
>>>>> In the debugger, A(I) and B(I) show me the values but DISPLAY pukes
>>>>> on them. It'd be great too if there was a way to DISPLAY them in
>>>>> HEX but just getting it to DISPLAY without regurgitaing garbage
>>>>> would be great.
>>>>
>>>> Add a couple of temporary variables:
>>>>
>>>> WORKING-STORAGE SECTION.
>>>> 01 AI PIC 9(4) DISPLAY.
>>>> 01 BI PIC 9(4) DISPLAY.
>>>>
>>>> and do:
>>>>
>>>> MOVE A(I) TO AI
>>>> MOVE B(I) TO BI
>>>> DISPLAY "First[" I "]: " AI "  Second[" I "]: " BI.
>>>>
>>>> If anyone that actually knows Cobol has a better solution then
>>>> I am also interested!
>>>
>>> I really don't have that much experience with VMS COBOL and have no idea
>>> what $MGBLSC means,
>>
>> SYS$MGLBSC is the VMS system service to map a global section.
>>
>>>                      but, if it is merely a display problem how about a
>>> REDEFINES from COMP to DISPLAY instead of another variable and the MOVE?
>>
>> How would that look like?
>
> Can you point me at a copy of the VMS COBOL Reference Manual?
> This is something VMS specific.  I tried a couple sites.  One
> of them returned XML errors and sector7 pointed me at localhost.
> If I can grab a quick look at the manual I can probably provide
> a fairly clean way to do it.  I may even try to figure out how
> to get to EISNER after the port change and then I will actually
> test what I write.
>

Try https://docs.vmssoftware.com/vsi-cobol-for-openvms-reference-guide
There is also a User guide

--
Chris

On 9/8/2023 6:59 PM, Chris Townley wrote:
> On 08/09/2023 23:50, bill wrote:
>> On 9/8/2023 4:40 PM, Arne Vajhøj wrote:
>>> On 9/8/2023 1:55 PM, bill wrote:
>>>> On 9/8/2023 1:13 PM, Arne Vajhøj wrote:
>>>>> On 9/8/2023 12:45 PM, Brian Schenkenberger wrote:
>>>>>> I have the SYS$MGBLSC working... at least, in the debugger.  I
>>>>>> defined a test global section with two longwords.
>>>>>>
>>>>>> 1,-1
>>>>>> 2,-2
>>>>>> 3,-3
>>>>>> etc.,-etc.
>>>>>> 0,0
>>>>>>
>>>>>> I have the following for the global section's element definition:
>>>>>>
>>>>>> LINKAGE SECTION.
>>>>>>
>>>>>> 01 GLOBAL-SECTION.
>>>>>>   02 ELEMENT OCCURS 2000 TIMES.
>>>>>>     03 A        PIC S9(9) COMP.
>>>>>>     03 B        PIC S9(9) COMP.
>>>>>>
>>>>>> and the procedure...
>>>>>>
>>>>>> PROCEDURE DIVISION USING GLOBAL_SECTION.
>>>>>> PARAGRAPH-MAIN.
>>>>>>     PERFORM PARAGRAPH-ENTER THRU PARAGRAPH-EXIT
>>>>>>             VARYING I FROM 1 BY 1 UNTIL A(I) = 0 AND B(I) = 0.
>>>>>> PARAGRAPH-ENTER.
>>>>>>     DISPLAY "First[" I "]: " A(I) "  Second[" I "]: " B(I).
>>>>>> PARAGRAPH-EXIT.
>>>>>>     EXIT.
>>>>>> END PROGRAM GBLSEC.
>>>>>>
>>>>>> In the debugger, A(I) and B(I) show me the values but DISPLAY
>>>>>> pukes on them. It'd be great too if there was a way to DISPLAY
>>>>>> them in HEX but just getting it to DISPLAY without regurgitaing
>>>>>> garbage would be great.
>>>>>
>>>>> Add a couple of temporary variables:
>>>>>
>>>>> WORKING-STORAGE SECTION.
>>>>> 01 AI PIC 9(4) DISPLAY.
>>>>> 01 BI PIC 9(4) DISPLAY.
>>>>>
>>>>> and do:
>>>>>
>>>>> MOVE A(I) TO AI
>>>>> MOVE B(I) TO BI
>>>>> DISPLAY "First[" I "]: " AI "  Second[" I "]: " BI.
>>>>>
>>>>> If anyone that actually knows Cobol has a better solution then
>>>>> I am also interested!
>>>>
>>>> I really don't have that much experience with VMS COBOL and have no
>>>> idea
>>>> what $MGBLSC means,
>>>
>>> SYS$MGLBSC is the VMS system service to map a global section.
>>>
>>>>                      but, if it is merely a display problem how about a
>>>> REDEFINES from COMP to DISPLAY instead of another variable and the
>>>> MOVE?
>>>
>>> How would that look like?
>>
>> Can you point me at a copy of the VMS COBOL Reference Manual?
>> This is something VMS specific.  I tried a couple sites.  One
>> of them returned XML errors and sector7 pointed me at localhost.
>> If I can grab a quick look at the manual I can probably provide
>> a fairly clean way to do it.  I may even try to figure out how
>> to get to EISNER after the port change and then I will actually
>> test what I write.
>>
>
> Try https://docs.vmssoftware.com/vsi-cobol-for-openvms-reference-guide
> There is also a User guide
>

Thank you. I'll try there. The users guide won;t cut it. I
need the reference guide.

bill

On Friday, September 8, 2023 at 12:45:07 PM UTC-4, Brian Schenkenberger wrote:

> I have the SYS$MGBLSC working... at least, in the debugger.:
: > I have the following for the global section's element definition:
>
> LINKAGE SECTION.
>
> 01 GLOBAL-SECTION.
> 02 ELEMENT OCCURS 2000 TIMES.
> 03 A PIC S9(9) COMP.
> 03 B PIC S9(9) COMP.
>
> and the procedure...
>
> PROCEDURE DIVISION USING GLOBAL_SECTION.

Good, that creates a subroutine expecting a pointer to a structure, which may be in a global section previously mapped.
But before we go there, what exactly are the customer requirements?
There is also something called 'EXTERNAL DATA', essentially named Psects/common blocks.

> PARAGRAPH-MAIN.
> PERFORM PARAGRAPH-ENTER THRU PARAGRAPH-EXIT
> VARYING I FROM 1 BY 1 UNTIL A(I) = 0 AND B(I) = 0.
> PARAGRAPH-ENTER.
> DISPLAY "First[" I "]: " A(I) " Second[" I "]: " B(I).
> PARAGRAPH-EXIT.
> EXIT.
> END PROGRAM GBLSEC.
>
> In the debugger, A(I) and B(I) show me the values but DISPLAY pukes on
> them. It'd be great too if there was a way to DISPLAY them in HEX but
> just getting it to DISPLAY without regurgitaing garbage would be great.

Ask yourself AITA for expecting a compiler NOT to do exactly what I ask? Garbage in, Garbage out - as requested.

You are TA for being an ancient hack (much like myself) who can only think bits and bytes when he can just do text!
Load your global with ascii "+001" and "-001" or "AAAB" and similar and call it is PIC X(4) or PIC 9(4) USAGE DISPLAY and all will be well :-).

Or... DISPLAY WITH CONVERSION !

Or, RTFM ... "5. Numeric items do not require the CONVERSION phrase to be displayed correctly with conversion if you specify /DISPLAY_FORMATTED (on OpenVMS Alpha")

Or, as Arne suggests, move (= convert) them into a display helper variable and use that.
This may be best for many cases because (if I recall correctly) any use of "WITH CONVERSION" activates some bonus screen handling you may not care for

(I hope I do not have to litter this with smiley's to indicate these are all friendly pokes, do I?)

>
> I also can't figure out how to define GLOBA:L-SECTION ELEMENT OCCURS *
> TIMES. The number of the elements in the global section could be quite
> variable.

With the linkage section it's all just virtual right? take a thousand, take a million, it matters none I suspect -- haven't tried i a while.

Ah... is this a peephole into the actual user requirements?
Are the elements fixed length?
Anyways, could you not make the linkage section just for one 'element' and do pointer math on the outside to provide the right element?
Or provide a second lower level function with just the 1 element also passed as linkage and called from the one you have?
Remember these are functions 'giving', but they can only 'give' an R0 return value. Per Reference Guide: "The identifier must refer to an elementary integer numeric data
item with COMP, COMP-1, or COMP-2 usage and no scaling positions."

Greetings my friend! I'll re-poke some folks for I64 access as we (or rather they! have a mutual shared goal.

Hein.

On 9/8/2023 12:45 PM, Brian Schenkenberger wrote:
> It'd be great too if there was a way to DISPLAY them in HEX

I don't know the right Cobol way to display as hex, but
FAO work in Cobol as well.

identification division.
program-id.hex1.
* data division.
working-storage section.
01 v pic 9(9) comp.
01 fmt pic x(7) value "!SL !XL".
01 buflen pic 9(9) comp.
01 buf pic x(100).
* procedure division.
main-paragraph.
move 123 to v
call "LIB$SYS_FAO"
using
by descriptor fmt
by reference buflen
by descriptor buf
by value v
by value v
end-call
display buf(1:buflen)
stop run.

Arne

On 9/8/2023 10:18 PM, Arne Vajhøj wrote:
> On 9/8/2023 12:45 PM, Brian Schenkenberger wrote:
>> It'd be great too if there was a way to DISPLAY them in HEX
>
> I don't know the right Cobol way to display as hex, but
> FAO work in Cobol as well.
>
> identification division.
> program-id.hex1.
> *
> data division.
> working-storage section.
> 01  v       pic 9(9) comp.
> 01  fmt     pic x(7) value "!SL !XL".
> 01  buflen  pic 9(9) comp.
> 01  buf     pic x(100).
> *
> procedure division.
> main-paragraph.
>     move 123 to v
>     call "LIB$SYS_FAO"
>         using
>            by descriptor fmt
>            by reference buflen
>            by descriptor buf
>            by value v
>            by value v
>     end-call
>     display buf(1:buflen)
>     stop run.

Or if you really want to hack it:

identification division.
program-id.hex2.
* data division.
working-storage section.
01 v pic 9(9) comp.
01 fmt pic x(11) value "%d %08x%c%c".
01 cr pic 9(9) comp value 13.
01 lf pic 9(9) comp value 10.
* procedure division.
main-paragraph.
move 123 to v
call "DECC$GXPRINTF"
using
by reference fmt
by value v
by value v
by value cr
by value lf
end-call
stop run.

Arne

On 9/8/2023 6:59 PM, Chris Townley wrote:
> On 08/09/2023 23:50, bill wrote:
>> On 9/8/2023 4:40 PM, Arne Vajhøj wrote:
>>> On 9/8/2023 1:55 PM, bill wrote:
>>>> On 9/8/2023 1:13 PM, Arne Vajhøj wrote:
>>>>> On 9/8/2023 12:45 PM, Brian Schenkenberger wrote:
>>>>>> I have the SYS$MGBLSC working... at least, in the debugger.  I
>>>>>> defined a test global section with two longwords.
>>>>>>
>>>>>> 1,-1
>>>>>> 2,-2
>>>>>> 3,-3
>>>>>> etc.,-etc.
>>>>>> 0,0
>>>>>>
>>>>>> I have the following for the global section's element definition:
>>>>>>
>>>>>> LINKAGE SECTION.
>>>>>>
>>>>>> 01 GLOBAL-SECTION.
>>>>>>   02 ELEMENT OCCURS 2000 TIMES.
>>>>>>     03 A        PIC S9(9) COMP.
>>>>>>     03 B        PIC S9(9) COMP.
>>>>>>
>>>>>> and the procedure...
>>>>>>
>>>>>> PROCEDURE DIVISION USING GLOBAL_SECTION.
>>>>>> PARAGRAPH-MAIN.
>>>>>>     PERFORM PARAGRAPH-ENTER THRU PARAGRAPH-EXIT
>>>>>>             VARYING I FROM 1 BY 1 UNTIL A(I) = 0 AND B(I) = 0.
>>>>>> PARAGRAPH-ENTER.
>>>>>>     DISPLAY "First[" I "]: " A(I) "  Second[" I "]: " B(I).
>>>>>> PARAGRAPH-EXIT.
>>>>>>     EXIT.
>>>>>> END PROGRAM GBLSEC.
>>>>>>
>>>>>> In the debugger, A(I) and B(I) show me the values but DISPLAY
>>>>>> pukes on them. It'd be great too if there was a way to DISPLAY
>>>>>> them in HEX but just getting it to DISPLAY without regurgitaing
>>>>>> garbage would be great.
>>>>>
>>>>> Add a couple of temporary variables:
>>>>>
>>>>> WORKING-STORAGE SECTION.
>>>>> 01 AI PIC 9(4) DISPLAY.
>>>>> 01 BI PIC 9(4) DISPLAY.
>>>>>
>>>>> and do:
>>>>>
>>>>> MOVE A(I) TO AI
>>>>> MOVE B(I) TO BI
>>>>> DISPLAY "First[" I "]: " AI "  Second[" I "]: " BI.
>>>>>
>>>>> If anyone that actually knows Cobol has a better solution then
>>>>> I am also interested!
>>>>
>>>> I really don't have that much experience with VMS COBOL and have no
>>>> idea
>>>> what $MGBLSC means,
>>>
>>> SYS$MGLBSC is the VMS system service to map a global section.
>>>
>>>>                      but, if it is merely a display problem how about a
>>>> REDEFINES from COMP to DISPLAY instead of another variable and the
>>>> MOVE?
>>>
>>> How would that look like?
>>
>> Can you point me at a copy of the VMS COBOL Reference Manual?
>> This is something VMS specific.  I tried a couple sites.  One
>> of them returned XML errors and sector7 pointed me at localhost.
>> If I can grab a quick look at the manual I can probably provide
>> a fairly clean way to do it.  I may even try to figure out how
>> to get to EISNER after the port change and then I will actually
>> test what I write.
>>
>
> Try https://docs.vmssoftware.com/vsi-cobol-for-openvms-reference-guide
> There is also a User guide
>

Afraid I will have to take a pass on this one. Too much VMS
specific stuff that makes no sense to me in COBOL.
An example:
------------------------------
LINKAGE SECTION.

01 GLOBAL-SECTION.

-----------------------

PROCEDURE DIVISION USING GLOBAL_SECTION.

-----------------------------

Note that the names don't match. And, GLOBAL is a reserved word.

And I thought IBM COBOL was convoluted.

bill