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
PDF Serena(TM) ChangeMan(TM) ZMF Version 5
To obtain an ID and password for access to eSupport, email support@serena.com ... 2. Conversion procedures are required when upgrading to ChangeMan SSM 8.2.0 from a prior release.
CMS-XML SSM831 S878 Abend during Change Basket creation after upgrading from SSM V821
SSM831 S878 Abend during Change Basket creation after upgrading from SSM V821
CMS-XML SSM83x: S0C4 abend in module HPSSERV in RTCT at OFFSET=00013396 after upgrade from SSM82x
SSM83x: S0C4 abend in module HPSSERV in RTCT at OFFSET=00013396 after upgrade from SSM82x
CMS-XML HPSINTEG is issueing a RC=04 during weekly run after upgrade to ZMF 7.1.3.02.
HPSINTEG is issueing a RC=04 during weekly run after upgrade to ZMF 7.1.3.02.
CMS-XML SSM830: All releases when upgrading to z/OS 1.7
SSM V8.3 is scheduled to be released sometime after the first half of next year (2006) with support for z/OS 1.7. The expected impact to SSM in z/OS 1.7 will be support for the new TYPE=LARGE sequential files. Depending on your use of this new data set type, we may have to supply a tolerance patch for current SSM releases.
CMS-XML SSM Upgrade from V821 to V831 getting HPS0703W messages during fingerprinting
After upgrading from SSM V821 to V831 the customer is reporting the following message for several PDS data sets: I am being told this does not happen under the old release (V821): HPS0703W HPSDSFTP 12:28:46 Begin TTR not found x'01EF00' member 14,773 of 142,172 member name BCCRCVCV
CMS-XML SSM832: MRT (Member Reference Tracking) definitions go missing after running HPSMAINT and HPSINTEG processes
The situation is that existing MRT definitions are "somehow" being dropped/ lost /deleted form the SSM database. Background:
CMS-XML SSM823: Problems with not receiving E-mail notifications
Reporting problems with E-mail Notifications If you are having problems receiving E-mail notifications, after going through the Verification process, please supply support with the following documentation: 1. The entire output of the E-mail notification STC. Insure that the DEBUG parm was set to "1" in the MAIL4NFY member as shown below:
CMS-XML Notification email is missing Subject
Notification email is missing Subject
CMS-XML mail2exe failing with s0c4
mail 2exe failing with s0c4
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs