Actually, I think I know how to do that:
// EXEC REXXBAT,PARM='DCDOWN'
So is it your impression that PCS variables and IBM variables are
totally different despite the fact that they both begin with an ampersand?
I'll have to do some experimenting. Thanks, Bill!
- Tom.
At 10:40 AM 6/14/2007, you wrote:
On the PCS menu screen option V takes you to variable where you
define it. I used &DATACOM. Then I defined the message and run the
REXX IMOD DCUP which looks like this
/**/
call $pvar datacom dcomup
exit
Then in the event I put a Y next to variable and defined it like this
VARIABLE NAME COND VARIABLE VALUE
_ &DATACOM EQ ===> DCOMUP
When the Datacom down message is seen it runs IMOD DCDOWN
/**/
call $pvar datacom dcomdn
exit
I have not tried to use a REXX IMOD from JCL so I am not sure on the
syntax. Maybe Angie will call you.
---- Tom Cluster <[EMAIL PROTECTED]> wrote:
>
> Hi, Bill,
>
> I like this approach. I've not worked with PCS variables before. Is
> this a "global variable?" Can you give me any idea what the commands
> are like to set them? Is there an AR command? If I want to set it
> in a FAQS message element would I just issue an AR command to do
> it? Or would I trigger an imod which would do it?
>
> I get the feeling from what I've seen that PCS variables have an
> ampersand in the first position, just like IBM variables. is there
> any relationship between them?
>
> Thanks.
>
> - Tom.
>
> At 10:11 AM 6/14/2007, you wrote:
> >Tom,
> >
> >You could define a variable and set it instead of demanding the
> >event then have the event set to run at 8AM every day but be
> >dependent on the variable being set. You would have to set the
> >variable off at the end of the run for that day.
> >
> >I have several jobs that are dependent on Datacom being active so I
> >defined a variable that is set on when the Datacom active message is
> >recognized and set off when the shutdown message occurs.
> >
> >---- <[EMAIL PROTECTED]> wrote:
> > >
> > > I have a FAQS/ASO message element which detects a certain condition a
> > > issues a DEMAND command to PCS. I wish the demanded job to run at
> > > the next 8 AM. In other words, if it's before midnight I want it to
> > > run at 8 AM the next day, and if it's after midnight I wish it to run
> > > at 8 AM the same day. The problem is that if I put in an early time
> > > of 32:00 it will work fine if demanded before midnight, but if
> > > demanded after midnight it will run at 8 AM the next day, not the
> > > same day - 24 hours late.
> > >
> > > I understand why this is, and in the end I may do it another way -
> > > for example, making the run occur every day at 8 AM and doing
> > > something within the run to branch to EOJ if the message element
> > > hadn't "sprung." But I'm wondering if anyone has a way to make
> > > FAQS/PCS (CA version) schedule it the way I wish it to be scheduled -
> > > that is, the way I described it in the first paragraph.
> > >
> > > - Tom.
> > >
> > > Tom Cluster
> > > County of Sonoma
> > > Santa Rosa, CA
> > > (707) 565-3384 (Tuesdays and Wednesdays only)
> > >
> > >
> > >
> >
> >--
> >Bill Dodge
> >email: [EMAIL PROTECTED]
> >Phone: (703)627-2455
> >
> >"If you don't know where you are going, any road will take you there."
> >Lewis Carroll
> >"If you don't know where you are, a map won't help" Unknown
>
> Tom Cluster
> County of Sonoma
> Santa Rosa, CA
> (707) 565-3384 (Tuesdays and Wednesdays only)
>
>
>
--
Bill Dodge
email: [EMAIL PROTECTED]
Phone: (703)627-2455
"If you don't know where you are going, any road will take you there."
Lewis Carroll
"If you don't know where you are, a map won't help" Unknown
Tom Cluster
County of Sonoma
Santa Rosa, CA
(707) 565-3384 (Tuesdays and Wednesdays only)
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
