× 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.



If you prompt the command, put the cursor on the heading and press F1,
it'll show you what messages this command will throw.




Mark


Mark Walter
Sr. Programmer/Analyst
Hanover Wire Cloth a div of CCX, Inc.
mwalter@hanoverwire.com
http://www.hanoverwire.com
717.637.3795 Ext.3040



                    "Andy
                    Nolen-Parkhouse"           To:     <midrange-l@midrange.com>
                    <aparkhouse@mediaon        cc:
                    e.net>                     Subject:     RE: Command Message 
Ids
                    Sent by:
                    midrange-l-admin@mi
                    drange.com


                    12/14/01 10:20 AM
                    Please respond to
                    midrange-l






Dare,

The CL Reference Manual for your release will have a section for every
command labeled 'Error Messages for cmdname'.  Is this what you're
looking for?  What error messages (and their Ids) can be issued as a
result of this command.  What do I monitor for?

Andy Nolen-Parkhouse

> -----Original Message-----
> From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]
> On Behalf Of Dare
> Sent: Friday, December 14, 2001 10:10 AM
> To: MIDRANGE-L@midrange.com
> Subject: Command Message Ids
>
> This is a multi-part message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> Hi guys,
>
> Is there a way to display or find out what MESSAGE IDs are attached to
a
> COMMAND.  I'm on V4R5M0.
>
> Thanks,
>
> Dare
> --
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.







As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.