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 Batch stage with SB doesn't pass user options to compile
Batch stage with SB doesn't pass user options to compile
CMS-XML User options from component history are not passed to CMNEX026 during a Mass Stage.
User options not being passed to CMNEX026 during a Mass Stage , even though SUPPRESS HISTORY "NO" is specified and the generated stage JCL does contains the appropriate options from the component's history.
CMS-XML Inconsistent variables passed to HLLX BULD01R0 at recompile time
Inconsistent variables are being passed to the 'post initial recompile panel' (CMNRCMPR/CMNRCMP0) HLLX BULD01R0 depending on where the function is being invoked. For example, if a user enters the package list recompile option (5.RC) they see the following output from the exit:
CMS-XML WD4ZMF: Overridden component build options not passed to build process
If a user overrides build options when submitting a request under the WD4ZMF client (e.g. DB2 Precompile, User Options , etc.) the overridden values are not being passed to the build process. That is, it appears that it is impossible to override package/component history from WD4ZMF.
CMS-XML How to save compile, link and user options without baselineing a package.
3) set the install time for the package to 1 or 2 minutes later 4) when the install time has passed , go to monitor limbo (or have someone do it who has the authority) and delete the package 5) the next time the component(s) are compiled or recompiled the options set in the deleted package will be used
CMS-XML User options not available to CMNEX026 during Relink
Component user options are not stored alongside ILOD-related components (e.g. LOD, DBR, LST, etc.). Hence they are not passed to CMNEX026 during relink processing.
CMS-XML Recompile not passing correct parms to CMNEX026
Customers using ZMF 6.1 have reported a problem where incorrect parameters are being passed to exit 26 in the OPT call during recompile processing. For example, the X26£LANG, X26£PROC and user option fields (X26£UOPn/X26£OPnn) are not being set correctly when the exit is invoked. Compile requests for source components that have been checked out and which are resident in the package are NOT affected by the same problem.
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 ZMF4ECL: Component and user variables set in BULD01Ux not passed to submitted JCL
Component and user variables being set in HLLXs BULD01US or BULD01UV are not being passed to the file tailored component build job in the ZMF4ECL interface. They are being passed if the relevant panels are displayed and exits executed in the ISPF interface.
CMS-XML HLLX BULD0004 causing incorrect component history options to be used
HISTORY ASSUMED/CMN2571I - Translator options obtained from component history. Also, some of the component history passed to the build procedure and stored for this component within the package is incorrect (e.g. the DB2 build option ).
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs