Find Answers

Filter Search Results
All Products:

Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Checkout from another package to a personal library fails "CMN8490I - Dataset name not specified"
CMNCKOT3 Checkout Command ===> CMN 000 CMN8490I - Dataset name was not specified .
CMS-XML ‘CMN8490I - Release Area Name was not specified’ running RLSMAREA PACKAGE DEMOTE service
CMN8490I - Release Area Name was not specified ’ running RLSMAREA PACKAGE DEMOTE service
CMS-XML WD4ZMF: Recompile fails with 'CMN8490I - Member Name was not specified'
WD4ZMF: Recompile fails with ' CMN8490I - Member Name was not specified '
CMS-XML FORMS - PKG - LIST service returns CMN8490I - DETAIL was not specified.
FORMS - PKG - LIST service returns CMN8490I - DETAIL was not specified .
CMS-XML ‘CMN8490I – Status flag(s) was not specified’ calling XML service CMPONENT PKG_COMP UPDATE using SERXMLCC
CMN8490I – Status flag(s) was not specified ’ calling XML service CMPONENT PKG_COMP UPDATE using SERXMLCC
CMS-XML 8.1.0 Attempt to add a new site in A.G.6 on an ALL site, you will receive error CMN8490I - SER#PARM DSN was not specified
8.1.0 Attempt to add a new site in A.G.6 on an ALL site, you will receive error CMN8490I - SER#PARM DSN was not specified
CMS-XML Option 1.B receiving error ‘CMN8490I - Application was not specified’.
When a new user enters ChangeMan and attempts to browse a component in baseline using option 1.B (‘Build’, then ‘Browse’) they get the message ‘CMN8490I - Application was not specified’. The CMN8490I message is also issued in the following scenario.
CMS-XML WD4ZMF - "CMN8490I - Compile procedure was not specified" is incorrectly issued.
<field name="LinkOptions" readonly="N" default="/> </profile> Since all the required fields on the BUILD screen are set, they should only need to press the ok button, but when they do, CMN8490I is issued.
CMS-XML Multiple SRC component overlay checkouts fail with CMN8490I or no error message at all
CMN8490I - library type was not specified . The problem affects multiple component checkout overlay requests issued in ISPF and in XML Service/Client Pack (e.g. ZMF4ECL) interfaces.
CMS-XML Invalid CMN8490I (compile procedure not specified) or 'CMNSTG09 error' staging like-Other components
Panel 'CMNSTG09' error/Invalid cursor field/area specified as a parameter. These problems do not appear to have existed in the same manner on earlier versions of the product (i.e. 5.6 or 6.1). In our recreation of the problem the components can be staged specifying the member name directly in the initial staging panel CMNSTG02.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs