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 CMNINIT User Abend 44 not issued as expected when logging on to mixed ZMF releases in split screen mode.
CMNINIT User Abend 44 not issued as expected when logging on to mixed ZMF releases in split screen mode.
CMS-XML ZMF4ECL: SAXParseException error displayed in relation to failed user logon attempt
ZMF4ECL: SAXParseException error displayed in relation to failed user logon attempt
CMS-XML User is not notified on SHUTDOWN when ZMF logon CLIST uses CONNECT(T)
"It is not possible to perform this function in the existing SerNet architecture. Users may now be logged on using TCP/IP and may be logged on from other systems." The previous comment applies to ZMF 5.3.x and ZMF 5.5.x.
CMS-XML User unable to edit and save changes, when component has been saved previously by someone else.
If USERA attempts to edit a component that was previously saved by USERB, the changes are not saved and "Checkin failed CMN8262I - Component to be staged is locked by USERB." is issued. Also, Admins are allowed to edit the component successfully. If the user logins to ISPF ZMF, saves the component there and then attempt the edit in ZMF for Eclipse, the edit is then successful.
CMS-XML Login to ZMF loops during failed attempt to allocate temp dataset.
As an example, the following RACF errors might be displayed for each failed allocation. ICH408I USER (JJONES ) GROUP(CMNSUP ) NAME(JEFF JONES ) 590
CMS-XML ZMF users connecting via TCP/IP (Load Balancing Option) require an OMVS segment
2. Change the login clist to run with the TEST option, and make sure the SERPRINT ddname is allocated in the CLIST. Run the CLIST to connect to the ZMF task. Browse the SERPRINT ddname allocated to the TSO user's address space. If the userid does not have an OMVS segment, you will see the following error in SERPRINT.
CMS-XML S102 in started task, S102 at each user, followed by S0C4 in STC,
An S102 occured in the started task, followed by an S102 in every logged on user (30 total S102s), followed by an S0C4 in the started task.
CMS-XML CMN408I - Component activated messages, incorrectly sent to TSO user.
When a component is activated using the checkin/stage dialog, CMN408I - Component activated messages are incorrectly sent to the TSO user ID, if the user is logged on . Since message is already being sent to the user ID logged into the Eclipse client, the additional CMN408I message sent to TSO is confusing.
CMS-XML ZMF4ECL: Users unable to connect to ZMF Server (SER8210E)
SER8210E Session rejected because no initial logon Notes: - Customer is not using SSL connections and all settings are appropriate for this.
CMS-XML SER10ty and Changeman ZMF - What does the Concurrent Server Users limit?
What the "Concurrent Server Users" limits is the number of logons to Sernet using TCP/IP. ChangeMan ZMF logons , even when they come from another z/OS system and therefore use TCP/IP, issue a START command - not a logon . Because of this architecture, this parameter will not limit the number of Change Man ZMF users who can log on to the started task.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs