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 The data source 'DSN=xy Oracle;UID=xz' could not be verified
the server name, login ID, and password to make sure
CMS-XML Running a XML service and getting 'Reason Code=8130' that is not documented
b) Verify the ChangeMan STC JCL has the parm 'XML=YES'. c) Verify XML job SER#PARM DSN references the same IP address and port# used by the ChangeMan STC. d) Verify client LPAR has IP connectivity to ChangeMan STC LPAR.
CMS-XML Get the following error in the browser when opening or submitting an item. "The item could not be found."
Open the ODBC datasource screen in Windows which is usually in the Administrative Tools area Go to the System DSN tab and just verify that your new ODBC connection is using the driver called "ODBC Driver 11 for SQL Server" If it's not using that driver you can manually create one on that screen and select the driver then open configurator and point to the new ODBC Connection.
CMS-XML Dim CM: How to check the current object type sequence values using the objtypeseq command
dmdba basedb/password@ dsn BASEDB> objtypeseq The output from this command may look something like this:
CMS-XML KM-Dim8: How to check that item library files exist for each item revision in the database.
Run the following SQL to create a UNIX/Linux shell script that confirms the existence of the appropriate file in the item library: sqlplus <basedb>/<password>@< dsn > SQL> set heading off
CMS-XML KM-Dim10: How to test multiple checkin checkout problems on Unix
$ cat dm.sh dmcli -user dmsys -pass dmsys -host stal-al-sun3:671 -dbname intermediate - dsn ora9 -cmd exit The login information needs to be modified to reflect your system settings.
CMS-XML MRM - SD23 abend occurs when specifying an invalid DSN while using M+R within Change Man 5.1.
Verify that IBM APARs OW45887 and OW38662 have been applied at your installation. These APARS describe two problems with these exact symptoms.
CMS-XML Dim10: Build of DB2 cobol program / IKJ56246I FILE DBRMLIB NOT ALLOCATED, FILE IN USE
1READY DSN SYSTEM(T02) DSN BIND PACKAGE(FFFLBTCH) MEMBER(AFFBAGJA) RELEASE(COMMIT) OWNER(CLICX) QUALIFIER(CLICX) VALIDATE (BIND) ISOLATIO N(CS) CURRENTDATA( NO ) ACTION(REPLACE) FLAG(I) EXPLAIN(YES) IKJ56246I FILE DBRMLIB NOT ALLOCATED, FILE IN USE
CMS-XML FDM: VERIFY gives non-standard member name error
The datase members look as follows: - DSN =IMS.FORMATA,VOL=SER=OS3P9B MEM=: -------------------------------------- CMD NAME DATA/MSG ALIASOF LEN/LKED -- ATTRIBUTES - APF MODE MAIN
CMS-XML STR710: VERIFY : NOLOAD results in PDS999E ABEND S80A U0000 AT +005FC6 IN PROGRAM PDSSPACE
- DSN =SYS1.LINKLIB,VOL=SER=BH3RES MEM=: ---------------
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs