On newly created projects in test and production, when we try to pull out the log information using dsjob, we get a -1003 error. I suspect that this means that the Template is corrupt. How do we fix it?
$ dsjob -logdetail SMds02 LIR_DlySvcCshrCriteriaPfrmHst_060_Ld
Error -1003 getting details for wave 0
Status code = -1003
Thanks.
Error using dsjob to get latest log information (wave=0)
Moderators: chulett, rschirm, roy
-
Ultramundane
- Participant
- Posts: 407
- Joined: Mon Jun 27, 2005 8:54 am
- Location: Walker, Michigan
- Contact:
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Does this occur after you reset the job? There is no "template" used for dsjob. Wave number is an internal number used by DataStage to identify unique runs (for example a reset run or multi-instance runs).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
Ultramundane
- Participant
- Posts: 407
- Joined: Mon Jun 27, 2005 8:54 am
- Location: Walker, Michigan
- Contact:
wave number in dsjob -logdetail is used to identify which log to dump. -wave 0 (default) means the most current log. I have tried following a reset of the job and it still fails. This only occurs for newly created projects. That is, if I create a new project this happens now.ray.wurlod wrote:Does this occur after you reset the job? There is no "template" used for dsjob. Wave number is an internal number used by DataStage to identify unique runs (for example a reset run or multi-instance ...
-
Ultramundane
- Participant
- Posts: 407
- Joined: Mon Jun 27, 2005 8:54 am
- Location: Walker, Michigan
- Contact:
After much work and patch investigation on my part, I was able to find out that IBM backed out some changes from our Template for dsjob. I was able to build some commands to fix the Template and the new Projects.
To fix the Template:
To fix the Projects:
To fix the Template:
Code: Select all
PDIR="/ascsoft/DS752/P002_COMPOUND/patch_meijer"
## Fix DS_RESENU issue caused by IBM
rm $DSHOME/../Template/DSG_BP.O/DSR_LOG.B
cp ${PDIR}/root/DSR_LOG.B ${DSHOME}/../Template/DSG_BP.O/DSR_LOG.B
chmod 755 $DSHOME/../Template/DSG_BP.O/DSR_LOG.B
rm $DSHOME/../Template/DSG_BP.O/DSGetLogEventIds.B
cp ${PDIR}/root/DSGetLogEventIds.B ${DSHOME}/../Template/DSG_BP.O/DSGetLogEventIds.B
chmod 755 ${DSHOME}/../Template/DSG_BP.O/DSGetLogEventIds.B
rm ${DSHOME}/../Template/dsinclude/JOBCONTROL.H
cp ${PDIR}/root/JOBCONTROL.H ${DSHOME}/../Template/dsinclude/JOBCONTROL.H
chmod 755 ${DSHOME}/../Template/dsinclude/JOBCONTROL.H
$DSHOME/bin/loadfile ${PDIR}/ds_res.enu.u DS_RESENU
$DSHOME/bin/uvsh <<EOF
CATALOG DSG_BP DSGetLogEventIds DSGetLogEventIds.B LOCAL
Q
EOF
Code: Select all
PDIR="/ascsoft/DS752/P002_COMPOUND/patch_meijer"
## Fix DS_RESENU issue caused by IBM
rm $DSHOME/../Projects/${1}/DSG_BP.O/DSR_LOG.B
cp ${PDIR}/root/DSR_LOG.B ${DSHOME}/../Projects/${1}/DSG_BP.O/DSR_LOG.B
chmod 755 $DSHOME/../Projects/${1}/DSG_BP.O/DSR_LOG.B
rm $DSHOME/../Projects/${1}/DSG_BP.O/DSGetLogEventIds.B
cp ${PDIR}/root/DSGetLogEventIds.B ${DSHOME}/../Projects/${1}/DSG_BP.O/DSGetLogEventIds.B
chmod 755 ${DSHOME}/../Projects/${1}/DSG_BP.O/DSGetLogEventIds.B
rm ${DSHOME}/../Projects/${1}/dsinclude/JOBCONTROL.H
cp ${PDIR}/root/JOBCONTROL.H ${DSHOME}/../Projects/${1}/dsinclude/JOBCONTROL.H
chmod 755 ${DSHOME}/../Projects/${1}/dsinclude/JOBCONTROL.H
$DSHOME/bin/loadfile ${PDIR}/ds_res.enu.u DS_RESENU
$DSHOME/bin/uvsh <<EOF
CATALOG DSG_BP DSGetLogEventIds DSGetLogEventIds.B LOCAL
Q
EOF
cd -