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 Release Cadence for ChangeMan ZMF – Post-February 2021
Release Cadence for ChangeMan ZMF – Post -February 2021
CMS-XML "Approve" button is grayed out after an unplanned package is baselined. POST approvals cannot be done.
"Approve" button is grayed out after an unplanned package is baselined. POST approvals cannot be done.
CMS-XML "Approve" is grayed out after an unplanned package is baselined. POST approvals cannot be done.
"Approve" is grayed out after an unplanned package is baselined. POST approvals cannot be done.
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 ZDD: HLLX update exit inconsistencies
a) if no package data has been updated in the dialog the post -processing exit is not invoked in ZDD. It is invoked in ISPF.
CMS-XML ZMF4ECL: HLLX update exit inconsistencies
a) if no package data has been updated in the dialog the post -processing exit is not invoked in ZMF4ECL. It is invoked in ISPF.
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 ZDD not clearing fields manipulated in HLLX PCRE01PU
These variables are initialised to 'blank' in the pre-package user options exit point (PCRE00PU). The post -package user options exit (PCRE01PU) ensures that no 'gaps' are left in variable usage. So, for example, if USR0802 has been left 'blank' but USR0803 has been given a value, that value will be moved to USR0802 and USR0803 will be re-initialised to blanks.
CMS-XML ZMF4ECL not clearing fields manipulated in HLLX PCRE01PU
These variables are initialised to ‘blank’ in the pre-package user options exit point (PCRE00PU). The post -package user options exit (PCRE01PU) ensures that no ‘gaps’ are left in variable usage. So, for example, if USR0802 has been left ‘blank’ but USR0803 has been given a value, that value will be moved to USR0802 and USR0803 will be re-initialised to blank.
CMS-XML New Features in ChangeMan ZMF for Eclipse 8.1.3
exit points, *00PU or *00UV. Any change to the profile name from the HLLX post -processing exit points, *01PU or *01UV, will be ignored.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs