Auditing User Level Activities in Jbase

Start
Prev
1
Next
End

nita
Topic Author
Offline
New Member

7 years 1 week ago #21480 by nita

Auditing User Level Activities in Jbase was created by nita

Hi,

I have deployed User-admin-info-gatherer tool provided by Temenos for auditing jed activities. But got issue as "UNABLE TO OPEN F.JBASE.JED.AUDIT.LOG". The demo of issue is:

cd MONITOR.BP
jed TEST.ST
UNABLE TO OPEN F.JBASE.JED.AUDIT.LOG(got this message sometimes)
But while doing jed as
jed MONITOR.BP/TEST.ST there is no issue.

Thanks in advance,
Nita

Please Log in or Create an account to join the conversation.

VK
Offline
Platinum Member
Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test

7 years 1 week ago #21482 by VK

Replied by VK on topic Auditing User Level Activities in Jbase

Hi
Looks like the "control" file F.JBASE.JED.AUDIT.LOG resides in bnk.run. When you change your current directory to MONITOR.BP it can't be found. You can check it by:

LIST . LIKE ...JBASE...

Really, I wonder how this can be called a control... Anyone who has access to jsh can easily clear this table to cover all activities...

Cheers
VK

Please Log in or Create an account to join the conversation.

nita
Topic Author
Offline
New Member

7 years 1 week ago #21483 by nita

Replied by nita on topic Auditing User Level Activities in Jbase

Hi VK,

Thanks for your response. But the control file of F.JBASE.JED.AUDIT.LOG is not in bnk.run. Also I have attached the VOC here

F.JBASE.JED.AUDIT.LOG
001 F
002 ../bnk.data/eb/F.JBASE.JED.AUDIT.LOG
003 ../bnk.dict/F.JBASE.JED.AUDIT.LOG]D

Thanks,
Nita

Please Log in or Create an account to join the conversation.

VK
Offline
Platinum Member
Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test

7 years 1 week ago #21484 by VK

Replied by VK on topic Auditing User Level Activities in Jbase

Hi
I don't know why there are errors when you change the current directory but normally one doesn't change it.
Though (if you prefer it) you can try to launch JED this way (note the dot meaning "the current folder"):

cd MONITOR.BP
JED . TEST.ST

Cheers
VK

Please Log in or Create an account to join the conversation.

jpb
Offline
Moderator
retired . . . ¯\_(ツ)_/¯

7 years 1 week ago #21486 by jpb

Replied by jpb on topic Auditing User Level Activities in Jbase

If you can do LIST F.JBASE.JED.AUDIT.LOG without error you should check your trigger routine, most probably the file open is wrong there . . .

Please Log in or Create an account to join the conversation.

VK
Offline
Platinum Member
Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test

7 years 1 week ago #21487 by VK

Replied by VK on topic Auditing User Level Activities in Jbase

Hi
actually when you're out of bnk.run VOC entries are inaccessible:

jsh ~ -->CD BP
jsh  ~\BP -->LIST F.SPF
No file name could be found for your query

jsh R13Daily ~\BP -->CD ..
jsh R13Daily ~ -->LIST F.SPF
LIST F.SPF

@ID.................. SYSTEM
@ID.................. SYSTEM
SYSTEM.SPEC.......... SYSTEM
...

Cheers
VK

Please Log in or Create an account to join the conversation.

jpb
Offline
Moderator
retired . . . ¯\_(ツ)_/¯

7 years 1 week ago #21490 by jpb

Replied by jpb on topic Auditing User Level Activities in Jbase

That's why I think the file open is wrong, the trigger should work no matter in which actual path you work.
So open with full path (e.g. using $HOME) should be used.

Please Log in or Create an account to join the conversation.

nita
Topic Author
Offline
New Member

7 years 4 days ago #21501 by nita

Replied by nita on topic Auditing User Level Activities in Jbase

Thanks jbp. I understand now and tried with following ammendment and it seems to work.

IF FILEINFO(c$f.jBase.jed.audit.log,0) = 0 THEN ;* If not alre
0081 EXECUTE "pwd"
0082 EXECUTE "cd"
0083 OPEN "F.JBASE.JED.AUDIT.LOG" TO c$f.jBase.jed.audit.log ELSE
0084
0085 CRT "UNABLE TO OPEN F.JBASE.JED.AUDIT.LOG"
0086 RETURN
0087 END
0088 END
0089 WRITE RjBASEJedLog TO c$f.jBase.jed.audit.log, RecID
0090 *
0091 RETURN

Thanks again.

Please Log in or Create an account to join the conversation.

Start
Prev
1
Next
End

Time to create page: 0.086 seconds