COBOL LE Runtime Environment Problem
Select messages from
# through # FAQ
[/[Print]\]

MVSFORUMS.com -> Application Programming

#1: COBOL LE Runtime Environment Problem Author: shiv_swami PostPosted: Mon May 23, 2005 11:53 am
    —
We are looking at upgrading COBOL to LE, The initial testing for one of the jobs with LE run-envirnment failed with RC OF U4038

Code:
IEA995I SYMPTOM DUMP OUTPUT  349                                   
  USER COMPLETION CODE=4039 REASON CODE=00000000                   
 TIME=09.12.52  SEQ=00543  CPU=0000  ASID=013E                     
 PSW AT TIME OF ERROR  078D1000   9332D2EE  ILC 2  INTC 0D         
   ACTIVE LOAD MODULE           ADDRESS=132171E0  OFFSET=0011610E 
   NAME=CEEPLPKA                                                   
   DATA AT PSW  1332D2E8 - 00181610  0A0D58D0  D00498EC           
   AR/GR 0: 80B99B60/84000000   1: 00000000/84000FC7               
         2: 00000000/0002DF80   3: 00000000/00000002               
         4: 00000000/0002DF80   5: 00000000/00000718               
         6: 00000000/13212888   7: 00000000/00000010               
         8: 00000000/932A7068   9: 00000000/0002E6CF               
         A: 00000000/0002DB14   B: 00000000/1332D218               
         C: 00000000/00027A50   D: 00000000/00030268               
         E: 00000000/932A71A8   F: 00000000/00000000               
 END OF SYMPTOM DUMP                                               

Reason of abend as seen in sysout was :-

Code:
 IGZ0035S There was an unsuccessful OPEN or CLOSE of file REJSUMM in program PMPBIRBC at relative location X'1F40'.
          Neither FILE STATUS nor an ERROR declarative were specified. The status code was 96.       
          From compile unit PMPBIRBC at entry point PMPBIRBC at compile unit offset +00001F40 at entry offset +00001F40
          at address 000090C8.   


The file REJSUMM is defined in cobol program but not opened or closed. There is no corresponding DD statement in the JCL for job.
We have lot of similar old programs with files defined in COBOL but unreferenced in JCLs.Is there a way to put a FIX or something in LE Runtime for allowing status code of 96 ?
The other cumbersome option would be to put DD Dummy statement for all such unreferenced files.

#2:  Author: kolusuLocation: San Jose PostPosted: Mon May 23, 2005 12:24 pm
    —
shiv_swami,

I guess Your site had the CBLQDA OFF. CBLQDA(ON) is the setting that dynallocs a file when an output DD name is opened but missing from the TIOT. This can cause error when a programmer mis-spells the ddname in his JCL. The output file will be empty as the CLQDA setting had dynamically allocated the correct DDname and deleted after the completion of the job(default disp parameter =(new,delete,delete))

You can change this setting in the linklist copy of CEEDOPTS (the table of installation Default OPTionS).

Run your pgm with the following parm and CEEDOPT DD and check the LE default setting.

Code:

//STEP0100 EXEC PGM=YOUR COBOL PGM,,PARM='/RPTOPTS(ON),MSGFILE(CEEDOPT)'
//CEEDOPT  DD SYSOUT=*


If CBLQDA is turned off then you can override it via parm.

Code:

//STEP0100 EXEC PGM=YOUR COBOL PGM,PARM='/CBLQDA(ON)'


Hope this helps...

Cheers

kolusu

#3:  Author: shiv_swami PostPosted: Mon May 23, 2005 4:37 pm
    —
Hi Kolusu,

Thanks very much for quick response. Now I understand that the QSAM files could be handled by defaulting the dynamic allocation to ON. What would happen to VSAM files that are unreferenced. Is there a separate option Dynamic allocation of VSAM files ?
Could you also give some pointers to documentation/experiences for migration to LE from OS/VS COBOL and COBOL II environment.
I have already downloaded a few manuals from
http://www-1.ibm.com/servers/eserver/zseries/zos/le/

#4:  Author: kolusuLocation: San Jose PostPosted: Mon May 23, 2005 8:04 pm
    —
Shiv_swami,

Quote:

Is there a separate option Dynamic allocation of VSAM files ?


hmm the COBOL routine for OPEN of a VSAM file is IGZEVOC but I am not sure about the dynamic allocation. Sorry.

Quote:

Could you also give some pointers to documentation/experiences for migration to LE from OS/VS COBOL and COBOL II environment.


You should be looking at cobol runtime migration guides

COBOL for OS/390 & VM V2R1 - COBOL for MVS & VM V1R2 Compiler and Run-Time Migration Guide

Hope this helps...

Cheers

Kolusu



MVSFORUMS.com -> Application Programming


output generated using printer-friendly topic mod. All times are GMT - 5 Hours

Page 1 of 1

Powered by phpBB © 2001, 2005 phpBB Group