| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
I just had a problem starting the AIDA server at a customer's site.
After working with the CSC, we discovered why it wasn't starting, but
I'm wondering if anyone knows the cause.
The SSP was set up as:
ALL-IN-1 Accounts:
Account for batch jobs: MANAGER
Account to receive exception reports: HOUSEKEEPING, ANOTHER
Holding account for orphan drawers: MANAGER
and when we did the MAS STA, it said there were no privileges to access
the batch queue. Turns out the job was being submitted under the
username HOUSEKEEPING, which didn't have enough privileges. Obviously
the SSP was set up properly for batch jobs to be submitted under the
username MANAGER... After giving HOUSEKEEPING privileges, it started
up.
Any ideas why this job was erroneously started under HOUSEKEEPING.
Didn't seem to be a problem for other jobs (presuming other jobs were
started from ALL-IN-1).
Thanks in advance for any help.
Rod Rehor
Minneapolis Sales Support
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4246.1 | we've seen this a few times | AIMTEC::WICKS_A | Atlanta's Most (In)famous Welshman | Thu Jun 09 1994 16:51 | 9 |
Rod,
Everything is explained in the STARS article entitled
[ALL-IN-1] V3.0: AIDA Server Will Not Start From MAS
so it shouldn't have been a surprise to anyone here at the CSC.
regards,
Andrew.D.Wicks
| |||||
| 4246.2 | Here's the fix | AIMTEC::MORABITO_P | Fri Jun 10 1994 00:22 | 61 | |
Hi Rod, The problem is that the script OA$LIB:SM_AIDA_START_SERVER.SCP uses the following to determine which account should start the AIDA Server. GET #sm_aida_batch_account = sm_policies.manager_accnt['system'] "MANAGER_ACCNT" should really be "BATCH_ACCNT". The field "MANAGER_ACCOUNT" is referenced by "Account to receive exception reports". Therefore, to fix this problem, you need to edit SM_AIDA_START_SERVER.SCP, using Customization Management. To do this, do the following: $ALLIN/USER=MANAGER CM ABE SEL NAME: SM_AIDA_START_SERVER TYPE: DO <CR> CO CM E Locate the following line: GET #sm_aida_batch_account = sm_policies.manager_accnt['system'] ^^^^^^^ Change this line to the following: GET #sm_aida_batch_account = sm_policies.batch_accnt['system'] ^^^^^ GOLD F MLA PME ML Now when SM MAS STA is executed, the batch account will be used rather than the exception report account. Paul | |||||