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 HPS0023E error when saving SSV versions on dynamically added dasd volumes.
Customer has been using SSV on their ZMF 5.3.0 system without incident until today. Coincidently, their systems folks dynamically added 20 DASD volumes to the system today (PRD091 - PRD110) and it is on one of these volumes that they experienced the problem (PRD092). Received the following HPS* messages today when attempting to stage /delete modules:
CMS-XML V7.1.2: CMNVSRVC RC=0008,MSG=CMN8711I - Save staging version error
====================================================== With newly created SSV VSAM files that are documented in Step 6 of the install guide, everything works correctly. The problem therefore appears to be with the converted staging files from Step 10 of the Conversion Guide.
CMS-XML SSM832 Getting an S878 Abend running through the DEMO Option processes
At no stage was I informed that there should be a REGION= parameter in the job card. ... Member Name ===> DEMOFGP ( Saved member in the user JCL library ) ... in the HPSPLIB library : STRSUP.SSM832.PARMLIB ... Comparison Utility ==> BUILT -IN BUILT -IN/COMPAREX/SUPERC
CMS-XML Questions on XML licensing and CSA
b) Library name in LICDSN load module in system link list, or in product STEPLIB or JOBLIB. ... 4) Is there any way to free up the CSA that LICUPDAT allocated?
CMS-XML HPS0713W HPSDSFTP PDS directory is damaged followed by a S130 abend.
- statusMessage : CMN8711I - Save staging version error; Function = 6, Reason code = Abend. ... When you go to the staging dataset nothing specific is noticeable, however the dataset is a PDS/E and not a PDS.
CMS-XML SER0953E Task abnormally terminated: Comp=S0C4 Function=ATTACH/SSV NSI=000C62C4
Encountered the following abend when trying to exit components were modifying or staging from devlopment. ... The user gets the following messages: CMN8711I - Save staging version error; Function = CREATE , Reason code = DOWN
CMS-XML S0B0 abend - corrupted PDSE Libs.
The following caller chain was found by chaining back through the R13 save areas: 7FFC8E00 00000000 00127A80 00000000 8671399A 7FFC8E10 867193A0 00000004 7FFC8F08 7FFC8F54
CMS-XML Message 'GIM44402W IGGDARU3 WAS NOT ASSEMBLED FOR SRC IGGDARU3' results during SMP/E APPLY
During the APPLY of SSM using SMP/E, the following message can occur. GIM44402W IGGDARU3 WAS NOT ASSEMBLED FOR SRC IGGDARU3 IN SYSMOD HSSM860 BECAUSE THERE IS NO MOD ENTRY FOR IGGDARU3. SMP/E CANNOT DETERMINE THE TARGET LIBRARY FOR THE ASSEMBLER OUTPUT.
CMS-XML SSM v832: Missing HPS292E message
1. From the Main SSM Menu go into Options and type in a non-existant dataset for your JCL library and PF3 out to save the changes. 2. Then from the Main Menu again, go into Administration, then Group Administrator. 3. Select a Department, then the Delete Object option.
CMS-XML SSM823: Member RESTORE gets JCL error when specifying BLK for new recovery DSN.
Directory ===> 45 (5-500) Member Name ===> SERALLOC ( Saved member name in the user JCL library ) Press ENTER to generate recovery JCL or END to exit
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs