'After Request job' condition on Banner RA Agent generates error

Document ID : KB000090498
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
'After Request job' condition on Banner RA Agent generates error
Resolution:
Detailed Description and Symptoms

?Receive AwE-5117 error when trying to run a job with a 'After Request job' condition calling a Banner RA Agent. This is specic to when the job in question is running against a Banner RA agent. Also, the Login on the condition is set to use a different login from the one the Banner RA agent is set to use.

 


Investigation

?

Steps taken to reproduce the issue:
  1. Create a copy of TEST_MODULE called TEST_MODULE_180507.
     
  2. Created a copy of the AAPACKN (Banner RA) job called AAPACKN_180507.
     
     
  3. Created an After condition on TEST_MODULE_180507:
     
     
    AFTER
    Always True
    REQUEST Job 'AAPACKN_180507'
     
     
  4. Condition Details of Above job:
     
 
Job: AAPACKN_180507
Requestor: DARNOLD
Agent: BANNER
DB Login: BANNERFAKE2
 
When TEST_JOB_180507 is requested it generates a AwE-5117 error while trying to kick off the After Condition.


Solution

?

For Banner RA jobs the normal method of requesting the jobs to run on the Banner DB with different login credentials is to use the 'Login Override' field in the Banner tab of the job itself.

If an option on a Banner RA job needs to be overwritten, the Job Arguments field needs to be used and filled in with the xmlname for the override option and the login that needs to be used. For example, xmlBannerJobLoginId=banworx@test2