Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML 8.2 Patch 4 COBOL XML fails with ‘SER6205E connection failed’
8.2 Patch 4 COBOL XML fails with ‘ SER 6205 E connection failed’
CMS-XML ZMF4ECL: Users unable to connect to ZMF Server (SER8210E)
ZMF4ECL: Users unable to connect to ZMF Server ( SER 8210 E )
CMS-XML ‘SER8500E FILE service not found for product CMN’ when using XMLCFIL* COBOL copybooks
SER 8500 E FILE service not found for product CMN’ when using XMLCFIL* COBOL copybooks
CMS-XML SER0953E Task abnormally terminated: Comp=U0067 Function=MASTER/UPDATE NSI=
SER 0953 E Task abnormally terminated: Comp=U0067 Function=MASTER/UPDATE NSI=
CMS-XML SSM Started Task gets error SER0603E TCP/IP logons will not be allowed due to an error in passticket initialization
SSM Started Task gets error SER 0603 E TCP/IP logons will not be allowed due to an error in passticket initialization
CMS-XML ZMF4ECL: Users still unable to connect to ZMF Server with SER8210E error messages, despite applying previous fixes
ZMF4ECL: Users still unable to connect to ZMF Server with SER 8210 E error messages, despite applying previous fixes
CMS-XML ZMF4ECL: Multiple users still unable to connect to ZMF Server (SER8210E) despite running fix for OCTCR46A38001
ZMF4ECL: Multiple users still unable to connect to ZMF Server ( SER 8210 E ) despite running fix for OCTCR46A38001
CMS-XML Invalid SER8207E message after upgrade from 7.1.3.03 to 8.1.2 caused by incorrect version of SERLCSEC
Invalid SER 8207 E message after upgrade from 7.1.3.03 to 8.1.2 caused by incorrect version of SERLCSEC
CMS-XML SER8602E - SER#PARM record length too small to hold DNS name. IP address used instead.
Prior to ZMF 8.1.1, the SER #PARM data set only supported IP V4 addresses, and only supported DNS names up to 15 characters in length. In order to
CMS-XML Unexpected SER7905E (Lock table is full) messages requiring ZMF Server task restart to resolve
Once this occurs the Server started task is effectively dead and a restart is required to clear the problem. Displaying the content of the lock table using the LOCK command shows a nominal amount of locks in effect, i. e . 10 or less in each case, and the table should certainly not be full.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs