I have gotten those every time I IPL or do a STRHOSTSVR
For like the last 3 years....and nothing ever has been affected.

I never worried about it much it....but am curious also if anyone knows
If it stores these routing entries somewhere and these are just "warnings"
actually.
(i.e. just trying to duplicate what is already there and it's not smart
enough to just say "Hey...I already have one...but don't worry".)



Jim Norbut
Systems Administrator
Grubb & Ellis Company
Phone   (847) 753-7620
Fax     (847) 753-9854

 -----Original Message-----
From:   Rodriguez, Jose Amable [mailto:jarodriguez@grupom.com.do]
Sent:   Friday, December 28, 2001 10:44 AM
To:     midrange-l@midrange.com
Subject:        STRHOSTSVR Errors

Hello all,

        I have the following error message when I issue the STRHOSTSVR
command on our new 820 (V5R1).

Does anyone have any idea what all this means and how I can go ahead and
correct.


I took a look at the QSYSWRK subsystem and the routing entries, but I see no
duplicates as the error indicates.


Here is the job log:


 7 > STRHOSTSVR SERVER(*ALL) RQDPCL(*TCP)

     Routing entry sequence number 2536 already exists.

     Compare value conflicts with routing entry 2536.

     Job 003159/QUSER/QZSCSRVSD submitted to job queue QSYSNOMAX in library

       QSYS.

     Routing entry sequence number 2537 already exists.

     Compare value conflicts with routing entry 2537.

     Job 003160/QUSER/QZHQSRVD submitted to job queue QSYSNOMAX in library

       QSYS.

     Routing entry sequence number 2538 already exists.

     Compare value conflicts with routing entry 2538.

     Job 003161/QUSER/QNPSERVD submitted to job queue QSYSNOMAX in library

       QSYS.

     Routing entry sequence number 2539 already exists.

     Compare value conflicts with routing entry 2539.

     Job 003162/QUSER/QZRCSRVSD submitted to job queue QSYSNOMAX in library

       QSYS.

     Routing entry sequence number 2540 already exists.

     Compare value conflicts with routing entry 2540.

     Job 003163/QUSER/QZSOSGND submitted to job queue QSYSNOMAX in library

       QSYS.

     Routing entry sequence number 200 already exists.

     Compare value conflicts with routing entry 200.

     Job 003164/QUSER/QPWFSERVSD submitted to job queue QPWFSERVER in
library
       QSYS.

     Routing entry sequence number 600 already exists.

     Compare value conflicts with routing entry 600.

     Job 003165/QUSER/QZDASRVSD submitted to job queue QPWFSERVER in library

       QSYS.

     Routing entry sequence number 2541 already exists.

     Job 003166/QUSER/QZSOSMAPD submitted to job queue QSYSNOMAX in library

       QSYS.

 7 > DSPJOB



Thank you,

-jose a.

-----Original Message-----
From: jt [mailto:jt@ee.net]
Sent: Friday, December 28, 2001 12:38 PM
To: midrange-l@midrange.com
Subject: RE: 18 CPW? (was RE: V5R1M0 and you...)


I'm having trouble reading between the lines, here...

LOL...!

| -----Original Message-----
| From: midrange-l-admin@midrange.com
| [mailto:midrange-l-admin@midrange.com]On Behalf Of Adam Lang
| Sent: Friday, December 28, 2001 11:26 AM
| To: midrange-l@midrange.com
| Subject: Re: 18 CPW? (was RE: V5R1M0 and you...)
|
|
| This is a multi-part message in MIME format.
| --
| here is what Andrew sent me.
|
| Adam Lang
| Systems Engineer
| Rutgers Casualty Insurance Company
| http://www.rutgersinsurance.com
| ----- Original Message -----
| From: "jt" <jt@ee.net>
| To: <midrange-l@midrange.com>
| Sent: Thursday, December 27, 2001 10:04 PM
| Subject: RE: 18 CPW? (was RE: V5R1M0 and you...)
|
|
| > Andrew,
| >
| > I'd be EXTREMELY INTERESTED to hear details on this, also.
| Especially if
| > that wasn't a typo, and you meant 1070...
| >
| > I also wonder, like Adam, what kind of stipulations they put on the use.
| > And how you mean "ALL the software"...  (Probably doesn't include
| Sametime,
| > by any chance...?)
| >
| > TIA
| >
| > jt
| >
| > | -----Original Message-----
| > | From: midrange-l-admin@midrange.com
| > | [mailto:midrange-l-admin@midrange.com]On Behalf Of Adam Lang
| > | Sent: Thursday, December 27, 2001 1:32 PM
| > | To: midrange-l@midrange.com
| > | Subject: Re: 18 CPW? (was RE: V5R1M0 and you...)
| > | Importance: High
| > |
| > |
| > | Ok, so I wouldn't see my electric bill jump $100 a month?
| > |
| > | I would be SOOOO cool having an AS/400 in my house and
| running Linux on
| it
| > | too. :)
| > |
| > | What does "one" person mean?  I can set it up in my house and only I
| > | administer/install/code on it, but can I use it as a webserver for
| outside
| > | use for non profit stuff?
| > |
| > | If you got a link to IBM that details that, I would like to look
| > | into it...
| > | mighty interesting stuff. :)
| > |
| > | Adam Lang
| > | Systems Engineer
| > | Rutgers Casualty Insurance Company
| > | http://www.rutgersinsurance.com

_______________________________________________
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-Ups:

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.