Validate data transmission to SARFSS printers - OM View and OM Deliver

Products

• OM View
• OM Deliver

Issue/Introduction

Confirm that OM View or OM Deliver data correctly routes to FSS printers by verifying the configuration and active started tasks.

This validation ensures that the defined SARFSS collectors are actively processing reports from the SARINDEX.

Environment

z/OS

OM View

OM Deliver

Resolution

To validate that data is being sent to the FSS printers, there are a number of ways to verify:

1. Check the SARFSS Started Task (STC) Logs: 
   
   
   1. Review the SARLOG and SYSPRINT output for the SARFSS started task (e.g., PRT####).
   2. Successful initialization and report processing are logged here.
      
      
2. Verify the PPOPTION Dataset: 
   
   
   1. Confirm the SARFSS PROC points to the correct PPOPTION member. For example:
   2. //PRT#### DD DISP=SHR,DSN=####.VIEW.PPOPTION(PRT####)
   3. Ensure the TYPE parameter (VIEW, ACIF, or PDF) matches the report type being sent.
      
      
3. Monitor JES Output: Verify the status of the virtual printers in JES. Use the following command to check the mode and class:
   
   
   1. $DU,PRT####
   2. Ensure MODE=FSS and the FSS name matches your SARFSS configuration.
      
      
4. Confirm Database Connectivity:
    
   
   1. Ensure the SARINDEX DD in the SARFSS PROC points to the same database being used by the primary View/Deliver regions:
   2. //SARINDEX DD DISP=SHR,DSN=####.SARINDEX
   
   
   
5. Check for SMF type 6 records:
   
   
   1. SARFSS generates a standard z/OS SMF Type 6 (Output Writer) record. If there are no type 6 records present, SARFSS is not being used.

Additional Information

For more details on setting up the collector, see Configure the FSS Collector.