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



This is a multi-part message in MIME format.
--
--
[ Picked text/plain from multipart/alternative ]
I had this problem on my LPAR last week and I used the CHGLICINF for 5722XW1 
(5050) to chanage the usage limit to *NOMAX. The base product (5050) doesn't 
have a LICKEY,
only feature 5101 has a LICKEY.

Dave Snyder wrote:

> We ended up getting this message eliminated by performing the QSYS/STRHOSTSVR 
>SERVER(*ALL) command. We were told not to use this anymore but I guess that 
>was bad info.
>
> We are now periodically getting the following message:  Message . . . . :   
>Usage limit exceeded - operator action required.
>  Cause . . . . . :   The usage limit for product 5722XW1, license term V5,
>    feature 5050 has been exceeded. License user *JOB for job
>    855248/QUSER/QZSCSRVS was added with 1 uses. The system operator has been
>    notified.
>
> Not sure what this is for. The product is: 5722XW1  V5        5050    Client 
>Access/400 Windows Family Base  and we did not receive a license for this.
> We do have a *NOMAX for product: 5722XW1  V5R1M0    5101    Client Access/400 
>Windows Family Option 1
>
> What is the difference?
>
> Dave
>
> >>> <rob@dekko.com> 9/23/02 1:35:32 PM >>>
> This is a multipart message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> Has anyone actually followed this document and have it work?  I am
> thinking of doing so.
>
> What we've done with the users is upgrade their Client Access.  Either put
> on V5R2 and the latest service pack, or put on the latest service pack for
> the version of Client Access they were running.  The help desk is really
> scrambling on this today after upgrading the 840 12 way this weekend.  I
> told them several months ago this would happen.
>
> We have one plant that is a little torqued.  Despite numerous urgings to
> get the heck off their old DOS based PC's and do barcoding from their BPCS
> application like the rest of our plants they haven't.  Now these PC's are
> failing.  The QuickBasic programs are returning bad values from shared
> folders.  However DIR and other DOS commands return the correct values.
> VP of IS - fishing in Wisconsin
> Chief of development - backpacking in Appalachia
> Guy who wrote the PC application years ago - something like 'they were
> warned...'
> System Analyst for that division - 1 day vacation day
>
> I'll see what the lead analyst wants to do...
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
> bdietz@3x.com
> Sent by: midrange-l-admin@midrange.com
> 09/22/2002 02:52 PM
> Please respond to midrange-l
>
>         To:     midrange-l@midrange.com
>         cc:
>         Fax to:
>         Subject:        Re: CWBUNPLA - HELP
>
> I found this:
> 
>http://www-1.ibm.com/support/docview.wss?rs=0&org=as400&doc=B03C60533D594BEA86256A1D0076ABF7
>
> Not much help.  Do you see anything in the joblog of the any of the server
> jobs QZ*.
>
> -------------------------
>  Bryan Dietz
> 3X Corporation
> 614-410-9205
>
> "Dave Snyder" <dsnyder@blcnet.com>
> Sent by: midrange-l-admin@midrange.com
> 09/22/2002 02:03 PM
> Please respond to midrange-l
>
>         To:     midrange-l@midrange.com
>         cc:
>         Subject:        CWBUNPLA - HELP
>
> We just upgraded to V5R1 from V4R5. We are now getting the "CWBUNPLA Error
> occurred while retrieving usage information for DSNYDER on 10.100.4.4"
> error message when connecting to the AS400 via Client Access Express. Any
> clue as to what this message is about and what to do about it?
> Dave
>
> _______________________________________________
> 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.
>
> _______________________________________________
> 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.
--
Content-Description: Card for Jeffry Kennedy

[ jkennedy.vcf of type text/x-vcard deleted ]
--



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.