The lock is belongs from different process(9908) and you're trying to terminate  via different process(10376) not is not possible. You can verify and terminate the 9908 in process  (System Operation>Process) if no longer required for prevent multiple locks set again and click remove all locks for process and remove it.

• Use $test  special variable in your code to check the for success/failure lock. If lock is success it return 1 otherwise return 0 based on this result you can continue your logic flow.
• Always use incremental lock with timeout (ex: lock +^test:0) 

LEARNING>w $test
0
LEARNING>lock +^test:0
 
LEARNING>w $test
1
LEARNING>

Basically. The tcommiit will commit the current open transaction. Lock -^global (decremental lock ) is used to release the incremental lock( lock +^global) so everytime if you do incremental lock then you should decrement the lock) by using lock -^gbl syntax

Argumentless lock is release all the locks in the process. So this is not highly recommend in code. And incremental locks are highly recommend for use.

I see you're locking the global  +^IudexNqlInByte not unlocking. can you check the below

tstart
	if staten["IUDX" {
		lock +^IudexNqlInByte(1):0
		if $test{ 
			set IudexNqlInByte(1,inc)=obj.%Id()
			lock -^IudexNqlInByte(1)
		}
	}
	else {
		lock +^ToshibaNQLIn(1):0
		if $test {
			set ^ToshibaNQLIn(1,inc)=obj.%Id()
			lock -^ToshibaNQLIn(1)
		}
	}
tcommit

Hello @Robert Steed

Is the terminating process via SMP (System Operation>Process>SelectProcess Detail>Terminate) isn't working?

Hello Yone,

Why don't you use %Stream.GlobalCharacter stream object to store  Long string instead of %String property. You can extend your class with %JSON.Adaptor and create a JSON object and directly import with your contents like below.

ClassMethod Import()
{
    set json=[{"ID_SICH":"121212","FECHA_DERIVACION":123,"MEDICO_PETICIONARIO":(tResponse.Data)}]
    set obj = ##Class(Mensajes.Response.Radiologia.CConcertados.BusquedaOrdenesNEGRINResponse).%New()
    set stt= o.%JSONImport(json)
    if $$$ISERR(stt) write $SYSTEM.OBJ.DisplayError(stt)
    set stt= obj.%Save()
    if $$$ISERR(stt) write $SYSTEM.OBJ.DisplayError(stt)
}

Hello @Kari Vatjus-Anttila 

This was a nice implementation for securing the individual REST calls. However, Will loose the benefits of built JWT Authentication for web application(from 2022 version). Maintaining two separate web applications for secure and unsecured seems useful.

Thank you for the samples. Now it works fine and I get JWT. I have seen this parameters in some other post in community. What is the exact use of these parameters dispatcher class.

 Parameter TokenLoginEndpoint = "login"; Parameter TokenLogoutEndpoint = "logout"; Parameter TokenRevokeEndpoint = "revoke"; Parameter TokenRefreshEndpoint = "refresh";

Yes. my web application is /api and invoked this http://localhost:52774/api/login

Hello @Luis Angel Pérez Ramos 

I've enabled and configured JWT in my Web application. I'm trying to call the /login method from post man with body of contents  {"user":"{YOURUSER}", "password":"{YOURPASSWORD}"} but I got 404 not found error. Did I anything missed/required.

As you mentioned 

With this configuration we will not need anything else to start using this authentication mode in our web applications.

However This is for clarification

Do I need to write a custom login method or existing is enough? 

Do I need to include  /login, /logout etc.. endpoints in urlmap?

Hello @Yone Moreno 
Just a thought. Convert the HL7 message into SDA. Create a clone class like SDA with extends of Ens.Request. Create a instance of the class and import the String into the object and finally store it like below.

ClassMethod HL7ToCustomEnsReq()
{
    #dim xml As %Stream.GlobalCharacter
    set hl7 = ##class(EnsLib.HL7.Message).%New()
    
    set tSC = ##class(HS.Gateway.HL7.HL7ToSDA3).GetSDA(hl7,.xml)
    $$$ThrowOnError(tSC)
    
    set reqObj = ##class(Mensajes.Request.ConsentimientoInformado.HUC.ORUHL725OutRequest).%New()
    do reqObj.XMLImportSDAString(xml.Read())
    set tSC = reqObj.%Save()
    $$$ThrowOnError(tSC)
}

Thanks you @Guillaume Rongier !

Hopefully this will be helpful

As per the documentation The I had raised the same question Currently, InterSystems products do not provide the ability to validate a resource against a profile. Validation is limited to the base FHIR specification.

Thanks @Luis Angel Pérez Ramos for pointing the documentation