Author Topic: SB+ and Redback Phantoms  (Read 4505 times)

precisonline

  • President
  • Administrator
  • Rock Star
  • *****
  • Posts: 1612
    • Precision Solutions
SB+ and Redback Phantoms
« on: June 21, 2007, 08:50:57 AM »
In a recent Schedule Definition installation, we ran into all sorts of confusion regarding having a single account that can run both SB+ and Redback phantoms.  First, some background:

SB+ Job Schedule phantoms need SB.LOGIN to be started in the LOGIN proc/paragraph.  Redback phantoms need WW.SB.RB to be started in the LOGIN proc/paragraph.  Obviously, both cannot be started in the same LOGIN.  We first tested @USER.TYPE under the assumption that SB+ phantoms set @USER.TYPE = 1 and RB phantoms set @USER.TYPE to 0, using this paragraph:

PA
IF @USER.TYPE = 1 THEN SB.LOGIN
WW.SB.RB

However, for some reason this caused SB.LOGIN to be invoked for both SB+ and RB tasks.  Yes, WW.SB.RB invokes SB.LOGIN, but it's supposed to sense when it's a RB job and just drop to TCL.  This made us believe that @USER.TYPE was 1 for RB jobs (which we have since learned it is 0.)  In this configuration however, rather than dropping to TCL, WW.SB.RB was running SB.LOGIN for some unexplained reason.  In the end then, we found this to be the golden ticket:

PA
IF @USER.TYPE = 1 THEN GO PHAN
WW.SB.RB
GO EXIT
PHAN:
SB.LOGIN
EXIT:

This is basically the same as before but with a lot more lines and this one works.  SB.LOGIN logs the port off when its done so there really isn't much difference between the two variations, except for one works and the other doesn't.

FYI
-Kevin
Accidents "happen"; success, however, is planned and executed.