Why do some late jobs not receive message SCNP-11?
The SCNP-11 JOB xxxxxxxx (nnnn) SYS=xxxxxxxx *** IS LATE *** message is produced for jobs that are late in CA 7. If a job becomes late when it is in the REQUEST queue, a SCNP-11 message is produced. If the job is in the READY or ACTIVE queue when it becomes late, the SCNP-11 message may or may not be issued, depending on the value of REPROMPT=nn. If REPROMPT=0 is specified on the SCHEDULE statement in the Initialization File (pointed to by the UCC7IN DD statement in the CA 7 online procedure) re-prompting is turned off. This also turns off the prompt for jobs that 'go late' in any other queue except the REQUEST queue. Note also that the REPROMPT=nn value can be changed with the SSCAN command (SSCAN,REPRMPT=nn) and can be displayed by issuing the SSCAN command with no keywords.
Also note that if LATEPROMPT=LATE is specified on the OPTIONS statement in the Initialization file, any job with PROMPT=N specified on the DB.1 Job Definition panel will never generate the SCNP-11 message in any queue.
Additionally, the Automated Recovery Facility (ARF) late type exception conditions rely on this prompting. If the SCNP-11 message is not generated, the LATE condition is not recognized by ARF and the ARFSET rule will not be invoked. Also note that for ARF type LA checking, the late condition is only recognized if the SCNP-11 message is generated while the job is in the REQUEST queue. The ARFSET rule will not be invoked if the SCNP-11 message is generated while the job is in the READY or ACTIVE queue.
CA 7 Message Guide for the SCNP-11 message.
CA 7 Systems Programmer Guide for Initialization File statements and keywords.
CA 7 Database Maintenance Guide for ARF usage.
CA 7 Command Reference Guide for SSCAN commands and keywords.
Also see technical document TEC442028 for information on how CA 7 calculates late conditions for jobs.
As always, please contact CA Technologies support for CA 7 if you have further questions.