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 Checkin (drag/drop) with Build option enabled does not issue the Build.
Checkin (drag/ drop ) with Build option enabled does not issue the Build.
CMS-XML Checkin (drag/drop) with the Build option selected does not present the Build dialog.
Checkin (drag/ drop ) with the Build option selected does not present the Build dialog.
CMS-XML ZMF4ECL 'Sort Packages Descending on Serena Explorer' not working after upgrade
ZMF4ECL 'Sort Packages Descending on Serena Explorer' not working after upgrade
CMS-XML "Approve" is grayed out after an unplanned/TEMP package is in TCC status. POST approvals cannot be done.
"Approve" is grayed out after an unplanned/TEMP package is in TCC status. POST approvals cannot be done.
CMS-XML Duplicates in Language drop down if no component history.
Duplicates in Language drop down if no component history.
CMS-XML HLLX BULD0101 Exit not called in ZMF4ECL.
This is being reported as an inconsistency defect as the following HLLX BULD0101 Exit is called in ZMF, however if you list the components in a package when you stage the component the post HLLX BULD0101 is not called in ZMF4ECL.
CMS-XML Check In with Build - components not selected.
When you perform a Checkin (drag/ drop ) with the Build option enabled it does not issue the Build. When performing a checkin (from say another package) with drag and drop we are presented with a panel which gives us the chance (with source like components) to perform a build at the same time.
CMS-XML JOBCARDs being set in HLLX are not being displayed when the function is executed.
JOBCARDs set by HLLX in the pre-submission exit points are not displayed in the interface, but are being set and used by the post -submission exit points. These are the HLL exit points: BULD0004 - BULD0104 ... for BUILD function
CMS-XML Problems related to ZDD binary file checkin processing
a) When copying a binary file containing ascii Chinese characters from ZDD to a mainframe dataset everything works OK. However, when checking the same file into a package library type using ZDD some data is either being dropped or incorrectly translated.
CMS-XML ZDD: Inconsistencies in ISPF and Client Pack invocation of HLLX BULD* routines
The customer’s use case is two fold: a) for some component types they wish to allow users access to change component user options (build skel variables &CUSRnnn/HLLX variables userOptionxxyy) and for others they do not. b) similarly, they wish to unilaterally pre-set and post -set both component user options and some build process custom variables (skel variables Vnn/HLLX variables userVariablenn), regardless of any settings provided by the user.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs