NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
3 replies Latest Post - 2012-03-29T23:27:27Z by JohnTilling
Pinned topic CICS Explorer reporting insufficient CSDSTRNO.
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
I am trying to use the CICS Explorer to view the CSD definitions into CICS TS 4.2. It is ending with a CNX00591E: EXEC CICS command(CSD STARTBRGROUP) RESP(CSDERR) RESP2(5). And this error withing the MSGUSR log in the region: ...CONL Unable to perform request - The CSDSTRNO operand in the System Initialization Table(SIT) is too small. I have increased CSDSTRNO TO 254 without getting it to work. I have also successfully done a CECI STARTBRGROUP with no errors. What can I try so that the Explorer will display correctly. BTW, I have used the Explorer to define an new object in the CSD. Thank you.
Updated on 2012-03-29T23:27:27Z at 2012-03-29T23:27:27Z by JohnTilling
isocics 060001JCV412 PostsACCEPTED ANSWER
Re: CICS Explorer reporting insufficient CSDSTRNO.2012-03-29T11:38:18Z in response to isocicsThe CSDSTRNO parameter does not take effect unless the region is started COLD or INITIAL. So I issued a CECI EXEC CICS SET FILE(DFHCSD) STRINGS(24) and the EXPLORER started to work. Interesting that this particular parameter cannot be overrid without a COLD start but the value of CSDSTRNO is taken from the global catalog. Issued solved.
SystemAdmin 110000D4XK124 PostsACCEPTED ANSWER
Re: CICS Explorer reporting insufficient CSDSTRNO.2012-03-29T11:59:26Z in response to isocicsHi
Glad you got your problem sorted out. I thought I best check our documentation just incase there was something missing regarding CSDSTRNO but it looks like this has the following statement:
This parameter is effective only on a CICS cold or initial start. On a warm or emergency restart, file resource definitions for the CSD are recovered from the global catalog. However, you can redefine the number of strings for the CSD dynamically with an EXEC CICS SET FILE command.
I would assume this has something to do with the way that the CSD is processed during the startup of a CICS region and its very early in processing, but I'm not sure of the finer details.
Good one to know for the future.
JohnTilling 120000GQ997 PostsACCEPTED ANSWER
Re: CICS Explorer reporting insufficient CSDSTRNO.2012-03-29T23:27:27Z in response to isocicsHi,
Yes, the only reason the CSD parameters are in the SIT is because you can't RDO define the CSD file because RDO needs uses the CSD file! Hence these SIT parameters are the equivalent of RDO defining the CSD file. With RDO the definition from the CSD is only used on a cold or initial start. On a warm or emergency start the definition is recovered from a catalog, hence the same applies to these SIT parms for the CSD, they only apply on cold or initial starts.