Tuxedo Application Runtime for CICS and Batch 12cR1: ACCLOCK File Remains Lock Information In Some Cases
(Doc ID 1560352.1)
Last updated on OCTOBER 30, 2024
Applies to:
Oracle Tuxedo Application Runtime for CICS and Batch - Version 12.1.1.0 and laterInformation in this document applies to any platform.
Symptoms
When using following pattern, file lock information remains and never cleared.
m_FileAssign -d NEW,CATLG -S ${DATA}/BASE.GDG FILE1 ${DATA}/NEW.FILE
artjeadmin -l result:
00040|< 00013|<
or
m_FileRename ${DATA}/APP.GDG.DEF ${DATA}/APP.GDG.DEF.BAK
artjeadmin -l result:
And if LABEL is not defined, also lock will not be cleared.
#!/usr/bin/ksh
m_JobBegin -j JOB001 -s START -v 2.0 -c A
while true ;
do
m_PhaseBegin
case ${CURRENT_LABEL} in
(START)
JUMP_LABEL=STEP1
;;
(STEP1)
# JUMP_LABEL=STEP2
;;
(STEP2)
m_FileAssign -d SHR FILE1 $DATA/app
m_FileAssign -d OLD FILE2 $DATA/app2
JUMP_LABEL=END_JOB
;;
(END_JOB)
break
;;
(*)
m_RcSet ${MT_RC_ABORT:-S999} "Unknown label : ${CURRENT_LABEL}"
break
;;
esac
m_PhaseEnd
done
m_JobEnd
00043|<Changes
Cause
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
Symptoms Changes Cause Solution References