Separating the Spool Files From the Main Catalog File

Using FHRedir and an allocation override rule

You can use the File Handling Redirector (FHRedir) module in combination with an allocation override rule to send the casspool control files and the spool datasets to a different Fileshare server from the one where the main catalog is stored.

There are different locations in FHRedir for the catalog and the spool files:

/f C:\ES_ERRORS\FAST_CAT_FS\CATALOG.DAT /s CATSERVER
/f C:\ES_ERRORS\FAST_CAT_FS\SMS.DAT /s CATSERVER

/f C:\ES_ERRORS\FAST_CAT_FS\spldsn.dat /s SPOOLSERVER 
/f C:\ES_ERRORS\FAST_CAT_FS\spljob.dat /s SPOOLSERVER 
/f C:\ES_ERRORS\FAST_CAT_FS\spoolmsg.dat /s SPOOLSERVER 
/f C:\ES_ERRORS\FAST_CAT_FS\spoolsub.dat /s SPOOLSERVER 
/f C:\ES_ERRORS\FAST_CAT_FS\spoolout.dat /s SPOOLSERVER

In order to send the spool files to the same Fileshare server as the spool control files and store all these files together, create and apply the following allocation override rule:

# RECORDTYPE = S 

RULE:
	- CONDITION:	RECORDTYPE
	  VALUE:		S
	SUBDIRECTORY:	$$SPOOLSERVER\SPOOL\
---

Using the MVSSPOOLDIR environment variable

You can use the MVSSPOOLDIR environment variable to specify the location of all spool control files. If you set this variable to a value that contains the name of a Fileshare server (for example, $$SPOOLSERVER), you do not need to specify the FHRedir settings mentioned in the previous approach because all control files would be directed to the Fileshare server.

Using multiple catalogs and allocation override rules

You can use multiple catalogs in combination with some allocation override rules to direct all spool files to a separate location which could be a Fileshare server. See Multiple Catalog Support for more details.