RE: Killing off all jobs with a given jobname from CL

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Elvis Budimlic
Sent: Tuesday, May 05, 2009 1:41 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Killing off all jobs with a given jobname from CL

I'd stick with the API, even in CL. APIs are much easier to handle with

new CL support.

That said, something REALLY quick and dirty might be:

WRKACTJOB OUTPUT(*PRINT) JOB(<desired job name, generics possible>)
CRTPF QTEMP/OUTPUT RCDLEN(132)
CPYSPLF FILE(QPDSPAJB) TOFILE(QTEMP/OUTPUT) SPLNBR(*LAST)
RCVF ......

Hth, Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com


-----Original Message-----
Subject: Killing off all jobs with a given jobname from CL

We have a situation in which we need to unconditionally and immediately
end all jobs (regardless of status) with a specified name, without user
intervention (it will be going into an end-of-day process), and
preferably without having to end a subsystem.

Obviously, I could do it from a HLL, calling QUSLJOB, but if there's a
way to do it from CL, that would be quicker and easier.

I've done similar things with terminal sessions, by listing all devices
fitting a given naming convention, varying them off, and varying them
back on, but I don't see anything comparable for jobs.

--
JHHL
--



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

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.