MQSeries.net :: View topic

Bear · Posted: Mon Sep 30, 2013 7:25 am Post subject:

Have downloaded and "successfully" installed TX Beta 8.1 on Windows Server 2008.
When trying to invoke a CICS Terminal a 3270 style screen appears but unable to enter data. Region ID appears with Terminal ID.
Have successfully had TX working on other platforms but not Windows. All seems fine in other respects, e.g. the Admin Console is OK, so too is the sfs_server by all indications.
In the Windows Event Viewer I see an error 'Event ID 5555 from source CICSTS' frequently. Following is a text of the error.

Log Name: Application
Source: CICSTS
Date: 30/09/2013 10:29:48 AM
Event ID: 5555
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: WinServer
Description:
The description for Event ID 5555 from source CICSTS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ERZ096059E/0089: The cicscp command was incorrect.

the message resource is present but the message is not found in the string/message table

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="CICSTS" />
<EventID Qualifiers="49152">5555</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-09-30T14:29:48.000000000Z" />
<EventRecordID>32344</EventRecordID>
<Channel>Application</Channel>
<Computer>WinServer</Computer>
<Security />
</System>
<EventData>
<Data>ERZ096059E/0089: The cicscp command was incorrect.</Data>
</EventData>
</Event>

Have been on to many blogs and IBM sites looking for a solution. None forthcoming. Nothing even close that resembles this error. I have looked to the possibility of corruption of the code but no proof of that I can see.

I had the exact same problem with TX V7.1, went to V8.1 with the hope that it may circumvent the issue but no such luck. Anyone with a glimmer of hope as to what could be the issue would certainly be welcomed. BB.
_________________
Software Specialist