The others have given good advice. I would suggest finding out which rule
is doing the start of the server. I would then see why that rule is being
triggered multiple times. This is the proper way. However, I'll also give
you my "improper" way. We used to have operators who would do multiple
START commands for CICS regions. This was irritating because it was
somewhat difficult to get the extra regions out of the system. Yes, we
could cancel with an A=. But that generated problem reports. Which caused
management to "bug" us. So I wrote up a CA-OPS/MVS rule to control the
START command. You, and others, might find it interesting. Or you might not.
)CMD START
)PROC
smfid=OPSINFO('SMFID')
EasyRuleCmdText = TRANSLATE(CMD.TEXT,' ',',')
upper EasyRuleCmdText
WhatIsStarting=word(EasyRuleCmdText,2)
WhatIsStarting=TRANSLATE(WhatIsStarting," ",".")
WhatIsStarting=word(WhatIsStarting,1)
/*
Do not allow Production or Clone CICS regions
to start on the Development system
*/
if (smfid='DEV1') then do
if 'PCICS' = LEFT(WhatIsStarting,5) then return "REJECT"
if 'CCICS' = LEFT(WhatIsStarting,5) then return "REJECT"
end
/*
Do not allow non-Production CICS regions on the Production system
*/
if (smfid='LIH1') then do
if 'TCICS' = LEFT(WhatIsStarting,5) then return "REJECT"
if 'MCICS' = LEFT(WhatIsStarting,5) then return "REJECT"
IF 'IMCM' = WhatIsStarting then return "REJECT"
end
/*
Some things require multiple instances 2b started. List them here.
*/
MULTIPLEOK="INIT BMCCAS OPSOSF BBISSA1 DUMPSMF C41PDUMP CMRDJCL "
MULTIPLEOK=MULTIPLEOK "TS13DUMP SCHSRVR ATTSRVR CCITCPGW"
/* Test to see if multiple starts are OK. If so, allow the start */
if (0<>WORDPOS(WhatIsStarting,MultipleOK)) then return "NOACTION"
/*
if multiple starts are not allowed, then check to see if the STC
is already running. If so, abort the start, else allow it.
*/
if (0<OPSTATUS("A","A",WhatIsStarting))
then do
Msg_Start.1="Dude!"
Msg_Start.2="Notice."
Msg_Start.3="Achtung!"
Msg_Start.4="Oh, WOW!"
Msg_Start.5="Heavy,"
Msg_Start.0=5
Msg_End.1="is already running!"
Msg_End.2="is currently running."
Msg_End.3="is, like, you know, already doing it''s thing."
Msg_End.0=3
Msg_Number_S = 1+RANDOM(Msg_Start.0-1)
Msg_Number_E = 1+RANDOM(Msg_End.0-1)
MS = Msg_Start.Msg_Number_S
ME = Msg_End.Msg_Number_E
Address WTO
"TEXT('"MS WhatIsStarting ME"') ",
"DESC(5) LOWLITE MCSFLAGS(RESP) ROUTE(MSTRINFO)"
return "REJECT"
end
else return "NOACTION"
OK, you might want to clean up the message that I put out when the START is
aborted due to the STC already running. I was in a winsome mood that day.
On Sun, Mar 9, 2014 at 10:57 PM, baby eklavya <[email protected]>wrote:
> We are running z/os 1.11 and also have SAS 8.2 in our shop .Each time after
> IPL ,automation issues the start command for SAS server3 started task
> repeatedly ( more than 100 times).But the fun part is that , the task is
> actually started with one of the start commands issued initially . But
> automation still keeps issuing the start command for this task and
> eventually gives up saying the task cannot be started .
>
> Is this a timing issue ? or a communication problem between the task and
> automation product ( CA OPSMVS) . How can i fix this ?
>
> Regards,
> Baby
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
--
Wasn't there something about a PASCAL programmer knowing the value of
everything and the Wirth of nothing?
Maranatha! <><
John McKown
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
