X-no-Archive:yes
I am working on a job to clean up sets of old spool files, using
SPOOLF;DELETE;SHOW;SELEQ=[various arguments]. I thought that we might not
want to automatically delete jobs that had aborted, at least not as part of
this job, so I included JOBABORT=FALSE in the select equations. Testing
these with LISTSPF, I got to our SMBMON jobs, which are "aborted by system
management" before the backup, using ABORTJOB. I would think that ABORTJOB
would set JOBABORT to true. Nevertheless, these stdlists listed with
LISTSPF O@;SELEQ=[JOBNAME=?MBMON AND OWNER=MGR.SAMBA AND JOBABORT=FALSE]

Am I just misunderstanding the significance of JOBABORT? Wouldn't
JOBABORT=TRUE for any aborted job, even those "aborted by system
management"? Or is this only true for jobs that end with "REMAINDER OF JOB
FLUSHED"? A search of the LaserROM was not very instructive.

A call to HPRC tells me that there was an SR for this issue, SR 1653043398,
as an enhancement request (!), and that it was closed February 2, 2000.
Another SR 5003358796 explained that this is a feature, not a bug, as some
customers depend on jobs aborted by system management NOT having
JOBABORT=TRUE. I cannot find where the manual does not state that this
should or should not be the case. The manuals do state under ABORTJOB:
"Although the job/session is abnormally terminated, log records are issued,
and CPU-times and connect-times are updated.".