End Background Session for firefihter ID

[former_member84844]

Hi All

We are using a de-centralised FF ID for emergency access and my question is with regards to the firefighter ID being locked after a background job was scheduled to run immediately. below are the steps

Firefighter logs on with the FFID

A background job is run using the FFID

Firefighter logs off from the FFID

In SM04 there is an active session running against the FF ID

FFID in now locked because of the session, when ending the session it then cancels the background job that was running. Is this the way it should work? Meaning that the firefighter must then wait for the session to finish in SM04 only then they will be able to use the FFID?

[madhusap]

Hi Mthunzi,

Why are you scheduling background jobs with Firefighter ID? Generally it is not recommended to run the background jobs through a FF ID.

Instead you can schedule the job to run with System ID by using Firefighter ID and this should resolve your issue.

Regards,

Madhu

[former_member682099]

Hi Madhu,

is it a standard behavior that when any background job runs (running user is FF user) , even for batch work processes FF ID is locked ?

Thanks,

Soumya

[eduardohartmann]

Hi Mthunzi,

Have a look at this note: 3053802 - Background job is getting canceled when scheduled with a Firefighter ID

It explains that the FF ID should not be used for running jobs, nor massive processing.

I was having the same situation and took a long time to find the answer.

Kind regards,

Eduardo Hartmann

[former_member84844]

Hi Madhu

Thanks for your feedback, the consultants were scheduling jobs which take few minutes. I will suggest that they run them using a system user going forward.

Regards

Itumeleng