This section provides an overview of the BSA components.
The Subsystem Function Facility (SFF) is the heart of the BSA platform and provides the operating environment in which most application functions will execute. SFF services are written with performance and availability in mind. SFF services include:
Base System Facilities (BSF) is a set of services used in common by BSA and product components. BSF services include:
The Base Output Facility (BOF) provides a set of services for managing printing requests to 3270-type printers (or emulations). SNA LU types 0, 1, 3 and 6.2 protocols are supported. BOF supports printing to JES and printing to file, and manages the printing to VTAM printers initiated by _beta doc|z.
The Base Archive Facility (BAF) provides a set of services for writing to archives, reading from archives, and administering archived data.
The Data Management Facility (DMF) and Beta Query Language (BQL) consist of a set of database access services providing keyed, sequential, or indexed table database access services in an SFF operating environment. All information is stored and retrieved in VSAM ESDS datasets providing an optimum in performance, reliability and maintainability.
DMF and BQL also provide facilities for coordinating database activities between their own applications and z/OS dataset services and facilities. These include services for locking resources, software caching, and dataset backup services in a shared-DASD multi-CPU environment.
The Open Communication Facility (OCF) provides peer-to-peer communication services between programs written for an SFF operating environment. It also provides functions running in other environments or other SFF operating environments.
OCF uses the Advanced Program-to-Program Communication (APPC) services of z/OS to facilitate communications with these external functions. Alternatively, you can also use OCF via TCP/IP.
BSA XCF communication uses the extended capabilities of the Cross Coupling Facility (XCF) component of the z/OS operating system. It enables different Beta products and CPUs to be accessed across LPAR boundaries without requiring the use of an additional task such as the OCF Cross System Router.
The VTAM Dialog Facility (VDF) is a set of services for managing the dialog between 3270-type display terminals running in a native VTAM (non-TSO) environment and applications running in an SFF operating environment. VDF enables users in non-TSO environments to access Beta products.
The add-ons _beta caf and _beta iaf enable access to Beta products from CICS and IMS operating environments. VDF is the basic component for the operation of the add-ons _beta vaf, _beta caf, and _beta iaf. These add-ons are included in the TES (Transaction Environment Support) license article.
_beta caf provides extensions to the VDF to allow for the display of VDF-formatted screens in the CICS operating environment.
Separate documentation is available for _beta caf.
_beta iaf provides extensions to the VDF to allow for the display of VDF-formatted screens in the IMS operating environment.
Separate documentation is available for _beta iaf.
_beta vaf provides extensions to VDF to allow VDF formatted screens to be displayed in a native VTAM environment.
Separate documentation is available for _beta vaf.
_beta report is a powerful tool for generating reports in batch.
_beta report provides a wide range of predefined reports. You can also design your own reports to meet special requirements.
Separate documentation is available for _beta report.
The BSA Service Manager enables dynamic control of the products in the running system. It displays the running activities and connections and facilitates the maintenance and support of functions. The functionality is integrated into an online application and can run within a product ISPF online application, or can be used as a separate ISPF application.
Separate documentation is available for the BSA Service Manager.