CA Service Management

I´m using bopcmd with gencr.frg script to open tickets form command line.

The problem is that some of my categories and groups has accent characters in its name.

Because of this, the bopcmd is failing to find groups and categories.

Is there a way to use this with accent characters?

Hi Paulo,

When you say that  the bopcmd is failing to find groups and categories, do you see any error(s) at SDM interface or log files?

Which is the release and cumulative patches applied?

Regards,

Roberto

Roberto

SDM 14.1 Cum 4.

No errors in the log, only in the return of bopcmd command:

C:\temp>bop_cmd -u dsouza@construdecor.com.br -f gencr.frg "gencr('Revisar Lista de Usuários Ativos SAP', '','', '3', 'A
berto', 'Segurança da Informaçao.Revisao de Acessos','', '', '','', '', '', 'Request')"
06/11/2018 13:48:53 ERROR Can't find category 'Seguran�a da Informa��o.Revis�o de Acessos': 'not found'

Paulo, if you want to trouble shoot a bit before open a Support case, you can edit the gencr.cfg file change

//printf("gencr\n");
        //printf("argc='%d'\n",argc);
        //int x;
        //for(x=0; x<argc; x++) {
        //      //printf("argv[%d]='%s'\n",x,argv[x]);
        //}

to

        printf("gencr\n");
        printf("argc='%d'\n",argc);
        int x;
        for(x=0; x<argc; x++) {
           printf("argv[%d]='%s'\n",x,argv[x]);
        }

and see if the argc is taken correctly. Thanks _Chi

paulofreire75 

If you have not already done so, please open a CA Support case so that CA Support can attempt to reproduce the behavior.

If the behavior is reproducible internally, the CA Service Management Engineering team would need to get involved to determine why the bop_cmd command is not translating accent characters correctly.

Looks like there was a test fix created for CA SDM 14.1 CUM#2 that resolved similar issues with accent characters.

CA Support would need to check with Engineering to see if that test fix was ported and included in CA SDM 14.1 CUM#4.

paulofreire75 

Did you need up opening a CA Support case for this behavior?

If so, please provide the CA Support case #.