New options requested for Ims2disk.sh

Ims2disk.sh script has remain largely unchanged since 2010. There are standard desired behaviors that would increase usability of the script while simplifying the configuration in the servers cron.

Current standard functionality of Ims2disk.sh is to:

1. Complete a full dump of the ims db from LOCAL

2. Load the full dump into MAINT

Requesting 3 new options for Ims2disk.sh:

1. Add a new Ims2disk.sh flag that would force a 'dump tran ims' just prior to full dump

1. Why? When full dump/load takes long time (>12 hrs) on systems with large db and slow NAS - the logsegment in LOCAL is at risk of filling up.

2. Add a new flag to Ims2disk.sh that would automatically run an incremental dump.

1. Why? This would eliminate lengthy cron jobs with multiple scripts in a single line. Instead of the standard functionality listed above, the new sequence could be:

   1. Complete a full dump of ims from LOCAL

   2. Complete an incremental dump from LOCAL

   3. Load full dump to MAINT

   4. Load first incremental dump to MAINT

3. Add a new flag to Ims2disk.sh that calls Execdbcc.sh when completed.

1. Why? This would simplify cron and run the dbcc checks automatically post full backup without needing to 'guess' when the full backup completes to schedule the dbcc.

<EOM>