|
The only thing I think looks odd, but I am not sure if it matters completely is that after your .MBR at the end, I have another "parm" - mine looks like the following: CALL PGM(QHTTPSVR/QZHBHTTP) PARM('1' 'AS400LIVE' '-uiMin' '5' '-uiMax' '20 ' '-cEAMap' '*CCSID' '-cAEMap' '*CCSID' '-uiCCSID' '819' '-r' '/QSYS.LIB/Q USRSYS.LIB/QATMHTTPC.FILE/AS400LIVE.MBR' '-minat' '5' '-maxat' '20') What exact message are you getting - you only mention that you receive a wrong status, do you have a message log, error screen or some such thing??? As for spool files by user QTHHHTTP, you do mean QTMHHTTP don't you??? I have found that the job logs or even the program dumps do not always go to that user profile, therefore you should check your outqs (QEZDEBUG and QEZJOBLOG) for any recent listings. Unfortunately (depending on your point of view; I do not currently have any logs to see which user profile they have come up under; but I thought it was qpgmr or qsysopr. HTH Mark -----Original Message----- From: web400-admin@midrange.com [mailto:web400-admin@midrange.com]On Behalf Of Radoslaw Nowicki Sent: Tuesday, January 29, 2002 5:46 AM To: web400@midrange.com Subject: [WEB400] CNDW status of QHTTPSVR Hi *all my problem is that the qhttpsvr recive wrong status CNDW. I am sure there must be somethig I have missed... This is what I allredy checked: 1. QTMHHTTP is *Enabled 2. The firts job of QHTTPSVR (that one with CNDW status) looks ok (imo) ">> CALL PGM(QHTTPSVR/QZHBHTTP) PARM('1' 'MAGAZYN' '-uiMin' '10' '-uiMax' '40' '-cEAMap' '*CCSID' '-cAEMap' '*CCSID' '-uiCCSID' '819' '-r' '/QSYS.LIB/QU SRSYS.LIB/QATMHTTPC.FILE/MAGAZYN.MBR') " 3. There are no spool files generated by QTHHHTTP user 4. The QSYSOPR message queue sais only that the server ist started Can anybody help me? Radek
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.