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: Additional MRT (Member Reference Tracking) documentation notes
SSM823: Additional MRT (Member Reference Tracking) documentation notes
CMS-XML SSM823: Additional notes on how to verify SSM TSO Notification facility
SSM823: Additional notes on how to verify SSM TSO Notification facility
CMS-XML SSM830: Note regarding conversion of SSM V8.2.3 Master Files to V8.3.0
SSM830: Note regarding conversion of SSM V8.2.3 Master Files to V8.3.0
CMS-XML SSM832: Msg. starting TSO Notif. STC: IRX0034I Error running NOTE2EXE, line 384: Logical value not 0 or 1
SSM832: Msg. starting TSO Notif. STC: IRX0034I Error running NOTE 2EXE, line 384: Logical value not 0 or 1
CMS-XML ChangeMan SSM 8.3.4 patch SSM83401
Notes : - Download the README for details regarding this patch. The README is located on the support website under 'MY DOWNLOADS' DOCUMENTATION for the ChangeMan SSM 8.3.4 release.
CMS-XML ChangeMan SSM 8.3.4 Patch SSM83402
Notes : - Download the README for details regarding this patch. The README is located on the support website under 'MY DOWNLOADS' DOCUMENTATION for the ChangeMan SSM 8.3.4 release.
CMS-XML During IMPORT APPLY processing Scratch datasets not deleted
During IMPORT APPLY processing, SSM does not scratch the datasets noted in 'SCR DSN:'. //JOBLIB DD DISP=SHR,DSN=STRSUP.SSM834.LOAD // DD DISP=SHR,DSN=STRSUP.SSM834.SERCOMC.LOAD
CMS-XML Incorrect totals for VS_UPD in EVENTs report.
The opening totals section of the report (at line 971) notes "132" such events. However, the ensuing report lists only 131 such events (with the "totals section" label of VS_UPD being the 132nd. (So the totals, at least for VS_UPD, are off by 1, as there are only 131 actual VS_UPD events reported.)
CMS-XML SSM830: Over-ridings HPSPARMS sitemaster/objectmaster/deltamaster database names.
DETAILS: In releases prior to SSM V8.3.0, having the SSM (VSAM) database names hard coded in the HPSPARMS members caused some customers to have the concerns as noted below: 1) hard coding is not industry standard (i.e. symbolic substitution within DSNs is preferred)
CMS-XML SSM832 High EXCP consumption for syntax error HPS0012E.
An inadvertent user error in control card formatting, identified that the SMS processing step required over 1:30 minutes to complete, and used 123K EXCPs before ultimately failing, noting the syntax error. This is an extraordinary resource consumption for a 4-line input control card (statements) containing a syntax error. Also, that the same EXCP counts occur in our batch jobs running SHOWxx reports:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs