Schedules containing PRESCHEDULECMD fail

[bdmaner]

Hi



After upgrading our TSM (AIX) server to 5.1.5.4 and the AIX clients to 5.1.5.8 the PRESCHEDULECMD and POSTSCHEDULECMD options don't work specified from the client schedules. This used to work fine and 4.x client work fine on the 5.x server. I tried different quotes, with or without the preceding -, CAPS on caps off, sing a song to the server, but it didn't help



Log says:

01/21/03 09:28:38 ANR2017I Administrator xxx issued command: DEFINE

SCHEDULE AIX_DOMAIN @170 ACTION=INCREMENTAL

OPTIONS="-preschedulecmd='/usr/tivoli/tsm/client/ba/bin/-

tsm-pre-ax0013.sh' -postschedulecmd='/usr/tivoli/tsm/cli-

ent/ba/bin/tsm-post-ax0013.sh'" PRIORITY=1

PERUNITS=ONETIME DURATION=5 DURUNITS=DAYS

01/21/03 09:28:38 ANR2500I Schedule @170 defined in policy domain

AIX_DOMAIN.

01/21/03 09:28:38 ANR2017I Administrator xxx issued command: DEFINE

ASSOCIATION AIX_DOMAIN @170 AX0013

01/21/03 09:28:38 ANR2510I Node AX0013 associated with schedule @170 in

policy domain AIX_DOMAIN.

01/21/03 09:28:38 ANR2505I 1 schedules were defined for DEFINE CLIENTACTION.

01/21/03 09:28:51 ANR0406I Session 1972 started for node AX0013 (AIX)

(Tcp/Ip 127.0.0.1(34077)).

01/21/03 09:28:51 ANR0484W Session 1972 for node AX0013 (AIX) terminated -

protocol violation detected.



DSMSCHED.LOG says:

ANS1108E Invalid option (-PRESCHEDULECMD) for the INCREMENTA

L command



I say: damn





Any help would pe appreciated...



TIA



Cheers Erik

 

[barsik]

Sorry, with 5.1.5 you cannot specify pre/postschedulecmd as an option in the schedule definition. Although the commands will work of you put them in the client option set or dsm.opt.

 

[bdmaner]

I heard it's a bug in the AIX 5.x client. The W32 client works OK. So if this was a global decision to no longer support this as a schedule option, the W32 client also wouldn't work



Right? :lol:

 

[barsik]

I do not know whether it was a global decision... Anyway you can stick to Windows clients since they work