How to define & monitor parent and child STCs withthe same name to SSM?

[Steve__Ives]

We havean STC that when started, automatically starts another STC with the same name. They have different UP messages and we were wondering how best to define this to SSM and track them? Both tasks stay up for the duration of the IPL - neither are transiemt.

Thanks, Steve

(What actually happens is the first task starts and goes DS=UP, CS=UP and then the child task starts but the UP message is different, so the entry in STCTBLE goes to DS=UP, CS=STARTING.

We have an 'UP MESSAGE' column in STCTBL and I assume there is a default  rule somewhere checking this column for the UP message for each task that starts.

[Steve__Ives]

So I was thinking of adding some code to the UP checking to use OPSSTATUS to count the number of this task running as if the answer is 2, then this must be th child task and so don't do anything.

Edit:

New idea. We are going to find a suitable 'UP' message in the child task and use that as the UP message. We will only track one STC in SSM.

[Jorge Aparicio]

Hello Steve,

I understand that despite the start of the second task is not handled via SSM, you need this to be tracked on SSM. 

I think the column 'UP MESSAGE' is a user defined column, equivalent on SSM Version 3 would be SSM#ACTCMP. Therefore I assume you have a user defined rule which looks for the 'UP MESSAGE' column. You might want to search for OPS7914T message events which inform on the resource status update along with more information to identify which is this user defined rule, to understand why it keeps the STC as DS=UP, CS=STARTING.

I hope this helps! Good luck Steve!

[Carlos Filho]

Hi Steve,

A possible approach that may work depending on the nature of your tasks is to use the stepname to differentiate the tasks. For example, if the jobname of your tasks is SSMTASK and you have 2 tasks with the same name you would define 2 entries in the resource table:
Name:
SSMTASK.STEPA
SSMTASK.STEPB

The "jobname" column would be the same for the 2 tasks "SSMTASK".
You would need to start the tasks using the command S SSMTASK.STEPA and S SSMTASK.STEPB for example.

To detect the termination, you can use an EOS rule as it allows checking the stepname of the task that finished. This can work if the task has only one step.

For example:

)EOS  SSMTASK                           
)PROC                                    
JOB  = EOS.JOBNAME                       
STEP = EOS.STEPNAME                      
address SQL                              
"UPDATE STCTBL SET CURRENT_STATE='DOWN'",
"WHERE NAME = '"JOB"."STEP"'"            

Let me know if this helps.

Regards,
Mario