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
ERO Email notification not sent
CMS-XML Post Approval notification is incorrect when using EMAIL method
When an unplanned package is created and you have more than one post approval notification level using EMAIL as the notification vehicle, the first level post approval email notification is correct and looks like this: Package: TEST000769 Title: TEST
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 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 ISPF variables missing values when post-approval uses BATCH for the notification vehicle
Customer is getting two or three instances a week of e/ mails notifications for post approvals failing to be delivered because the package creator (PCRTID) is low values (missing) and so an invalid e/ mail address is being created.
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 New Features in ChangeMan ZMF 8.2
) that can connect through your company firewall. You specify the email notification links for the zMobile application through ZMF global administration on the
CMS-XML Release Cadence for ChangeMan ZMF – Post-February 2021
on the following link: If you have not already done so, please register to our Community site and subscribe for email notifications . 3. When is this changing?
CMS-XML Separating BATCH approval notifications for different users
Separating BATCH approval notifications for different users
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs