This site uses cookies to improve usability. With further use you agree to this. Privacy Policy


HOSTSYSTEM UB

Consulting and Software-Development

clearclear

SLM

System Library Manager


 

Surveillance of important system
libraries on the member level

 

SYSTEM LIBRARY MANAGER



SLM is a software product designed for HOST systems. Important system libraries may be supervised on the member level. The main characteristics of SLM are:
  • Audit: Who has altered where, when, what and why?
  • Archiving/Version comparison: Each alteration may be retraced as regards content. Comparison of any version is made possible.
  • Backup: You may back out alterations, go back to any preceding version, restore deleted members and reconstruct entire libraries precisely, e. g. the SYS1.PARMLIB of 2009-12-24 18:31:04 library.
  • File access will either be open (alterations processed the usual way, the archiving carried out in the background) or restrictive, that is, alterations will have to be executed using particular edit macros (e. g. LSAVE, LDELETE), the alteration to be carried out in SLM first and within the respective library afterwards.
  • The cause of the alteration will be called for due to the respective settings.
  • Reducing data flood: Some members might be altered extremely often, so that in the course of archiving a great amount of data is being produced. This may be reduced by the use of parameter control.
  • Customer requirements and ideas are always welcome.


SMDS

System Maintenance & Distribution System


 

Administering system-oriented
HOST Software

 

SYSTEM MAINTENANCE &
DISTRIBUTION SYSTEM



SMDS is a software product designed for administering system-oriented HOST software

By use of SMDS software products, releases and environments may be defined.
Application resp. backout of product/release may be controlled individually by functionally extended REXX procedures.
Actions will either be carried out manually or by automatical event resp. time control.
Software application will be carried out step-by-step:
  • Back up of the existing environment
  • Preparing a new environment
  • Activating the new environment
  • Fallback, if need be
All actions will be protocolled, the software status and the time of application will be clearly displayed according to the respective environment.