Find Answers

Filter Search Results
All Products:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
  Results
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 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 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 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.
CMS-XML ZMF4ECL: 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 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.
CMS-XML ZMF4ECL checkout conflicts can be bypassed
It is worth noting that the expected notifications are visible post -checkout in the ZMF Notifications view. To ensure consistency with the ISPF interface, we should probably force users to see any potential conflicts before the checkout is completed.

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs