Conference decwet::networker

694.0. "save return status" by TELEM::WAINRIGHT () Tue May 20 1997 15:41

	we have a file that is corrupt and we were tracing our backups
	and found that they were 'succeeding'...but of course the file
	was not any good.

	anyway my question is related to the return status from the
	save command...it appears to always be zero...is that correct
	from your knowledge of the product?

	I would have thought that a "I/O error" would translate to
	a non-zero status?


# ls -l /oracle/DDA/sapdata4/btabd_2
total 532488
-rw-r-----   1 oradda   dba      545267712 May 20 15:14 btabd.data2
#
#
# save -g mro_db /oracle/DDA/sapdata4/btabd_2
save: Using iron.gppc.dec.com as server for sulfur.gppc.dec.com
/oracle/DDA/sapdata4/btabd_2/btabd.data2
/oracle/DDA/sapdata4/btabd_2/btabd.data2: I/O error
/oracle/DDA/sapdata4/btabd_2/
/oracle/DDA/sapdata4/
/oracle/DDA/
/oracle/
/

save: /oracle/DDA/sapdata4/btabd_2  349 MB 00:02:28      6 files
# print ${?}
0
#
#
# save -qg mro_db /oracle/DDA/sapdata4/btabd_2
save: Warning - `/oracle/DDA/sapdata4/btabd_2/btabd.data2' size shrunk during save
save: Expected 545267712 bytes for `/oracle/DDA/sapdata4/btabd_2/btabd.data2', got 357220352 bytes
save: /oracle/DDA/sapdata4/btabd_2  349 MB 00:05:10      6 files
# print $?
0
#
# save -vg mro_db /oracle/DDA/sapdata4/btabd_2
save: Using iron.gppc.dec.com as server for sulfur.gppc.dec.com
save: got prototype for /
save: got prototype for /oracle/
save: got prototype for /oracle/
save: got prototype for /sapmnt/
save: got prototype for /usr/
save: got prototype for /oracle/DDA/
save: got prototype for /oracle/DDA/
save: got prototype for /oracle/DDA/
save: got prototype for /oracle/DDA/
save: got prototype for /oracle/DDA/
save: got prototype for /oracle/DDA/
save: got prototype for /oracle/DDA/
save: got prototype for /oracle/DDA/
save: got prototype for /oracle/DDA/
save: got prototype for /oracle/DDA/
save: got prototype for /oracle/DDA/
save: got prototype for /oracle/DDA/
save: got prototype for /usr/sap/
chdir(/oracle/DDA/sapdata4/btabd_2)
Name=`/oracle/DDA/sapdata4/btabd_2/', name=`/oracle/DDA/sapdata4/btabd_2/', fname=`./'
save: found protofile spec for /:
  mntasm : usr 
save: found protofile spec for /oracle/:
  mntasm : DDA 
save: found protofile spec for /oracle/DDA/:
  mntasm : sapreorg 
walk(/oracle/DDA/sapdata4/btabd_2/, ./)
walk(/oracle/DDA/sapdata4/btabd_2/btabd.data2, btabd.data2)
uasm -s /oracle/DDA/sapdata4/btabd_2/btabd.data2
/oracle/DDA/sapdata4/btabd_2/btabd.data2 file opened for AdvFS extended attrs
/oracle/DDA/sapdata4/btabd_2/btabd.data2: I/O error
uasm -s /oracle/DDA/sapdata4/btabd_2/
/oracle/DDA/sapdata4/btabd_2/ file opened for AdvFS extended attrs
Connecting directories...
dir: /oracle/DDA/sapdata4/, fstype: 3, fsid: 0
uasm -s /oracle/DDA/sapdata4/
/oracle/DDA/sapdata4/ file opened for AdvFS extended attrs
dir: /oracle/DDA/, fstype: 3, fsid: 0
uasm -s /oracle/DDA/
/oracle/DDA/ file opened for AdvFS extended attrs
dir: /oracle/, fstype: 2, fsid: 0
uasm -s /oracle/
dir: /, fstype: 2, fsid: 0
uasm -s /

save: /oracle/DDA/sapdata4/btabd_2  349 MB 00:06:38      6 files
# print $?
0

DIAGNOSTICS

  Exit Codes

  0    Normal exit.  This means that a save set was correctly created on the
       server.  Messages about individual file backup failures are warnings,
       and do not cause abnormal exit.
  1    Abnormal exit.  A save set was not correctly created on the server.

	thanks for the clarification, cause the man pages I had
	for 3.2a didn't have that additional information