Need user in OFS message show as inputer

hi ALL
When we use ofs message to post txn by EB.PHANTOM it will take user as inputter from OFS.SOURCE that we define but I want use ofs message and inputter of txn get from user we input in OFS MESSAGE as :
FUNDS.TRANSFER,TEST/I/PROCESS,TEST.1/123456/xxxx -> I want when ft generate get inputer as TEST.1

Thanks

Dear kda,

Do you want to perform the transaction in online or offline mode of T24?

If online then what you expect can be done. But offline it will always take the user specified in phantom. You can't change the inputter. If still you need to have the user which is there in OFS.MESSAGE then introduce a new local field in the corresponding application to store the user name by adding your own logic.

Hope in some cases bank may wish to know who has initiated the transaction from outside T24.

After company pass the "User to be replaced"

- Read somewhere... Not 100% sure ... test and see

FUNDS.TRANSFER,TEST/I/PROCESS,TEST.1/123456/COMPANY/USER.TO.REPLACE...

I just tested it & works fine .... The 1st User ADMIN1 in the OFS Mesg is Replaced by the 2nd User SARAN1, which you can see in the Audit fields of OFS Response

jsh t24uat ~ -->tSS OFS.TEST
<tSS version="1.1"><t24version>R09.000</t24version><t24pid>8580</t24pid><t24ofssource>OFS.TEST</t24ofssource><clientIP/></tSS>
TSA.SERVICE,FB/I/PROCESS,ADMIN1/Password123/BH0010001/SARAN1,BNK^FB.ATM.BAL.UPLOAD,SERVICE.CONTROL:1:1=START
BNK/FB.ATM.BAL.UPLOAD/OFS131450055840304.01/1,DESCRIPTION:1:1=FB.ATM.BAL.UPLOAD,WORK.PROFILE:1:1=ONE,USER:1:1=INPUTTER,SERVICE.CONTROL:1:1=START,DATE:1:1=20130525,DATE:2:1=20130523,DATE:3:1=20130522,D
...
...
CURR.NO:1:1=116,INPUTTER:1:1=558_SARAN1_I_INAU_OFS_OFS.TEST,DATE.TIME:1:1=1306181111,DATE.TIME:2:1=1306181111,AUTHORISER:1:1=558_SARAN1_OFS_OFS.TEST,CO.CODE:1:1=BH0010001,DEPT.CODE:1:1=1
exit
jsh t24uat ~ -->

Dear gm.saran,

I believe that you have used SOURCE.TYPE as SESSION in OFS.SOURCE record.

Have to tried alias name in OFS string with SOURCE.TYPE as BATCH in OFS.SOURCE record?

Hi gm.saran
I tested, it show security validation
Hi all

I follow above still not success
Please find the OFS.SOURCE I set:

SOURCE.NAME....... TEST.OFS

---

1 DESCRIPTION....... TEST OFS
2 SOURCE.TYPE....... BATCH
13 LOG.FILE.DIR...... TEST.LOG
14 LOG.DETAIL.LEVEL.. NONE
16 MAINT.MSG.DETS.... Y
17 DET.PREFIX........ STP
18 IN.QUEUE.DIR...... DIR.IN
20 OUT.QUEUE.DIR..... DIR.OUT
24 SYNTAX.TYPE....... OFS
26 GENERIC.USER...... EBPHANTOM


Thanks

Dear kda,

If you are going to run tSS in jshell prompt then SOURCE.TYPE should be TELNET (online) in OFS.SOURCE record.

What gm.saran passed in OFS string is called alias name (optional) and it's used when there are transactions from external users or third party systems during online.

For BATCH mode (offline), you might have already uploaded the formatted OFS messages in IN.QUEUE directory, from where system fetches and executes the message. It's not even necessary to pass user credentials in the message for batch mode, as system takes the user name provided in EB.PHATNOM/OFS.SOURCE field GTS.USER.

Yes, it's for external interface

Model Bank OFS SOURCE SEE

SOURCE.NAME....... OFS.TEST

---

1 DESCRIPTION....... OFS TEST
2 SOURCE.TYPE....... TELNET
3. 1 LOGIN.ID....... R09
14 LOG.DETAIL.LEVEL.. NONE
16 MAINT.MSG.DETS.... Y
17 DET.PREFIX........ OFS
24 SYNTAX.TYPE....... OFS
26 GENERIC.USER...... INPUTTER
42 CURR.NO........... 1

---

But the requirement of kda is for BATCH mode, which is not possible using alias name.

Hi, yes
So above, can use user normal to show it when txn was generated

Thanks

Attach a RTN in IN.MSG.RTN to replace the "OPERATOR" variable and try . . . we use this for some activities where SOURCE.TYPE is GLOBUS.

Try this...

Hi Gm.saran

could u give me sample

Thanks

@gm.saran, are you able to access the common variable "OPERATOR" in your IN.MSG.RTN?
Because what I have seen is common variables are not available in IN.MSG.RTN and OUT.MSG.RTN.

Can you please let us know whether you are able to access?

Yes, we use it for a couple of services, to be started in specific user name. This is the actual subroutine running and getting the desired results . . . we are in R9

===
$INSERT I_COMMON
$INSERT I_EQUATE

OPERATOR='ATMUSER1'

RETURN
===