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 Allocation of Staging dataset must be done by Change Man.
Allocation of Staging dataset must be done by Change Man.
CMS-XML Production staging libraries are not being allocated as PDSE's
Production staging libraries are not being allocated as PDSE's
CMS-XML Staging libraries being allocated with one extra space unit (CYL or TRK)
Staging libraries being allocated with one extra space unit (CYL or TRK)
CMS-XML Incorrect message when unable to allocate staging library
Incorrect message when unable to allocate staging library
CMS-XML "Stage All" function with HFS files produces error message ' UTILITY DATA SET NOT ALLOCATED'
When you create a package and do a Stage From Development (S1 from the list screen) and use a HFS file for your development library and enter the " Stage All" command to stage all components in a given directory you receive the following message: IKJ56231I UTILITY DATA SET NOT ALLOCATED, SYSTEM OR INSTALLATION ERROR+ IKJ56231I TEXT UNIT x'0002' CONTAINS INVALID PARAMETER ***
CMS-XML "CMN2650I - Unable to allocate" is issued when a component is staged (without edit) for the second time, and "ELIMINATE SAVE TO PERSONAL LIB" is set to "NO" and "ALLOW CHECKOUT TO PERSONAL LIB." is set to "YES".
"CMN2650I - Unable to allocate " is issued when a component is staged (without edit) for the second time, and "ELIMINATE SAVE TO PERSONAL LIB" is set to "NO" and "ALLOW CHECKOUT TO PERSONAL LIB." is set to "YES".
CMS-XML Part. pkg audit attempts to allocate a non-existent staging copybook library, resulting in IKJ56228I messages in the started task.
When audit runs, it will attempt to allocate the non-existent CPY staging dataset for the package which contains no copybooks. This seems to happen while audit is building the list of copybook libraries to search. In the example below, dataset "CMNSUP.CMN.S560ALL.JEFF.#000777.CPY"
CMS-XML Compile SUCCESS Step could fail because the &&BAT90CTL temporary file is allocated with a BLKSIZE=0
For example, while staging a component using a Compile Procedure that did not generate any source-to-load relationship within the procedure (i.e. did not create a &&BAT90CTL file and populate it with records before the SUCCESS job step is run), the job ended with a IEC141I 013-34 error
CMS-XML Warning message appears after clicking link to another SBM server in distributed installation
Warning message appears after clicking link to another SBM server in distributed installation
CMS-XML Links not working in Advanced Distribution report list
Links not working in Advanced Distribution report list
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs