Question & Answer
Question
Is the information about the NONE option for FRLOG in the CICS VSAM Recovery for z/OS (CICS VR) documentation correct? If it is not, what information is logged when NONE is specified?
I am working on a POC for the Classic change data capture (CDC) for VSAM. In order for Classic CDC to capture changes from a VSAM file, it has to be altered to have a FRLOG option.
According to the CICS VR documentation, FRLOG has NULL, NONE, REDO, UNDO, and ALL options. By default I would think FRLOG(ALL) option will give everything in the log. However when using this option, customer cannot run their batch update job after the alter. The file cannot be opened by the batch job. We were told by Classic team to use the FRLOG=NONE option and this option actually worked. I am really confused because according to the manual NONE option will not log any changes. Here is the paragraph from the manual:
NONE
Indicates the data set is eligible for VSAM batch logging, but batch logging is currently disabled for the VSAM data set. Changes made to the data set by batch applications are not logged by batch logging. If FRLOG(NONE) is specified, the data set must conform to the VSAM batch logging restrictions listed.
Answer
James, based on our chat, you are using CICS VSAM Recovery for z/OS V5.2 and InfoSphere Data Replication for VSAM for z/OS 11.3.0. When you run the batch job and have FRLOG(ALL) and LOGREPLICATE specified the batch JESMSGLG show messages:
JOB12575 +PEM0998E 49058 RQ=OPEN ER=008/135 DD=CIF DB=CIF
JOB12575 $HASP375 jobname ESTIMATE EXCEEDED BY 5,000 LINES
JOB12575 IEA995I SYMPTOM DUMP OUTPUT 235
USER COMPLETION CODE=4049 REASON CODE=00049058
TIME=08.55.47 SEQ=32814 CPU=0000 ASID=0095
PSW AT TIME OF ERROR 078D1000 95C1D210 ILC 2 INTC 0D
ACTIVE LOAD MODULE ADDRESS=15C00000 OFFSET=0001D210
NAME=BATCHPEM
DATA AT PSW 15C1D20A - 00181610 0A0DA708 000258F0
GR 0: 00000000_84000000 1: 00000000_84000FD1
2: 00000000_00049058 3: 00000000_15D8C2E8
4: 00000000_15C73AB8 5: 00000000_00000000
6: 00000000_15CB09AC 7: 00000000_15D8C2E8
8: 00000000_15C9E418 9: 00000000_00000019
A: 00000000_15C753F0 B: 00000000_15C71010
C: 00000000_15C1D634 D: 00000000_15C75558
E: 00000000_95C1D1DC F: 7F563700_00049058
END OF SYMPTOM DUMP
JOB12575 DWW269I BATCH LOGGING REQUESTED: FRLOG(ALL),LOGREPLICATE 236
SPHERE: xxxx.yyyy
REDOS: 0
UNDOS: 0
JOB12575 DWW267I VSAM BATCH REDO LOGGING FAILED. 241
ASID (IN HEX): 0095
RETURN CODE (IN HEX): 00000024
REASON CODE (IN HEX): 73050090
JOB12575 DWW268I VSAM BATCH UNDO LOGGING FAILED. 242
ASID (IN HEX): 0095
RETURN CODE (IN HEX): 00000024
REASON CODE (IN HEX): 73050090
JOB12575 IEF450I jobname STEP1 stepname - ABEND=S000 U4049 REASON=00049058 243
TIME=08.55.48
JOB12575 CSC999I JOB jobname stepname STEP1 : CC=U4049
...so to answer your questions... 1) The CICS VR topic on Enabling CICS VR VSAM batch logging needs clarification related to FRLOG(NONE) and LOGREPLICATE options being specified together. I submitted an IBM Knowledge Center update on the topic in CICSVR to update the LOG(NONE) description to be:
NONE
Indicates the data set is eligible for VSAM batch logging, but batch logging is currently disabled for the VSAM data set. Changes made to the data set by batch applications are not logged by batch logging however, if the LOGREPLICATE option and FRLOG(NONE) are specified, replication logging is performed for the VSAM sphere.
2) APAR OA44268 allowed VSAM to call CICSVR for FRLOG(NONE) and LOGREPLICATE.
I also think FRLOG(ALL) and LOGREPLICATE would work if the CICSVR server was configured for UNDO logging. I suspect the CICSVR server logs and/or z/OS SYSLOG will have some additional messages around the time of the batch job fails with the DWW269I and DWW267I and DWW268I messages. The reason code x'73050090' in the DWW267I and DWW268I just says batch logging failed.
You can also issue DFSMS command SETSMS CICSVR_UNDOLOG_CONTROL(DISPLAY CONTROL) to determine if UNDO logging is active.
Product Synonym
CICSVR CICS VR
Was this topic helpful?
Document Information
Modified date:
19 September 2019
UID
dwa1207796