XCOMM1610I Control Center Connection Rejected with CA XCOM for z/OS
Article ID: 202318
Updated On:
Products
Issue/Introduction
Before applying SO15969 CONTROL CENTER ACCESS DENIED (XCOMM1613E) WITH SECURITY=NONE and SO14571 ABEND S0C4 AT XCOMHTTP+7CE DURING PORT SCANS attacks by Qualys servers would interfere with transfers and STC would need to be recycled.
After maintenance, attacks do not interfere with transfers, but now the attacks are getting message about Command Center rejections: This is occurring on all LPAR's where the Command Center has been implemented.
XCOMM0805I TCP/IP CONNECTION ENDED WITH IP=10.162.16.39
HTTP XCOMM1610I Control Center Connection Rejected - GET / HTTP/1.0
XCOMM0780E Txpi 228: Select exception condition for socket 0
XCOMM0780E Txpi 215: Socket send error return value = 140
XCOMM0805I TCP/IP CONNECTION ENDED WITH IP=10.162.16.39
HTTP XCOMM1610I Control Center Connection Rejected - GET /console/login
XCOMM1610I Control Center Connection Established
XCOMM1611I User nnnnn authorized to use the Control Center
XCOMM1610I Control Center Connection Established
Since there are different servers attacking each day, there is no way to prevent this via Internet Protocol Security IPsec.
Is there a way to officially logoff the Command Center, because when entering the URL it reconnected me w/o password verification.
Environment
Release : 12.0
Component : CA XCOM Data Transport for z/OS
Cause
XCOM may need a larger region size
Resolution
The XCOMM1610I messages are produced by the scan since the Control Center is started using the GET command form the browser.
Use the XCOM Storage Usage Worksheet to calculate/determine how much storage the XCOM task needs.
Yes, when you enter the URL it will connect you to the server without asking to reenter the password because it is saved in a cookie, if you have the cookie box checked on the top of the Settings tab.
Additional Information
For more information about the Control Center, refer to our online documentation: Control Center
Feedback
