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 Startool FDM RESTORE cmd failed with error PDS896E in Version (7.7.0 2009.114)
3) Performed step 2 again with same member names. 4) Attempt a RESTORE on the dataset; make sure enter a filter in the ‘Find data’ field. Result is: After hang for a long time the error messages below are displayed
CMS-XML V (VIEW) line command fails with PDS872E error message for PDSE data sets
Workaround: Use VE to invoke VERIFY
CMS-XML FDM: VERIFY gives non-standard member name error
NOLOAD - the standard MVS LOAD macro fails with this type of member name. (The actual failing process was FIND, as described in message IEW4007.)
CMS-XML CSV028I ABEND106-14
CSV031I LIBRARY ACCESS FAILED FOR MODULE LCA600KM, RETURN CODE 14, REASON CODE 26110021, DDNAME SYS00001 ... To check the size of the user private area, issue FDM command LISTENV and see how larger the private area is.
CMS-XML DSNT408I SQLCODE = -104 when inserting a new row into a DB2 table.
3. Enter the DB2 table information and make sure the "service" is EDIT. ... 9. PF3 and you get the following message: PDS#304Q SQL INSERT or UPDATE for some changes failed , SAVE not allowed
CMS-XML DB2 -- error code 0000000C -- reason code 00F30040
Ensure the FDM.CNTL(BINDJCL) job run against the DB2 subsystem on the MVS system in which the error was encountered. ... Also, ensure the DB2 subsystem against which the db2 plan will be run is up before running FDM.CNTL(BINDJCL). ... Explanation: The allocation of the plan to the connection failed .
CMS-XML startool DELETE of members results in job hung
Apply the following IBM PTF associated with the APAR and ensure patch FDM 7.7.0.8 is installed. ... THE BROKEN PDSE STILL NEEDS TO BE RECOVERED.
CMS-XML GIM54502E ** ALLOCATION FAILED FOR PDSELOD
GIM54502E ** ALLOCATION FAILED FOR PDSELOD
CMS-XML FDM: PDS730E DYNAMIC PLIB DEFINITION FAILED
FDM: PDS730E DYNAMIC PLIB DEFINITION FAILED
CMS-XML PDS696E FIXPDS DSCB can only be used to verify DSCB data
PDS696E FIXPDS DSCB can only be used to verify DSCB data
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs