Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML FDM: VERIFY gives non-standard member name error
FDM: VERIFY gives non-standard member name error
CMS-XML LISTV processing using option 3.4 gets INVALID DSN1 NAME error
LISTV processing using option 3.4 gets INVALID DSN1 NAME error
CMS-XML REPRO member AS (new member name) gets syntax error PDS844E in batch
Prior to FDM 7.6.2, the following syntax with a space between AS and the new member name worked in batch. This syntax has never been valid issuing the same command through the panel interface. REPRO X* AS (N)
CMS-XML DSNT408I SQLCODE = -010, ERROR with DB2 long table name exceeding 24 characters
Source for display ===> DB2 (type-in, "D":"DB2" or "T":"TABLE") Subsystem name ===> S102 (Current Subsystem, or may change!) Creator name or mask ===> USER (type-in, creator name or masked..)
CMS-XML Incorrect check for new renamed member names in Member List.
When you rename member in a pds in FDM member List (ML;ren), the validity check for the new member name is not happening as it is possible to rename members with a special characters in them. Here are some samples:
Detail: When accessing FDM, the following error messages are received. User is then unable to get into the product.
CMS-XML FDM Customer getting PDS#309W error even though he has P720BIG applied.
One of my customers is getting the following message: PDS#309W The copybook name table is too small Is there a size limitation on the number of data items StarTool can
CMS-XML LV as alias of STARTOOL gets 'startool initialization error' dsn not cataloged
Per the installation guide, FDM can be invoked with alternate entry names - section 'invoking startool fdm with alternate entry names ' One of these entry names is LV for LISTV and can be defined as an alias of the STARTOOL module. Once this is done, from within ISPF the customer can issue command: TSO LV vvv where vvv is some volume mask.
CMS-XML PDS#301E String not found using COPYBOOK FIND cpybook-field NAME
In copybook mode, both standard and extended, use of FIND cpybook-field NAME results in 'PDS301E String not found error '. 1) selec t option 4 - pedit/pview specify dataset name containing data
CMS-XML FDM support of DB2 Tables With Long Column Names
SQL Error Timestamp. 2008-11-13-
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs