[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

1763.0. "How to abort an Export command ?" by ANNECY::BONNIER (Jean-Luc ... EIC/T&N Annecy France) Tue Nov 05 1991 09:57

When an EXPORT command has been posted, what is the impact of
stopping the batch job with the STOP/ENTRY=xxx ?

without having done DELETE EXPORTING ... before.

Is the Rdb file consistent ?

Thanks.
Jean-Luc

T.RTitleUserPersonal
Name
DateLines
1763.1use Suspend Exporting or Delete Exporting commandTOOK::SHMUYLOVICHTue Nov 05 1991 17:3120
	In order to stop Export command you should use Suspend Exporting
or Delete Exporting commands.
	The Suspend Exporting command stops exporting request and turns it
into "suspended" state which means that no action will be performed (no more
data will be written into the rdb file) until this requests is activated. 
Suspended request can be activated by Resume Exporting command.
	The Delete Exporting command stops and deletes exporting requests.
If you want to continue exporting for the same target entity you must
create a new exporting request using Export command.

	When you stop batch job (background process) you kill the process
which gets data and writes them into the rdb file. This does not effect 
existing exporting requests and rdb file. When you restart the background
process all active exporting requests automatically continue their execution
(continue collecting data and writing them in rdb).

	Sam