Skip to main content

Transaction Processing Facility (TPF) - Online Maintenance TPF Online Maintenance TPF Online Maintenance Skip to: Abstract | Comments | Solution | Related Segments | Migration | Download

SUBJECT:         APAR  NUMBER: PJ27361 
 
REFERENCE:  AREA:     ISO-C SUPPORT 
            SEGMENT:  CEESG00340 - RELEASE:  TPF4  (ObjOnly) 
            SEGMENT:  CSTRTL40   - RELEASE:  TPF4  (Assembler) 
 
 
Pre-requisite APARs are: 
FOR SEGMENT CEESG00340 (ObjOnly)   - REL TPF4 
 PJ24472  PJ25084  PJ26377  
FOR SEGMENT CSTRTL40   (Assembler) - REL TPF4 
 PJ17852  PJ21167  PJ21907  PJ24472  
 PJ24528  PJ25084  PJ25632  
 PJ25807  PJ25981  PJ26218  PJ26502  
 PJ26468  PJ26757  PJ27254  
To be applied in the order listed for each segment. 

ABSTRACT OF PROBLEM 
___________________ 
Because  of APARs PJ26377 and PJ26757, unresolved references for 
memcmp, strncat, strncmp, and strncpy functions may occur during 
prelinking and linking TPF modules. 
 

COMMENTS ON PROBLEM 
___________________ 
Unresolved references for memcmp, strncat, strncmp, and  strncpy 
functions  may  occur during prelinking and linking TPF modules. 
This happens when the CSTRTL startup program  and  the  CEESG003 
special stub are assembled with the NOBATCH assembler option. 
  APARs PJ26377 and PJ26757 added code to these startup programs 
to  correct  unresolved references for memcmp, strncat, strncmp, 
and strncpy functions when prelinking and  linking  TPF  modules 
that  were  compiled  with OPT(0) using the OS/390 V2R6 or later 
compiler. 
  The APARs created multiple assembler programs for each startup 
program (multiple END cards).  This requires the BATCH assembler 
option.  Unresolved references still occur when the startup pro- 
grams are compiled with the NOBATCH option. 
 

SOLUTION 
________ 
  Removed the multiple END cards in CSTRTL startup code. 
  Removed the multiple END cards in the CEESG003 special stub. 
  CSTRTL and CEESG003 now have one END card each.  The  customer 
can assemble CSTRTL using the BATCH or NOBATCH option.  CEESG003 
is  an  object-code-only  special stub used by CSTRTD and CSTDLL 
startup code. 
 
DEPENDENCIES 
____________ 
 
Related Segments Affected By This APAR. 
_______________________________________ 
 
Segments to be assembled or compiled: 
 
Segments to be link edited: 
 
Load Modules to be loaded: 
 
Migration Considerations 
======================== 
As follows 
CEESG003 is an object-code-only special stub object module. 
The object module should be placed in the ACP.STUB.REL40 data set. 
 
If CEESG003 is in ACP.CLIB.REL40 data set, delete CEESG003 from this 
data set.  CEESG003 should only be in ACP.STUB.REL40 data set. 
 
TPF assembled APAR PJ26757's CEESG003 object-code-only special stub 
object module using the BATCH assembler option. 
Customers will not see any unresolved references when linking 
DLMs and DLLs with APAR PJ26757's CEESG003 stub object module. 
Therefore, customers do not need to relink DLMs and DLLs using 
APAR PJ27361's CEESG003 stub object module. 
 
 
BUILD/TEST INSTRUCTIONS 
_______________________ 
 
 ===BUILD Instructions=== 
 
CEESG003 is one of the special stubs.  It is not really a  stub, 
but the object must be placed in the stub data set.  For TPF the 
object  should go into the ACP.STUB.INTGVP40 stub data set.  The 
customer's version of this stub data set is  the  ACP.STUB.REL40 
data set. 
 
Stubs to be built: 
 
 ===TEST Instructions=== 
 
No special test instructions. 
 
-- END APAR PJ27361 
 
 
 



Download file(s): Login once to access server, leave window open, then click on link(s) below. Source Binary