Hi Prino,
Thank you very much for starting CICS. I am happily working on it.
However, I am facing one small issue. My transactions are working fine for the first time. But, from the second time on wards, junk data is getting passed to the screen while sending the map and PROG753 is getting displayed in the status bar. I tried by initializing all the map variables and other variables used in my program, but to no avail. Then I googled on the issue and came up with a possible cause.
Type CLER on the CICS screen and press PF5 and then keep pressing PF8 until you see the STORAGE parameter on the Runtime OPTIONS column. Refer below screenprint:
CLER PAGE 4 OF 5
Language Environment Region Level Runtime Options.
Current Settings
LAST WHERE SET OPTIONS
-------------------- -------------------------------------------------------
Installation default PRTUNIT(6)
Installation default PUNUNIT(7)
Installation default RDRUNIT(5)
Installation default RECPAD(OFF)
Installation default RPTOPTS(OFF)
CICS CLER Trans RPTSTG(OFF)
Installation default NORTEREUS
Installation default NOSIMVRD
Installation default STACK(4096,4080,ANYWHERE,KEEP,4096,4080)
Installation default STORAGE(NONE,NONE,NONE,0)
Installation default TERMTHDACT(TRACE,CESE,96)
Installation default NOTEST(ALL,"*","PROMPT","INSPPREF")
PF: 1=Help 3=Quit 7=Back 8=Forward 10=RPT->CES
The STORAGE parameter for CICS with COBOL programs needs to be STORAGE=(00,NONE,NONE,0K) for the program to flush all junk data. Further investigation revealed that a job to update the runtime options for COBOL and LE for CICS can be found in library CEE.SCEESAMP. The options source itself is member CEECOPT, and the job to update it is in CEEWCOPT. I do not have the authorization to edit or submit these jobs. Do we need to submit this job(after making the necessary changes, of course)? Or, can this be taken care of during the next planned startup of CICS? Or, can other methods be used(Please refer http://cicswiki.org/cicswiki1/index.php?title=How_do_I_set_or_change_LE_runtime_options%3F)? Or, is there a simple solution for this problem?
Can you please spend some of your expertise on this issue and suggest a solution? Thanks in advance.
Regards,
Prabakaran(Mainframe userid: JDSP).