[Info-vax] COBOL example $MGBLSC
Arne Vajhøj
arne at vajhoej.dk
Sat Sep 9 13:42:55 EDT 2023
On 9/9/2023 9:15 AM, bill wrote:
> 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:
>>>>> 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.
I think there are 3 parts of this:
A) how to call VMS system service SYS$MGBLSC
B) how to use returned address for Cobol data, which is where the
routine call somes in
C) how to display a comp
A and B are settled.
So you can focus on C.
Arne
More information about the Info-vax
mailing list