CMD rule for IMS

[Wladyslaw Borysow]

Hello,

in our shop we use CMD rule to stop BMP region used by IOF. Acc. to rule list STATS it is not fired. I want to find the reason why and how to fix it.

From what I see in opslog the event looks like:

Job Name | Time | Date | ASID | MSF ID | MSF DEST | OJobname |
OPSS0160 | 08:46:35 | 22MAR2020 | 0160 | SY3 | SY3 | NONE |
________________________________________________________________________|
MessageNum | Elapsed | SysID | AF | Flags | Disp | OPSF | Conid |
0159586490 | 0000065 | SY | 00 | 000000 | NOA | 8000 | M0008 |
________________________________________________________________________|
Release | Jobnm | Jobid | WTO ID | Token | Xconid |
13.05.00 | NONE | S28997 | 00000000 | | M02000008 |
________________________________________________________________________|
ConsName | IMSID | IMSType| CLS | RouteDesc | TimeStmp | SYSNAME |
OSY3S00 | NONE | NON | NON | 0000 0000 | NONE | SY3 |
________________________________________________________________________|
Length | Special | DSP name | User | UserX | TermName |
017 | | OSY3S00 | NONE | 0000000000000000 | NONE |
________________________________________________________________________|
User ID | Event | Color | Autotokn | Hex Autotokn | Exit |
OPSUSER | CMD | NONE | | 0000000000000000 | MVS |
________________________________________________________________________|
Ruleset.Rulename | Count | Ruleset.Rulename1 | Ruleset.Rulename2 |
HP.CMDOPER | 01 | HP.CMDOPER | NONE.NONE |
________________________________________________________________________|
Ruleset.Rulename3 | Ruleset.Rulename4 | Ruleset.Rulename5 | Address |
NONE.NONE | NONE.NONE | NONE.NONE | 0EBE5E80 |
________________________________________________________________________|
Message ID | Event ID | Route Codes<-->64 65<-->96 97<->128 DESC |
REPLY | REPLY | 00000000 00000000 00000000 00000000 0000 |
________________________________________________________________________|
----+----1----+----2----+----3----+----4----+----5----+----6----+----7 |
R 121,/CHE FREEZE



and the rule which is not fired is:

)CMD /CHE*
)PROC
cmd = cmd.verb
cmdtext = cmd.text
job = cmd.jobname
/* imsid = cmd.imsid */
imsid = substr(job,1,4)
Select
When cmd = '/CHE' & ,
( pos('FREEZE',cmdtext) > 0 | ,
pos('DUMPQ',cmdtext) > 0 | ,
pos('PURGE',cmdtext) > 0 ) then do
do n = 1 to 16
RetCode = opsprm('SHOW','IMS'n'ID')
do while queued() ¬= 0
pull record
say 'SETBMP' record
record_imsid = strip(word(record,5),B,"'")
if record_imsid = imsid then do
T = OPSPRM('SET','IMS'n'INITBMP','NO')
end
end
end
end
Otherwise nop
End
Return

We already have some CMD rules and they work so I suspect that CMD-event definition is wrong.
Any help would be appreciated.
Thank You!

[Ron Sheehan]

If you look at the event detail, you will see that your event ID is "REPLY", not "/CHE".  

[Wladyslaw Borysow]

Hello Ron,

thank you. What do you suggest to use in CMD-event defintion? Just asteriks?

)CMD *
)PROC

[Ron Sheehan]

In order for this to work using a response to the story, you would have to code the event as )CMD REPLY.

[Wladyslaw Borysow]

Hello,
thank you very much. Will test it.

[Wladyslaw Borysow]

Hello once again,
 
I found that logic in our CMD rule is actually very similar to OPS/MVS provided rules:

CCLXRULS(CHE)

)CMD /CHE
)INIT
/*********************************************************************/
/* */
/* Proprietary and Confidential Information */
/* and Intellectual Property of CA */
/* Copyright (C) 2000 CA */
/* All Rights Reserved. */
/* */
/* Name - /CHE (event identifier /CHECKPOIN) */
/* FUNCTION - Shutdown the IOF BMP at termination checkpoint */
/* */
/* Notes - This complements the DFS994I message that sets the */
/* BMP active only after a restart of the IMS control */
/* region is complete. */
/* */
/* In order to process /CHECKPOINT as well as /CHE, */
/* copy this member to a member called CHECKPOI */
/* and change the )CMD /CHE event specifier to */
/* )CMD /CHECKPOIN (note that the 'T' is dropped) */
/* for the non-alias version. */
/* */
/*********************************************************************/

So the question is why it is advised by official product support to use /CMD /CHE rule instead of /CMD REPLY?

I am trying to understand why CMD /CHE rule doesn't work for us...I don't see any Event-id /CHE in OPSLOG

This is the our OPSLOG:

22MAR 13:59:22 R 153,/CHE FREEZE
22MAR 13:59:22 R 153,/CHE FREEZE
22MAR 13:59:22 IEE600I REPLY TO 153 IS;/CHE FREEZE
22MAR 13:59:22 /CHE FREEZE

First event is MSG, Event-ID is R
Second event is CMD, Event-ID is REPLY
Third event is MSG, Event-ID is IEE600I
Fourth event MSG, Event-ID is NONE

Thanks!

[Ron Sheehan]

The /CHE command would have to be entered as the actual command you are issuing.  By going through the IMS WTOR, your command is not /CHE as you can see in the event details.  The command event in your case is 'REPLY'.

Ronald Sheehan

Engineering Services Architect
Broadcom |  9815 David Taylor Drive, Charlotte | Charlotte, NC 28277
Office: [phone] | Mobile: [phone] | [e-mail]

[Wladyslaw Borysow]

Hello Ron,

Thank you once again. It looks that you are right - the rexx routine is issuing the command as an answer to wtor  - Call ISSUE_REPLY "/CHE FREEZE"

I will correct CMD rule.

Best Regards,
Wladyslaw

[Dave Gorisek]

Why not just stop the BMP in the REXX that is issuing the /CHE freeze command rather than have CMD rule to fire on action from the REXX....more efficient to do it in the initiating REXX....​

[Wladyslaw Borysow]

Hello Dave,

thank you for the remark.
Actually due to other problems with CMD rule I decided to add simple rexx for stop of BMP to STCTBL_ACT.
Regards,
Wladyslaw