CICS does not like COBOL programs

CICS does not like COBOL programs

Post by Markus B?rtsch » Thu, 28 Jun 2001 22:13:37



We are in the process of moving some MVS CICS apps to an AIX box. We've
set up the CICS there and so far everything seems working. We were able
to compile and run the 'C' samples from the Manual, for example.

But it seems to be impossible to get a COBOL program working. All
programs we tried compile and link fine (using cicstcl) and the IBM
COBOL Set compiler.

Environment:                                                          
- AIX 4.3.3 ML07.                                                      
- CICS 4.3.0.4                                                        
- IBM Cobol 1.1.1.7                                                    
- DB2 V7.1                                                            
- CICS is defined with DB2 as file store and RPC-only.                

Example:                                                              

       IDENTIFICATION DIVISION.                            ELID004                                                                
       PROGRAM-ID.  COCO.                                  ELID008                                                                
       ENVIRONMENT DIVISION.                               ELID018                                                                
       CONFIGURATION SECTION.                              ELID020                                                                
       DATA DIVISION.                                      ELID027                                                                
       WORKING-STORAGE SECTION.                            ELID031                                                                
       77  HELLO PIC X(20) VALUE 'Hello from COBOL !'.     ELIF009                                                                
       COPY DFHBMSCA.                                                  
       COPY DFHAID.                                                    
       PROCEDURE DIVISION.                                 ELIG051                                                                
           EXEC CICS SEND TEXT FROM(HELLO) LENGTH(20)      ELIG058                                                                
           END-EXEC.                                       ELIG153                                                                
           STOP RUN.                                                  


ERZ004047I/9005: Running the translation step: 'cicstran -lIBMCOB -s -e
-d -qAPOST COCO.ccp'                                                  
ERZ004060I/5015: cicstran translation ended: 0 error(s), 0 warning(s).
ERZ004049I/0096: Running the compile and link step: 'cob2_r -qLIB -bI:/u
sr/lpp/cics/lib/cicsprIBMCOB.exp -e _iwz_cobol_main -L/usr/lib/dce -ldce
libc_r -ldcepthreads -qAPOST -g -qlist,map -o COCO.ibmcob COCO.cbl'    
PP 5765-548 IBM COBOL Set for AIX       1.1   in progress ...          
End of compilation 1,  program COCO,  no statements flagged.          


/home/maba/cics_cobol                                                  


PathName="/home/maba/cics_cobol/COCO.ibmcob" RSLKey=1                                                    


# now we call the 'COCO' transaction and get an ASRA Abend            

Look at the logfiles:                                                  

IWZ995C  SIGSEGV signal received while executing code at location
0xd00bafd8.
IWZ901S  Program exits due to severe or critical error.
ERZ014016E/0028 06/26/01 19:24:15 acc2aix  TX2R: Transaction 'RTBA',
Abend 'ASRA', at 'TX2R'.


ERZ015028W/0154 06/26/01 19:24:15 acc2aix  BT7A: Exception in user
application code - exception string is: 'pthread_cancel_e'                  
ERZ016050W/0234 06/26/01 19:24:15 acc2aix  BT7A: Logical unit of work
for transaction 'COCO' has been backed out; Distributed Transaction
Service (TRAN) reason 'ENC-tra-1025: A client (not the transaction
service) aborted'                                                                

What do we have to du to get our cobol program to work ?

--
  Markus Baertschi
  Bas du Ross 14b
  CH-1163, Etoy, Switzerland

 
 
 

CICS does not like COBOL programs

Post by Philip Morte » Fri, 29 Jun 2001 20:05:02


[ stuff snipped ]


> PathName="/home/maba/cics_cobol/COCO.ibmcob" RSLKey=1

This should be:

 PathName="/home/maba/cics_cobol/COCO" RSLKey=1

that is to say,  you should omit the extension.

See the CICS Admin Ref under PD entries:

For programs written in a language other than Java, the filename
specified in the PathName attribute must not  contain an extension. For
programs written in Java, the filename must include the .class suffix.
CICS searches for  the program file based on its installed extension in
the following orders:

          On CICS for Open Systems when Micro Focus COBOL Animator is
not used (not all languages are
          available on all operating systems):

             1.C program files (no extension)

             2.IBM COBOL files (with extension .ibmcob)

Philip Morten

 
 
 

CICS does not like COBOL programs

Post by Philip Morte » Tue, 24 Jul 2001 18:32:42




> PathName="/home/maba/cics_cobol/COCO.ibmcob" RSLKey=1

Try it without the extension on the PathName, that is:

$ cicsadd -c pd COCO PathName="/home/maba/cics_cobol/COCO" RSLKey=1

See the following from the Administration Guide under PD definition:

----------------------------------------------------------------------------------------------------
For programs written in a language other than Java, the filename
specified in the PathName attribute
must not contain an extension. For programs written in Java, the
filename must include the .class
suffix. CICS searches for the program file based on its installed
extension in the following orders:

     On CICS for Open Systems when Micro Focus COBOL Animator is not
used (not all languages
     are available on all operating systems):

        1.C program files (no extension)

        2.IBM COBOL files (with extension .ibmcob)

        3.Micro Focus COBOL native code files (with extension .gnt)

        4.Micro Focus COBOL intermediate code files (with extension
.int)

        5.IBM PL/I files (with extension .ibmpli)

        6.IBM C++ files (with extension .ibmcpp)
----------------------------------------------------------------------------------------------------

Philip Morten

 
 
 

1. Cobol/CICS migration to Unix/Unikix

Posting for a friend:

We are involved in a migration project for a Cobol/CICS application, running
now on an IBM mainframe under VM VSE/ESA environment, to Unix.  To do that
we are evaluating a Sequent machine with Unikix.

Does anyone have experience doing this kind of of migration, that you
are willing to share with us?

We would like to know about problems that we may encounter during the
migration process, perfomance issues of the application running on Unix, and
anything you find interesting to mention.

Please e-mail to:


Thank you in advance.
---------------------------------------------------------------------------
Adriana Goic B.                                    Computer Division

---------------------------------------------------------------------------
Adriana Goic B.                                    Fundacion Chile

2. Ipchains

3. Distributed CICS (formerly CICS/6000)???

4. apache...srm.conf->new directoryindex

5. Help-PC likes linux so much won't run DOS

6. Oracle 8i Installation

7. Mouse Likes DOS but hates Linux

8. VMWARE installation

9. Newbie: Likes to learn to write GUI programs in X11

10. CICS: Can not define file schema

11. mountd not liking /etc/exports in 2.8, 3.0

12. Look likes iproute2 does not work properly.

13. VGA Graphics Programming Under Linux Not DOS