Skip to main content

initiator class

  • December 23, 2019
  • 5 replies
  • 0 views

Hi,

In one of our test batch region, we encountered a scenario where in the jobs which were submitted in Control M were getting failed because takes the A class initiator eventhough in the JCL it is N class initiator. Whereas the jobs submitted in Microfocus console it runs fine using N class initiator. We resolved it temporarily by disabling the A class initiator.

 

Product : Microfocus enter prise server 4.0 PU7

Server : Windows Server 2016.

 


#EnterpriseServer

5 replies

  • Rocketeer
  • 19312 replies
  • December 30, 2019

Hi,

In one of our test batch region, we encountered a scenario where in the jobs which were submitted in Control M were getting failed because takes the A class initiator eventhough in the JCL it is N class initiator. Whereas the jobs submitted in Microfocus console it runs fine using N class initiator. We resolved it temporarily by disabling the A class initiator.

 

Product : Microfocus enter prise server 4.0 PU7

Server : Windows Server 2016.

 


#EnterpriseServer

Are you using Micro Focus Batch Scheduler Integration (MFBSI) or Control M's proprietary module to integrate Control M with Enterprise Server?

If it's MFBSI, please provide your MFBSI configuration file. If it's the Control M module, you may need to contact BMC, though Micro Focus Customer Care may also be able to help you.

Note that in general, the job class specified in the JCL can be overridden during job submission, whether the job is submitted using the Enterprise Server web interface, the cassub command line, the CASSUB API, or another mechanism such as the internal reader. My guess is that Control M is overriding the class specified in the JCL when it submits the job, but I've never used Control M and I don't know what options there are for instructing it to respect the class given in the JCL.


  • 0 replies
  • December 30, 2019

Are you using Micro Focus Batch Scheduler Integration (MFBSI) or Control M's proprietary module to integrate Control M with Enterprise Server?

If it's MFBSI, please provide your MFBSI configuration file. If it's the Control M module, you may need to contact BMC, though Micro Focus Customer Care may also be able to help you.

Note that in general, the job class specified in the JCL can be overridden during job submission, whether the job is submitted using the Enterprise Server web interface, the cassub command line, the CASSUB API, or another mechanism such as the internal reader. My guess is that Control M is overriding the class specified in the JCL when it submits the job, but I've never used Control M and I don't know what options there are for instructing it to respect the class given in the JCL.

Hi MIke,

Is there any specific reason the initiators gets overridden? Because the jobs were running fine when we submit in enterprise server but not in Control M.

Also the Control M team justified that there is nothing to do with their tool and no settings has been changed.

 

 

 


  • Rocketeer
  • 19312 replies
  • December 30, 2019

Hi MIke,

Is there any specific reason the initiators gets overridden? Because the jobs were running fine when we submit in enterprise server but not in Control M.

Also the Control M team justified that there is nothing to do with their tool and no settings has been changed.

 

 

 

Actually, I checked the documentation, and it doesn't appear that the class can be overridden when the job is submitted. I must have misremembered. So I don't know what's going on in your case. I suggest you open an incident with Micro Focus Customer Care, who can help you gather all the appropriate diagnostics.


  • 0 replies
  • January 2, 2020

Actually, I checked the documentation, and it doesn't appear that the class can be overridden when the job is submitted. I must have misremembered. So I don't know what's going on in your case. I suggest you open an incident with Micro Focus Customer Care, who can help you gather all the appropriate diagnostics.

Hi Mike,

One of the job failed with the below log. What is it referring to 

MVSER0031S "DB2P" is not a valid subsystem id. Sub-command stream flushed.:
MVSER0099S Remainder of command stream flushed.


  • Rocketeer
  • 19312 replies
  • January 2, 2020

Hi Mike,

One of the job failed with the below log. What is it referring to 

MVSER0031S "DB2P" is not a valid subsystem id. Sub-command stream flushed.:
MVSER0099S Remainder of command stream flushed.

I don't know. I'm not familiar with that message, I don't find any reference to it in the product documentation, and a quick check of some of the sources didn't turn it up either. You'll have to open an incident with Micro Focus Customer Care.