IBM Books

Replication Guide and Reference


Operating Apply for MVS

A replication administrator can use the commands in the following sections to perform the following Apply for MVS tasks:

You can submit the commands from TSO or an MVS console.

Before You Start the Apply Program

Before you start the Apply program, ensure that:

Starting Apply for MVS

After you start Apply, it runs continuously until:

To start Apply for MVS:

  1. Prepare the JCL for MVS by specifying the appropriate optional invocation parameters in the PARM field of the ASNARUNnn command. Tailor the JCL to meet your site's requirements. Sample JCL appears in the program directory for Apply for MVS.

    An example of this line in the invocation JCL is:

    //ASNARUN EXEC PGM=ASNAP,PARM='Apply_qual DB2_subsystem_name DISK'
    

    Table 10 defines the required and optional positional parameters.


Table 10. ASNARUN Invocation Parameter Definitions

Parameter
Definition

Apply_qual
Specifies the Apply program qualifier the Apply program instance uses to identify the subscriptions to be served. This is a positional parameter that is required as the first parameter.

DB2_subsystem_name
The default is DSN. This is a positional parameter that is required as the second parameter.

Control_server_name
Specifies the name of the server where the replication control tables will reside. If you do not specify this optional positional parameter, the default is the current server.

LOADXit
Specifies that the Apply program is to invoke ASNLOAD, an exit program that can call an IBM or multivendor utility, to initialize a target table. This keyword parameter is optional.

NOLOADXit  (default) 
Specifies that the Apply program will not invoke ASNLOAD. This keyword parameter is optional.

Currently, no utility program is available for use by ASNLOAD on DB2 for MVS.


MEMory  (default) 
Specifies that a memory file stores the fetched answer set. The Apply program fails if there is insufficient memory for the answer set. This keyword parameter is optional.

DISK
Specifies that a disk file stores the fetched answer set. This keyword parameter is optional.

INAMsg  (default) 
Specifies that the Apply program is to issue a message when the Apply program is inactive.

NOINAMsg
Specifies that the Apply program will not issue this message. This keyword parameter is optional.

NOTRC  (default) 
Specifies that the Apply program does not generate a trace.

TRCERR
Specifies that the Apply program generates a trace that contains only error information. This keyword parameter is optional.

TRCFLOW
Specifies that the Apply program generates a trace that contains error and execution flow information. This keyword parameter is optional.

NOTIFY
Specifies that the Apply program is to invoke ASNDONE, an exit program that returns control to the user when the Apply program processing ends. This keyword parameter is optional.

NONOTIFY  (default) 
Specifies that the Apply program will not invoke ASNDONE.

Scheduling Apply for MVS

Use either the $TA JES2 command or the AT NetView command to start Apply for MVS at a specific time.

To start Apply for MVS at a specific time:

  1. Create a procedure that calls Apply for MVS in the PROCLIB.

  2. Modify the ICHRIN03 RACF module (or appropriate definitions for your MVS security package) to associate the procedure with a user ID.

  3. Link edit the module in SYS1.LPALIB.

See MVS/ESA JES2 Commands for more information about using the $TA JES2 command, and See NetView for MVS Command Reference for more information about using the AT NetView command.

Stopping Apply for MVS

Enter the following command from TSO or an MVS console:

>>-P--jobname--------------------------------------------------><
 


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]