| Author |
Messages |
|
SuperUser
 
Posts:26
 |
| 10/01/2003 9:35 AM |
|
Open Issue 11817634/2
Title: DAR: PRE/POST IDENTIFY RETURN CODE Opened: Apr 22, 2002
Contact: Phone:
Company: 181513 - RAYMOND JAMES & ASSOCIATES INC
Product: TNGASO Release: 6.61
Priority: 4 OS: WIN2000
Technician: ACTION:
Languages: ENGLISH
-------------------------------------------------- ------------------------------
Apr 29, 2002 11:55
-------------------------------------------------- ------------------------------
Definition:
win 2000, Arcserve 6.61 build ??
Client wants to use a pre post option. This option will run an application
that will search for a file. If the file is found then he wants the back up
to run. if the file is not found then he does not want the job to run.
See this entry from original issue for full details:APR 18 2002 10:54
Resolution:
Issue Activity:
Apr 29, 2002 11:29 STAR STAR
ccn: 11817634;02
-----Original Message-----
From: Dellunto, Alan
Sent: Monday, April 29, 2002 11:22 AM
To: pcs@ca.com
Subject: 11817634
ccn: 11817634;02
We at Raymond James are trying to automate a manual processes when it comes
to backups. We presently have a few instances were we have people sending
emails as notification to start backups. The reason is we need to shut down
the SQL service before we begin the specific backups. The pre/post command
allows someone to watch a batch file and depending on the setting in the
pre/post command will trigger the backup to run. So for example I can
schedule a backup to run at 8:00 PM and set the pre/post command to watch a
specific batch file. I also set a setting for the error code on the batch
file to be a 0. So when the bat file completes with error code 0 the backup
will start. So basically the only error checking here is to see if the DOS
prompt hangs or if it doesn't. If it doesn't, you say the error code is 0
if the DOS prompt hangs it is an error code 1. If the DOS prompt doesn't
hang but comes back with an error you still consider that a 0 because it
didn't hang.
What we are suggesting is allowing us to watch an application and allow the
backups to react to a completion code. I was told that this would be
unlikely as it would effect a lot of existing customers. I disagree with
this. Let me explain, all that would have to happen is that you would have
an additional parameter that works along with the setting for the 0 error
code. The extra parameter would be used when the batch file competes with
an error code of 0 but has an error. An example would be another field in
the setting that allows the user to say if there are errors/no errors. So
if I left the setting to errors everything would work exactly as it is right
now. If I chose no error you would actually be looking at the errors that
would be associated with the output of the batch file. So you could
architecturally let customers that use it the way they are now continue but
let other customers key off the extra parameter. This is really hard to
explain in an email but I would be happy to talk to some one about the idea.
The whole idea here comes from the way CA uses completion codes on Unicenter
Workload to tell if a job really works or not.
Richard Carlson
Apr 29, 2002 11:55 STAR STAR
ccn: 11817634;02
We at Raymond James are trying to automate a manual processes when it comes
to backups. We presently have a few instances were we have people sending
emails as notification to start backups. The reason is we need to shut down
the SQL service before we begin the specific backups. The pre/post command
allows someone to watch a batch file and depending on the setting in the
pre/post command will trigger the backup to run. So for example I can
schedule a backup to run at 8:00 PM and set the pre/post command to watch a
specific batch file. I also set a setting for the error code on the batch
file to be a 0. So when the bat file completes with error code 0 the backup
will start. So basically the only error checking here is to see if the DOS
prompt hangs or if it doesn't. If it doesn't, you say the error code is 0
if the DOS prompt hangs it is an error code 1. If the DOS prompt doesn't
hang but comes back with an error you still consider that a 0 because it
didn't hang.
What we are suggesting is allowing us to watch an application and allow the
backups to react to a completion code. I was told that this would be
unlikely as it would effect a lot of existing customers. I disagree with
this. Let me explain, all that would have to happen is that you would have
an additional parameter that works along with the setting for the 0 error
code. The extra parameter would be used when the batch file competes with
an error code of 0 but has an error. An example would be another field in
the setting that allows the user to say if there are errors/no errors. So
if I left the setting to errors everything would work exactly as it is right
now. If I chose no error you would actually be looking at the errors that
would be associated with the output of the batch file. So you could
architecturally let customers that use it the way they are now continue but
let other customers key off the extra parameter. This is really hard to
explain in an email but I would be happy to talk to some one about the idea.
The whole idea here comes from the way CA uses completion codes on Unicenter
Workload to tell if a job really works or not.
Richard Carlson
ATG Technician
IT Operations (12J)
Raymond James and Assoc., Inc.
(727) 573-3800 ext. 10333
(800) 248-8863 ext. 10333
rcarlson@it.rjf.com
|
|
|
|
|