The *SCHEDULECMD commands are launched via the command interpreter
specified by the ComSpec environment variable, which points to the cmd.exe
file on Windows NT systems. cmd.exe supports the launch of scripts and
binary executables ("programs"). Therefore, *SCHEDULECMD can be used to
launch scripts as well as executable modules.
APAR IC40249 is suspect, as it is fixed in 5.2.4. In particular, even if
the specified command were invalid, I would expect to see a message in the
dsmsched.log file indicating that it is attempting to launch the command.
If that isn't the issue, then a thorough examination of the TSM
environment needs to be made to understand what is happening:
- Server-side client option sets that might impact PRESCHEDULECMD
- Definitions of schedules associated with this node, in particular the
OPTIONS setting
- Firm verification of the client options file that is being used by the
scheduler (confirm that the scheduler is using the options file you think
it is using)
- Verification of the client options file to ensure that there are not any
duplicate options that might be causing a conflict.
- Try running "dsmc query options *schedulecmd" using the same options
file and node name that the scheduler is using, to verify that TSM is
seeing the option correctly.
- Examine dsmerror.log for any related error messages.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
IBM Tivoli Storage Manager support web page:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 2005-11-07
11:13:07:
> Hi,
>
> PreschedCMD starts a program, not a plain file.
>
> The last line in OPT file should be:
>
> Preschedulecmd "C:\WINNT\SYSTEM32\cmd.exe /C D:
> \Hyperion\Export\Scripts\EssExport_Schedule.bat"
>
> Note, the TSM must be told which program is to be started,
> in my environment the line would be:
> Preschedulecmd "C:\prog\JPSoft\4nt.exe /C D:
> \Hyperion\Export\Scripts\EssExport_Schedule.bat"
>
> and TSM cannot predict know what interpreter shall be used unless
> you tell him.
>
>
> Well, I´d still await an error messag in log files anyway..
>
> regards
> Juraj
>
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im
> > Auftrag von Paul Van De Vijver
> > Gesendet: Montag, 07. November 2005 14:31
> > An: ADSM-L@VM.MARIST.EDU
> > Betreff: Preschedulecmd not executed
> >
> > Hi,
> >
> > Can anybody tell me why the next preschedulecmd is not exectuted ?
> > I have no idea what can be wrong.
> >
> > Backup finishes ok, but preschedulecmd has not been executed
> > and there is no trace at all from the preschedulecmd in the
> > dsmsched.log or dsmerror.log
> >
> > The 'scheduler' service was restarted before the backup was initiated
> >
> > Thanks for any info,
> >
> > Paul
> >
> > TSM client V5.2.3.0 (on Windows 2003)
> > TSM Server V5;2.6.0 (on Z/OS mainframe)
> >
> > Last line in DSM.OPT
> >
> > Preschedulecmd D:\Hyperion\Export\Scripts\EssExport_Schedule.bat
> >
> > Extraction dsmsched.log :
> >
> > 06.11.2005 03:25:32 Next operation scheduled:
> > 06.11.2005 03:25:32
> > ------------------------------------------------------------
> > 06.11.2005 03:25:32 Schedule Name: @137273
> > 06.11.2005 03:25:32 Action: Incremental
> > 06.11.2005 03:25:32 Objects:
> > 06.11.2005 03:25:32 Options:
> > 06.11.2005 03:25:32 Server Window Start: 03:21:20 on 06.11.2005
> > 06.11.2005 03:25:32
> > ------------------------------------------------------------
> > 06.11.2005 03:25:32
> > Executing scheduled command now.
> > 06.11.2005 03:25:32 --- SCHEDULEREC OBJECT BEGIN @137273
> > 06.11.2005 03:21:20
> > 06.11.2005 03:25:32 Incremental backup of volume '\\xyzintraxyz\c$'
> > 06.11.2005 03:25:32 Incremental backup of volume '\\xyzintraxyz\d$'
> > 06.11.2005 03:25:32 Incremental backup of volume 'SYSTEMSTATE'
> > 06.11.2005 03:25:32 Backup System State using shadow copy...
> > 06.11.2005 03:25:37 Backup System State: 'System Files'.
> >
> > etc
> >
> >
> >
> >
> > The information contained in this communication is
> > confidential and may be legally privileged. It is intended
> > solely for the use of the individual or the entity to whom it
> > is addressed and others authorised to receive it. If you have
> > received it by mistake, please let the sender know by e-mail
> > reply and delete it from your system.
> > If you are not the intended recipient you are hereby notified
> > that any disclosure, copying, distribution or taking any
> > action in reliance of the contents of this information is
> > strictly prohibited and may be unlawful.
> > Honda Europe NV is neither liable for the proper and complete
> > transmission of the information contained in this
> > communication nor for any delay in its receipt.
> >
> >
