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 Component user options being lost when built from ZDD 8.1.2
A customer has reported an issue where existing component history data (e.g. component user options ) are being lost when a ZMF package component is built via ZDD 8.1.2. When the ‘Override History’ option is selected , the user options are not passed to the build process despite the correct, existing values being specified. Subsequent rebuilds of the same component will obviously use the new, blank settings.
CMS-XML ZMF4ECL setting extended user options incorrectly
Using ZMF4ECL a customer is expecting a component to have userOption0302 set to N by both existing baseline component history and by defaulting the value in the ZDDOPTS BUILD member. Although the Build Component/ Build Parameters initially show the field set to N an incorrect value of YES is being passed to the CMN ZMF Server. The wrong value may be influenced by other user fields.
CMS-XML WD4ZMF: Component build options not being set correctly in build dialog
Please note that user options (i.e. the USROPnn variables) are not affected by this problem and the updates are both passed and retained for future use. Also, when a source component that requires a DB2 pre-compile is checked out into a package the pre-compile flag is not being automatically pre-checked.
CMS-XML HLLX BULD00US not mapping UserOptions correctly when build component through ZMF4ECL
When you have the HLLX exit BULD00US active it does not pass the userOptions through HLLX properly when building the component through ZMF4ECL.
CMS-XML The DOC for the ZDDOPTS BUILD member shows 0-32 as the length for the label attribute, but over 200 bytes are actually passed if defined.
The DOC for the ZDDOPTS BUILD member shows 0-32 as the length for the label attribute, but over 200 bytes are actually passed if defined.
CMS-XML ZMF4ECL Build 174, like-Other JOBCARDS are not being passed through to the ZMF Server.
ZMF4ECL Build 174, like-Other JOBCARDS are not being passed through to the ZMF Server.
CMS-XML Data available at the BULD0004and BULD0104 HLLX exit points, is inconsistent depending on where call originated.
Data passed to HLLX exit points for BUILD , is not consistent when called from different clients.
CMS-XML ZDD: Inconsistencies in ISPF and Client Pack invocation of HLLX BULD* routines
Using ISPF as the benchmark, all works well. The BULD0nUS and BULD0nUV exits can be set up to implement the requirements and they are passed to the build procedure in the expected manner. In the following extract, CUSR014 has been set to ‘Y’ in BULD00US, CUSR015 to ‘N’ in BULD01US, V03 to ‘PRESET’ in BULD00UV and V04 to ‘POSTSET’ in BULD01UV.
CMS-XML ZMF4ECL: Inconsistencies in ISPF and Client Pack invocation of HLLX BULD* routines
Using ISPF as the benchmark, all works well. The BULD0nUS and BULD0nUV exits can be set up to implement the requirements and they are passed to the build procedure in the expected manner. In the following extract, CUSR014 has been set to 'Y' in BULD00US, CUSR015 to 'N' in BULD01US, V03 to 'PRESET' in BULD00UV and V04 to 'POSTSET' in BULD01UV.
CMS-XML The DOC for the ZDDOPTS BUILD member shows 0-32 as the length for the label attribute, but 64 bytes are actually passsed.
The ZDDOPTS documentation indicates that 0-32 bytes can be specified for the label attribute, but up to 64 bytes are actually being passed \ displayed. ZMF4ECL accepts more that 32 bytes as well. 200 bytes are being specified for the label.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs