Job control statements for CECVSMLD
Use these job control statements to run the CECVSMLD VSAM log delta utility.
Sample JCL for running the VSAM log delta utility is provide in USERSAMP member CECVSLDU.
Table 1 shows the statements and their use. Table 2 shows the parameter keywords and their values.
Statement | Use |
---|---|
EXEC | Specifies the program name (PGM=CECVSMLD) or, if the job control statements reside in a procedure library, the procedure name. |
PARM | None; parameters are specified through the CECPARMS DD. |
STEPLIB | Specifies the location of the CECVSMLD executable program, which is found in SCACLOAD. |
SYSPRINT | Defines a sequential data set for debug messages. The data set can be written to a system output device, a tape volume, or a DASD volume. |
CECADODL | Defines a sequential data set for output messages. The data set can be written to a system output device, a tape volume, or a DASD volume. |
MSGCAT | Specifies the location of the Classic message catalog, which is distributed as SCACMSGS. |
CECPARMS | DD statement that allows you to specify keyword=value pairs of parameters. Any line that begins with an asterisk (*) character is ignored as a comment. |
OLDFILE | DD statement where you provide earlier version of the VSAM data. |
NEWFILE | DD statement where you provide the updated version of the VSAM data. |
Keyword | Value | Explanation |
---|---|---|
APPLID | Follows z/OS® job name rules:
Example: CECAPPL1 |
You can name your job or accept the default of the job name. This value is used when log blocks are written and takes the place of a CICS® region name. This must be a unique identifier in your replication log. Do not use the name of an existing CICS region. This value might be used to group changes from the job by replication, so you need a unique value to avoid interfering with other replication activity. |
DEBUG | TRUE | [FALSE] | The default is FALSE. Enable debugging at the direction of IBM® support. |
ESDSLDXT | Load module name for the logical delete exit. This name must follow load module naming
standards. Example: CECVSMLX |
You code a logical delete exit when you have ESDS data and might have OLDFILE RBA values that do not exist in the NEWFILE so the VSAM log delta utility would normally create a delete record. ESDS does not allow delete so the exit provides you a mechanism to update the record image so it reflects a logical delete in the target replica. |
LOCAL | [TRUE] | FALSE | Times that are displayed in the CECADODL DD should be in LOCAL time of the system where
CECVSMLD runs when TRUE and in GMT time when FALSE. If no value is specified, the default is TRUE. |
MODELDD | DDname This value must follow name restrictions for DD names. Example: LOGINFDD |
Name of the DD that reflects the VSAM cluster to use during catalog search when OLDFILE or NEWFILE reference DD DUMMY or a sequential data set name. This allows you to provide an alternate DD for catalog attributes when you use a non-VSAM data set name. |
RETMSGMS | This should be a numeric value in the range of 1 to 2,147,483,647. Example: RETMSGMS=10000 |
The default is 10000. The value is specified in milliseconds. After each retry that counts against the retry limit (see RETRY keyword), if the total elapsed retry time exceeds this value in milliseconds, message CECY0273I is written to the CECADODL DD with information about retry progress. The message is re-issued while the retry processing continues each time this period elapses. |
RETRY | This should be a numeric value in the range of 1 to 2,147,483,647. Example: RETRY=100 |
When a retryable condition occurs it is retried up to this number of times before being
considered an error. Each attempt to write a new block receives the full number of retries that were
specified and the write for that block is retried at most this many times while a retryable
condition is returned. Retryable conditions are z/OS system logger codes that are returned from an IXGWRITE attempt. Retryable codes are return code 8 with reason codes in the set 85D, 860-865, 867, 868, and 891. When codes 8/868 are received they are retryable, but this specific code set does not count against the retry limit so this code set is retried indefinitely until the staging data set is formatted. You can combine the RETRY and WAIT keywords to determine a maximum retry period for retryable conditions. The defaults result in about 10 seconds for the possible retry period. |
RPTONLY | TRUE | [FALSE] | The default is FALSE. Provides minimal reporting of the comparison when set to TRUE without connecting to or logging changes in the replication log. |
TASKID | An arbitrary value that is set to simulate the CICS
task number that is associated with changes that are logged by the utility. This should be a numeric value in the range of 1 – 134,217,727 Example: TASKID=12345 |
The value is converted to packed decimal internally and might be used to group changes from
the job by replication within the APPLID. Your input is returned in packed decimal, hexadecimal format with the sign nibble appended when displayed by the VSAM log delta utility. |
TERMID | An arbitrary value set to simulate the CICS terminal
associated with changes logged by the utility. This should be an alphabetic, four-character value. Example: TERMID=CEC1 |
This value might be used to group changes from the job by replication within the APPLID. It is recommended you use a value with the CEC product prefix to help identify changes from the VSAM log delta utility. |
TRANID | An arbitrary value set to simulate the CICS
transaction that is associated with changes that are logged by the utility. This should be an alphabetic, four-character value. Example: TRANID=CECL |
This value might be used to group changes from the job by replication within the APPLID. It is recommended that you use a value with the CEC product prefix to help identify changes from the VSAM log delta utility. |
WAIT | This should be a numeric value in the range of 1 to 2,147,483,647. Example: WAIT=100 |
The default is 100. The value is specified in milliseconds. When a retryable condition occurs it is retried after a wait of this number of milliseconds. You can combine the RETRY and WAIT keywords to determine a maximum retry period for retryable conditions. The defaults result in about 10 seconds for the possible retry period. |