DB2 Replication Guide and Reference
An administrator can use the commands in the following sections to perform
the following Apply for MVS tasks:
- Starting
- Scheduling
- Stopping
You can submit the commands from TSO or an MVS console.
Before you start the Apply program, ensure that:
- The control tables are defined.
- At least one subscription is created and activated.
- The Apply program package is created.
See the Apply for MVS program directory and Chapter 22. Sample Invocation JCL for information on BIND programs to create the Apply program
packages. You must bind the Apply program to both the source and target
databases.
- You must customize and execute the following JCL:
- The link edit sample JCL
- The sample JCL to build the VSAM message file
- The Apply bind sample JCL
- The Apply Run/Invocation sample JCL
- For DB2 for MVS/ESA, you need to have SYSADM or DBADM privileges at the
source, control, and target server. You must also have the proper
authorization to run the Apply program, including EXECUTE privileges for Apply
program packages.
For DB2 Universal Database, you must have DBADM or CONTROL or SELECT
authority that meets all requirements for defining a replication source and
target.
After you start the Apply program, it runs continuously until:
- You stop it in an orderly way.
- An unexpected error or failure occurs.
To start the Apply for MVS program:
- 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. Invocation JCL is
included with the Apply for MVS product.
An example of this line in the invocation JCL is:
//ASNARUN EXEC PGM=ASNAPVnn,PARM='Apply_qual DB2_subsystem_name DISK'
Where nn indicates the version of Apply required for a given
version of DB2 for MVS:
- For the Apply program running on DB2 for MVS Version 3 Release 1,
nn is 23
- For the Apply program running on DB2 for MVS Version 4 Release 1,
nn is 24
- For the Apply program running on DB2 for OS/390 Version 5 Release 1,
nn is 25
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. The Apply qualifier is case
sensitive and must match the value of APPLY_QUAL in the subscription set
table. This is a positional parameter that is required as the first
parameter.
|
- DB2_subsystem_name
- 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.
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.
|
- SLEEP (default)
- Specifies that the Apply program is to go to sleep if no new subscriptions
are eligible for processing.
- NOSLEEP
- Specifies that the Apply program is to stop if no new subscriptions are
eligible for processing. This keyword parameter is optional.
|
- DELAY(n)
- Where n=0, 1, 2, 3, 4, 5, or 6. Specifies the delay time
(in seconds) at the end of each Apply program cycle when continuous
replication is used. This keyword parameter is optional.
- DELAY(6) (default)
- Specifies a delay time of 6 seconds at the end of each Apply program cycle
when continuous replication is used.
|
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:
- Create a procedure that calls Apply for MVS in the PROCLIB.
- Modify the ICHRIN03 RACF module (or appropriate definitions for your MVS security package) to
associate the procedure with a user ID.
- 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.
Enter the following command from TSO or an MVS console to stop the Apply
for MVS program:
>>-P--jobname--------------------------------------------------><
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
[ DB2 List of Books |
Search the DB2 Books ]