Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML ERO Email notification not sent
Customer does not receive email notifications when a package is attached to a release or when the release is blocked.
CMS-XML Sending dumps to Serena via e-mail or FTP.
What format should I use when sending dumps electronically to SERENA for Change Man problems?
CMS-XML Not all Batch Approval notifications sent if ECP is used for prior approval level
If you have your first level of Planned Approvals defined to use SERNET so you receive an email from ECP when the package is frozen, and also have at least two different Batch Approval notifications for your level two approvals, when you approve the first level via ECP, not all the Batch Notifications for level two approvals are sent (only one is sent ). In the JESMSGLG for your Started Task and you will see the following for each Batch Notification that is not sent:
CMS-XML CMNSMTP does not generate MIME headers correctly so they show up in the email
When you use the SAMPLE member CMNSMTP REXX exec to send notification emails , the MIME headers added by the REXX exec are showing up in the email The following lines appear at the beginning of the email : Mime-Version 1.0 Content-type: multipart/mixed
CMS-XML Sending dumps to Serena via tape.
8. The JCL / job output from cutting the tape should be sent to SERENA. Instead of downloading this to the tape, it should either be sent by (1) email (2) mail via the post office (or delivery service such as UPS/Federal Express) (3) fax (4) FTP to the SERENA FTP server. It is important to note that the tape may be mailed to our data center, but the JCL should come to support personnel.
CMS-XML Unable to send SERNET notification messages through ChangeXpress
If you set up to notify by e-mail through ChangeXpress, the e-mail is not generated. Instead there is an error message in the JESMSGLG:
CMS-XML USER - SERVICE - NOTIFY XML Service does not send data, when 4 is used.
The USER - SERVICE - NOTIFY XML Service does not send <textMessage> data, when <notifierType> 4 is used. Also, there are several package information related headers incorrectly sent in the e-mail , but with no data, as follows:
CMS-XML Instructions for Sending and Receiving files in XMIT format.
4. The file created by step 3, should be downloaded to your PC, using a BINARY transfer. 5. Send file(s) to SERENA either as an attachment to either an e-mail , or directly to your Case on our Support website. NOTE: For more information regarding XMIT, issue this command from Option 6: "TSO HELP XMIT"
CMS-XML New Features in ChangeMan ZMF 8.2
ZMF to send email notifications with an embedded link to package approvers, package approvers can click on the link in the email notification, or copy the link and paste it into a browser. Refer to the chapter on "Approving or Rejecting a Package" in the
CMS-XML Getting repeated S602 abend which bring CMN down
Since upgrading to V5.2.1 the S602 abends have happened twice. They re-cycle CMN and all appears to be fine. Customer sent the SERPRINT and SYSUDUMP in an e-mail .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs