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 REPLACE command no longer accepts space before WRITE parameter
REPLACE command no longer accepts space before WRITE parameter
CMS-XML DSNTYPE incorrectly accepts DSNTYPE=PS for MODEL command
Space units ===> TRK (BLK, TRK or CYL) Round space ===> NO (YES or NO to round up to nearest CYL) Primary space===> 1 CURRENT Allocated space: 1 TRKS
CMS-XML REPLACE panel not accepting mixed T and C for FIND and REPLACE fields - gets 'unmatched quotes' error
Find conditions ==> (WORD, PREFIX or SUFFIX) Update on disk ==> NO (YES or NO ; use NO for a test run) Update ISPF statistics ==> YES (YES or NO)
CMS-XML SMP/E ACCEPT gets message IEB198I RECFM 'U' REQUIRED WITH COPYMOD FOR DDNAME SYSUT1 -- DATA SET HAS RECFM=VS
IEB1030I DDNAME AFD77LOD REFERS TO PDS DATA SET ON VOLUME S00DL6 NAMED INSTALL.STARTOOL.V770.ALOAD IEB166I NO MEMBERS COPIED TO DATA SET REFERENCED BY AFD77LOD IEB151I JOB HAS TERMINATED WITH ERROR(S)
CMS-XML FIXPDS against PDSE requires OLD
FIXPDS against a PDSE (Type=library) requires OLD allocation. DISP=OLD in the JCL is not making FDM recognize the data set as allocated with OLD. Does FDM honor DISP=OLD in th JCL? //S2 EXEC PGM=IKJEFT01,REGION=4M,DYNAMNBR=20 //PDSE DD DISP=OLD,DSN=TEMP.JES2.CNTL
CMS-XML Panel SZFXELOM get error 'command contains invalid keyword' if parameters exist
New panel SZFXELOM cannot accept parameters. However, from option 2 – parameters can be specified from the subsequent panel which are then passed to SZFXELOM and specified under field ‘Enter Options for PEDIT’. Selecting YES to continue browse will result in error as seen below.
CMS-XML LISTC command gets Message "Invalid DSN1 name" with national characters
Panels PDSLCMSX and PDSM034 after an "LC" command will not accept $,#,@ as first char of LEVEL/DSN; message 'Invalid DSN1 name' occurs. A national character will be accepted in other levels of the DSN.
CMS-XML FDM: LISTC (option 3.4) and GDG dataset masks
Catalog management does not recognize a dataset mask like TEST.GDG.G0001V00.** or TEST.GDG.G0001V00 as a GDG when a double asterisk ( ** ) is added at the end.
CMS-XML CMDS aganst an empty load ibary result in PDS#101 message: "invalid command "
Using an empty load lib, enter the command LLA or MAP. Neither is accepted . The message displayed is:
CMS-XML FIND and REPLACE commands not working when searching for hex strings resulting in PDS551W
The reason for the error was that the REPLACE and FIND commands were not recognizing hex values that contain 2 alphabetic characters such as x'FA' when combined with those such as x'f1' <example: x'f1f9faf1' >. If the x'fa' is by itself, the search will occur successfully.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Title: Dimensions CM: Deploying Emergency Fixes (demonstration)
This demonstration shows you how to deploy an emergency fix to a live production environment in Dimensions CM. You will learn how to promote requests to any stage in the Global Stage Lifecycle, promote and deploy in the same operation, and browse deployment areas.
Title: Dimensions CM: Deploying Requests (demonstration)
This demonstration shows you how to deploy requests in Dimensions CM. You will learn how to promote requests to the next stage in the Global Stage Lifecycle, deploy requests by
Title: Dimensions CM: Scheduling Deployment (demonstration)
This demonstration shows you how to schedule a deployment in Dimensions CM. You will learn how to set a deployment sequence, schedule a deployment, and use the Queue tab in the Deployment view

Additional Assistance

  • Submit a Case Online
  • FAQs