This is as expected.  Enterprise COBOL V4.2 produced normal "load modules" while Enterprise COBOL V6.x produces "program objects".  A completely new structure for COBOL programs.  As for the writable static map, EC V6 does not produce one.  As for the linkage errors, are these modules coming from an old style PDS or PDSE?  EC V6 modules must reside in PDSEs since they are program objects and not load modules.

--
________________________________________________________________________________
Regards,
Thomas Dunlap   Independent Consultant   tsdun...@wowway.com   cell-614 975-4801

On 12/23/2021 12:10 PM, Steely.Mark wrote:
We are in the process of going to Cobol V6.3. We are taking our current process 
and trying to make the updates required for 6.3.

When a program is compiled the OBJECT compile option is used - which creates a 
SYSLIN file.

The SYSLIN files look completely different between the two versions.

V4.2

.ESD      ..  ..@@DOPLNK........                                        WUS10001
.END ...      ..            ....15655S7100 420021354                    WUS10002
.XSD      ..................    @@XINIT@                                WUS10003
.END ...      ..            ....15655S7100 420021354                    WUS10004
.XSD      ......................WUS110                                  WUS10005
Etc......

V6.3

.0..............................................................................
...............................................................-........WUS110..
.........................................Ø.......................Ø......C_CEESG0
Etc....

Then we take this file and execute through the PRELINK step.
The prelink program name is EDCPRLK.

This is where the problem occurs.

V4.2 - produces:

=======================================================================
|                         Writable Static Map
=======================================================================

   OFFSET    LENGTH  FILE ID  INPUT NAME

        0        20   00004   <xs_Make>
       20        20   00004   <AuInterface_LoadVehicle>
       40        20   00004   <AuInterface_LoadTrans>
       60        20   00004   <AuInterface_LoadSuspension>
       80        20   00004   <AuInterface_LoadPACE>
Etc.....


V6.3 - produces:

========================================================================
|                         Writable Static Map                          |
========================================================================

INFORMATIONAL EDC4013: No map displayed as no writable static was found.


I found one mention that the pre-link  step is not needed for V6.3

Then when the link step is executed the following messages are seen:

V6.3
IEW2456E 9207 SYMBOL AuInterface_Create UNRESOLVED.  MEMBER COULD NOT BE 
INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL xs_Make UNRESOLVED.  MEMBER COULD NOT BE INCLUDED FROM THE 
DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL AuInterface_LoadPolicy UNRESOLVED.  MEMBER COULD NOT BE 
INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL AuInterface_LoadPolicyCodes UNRESOLVED.  MEMBER COULD NOT 
BE INCLUDED FROM THE DESIGNATED CALL
          LIBRARY.


V4.2 - link is successful.

Is there a different process for v6.3 programs.

Any help would be appreciated.

Thank You




*** Disclaimer ***
This communication (including all attachments) is solely for the use of the 
person to whom it is addressed and is a confidential AAA communication. If you 
are not the intended recipient, any use, distribution, printing, or copying is 
prohibited. If you received this email in error, please immediately delete it 
and notify the sender.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to