We get these console messages quite a lot in our CICS-TX v6.1 system on AIX v5.3 :-
ERZ045003E.... A transaction ('CSSF') attempted to start with an invalid StartType/FacilityType combination
ERZ014028E.... Transaction 'CSSF' was unsuccessful in the invocation mode check and could not be started.
ERZ014016E.... Transaction 'CSSF', Abend 'A146', at '????'.
The CSSF transaction context is defined as :-
In or Out Terminal
Internal ATI Start
Should we change it to "Any Facility" and "Any Start Type"?
All terminals are autoinstalled.
This topic has been locked.
6 replies Latest Post - 2009-09-23T21:49:46Z by jentek
Pinned topic CSSF problem
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2009-09-23T21:49:46Z at 2009-09-23T21:49:46Z by jentek
Re: CSSF problem2009-09-23T05:13:53Z in response to jentekSteve,
As I see, the default invocation mode for CSSF transaction is:
Looks like you have changed the above default values. Any reason for doing that?. Do you get this problem with the default values?
Re: CSSF problem2009-09-23T16:48:16Z in response to SystemAdminHi Hari,
I didn't post the "Valid Run States" but they are "at_normal_running|at_shutdown_start"
And checking my values in the web admin screen with yours, they appear to be the same, because Any_Start is the same as User|ATI|Triggered|Internal.
I don't think we changed anything in that area from the supplied transaction, but maybe in the security fields. My security values are "Private, 1, None, Internal" in the web screen.
hmmm, should that be Public?
Re: CSSF problem2009-09-23T19:13:15Z in response to jentekSteve,
You should approach IBM support for this.
Till then, if you can prevent CHAT failures, it should address CSSF abends.
CHAT can fail if the terminal with same termid is already installed.