DSPJRN Discrepency - Watch Out!

[John Earl <johnearl@xxxxxxxxxxxxxxx>]

If you do a DSPJRN command against a job, lets say QZDASOINIT, and
specify the Job Name and the Job Number, you would expect that you'd
only get records that match that particular Job Name and Number...  
Not True!  You'll get all matches for QZDASOINIT (potentially
hundreds).  If you're not carefull enough to check the job name on
each journal entry you'll likely be fooled into thinking all of those
entries were generaed by that one job.  

The Journal Managemnet folks at IBM claim that this is working as it
should, and that if you specify user name as well, then you will get
the subset you are looking for (true).  They will search their
database by Job or Job/User or Job/User/Number but not by
Job/*n/Number (as other OS/400 interfaces will).

You would think that if Job/*N/Number was not allowed, that the
command validity checker would flag this as an error, but it doesn't. 
:(  

Just thought some of you might like to know.

jte


--
John Earl                                          
johnearl@powertechgroup.com
The PowerTech Group                        206-575-0711
PowerLock Network Security              www.400security.com
The 400 School                                www.400school.com
--
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---