Ans1512e Rc:128

[oetjmackey]

HOWDY

Trying to execute a .cmd file on windows 2003 R2 server using TSM central scheduler. have searched the adsm.org archives, and talked to IBM support. Has anybody had the following problem.

Schedule name: ta_devdb_supxprop
action: command
objects: e:\db\run\backup_supxprop.cmd
window start 21:55 on 04/23/2007
Finished command. Return code is: 128

ANS1909E The scheduled command failed.
ANS1512E Scheduled event 'ta_devdb_supxprop' failed. Return code=128

There is nothing in the dsierror.log, or dsmsched.log that is reported. no output at all.

Anything helps, next I plan on running a trace on the client to see if i can see anything.

The wierd thing is when I run this in the forground by executing dmscutil and then running the scheduled command, the backup works fine. I am stumped

 

[Harry_Redl]

Hi,

fast shot - rights (does the account the service runs under - LocalSystem? - have the appropriate access? - maybe network access?)

can you show us the script?

Harry

 

[cheffern]

Yes - check the rights first off...

I have noted (for DP's though, not the client itself) that you have to setup a special service in some cases, and give it access to the "Application" you want it to run - ie, the cmd - in the registry.

Since you say this works when you run it manually, it may be the case...

1st check permissions on the user running the job -
Then if that doesn't work I can post my little work-around, see if it would help you...

But do post the script and details so I would be able to format it properly...

-Chef

 

[may]

it can be a privilege problem or a variable one (environement),
what the systeme Logs says

 

[tmmckinn]

My guess is that you have a scheduler service using an error and sched log (dsmerror.log and dsmsched.log). This scheduler service is executing the schedule at the desired time, using the .cmd script. This script will post results to one or two log files. If the log files referenced in the script are the same as any used in the scheduler service, there likely be a file sharing error...the command script cannot append log files already open by the scheduler service. This is probably why it works manually, because the scheduler service wouldn't have the log files open during a manual run.

 

[reddy]

may be check for backup script 'execusion permisions'.

 

[oetjmackey]

Interesting I will have to think about it.

here is the contents of the .cmd file. At the current moment it does not specify an append >> or a write over >. So my guess is by default the the output will be written to the dsmsched.log, or dsmerror.log.

contents

db2cmd db2 connect to toolsdb
db2cmd db2 BACKUP DATABASE toolsdb ONLINE USE TSM OPEN 3 SESSIONS WITH 6 BUFFERS BUFFER 1024 PARALLELISM 3 INCLUDE LOGS WITHOUT PROMPTING

The errors in the dsmsched.log appear as follows.

04/23/2007 19:40:35 --- SCHEDULEREC QUERY BEGIN
04/23/2007 19:40:35 --- SCHEDULEREC QUERY END
04/23/2007 19:40:35 Next operation scheduled:
04/23/2007 19:40:35 ------------------------------------------------------------
04/23/2007 19:40:35 Schedule Name: TA_DEVDB01_TOOLSDB
04/23/2007 19:40:35 Action: Command
04/23/2007 19:40:35 Objects: e:\db\run\backup_TOOLSDB.CMD
04/23/2007 19:40:35 Options:
04/23/2007 19:40:35 Server Window Start: 20:41:00 on 04/23/2007
04/23/2007 19:40:35 ------------------------------------------------------------
04/23/2007 19:40:35 Waiting to be contacted by the server.
04/23/2007 20:41:36 Querying server for next scheduled event.
04/23/2007 20:41:36 Node Name: TA_DEVDB01
04/23/2007 20:41:38 Session established with server ASTAIRE: AIX-RS/6000
04/23/2007 20:41:38 Server Version 5, Release 3, Level 4.0
04/23/2007 20:41:38 Server date/time: 04/23/2007 20:41:05 Last access: 04/23/2007 19:40:20
04/23/2007 20:41:38 --- SCHEDULEREC QUERY BEGIN
04/23/2007 20:41:38 --- SCHEDULEREC QUERY END
04/23/2007 20:41:38 Next operation scheduled:
04/23/2007 20:41:38 ------------------------------------------------------------
04/23/2007 20:41:38 Schedule Name: TA_DEVDB01_TOOLSDB
04/23/2007 20:41:38 Action: Command
04/23/2007 20:41:38 Objects: e:\db\run\backup_TOOLSDB.CMD
04/23/2007 20:41:38 Options:
04/23/2007 20:41:38 Server Window Start: 20:41:00 on 04/23/2007
04/23/2007 20:41:38 ------------------------------------------------------------
04/23/2007 20:41:38
Executing scheduled command now.
04/23/2007 20:41:38
Executing Operating System command or script:
e:\db\run\backup_TOOLSDB.CMD
04/23/2007 20:41:38 Finished command. Return code is: 128
04/23/2007 20:41:38 ANS1909E The scheduled command failed.
04/23/2007 20:41:38 ANS1512E Scheduled event 'TA_DEVDB01_TOOLSDB' failed. Return code = 128.
04/23/2007 20:41:38 Sending results for scheduled event 'TA_DEVDB01_TOOLSDB'.

The dsmerror.log shows no more detail

04/23/2007 20:41:38 ANS1512E Scheduled event 'TA_DEVDB01_TOOLSDB' failed. Return code = 128.
04/23/2007 20:49:35 ANS1909E The scheduled command failed.

So I am pretty confident that it is not a file access issue, but I am not for sure have you seen this error code before?

I plan on running a trace as soon as I get the time.

Josh