Topic
6 replies Latest Post - ‏2009-09-23T21:49:46Z by jentek
jentek
jentek
29 Posts
ACCEPTED ANSWER

Pinned topic CSSF problem

‏2009-09-22T22:16:37Z |
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
User Start
ATI Start
Internal ATI Start
Triggered Start

Should we change it to "Any Facility" and "Any Start Type"?
All terminals are autoinstalled.
Thanks
Steve
Updated on 2009-09-23T21:49:46Z at 2009-09-23T21:49:46Z by jentek
  • SystemAdmin
    SystemAdmin
    308 Posts
    ACCEPTED ANSWER

    Re: CSSF problem

    ‏2009-09-23T05:13:53Z  in response to jentek
    Steve,

    As I see, the default invocation mode for CSSF transaction is:
    
    in_out_terminal|any_start|at_normal_running|at_shutdown_start
    


    Looks like you have changed the above default values. Any reason for doing that?. Do you get this problem with the default values?

    Cheers,
    Hari
    • jentek
      jentek
      29 Posts
      ACCEPTED ANSWER

      Re: CSSF problem

      ‏2009-09-23T16:48:16Z  in response to SystemAdmin
      Hi 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?
  • SystemAdmin
    SystemAdmin
    308 Posts
    ACCEPTED ANSWER

    Re: CSSF problem

    ‏2009-09-23T18:44:09Z  in response to jentek
    Steve,
    Do you observe CHAT transaction failures in the console just before these CSSF failures ?
    regards,
    -manju
    • jentek
      jentek
      29 Posts
      ACCEPTED ANSWER

      Re: CSSF problem

      ‏2009-09-23T19:04:52Z  in response to SystemAdmin
      Yes I did, it's ERZ014016E .... Transaction 'CHAT', Abend 'A11A', at '????'.

      Abend A11A is "The terminal autoinstall was unsuccessful"

      But no other clues.
  • SystemAdmin
    SystemAdmin
    308 Posts
    ACCEPTED ANSWER

    Re: CSSF problem

    ‏2009-09-23T19:13:15Z  in response to jentek
    Steve,
    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.

    regards,
    -manju
    • jentek
      jentek
      29 Posts
      ACCEPTED ANSWER

      Re: CSSF problem

      ‏2009-09-23T21:49:46Z  in response to SystemAdmin
      Thanks Manju

      We do have the feature turned on that generates an alternate termid if the requested one is in use.

      steve