Skip to main content

We utilize &COMO& for logging process activities that are run in brackground.  This works great for our purpposes, and we can turn this feature Off/On by process in a control file record.

However, on our Development machine, a number of records appear whose origin we cannot determine.  Here is an example (SLICE is possibly one of our U2 account names OR could be a test user's login):

>CT &COMO&     SCHEDULER_SLICE_30868074
0001 COMO SCHEDULER_SLICE_30868074 established 11:07:20 05 DEC 2023

Notes:

  1. Our production system does not seem to get any of these.
  2. We run Universe 11.3.1 Pick format on AIX 7.2

Does anyone have an idea what is generating these? 

Nelson

We utilize &COMO& for logging process activities that are run in brackground.  This works great for our purpposes, and we can turn this feature Off/On by process in a control file record.

However, on our Development machine, a number of records appear whose origin we cannot determine.  Here is an example (SLICE is possibly one of our U2 account names OR could be a test user's login):

>CT &COMO&     SCHEDULER_SLICE_30868074
0001 COMO SCHEDULER_SLICE_30868074 established 11:07:20 05 DEC 2023

Notes:

  1. Our production system does not seem to get any of these.
  2. We run Universe 11.3.1 Pick format on AIX 7.2

Does anyone have an idea what is generating these? 

Nelson

Hi Nelson,

Do you have WebDE running on your Development machine? I think I have seen COMO files with a similar name being generated by WebDE based on how it is configured.

Does the information in the &COMO& file itself provide any clues?

Neil

We utilize &COMO& for logging process activities that are run in brackground.  This works great for our purpposes, and we can turn this feature Off/On by process in a control file record.

However, on our Development machine, a number of records appear whose origin we cannot determine.  Here is an example (SLICE is possibly one of our U2 account names OR could be a test user's login):

>CT &COMO&     SCHEDULER_SLICE_30868074
0001 COMO SCHEDULER_SLICE_30868074 established 11:07:20 05 DEC 2023

Notes:

  1. Our production system does not seem to get any of these.
  2. We run Universe 11.3.1 Pick format on AIX 7.2

Does anyone have an idea what is generating these? 

Nelson

Neil

Thanks for WebDE tip.

As I posted above, the COMO record tells us nothing:

>CT &COMO&     SCHEDULER_SLICE_30868074
0001 COMO SCHEDULER_SLICE_30868074 established 11:07:20 05 DEC 2023

Nelson

We utilize &COMO& for logging process activities that are run in brackground.  This works great for our purpposes, and we can turn this feature Off/On by process in a control file record.

However, on our Development machine, a number of records appear whose origin we cannot determine.  Here is an example (SLICE is possibly one of our U2 account names OR could be a test user's login):

>CT &COMO&     SCHEDULER_SLICE_30868074
0001 COMO SCHEDULER_SLICE_30868074 established 11:07:20 05 DEC 2023

Notes:

  1. Our production system does not seem to get any of these.
  2. We run Universe 11.3.1 Pick format on AIX 7.2

Does anyone have an idea what is generating these? 

Nelson

Thanks Nelson. I didn't realize the content was just the single line. Thought you might only be displaying the first line so as to not clutter up the post. 

We utilize &COMO& for logging process activities that are run in brackground.  This works great for our purpposes, and we can turn this feature Off/On by process in a control file record.

However, on our Development machine, a number of records appear whose origin we cannot determine.  Here is an example (SLICE is possibly one of our U2 account names OR could be a test user's login):

>CT &COMO&     SCHEDULER_SLICE_30868074
0001 COMO SCHEDULER_SLICE_30868074 established 11:07:20 05 DEC 2023

Notes:

  1. Our production system does not seem to get any of these.
  2. We run Universe 11.3.1 Pick format on AIX 7.2

Does anyone have an idea what is generating these? 

Nelson

Additional info:

It seems that this happens when MVIS initiates the call to our UniVerse subroutine.  (We turn COMO on in our process). 

Is this some latent MVIS action that happens before our subroutine actually turns COMO on and assigns a COMO filename?

We utilize &COMO& for logging process activities that are run in brackground.  This works great for our purpposes, and we can turn this feature Off/On by process in a control file record.

However, on our Development machine, a number of records appear whose origin we cannot determine.  Here is an example (SLICE is possibly one of our U2 account names OR could be a test user's login):

>CT &COMO&     SCHEDULER_SLICE_30868074
0001 COMO SCHEDULER_SLICE_30868074 established 11:07:20 05 DEC 2023

Notes:

  1. Our production system does not seem to get any of these.
  2. We run Universe 11.3.1 Pick format on AIX 7.2

Does anyone have an idea what is generating these? 

Nelson

Unfortunately, I should have psoted this under the Tools thread :-)

Stuart just showed me that the solution is in the MVIS account configuration under Optional Settings.

We had Enable Server-side logging for this account turned on!

Thanks Stuart.

Terms & ConditionsAccessibility statement