|
We have ordered PTF MF30222 pdid 5722999 Which IBM says will fix the problem. The steps we did was just to get us up and running today.... J. Scott Carter Programmer/Analyst e-mail: Mailto:scarter@xxxxxxxxxxx Phone: 214.583.0348 It's not the destination that counts in life it's the journey. The journey with the people we love is all that really matters. Such a simple truth so easily forgotten. |---------+-------------------------------> | | "Tom Jedrzejewicz @ | | | San Pedro" | | | <TJedrzejewicz | | | Sent by: | | | midrange-l-bounces@x| | | idrange.com | | | | | | | | | 03/24/2003 12:21 PM | | | Please respond to | | | Midrange Systems | | | Technical Discussion| | | | |---------+-------------------------------> >--------------------------------------------------------------------------------------------------------------| | | | To: <midrange-l@xxxxxxxxxxxx> | | cc: | | Subject: RE: CWBSY1008 | >--------------------------------------------------------------------------------------------------------------| I had a similar experience when upgrading a box from V4R3->V4R5->V5R1. The telnet server would not respond to requests. Dealing with the TCP and HOST servers brought no resolution. It was corrected when I put the Group PTF's that came with the latest CUM onto the system. >>> SCarter@xxxxxxxxxxx 03/24/03 10:08AM >>> We just had a similar problem this morning, upgraded to v5r2 last night. We actually had two problems. Problem One: Users could not sign on to the system, but MIS could. This turned out to be the users did not have access to the JOBD. We gave them access to the jobd and could sign on. Problem two : We could not use jdbc or odbc IBM had us endhostsvr(*file) and endhostsvr (*database) and restart several times. also had us end a couple of jobs running in qserver and qusrwrk SBS before doing strhostsvr(*file) and strhostsvr(*database) J. Scott Carter Programmer/Analyst e-mail: Mailto:scarter@xxxxxxxxxxx Phone: 214.583.0348 It's not the destination that counts in life it's the journey. The journey with the people we love is all that really matters. Such a simple truth so easily forgotten. |---------+---------------------------------> | | "Jan Rockstedt" | | | <jan.rockstedt@xxxxxxx| | | inmedia.se> | | | Sent by: | | | midrange-l-bounces@xxx| | | range.com | | | | | | | | | 03/24/2003 11:10 AM | | | Please respond to | | | Midrange Systems | | | Technical Discussion | | | | |---------+---------------------------------> > --------------------------------------------------------------------------------------------------------------| | | | To: <midrange-l@xxxxxxxxxxxx> | | cc: | | Subject: RE: CWBSY1008 | > --------------------------------------------------------------------------------------------------------------| Hi again ! The quser id not disabled >Check to see if the User QUSER is disabled. >Groetjes (Greetings) >=========================================================== >Name: Eduard van den Braken >E-mail: e.vd.braken@xxxxxxxxx >Town: Leusden -- the Netherlands >Homepage: http://home.hccnet.nl/e.vd.braken/ >=========================================================== I use V5R2M0 on the client with the leatest service pack. I also use the leatest CUM pack. >I know not what version of the client you are using, nor what service pack >you have on that client. I didn't find anything on the APARs Search. I can telnet to the as/400 from another as/400, but i can not go direct with CAE. I can ping direct from the client to the as/400 without any problem. Any other sugestion ? //Jan _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, downloading, storing or forwarding of this communication is prohibited. If you have received this communication in error, please notify us immediately via email and delete the message from your computer files and/or data base. Thank you. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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 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.