|
Since the subsystem itself is allocated when active, "another job (in
a different subsystem)" might better be implemented using a loop on a
failed request to allocate the *SBSD object for exclusive use [with a
long WAIT() specified to limit the polling effect].?
Similar to what Dennis describes, I had modified the CPF0927 to be
"alertable" [alert capable] and then to either add a data queue entry
or
generate a SNMP trap; using Alert Filters and Actions from GO CMDALR
and
activating with CHGMSGD CPF0927 ALROPT(*IMMED 1)
Regards, Chuck
On 2/2/11 10:45 AM, Albert York wrote:
You could have a job run in the subsystem which exclusively allocates--
a data area and another job (in a different subsystem) which waits
until that data area is free, which will happen when the first job
ends because the subsystem has ended.
something like this:
PGM
ALCOBJ OBJ((MYDTAARA *DTAARA *EXCL))
SBMJOB CMD(CALL PGM(MONITORJOB)) JOB(MONITOR) +
JOBQ(OTHERJOBQ)
WAIT:
DLYJOB DLY(999999)
GOTO CMDLBL(WAIT)
ENDPGM
On Wed, Feb 2, 2011 at 10:09 AM, Dennis wrote:
I have done this in the past by monitoring QHST for the CPF0995
and/or CPF0927 messages associated with Subsystem end. Of course,
such monitors need to run in a different subsystem from the one
that has your interest.
"Jason Abreu"<jason.abreu@xxxxxxxxxxxxxxxxxxxx> wrote:
Thank you all for the very quick response about the ADDAJE
command and the note about modifying the JOBD.
Any notes about running a job when a subsystem is ended?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.