Customer is using RBD 9.1.1 to generate VG-migrated program to z/OS CICS 5.1.   

There is a  link error  caused by  COBOL statement :  call "ELARSTWA"  ......  .

I can't find out ELARSTWA in Rational COBOL RT SELALMD .   Does it mean  

a PTF is required ?   

Hi Chao,

I didn't find ELARSTWA in SELALMD library too.

The statement call "ELARSTWA" was generated by EGL or VAG or writing by developer ?

By EGL.

           MOVE EIBFN TO EZEAPP-ENTRY-FUNCTION           EXEC CICS IGNORE CONDITION ERROR END-EXEC           CALL "ELARSTWA" USING DFHEIBLK                                 DFHCOMMAREA (1: EIBCALEN)                                 EZEAPP-PROFILE           SET ADDRESS OF EZERTS-CONTROL-BLOCK TO EZEAPP-RTS-PTR           EXEC CICS HANDLE ABEND LABEL(EZECONTROLLABEL) END-EXEC

. 

If I am correct the ELARSTWA module is embedded within the linkedit module ELARSINC, look:

  SECTION    CLASS                                      ------- SOURCE --------
               198  ELARSINC           CSECT       800  SELALMD   01  ELARSINC
       1C      1B4     ELARSTWA           LABEL
       22      1BA     ELARSINT           LABEL
       28      1C0     ELAASTRM           LABEL

Look if your sysprint of the linkedit to the program has the include cards below:

IEW2322I 1220 1

IEW2322I 1220 2 INCLUDE OBJLIB(program_name)

IEW2322I 1220 3 INCLUDE SELALMD(ELARSINC)

IEW2322I 1220 4 INCLUDE SYSLIB(DFHEAI,DSNCLI)

Hsieh is correct in that ELARSTWA is part of the ELARSINC module. This module is included by the EGL-generated LED deck, that gets created when an EGL programs is generated for CICS. 

I suspect that there is something wrong with how the linkedit is occurring. Were the FDA* members for the build server changed? Is the RBD build server being used?

What would be of interest is the listing from the linkedit.

Hi,

The following message is returned in the linkedit step.    

IEW2456E SYMBOL ELARSTWA UNSOLVED. 

There are many IEW2456E instances in Google search, but no ELARSTWA instance. 

Any  experience/comments for sharing.   

That is because the link edit isn't correctly finding the ELARSINC module. Can you provide the linkedit listing?

You can also attach the generation output file .LED and the pseudo-JCL FDA this.

L.H.,

It sounds like it is correct, but you should make sure the compile option NODYNAM is being used on the COBOL compile.  

take care.

Mark

I checked FDAPTCL  ( in SYS1.PROCLIB)  to confirm   NODYNAM is used in compile step.  

The generated .LED file is below.  linkedit output file is attached. 

INCLUDE OBJLIB(SZIACBR)INCLUDE SELALMD(ELARSINC)INCLUDE SYSLIB(DFHEAI,DSNCLI)NAME SZIACBR(R)

L.H.,

The LED file looks correct and matches what I get when I generate.  However, the output does not look correct in the linkedit step and it looks like they are including ELARSINT instead of ELARSINC.    ELARSINT is used for batch/non-CICS translated programs.    It actually looks like that there are no include cards being used by the linkage editor or that output has been suppressed. .   I have attached an example link edit listing from a CICS (non-DB2) program that I generated/built.

Can you check and see if the FDAPTCL has been changed such that the link edit info is not being processed correctly or passed to the link edit step? 

The specific things to look for is how the SYSLIN is being provided (see copied text below). .  For example, did you need or did they change upload the led to a PDS in the UPLOAD step,  but not change the linkedit step?  Are they using their own build process that does not use the generated .led file.  Given you did not send a <pgmname>.L.SYSPRINT, I am wondering if they are using their own compile/link processing instead of the build scripts.

From the UPLOAD step (LED file processing is commented out by default):

//UPLOAD EXEC PGM=IEFBR14                                               
//* UPLOAD CICS PPT ENTRIES FROM CLIENT (&MBR.PPT)                      
//EZEPPT   DD  DSN=&CGHLQ..&SYSTEM..EZEPPT,DISP=SHR,CCUEXT=PPT          
//EZEPCT   DD  DSN=&CGHLQ..&SYSTEM..EZEPCT,DISP=SHR,CCUEXT=PCT          
//X1  IF &EZEDESTDIR..NE.NONE                                           
//MYXML  DD HFSPATH=&EZEDESTDIR,CCUEXT=(WSBIND,WSDL)                    
//X1 ENDIF                                                              
//*UNCOMMENT IF COBOL SOURCE AND LINK EDIT CMDS SHOULD BE SAVED         
//*EZESRC   DD  DSN=&CGHLQ..&SYSTEM..EZESRC,DISP=SHR,CCUEXT=CBL         
//*EZELED   DD  DSN=&CGHLQ..&SYSTEM..EZELED,DISP=SHR,CCUEXT=LED        

In the Link step from my FDAPTCL (does NOT use PDS)

//L        EXEC PGM=IEWL,COND=(5,LT,C),REGION=&RGN,              
//     PARM='RENT,REUS,LIST,XREF,MAP,AMODE(&AMODE),RMODE(&RMODE)'
//SYSLIB   DD  DISP=SHR,DSN=&DFHLOAD                             
//         DD  DISP=SHR,DSN=&COBCICS                             
//         DD  DISP=SHR,DSN=&COBLIB                              
//         DD  DISP=SHR,DSN=&DSNLOAD                             
//SELALMD  DD  DISP=SHR,DSN=&ELA..SELALMD                        
//OBJLIB   DD  DISP=SHR,DSN=&CGHLQ..&SYSTEM..OBJECT              
//* LINK EDIT CONTROL FILE UPLOADED FROM CLIENT (&MBR.LED)       
//*SYSLIN    DD  DISP=SHR,DSN=&CGHLQ..&SYSTEM..EZELED(&MBR)      
//SYSLIN    DD  CCUEXT=LED,DISP=(NEW,DELETE),                    
//    UNIT=SYSDA,SPACE=(TRK,(10,10)),                            
//    DCB=(RECFM=FB,LRECL=80,BLKSIZE=3200)