Tweet
Hi, Any thoughts on why jobs (admin, default) under sbs qhttpsvr, would not stay active? The job starts but ends with a reason code 0. Thanks
-
-
HTTP SERVER
Does the job log give you any clue? If you don't have a job log for it, since it was a normal end, you might want to change the job description to keep the job logs, until you figure out what the problem is anyway. Regards, Jim Langston -
HTTP SERVER
Hi Jamie, I did change the job description, however, there are no logs generated. This in itself, is not normal. Therefore, I am not sure why the jobs would not stay active. ThanksComment
-
HTTP SERVER
There should be job logs under the QTMHHTTP user profile for the jobs that ended abnormally. If anything, you could start the job, get into it write away (using WRKACTJOB JOB(instance_name), do a 5 next to it, and then view the job log before it bombs. Look at spooled files under QTMHHTTP first.Comment
-
HTTP SERVER
There can be many reason why the instance did not stay up, like port conflict, SSL is enable but can not find the keyring file, or ... The best way to determine the exact problem is to start the instance as the following command: STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN '-vv') After the instance ended, display spool file by WRKSPLF with QTMHHTTP as the user. From there you should look for the last two spool files - one is the job log and the other one is QPZHBTRC file, which is the HTTP server trace and it has a lot of detail info. These two reports should tell you what is the cause of the problem. ShawnComment
Comment