MVSFORUMS.com

NicolasF · Posted: Tue May 15, 2007 7:21 pm Post subject: Problem starting CICS

I'm getting this message when I want to start CICS. Does anyone have any idea how I can fix this??

*21.17.02 STC00220 *02 DFHPA1909 CICS DATA 216
* ht IS INVALID FOR KEYWORD CICSSVC=. RESPECIFY KEYWORD AND DATA.

It's driving me nuts! Sad

warp5 · Posted: Wed May 16, 2007 12:56 am Post subject:

Take a look at your CICS parameters, either sysin, overrides, or SIT. What do you have for CICSSVC? We use CICSSVC=216. Have you looked at the error messages for explanations?

Problem
You are starting a new CICS

NicolasF · Posted: Wed May 16, 2007 10:32 am Post subject:

This is my config in the member IEASVCCI of the PARMLIB:

SVCPARM 216,REPLACE,TYPE(3),APF(NO),EPNAME(DFHCSVC) /* CICS SVC */

This is the SYSIN of the CICS:

CICS Guy · Intermediate Joined: 30 Apr 2007 Posts: 292 Topics: 3

NicolasF · Posted: Wed May 16, 2007 4:07 pm Post subject:

OK, so... how can I check If the SVC number does correspond to the correct level of DFHCSVC?? or how can I try a different number...??

CICS Guy · Intermediate Joined: 30 Apr 2007 Posts: 292 Topics: 3

Dealing with multiple releases of CICS?

NicolasF · Posted: Wed May 16, 2007 10:26 pm Post subject:

Nope, it just stopped working. The thing is that I'm not the CICS specialist, so I don't have much experience with it... Rolling Eyes

CICS Guy · Intermediate Joined: 30 Apr 2007 Posts: 292 Topics: 3

Somebody did something, it didn't "just stop" working. The error message is telling you why, somebody there now has to resolve the how....

shagnwrx · Posted: Thu May 17, 2007 4:20 pm Post subject:

Nicolas,

Can you paste in the DFHSITxx contents here? xx would equal the suffix specified on the SIT= parameter of your start command, sysin, or hardcoded in the JCL proc itself.

Could be any number of things at this point from LPA being switched, switching of CICS libraries in the LPA, erroneously using a different DFHSIT module than from before, or even somebody changing the SVC number in the IEASYSxx member of parmlib for the DFHCSVC entry.

I'm with CICS Guy on this.. Sounds like the Sys Progs may have been staging for a new release of CICS, and fudged the LPA list (Not that I've done anything like that before Embarassed

)
_________________
SCCA South East Division RallyCross

NicolasF · Posted: Fri May 18, 2007 10:26 am Post subject:

OK, we fixed it, apparently someone issued some kind of "SET" command and modified the LPA list. So we did a cold start and reloaded the CICS LPA modules and now it work Very Happy

. Thanks for the help!