on 05-07-2009 9:10 PM
To make sure our LC internal consistency checks are valid, we need to make sure that
all CIF activities are stopped.
Could you tell a way to verify they are stopped?
And if they are not stopped, how to stop them?
Thanks a lot!
Hello Kelly,
In the option that you have mentioned, ie Released ---> Planned under /n/sapapo/om17, it will just display the list of jobs/programmes which are in released condition. Once you set the button, all jobs under release will get status planned. But this transaction normally needs to be carried out only if you are taking up of all jobs to planned condition if there is any risk/incident happened in livecache or under certain critical business conditions to withdraw all jobs. One more risk associated with changing status from released to planned is that there are more chances that the job scheduled periodicities can change upon withdrawing and then releasing the job.
CIf activity will not stop only on stopping the jobs. It will stop only based on stoppage of jobs/programmes/users/cif queues etc., in order to achive this, you can follow the procedure which I have mentioned in my above previous post.
Regards
R. Senthil Mareeswaran.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kelly,
In OM17 screen, click unlock users so that there won't be any user carrying out transaction of both master data & transactional data which will generate queue. Once the queue generation is stopped, the existing queues can be stopped by clicking on stop cif queue. There should not be any active or scheduled jobs during the consistency check period which will inturn generate huge queues.
The queue movement can be checked in smq1 & smq2 transactions. If there are no active jobs & no active users, the CIF has no initiators to carryout its function and it has been stopped.
Regards
R. Senthil Mareeswaran.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks!
On /nsapapo/om17, select "overview active users/tasks/jobs", there is a button
called "released->plan". My understanding is that
click this button once, the selected job will be taken back from released status and will be held
until I click the same button again, then it will become "released" again.
The on-line document does not explain this. Please help confirm my guess.
Thanks!
look at the queue monitor /n/sapapo/cq and check for "STOP" queues.
to turn them off, use /n/sapapo/om17
there are also batch program equivalents, I forget the names, but will post tomorrow when I logon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.