Cannot Assign GDG File With Relative Version (Doc ID 1502359.1)

Last updated on OCTOBER 23, 2023

Applies to:

Symptoms

When using following JOB, m_FileAssign fails due to relative version number was not found.

The problem happen with following case,

  1)Use GDG DB management.
  2)Define max generation number is 1 using m_GenDefine -s 1
  3)Use MT_GDG_COMMIT=STEP
  4)Specify relative version which is created before step.

  m_JobBegin -j GDGMAX1 -s START -v 2.0 -c A
  while true ;
  do
         m_PhaseBegin
         case ${CURRENT_LABEL} in
  (START)
         m_GenDefine -s 1 ${DATA}/ORACLE.DEMO.GDGF88
         JUMP_LABEL=STEP1
         ;;
  (STEP1)
         m_FileAssign -d NEW,CATLG,DELETE -g +1 FILE1
  ${DATA}/ORACLE.DEMO.GDGF88
         m_ProgramExec IEFBR14
         JUMP_LABEL=STEP2
         ;;
  (STEP2)
         m_FileAssign -d SHR -g +1 FILE01 ${DATA}/ORACLE.DEMO.GDGF88
         m_ProgramExec IEFBR14
         JUMP_LABEL=END_JOB
         ;;
  (END_JOB)
         break
         ;;
  (*)
         m_RcSet ${MT_RC_ABORT:-S999} "Unknown label : ${CURRENT_LABEL}"
         break
         ;;
  esac
  m_PhaseEnd
  done
  m_JobEnd

  
  The error message:
  

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.