sbamsey
Member
RE: OneWorld User Access
John,
In OneWorld you can set "security history" on, which writes to F9312.
Set Enterprise Server JDE.INI [Security] stanza, History=1. This logs to
F9312, which should be monitored and purged regularly. After setting this
up at our site I noticed errors in JDENET_K kernel for security - F9312 not
found in SystemB733. No OCM's existed, therefore One World was defaulting
to the data library. I set up OCM's to System B733 for F9312 for the
environments we want to monitor and placed one file set in SYSB733. Once
your file starts populating you can report on it via a OneWorld report or
through MS Access/ODBC.
Sheena
________________________________
Sheena Bamsey
ERP JDE Tech Team Lead
Information Systems
Skyjack Inc.
Guelph, Ont.
John,
In OneWorld you can set "security history" on, which writes to F9312.
Set Enterprise Server JDE.INI [Security] stanza, History=1. This logs to
F9312, which should be monitored and purged regularly. After setting this
up at our site I noticed errors in JDENET_K kernel for security - F9312 not
found in SystemB733. No OCM's existed, therefore One World was defaulting
to the data library. I set up OCM's to System B733 for F9312 for the
environments we want to monitor and placed one file set in SYSB733. Once
your file starts populating you can report on it via a OneWorld report or
through MS Access/ODBC.
Sheena
________________________________
Sheena Bamsey
ERP JDE Tech Team Lead
Information Systems
Skyjack Inc.
Guelph, Ont.
