4 Replies Latest reply on Jan 27, 2020 11:14 AM by Soporte Colombia

    ctmudly in problems after upgrade to version 9.0.19.000 9.0.19.100 9.0.19.200

    Soporte Colombia
      Share This:

      Hi,

      I had very hard problems with command "ctmudly" after upgrade to version 9.0.19.000 9.0.19.100 9.0.19.200

      Folders with specific user daily didn´t work

      The command: ctmudly -DAILY_NAME USERXXXX -ODATE ODAT , and only finish with: User Daily: partial copy and all folders, smart and jobs were not ordened.

       

      Workaround:

      1. But when i had check with command: ctmudchk -DAILY USERXXX -ACTION LIST -ODATE ODAT
      2. List all jobs
      3. And execute for force the order: ctmudchk -DAILY USERXXX -ACTION ORDER -ODATE ODAT

       

      For fix it:

      1. verify the symtopms
      2. In planning domain open the folders and change the specific user daily USERXXX for new USERYYY
      3. Change jobs or command with ctmudly
      4. End

       

      best regards

      Juan Rendon

      www.axity.com

        • 1. Re: ctmudly in problems after upgrade to version 9.0.19.000 9.0.19.100 9.0.19.200
          Mark Francome

          Hi Juan,

           

          What platform are you running the Control-M Server on?

           

          Regards,

           

          Mark.

          • 2. Re: ctmudly in problems after upgrade to version 9.0.19.000 9.0.19.100 9.0.19.200
            Soporte Colombia

            Hi,

            Control-M/EM, Server and Agent default on x86_64-linux

            Red Hat Enterprise Linux Server release 7.6X

             

            Regards,

            Juan Rendon

            • 3. Re: ctmudly in problems after upgrade to version 9.0.19.000 9.0.19.100 9.0.19.200
              Mark Francome

              I once (a long time ago) had issues with NDP and so I introduced the following checks ... on the Control-M Server I have a job that runs this from the command line -

               

              VAR1=`ctmudchk -DAILY SYSTEM -ACTION LIST | grep ' JOB \| CMD \| DMY '`; if [ -n "$VAR1" ]; then echo "$VAR1"  | mailx -s "The following potential jobs were not ordered by New Day Processing" john.doe@hotmail.com ; else echo "Nothing found"; fi

               

              the above uses the ctmudchk utility on the Control-M Server to see if the user daily really is looking at all the jobs that it should be (in the example all my tables use SYSTEM user daily). This sometimes shows errors when people have been in the process of uploading tables when the New Day has been in process.

               

              My second check is that the New Day actually does what it should from a system perspective. I run this from the Control-M Server command line (my New Day is at 12 noon, hence the times specified) -

               

              ctmlog list %%$ODATE 1159 %%$ODATE 1211 | $HOME/ctm_server/my_server/scripts/ctmlog_ok.pl

               

              In the script I have this -

               

              #!/usr/bin/perl

               

              my( @MUSTFIND ) = (

               

                      "NEW DAY PROCEDURE STARTED",

                      "CONTROL-M LOG CLEANUP STARTED",

                      "CLEANUP ENDED. DAYS=",

                      "DAILY SYSTEM STARTED",

                      "DAILY SYSTEM ENDED",

               

              );

               

              ################################################

               

              %mustfind = map { ($_,1) } @MUSTFIND;

               

              my( $rin ) = q();

               

              vec($rin,fileno(STDIN),1) = 1;

               

              if ( select($rout=$rin, undef, undef, 10) ) {

               

                      my( $logline );

               

                      while ( $logline = <STDIN> ) {

               

                              my( $msgid,$desc ) = (split /\|/o,$logline)[1,7];

               

                              if ( $desc ) {

               

                                      foreach my $mf ( @MUSTFIND ) {

               

                                              if ( $desc=~/$mf/ ) {

               

                                                      $desc =~ s/\s+/ /go;

               

                                                      print "$msgid|$desc\n";

               

                                                      delete $mustfind{$mf};

               

                                              }

               

                                      }

               

                              }

               

                      }

               

              } else {

               

                      die "No input found.\n";

               

              }

               

              if ( %mustfind ) {

               

                      foreach ( keys %mustfind ) {

               

                              print "Did not find - $_\n";

               

                      }

               

                      exit 1;

              }

               

              exit 0;


              This will search the Control-M log for the key messages listed just after the start of the script, if one of these is not produced then you have system issues somewhere.

              • 4. Re: ctmudly in problems after upgrade to version 9.0.19.000 9.0.19.100 9.0.19.200
                Soporte Colombia

                Thks,

                 

                But the error only appears with specific user daily.

                The system daily works ok.

                 

                Regards

                Juan Rendon