Only ONEWORLD user creates JDE(DEBUG).LOG on AS/400

Tom_Davidson

Tom_Davidson

VIP Member
We are having an issue with OneWorld.

When we issue a RUNUBE when signed in with any user EXCEPT ONEWORLD the
JDE_jobnum.LOG and JDEDEBUG_jobnum.LOG are not created.

RUNUBE is executed from the green screen command line.

We have tried signing in as JDE, myself, and QSECOFR.

We have our INI set up to create the logs.

Has anyone else seen this issue:

TIA,
Tom Davidson

Xe Update 2, SP17.1C, ES: AS/400 V4R5; DS: SQL; TSE Citrix Metaframe 1.8




OW 7332 SP 11.3VER, NT 4.0 SP 5, TSE 4.0 SP 4, Metrframe 1.8, CO SQL 7.0
 
Not sure if it'll help your problem, but I remember seeing something about
issuing the GRTOBJAUT command to the ONEWORLD user profile.
Otherwise, do profiles other than OneWorld have authority to create files in
the JDEB7333 IFS.
 
Rich,

*PUBLIC has all rights to the JDB7333 directory. It doesn't appear to be
an authority issue, we log authority violations.

Tom

Xe Update 2, SP 17.1C, ES: AS/400, DS SQL, TSE Citrix Metaframe 1.8a




Not sure if it'll help your problem, but I remember seeing something about
issuing the GRTOBJAUT command to the ONEWORLD user profile.
Otherwise, do profiles other than OneWorld have authority to create files
in
the JDEB7333 IFS.





OW 7332 SP 11.3VER, NT 4.0 SP 5, TSE 4.0 SP 4, Metrframe 1.8, CO SQL 7.0
 
We had issues like this before too. Even though the users had ALLOBJ authority, it would still have issues until the grtobjaut command was run.

GRTOBJAUT OBJ(YOURUSERID) OBJTYPE(*USRPRF) USER(ONEWORLD) AUT(*ALL)

Good Luck!



OneWorld XE SP15.1
AS/400 V4R5 Enterprise
NT2000 Application/Batch Servers
Windows 2000/Citrix
 
I gave this a try. No luck. Thanks for the suggestion. If you have any
other ideas let me know.

The kicker is that ONLY JDE is unable to create logs. Even my ID that is
excluded from ONEWORLD & JDE profiles is able to create the JDE_xxxxxx.log
and JDEDEBUG_xxxxxx.log's.

Tom Davidson
Xe Update 2, SP 17.1D: ES AS/400: DS NT: TSE Citrix Metaframe 1.1a



We had issues like this before too. Even though the users had ALLOBJ
authority, it would still have issues until the grtobjaut command was run.

GRTOBJAUT OBJ(YOURUSERID) OBJTYPE(*USRPRF) USER(ONEWORLD) AUT(*ALL)







OW 7332 SP 11.3VER, NT 4.0 SP 5, TSE 4.0 SP 4, Metrframe 1.8, CO SQL 7.0
 
Back
Top