FMO

FMO's architecture comprises several key components designed to provide efficient and secure PDS member management on z/OS. The core component is the FMO engine, responsible for processing commands and managing PDS operations. This engine interacts with the z/OS system through standard system calls and JCL execution.

The second major component is the archiving module, which automates the process of identifying and archiving unused PDS members. This module uses configurable policies to determine which members to archive, based on factors such as age and usage. The archiving process involves moving members to a designated archive dataset, freeing up space in the original PDS.

The REUSE command triggers the space reclamation process. The third key component is the security integration module, which interfaces with the z/OS security manager (RACF) to enforce access control at the member level. This module ensures that only authorized users can access specific members.

The SMF logging component records all member access events, providing a detailed audit trail. The LLA update module ensures that the system always has access to the latest versions of members. Communication between components occurs through z/OS system services and data sets.

There are no specific network ports required for FMO's operation. The configuration files are used to define archiving policies, security settings, and other operational parameters. The LIST command provides a view of member details.

The UPDATE command ensures LLA is current.