Re: Monitor Date Conversion Fills Job Log

Thanks Scott & all.  I think what works best for me is encapsulating my
code in a service program procedure.  I only want to filter out job log
messages relating to zero dates, which are really valid (as pseudo nulls
... unfortunately real nulls have a less than seamless implementation).  If
there's other garbage I want to know about it.

Thanks, Dave

David Keck
NBTY, Inc
Phone (631) 200-5809
DavidKeck@xxxxxxxx


                                                                       
             Scott Klement                                             
             <rpg400-l@scottkl                                         
             ement.com>                                                 To
             Sent by:                  RPG programming on the AS400 /  
             rpg400-l-bounces+         iSeries <rpg400-l@xxxxxxxxxxxx> 
             davidkeck=nbty.co                                          cc
             m@xxxxxxxxxxxx                                            
                                                                   Subject
                                       Re: Monitor Date Conversion Fills
             11/23/2004 01:31          Job Log                         
             PM                                                        
                                                                       
                                                                       
             Please respond to                                         
              RPG programming                                          
              on the AS400 /                                           
                  iSeries                                              
             <rpg400-l@midrang                                         
                  e.com>                                               
                                                                       
                                                                       





Hi David,

> In populating a file with true date fields from another large file with
> YYMMDD signed numeric date fields I find that my job log fills up with
> RNX0112 messages (Date Not Valid) due to numerous Zero YYMMDD date
values.

Yeah, the MONITOR operation seriously needs improving!  In order for it to
be useful, you have to use it in conjunction with APIs to receive, remove,
promote, etc. the program message that caused the error.

(The other problem with MONITOR is that you can't really monitor for
specific messages, unless they happen to correspond to an RPG status code.
It would be awfully nice if you could specify the message IDs that you
want to trap like you can in CL.)

Anyway, you can use the QMHRCVPM API to retrieve and remove the error
message from the program queue.  (The job log is a listing of all program
queues in a job, so removing it from the program queue also removes it
from the job log.)

I wrote a programming tip on this topic that demonstrates what you're
trying to do. If you've got a Professional membership to the iSeries
Network, you can read it at the following link:
http://www.iseriesnetwork.com/article.cfm?ID=18093
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



Confidentiality Notice: This communication and attachments are intended for
the personal and confidential use of the designated recipient(s) named
above.  This communication and attachments are intended for the recipient
only.  If the reader of this message is not an intended recipient(s) or
agent of the intended recipient(s), you are hereby notified that you have
received this document in error, and that any use, review, distribution, or
copying of this message or any attachment is strictly prohibited.  If you
have received this communication in error, please notify the sender
immediately by replying to sender and deleting all copies of the
communication and attachments.  Although this E-mail and attachments  are
believed to be virus and defect free, it is the responsibility of the
recipient to ensure that the same are virus and defect free.  The sender
disclaims all responsibility for any loss or damage arising from the use of
this communication or attachment.Thank you.