• Subject: Re: DSPJRN Discrepency - Watch Out!
  • From: John Earl <johnearl@xxxxxxxxxxxxxxx>
  • Date: Sun, 23 Jan 2000 17:31:24 -0800
  • Organization: The PowerTech Group

Kirk,

Yes, but....   it doesn't matter if the job in question is QZDASOINIT
or DSP01.  If you give the DSPJRN command a job number it should
either honor it or refuse to accept it.   Ignoring it and presenting
you with all of the jobs that match the job name is a bug.

jte

Kirk Goins wrote:
> 
> I can see why it does it... These jobs can service 100's of users per
> qzdasoinit job.
> 
> ---------------------------------
> Kirk Goins
> IBM Certified AS/400 Technical Solutions
> Pacific Information Systems - An IBM Premier Business Partner
> 503-290-2104
> kirkg@pacinfosys.com
> ---------------------------------
> 
> > -----Original Message-----
> > From: John Earl [SMTP:johnearl@400security.com]
> > Sent: Monday, January 17, 2000 3:50 PM
> > To:   MIDRANGE-L@midrange.com
> > Subject:      DSPJRN Discrepency - Watch Out!
> >
> > 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
> > +---
> +---
> | 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
> +---

--
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
+---

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].