Identifying spooled files for replication - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Administrator Reference
Copyright
2023
First publish date
1999
ft:lastEdition
2024-05-07
ft:lastPublication
2024-05-07T13:36:02.962500

Spooled files are a fully supported object type in MIMIX and can be included or excluded from replication. It is important to consider which spooled files must be replicated and which should not. Some output queues contain a large number of non-critical spooled files and probably should not be replicated. Most likely, you want to limit the spooled files that you replicate to mission-critical information. It may be useful to direct important spooled files that should be replicated to specific output queues instead of defining a large number of output queues for replication.

When an output queue (*OUTQ) identified by a data group object entry is replicated, any active writers associated with the *OUTQ on the target system are ended and restarted if necessary. Spooled files associated with the *OUTQ are not automatically replicated because the default values for Replicate spooled files is *NO. When you specify *ALL, *OUTQ or *SPLF for the Object type field and specify *YES for Replicate spooled files, then the Spooled file criteria (SPLF) parameter allows you to fine-tune the selection by specifying values for the three elements: Spooled file name, Job name, and Job user. When MIMIX processes an output queue that is identified by an object entry with the appropriate settings, and when a more specific exclude entry for spooled files is not defined, then all spooled files for the output queue (*OUTQ) are replicated by system journal replication processes. Table 11 identifies the values required for spooled file replication.

Table 1. Data group object entry parameter values for spooled file replication

Parameter or Element

Value

Object type (OBJTYPE)

*ALL, *OUTQ, or *SPLF1

Replicate spooled files (REPSPLF)

*YES

Spooled file criteria (SPLF)

Elements:

  • Spooled file name

  • Job name

  • Job user

*ALL, generic name, name

1When creating an entry to exclude spooled files from replication, the only valid object type is *SPLF

When an output queue is selected for replication and the data group object entry specifies *YES for Replicate spooled files, MIMIX ensures that the values *SPLFDTA and *PRTDTA are included in the system value for the security auditing level (QAUDLVL). This causes the system to generate spooled file (T-SF) entries in the system journal. When a spooled file is created, moved, deleted, or its attributes are changed, the resulting entries in the system journal are processed by a MIMIX object send job and are replicated.

Table 12 shows an example for a data group object entry that will replicate all objects and spooled files for a library. This entry will not replicate the library.

Table 2. Replicate all objects and spooled files using one data group object entry.

Source Library

Object Type

Object Name

Attribute

Replicate Spooled Files

Spooled File Criteria

Process Type

  Spooled file name Job name Job user  

LIBA

*ALL

*ALL

*ALL

*YES

*ALL

*ALL

*ALL

*INCLD

The first data group object entry listed in Table 13 will replicate all objects and spooled files in a library. This entry will not replicate the library. The second data group object entry excludes the spooled files in the library that have names starting with QPJOB.

Table 3. Replicate all objects and spooled files in a library and exclude spooled files that have names start­ing with QPJOB.

Source Library

Object Type

Object Name

Attribute

Replicate Spooled Files

Spooled File Criteria

Process Type

          Spooled file name Job name Job user  

LIBA

*ALL

*ALL

*ALL

*YES

*ALL

*ALL

*ALL

*INCLD

LIBA

*SPLF

*ALL

*ALL

*YES

QPJOB*

*ALL

*ALL

*EXCLD

Table 14 shows an example of the data group object entries needed to replicate all output queues in a library and to only replicate the spooled files in the library named IMPORTANT.

Table 4. Replicate output queue objects in the library, except 1.

Source Library

Object Type

Object Name

Attribute

Replicate Spooled Files

Spooled File Criteria

Process Type

         

Spooled file name

Job name Job user  

LIBA

*OUTQ

*ALL

*ALL

*NO

-

-

-

*INCLD

LIBA

*SPLF

*ALL

*ALL

*YES

IMPORTANT

*ALL

*ALL

*INCLD

A replicated spooled file is uniquely identified by its spooled file name and number, the three-part name of the job that produced the spooled file (name/user/number), the name of the system on which the job that created the spooled file ran, and the date and time when the spooled file was created. When configuring data group object entries, the system or creation time stamp are not specified.

Activity entries include all of the fields for uniquely identifying a spooled file. Commands available for comparing and synchronizing objects that identify spooled files support fields for specifying the creating system and time stamp so that a unique spooled file can be identified.