RE: Autoreply vs. Operator Intervention on CPF5034

[CWilt@xxxxxxxxxxxx]

Take a look at the INQMSGRPY parameter of the SBMJOB command.

HTH,
Charles


> -----Original Message-----
> From: Kaynor@xxxxxxx [mailto:Kaynor@xxxxxxx]
> Sent: Wednesday, March 24, 2004 11:17 PM
> To: MIDRANGE-L@xxxxxxxxxxxx
> Subject: Autoreply vs. Operator Intervention on CPF5034
> 
> 
> In order to enforce a new business data integrity rule, I 
> created a Logical 
> File with OMIT criteria and UNIQUE keyword.   Its maintenance 
> is *IMMED.
> 
> I was surprised to find that a batch process adding records 
> to this file did 
> not stop for operator intervention when this Logical File 
> restriction failed.  
>  The database updated failed, but the joblog shows two errors:   
>        1) The severity 10 CPF5009 "Duplicate record key in 
> member" message 
> which does not take a reply; and 
>        2) The severity 30 CPF5034 "Duplicate key on access 
> path" message.
> 
> The CPF5034 message appears to be shipped for V5R2 with a 
> default of "C - 
> Cancel."   
> 
> The DSPMSGD help text implies that "autoreply" is triggered 
> by the receiver 
> of the message, but I can't find documentation of how a job 
> or a program turns 
> on autoreply.  Even a call to IBM support has not provided an 
> answer.    I'm 
> probably looking under the wrong keyword.    
> 
> Can someone point me to how autoreply vs. operator intervention is 
> determined?   Basically, I'd like this error to require 
> operator intervention in certain 
> jobs.   We have other, similar cases as well.
> 
> TIA,
> --Chapin Kaynor
>     Vermont
> 
> 
> _______________________________________________
> 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.
>