× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




On 22/11/2006, at 2:18 AM, rob@xxxxxxxxx wrote:

Here!  Here!

Don't you mean: Hear! Hear! Hmm?

Just last week a coworker was sure that he had a security limitation that
was causing him an issue with a canned software package.  It did a
deletion of a user space and then did a creation. Apparently IBM lumped
too damned many possibilities in the message for the deletion of a user
space (second level text for CPF2125 indicates that it may either be a
security failure, or it did not exist, etc - how stupid can you get?)
Now, in this case, IBM got lazy and decided to make it harder to do an
appropriate monmsg.

I'd expect this error message only if a generic name was used or a particular special value was used for the library qualifier.

When deleting a specific user space I'd expect specific error messages for each condition. That is certainly what is implied by the command help text.

I'd expect these when deleting a single user space:
        CPF2105     Object &1 in &2 type *&3 not found.
        CPF2110     Library &1 not found.
        CPF2113     Cannot allocate library &1.
        CPF2114     Cannot allocate object &1 in &2 type *&3.
        CPF2176     Library &1 damaged.
        CPF2182     Not authorized to library &1.
        CPF2189     Not authorized to object &1 in &2 type *&3.          

I'd expect these when using a generic name or library special value *ALL or *ALLUSR
        CPF2117     &4 objects type *&3 deleted. &5 objects not deleted.
        CPF2125     No objects deleted.

If one of these generic messages is sent I'd also expect the job log to show diagnostic messages for each object or library that failed. Using the message key of the generic exception it is easy to retrieve the previous diagnostic messages as long as IBM code sent them to the correct program queue.

So I don't think sending a generic message is a defect. Failing to send a proper diagnostic message or sending the diagnostic message to the wrong program queue would be a defect.

Are you sure your cow-orker is using the DLTUSRSPC command correctly?

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------




As an Amazon Associate we earn from qualifying purchases.

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-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.