Mont?e au plan / Up to Plan

shinz · Post by **shinz** » 08 Feb 2007 10:00

Bonjour, debutant sur ControlM/em, je voudrais savoir comment activer la mont?e au plan, car aujourd'hui rien ne monte et les jobs que je lance a la "mano" restent en l'etat et ne sont pas "purg?s" alors qu'ils sont ended ok .

Normalement pour que les tables montent il faut que je d?clare SYSTEM dans l'option USER Dayli, ce que j'ai fait a partir du scheduling table manager mais je pense qu'il doit y avoir autre chose a faire.

C'est sur un serveur Windows .

Merci d'avance pour vos reponses .

*****************************************************************

Hello, beginning on ControlM/em, I would like to know how to activate the rise in the plan, because today nothing goes up and the jobs which I launch "manually" remain in the state and ?are not purged? whereas they are ended ok.

Normally so that the tables go up one needs that I state SYSTEM in the option to USER Dayli, which I made from the scheduling table manage but I think that there must be another thing has to make.

It is on a Windows server.

Thank you in advance for your answers.

Walty · Post by **Walty** » 08 Feb 2007 11:39

Bonjour,

si dans votre table de scheduling vous avez sp?cifi? le User Daily a (SYSTEM) votre table sera scann?e et les jobs mis au plan en fonction des crit?res de planification d?finis dans l'onglet Scheduling lors de leur cr?ation.

- Avez-vous effectu? l'action Upload apr?s votre modification via le Scheduling Table Manager pour la table concern?e ?
Vous devriez avoir toutes vos tables avec le champ 'Modified' a 'No' pour ?tre synchrone entre la Db de Control-M/Server et Control-M/EM

- Si aucun job n'est mis au plan, vos crit?res de planification ne sont certainement pas corrects
- Les jobs ENDED-OK sont supprim?s de l'Active Job File (AJF) lors de l'ex?cution du prochain DAILY SYSTEM, donc restent normalement visibles 24h

- V?rifier les param?tres de configuration de votre Control-M/Server (ctm_menu, opt 6, opt2, opt2) pour vous assurer que la date Control-M est correcte
- Ex?cuter l'utilitaire (ctmudlst) pour v?rifier la bonne ex?cutiondu DAILY SYSTEM

Exemple:
La commande: ctmudlst LIST SYSTEM
vous donnera le r?sultat: User daily SYSTEM last run on 20070208

Vous pouvez analyser ce qui c'est pass? dans la DB de Control-M/Server via l'utilitaire (ctmlog) en mode commande.
Ce qui est int?ressant de rechercher est:

- Execution du DAILY SYSTEM
- Execution du Control-M Log Cleanup
- Les jobs mis au plan par le DAILY SYSTEM

La recherche s'effectuera donc sur le param?tre (LISTMSG) avec les valeurs suivantes:

- 5061 vous indique quand le 'USER DAILY SYSTEM' a commenc?
- 5062 vous indique quand le 'USER DAILY SYSTEM' c'est termin?
- 5011 vous indique quand le ' CONTROL-M LOG CLEANUP' a commenc?
- 5006 vous indique quand le ' CONTROL-M LOG CLEANUP' c'est termin?
- 5065 vous indique les jobs mis au plan par le 'DAILY SYSTEM'

Exemple:
La commande : ctmlog listmsg 5061 20070208 0100 20070208 0900
va vous donner le r?sultat :

Date: 08-Feb-2007. Page: 1

CTMLOG REPORT from 20070208 010000 to 20070208 090099

Msgidm : 5061
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|Date|Time|Jobname |Order|SS|MID |Message |
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|0208|0118|p01ctm01 |00000|CD|5061|USER DAILY SYSTEM STARTED

En esp?rant vous avoir apport? un compl?ment d'information
Cordialement

Walty

*********************************************************************

Hello,

if in your scheduling table you specified to use it Daily has (SYSTEM) your table is scanned and jobs put at the plan according to the criteria of planning defined in the Scheduling tab during their creation.

