Unable to start CICS region CF0038

I am tryng to get experience with Enterprise Server but when I started a Test region with

casstart32 -rTEST -m10.0.130.234:86 -S:c

I get

CASMG9999E    0000,Message file missing,   12:21:20

CAMSG9999E  CF0038,casstart,TEST,0000 12:21:20

Where I can find these error messages?

Best regards and thanks in advance

Horaico 

Labels:

Enterprise Server
  • Hi Horaico,

    Can you advise why you need to specify the -m parameter? If you just try casstart32 -rTEST -S:c does that work for you? Are you trying to star a region on a remote MFDS instance?

  • Hi

    thanks for your reply.

    I am not trying to connect a remote instance

    I tried the command : casstart32 -rTEST -S:c with the same previous messages

    I also find the messages in console.log

    231226 15052569 CASCD0099I ES Build Tag: ED7.0/20220308_PU07a 15:05:25

    231226 15052569 CASCD0028I Console Daemon running with effective user ID = 01001 15:05:25

    231226 15052667 CASCD0120I Server manager created for ES TEST, process-id = 9441 15:05:26

    231226 15052667 CASCD0126I Could not create Region man231226 15052569 CASCD0028I Console Daemon running with effective user ID = 01001 15:05:25

    231226 15052667 CASCD0120I Server manager created for ES TEST, process-id = 9441 15:05:26

    231226 15052667 CASCD0126I Could not create Region manager, reason = 0013 15:05:26

    231226 15052667 CASCD0141S Server manager TEST failed in initialization, exited with value 0000000255 15:05:26

    231226 15052667 CASCD0139I ES Daemon auto-shutdown started 15:05:26

    231226 15052667 CASCD0101I ES Daemon Terminated 15:05:26

    231226 15052667 CASCD0174I ES Console process termination control thread exited 15:05:26

    Any ideas how to solve the problem or how to get more information?

    Thanks in advance

    Horacio Merovich

  • Suggested Answer

    Hi,
    I do not have any information about your region's configuration but suspect there may be an issue with invalid paths and missing directories in the ES properties. Typically this sort of problem can occur when one of the directory locations specified in the ES region properties is invalid or missing. I recommend you to review those and confirm all are valid.