Cluster Information - NUFLCL

The Cluster Information Report provides a comprehensive listing of all data clusters used within the system. Each entry describes a cluster's subsystem, identifier, purpose, associated dataset, type, key, and length. This report is essential for system analysts who need to understand data architecture and dependencies.

Selection Criteria

When generating the Cluster Information Report, users can filter the data using the following selection criteria available on the NUFLCL screen:

Field	Description
01 Subsystems	Filter clusters by subsystem (e.g., AR, GL, PY, AP).
02 Clusters	Specify particular cluster identifiers to include.
03 Subsystem/Cluster	Combine subsystem and cluster filters for more precise selection.
04 Data Set Names	Filter by specific dataset names (e.g., AR-ACCT-MSTR, GLB-BUDG-MSTR).
05 Data Set Type	Filter by dataset type: Master (M), Detail (D), Auxiliary (A), Parameter (P), External (X).

Report Header Details

Each page of the report includes:

Backup Taken: Timestamp of the data snapshot (e.g., 20241114)
Report Date: Date and time of report generation (e.g., SEP 03, 2025, 11:37 AM)
Requestor: The user who initiated the report (e.g., JENNIFER)
Job Info: Includes job number, program ID, and report ID (e.g., SY400 <1.43>, NUFLCL01)
Location: System or department location (e.g., BI-TECH)

Column Definitions

Each row in the report contains the following columns:

Column	Description
Subs	Subsystem code (e.g., AR, GL, PY, AP)
Clust	Cluster identifier (e.g., ACCT, ACT, AID)
Description	Brief description of the cluster's purpose
Data Set	Name of the associated dataset or master file
Type	Type of dataset: `M` for Master, `D` for Detail, `A` for Auxiliary, `P` for Parameter, `X` for External
Key	Key type or identifier used in the dataset (e.g., `ID`, `NUM`, `CD`)
Length	Length of the key field (numeric value)

How to Use this Report

Locate Cluster Information
1. Use the Clust and Description columns to find clusters relevant to your module or subsystem.
Understand Data Relationships
1. The Data Set and Type columns help identify whether the cluster is a master record, detail record, or auxiliary data.
Validate Key Structures
1. Use the Key and Length columns to verify key formats and ensure consistency across modules.
Troubleshoot or Audit
1. When debugging or auditing data flows, refer to this report to trace which clusters are involved and how they are structured.

Example:

AR ACCT Acct Information AR-ACCT-MSTR M 218

Subsystem: AR (Accounts Receivable)
Cluster: ACCT
Description: Acct Information
Dataset: AR-ACCT-MSTR
Type: Master
Key Length: 218