- Did you carry out the Upload action after your modification via Scheduling Table Manager for the concerned table?
You should have all your tables with the field ?Modified? has ?No? to be synchronous between the dB of Control-M/Server and Control-M/EM

- If no job is put at the plan, your criteria of planning are certainly not correct
- Jobs ENDED-OK are removed from Active Job Files (AJF) during the execution of next DAILY SYSTEM, therefore remain normally visible 24h

- Check parameters configuration of your Control-M/Server (ctm_menu, opt 6, opt2, opt2) to ensure you that the date Control-M is correct

- To carry out the utility (ctmudlst) to check good ex?cution of DAILY SYSTEM

Example:
The command: ctmudlst LIST SYSTEM
your result will give: USER daily SYSTEM last run one 20070208

You can analyze what it passed in the dB of Control-M/Server via the utility (ctmlog) in command mode.

What is interesting to seek is:

- Execution of DAILY SYSTEM
- Execution of the Control-M Log Cleanup
- Jobs put at the plan by DAILY SYSTEM

Research will thus be carried out on parameter (LISTMSG) with the following values:
- 5061 indicates to you when it ?TO USE DAILY SYSTEM? started
- 5062 indicates to you when it ?TO USE DAILY SYSTEM? it is finished
- 5011 indicates to you when the ?CONTROL-M LOG CLEANUP? started
- 5006 indicates to you when the ?CONTROL-M LOG CLEANUP? it is finished
- 5065 indicates to you the jobs put at the plan by ?DAILY SYSTEM?

Example:
The command: ctmlog listmsg 5061 20070208 0100 20070208 0900
will give you the result:

Date: 08-Feb-2007. Page: 1

CTMLOG REPORT from 20070208 010000 to 20070208 090099

Msgidm : 5061
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|Date|Time|Jobname |Order|SS|MID |Message |
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|0208|0118|p01ctm01 |00000|CD|5061|USER DAILY SYSTEM STARTED

While hoping to have brought a further information to you
Cordially

Walty

shinz · Post by **shinz** » 08 Feb 2007 3:13

Merci pour toutes ces indications !

Apres verif, les maxwait etaient a 99 ce qui explique pourquoi ils ne sont pas purg?s de l'ajf et ce meme si ended ok .

Pour ce qui est de la planif, normalement c'est bon, je suis synchro entre la DB et le serveur (modified no), et j'ai fait une petite verif avec la commande

ctmudchk -DAILY SYSTEM -ACTION LIST -ODATE 20070209

normalement c'est ok il me dit :

ctmudchk -DAILY SYSTEM -ACTION LIST -ODATE 20070209
Date: 08-Feb-2007. Page: 1

Jobs not ordered for Daily SYSTEM

+-----------------------------------------------+
JOBNAME TABLENAME
+-----------------------------------------------+
JOB1 TABLE1
JOB2 TABLE1
Job Object statistic
====================
Total User CPU Time: 0.094 second

Total Kernel CPU Time: 0.031 second

This Period Total User CPU Time: 0.094 second

This Period Total Kernel CPU Time: 0.031 second

Total Processes: 3

Active Processes: 0

Total Terminated Processes: 0

********************************************************************

Thank you for all these indications!

After verification, maxwait them were has 99 what explains why they are not purged a ajf and this same if ended ok.

As regards planif, normally it is good, I am synchronize between the dB and the server (modified No), and I made small verif with the command

ctmudchk -DAILY SYSTEM -ACTION LIST -ODATE 20070209

normally it is ok it says to me:

ctmudchk -DAILY SYSTEM -ACTION LIST -ODATE 20070209
Date: 08-Feb-2007. Page: 1

Jobs not ordered for Daily SYSTEM

+-----------------------------------------------+
JOBNAME TABLENAME
+-----------------------------------------------+
JOB1 TABLE1
JOB2 TABLE1
Job Object statistic
====================
Total User CPU Time: 0.094 second

Total Kernel CPU Time: 0.031 second

This Period Total User CPU Time: 0.094 second

This Period Total Kernel CPU Time: 0.031 second

Total Processes: 3

Active Processes: 0

Total Terminated Processes: 0