jclju1
5th December 2016, 10:42
Does anyone have any idea why one session returns different result if it is started manually, as if running in the job? Session run by the same user, so there are all settings equal. It seems that session when start in job ignores one if statement. If run in job, session returns items which should be eliminated in if statement. If we started session manualy, those items were skipped and this is correct.

Regards.

bhushanchanda
5th December 2016, 11:08
It could possibly a bug in the code. It sounds like one. What session is that?

jclju1
5th December 2016, 11:10
This is not standard session, so I am almost sure that it is bug but I can not find what is wrong.

sachinbaan
5th December 2016, 13:37
If it is ignoring any condition then there may be code to ignore condition if it is executed manually, i faced this issue in one of my customization where job.process was used.

if not job.process then
/* Manual Execution
endif

jclju1
6th December 2016, 10:18
There are not "if not job.process then" or "if job.process then" in source code.

pillai.ganesh
6th December 2016, 11:44
Open session - Sessions by Job (ttaad5501m000). Select the session which your job is running and check the "Session Settings" that the Job uses while running the session. [Specific Option -> "Change Session Settings"]
This setting is independent of login and is specific to the JOB.

Hope this information helps in your investigation.

jclju1
6th December 2016, 11:47
I already checked Session Settings, it is the same as in case when we start session outside job.

mark_h
6th December 2016, 14:34
Can you post the section of code where you are having issues?