Starting the Apply program (Linux, UNIX, Windows, z/OS)

You can start an instance of the Apply program to begin applying data to your targets.

Before you begin

Ensure that:

Connections are configured to all necessary replication servers.
You have the proper authorization.
The control tables that contain the source and control data for the desired Apply qualifier are created.
The replication programs are configured.
z/OS®: You manually bound the Apply program to all necessary servers.
Linux, UNIX, Windows: A password file exists for end-user authentication for remote servers.

Also, make sure that the following conditions are met:

At least one active subscription set exists for the Apply qualifier and that the subscription set contains one or more of the following items:
- Subscription-set member
- SQL statement
- Procedure
All condensed target tables must have a target key, which is a set of unique columns, either a primary key or unique index, that the Apply program uses to track which changes it replicates during each Apply cycle. (Non-condensed CCD tables do not have primary keys or unique indexes.)

About this task

When you start the Apply program, you can also specify startup parameters.

Procedure

Use one of the following methods:

Option Description

Option	Description
asnapply system command	Use this command to start Apply.
z/OS console or TSO	On z/OS, you can start the Apply program by using JCL or as a system-started task. You can specify new invocation parameter values when you start an Apply program with JCL. z/OS has a 100-byte limit for the total length of parameters that you can specify in the PARMS= field. To overcome this limitation, replication programs now allow you to specify as many additional parameters as needed in the SYSIN data set. When the SYSIN DD statement is included in the invocation JCL, the Apply program automatically concatenates what is specified in the SYSIN data set to the PARMS= parameters. You can only specify Apply parameters in the SYSIN data set. Any LE parameters must be specified in the PARMS= field or in LE _CEE_ENVFILE=DD, followed by a slash(/). Example: `//* asterisk indicates a comment line // APP EXEC PGM=ASNAPP,PARMS='LE/Apply parameters' //* Parameters can be any or no LE parameters and any or //* no Apply parameters //SYSIN DD * //* additional Apply parameters, one or more //* parameters on each line APPLY_SERVER=DSN!! APPLY_QUAL=APPCAT DEBUG=Y LOGSTDOUT=N`
Windows services	You can create a DB2® replication service on the Windows operating system to start the Q Apply program automatically when the system starts.

asnapply system command

Use this command to start Apply.

z/OS console or TSO

On z/OS, you can start the Apply program by using JCL or as a system-started task. You can specify new invocation parameter values when you start an Apply program with JCL.

z/OS has a 100-byte limit for the total length of parameters that you can specify in the PARMS= field. To overcome this limitation, replication programs now allow you to specify as many additional parameters as needed in the SYSIN data set.

When the SYSIN DD statement is included in the invocation JCL, the Apply program automatically concatenates what is specified in the SYSIN data set to the PARMS= parameters. You can only specify Apply parameters in the SYSIN data set. Any LE parameters must be specified in the PARMS= field or in LE _CEE_ENVFILE=DD, followed by a slash(/).

Example:

//* asterisk indicates a comment line
// APP EXEC PGM=ASNAPP,PARMS='LE/Apply parameters'
//* Parameters can be any or no LE parameters and any or
//* no Apply parameters
//SYSIN DD *
//* additional Apply parameters, one or more
//* parameters on each line
  APPLY_SERVER=DSN!! APPLY_QUAL=APPCAT 
  DEBUG=Y LOGSTDOUT=N

Windows services You can create a DB2® replication service on the Windows operating system to start the Q Apply program automatically when the system starts.

After you start the Apply program, it runs continuously (unless you used the copyonce startup parameter) until one of the following events occurs:

You stop the Apply program by using the Replication Center or a command.
The Apply program cannot connect to the Apply control server.
The Apply program cannot allocate memory for processing.

To verify whether an Apply program started, use one of the following methods:

z/OS: If you are running in batch mode, examine the z/OS console or z/OS job log for messages that indicate that the program started.
Examine the Apply diagnostic log file (apply_server.apply_qualifier.APP.log on z/OS and db2instance.apply_server.apply_qualifier.APP.log on Linux, UNIX, and Windows) for a message that indicates that the program is capturing changes.
Check the IBMSNAP_APPLYTRACE table for a message that indicates that the program is applying changes.
Use the Apply Messages window in the Replication Center to see a message that indicates that the program started. To open the window, right-click the Apply qualifier in the contents pane that identifies the Apply program whose messages you want to view and select Reports > Apply Messages.