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 Why can't &&LIST* data sets be allocated to VIO?
Under the current design of MVS dynamic allocation, it is not possible to correct this. The purpose of SERPRINT is to dynamically allocate temporary data sets created in previous steps. There are three ways to allocate data sets:
CMS-XML SERPRINT temporary datasets
SERPRINT temporary datasets
CMS-XML SER0664W message in SERPRINT
SER0664W message in SERPRINT
CMS-XML SER2062W messages in SERPRINT
SER2062W messages in SERPRINT
CMS-XML Add SERPRINT ddname to CMNJOBS and CMNRPC procs
Add SERPRINT ddname to CMNJOBS and CMNRPC procs
CMS-XML Where does the SER_82OI environmental message being displayed within the SERPRINT portion of the SERVER obtain its information?
Where does the SER_82OI environmental message being displayed within the SERPRINT portion of the SERVER obtain its information?
CMS-XML Space Utilization for Temporary VIO Data Set is Incorrect
Space Utilization for Temporary VIO Data Set is Incorrect
CMS-XML Unnecessary SER6011I messages being issued to SERVER started task SERPRINT
Unnecessary SER6011I messages being issued to SERVER started task SERPRINT
CMS-XML CMN100 report generates SER8414W in SERPRINT for BASELIB SERVICE LIST
CMN100 report generates SER8414W in SERPRINT for BASELIB SERVICE LIST
CMS-XML CMNEX201 is not listed as loaded in started task SERPRINT
CMNEX201 is not listed as loaded in started task SERPRINT
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs