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 SSM823: Getting 16D Abend, and message ISPC506E: Error File SSMHFSK not found or was empty.
1 View Display source data or listings Time. . 2 Edit Create or change source data Terminal. ... 10 SCLM SW Configuration Library Manager MVS acct.
CMS-XML Detect and Sync Option S.A.2 generated JCL results in HPS0100W HPSTRANS 15:04:34 * Failure * Dynamic allocation of: /
Select subset by DSN pattern ==> (Optional) Select subset by DSN type ==> PO,PS, DA , SRC ,LOAD (Optional) --OR--
CMS-XML Message 'GIM44402W IGGDARU3 WAS NOT ASSEMBLED FOR SRC IGGDARU3' results during SMP/E APPLY
Message 'GIM44402W IGGDARU3 WAS NOT ASSEMBLED FOR SRC IGGDARU3' results during SMP/E APPLY
CMS-XML s.0.1 source and text masking missing comman separator after squeeze in MASK=(SQUEEZECASE=UPPER)
s.0.1 source and text masking missing comman separator after squeeze in MASK=(SQUEEZECASE=UPPER)
CMS-XML HPS0568E HPSTRANS 11:06:40 SERCOPY failed with RC=8
The IEB1074E from IEBCOPY or FCO473A from PDSMAN indicate that the source dataset is a PDSE ( type =library) while the dataset of the same name on the target system is just a standard PDS. If SSM detects differences, it will not attempt to modify the attributes of the target dataset.
CMS-XML No corresponding END on a DO statement in MAIL2EXE.
The following paragraph of code does not have a corresponding END on the DO statement in the SSM 834 MAIL2EXE source . 000099 if UserList = ' ' then NOP 000100 else
CMS-XML SSM832 Additional fix for reported MOVEGRP problem, Msg. HPS1335W with RC=9 or RC=10
This is an additional fix to a previously reported MOVEGRP problem, where not finding a pre-existing SAF-based TARGET group before attempting to move a TSO-based SOURCE group, resulting in HPS1335W messages with a RC=9 or RC=10.
CMS-XML SSM823: Messages HPS0174W & HPS0108W generated during HPSINTEG processing indicating defective history record will have bytes removed.
11). I do not understand the nature of this problem ( origin /symptom), nor what actions can be taken to correct/resolve this condition.
CMS-XML HPS0713W HPSDSFTP PDS directory is damaged followed by a S130 abend.
targetComponent = ABCD componentType = SRC -E- SERXMLRC returned - xmlRC:8
CMS-XML CMN8711I - Save staging version error; Function = 8, Reason code = 0018.
Saved staging versions not deleted. AAAA000001 SRC
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs