Binder using Cobol85 host and Cobol74 Coms program
From
TKosfeld@21:1/5 to
All on Sun Feb 2 19:56:09 2020
Hello everybody.
I could use some help with a binder error.
Trying to bind a cobol74 coms program to a Cobol85 host I get the
following error:
AWS-ARRAY-OUT <---- THIS NEW GLOBAL VARIABLE HAS BEEN ADDED TO THE HOST
-- THIS IS A WARNING ONLY
AWS-ARRAY-OUT (02,0031) HAS BEEN CHANGED TO (02,017C)
AWS-AREA-CONVERSACIONAL (02,0032) HAS BEEN CHANGED TO (02,011A)
AWS-AREA-COMS (02,0033) HAS BEEN CHANGED TO (02,011C)
COMS-IN (02,0034) HAS BEEN CHANGED TO (02,001D)
COMS-OUT (02,0035) HAS BEEN CHANGED TO (02,0020)
SADSSUBS (02,0036) HAS BEEN CHANGED TO (02,0178)
SISTSUBS (02,0037) HAS BEEN CHANGED TO (02,0179)
DCILIBRARY (02,0038) HAS BEEN CHANGED TO (02,0083)
.DCIENTRYPOINT <---- THIS NEW GLOBAL VARIABLE HAS BEEN ADDED TO THE
HOST -- THIS IS A WARNING ONLY
.DCIENTRYPOINT (02,0039) HAS BEEN CHANGED TO (02,017D)
A STATEMENT "USE <HOST-FILE-LIBOBJECT-NAME> FOR
<SUBPROGRAM-LIBOBJECT-NAME>" IS REQUIRED <<<<<<<<<<<<<<<<<<<<<<<< .GET_DESIGNATOR_USING_NAME <---- THIS NEW GLOBAL VARIABLE HAS BEEN
ADDED TO THE HOST -- THIS IS A WARNING ONLY
.GET_DESIGNATOR_USING_NAME (02,003A) HAS BEEN CHANGED TO
(02,017E)
A STATEMENT "USE <HOST-FILE-LIBOBJECT-NAME> FOR
<SUBPROGRAM-LIBOBJECT-NAME>" IS REQUIRED <<<<<<<<<<<<<<<<<<<<<<<<
DMSTATUS (02,0002) HAS BEEN CHANGED TO (02,0008)
<SEGMENT DICTIONARY ITEM> (01,0002) HAS BEEN CHANGED TO
(01,0044) = 03 000001B00065
<SEGMENT DICTIONARY ITEM> (01,0003) HAS BEEN CHANGED TO
(01,0045) = 03 000034200066
<SEGMENT DICTIONARY ITEM> (01,0004) HAS BEEN CHANGED TO
(01,0046) = 05 0C0020440082
<SEGMENT DICTIONARY ITEM> (01,0005) HAS BEEN CHANGED TO
(01,0042) = 05 0F0000FFE028
<SEGMENT DICTIONARY ITEM> (01,0007) HAS BEEN CHANGED TO
(01,0041) = 03 000007400088
<SEGMENT DICTIONARY ITEM> (01,000A) HAS BEEN CHANGED TO
(01,0043) = 05 0F0000FFE0CE
Prindbindinfo shows the following for the Cobol74 program:
000041 H(02,0039) .DCIENTRYPOINT 000042 H(02,003A) .GET_DESIGNATOR_USING_NAME
000022 H(02,0026) AGENDA-DESIG 000023 H(02,0027) AGENDA-HOST
000011 H(02,001B) AREA-GLOBAL 000030 H(02,002E) AREAS-DO-GEMCOS
000035 H(02,0033) AWS-AREA-COMS 000034 H(02,0032) AWS-AREA-CONVERSACIONAL
000032 H(02,0030) AWS-ARRAY-IN 000033 H(02,0031) AWS-ARRAY-OUT
000026 H(02,002A) AWS-EST-ORIGEM 000031 H(02,002F) AWS-SALVA-SINC
000036 H(02,0034) COMS-IN 000037 H(02,0035) COMS-OUT
000020 H(02,0024) COMS-RESULT 000040 H(02,0038) DCILIBRARY
And for the Cobol85 host:
000324 H(02,016D) .Heap_double 000323 H(02,016C) .Heap_ebcdic
000325 H(02,016E) .Heap_hex 000319 H(02,0168) .Stack_pointer
000334 H(02,0177) .SIRW_table 000285 H(02,0145) .SUPPORT
000332 H(02,0175) $%%00 000056 H(02,004D) $%CANCEL_PROG
000054 H(02,004A) $%C85_LIB_SUPPORT 000103 H(02,0087) $%DCIENTRYPOINT
000145 H(02,00B9) $%DMEXCEPTIONNAME 000150 H(02,00BE) $%DMEXCEPTIONTEXT
000149 H(02,00BD) $%DMSTRUCTURENAME 000142 H(02,00B5) $%DMSUPPORT
000141 H(02,00B4) $%GET_DESIGNATOR_USING_NAME 000140 H(02,00B3) $%GET_NAME_USING_DESIGNATOR
I tried the following binder statement, but got a syntax error:
Use $%GET_NAME_USING_DESIGNATOR for .GET_DESIGNATOR_USING_NAME
I also tried the same for dcientrypoint.
Any help would be welcome.
I considered open a support request to Unisys, but thought that maybe
this topic could bring some life to this group.
Thanks for any help..
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)
From
TKosfeld@21:1/5 to
Paul Kimpel on Tue Feb 4 20:55:12 2020
On 2/3/2020 9:51 PM, Paul Kimpel wrote:
-------- Original Message --------
Subject: Binder using Cobol85 host and Cobol74 Coms program
From: TKosfeld <tkosfeld@gmx.net>
To:
Date: Sun Feb 02 2020 14:56:09 GMT-0800 (Pacific Standard Time)
Hello everybody.
I could use some help with a binder error.
Trying to bind a cobol74 coms program to a Cobol85 host I get the
following error:
AWS-ARRAY-OUT <---- THIS NEW GLOBAL VARIABLE HAS BEEN ADDED TO THE
HOST -- THIS IS A WARNING ONLY
AWS-ARRAY-OUT (02,0031) HAS BEEN CHANGED TO (02,017C)
AWS-AREA-CONVERSACIONAL (02,0032) HAS BEEN CHANGED TO (02,011A)
AWS-AREA-COMS (02,0033) HAS BEEN CHANGED TO (02,011C)
COMS-IN (02,0034) HAS BEEN CHANGED TO (02,001D)
COMS-OUT (02,0035) HAS BEEN CHANGED TO (02,0020)
SADSSUBS (02,0036) HAS BEEN CHANGED TO (02,0178)
SISTSUBS (02,0037) HAS BEEN CHANGED TO (02,0179)
DCILIBRARY (02,0038) HAS BEEN CHANGED TO (02,0083)
.DCIENTRYPOINT <---- THIS NEW GLOBAL VARIABLE HAS BEEN ADDED TO THE
HOST -- THIS IS A WARNING ONLY
.DCIENTRYPOINT (02,0039) HAS BEEN CHANGED TO (02,017D)
A STATEMENT "USE <HOST-FILE-LIBOBJECT-NAME> FOR
<SUBPROGRAM-LIBOBJECT-NAME>" IS REQUIRED <<<<<<<<<<<<<<<<<<<<<<<<
.GET_DESIGNATOR_USING_NAME <---- THIS NEW GLOBAL VARIABLE HAS BEEN
ADDED TO THE HOST -- THIS IS A WARNING ONLY
.GET_DESIGNATOR_USING_NAME (02,003A) HAS BEEN CHANGED TO
(02,017E)
A STATEMENT "USE <HOST-FILE-LIBOBJECT-NAME> FOR
<SUBPROGRAM-LIBOBJECT-NAME>" IS REQUIRED <<<<<<<<<<<<<<<<<<<<<<<<
DMSTATUS (02,0002) HAS BEEN CHANGED TO (02,0008)
<SEGMENT DICTIONARY ITEM> (01,0002) HAS BEEN CHANGED TO >> (01,0044) = 03 000001B00065
<SEGMENT DICTIONARY ITEM> (01,0003) HAS BEEN CHANGED TO >> (01,0045) = 03 000034200066
<SEGMENT DICTIONARY ITEM> (01,0004) HAS BEEN CHANGED TO >> (01,0046) = 05 0C0020440082
<SEGMENT DICTIONARY ITEM> (01,0005) HAS BEEN CHANGED TO >> (01,0042) = 05 0F0000FFE028
<SEGMENT DICTIONARY ITEM> (01,0007) HAS BEEN CHANGED TO >> (01,0041) = 03 000007400088
<SEGMENT DICTIONARY ITEM> (01,000A) HAS BEEN CHANGED TO >> (01,0043) = 05 0F0000FFE0CE
Prindbindinfo shows the following for the Cobol74 program:
000041 H(02,0039) .DCIENTRYPOINT
000042 H(02,003A) .GET_DESIGNATOR_USING_NAME
000022 H(02,0026) AGENDA-DESIG
000023 H(02,0027) AGENDA-HOST
000011 H(02,001B) AREA-GLOBAL
000030 H(02,002E) AREAS-DO-GEMCOS
000035 H(02,0033) AWS-AREA-COMS
000034 H(02,0032) AWS-AREA-CONVERSACIONAL
000032 H(02,0030) AWS-ARRAY-IN
000033 H(02,0031) AWS-ARRAY-OUT
000026 H(02,002A) AWS-EST-ORIGEM
000031 H(02,002F) AWS-SALVA-SINC
000036 H(02,0034) COMS-IN
000037 H(02,0035) COMS-OUT
000020 H(02,0024) COMS-RESULT
000040 H(02,0038) DCILIBRARY
And for the Cobol85 host:
000324 H(02,016D) .Heap_double
000323 H(02,016C) .Heap_ebcdic
000325 H(02,016E) .Heap_hex
000319 H(02,0168) .Stack_pointer
000334 H(02,0177) .SIRW_table
000285 H(02,0145) .SUPPORT
000332 H(02,0175) $%%00
000056 H(02,004D) $%CANCEL_PROG
000054 H(02,004A) $%C85_LIB_SUPPORT
000103 H(02,0087) $%DCIENTRYPOINT
000145 H(02,00B9) $%DMEXCEPTIONNAME
000150 H(02,00BE) $%DMEXCEPTIONTEXT
000149 H(02,00BD) $%DMSTRUCTURENAME
000142 H(02,00B5) $%DMSUPPORT
000141 H(02,00B4) $%GET_DESIGNATOR_USING_NAME
000140 H(02,00B3) $%GET_NAME_USING_DESIGNATOR
I tried the following binder statement, but got a syntax error:
Use $%GET_NAME_USING_DESIGNATOR for .GET_DESIGNATOR_USING_NAME
I also tried the same for dcientrypoint.
Any help would be welcome.
I considered open a support request to Unisys, but thought that maybe
this topic could bring some life to this group.
Thanks for any help..
I am baffled by what you are trying to accomplish with this. It appears
that you are trying to bind together two host programs, not a host with
one or more supporting routines. Can you tell us more about what you are trying to do and the relationship between these two programs? Seeing the specific declarations involved with binding (Procedure Division header, Linkage Section, Declaratives, etc.) would also be helpful.
Paul
Hi Paul.
You probably wont remember me, but I attended some of your Unite
presentations years ago.
The application in it's current version is compiled using Cobol74.
We have one host program that handles all the common functions (receive
the message from Coms, handle security, checks input data, etc).
Depending on the option passed, this host program calls a subprogram
that has the business logic (database/file access, calculations,
updates, etc).
It has been running like this forever.
I'm trying to make it Cobol85 compatible and started with the host
program. If I compile both the host and the subprogram using Cobol85
they bind just fine, but due to C85 and C74 differences I'll have to
change all the subprogram that belong to a single host at once. That
might be hard to do.
Looking at the messages again, I'm starting to think that the difference
might be dcisupport library. Cobol74 uses dcisupport and Algol for
example uses Comssupport.
Regards....
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)