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 CMN500 report and CMNREPT5 & CMNREPT6 panels.
CMN500 report and CMNREPT 5 & CMNREPT6 panels.
CMS-XML CMNREPT1 panel only allows 43 byte Report Descriptions
COPYLIB CMNRPTDS has 44 byte Report Descriptions Panel CMNREPT1 only allows 43 byte Report Descriptions Panel CMNREPT6 , which displays the Reports, allows 44 byte Report Descriptions
CMS-XML V6.1.2 - Package Number field for CMN180 report must contain leading zeroes
If the CMN180 report is submitted for a specific Package ID, when the Package Number field on the REPORT SELECTION LIST panel ( CMNREPT6 ) is specified without the leading zeroes, the report will be empty and will display “No components found” message: =========================
CMS-XML Typos in CMN070 and CMN920 reports
Typos in CMN070 and CMN920 reports. CMN070: report is anly available online CMN920 on CMNREPT6 Description: Staging Libray Aging Report
CMS-XML CMN950 report is ignoring the ending date
CMN950 report is ignoring the ending date. The from date works fine, The title of the report shows the ‘To’ date entered on panel CMNREPT6 ; however the report includes packages pass the ‘to’ date.
CMS-XML 'Package Number' field for CMN180 report must contain leading zeroes
When the CMN180 report is submitted for a specific package and the 'Package Number' field on the REPORT SELECTION LIST panel ( CMNREPT6 ) is specified without the leading zeroes (ex: 3728), the report will be empty and will display 'No components found' message. This is not consistent with other admin reports (leading zeroes are not mandatory for CMN080, etc.).
CMS-XML Invalid "No packages found" message in CMN500.
Invalid "No packages found" message in CMN500. When the CMN500 report is submitted with only the application name being entered in the Report Variable field on the CMNREPT6 panel ID, the job ends with RC=4 and the "No packages found" message is displayed in the SYSTSPRT of the job. NOTE: When a package ID is entered instead of the application name, the CMN500 report is submitted correctly.
CMS-XML S878 followed by a S40D abend in CMN180 for 1 appl with no pkg number & date range
Customer received an S878 abend followed by a S40D abend in V7.1.3B when running CMN180 report for one application without a package ID and/or without date range being specified on the CMNREPT6 (REPORT SELECTION LIST) panel. When selection criteria are present on the panel to reduce the amount of data to be reported, then the CMN180 report completes successfully.
CMS-XML Report variable in report functions is translated incorrectly.
For example: CMNREPT6 Report Selection List Row 11 to 20 of 35 Command ===> Scroll ===> CSR
CMS-XML New Features in ChangeMan ZMF 8.2 Patch 1
In previous releases, if you selected the Component History By Package Report (Report 170) from either global or application administration functions, and you specified only the application mnemonic on the Report Selection List ( CMNREPT6 ) panel, the following messages were displayed: Short message: INVALID FIELD
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs