Conference microw::acmsxp

255.0. "Tasknames with underscores or hyphens" by UTRTSC::WDEBAKKER (Feed your head) Fri Feb 28 1997 07:36

Hello,

A customer came with the following question. They're using:
OpenVMS V6.2-1H3
ACMSxp V2.1 for OpenVMS Alpha
Debugger V6.2-100
DEC COBOL V2.4-863

When we use an underscore or hyphen in a taskname, linking of a
client COBOLprogram will yield an undefined symbol:

%LINK-W-NUDFSYMS, 1 undefined symbol:
%LINK-I-UDFSYM,        TEST1_TSK
%LINK-W-USEUNDEF, undefined symbol TEST1_TSK referenced
 in psect $LINK$ offset %X00000080
 in module TEST_DRIVER file PRJ_DISK_1:[LOGISF.PROG.OBJ]TEST_DRIVER.OBJ;1

This seems to be contradictory with the STDL Encyclopedia.
Further testing revealed:
1. From the objects and maps it appears that the COBOL compiler
   transforms tasknames with hyphens into tasknames with
   underscores.
2. From the objects and maps it appears that the STDL compiler
   transforms tasknames with hyphens into tasknames with
   underscores.
3. Contrary to the STDL Encyclopedia lowercase names _are_ allowed.

In the STDL-encyclopedia (ACMSxp for OPENVMS Alpha versie 2.o) it says
  (Linking to Build a User-Written Client Program)
. Task names for tasks called from a COBOL user-written client must use
  uppercase characters and cannot  use underscores.
  page 39
  (Using COBOL COPY Files Generated by the STDL Compiler)
. Replace underscore with hyphens
  page 62
  (Compiling User-Written Client Programs)
                            If the task names contain either
   a hyphen (-) or underscore (_) character, the compilation
   generates an additional client stub for each task group for use
   by the COBOL client program. The generated client stub file
   has a name in the following format:

   task-group-name_CLI_COB.OBJ


Willem

    When compiling the task group specification, use the /cobol_copy  stdl
    command option.  This will produce a COBOL jacket routine which should
    take care of this problem.
    
    example:  stdl /cobol_copy  foo_grp.stdl
    
    /sharon

/sharon

They do use the /cobol_copy option, but still they claim that
no files are being generated.
Does this sound familiar?


Willem

It appeared to be a customer error, 
.1 was correct.

Sorry for  the confusion
Willem